Vendor SW release for 3GPP E-UTRAN features

Vendor 3GPP
SW SW REL
release for Feature
in which Vendor IDEA functionality Applicabilit
which
SN Feature No. Feature Name this Basic/Op y ( Per Status
this Grouping
functio tional Cell / Per
feature nality is eNB )
is address
availabl
e ed
1 ZLF31-00-001 System Compliance for 3GPP E-UTRAN R8 V2.1 R8 Basic System ComplianceeNodeB on
2 ZLF31-00-002 System Improvements for 3GPP E-UTRAN R9 V2.2 R9 Basic System ComplianceeNodeB on
3 ZLF31-00-003 System Improvements for 3GPP E-UTRAN R10 LR14 R10 Basic System ComplianceeNodeB on
4 ZLF31-00-004 E-UTRAN Interfaces V2.1 R8/R9 Basic System ComplianceeNodeB on
5 ZLF31-00-005 Radio Channels(except EMBMS Channels) V2.1 R8/R9 Basic System ComplianceeNodeB on
6 ZLF31-00-006 Support UE Category 1~3 V2.1 R8 Basic System ComplianceeNodeB #N/A
7 ZLF31-00-007 Support UE Category 4 LR12.2 R8/R9 Optional System ComplianceCell on
8 ZLF31-00-009 Radio Channels(EMBMS Channels) LR15 R10 Optional System Compliancecell of
9 ZLF31-00-010 Support UE category 6 LR14 R10 Optional System ComplianceCell on

10 ZLF31-01-001 10MHz,20MHz V2.1 R8/R9 Optional LTE Bandwidth cell on
11 ZLF31-01-002 5MHz,15MHz V2.1 R8/R9 Basic LTE Bandwidth cell on
12 ZLF31-01-003 3MHz LR13.1 R8/R9 Optional LTE Bandwidth cell of
13 ZLF31-01-004 1.4MHz LR14 R8/R9 Optional LTE Bandwidth cell of
14 ZLF31-02-001 Peak Data Rate/cell(DL/UL): 100Mbps/50Mbps V2.1 R8/R9 Basic System Performanccell on
15 ZLF31-02-002 Peak Data Rate/cell(DL/UL): 150Mbps/50Mbps V2.1 R8/R9 Basic System Performanccell on
16 ZLF31-03-001 120KM/H V2.1 R8/R9 Basic High Speed eNodeB on
17 ZLF31-03-002 350KM/H LR12.2 R8/R9 Optional High Speed eNodeB OFF
18 ZLF31-04-001 15km V2.1 R8/R9 Basic Coverage eNodeB on

19 ZLF31-04-002 40km V2.2 R8/R9 Optional Coverage cell OFF
on
20 ZLF31-05-001 SRB1 and SRB2 for DCCH + 4 DRB Combination V2.1 R8/R9 Basic
Services and Radio Access Bearers
Cell
#N/A
SRB1 and SRB2 for DCCH + 8 DRB Combination LR12.1 R8/R9 Optional on
21 ZLF31-05-002 Services and Radio Access Bearers
Cell
#N/A
22 ZLF31-05-003 Location Service(CID, AGNSS) LR15 R8/R9 Optional Location Service Cell on
23 ZLF31-05-005 eMBMS LR15 R10 Optional EMBMS eNodeB OFF
24 ZLF31-05-008 Emergency Call LR13.1 R9 Basic Services and Radio cell OFF
25 ZLF31-05-011 System Load based Dynamic AC Barring LR15 R10 Optional Services and Radio cell of
26 ZLF31-05-013 Location Service(ECID) LR15 R9 Optional Location Service Cell of
27 ZLF31-06-001 System Information Broadcasting V2.1 R8/R9 Basic Connection Manag eNodeB on
28 ZLF31-06-002 Paging V2.1 R8/R9 Basic Connection Manag eNodeB on
29 ZLF31-06-003 RRC Connection Management V2.1 R8/R9 Basic Connection Manag eNodeB on
30 ZLF31-06-004 NAS Signaling Transfer V2.1 R8/R9 Basic Connection Manag eNodeB on
31 ZLF31-06-005 UE Context Management V2.1 R8/R9 Basic Connection Manag eNodeB on
32 ZLF31-06-006 UE Capability Enquiry V2.1 R8/R9 Basic Connection Manag eNodeB on
Connection on
33 ZLF31-06-007 Radio Access Bearer Management V2.1 R8/R9 Basic eNodeB
Management #N/A
34 ZLF31-06-008 S1 Interface Management V2.1 R8/R9 Basic Connection Manag eNodeB on
35 ZLF31-06-009 X2 Interface Management V2.1 R8/R9 Basic Connection Manag eNodeB on
36 ZLF31-06-010 S1-Flex V2.2 R8/R9 Basic Connection Manag eNodeB on
37 ZLF31-06-011 Context Fetch LR13.2 R8/R9 Optional Connection Manag eNodeB on
38 ZLF31-06-012 LTE State Transition LR14 R8/R9 Optional Connection Manag Cell on
39 ZLF31-07-001 Intra-LTE Cell Selection and Reselection V2.1 R8/R9 Basic Mobility Managementcell on
40 ZLF31-07-002 Intra-LTE Redirection V2.1 R8/R9 Basic Mobility Managementcell of
41 ZLF31-07-003 Intra-LTE Intra Frequency HO V2.1 R8/R9 Basic Mobility Managementcell on
42 ZLF31-07-004 LTE->GERAN Cell Reselection V2.1 R8/R9 Basic Mobility Managementcell on
Mobility on
43 ZLF31-07-005 LTE->GERAN Redirection V2.1 R8/R9 Basic cell
Management #N/A
44 ZLF31-07-006 LTE->UTRAN Cell Reselection V2.1 R8/R9 Basic Mobility Managementcell on
Mobility on
45 ZLF31-07-007 LTE->UTRAN Redirection V2.1 R8/R9 Basic cell
Management #N/A
46 ZLF31-07-008 LTE-1xRTT Cell Reselection V2.1 R8/R9 OptionalMobility Managementcell of
47 ZLF31-07-010 LTE->eHRPD Cell Reselection V2.1 R8/R9 OptionalMobility Managementcell of
48 ZLF31-07-011 LTE->eHRPD Redirection V2.1 R8/R9 OptionalMobility Managementcell of
49 ZLF31-07-012 Intra-LTE Inter Frequency HO V2.1 R8/R9 Basic Mobility Managementcell of
50 ZLF31-07-013 LTE->GERAN CCO without NACC V2.1 R8/R9 OptionalMobility ManagementCell of

51 ZLF31-07-014 LTE->GERAN CCO with NACC V2.1 R8/R9 OptionalMobility ManagementCell OFF
52 ZLF31-07-015 LTE->UTRAN PS Handover V2.1 R8/R9 Basic Mobility ManagementCell of
53 ZLF31-07-016 UTRAN->LTE PS Handover V2.2 R8/R9 Basic Mobility ManagementCell of
54 ZLF31-07-017 LTE->GERAN PS Handover LR15 R8/R9 OptionalMobility Managementcell of

55 ZLF31-07-018 GERAN->LTE PS Handover LR15 R8/R9 OptionalMobility Managementcell of
56 ZLF31-07-019 LTE->eHRPD PS Optimized Handover LR14 R8/R9 OptionalMobility Managementcell of
57 ZLF31-07-020 LTE->UTRAN SRVCC LR12.2 R8/R9 OptionalMobility Managementcell of
58 ZLF31-07-021 LTE->GERAN SRVCC LR14 R8/R9 OptionalMobility Managementcell of
Mobility on
59 ZLF31-07-023 CSFB to UTRAN V2.2 R8/R9 Basic Cell
Management #N/A
Mobility on
60 ZLF31-07-024 CSFB to GERAN V2.2 R8/R9 Optional Cell
Management
Mobility
60 ZLF31-07-024 CSFB to GERAN V2.2 R8/R9 Optional Cell
Management #N/A
61 ZLF31-07-025 CSFB to 1xRTT LR14 R8/R9 OptionalMobility Managementcell of
62 ZLF31-07-026 Subscription Based Mobility Management LR12.2 R8/R9 OptionalMobility ManagementCell OFF
63 ZLF31-07-027 LAI enabled CSFB Enhancement LR14 R10 OptionalMobility ManagementCell OFF
64 ZLF31-07-028 Mobility with TDD network LR12.2 R8/R9 OptionalMobility Managementcell of
65 ZLF31-07-033 Service aware IRAT Handover management LR14 R8/R9 OptionalMobility ManagementCell of
66 ZLF31-08-001 Radio Admission Control V2.1 R8/R9 Basic

Radio Resource Management
cell on
67 ZLF31-08-004 Congestion Control V2.1 R8/R9 Basic

cell of
of
Radio Resource
68 ZLF31-08-005 Intra-LTE Load Balancing V2.2 R8/R9 Basic cell
Management
#N/A
69 ZLF31-08-006 IRAT L->U Load Balancing LR13.1 R8/R9 Optional

Cell of
70 ZLF31-08-007 ECN LR15 R9 Optional

Cell of
71 ZLF31-08-008 LTE Load Control V2.2 N/A Basic

cell of
72 ZLF31-08-010 IRAT U->L Load Balancing LR15 R10 Optional

Cell of
73 ZLF31-08-011 VOIP Admission Control Enhancement LR15 R10 Optional

cell on
74 ZLF31-09-001 Standard QCI (1~9) V2.1 N/A Basic QoS Management cell #N/A
75 ZLF31-09-002 Extended QCI LR13.1 R8/R9 Optional QoS Management Cell on
76 ZLF31-09-003 GBR service rate downsizing LR14 R10 Optional QoS Management cell OFF
77 ZLF31-10-001 MAC PDU and Functions V2.1 R8/R9 Basic User Plane Process cell on
78 ZLF31-10-002 RLC PDU and Functions V2.1 R8/R9 Basic User Plane Process cell on
79 ZLF31-10-003 PDCP PDU and Functions V2.1 R8/R9 Basic User Plane Process cell on
80 ZLF31-10-004 Header Compression Profile 0x0000 V2.2 R8/R9 Basic User Plane Process Cell on
81 ZLF31-10-005 Header Compression Profile 0x0001 V2.2 R8/R9 Basic User Plane Process Cell on
82 ZLF31-10-006 Header Compression Profile 0x0002 V2.2 R8/R9 Optional User Plane Process Cell of
83 ZLF31-10-007 Header Compression Profile 0x0004 V2.2 R8/R9 Optional User Plane Process Cell of
84 ZLF31-10-008 Header Compression Profile 0x0006 LR13.1 R8/R9 Optional User Plane Process Cell of
85 ZLF31-10-009 TCP Optimization LR13.1 R8/R9 Optional User Plane Process cell on
86 ZLF31-11-001 Reserved Mode V2.1 R8/R9 Basic Integrity check cell of
87 ZLF31-11-002 128-EIA1 V2.1 R8/R9 Basic Integrity check cell on
88 ZLF31-11-003 128-EIA2 V2.1 R8/R9 Basic Integrity check cell on
89 ZLF31-11-004 EEA0 V2.1 R8/R9 Basic Encryption/Decryptioncell on
92 ZLF31-11-007 128-EIA3 LR13.1 R10 Basic Encryption/Decryptioncell on
93 ZLF31-11-008 EEA3 LR13.1 R10 Basic Encryption/Decryptioncell on
94 ZLF31-12-001 Dedicated Carrier Sharing V2.1 R8/R9 Optional RAN Sharing cell OFF
95 ZLF31-12-002 Shared Carrier Sharing V2.1 R8/R9 Optional RAN Sharing cell OFF
96 ZLF31-12-003 Multi PLMN Support V2.1 R8/R9 Optional RAN Sharing cell OFF
97 ZLF31-12-004 UE Route Selection V2.1 R8/R9 Optional RAN Sharing cell OFF
98 ZLF31-12-005 Basic Mobility Control of RAN Sharing V2.2 R8/R9 Optional RAN Sharing cell of
99 ZLF31-12-006 Transport Traffic Separation of RAN Sharing LR12.1 R8/R9 Optional RAN Sharing eNodeB OFF
100 ZLF31-12-007 Operator Specific Radio Resource Management LR14 R8/R9 Optional RAN Sharing cell OFF
101 ZLF31-12-008 Inter PLMN Mobility V3.0 R8/R9 Optional RAN Sharing cell OFF
Operator Specific Transport Resource

102 ZLF31-12-009 LR13.1 R8/R9 Optional RAN Sharing eNodeB OFF
Management
103 ZLF31-12-010 IRAT L->U Mobility of RAN Sharing LR12.1 R8/R9 Optional RAN Sharing cell OFF
104 ZLF31-12-011 Operator Specific PM/FM LR12.2 R8/R9 Optional RAN Sharing cell OFF
Voice Management (CSFB to UTRAN) of RAN

105 ZLF31-12-012 LR12.1 R8/R9 Optional RAN Sharing cell OFF
Sharing
106 ZLF31-12-013 IRAT L->G Mobility of RAN Sharing LR14 R8/R9 Optional RAN Sharing cell OFF
Voice Management (CSFB to GERAN) of RAN

107 ZLF31-12-014 LR12.1 R8/R9 Optional RAN Sharing cell OFF
Sharing
Operator specific User/Service priority

108 ZLF31-12-015 LR15 R8/R9 Optional RAN Sharing cell OFF
management of Shared Carrier
Operator Specific RRC Resource Management of

109 ZLF31-12-016 LR15 R8/R9 Optional RAN Sharing cell OFF
Shared Carrier
110 ZLF31-13-001 UL/DL HARQ V2.1 R8/R9 Basic Scheduling and Lin eNodeB on
111 ZLF31-13-002 Dynamic Scheduling V2.1 R8/R9 Basic Scheduling and Lin eNodeB ON
112 ZLF31-13-003 UL/DL Frequency Selective Scheduling V2.1 R8/R9 Basic Scheduling and Lin eNodeB ON
113 ZLF31-13-005 TTI Bundling V2.1 R8/R9 Optional VoLTE eNodeB of
114 ZLF31-13-006 Semi-Persistent Scheduling V2.1 R8/R9 Optional VoLTE eNodeB of
115 ZLF31-13-007 Long DRX V2.1 R8/R9 Optional Scheduling and Lin eNodeB on
116 ZLF31-13-008 Short DRX LR13.2 R8/R9 Optional Scheduling and Lin eNodeB on
117 ZLF31-13-009 QoS Scheduler V2.1 R8/R9 Basic Scheduling and Lin eNodeB on
118 ZLF31-13-011 Pseudo GBR for NGBR V2.2 R8/R9 Basic Scheduling and Lin eNodeB on
119 ZLF31-13-012 Advanced AMC V2.1 R8/R9 Basic Scheduling and Lin eNodeB on
120 ZLF31-13-013 PDCCH Link Adaptation V2.2 R8/R9 Basic Scheduling and Lin eNodeB on
Enhanced Adaptive Intra-Mode MIMO Schemes

121 ZLF31-13-015 V2.2 R8/R9 Basic Scheduling and Lin eNodeB #N/A
(need to test)
122 ZLF31-13-016 Adaptive Inter-Mode MIMO Schemes V3.0 R8/R9 Optional Scheduling and Lin eNodeB on
Adaptive Frequency Selective/Non Frequency

123 ZLF31-13-017 V2.2 R8/R9 Optional Scheduling and Lin eNodeB OFF
Selective Scheduler Based on Service
124 ZLF31-13-019 Static ICIC V2.1 R8/R9 Basic Scheduling and Lin eNodeB OFF
125 ZLF31-13-020 Dynamic ICIC LR13.1 R8/R9 Optional Scheduling and Lin eNodeB OFF
126 ZLF31-13-022 Advanced Operator Configurable QoS Scheduler V3.0 R8/R9 Basic Scheduling and Lin eNodeB on
127 ZLF31-13-025 Advanced VoIP Support LR13.1 R8/R9 Optional VoLTE eNodeB OFF
128 ZLF31-13-026 VoIP DRX LR14 R8/R9 Optional VoLTE eNodeB OFF
Adaptive Inter-Mode MIMO Schemes for 4*2

129 ZLF31-13-028 LR13.1 R8/R9 Optional Radio Part eNodeB OFF
MIMO
130 ZLF31-13-030 Adaptive UL MIMO Mode LR14 R8/R9 Optional Radio Part eNodeB OFF
Full Adaptive Intra-Mode MIMO Schemes for

131 ZLF31-13-032 LR12.2 R8/R9 Optional Radio Part eNodeB OFF
4*2 MIMO
132 ZLF31-13-034 MBR > GBR in R10 LR14 R10 Optional Radio Part eNodeB ON
133 ZLF31-14-001 Basic Physical Layer Support V2.1 R8/R9 Basic Radio Part eNodeB on
134 ZLF31-14-002 Extended CP LR15 R8/R9 Optional EMBMS eNodeB OFF
135 ZLF31-14-004 PRACH Format 0 V2.1 R8/R9 Basic Radio Part eNodeB on
136 ZLF31-14-005 PRACH Format 1 V2.2 R8/R9 Optional Radio Part eNodeB OFF
137 ZLF31-14-006 PRACH Format 2,3 LR12.2 R8/R9 Optional Radio Part eNodeB OFF
138 ZLF31-14-007 PRACH Restricted Set Preamble LR12.2 R8/R9 Optional Radio Part eNodeB OFF
139 ZLF31-14-008 UL QPSK/16QAM, DL QPSK/16QAM/64QAM V2.1 R8/R9 Basic Radio Part eNodeB on
140 ZLF31-14-009 UL 64QAM V2.1 R10 Optional LTE-A eNodeB ON
141 ZLF31-14-010 TX Diversity (2 Antennas) V2.1 R8/R9 Basic Radio Part eNodeB on
142 ZLF31-14-011 Open Loop 2*2 Spatial Multiplexing (LD-CDD) V2.1 R8/R9 Basic Radio Part eNodeB on
143 ZLF31-14-012 Closed Loop 2*2 Spatial Multiplexing V2.1 R8/R9 Basic Radio Part eNodeB of
144 ZLF31-14-013 Closed Loop 2*2 Spatial Multiplexing (rank = 1) V2.1 R8/R9 Basic Radio Part eNodeB of
145 ZLF31-14-014 TX Diversity (4 Antennas) V3.0 R8/R9 Optional 4 x 4 MIMO eNodeB OFF
146 ZLF31-14-015 Open Loop 4*2 Spatial Multiplexing (LD-CDD) LR12.2 R8/R9 Optional 2 x 4 MIMO eNodeB of
147 ZLF31-14-016 Closed Loop 4*2 Spatial Multiplexing V3.0 R8/R9 Optional 2 x 4 MIMO eNodeB of
148 ZLF31-14-017 Closed Loop 4*2 Spatial Multiplexing (rank = 1) V3.0 R8/R9 Optional 2 x 4 MIMO eNodeB OFF
149 ZLF31-14-018 Open Loop 4*4 Spatial Multiplexing (LD-CDD) V2.2 R8/R9 Optional 4 x 4 MIMO eNodeB OFF
150 ZLF31-14-021 Uplink 2-Ways MRC V2.1 R8/R9 Basic MRC eNodeB OFF
151 ZLF31-14-022 Uplink 2-Ways IRC V2.1 R8/R9 Basic IRC eNodeB ON
152 ZLF31-14-023 Uplink 4-Ways MRC V2.2 R8/R9 Basic MRC eNodeB OFF
153 ZLF31-14-024 Uplink 4-Ways IRC LR12.2 R8/R9 Basic IRC eNodeB of
154 ZLF31-14-025 Uplink MU-MIMO with 2 layers LR14 R8/R9 Optional LTE-A eNodeB of
UL Open-Loop Power Control With FPC

155 ZLF31-14-030 V2.1 R8/R9 Basic Radio Part eNodeB of
Supported
156 ZLF31-14-031 PUSCH/SRS Closed-Loop Power Control V2.2 R8/R9 Optional Radio Part eNodeB on
PUSCH/SRS Closed-Loop Power Control, OI

157 ZLF31-14-032 LR14 R8/R9 Optional Radio Part eNodeB on
Based
158 ZLF31-14-033 PUCCH Closed-Loop Power Control V2.2 R8/R9 Optional Radio Part eNodeB on
159 ZLF31-14-035 PUSCH Frequency Hopping LR12.2 R8/R9 Optional Radio Part eNodeB on
160 ZLF31-14-036 Uplink 8-Ways MRC LR13.2 R8/R9 Optional Radio Part eNodeB of
161 ZLF31-14-037 Uplink 8-Ways IRC LR13.2 R8/R9 Optional Radio Part eNodeB of
162 ZLF31-14-038 PUCCH IRC LR15 R8/R9 Optional Radio Part eNodeB of
163 ZLF31-15-001 OCNG V2.1 R8/R9 Optional RAN Management eNodeB on
164 ZLF31-15-002 PUCCH Blanking V2.1 R8/R9 Optional RAN Management eNodeB of
165 ZLF31-15-003 GL Power Sharing LR14 R8/R9 Optional RAN Management eNodeB of
166 ZLF31-15-004 Super Cell (testing in queue) LR13.2 R8/R9 Optional RAN Management eNodeB #N/A
167 ZLF31-15-005 Split cells by 2-path RRU LR13.2 R8/R9 Optional RAN Management eNodeB of
168 ZLF31-15-006 Compact Bandwidth LR14 R8/R9 Optional RAN Management eNodeB of
169 ZLF31-16-001 Dynamic Bandwidth Extension LR15 R8/R9 Optional RAN Management eNodeB of
170 ZLF32-00-001 FE/GE Interface V2.1 N/A Basic Physical Interface eNodeB ？？on
171 ZLF32-00-003 2 FE/GE Transmission Interface LR12.2 N/A Optional Physical Interface eNodeB ？？on
172 ZLF32-00-004 Daisy Chain Network Organization V2.1 N/A Optional Physical Interface eNodeB ？？on
173 ZLF32-00-005 2 X 10GE Transmission Interface LR14 N/A Optional Physical Interface eNodeB ？？on
174 ZLF32-01-001 VLAN V2.1 N/A Basic Link Layer eNodeB ？？on
175 ZLF32-01-002 VLAN Mapping V2.1 N/A Basic Link Layer eNodeB ？？on
176 ZLF32-01-004 Link Aggregation LR14 N/A Optional Link Layer eNodeB ？？on
177 ZLF32-02-001 DHCP V2.1 N/A Basic Network Layer eNodeB ？？on
178 ZLF32-02-002 IPv4 Protocol Stack V2.1 N/A Basic Network Layer eNodeB ？？on
179 ZLF32-02-003 IPv6 Protocol Stack LR12.2 N/A Optional Network Layer eNodeB ？？OFF
180 ZLF32-02-004 IPv4/IPv6 Dual Stack LR12.2 N/A Optional Network Layer eNodeB ？？on
181 ZLF32-02-005 IPv4 Address V2.1 N/A Basic Network Layer eNodeB on
182 ZLF32-02-006 IP Jumbo Frame LR12.1 N/A Optional Network Layer eNodeB ？？on
183 ZLF32-03-001 Traffic Marking and Mapping V2.1 N/A Basic Network Layer eNodeB ？？on
184 ZLF32-03-004 Uplink Bandwidth Assignment V3.0 N/A Optional Network Layer eNodeB ？？on
185 ZLF32-03-005 Traffic Statistics V2.2 N/A Basic Network Layer eNodeB ？？on
186 ZLF32-03-006 Traffic Aggregation with Ethernet Interface LR12.2 N/A Optional Network Layer eNodeB ？？on
187 ZLF32-04-001 IPsec V2.1 N/A Optional IPSEC eNodeB ??
188 ZLF32-04-002 IKEv1 V2.1 N/A Optional IPSEC eNodeB ??

189 ZLF32-04-003 IKEv2 V3.0 N/A Optional IPSEC eNodeB ??
190 ZLF32-04-004 IPsec Protect S1 CP Traffic V2.1 N/A Optional IPSEC eNodeB ??
191 ZLF32-04-005 IPsec Protect S1 MP Traffic V2.1 N/A Optional IPSEC eNodeB ??
192 ZLF32-04-006 IPsec Protect S1 UP Traffic V2.2 N/A Optional IPSEC eNodeB ??
193 ZLF32-04-007 IPsec Protect X2 Traffic V2.2 N/A Optional IPSEC eNodeB ??
194 ZLF32-04-009 PKI and Certificate Management V2.2 N/A Optional IPSEC eNodeB ??
195 ZLF32-04-011 ACL LR14 N/A Optional Security eNodeB on
196 ZLF32-04-014 SSH LR13.1 N/A Optional Security eNodeB on
197 ZLF32-04-016 IPsec QoS LR15 N/A Optional Security eNodeB of

198 ZLF32-04-017 IPSec for IPv6 LR15 N/A Optional Security eNodeB of
199 ZLF32-04-018 SFTP LR13.1 N/A Basic Security eNodeB on
200 ZLF32-04-019 SNMP LR13.1 N/A Basic Security eNodeB on
201 ZLF32-05-001 GPS Synchronization V2.1 N/A Basic Synchronization eNodeB of
202 ZLF32-05-002 Synchronization Ethernet V3.0 N/A Optional Synchronization eNodeB of
203 ZLF32-05-003 IEEE1588v2 Frequency Synchronization V2.1 N/A Optional Synchronization eNodeB on
204 ZLF32-05-004 Line Clock V2.2 N/A Optional Synchronization eNodeB of

205 ZLF32-05-005 1PPS+TOD V2.2 N/A Optional Synchronization eNodeB of
206 ZLF32-05-006 Synchronization Priority Scheme V2.1 N/A Optional Synchronization eNodeB of
207 ZLF32-05-009 Glonass Synchronization LR13.2 N/A Optional Synchronization eNodeB of
208 ZLF32-05-010 IEEE1588v2 Phase Synchronization V2.2 N/A Optional Synchronization eNodeB on
209 ZLF32-05-020 Beidou Synchronization LR13.2 N/A Optional Synchronization eNodeB of
210 ZLF32-05-030 NTP Time Information V2.1 N/A Basic Synchronization eNodeB ON
211 ZLF32-06-001 802.3ah LR15 N/A Optional Ethernet OAM and eNodeB ？？of
212 ZLF32-06-002 802.1ag LR15 N/A Optional Ethernet OAM and eNodeB ？？of
213 ZLF32-06-003 Y.1731 LR15 N/A Optional Ethernet OAM and eNodeB ？？of
214 ZLF32-06-004 BFD LR12.1 N/A Optional Ethernet OAM and eNodeB ？？of
215 ZLF32-06-005 IP SLA LR12.2 N/A Optional Ethernet OAM and eNodeB ？？of
216 ZLF32-09-001 Transport Resource Static Sharing LR12.2 N/A Optional Transport ResourceeNodeB ??on
217 ZLF32-09-002 Transport Resource Dynamical Sharing LR14 N/A Optional Transport ResourceeNodeB ??on
218 ZLF33-01-004 eNB Self-discovery V2.1 R8 Optional SON eNodeB OFF
219 ZLF33-01-005 eNB Self-discovery Enhanced V2.2 R8 Optional SON eNodeB OFF
220 ZLF33-01-006 eNB Authentication V3.0 N/A Optional SON eNodeB of
221 ZLF33-01-007 Transport Self-setup V2.1 R8 Optional SON eNodeB of
222 ZLF33-01-010 Self-Test V2.2 N/A Optional SON eNodeB of
Automatic Configuration PCI Based on

223 ZLF33-01-020 V2.1 R8 Optional SON cell OFF
Centralized Assignment
Automatic Configuration PCI Based on
224 ZLF33-01-021 LR12.1 R8 Optional SON cell OFF
Distributed Assignment
225 ZLF33-01-022 Intra-Frequency ANR V2.1 R8 Optional SON cell on
226 ZLF33-01-023 Inter-Frequency ANR V2.2 R8 Optional SON cell of
227 ZLF33-01-024 Inter-RAT LTE-GSM ANR LR12.2 R8 Optional SON cell OFF
228 ZLF33-01-026 Inter-RAT LTE-UMTS ANR LR12.2 R8 Optional SON cell OFF
229 ZLF33-01-027 Intra-Frequency Fast ANR LR13.2 R8 Optional SON cell OFF
230 ZLF33-01-028 Inter-Frequency Fast ANR LR13.2 R8 Optional SON cell OFF
231 ZLF33-01-029 LTE ANR Self-Learning LR13.2 R8 Optional SON cell OFF
232 ZLF33-01-030 Neighbor Cell Configuration Auto-update LR13.2 R8 Optional SON cell on
233 ZLF33-02-005 Intra-LTE Coverage Problem Detection V2.2 R10 Optional SON cell of
234 ZLF33-02-009 Intra-Frequency Mobility Robust Optimization V2.2 R9 Optional SON cell of
235 ZLF33-02-010 Inter-Frequency Mobility Robust Optimization LR12.2 R9 Optional SON cell of
Inter-RAT LTE-GSM Mobility Robust

236 ZLF33-02-011 LR15 R10 Optional SON cell of
Optimization
237 ZLF33-02-013 Inter-Frequency Mobility Load Balancing LR14 R9 Optional SON cell OFF
238 ZLF33-02-014 Intra-Frequency Mobility Load Balancing LR14 R9 Optional SON cell OFF
239 ZLF33-02-017 RACH Power Parameters Optimization V3.0 R9 Optional SON cell OFF
RACH Group and Physical Resource Parameters
240 ZLF33-02-025 LR13.2 R10 Optional SON cell OFF
Optimization
241 ZLF33-02-030 Immediate MDT LR14 R10 Optional SON cell ON
242 ZLF33-02-031 Logged MDT LR14 R10 Optional SON cell ON
Inter-RAT LTE-UMTS Mobility Robust

243 ZLF33-02-033 LR15 R10 Optional SON cell of
Optimization
244 ZLF33-02-034 Inter-RAT LTE-UMTS Mobility Load Balancing LR14 R10 Optional SON cell of
245 ZLF33-03-001 Automatic Inventory V2.1 R8 Optional SON eNodeB on
of
246 ZLF33-03-002 BBU board self-detection LR13.1 N/A Optional SON eNodeB
#N/A
of
247 ZLF33-03-003 RRU self-detection LR13.2 N/A Optional SON eNodeB
#N/A
248 ZLF33-04-003 Software & Hardware Self-Healing V2.2 R9 Optional SON eNodeB of
249 ZLF33-05-002 Intelligent OFDM Symbol Shutdown LR12.1 N/A Optional SON eNodeB ON
250 ZLF33-05-003 Intra-RAT Overlaid Cell Shutdown LR13.1 R10 Optional SON eNodeB OFF
251 ZLF33-05-005 Time Scheduled eNB Shutdown LR13.1 R10 Optional SON eNodeB OFF
252 ZLF33-05-007 Intelligent PSU Shutdown LR14 R10 Optional SON eNodeB ??
253 ZLF33-05-009 Intelligent Channel Shutdown LR14 R10 Optional SON eNodeB of
254 ZLF34-00-003 DL intra-eNB CoMP (Coordiated Scheduling) LR14 R10 Optional CoMP eNodeB of
255 ZLF34-00-012 UL intra-eNB CoMP (Joint Reception) LR12.2 R10 Optional CoMP eNodeB of
256 ZLF34-00-013 Carrier Aggregation(Inter-Band) LR14 R10 Optional CA eNodeB of

257 ZLF34-00-015 Carrier Aggregation(Intra-Band) LR14 R10 Optional CA eNodeB of
258 ZLF34-00-017 Carrier Aggregation(three carriers) LR15 R10 Optional CA eNodeB OFF
259 ZLF34-00-020 CA based ICIC LR15 R12 Optional CA eNodeB OFF
260 ZLF34-00-021 UL SU-MIMO LR15 R10 Optional SU-MIMO cell on
261 ZLF34-00-024 DL inter-eNB CoMP(Coordinated Scheduling) LR13.2 R10 Optional CoMP eNodeB of
262 ZLF34-00-026 UL inter-eNB CoMP (Joint Reception) LR13.2 R9 Optional CoMP eNodeB of
263 ZLF34-00-027 Carrier Aggregation(FDD+TDD) LR15 R12 Optional CA eNodeB OFF
264 ZLF35-00-002 Mobility with Hybird or CSG cell LR14 R10 Optional HetNET cell OFF
265 ZLF35-00-003 static eICIC for Het-Net(ABS) LR14 R10 Optional HetNET cell OFF
266 ZLF35-00-004 feICIC for Het-Net(ABS) LR15 R10 Optional HetNET cell OFF
267 ZLF35-00-005 Dynamic eICIC for Het-Net(ABS) LR14 R10 Optional HetNET cell OFF
268 ZLF35-00-006 Hetnet ANR LR15 R10 Optional HetNET cell OFF
269 ZLF35-00-007 Hetnet X2 Self estalishment LR15 R10 Optional HetNET cell OFF
270 ZLF35-00-008 Hetnet Mobility Load Balance LR15 R10 Optional HetNET cell OFF
271 ZLF36-00-001 Independent Tilt per DL/UL LR12.2 N/A Optional AAS cell of
272 ZLF36-00-002 Individual tilt per carrier with the same technolo LR15 N/A Optional AAS cell of
273 ZLF36-00-003 Individual tilt per technology LR15 N/A Optional AAS cell of
Self-healing compensation in case of radio
274 ZLF36-00-004 LR15 N/A Optional AAS cell of
module failure
275 ZLF36-00-005 Beam shape control LR15 N/A Optional AAS cell of
276 ZLF36-00-006 Circular polarization configured by software LR15 N/A Optional AAS cell of
277 ZLF36-00-007 Vertical sectorization LR13.2 N/A Optional AAS cell of
278 ZLF36-00-008 Virtual four way diversity LR13.2 N/A Optional AAS cell of
1 ZLF31-00-015 System Complying with 3GPP E-UTRAN R11 LR15 N/A Optional System ComplianceeNodeB on
2 ZLF31-00-012 Support UE category 9 LR15 R11 Optional System Compliancecell on
3 ZLF31-05-004 Location Service(OTDOA) LR15 R9 Optional Location Service cell OFF
4 ZLF31-05-007 ETWS LR15 R9 Optional Services and Radio cell OFF
5 ZLF31-05-009 CMAS LR15 R9 Optional Services and Radio cell OFF
6 ZLF31-05-010 MTC Access Control LR15 R10 Optional Services and Radio cell of
7 ZLF31-05-012 MTC EAB LR15 R11 Optional Services and Radio cell of
8 ZLF31-05-018 Location Service(Qcell) LR15 R8/R9 Optional Location Service cell OFF
9 ZLF31-06-013 MFBI LR15 R10 Optional Connection Manag cell ??
10 ZLF31-07-029 Measurement based LAI enabled CSFB Enhance LR15 R10 OptionalMobility Managementcell OFF
11 ZLF31-07-034 Service Triggered Inter-frequency HO LR15 R8/R9 OptionalMobility Managementcell of
12 ZLF31-07-035 QCI Level Mobility Management Enhancement LR15 R8/R9 OptionalMobility Managementcell of
13 ZLF31-07-036 Customized Subscription Based Mobility Manag LR15 R8/R9 OptionalMobility Managementcell of
14 ZLF31-07-037 UE Speed Based Mobility Management Enhance LR15 R8/R9 OptionalMobility Managementcell of
15 ZLF31-07-038 LTE->UTRAN PS Handover Enhancement LR15 R8/R9 OptionalMobility Managementcell OFF
16 ZLF31-07-039 Multi PLMN Mobility Management Enhancement LR15 R8/R9 OptionalMobility Managementcell OFF
17 ZLF31-07-041 Neighbor cell VoLTE capacity based Intra-LTE Ha LR15 R8/R9 OptionalMobility Managementcell OFF
18 ZLF31-07-042 VoLTE User Experience Awared Inter-frequency LR15 R8/R9 Optional Radio Resource Ma cell OFF
19 ZLF31-07-043 VoLTE User Experience Awared SRVCC LR15 R8/R9 Optional Radio Resource Ma cell OFF
20 ZLF31-12-017 Further multi PLMN Shared Carrier LR15 R8/R9 Optional RAN Sharing cell OFF
21 ZLF31-12-018 Operator Specific Customized Subscription Bas LR15 R8/R9 Optional RAN Sharing cell OFF
22 ZLF31-12-019 Intra-LTE ANR of Dedicated Carrier Sharing LR15 R8/R9 Optional RAN Sharing cell OFF
23 ZLF31-13-035 Voice Quality Enhancement for VoLTE LR15 R8/R9 Optional VoLTE cell OFF
24 ZLF31-13-040 Voice Capacity Enhancement for VoLTE LR15 R8/R9 Optional VoLTE cell OFF
25 ZLF31-13-041 NI Based Interference Avoidance Scheduling LR15 R8/R9 Optional Scheduling and Lin cell ON
26 ZLF31-13-042 Small Packets Service Optimization LR15 R8/R9 Optional Scheduling and Lin cell ON
27 ZLF31-13-043 TCP RTT Optimization LR15 R8/R9 Optional Scheduling and Lin cell ON
28 ZLF31-13-046 Explicit Congestion Notification-Alternative(ECN- LR15 R8/R9 Optional Scheduling and Lin cell OFF
29 ZLF31-15-008 SDMA for Super Cell LR15 R8/R9 Optional RAN Management cell of
30 ZLF31-16-004 Supporting non-standard bandwidth by lossy comprLR15 R8/R9 Optional LTE Bandwidth cell #N/A
31 ZLF32-03-008 Traffic Congestion Management LR15 N/A Optional QoS Management cell on
32 ZLF32-04-021 IPSec Tunnel Backup LR15 N/A Optional IPSEC cell ？？
33 ZLF32-06-007 TWAMP Server LR15 N/A Optional RAN Management cell ？？on
34 ZLF33-01-031 CoMP Self Configuration LR15 R10 Optional CoMP cell of
35 ZLF33-02-040 Adaptive capacity adjustment LR15 N/A Optional SON cell of
36 ZLF33-02-041 Antenna Self-adaption LR15 N/A Optional SON cell of
37 ZLF33-05-012 Power Consumption Visualization LR15 R9 Optional SON cell ？？
38 ZLF33-05-014 Intelligent OFDM Symbol Shutdown, Phase 2 LR15 N/A Optional SON cell of
39 ZLF34-00-034 Cloud CA (centralized) LR15 R10 Optional CA cell OFF
40 ZLF34-00-035 RRC user based CA enable and backof LR15 R10 Optional CA cell OFF
41 ZLF34-00-036 Flexible Scell configuration of multi-carriers LR15 R10 Optional CA cell OFF
46 ZMF02-11-014 UL Dynamic Carrier Extension LR15 R8/R9 Optional Spectrum Effiency cell of
47 ZLF34-00-016 Carrier Aggregation(UL 2CC) LR16 R11 Optional CA cell OFF

48 ZLF34-00-031 Support DL 256QAM LR16 R12 Optional LTE-A cell of
49 ZLF34-00-033 Support DL MIMO4*4 based on TM9 LR16 R10 Optional 4 x 4 MIMO cell OFF
50 ZLF34-00-037 LTE-U LR16 R13 Optional CA cell OFF
51 ZLF34-00-038 LTE and WLAN aggregation LR16 R13 Optional CA cell OFF
52 ZLF34-00-041 Inter-eNB JR based on relax transmission bandwi LR16 R10 Optional JR cell of
53 ZLF34-00-044 Intra-eNB JR between macro and micro LR16 R10 Optional JR cell OFF
54 ZLF34-00-045 Inter-eNB JR between macro and micro LR16 R10 Optional JR cell OFF
55 ZLF34-00-049 Carrier Aggregation(DL 3 CC, FDD+TDD) LR16 R13 Optional CA cell OFF
56 ZLF34-00-050 NB-IOT LR16 R13 Optional NB-IOT cell OFF
57 ZLF34-00-051 Cloud CA (distributed) LR16 R10 Optional CA cell OFF
58 ZLF34-00-056 service based PCC dynamic selection LR16 R11 Optional LTE-A cell ??
59 ZLF34-00-057 Netwok assistant CRS-IC without ABS LR16 R11 Optional LTE-A cell ??
60 ZLF35-00-008 HetNet Mobility Load Balance LR16 R10 Optional HetNET cell OFF
Inventory
Remarks
(a) Vendor confirms that the mentioned list is complete feature list of the Software quoted for June-2015 SW release & Dec-2015 SW release and no ommissions
(b) Any omission in feature list supplied by vendor will result in automatic classification of that feature and related dependent feature/license to be classified as IDE
(c ) At all time IDEA way of Licensing needs to be followed , Vendor will need to keep mapping between IDEA licensing to their way of Licensing.
(d ) All IDEA Basic features , will be part of the deliverables
(e) There are no pre-requsities for the IDEA basic features , all the features which are in IDEA optional various catergories - they include all the pre-requisite feature
(f) All Optional - Hetnet Features are default for the each small eNB cells and 5 eNB macro cells which are neighbour to this small cell eNB
(g) Carrier Aggregation features works for 2CC upto 40Mhz
(h) All Idea Features(Basic /Optional) are marked in column G.For optional feature grouping is marked in column H.
EXPLANATION
3GPP R8 is the first release for LTE from 3GPP and covers specificat LTE mobile system; it was
completed in Mar. 2009.
3GPP R9 is the further enhancement of 3GPP R8; it was completed in Mar. 2010.
It describes 3GPP R10 FDD basic functions of eNodeB.
It describes the connections between network elements in E-UTRAN
Logical channels, transport channels and physical channels are defined in 3GPP protocol;
Support for cat 3 Ues
ZTE eNodeB supports UE category 4, with maximum DL/UL throughput 150Mbps/50Mbps.
Radio channels required for eMBMS( LTE Adv)
LTE Adv Rel 10 to support 2CC for DL

ZTE eNodeB supports 20MHz and10MHz bandwidths.
ZTE eNodeB supports 15MHz, 5MHz bandwidths.
ZTE eNodeB will support 3MHzbandwidths
ZTE eNodeB will support 1.4MHz bandwidths.
ZTE eNodeB supports the cell peak data throughput @ 100Mbps/50Mbps.
ZTE eNodeB supports high speed UE with velocity up to 120km/h.
ZTE eNodeB supports cell radius extended to 15km. No site planned to cover such range
This feature supports the extended cell radius with LTE service coverage.
This feature supports multiple bearers to supply users more convenient services and improve user
experience.
For Multiple Bearers
This feature supports multiple bearers to supply users more convenient services and improve user
experience.
For Multiple Bearers
This feature detects the location of a UE in the LTE network through the Assisted Global Navigation
Satellite System (AGNSS) or basic Cell ID (CID) positioning mode to provide the location information
about the UE for value-added services such as the emergency call service and automotive navigation.
Rel 10 LTE-Adv (LR15) : This feature provides the point-to-multipoint unidirectional multimedia
broadcast mechanism to save the resources in the network and improve the resource utilization
This feature supports emergency service in special scenario.
LR 15 Supported feature
This feature detects the location of a UE in the LTE network in E-CID positioning mode to provide the
location information about the UE for value-added services such as the emergency call service and
automotive navigation
This feature enables the UE to obtain the latest system information such as network identification, cell
selection and reselection, initial access and measurement control and location information.
This feature enables paging of UEs.
This feature enables RRC connection between UE and E-UTRAN.
This feature enables information interaction between UE and EPC.
This feature enables UE information management between E-UTRAN and EPC to support user
individual signaling.
This feature enables UE radio capability information transferred from UE to the network.
This feature enables E-UTRAN resources management for user data transport.
#N/A
This feature enables interaction between E-UTRAN and EPC.
This feature enables interaction between eNodeB and neighbor eNodeB.
This feature is used to:Implement networking redundancy;Implement MME load balancing.
This feature is used to improve the success rate of RRC re-establishment, thereby reducing rate of
dropped call and improve handover success rate.
to manage RR efectively by diferent states (RRC Active, RRC Only, RRC Idle & DRX State)
This is used for UE receiving registration area information , system information and other AS and NAS
Information from the PLMN. And if registered, UE can receive paging and notification messages from
the PLMN, or initiate transfer to connected mode.
This feature is used to guide UE to a suitable cell of E-UTRAN.
This feature is used to guarantee service continuality for subscriber mobility in intra frequency
scenario.
This feature is used for UE receiving paging and notification messages from the PLMN,or initiate
transfer to connected mode in GERAN coverage, in case lack of LTE coverage.
This feature is used to guide UE to a suitable cell of GERAN.
Yes Supported
transfer to connected mode in UTRAN coverage, in case lack of LTE coverage.
This feature is used to guide UE to a suitable cell of UTRAN.
Yes Supported
transfer to connected mode in 1xRTT coverage, in case lack of LTE coverage.
transfer to connected mode in eHRPD coverage,in case lack of LTE coverage.
This feature is used to guide UE to a suitable cell of eHRPD.
This feature is used to guarantee service continuality for subscriber mobility in inter frequency
scenario.
This feature is used to guarantee service continuality for subscriber mobility.
This feature is used to guarantee service continuality for subscriber mobility. 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
This feature is used to guarantee service continuality for subscriber mobility. 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
LR15 Supported (UE support also)

This feature is used to guarantee voice continuality for subscriber mobility.

Yes Supported
Yes Supported
This feature is used to guarantee service continuality according to operator’s policies.
This feature is used for CSFB optimization and further reduces CSFB latency.
If we have one more TDD carrier
This feature enables diferent service types between voice and data,flexible IRAT measurement policy
strategy.
The task of RAC (Radio Admission Control) is to admit or reject the establishment requests for new
radio bearers, by taking in QoS of in-progress and new services.
This feature enables best utilization of system resources by service priorities, and guarantees system
stability.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.
This feature enables reasonable utilization of system resources by service priorities and further
guarantees system stability, Intra-LTE load balancing algorithms are used in multi frequencies scenario
and may result in handover or cell reselection decisions with the purpose of redistributing traffic from
highly loaded cells to lower loaded cells.
Intra Freq Mobility load balancing, supports exchanging load information over the X2 interface
This feature enables reasonable utilization of system resources by service priorities and further
guarantees system stability, IRAT L->U load balancing algorithms are used in 3G Overlapping with LTE,
and may result in handover or cell reselection decisions with the purpose of redistributing traffic from
highly loaded cells to lower loaded cells.
Explicit Congestion Notification-Alternative(ECN-A). This feature is used to improve VoLTE coverage and
reduce the eNodeB load, increasing the system capacity and improving user experience, by adjusting
the codec rate.
This feature is used to guarantee system stability.In case network load excess of the maximum capacity,
load control strategy can be used.Network load control is mainly dependent on radio bearer release
mechanism and is used per cell.
This feature is used to balance distribution of the traffic load over the serving UTRAN cell and its
neighbor LTE cells in a scenario consisting of LTE and UTRAN. The purpose of this feature is to
efectively use the overall resources of the LTE/UTRAN network system, improve the overall system
capacity, and ensure system stability.
LR15 Supported for VOIP Services

QCI Support
Extended QCI Support
This feature is used to provide flexible choice policy for operator in case of network congestion. When
this function is enabled eNodeB can reduce the guaranteed data rate for GBR service. The reduction of
GBR data rate will be performed
according GBR service priority.
All the MAC PDU formats, including MAC CE formats are supported as per 3GPP TS 36.321. e.g.
Scheduling information reporting, Error correction through HARQ, Transport format selection, Logical
channel prioritazation etc.
All the RLC PDU formats & functions are supported as per 3GPP TS 36.322. e.g. Transfer of upper layer
PDUs, RLC re-establishment, Duplicate detection (only for UM and AM data transfer) etc
All the PDCP PDU formats & functions are supported as per 3GPP TS 36.323. e.g. TTransfer of data
(user plane or control plane), Maintenance of PDCP SNs, Timer based discard, Duplicate discarding etc.
This feature enables overhead reduction of packet header on radio interface, A ROHC profile is a
compression protocol, which specifies how to compress specific
header combinations. ROHC profiles provide the details of the header compression framework . Profile
0x0000 is used for uncompressed.
compression protocol, which specifies how to compress specificheader combinations. ROHC profiles
provide the details of the header compression framework. Profile 0x0001 is used for RTP/UDP/IP
compression protocol, which specifies how to compress specific header combinations. ROHC profiles
provide the details of the header compression framework. Profile 0x0002 is used for UDP/IP
compression protocol, which specifies how to compress specific
header combinations. ROHC profiles provide the details of the header compression framework. Profile
0x0004 is used for IP
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
Improves user TCP traffic performance, This feature can monitor and control the transmission of the
uplink TCP ACK to adjust the UL data, When the UL data is decreased the TCP Ack/Nack information
corresponding to DL Data is protected. It is also used to distinguish and transmit the TCP ACK of UL
Data to protect the UL throughput. It enhances the DL & UL transmissions.
This feature enables avoidance of fraudulent attack from the UE or network equipment that is
disguised by the third party.
Integrity protection is provided to NAS and RRC signaling. The integrity protection of RRC signaling
includes both integrity protection and integrity verification and is performed in PDCP.EIA0 for null
integrity protection algorithm is supported.
includes both integrity protection and integrity verification and is performed in PDCP.128-EIA1 for
SNOW 3G algo is supported
includes both integrity protection and integrity verification and is performed in PDCP.128-EIA2 for AES
algo is supported.
This feature enables confidentiality protection for the data & signalling stream. The aim is to ensure the
communication confidentiality between Ue & eNodeB. The ciphering procedure of RRC signalling and
UP (User Plane) data is requested and terminated in eNodeB.
UP (User Plane) data is requested and terminated in eNodeB.128-EEA1 for SNOW 3G based algo is
supported.
UP (User Plane) data is requested and terminated in eNodeB.128-EEA2 for AES based algo is
supported.
includes both integrity protection and integrity verification and is performed in PDCP.128-EIA3 for ZUC
algo is supported.
UP (User Plane) data is requested and terminated in eNodeB.128-EEA13 for ZUC based algo is
supported.
This feature helps operators to reduce CAPEX and OPEX by building and maintaining one network.
Simultaneous connection with multiple independent core network architecture is supported. Also
simultaneous connection with other shared or non shared eNodeB is supported. Independent or
common antenna can be used according to diferent sharing spectrum usage.
This feature is used for operators to reduce CAPEX and OPEX by building and maintaining one network.
Comparing to dedicated carrier network sharing, radio
resources can be used more efficiently. Simultaneous connection with multiple independent core
network architecture is
supported. Also simultaneous connection with other shared or non shared eNodeB is supported.
Common antenna can be used for RAN sharing with shared carrier.
Multi PLMNs are supported in both dedicated and shared carrier sharing. For dedicated carrier sharing,
multi PLMNs are managed by one PLMN for each cell. For shared carrier sharing, multi PLMN's are
managed by multi PLMN's for each cell. The PLMN information is broadcasted through system
information.
When a UE performs an initial access to a shared network, one of the available core network operators
shall be selected to serve the Ue. Ue indicated the selected Core Network Operator through selected
PLMN-id with RRC connection complete message, which serves the UE currently to which the UE is
currently attached. The selection of core network operator by the UE shall be respected by the
network. The eNodeB shall select an appropriate MME for the PLMN indicated by the UE in case of
MOCN. In case of UE registration failure, the eNodeB shall behave as in the case of a non shared
network.
This feature is used for operators to reduce CAPEX and OPEX by building and maintainance of one
network.
Basic mobility control in RAN sharing scenarios support intra LTE mobility within shared LTE areas with
following functions: Cell reselection/X2 Handover/S1 Handover within shared LTE areas. Cell
selection/X2/S1 Handover within shared & non shared areas.
network.
Traffic separation for two or more CN operators within the shared E-UTRAN can be realized using
VLANs. For example, the VLANs can be partitioned for S1/X2 interface as per operator basis, OAM and
other traffic for all operators. It can be flexibly configured by OMC according to operator’s requirement.
Same Band in Sharing by Diferent operators
network.
Inter PLMN mobility is supported for cases, such as at the border of shared and non-shared area,
according to operator’s policy. Activation of this feature will be configurable in accordance with
operator policy.
network. Transport resource partition are identified for UL transport network sharing configuration
from eUTRAN point of view, while the partition for DL are to be identified and provided from Core
Network point of view.
PS Handover from LTE to UTRAN in an LTE Network-Sharing Scenario

Redirection from LTE to UTRAN/GERAN in an LTE Network-Sharing Scenario
In network sharing mode, the performance/fault statistics provides counters and indicators for
diferent PLMNs
(CSFB to UTRAN/GERAN) of RAN Sharing
This feature provides a flexible mobility management policy in a LTE network-sharing scenario
consisting of LTE and GERAN. If the LTE network coverage is not available for a UE, the UE is instructed
to select a suitable cell at a GERAN frequency to ensure service continuity for the UE
This feature provides a flexible mobility management policy in an LTE network-sharing scenario
consisting of LTE and GERAN. If the LTE network does not support the VoIP voice service, this feature
falls back the UE to the CS domain in the GERAN network to provide the voice service to the UE
When LTE network-sharing is implemented in shared carrier mode, this feature provides diferential
QoS management policies for diferent operators. This minimizes or avoids the QoS diferences among
the UEs or services of the same level caused by the diferent QoS mapping rules in each operator's core
network
When LTE network-sharing is implemented in shared carrier mode, this feature provides the flexible
RRC resource partition for operators. This ensures basic RRC resources for each operator and increases
the RRC resource utilization of the system
The feature enables fast retransmission and decrease the BLER. ZTE eNodeB supports both Chase-
Combining & Incremental Redundancy, DL asynchronous adaptive, UL synchronous adaptive & non
adaptive HARQ, max HARQ transmission times.
The feature enables dynamic scheduling function. The dynamic scheduling function supports the
following time domain scheduling
strategies with operator configurable: MAX C/I; Round Robin; Proportional Fairness. The dynamic
scheduling function supports the non-frequency selective scheduling unction, which is called wide
band CQI allocation in ZTE’s eNodeB
The feature enables cell throughput improvement and guarantees QoS requirements in low speed
environment. ZTE eNodeB calculates the DL channel SINR based on CQI reports sent by UEs, to acquire
the DL channel conditions, the UL channel SINR based on Sounding RS sent by UEs, to acquire the UL
channel conditions.
The feature enables the improvement of cell edge user coverage. In it the same transport block is
repeatedly transmitted in four consecutive sub frames with diferent RV parameter. TTI (Transmission
Time Interval) bundling is applicable for uplink transmission and for specific applications such as VoIP.
The feature enables to decrease signaling overhead and increase system capacity, especially VoIP
capacity. The principle of SPS is to pre allocate resources at fixed sub-frames for initial transmission,
while dynamic scheduling is still considered for retransmission, to decrease the delay of service.
The feature mainly supports UE power saving. DRX function can be configured for an
‘RRC_CONNECTED’ UE. Then the UE does not
need to monitor the PDCCH continuously. Long DRX period is beneficial for lengthening the Ue Battery
life.Long DRX may also be used for CGI measurement in ANR function.
The feature mainly supports UE power saving. DRX function can be configured for an
‘RRC_CONNECTED’ UE. Then the UE does not
need to monitor the PDCCH continuously. Long DRX period is beneficial for lengthening the Ue Battery
life.Long DRX may also be used for CGI measurement in ANR function.
The feature supports the QoS scheduling function in LTE, and guarantees the QoS requirements, like
GBR, AMBR, and PDB for specific service. The QoS requirements defined in 3GPP are: Priority;
GBR/MBR for GBR services; MBR for non-AMBR for all the services of one UE; Packet Error Rate (PER),
Packet Delay Budget (PDB) for specific service from QCI(1~9).
The feature guarantees no low priority NGBR users will starve in case huge volume
traffic from high priority NGBR users. ZTE’s eNodeB will support pseudo GBR, or mini-GBR value, for
NGBR services on both DL and UL. In this way, a minimum GBR can be guaranteed for all NGBR
services,including low priority users.The pseudo GBR for each NGBR QCI can be operator configurable.
The feature enables to increase system capacity and improve coverage.According to CQI reported by
UE and UL SINR measured by eNodeB, eNodeB can
acquire the current channel quality. Considering the channel conditions, bufer status, and the UE
capability, eNodeB can determine the modulation order and coding rate to be used.
The feature enables to increase system capacity and improve coverage. PDCCH link adaptation function
dynamically adjusts the PDCCH CCE aggregation level
and PDCCH transmission power adaptive to radio environment.In cell edge or low SINR environment,
large PDCCH CCE aggregation level, like 4 or 8,
is deployed, and the transmission power of PDCCH is boost, and vice verse.
The feature supports the link adaptation for the enhanced DL intra MIMO-modes adaptation function
in LTE to improve the system performance.
ZTE eNodeB supports the following intra mode DL transmission schemes adaptation: Open-loop intra-
mode adaptation, Closed-loop intra-mode adaptation.
The feature supports the link adaptation for the enhanced DL inter MIMO-modes adaptation function
in LTE to improve the system performance.
ZTE eNodeB supports the following intra mode DL transmission & transmission modes adaptation:
Open-loop intra-mode adaptation, Closed-loop intra-mode adaptation.
The feature supports the adaptive switch between frequency selective and nonfrequency selective
scheduling in LTE, to improve cell throughput and guarantee QoS requirements in low and high speed
environment.
The feature supports the static Fractional FR(Frequency reuse ) & soft FR functions in LTE.
The feature supports the dynamic ICIC function via adaptive SFR scheme with load information
exchanged among neighboring cells in LTE, to coordinate the system interference and increase the
system capacity.
The feature supports the advanced operator configurable QoS scheduler with scheduling weights
configurable and QCI absolute/relative scheduling priority configurable. With this feature, QCI
scheduling priority can be configured as Gold, Silver & bronze.And diferent QCI scheduling priority
configuration supports absolute or relative QCI scheduling priority.
The feature supports the advanced VoIP features.ZTE eNodeB will supports the following advanced
VoIP features:
Support SPS state machine management, to switch between SPS during voice period and dynamic
scheduling during silent period; Support SPS adaptation based on VOIP codec rate & for near field
users, together with TTI bundling for far field users.
The feature supports for adaptive DRX cycles according to Silence Indicator (SID)for LTE voice.ZTE
eNodeB will support for adaptive DRX cycles according to Silence Indicator (SID)for LTE voice,that is
short DRX combined with Long DRX to save more power consumption.Notice, in fact, Long DRX only is
enough for VoIP service.
The feature supports the link adaptation for the enhanced DL inter MIMO-modes adaptation function
in LTE to improve the system performance in case of DL 4*2 MIMO.ZTE eNodeB supports the following
intra/inter mode DL transmission schemes adaptation in case of 4*2 MIMO: Open-loop intra-mode
adaptation, Closed-loop intra-mode adaptation.
The feature supports the adaptive UL MIMO mode function. ZTE eNodeB will support the adaptive UL
MIMO mode between UL MU-MIMO and UL-SIMO
The feature supports the link adaptation for the enhanced DL intra MIMO-modes adaptation function
in LTE to improve the system performance in case of DL 4*2 MIMO.ZTE eNodeB supports the following
intra/inter mode DL transmission schemes adaptation in case of 4*2 MIMO: Open-loop intra-mode
The feature supports MBR>GBR defined in 3GPP Release 10. In release 10 in 3GPP, MBR can be higher
than GBR for GBR service.The scheduler supports the throughput can be override GBR and limited by
MBR for GBR service.
This feature is a fundamental configuration for LTE FDD.ZTE eNodeB supports the basic physical layer
processing functions defined in 3GPP TS
36.211, 36.212, and 36.213.ZTE eNodeB supports normal cell radius (around several kilometers), basic
physical channels processing functions, like PCFICH,
PHICH, PDCCH, PDSCH, PRACH, PUCCH, and PUSCH, UL DMRS and Sounding RS,all the PDCCH formats
and aggregation levels, all the UCI formats,supports all the following DCI formats,supports DCI 1D to
support DL MU,supports DL resource allocation type 0 and 2 only.supports all the PA and PB
configurations defined in 3GPP TS 36.213. forDL power allocation.ZTE eNodeB supports all the
transport block sizes on DL and UL defined in 3GPP TS
This feature is used for initial network access and uplink time synchronization.
Format 0: normal 1 ms RA burst with 800us preamble sequence, for small cells (up to ~14km).
Format 1: 2ms RA burst with 800us preamble sequence, for large cells (up to
~77km) without a link budget problem.
Format 2: 2ms RA burst with 1600us preamble sequence, for ~19km) supporting low data rates;
Format 3: 3ms RA burst with 1600us preamble sequence, for very large cells (up to ~100km).
This feature is used for initial network access and uplink time synchronization in high speed
environment.
This feature enables the eNodeB to receive PUSCH and transmit PDSCH.
ZTE eNodeB provides QPSK and 16QAM demodulation in uplink.
ZTE eNodeB provides QPSK, 16QAM and 64QAM modulation in downlink.
This feature enables the eNodeB to get higher UL data rate and UL spectrum efficiency
This feature provides 64QAM demodulation in uplink, UE category 5 supports 64QAM in uplink.
This feature is used to transmit downlink data and control signaling to improve coverage and
robustness of radio channels in case of 2 antenna environment.
This feature increases system capacity and spectrum efficiency in a 2*2 MIMO
environment.
environment.
environment.
This feature is used to transmit downlink data and control signaling to improve coverage and
robustness of radio channels in case of 4 antenna environment.
This feature increases system capacity and spectrum efficiency in a 4*2 MIMO environment, with 4
antennas in eNodeB and 2 antennas in UE.
environment.
This feature improves coverage and robustness of uplink radio channels in case of 2 reception antenna
environment.
environment.
environment.
environment.
This feature increases UL system capacity and spectrum efficiency by MU-MIMO with 2 layers in case of
2 or 4 antennas in eNodeB.
Uplink Multi-User MIMO (MU-MIMO) means several UEs communicate simultaneously with a common
base station using the same frequency - and time - domain resources in uplink.
The introduction of PUSCH/SRS and PUCCH open - loop power control aims to trace the fluctuation of
path - loss and aid AMC for link adaptation and mitigate the inter – cell interference. The open loop
part of the scheme is often
called Fractional Power Control (FPC) because it allows User
Equipments (UE) to partially compensate the path-loss
path - loss and aid AMC for link adaptation.
path - loss and aid AMC for link adaptation.
The introduction of PUCCH power control aims to trace the fluctuation of path loss and guarantee the
successful demodulation rate of PUCCH.
PUSCH frequency hopping is suitable for small payloads and/or fast moving UEs to provide frequency
diversity.
If eight receive antennas are deployed on an eNodeB and the cell interference is minor, this feature is
used to improve uplink coverage quality through MRC reception schemes
If eight receive antennas are deployed on an eNodeB and the cell interference is high (such as a
commercial network with a great number of UEs), this feature is used to improve uplink coverage
through IRC reception schemes.
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 UEs), this feature is used to improve PUCCH reception
performance by reducing PUCCH reception interference
This feature enables the operator to configure the OFDM Channel Noise Generator (OCNG) function in
the eNodeB so that the system can emulate many virtual users in the downlink network load test.
The PUCCH blanking functionality supports non - 3GPP UL system bandwidth with PUCCH over-
dimensioning.
The feature supports semi- static power sharing between GSM and LTE, in case GL co- PA, in order to
improve performance of LTE cells, When GSM intelligently shutdown one or more GSM frequency in
case of low load for power saving, the release power can be shared by LTE.
The feature supports several RRUs in one eNB combined as one super cell, with the same logic cell id.
The feature supports 2 single-port cells split by one 2-ports RRU, which is useful in case of indoor DAS
coverage, in order to decrease required number of RRUs.
In a scenario where GSM and LTE provide the same coverage on the same frequency band, this feature
supports compressing the guaranteed bandwidth of LTE to reduce interference and maximize the
spectral utilization
LR15 Supported
ZTE eNodeB supports FE/GE (RJ45), GE (Optical/Electrical), 10/100/1000Base – T interfaces with auto
negotiation, 1000Base- LX/1000Base-BX/ 1000Base-SX (MM) fiber/100Base-FX interfaces, standard
SFP on all Ethernet transport interfaces.
eNodeB provides 2 FE/GE interfaces for transmission, these 2 interfaces can be configured backup each
other to improve the availability.
BBU can interconnect via Ethernet interface like a daisy chain, Ethernet switch is built in BBU, the traffic
aggregates towards to the core network via the first BBU.
eNodeB CCE board provides 2 GE interfaces and 2 10GE optical interfaces

independently for transmission, these 2 GE interfaces can be configured backup each and share the
load, extend bandwidth, so do the 2 10GE interface.
VLAN is often adopted in Ethernet network to implement traffic separation, thus avoiding traffic
broadcast storm normally happened in Ethernet network due to its broadcast.
The flows of control plane, user plane, and OMC channel can flexibly be
one or more diferent VLANs. If IPSec function is enabled, IPSec tunnel can be
configured to arbitrary VLAN.
The IEEE802.3ad LAG protocol is used for bandwidth dynamically binding and backup for 2 Ethernet
interfaces each other.
DHCP (Dynamic Host Configuration Protocol) is very useful for the management and distribution of IP
network configuration, particularly as networks grow beyond hundreds of clients.
LTE eNodeB supports IP and corresponding upper layer protocols to implement user plane and control
plane (also OMC plane, same as control plane) functions. ZTE eNodeB
eNodeB supports IPv6 compliance with IETF RFC2460 + RFC5095, provides upper
layer application over it.
eNodeB supports IPv4 & IPv6 Dual Stack on all the Ethernet interfaces simultaneously;
the IP version (IPv4 or IPv6) can be selected
ZTE eNodeB can be configured with a unique IP address, all the logical interfaces such as S1, X2, and
OMC will use this IP address. One eNodeB needs only one IP address thus reducing the required IP
address number.
ZTE eNodeB supports IPv4 Jumbo frame on all the Ethernet interfaces to avoid packet fragment and
recombination when using IPSec function on S1 or X2 interface. The maximum size of Jumbo frame is
up to 1800bytes.
DifServ model is often adopted as QoS and traffic scheme in LTE transport network, and this scheme
divides the IP traffic in backhaul network into several priority levels(for example 3 levels as Gold, Silver
and Bronze, or 8 level as 802.1p) and handles traffic at each level with diferent forwarding processes.
The total bandwidth can be assigned via OMC for S1, X2 and OMC, or independently
assign CP, UP and OMC traffic bandwidth and priority.
eNodeB provides the throughput statistics of incoming and outgoing, and the packet number of
diferent types, the bandwidth according to the IP addresses and VLANs.
ZTE eNodeB can be configured as Ethernet aggregator which used to aggregate the traffic of 2G/3G.The
next phase, LTE eNodeB can manage the traffic of 2G/3G and LTE traffic itself, reserve traffic bandwidth
of 2G/3G and guarantee the QoS of this traffic.
The operator needs to protect the communications via S1 and X2 interfaces, which is normally ensured
by using IPSec channels between eNodeB and IPSec gateway.
Internet Key Exchange (IKE or IKEv2) is the protocol used to set up a security
association (SA) in the IPsec protocol suite. IKE builds upon the Oakley protocol and ISAKMP.
Implement Cryptographic Algorithms for Use in the Internet Key Exchange Version 2 (IKEv2), EAP
Method for 3rd Generation Authentication and Key Agreement (EAP – AKA) and Multiple
Authentication Exchanges in the IKEv2 Protocol.
Protect the S1 CP traffic using IPsec. The IPsec tunnel is set up between eNodeB and security gateway,
when IPsec deployed, control plane signaling should be protected by IPsec.
Protect the MP traffic using IPsec. The IPsec tunnel is set up between eNodeB and security gateway,
when IPsec deployed, OMC data should be protected by IPsec.
Protect the S1 UP traffic using IPsec. The IPsec tunnel is set up between eNodeB and security gateway,
when IPsec deployed, user plane data protection is optional, in most scenarios, it isn’t needed for
protecting UP data.
Protect the X2 traffic using IPsec, it includes control signaling and user data. The Ipsec tunnel can be set
up between eNodeBs directly and indirectly.
PKI certificate is useful when there are large numbers of eNodeBs to declare itself and implement
authentication with core network.
ZTE eNodeB supports Access Control List function on transport side, it can be
configured L2 filter based source and destination COS value. ZTE eNodeB can also be configured L3
filter based source and destination IP address, source and destination port number.
Realize eNodeB and OMC communication using SSH protocol.
LR15 Supported
LR15 Supported
eNodeB supports security transmission with OMC, it use vendor define message encrypt meth via
TCP/UDP socket to transmit messages, and use SFTPv3 to transmit files.
OMC supports SNMP protocols & OMC can support inter connection with NMS through northbound
SNMP interface.
this interface.
OMC northbound SNMP interface ofers NMS with fault management function.
For LTE FDD network, frequency synchronization is required between eNodeBs frequency
synchronization is normally achieved through
TDM transport network or by GPS system.
Ethernet uses the physical layer interface to pass frequency information

from node to node. Synchronous Ethernet can implement the frequency synchronization.
also called as Precision Time Protocol, which synchronizes clock to a distributed system consisting of
one or more nodes by network communication.
eNodeB can receive and deliver 1PPS+TOD synchronization clock reference.

ZTE eNodeB supports a synchronization priority scheme whereby the network operator shall be able
to freely assign a priority to each possible synchronization source
eNode B can get frequency and phase clock reference from Glonass system with a integrated receiver,
this receiver can share the antenna signal input with GPS
all the nodes between the clock server and slaves should support IEEE 1588 BC mode, and comply with
the regulation of ITU-T G.8271..
#N/A
The NTP/SNTP network time synchronization protocols so that it can synchronize time with server of a
third-party system and provide synchronization time sources for NEs.
#N/A
#N/A
#N/A
BFD (Bidirectional Forwarding Detection) is a detection protocol designed to provide fast forwarding
path failure detection for all media types, encapsulations, topologies, and
routing protocols.
Measure the transport network IP performance condition using service level agreement protocol, such
as delay, jitter and packet loss rate.
It can be assigned to diferent radio modes. The bandwidth is fixed for GSM, UMTS, and LTE.
Radio mode is configured with a specific priority based on the same principle, it can get transport
resource in a preemptive way, and the traffic with
highest priority will be sent first.
The eNodeB will boot and perform a self-detection. The feature depends on the prerequisites that the
transport parameters for the eNodeB should be planned in advance, including VLAN partition, IP
addresses, etc.
The feature is used in the scenario where the DHCP relay is disallowable. DHCP relay agent eNodeB, all
the eNodeBs in the same sub-network self-configure eNodeB IP and OMC IP, AGW IP, SGW IP.
The feature includes two aspects, Automatic acquisition of security data & Automatic establishment of
security tunnel
Transport self-setup involves the following scenarios: Initial Network deployment or a new eNodeB
insertion into network, X2 transport self- setup, S1 self-setup
eNodeB uses the self-test function to judge whether the eNodeB can provide service or not.
The feature enables to assign initial PCI for cell without conflict & confusion reducing manual efort on
PCI assignment.
This enables to minimize the probability of PCI conflict and confusion, thus reducing manual efort on
PCI assignment.
The feature involves following aspects: neighbor cell detection and addition, automatic neighbor cell
removal, switch on/of ANR automatically;,white/black list management, ANR management in OMC
The feature enables to reduce the network failures due to missing or wrong inter-frequency neighbor
definition and better balance the traffic level in Inter
the
. etter Inter-frequency clls
For Inter-RAT scenarios, each cell contains an Inter RAT Frequency Search list. This list contains all
frequencies that shall be searched. ZTE support LTE-GSM ANR.
Each cell contains an Inter RAT Frequency Search list. This list contains all frequencies that shall be
searched. ZTE support LTE-UMTS ANR. The feature enables to reduce the network failures due to
missing or wrong inter-RAT LTE-UMTS neighbor definition.
During the initial phase of the deployment of inter-frequency eUTRAN cells, there are a quantity of
inter-frequency neighbor cells to detection and addition, so that the process can be fastened.
During the initial phase of the deployment of inter-frequency eUTRAN cells, there are a quantity of
inter-frequency neighbor cells to detection and addition, so that the process can be fastened.
ANR aims at the neighbor cell optimization as the predefined policies. And the unsuitable policies will
slow down the optimization procedure. Besides, the feature caches the CGI information for the PCI to
reduce the measurements to the unkown PCI of the new neighbor cells.
The feature supports automatic configuration update to OMC based on the configuration exchange
through X2 interface, so that the inconsistence can be avoid.
The feature enables to avoid coverage hole in LTE network and to decrease the level of DL inter-cell
interfrence
The configuration of the threshold for the target MRO parameter; the configuration of the target KPIs
for MRO). The activation / deactivation of MRO are triggered by the pre- configuration.
Minimize the handover failures rate/Reduce the unnecessary handovers/Increase the network
capacity/Decrease UE power consumption
LR15 Supported & Rel10 SON MRO Feature
Decrease congestion probability/Achieve the optimum E-UTRAN performance/Increase network

capacity/Increase the network load balancing capability
intra-frequency camp load balancing(serving cell and neighbor cell frequency priority is the same) and
traffic load balancing.
Decrease collision probability and improve radio resource efficiency

Decrease collision probability and improve radio resource efficiency,Reduce access delay of
PRACH,Avoid PRACH interference between cells and Minimize the manual intervention
Minimized the system collects UE measurements autonomously and Minimize the need of manual
drive tests.
Minimized the system collects UE measurements autonomously and Minimize the need of manual
drive tests.
Rel10 LTE Advanced Load Balancing : eNodeB exchanges load information through the RIM procedure
over the S1 interface, and then calculate the load amount of the serving cell and its inter-RAT neighbor
cell
eNodeB will deliver the inventory information to OMC after eNodeB startup
The feature enables to minimize operational efort during RRU provision It also autonomously makes
RRU working normally.
The feature minimizes manual eforts during the expansion of BBU boards. It can also automatically
ensure proper board operation
The feature enables to minimize operational efort during RRU provision It also autonomously makes
RRU working normally.
The feature minimizes manual eforts during the RRU provisioning procedure. It can also automatically
ensure proper RRU operation
The feature enables to solve software and hardware fault automatically
This feature supports intelligent OFDM symbol shutdown function in normal sub-frames, in order to
achieve power saving during no traffic or low traffic scenario
The feature enables to save energy consumption and decrease Operator’s OPEX.
The feature enables to save energy consumption and decrease Operator’s OPEX some special area
where eNB canbe shutdown for some specific period based operator’s configuration
LTE-Adv power saving feature
This feature shuts down RF channels for energy saving. the eNodeB can intelligently shut down RF
channels based on the cell load within a specified period, for example, changing two transmit channels
to one transmit channel, for MIMO degradation and RRU power consumption reduction.
This feature improves the transmission quality of the cell-edge in DL
In this feature the cells of the same eNodeB are coordinated with joint reception and processing of the
signal from the same UE to improve the coverage in UL
Rel 10 LTE-Adv
Rel 10 LTE-Adv
Rel 10 LTE-Adv
Rel 10 LTE-Adv
Rel 10 LTE-Adv
Rel 10 LTE-Adv
Rel 10 LTE-Adv
Rel 10 LTE-Adv
Inbound cell reselection/intra-RAT PS handover to Hybrid or CSG cell and Outbound cell
reselection/intra-RAT PS handover from Hybrid or CSG cell
This feature is used to solve the interference problem HetNet, in which low power nodes (e.g. Pico or
Femto) are placed throughout a macro Cell layout (overlaid).
Rel 10 LTE-Adv (LR15)
This feature is used to solve the interference problem for HetNet, in which low power nodes (e.g. Pico
or Femto) are placed throughout a macro cell layout (overlaid).
The feature includes automatic neighbor cell addition and deletion in the Hetnet
The feature includes X2 detection and deletion
The AAS supports individual tilt setting in Tx (DL) and Rx (UL)
AAS
AAS
AAS
AAS
AAS
AAS
AAS
3GPP Compliance as per Rel11
LTE Advaced Rel 11 UE Cat 9
This feature detects the location of a UE in the LTE network in OTDOA positioning mode to provide the
location information about the UE for value-added services such as the emergency call service and
automotive navigation.
Services Related to ETWS
Services reated to CMAS. for informing mobile terminal users of current alarm event such as child
abduction, by sending commercial warning notifications
LTE Advanced & related to IoT. This feature, applicable to the Internet of things, controls access of MTC
terminals to guarantee system stability
LTE-Adv & IoT Related. This feature is applicable to overload control on MTC terminals in a scenario
where the system or cell experiences high load in the Internet of things. This prevents the networks
(RAN and CN) from being overloaded and ensures the system (or cell) stability.
This feature detects the location of a UE in the LTE network in Qcell deployment to provide the location
information about the UE for value-added services such as intelligent shopping center
LTE-Adv. This feature ensures that a UE can operate properly when moving between diferent network
frequency bands by sending Multiple Frequency Band Indicator (MFBI) to the UE. This solves the
compatibility problem of a UE accessing and moving between diferent network frequency bands in the
scenario where the frequency bands are overlapped with each other or contained by other frequency
bands.
This feature optimizes the CSFB performance in a scenario consisting of LTE, UTRAN, and GERAN. For
the measurement-based CSFB mode, this feature avoids the LAU procedure to shorten the time delay
of CSFB and guarantee the CSFB success rate
This feature is used in multi LTE frequency deployment and VoLTE deployment scenario, the
network provide flexible service management strategy. According to voice/data service type,
the network can provide different services in different LTE frequencies.
This feature is used in LTE network, the network provide flexible handover enhancement
strategy. According to different service characteristics, the network can configure QCI level
measurement parameters to provide different handover strategy
This feature is used in LTE network, especially multi LTE frequency deployment scenario,
according to LTE user subscription information, the network perform differentiated mobility
management with local strategy mapping to indicator user to different frequencies.
This feature is used in LTE high-speed network (such as high-speed train) and normal, LTE
network co-existence scenario. According to UE speed detection, the network guarantee
high-speed UEs stay in high-speed network, avoid ordinary UEs stay in high-speed network,
thus improve high-speed UE experience
supports the RIM procedure. This feature is used in LTE network and UTRAN network co-
existence scenario. According to both signaling quality and load status of UTRAN neighboring
cell, the network select handover target cell to avoid UE handover to higher load UTRAN
neighboring cell and raising internal load balancing among UTRAN multi frequency
This feature is used in LTE multi PLMN network, or LTE network and UTRAN/GERAN multi
PLMN network co-existence scenario. The network provides flexible frequency or network
selection strategies
LR15 VOLTE Support
LR15 VOLTE Support

LR15 VOLTE Support
This feature enables a maximum of four operators to share an LTE network in shared carrier
mode.
This feature is used in LTE RAN sharing scenario, especially multi LTE frequency deployment
scenario, according to LTE user subscription information, the network perform differentiated
mobility management with local strategy mapping to indicator user belong to different
operator to different frequencies
This feature is used in LTE dedicated carrier sharing scenario, the network supports detecting
and adding missing neighboring cells through terminal measurements, to improve system
handover performance
Improve voice quality of VoLTE
Improve voice capacity of VoLTE
LR 15 Supported
LR 15 Supported
LR 15 Supported
This feature is used to improve VoLTE coverage and reduce the eNodeB load, increasing the
system capacity and improving user experience, by adjusting the codec rate.
This feature supports SDMA for super cell, in order to improve system capacity obviously.
Support non-standard .bandwidth such as 4.6M. Support non-standard .bandwidth such as

4.6M by RRU filter redesign and BBU scheduling algorithm.
This feature ensures that the most important data will be sent in the fastest speed, packets
from higher priority queues have a very low delay, the performance indicators such as the
loss rates and pass rates can get a certain degree of protection when the network congestion
Improve the reliability of IPSec path. When the LTE system deployment have independent
security gateway, eNodeB can be set different IPSec tunnel with two security gateway.
This feature measures the performance of bearer networks based on the IETF TWAMP,
providing a basis for monitoring and fault location
LR15 LTE-Adv Rel10. The feature supports to detect the availability and priority about the
CoMP neighbor. So the effort for the CoMP neighbor analysis and configuration can be
reduced and even saved
This feature enables PUCCH resource self-adaption based on the monitoring of UE number,
physical resource block (PRB) usage, and based on the result changes the parameters about
physical resources , and can bring the following benefits:  Balance the user experience and
resource usage of the network in different heavy traffic scenario
 Reduce the complexity and efforts of manual operation.
The feature keeps maximum user experience when available antennas decrease. So the
network performance will be kept steady and less affect in real time.
The eNodeB power consumption is displayed on the OMC in a visual way. This feature
supports visual display of BBU and RRU power consumptions on the OMC/SON, so that
energy saving effects can be easily determined.
This feature enables OFDM symbol shutdown in case of MBSFN subframes during the low-
traffic period for further energy saving
LR15 LTE-Adv Rel10
LR15 LTE-Adv Rel10
LR15 LTE-Adv Rel10
WIP
LR 16 Supported feature LTE-Adv Rel10


015 SW release and no ommissions have been done
eature/license to be classified as IDEA Basic and vendor will have to provide at no additional costs to IDEA
way of Licensing.
include all the pre-requisite features

Reason Capacity Impact on IDEA Traffic Profile - Medium
No Change
No Change
No Change
No Change
No Change
150, 50 No Change
No Change
1.only for 20MHz;

2.MME need add some equ; No Change
3.UE need support;
No Change
Support，no this scence The more system bandwidth,the more capacity.
The more system bandwidth,the more capacity.
bandwith is not enough No Change
bandwith is not enough No Change
No Change
no this scence No Change
no site plan to coverage so far No Change

no site plan to coverage so far No Change
now no have this service现在应该没有需要这样的业务

No Change
now no have this service现在应该没有需要这样的业务

No Change
eNB透传，没有参数 No Change
1.only for 20MHz;

2.MME need add some equ：BMSC&MCE No Change
3.UE need support;
1.CN do not have IMS; No Change

2.LTE do not support voice now.
need CSON,Updage dependency with C-SON No Change
If nessary can open,but it cost some recourse.可以开通，会有信令流， No Change

消耗资源
No Change
No Change
No Change
No Change
No Change
No Change
No Change
No Change
No Change
No Change
跨站重建立 No Change
Suggest open从指导书看建议看起，有好处，减小信令开销 No Change
No Change
Idea no suggest this stragety No Change
No Change
No Change
No Change
No Change
No Change
Support;No this scene No Change
only one LTE frequency now No Change

Support;Need CN support，now RJS fail,because CN reason核心网还在 No Change

调整中
Support;Need CN support，now RJS fail,because CN reason核心网还在 No Change

调整中
idea no suggest No Change

too less Ues support，idea no suggest No Change
support,No this scene No Change
idea suggest CSFB to GSM

No Change

No Change
No Change
Idea do not need this stragety now,if need we can open No Change
Netweok is not shared and only one PLMN now No Change
No TDD network now No Change
For VOLTE No Change
No Change
1.now do not separate high and low service; No Change

2.it is bad for KPI,E-RAB drop rate maybe increase;
no high load cell now

No Change
no high load cell now No Change
due to terminal No Change
no high load cell now No Change
not high load cell now No Change
parameter name：voIPSwitch No Change

No Change
No Change
NO GBR server now No Change
No Change
No Change
No Change
No Change
IP+UDP+RTP No Change
IP+UDP No Change
most ue do not support,we can open No Change
most ue do not support,we can open No Change
No Change
only can add 4 method No Change
No Change
No Change
No Change
No Change
No Change
No Change
No Change
Network is not shared and only one PLMN No Change

Network is not shar No Change
Network is not shared No Change

No Change
No Change
No Change
it is usually used for VOLTE No Change
it is usually used for VOLTE No Change
No Change
No Change
No Change
No Change
No Change
No Change
Increase capacity according to rank of MIMO radio channel
Delete, because new frequency domain algorithm for VoLTE is PRB No Change
randomized allocation.
only select one,we need to compare and then decide No Change
only select one,we need to compare and then decide No Change

No Change
Volte No Change
Volte No Change
no 4 antenna Increase capacity according to rank of MIMO radio channel
parameter：mumimoEnableUl，start to open Increase capacity according to rank of MIMO radio channel
no GBR server now No Change
No Change
all normal CP now No Change
only select one No Change
no have this scene No Change
Higher coding schema can increase capacity according to
Higher coding schema can increase capacity according to
No Change
ZTE suggest open loop；closed loop is sensitived to speed,闭环空间复用 Increase capacity according to rank of MIMO radio channel
对速率敏感
zte suggest open loop；and mutex Increase capacity according to rank of MIMO radio channel
no 4 antenna No Change
now use IRC No Change
No Change
no 4 receive，only 2.天线配置是2T2R. No Change
no 4 receive，only 2.天线配置是2T2R. No Change
we can open ,need to try. Increase capacity according to rank of MIMO radio channel
UL MIMO is closed No Change
No Change
No Change
No Change
No Change
now only 2 antenna No Change
now only 2 antenna No Change
MRC No Change
No Change
1.PUCCH blanking cost some ul resource and it is bad for ul throughput;

No Change
2.it is good for reduce interference,and now ul has less interference.
LTE USE 2*20W. No Change
Feature is ok,but not plan super cell now No Change
no plan No Change
no plan，now only use 5MHz No Change
no plan，now only use 5MHz No Change
No Change
No Change
No Change
No Change
No Change
No Change
No Change
No Change
No Change
ZTE support and idea did not plan V6 IP No Change
No Change
No Change
No Change
No Change
No Change
No Change
No Change
参数未空，未配置 No Change
No Change
No Change
Delay to LR17 No Change

Delay to LR17 No Change
No Change
No Change
not add GPS No Change
no add clock source No Change
No Change

1.only one synchronizatio method
No Change
2.no have this scene
do not select this GPS No Change
No Change
not select Chinese beidou,no GPS No Change
No Change


No Change
No Change
too diferent scene,不知道怎么回答 No Change
too diferent scene,不知道怎么回答 No Change
没查到 No Change
没查到 No Change
没查到 No Change
can not add idea&zte suggestion rules No Change
can not add idea&zte suggestion rules No Change
No Change
measure interF and interRAT will cost some recourse No Change
we add the rules No Change
No Change
we can open ,need to try. No Change
now no need and this maybe interface UE mobility可能影响UE的移动性 No Change

能（切换参数和重选参数变化了）

existing cover scene do not need to opptimization rach,it is OK. No Change

existing cover scene do not need to opptimization rach,it is OK. No Change
RJS do not add NDS now,after add NDS we can open this/ No Change
RJS do not add NDS now,after add NDS we can open this/ No Change

No Change
No Change
No Change
No Change
not belong to SON No Change
only one frequency,do not suggest close No Change
for coverage and user perception No Change
No Change
do not suggest ,for user perception No Change
RJS will do this No Change
RJS will do this No Change
only one LTE frequency now Increase capacity according to aggregated carriers
No Change
Support，need to add board No Change
Support，need to add board No Change
No HetNet scene No Change

智能天线Advanced AntennaSystems No Change

必须遵守R11，这都是个Feature啊，奇才 No Change
no parameter,default No Change
If nessary can open,but it cost some recourse.可以开通，会有信令流， No Change

消耗资源
If nessary can open（Earthquake and Tsunami Warning System）地震海 No Change

啸系统
No Change
no have Machine Type Communication 没有机器类型通讯场景，如智 No Change

能停车，智能水表
no have Machine Type Communication 没有机器类型通讯场景，如智 No Change

能停车，智能水表
no Qcell No Change
No Change
only one frequency now No Change
do not suggest,because there is not diferent qci server now. No Change
Idea no not need this stragety now,if need we can open No Change
no High-Rail Coverage and high-speed coverage No Change
Need CN support No Change
only one plmn No Change
no volte No Change
no volte No Change
no volte No Change
Volte No Change
Volte No Change
貌似是默认开启的吧？？ No Change
NO VOLET，this feature is used for volte No Change
no plan super cell now No Change
support,but no this scene No Change
No Change
No Change
No Change
No Change
no aas不是智能天线 No Change
No Change
No Change
Increase capacity according to spectrum status
most ue do not support,we can open Higher coding schema can increase capacity according to
only 2T2R Increase capacity according to rank of MIMO radio channel
JR:Join reception 个人认为是基于下面2个Feature的，但是下面的2个 No Change

Feature未开启，因为没有这个场景，都是宏站
ONLY macro sites No Change
not understand No Change
not understand No Change

Pre-requisite features if Any IDEA License mehodology - Anything required ?
None None
None None
None None
None None
None None
None None
None None
None None
None None
None Bandwidth License
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
ZLF31-07-015/ZLF31-07-017 None
ZLF31-07-023/ZLF31-07-024 None
None None
ZLF31-07-015/ZLF31-07-017 None
None None
None None
ZLF31-07-012 None
ZLF31-07-015 None
None None
None None
None None
None None
None None
None None
ZLF31-09-001 None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
ZLF31-12-002 None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
ZLF31-13-025 Advanced VoIP Support None
None None
ZLF31-13-007 Long DRX None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
ZLF31-14-031 None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
ZLF32-01-001 None
ZLF32-00-005 None
None None
None None
None None
ZLF32-02-002
None
ZLF32-02-003
None None
ZLF32-02-002 None
None None
None None
None None
ZLF32-00-003 None
None None
None None
None None
ZLF32-04-001 None
ZLF32-04-001 None
ZLF32-04-001 None
ZLF32-04-001 None
ZLF32-04-001 None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
ZLF32-05-001
None
ZLF32-05-003
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
ZLF33-01-004 None
ZLF33-01-004 None
None None
None None
None None
None None
None None
None None
None None
None None
ZLF33-01-022 None
ZLF33-01-023 None
ZLF33-01-022
ZLF33-01-023
ZLF33-01-024 None
ZLF33-01-026
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
ZLF32-05-001 GPS Synchronization None
None None
None None
None None
None None
None None
None None
ZLF31-07-023 LTE->UTRAN CSFB and ZLF31-07-024 LTE- None

>GERAN CSFB
None None
ZLF31-07-003 Intra-LTE Intra Frequency HO, ZLF31-07-012 None

Intra-LTE Inter Frequency HO
None None
None None
ZLF31-07-015 LTE->UTRAN PS Handover None
ZLF31-07-003 Intra-LTE Intra Frequency HO, ZLF31-07-

012 Intra-LTE Inter Frequency HO, ZLF31-07-015 LTE-
>UTRAN PS Handover, ZLF31-07-023 LTE->UTRAN CSFB, None
ZLF31-07-024 LTE->GERAN CSFB, ZLF31-12-008 Inter
PLMN Mobility
None None
None None
None None
ZLF31-12-002 Shared Carrier Sharing None
ZLF31-12-001 Dedicated Carrier Sharing and ZLF31-12- None

002 Shared Carrier Sharing
ZLF31-12-001 Dedicated Carrier Sharing None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
ZLF33-05-002 Intelligent OFDM Symbol Shutdown None
None None
None None
None None
None None
ZLF34-00-013 Carrier Aggregation (Inter-Band), ZLF34- None

00-015 Carrier Aggregation (Intra-Band)
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
None None
Vendor - Pre-requisite functionality required from
IDEA FDD Basic/Optional - New LR16
Core/Any nodes
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Optional
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Optional
None Basic
None Basic
None Basic
None Basic
MME: ZUF-52-05-012 Location Service

ZUF-52-06-009 SLg Interface Basic
ZUF-52-06-010 SLs Interface
None Optional
MME:ZUF-52-05-013 LTE IMS Emergency Session

Support Basic
PGW:ZUF-63-09-013 Emergency Service
None Basic
MME: ZUF-52-05-012 Location Service

ZUF-52-06-009 SLg Interface
Basic
ZUF-52-06-010 SLs Interface
None Basic
MME:ZUF-52-01-007 Paging and Network Triggered
Service Request Basic
ZUF-52-01-036 Paging Policy
None Basic
MME:ZUF-52-04-002 NAS Encrypted Protection Basic
ZUF-52-04-003 NAS Integrity Protection
None Basic
None Basic
None Basic
MME：ZUF-52-06-001 S1-MME Interface

SGW：ZUF-62-05-004 S1-U Interface Basic
None Basic
MME：ZUF-52-01-016 MME POOL Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Optional
None Optional
None Optional
None Basic
None Basic
None Basic
ZUF-52-03 Handover Basic

None Optional
MME：ZUF-52-05-008 SRVCC Basic
MME：ZUF-52-05-008 SRVCC Basic

PGW：ZUF-63-01-012 SRVCC Support
MME：ZUF-52-01-027 CS Fallback Basic
ZUF-52-06-007 SGs Interface
None Optional
MME：ZUF-52-01-003 Intra-MME TA Update

ZUF-52-01-004 Inter-MME TA Update
ZUF-52-01-005 TA/RA Update between MME and GnGp Basic
SGSN

None Optional
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
ZUF-52-02-020 QCI Extension Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
PGW:ZUF-63-09-016 TCP Proxy Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Optional
None Optional
MME：ZUF-52-01-033 Support Multi-PLMN Optional
None Optional
None Optional
None Optional
None Optional
MME：ZUF-52-01-033 Support Multi-PLMN Optional
None Optional
None Optional
None Optional
MME：ZUF-52-01-027 CS Fallback Optional

None Optional
MME：ZUF-52-01-027 CS Fallback Optional

None Optional
None Optional
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Optional
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Optional
None Optional
None Basic
None Basic
None Basic
None Basic
None Optional
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Optional
None Basic
None Basic
None Basic
None Basic
None Basic
MME：ZUF-52-02-015 PDP Type for IPv6

PGW：ZUF-63-01-008 IPv6 EPS Bearer Service Basic
MME：ZUF-52-02-016 IPv4v6 Dual Stack

PGW：ZUF-63-01-009 IPv4v6 Dual Stack EPS Bearer Basic
Service
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Optional
None Optional
None Optional
None Optional
None Optional
None Optional
None Optional
None Optional
None Basic
None Basic
None Optional
None Optional
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Optional
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
MME：ZUF-52-05-017 MDT Basic
MME：ZUF-52-05-017 MDT Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Basic
None Optional
None Optional
None Optional
None Optional
None Basic
None Basic
None Basic
None Optional
None Optional
None Optional
None Optional
None Optional
None Optional
None Optional
None Optional
None Optional
None Optional
None Optional
None Optional
None Basic
None Optional
None Optional
None Basic
None Optional
None Optional
CN: supports OTDOA positioning

E-SMLC: supports OTDOA positioning Optional
Optional
CN:supports the ETWS function
CN: supports the CMAS function Optional
CN: supports the MTC access control function Optional
None Optional
None Optional
None Optional
CN: supports the LAI-based enhanced CSFB function Optional
None Optional
None Optional
CN: supports customized SPID Optional
None Optional
CN: supports the RIM procedure Optional
None Optional
CN: supports VoLTE Optional
CN: supports VoLTE Basic

CN: supports VoLTE and SRVCC Basic
None Optional
CN: supports customized SPID Optional
None Optional
None Basic
None Basic
None Optional
None Optional
None Optional
None Optional
None Optional
None Optional
None Optional
None Optional
CN supports TWAMP Optional
None Basic
None Basic
None Basic
None Basic
None Basic
None Optional
None Optional
None Optional
None Optional
None Optional
None Optional
None Basic
None Optional
None Optional
None Basic
None Basic
None Basic
None Optional
None Optional
None Optional
None Optional
None Optional
None Optional
IDEA FDD Optional Features Grouping - New LR16
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
IDEA Optional Features - eMBMS
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
IDEA Optional Features - Others
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package DRX length
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
IDEA Optional Features - CDMA
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
IDEA Optional Features - TDD
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
IDEA Optional Features - RAN-SHARING


Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
IDEA Optional Features - IPSEC

Basic Package
Basic Package

Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
IDEA Optional Features - CA

Basic Package
Basic Package
Basic Package
IDEA Optional Features - SmallCell

Basic Package
Basic Package
IDEA Optional Features - TDD
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package
Basic Package

Basic Package
Basic Package
Basic Package
Basic Package

RRC Connection state timers
Feature Name STATE状态 Release
System Compliance for 3GPP E-UTRAN R8 on R8
System Improvements for 3GPP E-UTRAN R9 on R9

System Improvements for 3GPP E-UTRAN R10 on R10
E-UTRAN Interfaces on R8/R9
Radio Channels(except EMBMS Channels) on R8/R9
Support UE Category 1~3 on #N/A
Support UE Category 4 on R8/R9
Radio Channels(EMBMS Channels) of R10
Support UE category 6 on R10

10MHz,20MHz on R8/R9
5MHz,15MHz on R8/R9
3MHz of R8/R9
1.4MHz of R8/R9
Peak Data Rate/cell(DL/UL): 100Mbps/50Mbps on R8/R9
Peak Data Rate/cell(DL/UL): 150Mbps/50Mbps on R8/R9
120KM/H on R8/R9
350KM/H OFF R8/R9
15km on R8/R9
40km OFF R8/R9
SRB1 and SRB2 for DCCH + 4 DRB Combination on R8/R9
on #N/A
SRB1 and SRB2 for DCCH + 8 DRB Combination on R8/R9
on #N/A
Location Service(CID, AGNSS) on R8/R9
eMBMS OFF R10
Emergency Call OFF R9
System Load based Dynamic AC Barring of R10

Location Service(ECID) of R9
System Information Broadcasting on R8/R9
Paging on R8/R9
RRC Connection Management on R8/R9
NAS Signaling Transfer on R8/R9
UE Context Management on R8/R9
UE Capability Enquiry on R8/R9

Radio Access Bearer Management on R8/R9
on #N/A
S1 Interface Management on R8/R9
X2 Interface Management on R8/R9
S1-Flex on R8/R9
Context Fetch on R8/R9
LTE State Transition on R8/R9
Intra-LTE Cell Selection and Reselection on R8/R9
Intra-LTE Redirection of R8/R9

Intra-LTE Intra Frequency HO on R8/R9
LTE->GERAN Cell Reselection on R8/R9
LTE->GERAN Redirection on R8/R9

on #N/A
LTE->UTRAN Cell Reselection on R8/R9
LTE->UTRAN Redirection on R8/R9

on #N/A
LTE-1xRTT Cell Reselection of R8/R9
LTE->eHRPD Cell Reselection of R8/R9
LTE->eHRPD Redirection of R8/R9

Intra-LTE Inter Frequency HO of R8/R9
LTE->GERAN CCO without NACC of R8/R9
LTE->GERAN CCO with NACC OFF R8/R9
LTE->UTRAN PS Handover of R8/R9
UTRAN->LTE PS Handover of R8/R9
LTE->GERAN PS Handover of R8/R9
GERAN->LTE PS Handover of R8/R9
LTE->eHRPD PS Optimized Handover of R8/R9

LTE->UTRAN SRVCC of R8/R9
LTE->GERAN SRVCC of R8/R9
CSFB to UTRAN on R8/R9
on #N/A
CSFB to GERAN on R8/R9
on #N/A
CSFB to 1xRTT of R8/R9
Subscription Based Mobility Management OFF R8/R9
LAI enabled CSFB Enhancement OFF R10
Mobility with TDD network of R8/R9

Service aware IRAT Handover management of R8/R9
Radio Admission Control on R8/R9
Congestion Control of R8/R9
Intra-LTE Load Balancing of R8/R9
of #N/A
IRAT L->U Load Balancing of R8/R9
ECN of R9
LTE Load Control of N/A
IRAT U->L Load Balancing of R10
VOIP Admission Control Enhancement on R10
Standard QCI (1~9) on #N/A

Extended QCI on R8/R9
GBR service rate downsizing OFF R10
MAC PDU and Functions on R8/R9
RLC PDU and Functions on R8/R9
PDCP PDU and Functions on R8/R9
Header Compression Profile 0x0000 on R8/R9
Header Compression Profile 0x0001 on R8/R9
Header Compression Profile 0x0002 of R8/R9
TCP Optimization on R8/R9

Reserved Mode of R8/R9
128-EIA1 on R8/R9
128-EIA2 on R8/R9
EEA0 on R8/R9
EEA1 on R8/R9
EEA2 on R8/R9
128-EIA3 on R10
EEA3 on R10
Dedicated Carrier Sharing OFF R8/R9
Shared Carrier Sharing OFF R8/R9
Multi PLMN Support OFF R8/R9

UE Route Selection OFF R8/R9
Basic Mobility Control of RAN Sharing of R8/R9
Transport Traffic Separation of RAN Sharing OFF R8/R9
Operator Specific Radio Resource Management OFF R8/R9
Inter PLMN Mobility OFF R8/R9
Operator Specific Transport Resource Management OFF R8/R9
IRAT L->U Mobility of RAN Sharing OFF R8/R9
Operator Specific PM/FM OFF R8/R9

Voice Management (CSFB to UTRAN) of RAN Sharing OFF R8/R9
IRAT L->G Mobility of RAN Sharing OFF R8/R9
Voice Management (CSFB to GERAN) of RAN Sharing OFF R8/R9
Operator specific User/Service priority management of Sh OFF R8/R9
Operator Specific RRC Resource Management of Shared Ca OFF R8/R9
UL/DL HARQ on R8/R9

Dynamic Scheduling ON R8/R9
UL/DL Frequency Selective Scheduling ON R8/R9
TTI Bundling of R8/R9
Semi-Persistent Scheduling of R8/R9
Long DRX on R8/R9
Short DRX on R8/R9
QoS Scheduler on R8/R9
Pseudo GBR for NGBR on R8/R9
Advanced AMC on R8/R9
PDCCH Link Adaptation on R8/R9
Enhanced Adaptive Intra-Mode MIMO Schemes on #N/A
Adaptive Inter-Mode MIMO Schemes on R8/R9

Adaptive Frequency Selective/Non Frequency Selective Sc OFF R8/R9
Static ICIC OFF R8/R9
Dynamic ICIC OFF R8/R9
Advanced Operator Configurable QoS Scheduler on R8/R9
Advanced VoIP Support OFF R8/R9
VoIP DRX OFF R8/R9
Adaptive Inter-Mode MIMO Schemes for 4*2 MIMO OFF R8/R9
Adaptive UL MIMO Mode OFF R8/R9
Full Adaptive Intra-Mode MIMO Schemes for 4*2 MIMO OFF R8/R9
MBR > GBR in R10 ON R10
Basic Physical Layer Support on R8/R9
Extended CP OFF R8/R9
PRACH Format 0 on R8/R9

PRACH Format 1 OFF R8/R9
PRACH Format 2,3 OFF R8/R9
PRACH Restricted Set Preamble OFF R8/R9
UL QPSK/16QAM, DL QPSK/16QAM/64QAM on R8/R9
UL 64QAM ON R10
TX Diversity (2 Antennas) on R8/R9
Open Loop 2*2 Spatial Multiplexing (LD-CDD) on R8/R9
Closed Loop 2*2 Spatial Multiplexing of R8/R9
Closed Loop 2*2 Spatial Multiplexing (rank = 1) of R8/R9
TX Diversity (4 Antennas) OFF R8/R9
Open Loop 4*2 Spatial Multiplexing (LD-CDD) of R8/R9
Closed Loop 4*2 Spatial Multiplexing of R8/R9
Closed Loop 4*2 Spatial Multiplexing (rank = 1) OFF R8/R9
Open Loop 4*4 Spatial Multiplexing (LD-CDD) OFF R8/R9
Uplink 2-Ways MRC OFF R8/R9
Uplink 2-Ways IRC ON R8/R9
Uplink 4-Ways MRC OFF R8/R9
Uplink 4-Ways IRC of R8/R9

Uplink MU-MIMO with 2 layers of R8/R9
UL Open-Loop Power Control With FPC Supported of R8/R9
PUSCH/SRS Closed-Loop Power Control on R8/R9
PUSCH/SRS Closed-Loop Power Control, OI Based on R8/R9
PUCCH Closed-Loop Power Control on R8/R9
PUSCH Frequency Hopping on R8/R9
Uplink 8-Ways MRC of R8/R9
Uplink 8-Ways IRC of R8/R9
PUCCH IRC of R8/R9
OCNG on R8/R9
PUCCH Blanking of R8/R9
GL Power Sharing (LTE down & give power t gsm) of R8/R9
Super Cell on #N/A
Split cells by 2-path RRU of R8/R9
Compact Bandwidth of R8/R9
Dynamic Bandwidth Extension of R8/R9

FE/GE Interface ？？on N/A
2 FE/GE Transmission Interface ？？on N/A
Daisy Chain Network Organization ？？on N/A
2 X 10GE Transmission Interface ？？on N/A
VLAN ？？on N/A
VLAN Mapping ？？on N/A
Link Aggregation ？？on N/A
DHCP ？？on N/A
IPv4 Protocol Stack ？？on N/A
IPv6 Protocol Stack ？？OFF N/A
IPv4/IPv6 Dual Stack ？？on N/A
IPv4 Address on N/A
IP Jumbo Frame ？？on N/A
Traffic Marking and Mapping ？？on N/A
Uplink Bandwidth Assignment ？？on N/A
Traffic Statistics ？？on N/A
Traffic Aggregation with Ethernet Interface ？？on N/A

IPsec ?? N/A
IKEv1 ?? N/A
IKEv2 ?? N/A
IPsec Protect S1 CP Traffic ?? N/A
IPsec Protect S1 MP Traffic ?? N/A
IPsec Protect S1 UP Traffic ?? N/A
IPsec Protect X2 Traffic ?? N/A
PKI and Certificate Management ?? N/A
ACL on N/A
SSH on N/A
IPsec QoS of N/A
IPSec for IPv6 of N/A
SFTP on N/A
SNMP on N/A
GPS Synchronization of N/A
Synchronization Ethernet of N/A
IEEE1588v2 Frequency Synchronization on N/A
Line Clock of N/A

1PPS+TOD of N/A
Synchronization Priority Scheme of N/A
Glonass Synchronization of N/A
IEEE1588v2 Phase Synchronization on N/A
Beidou Synchronization of N/A
NTP Time Information ON N/A
802.3ah ？？of N/A

802.1ag ？？of N/A
Y.1731 ？？of N/A
BFD ？？of N/A
IP SLA ？？of N/A
Transport Resource Static Sharing ??on N/A
Transport Resource Dynamical Sharing ??on N/A
eNB Self-discovery OFF R8
eNB Self-discovery Enhanced OFF R8
eNB Authentication off N/A
Transport Self-setup off R8
Self-Test off N/A
Automatic Configuration PCI Based on Centralized Assign OFF R8
Automatic Configuration PCI Based on Distributed Assign OFF R8
Intra-Frequency ANR on R8
Inter-Frequency ANR of R8
Inter-RAT LTE-GSM ANR OFF R8

Inter-RAT LTE-UMTS ANR OFF R8
Intra-Frequency Fast ANR OFF R8
Inter-Frequency Fast ANR OFF R8
LTE ANR Self-Learning OFF R8
Neighbor Cell Configuration Auto-update on R8
Intra-LTE Coverage Problem Detection of R10
Intra-Frequency Mobility Robust Optimization of R9
Inter-Frequency Mobility Robust Optimization of R9
Inter-RAT LTE-GSM Mobility Robust Optimization of R10
Inter-Frequency Mobility Load Balancing OFF R9
Intra-Frequency Mobility Load Balancing OFF R9
RACH Power Parameters Optimization OFF R9
RACH Group and Physical Resource Parameters Optimizati OFF R10
Immediate MDT ON R10
Logged MDT ON R10
Inter-RAT LTE-UMTS Mobility Robust Optimization of R10

Inter-RAT LTE-UMTS Mobility Load Balancing of R10
Automatic Inventory on R8
BBU board self-detection of N/A
of #N/A
RRU self-detection of N/A
of #N/A
Software & Hardware Self-Healing of R9
Intelligent OFDM Symbol Shutdown ON N/A
Intra-RAT Overlaid Cell Shutdown OFF R10
Time Scheduled eNB Shutdown OFF R10
Intelligent PSU Shutdown ?? R10
Intelligent Channel Shutdown of R10
DL intra-eNB CoMP (Coordiated Scheduling) of R10
UL intra-eNB CoMP (Joint Reception) of R10
Carrier Aggregation(Inter-Band) of R10

Carrier Aggregation(Intra-Band) of R10
Carrier Aggregation(three carriers) OFF R10
CA based ICIC OFF R12
UL SU-MIMO on R10
DL inter-eNB CoMP(Coordinated Scheduling) of R10
UL inter-eNB CoMP (Joint Reception) of R9
Carrier Aggregation(FDD+TDD) OFF R12
Mobility with Hybird or CSG cell OFF R10
static eICIC for Het-Net(ABS) OFF R10
feICIC for Het-Net(ABS) OFF R10
Dynamic eICIC for Het-Net(ABS) OFF R10
Hetnet ANR OFF R10

Hetnet X2 Self estalishment OFF R10
Hetnet Mobility Load Balance OFF R10
Independent Tilt per DL/UL of N/A
Individual tilt per carrier with the same technology of N/A
Individual tilt per technology of N/A
Self-healing compensation in case of radio of N/A

module failure
Beam shape control of N/A
Circular polarization configured by software of N/A
Vertical sectorization of N/A
Virtual four way diversity of N/A
System Complying with 3GPP E-UTRAN R11 on N/A
Support UE category 9 on R11
Location Service(OTDOA) OFF R9
ETWS OFF R9
CMAS OFF R9
MTC Access Control of R10
MTC EAB of R11
Location Service(Qcell) OFF R8/R9
MFBI ?? R10
Measurement based LAI enabled CSFB Enhancement OFF R10
Service Triggered Inter-frequency HO of R8/R9
QCI Level Mobility Management Enhancement of R8/R9
Customized Subscription Based Mobility Management of R8/R9
UE Speed Based Mobility Management Enhancement of R8/R9
LTE->UTRAN PS Handover Enhancement OFF R8/R9
Multi PLMN Mobility Management Enhancement OFF R8/R9
Neighbor cell VoLTE capacity based Intra-LTE Handover OFF R8/R9

VoLTE User Experience Awared Inter-frequency Handover OFF R8/R9
VoLTE User Experience Awared SRVCC OFF R8/R9
Further multi PLMN Shared Carrier OFF R8/R9
Operator Specific Customized Subscription Based Mobili OFF R8/R9
Intra-LTE ANR of Dedicated Carrier Sharing OFF R8/R9
Voice Quality Enhancement for VoLTE OFF R8/R9

Voice Capacity Enhancement for VoLTE OFF R8/R9
NI Based Interference Avoidance Scheduling ON R8/R9
Small Packets Service Optimization ON R8/R9
TCP RTT Optimization ON R8/R9
Explicit Congestion Notification-Alternative(ECN-A) OFF R8/R9
SDMA for Super Cell of R8/R9

Supporting non-standard bandwidth by lossy compressionon #N/A
Traffic Congestion Management on N/A
IPSec Tunnel Backup ？？ N/A

TWAMP Server ？？on N/A
CoMP Self Configuration of R10
Adaptive capacity adjustment of N/A
Antenna Self-adaption of N/A
Power Consumption Visualization ？？ R9
Intelligent OFDM Symbol Shutdown, Phase 2 off N/A
Cloud CA (centralized) OFF R10

RRC user based CA enable and backof OFF R10
Flexible Scell configuration of multi-carriers OFF R10
UL Dynamic Carrier Extension of R8/R9
Carrier Aggregation(UL 2CC) OFF R11
Support DL 256QAM of R12
Support DL MIMO4*4 based on TM9 OFF R10

LTE-U OFF R13
LTE and WLAN aggregation OFF R13
Inter-eNB JR based on relax transmission bandwidth of R10
Intra-eNB JR between macro and micro OFF R10

Inter-eNB JR between macro and micro OFF R10
Carrier Aggregation(DL 3 CC, FDD+TDD) OFF R13
NB-IOT OFF R13
Cloud CA (distributed) OFF R10
service based PCC dynamic selection ?? R11
Netwok assistant CRS-IC without ABS ?? R11
HetNet Mobility Load Balance OFF R10
Explanation
3GPP R8 is the first release for LTE from 3GPP and covers specificat LTE mobile system; it was completed in Mar. 2009.
3GPP R9 is the further enhancement of 3GPP R8; it was completed in Mar. 2010.
It describes 3GPP R10 FDD basic functions of eNodeB.
It describes the connections between network elements in E-UTRAN
Logical channels, transport channels and physical channels are defined in 3GPP protocol;
#N/A
ZTE eNodeB supports UE category 4, with maximum DL/UL throughput 150Mbps/50Mbps.
Radio channels required for eMBMS( LTE Adv)
LTE Adv Rel 10 to support 2CC for DL

ZTE eNodeB supports 20MHz and10MHz bandwidths.
ZTE eNodeB supports 15MHz, 5MHz bandwidths.
ZTE eNodeB will support 3MHzbandwidths
ZTE eNodeB will support 1.4MHz bandwidths.
ZTE eNodeB supports cell radius extended to 15km. No site planned to cover such range
This feature supports the extended cell radius with LTE service coverage.
This feature supports multiple bearers to supply users more convenient services and improve user experience.
#N/A
This feature supports multiple bearers to supply users more convenient services and improve user experience.
#N/A
This feature detects the location of a UE in the LTE network through the Assisted Global Navigation Satellite System (AGNSS) or
basic Cell ID (CID) positioning mode to provide the location information about the UE for value-added services such as the
emergency call service and automotive navigation.
Rel 10 LTE-Adv (LR15) : This feature provides the point-to-multipoint unidirectional multimedia broadcast mechanism to save
the resources in the network and improve the resource utilization
This feature supports emergency service in special scenario.
LR 15 Supported feature
This feature detects the location of a UE in the LTE network in E-CID positioning mode to provide the location information
about the UE for value-added services such as the emergency call service and automotive navigation
This feature enables the UE to obtain the latest system information such as network identification, cell selection and
reselection, initial access and measurement control and location information.
This feature enables paging of UEs.
This feature enables RRC connection between UE and E-UTRAN.
This feature enables information interaction between UE and EPC.
This feature enables UE information management between E-UTRAN and EPC to support user individual signaling.
This feature enables UE radio capability information transferred from UE to the network.
This feature enables E-UTRAN resources management for user data transport.
#N/A
This feature enables interaction between E-UTRAN and EPC.
This feature enables interaction between eNodeB and neighbor eNodeB.
This feature is used to:Implement networking redundancy;Implement MME load balancing.
This feature is used to improve the success rate of RRC re-establishment, thereby reducing rate of dropped call and improve
handover success rate.
to manage RR efectively by diferent states (RRC Active, RRC Only, RRC Idle & DRX State)
This is used for UE receiving registration area information , system information and other AS and NAS Information from the
PLMN. And if registered, UE can receive paging and notification messages from the PLMN, or initiate transfer to connected
mode.
This feature is used to guide UE to a suitable cell of E-UTRAN.
This feature is used to guarantee service continuality for subscriber mobility in intra frequency scenario.
This feature is used for UE receiving paging and notification messages from the PLMN,or initiate transfer to connected mode
in GERAN coverage, in case lack of LTE coverage.
This feature is used to guide UE to a suitable cell of GERAN.
#N/A
in UTRAN coverage, in case lack of LTE coverage.
This feature is used to guide UE to a suitable cell of UTRAN.
#N/A
in 1xRTT coverage, in case lack of LTE coverage.
in eHRPD coverage,in case lack of LTE coverage.
This feature is used to guide UE to a suitable cell of eHRPD.
This feature is used to guarantee service continuality for subscriber mobility in inter frequency scenario.
This feature is used to guarantee service continuality for subscriber mobility. 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
This feature is used to guarantee service continuality for subscriber mobility. 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

#N/A
#N/A
This feature is used to guarantee service continuality according to operator’s policies.
This feature is used for CSFB optimization and further reduces CSFB latency.
If we have one more TDD carrier

This feature enables diferent service types between voice and data,flexible IRAT measurement policy strategy.
The task of RAC (Radio Admission Control) is to admit or reject the establishment requests for new radio bearers, by taking in
QoS of in-progress and new services.
This feature enables best utilization of system resources by service priorities, and guarantees system stability.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.
This feature enables reasonable utilization of system resources by service priorities and further guarantees system stability,
Intra-LTE load balancing algorithms are used in multi frequencies scenario and may result in handover or cell reselection
decisions with the purpose of redistributing traffic from highly loaded cells to lower loaded cells.
#N/A
This feature enables reasonable utilization of system resources by service priorities and further guarantees system stability,
IRAT L->U load balancing algorithms are used in 3G Overlapping with LTE, and may result in handover or cell reselection
decisions with the purpose of redistributing traffic from highly loaded cells to lower loaded cells.
Explicit Congestion Notification-Alternative(ECN-A). This feature is used to improve VoLTE coverage and reduce the eNodeB
load, increasing the system capacity and improving user experience, by adjusting the codec rate.
This feature is used to guarantee system stability.In case network load excess of the maximum capacity, load control strategy
can be used.Network load control is mainly dependent on radio bearer release mechanism and is used per cell.
This feature is used to balance distribution of the traffic load over the serving UTRAN cell and its neighbor LTE cells in a
scenario consisting of LTE and UTRAN. The purpose of this feature is to efectively use the overall resources of the LTE/UTRAN
network system, improve the overall system capacity, and ensure system stability.
LR15 Supported for VOIP Services
#N/A
Extended QCI Support
This feature is used to provide flexible choice policy for operator in case of network congestion. When this function is enabled
eNodeB can reduce the guaranteed data rate for GBR service. The reduction of GBR data rate will be performed
according GBR service priority.
All the MAC PDU formats, including MAC CE formats are supported as per 3GPP TS 36.321. e.g. Scheduling information
reporting, Error correction through HARQ, Transport format selection, Logical channel prioritazation etc.
All the RLC PDU formats & functions are supported as per 3GPP TS 36.322. e.g. Transfer of upper layer PDUs, RLC re-
establishment, Duplicate detection (only for UM and AM data transfer) etc
All the PDCP PDU formats & functions are supported as per 3GPP TS 36.323. e.g. TTransfer of data (user plane or control
plane), Maintenance of PDCP SNs, Timer based discard, Duplicate discarding etc.
This feature enables overhead reduction of packet header on radio interface, A ROHC profile is a compression protocol, which
specifies how to compress specific
header combinations. ROHC profiles provide the details of the header compression framework . Profile 0x0000 is used for
uncompressed.
specifies how to compress specificheader combinations. ROHC profiles provide the details of the header compression
framework. Profile 0x0001 is used for RTP/UDP/IP
specifies how to compress specific header combinations. ROHC profiles provide the details of the header compression
framework. Profile 0x0002 is used for UDP/IP
specifies how to compress specific
header combinations. ROHC profiles provide the details of the header compression framework. Profile 0x0004 is used for IP
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
Improves user TCP traffic performance, This feature can monitor and control the transmission of the uplink TCP ACK to adjust
the UL data, When the UL data is decreased the TCP Ack/Nack information corresponding to DL Data is protected. It is also
used to distinguish and transmit the TCP ACK of UL Data to protect the UL throughput. It enhances the DL & UL transmissions.
This feature enables avoidance of fraudulent attack from the UE or network equipment that is disguised by the third party.
Integrity protection is provided to NAS and RRC signaling. The integrity protection of RRC signaling includes both integrity
protection and integrity verification and is performed in PDCP.EIA0 for null integrity protection algorithm is supported.
protection and integrity verification and is performed in PDCP.128-EIA1 for SNOW 3G algo is supported
protection and integrity verification and is performed in PDCP.128-EIA2 for AES algo is supported.
This feature enables confidentiality protection for the data & signalling stream. The aim is to ensure the communication
confidentiality between Ue & eNodeB. The ciphering procedure of RRC signalling and UP (User Plane) data is requested and
terminated in eNodeB.
terminated in eNodeB.128-EEA1 for SNOW 3G based algo is supported.
terminated in eNodeB.128-EEA2 for AES based algo is supported.
protection and integrity verification and is performed in PDCP.128-EIA3 for ZUC algo is supported.
terminated in eNodeB.128-EEA13 for ZUC based algo is supported.
This feature helps operators to reduce CAPEX and OPEX by building and maintaining one network. Simultaneous connection
with multiple independent core network architecture is supported. Also simultaneous connection with other shared or non
shared eNodeB is supported. Independent or common antenna can be used according to diferent sharing spectrum usage.
This feature is used for operators to reduce CAPEX and OPEX by building and maintaining one network. Comparing to
dedicated carrier network sharing, radio
resources can be used more efficiently. Simultaneous connection with multiple independent core network architecture is
supported. Also simultaneous connection with other shared or non shared eNodeB is supported. Common antenna can be
used for RAN sharing with shared carrier.
This feature is used for operators to reduce CAPEX and OPEX by building and maintaining one network. Multi PLMNs are
supported in both dedicated and shared carrier sharing. For dedicated carrier sharing, multi PLMNs are managed by one
PLMN for each cell. For shared carrier sharing, multi PLMN's are managed by multi PLMN's for each cell. The PLMN
information is broadcasted through system information.
This feature is used for operators to reduce CAPEX and OPEX by building and maintaining one network. When a UE performs
an initial access to a shared network, one of the available core network operators shall be selected to serve the Ue. Ue
indicated the selected Core Network Operator through selected PLMN-id with RRC connection complete message, which
serves the UE currently to which the UE is currently attached. The selection of core network operator by the UE shall be
respected by the network. The eNodeB shall select an appropriate MME for the PLMN indicated by the UE in case of MOCN.
In case of UE registration failure, the eNodeB shall behave as in the case of a non shared network.
This feature is used for operators to reduce CAPEX and OPEX by building and maintainance of one network.
Basic mobility control in RAN sharing scenarios support intra LTE mobility within shared LTE areas with following functions:
Cell reselection/X2 Handover/S1 Handover within shared LTE areas. Cell selection/X2/S1 Handover within shared & non
shared areas.
Traffic separation for two or more CN operators within the shared E-UTRAN can be realized using VLANs. For example, the
VLANs can be partitioned for S1/X2 interface as per operator basis, OAM and other traffic for all operators. It can be flexibly
configured by OMC according to operator’s requirement.
Same Band in Sharing by Diferent operators
Inter PLMN mobility is supported for cases, such as at the border of shared and non-shared area, according to operator’s
policy. Activation of this feature will be configurable in accordance with operator policy.
This feature is used for operators to reduce CAPEX and OPEX by building and maintainance of one network. Transport
resource partition are identified for UL transport network sharing configuration from eUTRAN point of view, while the
partition for DL are to be identified and provided from Core Network point of view.
PS Handover from LTE to UTRAN in an LTE Network-Sharing Scenario

Redirection from LTE to UTRAN/GERAN in an LTE Network-Sharing Scenario
In network sharing mode, the performance/fault statistics provides counters and indicators for diferent PLMNs
(CSFB to UTRAN/GERAN) of RAN Sharing
This feature provides a flexible mobility management policy in a LTE network-sharing scenario consisting of LTE and GERAN. If
the LTE network coverage is not available for a UE, the UE is instructed to select a suitable cell at a GERAN frequency to ensure
service continuity for the UE
This feature provides a flexible mobility management policy in an LTE network-sharing scenario consisting of LTE and GERAN. If
the LTE network does not support the VoIP voice service, this feature falls back the UE to the CS domain in the GERAN
network to provide the voice service to the UE
When LTE network-sharing is implemented in shared carrier mode, this feature provides diferential QoS management policies
for diferent operators. This minimizes or avoids the QoS diferences among the UEs or services of the same level caused by
the diferent QoS mapping rules in each operator's core network
When LTE network-sharing is implemented in shared carrier mode, this feature provides the flexible RRC resource partition for
operators. This ensures basic RRC resources for each operator and increases the RRC resource utilization of the system
The feature enables fast retransmission and decrease the BLER. ZTE eNodeB supports both Chase-Combining & Incremental
Redundancy, DL asynchronous adaptive, UL synchronous adaptive & non adaptive HARQ, max HARQ transmission times.
The feature enables dynamic scheduling function. The dynamic scheduling function supports the following time domain
scheduling
strategies with operator configurable: MAX C/I; Round Robin; Proportional Fairness. The dynamic scheduling function
supports the non-frequency selective scheduling unction, which is called wide band CQI allocation in ZTE’s eNodeB
The feature enables cell throughput improvement and guarantees QoS requirements in low speed environment. ZTE eNodeB
calculates the DL channel SINR based on CQI reports sent by UEs, to acquire the DL channel conditions, the UL channel SINR
based on Sounding RS sent by UEs, to acquire the UL channel conditions.
The feature enables the improvement of cell edge user coverage. In it the same transport block is repeatedly transmitted in
four consecutive sub frames with diferent RV parameter. TTI (Transmission Time Interval) bundling is applicable for uplink
transmission and for specific applications such as VoIP.
The feature enables to decrease signaling overhead and increase system capacity, especially VoIP capacity. The principle of
SPS is to pre allocate resources at fixed sub-frames for initial transmission, while dynamic scheduling is still considered for
retransmission, to decrease the delay of service.
The feature mainly supports UE power saving. DRX function can be configured for an ‘RRC_CONNECTED’ UE. Then the UE does
not
need to monitor the PDCCH continuously. Long DRX period is beneficial for lengthening the Ue Battery life.Long DRX may also
be used for CGI measurement in ANR function.
The feature mainly supports UE power saving. DRX function can be configured for an ‘RRC_CONNECTED’ UE. Then the UE does
not
need to monitor the PDCCH continuously. Long DRX period is beneficial for lengthening the Ue Battery life.Long DRX may also
be used for CGI measurement in ANR function.
The feature supports the QoS scheduling function in LTE, and guarantees the QoS requirements, like GBR, AMBR, and PDB for
specific service. The QoS requirements defined in 3GPP are: Priority; GBR/MBR for GBR services; MBR for non-AMBR for all
the services of one UE; Packet Error Rate (PER), Packet Delay Budget (PDB) for specific service from QCI(1~9).
The feature guarantees no low priority NGBR users will starve in case huge volume
traffic from high priority NGBR users. ZTE’s eNodeB will support pseudo GBR, or mini-GBR value, for NGBR services on both DL
and UL. In this way, a minimum GBR can be guaranteed for all NGBR services,including low priority users.The pseudo GBR for
each NGBR QCI can be operator configurable.
The feature enables to increase system capacity and improve coverage.According to CQI reported by UE and UL SINR
measured by eNodeB, eNodeB can
acquire the current channel quality. Considering the channel conditions, bufer status, and the UE capability, eNodeB can
determine the modulation order and coding rate to be used.
The feature enables to increase system capacity and improve coverage. PDCCH link adaptation function dynamically adjusts
the PDCCH CCE aggregation level
and PDCCH transmission power adaptive to radio environment.In cell edge or low SINR environment, large PDCCH CCE
aggregation level, like 4 or 8,
is deployed, and the transmission power of PDCCH is boost, and vice verse.
#N/A
The feature supports the link adaptation for the enhanced DL inter MIMO-modes adaptation function in LTE to improve the
system performance.
ZTE eNodeB supports the following intra mode DL transmission & transmission modes adaptation: Open-loop intra-mode
The feature supports the adaptive switch between frequency selective and nonfrequency selective scheduling in LTE, to
improve cell throughput and guarantee QoS requirements in low and high speed environment.
The feature supports the static Fractional FR(Frequency reuse ) & soft FR functions in LTE.
The feature supports the dynamic ICIC function via adaptive SFR scheme with load information exchanged among neighboring
cells in LTE, to coordinate the system interference and increase the system capacity.
The feature supports the advanced operator configurable QoS scheduler with scheduling weights configurable and QCI
absolute/relative scheduling priority configurable. With this feature, QCI scheduling priority can be configured as Gold, Silver
& bronze.And diferent QCI scheduling priority configuration supports absolute or relative QCI scheduling priority.
The feature supports the advanced VoIP features.ZTE eNodeB will supports the following advanced VoIP features:
Support SPS state machine management, to switch between SPS during voice period and dynamic scheduling during silent
period; Support SPS adaptation based on VOIP codec rate & for near field users, together with TTI bundling for far field users.
The feature supports for adaptive DRX cycles according to Silence Indicator (SID)for LTE voice.ZTE eNodeB will support for
adaptive DRX cycles according to Silence Indicator (SID)for LTE voice,that is short DRX combined with Long DRX to save more
power consumption.Notice, in fact, Long DRX only is enough for VoIP service.
The feature supports the link adaptation for the enhanced DL inter MIMO-modes adaptation function in LTE to improve the
system performance in case of DL 4*2 MIMO.ZTE eNodeB supports the following intra/inter mode DL transmission schemes
adaptation in case of 4*2 MIMO: Open-loop intra-mode adaptation, Closed-loop intra-mode adaptation.
The feature supports the adaptive UL MIMO mode function. ZTE eNodeB will support the adaptive UL MIMO mode between
UL MU-MIMO and UL-SIMO
The feature supports the link adaptation for the enhanced DL intra MIMO-modes adaptation function in LTE to improve the
system performance in case of DL 4*2 MIMO.ZTE eNodeB supports the following intra/inter mode DL transmission schemes
adaptation in case of 4*2 MIMO: Open-loop intra-mode adaptation, Closed-loop intra-mode adaptation.
The feature supports MBR>GBR defined in 3GPP Release 10. In release 10 in 3GPP, MBR can be higher than GBR for GBR
service.The scheduler supports the throughput can be override GBR and limited by MBR for GBR service.
This feature is a fundamental configuration for LTE FDD.ZTE eNodeB supports the basic physical layer processing functions
defined in 3GPP TS
36.211, 36.212, and 36.213.ZTE eNodeB supports normal cell radius (around several kilometers), basic physical channels
processing functions, like PCFICH,
PHICH, PDCCH, PDSCH, PRACH, PUCCH, and PUSCH, UL DMRS and Sounding RS,all the PDCCH formats and aggregation levels,
all the UCI formats,supports all the following DCI formats,supports DCI 1D to support DL MU,supports DL resource allocation
type 0 and 2 only.supports all the PA and PB configurations defined in 3GPP TS 36.213. forDL power allocation.ZTE eNodeB
supports all the transport block sizes on DL and UL defined in 3GPP TS
Format 0: normal 1 ms RA burst with 800us preamble sequence, for small cells (up to ~14km).
Format 1: 2ms RA burst with 800us preamble sequence, for large cells (up to
~77km) without a link budget problem.
Format 2: 2ms RA burst with 1600us preamble sequence, for ~19km) supporting low data rates;
Format 3: 3ms RA burst with 1600us preamble sequence, for very large cells (up to ~100km).
This feature is used for initial network access and uplink time synchronization in high speed environment.
This feature enables the eNodeB to receive PUSCH and transmit PDSCH.
ZTE eNodeB provides QPSK and 16QAM demodulation in uplink.
ZTE eNodeB provides QPSK, 16QAM and 64QAM modulation in downlink.
This feature enables the eNodeB to get higher UL data rate and UL spectrum efficiency
This feature provides 64QAM demodulation in uplink, UE category 5 supports 64QAM in uplink.
This feature is used to transmit downlink data and control signaling to improve coverage and robustness of radio channels in
case of 2 antenna environment.
environment.
environment.
environment.
This feature is used to transmit downlink data and control signaling to improve coverage and robustness of radio channels in
case of 4 antenna environment.
This feature increases system capacity and spectrum efficiency in a 4*2 MIMO environment, with 4 antennas in eNodeB and 2
antennas in UE.
antennas in UE.
antennas in UE.
environment.
This feature improves coverage and robustness of uplink radio channels in case of 2 reception antenna environment.
This feature increases UL system capacity and spectrum efficiency by MU-MIMO with 2 layers in case of 2 or 4 antennas in
eNodeB.
Uplink Multi-User MIMO (MU-MIMO) means several UEs communicate simultaneously with a common base station using the
same frequency - and time - domain resources in uplink.
The introduction of PUSCH/SRS and PUCCH open - loop power control aims to trace the fluctuation of path - loss and aid AMC
for link adaptation and mitigate the inter – cell interference. The open loop part of the scheme is often
called Fractional Power Control (FPC) because it allows User
Equipments (UE) to partially compensate the path-loss
for link adaptation.
for link adaptation.
The introduction of PUCCH power control aims to trace the fluctuation of path loss and guarantee the successful
demodulation rate of PUCCH.
PUSCH frequency hopping is suitable for small payloads and/or fast moving UEs to provide frequency diversity.
If eight receive antennas are deployed on an eNodeB and the cell interference is minor, this feature is used to improve uplink
coverage quality through MRC reception schemes
If eight receive antennas are deployed on an eNodeB and the cell interference is high (such as a commercial network with a
great number of UEs), this feature is used to improve uplink coverage through IRC reception schemes.
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 UEs), this feature is used to improve PUCCH reception performance by reducing PUCCH reception
interference
This feature enables the operator to configure the OFDM Channel Noise Generator (OCNG) function in the eNodeB so that the
system can emulate many virtual users in the downlink network load test.
The PUCCH blanking functionality supports non - 3GPP UL system bandwidth with PUCCH over-dimensioning.
The feature supports semi- static power sharing between GSM and LTE, in case GL co- PA, in order to improve performance of
LTE cells, When GSM intelligently shutdown one or more GSM frequency in case of low load for power saving, the release
power can be shared by LTE.
#N/A
The feature supports 2 single-port cells split by one 2-ports RRU, which is useful in case of indoor DAS coverage, in order to
decrease required number of RRUs.
In a scenario where GSM and LTE provide the same coverage on the same frequency band, this feature supports compressing
the guaranteed bandwidth of LTE to reduce interference and maximize the spectral utilization
LR15 Supported
ZTE eNodeB supports FE/GE (RJ45), GE (Optical/Electrical), 10/100/1000Base – T interfaces with auto negotiation, 1000Base-
LX/1000Base-BX/ 1000Base-SX (MM) fiber/100Base-FX interfaces, standard SFP on all Ethernet transport interfaces.
eNodeB provides 2 FE/GE interfaces for transmission, these 2 interfaces can be configured backup each other to improve the
availability.
BBU can interconnect via Ethernet interface like a daisy chain, Ethernet switch is built in BBU, the traffic aggregates towards to
the core network via the first BBU.
eNodeB CCE board provides 2 GE interfaces and 2 10GE optical interfaces

independently for transmission, these 2 GE interfaces can be configured backup each and share the load, extend bandwidth,
so do the 2 10GE interface.
VLAN is often adopted in Ethernet network to implement traffic separation, thus avoiding traffic broadcast storm normally
happened in Ethernet network due to its broadcast.
The flows of control plane, user plane, and OMC channel can flexibly be
one or more diferent VLANs. If IPSec function is enabled, IPSec tunnel can be
configured to arbitrary VLAN.
The IEEE802.3ad LAG protocol is used for bandwidth dynamically binding and backup for 2 Ethernet interfaces each other.
DHCP (Dynamic Host Configuration Protocol) is very useful for the management and distribution of IP network configuration,
particularly as networks grow beyond hundreds of clients.
LTE eNodeB supports IP and corresponding upper layer protocols to implement user plane and control plane (also OMC plane,
same as control plane) functions. ZTE eNodeB
eNodeB supports IPv6 compliance with IETF RFC2460 + RFC5095, provides upper
layer application over it.
eNodeB supports IPv4 & IPv6 Dual Stack on all the Ethernet interfaces simultaneously;
the IP version (IPv4 or IPv6) can be selected
ZTE eNodeB can be configured with a unique IP address, all the logical interfaces such as S1, X2, and OMC will use this IP
address. One eNodeB needs only one IP address thus reducing the required IP address number.
ZTE eNodeB supports IPv4 Jumbo frame on all the Ethernet interfaces to avoid packet fragment and recombination when
using IPSec function on S1 or X2 interface. The maximum size of Jumbo frame is up to 1800bytes.
DifServ model is often adopted as QoS and traffic scheme in LTE transport network, and this scheme divides the IP traffic in
backhaul network into several priority levels(for example 3 levels as Gold, Silver and Bronze, or 8 level as 802.1p) and handles
traffic at each level with diferent forwarding processes.
The total bandwidth can be assigned via OMC for S1, X2 and OMC, or independently
assign CP, UP and OMC traffic bandwidth and priority.
eNodeB provides the throughput statistics of incoming and outgoing, and the packet number of diferent types, the
bandwidth according to the IP addresses and VLANs.
ZTE eNodeB can be configured as Ethernet aggregator which used to aggregate the traffic of 2G/3G.The next phase, LTE
eNodeB can manage the traffic of 2G/3G and LTE traffic itself, reserve traffic bandwidth of 2G/3G and guarantee the QoS of
this traffic.
The operator needs to protect the communications via S1 and X2 interfaces, which is normally ensured by using IPSec
channels between eNodeB and IPSec gateway.
Internet Key Exchange (IKE or IKEv2) is the protocol used to set up a security
association (SA) in the IPsec protocol suite. IKE builds upon the Oakley protocol and ISAKMP.
Implement Cryptographic Algorithms for Use in the Internet Key Exchange Version 2 (IKEv2), EAP Method for 3rd Generation
Authentication and Key Agreement (EAP – AKA) and Multiple Authentication Exchanges in the IKEv2 Protocol.
Protect the S1 CP traffic using IPsec. The IPsec tunnel is set up between eNodeB and security gateway, when IPsec deployed,
control plane signaling should be protected by IPsec.
Protect the MP traffic using IPsec. The IPsec tunnel is set up between eNodeB and security gateway, when IPsec deployed,
OMC data should be protected by IPsec.
Protect the S1 UP traffic using IPsec. The IPsec tunnel is set up between eNodeB and security gateway, when IPsec deployed,
user plane data protection is optional, in most scenarios, it isn’t needed for protecting UP data.
Protect the X2 traffic using IPsec, it includes control signaling and user data. The Ipsec tunnel can be set up between eNodeBs
directly and indirectly.
PKI certificate is useful when there are large numbers of eNodeBs to declare itself and implement authentication with core
network.
ZTE eNodeB supports Access Control List function on transport side, it can be
configured L2 filter based source and destination COS value. ZTE eNodeB can also be configured L3 filter based source and
destination IP address, source and destination port number.
Realize eNodeB and OMC communication using SSH protocol.
LR15 Supported
LR15 Supported
eNodeB supports security transmission with OMC, it use vendor define message encrypt meth via TCP/UDP socket to transmit
messages, and use SFTPv3 to transmit files.
OMC supports SNMP protocols & OMC can support inter connection with NMS through northbound SNMP interface.
this interface.
OMC northbound SNMP interface ofers NMS with fault management function.
For LTE FDD network, frequency synchronization is required between eNodeBs frequency synchronization is normally achieved
through
TDM transport network or by GPS system.
Ethernet uses the physical layer interface to pass frequency information
from node to node. Synchronous Ethernet can implement the frequency synchronization.
also called as Precision Time Protocol, which synchronizes clock to a distributed system consisting of
one or more nodes by network communication.
ZTE eNodeB supports a synchronization priority scheme whereby the network operator shall be able to freely assign a priority
to each possible synchronization source
eNode B can get frequency and phase clock reference from Glonass system with a integrated receiver, this receiver can share
the antenna signal input with GPS
all the nodes between the clock server and slaves should support IEEE 1588 BC mode, and comply with the regulation of ITU-
T G.8271..
#N/A
The NTP/SNTP network time synchronization protocols so that it can synchronize time with server of a third-party system and
provide synchronization time sources for NEs.
#N/A
#N/A
#N/A
BFD (Bidirectional Forwarding Detection) is a detection protocol designed to provide fast forwarding path failure detection for
all media types, encapsulations, topologies, and
routing protocols.
Measure the transport network IP performance condition using service level agreement protocol, such as delay, jitter and
packet loss rate.
It can be assigned to diferent radio modes. The bandwidth is fixed for GSM, UMTS, and LTE.
Radio mode is configured with a specific priority based on the same principle, it can get transport resource in a preemptive
way, and the traffic with
highest priority will be sent first.
The eNodeB will boot and perform a self-detection. The feature depends on the prerequisites that the transport parameters
for the eNodeB should be planned in advance, including VLAN partition, IP addresses, etc.
The feature is used in the scenario where the DHCP relay is disallowable. DHCP relay agent eNodeB, all the eNodeBs in the
same sub-network self-configure eNodeB IP and OMC IP, AGW IP, SGW IP.
The feature includes two aspects, Automatic acquisition of security data & Automatic establishment of security tunnel
Transport self-setup involves the following scenarios: Initial Network deployment or a new eNodeB insertion into network, X2
transport self- setup, S1 self-setup
eNodeB uses the self-test function to judge whether the eNodeB can provide service or not.
The feature enables to assign initial PCI for cell without conflict & confusion reducing manual efort on PCI assignment.
This enables to minimize the probability of PCI conflict and confusion, thus reducing manual efort on PCI assignment.
The feature involves following aspects: neighbor cell detection and addition, automatic neighbor cell removal, switch on/of
ANR automatically;,white/black list management, ANR management in OMC
The feature enables to reduce the network failures due to missing or wrong inter-frequency neighbor definition and better
balance the traffic level in Inter
the
. etter Inter-frequency clls
For Inter-RAT scenarios, each cell contains an Inter RAT Frequency Search list. This list contains all frequencies that shall be
searched. ZTE support LTE-GSM ANR.
Each cell contains an Inter RAT Frequency Search list. This list contains all frequencies that shall be searched. ZTE support LTE-
UMTS ANR. The feature enables to reduce the network failures due to missing or wrong inter-RAT LTE-UMTS neighbor
definition.
During the initial phase of the deployment of inter-frequency eUTRAN cells, there are a quantity of inter-frequency neighbor
cells to detection and addition, so that the process can be fastened.
During the initial phase of the deployment of inter-frequency eUTRAN cells, there are a quantity of inter-frequency neighbor
cells to detection and addition, so that the process can be fastened.
ANR aims at the neighbor cell optimization as the predefined policies. And the unsuitable policies will slow down the
optimization procedure. Besides, the feature caches the CGI information for the PCI to reduce the measurements to the
unkown PCI of the new neighbor cells.
The feature supports automatic configuration update to OMC based on the configuration exchange through X2 interface, so
that the inconsistence can be avoid.
The feature enables to avoid coverage hole in LTE network and to decrease the level of DL inter-cell interfrence
The configuration of the threshold for the target MRO parameter; the configuration of the target KPIs for MRO). The activation
/ deactivation of MRO are triggered by the pre- configuration.
Minimize the handover failures rate/Reduce the unnecessary handovers/Increase the network capacity/Decrease UE power
consumption
Decrease congestion probability/Achieve the optimum E-UTRAN performance/Increase network capacity/Increase the
network load balancing capability
intra-frequency camp load balancing(serving cell and neighbor cell frequency priority is the same) and traffic load balancing.
Decrease collision probability and improve radio resource efficiency
Decrease collision probability and improve radio resource efficiency,Reduce access delay of PRACH,Avoid PRACH interference
between cells and Minimize the manual intervention
Minimized the system collects UE measurements autonomously and Minimize the need of manual drive tests.
Minimized the system collects UE measurements autonomously and Minimize the need of manual drive tests.

Rel10 LTE Advanced Load Balancing : eNodeB exchanges load information through the RIM procedure over the S1 interface,
and then calculate the load amount of the serving cell and its inter-RAT neighbor cell
eNodeB will deliver the inventory information to OMC after eNodeB startup
The feature enables to minimize operational efort during RRU provision It also autonomously makes RRU working normally.
#N/A
The feature enables to minimize operational efort during RRU provision It also autonomously makes RRU working normally.
#N/A
The feature enables to solve software and hardware fault automatically
This feature supports intelligent OFDM symbol shutdown function in normal sub-frames, in order to achieve power saving
during no traffic or low traffic scenario
The feature enables to save energy consumption and decrease Operator’s OPEX.
The feature enables to save energy consumption and decrease Operator’s OPEX some special area where eNB canbe
shutdown for some specific period based operator’s configuration
LTE-Adv power saving feature
This feature shuts down RF channels for energy saving. the eNodeB can intelligently shut down RF channels based on the cell
load within a specified period, for example, changing two transmit channels to one transmit channel, for MIMO degradation
and RRU power consumption reduction.
This feature improves the transmission quality of the cell-edge in DL
In this feature the cells of the same eNodeB are coordinated with joint reception and processing of the signal from the same
UE to improve the coverage in UL
Rel 10 LTE-Adv
Rel 10 LTE-Adv
Rel 10 LTE-Adv
Rel 10 LTE-Adv
Rel 10 LTE-Adv
Rel 10 LTE-Adv
Rel 10 LTE-Adv
Rel 10 LTE-Adv
Inbound cell reselection/intra-RAT PS handover to Hybrid or CSG cell and Outbound cell reselection/intra-RAT PS handover
from Hybrid or CSG cell
This feature is used to solve the interference problem HetNet, in which low power nodes (e.g. Pico or Femto) are placed
throughout a macro Cell layout (overlaid).
This feature is used to solve the interference problem for HetNet, in which low power nodes (e.g. Pico or Femto) are placed
throughout a macro cell layout (overlaid).
The feature includes automatic neighbor cell addition and deletion in the Hetnet
The feature includes X2 detection and deletion
The AAS supports individual tilt setting in Tx (DL) and Rx (UL)
AAS
AAS
AAS
AAS
AAS
AAS
AAS
3GPP Compliance as per Rel11
LTE Advaced Rel 11 UE Cat 9
This feature detects the location of a UE in the LTE network in OTDOA positioning mode to provide the location information
about the UE for value-added services such as the emergency call service and automotive navigation.
Services Related to ETWS
Services reated to CMAS. for informing mobile terminal users of current alarm event such as child abduction, by sending
commercial warning notifications
LTE Advanced & related to IoT. This feature, applicable to the Internet of things, controls access of MTC terminals to guarantee
system stability
LTE-Adv & IoT Related. This feature is applicable to overload control on MTC terminals in a scenario where the system or cell
experiences high load in the Internet of things. This prevents the networks (RAN and CN) from being overloaded and ensures
the system (or cell) stability.
This feature detects the location of a UE in the LTE network in Qcell deployment to provide the location information about the
UE for value-added services such as intelligent shopping center
LTE-Adv. This feature ensures that a UE can operate properly when moving between diferent network frequency bands by
sending Multiple Frequency Band Indicator (MFBI) to the UE. This solves the compatibility problem of a UE accessing and
moving between diferent network frequency bands in the scenario where the frequency bands are overlapped with each
other or contained by other frequency bands.
This feature optimizes the CSFB performance in a scenario consisting of LTE, UTRAN, and GERAN. For the measurement-based
CSFB mode, this feature avoids the LAU procedure to shorten the time delay of CSFB and guarantee the CSFB success rate
This feature is used in multi LTE frequency deployment and VoLTE deployment scenario, the network provide flexible service
management strategy. According to voice/data service type, the network can provide diferent services in diferent LTE
frequencies.
This feature is used in LTE network, the network provide flexible handover enhancement strategy. According to diferent
service characteristics, the network can configure QCI level measurement parameters to provide diferent handover strategy
This feature is used in LTE network, especially multi LTE frequency deployment scenario, according to LTE user subscription
information, the network perform diferentiated mobility management with local strategy mapping to indicator user to
diferent frequencies.
This feature is used in LTE high-speed network (such as high-speed train) and normal, LTE network co-existence scenario.
According to UE speed detection, the network guarantee high-speed UEs stay in high-speed network, avoid ordinary UEs stay
in high-speed network, thus improve high-speed UE experience
supports the RIM procedure. This feature is used in LTE network and UTRAN network co-existence scenario. According to both
signaling quality and load status of UTRAN neighboring cell, the network select handover target cell to avoid UE handover to
higher load UTRAN neighboring cell and raising internal load balancing among UTRAN multi frequency
This feature is used in LTE multi PLMN network, or LTE network and UTRAN/GERAN multi PLMN network co-existence
scenario. The network provides flexible frequency or network selection strategies
LR15 VOLTE Support
LR15 VOLTE Support
LR15 VOLTE Support
This feature enables a maximum of four operators to share an LTE network in shared carrier mode.
This feature is used in LTE RAN sharing scenario, especially multi LTE frequency deployment scenario, according to LTE user
subscription information, the network perform diferentiated mobility management with local strategy mapping to indicator
user belong to diferent operator to diferent frequencies
This feature is used in LTE dedicated carrier sharing scenario, the network supports detecting and adding missing neighboring
cells through terminal measurements, to improve system handover performance
Improve voice quality of VoLTE
Improve voice capacity of VoLTE
LR 15 Supported
LR 15 Supported
LR 15 Supported
This feature is used to improve VoLTE coverage and reduce the eNodeB load, increasing the system capacity and improving
user experience, by adjusting the codec rate.
This feature supports SDMA for super cell, in order to improve system capacity obviously.
#N/A
This feature ensures that the most important data will be sent in the fastest speed, packets from higher priority queues have a
very low delay, the performance indicators such as the loss rates and pass rates can get a certain degree of protection when
the network congestion
Improve the reliability of IPSec path. When the LTE system deployment have independent security gateway, eNodeB can be
set diferent IPSec tunnel with two security gateway.
This feature measures the performance of bearer networks based on the IETF TWAMP, providing a basis for monitoring and
fault location
LR15 LTE-Adv Rel10. The feature supports to detect the availability and priority about the CoMP neighbor. So the efort for the
CoMP neighbor analysis and configuration can be reduced and even saved
This feature enables PUCCH resource self-adaption based on the monitoring of UE number, physical resource block (PRB)
usage, and based on the result changes the parameters about physical resources , and can bring the following benefits: 
Balance the user experience and resource usage of the network in diferent heavy traffic scenario
 Reduce the complexity and eforts of manual operation.
The feature keeps maximum user experience when available antennas decrease. So the network performance will be kept
steady and less afect in real time.
The eNodeB power consumption is displayed on the OMC in a visual way. This feature supports visual display of BBU and RRU
power consumptions on the OMC/SON, so that energy saving efects can be easily determined.
This feature enables OFDM symbol shutdown in case of MBSFN subframes during the low-traffic period for further energy
saving
LR15 LTE-Adv Rel10
LR15 LTE-Adv Rel10
LR15 LTE-Adv Rel10
WIP


Remarks
1.only for 20MHz;

2.MME need add some equ;
3.UE need support;
Support，no this scence

bandwith is not enough
bandwith is not enough
no this scence
no site plan to coverage so far
no site plan to coverage so far
now no have this service现在应

该没有需要这样的业务
now no have this service现在应

该没有需要这样的业务
eNB透传，没有参数
1.only for 20MHz;

2.MME need add some equ：
BMSC&MCE
3.UE need support;
1.CN do not have IMS;

2.LTE do not support voice now.
need CSON,Updage dependency

with C-SON
If nessary can open,but it cost
some recourse.可以开通，会有
信令流，消耗资源
跨站重建立
Suggest open从指导书看建议
看起，有好处，减小信令开销
Idea no suggest this stragety
Support;No this scene

only one LTE frequency now
Support;Need CN support，now
RJS fail,because CN reason核心
网还在调整中
Support;Need CN support，now
RJS fail,because CN reason核心
网还在调整中
idea no suggest
too less Ues support，idea no
suggest
support,No this scene
Idea do not need this stragety

now,if need we can open
Netweok is not shared and only

one PLMN now
No TDD network now
For VOLTE
1.now do not separate high and

low service;
2.it is bad for KPI,E-RAB drop
rate maybe increase;
due to terminal
not high load cell now
parameter name：voIPSwitch
NO GBR server now
IP+UDP+RTP
IP+UDP
most ue do not support,we can

open

open
only can add 4 method
Network is not shared and only

one PLMN

one PLMN

one PLMN
one PLMN

one PLMN
Network is not shar
Network is not shar
Network is not shar
Network is not shar
Network is not shar
Network is not shar

Network is not shar
Network is not shar
Network is not shar
Network is not shar
Network is not shared

it is usually used for VOLTE
it is usually used for VOLTE

Delete, because new frequency
domain algorithm for VoLTE is
PRB randomized allocation.
only select one,we need to

compare and then decide
only select one,we need to
compare and then decide
Volte
Volte
no 4 antenna
parameter：
mumimoEnableUl，start to
open
no 4 antenna
no GBR server now
all normal CP now
only select one

only select one
only select one
no have this scene
ZTE suggest open loop；closed

loop is sensitived to speed,闭环
空间复用对速率敏感
zte suggest open loop；and

mutex
no 4 antenna
no 4 antenna
no 4 antenna
no 4 antenna
no 4 antenna,
now use IRC
no 4 receive，only 2.天线配置
是2T2R.
no 4 receive，only 2.天线配置
是2T2R.
we can open ,need to try.
UL MIMO is closed
now only 2 antenna
now only 2 antenna
MRC
1.PUCCH blanking cost some ul

resource and it is bad for ul
throughput;
2.it is good for reduce
interference,and now ul has less
interference.
LTE USE 2*20W.
no plan
no plan，now only use 5MHz
no plan，now only use 5MHz

ZTE support and idea did not
plan V6 IP
参数未空，未配置
Delay to LR17
Delay to LR17
not add GPS
no add clock source
no have this scene

no have this scene
1.only one synchronizatio
method
2.no have this scene
do not select this GPS
not select Chinese beidou,no

GPS
no have this scene

no have this scene
no have this scene
no have this scene
no have this scene
too diferent scene,不知道怎么

回答
too diferent scene,不知道怎么
回答
没查到
没查到
没查到
can not add idea&zte suggestion
rules
can not add idea&zte suggestion
rules
measure interF and interRAT will

cost some recourse

cost some recourse
cost some recourse

cost some recourse
cost some recourse
we add the rules
now no need and this maybe

interface UE mobility可能影响
UE的移动性能（切换参数和重
选参数变化了）

existing cover scene do not need

to opptimization rach,it is OK.
existing cover scene do not need

to opptimization rach,it is OK.
RJS do not add NDS now,after

add NDS we can open this/
RJS do not add NDS now,after

add NDS we can open this/

not belong to SON
only one frequency,do not

suggest close
for coverage and user
perception
do not suggest ,for user

perception
RJS will do this
RJS will do this

Support，need to add board

Support，need to add board
No HetNet scene
No HetNet scene
No HetNet scene
No HetNet scene
No HetNet scene
No HetNet scene
No HetNet scene
智能天线Advanced
AntennaSystems
AntennaSystems
AntennaSystems
AntennaSystems
AntennaSystems
AntennaSystems
AntennaSystems
AntennaSystems
必须遵守R11，这都是个
Feature啊，奇才
no parameter,default
If nessary can open,but it cost

some recourse.可以开通，会有
信令流，消耗资源
If nessary can
open（Earthquake and Tsunami
Warning System）地震海啸系
统
no have Machine Type

Communication 没有机器类型
通讯场景，如智能停车，智能
水表
no have Machine Type
Communication 没有机器类型
通讯场景，如智能停车，智能
水表
no Qcell
one PLMN
only one frequency now
do not suggest,because there is

not diferent qci server now.
Idea no not need this stragety

now,if need we can open
no High-Rail Coverage and high-

speed coverage
Need CN support
only one plmn
no volte
no volte
no volte
Volte
Volte
貌似是默认开启的吧？？
NO VOLET，this feature is used
for volte
no plan super cell now
no aas不是智能天线


open
only 2T2R
JR:Join reception 个人认为是基

于下面2个Feature的，但是下
面的2个Feature未开启，因为
没有这个场景，都是宏站
no have this scene
ONLY macro sites
no have this scene
not understand
not understand
No HetNet scene
Vendor 3G SW 3GPP 3G SW REL
release in which for which this
Sr. No Feature No. Feature Name this feature is functionality is
available addressed
1 ZWF21-03-100 Cell reselection with LTE UR12 R8
2 ZWF21-03-026 Target cell Load based inter-RAT HO UR11 R8
3 ZWF21-03-101 CS Fallback from LTE Support UR11 R8
4 ZWF21-03-110 Handover with LTE UR13 R8
5 ZWF21-03-111 Fast Return to LTE UR13 R8
6 ZWF21-03-120 SR-VCC UR12 R8
7 ZWF27-02-002 User Dedicated Frequency Priority UR12 R8

8 ZWF21-01-021 RRC Connection Redirect UR13 R8
9 ZWF21-30-031 Direct Tunnel UR13 R8
RAB Combination for Multiple Packet
10 ZWF21-02-007 UR13 R8
Data Services
FEATURES AVAILABLE IN SEPT-2017 RELEASE

1 ZWF21-03-030 Load Based PS HO to LTE UR15 R8
Packet Service Fast Return to LTE for

2 ZWF21-03-112 UR15 R8
Inactive Mode
Packet Service Fast Return to LTE for

3 ZWF21-03-113 UR15 R8
Active Mode
Remarks
(a) Vendor confirms that the mentioned list is complete feature list of the Software quoted for June-2015 SW relea
(b) Any omission in feature list supplied by vendor will result in automatic classification of that feature and related
(c ) At all time IDEA way of Licensing needs to be followed , Vendor will need to keep mapping between IDEA licens
(e) There are no pre-requsities for the IDEA basic features , all the features which are in IDEA optional various cater
(f) All pre-requsite features which has been termed as basic or optional , when it is purchased , the corresponding
Capacity
Corresponding 4G SW 3GPP 4G SW REL Vendor Feature Impact on
IDEA Applicability in
release where this for which this IDEA
feature is required to functionality is Basic/Option functionality
al Grouping 3G ( Per Cell / Per Traffic
interact addressed eNB ) Profile in
3G
LR13 R8 Basic 3G Interworking Per Cell Not
LR14 R8 Optional 3G Interworking Per Cell Not

quoted for June-2015 SW release & Dec-2015 SW release and no ommissions have been done
on of that feature and related dependent feature/license to be classified as IDEA Basic and vendor will have to provide at no additional
mapping between IDEA licensing to their way of Licensing.
e in IDEA optional various catergories - they include all the pre-requisite features
purchased , the corresponding dependt defeatures comes with the new features
IDEA Vendor - Pre- Any supplied
License IDEA
requisite HW of vendor
Pre-requisite features if Any mehodolo Basic/Option
functionality which donot
gy - al - LR15 for
required from support this
Anything FDD & TDD
Core/Any nodes feature
required ?
None None None Not Basic
None None ZUF-52-03 Handover Not Basic
If PS handover method is MME：ZUF-52-01-

adopted, the using of this 027 CS Fallback
None Not Basic
feature depends on "ZWF21- ZUF-52-06-007 SGs
03-110 Handover with LTE" Interface
None None ZUF-52-03 Handover Not Basic
If PS handover method is
adopted, the using of this
feature depends on "ZWF21-
03-110 Handover with LTE". None Not Basic
If based on SPID is appied, it
depends on ZWF27-02-002
User Dedicated Frequency
Priority.
If PS handover method is MME：ZUF-52-05-

adopted, the using of this 008 SRVCC
None Not Basic
feature depends on "ZWF21- PGW：ZUF-63-01-012
03-110 Handover with LTE" SRVCC Support
None None ZUF-52-03 Handover NOT Basic
ZWF21-03-101 LTE CS Fallback, None NONE NOT Basic

ZWF21-03-120 SR-VCC
ZWF21-03-101 LTE CS Fallback, None NONE NOT Basic

ZWF21-03-120 SR-VCC
ve to provide at no additional costs to IDEA

IDEA
Optional
Features
Grouping -
LR15 for
FDD & TDD
Basic
Basic
Basic
Basic
Basic
Basic
Basic
Basic
Basic
Vendor 2G SW 3GPP 2G SW Corresponding
4G SW release
release in REL for where this
Sr. No Feature No. Feature Name which this which this feature is
feature is functionality required to
available is addressed interact
1 ZGO-02-03-008 GSM/LTE Cell Reselection UR11 R8 LR13
2 ZGO-02-03-013 Inter-RAT NACC UR11 R8 LR13
3 ZGO-02-03-014 Fast Return from GSM to E-UTRAN UR11 R8 LR13
4 ZGO-02-03-016 GSM/LTE SRVCC UR13 R8 LR14
5 ZGO-02-03-019 CSFB from LTE to GSM UR13 R8 LR14
6 ZGO-02-03-015 Subscriber Profile ID(SPID) UR13 R8 LR14

7 ZGO-02-03-017 GSM/LTE NCCR UR13 R8 LR14
8 ZGO-02-03-021 GSM/LTE Load Sharing UR13 R9 LR14
Remarks
(a) Vendor confirms that the mentioned list is complete feature list of the Software quoted for June-2015 SW release
(b) Any omission in feature list supplied by vendor will result in automatic classification of that feature and related dep
(c ) At all time IDEA way of Licensing needs to be followed , Vendor will need to keep mapping between IDEA licensing
(e) There are no pre-requsities for the IDEA basic features , all the features which are in IDEA optional various catergor
(f) All pre-requsite features which has been termed as basic or optional , when it is purchased , the corresponding dep
IDEA
3GPP 4G License
SW REL for Vendor Capacity
Feature
which this Basic/Opti IDEA functionality Applicability Impact on Pre-requisite mehodol
in 2G ( ogy -
functionalit Grouping IDEA Traffic features if Any Anything
onal Per Cell / Per eNB )
y is Profile in 2G required
addressed ?
R8 Optional 2G Interworking Per TRX Not None None

ZGO-02-03-008
R8 Optional 2G Interworking Per TRX Not GSM/LTE Cell None
Reselection
ZGO-02-03-008
R8 Optional 2G Interworking Per TRX Not GSM/LTE Cell None
Reselection

quoted for June-2015 SW release & Dec-2015 SW release and no ommissions have been done
on of that feature and related dependent feature/license to be classified as IDEA Basic and vendor will have to provide at no additional
mapping between IDEA licensing to their way of Licensing.
in IDEA optional various catergories - they include all the pre-requisite features
purchased , the corresponding dependt defeatures comes with the new features
Vendor - Pre- Any supplied IDEA
Basic/Optio IDEA Optional
requisite HW of vendor Features
functionality which donot nal - LR15
for FDD & Grouping - LR15
required from support this for FDD & TDD
Core/Any nodes feature TDD
None Not Basic Basic
MME：ZUF-52-05-008
SRVCC Not Basic
PGW：ZUF-63-01-012
SRVCC Support
MME：ZUF-52-01-027 CS
Fallback Not Basic Basic
ZUF-52-06-007 SGs
Interface
Subscriber Profile ID Not Basic Basic
ZUF-52-03 Handover Not Basic Basic
ve to provide at no additional costs to IDEA

Features - Future Testings
2t4r (MIMO)
GL Power Sharing (LTE down & give power t gsm)
LTE->GERAN CCO without NACC
LTE->GERAN CCO with NACC
Enhanced Adaptive Intra-Mode MIMO Schemes (MIMO TM3 vs TM4)
Super Cell
LTE->UTRAN PS Handover
UTRAN->LTE PS Handover
RIM
PCID (SON)
Static ICIC
Dynamic ICIC
Supporting non-standard bandwidth by lossy compression

Vendor SW release for 3GPP E-UTRAN features

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Vendor SW release for 3GPP E-UTRAN features

Uploaded by

Copyright:

Available Formats

Vendor 3GPP

6 ZLF31-00-006 Support UE Category 1~3 V2.1 R8 Basic System ComplianceeNodeB #N/A

7 ZLF31-00-007 Support UE Category 4 LR12.2 R8/R9 Optional System ComplianceCell on

8 ZLF31-00-009 Radio Channels(EMBMS Channels) LR15 R10 Optional System Compliancecell of

9 ZLF31-00-010 Support UE category 6 LR14 R10 Optional System ComplianceCell on

12 ZLF31-01-003 3MHz LR13.1 R8/R9 Optional LTE Bandwidth cell of

13 ZLF31-01-004 1.4MHz LR14 R8/R9 Optional LTE Bandwidth cell of

16 ZLF31-03-001 120KM/H V2.1 R8/R9 Basic High Speed eNodeB on

17 ZLF31-03-002 350KM/H LR12.2 R8/R9 Optional High Speed eNodeB OFF

18 ZLF31-04-001 15km V2.1 R8/R9 Basic Coverage eNodeB on

23 ZLF31-05-005 eMBMS LR15 R10 Optional EMBMS eNodeB OFF

26 ZLF31-05-013 Location Service(ECID) LR15 R9 Optional Location Service Cell of

31 ZLF31-06-005 UE Context Management V2.1 R8/R9 Basic Connection Manag eNodeB on

32 ZLF31-06-006 UE Capability Enquiry V2.1 R8/R9 Basic Connection Manag eNodeB on

34 ZLF31-06-008 S1 Interface Management V2.1 R8/R9 Basic Connection Manag eNodeB on

35 ZLF31-06-009 X2 Interface Management V2.1 R8/R9 Basic Connection Manag eNodeB on

36 ZLF31-06-010 S1-Flex V2.2 R8/R9 Basic Connection Manag eNodeB on

37 ZLF31-06-011 Context Fetch LR13.2 R8/R9 Optional Connection Manag eNodeB on

40 ZLF31-07-002 Intra-LTE Redirection V2.1 R8/R9 Basic Mobility Managementcell of

41 ZLF31-07-003 Intra-LTE Intra Frequency HO V2.1 R8/R9 Basic Mobility Managementcell on

42 ZLF31-07-004 LTE->GERAN Cell Reselection V2.1 R8/R9 Basic Mobility Managementcell on

44 ZLF31-07-006 LTE->UTRAN Cell Reselection V2.1 R8/R9 Basic Mobility Managementcell on

46 ZLF31-07-008 LTE-1xRTT Cell Reselection V2.1 R8/R9 OptionalMobility Managementcell of

47 ZLF31-07-010 LTE->eHRPD Cell Reselection V2.1 R8/R9 OptionalMobility Managementcell of

48 ZLF31-07-011 LTE->eHRPD Redirection V2.1 R8/R9 OptionalMobility Managementcell of

49 ZLF31-07-012 Intra-LTE Inter Frequency HO V2.1 R8/R9 Basic Mobility Managementcell of

50 ZLF31-07-013 LTE->GERAN CCO without NACC V2.1 R8/R9 OptionalMobility ManagementCell of

52 ZLF31-07-015 LTE->UTRAN PS Handover V2.1 R8/R9 Basic Mobility ManagementCell of

53 ZLF31-07-016 UTRAN->LTE PS Handover V2.2 R8/R9 Basic Mobility ManagementCell of

54 ZLF31-07-017 LTE->GERAN PS Handover LR15 R8/R9 OptionalMobility Managementcell of

57 ZLF31-07-020 LTE->UTRAN SRVCC LR12.2 R8/R9 OptionalMobility Managementcell of

58 ZLF31-07-021 LTE->GERAN SRVCC LR14 R8/R9 OptionalMobility Managementcell of

64 ZLF31-07-028 Mobility with TDD network LR12.2 R8/R9 OptionalMobility Managementcell of

66 ZLF31-08-001 Radio Admission Control V2.1 R8/R9 Basic

67 ZLF31-08-004 Congestion Control V2.1 R8/R9 Basic

69 ZLF31-08-006 IRAT L->U Load Balancing LR13.1 R8/R9 Optional

70 ZLF31-08-007 ECN LR15 R9 Optional

71 ZLF31-08-008 LTE Load Control V2.2 N/A Basic

72 ZLF31-08-010 IRAT U->L Load Balancing LR15 R10 Optional

73 ZLF31-08-011 VOIP Admission Control Enhancement LR15 R10 Optional

75 ZLF31-09-002 Extended QCI LR13.1 R8/R9 Optional QoS Management Cell on

86 ZLF31-11-001 Reserved Mode V2.1 R8/R9 Basic Integrity check cell of

87 ZLF31-11-002 128-EIA1 V2.1 R8/R9 Basic Integrity check cell on

88 ZLF31-11-003 128-EIA2 V2.1 R8/R9 Basic Integrity check cell on

89 ZLF31-11-004 EEA0 V2.1 R8/R9 Basic Encryption/Decryptioncell on

90 ZLF31-11-005 EEA1 V2.1 R8/R9 Basic Encryption/Decryptioncell on

91 ZLF31-11-006 EEA2 V2.1 R8/R9 Basic Encryption/Decryptioncell on

92 ZLF31-11-007 128-EIA3 LR13.1 R10 Basic Encryption/Decryptioncell on

93 ZLF31-11-008 EEA3 LR13.1 R10 Basic Encryption/Decryptioncell on

Operator Specific Transport Resource

Voice Management (CSFB to UTRAN) of RAN

Voice Management (CSFB to GERAN) of RAN

Operator specific User/Service priority

Operator Specific RRC Resource Management of

113 ZLF31-13-005 TTI Bundling V2.1 R8/R9 Optional VoLTE eNodeB of

114 ZLF31-13-006 Semi-Persistent Scheduling V2.1 R8/R9 Optional VoLTE eNodeB of

Enhanced Adaptive Intra-Mode MIMO Schemes

Adaptive Frequency Selective/Non Frequency

Adaptive Inter-Mode MIMO Schemes for 4*2

Full Adaptive Intra-Mode MIMO Schemes for

134 ZLF31-14-002 Extended CP LR15 R8/R9 Optional EMBMS eNodeB OFF

140 ZLF31-14-009 UL 64QAM V2.1 R10 Optional LTE-A eNodeB ON

UL Open-Loop Power Control With FPC