ZTE SDR Software Release Notes (V4 16 10 20P83) - V1 0

ZTE SDR Software Release
Notes
Version:[4.16.10.20P83]
ZTE SDR Software Release Notes

Version Date Author Reviewer Notes
TIAN Xuefei
V1.0 2018/3/15 XU Wei Project team 1st edition
LIANG Jing
© 2018 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used
without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document is subjected to
change without notice.
ZTE Confidential & Proprietary 1

TABLE OF CONTENTS
Version:[4.16.10.20P80] ..................................................................................................... 1
ZTE SDR Software Release Notes..................................................................................... 1
TABLES ............................................................................................................................ 17
1 About This Document ................................................................................................... 28
2 Brief Description ........................................................................................................... 28

2.1 Release Notes.............................................................................................................. 28
2.2 Hardware ..................................................................................................................... 28
2.2.1 Change of Hardware Support .................................................................................... 28
2.2.2 Supportable Hardware Board .................................................................................... 28
2.3 Associated NEs’ Version .............................................................................................. 28
2.4 NEs’ Version Compatibility ........................................................................................... 29
2.5 Supported Upgrade Path .............................................................................................. 29
Table 2-4 Supported upgrade path ............................................................................... 29

2.6 3GPP Release (Optional) ............................................................................................. 30
3 Change of Device Capacity and Performance Index .................................................. 30
4 Change of Operation & Maintenance ........................................................................... 30

4.1 Change of GU Parameters ........................................................................................... 30
4.2 Change of GU Alarms .................................................................................................. 30
4.3 Change of GU Performance Index and Counter ........................................................... 30
4.4 Change of LTE Parameters .......................................................................................... 31
4.5 Change of LTE Alarms ................................................................................................. 31
4.6 Change of LTE Performance Index and Counter .......................................................... 31
4.7 NB Parameters............................................................................................................. 31
4.8 NB Alarms .................................................................................................................... 31
4.9 NB Counter .................................................................................................................. 31
5 Change of Functions..................................................................................................... 32
5.1 Change of GU Function List ......................................................................................... 32
5.2 New GU Function ......................................................................................................... 33
5.2.1 NodeB Cold Patch Function ...................................................................................... 33
5.2.2 R8863 S9000 (B8A/A8A/B8N) Supports 3.8M ........................................................... 35
5.2.3 Robort serving cell change ........................................................................................ 36
5.2.4 Optimization of HSDPA Signaling Packet Scheduling ............................................... 37
5.2.5 Performance Improvement in the Macrodiversity UL/DL Unbalanced Area................ 38
5.2.6 Conservative SG assignment in Multi-RAB Services ................................................. 42
2 ZTE Confidential & Proprietary

5.2.7 Adaptive HSDPA Retransmission .............................................................................. 43

5.2.8 Dynamic HSDPA target bler ...................................................................................... 45
5.2.9 Voice quality optimization in weak signal scenario..................................................... 46
5.2.10 Voice error cancellation for special UE .................................................................... 47
5.2.11 EVA for RACH......................................................................................................... 48
5.2.12 R8892N M8090 supports NBIC function ............................................................... 49
5.2.13 R8892N M8090 Supports Adaptive NBIC ................................................................ 49
5.2.14 Single PB1120A Supports 6 LTE Cells (dual UL mode) .......................................... 50
5.2.15 Add TMA and RET Information to Northbound Asset Report ................................... 52
5.2.16 Access distance compensation ............................................................................... 53
5.3 Enhanced and Optimization GU Function ..................................................................... 55
5.3.1 Remove the Constraint of DC Frequency Interval ≤ 5M at OMMB Side ..................... 55
5.3.2 HS-DPCCH Demodulation Optimization .................................................................... 56
5.3.3 HS-SCCH Power Optimization .................................................................................. 57
5.4 LTE Impacted Feature List ........................................................................................... 58
5.5 LTE New Features Description ..................................................................................... 62
5.5.1 User Service Restriction for Special Scenario ........................................................... 62
5.5.2 TWAMP Client........................................................................................................... 63
5.5.3 Carrier Aggregation(UL 2CC) .................................................................................... 65
5.5.4 Carrier Aggregation (DL 3CC, FDD+TDD)................................................................. 69
5.5.5 Cloud CA (distributed) ............................................................................................... 71
5.5.6 Support DL MIMO4*4 based on TM9......................................................................... 72
5.5.7 Downlink 256QAM..................................................................................................... 73
5.5.8 Network assistant CRS-IC without ABS..................................................................... 75
5.5.9 CA User Experience Aware Intra-LTE Load Balancing .............................................. 77
5.5.10 Dynamic authorization based on RB utilization of a cell ........................................... 78
5.5.11 Qcell energy saving ................................................................................................. 79
5.5.12 Ultra extended Cell Radius ...................................................................................... 82
5.5.13 DL Frequency offset pre-compensation ................................................................... 83
5.5.14 VoLTE in CA cell ..................................................................................................... 84
5.5.15 Support Recovery for Voice Packet Loss ................................................................ 85
5.5.16 A1 and A2 thresholds for voice/data distinguishing.................................................. 87
5.5.17 Inter-RAT user migration supported by Magic Radio ............................................... 88
5.5.18 X2 self-establishment optimization .......................................................................... 89
5.5.19 CA neighbor cell self-configuration .......................................................................... 92
5.5.20 ANR Consider not adding neighbor cells with illegal PLMNs ................................... 94
5.5.21 Downlink CA and 256QAM enabled simultaneously ................................................ 95
5.5.22 DL single-carrier 4*4 MIMO and 256QAM ............................................................... 96
5.5.23 A3 Not Being Deleted When B2 measurement is configured for Voice Quality Based
SRVCC ............................................................................................................ 99
5.5.24 Concurrence of Voice Quality Based and Coverage Based SRVCC...................... 100
5.5.25 Time to trigger SRVCC can be configured ............................................................. 101

5.5.26 Increase the demand for counter based on PDCP Discard Cause......................... 102
5.5.27 PDSCH scheduling RB is configurable for single direction within the standard
bandwidth ...................................................................................................... 105
5.5.28 Single RB allocation for VoLTE UE ....................................................................... 106
5.5.29 CPU Load requires adding counters to determine the stage .................................. 107
5.5.30 X2 Self-Establishment between Two Shared eNodeBs with Different Primary PLMNs108
5.5.31 LTE and NB Sharing One Association ................................................................... 109
5.5.32 Auto-Adaption Congestion Control: AC Barring ..................................................... 111
5.5.33 First Packet IP Delay Statistics Supported............................................................. 114
5.5.34 Downlink CA and Downlink 4*4MIMO.................................................................... 115
5.5.35 Downlink CA and Downlink 4*4MIMO and 256QAM .............................................. 116
5.5.36 UDC ...................................................................................................................... 118
5.5.37 Total Cell Transmit Power Statistics (Maximum and Average Power) .................... 119
5.5.38 Key Counter Statistics for Multiple PLMNs ........................................................... 121
5.5.39 E-CID Positioning Supports Type 2 TA Measurement Reporting ........................... 123
5.5.40 Dynamic Broadcast Weights ................................................................................. 125
5.5.41 Scheduling Evasion for SRLTE Terminal............................................................... 126
5.6 LTE Enhanced Features ............................................................................................ 127
5.6.1 Context Fetch .......................................................................................................... 127
5.6.2 eMBMS Counting .................................................................................................... 129
5.6.3 Service Based PCC Dynamic Selection .................................................................. 130
5.6.4 Flexible Scell configuration of multi-carriers............................................................. 131
5.6.5 Up to Three Coordinating Cells in CS...................................................................... 133
5.6.6 Flexible UE Handling Strategies Supported in Case of an S1 Link Failure .............. 134
5.6.7 Supporting CSFB Process Optimization During VoLTE Conversation ..................... 138
5.6.8 To Prohibit eSRVCC before Alerting in VoLTE Call ................................................. 139
5.6.9 eNodeB supports 512 groupIds for each S1 ............................................................ 140
5.7 NB-IoT Function List................................................................................................... 141
5.8 NB-IoT Function Description ...................................................................................... 144
5.8.1 Support CP (Control Plane) Service ........................................................................ 144
5.8.2 Support 3.75K ST .................................................................................................... 144
5.8.3 Support 15K ST/MT................................................................................................. 145
5.8.4 Support Standalone Mode ....................................................................................... 146
5.8.5 Support Short/Long CP NB-PRACH ........................................................................ 147
5.8.6 Support System Information Broadcast ................................................................... 148
5.8.7 Support Idle MS Mobility.......................................................................................... 149
5.8.8 Support Paging Function ......................................................................................... 149
5.8.9 Support DL Data Transmission via Single Antenna Port .......................................... 150
5.8.10 Support DL Data Transmission via Two Antenna Ports (SFBC) ............................ 151
5.8.11 Support NB-PDCCH Frequency Reuse ................................................................. 152
5.8.12 Support Enhanced 20dB Coverage ....................................................................... 153
5.8.13 Support 2-Antenna MRC and IRC ......................................................................... 154

5.8.14 Support 3.75k/15k ACK Channel ........................................................................... 155

5.8.15 CCE1 Supports NB-IoT Single Mode..................................................................... 156
5.8.16 CCE1 Supports LN Hybrid Mode ........................................................................... 157
5.8.17 BPN2 Supports NB-IoT Single Mode ..................................................................... 158
5.8.18 BPN2 Supports LN Hybrid Mode ........................................................................... 158
5.8.19 Support BPN0A (Only for China Telecom and China Unicom)............................... 159
5.8.20 BPN0_b supports NB-IoT Single Mode ................................................................. 160
5.8.21 CC16B Supports NB-IoT Single Mode................................................................... 161
5.8.22 CC16B Supports LN Hybrid Mode ......................................................................... 162
5.8.23 CCE1A Supports NB-IoT Single Mode .................................................................. 163
5.8.24 CCE1A Supports LN Hybrid Mode ........................................................................ 164
5.8.25 BPN1A Supports NB-IoT Single Mode .................................................................. 165
5.8.26 Use USB Disk to Open a Site ................................................................................ 165
5.8.27 Support Uplink Frequency Hopping Function ........................................................ 166
5.8.28 CCE1 Supports GLN Hybrid Mode ........................................................................ 167
5.8.29 BPN2 Supports GN Hybrid Mode .......................................................................... 168
5.8.30 CC16D Supports NB-IoT Single Mode .................................................................. 169
5.8.31 CC16D Supports LN Hybrid Mode ......................................................................... 170
5.8.32 BPN2A Supports N Single Mode and LN Hybrid Mode .......................................... 171
5.8.33 Number of NB RRC Instances Supported by CC ................................................... 172
5.8.34 3.75K SINR and Power Measurement Reporting .................................................. 172
5.8.35 Support eDRX Function......................................................................................... 173
5.8.36 Support Connection State SR (Scheduling Request) ............................................. 174
5.8.37 Redirection Based on the number of RRC Connections ........................................ 175
5.8.38 15K SINR and Power Measurement Reporting ..................................................... 177
5.8.39 Support UL/DL AMC .............................................................................................. 178
5.8.40 Configure the Number of Tones Over a Sub-carrier Space ................................... 179
5.8.41 Admission Control Based on UL PRB.................................................................... 180
5.8.42 Support 3.75K Even Subframe Scheduling............................................................ 181
5.8.43 EAB Admission Control Based on the Number of RRC Connections ..................... 182
5.8.44 Optimize Paging Process ...................................................................................... 183
5.8.45 Configure AMC B-type Parameters ....................................................................... 184
5.8.46 Support UP Basic Function ................................................................................... 186
5.8.47 Support UP Suspending and Resuming Process .................................................. 187
5.8.48 OMMB Supports PNP ........................................................................................... 187
5.8.49 BPN1_A Supports N and LN ................................................................................. 189
5.8.50 OMMB Supports NB License ................................................................................. 190
5.8.51 Support CCE1B Board .......................................................................................... 191
5.8.52 Support FS5B Borad ............................................................................................. 192
5.8.53 Support LN Same SCTP Associated ..................................................................... 193

6 Solved Defects ............................................................................................................ 196

6.1 Solved GU Defect List ................................................................................................ 196
6.2 Description of GU Solved Defects .............................................................................. 199
6.2.1 SCTP Message Retransmission Rate is wrongly calculated .................................... 199
6.2.2 Impose Constraints on 4-diversity ........................................................................... 199
6.2.3 After Upgrading from V4.15 to V4.16, Antenna Supporting Capability of R8119
F1821A is Changed from 4 Channels to 6 Channels. The Relevant
Configuration at OMMB Has to be Changed Mannually. ................................ 201
6.2.4 Operator 1 HSDPA Power is Wrongly Counted ....................................................... 201
6.2.5 When BPN2 Service Mode is Changed from Non-UMTS to Including UMTS, Inter-BP
User Service Becomes Abnormal .................................................................. 202
6.2.6 CR0 at Slot 4 is Wrongly Recognized, Causing DPA Rate = 0 ................................ 203
6.2.7 After Replacing BPC With BPK in a Site, RACH BLER Rises.................................. 204
6.2.8 HSPA UEs Fails to Access a High-load Site. This Situation Cannot be Recovered. 204
6.2.9 In the Configuration of BPC Board, Drop Call Rate Becomes Worse in 2.5Km
Coverage Radius and High-speed Cell .......................................................... 204
6.2.10 R8892E M1821 Does not Support Rx Spectrum Analysis and Carrier Spectrum
Analysis in OMMB RF Analysis Function ....................................................... 205
6.2.11 Adjust BPN Delay Measured at Optical Port .......................................................... 206
6.2.12 Some Sites Are Configured with CCA. After Running FCE Hot Patch, These Sites
Repeatedly Reset. ......................................................................................... 206
6.2.13 BPN2 Resets......................................................................................................... 207
6.2.14 UE cannot access to the network When the VAMOS switch is on ......................... 207
6.2.15 In the situation that R8892N is used, uplink RQ becomes worse ........................... 208
6.2.16 When CR0 boardfunctionmode is configured to be LTE-FDD CloudRadio[5], KPIs
may decrease and CE resources may become insufficient in UMTS large-traffic
sites ............................................................................................................... 208
6.2.17 In IPA Configuration, Some Handsets Drop Calls During Ringing Period .............. 209
6.2.18 The TA value in the cell is a little larger. ................................................................ 210
6.2.19 When Running PIM Detection Function in a Batch, Many Sites Return Serious Alarm
State .............................................................................................................. 210
6.2.20 Optimize the Statistical Value of CPICH Average Power Counter ......................... 211
6.2.21 When signal quality is poor, DTX ratio is high for HSDPA UEs .............................. 212
6.2.22 In a multi-mode site, after incrementally changing GSM or LTE configuration data
such as GSM IP or LTE IP, new UEs cannot access to UMTS site............. 213
6.2.23 Transmission link changeover causes GSM process to become abnormal and reset214
6.2.24 CSSR KPI keeps abnormal when IUB Transmission recovers from congestion..... 215
6.2.25 There is a problem of abnormal statistical indicators in two sites of Algeria ........... 215
6.2.26 Average CPU Usage of the CC Board on the eNodeB Is Greater Than 100% and
Displayed As 3000% ...................................................................................... 217

6.2.27 When NodeB reboots or BPN2 board reboots, there is a small probability that
RLC retransmission rate reaches 100% in some cells, but HSDPA throughput
approximates to 0. ...................................................................................... 217
6.2.28 Activate TWAMP monitoring function. Several sites have packet loss and jitter
problem in the uplink direction........................................................................ 219
6.2.29 C370130001 (link connection time between Node B and OMCB) becomes abnormal
on Algeria’s network. Occasionally the value shown in EMS is 1200 seconds.219
6.2.30 After putting 900M 2T cells into operation, some cells are repeatedly deleted and
set up. Services are affected ........................................................................ 220
6.2.31 Some brands of UEs process uplink DTX abnormally, causing small MOS ........... 220
6.2.32 In the coordinated configuration of UBPG1 board and R8863 baseband
combined-cabinet mode, partial carriers have no power output in downlink
direction ......................................................................................................... 221
6.2.33 In the configuration of R8863 baseband combined-cabinet mode, carrier intelligent
shutdown function has a defect ...................................................................... 222
6.2.34 Failure in loading BP hot patch causes HSDPA RLC retransmission rate to nearly
reach 100% ................................................................................................... 223
6.2.35 In the environment that dual-CC is configured and FCE is connected to RSU40
U216, FCE reports an alarm, indicating software runs abnormally. ................ 225
6.2.36 After eNB reset, CSSR degraded in some cells ..................................................... 225
6.2.37 In some sites, BPK-d repeatedly reports “software runs abnormally” when traffic is
busy. .............................................................................................................. 227
6.2.38 BPN board may reset when CPU Load is high ...................................................... 227
6.3 Solved LTE Issues List ............................................................................................... 228
6.4 Solved LTE Issues Description ................................................................................... 242
6.4.1 20160524164447 VoLTE RTP packet loss .............................................................. 242
6.4.2 20160624095904 Optical module alarms on multiple sites after version upgrade to
V3.3 ............................................................................................................... 243
6.4.3 20160625183337 When an FDD LTE eNodeB is upgraded, the KPI counter
"C373505499 increases greatly ..................................................................... 244
6.4.4 20160720085806 Super cell outage on 15 eNodeBs after version upgrade due to
"License limited"............................................................................................. 244
6.4.5 20160826231938 eSRVCC handover fails, causing abnormal UE release .............. 245
6.4.6 20160831112249 Downlink retransmission interval is large in the VoLTE test ........ 246
6.4.7 20160914192815 In combination mode for the R8863 S2100, the “Referenced Signal
Power of BP Resource” of OMMB cannot be configured to 18.2 db ............... 247
6.4.8 20160918105816 Specific UEs cannot access the network after upgrading from
V3.20.50.20 P10 to V3.30.20.30 .................................................................... 248
6.4.9 20160918174531 RRC request rejected due to eNodeB admit failure ..................... 249
6.4.10 20160923051749 After the system is upgraded to V3.3.20 P40, the incoming
handover failure rates on S1 and X2 increase................................................ 250

6.4.11 20160927093722 High call drop rate due to the PERIOD_TA_MEAS option selected
for the MR task .............................................................................................. 251
6.4.12 20161009150741 Large Number of messages indicating context modification failure
due to other causes after system upgrade to V3.3 ......................................... 252
6.4.13 20161025110052 Scheduling according to DRX Enabling when Cell Connect
Reestablishment with DRX is disabled ........................................................... 253
6.4.14 20161101151720 CSFB failure ............................................................................. 253
6.4.15 20161107045420 BPL1 board reset repeatedly due to more than 64 UTRAN
neighbor cells after SDR15 version upgrade .................................................. 254
6.4.16 20161107094430 eNodeB KPI (downlink transmission bandwidth (megabit/s))
abnormal........................................................................................................ 255
6.4.17 20161107115518 Five cells disconnected and having no msg1 ............................ 256
6.4.18 20161118091237 GL RRU having parameter configuration error alarms after system
upgrade to V4.15 ........................................................................................... 256
6.4.19 20161122003533 Secondary carrier RB insufficiency in CA handover .................. 257
6.4.20 20161122112839 Probabilistic call failure due to UE not responding to Paging
messages in reestablishment scenarios for the CSFB test ............................. 258
6.4.21 20161220114504 Admission failure on eNodeBs with CA function ........................ 259
6.4.22 20170105095756 eNodeB using a temporary License file in default state for a
moment after system upgrade from V3.3 to V3.4 ........................................... 260
6.4.23 20170116100312 No downlink traffic after handover from a ZTE eNB to a Nokia eNB
...................................................................................................................... 260
6.4.24 20170220160622 In six cells with 4 ant mode, one of the cells on BPL1 setup fail 261
6.4.25 20170112055252 After activating the speedtest switch, UE executing speedtest
preempts RB resources ................................................................................. 262
6.4.26 20170131000002 The self-defined CSFB failure times are found minus after
upgrading from UR14 to UR15 ....................................................................... 263
6.4.27 20170203111053 C373384345 Average User Number Cat 6 was reduced after
upgrading to 4.15.10.30P30. .......................................................................... 264
6.4.28 20170215060648 UE fails to execute intra-frequency handover for SRVCC based on
signal quality .................................................................................................. 264
6.4.29 20170216211458 Signal quality based SRVCC has no protection mechanism during
threshold triggering ........................................................................................ 265
6.4.30 20170214031031 When eNodeB upgrades to a new version, the CDT data does not
contain CT signal ........................................................................................... 266
6.4.31 20170213205208 After Fast Return to the 1.8G LTE cell in CSFB procedure, UE
handover to higher 2.6 G PCELL frequency, and then UE can’t receive Modify
EPS bearer context request message from MME........................................... 267
6.4.32 20170127081650 The load balance UE which has fast return to LTE cell after CSFB
cannot receive the S1 Modify EPS bearer context request message ............. 268
6.4.33 20170303172448 RRC Release After an Initial Message is Sent to the New MME269

6.4.34 20170303151948 The eNodeB Name and Cell Name Is Abnormal in Performance
Data Query .................................................................................................... 270
6.4.35 20170302103414 Decrease of the LTE CSFB SR Indicator from 99.9% Before
Upgrade to 99.4% After Upgrade With a Deterioration Rate of 0.5%.............. 271
6.4.36 20170301102122 Voices Not Heard Clearly in Some Cases When F7 Mobile Phones
Call Samsung Mobile Phones ........................................................................ 272
6.4.37 20170228092821 Abnormal Value in the KPI Statistical Results of a Field Site..... 273
6.4.38 20170224120329 Increased UL IP Throughput After the eNodeB Upgraded From
V3.2 to V3.3 ................................................................................................... 273
6.4.39 20170207222615 Deterioration of the E-RAB Call Drop Rate After the eNodeB
Upgraded from 4.13.10.30P42 to 4.15.10.20P51 ........................................... 274
6.4.40 20170206173525 Active E-RAB Drop Rate Increase After Upgrading to V3.3....... 275
6.4.41 20170206172312 Serious Decrease in the CQI , Equivalent Throughput and 64QAM
After the BPL0 Site Was Upgraded from V3.2 to V3.3 ................................... 276
6.4.42 20170204102421 Paging Loss in Sites with No Paging Congestion ...................... 277
6.4.43 20170118090200 Falsely High Statistics of the Number of RRC Users ................. 277
6.4.44 20160707102904 Statistical Result of "C373505499 Greater Than P340440 ........ 278
6.4.45 20160907231755 eNodeB Failing to Select the Correct PLMN to Return an ACK
Message After Receiving RIM information During 2G RIM Information Exchange
in the MOCN Shared Network ........................................................................ 279
6.4.46 20160819184450 No More Than Nine Blackcell Lists Related to Forbidden TACs 280
6.4.47 20160809141629 Increased RRC Call Drop Rate After the Upgrade .................... 281
6.4.48 20161012160546 Serious Uplink Packet Loss Rate in Random Distribution With No
Top Cell ......................................................................................................... 282
6.4.49 20161009044205 The Number of Intra-eNB Inter-Frequency Handovers is
Significantly Decreased After DRX Closed ..................................................... 283
6.4.50 20161114095807 High VoLTE Call Drop Rate Due to Redirection ........................ 284
6.4.51 20160728180828 Deterioration of the RRC Call Drop Rate and E-RAB Call Drop
Rate After Upgrade to V3.30.20.21 ................................................................ 285
6.4.52 20161008115245 Intra-eNodeB Handover Failure During Migration (Inverted NAS
Sequence) ..................................................................................................... 286
6.4.53 20161009150018 Decreased CN Traffic Due to S1 Reset..................................... 287
6.4.54 20161104204855 After Version Upgrade, There Are Many Link Disconnections Due
to the S1 Link Error in A Few Sites, but the SCTP Link Is Disconnected Only
Once .............................................................................................................. 288
6.4.55 20161222165128 The BPN2 Board Restart Fault ................................................. 289
6.4.56 20161227172031 Total Number of Abnormal Releases of Eight QCI1s in Some Cells
Is Smaller Than the Value of C373505300 ..................................................... 290
6.4.57 20170104042608 The eNodeB Sends an Empty Reconfiguration Message but the
UE Does Not Return an Assignment Complete Message, so the eNodeB
Releases the UE Upon Timeout ..................................................................... 291

6.4.58 20170329144600 Baseband Reset Problem Due to a Software Operation Error in CA

Sites along the Subway.................................................................................. 292
6.4.59 20161008140129 Decreased CSFB Success Rate after the UTRAN ANR Switch Is
Enabled ......................................................................................................... 293
6.4.60 20161103090911 After the Customized Description Field in AISG Configuration Is
Modified, the AISG Communication Link Disconnection Alarm will Be Reported
during AISG Rescanning................................................................................ 294
6.4.61 20161018173804 Automatic Reset during RRU Operation .................................... 295
6.4.62 20161022123503 Increased NI Noise After the R8882 S2100 B Is Upgraded to V4.15
...................................................................................................................... 296
6.4.63 20170103083733 Sudden Increase of the CC Board Load From 10% to 66% in an
eNodeB.......................................................................................................... 297
6.4.64 20170116172728 Low Rate in Indoor Distribution RRU Cascading Coverage and is
Recovered After the Sampling Rate is Modified ............................................. 298
6.4.65 20170309164357 Abnormal Handover Indicator ................................................... 299
6.4.66 20170112163626 Clearance Time of Some History Alarms Earlier Than Occurrence
Time............................................................................................................... 300
6.4.67 20161229093729 Failure to Query Physical Devices in Dynamic Management .... 301
6.4.68 20170419100448 Qcell pRRU Rack Number Cannot Exceed 216 ........................ 302
6.4.69 20161012144430 Sleeping Cell Problem .............................................................. 303
6.4.70 20161018173856 Incorrect Counters C373930024 & C373930025 ....................... 304
6.4.71 20161104104133 After A Broken SCTP Link is Recovered, There Is No
Transmission Power on the RRU and Services are Interrupted; Services are
Recovered After the PA is Disconnected and Enabled Again ......................... 306
6.4.72 20161116110433 Repeated Reset of the CC Board at a Site ................................ 307
6.4.73 20161215133123 Average CPU Usage of the CC Board on the eNodeB Is Greater
Than 100% and Displayed As 3000% ............................................................ 308
6.4.74 20161202070358 Frequent Disconnection of the OMC Link After FST+OMC+IPSec
Configurations Are Added on the UR15 eNodeB Version ............................... 309
6.4.75 20161209161221 Supporting Automatic Update of the Summer Time and Summer
Time Start/End Time Format of Month-Week-Day.......................................... 310
6.4.76 20170105091354 Maximum Throughput (Mbps) of DL Received Data of the eNodeB
Exceeds 1Gbps in Actual Statistics ................................................................ 311
6.4.77 20161207095523 No Power on the RRU During Query......................................... 312
6.4.78 20170110013514 Repeated Printing of UDT Signaling Messages ........................ 313
6.4.79 20160729141028 UDT Decodes noncriticalextension in Error ............................... 314
6.4.80 20160811171346 MTS Data Fail to Display IMSI on the EMS ............................... 315
6.4.81 20161114223551 Time is Six Hours Later Than the Local Time After Northbound
Trace Decoding.............................................................................................. 316
6.4.82 20170213175520 High E-RAB Call Drop Rates in Top Sites ................................. 317
6.4.83 20170121120334 Traffic of CA Terminals Lower Than Traffic of Non-CA Terminals in
Speed Tests................................................................................................... 318

6.4.84 20170112082841 Increase of Prach Average NI by 30 dB or Above After UL CoMP

Deployment.................................................................................................... 319
6.4.85 20170328171015 NI Is -120 In Case of Bypass and Is -70 In Case of Non-Bypass
after Tower-Mounted Amplifiers Are Added to the RRU ................................. 319
6.4.86 20160627194034 After BPN2 Replaces BPL1, the Minimum Power of a Cell Is
Increased, the Minimum Power of Another Cell Is Reduced, and the Power of 0
mW Occurs Before and After Replacement .................................................... 320
6.4.87 20161108143331 Statistical Result of C373414597 (Average NI of Carrier(dBm))
Inconsistent With the Average Value of PB-Level Statistics ........................... 321
6.4.88 20161104162805 Low Speed at Far Points in CAs in the FDD+TDD Network ...... 322
6.4.89 20170414182659 RTP Packet Loss Due to Large Downlink Scheduling Intervals
before Handover ............................................................................................ 323
6.4.90 20170418002209 Inaccurate Average RSRP Value of the Serving/Target Cell ..... 324
6.4.91 20170420110700 Lighting Fault of Optical Module for Newly added R8861 .......... 324
6.4.92 20170420171152 Simultaneous Report of GPS Positioning Alarms from FDD LTE
eNodeBs Failing to Position in Different Areas During Several Timing Periods325
6.4.93 20170505094113 Large Changes to Maximum NI and Average NI of the PRACH
after a Version Update to V3.3 ....................................................................... 327
6.4.94 20170422023728 RRU Disconnections in Some New LTE Sites........................... 327
6.4.95 20170418163230 Large Number of Reestablishment Requests Caused by a Sector
Reconfiguration Failure .................................................................................. 328
6.4.96 20170412181047 Data Output Existing in the Counter (Based on Blind Handover)
when Load/Measurement Based Load Balance is Enabled ............................ 329
6.4.97 20170412122658 Deteriorated KPIs after a New eNodeB-Level License File is
Loaded........................................................................................................... 331
6.4.98 20170406100941 CellID Reported as 65535 Sometimes ...................................... 331
6.4.99 20170405152832 Deteriorated E-RAB Call Drop Rate after the Netmax-L Is Enabled332
6.4.100 20170401154539 Some UEs are Released after Load Balancing Based on RRC
User Access and CA are Enabled at the Same Time ..................................... 333
6.4.101 20170327102011 Two Sleep Cells in a Single eNodeB ....................................... 334
6.4.102 20160907063911 Uplink BLER is High When Adding and Removing Secondary
Carrier, Affecting UE Uplink throughput ......................................................... 335
6.4.103 20170609195530 Low Speed of Some Samsung S8 UEs in the Speed Test ...... 335
6.4.104 20170601042826 LTE-UMTS Handover Failure .................................................. 336
6.4.105 20170526143015 Added E-RAB Setup Successful Rate Drops Greatly (Even to 30%
on Some Sites) After Deploying the MR Feature in the Current LTE Network 337
6.4.106 20170519194516 Number of Inter-Frequency Handover Out Requests With/Without
GAP Changed Greatly ................................................................................... 338
6.4.107 20170515223238 Abnormal RSSI KPI on a Site in the Current Network ............. 339
6.4.108 20170523211629 UL throughput in PCC of CA UE continue to drop below 10M in
intra-cell handover process ............................................................................ 340

6.4.109 20170713144315 When NB-IOT is Enabled on LTE eNodeB, More than 60 Sites
Reported Blocking Alarms. 40 Sites Recovered itself, and More than a Dozen
Need Manual Processing ............................................................................... 341
6.4.110 20170725190154 Software Runs abnormal in the CA Use Handover with SCC
Scenario ........................................................................................................ 342
6.4.111 20170625105513 Some of the Sites the VoLTE Calls are Dropped When Using
Apple Phone, and the Phone Interface Appeares “Call Failed”....................... 343
6.4.112 20170821161304 VoLTE UE is Released after eNodeB Receiving the UE Context
Modification Request with the CSFB Indication .............................................. 344
6.4.113 20170612124416 BPN2 board Resets and Reports Alarm “software runs abnormal”
...................................................................................................................... 345
6.4.114 2017071721244 CSSR Indicators of the Whole Network are Descreased ........... 346
6.4.115 20170906234253 In 3CC CA Test, Throughput is Reduced to Zero and
Reestablishment Occurs ................................................................................ 347
6.4.116 20170903184453 KPI statistics of TA distribution are exception.......................... 348
6.4.117 20170908155846 One or More Cells Scheduling Capacity Per TTI are Insufficient
for BPN2 with 6 cells ...................................................................................... 349
6.4.118 20170922130010 P10 UE is Released Frequently after Accessing, SCC is not
added and UE can not Do Service in CA Test ................................................ 350
6.4.119 20171024144305 RRC Connection Reconfiguration for 3CC CA Fails and UE
Starts RRC Connection Reestablishment....................................................... 351
6.4.120 20171022052609 eNodeB Reset Due to BNP2 Reset after LB and Cell Reselection
Priority Are Disabled ...................................................................................... 352
6.4.121 20171003182210 RRC Call Drop Rate Is Increased and Is Restored after the CCE
Board Is Restarted ......................................................................................... 353
6.4.122 20170922133939 CA User Data Volume Does Not Match the 2CC and 3CC
Statistical Result ............................................................................................ 354
6.4.123 20170912102025 Sleeping Cell Is Detected on an eNodeB ................................ 354
6.4.124 20170829144028 R8988 S3500 Cannot Enable AISG and Necessary Information
for Dynamic Management Is Missing on the EMS .......................................... 355
6.4.125 20170811181731 Sleeping Cell Is Detected on a Qcell and No UE Accesses the
Cell ................................................................................................................ 356
6.4.126 20170726104847 CCE1 Restarts Repeatedly after a Hot Patch Is Installed ........ 357
6.4.127 20170714002057 UE Capability (Supporting for 4x4 MIMO) Displayed in the
Samsung S8 UE Log Is Different from That of the ZTE eNodeB Log ............. 358
6.4.128 20171009231056 Incorrect Average Number of RRC Connections (Counter
C373200030) Is Reported .............................................................................. 359
6.4.129 20171017162247 High Type-2 Location Information Report Failure Rate and Low
Location Success Rate .................................................................................. 360
6.4.130 20171019115216 One of Four SpeedTest UEs Has No Data Flow with SpeedTest
Being Enabled on the eNodeB ....................................................................... 361
6.4.131 20170926095849 Handover Prepareration Failure in MOCN Network Sharing Site362

6.4.132 20171106235623 E-RAB Drop Rate Deteriorated Significantly after Upgrade to

V4.16.10.20P50 ............................................................................................. 363
6.4.133 20171023094938 LTE DL 64QAM Usage is Dropped after Upgrade to UR16 ..... 364
6.4.134 20171204172423 The iphone Siri Service is Abnormal after TCP Proxy is Enabled365
6.4.135 20171102034758 Cell RRC Number and ERAB Number are zero ...................... 366
6.4.136 20171017104554 RRUs are Reset with the Reason "the watchdog resets" ........ 367
6.4.137 20171009230453 The HTTP Download Speed is Low After TCP ACK Split is
Enabled ......................................................................................................... 368
6.4.138 20170914094904 QCELL LTE Sites Enter into "sleep" Causing Users Unable to
Access and Zero Cell Throughput .................................................................. 369
6.4.139 20170902171018 The Number of Re-establishment Requests Due to "Other
Reason" on the FDD Sites is Increased Suddenly ......................................... 370
6.4.140 20171211222411 Handover Preparation Failed when UE hands over from Normal
eNodeB to Sharing eNodeB ........................................................................... 371
6.4.141 20171214043047 RRC Setup Success Rate Drops Sharply Because of Number of
E-RAB Release Due to Uu Interface Timeout increasing ............................... 372
6.4.142 20171117091909 Records with a Cell ID of 65535 Exist in the Cell-level Counters'
Statistics ........................................................................................................ 373
6.4.143 20171211110050 After upgrade to V3.40.20.10P50, VOLTE call dropped rate
increases. ...................................................................................................... 373
6.4.144 20171209110551 After Upgrade to V4.16.10.20P50, An Abnormal FDD Product
Process Causes the Baseband Board to Reset ............................................. 375
6.4.145 20171204033111 The FTP Upload Rate is low Because of IPSec Packets
Decrypting Abnormal ..................................................................................... 376
6.4.146 20171205162142 Number of RRC Connection Users in Frequency 1.8G and 2.6G
is unevenly Distributed After the MR Inter-frequency Measurement is Enabled377
6.4.147 20180125214144 Parts of pRRUs Have No power for 2.6G QCell Site ............... 378
6.4.148 20180111005819 One Cell (CellID = 6) of A Site Setup Failure after Upgrading . 379
6.4.149 20180205143606 The AISG Inventory Information Reported by the eNodeB is
Inaccurate ...................................................................................................... 380
6.4.150 20180129141023 The Call Drop Rate is Deteriorated ......................................... 381
6.4.151 20180327161502 E-RAB Drop Rate is Increased................................................ 382
6.4.152 20180309111551 After One XGW on The Network Goes Offline, some BS8922
Have Alarms: S1 GTP-U path unavailable (198094466) ................................ 383
6.4.153 20180326153047 The Success Rate of RRC Connection Setup Is Decreased ... 384
7 Left-Behind Defects .................................................................................................... 385
Null .................................................................................................................................. 385
8 Version Restrictions and Things to be Noticed ........................................................ 386

8.1 Macro-NodeB Version Restrictions............................................................................. 386

8.1.1 Version Package Download Restriction ................................................................... 386

8.1.2 Restriction on Version Package Pre-Activation, Taking Effect After Activation
Operation ....................................................................................................... 386
8.1.3 Activation Effective, Activation Cancellation Operations Aiming at all Version
Packages ....................................................................................................... 387
8.1.4 Version Package Deletion Restriction...................................................................... 388
8.1.5 To Configure Ultra Cell UL Enhancement Cell, AI_TIMING of All Cells Must be 1 and
Cell Radius Must Be ≤10KM .......................................................................... 388
8.1.6 Super-far Cell Restriction ........................................................................................ 388
8.1.7 If Ultra Cell UL Enhancement and Ultra-cell Dl Power & HSDPA Code Multiplexing
Functions Change, All BPK Boards Will Reset ............................................... 389
8.1.8 CS Over HSPA Function ......................................................................................... 389
8.1.9 In Hybrid GU configuration, there is an STSR cell that is built with RSU82 GUL9016,
RSU82 GUL1816 and other RRU, which is connected to BBU with a super-long
optical fiber. Supposed that the distance from RSU82 to BBU is L1, the distance
from the RRU to BBU is L2. A Restriction is that L2 shouldn’t be longer than L1
for more than 25Km ....................................................................................... 390
8.1.10 1T RRU (R8881) Optical Rate Restriction ............................................................. 391
8.1.11 1T RRU (R8881, RSU60E, RSU40) Only Supports 22V High Class of AISG and
NSBT ............................................................................................................. 391
8.1.12 HSSCCH Code Restriction .................................................................................... 392
8.1.13 Ultra-cell Dl Power & HSDPA Code Multiplexing Function Restriction ................... 392
8.1.14 Restriction on RRU if it is Connected to BS8912 U2100 ........................................ 393
8.1.15 Configure One Detection Mode for Static Route Table .......................................... 393
8.1.16 Restriction on the Number of Remote Racks ......................................................... 394
8.1.17 FS5 Configuration Requirement at Background..................................................... 394
8.1.18 Bearer Pre-Configuration Function Only Supports IP Transmission, It Neither
Supports ATM+IP Dual-stack nor ATM Transmission .................................... 395
8.1.19 Restriction on Hybrid Scenario While Upgrading CCA to CCC .............................. 395
8.1.20 CC0/CC2 not Support IPV6 Due to its Chip Limit .................................................. 396
8.1.21 Restriction on BPK_d Configuration ...................................................................... 396
8.1.22 Maximum 4 Levels of Cascading Connection of 1T RRU (R8881, RSU60E, R8861)
and Old 1T RRU (RTR, RTR2, DTR, ADTR) .................................................. 397
8.1.23 Things to be Noticed When RSU82 GUL1816 Uses Cross Diversity and Primary &
Diversity Detection ......................................................................................... 397
8.1.24 Things to be noticed when RSU82 GUL1816 starts manual frequency scanning
function via OMMB ......................................................................................... 398
8.1.25 In the situation that new 1T RU runs frequency scanning function and PA is enabled,
Tx frequency is not the configured one. This may bring interference to
non-configured frequency point. ..................................................................... 399

8.1.26 During the process that new 1T RU runs frequency scanning function, manually
activating/deactivating PA operation should be avoided unless there is a special
reason............................................................................................................ 399
8.1.27 Number of Cells, Number of Carriers Supported by CC0/CC2 ............................... 400
8.1.28 Restriction on Cell Entire Frequency Band Scanning Function .............................. 400
8.1.29 Restriction on Air-interface Soft Synchronization Function .................................... 401
8.1.30 Things to be Noticed in UBPG3 Configuration ....................................................... 401
8.1.31 Restriction on Smart Power-on/off Function .......................................................... 402
8.1.32 Restriction on GU Power-sharing Function ............................................................ 402
8.1.33 Restriction on DBB Hotpatch Loading ................................................................... 403
8.1.34 Restriction on Local Switch ................................................................................... 403
8.1.35 Restriction on BCCH Changeover Function........................................................... 404
8.1.36 Super NodeB not Support IPV6 (IPOE1 not Support IPV6) ................................... 404
8.1.37 IPV6 OMCB Channel not Support IPV6 IN IPV6 ................................................... 404
8.1.38 Restriction on EVA Function .................................................................................. 405
8.1.39 Restriction on GL Power Sharing .......................................................................... 405
8.1.40 Restriction on UL Adaptive Filter ........................................................................... 405
8.1.41 VAMOS (Voice services over Adaptive Multiuser channels on One Slot) Capability
Limit ............................................................................................................... 406
8.1.42 In the Configuration of Single-UMTS RUs, the Configured Antenna Unbalanced
Alarm Parameter (AntDetectorU) May be Invalid............................................ 407
8.1.43 UBPG0 Does not Support NCC Extended Channel ............................................... 407
8.1.44 Cross Diversity is not Supported in R8882/RSU82 UL Hybrid Scenario ................ 408
8.1.45 Cell Deletion/Addition Due to the Change of Interference Cancellation (IC) Switch408
8.1.46 If Changing DC Relation via OMMB, the Corresponding Cell May be Deleted/Added409
8.1.47 Constraints When Both FS and BPN2 Provide Optical Ports in GSM System ....... 409
8.1.48 Constraints When CR0 is Inserted to Slot 4........................................................... 410
8.1.49 The CC0/2 board can only support 72 GSM carriers ............................................. 410
8.1.50 Configuration restriction on access distance compensation ................................... 410
8.2 Restrictions on QCELL Version .................................................................................. 411
8.2.1 A Group of Cascaded PBs with 10G Optical Port Can Support Up to UMTS UL/DL 20
IQ Channels ................................................................................................... 411
8.2.2 QCELL System Does not Support 6G Optical Port .................................................. 412
Table 8-50 QCELL System Does not Support 6G Optical Port .................................... 412
8.2.3 The Bandwidth of UMTS Local Cell Supports 5M\4.8M\4.6M .................................. 412
Table 8-51 The Bandwidth of UMTS Local Cell Supports 5M\4.8M\4.6M .................... 412
8.2.4 CC0\CC2 Does not Support QCELL Configuration Scenario ................................... 413

Table 8-52 CC0\CC2 Does not Support QCELL Configuration Scenario .................... 413
8.2.5 In QCELL Networking Scenario, LTE Baseband Resource Should be Configured to be
PB Mode ........................................................................................................ 413
8.2.6 Port 2 and 3 of PB1000 are Unavailable for the Moment, Not Supporting Relevant
Function ......................................................................................................... 414
8.2.7 The Range of PB Rack Number is 3-201; the Range of PRRU Rack Number is 3-201.
214-251 ......................................................................................................... 414
8.2.8 Support Up to 24 PBs, 192 PRRUs ......................................................................... 415
Table 8-56 Support Up to 24 PBs, 192 PRRUs ............................................................. 415

8.2.9 Previous PB Reset Will Affect the PRRU, Connected to Next PB ............................ 415
8.2.10 PRRU Does not Support the LTE FDD Cells From Different Baseband Process
Boards ........................................................................................................... 416
8.2.11 QCELL System Supports Up to 4-level Cascading Connection and Total length of
4-level Optical Fiber should not Exceeds 10KM ............................................. 416
8.2.12 Previous PB1000 Boot Version Cannot Cooperate With EPLD Version C5 or Above.
Otherwise, the Device Keeps Staying at BOOT State After Powered on. ....... 417
8.3 Version Restrictions of LTE ........................................................................................ 418
8.4 NB-IoT Version Restrictions and Left-Behind Defects ................................................ 418
8.5 Other Issues ............................................................................................................... 418

TABLES
Table 2-1 Release upgrading information .............................................................................29

Table 2-2 Associated NEs’ Version ......................................................................................29
Table 2-3 RNC version compatibility ..................................................................................30
Table 2-4 Supported upgrade path ....................................................................................30
Table 2-5 3GPP release ....................................................................................................31
Table 5-1 New software function list ..................................................................................33
Table 5-2 NodeB cold patch function .................................................................................34
Table 5-3 R8863 S9000(B8A/A8A/B8N) supports 3.8M .....................................................36
Table 5-4 Robort serving cell change .................................................................................37
Table 5-5 Optimization of HSDPA Signaling Packet Scheduling ........................................38
Table 5-6 Performance improvement in the macrodiversity UL/DL unbalanced area .........39
Table 5-7 Conservative SG assignment in Multi-RAB Services..........................................43
Table 5-8 Adaptive HSDPA Retransmission ......................................................................44
Table 5-9 Dynamic HSDPA target bler ...............................................................................46
Table 5-10 Remove the constraint of DC frequency interval ≤ 5M at OMMB side ...........56
Table 5-11 HS-DPCCH demodulation optimization ..........................................................57
Table 5-12 HS-SCCH power optimization ..........................................................................58
Table 5-13 Feature Change List.........................................................................................59
Table 5-14 User Service Restriction for Special Scenario ..................................................63
Table 5-15 TWAMP client ..................................................................................................64
Table 5-16 Uplink carrier aggregation ................................................................................66
Table 5-17 Carrier Aggregation (DL 3CC, FDD+TDD) .......................................................70
Table 5-18 Cloud CA (distributed)I .....................................................................................72
Table 5-19 Support DL MIMO4*4 based on TM9 ...............................................................73
Table 5-20 Downlink 256QAM ...........................................................................................74
Table 5-21 Network assistant CRS-IC without ABS ...........................................................76

Table 5-22 Special consideration of selecting a target cell for a CA user for load balancing
.............................................................................................................................................78
Table 5-23 Dynamic authorization based on RB utilization of a cell ...................................79
Table 5-24 Qcell energy saving..........................................................................................80
Table 5-25 Ultra extended Cell Radius...............................................................................83
Table 5-26 DL Frequency offset pre-compensation............................................................84
Table 5-27 VoLTE in CA cell ..............................................................................................85
Table 5-28 Support Recovery for Voice Packet Loss .........................................................86
Table 5-29 A1 and A2 thresholds for voice/data distinguishing ..........................................88
Table 5-30 Inter-RAT user migration supported by Magic Radio ........................................89
Table 5-31 X2 self-establishment optimization ...................................................................90
Table 5-32 CA neighbor cell self-configuration ...................................................................93
Table 5-33 ANR Consider not adding neighbor cells with illegal PLMNs ............................95
Table 5-34 Downlink CA and 256QAM enabled simultaneously .........................................96
Table 5-35 DL single-carrier 4*4 MIMO and 256QAM ........................................................97
Table 5-36 A3 Not Being Deleted When B2 measurement is configured for Voice Quality
Based SRVCC....................................................................................................................100
Table 5-37 Concurrence of Voice Quality Based and Coverage Based SRVCC ..............101
Table 5-38 Time to trigger SRVCC can be configured .....................................................102
Table 5-39 Increase the demand for counter based on PDCP Discard Cause. ................103
Table 5-40 PDSCH scheduling RB is configurable for single direction within the standard
bandwidth ...........................................................................................................................106
Table 5-41 Single RB allocation for VoLTE UE ................................................................107
Table 5-42 CPU LOAD requires adding counters to determine the stage .........................108
Table 5-43 X2 Self-Establishment Between Two Shared eNodeBs with Different Primary
PLMNs ...............................................................................................................................109
Table 5-44 LTE and NB Sharing One Association............................................................110
Table 5-45 Auto-Adaption Congestion Control: AC Barring ..............................................112
Table 5-46 First Packet IP Delay Statistics Supported .....................................................115
Table 5-47 Downlink CA and Downlink 4*4MIMO ............................................................116
Table 5-48 Downlink CA and Downlink 4*4MIMO and 256QAM.......................................117

Table 5-49 UDC ...............................................................................................................119

Table 5-50 Total Cell Transmit Power Statistics (Maximum and Average Power) ............120
Table 5-51 Key Counter Statistics for Multiple PLMNs .....................................................122
Table 5-52 E-CID Positioning Supports Type 2 TA Measurement Reporting....................124
Table 5-53 Dynamic Broadcast Weights ..........................................................................126
Table 5-54 cheduling Evasion for SRLTE Terminal ..........................................................127
Table 5-55 Context Fetch.................................................................................................128
Table 5-56 eMBMS counting............................................................................................130
Table 5-57 Service Based PCC Dynamic Selection .........................................................131
Table 5-58 Flexible Scell configuration of multi-carriers ...................................................132
Table 5-59 up to three Coordinating Cells in CS ..............................................................134
Table 5-60 Flexible UE Handling Strategies Supported in Case of an S1 Link Failure .....136
Table 5-61 Supporting CSFB process optimization During VoLTE Conversation .............139
Table 5-62 To Prohibit eSRVCC before Alerting in VoLTE Call ........................................141
Table 5-63 eNodeB supports 512 groupIds for each S1 ...................................................142
Table 5-64 NB supported function list .................................................................................143
Table 6-1 solved GU defect list ........................................................................................198
Table 6-2 Solved Issues List ............................................................................................233
Table 6-3 VoLTE RTP packet loss ...................................................................................248
Table 6-4 Optical module alarms on multiple sites after version upgrade to V3.3.............249
Table 6-5 When an FDD LTE eNodeB is upgraded), the KPI counter increases greatly ..249
Table 6-6 Super cell outage on 15 eNodeBs after version upgrade due to "License limited"
...........................................................................................................................................250
Table 6-7 eSRVCC handover fails, causing abnormal UE release ...................................251
Table 6-8 Downlink retransmission interval is large in the VoLTE test..............................252
Table 6-9 In combination mode for the R8863 S2100, the “Referenced Signal Power of BP
Resource” of OMMB cannot be configured to 18.2 db. .......................................................253
Table 6-10 Specific UEs cannot access the network after upgrading from V3.20.50.20 P10
to V3.30.20.30 ....................................................................................................................254
Table 6-11 RRC request rejected Due to eNodeB admit failure .......................................255

Table 6-12 After the system is upgraded to V3.3.20 P40, the incoming handover failure rates
on S1 and X2 interfaces increase .......................................................................................256
Table 6-13 High dropped call rate due to the PERIOD_TA_MEAS option selected for the MR
task ....................................................................................................................................256
Table 6-14 Large number of messages indicating context modification failure due to other
causes after system upgrade to V3.3 .................................................................................258
Table 6-15 Scheduling according to DRX Enable when Cell Connect Reestablishment with
DRX is disabled ..................................................................................................................259
Table 6-16 CSFB failure ..................................................................................................259
Table 6-17 BPL1 board reset repeatedly due to more than 64 UTRAN neighbor cells after
SDR15 version upgrade .....................................................................................................260
Table 6-18 eNodeB KPI (downlink transmission bandwidth (megabit/s)) abnormal ..........261
Table 6-19 Five cells disconnected and having no msg1 .................................................262
Table 6-20 GL RRU having parameter configuration error alarms after system upgrade to
V4.15..................................................................................................................................262
Table 6-21 Secondary carrier RB insufficiency in CA handover .......................................263
Table 6-22 Probabilistic call failure due to UE not responding to Paging messages in
reestablishment scenarios for the CSFB test ......................................................................264
Table 6-23 Admission failure on eNodeBs with CA function .............................................265
Table 6-24 eNodeB using a temporary License file in default state for a moment after
system upgrade from V3.3 to V3.4 .....................................................................................266
Table 6-25 No downlink traffic after handover from a ZTE eNB to a Nokia eNB ...............266
Table 6-26 In six cells 4 ant mode，one of the cells on BPL1 setup fail ...........................267
Table 6-27 Activate the speedtest switch, UE executing speedtest preempts RB resources
...........................................................................................................................................268
Table 6-28 The self-defined CSFB failure times are found minus after upgrading from UR14
to UR15 ..............................................................................................................................269
Table 6-29 C373384345 Cat3 Average User Number did not change, Cat 6 was reduced
after upgrading to 4.15.10.30P30. ......................................................................................270
Table 6-30 UE fails to execute intra-frequency handover for SRVCC based on signal quality
...........................................................................................................................................270
Table 6-31 Signal quality based SRVCC has no protection mechanism during threshold
triggering ............................................................................................................................271

Table 6-32 When eNodeB upgrade to a new version, the CDT data does not contain CT
signal..................................................................................................................................272
Table 6-33 After FAST RETURN to the 1.8G LTE cell in CSFB procedure, UE handover to
higher 2.6 G PCELL frequency, and then UE can’t receive Modify EPS bearer context request
message from MME ...........................................................................................................273
Table 6-34 the load balance UE which has fast return to LTE cell after CSFB cannot receive
the S1 Modify EPS bearer context request message ..........................................................274
Table 6-35 RRC Release After an Initial Message is Sent to the New MME ....................275
Table 6-36 The eNodeB Name and Cell Name Is Abnormal in Performance Data Query 276
Table 6-37 Decrease of the LTE CSFB SR Indicator from 99.9% Before Upgrade to 99.4%
After Upgrade With a Deterioration Rate of 0.5% ...............................................................277
Table 6-38 Voices Not Heard Clearly in Some Cases When F7 Mobile Phones Call
Samsung Mobile Phones ....................................................................................................278
Table 6-39 Abnormal Value in the KPI Statistical Results of a Field Site ..........................279
Table 6-40 Increased UL IP Throughput After the eNodeB Upgraded From V3.2 to V3.3 in
the LTE Project...................................................................................................................279
Table 6-41 Deterioration of the E-RAB Call Drop Rate After Version Upgrade from
4.13.10.30P42 to 4.15.10.20P51 ........................................................................................280
Table 6-42 Active E-RAB Drop Rate Increase After Upgrading to V3.3 ............................281
Table 6-43 Serious Decrease in the CQI, Equivalent Throughput and 64QAM After the BPL0
Site Was Upgraded from V3.2 to V3.3 ................................................................................282
Table 6-44 Paging Loss in Sites with No Paging Congestion (Especially the BPN Board)
...........................................................................................................................................283
Table 6-45 Falsely High Statistics of the Number of RRC Users ......................................283
Table 6-46 Statistical Result of "C373505499 Greater Than P340440 .............................284
Table 6-47 eNodeB Failing to Select the Correct PLMN to Return an ACK Message After
Receiving RIMinformation During 2G RIM Information Exchange in the MOCN Shared
Network ..............................................................................................................................285
Table 6-48 No More Than Nine Blackcell Lists Related to Forbidden TAC .......................286
Table 6-49 Increased RRC Call Drop Rate After the Upgrade of an eNodeB ...................287
Table 6-50 Serious Uplink Packet Loss Rate in Random Distribution...............................288
Table 6-51 The Number of Intra-eNB Inter-Frequency Handovers is Significantly Decreased
After DRX Closed ...............................................................................................................289
Table 6-52 High VoLTE Call Drop Rate Due to Redirection .............................................290

Table 6-53 Deterioration of the RRC Call Drop Rate and E-RAB Call Drop Rate After
Upgrade to V3.30.20.21 .....................................................................................................291
Table 6-54 Intra-eNodeB Handover Failure (Inverted NAS Sequence) ............................292
Table 6-55 Decreased CN Traffic Due to S1 RESET .......................................................293
Table 6-56 After Version Upgrade, There Are Many Link Disconnections Due to the S1 Link
Error in A Few Sites, but the SCTP Link Is Disconnected Only Once .................................294
Table 6-57 BPN2 Board Operation Error..........................................................................295
Table 6-58 Total Number of Abnormal Releases of Eight QCI1s in Some Cells Is Smaller
Than the Value of "C373505300.........................................................................................296
Table 6-59 The eNodeB Sends an Empty Reconfiguration Message but the UE Does Not
Return an Assignment Complete Message, so the eNodeB Releases the UE Upon Timeout
...........................................................................................................................................297
Table 6-60 Baseband Reset Problem Due to a Software Operation Error in CA Sites along
the Subway ........................................................................................................................298
Table 6-61 Decreased CSFB Success Rate After the UTRAN ANR Switch Is Enabled ...299
Table 6-62 After the Customized Description Field in AISG Configuration Is Modified, the
AISG Communication Link Disconnection Alarm Is Reported During AISG Rescanning.....300
Table 6-63 Automatic Reset during RRU Operation .........................................................301
Table 6-64 Increased NI Noise After the R8882 S2100 B Is Upgraded to V4.15 ..............302
Table 6-65 Sudden Increase of the CC Board Load From 10% to 66% in an eNodeB .....303
Table 6-66 Low Rate in Indoor Distribution RRU Cascading Coverage and Is Recovered
After the Sampling Rate is Modified ....................................................................................304
Table 6-67 Abnormal Handover Indicator in Two Sites ....................................................305
Table 6-68 Clearance Time of Some History Alarms Earlier Than Occurrence Time .......306
Table 6-69 Failure to Query Physical Devices in Dynamic Management ..........................307
Table 6-70 Qcell pRRU Rack Number Cannot Exceed 216 .............................................308
Table 6-71 Sleeping Cell Problem in the India Idea LTE Project ......................................309
Table 6-72 Abnormal KPI Indicators Due to Errors with Counters C373930024 &
C373930025 .......................................................................................................................310
Table 6-73 After A Broken SCTP Link is Recovered, There Is No Transmission Power on
the RRU and Services are Interrupted; Services are Recovered After the PA is Shut Down
and Restarted .....................................................................................................................312
Table 6-74 Repeated Reset of the CC Board at a Site .....................................................313

Table 6-75 Average CPU Usage of the CC Board on the eNodeB Is Greater Than 100% and
Displayed As 3000% ..........................................................................................................314
Table 6-76 Frequent Disconnection of the OMC Link After FST+OMC+IPSec Configurations
Are Added on the UR15 eNodeB Version ...........................................................................315
Table 6-77 Supporting Automatic Update of the Summer Time and Summer Time Start/End
Time Format of Month-Week-Day.......................................................................................316
Table 6-78 Maximum Throughput (Mbps) of DL Received Data of the eNodeB
Exceeds1Gbps in Actual Statistics .....................................................................................317
Table 6-79 No Power on the RRU During Query ..............................................................318
Table 6-80 Repeated Printing of UDT Signaling Messages..............................................319
Table 6-81 UDT Decodes noncriticalextension in Error ....................................................320
Table 6-82 MTS Data Fail to Display IMSI on the EMS ....................................................321
Table 6-83 Time is Six Hours Later Than the Local Time After Northbound Trace Decoding
...........................................................................................................................................322
Table 6-84 High E-RAB Call Drop Rates in Top Sites ......................................................323
Table 6-85 Traffic of CA Terminals Lower Than Traffic of Non-CA Terminals in Speed Tests
...........................................................................................................................................324
Table 6-86 Increase of Prach Average NI by 30 dB or Above After UL Comp Deployment
...........................................................................................................................................325
Table 6-87 NI Is -120 In Case of Bypass and Is -70 In Case of Non-Bypass After
Tower-Mounted Amplifiers Are Added to the RRU ..............................................................325
Table 6-88 After BPN2 Replaces BPL1, the Minimum Power of one Cell Is Increased, the
Minimum Power of Another Cell Is Reduced, and the Power of 0 mW Occurs Before and After
Replacement ......................................................................................................................326
Table 6-89 Statistical Result of C373414597 (Average NI of Carrier(dBm)) Inconsistent With
the Average Value of PB-Level Statistics............................................................................327
Table 6-90 Low Speed of Far Points in CAs in the FDD+TDD Network ...........................328
Table 6-91 RTP packet loss due to large downlink scheduling intervals before handover 329
Table 6-92 Inaccurate average RSRP of the serving cell or target cell .............................330
Table 6-93 Lighting fault of Optical module for newly added R8861 .................................330
Table 6-94 Simultaneous report of GPS positioning alarms from FDD LTE eNodeBs failing
to position in different areas during several timing periods..................................................331
Table 6-95 Large changes to maximum NI and average NI of the PRACH after a version
upgrade to V3.3 ..................................................................................................................333

Table 6-96 RRU disconnections in some new LTE sites ..................................................333

Table 6-97 Large number of reestablishment requests caused by a sector reconfiguration
failure .................................................................................................................................334
Table 6-98 Data Output Existing in the Counter (Based on Blind Handover) when
Load/Measurement Based Load Balance is Enabled..........................................................335
Table 6-99 Deteriorated KPIs After a New License Is Loaded ..........................................337
Table 6-100 CellID reported as 65535 sometimes ...........................................................337
Table 6-101 Deteriorated E-RAB call drop rate after the Netmax-L is enabled .................338
Table 6-102 Some UEs are Released after Load Balancing Based on RRC User Access and
CA are Enabled at the Same Time .....................................................................................339
Table 6-103 Two sleep cells in a single eNodeB ..............................................................340
Table 6-104 Uplink Bler is High When Adding and Removing Second Carrier, Affecting UE
Uplink throughput ...............................................................................................................341
Table 6-105 UL throughput in PCC of CA UE continue to drop below 10M in intra-cell
handover process ...............................................................................................................346
Table 6-106 When NB-IOT is Enabled on LTE eNodeB, More than 60 Sites Reported
Blocking Alarms. 40 Sites Recovered itself, and More than a Dozen Need Manual Processing
...........................................................................................................................................347
Table 6-107 Software Runs abnormal in the CA Use Handover with SCC Scenario ........348
Table 6-108 Some of the sites the VoLTE calls are dropped when using Apple phone, and
the phone interface appeares “Call Failed” .........................................................................349
Table 6-109 VoLTE UE is Released after eNodeB Receiving the UE Context Modification
Request with the CSFB Indication ......................................................................................350
Table 6-110 BPN2 board resets and reports alarm “software runs abnormal” ..................351
Table 6-111 CSSR Indicators of the Whole Network are Descreased ..............................352
Table 6-112 In 3CC CA Test, Throughput is Reduced to Zero and Reestablishment Occurs
...........................................................................................................................................353
Table 6-113 KPI statistics of TA distribution are exception ...............................................354
Table 6-114 One or More Cells Scheduling Capacity Per TTI are Insufficient for BPN2 ...355
Table 6-115 P10 UE is Released Frequently after Accessing, SCC is not added and UE can
not Do Service in CA Test ..................................................................................................356
Table 6-116 Handover Prepareration Failure in MOCN Network Sharing Site ..................368

Table 6-117 E-RAB Drop Rate Deteriorated Significantly after Upgrade to V4.16.10.20P50
...........................................................................................................................................369
Table 6-118 LTE DL 64QAM Usage is Dropped after Upgrade to UR16 ..........................370
Table 6-119 The iphone Siri Service is Abnormal after TCP Proxy is Enabled .................371
Table 6-120 Cell RRC Number and ERAB Number are zero ...........................................372
Table 6-121 RRUs are Reset with the Reason "the watchdog resets"..............................373
Table 6-122 The HTTP Download Speed is Low After TCP ACK Split is Enabled ...........374
Table 6-123 QCELL LTE Sites Enter into "sleep" Causing Users Unable to Access and Zero
Cell Throughput ..................................................................................................................375
Table 6-124 The Number of Re-establishment Requests Due to "Other Reason" on the FDD
Sites is Increased Suddenly ...............................................................................................376
Table 5-124 Handover Preparation Failed when UE hands over from Normal eNodeB to
Sharing eNodeB .................................................................................................................377
Table 5-125 RRC setup success rate drops sharply because of Number of E-RAB Release
due to Uu interface Timeout increasing ..............................................................................378
Table 5-126 Records with a Cell ID of 65535 Exist in the Cell-level Counters' Statistics ..379
Table 5-127 After upgrade to V3.40.20.10P50, VOLTE call dropped rate increases. .......379
Table 5-128 After upgrade to V4.16.10.20P50, an abnormal FDD product process causes
the baseband board to reset ...............................................................................................381
Table 5-129 The FTP upload rate is low because of IPSec packets decrypting abnormal.
...........................................................................................................................................382
Table 5-147 Number of RRC Connection Users in Frequency 1.8G and 2.6G is unevenly
Distributed After the MR Inter-frequency Measurement is Enabled.....................................383
Table 5-148 Parts of pRRUs Have No power for 2.6G QCell Site ....................................384
Table 5-149 One Cell (CellID = 6) of A Site Setup Failure After Upgrading ......................385
Table 5-150 The AISG inventory information reported by the eNodeB is inaccurate ........386
Table 5-151 the call drop rate is deteriorated ...................................................................387
Table 5-152 E-RAB drop rate is increased .......................................................................388
Table 5-153 After one XGW on the network goes offline, some BS8922 have alarms: S1
GTP-U path unavailable (198094466) ................................................................................389
Table 5-154 the success rate of RRC Connection Setup is decreased ............................390
Table 8-1 Version package download restriction ..............................................................392

Table 8-2 Restriction on version package pre-activation, taking effect after activation
operation ............................................................................................................................392
Table 8-3 Activation effective, activation cancellation operations aiming at all version
packages ............................................................................................................................393
Table 8-4 Version package deletion restriction .................................................................394
Table 8-5 To configure Ultra Cell UL Enhancement cell, AI_TIMING of all cells must be 1
and cell radius must be ≤10KM ........................................................................................394
Table 8-6 Super-far cell restriction ...................................................................................394
Table 8-7 If ultra cell UL enhancement and ultra-cell Dl Power & HSDPA code multiplexing
functions change, all BPK boards will reset ........................................................................395
Table 8-8 CS Over HSPA function......................................................................................395
Table 8-9 In Hybrid GU configuration, there is an STSR cell that is built with RSU82 GUL9016,
RSU82 GUL1816 and other RRU, which is connected to BBU with a super-long optical fiber.
Supposed that the distance from RSU82 to BBU is L1, the distance from the RRU to BBU is
L2. A Restriction is that L2 shouldn’t be longer than L1 for more than 25Km ......................396
Table 8-10 1T RRU (R8881) optical rate restriction ............................................................397
Table 8-11 1T RRU (R8881, RSU60E, RSU40) only supports 22V high class of AISG and
NSBT .................................................................................................................................397
Table 8-12 HSSCCH code restriction .................................................................................398
Table 8-13 Ultra-cell Dl Power & HSDPA Code Multiplexing function restriction .................398
Table 8-14 Restriction on RRU if it is Connected to BS8912 U2100 ...................................399
Table 8-15 Configure One Detection Mode for Static Route Table .....................................399
Table 8-16 Restriction on the Number of Remote Racks ....................................................400
Table 8-17 FS5 Configuration Requirement at Background ................................................400
Table 8-18 Bearer Pre-configuration function only supports IP transmission, it neither
supports ATM+IP dual stack nor ATM transmission ...........................................................401
Table 8-19 Restriction on hybrid scenario while upgrading CCA to CCC ............................401
Table 8-20 CC0/CC2 not support IPV6 due to its chip limit ..............................................402
Table 8-21 Restriction on BPK_d configuration ..................................................................402
Table 8-22 Maximum 4 levels of cascading connection of 1T(R8881, RSU60E, R8861) and
old 1T RRU (RTR, RTR2, DTR, ADTR) ..............................................................................403
Table 8-23 Things to be noticed when RSU82 GUL1816 uses cross diversity and primary &
diversity detection...............................................................................................................403

Table 8-24 Things to be noticed when RSU82 GUL1816 starts manual frequency scanning
function via OMMB .............................................................................................................404
Table 8-25 In the situation that new 1T RU runs frequency scanning function and PA is
enabled, Tx frequency is not configured one. This may bring interference to non-configured
frequency point. ..................................................................................................................405
Table 8-26 During the process that new 1T RU runs frequency scanning function, manually
activating/deactivating PA operation should be avoided unless there is a special reason. ..405
Table 8-27 Number of cells and number of carriers supported by CC0/CC2 ....................406
Table 8-28 Restriction on cell entire frequency band scanning function ..............................406
Table 8-29 Restriction on air-interface soft synchronization function ..................................407
Table 8-30 Things to be noticed in UBPG3 configuration ...................................................407
Table 8-31 Restriction on smart power-on/off function ........................................................408
Table 8-32 Restriction on GU power-sharing function.........................................................408
Table 8-33 Restriction on DBB hotpatch loading ..............................................................409
Table 8-34 Restriction on local switch ..............................................................................409
Table 8-35 Restriction on BCCH changeover function .....................................................410
Table 8-36 Super NodeB not support IPV6 (IPOE1 not support IPV6) .............................410
Table 8-37 IPV6 OMCB channel not support IPV6 IN IPV6 ..............................................410
Table 8-38 Restriction on EVA function............................................................................411
Table 8-39 Restriction on GL power sharing .......................................................................411
Table 8-40 Restriction on UL adaptive filter .....................................................................411
Table 8-41 VAMOS capability limit ...................................................................................412
Table 8-42 In the configuration of single-UMTS RUs, the configured antenna unbalanced
alarm parameter (AntDetectorU) may be invalid .................................................................413
Table 8-43 UBPG0 does not support NCC extended channel ..........................................413
Table 8-44 Cross diversity is not supported in R8882/RSU82 UL hybrid scenario............414
Table 8-45 Cell deletion/addition due to the change of IC switch ........................................414
Table 8-46 If changing DC relation via OMMB, the corresponding cell may be deleted/added
...........................................................................................................................................415
Table 8-47 Constraints when both FS and BPN2 provide optical ports in GSM system ......415
Table 8-48 Constraints when CR0 is inserted to slot 4 .......................................................416

Table 8-49 A Group of Cascaded PBs with 10G Optical Port Can Support Up to UMTS UL/DL
20 IQ Channels ..................................................................................................................418
Table 8-50 QCELL System Does not Support 6G Optical Port ...........................................418
Table 8-51 The Bandwidth of UMTS Local Cell Supports 5M\4.8M\4.6M............................418
Table 8-52 CC0\CC2 Does not Support QCELL Configuration Scenario ............................419
Table 8-53 In QCELL Network scenario, LTE Baseband Resource Should be Configured to
be PB Mode .......................................................................................................................419
Table 8-54 Port 2 and 3 of PB1000 are Unavailable for the Moment, Not Supporting Relevant
Function .............................................................................................................................420
Table 8-55 The Range of PB Rack Number is 3-201; the Range of PRRU Rack Number is
3-201. 214-251 ...................................................................................................................420
Table 8-56 Support Up to 24 PBs, 192 PRRUs ..................................................................421
Table 8-57 Previous PB Reset Will Affect the PRRU, Connected to Next PB .....................421
Table 8-58 PRRU Does not Support the LTE FDD Cells From Different Baseband Process
Boards................................................................................................................................422
Table 8-59 QCELL System Supports Up to 4-level Cascading Connection and Total length of
4-level Optical Fiber should not Exceeds 10KM..................................................................422
Table 8-60 Previous PB1000 Boot Version Cannot Cooperate With EPLD Version C5 or
Above .................................................................................................................................423

1 About This Document

This file will clearly describe ZTE SDR Software ZXSDR NB_V4.16.10.20P83 Release Notes
(here after called “the notes”), covering newly added function, solved defect, verification
method and expected result of each modification. It will be taken as reference for field test and
software upgrade.
2 Brief Description
2.1 Release Notes

Table 2-1 Release upgrading information
Current software (patch) version Previous software (patch) version
NB_V4.16.10.20P83 NB_V4.16.10.20P81
2.2 Hardware
2.2.1 Change of Hardware Support
Null
2.2.2 Supportable Hardware Board

Refer to the attached Supportable specifications and board type.xls
2.3 Associated NEs’ Version
Table 2-2 Associated NEs’ Version
RNC V3.16.10.xx/ V4.16.10.xx
OMMB V12.16.50P50
iBSC iBSCV6.30.30xx
iBSCV6.50.30xx

LTE V3.40.20.10P83
2.4 NEs’ Version Compatibility
Table 2-3 RNC version compatibility
SDR Compatible Compatible Compatible OMMB

RNC iBSC
V4.16.10.20P83 V3.13.10.xx V6.20.71XX V12.16.50P50
V4.13.10.xx V6.30.10XX
V3.14.10.xx V6.50.10XX
V4.14.10.xx V6.30.20XX
V3.15.10.xx V6.50.20XX
V4.15.10.xx V6.30.30XX
V3.16.10.xx V6.50.30XX
V4.16.10.xx
2.5 Supported Upgrade Path

The table below lists the supported upgrades from earlier versions to this version.
Table 2-4 Supported upgrade path
Roadmap node Version details

V4.13.10.20PXX
V4.13.10.30PXX
UR13
V4.13.15.30PXX
V4.13.15.40PXX
V4.14.10.20PXX
UR14
V4.14.10.30PXX
V4.15.10.20PXX
UR15
V4.15.10.30PXX
UR16 V4.16.10.20PXX

2.6 3GPP Release (Optional)
Table 2-5 3GPP release
Mode Current version supported 3GPP Previous version supported 3GPP

release release
UMTS R11 R11
LTE/NB-IoT R12 R10
3 Change of Device Capacity and Performance

Index
Null
4 Change of Operation & Maintenance
4.1 Change of GU Parameters
Refer to annex 1, 4
4.2 Change of GU Alarms
Refer to annex 2
4.3 Change of GU Performance Index and Counter
Refer to annex 3

4.4 Change of LTE Parameters
Refer to AnnexLB1, AnnexLB2.
4.5 Change of LTE Alarms
Refer to AnnexLB3, AnnexLB4.
4.6 Change of LTE Performance Index and Counter
Refer to AnnexLB5.
4.7 NB Parameters
Refer to annex 5
4.8 NB Alarms
Refer to annex 6
4.9 NB Counter
Refer to annex 7

5 Change of Functions
5.1 Change of GU Function List
Table 5-1 New software function list
Function ID Function New Defa basic/ Mode Relativity Version

or ult optional with other
enhan state function NE
ced
NodeBV416100 NodeB Cold Patch New Supp Basic UMTS OMMB 4.16.10.20P20
10 Function ort
NodeBV416100 R8863 S9000 New Supp Basic UMTS OMMB 4.16.10.20P20

20 (B8A/A8A/B8N) ort
Supports 3.8M
NodeBV416100 Robort serving cell New Supp Basic UMTS OMMB 4.16.10.20P20
30 change ort
NodeBV416100 Optimization of HSDPA New Supp Basic UMTS OMMB 4.16.10.20P20

40 Signaling Packet ort
Scheduling
NodeBV416100 Performance New Supp Basic UMTS RNC 4.16.10.20P20
50 Improvement in the ort
Macrodiversity UL/DL
Unbalanced Area
NodeBV416100 Conservative SG New Supp Basic UMTS OMMB 4.16.10.20P20
60 assignment in ort
Multi-RAB Services
NodeBV416100 Adaptive HSDPA New Supp Basic UMTS OMMB 4.16.10.20P20
70 Retransmission ort
NodeBV416100 Dynamic HSDPA target New Supp Basic UMTS OMMB 4.16.10.20P20
80 bler ort
NodeBV416100 Voice shedding in weak New Supp Basic UMTS OMMB 4.16.10.20P20
90 signal ort
NodeBV416101 Voice error cancellation New Supp Basic UMTS OMMB 4.16.10.20P20
00 for special UE ort

NodeBV416101 EVA for RACH New Supp Basic UMTS OMMB 4.16.10.20P20
10 ort
NodeBV416101 R8892N New Supp Basic UMTS OMMB 4.16.10.20P20

20 M8090 supports NBI ort
C function.
NodeBV416101 Remove the constraint Optimi Supp Basic UMTS OMMB 4.16.10.20P20
30 of DC frequency zed ort
interval ≤ 5M at OMMB
side
NodeBV416101 HS-DPCCH Optimi Supp Basic UMTS OMMB 4.16.10.20P20
40 Demodulation zed ort
Optimization
NodeBV416101 HS-SCCH Power Optimi Supp Basic UMTS OMMB 4.16.10.20P20
50 Optimization zed ort
NodeBV416101 R8892N New Supp Basic UMTS OMMB 4.16.10.20P30

60 M8090 Supports ort
Adaptive NBIC
NodeBV416101 Single PB1120A New Supp Basic UL OMMB 4.16.10.20P30
70 Supports 6 LTE Cells ort
(dual UL mode)
NodeBV416101 Add TMA and RET New Supp Basic GULN OMMB 4.16.10.20P30
80 Information to ort
Northbound Asset
Report
NodeBV416101 Access distance New Supp Basic UMTS OMMB 4.16.10.20P50
90 compensation ort
5.2 New GU Function
5.2.1 NodeB Cold Patch Function
Table 5-2 NodeB cold patch function

NodeB cold patch function is defined as follow. When a part of

software changes, the operator can download a cold patch, then
reset the referred board.
Function
During parent-package download operation, an operator can tick
description
this option if he does not want the cold patch to be overlaid. By
doing this, if a NodeB site runs the cold patch, the cold batch will
not be automatically overlaid by the upgrading operation in a
batch.
Impact on device No
performance
Function No. No
Impact on network No
performance
Hardware No
dependence
Impact on the No
interface of an
associated network
element
Is it controlled by No
license?
Associated No
parameter
Associated counter No
Associated alarm No
and notification

Testbed verification:
At OMMB side, select a network element to upgrade its
specification package. This NE is running a cold patch. Before
downloading its parent package, select “overlay patch” option.
Then download operation will cause cold patch to be overlaid with
parent package. If not selecting the “overlay patch” option,
Verification method download operation will not cause cold patch to be overlaid. In
and pass criterion default, the “overlay patch” option is not selected.
Use EMS to upgrade multiple NEs. In default, “overlay patch”
option is not ticked. Dowload parent package will not cause the
cold patch to be overlaid at NodeB side.
Field verification:
Field verification adopts the same method as testbed verfication.
Impact on other No
functions
The upgrading interface at OMMB side provides an “overlay

patch” option. In default, cold patch is not overlaid. Tick this
Use guide
option, then upgrading parent package will cause cold patch to be
overlaid.
5.2.2 R8863 S9000 (B8A/A8A/B8N) Supports 3.8M
Table 5-3 R8863 S9000(B8A/A8A/B8N) supports 3.8M
Function
description R8863 S9000(B8A/A8A/B8N) supports 3.8M
Impact on device No
performance
Function No.
Impact on network
performance
Hardware R8863 S9000(B8A/A8A/B8N)
dependence
Impact on the No
interface of an
associated network
element

license?
Associated ULocalCell. rcvFilterBandwidth
parameter
Associated alarm No
and notification
Verification method TestBed verification:

and pass criterion Configure a 3.8M UMTS cell and make phone calls.
Impact on other No
functions
Use guide No
5.2.3 Robort serving cell change
Table 5-4 Robort serving cell change
Serving cell change may cause user CQI to fluctuate largely and
Function
description BLER to become high. This function will reduce BLER and
residual error blocks by adjusting CQI before serving cell change.
Impact on device No
performance
Function No.
performance
Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?
Associated NodeBFunctionReservePara. reserveParamter106

parameter

C372490160: Number of received NACK messages in total

Associated counter C372490161: Number of received ACK messages in total
C372490164: Numer of residual error blocks
Associated alarm No
and notification
Testbed verification:
Set NodeBFunctionReservePara.reserveParamter106 to be 3.
Let a test UE soft handover between two cells. Monitor the UE’s
scheduling information. Check whether BLER of this UE
Verification method decreases.
and pass criterion Field verification:
Select a site.Compare the performance before and after the
activatation.
Basic KPIs are not decreased. Both BLER and residual error
blocks show a decreasing thrend.
Impact on other No
functions
Set NodeBFunctionReservePara.reserveParamter 106 to be 3 to
Use guide
activate this function. Set it to be 0 to deactivate this function.
5.2.4 Optimization of HSDPA Signaling Packet Scheduling
Table 5-5 Optimization of HSDPA Signaling Packet Scheduling
Function With SRB Over HSPA configuration, signaling packet and data
description packet will be sent over one sub-frame simultaneously.
Impact on device No
performance
Function No.
Both signaling packet and data packet are scheduled at the same
Impact on network
time. This can increase air-interface scheduling efficiency. This
performance
function will not affect the basic KPIs.
Hardware No
dependence
Impact on the No
interface of an
associated network
element

license?
Associated NodeBFunctionReservePara.reserveParamter107
parameter
C372490407: how many times that data is buffered in dual Que
Associated counter
C372490408: how many times that data in dual Que is scheduled
Associated alarm No
and notification
TestBed verification:
With SRB Over HSPA, a test UE starts full-scheduling FTP
download service. After analyzing UE data, it is found that SRB
Verification method signaling Queue and service bearing Queue are scheduled over
and pass criterion one TTI.
Field verification:
Select a site. Compare the performance before and after the
activation.
Basic KPIs will not decrease.
Impact on other No
functions
Set NodeBFunctionReservePara.reserveParameter107 to be 1 to
Use guide
activate this function. Set it to be 0 to deactivate this function.
5.2.5 Performance Improvement in the Macrodiversity UL/DL Unbalanced Area
Table 5-6 Performance improvement in the macrodiversity UL/DL unbalanced area
In the macrodiversity unbalanced UL/DL scenario (e.g.

macro/micro-site network), this scheme consists of 6 parts:
Part1: In the macrodiversity scenario, the serving RL will not

Function report a “RL failure” message in the case of lost synchronization.
description
The serving RL will report a “RL restore” message even if it is not
restored.
Part2: In the slightly unbalanced scenario, the non-serving RL will

not transfer HS-DPCCH decoding information to RNC.

Part3: If the value of (Sir-SirTarget) of non-serving RL exceeds a

given threshold, the SirTarget of the serving RL will be adjusted
accordingly.
Part4: If a site doesn’t support the function of “inter NodeB
cooperative HSPA scheduling” or this function is not activated,
the SirTarget of the non-serving RL will be increased to a
maximum when the uplink Sir of serving RL is bad.
Part5: Different E-TFCI PO will be used according to different

unbalanced UL/DL levels.
Part6: Iur-based cooperative HSUPA scheduling
Note: part 4 and part 5 should be activated together.

Impact on device No
performance
Function No.
In Iur macrodiversity UL/DL unbalanced scenario, this function
Impact on network
may improve HSUPA throughput when the serving cell fails to
performance
demodulate SI and E-DPDCH.
Hardware BPK series boards, BPN series board
dependence
Impact on the Accordingly, RNC version should support this function.
interface of an
associated network
element
license?
 Parameters used in Part1-Part5:
OMMR:
URncFunction. coSchedulingUPASw
UIurLink.coHsupaSuppInd
Associated
URncFunction.HsdpcchHostIPv4
parameter
URncFunction.HsdpcchHostIPv6
UIubLink.HsdpcchIpDscp
URncFunction.HspaCoopIurHostIPv4
URncFunction.HspaCoopIurHostIPv6

UHspa.hsImBlPOAdjSwi
UExtCelInfoFDD.rEtfciPOImBlSwi
rEtfcNumTti10T1
rEtfcNumTti2T1
rEtfciTti10T1
rEtfciTti2T1
rEtrciPOTti10T1
rEtrciPOTti2T1
UHspa.edchHarqPOFddImBl
OMMB:
Hspa. interNodebCoUPASwitch
NodeBFunctionReservePara. reserveParamter85 bit1
NodeBFunctionReservePara. reserveParamter108
Hspa.imBalRecfgEtfciPOSwitch
 Parameters used in inter-IUR HSUPA cooperative
scheduling:
OMMR:
NSrvHsdpcchSwitch
HostIPV4OfHsdpcch/HostIPV6OfHsdpcch:ServiceIpAddress
OMMB:
HSPA.InterNodebCoDpaSwitch
NodeBFunctionReservePara85 bit1
NodeBFunctionReservePara108

 Parameter used in HSDPA cooperative scheduling:
OMMR:
NSrvHsdpcchSwitch
HostIPV4OfHsdpcch/HostIPV6OfHsdpcch:ServiceIpAddress
OMMB:
HSPA.InterNodebCoDpaSwitch
NodeBFunctionReservePara85 bit1
C372500171: HSUPA NonSrv Cooperative scheduled User
C372490162: Number of Received DTX – HSDPA
C372490391: Number of NonSrv Cooperative Scheduling ACKs
C372490392: Number of NonSrv Cooperative Scheduling
Associated counter
NACKs
C372490393: NonSrv Cooperative Scheduling Delay
307271: HSDPA Average Throughput per cell_ACK
307272: HSDPA Average Throughput per user_ACK
Associated alarm No
and notification
Create a macrodiversity unblanced UL/DL scenario and do the
following test.:
(part1) UE initiates a PS Call and runs a HSDPA FTP download

service in Cell1. Then, Cell2 is added in the active set. If the part
1 function is deactivated, the serving RL(Cell1) will report a “RL
Verification method
and pass criterion failure” message. If it is activated, the serving RL will not report a
“RL failure” message.
(part2) Adjust the test environment so that the UE stays in the

slightly unbalanced area. The UE runs an HSDPA FTP download
service. If the function of “inter NodeB cooperative HSUPA
scheduling” is activated, and the part 2 function is deactivated,

the non-serving RL will transfer HS-DPCCH decoding information

to RNC. However if the part 2 function is activated, the
non-serving RL will not transfer the HS-DPCCH decoding
information to RNC.
(part3) UE runs a HSDPA FTP download service. The function of

“inter NodeB cooperative HSDPA scheduling” is activated, and
downlink Ec/No of the non-serving RL is bad. In this situation, if
the part 3 funcion is activated, the value of (Sir-SirTarget) of the
non-serving RL will decrease
(part4 and part5) Activate the part 4 function and part 5 function
together. Deactivate the function of “inter NodeB cooperative
HSDPA scheduling”. UE makes a PS call and runs an HSUPA
FTP upload service. The uplink SirTarget of the non-serving RL
will be adjusted to its maximum. RNC will allocate different
E-TFCI PO according to different unbalanced levels.
(part6) In the scenario of Iur-based macrodiversity UL/DL

unbalanced area, the system fails to demodulate SI and
E-DPDCH, UE starts an HSUPA FTP upload service. In this
situation, the HSUPA throughput will be improved when the part 6
function is activated.
Field verification:
Select a macrodiversity site with unbalanced UL/DL signals
(including Iur). Activate all these functions and compare the
performance before and after activation.
The basic KPIs are not decreased. In the UL/DL unbalanced

area, a drive test result shows that these functions benefit
HSPA throughput
Impact on other No
functions
Use guide Refer to the related FG
5.2.6 Conservative SG assignment in Multi-RAB Services
Table 5-7 Conservative SG assignment in Multi-RAB Services

Function For CS+DPA/UPA multi-RAB service, HSUPA SG will be limited

description in order to give more power to CS service.
Impact on device No
performance
Function No.
Impact on network The voice quality for multi-RAB services is improved.

performance
Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?
parameter NodeBFunctionReservePara.reserveParamter118
Associated counter
Associated alarm No
and notification
Use two UEs to initiate CS call in a cell. Meanwhile, the calling UE
starts a HSUPA upload service. FTP upload rate decreases and
Verification method UE transmission power decreases.
and pass criterion
Field verification:
Select a site. Compare the performance before and after the
activation.
Basic KPIs will not be affected.
Impact on other No
functions
Use guide
5.2.7 Adaptive HSDPA Retransmission
Table 5-8 Adaptive HSDPA Retransmission

When UE downlink data packets are retransmitted, NodeB

re-allocates code and modulation mode to UE according to
Function
current CQI, code and power at retransmission time. Note that
description
during the retransmission process, code and modulation mode
are changed, but TBsize is not changed.
Impact on device No
performance
Function No.
Impact on network HSDPA throughtput is slightly improved. The counters associated
performance with QPSK\16QAM\64QAM will change slightly.
Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?
parameter
901388:HSDPA Average Throughput per Cell
901389:HSDPA Average Throughput per User
Associated counter 300912:HSDPA MAC-hs Retransmit Rate(%)
300911:HSDPA DL Retransmit Rate(RLC)(%)
901374:64QAM Ratio
Associated alarm No
and notification
Set NodeBFunctionReservePara.reserveParamter103 to be
Verification method
100000.
and pass criterion
HSDPA average throughput per user is slightly improved.
Impact on other No
functions
Set NodeBFunctionReservePara. reserveParameter 103 to be 100000
Use guide to activate this function.
Set it to be 0 to deactivate this function.

5.2.8 Dynamic HSDPA target bler
Table 5-9 Dynamic HSDPA target bler
According to the quality of downlink signal, NodeB automatically

Function adjusts BLER target. When CQI is stable, a smaller BLER target
description is used. However when CQI fluctuates widely, a bigger BLER
target is used.
Impact on device No
performance
Function No.
Impact on network HSDPA throughtput is slightly improved. User BLER, Mach-hs
performance retransmission rate and 64QAM ratio increase.
Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?
parameter
901374:64QAM Ratio
Associated alarm No
and notification
Verification method HSDPA average throughput per user increases. HSDPA
and pass criterion MAC-HS retransmission rate and 64QAM ratio increase.
This function brings obvious gain in drive test.
Impact on other No
functions
Use guide

5.2.9 Voice quality optimization in weak signal scenario
Table 5-10 Voice quality optimization in weak signal scenario
Function In the situation that UL signal quality is below a threshold, NodeB does
description not send voice packet to RNC to avoid unpleasant noise.
Impact on device No.
performance
Function No.
Impact on network CS UL BLER decreases. Other KPIs are not affected.
performance
Hardware No.
dependence
Impact on the No.

interface of an
associated network
element
Is it controlled by No.
license?
Associated NodeBFunctionReservePara. reserveParamter132 bit1
parameter
Associated counter No.
Associated alarm No.
and notification
Set bit1 of NodeBFunctionReservePara. reserveParamter132 to be 1.
Verification method
After activating this function, there is less unpleasant noise, CS UL BLER
and pass criterion
decreases.Other KPIs are not affected.
Impact on other No.
functions
Set bit1 of NodeBFunctionReservePara.reserveParamter132 to
be 1 to activate this function.
Use guide Set bit1 of NodeBFunctionReservePara.reserveParamter132 to
be 0 to deactivate this function.
This function is activated by default.

5.2.10 Voice error cancellation for special UE
Table 5-11 Voice error cancellation for special UE
In CS encryption mode,the duplicated cipher voice packet from special

Function
UE,such as UE with SUMSUNG chipset, will make upleasant noise.With
description
this function activated,this kind of unpleasant noise will be ignored.
performance
Function No.
performance
Hardware No.
dependence
Impact on the No.
interface of an
associated network
element
license?
Associated NodeBFunctionReservePara. reserveParamter132 bit0
parameter
and notification
Encryption algorithm is activated.
Verification method Get a Samsung handset and initiate CS + PS service. Some noise will be
and pass criterion heared during the calling period.
No noise is heard.
Impact on other No.
functions
be 1 to activate this function.
Use guide
be 0 to deactivate this function

5.2.11 EVA for RACH
Table 5-12 EVA for RACH
Function Applying EVA method to RACH packet will improve RACH BLER.
description
performance
Function No.
Impact on network After activating EVA for RACH function, RACH BLER decreases. Other
performance KPIs are not affected.
Hardware No.
dependence
Impact on the No.

interface of an
associated network
element
license?
parameter
C372480185:Number of correct EVA packets in RACH
Associated counter C372480186:Total Number of Error Blocks in RACH
300866:UL Bler for RACH(%)
and notification
Verification method Set NodeBFunctionReservePara. reserveParamter99 to be 1.

and pass criterion RACH BLER decreases.
Impact on other No.
functions
Set NodeBFunctionReservePara. reserveParamter99 to be 1 to activate
this function.
Use guide
Set NodeBFunctionReservePara. reserveParamter99 to be 0 to
deactivate this function.

5.2.12 R8892N M8090 supports NBIC function
Table 5-13 R8892N M8090 supports NBIC function
Function R8892N M8090 supports NBIC function..

description
performance
Function No.
If in-band narrow band interference signal exists in a UMTS
Impact on network
cell, activating this function brings two benefits:the cell’s RTWP
performance
decreases and uplink receiving performance is improved.
Hardware R8892N M8090 (BAA/BAE)
dependence
Impact on the No.
interface of an
associated network
element
license?
Associated ULocalCell.enableNBIC
parameter
and notification
In the situation that narrow band interference signal exists in a
Verification method
UMTS cell, activate NBIC function. The cell’s RTWP decreases and
and pass criterion
UPA throughput increases..
Impact on other No.
functions
Use guide No
5.2.13 R8892N M8090 Supports Adaptive NBIC
Table 5-13 R8892N M8090 Supports Adaptive NBIC

Function
R8892N M8090 supports adaptive NBIC
description
Impact on device
No
performance
Function No.
After activating this function, the system can automatically
check whether there is in-band interference in a UMTS cell. If
Impact on network yes, the system automatically activates NBIC; otherwise,
performance NBIC is deactivated. After activating NBIC, interference signal
can be suppressed, finally cell RTWP decreases and UL
receiving performance is improved.
Hardware
R8892N M8090 (BAA/BAE)
dependence
Impact on the
interface of an
No
associated network
element
Is it controlled by
No
license?
Associated
ULocalCell.enableNBIC
parameter
Associated alarm
No
and notification
Activate adaptive NBIC function. When there is interference
signal, NBIC is automatically activated. Then RTWP
Verification method decreases and UPA throughput is improved. However, when
and pass criterion there is no interference signal, NBIC function is automatically
deactivated. In this case, RTWP and UPA throughput are not
affected.
Impact on other
No
functions
Use guide No
5.2.14 Single PB1120A Supports 6 LTE Cells (dual UL mode)
Table 5-13 Single PB1120A Supports 6 LTE Cells (dual UL mode)

Function Single PB1120A supports 6 LTE cells (dual UL mode)

description
Impact on device
performance
Function No. No
Impact on network The number of LTE or UMTS cells is affected.

performance
Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?
Associated No
parameter
Associated alarm No
and notification
Verification method:
PB1120A is configured to operate in GUL_6FD (IQ
Compressed) mode. Synchronize data configuration in
Verification method entire-table mode.
and pass criterion Passing criterion:
Single PB1120A is configured with 6 LTE cells and 10 UMTS
cells. Cell status is normal, UEs can be accessed and services
are normal.
Impact on other No
functions

1. PB1120A is configured to operate in QCell GUL Mode,

supporting 4L+20U. OMMB has a constraint on configuration –
not allowing more than 4L or 20U.
2. PB1120A is configured to operate in GUL_6FD (IQ
Compressed) mode, supporting 6L+10U. OMMB allows the
configuration of more than 10U. But PB1120A receives an IQ
configuration failure message.
Use guide
3. If several PB1120A boards are cascaded to the same FS
optical port, they must keep the same configuration mode.
4. If the configuration of PB1120A is changed from
QCell GUL mode to GUL_6FD (IQ Compressed) mode,
V4.16.10.20P30 or above version requires entire-table
synchronization to activate the configuration; however
V4.16.20 supports incremental synchronization mode.
5.2.15 Add TMA and RET Information to Northbound Asset Report
Table 5-17 Add TMA and RET information to Northbound asset report
Product model is added to the AISG asset report. This product model
Function
description can be obtained by viewing device information. In the asset information
structure, product model is saved in acVendorUnitTypeNumber.
Impact on device No
performance
Function No. No
performance
Hardware TMA, RET
dependence
Impact on the No
interface of an
associated network
element
license?
Associated No
parameter

Associated alarm No
and notification
OMMB:
Connect and configure TMA/RET. Then click Dynamic Management -->
View Device Information to view product model.
Execute MML command: (sub-network X, network element Y)
SET INVENTORYUNIT:MOI="SubNetwork=X,MEID=Y",INVENTORYTY
PE=1;
If the command is successful, it returns with generated file path (relative
path to OMMB server). Log in to OMMB server and get the file:
Verification method HW-b.CSV. View the value of vendorUnitTypeNumber of the
and pass criterion corresponding AISG asset. Here the product model should be the same
as that obtained by viewing product model.
EMS:
Connect and configure TMA/RET. Then click Dynamic Management
-->Vie Device Information to view product model.
Wait for half an hour. Open Fixed Asset Management interface to view
asset information. Here the VendorUnitTypeNumber field should record
the same product model as that obtained by viewing product model.
Impact on other No
functions
Asset information contains RET and TMA information. Each SN is
Use guide
associated to one record.
5.2.16 Access distance compensation
Table 5-18 Access distance compensation

Active devices (e.g. repeaters, trunk amplifiers) are used in

some special cells. These active devices generate additional
delay difference. Because of the additional delay difference,
cell coverage area is shrunk. This brings a problem - far-end
Function UEs cannot be accessed to the cells.
description This feature is introduced to solve the accessing problem. If an
antenna system contains active devices (e.g. repeaters) and it
has additional delay difference problem, this feature can be
activated to make access distance compensation.
Impact on device No
performance
Function No. No
Impact on network Cell coverage is kept within a normal range. KPIs are restored
performance to normal values.
Hardware BPN2 series boards

dependence
Impact on the No
interface of an
associated network
element
license?
Associated UlocalCell.2msGain
parameter
Associated alarm No
and notification

Configure a local cell parameter, named UlocalCell.2msGain, at
OMMB side. Set UlocalCell.2msGain to a value in the range of
0-255. This parameter is in a unit of 500m, where 255 means
extending 127.5Km coverage distance. Note that there is a
special case when the value is 0 or 1. In this case, it means not
extending coverage distance.
For example, in a 10km radius cell, set UlocalCell.2msGain to
10, it means extending 5Km coverage distance. After activating
this feature, the system can make 5Km distance compensation
Verification method against additional delay difference caused by active devices in
and pass criterion the cell. By doing this, the cell coverage is kept within a normal
range.
Outfield verification:
Configure a local cell parameter,
namedUlocalCell.2msGain, at OMMB side. Set
UlocalCell.2msGain to a value in the range of 0-255.
After activating this feature, the system can make
compensation against additional delay difference caused by
active devices in the cell. By doing this, the cell coverage is
kept within a normal range.
Impact on other No
functions
Use guide
5.3 Enhanced and Optimization GU Function
5.3.1 Remove the Constraint of DC Frequency Interval ≤ 5M at OMMB Side
Table 5-10 Remove the constraint of DC frequency interval ≤ 5M at OMMB side
As GSM\UMTS\LTE hybrid scenario is widely seen, there is a

Function requirement to flexibly configure center frequency in DC cell.
description Thus, the DC\MC\DB frequency interval constraint must be
removed from OMMB.

Impact on device No
performance
Function No.
performance
Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?
Associated No
parameter
Associated alarm No
and notification
1. At OMMB side, set two cells to work as a DC cell, whose center
frequency interval is less than 5M.
Verification method 2. At RNC side, configure the same DC relation with OMMB .
and pass criterion Then cellsetup successfully.
3. When DC UEs access to the system, service scheduling is
normal.
Impact on other No
functions
At OMMB side, set two cells to work as a DC cell. Configure
Use guide
different DC frequency interval.
5.3.2 HS-DPCCH Demodulation Optimization
Table 5-11 HS-DPCCH demodulation optimization
According to the quality of UL signal, the system automatically

Function
adjusts HS-DPCCH demodulation threshold to improve HSDPA
description
user experience.

Impact on device No
performance
Function No.
Impact on network DTX ratio increases; RLC retransmission rate decreases.
performance
Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?
Associated NodeBFunctionReservePara. reserveParamter 14
parameter
901397:Ratio of HSDPA DTX
Associated alarm No
and notification
Set NodeBFunctionReservePara.reserveParamter 14 to be 2.
Verification method After activating this function, HSDPA MAC-HS retransmission
and pass criterion rate slightly increases, HSDPA RLC retransmission rate
decreases, HSDPA DTX ratio slightly increases.
Impact on other No
functions
Use guide
5.3.3 HS-SCCH Power Optimization
Table 5-12 HS-SCCH power optimization
During HS-SCCH power adjustment process, HSDPA scheduling

Function
time is considered to reduce the total number of TTIs when single
description
HS-SCCH power reaches a peak.

Impact on device No
performance
Function No. No
performance
Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?
parameter
C372490267: Total number of TTIs when single HS-SCCH power
Associated counter
reaches a peak
Associated alarm No
and notification
Verification method Set NodeBFunctionReservePara. reserveParamter120 to be 5.
and pass criterion C372490267decreases.
Impact on other No
functions
Set reserve parameter 120 to be 5 to activate this function.
Use guide
Set it to be 0 to deactivate this function.
5.4 LTE Impacted Feature List
Table 5-13 Feature Change List
Feature ID Function New Default Mode Relati Version

or state vity
enhan with
ced other
NE
V4.16.10.20(
ZLF31-06-017 User Service Restriction new closed LTE OMMB V3.40.20.10)

for Special Scenario
V4.16.10.20(
ZLF32-06-008 TWAMP client new closed LTE OMMB V3.40.20.10)
Carrier Aggregation(UL V4.16.10.20(
ZLF34-00-016 2CC) new closed LTE OMMB V3.40.20.10)
Carrier Aggregation(DL V4.16.10.20(

ZLF34-00-049 3CC, FDD+TDD) new closed LTE OMMB V3.40.20.10)
V4.16.10.20(
ZLF34-00-051 Cloud CA (distributed) new closed LTE OMMB V3.40.20.10)
TM9-based DL V4.16.10.20(
ZLF34-00-033 4-antenna MIMO new closed LTE OMMB V3.40.20.10)
V4.16.10.20(
ZLF34-00-031 Downlink 256QAM new closed LTE OMMB V3.40.20.10)
Netwok assistant V4.16.10.20(
ZLF34-00-057 CRS-IC without ABS new closed LTE OMMB V3.40.20.10)
CA User Experience V4.16.10.20(

Aware Intra-LTE Load V3.40.20.10)
ZLF31-08-013 Balancing new closed LTE OMMB
Dynamic authorization V4.16.10.20(
based on RB utilization V3.40.20.10)
of a cell new closed LTE OMMB
V4.16.10.20(
N/A Qcell energy saving new closed LTE OMMB V3.40.20.10)
Ultra-extended cell V4.16.10.20(
ZLF31-04-003 radius new closed LTE OMMB V3.40.20.10)
DL Frequency offset V4.16.10.20(

ZLF31-13-060 pre-compensation new closed LTE OMMB V3.40.20.10)
V4.16.10.20(
N/A VoLTE in CA cell new support LTE None V3.40.20.10)
Support Recovery for V4.16.10.20(
ZLF31-13-050 Voice Packet Loss new closed LTE OMMB V3.40.20.10)
A1 and A2 thresholds for V4.16.10.20(

ZLF31-07-035 voice/data V3.40.20.10)
distinguishment new support LTE None
Inter-RAT user migration V4.16.10.20(

supported by Magic V3.40.20.10)
Radio new closed LTE OMMB

ZLF31-06-011 enhan V4.16.10.20(

Context Fetch ced closed LTE OMMB V3.40.20.10)
X2 self-establishment V4.16.10.20(
optimization new closed LTE OMMB V3.40.20.10)
CA neighbor cell V4.16.10.20(

self-configuration new closed LTE OMMB V3.40.20.10)
ANR consider not V4.16.10.20(

adding neighbor cells V3.40.20.10)
ZLF33-01-032 with illegal PLMNs new closed LTE OMMB
Downlink CA and V4.16.10.20(

256QAM enabled V3.40.20.10)
simultaneously new closed LTE OMMB
DL single-carrier 4*4 V4.16.10.20(

MIMO and 256QAM new closed LTE OMMB V3.40.20.10)
A3 Not Being Deleted V4.16.10.20(

When B2 measurement V3.40.20.10)
is configured for Voice
Quality Based SRVCC new support LTE None
Concurrence of Voice V4.16.10.20(
Quality Based and V3.40.20.10)
Coverage Based
SRVCC new support LTE None
Time to trigger SRVCC V4.16.10.20(
can be configured new support LTE None V3.40.20.10)
Increase the demand for V4.16.10.20(

counter based on PDCP V3.40.20.10)
Discard Cause. new closed LTE OMMB
PDSCH scheduling RB V4.16.10.20(
is configurable for single V3.40.20.10)
direction within the
standard bandwidth new closed LTE OMMB
Single RB allocation for V4.16.10.20(

VoLTE UE new closed LTE OMMB V3.40.20.10)
CPU LOAD requires V4.16.10.20(

adding counters to V3.40.20.10)
determine the stage new support LTE None
X2 Self-Establishment V4.16.10.20
Between Two Shared new support LTE OMMB P10(V3.40.2

eNodeBs with Different 0.10P10)

Primary PLMNs
V4.16.10.20
LTE and NB Sharing P10(V3.40.2
One Association new support LTE OMMB 0.10P10)
Auto-Adaption V4.16.10.20
Congestion Control: AC P10(V3.40.2
Barring new closed LTE OMMB 0.10P10)
V4.16.10.20
First Packet IP Delay P10(V3.40.2
Statistics Supported new support LTE OMMB 0.10P10)
V4.16.10.20
Downlink CA and P10(V3.40.2
Downlink 4*4MIMO new support LTE OMMB 0.10P10)
Downlink CA and V4.16.10.20
Downlink 4*4MIMO and P10(V3.40.2
256QAM new support LTE OMMB 0.10P10)
Total Cell Transmit V4.16.10.20

Power Statistics P10(V3.40.2
MktR-FP-0945 (Maximum and Average 0.10P10)
70 Power) new closed LTE OMMB
V4.16.10.20
MktR-FP-0930 Key Counter Statistics P10(V3.40.2
76 for Multiple PLMNs new closed LTE OMMB 0.10P10)
E-CID Positioning V4.16.10.20
MktR-FP-0290 Supports Type 2 TA P10(V3.40.2
670 Measurement Reporting new closed LTE OMMB 0.10P10)
V4.16.10.20
enhan P10(V3.40.2
ZLF31-05-016 eMBMS counting ced closed LTE OMMB 0.10P10)
V4.16.10.20
Service Based PCC enhan P10(V3.40.2
ZLF34-00-056 Dynamic Selection ced closed LTE OMMB 0.10P10)
V4.16.10.20
P10(V3.40.2
ZLF31-10-010 UDC new closed LTE OMMB 0.10P10)
Flexible Scell V4.16.10.20
configuration of enhan P10(V3.40.2
ZLF34-00-036 multi-carriers ced closed LTE OMMB 0.10P10)

V4.16.10.20
ZLF34-00-003 Up to Three enhan P10(V3.40.2
ZLF34-00-024 Coordinating Cells in CS ced support LTE OMMB 0.10P10)
Flexible UE Handling V4.16.10.20
Strategies Supported in P10(V3.40.2
Case of an S1 Link enhan 0.10P10)
Failure ced closed LTE OMMB
Supporting CSFB
process optimization V4.16.10.20P
During VoLTE enhan 20(V3.40.20.
Conversation ced closed LTE OMMB 10P20)
To Prohibit eSRVCC V4.16.10.20P
before Alerting in VoLTE enhan 40(V3.40.20.
Call ced support LTE OMMB 10P40)
V4.16.10.20P
eNodeB supports 512 enhan 40(V3.40.20.
groupIds for each S1 ced support LTE OMMB 10P40)
To Prohibit eSRVCC V4.16.10.20P
before Alerting in VoLTE enhan 60(V3.40.20.
Call ced support LTE OMMB 10P60)
V4.16.10.20P
eNodeB supports 512 enhan 60(V3.40.20.
groupIds for each S1 ced support LTE OMMB 10P60)
5.5 LTE New Features Description
5.5.1 User Service Restriction for Special Scenario
Table 5-14 User Service Restriction for Special Scenario
Feature Name User Service Restriction for Special Scenario

Feature UE data limit based on timing advance measurement: An eNodeB
Description can determine whether a UE is out of the specified coverage area in
accordance with the Timing Advance (TA) value.
The eNodeB can forcedly release the UE service after determining

that the UE is out of the specified coverage area.

Feature No. ZLF31-06-017
Impact on None
Equipment
Performance
Impact on Network Abnormal release rate of RRC connection
Performance Abnormal release rate of E-RAB connection
Hardware BPN, BPL
Dependency
License Control Yes, LTE-FDD_ENB_F022
Related Parameter EUtranCellFDD.taLimitedReleaseSwch
ServiceMAC.taMaxThr
Related Counter C373200158:Number of RRC Connection Release due to TA
exceed
C374067458:Number of E-RAB Release by ENODEB due to TA
exceed
Related Alarm None
Verification Method Verification method:
and Pass Criterion 1. Set Limited Switch to “Open”,
2. Set ServiceMAC.taMaxThr to 0, and connect the UE to the
network.
Pass criterion:
1. The UE service is triggered to be released due to TA exceeding
the limit.
Impact on Other None

Features
Note None
5.5.2 TWAMP Client
Table 5-15 TWAMP client
Feature Name TWAMP client

Feature The Two-Way Active Measurement Protocol (TWAMP) defines a
Description method for measuring IP performance (delay, jitter, and packet loss)

between any two devices that support this standard in a network.

TWAMP defines two groups of protocols. One group of protocols,
which are called control protocols, is used for setting up
performance measurement sessions and they are implemented
through collaboration between two logical entities: a client and a
server. The other group of protocols is used for test data sending
and receiving. And they are implemented through collaboration
between two logical entities: a session-sender and a
session-reflector.
The eNodeB acts as a TWAMP client, and initiates the
measurement of detection delay, jitter and packet loss rate.
Impact on None
Equipment
Performance
Impact on Network None
Performance
Hardware None
Dependency
License Control None
Related Parameter TwampClient
Related Counter C370310000 Total number of TWAMP detect packets transmitted
C370310001 Total number of TWAMP detect packets received
C370310002 Total transmission delay in TWAMP detect
C370310003 Total transmission Jitter in TWAMP detect
Related Alarm None
and Pass Criterion 1. Configure the TWAMP server on another device.
2. Configure the TWAMP client on the eNodeB
Pass criterion:
1. The eNodeB reports related KPIs 15 minutes later.

Features
Note None

5.5.3 Carrier Aggregation(UL 2CC)
Table 5-16 Uplink carrier aggregation
Feature Name Uplink carrier aggregation
Feature Uplink Carrier Aggregation (CA) is the function of increasing the

Description bandwidth through the aggregation of multiple carriers in order to
increasing the peak rate of a single user. Only supports only FDD,
Taking the aggregation of two carriers as an example, the uplink
transmission rate can be improved by combining two LTE
Component Carriers (CCs) together for the UE service to achieve
the maximum transmission bandwidth of 40MHz. The carriers of a
CA can be intra-band contiguous, intra-band uncontiguous, or two
inter-band component carriers.
Impact on None
Equipment
Performance
Impact on Network The uplink peak rate of a single user and system throughput are
Performance greatly improved.
Hardware BPL1, BPN0，BPN2, FS, CR0, and RRU

Dependency
License Control Yes, SDR_F025_L
Related GlobleSwitchInformation.fairSchdSwch
Parameter CarrierAggregatin.pcellPRBRatioActThrUl
CarrierAggregatin.scellPRBRatioActThrUl
CarrierAggregatin.crossCAScheSwch
CarrierAggregatin.pcellPRBRatioDeActThrUl
CarrierAggregatin.scellPRBRatioDeActThrUl
CarrierAggregatin.sccMcsEDeactThr
CarrierAggregatin.caSccActSinrThrUl
CarrierAggregatin.caSccDeactSinrThrUl
CarrierAggregatin.deactCATimer
CarrierAggregatin.scellActBuSizeThdUL
CarrierAggregatin.scellActBufDelayThdUL
CarrierAggregatin.caSchdSizeDeActThrUL
CarrierAggregatin.caSccActGbrThrUl

Related Counter KPI No Kpi name

C374241900 MCS0 PCell uses up RB number
C374241934 PCell cell uplink initial TB block error number
C374241935 PCell cell uplink initial total number of TB blocks
C374241938 SCell cell uplink initial TB block error number
C374241939 SCell cell uplink initial total number of TB blocks
C374241940 The number of the largest cross site UE
C374241941 The average number of - UE
C374241942 MCS0 SCell uses up RB number


C374210750 SCell uplink CA maximum number of users
C373343897 Cell CA to activate the user uplink PDCP high total
throughput
C373343898 Cell CA to activate the user uplink PDCP total
throughput is low
C373343899 Cell CA to activate the user uplink PDCP data
transmission total length
C373384352 Maximum number of users with CA capability
C373384356 Maximum CA enable user number
C373384367 Average number of auxiliary carrier
C373384376 CA scenario RRC connect the maximum number of

users
C373384377 Average number of instances of RRC connections in
CA scenarios
C373384382 Average number of users with CA capability
C373384384 Maximum CA enable user number
C373384385 Uplink average CA enable user number
C373384391 PCell average configuration uplink CA 2CC user
number
C373384392 PCell maximum configuration uplink CA 2CC user
number
C373384393 PCell average number of active CA users on the
uplink
C373384394 PCell maximum activation up the number of CA users
C373384395 PCell to activate the uplink CA average 2CC user
number
C373384396 PCell maximum activation upward CA 2CC user
number
C373384397 SCell uplink CA activation average number of users
C373384398 SCell uplink CA activation maximum number of users
C373384399 SCell uplink CA average number of users
C373596956 Borrowing PDSCH PRB (DTCH) Scell number
C373596957 Borrowing PDSCH PRB Scell number
C373596958 Activate Scell execution times
C373596959 Activate Scell success
C373596960 To activate the Scell execution times
C373596961 To activate Scell success
C373597001 SCell to activate the number of hidden type to activate
the timer timeout
C373597002 SCell to activate the number of non sent to activate
the MACCE (do not include implicit to activate)
C373597023 UE SCC uplink scheduling occupies RB number
C373597024 UE TB uplink scheduling SCC number
C373597025 UE PCC uplink scheduling occupies RB number
C373597026 UE TB uplink scheduling PCC number
C373597027 UE SCC uplink scheduling data
C373597028 UE PCC uplink scheduling data
C373597029 Ascending activation Scell request
C373597030 Uplink to activate Scell request times
C373597085 UE PCC uplink scheduling
C373597087 CA activated UE uplink scheduling takes RB number
C373597089 CA activates UE uplink scheduling

C373597091 CA to borrow the total number of PUSCH PRB SCell

C373597092 CA when the total number of PUSCH borrowed by
PRB PCell
C373220662 SCell try to add the number of blind
C373220663 Blind add Scell success
C373220664 Secondary cell handover attempt
C373220665 Secondary cell switch success
C373220667 UE because SPID limits the number of CA does not
enable
C373220668 Add SCell UL to try the number of times
C373220669 Add Scell UL success
C373220670 Delete SCell UL attempt times
C373220671 Delete Scell UL success
Related Alarm None
Verification Verification method:

Method and Pass 1. Configure FDD two cells to be of the uplink and downlink CA
Criterion collaboration type, set the system bandwidth to 20MHz + 20MHz,
and do uplink service after the UE is accessed.
Pass criterion:
When the two cells have the same configuration, access at the near
point. After the UE doing uplink service (UDP or FTP), the traffic is
over 1.8 times higher than that of the single carrier.

Features
Note 1. Aggregation of carriers of different versions is not supported.

2. Multi-TA is not supported.
3. Simultaneous PUCCH and PUSCH transmission is not
supported.
4. Cross-carrier scheduling is not supported.
5. Type2 EXT-PHR(extended PHR) is not supported.
5.5.4 Carrier Aggregation (DL 3CC, FDD+TDD)
Table 5-17 Carrier Aggregation (DL 3CC, FDD+TDD)
Feature Name Carrier Aggregation (DL 3CC, FDD+TDD)

Feature In network deployment, if there are no idle frequency bands in the

Description same wireless mode to form a CA, idle frequency bands in different
wireless modes can be selected to form a CA to provide services for
UEs. This version supports DL FDD+TDD three-carrier aggregation.
Impact on None
Equipment
Performance

Performance
Hardware BPL1, BPN0, BPN2, FS5C, and CR0

Dependency
Related Parameter None
Related Counter C374281118: SCELL Number of Successfully transferred DL MAC

TB for SCell which PCell of UE is another frame structure
C374281119: Number of Successfully transferred UL MAC TBSize
for SCell which PCell of UE is another frame structure
C374281120: Number of UL RB for SCell which PCell of UE is
another frame structure
Related Alarm None

Method and Pass 1. Make a UE supporting FDD+TDD 3CC CA access the network
Criterion and do the DL full-buffer UDP service test.
2. Make the UE supporting FDD+TDD 3CC CA access the network,
and increase or decrease attenuation.
3. Modify the transmission mode, make the UE supporting
FDD+TDD 3CC CA access the network and do the DL full-buffer
UDP service test.
Pass criterion:
1. The traffic at the near point can reach the peak throughput.
2. When the attenuation is increased or decreased to certain
threshold, event A2 is triggered to delete secondary carriers or
event A4 is triggered to add secondary carriers.

3. The traffic at the near point can reach peak throughput

Features
Note None
5.5.5 Cloud CA (distributed)
Table 5-18 Cloud CA (distributed)I
Feature Name Cloud CA (distributed)
Feature Cloud CA (distributed) refers to the aggregation of multiple CCs on

Description difference BBUs, aiming to provide service for UEs, which will
achieve the flexible deployment carrier aggregation.
Impact on None
Equipment
Performance

Performance
Hardware BPL1, BPN0, BPN2, FS5C, and CR0

Dependency
Related Parameter ENBFunctionFDD.crossEnbDelayThrsh

GlobleSwitchInformation.crossEnbDelaySwch
CarrierAggregatin.caCrossBbuMaxRBNum
Related Counter None
Related Alarm None

Method and Pass 1. Set the inter-eNodeB delay time to 0-4 ms, do the DL full-buffer
Criterion UDP test after the CA UE accesses the network.
2. Modify the delay time to be larger than 4 ms, and do the DL
full-buffer UDP test after the CA UE accesses the network.
3. Modify the inter-eNodeBdelay time from over 4ms to less than 4
ms, and do the DL full-buffer UDP test.

Pass criterion:
1. UEs can be configured with SCCs properly. In the scenario of
single UE, if the delay time is 0−0.2 ms, the number of scheduled
packets for SCC per second is 1000. If the delay time is 0.2−1 ms,
the number of scheduled packets for SCC per second is 720; if the
delay time is 1−2 ms, the number of scheduled packets for SCC per
second is 570. If the delay time is 2−3 ms, the number of scheduled
packets for SCC per second is 470. If the delay time is 3−4 ms, the
number of scheduled packets for SCC per second is 400.
2. For a UE with configured SCCs, the SCCs are deleted. For a
newly attached UE, no SCC is configured. The throughput of the
primary carrier satisfies the expected result.
3. No SCC is added.
Impact on Other 1. Exclusive with PCFICH adaptive

Features
Note 1. The two eNodeBs for Inter-BBU CA must have the same
version.
2. Support the maximum of 4ms inter-BBU delay.
3. Support up to two inter-BBUs with 3CC CA, but only supports
only one collaboration link with a delay longer than 0.2ms.
5.5.6 Support DL MIMO4*4 based on TM9
Table 5-19 Support DL MIMO4*4 based on TM9
Feature Name Support DL MIMO4*4 based on TM9
Feature In the downlink 4-antenna configuration of the eNodeB, TM9-based

Description downlink MIMO is supported. According to UE capacity and RI
report information, the eNodeB can implement downlink
transmission on 1-4 layers.
Impact on In the C-RS 4-port configuration, performance of TM9 is worse than

Equipment performance of TM3 in the case of UE supporting 4-layer TM3 and
Performance 4-layer TM9 both.
Impact on Network In the C-RS 4-port configuration, UEs that do not support 4-port
Performance C-RS may not access the network or performance may deteriorate.

Hardware BPN0, BPN2

Dependency
Related EUtranCellFDD.flagSwiMode
Parameter EUtranCellFDD.cellRSPortNum
CSIRSConfig.csiRSSWCH
CSIRSConfig.csiRSAntPortsCount
CSIRSConfig.anttoCSIRSPortMap
Related Alarm None

Method and Pass Normal cell, 4 antennas, C-RS configured with two ports, and
Criterion CSI-RS configured with four ports.
Pass criterion:
1. MIMO mode is configured as TM9 intra-transmode adaptation.
The eNodeB supports TM9 intra-transmode adaptation, and can
have a peak throughput of TM9 4*4 MIMO.
2. MIMO mode is configured as inter-transmode. The eNodeB
supports inter-transmode between TM3 and TM9, and can have the
maximum throughput.

Features
Note None
5.5.7 Downlink 256QAM
Table 5-20 Downlink 256QAM
Feature Name Downlink 256QAM Support
Feature The purpose of this feature is to improve the downlink throughput of

Description a UE at the near point. With this feature, more bits per frequency
unit can be carried through high-order modulation to increase the
downlink throughput effectively. It uses 256QAM to promote the
transmission speed of UEs in the center of a cell. At the same time,

256QAM has a high demand on the demodulation capability of UEs

and radio channels.
Impact on None
Equipment
Performance
Impact on Network The spectrum efficiency and downlink throughput are improved. The
Performance data transmission speed of UEs in the center of a cell and the user
experience are improved.
Hardware BPL1,BPN2
Dependency
Related Parameter EUtranCellFDD.qamSwch
Related Counter C373515750: Number of DL Init TBs with 256QAM Modulation

C373515751: Number of Successful Transported DL Init TBs with
256QAM Modulation
C373515752: Number of DL TBs with 256QAM Modulation Short
Name
C373515753: DL Data Volume with 256QAM Modulation Short
Name
C373515754: DL Data Volume Retransmission with 256QAM
Modulation
C373515756: DL scheduled UE Number configured new CQI table
with 256QAM Modulation
C373515789: Number of RB obtained DL by MCS31 for 256QAM
ITBS table2
C373515790: Total Number of DL TB Remained Error Packets for
256QAM
C373515845: Number of RB obtained DL by 256QAM Modulation
Mode
C374027264~C374027279: Number of CQI0 Used for 256QAM
CQI table2 ~Number of CQI15 Used for 256QAM CQI table2
C374281050~C374281077: Number of RB obtained DL by MCS0
for 256QAM ITBS table2 ~ Number of RB obtained DL by MCS27
for 256QAM ITBS table2

ITBS table2
ITBS table2
ITBS table2
Related Alarm None

Method and Pass When a UE stays at the nearest point, it can have the peak
Criterion throughput, and then it can switch to 256QAM. When the UE moves
to a further point, it can switch to 64QAM.
Pass criterion:
Thanks to 256QAM, the throughput curve of 256QAM switch_on is
better than the corresponding curve of 256QAM switch_off at the
near point. When the 256QAM switch is off, during the course of
moving away, UE will perform handover from 256QAM to 64QAM
with no-negative influence on the throughput.

Features
Note None
5.5.8 Network assistant CRS-IC without ABS
Table 5-21 Network assistant CRS-IC without ABS
Feature Name Network assistant CRS-IC without ABS
Feature With the CRS interference cancellation technology, the auxiliary

Description information is sent to a UE with the ability of eliminating interference
to inform the UE of the cell list information on which interference
cancellation operations need to be performed, ensuring correct
interference cancellation operations.
Impact on This feature solves the problem of residual CRS interference in the
Equipment ABS sub-frame to ensure that users can have the normal services
Performance under strong interference.

Performance
Hardware BPL1, BPN, and RRU

Dependency
Related Parameter HetNeteICICConfig.enableCRSICSwch

HetNeteICICConfig.absFuncCfg
UeEUtranMeasurement.measCfgIdx
HetNetMacMicRelation.mcc
HetNetMacMicRelation.mnc
HetNetMacMicRelation.neNodeBId
HetNetMacMicRelation.hcId
HetNetMacMicRelation.cellType
EUtranCellFDD.cellLocalId
Related Counter C373515513: Number of RB obtained UL by MCS1

C373343603: Maximum Cell UL PDCP Throughput
Related Alarm None

Method and Pass 1. Enable the interference cancellation function; make sure the UE
Criterion have the interference cancellation capability. Configure
intra-frequency neighbor cells and X2 connections, and make the
UE access the serving cell.
Pass criterion:
1. The measurement configuration for interference neighbor cell
discovery is sent to the UE. The UE reports the interference
neighbor cell discovery report, and fills the interference neighbor
cell information into the CRS auxiliary information list configured for
the UE.
2. The measurement configuration for interference neighbor cell
discovery is sent to the UE. The UE reports the interference
neighbor cell discovery report. The neighbor cell list is empty. If the
UE is configured with the CRS assistance information list, the UE is
configured to delete the CRS assistance information list.

Features
Note In a macro-micro scenario, if a micro cell shares the same coverage

with multiple macro cells at the same time, the CRS interference

cancellation function will be affected.

Reason: The CRS interference is removed in the macro-micro
scenario, and the assistance information for the UE is used to
support one interference cell only, and multiple interference cells
are not supported.
5.5.9 CA User Experience Aware Intra-LTE Load Balancing
Table 5-22 Special consideration of selecting a target cell for a CA user for load
balancing
Feature Name CA User Experience Aware Intra-LTE Load Balancing
Feature When a CA user executes load balancing, the candidate target cells
Description that can be used as primary carriers and have CA coordination
relationships should be preferentially sorted.
Impact on None
Equipment
Performance
Impact on None
Network
Performance
Hardware BPL1, BPN0 and BPN2

Dependency
Related LoadMNGCell.prbBasedLBCAFilterSwch
Parameter LoadMNGCell.cuBasedLBCAFilterSwch
Related Alarm None

Method and Pass 1. Users inside the serving cell are CA users.
Criterion 2. The serving cell satisfies the load balancing triggering conditions.
3. The serving cell has a neighbor cell (cell1) which is configured with
the CA coordination relationship and can be used as the primary
carrier.

4. The serving cell has a common neighbor cell (cell2), and check the
load balancing result.
Pass criterion:
1. The CA user performs handover to cell1 first.

Features
Note The switch of BasedLBCAFilterSwch must be disabled.
5.5.10 Dynamic authorization based on RB utilization of a cell
Table 5-23 Dynamic authorization based on RB utilization of a cell
Feature Name Dynamic authorization based on RB utilization of a cell
Feature The feature of dynamic authorization based on RB utilization of a cell

Description is used to allocate RBs dynamically for SR based on the historical RB
utilization.
The SR of normal services allocates RB2 regularly, and the MCS is
obtained according to the actual channel quality condition. To shorten
the response time from SR to PUSCH scheduling, this feature
dynamically allocates the RBs of SR based on the historical RB
utilization for non-QCI1 / QCI2, and non-RA UEs. While the MCS of
SR scheduling does not change.
Feature No. N/A
Impact on None
Equipment
Performance
Impact on If the RB2 of the SR is not enough to wrap the data, a subsequent
Network BSR grant is required to transmit the data. It may cause at least a
Performance delay of 7 ms from SR to PUSCH scheduling. This feature can
shorten the response time from SR to PUSCH scheduling..
Hardware BPL1, BPN

Dependency
Related EUtranCellFDD.srRBNumAuthMode
Parameter

EUtranCellFDD.filteWndLen4SRMode1
EUtranCellFDD.filteFactor4SRMode1
EUtranCellFDD.rbNumMultiFactor4Mod1
EUtranCellFDD.rbRatioLowThr4Mod1
EUtranCellFDD.rbRatioHighThr4Mod1
Related Alarm None

Method and Pass 1. Configure srRBNumAuthMode to the mode of based on cell RB
Criterion utilization (1), and configure the related parameters mentioned above.
2. Start the uplink services. The throughput becomes greater
gradually. Cell RB utilization should satisfy the following 3 scenarios:
1)RB utilization < = rbRatioLowThr4Mod1
2)rbRatioLowThr4Mod1< RB utilization < =
rbRatioHighThr4Mod1
3)RB utilization > rbRatioHighThr4Mod1
Pass criterion:
Under the above 3 scenarios:
Check UE’s state from reporting SR to PUSCH response. From the
scenarios 1) to scenarios 3), the response time becomes longer.

Features
Note The RB utilization rate is determined by factors including the filter

window length and filter factor, and is a little different from the KPI
statistics.
5.5.11 Qcell energy saving
Table 5-24 Qcell energy saving
Feature Name Qcell energy saving
Feature The Qcell supports the following energy-saving functions:

Description 1. Carrier shutdown and channel shutdown
In the case of the Qcell being configured with multiple carriers, one
or multiple carriers can be shut down (all RF power amplifiers of the
carriers are shut down) when the load is lower than a threshold, and

finally only one frequency is used to provide the basic coverage.

2. Symbol shutdown
When the load is lower than a threshold, intelligent OFDM symbol
shutdown is performed for one or multiple carriers of the Qcell.
3. pRRU power-off
The power supply for the PB network interface is automatically
turned on and off to power on and off the pRRUs within the
specified time. Users can also power on and off the pRRU through
“Board Power on/off” in the Dynamic Management module of the
EMS.
Feature No. N/A
Impact on None
Equipment
Performance

Performance
Hardware 1. supporting carrier shutdown and channel shutdown:

Dependency R8108&R8119
2. Supporting symbol shutdown: R8108 F851821(A5A)
3. Supporting pRRU power-off: R8102&R8108&R8119
License Control Yes

carrier shutdown: LTE-FDD_ENB_F073
channel shutdown: LTE-FDD_ENB_F074
symbol shutdown: LTE-FDD_ENB_F072
pRRU power-off has no license
Related Parameter carrier shutdown: SonControl, SonPolicyEs

channel shutdown: SonControl, SonPolicyEs
symbol shutdown: SonControl, SonPolicyEs
pRRU power-off: PrruPowerSaving
Related Alarm pRRU power-off: “PicoRRU enters energy conservation status” and
“PicoRRU exits energy conservation status”
Verification 1. carrier shutdown

Method and Pass Verification method:
Criterion 1)Multi-frequencies with the same coverage area, when the
number of users and the load of energy-saving cell are lower

than the energy-saving strategy threshold;

2) The load of the basic coverage area is increased.
Pass criterion:
1) The number of users and the load of the energy-saving cell
are below the threshold, the energy-saving cell is shutdown;
2) The load of the basic coverage area is greater than the
wake-up threshold, the energy-saving cell is wake-up.
2. channel shutdown
1) The users number and the load of LTE cell are low;
2) The users number or load of LTE cell gradually increased;
Pass criterion:
1) The users number and the load of LTE cell satisfy the
channel shutdown strategy threshold at the same time, the
eNodeB shutdown half of the RRU channel;
2)when the load or the number of users is greater than the
recovery threshold of energy-saving strategy, active the
channel to return to normal state.
3. symbol shutdown
1) The load of LTE cell are low;
2) The load of LTE cell gradually increased;
Pass criterion:
1) RRU symbol shutdown, the physical equipment enters into
energy-saving state;
2) The physical equipment exit energy-saving state.
4. pRRU shutdown
In the EMS, configure the time during which energy saving is
required and the pRRUs that do not need to be powered off.
Pass criterion:
1. All pRRUs can be powered on and off in the configured time
periods except for those that do not need to be powered off.
2. On OMC, select Dynamic Management > Board Information
Query > Energy Saving Status. The displayed information
indicates that the pRRUs can be powered off properly.

Features

Note The pRRU power-off policy should be disabled before version

upgrade.
5.5.12 Ultra extended Cell Radius
Table 5-25 Ultra extended Cell Radius
Feature Name Ultra extended Cell Radius

Feature This feature provides 100 km cell radius coverage beyond 0-30 km in
Description low-speed scenarios so that super-far coverage can be implemented
in sea scenarios.
Impact on The cell coverage area increases.
Equipment
Performance
Impact on None
Network
Performance
Hardware BPN0, BPN2
Dependency Support the following RRU models: R8861 series, R8881 series,
R8862 series, R8862 (A) series, R8872 series, UBR (R8892E) series,
A8602 series, R8812 series, R8402 series and R8412 series.
Related EUtranCellFDD.RingCoverSwch
Parameter EUtranCellFDD.RingCoverAdjustQuantity
PrachFDD.Ncs
PrachFDD.NumRAPreambles
PrachFDD.SizeRAGroupA
PrachFDD.MacNonContenPreamble
PrachFDD.prachFMRecOnTASwch
PrachFDD.prachUltiCapSwch
PrachFDD.prachSupFarCoverSwch
ENBFunctionFDD.sceneCfg
PrachFDD.highSpeedFlag
PrachFDD.prachConfigIndex
Related Alarm None

Method and Pass 1. Enable the ring coverage function. Refer to the ZTE LTE FDD
Criterion Extended Cell Radius Feature Guide.
Pass criterion:
1. After this feature is enabled, UEs in the 100 km range outside of
0-30 km can access the network properly.
Features
Note None
5.5.13 DL Frequency offset pre-compensation
Table 5-26 DL Frequency offset pre-compensation
Feature Name DL Frequency offset pre-compensation
Feature This feature supports that a CP compensates downlink signals

Description according to the available UL frequency deviation. It reduces the
requirement of UE solving the largest frequency deviation capacity in
high-speed scenarios (300km/h) and eliminates the superposition
influence caused by multiplex signals with large frequency deviation
difference. It improves UE demodulation performance, average cell DL
throughput, and user's experience.
Impact on None
Equipment
Performance
Impact on The E-RAB dropped call rate decreases and the UE demodulation
Network performance, average cell DL throughput, and user experience are
Performance improved.
Hardware BPN0, BPN2

Dependency
License Yes
Control
Related EUtranCellFDD.freqOffCompenSwchDl
Parameter
Related C374070033: Number of DL Frequency Offset value Precompensated

Counter in the range of 0Hz to 100Hz

C374070034: Number of DL Frequency Offset value Precompensated
in the range of 101Hz to 200Hz
C374070038: Number of DL Precompensation Frequency Offset value
exceed 500Hz
C374070039: Number of activated DL Frequency Offset
Precompensation
Related Alarm None

Method and In single-UE or multi-UE 6CP high-speed channel model (300 km/h),
Pass Criterion perform the uplink/downlink UDP/FTP service test.
Pass criterion:
After this feature is enabled, the average SINR，scheduling MCS and
throughput of the UE is higher than those when this feature is disabled.
Impact on None
Other Features
Note 1. The baseband board types must be BPN0 or BPN2.

2. Each core of BPN board supports only one CP(two antennas or
four antennas).
5.5.14 VoLTE in CA cell
Table 5-27 VoLTE in CA cell
Feature Name VoLTE in CA cell
Feature With the CA coordination relationship configuration, a UE can

Description access the network, make calls, and perform voice services
properly. The UE can perform handover among carriers during
calling, or between a CA cell and a normal cell. All UEs, supporting

CA or not, can perform VoLTE calls and voice services.
Feature No. N/A
Impact on Equipment performance is not affected because RTP packets are

Equipment transmitted on the PCC only.
Performance
Impact on Network Network performance is not affected because there is no difference

Performance between CA cells and normal cells.
Hardware None
Dependency
Related Alarm None

and Pass Criterion 1.UEs make call in the fixed, moving or handover scenes, the data
service can exist simultaneously.
Pass Criterion:
1. Call setup success rate is higher than 99%, handover setup

success rate is higher than 99%, and call drop rate is lower than
1%.
2. The RTP packet loss rate and PDCP packet loss rate are lower
than 1%, DL PDCP delay is lower than 50 ms, and DL PDCP
packet discarding rate is lower than 1%.
Impact on Other Other features are not affected because there is no difference
Features between CA cells and normal cells.
Note The VoLTE service is transmitted on the PCC only and SCCs will
not be activated unless there are data services simultaneously.
5.5.15 Support Recovery for Voice Packet Loss
Table 5-28 Support Recovery for Voice Packet Loss
Feature Name Support Recovery for Voice Packet Loss

Feature When QCI1 continuous ROHC decompression fails, if the number of

Description failures reaches the default threshold, the UE voice service is
restored to normal status by triggering intra-cell handover.
When QCI1 continuous decryption fails, if the number of failures
reaches the default threshold, the UE voice service is restored to
normal status by triggering intra-cell handover.
Impact on None
Equipment
Performance
Impact on Network Reduce the uplink and downlink RTP packet loss rate.
Performance
Hardware None
Dependency
Related Parameter PDCP.profile1 is set to 1, that is set QCI1and QCI2support RoHC

Profile1
EUtranCellFDD.deRohcSch is set to open
GlobleSwitchInformation.unidireDetectEnableSwch is set to open
GlobleSwitchInformation.unidireRecoverySwch is set to open
Related Counter C374251712: Number of attempts to intra cell handover since

header decompression failure on QCI1 bearer UL direction
C374251713: Number of attempts to intra cell handover since
decryption failure on QCI1 bearer UL direction
Related Alarm None

Method and Pass 1. UE1 and UE2 make voice calls successfully, and QCI1 is
Criterion established properly.
2. UE1 and UE2 are at the far point where there are continuous
PDCP decryption failures. When the number of PDCP decryption
failure packets is larger than the default threshold, the voice service
becomes normal after intra-cell handover is triggered, and there are
no dropped calls.
3. UE1 and UE2 are at the far point where there are continuous
compression package decompression failures. When the number of
decompression failure packets is larger than the default threshold,

the voice service becomes normal after intra-cell handover is

triggered, and there are no dropped calls.
Pass criterion:
1. For each intra-cell handover due to PDCP decryption failure, in
the 15-minute granularity time, C374251713 is incremented by one,
and the C374251712 does not count.
2. For each intra-cell handover due to RoHC decompression failure,
in the 15-minute granularity time, C374251712 is incremented by
one, and the C374251713 does not count.

Features
Note None
5.5.16 A1 and A2 thresholds for voice/data distinguishing
Table 5-29 A1 and A2 thresholds for voice/data distinguishing
Feature Name A1 and A2 thresholds for voice/data distinguishing
Feature Thresholds of event A1 and event A2 measurement can be configured

Description separately for data or voice services.
Impact on None
Equipment
Performance

Performance
Hardware CC16, CCE1, BPL1, BPN0 and BPN2

Dependency
License Control No
Related Parameter CellMeasGroup.clsInterFVoiceMeasCfg

CellMeasGroup.opeInterFVoiceMeasCfg
EUtranCellMeasurement.perQCIMeasSwch

Related Alarm None

Method and Pass 1. Configure inter-frequency frequency points and inter-frequency neighbor
Criterion cells.
2. Make a UE access the serving cell. The eNodeB sends event A2
inter-frequency measurement with data measurement threshold.
3. Set up a voice service, and The eNodeB sends event A2 inter-frequency
measurement with voice measurement threshold.
4. The UE sends the A2 measurement report to the eNodeB. The eNodeB
sends event A3 and A1 measurement, and A1 measurement uses voice
measurement threshold.
5. Release the voice service. The eNodeB sends event A1 measurement with
data measurement threshold.
Pass criterion:
1. The thresholds of data/voice A1 and A2 reported in the reconfiguration
message is the same as those configured in the EMS.

Features
Note None
5.5.17 Inter-RAT user migration supported by Magic Radio
Table 5-30 Inter-RAT user migration supported by Magic Radio
Feature Name Inter-RAT user migration supported by Magic Radio.
Feature In a Magic Radio DBE scenario, migrated users include data users
Description and VoLTE users. Data users are migrated based on blind
redirection to accelerate user migration. VoLTE users are migrated
according to handover based on measurement or blind
measurement according to the configuration.
Feature No. N/A
Impact on None
Equipment
Performance
Impact on Network The dropped call rate of VoLTE users is reduced, and the data user

Performance migration speed is increased.
Hardware None
Dependency
Related Parameter GlobleSwitchInformation.magicRadioUserMigStrategy
Related Counter C374017120 : Number of Outgoing Handover Preparation

Attemps(Based on Magic Radio)
C374017121 : Number of Outgoing HO Success(Based on Magic
Radio)
C373576640 : Number of Redirection Requests intra RAT(Due to
Magic Radio)
C373576641 : Number of Redirection Requests from LTE to
UTRAN(Due to Magic Radio)
Related Alarm None

Method and Pass 1. Make data users and VoLTE users access the cell. The Magic
Criterion Radio DBE service is performed in the cell.
Pass criterion:
1. Data users are migrated based on blind redirection, VoLTE users
are migrated based on measurement or blind measurement
according to the configuration.

Features
Note None
5.5.18 X2 self-establishment optimization
Table 5-31 X2 self-establishment optimization
Feature Name X2 self-establishment optimization
Feature X2 self-establishment optimization include the following items：

Description SCTP full detection Improves the X2 self-establishment efficiency;
bottom connectivity detection reduces invalid X2 establishment;
Invalid X2 detection period is configurable, which is flexible to meet

the different scenes;

X2 adding and deleting process unified, reduces the X2 ping-pong
delete, makes each X2 state more stable, the expected X2 can be
added according to the priority.
Feature No. N/A
Impact on None
Equipment
Performance

Performance
Hardware None
Dependency
Related Parameter SonPolicyX2FDD.statisticTimer

SonPolicyX2FDD. x2DirectAddSwch
SonPolicyX2FDD.x2StatisticOptSwch
SonPolicyX2FDD.x2DirectDelSwch
SonPolicyX2FDD.x2InvalidDelSwch
SonPolicyX2FDD.x2InvalidDelTimerLen
SonPolicyX2FDD.statisticTimer
SonPolicyX2FDD.statisticTimerGrade
SonPolicyX2FDD.hoNumThrdOfX2Opt
SonPolicyX2FDD.numOfX2AddDelCnt
SonPolicyX2FDD.s1SctpNum
ENBFunctionFDD.shiftNumber
ENBFunctionFDD.x2WhiteList
ENBFunctionFDD.x2BlackList
GlobleSwitchInformationFDD.x2PassProcSwch
GlobleSwitchInformationFDD.x2RebuildSwch
Related Counter C373990480：Number of Getting Remote IP

C373990481：Number of Passive Getting Remote IP
C373990482：Number of Successful Getting Remote IP
C373990498：Number of Active X2 Self Setup Initiation
C373990499：Number of Passive X2 Self Setup Initiation
C373990500：Number of Different X2 Self Setup for Passive

C373990501：Number of Same X2 Self Setup for Passive

C373990502：Number of Active Ping Initiation
C373990503：Number of Active Ping Success
C373990504：Number of Passive Ping Initiation
C373990505：Number of Passive Ping Success
C373990506：Normal X2 Number
C373990507：Total X2 Number
Related Alarm None
Verification First.Verification Method:

Method and Pass The eNodeB is configured with the neighbor relationship, and the
Criterion eNodeB X2 record dissatisfaction, and the eNodeB used the X2
immediately add policy.
Pass Criterion:
The strategy was issued successfully.
X2 Self-Establishment successfully.
Second. Verification Method
The eNodeB is configured with the neighbor relationship, and the
eNodeB X2 record full, and the eNodeB used the X2 immediately
add policy.
Pass Criterion:
X2 Self-Establishment failed.
Third.Verification Method:
eNodeB X2 record dissatisfaction, and the underlying link can ping
through, and the eNodeB used the X2 immediately add policy.
Pass Criterion:
X2 Self-Establishment successfully.
Fourth.Verification Method:
eNodeB X2 record dissatisfaction, and the underlying link is
nowhere, and the eNodeB used the X2 immediately add policy.
Pass Criterion:
X2 Self-Establishment failed.
Fifth.Verification Method:

The eNodeB exist in the neighborhood relationship with many

eNodeBs, and the underlying link can ping through, and the eNodeB
X2 record there are two X2 on the full;
The eNodeB used the X2 statistic policy, in which the Threshold of
Handover Success Number Offset for X2 Replace is 50, and the
Maximum Number of X2 Add/Del in Each Period is 3;
The eNodeB has established X2 in the X2 Self-Setup/Self-Delete
Statistic Timer Length of the number of handover through the sort,
with the lowest number of handover for the last five
100,99,98,97,96, there is a neighbor relationship, but no Set up X2
in the X2 Self-Setup/Self-Delete Statistic Timer Length of the
number of handover through the sort, with the handover the highest
number of the top five 500,450,400,350,300;
Pass Criterion:
The successful establishment of three X2（The number of handover
are 500,450,400）, the successful removal of one X2(The number of
handover is 96).

Features
Note None
5.5.19 CA neighbor cell self-configuration
Table 5-32 CA neighbor cell self-configuration
Feature Name CA neighbor cell self-configuration
Feature CA neighbor cell self-configuration supports the following process:

Description eNodeB transmit the periodical measurement configuration of
inter-frequency cells with strongest signal to UE; and automatically
collects the UEs’ measurement reports and calculates the
overlapping coverage between cells (including inter-eNodeB and
intra-eNodeB) periodically. When CA self-configuration threshold is
satisfied, eNodeB configures the coordination type of configure the
neighbor cell relationship is CA coordination (downlink CA, uplink
CA, or uplink/downlink CA), and then automatically maintains the
CA coordination relationship configuration.
Feature No. N/A

Impact on None
Equipment
Performance

Performance
Hardware BPL1, BPN0, CCE1, FS5C, and CR0

Dependency
Related Parameter SonCS.CASelfConfigSwch

SonCS.CoperType
SonCS.CAAppointRptStartTime
SonCS.CAAppointRptEndTime
SonCS.StatisticGrade
SonCS.CASCOverlapThr
SonCS.MaxNum4CACoper
EUtranCellMeasurement.OverlapSrvRSRPThr
EUtranCellMeasurement.OverlapDifferRSRPThd
EUtranCellMeasurement.MAXUserNum4Overlap
CellMeasGroup.OverlapInterFPeriodMeasCfg
EUtranRelation.coperModSwch
Related Alarm None

Method and Pass
Criterion 1. Configure the eNodeB with the inter-frequency neighbor
relationship.
2. The eNodeB issues the CA self-configuration policy. CA
switch is turned on with week as its calculating granularity.
The delivery succeeds.
3. Enable the CA self-configuration, the serving cell transmit the
periodical measurement configuration of inter-frequency cells
with strongest signal, and collects the UEs’ measurement
reports and calculates the overlapping coverage after the
calculating period ends.
4. CA self-configuration is expired, and CA self-configuration
addition is enabled (the calculating granularity is week, then

Tuesday is the effective date of CA self-configuration).

Pass criterion:
1. If the overlapped coverage reaches the threshold, the CA
self-configuration succeeds, the coordination relationship of
neighbor cell is updated to the specified one (downlink CA, uplink
CA or uplink/downlink CA).
2. If the overlapped coverage does not reach the threshold, CA
coordination relationship is not configured.

Features
Note CA self-configuration is aimed for inter-frequency neighbor cells.
5.5.20 ANR Consider not adding neighbor cells with illegal PLMNs
Table 5-33 ANR Consider not adding neighbor cells with illegal PLMNs
Feature Name ANR Consider not adding neighbor cells with illegal PLMNs
Feature When an unknown neighbor cell is selected, it cannot be selected if

Description the PLMN of the neighbor cell exists in the list of illegal PLMNs
(include illegal LTE and UTRAN cells ).
Impact on None
Equipment
Performance

Performance
Hardware None
Dependency
Related Parameter ENBFunctionFDD.illegalPlmn.mcc

ENBFunctionFDD.illegalPlmn.mnc
ENBFunctionFDD.illegalPlmn
Related Counter C373990513：Number of Illegal Adjacent Cell

C373990514：Number of Measurement Statistics with Illegal
Adjacent Cell

Related Alarm None

Method and Pass 1. Set the list of illegal PLMNs, and trigger the ANR procedure.
Criterion
Pass criterion:
When an unknown neighbor cell is selected, it cannot be added if
the PLMN of the neighbor cell exists in the list of illegal PLMNs.

Features
Note None
5.5.21 Downlink CA and 256QAM enabled simultaneously
Table 5-34 Downlink CA and 256QAM enabled simultaneously
Feature Name Downlink CA and 256QAM enabled simultaneously
Feature Description After a CA-enabled UE which also supports 256QAM are

configured with SCCs, each SCC can be configured to be
256QAM-enabled or 256QAM-disabled as required. For such
UEs, if they are located at the near points of all CA cells,
high-order demodulation can be used for all cells to improve
downlink UE speed and improve the spectrum utilization of the
serving cells at the same time.
Feature No. N/A
Impact on Equipment When 256QAM is enabled, it can effectively improve the

Performance downlink UE speed on the corresponding CA and user
experience.
Impact on Network Spectrum efficiency and downlink speed are improved.

Performance
Hardware Dependency BPN2
Related Alarm None

Verification Method and Verification method:

Pass Criterion 1. Make a CA UE that supports 256QAM in each band
download large data.
Pass criterion:
At a very-near point of each serving cell, 256QAM can be
enabled for a UE, and the throughput is improved compared
with that for 64QAM. During the process of moving the UE far
away, 256QAM is disabled.

Features
Note None
5.5.22 DL single-carrier 4*4 MIMO and 256QAM
Table 5-35 DL single-carrier 4*4 MIMO and 256QAM
Feature Name DL single-carrier 4*4 MIMO and 256QAM
Feature Description This feature aims to improve the UE downlink throughput at the
near points. The purpose is achieved through the following two
methods: 1. Increase MIMO layers (up to 4 layers). 2. Use a
high-order modulation scheme so that more bits can be carried
per frequency-domain resource unit. 4*4MIMO and 256QAM
can improve the spectrum utilization and data transmission
speed in the center of a cell. At the same time, 4*4 MIMO and
256QAM have a high demand on demodulation capability of
UEs and radio channels.
Feature No. N/A
Impact on Equipment The downlink throughput of the corresponding UEs (the

Performance maximum number of layers equals to 4 or/and DL 256QAM is
supported) and user experience are improved.
Impact on Network The spectrum efficiency and downlink throughput are

Performance improved. The data transmission speed of UEs in the center of
a cell is improved.
Hardware Dependency BPN2
License Control Yes

DL 256QAM: LTE-FDD_ENB_F114
4*4MIMO: LTE-FDD_ENB_F057

EUtranCellFDD.tm34T4RSwch
EUtranCellFDD.tm44T4RSwch
Related Counter C373515750: Number of DL Init TBs with 256QAM Modulation

C373515751: Number of Successful Transported DL Init TBs
with 256QAM Modulation
C373515752: Number of DL TBs with 256QAM Modulation
Short Name
C373515753: DL Data Volume with 256QAM Modulation Short
Name
C373515754: DL Data Volume Retransmission with 256QAM
Modulation
C373515756: DL scheduled UE Number configured new CQI
table with 256QAM Modulation
C373515789: Number of RB obtained DL by MCS31 for
256QAM ITBS table2
C373515790: Total Number of DL TB Remained Error Packets
for
256QAM
C373515845: Number of RB obtained DL by 256QAM
Modulation Mode
C374027264~C374027279: Number of CQI0 Used for
256QAM CQI table2 ~Number of CQI15 Used for 256QAM CQI
table2
C374281050~C374281077: Number of RB obtained DL by
MCS0 for 256QAM ITBS table2 ~ Number of RB obtained DL
by MCS27 for 256QAM ITBS table2
256QAM ITBS table2
256QAM ITBS table2
256QAM ITBS table2
C373515608: Number of RB obtained DL by TM3 RANK3


C373454845: Number of DL TBs with TM3 RANK3
Notes: In the protocol 36.213 C50 version, in Section 7.1.7.1,
add the ITBS mapping table with 256QAM modulation "Table
7.1.7.1-1A Modulation and TBS index table2 for PDSCH",
Section 7.2.3 adds the CQI table with 256QAM modulation
"Table 7.2.3-2 4-bit CQI Table2 ",
To distinguish between the original table and the new table
corresponding to the scheduling MCS and CQI information, the
table with 256QAM modulation referred is defined "256QAM
CQI table2" or "256QAM ITBS table2"
Related Alarm None
Verification Method and Verification method:

Pass Criterion When a UE stays in the nearest point, 4*4 MIMO and 256QAM
can be enabled for the UE to reach the peak throughput. When
the UE is moving away to a farther point, it can switch to
64QAM, and number of layers is reduced to 1.
Pass criterion:
Thanks to 256QAM, the throughput curve of 256QAM
switch_on is better than the corresponding curve of 256QAM
switch_off at near points, and the number of layers reaches 4.
During the process of moving the UE far away, when the
TBSIZE threshold is reached, the UE switches from 256QAM
to 64QAM and the number of layers is reduced to 1.

Features
Note None

5.5.23 A3 Not Being Deleted When B2 measurement is configured for Voice

Quality Based SRVCC
Table 5-36 A3 Not Being Deleted When B2 measurement is configured for Voice
Quality Based SRVCC
Feature Name A3 Not Being Deleted When B2 measurement is configured for

Voice Quality Based SRVCC
Feature A3 measurement will not be deleted when B2 measurement is

Description configured for SRVCC based on voice quality. When The quality
based measurement is configured, eNodeB will delete the coverage
based intra-RAT measurement in last version, which results that the
UE handover can only depends on quality based measurement,
reducing the coverage based handover chances.
Feature No. N/A
Impact on No impact
Equipment
Performance
Impact on Reduce the number of SRVCC based on voice quality.

Network
Performance
Hardware None
Dependency
License None
Control
Related None
Parameter
Related None
Counter
Related Alarm None
Verification Verification Method:

Method and 1. Open SRVCC based on voice quality, and add both intra-RAT and
Pass Criterion inter-RAT neighbor cells.
2. Lower the wireless quality eNB will send A3 measurement if UEs'
RSRP is lower than threshold.
3. Lower the wireless quality further, eNB will send B2 measurement if

Feature Name A3 Not Being Deleted When B2 measurement is configured for

Voice Quality Based SRVCC
UE's UL SINR is lower than the threshold or DL MCS is lower than the
threshold.
Pass Criterion:
A3 measurement still exists when B2 measurement is delivered.
Impact on None
Other Feature
Note None
5.5.24 Concurrence of Voice Quality Based and Coverage Based SRVCC
Table 5-37 Concurrence of Voice Quality Based and Coverage Based SRVCC
Feature Name Concurrence of Voice Quality Based and Coverage Based SRVCC
Feature SRVCC triggered by voice quality and coverage simultaneously exist.

Description When the quality based measurement is configured and eNodeB will
delete the coverage based inter-RAT measurement in last version,
which results that the UE handover can only depends on quality based
measurement, reducing the coverage based handover chances.
Hence the requirements of quality based and coverage based
strategies are concurrent instead of being mutually exclusive.
Feature No. N/A
Impact on None
Equipment
Performance
Impact on None
Network
Performance
Hardware None
Dependency
License None
Control
Related None

Feature Name Concurrence of Voice Quality Based and Coverage Based SRVCC
Parameter
Related None
Counter
Related Alarm None

Method and 1. Configure SRVCC based on voice quality and SRVCC based on
Pass Criterion coverage, add inter-RAT neighbor cells.
2. Lower the channel quality, and eNodeB will send B2 measurement
based on coverage if inter-RAT measurement threshold is satisfied.
3. Lower the channel quality further, and eNodeB will send B2
measurement based on voice quality if the voice quality based SRVCC
threshold is satisfied; while the B2 measurement based on coverage
will not be deleted.
Pass Criterion:
Measurement based on coverage will not be deleted when
measurement base on voice quality is configured.
Impact on None
Other Feature
Note None
5.5.25 Time to trigger SRVCC can be configured
Table 5-38 Time to trigger SRVCC can be configured
Feature Name Delay between the time when UL SINR threshold or DL MCS
threshold are satisfied and when SRVCC is triggered can be
configured.
Feature Delay between the time when UL SINR threshold or DL MCS

Description threshold are satisfied and when SRVCC is triggered can be
configured.
Feature No. N/A
Impact on None
Equipment

Feature Name Delay between the time when UL SINR threshold or DL MCS
threshold are satisfied and when SRVCC is triggered can be
configured.
Performance
Impact on Reduce the number of SRVCC based on voice quality reduces.

Network Especially to reduce the wrong handover.
Performance
Hardware None
Dependency
Related ENBFunctionFDD.VolteQualityDetectPrd
Parameter
Related Alarm None

Method and Pass 1. Set ENBFunctionFDD.VolteQualityDetectPrd
Criterion 2. Satisfy the threshold of voice quality measurement, and calculate
the delay when measurement for SRVCC based on voice quality is
configured.
Pass Criterion:
Delay between the time when UL SINR threshold or DL MCS
threshold are satisfied and when SRVCC is triggered is nearly equal
to the expected delay time.

Feature
Note None
5.5.26 Increase the demand for counter based on PDCP Discard Cause.
Table 5-39 Increase the demand for counter based on PDCP Discard Cause.
Feature Name Increase the demand for counter based on PDCP Discard Cause.
Feature Before releasing UE, it is reported that in this connection, the

Description number of packet loss due to the PDCP based on the timer timeout

and the number of packet dropouts based on PDCP are full.
Feature No. N/A
Impact on None
Equipment
Performance
Impact on None
Network
Performance
Hardware BPL1,BPN
Dependency
Related Counter C373354034 cell downlink QCI1 SDU PDCP timeout to abandon
the number of packets
C373354035 cell downlink QCI2 SDU PDCP timeout to abandon
C373354043 cell downlink PDCP SDU timer time to abandon the
number of packages
C373354044 cell downlink QCI1 SDU S1 queue full discarded
packets number
packets number

packets number
packets number
packets number
packets number
packets number
packets number
packets number
C373354053 cell downlink PDCP SDU S1 queue number of
discarded packages
Related Alarm None

Method and Pass Through the large traffic test on downlink, and continue to
Criterion increase the traffic throughput more than the eNodeB capacity, to
trigger the packet loss, and check the number of packet loss of
cells by KPI .
Pass Criterion:
Compare the number of reported packet loss number and align it
with KPI.

Feature
Note None

5.5.27 PDSCH scheduling RB is configurable for single direction within the

standard bandwidth
Table 5-40 PDSCH scheduling RB is configurable for single direction within the
standard bandwidth
Feature Name PDSCH scheduling RB is configurable for single direction within

the standard bandwidth
Feature It uses PDSCH RB bitmap method to set which RB not allowed to

Description use. If certain RB bitmap set to 1, PDSCH RB resource is not
available.
Feature No. N/A
Impact on If the cell is overlapped with other cell, the relevant RB bitmap is
Equipment set to 1, PDSCH RB resource is not available.
Performance
Impact on Network After shielding the operation to set the relevant RB bitmap to 1, the
Performance intra-RAT frequency interference on overlapped cell is reduced.
Hardware BPL1/BPN2/BPN0
Dependency
Related Parameter PhyChannel.rbForbiddenBitMapDL
Related Counter C373424603: PRB Number Available on PDSCH Channel
Related Alarm None

Method and Pass Set certain PDSCH RB bitmap to 1, and enable UE to perform ftp
Criterion service.
Pass Criterion:
Oberserve UE log, eNodeB doesn't allocate RB resources on
relevant UE if the PDSCH RB bitmap is set to 1.

Feature
Note None

5.5.28 Single RB allocation for VoLTE UE
Table 5-41 Single RB allocation for VoLTE UE
Feature Name Single RB allocation for VoLTE UE
Feature In high quality wireless channel conditions, single RB allocation can be

Description scheduled by eNodeB for VoLTE UEs to improve spectrum utilization.
For uplink, the single RB can only be schedule in the nearest point to
transmit the voice message in mute period; while for downlink, just the
64QAM condition is satisfied, the single RB can be schedule to transmit
a voice message in activated period.
Feature No. N/A
Impact on No impact
Equipment
Performance
Impact on RB utilization is reduced.

Network
Performance
Hardware None
Dependency
License None
Control
Related GlobalSwitch.1RBAllocateSwch
Parameter
Related None
Counter
Related Alarm None

Method and 1. Disable the DRX, SPS (this feature is not exclusive with DRX/SPS;
Pass Criterion disabling it is to trigger the single RB scenario for the convenience
of verification);
2. Two UEs make calls in very near distance at the 23.85kbps voice
data rate.
Pass Criterion:
Single RB can be allocated during mute period for UL; 1RB is

Feature Name Single RB allocation for VoLTE UE
scheduled for downlink single voice message transmission.
Impact on None
Other Feature
Note This feature is not mutually exclusive with DRX/SPS. Because the
downlink DRX period is 40ms, while the voice message’s period is
20ms, about 2 voice messages can be transmitted during DRX being
activated. To trigger the single RB transmitting one voice message,
DRX is disabled. So does SPS.
5.5.29 CPU Load requires adding counters to determine the stage
Table 5-42 CPU LOAD requires adding counters to determine the stage
Feature Name CPU Load requires adding counters to determine the stage
Feature Description In order to observe the happened times of every CC load state
in a time box, the load level is reported once a second.
There are 4 CC load states: low, middle, high, and overload.
The last three states are reported to EMS in 1 second period.
Feature No. N/A
Impact on Equipment None

Performance

Performance
Hardware CC16/CC16B and CCE support the load level statistics

Dependency
Related Counter C374190630 Times of CC Middle Load

C374190631 Times of CC High Load
C374190632 Times of CC Overload Load
Related Alarm none
Verification Method Verification Method:

and Pass Criterion Test the eNB using hard RRC traffic mode.

Feature Name CPU Load requires adding counters to determine the stage
Pass Criterion:
Check if the counters above are greater than 0.Note that the
above counters are 0 when the CC load is continuously low.
Impact on Other none

Feature
Note none
5.5.30 X2 Self-Establishment between Two Shared eNodeBs with Different

Primary PLMNs
Table 5-43 X2 Self-Establishment Between Two Shared eNodeBs with Different

Primary PLMNs
Under the scenario that two eNodeBs are configured as shared

Feature eNodeB and the primary PLMNs of the two shared eNodeBs are
Description different, the X2 self-establishment function can be enabled. This
function sets up an X2 link between the two shared eNodeBs.
Feature No. N/A
Impact on None
Equipment
Performance
Impact on None
Network
Performance
Hardware None
Dependency
Related GlobleSwitchInformation.dedctRANSharingSwch
Parameter
Related None
Counter
Related Alarm None


Method and 1. Configure two eNodeBs as shared eNodeB. The primary PLMNs of
Criteria the two eNodeBs are different, and there is no X2 link between the two
eNodeBs.
2. Enable the X2 self-establishment function on the two eNodeBs to
trigger X2 self-establishment.
Criteria:
1. The X2 link between the two shared eNodeBs with different primary
PLMNs is set up successfully.
Impact on None
Other Features
Note None
5.5.31 LTE and NB Sharing One Association
Table 5-44 LTE and NB Sharing One Association
Feature When the FDD-LTE and the NB-IoT share one eNodeB, they also use
Description the same association and eNodeB ID.
Feature No. N/A
Impact on None
Equipment
Performance
Impact on None
Network
Performance
Hardware CC16, CCE1

Dependency
License None
Control
Related None
Parameter
Related C374000564: Number of S1 Configuration Update Triggered by NB-IoT

Counter Setup Procedure
C374000565: Number of Successful S1 Configuration Update

Feature When the FDD-LTE and the NB-IoT share one eNodeB, they also use
Description the same association and eNodeB ID.
Triggered by NB-IoT Setup Procedure

C374000566: Number of S1 Configuration Update Triggered by NB-IoT
eNodeB Configuration Update Procedure
C374000567: Number of Successful S1 Configuration Update
Triggered by NB-IoT eNodeB Configuration Update Procedure
C374000568: Number of S1 Reset Triggered by NB-IoT Reset All
Procedure
Related Alarm None

Method and 1. Configure an SCTP of the FDD and NB-IoT standards. Use this
Passing association to add an S1AP for FDD-LTE and NB-IoT products each.
Criterion 2. Configure FDD-LTE and NB-IoT cells.
3. Test the FDD and NB-IoT cells in terms of their S1 procedures, cell
access, and FTP services.
Passing Criterion:
1. The association and S1APs of the FDD-LTE and NB-IoT are normal.
2. The FDD-LTE and NB-IoT cells are normal.
3. The S1 procedures of the FDD-LTE and NB-IoT cells are normal.
Their cell access and FTP services are normal.
Impact on None
Other Features
Note None

5.5.32 Auto-Adaption Congestion Control: AC Barring
Table 5-45 Auto-Adaption Congestion Control: AC Barring
Feature When the "Cellreserved" is not set to "reserved" and the "Cellbarred" is
Description not set to "barred" in the PLMN, the AC Barring sets the access factor
of each type of call included in the SIB2 to avoid network congestion.
The mechanism has two working modes: static and dynamic. In static
mode, the access probability and waiting time of each type of call in the
SIB2 shall be broadcast according to the EMS configuration. In
dynamic mode, the access probability shall be broadcast dynamically
according to the real-time load and the waiting time shall be broadcast
according to the back-end configuration. The real-time load can be one
or several kinds of flowing, including: (1) master control board
hardware load; (2) RRC user ratio load; (3) Baseband board load.
Feature No. N/A
Impact on None
Equipment
Performance
Impact on None
Network
Performance
Hardware UEs are required to support the AC barring feature.

Dependency
License None
Control
Related EUtranReselection.acBarWorkMode
Parameter EUtranReselectionFDD.acBarringForEmergency
EUtranReselectionFDD.acBarringFactor
EUtranReselectionFDD.acBarringTime
EUtranReselectionFDD.acBarringForSpecialAC
EUtranReselectionFDD.acBarringFactorOrig
EUtranReselectionFDD.acBarringTimeOrig
EUtranReselectionFDD.acBarringForSpecialACtOriag
EUtranReselection.acbPengdingWin
LoadManagement.acbCpuThrsh
LoadManagement.acbCpuHys
LoadManagement.acbCpuLoadWin

LoadControlCell.acbRRCRatioThrsh
LoadControlCell.acbRRCRatioHys
LoadControlCell.acbRRCRatioLoadWin
Related C373404526: Number of ac-barringInfo shrinking, expected by CC

Counter Hardware load
C373404527: Number of ac-barringInfo keeping constant, expected by
CC Hardware load
C373404528: Number of ac-barringInfo expanding, expected by CC
Hardware load
C373404529: Number of ac-barringInfo shrinking, expected by User
ratio load
User ratio load
C373404531: Number of ac-barringInfo expanding, expected by User
ratio load
C373404532: Number of ac-barringInfo shrinking, expected by BPL
load
Bpl load
C373404534: Number of ac-barringInfo expanding, expected by Bpl
load
C373404535: Number of ac-barringInfo shrinking
C373404536: Number of ac-barringInfo keeping constant
C373404537: Number of ac-barringInfo expanding
Related Alarm None

Method and 1. Change the AC access levels of the allowed user SIM cards to 15
Passing and 9 respectively.

Criterion 2. Configure the system so that only the UEs whose AC levels are 15
can be accessed. Connect the UEs whose AC levels are 9 and 15 to
the network.
3. Configure the system so that the UEs whose AC levels range from
11 to 15 cannot be accessed. Connect the UEs whose AC levels are 9
and 15 to the network.
4. Change the signaling access probability factor (acBarringFactor) to 1
and configure the system so that only the UEs whose AC levels range
from 11 to 15 can be accessed. Connect the UEs whose AC levels are
9 and 15 to the network.
5. Change the signaling access probability factor (acBarringFactor) to
0.5 and configure the system so that only the UEs whose AC levels
range from 11 to 15 can be accessed. Connect the UEs whose AC
levels are 9 and 15 to the network.
Passing Criterion:
1. The parameters are changed successfully.
2. Only the UEs whose AC levels are 15 are connected to the network
and their services are normal. The UEs whose AC levels are 9 cannot
be connected to the network.
3. The UEs whose AC levels are 9 and 15 cannot be connected to the
network.
4. The UEs whose AC levels are 9 and 15 are connected to the
network.
5. The UEs whose AC levels are 9 have a certain probability of being
connected to the network. The UEs whose AC levels are 15 are directly
connected to the network.
Impact on None
Other Features

Note None
5.5.33 First Packet IP Delay Statistics Supported
Table 5-46 First Packet IP Delay Statistics Supported
Feature The first packet delay statistics is defined as the average delay of the
Description eNodeB in processing the first block of every DL session from the UE.
The first packet count statistics is defined as the first package number
of UE each downlink session.
Feature No. N/A
Impact on None
Equipment
Performance
Impact on None
Network
Performance
Hardware None
Dependency
Related None
Parameter
Related C373200025
Counter C373200026
Related Alarm None

Feature The first packet delay statistics is defined as the average delay of the
Description eNodeB in processing the first block of every DL session from the UE.
The first packet count statistics is defined as the first package number
of UE each downlink session.

Method and 1. The UE does the FTP service.
Passing Passing Criterion:
Criterion
1. The counters are correct.
Impact on None
Other Features
Note MTN, South Africa
5.5.34 Downlink CA and Downlink 4*4MIMO
Table 5-47 Downlink CA and Downlink 4*4MIMO
Feature This feature can improve single UE's downlink throughput according
Description the following two ways:
1.Increase carrier number in CA;
2.Increase DL MIMO layers, up to four layers.
Feature No. N/A
Impact on None
Equipment
Performance
Impact on Improve single UE's downlink throughput

Network
Performance
Hardware BPN2, BPN0, FS5C,CR0

Dependency
Related None
Parameter
Related None
Counter

Feature This feature can improve single UE's downlink throughput according
Description the following two ways:
2.Increase DL MIMO layers, up to four layers.
Related Alarm None

Method and 1.Configure two cells to downlink CA;
Pass Criterion 2.Enable 4*4MIMO feature for each cell
3. UE attaches and does downlink FTP or UDP service.
Pass Criterion:
1. 4*4MIMO can be enabled, and the throughput could reach peak rate
in the near point.
Impact on None
Other Feature
Note None
5.5.35 Downlink CA and Downlink 4*4MIMO and 256QAM
Table 5-48 Downlink CA and Downlink 4*4MIMO and 256QAM
Feature This feature can improve single UE's downlink throughput according to
Description the following three ways:
2.Increase MIMO layers, up to four layer(10 layer can be supported for
total three-carrier CA);
3. Support more bits per frequency-domain by high-level modulation
scheme.
Feature No. N/A
Impact on None
Equipment
Performance
Impact on None
Network
Performance
Hardware BPN2, FS5C, CR0

Feature This feature can improve single UE's downlink throughput according to
Description the following three ways:
2.Increase MIMO layers, up to four layer(10 layer can be supported for
total three-carrier CA);
3. Support more bits per frequency-domain by high-level modulation
scheme.
Dependency
License Control Yes

DL 256QAM: LTE-FDD_ENB_F114
4*4MIMO: LTE-FDD_ENB_F057
Related None
Parameter
Related None
Counter
Related Alarm None

Method and 1.configure three cells to downlink CA;
Pass Criterion 2.Enable 256QAM for each cell, and enable 4*4MIMO for only two cells
and the other is not enabled;
3. UE attaches and does downlink FTP or UDP service.
Pass Criterion:
1. 256QAM could be enabled for each cell, 4*4MIMO could be enabled
for the two cells which open 4*4MIMO, and the throughput could reach
peak rate in the near point.
Impact on None
Other Feature
Note None

5.5.36 UDC
Table 5-49 UDC
Feature Name UDC
Feature To solve the limitation of uplink LTE radio resource, the Uplink Data
Description Compression (UDC) feature can compress the repeated parts
(including header and load) of IP packets to increase the uplink LTE
radio resource usage .
Impact on The eNodeB needs to decompress the compressed packets, and

Equipment this may cost some CPU usage of baseband boards and cause the
Performance CPU usage to increase.CPU usage increase as throughput and
compression rates increase.
eNodeB has a UDC load control policy. When the CPU usage is
higher than the threshold, the newly accessed UE will not enable
UDC.
Impact on Network The uplink throughput of the network increases, and with the same
Performance throughput, the uplink PRB usage decreases compared to the case
that the UDC feature is disabled.
The compression efficiency is relying on the contents of the pakege
content, the higher the content repetition rate, the higher the
compression efficiency.
Hardware The BPL0 board does not support the UDC feature.
Dependency
Related Parameter GlobleSwitchInformation.ulDataCompSwch

PDCP.ulDataCompSupport
UpLinkDataCompression.ulDataCompSndIndCapOccasion
UpLinkDataCompression.ulDataCompIsUeSndCapFirst
PDCP.ulDataCompCtxtMemSizeMax
Related Counter C373525990:UL PDCP SDU volume high before UDC

decompression
C373525991:UL PDCP SDU volume low before UDC
decompression
C373525992:UL PDCP SDU volume high after UDC
decompression
C373525993:UL PDCP SDU volume low after UDC decompression

C373525994:UL PDCP SDU DUC decompression attempt number

C373525995:UL PDCP SDU UDC decompression success number
C373525996:UL PDCP SDU volume high UDC decompression
failure
C373525997:UL PDCP SDU volume low UDC decompression
failure
Related Alarm None

Method and Pass 1. Enable the UDC feature, and use a UE supporting the UDC
Criterion feature do the uplink service. The throughput is larger than the
actual uplink radio bandwidth.
Pass criterion:
1,Check the received throughput at the PDN. The throughput is
larger than the actual uplink radio bandwidth.
2,Or calculate the throughput after being decompressed
according to the decompressed data of counters. The
throughput is larger than the actual uplink radio bandwidth.
Impact on Other UDC cannot be used with ROHC at the same time.
Features
Note The compression efficiency of UDC strongly depends on the

transmitted messages’ content. If the contents’ repetition rate is
high, the compression rate is high as well, the data rate gain is more
apparent.
5.5.37 Total Cell Transmit Power Statistics (Maximum and Average Power)
Table 5-50 Total Cell Transmit Power Statistics (Maximum and Average Power)
Feature Supports the statistics of total downlink transmit power KPIs:

Description C373414591, C373414592, and C373414587.
The value of C373414587 comes from the value of the wireless
parameter ECellEquipmentFunction.cpTransPwr.
Feature ID MktR-FP-094570
Impact on None
Equipment
Performance

Feature Supports the statistics of total downlink transmit power KPIs:

Description C373414591, C373414592, and C373414587.
The value of C373414587 comes from the value of the wireless
parameter ECellEquipmentFunction.cpTransPwr.

Performance
Hardware The following models of RRUs support C373414591 and

Dependency C373414592:
RRUs with four transmit ports: R8854 S1800 and R8854 S2600
RRUs with two transmit ports: R8862A, R8872A S1800, and
R8892N M8090 (800 MHz LTE and 900 MHz GSM)
License Control or No
Not
Related ECellEquipmentFunction.cpTransPwr
Parameters
Related Counters C373414587: Maximum Available Cell Transmit Power

C373414591: Maximum Cell Transmit Power
C373414592: Average Cell Transmit Power
Related Alarms None

and Notifications

Method and 1. Use an RRU of a model specified in the Hardware Dependency
Passing Criteria part.
2. The cell runs normally
3. Ensure RRU transmit power properly.
Passing Criteria:
1. Observe cell KPIs on the EMS. All three of the total cell transmit
power counters report correct values.

Features
Note C373414587 is independent of hardware.

5.5.38 Key Counter Statistics for Multiple PLMNs
Table 5-51 Key Counter Statistics for Multiple PLMNs
Feature Supports the statistics of the following eight key counters for
Description multiple PLMNs:
C495295200 Number of Send Init UE Message by ENB
C495295201 Number of Received First Message by ENB after Init
UE Message
C495305499 Number of Abnormal Release Active E-RABE
C495867454 Number of Abnormal Release Active E-RAB Triggered
by MME
C374543804 UL Aggregated Volume High
C374543805 UL Aggregated Volume Low
C374543806 DL Aggregated Volume High through Uu
C374543807 DL Aggregated Volume Low through Uu
Impact on None
Equipment
Performance

Performance
Hardware None
Dependency
License Control or None

Not
Related None
Parameters
Related Counters C495295200: Number of Send Init UE Message by ENB

C495295201: Number of Received First Message by ENB after Init
UE Message
C495305499: Number of Abnormal Release Active E-RAB
C495867454: Number of Abnormal Release Active E-RAB
Triggered by MME
C374543804: UL Aggregated Volume High
C374543805: UL Aggregated Volume Low
C374543806: DL Aggregated Volume High through Uu

UE Message
by MME
C374543807: DL Aggregated Volume Low through Uu
Related Alarms None

and Notifications

Method and 1. In the network sharing or non-network sharing scenario, after a
Passing Criteria UE accesses the network successfully and selects a PLMN, perform
the uplink/downlink UDP/FTP service for the default bearer of the
UE. Check the following six counters on the EMS:
UE Message
2. In the network sharing or non-network sharing scenario, after a

UE accesses the network successfully and selects a PLMN, trigger
abnormal Active E-RAB release caused by eNodeB or MME, check
the following two EMS counters:
C495305499 Number of Abnormal Release Active E-RAB
by MME
Passing Criteria:
For the logical cell of the selected PLMN, the above eight counters

UE Message
by MME
are correct.

Features
Note Italian Requirement
5.5.39 E-CID Positioning Supports Type 2 TA Measurement Reporting
Table 5-52 E-CID Positioning Supports Type 2 TA Measurement Reporting
Feature E-CID positioning requires that the eNodeB should report TA

Description measurements, which are used to calculate the distance between
the UE and the eNodeB.
The positioning server uses UE measurements (RSRP and RSRQ)
reported by the eNodeB and serving cell location information to
locate the UE. In type 2 TA measurement reporting, the
non-competitive random access procedure of the UE in connected
status is triggered to calculate the TA value (time difference
between reception and transmission by the eNodeB), and the value
is reported to the positioning server.
Impact on None
Equipment
Performance

Feature E-CID positioning requires that the eNodeB should report TA

Description measurements, which are used to calculate the distance between
the UE and the eNodeB.
The positioning server uses UE measurements (RSRP and RSRQ)
reported by the eNodeB and serving cell location information to
locate the UE. In type 2 TA measurement reporting, the
non-competitive random access procedure of the UE in connected
status is triggered to calculate the TA value (time difference
between reception and transmission by the eNodeB), and the value
is reported to the positioning server.

Performance
Hardware BPL1, BPN2, CCE1, and CC16

Dependency
License Control or No
Not
Related PositionConfig.ecidPosiSwchUl
Parameters
Related Counters None
Related Alarms None

and Notifications

Method and Make the positioning server deliver a positioning request including a
Passing Criteria type 2 measurement task to the eNodeB.
Passing Criteria:
The eNodeB successfully collects neighbor cell measurement
information for positioning the UE and the time difference between
reception and transmission by the eNodeB, and successfully reports
the collected information and the cell location information to the
positioning server.

Features
Note 1. Inter-frequency neighbor-cell positioning is not supported.

2. The double-CC environment is not supported.

5.5.40 Dynamic Broadcast Weights
Table 5-53 Dynamic Broadcast Weights
Feature This feature provides the phase rotation of broadcast weights,

Description in order to reduce the differences between RSRPs received by
the CPE.
Feature No. None
Impact on None
Equipment
Performance
Impact on Network Reduce the differences between RSRPs received by the CPE
Performance
Hardware Baseband board: BPL, BPN

Dependency
License Control No
Related Parameter TdlBFwgt.cchAmPhaseIndex
Related Alarm None

Method and Pass Configure the parameter “CCH Broadcast Weight Amplitude and
Criterion Phase Index” (TdlBFwgt.cchAmPhaseIndex)
Pass Criterion:
Observe the differences between RSRPs received by the CPE, the
differences between RSRPs is reduced.

Feature
Note None

5.5.41 Scheduling Evasion for SRLTE Terminal
Table 5-54 cheduling Evasion for SRLTE Terminal
Feature This feature provides a scheduling evasion method for

Description identifying the throughput loss of a dual SIM dual standby
terminal at the eNodeB side, and can reduce the throughput
loss of the dual SIM dual standby terminal .
Feature No. None
Impact on 1 Uplink throughput of dual SIM dual standby terminal can

Equipment increase .
Performance 2 If the dual sim dual standby terminal supports CA, uplink
throughput under the CA scenario of the terminal can increase.
3 The call drop rate may increase.

Performance
Hardware Main control boadr: CC16,CCE

Dependency Baseband board: BPL1,BPN
Related Alarm None

Method and Pass 1 The dual sim dual standby terminal accesses.
Criterion 2 The dual sim dual standby terminal does uplink UDP service.
Pass Criterion:
When the feature is enabled, the uplink throughput of dual sim dual
standby terminal is higher than the feature off.

Feature
Note Different chip for dual sim dual standby terminal will have different
uplink throughput gain.

5.6 LTE Enhanced Features
5.6.1 Context Fetch
Table 5-55 Context Fetch
Feature Name Context Fetch
Feature ZTE provided the solution to enhance the RRC reestablishment

Description success rate, the call drop rate and handover success rate. To
distinguish from the Context Fetch feature introduced by 3GPP, the
feature involved in this solution is referred to as ZTE inter eNodeB
re-establishment.
Regarding the scenario described above, 3GPP introduced a
standardized solution i.e. Context Fetch toTS36.300 V12.4.0 in
2015.
ZTE inter eNodeB re-establishment and Context Fetch solve the
same problem in two different ways. There involves interoperation
and compatibility between these two features. Provided that
eNodeB A enables the ZTE inter eNodeB re-establishment feature
and neighbor eNodeB B enables the Context Fetch feature,
eNodeB B imposes no impact on the ZTE inter eNodeB
re-establishment of eNodeB A. In other words, assuming that a UE
in eNodeB B encounters radio link failure, and then RRC is
reestablished in eNodeB A where there is no UE context; eNodeB A
is capable of reestablishing RRC based on the ZTE inter eNodeB
re-establishment feature, but eNodeB A will influence the Context
Fetch feature of eNodeB B. Assuming that a UE in eNodeB A
encounters radio link failure, and then RRC is reestablished in
eNodeB B where there is no UE context; eNodeB B fails to get the
UE context from eNodeB A based on the Context Fetch feature,
which leads to RRC reestablishment failure. Due to the RRC
reestablishment failure, the UE then turns to RRC_IDLE status
before it requests another RRC reestablishment. To handle the
interoperation and compatibility, ZTE provides a Context Fetch
feature compatible with TE inter eNodeB re-establishment feature.
Impact on None
Equipment

Performance
Impact on Network When this feature is enabled, the RRC dropped call rate is reduced.
Performance
Hardware None
Dependency
Related Parameter GlobleSwitchInformation.interEnbReestabSwch

Users can choose the configuration options on the network
management：
0: Close;
1: ZTE Inter eNodeB Re-establishment
2: Context Fetch
3: Context Fetch Compatible With The ZTE Inter eNodeB
Re-establishment.
Related Counter C373200060 Number of Successful RRC Connection

Re-establishment Triggered by Handover Failure
C373200066 Number of Successful RRC Connection
Re-establishment Triggered by Reconfig Failure
C373200072 Number of Successful RRC Connection
Re-establishment Triggered by Other
Related Alarm None

Method and Pass 1. The parameter GlobleSwitchInformation.interEnbReestabSwch
Criterion of the source and target eNodeBs for the following combinations
should be re-established successfully: (1,1), (1,3), (2,1), (2,2), (2,3),
(3,1), (3,2), and (3,3).
2. The parameter GlobleSwitchInformation.interEnbReestabSwch
of the source and target eNodeBs for the following combinations
should fail to be re-established: (0,0), (0,1), (0,2), (0,3), (1,0), (1,2),
(2,0), and (3,0).
Pass criterion:
Depending on the actual scenario, the UE connection is
re-established successfully or fails.

Features

Note When GlobleSwitchInformation.interEnbReestabSwch is set to 1

(ZTE Inter eNodeB Re-establishment), it is suitable for the cases:
(1) there are only ZTE eNodeBs in the live network, no other
vendors’ eNodeBs exist; (2) there are both ZTE eNodeBs and other
vendors eNodeBs in the live network, while other vendor’s eNodeBs
do not support or enable the Context Fetch that 3GPP TS36.300
defines.
When GlobleSwitchInformation.interEnbReestabSwch is set to 2
(Context Fetch), it is suitable for the cases that the eNodeBs of
other manufacturers in the commercial network support the context
fetch feature.
When GlobleSwitchInformation.interEnbReestabSwch is configured
to 3 (Context Fetch Compatible With The ZTE Inter eNodeB
Re-establishment), it is suitable for the cases that the eNodeBs of
other manufacturers in the commercial network support the context
fetch feature and some ZTE eNodeBs only support ZTE
Inter-eNodeB re-establishment.
5.6.2 eMBMS Counting
Table 5-56 eMBMS counting
Feature Name eMBMS counting
Feature In the MBMS network, the counting procedure is used to determine

Description the number of subscribers in an MBSFN area, and the data is used
for adjusting network deployment and resource allocation.
The MBMS service is provided in an MBSFN area. If the number of
UEs that are receiving or about to receive an MBMS service in an
MBSFN area is smaller than a threshold, the MBMS of all cells in
the MBSFN area can be suspended. If the number of UEs that are
receiving or about to receive an MBMS service in an MBSFN area is
larger than a threshold, the MBMS of all cells in the MBSFN area
can be resumed. It can reduce resource waste.
The current version only supports Counting procedure, not supports
service suspension and resumption.
Impact on None
Equipment

Performance

Performance
Hardware MCE equipment

Dependency
Related Alarm None

Method and Pass The MCE triggers the counting procedure once or periodically. The
Criterion switch of triggering the counting procedure is configured on the
OMMB.
If it is triggered periodically, the triggering period should be
configured on the OMMB. The triggering period is not specified in
the protocol. It must be at least two times of the modification period.
Pass criterion:
1. The MCE initiates the procedure by sending an MBMS
SERVICE COUNTING REQUEST message to the eNodeB.
2. After receiving the MBMS SERVICE COUNTING REQUEST
message successfully, the eNodeB responds the MCE with an
MBMS SERVICE COUNTING RESPONSE message.

Features
Note None
5.6.3 Service Based PCC Dynamic Selection
Table 5-57 Service Based PCC Dynamic Selection
Feature Name (Service Based PCC Dynamic Selection)
Feature Inter-frequency handover triggered by voice services is not

Description supported in CA scenarios. Thus, measurement event A4 is
modified to A5 to support primary-secondary carrier handover

triggered by voice services in CA scenarios.
Impact on None
Equipment
Performance

Performance
Hardware None
Dependency
Related Parameter EUtranCellMeasurement.hoBaseServiceSwch
Related Alarm None

Method and Pass 1. Enable the services based handover function, enable the CA
Criterion function.
2. Make the UE access the serving cell.
3. Make the UE perform a voice call to trigger inter-frequency
handover based on voice services.
4. The eNodeB sends an RRC Connection Reconfiguration
message to the UE.
Pass criterion:
1. The measurement event in the RRC Connection Reconfiguration
message is event A5.

Features
Note None
5.6.4 Flexible Scell configuration of multi-carriers
Table 5-58 Flexible Scell configuration of multi-carriers
Feature Name Flexible Scell configuration of CA

Feature This feature provides Scell flexible selection according to the priority
Description of frequency and the load of candidate cells. The candidate cells
with higher frequency priority and lower load will be added as Scell.
The selection is performed in terms of frequency’s priority first, that
is, to select the candidate cells at high priority; if there are several
such groups, sequence them by the load information, add the cells
with low loads. Directly add the co-covered/co-included cells; for
neighbor cells, deliver A4 measurement, add SCC after A4
measurement is reported.
Impact on None
Equipment
Performance
Impact on Network When this function is enabled, the whole network resources will be
Performance fully used, improving the performance of UE and network.
Hardware BPL1, BPN

Dependency
License Control No
Related Parameter CarrierAggregatin.ScellSelBaseFreqPriSwch

CarrierAggregatin.ScellBaseDlPRBSwch
CarrierAggregatin.SCellPRBThrd
CarrierAggregatin.PRBThrd4GetLBInfo
CarrierAggregatin.ScellSelBaseWBSwch
EUtranCellMeasurement.ScellFreqPriority
CarrierAggregatin.CAmeasIDSwch
Related Alarm None

Method and Pass 1. Enabled “Flexible Scell configuration” feature;
Criterion 2. CA cell frequencies are set to different Scell priorities and loads;
CA UE accesses to the cell.
Pass Criterion:
The cell with higher frequency priority, lower load will be selected as

the Scell when this feature is enabled.

Feature
Note None
5.6.5 Up to Three Coordinating Cells in CS
Table 5-59 up to three Coordinating Cells in CS
To further meet the coordination requirements under the macro/micro

hybrid networking structure and super-dense networking scenario in
dense urban areas, the number of coordinating cells must be extended.
This feature supports coordination with up to three strong interference
Feature
cells. When a serving cell is configured with three or more coordinating
Description
cells, the coordinating cell set of a UE is determined based on the
measurement results of serving cells and neighbor cells. The
coordinating cell set includes a maximum of three coordinating cells.
The UE initiates CS requests to cells in the coordinating cell set.
Feature No. MktR-PE-20151030-05-0100400030

ZLF34-00-003
ZLF34-00-024
Impact on None
Equipment
Performance
Impact on In a dense networking structure where a UE is under the interference

Network from multiple cells, this feature can significantly improve the downlink
Performance rate of each single user and the system throughput.
Hardware BPL1, BPN0, BPN2, FS, CR0

Dependency
License Y, SDR_F043_L.
Control This is an extension of the downlink CoMP coordinating set of the LTE
FDD. This license item controls whether multiple coordinating cells are
supported on the downlink of the network.
Related PhyChannel.maxCoopNbrCellNum
Parameter

Related C373596966: Number of user-initiated coordination meeting the

Counter downlink CoMP threshold
C374222558: number of downlink CoMP CS users (GBR)
C374222559: number of downlink CoMP CS users (NonGBR)
C373596967: Number of new user-initiated coordination RBs meeting
the downlink CoMP threshold
C373597081: number of requests initiated by the downlink CoMP to
two coordinating neighbor cells
C373597082: number of requests initiated by the downlink CoMP to
three coordinating neighbor cells
Related Alarm None

Method and 1. The test shall be performed under the following three scenarios:
Criteria The maximum number of UE-level CoMP coordinating cells between
two macro cells is 3.
The maximum number of UE-level CoMP coordinating cells between
two micro cells is 3.
The maximum number of UE-level CoMP coordinating cells between a
macro cell and a micro cell is 3.
2. A UE is under the overlapping area of four cells, including the
serving cell. That is, the downlink measurement results upon the
serving cell and coordinating neighbor cells of the UE meet CoMP
requirements.
3. In each test cell, under the background interference load of 70% RB
usage, perform downlink services upon the UE.
4. Enable the downlink CoMP, and compare the UE rate and cell
throughput. Modify the maximum number of coordinating cells, and
compare the UE rate and cell throughput under different number of
coordinating cells.
Criteria:
1. When the maximum number of coordinating cells is set to 3 and the
UE initiates CS requests to three cells, the value of C373596966 is
three times that of C373597082. Similarly, when the maximum number
of coordinating cells is 2, the value of C373596966 is twice that of
C373597081.
2. When the maximum number of coordinating cells is set to 3 and the
UE initiates CS requests to three cells, the value of C373597081 is 0.
Similarly, when the maximum number of coordinating cells is 2, the

value of C373597082 is 0.
3. Compared with the scenario when the maximum number of
coordinating cells is 1 or 2, when it is set to 3, the UE rate and cell
throughput are both increased.
Impact on None
Other
Features
Note None
5.6.6 Flexible UE Handling Strategies Supported in Case of an S1 Link

Failure
Table 5-60 Flexible UE Handling Strategies Supported in Case of an S1 Link Failure
Feature When an S1 link failure occurs, the eNodeB supports flexible UE

Description handling strategies through switch configuration.
1. Keep the original V3.3 handling strategy: the eNodeB can redirect
the UE to an inter-frequency or inter-RATE neighbor cell,
regardless of whether the cell is a serving cell or not.
2. The eNodeB releases the UE without redirection when the cell is in
service.
Feature No. N/A
Impact on None
Equipment
Performance
Impact on When the second strategy is used, the E-RAB release, context release,
Network and RRC release KPIs deteriorate because the UE is released when
Performance an S1 link failure occurs.
Hardware None
Dependency
Related ENBFunctionFDD.s1LinkFailStrategy
Parameter
Related C373200041: Number of RRC Connection Release due to Optical Port

Counter Fault


service.
C373200050: Number of RRC Connection Release due to ENB

Redirection
C373210398: Number of E-RAB Release due to Optical Port Fault
C373210522: Number of QCI1 E-RAB Release by ENB Through

E-RAB Release Procedure due to Redirection








C373210531: Number of E-RAB Release by ENB Through E-RAB

Release Procedure due to Redirection

E-RAB Release Procedure due to S1 Link Error


service.

C373505354: Number of E-RAB Release by ENB Through E-RAB
Release Procedure due to S1 Link Error
C373220643: Number of Context Release due to Optical Port Fault
C373220618: Number of Context Release by ENB due to Redirection
Related Alarm None
Verification Verification Method 1:

Method and 1. Configure the ENBFunctionFDD.s1LinkFailStrategy (S1 Link Fail
Passing Strategy) switch to 1 (Redirect Ue).
Criterion 2. Make the UE access the serving cell.
3. Trigger an S1 link failure.
Passing Criterion:
1. The UE is redirected. The context release, E-RAB release, and RRC
release counters show "Redirection".
Verification Method 2:
1. Configure the ENBFunctionFDD.s1LinkFailStrategy (S1 Link Fail
Strategy) switch to 0 (Redirect Release Ue).
2. Make the UE access the serving cell


service.
3. Trigger an S1 link failure.

Passing Criterion:
1. The UE is released directly. The context release, E-RAB release,
and RRC release counters show "S1 Link Fail".
Impact on None
Other Features
Note None
5.6.7 Supporting CSFB Process Optimization During VoLTE Conversation
Table 5-61 Supporting CSFB process optimization During VoLTE Conversation
Feature Supporting CSFB process optimization During VoLTE Conversation.

Description This feature solves the call drop problem due to CSFB for VoLTE users.
It enables eNodeB hands UE over to 3G/2G network by SRVCC after
CN triggers CSFB during VoLTE conversation.
When receiving UE CONTEXT MODIFICATION REQUEST signaling
with “CS Fallback Indicator” sent by MME for VoLTE user, eNodeB
does not trigger the CSFB process; it selects proper GERAN, WCDMA
and TDS and its frequencies according to the UE supported SRVCC
capability, and then delivers B1/B2 event measurement; if no proper
system and frequency selected, the UE will not be processed.
After delivering the measurement task, if UE’s measurement report is
received in certain period of time, the reported neighbor cells are
screened and sequenced to trigger the handover; delete the
measurement if time expires or QCI 1 service is released.
Feature No. MktR-FP-0300850
Impact on None
Equipment
Performance


Impact on None
Network
Performance
Hardware None
Dependency
License No
Control
Related None
Parameter
Related None
Counter
Related Alarm None
Verification Verification:
Method and 1. Initiate voice service and establish QCI1 after UE accesses into
Pass Criterion eNodeB.
2. MME delivers UE CONTEXT MODIFICATION REQUEST signaling
with “CS Fallback Indicator” to eNodeB for the UE.
Pass Criterion:
1. eNodeB does not trigger CSFB for the UE.
2. eNodeB selects proper system and frequency for the UE and delivers
SRVCC measurement.
Impact on None
Other Feature


Note Make sure there are frequencies whose SRVCC measurement indicator
is configured to “Yes”, otherwise eNodeB will not deliver measurement
task.
5.6.8 To Prohibit eSRVCC before Alerting in VoLTE Call
Table 5-62 To Prohibit eSRVCC before Alerting in VoLTE Call
Feature Name To Prohibit eSRVCC before Alerting in VoLTE Call
Feature Most of the current core networks do not support eSRVCC during
Description VoLTE establishment. During the period from QCI1 establishment
to 180Ringing, if eSRVCC occurs, the call will be disconnected. So
the eNodeB needs to prohibit eSRVCC during this period.
Feature No. None
Impact on None
Equipment
Performance
Impact on Network The UE access rate for a far point volte call is improved.
Performance
Hardware CC16, CCE1, BPL1, BPN0

Dependency

Related Alarm None

Method and Pass 1. Set a GSM neighbor cell for the LTE cell.
Criterion
2. UE does VoLTE calls 50 times at a far point of the LTE
cell(RSRP<-120)
3. Record the VoLTE call success ratio.
Pass Criterion:
The VoLTE call success ratio is greater than 90%.

Feature
Note None
5.6.9 eNodeB supports 512 groupIds for each S1
Table 5-63 eNodeB supports 512 groupIds for each S1
Function eNodeB supports 512 groupIds for each S1.

description
Func No. None
Impact on None
Equipment
Performance
Impact on Network By support more groupIds, eNodeB can select the matched MME
Performance for UE, decreasing the signalliing interactions.
Hardware None
Dependency

Function eNodeB supports 512 groupIds for each S1.

description
Related Alarm None

Method and Pass
1 eNodeB creates S1 with two MMEs, config more than 128
Criterion
groupIds for MME1.
2 Make UE attach and the groupId carried by UE is the same as the

Nth groupId (N> 128) of MME1, and the groupId configured by the
MME2 is different from the one UE carried.
Pass Criterion:
The UE attach to MME1.

Feature
Note None
5.7 NB-IoT Function List
Table 5-64 NB supported function list
Function Function Version Status

ID
1 Support CP (Control Plane) Service V4.16.10.20P10 Available
Available
2 Support 3.75K ST V4.16.10.20P10
3 Support 15K ST/MT V4.16.10.20P10 Available

4 Support 3.75K/15K ACK Channel V4.16.10.20P10 Available
5 Support Standalone Mode V4.16.10.20P10 Available
Available
6 Support Short/Long CP NB-PRACH V4.16.10.20P10
Available
7 Support NB-PDCCH Channel V4.16.10.20P10
Available
8 Support Paging Function V4.16.10.20P10

Available
9 Support System Information Broadcast V4.16.10.20P10
10 Support Idle MS Mobility V4.16.10.20P10 Available
Support DL Data Transmission via Single Available

11 V4.16.10.20P10
Antenna Port
Support DL Data Transmission via Two Available
12 V4.16.10.20P10
Antenna Ports (SFBC)
13 Support NB-PDCCH Frequency Reuse V4.16.10.20P10 Available
14 Support Enhanced 20dB Coverage V4.16.10.20P10 Available
15 Support 2-Antenna MRC and IRC V4.16.10.20P10 Available
16 Support 3.75k/15k ACK Channel V4.16.10.20P10 Available
Available
17 V4.16.10.20P10
CCE1 Supports NB-IoT Single Mode
Available
18 V4.16.10.20P10
CCE1 Supports LN Hybrid Mode
19 BPN2 Supports NB-IoT Single Mode V4.16.10.20P10 Available
20 BPN2 Supports LN Hybrid Mode V4.16.10.20P10 Available
Support BPN0A (Only for China Telecom Available
21 V4.16.10.20P10
and China Unicom)
22 BPN0_b supports NB-IoT Single Mode V4.16.10.20P10 Available
23 CC16B Supports NB-IoT Single Mode V4.16.10.20P10 Available
Available
24 CC16B Supports LN Hybrid Mode V4.16.10.20P10
25 CCE1A Supports NB-IoT Single Mode V4.16.10.20P10 Available

Available
26 CCE1A Supports LN Hybrid Mode V4.16.10.20P10
27 BPN1A Supports NB-IoT Single Mode V4.16.10.20P10 Available

28 Use USB Disk to Open a Site V4.16.10.20P10 Available
Support Uplink Frequency Hopping Available
29 V4.16.10.20P10
Function
Available
30 CCE1 Supports GLN Hybrid Mode V4.16.10.20P10
31 BPN2 Supports GN Hybrid Mode V4.16.10.20P10 Available

32 CC16D Supports NB-IoT Single Mode V4.16.10.20P10
33 CC16D Supports LN Hybrid Mode V4.16.10.20P10 Available
BPN2A Supports N Single Mode and LN Available
34 V4.16.10.20P10
Hybrid Mode
Number of NB RRC Instances Supported Available
35 V4.16.10.20P10
by CC
36 3.75K SINR and Power Measurement V4.16.10.20P10 Available

Reporting
37 Support eDRX Function V4.16.10.20P10 Available
Support Connection State SR (Scheduling Available
38 V4.16.10.20P10
Request)
Redirection Based on the number of RRC Available
39 V4.16.10.20P10
Connections
15K SINR and Power Measurement Available
40 V4.16.10.20P10
Reporting
41 Support UL/DL AMC V4.16.10.20P10 Available
Configure the Number of Tones Over a Available
42 V4.16.10.20P10
Sub-carrier Space
43 Admission Control Based on UL PRB V4.16.10.20P10 Available
44 Support 3.75K Even Subframe Scheduling V4.16.10.20P10 Available
EAB Admission Control Based on the Available
45 V4.16.10.20P10
Number of RRC Connections
46 Optimize Paging Process V4.16.10.20P10 Available
47 Configure AMC B-type Parameters V4.16.10.20P10
48 Support UP Basic Function V4.16.10.20P10 Available
Support UP Suspending and Resuming Available
49 V4.16.10.20P10
Process
50 OMMB Supports PNP V4.16.10.20P10 Available
51 BPN1_A Supports N and LN V4.16.10.20P10 Available
52 OMMB Supports NB License V4.16.10.20P10 Available
53 Support CCE1B Board V4.16.10.20P10 Available
52 Support FS5B Board V4.16.10.20P10 Available
Support LN Same STCP Available
53 V4.16.10.20P10
5.8 NB-IoT Function Description
5.8.1 Support CP (Control Plane) Service

Function NB adds CP signaling access process so that data is carried over
description NAS.
Function ID
Impact on device No
performance

performance
Hardware UE chip version should support it.

dependence
Impact on the No
interface of an
associated network
element
license?
Associated It is supported in default.

parameter
Associated alarm No
and notification
Verification method In the situation of 3.75K ST, 15 ST or 15K 3/6/12Tones, UE can be

and pass criterion attached and run ping command.
Impact on other No
functions
Remark Null
5.8.2 Support 3.75K ST

Function The system can select 3.75K ST to run service over PUSCH.
description
Function ID
Impact on device No
performance
Impact on network Uplink coverage is enhanced.

performance
dependence
Impact on the No
interface of an
associated network
element

license?
In the NB-IOT Cell node, click PUCH and PDCH, then click
Associated
Selection Method of NPUSCH subcarrier and tones, select
parameter
3.75kHz
Associated alarm No
and notification
Verification method UE can be attached and run ping command.

and pass criterion
Impact on other No
functions
Remark Null
5.8.3 Support 15K ST/MT

The system can select 15K ST/MT to run service over PUSCH. It
Function
can distinguish between 15K ST and 15K MT according to
description
random access subcarrier position.
Function ID 3
Impact on device This shortens scheduling duration.

performance
Impact on network Uplink rate is improved.

performance

dependence
Impact on the No
interface of an
associated network
element
license?

In the NB-IOT Cell node, click PUCH and PDCH, then click
Selection Method of NPUSCH subcarrier and tones, select
Associated
15K ST/3tone/6tone/12tone respectively.
parameter
Hopping parameter: open NB-IOT cell, Open System
Information interface
Associated alarm No
and notification
Verification method In the situation of 15K ST, 15K MT 3/6/12Tones, random access is
and pass criterion normal, UE can be attached and run ping command.
Impact on other No
functions
Remark Null
5.8.4 Support Standalone Mode

Function The system supports standalone mode as declared in 3GPP standard
specification. NB-IoT uses independent frequency to implement
description deployment.
Function ID
Impact on device No
performance
performance
Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?
Associated SystemInformation.operationMode
parameter
Associated alarm No
and notification

Verification method Configure standalone mode as declared in 3GPP standard specification.

and pass criterion UE can be attached and run ping command.
Impact on other
functions
Remark Null
5.8.5 Support Short/Long CP NB-PRACH

Function The system supports short/long CP NB-PRACH to adapt to various
description coverage cells.
Function ID
Impact on device No
performance
performance

dependence
Impact on the No
interface of an
associated network
element
license?
Associated SystemInformation.nprach_CP_Length
parameter
Associated alarm No
and notification
Verification method Set short CP PRACH and long CP PRACH respectively. UE can be
and pass criterion attached and run ping command.
Impact on other
functions
Remark Null

5.8.6 Support System Information Broadcast

Function The system broadcasts SIB1 and SIB2 according to 3GPP standard
description specification.
Function ID No
Impact on device No
performance
performance
Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?
Associated No
parameter
Associated alarm No
and notification
Verification method UE can be accessed. The decoded contents of SIB1 and SIB2 by UE
and pass criterion should be consistent with those at network side.
Impact on other
functions
Remark Null
5.8.7 Support Idle MS Mobility

Function The system broadcasts SIB3, SIB4 and SIB5 according to 3GPP
standard specification.
description
Function ID No
Impact on device No
performance
performance

Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?
Associated No
parameter
Associated alarm No
and notification
1. UE is attached properly. The decoded contents of SIB3, SIB4 and

SIB5 are consistent with those at network side.
Verification method
and pass criterion 2. Attenuate signal strength in serving cell. Keep the signal strength in
adjacent cell stronger than that in servicing cell. UE can be handed
over to adjacent cell upon reselection process.
Impact on other
functions
Remark No
5.8.8 Support Paging Function

Function UE stays at RRC idle state. When CN (Core Network) needs to transmit
downlink data to this UE, it sends a paging message. After this UE
description receives this paging message, it enters RRC connection state.
Function ID No
Impact on device No
performance
performance
Hardware No
dependence

Impact on the No
interface of an
associated network
element
license?
Associated No
parameter
Associated alarm No
and notification
1. After UE is attached, it initiates ping command, then wait until it

enters idle state.
Verification method 2. Ping this UE at PDN. After eNodeB receives a paging message from
and pass criterion CN (Core Network), it sends this paging message to UE.
3. After this UE receives this paging message, it initiates access

operation and responds to this ping command.
Impact on other No
functions
Remark Null
5.8.9 Support DL Data Transmission via Single Antenna Port

Function The system supports downlink TM1 transmission mode according to
description 3GPP standard specification.
Function ID No
Impact on device No
performance
performance
Hardware No
dependence
Impact on the No
interface of an
associated network
element

license?
Associated No
parameter
Associated alarm No
and notification
1. Configure one downlink antenna. Set the number of antenna ports to

Verification method 1, set DL transmission mode to TM1.
and pass criterion
2. UE can be accessed to the network. UE can be attached and run
ping command.
Impact on other No
functions
Remark Null
5.8.10 Support DL Data Transmission via Two Antenna Ports (SFBC)

Function The system supports downlink TM2 transmission mode according to
3GPP standard specification.
description
Function ID No
Impact on device No
performance
performance
Hardware UE used chip should support it.

dependence
Impact on the No
interface of an
associated network
element
license?
Associated No
parameter

Associated alarm No
and notification
1. Configure 2 downlink antennas. Set the number antenna ports to 2,

Verification method set DL transmission mode to TM2.
and pass criterion
2. UE can be accessed to the network. UE can be attached and run ping
command.
Impact on other No
functions
Remark Null
5.8.11 Support NB-PDCCH Frequency Reuse

Function PDCCH supports the configuration of CCE 1 and CCE 2.
description
Function ID No
Impact on device No
performance
performance

dependence
Impact on the No
interface of an
associated network
element
license?
Associated No
parameter
Associated alarm No
and notification
Verification method 1. Configure PDCCH aggregation level to be CCE 1 or CCE 2.

and pass criterion
2. UE can be attached and can run ping command properly.

Impact on other No
functions
Remark Null
5.8.12 Support Enhanced 20dB Coverage
Coverage Enhancement is required to deploy those NB-IOT UEs,

which locate at the edge of cells or basement where signal is very
weak. UEs can flexibly use frequency resource in three kinds of
Function
operation modes to implement Coverage Enhancement. Three levels
description
of coverage enhancement can counteract signal energy fading,
corresponding to Maximum Coupling Loss (MCL) values of 144dB,
154dB and 164dB.
Function ID No
Impact on device Uplink performance is improved.

performance
Impact on Uplink performance is improved.

network
performance

dependence
license?
Associated Number of PRACH and PUSCH retransmissions

parameter
Associated No
counter
Associated alarm No
and notification
Verification method: uplink GAP is on in default, there is no restriction

on the configuration of MCS and RU.
Verification
Service is normal, ping command is OK.
method and pass
Number of retransmissions adopted by ZTE Microelectronics
criterion
Institute:
144DB 154DB 164DB

Coverage Enhancement is required to deploy those NB-IOT UEs,

which locate at the edge of cells or basement where signal is very
weak. UEs can flexibly use frequency resource in three kinds of
Function
operation modes to implement Coverage Enhancement. Three levels
description
of coverage enhancement can counteract signal energy fading,
corresponding to Maximum Coupling Loss (MCL) values of 144dB,
154dB and 164dB.
PRACH 1 1 16
PUSCH 8RU 1 1 16
Impact on other No
functions
Remark Null
5.8.13 Support 2-Antenna MRC and IRC

Function Support 2-antenna MRC (Maximum Ratio Combining ) and IRC
description (Interference Rejection Combining)
Function ID No
Impact on device No
performance
Impact on No
network
performance
Hardware Number of antennas supported by RRU

dependence
license?
Associated No
parameter
Associated No
counter
Associated alarm No
and notification
Verification Configure 2 Rx antennas. Set MRC or IRC respectively. UE can be

Function Support 2-antenna MRC (Maximum Ratio Combining ) and IRC

description (Interference Rejection Combining)
method and pass attached successfully and can run ping command.
criterion
Impact on other No
functions
Remark Null
5.8.14 Support 3.75k/15k ACK Channel

Function Support 3.75K or 15K PUSCH Format2
description
Function ID No
Impact on device Performance is improved.

performance
Impact on network Retransmission delay is reduced. Performance risk is reduced.

performance
Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?
Associated Cell related parameters

parameter
Associated alarm No
and notification
In the situation of 3.75K/15K, UE runs ping command. Let wireless
Verification method environment become worse. Test ping command delay and packet loss
and pass criterion rate before and after enabling HARQ respectively. The two indexes are
improved after enabling HARQ.
Impact on other No
functions

Remark Null
5.8.15 CCE1 Supports NB-IoT Single Mode

Function CCE1 supports NB-IoT single mode
description
Function ID
Impact on device No
performance
performance
Hardware CCE1
dependence
Impact on the No
interface of an
associated network
element
license?
Associated No
parameter
Associated alarm No
and notification
1. At OMMB, configure CCE1 for an NB site. Physical entity is
CCE1.
Verification method
2. Configure CCE1 to work in NB-IoT single mode.
and pass criterion
3. In NB-IoT single mode, NB-IoT product process runs normally.
4. In correct configuration, NB-IoT product service is normal.
Impact on other No
functions
Remark Null
5.8.16 CCE1 Supports LN Hybrid Mode

Function CCE1 supports LTE and NB-IoT hybrid mode
description

Function ID
Impact on device No
performance
performance
Hardware CCE1
dependence
Impact on the No
interface of an
associated network
element
license?
Associated No
parameter
Associated alarm No
and notification
1. At OMMB, configure CCE1 for an NB site. Physical entity is
CCE1A.
2. Configure CCE1 to work in LN hybrid mode.
Verification method
3. In LN hybrid mode, LTE product process and NB-IoT product
and pass criterion
process run independently without mutual dependence.
4. In correct configuration, LTE product service and NB-IoT
product service can run properly without affecting each other.
Impact on other No
functions
Remark Null
5.8.17 BPN2 Supports NB-IoT Single Mode

Function BPN2 supports NB-IoT single mode
description
Function ID
Impact on device No
performance

performance
Hardware BPN2
dependence
Impact on the No
interface of an
associated network
element
license?
Associated No
parameter
Associated alarm No
and notification
1. Configure BPN2 to work in NB-IoT single mode.
2. When BPN2 is configured to work in NB-IoT single mode, cells
Verification method
under this BPN2 can be set up successfully and services in these
and pass criterion
cells are normal.
3. Single BPN2 can support up to 12 NB cells.
Impact on other No
functions
Remark Null
5.8.18 BPN2 Supports LN Hybrid Mode

Function BPN2 supports LN hybrid mode.
description
Function ID
Impact on device No
performance
performance
Hardware BPN2
dependence

Impact on the No
interface of an
associated network
element
license?
Associated No
parameter
Associated alarm No
and notification
1. Configure BPN2 to work in LTE and NB-IoT hybrid mode.
2. When BPN2 is configured to work in LTE and NB-IoT hybrid mode,
Verification method
LTE cells and NB-IOT cells under this BPN2 can be set up
and pass criterion
successfully and services in these cells are normal.
3. Single BPN2 can support up to 6 LTE cells + 6 NB-IoT cells.
Impact on other No
functions
Remark Null
5.8.19 Support BPN0A (Only for China Telecom and China Unicom)
Function BPN0A supports NB-IoT single mode

description
Function ID
Impact on No
device
performance
Impact on No
network
performance
Hardware BPN0
dependence
license?


description
Associated No
parameter
Associated No
counter
Associated No
alarm and
notification
1. In the network management system, configure BPN0A to work in
1. At OMMB, configure BPN0A to work in NB single mode.
Verification
2. Single BPN0A can support up to 6 NB-IoT cells.
method and
3. Both product process and management process are normal. Cell
pass criterion status is normal.
4. Services in the cells are normal.
Impact on other No
functions
Remark
5.8.20 BPN0_b supports NB-IoT Single Mode
Function BPN0_b supports NB-IoT single mode

description
Function ID No
Impact on device No
performance
Impact on No
network
performance
Hardware BPN2
dependence
license?
Associated No

Function BPN0_b supports NB-IoT single mode

description
parameter
Associated No
counter
Associated alarm No
and notification
1. At OMMB, configure BPN0_b to work in NB single mode.
Verification 2. Single BPN0_b can support up to 12 NB-IoT cells.

method and pass 3. Both product process and management process are normal. Cell status is
criterion normal.
4. Services in the cells are normal.
Impact on other No
functions
Remark Null
5.8.21 CC16B Supports NB-IoT Single Mode

Function CC16B supports NB-IoT single mode.
description
Function ID
Impact on device No
performance
performance
Hardware CC16B
dependence
Impact on the No
interface of an
associated network
element
license?
Associated No
parameter

Associated alarm No
and notification
1. At OMMB, configure CCC board for an NB site. Physical entity is
CC16B.
Verification method
2. Configure CC16B to work in NB-IoT single mode.
and pass criterion
Impact on other No
functions
Remark Null
5.8.22 CC16B Supports LN Hybrid Mode

Function CC16B supports LTE and NB-IoT hybrid mode.
description
Function ID
Impact on device No
performance
performance
Hardware CC16B
dependence
Impact on the No
interface of an
associated network
element
license?
Associated No
parameter
Associated alarm No
and notification

1. At OMMB, configure CCC for an NB site. Physical entity is CC16B.

2. Configure CC16B to work in LN hybrid mode.
Verification method 3. In LN hybrid mode, LTE product process and NB-IoT product
and pass criterion process run independently without mutual dependence.
4. In correct configuration, LTE product service and NB-IoT product
service can run properly without affecting each other.
Impact on other No
functions
Remark Null
5.8.23 CCE1A Supports NB-IoT Single Mode

Function CCE1A supports NB-IoT single mode.
description
Function ID
Impact on device No
performance
performance
Hardware CCE1A
dependence
Impact on the No
interface of an
associated network
element
license?
Associated No
parameter
Associated alarm No
and notification
1. At OMMB, configure CCE1 board for an NB site. Physical entity
is CCE1A.
Verification method
2. Configure CCE1A to work in NB-IoT single mode.
and pass criterion

Impact on other No
functions
Remark Null
5.8.24 CCE1A Supports LN Hybrid Mode

Function CCE1A supports LTE and NB-IoT hybrid mode.
description
Function ID
Impact on device No
performance
performance
Hardware CCE1A
dependence
Impact on the No
interface of an
associated network
element
license?
Associated No
parameter
Associated alarm No
and notification
1. At OMMB, configure CCE for an NB site. Physical entity is CCE1A.
2. Configure CCE1A to work in LN hybrid mode.
Impact on other No
functions
Remark Null

5.8.25 BPN1A Supports NB-IoT Single Mode

description
Function ID
Impact on device No
performance
performance
Hardware BPN1A
dependence
Impact on the No
interface of an
associated network
element
license?
Associated No
parameter
Associated alarm No
and notification
1. Configure BPN1A to work in NB-IoT single mode.
2. When BPN1A is configured to work in NB-IoT single mode, cells
Verification method
under this BPN1A can be set up successfully and services in these
and pass criterion
cells are normal.
3. Single BPN1A can support up to 6 NB cells.
Impact on other No
functions
Remark Null
5.8.26 Use USB Disk to Open a Site
Function NB supports site-opening via USB disk.

description
Function ID No

Function NB supports site-opening via USB disk.

description
Impact on device No
performance
Impact on No
network
performance
Hardware No
dependence
license?
Associated No
parameter
Associated No
counter
Associated alarm No
and notification
1. Run umaker tool on a PC to create mirror files, then save them to U-disk.
To open a site, insert this U-disk to the USB port on CC board. Run VMP
module to load mirror files to this site.
Verification To create mirror files, you must complete the following options.
method and pass 1) Select CC running mode: master/slave CC, radio mode load sharing,
criterion service load sharing.
2) Select corresponding platform and product specification package.
3) Export MODB file from OMMB.
2. This site runs properly and service is normal.
Impact on other No
functions
Remark Null
5.8.27 Support Uplink Frequency Hopping Function

Function The system supports cell-level and UE-level frequency hopping
description function.
Function ID

Impact on device Interference cancellation

performance
Impact on network Uplink performance is improved.

performance
Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?
1. Cell and UE uses different switch parameters.
2. Cell-level parameter
groupHoppingEnabled:open or close
groupAssignmentNPUSCH：0~29
3. UE-level parameter
Associated UEGroupHoppDisabledSwch：
parameter 0：Ue use cell-specific groupHopping parameter
1：Disable UE groupHopping
Associated alarm No
and notification
Verification method In the situation of 3.75k,15K frequency hopping configuration, UE can be

and pass criterion randomly accessed and attached. UE can run ping command.
Impact on other No
functions
Remark
5.8.28 CCE1 Supports GLN Hybrid Mode

Function CCE1 supports GLN hybrid mode
description

Function ID 1
Impact on device NB can initiate 1200 instances.

performance
performance
Hardware CCE1, BPN2, R8862A

dependence
Impact on the OMMB should install GLN version.

interface of an
associated network
element
license?
Associated G\L\N related wireless parameters and hardware configuration

parameter
Associated alarm No
and notification
1. At OMMB, configure a site to support GLN hybrid mode.
Verification method 2. In G/L/N hybrid mode, each product process runs properly.
and pass criterion 3. Each product service is normal.
4. G/L/N operations are independent from each other.
Impact on other No
functions
Remark Null
5.8.29 BPN2 Supports GN Hybrid Mode

Function BPN2 supports GN hybrid mode.
description
Function ID
Impact on device BPN2 supports up to 6 NB-IoT cells, up to 36 GSM carriers. GSM
performance and NB-IoT do not share the same BPN2 chip.
performance

dependence

Impact on the OMMB should install GLN version.

interface of an
associated network
element
license?
Associated Configure BPN2 to work in GN hybrid mode

parameter
Associated alarm No
and notification
1. At OMMB, configure a site to support GLN hybrid mode.
Verification method 2. In G/N hybrid mode, each product process runs properly.
and pass criterion 3. Each product service is normal.
4. G/N operations are independent from each other.
Impact on other No
functions
Remark Null
5.8.30 CC16D Supports NB-IoT Single Mode

Function CC16D supports NB-IoT single mode.
description
Function ID
Impact on device No
performance
performance
Hardware CC16D
dependence
Impact on the No
interface of an
associated network
element

license?
Associated No
parameter
Associated alarm No
and notification
1. At OMMB, configure CCC for an NB site. Physical entity is
CC16D.
Verification method
2. Configure CC16D to work in NB-IoT single mode.
and pass criterion
Impact on other No
functions
Remark Null
5.8.31 CC16D Supports LN Hybrid Mode

Function CC16D supports LTE and NB-IoT hybrid mode.
description
Function ID
Impact on device No
performance
performance
Hardware CC16D
dependence
Impact on the No
interface of an
associated network
element
license?
Associated No
parameter

Associated alarm No
and notification
1. At OMMB, configure CCC for an NB site. Physical entity is CC16D.
2. Configure CC16D to work in LN hybrid mode.
Impact on other No
functions
Remark Null
5.8.32 BPN2A Supports N Single Mode and LN Hybrid Mode

Function BPN2A supports N single mode and LN hybrid mode.
description
Function ID No
Impact on device No
performance
performance
Hardware BPN2A
dependence
Impact on the No
interface of an
associated network
element
license?
Associated No
parameter
Associated alarm No
and notification

1. Configure BPN2A to work in NB single mode and LN hybrid mode.

2. When BPN2A is configured to work in NB and LN hybrid mode, FDD
Verification method cells and NB cells under this BPN2A can be set up successfully and
and pass criterion services in these cells are normal.
3. BPN2A can support up to 6 NB cells. In LN hybrid mode, BPN2A
can support up to 3L+3N cells.
Impact on other No
functions
Remark Null
5.8.33 Number of NB RRC Instances Supported by CC

Name of Board N LN GN GLN GUN ULN
CCE1 15000 3600 10800 1200 3600 1200
CCE1A (GPS module on
CCE1 is replaced with 15000 3600 10800 1200 3600 1200
Beidou module)
CCE0C (Based on CCE1,
dedicated for China
15000 3600 10800 1200 3600 1200
Unicom and China
Telecom)
CC16B 15000 3600 10800 1200 3600 1200
CC16D (GPS module on
CC16B is replaced with 15000 3600 10800 1200 3600 1200
Beidou module)
5.8.34 3.75K SINR and Power Measurement Reporting
Function Signal power and noise power are reported at PHY side.
CMAC uses the signal power and noise power to calculate
description SNR. SNR and noise floor are reported to OMMB.
Function ID No
Impact on device No
performance
performance

Hardware
dependence
Impact on the No
interface of an
associated network
element
license?
Associated Create relevant measurement task in EMS

parameter
Associated alarm No
and notification
A signal source constantly sends signals with fixed energy. The signal is
Verification method
saved at PHY side and is calculated. Check signal power, noise power
and pass criterion
and noise floor and make sure the values are correct.
Impact on other No
functions
Remark
5.8.35 Support eDRX Function
Function UE supports eDRX function. This UE negotiates with MME.

MME sends eDRX relevant parameters to eNodeB via a
description paging message.
Function ID No
Impact on device No
performance
performance

dependence
Impact on the No
interface of an
associated network
element

license?
In UE Paging interface, set starting time for hyper system frame

number: E-UTRAN Service configuration --- UE paging-- Begin
Time for which H-SFN to 0(UTC,Format:YYYY-MM-dd
HH:mm:ss)
Associated
parameter
Associated alarm No
and notification
1. At OMMB, configure a site to support GLN mode.
2. In G\L\N working mode, each product process runs properly.
3. Each product service is normal.
4. G/L/N operations are independent from each other.
Verification method
5. Configure Begin Time for H-SFN. The configuration should be kept
and pass criterion
consistency with CN. The default value is 2000-01-01 00:00:00
(YYYY-MM-dd HH:mm:ss) at CN side.
6. Verify paging process is normal.
7. 12bitNB-IOT UE-ID is carried in S1 paging message.
Impact on other No
functions
Remark
5.8.36 Support Connection State SR (Scheduling Request)
Function UE sends uplink data during RRC connection state. If it has

not obtained UL grant, it initiates PRACH access. eNodeB
description allocates UL wireless resource to this UE.
Function ID No

Impact on device No
performance
performance

dependence
Impact on the No
interface of an
associated network
element
license?
Associated No
parameter
Associated alarm No
and notification
1. UE is attached to the network. UE initiates ping command at
connection state. Because it has no UL wireless resource, it
Verification method
sends accessing message over PRACH.
and pass criterion
2. eNodeB allocates UL wireless resource to this UE.
3. UE succeeds in sending ping request.
Impact on other No
functions
Remark
5.8.37 Redirection Based on the number of RRC Connections

Function Redirection based on the number of RRC connections
description
Function ID No
Impact on device No
performance
Impact on network Control network congestion and keep balanced load

performance

Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?
Associated cellPermitTotalRrcNum
parameter
Associated counter C596080950, C596080951, C596080952
Associated alarm
and notification
1. Test redirection after admission failure:
1) Open cell admission control interface at OMMB, set
cellPermitTotalRrcNum to 1
2) Attach one UE. Wait until inactive timer is time out and
connection is released.
3) View X1-port release code and check whether it carries
redirection information.
[X1_RRC_CONNECTION_RELEASE_Len]:5
[X1_RRC_CONNECTION_RELEASE_CodeStream]: 28
23 00 E9 C2
Notes: RRM is fixed to write dwCenterFreq = 935,
carrierFreqOffset_r13 = 1. Decode the information and
check whether it is correct.
Verification method
and pass criterion
2. Test S1 reset caused redirection:
1) Attach one UE. Open dynamic management interface and

reset SCTP.
2) View whether UE is released and operates redirection.
3) Telnet and print: CPM_S1inst_Sctp_Reset_Handle
4) View X1-port release code and check whether it carries

redirection information:
[X1_RRC_CONNECTION_RELEASE_Len]: 5
[X1_RRC_CONNECTION_RELEASE_CodeStream]: 28
23 00 E9 C2

Impact on other No
functions
View signaling trace information to get precise redirection code. If

Remark you use CC print to get redirection code, the information is not
fixed because header content changes.
5.8.38 15K SINR and Power Measurement Reporting
Function Signal power and noise power are reported at PHY side.
CMAC uses the signal power and noise power to calculate
description SNR. SNR and noise floor are reported to OMMB.
Function ID 3
Impact on device No
performance
performance
Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?
Associated Create relevant measurement task in EMS

parameter
Noise interference counter (added in a patch), PUSCH SINR
Associated counter
counter
Associated alarm No
and notification

PHY reports signal power and band noise. CMAC calculates the average
SINR.
PHY reports measured idle noise. CMAC calculates an average value
Verification method and reports it to a counter at OMMB. Then view the value of this counter
and pass criterion to get idle noise at OMMB.
Use a spectrum analyzer: PHY reports signal power, band noise and idle
noise. In this test, the noise is normal.
Impact on other No
functions
Remark
5.8.39 Support UL/DL AMC

Function According to the change of channel quality, this system automatically
selects MCS/RU/REP according to UE UL/DL service. The purpose is to
description control service BLER and better use wireless resources.
Function ID No

performance
Impact on network Network is optimized.

performance
Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?
Associated Cell parameter
parameter
Associated alarm No
and notification
Verification method Several UEs run services. Adjust the strength of wireless signals, then
and pass criterion observe CMAC and L3 statistics.

Impact on other No
functions
Remark Null
AMC configuration:
5.8.40 Configure the Number of Tones Over a Sub-carrier Space

Function Configure the number of tones over a sub-carrier space
description
Function ID 3


performance

performance
Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?
Associated Cell related parameters, auto-adaption, 7 kinds of multi-tone

parameter configuration
Associated alarm No
and notification
Verification method Change the configuration of PUSCH in a cell. Enable HARQ and execute
and pass criterion PING command.
Impact on other No
functions
Remark Null
5.8.41 Admission Control Based on UL PRB

Function UE admission control is better implemented to fully use of UL
description PRB (Physical Resource Block).
Function ID No

performance
Impact on network Network congestion is controlled.

performance
Hardware No
dependence

Impact on the No
interface of an
associated network
element
license?
Associated Cell parameter

parameter
Associated alarm No
and notification
5.8.42 Support 3.75K Even Subframe Scheduling

Function 3.75k even subframe scheduling is implemented according to
description 3GPP standard specification.
Function ID

performance
performance
Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?
Associated No
parameter
Associated alarm No
and notification
Verification method In the situation of 3.75K configuration, UE runs ping command. Service is
and pass criterion normal. Scheduling sub-frame number starts from an even value.

Impact on other No
functions
Remark UE version should support even subframe scheduling function.
5.8.43 EAB Admission Control Based on the Number of RRC Connections
Function When the number of RRC connects reaches a defined

threshold, the system only allows the UE to be accessed,
description which belongs to callee type and has service request.
Function ID

performance
Impact on network
performance
Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?
Associated
parameter
Associated alarm No
and notification
Verification method Configure a small access threshold

and pass criterion
Impact on other No
functions
Remark

5.8.44 Optimize Paging Process

Function Optimize paging process
description
Function ID 3
Impact on device Paging success rate in different cells are improved.
performance

performance
Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?
Associated No
parameter
Associated alarm No
and notification
1. RNLC sends a Release message to MME. This message carries
coverage level and adjacent cell information.
2. MME initiates paging message to RNLC. This message carries

Verification method coverage level and adjacent cell information.
and pass criterion 3. RNLC sends paging message to RNLU according to adjacent cell
information. This message carries coverage level and number of
retransmissions.
4. CMAC schedules paging message according to the coverage level.
Impact on other No
functions
Remark Null

5.8.45 Configure AMC B-type Parameters

Function Configure AMC B-type parameters
description
Function ID
Impact on device No
performance
performance
Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?

R_CMACB table parameters:

ucENodeBIdx
dwUlContinualScheThrd
dwDlContinualScheThrd
dwPriDebug
ucMinPermitReptNumCEL0
ucSupportMcs11
ucCel2_Flag
ucCel1_Flag
ucCel0_Flag
ucIsAmcUlSetBsr
dwAmcUlReqBsr
aucCel2UlMCS[4]
aucCel2UlNsf[4]
awCel2UlRepeRm[4]
awCel2UltbSize[4]
aucCel1UlMCS[4]
aucCel1UlNsf[4]
Associated awCel1UlRepeRm[4]
parameter awCel1UltbSize[4]
aucCel0UlMCS[4]
aucCel0UlNsf[4]
awCel0UlRepeRm[4]
awCel0UltbSize[4]
aucCel2DlMCS[4]
aucCel2DlNsf[4]
awCel2DlRepeRm[4]
awCel2DltbSize[4]
aucCel1DlMCS[4]
aucCel1DlNsf[4]
awCel1DlRepeRm[4]
awCel1DltbSize[4]
aucCel0DlMCS[4]
aucCel0DlNsf[4]
awCel0DlRepeRm[4]
awCel0DltbSize[4]
ucset_pdcch_R_manually
ZTE Confidential & Proprietary ucIsAmcDlSetBsr 187
dwAmcDlReqBsr
ucIsUseAmc
Associated alarm No
and notification
Verification method Use DV function to change parameters at OMMB. Then deliver the
configuration to eNodeB. Login eNodeB and type debug command to
and pass criterion
view the corresponding parameters.
Impact on other AMC function

functions
Remark Null
5.8.46 Support UP Basic Function

Function Support UP basic functions
description
Function ID
Impact on device No
performance
performance
Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?
Associated No
parameter
Associated alarm No
and notification
Verification method After UP access, UE can run ping command in connection state.
and pass criterion

Impact on other No
functions
Remark Telnet CC process and type activeUECap command.
5.8.47 Support UP Suspending and Resuming Process

Function Support UP suspending and resuming process
description
Function ID
Impact on device No
performance
performance
Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?
Associated No
parameter
Associated alarm No
and notification
UP is accessed to the network. When inactive timer is time out, this

Verification method triggers suspending process. When UE sends a ping request, this
and pass criterion triggers resuming process. After the resuming operation is successful,
ping command can be normally executed.
Impact on other No
functions
Remark Null
5.8.48 OMMB Supports PNP

Function Support eNodeB site auto-opening function

description
Function ID ZNF45-01-001
Impact on device No
performance
performance
Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?
PnP policy configuration rules

Associated Parameter configuration rules for transmission link auto-setup
parameter function
DHCP parameter configuration rules
Associated alarm No
and notification

Pre-conditions:
1) eNodeB running version is the same as that configured at OMMB, for
example, LN site is configured.
2) At eNodeB side, view its running version information and make sure
the transmission link auto-setup switch is on (DHCP packet is reported).
1) Configure DHCP SERVER parameters at OMMB, including eNodeB
IP information.
2) Configure PNP policy at OMMB and deliver this policy to eNodeB.
3) eNodeB is powered on.
Verification method 4) DHCP link is automatically set up between eNodeB and OMMB.
eNodeB version is upgraded according to the PNP policy. Configuration
and pass criterion
parameters are delivered to eNodeB.
Pass criterion:
1) DHCP link is set up successfully between eNodeB and OMMB.
2) eNodeB version is upgraded according to the configured PHN policy
and configuration parameters are successfully delivered to eNodeB. If
eNodeB runs the same version as that configured at OMMB, it is
unnecessary to upgrade the version.
3) Check whether eNodeB runs the same version as that configured at

OMMB. Check whether the configuration parameters are kept
consistency between eNodeB and OMMB.
Impact on other No
functions
Remark Null
5.8.49 BPN1_A Supports N and LN

Function BPN1_A supports N and LN.
description
Function ID No
Impact on device No
performance
performance
Hardware BPN1_A, based on BPN2

dependence

Impact on the No
interface of an
associated network
element
license?
Associated No
parameter
Associated alarm No
and notification
1. Configure BPN1_A to work in NB and LN hybrid mode.
2. When BPN1_A is configured to work in NB and LN hybrid mode,
Verification method FDD cells and NB-IOT cells under this BPN1_A can be set up
and pass criterion successfully and services in these cells are normal.
3. Single BPN1_A can support up to 6 NB cells in NB mode, 3L+3N
cells in LN hybrid mode.
Impact on other No
functions
Remark Null
5.8.50 OMMB Supports NB License

Function NB license can be controlled by OMMB.
description
Function ID No
Impact on device No
performance
performance
Hardware No
dependence
Impact on the No
interface of an
associated network
element

license?
Associated No
parameter
OMMB related alarms:

License consumption exceeds alarm threshold (1034)
Associated alarm
License is expired
and notification
License will expire soon
The link between OMMB and license center is interrupted.
1. Design test cases according to control item algorithm and involved
scope, covering normal scenario, special scenario, out of license
limit. Refer to “NB-IoT License control item algorithm design
scheme_V4.16.10.20P10” for algorithm scheme.
2. Build license environment: create test data for control items. Apply
for license file.
Verification method 3. Conduct the test according to test cases. View license information at
and pass criterion OMMB. Calculate license information for each test case by hand.
Compare the difference.
Pass criterion:
1. For each test item, license data displayed at OMMB is the same as
that calculated by hand.
2. Check whether the license is out of limit. The detected license data
should matches with that defined in license file.
Impact on other No
functions
Remark
5.8.51 Support CCE1B Board

Function The system supports CCE1B 4G memory
description
Function ID

Impact on device no
performance
performance
Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?
Associated no
parameter
Associated alarm No
and notification
NB Single Mode Configure 36 Cell 144000 RRC
Verification method LN Mode Configure 36 Cell 7200 RRC

and pass criterion
GLN Mode Configure 36 Cell 7200 RRC
Impact on other
functions
Remark
5.8.52 Support FS5B Borad

Function The system supports FS5B Board
description
Function ID
Impact on device Not support SRIO switching

performance
performance

Hardware No
dependence
Impact on the No
interface of an
associated network
element
license?
Associated no
parameter
Associated alarm No
and notification
1. At OMMB, configure CCE for an NB site. Physical entity is
CCE1B.
Verification method 2. Configure CCE1B to work in NB-IoT single mode.
and pass criterion 3. In NB-IoT single mode, NB-IoT product process runs normally.
In correct configuration, NB-IoT product service is normal.
Impact on other
functions
Remark
5.8.53 Support LN Same SCTP Associated

Function
description
Function ID
Impact on device No
performance
performance
Hardware No
dependence

Impact on the No
interface of an
associated network
element
license?
Associated no
parameter
Associated alarm No
and notification
Configuration for LTE and NB-IoT community of common coupling and
Verification method S1AP,NB-IoT - related business
and pass criterion
Impact on other
functions
Remark


6 Solved Defects
6.1 Solved GU Defect List
Table 6-1 solved GU defect list
Defect No. Defect Name Level Mode Solve

Version
614005138472 SCTP Message Retransmission Rate is General UMTS 4.16.10.20P20
wrongly calculated
614005548292 Impose Constraints on 4-diversity General UL 4.16.10.20P20
614005425385 After Upgrading from V4.15 to V4.16, General UL 4.16.10.20P20
Antenna Supporting Capability of R8119
F1821A is Changed from 4 Channels to 6
Channels. The Relevant Configuration at
OMMB Has to be Changed Mannually.
614005369159 Operator 1 HSDPA Power is Wrongly General UMTS 4.16.10.20P20
Counted
614005613071 When BPN2 Service Mode is Changed General UL 4.16.10.20P20
from Non-UMTS to Including UMTS,
Inter-BP User Service Becomes Abnormal
614005612833 CR0 at Slot 4 is Wrongly Recognized, General UMTS 4.16.10.20P20
Causing DPA Rate = 0
614005612751 After Replacing BPC With BPK in a Site, General UMTS 4.16.10.20P20
RACH BLER Rises
614005612154 HSPA UEs Fails to Access a High-load Serious UMTS 4.16.10.20P20
Site. This Situation Cannot be Recovered.
614005462293 In the Configuration of BPC Board, Drop General UMTS 4.16.10.20P20
Call Rate Becomes Worse in 2.5Km
Coverage Radius and High-speed Cell
614005469482 R8892E M1821 Does not Support Rx General UMTS 4.16.10.20P20
Spectrum Analysis and Carrier Spectrum
Analysis in OMMB RF Analysis Function
614005681593 BPN2 Delay Measured is a little larger General UMTS 4.16.10.20P20
614005821686 Some Sites Are Configured with CCA. After Serious PLAT 4.16.10.20P20
Running FCE Hot Patch, These Sites
Repeatedly Reset

614005681665 BPN2 Resets Serious UMTS 4.16.10.20P20
614005781455 UE cannot access to the network When the Serious GSM 4.16.10.20P20
VAMOS switch is on
614005781458 In the situation that R8892N is used, General GSM 4.16.10.20P20
uplink RQ becomes worse.
614001285426 When CR0 boardfunctionmode is General UMTS 4.16.10.20P30
configured to be LTE-FDD CloudRadio[5],
KPIs may decrease and CE resources may
become insufficient in UMTS large-traffic
sites.
614003322051 In IPA Configuration, Some Handsets Drop General GSM 4.16.10.20P10
Calls During Ringing Period.
614005564065 The TA value in the cell is a little larger. General GSM 4.16.10.20P30
614005895200 When Running PIM Detection Function in a General PLAT 4.16.10.20P40

Batch, Many Sites Return Serious Alarm
State
614005893205 Optimize the Statistical Value of CPICH General UMTS 4.16.10.20P40
Average Power Counter
614005896225 When signal quality is poor, DTX ratio is General UMTS 4.16.10.20P40
high for HSDPA UEs
614006039083 In a multi-mode site, after General UMTS 4.16.10.20P40
incrementally changing GSM or LTE
configuration data such as GSM IP or LTE
IP, new UEs cannot access to UMTS
site.
614005564104 Transmission link changeover causes General GSM 4.16.10.20P50
GSM process to become abnormal and
reset
614001225426 CSSR KPI keeps abnormal when IUB General UMTS 4.16.10.20P20
Transmission recovers from congestion
614005628357 There is a problem of abnormal statistical Serious PLAT 4.16.10.20P20
indicators in two sites of Algeria
614005628978 Average CPU Usage of the CC Board on Serious PLAT 4.16.10.20P40
the eNodeB Is Greater Than 100% and
Displayed As 3000%
614006131267 When NodeB reboots or BPN2 board Serious UMTS 4.16.10.20P60
reboots,there is a small probability that
RLC retransmission rate reaches 100%
in some cells, but HSDPA throughput
approximates to 0.

614006129366 Activate TWAMP monitoring function. General PLAT 4.16.10.20P20

Several sites have packet loss and jitter
problem in the uplink direction.
614006152832 C370130001 (link connection time between General PLAT 4.16.10.20P60
Node B and OMCB) becomes abnormal on
Algeria’s network. Occasionally the value
shown in EMS is 1200 seconds.
614006152128 After putting 900M 2T cells into operation, General UMTS 4.16.10.20P50
some cells are repeatedly deleted and set
up.
614006161401 Some brands of UEs process uplink DTX General GSM 4.16.10.20P60
abnormally, causing small MOS
614006161402 In the coordinated configuration of UBPG1 Serious GSM 4.16.10.20P60
board and R8863 baseband
combined-cabinet mode, partial carriers
have no power output in downlink direction
614006161403 In the configuration of R8863 baseband Serious GSM 4.16.10.20P60
combined-cabinet mode, carrier intelligent
shutdown function has a defect
614006301725 In the environment that dual-CC is General UMTS 4.16.10.20P80
configured and FCE is connected to
RSU40 U216, FCE reports an alarm,
indicating software runs abnormally
614005688238 After eNodeB reconfigure or reset, CSSR General UMTS 4.16.10.20P80
degraded in some cells
614005685618 In some sites, BPK-d repeatedly reports General UMTS 4.16.10.20P80
“software runs abnormally” when traffic is
busy
614002730422 BPN board may reset when CPU Load is General UMTS 4.16.10.20P80
high
614006354457 BPN2 Resets due to an error in RL General UMTS 4.16.10.20P80
multipath searching process
614003560608 BPN2 resets at high service load General UMTS 4.16.10.20P80
614006257030 NodeB site is equipped with CCE1 board. Serious PLAT 4.16.10.20P81
After activating IPSEC function, this NodeB
irregularly resets
614006175541 If configuring multiple IPSEC paths, only General PLAT 4.16.10.20P81
one IPSEC path is normal
614006079481 In IPSEC path backup scenario, Node B General PLAT 4.16.10.20P81
repeatedly reports “IPSec link abnormal”

alarm.
614006344240 An input power problem of R8852 causes Serious PLAT 4.16.10.20P81

wrong PA protection and no output power
614006490856 In the situation of interoperation between Serious PLAT 4.16.10.20P81
SUN server and BBU, IMSI-based Log
collection fails.
614006490856 In dual-CC dual-master situation, some Serious PLAT 4.16.10.20P81
fans in FCE may rotate at abnormal speed
614005737391 Avoid a fault caused by broken RF switch General UMTS 4.16.10.20P81

6.2 Description of GU Solved Defects
6.2.1 SCTP Message Retransmission Rate is wrongly calculated

Defect No. 614005138472
Defect level General
Introduced version NB_V4.14.10.30
Run EMS to view SCTP message retransmission rate (counter
Phenomenon number = 307012). In some scenarios, this index exceeds
100%.
This counter does not precisely indicate real SCTP message
Influence
retransmission rate. This misleads a wrong action.
SCTP message retransmission rate is expressed as n1/n2,
where n1 is number of timeout-caused retransmitted packets
plus number of fast retransmitted packets, n2 is number of
totally transmitted messages. In old codes, n2 is wrongly
Reason analysis
counted, not considering the fact that some packets may be
retransmitted more than one time, i.e. timeout-caused
retransmitted packets and fast retransmitted packets are not
included. Thus, calculation result is inaccurate.
Modify the codes so that n2 contains number of
Solution timeout-caused retransmitted packets and number of fast
retransmitted packets.
External verification The calculated SCTP retransmission rate falls in a normal
method range.
Remark
6.2.2 Impose Constraints on 4-diversity

Defect No. 614005548292
In V4.15.10.30P10, there is a problem in the configuration of
R8881 S2100 4U+1L combined cabinet. The constraints on
Phenomenon
4-diversity are not implemented. And the configuration can be
delivered to NodeB.
Diversity antenna is unavailable. This affects service
Influence
performance.
Reason analysis The constraints on 4-diversity are not implemented.
Solution Impose the following constraints for 4-diversity configuration:

R8882 RSU82 UL can only use primary antenna.

R8881 S2100(B8B) R8881 S2100(B8C)4U+1L supports
combined-cabinet configuration and only primary antenna
can be used.
R8863 S2100(A8A) supports combined-cabinet
configuration and its UL can only use primary antenna.
1. In UL 4-diversity configuration, R8881 and R8863 are not
External verification allowed to configure diversity antenna.
method 2. In UL scenario, R8882 RSU82 is not allowed to configure
diversity antenna.
Before upgrading the version, any 4-diversity configuration
Remark must be corrected to remove the configuration of diversity
antenna.
6.2.3 After Upgrading from V4.15 to V4.16, Antenna Supporting Capability of R8119
F1821A is Changed from 4 Channels to 6 Channels. The Relevant Configuration at
OMMB Has to be Changed Mannually.
Defect No. 614005425385
After version upgrading, the antenna supporting capability of
R8119 F1821A is changed from 4 channels to 6 channels. The
Phenomenon
relevant configuration at OMMB cannot be converted
automatically.
The configuration data has to be changed manually.
Influence
Otherwise, LTE services will be interrupted.
In old version, OMMB shows that R8119 F1821A supports 4
channels. Among the 4 channels, 2 are UL-shared channels.
In the new version, R8119 F1821A supports 6 channels and
Reason analysis
UL channels are separated. During upgrading process, the
configuration data is not automatically converted. Therefore, it
needs to be changed manually.
First, delete the network element - R8119 F1821A from
Solution OMMB. Second, create it again and set 6-channel
configuration. At last, load this configuration data to NodeB.
External verification Load the configuration data. And OMMB shows that R8119
method F1821A supports 6 channels.
Remark This defect exists in V4.15.10.30 and previous version.

6.2.4 Operator 1 HSDPA Power is Wrongly Counted

Defect No. 614005369159
C372490311 is used to count operator 1 HSDPA average
power. When there is only one operator, two counters have big
Phenomenon
difference: “Operator 1 HSDPA average power” and “Cell DPA
total average power”.
Influence This counter value is wrong.
Reason analysis Only HSDPA data channel power is counted.
Both HSDPA data channel power and control channel power
Solution
are counted.
Observe the values of the two counters:
External verification
C372490310 Cell HSDPA total average power
method
C372490311 Operator 1 HSDPA average power
Remark
6.2.5 When BPN2 Service Mode is Changed from Non-UMTS to Including UMTS,
Inter-BP User Service Becomes Abnormal
Defect No. 614005613071
Introduced version Always exist
In original configuration, BPN2 works in single LMT or
non-UMTS service mode. Later, the configuration is changed
Phenomenon so that UMTS is included. When both BPKD and BPN provide
services to a UE, service becomes abnormal, causing RL
setup failure and RL reconfiguration failure.
Influence DPA RL setup fails and RL reconfiguration fails.
When BPN2 service mode is changed from non-UMTS to
including UMTS, the new board information is not timely
Reason analysis
notified to other BP boards. This causes inter-BP UE service to
become abnormal.
Perform entire-table synchronization operation on a
commercial site.
Solution
Modify the process so that service mode change will trigger
baseband parameter reconfiguration.
In hybrid configuration of BPN2 and other type of BP board,
when BPN2 service mode is changed from non-UMTS to
method
including UMTS, services are normal.

Remark Null
6.2.6 CR0 at Slot 4 is Wrongly Recognized, Causing DPA Rate = 0

Defect No. 614005612833
Introduced version 4.15.10.10
Phenomenon CR0 at slot 4 is wrongly recoginized, causing DPA rate = 0.
Influence The system fails to run DPA inter-board services.
CR0 is inserted at slot 4. At slot 3, it is a non-FS board or is an
FS board with lower capability than CR0. In this configuration,
Reason analysis
CR0 is wrongly recognized. HSDPA scheduler fails to obtain
inter-board CQI information. This affects scheduling function.
Solution Correct CR0 is recoginized.
External verification CR0 is configured at slot 4. Configure several BP boards in
method CR0 related cell. Cell DPA service is normal.
Remark Null

6.2.7 After Replacing BPC With BPK in a Site, RACH BLER Rises
Defect No. 614005612751
After replacing BPC with BPK in a site, RACH BLER rises
Phenomenon
slightly.
Influence Compared to BPC/BPN2, BPK brings higher RACH BLER.
BPK processes RACH wrong packets differently from
BPC/BPN2. BPK does not adopt RACH wrong-packet
Reason analysis
optimization algorithm. This difference brings different RACH
BLER between BPK and BPC/BPN2.
Solution BPK adopts RACH wrong-packet optimization algorithm.
A site is configured with BPK. Upgrade this site from lower
External verification version to V4.16, RACH BLER index slightly decreases. But
method this index does not show big difference between BPK and
BPC/BPN2RACH.
Remark Null
6.2.8 HSPA UEs Fails to Access a High-load Site. This Situation Cannot be
Recovered.
Defect No. 614005612154
Defect level Serious
HSPA UEs fails to access a high-load site. Many failures occur
Phenomenon due to NodeB. And the number of DPA UEs becomes 0. When
service traffic falls, this situation cannot be recovered.
Influence UEs cannot run HSPA services in some cells.
Reason analysis In high-load situation, CPU overload tag is wrongly set.
When CPU high-load information is reported, NodeB refuses
new RL setup request. Thus new UEs cannot access to the
Solution
high-load site. Later when the CPU load falls, new UEs can
access to it.
External verification When the load in a high-load site falls, service index becomes
method normal.
Remark
6.2.9 In the Configuration of BPC Board, Drop Call Rate Becomes Worse in 2.5Km Coverage
Radius and High-speed Cell

Defect No. 614005462293

In the configuration of BPC board, drop call rate becomes
Phenomenon
worse in 2.5Km coverage radius and high-speed cell.
In the configuration of BPC board, drop call rate in the
Influence
high-speed cell with 2.5Km radius is affected.
BPC board is configured and the high-speed cell has 2.5Km
Reason analysis
coverage radius. PRACH delay calculation has a defect.
Solution Modify the calculation defect to get correct PRACH delay.
External verification In the scenario of BPC and 2.5 Km-radius high-speed cell,
method observe whether drop call rate is normal.
Remark Null
6.2.10 R8892E M1821 Does not Support Rx Spectrum Analysis and Carrier Spectrum Analysis in
OMMB RF Analysis Function
Defect No. OC20170215318300
Introduced version V4.15.10.20
 R8892E M1821 does not support Rx spectrum and carrier
Phenomenon spectrum analysis in OMMB RF analysis function.
 In OMMB UDT, LTE spectrum scanning function provides low

resolution. It is impossible to use OMMB RF analysis function
Influence to scan UL frequency. Interference signal is hard to be
diagnosed.
At early stage, R8892E M1821 only supports LTE frequency

Reason analysis
scanning mode provided in OMMB UDT.
 In V4.15.30P30, R8892E M1821 supports Rx spectrum
analysis and carrier spectrum analysis provided in OMMB RF
Solution analysis function. These types of RRUs are involved:
R8402\R8892E\R8602
 Verify whether R8892E M1821 can support Rx spectrum

External verification analysis and carrier spectrum analysis in OMMB RF analysis
method function.
Remark Null

6.2.11 BPN2 Delay Measured is a little larger

Defect No. 614005681593

Introduced version V4.14
The measured BPN2 Propagation delay is inaccurate. RTT (Round
Phenomenon
Trip Delay) measured at BPN2 is a little larger.
UMTS service may not be accessed. And Statistical Propagation
Influence
Delay is a little larger
Reason analysis The measured BPN2 delay is inaccurate.
Solution Update BPN2 reported RTT value.
1. Configure a site with BPN2, then measure RTT value.

2. Stastical Propagation Delay interval may change, PD step1 may
method
increase after upgrade to UR16.
Remark
6.2.12 Some Sites Are Configured with CCA. After Running FCE Hot Patch,
These Sites Repeatedly Reset.
Defect No. 614005821686
Some Sites are configured with CCA. After runningFCE hot patch, these sites
Phenomenon repeatedly reset. In these sites, one RRU is configured with several tower
mounted amplifiers (TMA).
Influence These sites cannot work properly.
If one RRU is configured with 5 or more TMA devices, an asset module will
Reason analysis
have an out-of-bound access problem.
Modify relevant codes so that the asset module uses correct address to
Solution
access memory.
External verification One RRU is configured with 5 or more TMA devices. Let the RRU link be
method interrupted for 20-60 minutes. Then set up the link again. CC is normal.
Remark

6.2.13 BPN2 Resets

Defect No. 614005681665
Introduced version Unknown
Phenomenon BPN2 resets
Influence Because BPN2 resets, all the services borne on the board are interrupted.
UE dedicated measurement is implemented with codes. These codes have

Reason analysis
a logic error. Assert command triggers BPN2 to reset.
Solution Modify RL de-activation process.
External verification Use multiple UEs to initiate basic services. UE repeatedly set up services.
method Services are normal,KPIs are normal. BPN2 does not reset.
Remark
6.2.14 UE cannot access to the network When the VAMOS switch is on
Defect No. 614005781455

In a NodeB site, BP type is BPN2, RRU type is R8892N/R8854.
Phenomenon
When the VAMOS switch is on, UE cannot access to the network.
Influence UE cannot access to the network.
The VAMOS switch is on and RRU type is R8892N/R8854. In
this situation, next-frame power switch = off is sent from BPN2.
Reason analysis This brings an outcome –transmission power on BCCH is on
over the first two slots, it is off over the rest 6 slots. This causes
UE access fails.
If the VAMOS switch is on, set next-frame power switch = on
Solution
and power level = 0.
Run the patch. Set the VAMOS switch on. Then observe
whether UE can access to the network properly, whether
method
services are normal.
Remark NULL

6.2.15 In the situation that R8892N is used, uplink RQ becomes worse

Defect No. 614005781458

In the situation that R8892N is used, uplink RQ becomes
Phenomenon
worse.
Influence Uplink RQ is affected.
To locate a reason, R8892N adjacent channel interference index
Reason analysis is measured. Even though this index meets 3GPP standard, its
value is slightly low.
Optimize uplink GSM signal shaping filter so as to suppress
Solution
adjacent channel interference signal.
External verification Run the patch. Then observe whether uplink RQ is improved.
method
Remark NULL
6.2.16 When CR0 boardfunctionmode is configured to be LTE-FDD

CloudRadio[5], KPIs may decrease and CE resources may become insufficient
in UMTS large-traffic sites
Defect No. 614001285426

CR0 boardfunctionmode is configured to be LTE-FDD
CloudRadio[5]. Because UMTS cell auto-allocation
algorithm does not support such CR0 configuration, UMTS
Phenomenon cell auto-allocation becomes unbalanced. This may bring
several problems in high-traffic UMTS sites: CE is
congested, KPIs decrease and CE resources are
insufficient.
This may cause congested CE, decreased KPIs and
Influence
insufficient CE resources in high-traffic UMTS sites.
If CR0 boardfunctionmode is configured to be
LTE-FDDCloudRadio[5], the algorithm will deem that CR0
does not support UMTS cells. In this case, the
auto-allocation algorithm will adopt FS minimum allocation
Reason analysis
policy, i.e. BPN only supports 6 STSR cells and does not
support inter-board function. As a result, inter-board
resources cannot be shared, UMTS service encounters CE
congestion problem and KPIs decrease.

1. The system checks radio mode according to radiomode,

Solution rather than boardfunctionmode.
2. Allocate BP boards manually to avoid this problem.
1. Configure CR0 at slot 3/4. The content of radiomode
contains UMTS. Configure boardfunctionmode to be
LTE-FDD CloudRadio[5].
2. Configure one BPN2 board, which operates only in
method
UMTS mode.
3. Configure more than 6 STSR cells. There is no a
message that indicates insufficient resources.
After upgrading NodeB version from V4.15 to V4.16, the
following phenomenon occurs if changing data
configuration and synchronizing the configuration for the
Remark first time. Because of the above change, the relation
between UMTS cells and BP boards must be re-allocated,
cells are deleted and added, services are interrupted for the
moment.
6.2.17 In IPA Configuration, Some Handsets Drop Calls During Ringing Period

Defect No. 614003322051

Introduced version 4.13.10
In IPA configuration, a lab test finds a problem - some
Phenomenon
handsets easily drop calls during ringing period.
Influence Drop call rate is affected.
In IPA configuration, if a handset does not receive a DL
speech frame, frequency offset phenomenon may occur
during ringing period. As ringing time extends, frequency offset
Reason analysis becomes bigger. In serious situation, the call drops. However if
Node B actively sends some SID frames to the handset during
the ringing period, the frequency offset can be calibrated and
drop call problem can be avoided.
If no DL speech frame is sent during ringing period, Node B
Solution
actively sends SID frame to the handset.
External verification Upgrade the version. Then observe whether a handset has the
method dropped call problem when it rings for a long time.
Downlink RQ will become worse slightly. Enable/disable this
Remark
function through parameter.
6.2.18 The TA value in the cell is a little larger.

Defect No. 614005564065
Introduced version 4.15.10
Phenomenon The TA value in the cell is a little larger.
Influence Statistical TA performance is affected
Reason analysis RRU related hardware delay is a little larger.
Adjust the hardware delay of R8862/R8862A/R8872A/R8892N
Solution
according to the field test.
External verification No
method
Remark NO
6.2.19 When Running PIM Detection Function in a Batch, Many Sites Return
Serious Alarm State

Defect No. 614005895200

RRU partial channels are not configured and antenna connection is
abnormal. In this situation, if running PIM detection function in a
Phenomenon
batch, board serious fault alarm is given, even normal channels do
not return detection result.
PIM detection function doesn’t work well in the situation that RRU
Influence partial channels are not configured and antenna connection is
abnormal.
If running PIM detection function in a batch, all RRU channels
should be traversed. However when the function detects that
current channel is not configured and VSWR is over high, it will stop
Reason analysis
the detection task and report a serious fault alarm. The purpose is
to protect hardware and notify a maintenance engineer as early
as possible.
Modify the function termination condition. If the function detects that
a RRU channel is not configured and antenna connection is
Solution abnormal, it will report a detection abnormal result, but continue to
detect other channels. This PIM detection function will not stop until
all RRU channels have been detected.
Even though RRU partial channels are not configured and antenna
External verification connection is abnormal, the PIM detection function can still continue
method the detection task. Other channels with correct configuration and
normal antenna connection can return PIM detection result.
Optimize the version. In the situation that partial channels are not
Remark configured and antenna connection is abnormal, the PIM detection
function will not stop until all RRU channels have been detected.
6.2.20 Optimize the Statistical Value of CPICH Average Power Counter

Defect No. 614005893205

After activating the function of decreasing CPICH power in
Phenomenon high-load situation, the value of CPICH average power
recorded in C372480141 is much greater than its real value.
Because CPICH average power recorded in C372480141 is
Influence inaccurate, it cannot be used to precisely evaluate pilot
value.
The C372480141 counter will not start working unless the
function of reducing CPICH power in high-load situation is
activated and cell load reaches a certain threshold. As cell
Reason analysis
load changes, the values of collected CPICH power
samples may fluctuate between 0 and a real value. This
causes inaccurate CPICH average power.
After optimization, the two constraints on function switch
and cell load are removed. The system keeps reporting
Solution CPICH average power so that this counter can exactly
reflect how cell coverage is shrunk after decreasing CPICH
power.
External verification After modification, view the value of C372480141. It can be
method used to evaluate real CPICH power value.
Remark
6.2.21 When signal quality is poor, DTX ratio is high for HSDPA UEs

Defect No. 614005896225

Phenomenon When signal quality is poor, DTX ratio is high forHSDPA UEs.
Influence When signal quality is poor, HSDPA user experience is affected.
When downlink coverage is bad or signal quality is poor, HS-SCCH
Reason analysis transmission power is low. As a result, it is difficult for UE to
demodulate HS-SCCH. Thus UE reports more DTX cases.
When downlink coverage is bad or signal quality is poor, slightly
Solution raise HS-SCCH transmission power so as to enhance UE
demodulation capability.
External verification No
method
After upgrading the version, the following indexes may change:
Remark 1. 901397: Ratio of HSDPA DTX falls.
2. Other HSDPA related indexes may change.
6.2.22 In a multi-mode site, after incrementally changing GSM or LTE

configuration data such as GSM IP or LTE IP, new UEs cannot access
to UMTS site.
Defect No. 614006039083

Introduced version V4.16.10
In a multi-mode site, after incrementally changing GSM or LTE
Phenomenon configuration data such as GSM IP or LTE IP, new UEs cannot
access to UMTS site.
Influence UMTS new services become abnormal.
During the process of incrementally changing LTE configuration
Reason analysis
data, UMTS data is changed by mistakes.
Solution Modify the process.
External verification After incrementally changing LTE IP parameter, new UEs can
method access to UMTS site.
Remark

6.2.23 Transmission link changeover causes GSM process to become

abnormal and reset

Defect No. 614005564104

Introduced version NB_V4.16.10
Activate BFD function. Transmission link changeover triggers an
Phenomenon operation – update gateway IP. GSM process accesses an invalid
address. Consequently, GSM process resets.
Influence GSM services are interrupted.
GSM product platform informs the process to update gateway IP.
Reason analysis During the updating period, print function accesses an
invalid address. Consequently, GSP process resets.
Solution Modify the relevant codes
Upgrade the version. Activate BFD function. Then initiate
transmission link changeover. Observe whether GSM process
method
abnormally resets.
Remark NULL
6.2.24 CSSR KPI keeps abnormal when IUB Transmission recovers from
congestion
Defect No. 614001225426

Introduced version V4.15.10.20
CSSR KPI is degraded after IUB transmission is congested or hig
Phenomenon h packet loss. However, there is probability that CSSR KPI keeps
abnormal after IUB transmissoin revovers.
Influence CSSR KPI degraded
If huge RadioLink deletion signaling messages are lost due to hig
Reason analysis h IUB transmission congestion or huge packet loss ,there is proba
bility that NodeB RL resources may not be released correctly.
Optimize Nodeb internal RL resources release process, which will r
Solution elease all RL resources in the case of huge loss of signaling mes
sages.
External Running the patch, CSSR KPI is improved.
verification meth
od
Remark NULL
6.2.25 There is a problem of abnormal statistical indicators in two sites

of Algeria

Defect No. 614005628357

Introduced V4.14.10
version
On EMS, the counter C373281884 of 17005NE and the counter
Phenomenon
C373250984 of 17104NE appear abnormally large value.
Influence A certain 15 minutes a KPI index anomaly
Once a fault occurs in Algeria network and Shandong V3.2
version of this fault field is the same, through two real-time KPI
data and the Shandong field reproduced the results, each
counter is the abnormal high bit turnover caused (each counter
is stored in the WORD32, each fault is a bit high a jump from 0
to 1). Before generating the KPI file, we will all the data from the
temporary area to the history of the area, the history of the
Reason analysis
region is the timely application of the release of the memory, the
results of the Shandong field reproduction is the data in the
historical area of the abnormal. Because of the failure of the
reproduction rate is not high, each time in a different counter, the
home of some of the memory tracking mode can not be
implemented in the field, so the reason for the failure of bit can
not be found.
The historical memory is timely for the timely release, so there
are some uncertain factors, we use methods, the historic district,
Solution
these uncertain factors, access to data generated files directly
from scratch.
External Observe all KPI data to see if there is an unusually large value
verification met
hod
Remark NULL

6.2.26 Average CPU Usage of the CC Board on the eNodeB Is Greater Than
100% and Displayed As 3000%
Defect No. 614001225426
Introduced V4.14.10
version
On the EMS, the query result of the performance counter
Phenomenon (C370010001, Ratio of Average CPU Usage) is displayed as
3000%, which is far greater than 100%.
Influence Ratio of Average CPU Usage (C370010001) is abnormal.
KPI data saved inside the eNodeB uses the Ping-Pong
mechanism, and the eNodeB reports KPI data to the NM
server at fixed time points. When the time of the eNodeB
changes, the fixed time point of reporting KPI data might be
Reason analysis
skipped. At this time, the data area will be inverted twice.
Because the inversion interval is very short, one clearing
operation is omitted. As a result, residual values remain in the
average value counter, and it is displayed abnormally.
Bind the clearance and inversion of data areas. Before
inverting the data area, the system clears it first to ensure that
Solution
the current write data area is a clear area with no residual
data.
Change the time of the eNodeB, and check the Ratio of
External
Average CPU Usage counter (C370010001).
verification met
Criteria:
hod
The Ratio of Average CPU Usage counter (C370010001) i
s normal and it does not exceed 100%.
Remark NULL
6.2.27 When NodeB reboots or BPN2 board reboots, there is a small probability
that RLC retransmission rate reaches 100% in some cells, but HSDPA
throughput approximates to 0.
Defect No. 614006131267
Introduced V4.16
version
This phenomenon occurs when Node B reboots or BPN2
Phenomenon
board reboots. There is a small probability that

RLC retransmission rate reaches 100% in some cells, but

HSDPA throughput approximates to 0.
RLC retransmission rate becomes worse. UEs cannot run
Influence
HSDPA service.
During BPN2 board rebooting period, it may load a hot patch.
After loading a hot patch, there is a small probability that the
system fails to set inter-board message exchange switch
Reason analysis
to on. This brings a problem - HSDPA messages cannot be
transferred between two boards. As a result, HSDPA UEs
cannot be scheduled.
Take a protection measure. After BPN2 finishes loading a hot
Solution patch, the system can set inter-board message exchange
switch to on.
External
verification met
hod
Remark NULL

6.2.28 Activate TWAMP monitoring function. Several sites have packet loss
and jitter problem in the uplink direction
Defect No. 614006129366
Introduced V4.15
version
Activate TWAMP monitoring function. Several sites have
Phenomenon
packet loss and jitter problem in the uplink direction
TWAMP link measurement result cannot exactly indicate link
Influence
state.
CCE1 version has a defect. When it receives a TWAMP
packet, it deems it is from an unknown port. Because of flow
Reason analysis
control, this TWAMP packet is discarded. Thus, packet loss
occurs during TWAMP measurement.
Change the attribute of TWAMP packet to be a known-port
Solution packet. By doing this, TWAMP packet will not be discarded
due to flow control.
External Uplink state is normal. Activate TWAMP
verification met monitoring function. Packets are not lost.
hod
Remark NULL
6.2.29 C370130001 (link connection time between Node B and OMCB) becomes
abnormal on Algeria’s network. Occasionally the value shown in EMS is 1200
seconds.
Defect No. 614006152832
Introduced NB_V4.14.10
version
In EMS, view the value of C370130001(link connection time
Phenomenon between Node B and OMCB). Occasionally an
abnormal value is shown, i.e. 1200S.
Influence An abnormal KPI will affect user experience.
At Node B side, a module collects the data of two indexes every
5 minutes: link connection time between Node B and OMCB
(C370130001), link interruption times (C370130000). Node B
Reason analysis
reports the values of C370130000 and C370130001 to OMCB
every 15 minutes. Because data collecting process and
counter reporting process do not keep the same pace, it is

possible that the reported value may cover the data collected
over 2, 3 or 4 times. Thus, an abnormal value is shown in
EMS occasionally.
Solve the defect so that Node B reported value covers the
Solution
data collected over current 15 minutes.
1. In EMS, observe the values of C370130000
(link interruption times between Node B and OMCB) and
External
C370130001(link connection time between Node B and
verification met
OMCB).
hod
Passing criterion:
1. The values of C370130000 and C370130001 are
normal.
Remark NULL
6.2.30 After putting 900M 2T cells into operation, some cells are repeatedly
deleted and set up. Services are affected
Defect No. 614006152128
Introduced V4.14.10
version
After putting 900M 2T cells into operation, some cells are
Phenomenon
repeatedly deleted and set up. Services are affected.
When a cell is deleted/set up, services in the cell are
Influence
interrupted for the moment.
In a UL hybrid site, if LTE SON (Self Organizing Networks) or
ANR (Automatic Neighbor Relation) function is configured,
this will automatically trigger configuration update operation.
Reason analysis
Then database saved on CC is updated. As Node B database
configuration is updated, UMTS 2T cell information is updated
accordingly. As a result, cell deletion/setup occurs.
When the system detects that a LTE function triggers
Solution configuration update operation, Node B does not update
UMTS database. This can avoid UMTS cell deletion/setup.
External In a UL hybrid site, activate LTE ANR configuration. The
verification met UMTS 2T cell is not repeatedly deleted / set up.
hod
Remark NULL

6.2.31 Some brands of UEs process uplink DTX abnormally, causing small MOS
Defect No. 614006161401
Some UE brands such as SONY and HTC have a
Phenomenon problem. When UEs enter UL DTX state, MOS is 0.3
smaller than other UEs.
Influence Uplink MOS is affected.
According to 3GPP 26.093, UE should send a sid_first
frame after it finishes sending audio frames. However,
SONY and HTC UEs send a different frame, that is,
sid_update frame. When Node B receives this
Reason analysis sid_update frame, it does not interpret this situation as
end of audio frames. As a result, it does not immediately
enter DTX state. In this case, it sends this mute frame
without realizing this is a mistake. Finally, this causes
small MOS.
Node B stays at non-DTX state. When it detects a
Solution sid_update frame, it sends sid_first frame and enters DTX
state.
External verification Upgrade the version. Observe whether MOS rises.
method
Remark NULL
6.2.32 In the coordinated configuration of UBPG1 board and R8863 baseband

combined-cabinet mode, partial carriers have no power output in downlink direction

Defect No. 614006161402

In the coordinated configuration of UBPG1 board and
R8863 baseband combined-cabinet mode, there is a
Phenomenon
probability that carriers have no power output in downlink
direction.
Influence CS services are affected
UBPG1 board is configured. R8863 baseband
combined-cabinet mode is configured, too. Two kinds of
carriers may exist simultaneously in a cell: one operates
in R8863 baseband combined-cabinet mode, the other
Reason analysis
operates in non combined-cabinet mode. In this situation,
there is a defect when DSP fetches channel bitmap of the
first kind of carriers. Because of the defect, carriers have
no power output in downlink direction.
Modify the relevant codes so that each kind of carrier is
associated to its channel bitmap. Then DSP can obtain
Solution
correct channel bitmap of the corresponding kind of
carriers.
External verification Upgrade the version. Observe whether CS services are
method normal.
Remark NULL
6.2.33 In the configuration of R8863 baseband combined-cabinet mode, carrier

intelligent shutdown function has a defect

Defect No. 614006161403

In the configuration of R8863 baseband
combined-cabinet mode, activate intelligent shutdown
Phenomenon function. The CPU ratio of R8863 rises to a high level. In
serious situation, link interruption occurs and R8863
reboots.
The CPU ratio of R8863 rises to a high level. In serious
Influence
situation, link interruption occurs and R8863 reboots.
In the configuration of R8863 baseband
combined-cabinet mode, activate intelligent shutdown
function. In this situation, BBU sends a wrong extended
carrier shutdown bitmap to RRU. This brings a problem -
Reason analysis carrier shutdown messages are frequently exchanged
between BBU and RRU. Too many RRU messages are
not processed and piled up. Consequently CPU ratio
rises to a high level. In serious situation, link
interruption occurs and RRU reboots.
Modify the relevant codes. BBU can properly
Solution
process shutdown tag of extended carriers.
External verification Upgrade the version. Activate intelligent shutdown
method function. Observe whether R8863 runs properly.
Remark NULL
6.2.34 In the environment that dual-CC is configured and FCE is connected

to RSU40 U216, FCE reports an alarm, indicating software runs abnormally.
Defect No. 614006301725
Introduced 4.16.10.20P10
version
In the environment that dual-CC is configured and FCE is
Phenomenon connected to RSU40 U216, FCE reports an alarm, indicating
software runs abnormally.
Influence FCE reports a “software runs abnormally” alarm.
Partial RSU 485 message is not sent to two CC boards. Thus, one
Reason analysis
CC has not received relevant message.
RSU 485 driver adds a process especially for dual-CC environment
Solution
so that both CC boards will transfer FCE messages.

External Upgrade the version, this alarm disappears.

verification
method
Remark Null
6.2.35 After eNB reconfigure or reset, CSSR degraded in some cells

Defect No. 614005688238
After the site reconfigure or resets, some KPIs such as
Phenomenon CSSR (Call Setup Success Rate), CDR (Call Drop
Rate) decrease in some cells of this site.
RRC connection success rate and call drop rate in some
Influence
cells are affected.
If the clock jitters, there is a probability that BPN2 use
d clock jitters, too.
In scenario where a cell is setup on multi-BP boards.
It is possible that UE initiates access attempt preamble
(PRACH) to one BPN2, but the other BPN2 responds
Reason analysis AI symbol(AICH) to this UE.
In this situation, if CC clock jitters, the clocks used b
y two BPN2 boards may have deviation. This means A
I sent from NodeB to UE does not meet time slot requ
irement. At UE side, UE cannot receive the AI at the
expected slot, then UE access fails.
CC resets BPN2 board when CC detects clock jitters,
Solution
so that clock on BPN2s keeping aligned.
After upgrade, there is "The input frame synchronous s
External verification ignal is wrong" alarm if the clock jitters, and BPN2 will
method reboot. Then KPIs such as CSSR and CDR are norma
l.
Remark NULL
6.2.36 In some sites, BPK-d repeatedly reports “software runs abnormally”

when traffic is busy.
Defect No. 614005685618

In some sites, BPK-d repeatedly reports “software runs

Phenomenon
abnormally” when traffic is busy.
BPK-d resets and all services borne on theBPK-d are
Influence
interrupted temporarily.
During busy hours, some reason (e.g. transmission packet
loss) causes many RLs to be repeatedly deleted/added.
Reason analysis
This affects the CPU load on BP. Consequently, CPU is
overloaded and BP resets.
When the system detects that CPU is overloaded, it starts
Solution overload control policy to reject new UE to be accessed.
Finally, BP will not repeatedly reset.
External verification When traffic is busy, observe whether BPK-d
method reports “Software runs abnormally” alarm.
Remark NULL
6.2.37 BPN board may reset when CPU Load is high

Defect No. 614002730422
Phenomenon BP board resets
Influence Because BP board resets, online services are affected.

If CPU load is high, there is a certain probability that
compressed-mode signaling may not be timely
processed and the saved compressed signaling
Reason analysis information may be cleaned. Later when the system
can process this compressed-mode signaling, the
process becomes abnormal. As a result, BP board
resets.
The system runs a process to save compressed-mode
Solution information. Add a task lock to this process so as to
keep the integrity of compressed-mode information.
External Upgrade the version. Then observe whether BP board
verification method resets when CPU load is high.
Remark Null
6.2.38 BPN2 Resets due to an error in RL multipath searching process

Defect No. 614006354457

Phenomenon BPN2 resets

Because BPN2 resets, all service borne on this board
Influence
are interrupted.
There is a code logic error in UE handover dedicated
multipath searching process. Because of this, there is
Reason analysis
a certain probability that a processor may access wrong
memory, causing BPN2 to reset.
Modify relevant codes and enhance the tolerance of
Solution
RL multipath searching process.
Run basic services, repeatedly initiate multi-UE setup,
External
deletion and handover. Services are normal, KPIs are
verification method normal. BPN2 does not reset.
Remark Null
6.2.39 BPN board may reset when CPU Load is high

Defect No. 614003560608
Phenomenon BPN2 resets when service load is high

Because BPN2 resets, all service borne on this board
Influence
are interrupted.
When a site stays at high service load, services cannot
Reason analysis
be timely processed. This causes BPN2 to reset.
Optimize overload process method to reduce the
Solution probability that high service load causes BPN2 to
reset.
Run basic services, repeatedly initiate multi-UE setup/
deletion. Services are normal, KPIs are normal. BPN2
does not reset.
External
When a site stays at high service load, BPN2 does not
verification method reset during busy hour. Load control works properly so
that new UEs cannot be accessed. During busy hour,
RRC/RAB indexes may become worse.
Remark Null

6.2.40 NodeB site is equipped with CCE1 board. After activating IPSEC
function, this NodeB irregularly resets
Defect No. 614006257030
NodeB site is equipped with CCE1 board. After activating
Phenomenon
IPSEC function, this NodeB irregularly resets.
Because NodeB resets, services are interrupted for the

Influence
moment.
CCE1 adopts multi-core CPU. Different processes may be
distributed on different cores. If IPSEC function is
activated and virtual address is configured, NodeB checks
this virtual address and surely cannot pass the check. In
Reason analysis this case, the system will call a log print function to
produce much print information. Meanwhile if the other
core on CCE1 also calls this log print function, write
operation may conflict. Consequently, memory access
becomes abnormal, then Node B resets.
Temporary solution: close log print function.
Final solution: Set mutual exclusive limitation on the log
Solution
print function so that only one module is allowed to call the
log print function.
Upgrade the version. Check those Node sites equipped
with CCE1 board. There is no abnormal reset
method
phenomenon.
Remark
6.2.41 In IPSEC path backup scenario, Node B repeatedly reports “IPSec link
abnormal” alarm.
Defect No. 614006079481
In IPSEC path backup scenario, Node B repeatedly
Phenomenon
reports “IPSec link abnormal” alarm.

In IPSEC path backup scenario, backup link is repeatedly

Influence
deleted/added.
The system periodically checks the traffic of IPSec backup
path. Once it is idle for half an hour, the system will delete
Reason analysis the backup path. Later, it will add an IPSec path again. In
this case, such alarm is wrongly reported every once in a
while.
The system will not detect the traffic of a backup path.
Solution This can avoid triggering backup path deletion/addition
process.
External verification The “IPSec link abnormal” alarm will not be wrongly and
method repeatedly reported.
Upgrade the version. Check whether the “IPSec link
Remark
abnormal” alarm is reported every once in a while.
6.2.42 If configuring multiple IPSEC paths, only one IPSEC path is normal.
Defect No. 614006175541
In IPSEC path backup scenario, if configuring multiple
Phenomenon IPSEC paths, only one IPSEC path is normal, others are
disconnected.
Influence IPSEC path is abnormal.
If the system detects that a backup path is idle for half an
hour, it will delete this path. Later the system will add an
IPSEC path again. There is a potential problem when loss
of packet occurs – the relevant process cannot be properly
Reason analysis
protected. As a result, the occupied resources cannot be
released. Once this occurs, as there is an IPSEC path
setup request, no resources can be granted. Thus, new link
is disconnected.
The system will not detect the traffic of a backup path. The
Solution purpose is to avoid repeated path setup or resource
application, resources will not be abnormally occupied as

long as they are granted.

External verification Upgrade the version. Add IPSEC path and check whether
method the new IPSEC path is normal.
Remark
6.2.43 An input power problem of R8852 causes wrong PA protection and no

output power
Defect No. 614006344240
Introduced version 4.16

Three R8852 devices have a phenomenon – main power is
Phenomenon
normal, but R8852 no output power.
RRU has no output power and the covered cells are
Influence
abnormal.
After analysis, it is found that input voltage is normal, but
Reason analysis under-voltage tag is abnormal. This causes FPGA wrong
protection operation, no output power.
Modify the software so that it can block thewrong protection
Solution
function when abnormal input voltage is detected.
Run the patch, then observe whether the following situation
happens: RRU does not report an alarm, it has digital
method power, but doesn’t have analog power.
Passing criterion: this situation does not happen.
Remark
6.2.44 In the situation of interoperation between SUN server and BBU,

IMSI-based Log collection fails.
Defect No. 614006362631
Introduced version It always exists
In the situation of interoperation between SUN server and
Phenomenon
BBU, IMSI-based Log collection fails.
In the situation of interoperation between SUN server and
Influence
BBU, IMSI-based Log collection fails.
Reason analysis OMMB sends a signaling collection command. This

command packet belongs to large-packet fragmentation

type. There is a bit, named “don’t fragment” flag, in this
packet. Its value is 1, indicating that this packet is not
allowed to be fragmented.
After DPS reassembly process, IP header of the packet is
discarded. This brings a problem - after BRS process, the
IP packet is discarded due to abnormal IP. Consequently,
signaling collection fails.
If it is a fragmented packet and the value of “don’t fragment”
Solution flag is 1, reassembly process can properly handle this
special packet.
Install OMMB on SUN server. Tick all radio modes and
enable IMSI-based Log function. IMSI-based Log collection
method
is successful.
These boards are involved: CCE1, CCF0, CBBM0
Remark and CBBM1. Only CCE1 board is involved on Indonesia’s
network.
6.2.45 In dual-CC dual-master situation, some fans in FCE may rotate at

abnormal speed
Defect No. 614006490856
Create a repository task to upgrade the 2nd CC. If it is in
Phenomenon dual-CC dual-master situation, some fans in FCE may
rotate at abnormal speed.
Even though very few fans rotate at abnormal speed,
Influence
overall cooling effect will not be obviously affected.
MO starts a repository task to upgrade the 2 nd CC. If the
CPU version used by the repository file is different from that
used by the new board, DV file will not be synchronized.
Reason analysis Because it is impossible to obtain DV configuration, there is
a certain probability that FCE speed adjustment cannot be
properly controlled. Once this occurs, some fans may not
rotate at normal speed.

Create a repository task to upgrade the 2nd CC.

Solution
Synchronize DV configuration file to the new board.
After upgrading to the new version, view how the fans in
method FCE rotate in dual-CC dual-master situation. Check
whether any fan has abnormal rotational speed.
Remark Belgium
6.2.46 Avoid a fault caused by broken RF switch

Defect No. 614005737391
Introduced version 4.15
When a RF switch is broken, RRU reports an internal fault
Phenomenon
and disable PA.
Influence Services are interrupted.
When the RF switch is broken, it is impossible for RRU to
Reason analysis measure output power. Thus, RRU deems that PA is
broken.
Note that RRU keeps output power record before the
switch is broken. After the switch is broken, RRU can
Solution use this record to estimate output power according to the
change of total powerconsumption. Finally, services will not
be interrupted.
External verification Update version. Observe the RRU with broken RF switch. It
method does not report an internal fault and services are normal.
Only applicable to R8863 B8A operating in UMTS mode
Remark or UL mode.
Indonesia
6.3 Solved LTE Issues List
Table 6-2 Solved Issues List
Defect No. Defect Name Level Mode Solve

Version
20160524164447 VoLTE RTP packet loss B LTE V4.16.10.20(V
3.40.20.10)
20160624095904 Optical module alarms on D LTE V4.16.10.20(V
multiple sites after version 3.40.20.10)
upgrade to V3.3
20160625183337 When an FDD LTE eNodeB is C LTE V4.16.10.20(V
upgraded from V3.20.50.30 3.40.20.10)
P10 to V3.30.20.11
(V3.30.20.21 _FTL), the KPI
counter "C373505499
increases greatly
20160720085806 Supercell outage on 15 C LTE V4.16.10.20(V
eNodeBs after version upgrade 3.40.20.10)
due to "License limited"
20160826231938 eSRVCC handover fails, C LTE V4.16.10.20(V
causing abnormal UE release 3.40.20.10)
20160831112249 Downlink retransmission C LTE V4.16.10.20(V

interval is large in the VoLTE 3.40.20.10)
test
20160914192815 In combination mode for the B LTE V4.16.10.20(V
R8863 S2100, the “Referenced 3.40.20.10)
Signal Power of BP Resource”
of OMMB cannot be configured
to 18.2 db
20160918105816 Specific UEs cannot access B LTE V4.16.10.20(V

the network after upgrading 3.40.20.10)
from V3.20.50.20 P10 to
V3.30.20.30
20160918174531 RRC request rejected due to B LTE V4.16.10.20(V
eNodeB admit failure 3.40.20.10)
20160923051749 After the system is upgraded to B LTE V4.16.10.20(V

V3.3.20 P40, the incoming 3.40.20.10)
handover failure rates on S1
and X2 interfaces increase.
20160927093722 High dropped call rate due to B LTE V4.16.10.20(V
the PERIOD_TA_MEAS option 3.40.20.10)
selected for the MR task

20161009150741 Large number of messages B LTE V4.16.10.20(V

indicating context modification 3.40.20.10)
failure due to other causes
after system upgrade to V3.3
20161025110052 Scheduling according to DRX C LTE V4.16.10.20(V
Enable when Cell Connect 3.40.20.10)
Reestablishment with DRX is
disabled
20161101151720 CSFB failure B LTE V4.16.10.20(V
3.40.20.10)
20161107045420 BPL1 board reset repeatedly B LTE V4.16.10.20(V
due to more than 64 UTRAN 3.40.20.10)
neighbor cells after SDR15
version upgrade
20161107094430 eNodeB KPI (downlink C LTE V4.16.10.20(V
transmission bandwidth 3.40.20.10)
(megabit/s)) abnormal
20161107115518 Five cells disconnected and B LTE V4.16.10.20(V
having no msg1 3.40.20.10)
20161118091237 GL RRU having parameter C LTE V4.16.10.20(V

configuration error alarms after 3.40.20.10)
system upgrade to V4.15
20161122003533 Secondary carrier RB B LTE V4.16.10.20(V
insufficiency in CA handover 3.40.20.10)
20161122112839 Probabilistic call failure due to B LTE V4.16.10.20(V

UE not responding to Paging 3.40.20.10)
messages in reestablishment
scenarios for the CSFB test
20161220114504 Admission failure on eNodeBs B LTE V4.16.10.20(V
with CA function 3.40.20.10)
20170105095756 eNodeB using a temporary C LTE V4.16.10.20(V

License file in default state for 3.40.20.10)
a moment after system
upgrade from V3.3 to V3.4
20170116100312 No downlink traffic after B LTE V4.16.10.20(V
handover from a ZTE eNB to a 3.40.20.10)
Nokia eNB
20170220160622 In six cells 4 with ant mode, C LTE V4.16.10.20(V

one of the cells on BPL1 setup 3.40.20.10)

fail
20170112055252 After activating the speedtest B LTE V4.16.10.20(V
switch, UE executing 3.40.20.10)
speedtest preempts RB
resources
20170131000002 The self-defined CSFB failure C LTE V4.16.10.20(V
times are found minus after 3.40.20.10)
UR14 upgraded to UR15
20170203111053 C373384345 Average User B LTE V4.16.10.20(V

Number Cat 6 was reduced 3.40.20.10)
after upgrading to
4.15.10.30P30
20170215060648 The UE fails to execute C LTE V4.16.10.20(V

intra-RAT handover after the 3.40.20.10)
SRVCC procedure based on
signal quality
20170216211458 Signal quality based SRVCC B LTE V4.16.10.20(V
has no protection mechanism 3.40.20.10)
during threshold triggering
20170214031031 Hi3G, When eNodeB upgrade B LTE V4.16.10.20(V
to a new version, the CDT data 3.40.20.10)
does not contain CT signal
20170213205208 After FAST RETURN to the B LTE V4.16.10.20(V

1.8G LTE cell in CSFB 3.40.20.10)
procedure, UE handover to
higher 2.6 G PCELL
frequency, and then UE can’t
receive Modify EPS bearer
context request message from
MME
20170127081650 The load balance UE which B LTE V4.16.10.20(V
has fast return to LTE cell after 3.40.20.10)
CSFB cannot receive the S1
Modify EPS bearer context
request message
RRC Release After an Initial LTE V4.16.10.20P
Message is Sent to the New B 10(V3.40.20.1
20170303172448 MME 0P10)

The eNodeB Name and Cell LTE V4.16.10.20P

Name Is Abnormal in C 10(V3.40.20.1
20170303151948 Performance Data Query 0P10)
Decrease of the LTE CSFB SR LTE V4.16.10.20P
Indicator from 99.9% Before 10(V3.40.20.1
Upgrade to 99.4% After B 0P10)
Upgrade With a Deterioration
20170302103414 Rate of 0.5%
Voices Not Heard Clearly in LTE V4.16.10.20P
Some Cases When F7 Mobile 10(V3.40.20.1
B
Phones Call Samsung Mobile 0P10)
20170301102122 Phones
Abnormal Value in the KPI LTE V4.16.10.20P
Statistical Results of a Field B 10(V3.40.20.1
20170228092821 Site 0P10)
Increased UL IP Throughput LTE V4.16.10.20P
After the eNodeB Version Was B 10(V3.40.20.1
20170224120329 Upgraded From V3.2 to V3.3 0P10)
Deterioration of the E-RAB Call LTE V4.16.10.20P
Drop Indicator After eNodeB 10(V3.40.20.1
Was Upgraded from B 0P10)
4.13.10.30P42 to
20170207222615 4.15.10.20P51
LTE V4.16.10.20P
Increased Active E-RAB Drop C 10(V3.40.20.1
20170206173525 Rate After Upgraded to V3.3 0P10)
Serious Decrease in the CQI, LTE V4.16.10.20P
Equivalent Throughput and 10(V3.40.20.1
B
64QAM After BPL0 Site Was 0P10)
20170206172312 Upgraded from V3.2 to V3.3
LTE V4.16.10.20P
Paging Loss in Sites With No B 10(V3.40.20.1
20170204102421 Paging Congestion 0P10)
LTE V4.16.10.20P
Falsely High Statistics of the B 10(V3.40.20.1
20170118090200 Number of RRC Users 0P10)
Statistical Result of LTE V4.16.10.20P
C373505499 Greater Than B 10(V3.40.20.1
20160707102904 P340440 0P10)
eNodeB Failing to Select the LTE V4.16.10.20P
C
20160907231755 Correct PLMN to Return an 10(V3.40.20.1

ACK Message After Receiving 0P10)

RIMinformation During 2G RIM
Information Exchange in the
MOCN Shared Network
No More Than Nine Blackcell LTE V4.16.10.20P
Lists Related to Forbidden B 10(V3.40.20.1
20160819184450 TACs 0P10)
Increased RRC Call Drop Rate LTE V4.16.10.20P
After the Upgrade of an B 10(V3.40.20.1
20160809141629 eNodeB 0P10)
Serious Cell Uplink Packet LTE V4.16.10.20P
Loss Rate in Random B 10(V3.40.20.1
20161012160546 Distribution With No Top Cell 0P10)
The Number of Intra-eNB LTE V4.16.10.20P
Inter-Frequency Handovers is 10(V3.40.20.1
B
Significantly Decreased After 0P10)
20161009044205 DRX Closed
LTE V4.16.10.20P
High VOLTE Call Drop Rate B 10(V3.40.20.1
20161114095807 Due to Redirection 0P10)
Deterioration of the RRC Call LTE V4.16.10.20P
Drop Rate and E-RAB Call 10(V3.40.20.1
B
Drop Rate After Upgrade to 0P10)
20160728180828 V3.30.20.21
LTE V4.16.10.20P
Intra-eNodeB Handover B 10(V3.40.20.1
20161008115245 Failure During Migration 0P10)
LTE V4.16.10.20P
Decreased CN Traffic Due to B 10(V3.40.20.1
20161009150018 S1 RESET 0P10)
After Version Upgrade, There LTE V4.16.10.20P
Are Many Link Disconnections 10(V3.40.20.1
Due to the S1 Link Error in A B 0P10)
Few Sites, but the SCTP Link
20161104204855 Is Disconnected Only Once
LTE V4.16.10.20P
B 10(V3.40.20.1
20161222165128 The BPN2 Board Restart Fault 0P10)
Among KPI Counters in the LTE V4.16.10.20P
Existing VoLTE Network, the B 10(V3.40.20.1
20161227172031 Total Number of Abnormal 0P10)

Releases of Eight QCI1s in

Some Cells Is Smaller Than
the Value of "C373505300
The eNodeB Sends an Empty LTE V4.16.10.20P
Reconfiguration Message but 10(V3.40.20.1
the UE Does Not Return an 0P10)
Assignment Complete B
Message, so the eNodeB
Releases the UE Upon
20170104042608 Timeout
Baseband Reset Problem Due LTE V4.16.10.20P
to a Software Operation Error B 10(V3.40.20.1
20170329144600 in CA Sites Along the Subway 0P10)
Decreased CSFB Success LTE V4.16.10.20P
Rate After the UTRAN ANR B 10(V3.40.20.1
20161008140129 Switch Is Enabled 0P10)
After the Customized LTE V4.16.10.20P
Description Field in AISG 10(V3.40.20.1
Configuration Is Modified, the 0P10)
AISG Communication Link C
Disconnection Alarm will Be
Reported during AISG
20161103090911 Rescanning
LTE V4.16.10.20P
Automatic Reset during RRU C 10(V3.40.20.1
20161018173804 Operation 0P10)
Increased NI Noise After the LTE V4.16.10.20P
R8882 S2100 B Is Upgraded to B 10(V3.40.20.1
20161022123503 V4.15 0P10)
Sudden Increase of the CC LTE V4.16.10.20P
Board Load From 10% to 66% C 10(V3.40.20.1
20170103083733 in an eNodeB 0P10)
Speed Is Low in Indoor LTE V4.16.10.20P
Distribution Cascading RRU 10(V3.40.20.1
Coverage and Is Recovered C 0P10)
After the Sampling Rate is
20170116172728 Modified
LTE V4.16.10.20P
Exceptionally High Handover B 10(V3.40.20.1
20170309164357 Indicator 0P10)
20170112163626 Clearance Time of Some B LTE V4.16.10.20P

History Alarms Earlier Than 10(V3.40.20.1

Occurrence Time 0P10)
Failure to Query Physical LTE V4.16.10.20P
Devices in Dynamic B 10(V3.40.20.1
20161229093729 Management 0P10)
IQ Allocation Failure After the B LTE V4.16.10.20P
Qcell pRRU Rack No. Exceeds 10(V3.40.20.1
216, Causing the Array to 0P10)
Cross the Threshold and
20170419100448 Affecting the Global IQ
B LTE V4.16.10.20P
10(V3.40.20.1
20161012144430 Sleeping Cell Problem 0P10)
B LTE V4.16.10.20P
Incorrect Counters 10(V3.40.20.1
20161018173856 C373930024 & C373930025 0P10)
After A Broken SCTP Link is B LTE V4.16.10.20P
Recovered, There Is No 10(V3.40.20.1
Transmission Power on the 0P10)
RRU and Services are
Interrupted; Services are
Recovered After the PA is
Disconnected and Enabled
20161104104133 Again
B LTE V4.16.10.20P
Repeated Reset of the CC 10(V3.40.20.1
20161116110433 Board at a Site 0P10)
Average CPU Usage of the CC B LTE V4.16.10.20P
Board on the eNodeB Is 10(V3.40.20.1
Greater Than 100% and 0P10)
20161215133123 Displayed As 3000%
Frequent Disconnection of the B LTE V4.16.10.20P
OMC Link After 10(V3.40.20.1
FST+OMC+IPSec 0P10)
Configurations Are Added on
20161202070358 the UR15 eNodeB Version
Supporting Automatic Update B LTE V4.16.10.20P
of the Summer Time and 10(V3.40.20.1
Summer Time Start/End Time 0P10)
20161209161221 Format of Month-Week-Day
20170105091354 Maximum Throughput (Mbps) B LTE V4.16.10.20P

of DL Received Data of the 10(V3.40.20.1

eNodeB Exceeding 1Gbps in 0P10)
Actual Statistics
LTE V4.16.10.20P
No Power on the RRU During C 10(V3.40.20.1
20161207095523 Query of Cell 311977 0P10)
LTE V4.16.10.20P
Repeated Printing of UDT B 10(V3.40.20.1
20170110013514 Signaling Messages 0P10)
B LTE V4.16.10.20P
UDT Decodes 10(V3.40.20.1
20160729141028 noncriticalextension in Error 0P10)
B LTE V4.16.10.20P
MTS Data Fail to Display IMSI 10(V3.40.20.1
20160811171346 on the EMS 0P10)
Time is Six Hours Later Than B LTE V4.16.10.20P
the Local Time After 10(V3.40.20.1
20161114223551 Northbound Trace Decoding 0P10)
B LTE V4.16.10.20P
High E-RAB Call Drop Rates in 10(V3.40.20.1
20170213175520 Top Sites 0P10)
Traffic of CA Terminals Lower B LTE V4.16.10.20P
Than Traffic of Non-CA 10(V3.40.20.1
20170121120334 Terminals in Speed Tests 0P10)
Increase of Prach Average NI B LTE V4.16.10.20P
by 30 dB or Above After UL 10(V3.40.20.1
20170112082841 Comp Deployment 0P10)
NI Is -120 In Case of Bypass B LTE V4.16.10.20P
and Is -70 In Case of 10(V3.40.20.1
Non-Bypass After 0P10)
Tower-Mounted Amplifiers Are
20170328171015 Added to the RRU
After BPN2 Replaces BPL1, LTE V4.16.10.20P
the Minimum Power of cell10 10(V3.40.20.1
at 120024 Site Is Increased, 0P10)
the Minimum Power of cell12 B
at 120156 Site Is Reduced,
and the Power of 0 mW Occurs
20160627194034 Before and After Replacement
Statistical Result of LTE V4.16.10.20P
C
20161108143331 C373414597 (Average NI of 10(V3.40.20.1

Carrier(dBm)) Inconsistent 0P10)

With the Average Value of
PB-Level Statistics
Low Speed of Far Points in LTE V4.16.10.20P
CAs in the India FDD+TDD B 10(V3.40.20.1
20161104162805 Network 0P10)
RTP Packet Loss Due to Large LTE V4.16.10.20P
Downlink Scheduling Intervals C 10(V3.40.20.1
20170414182659 Before Handover 0P10)
Inaccurate Average RSRP LTE V4.16.10.20P
Value of the Serving Cell or B 10(V3.40.20.1
20170418002209 Target Cell 0P10)
Lighting fault of Optical LTE V4.16.10.20P
module for newly added B 10(V3.40.20.1
20170420110700 R8861 0P10)
Simultaneous Report of GPS LTE V4.16.10.20P
Positioning Alarms from FDD 10(V3.40.20.1
LTE eNodeBs Failing to C 0P10)
Position in Different Areas
20170420171152 During Several Timing Periods
Large Changes to Maximum NI LTE V4.16.10.20P
and Average NI of the PRACH B 10(V3.40.20.1
20170505094113 After a Version Update to V3.3 0P10)
LTE V4.16.10.20P
Broken RRU Connections in B 10(V3.40.20.1
20170422023728 Some New LTE Sites 0P10)
Large Number of LTE V4.16.10.20P
Reestablishment Requests 10(V3.40.20.1
B
Caused by a Sector 0P10)
20170418163230 Reconfiguration Failure
Data Output Existing in the LTE V4.16.10.20P
Counter (Based on Blind 10(V3.40.20.1
Handover) when C 0P10)
Load/Measurement Based
20170412181047 Load Balance is Enabled
LTE V4.16.10.20P
Deteriorated KPIs After a New B 10(V3.40.20.1
20170412122658 License Is Loaded 0P10)
LTE V4.16.10.20P
CellID Reported as 65535 B 10(V3.40.20.1
20170406100941 Sometimes 0P10)

Deteriorated E-RAB Call Drop LTE V4.16.10.20P

Rate After the Netmax-L Is B 10(V3.40.20.1
20170405152832 Enabled 0P10)
Some UEs are Released LTE V4.16.10.20P
after Load Balancing Based 10(V3.40.20.1
on RRC User Access and CA B 0P10)
are Enabled at the Same
20170401154539 Time
LTE V4.16.10.20P
Two Sleep Cells in a Single B 10(V3.40.20.1
20170327102011 eNodeB 0P10)
Uplink Bler is High When LTE V4.16.10.20P
Adding and Then Removing 10(V3.40.20.1
B
Secondary Carrier, Affecting 0P10)
20160907063911 UE Uplink throughput
V4.16.10.
Low Speed of Some Samsung 20P20(V3.40.
20170609195530 S8 UEs in the Speed Test B LTE 20.10P20)
V4.16.10.20P
20(V3.40.20.1
20170601042826 LTE-UMTS Handover Failure B LTE 0P20)
Added E-RAB Setup V4.16.10.20P
Successful Rate Drops Greatly 20(V3.40.20.1
(Even to 30% on Some Sites) 0P20)
After Deploying the MR
Feature in the Current LTE
20170526143015 Network B LTE
Number of Inter-Frequency V4.16.10.20P
Handover Out Requests 20(V3.40.20.1
With/Without GAP Changed 0P20)
20170519194516 Greatly C LTE
V4.16.10.20P
Abnormal RSSI KPI on a Site 20(V3.40.20.1
20170515223238 in the Current Network C LTE 0P20)
UL throughput in PCC of CA V4.16.10.20P
UE continue to drop below 20(V3.40.20.1
10M in intra-cell handover 0P20)
20170523211629 process B LTE
When NB-IOT is Enabled on V4.16.10.20P
LTE eNodeB, More than 60 30(V3.40.20.1
20170713144315 Sites Reported Blocking B LTE 0P30)

Alarms. 40 Sites Recovered

itself, and More than a Dozen
Need Manual Processing
Software Runs abnormal in the V4.16.10.20P
CA Use Handover with SCC 30(V3.40.20.1
20170725190154 Scenario B LTE 0P30)
Some of the Sites the VoLTE LTE
Calls are Dropped When Using
Apple Phone, and the Phone V4.16.10.20P
Interface Appeares “Call 40(V3.40.20.1
20170625105513 Failed” B 0P40)
VoLTE UE is Released after LTE
eNodeB Receiving the UE V4.16.10.20P
Context Modification Request 40(V3.40.20.1
20170821161304 with the CSFB Indication C 0P40)
BPN2 board Resets and LTE V4.16.10.20P
Reports Alarm “software runs 40(V3.40.20.1
20170612124416 abnormal” B 0P40)
LTE V4.16.10.20P
CSSR Indicators of the Whole 40(V3.40.20.1
2017071721244 Network are Descreased B 0P40)
In 3CC CA Test, Throughput V4.16.10.20P
is Reduced to Zero and C LTE 40(V3.40.20.1
20170906234253 Reestablishment Occurs 0P40)
V4.16.10.20P
KPI statistics of TA distribution C LTE 40(V3.40.20.1
20170903184453 are exception 0P40)
One or More Cells V4.16.10.20P
Scheduling Capacity Per TTI B LTE 50(V3.40.20.1
20170908155846 are Insufficient for BPN2 0P50)
P10 UE is Released
V4.16.10.20P
Frequently after Accessing,
C LTE 50(V3.40.20.1
SCC is not added and UE
0P50)
20170922130010 can not Do Service in CA Test
RRC Connection B
V4.16.10.20P
Reconfiguration for 3CC CA
LTE 60(V3.40.20.1
Fails and UE Starts RRC
0P60)
20171024144305 Connection Reestablishment
eNodeB Reset Due to BNP2 B V4.16.10.20P
Reset after LB and Cell LTE 60(V3.40.20.1
20171022052609 Reselection Priority Are 0P60)

Disabled
RRC Call Drop Rate Is B
V4.16.10.20P
Increased and Is Restored
LTE 60(V3.40.20.1
after the CCE Board Is
0P60)
20171003182210 Restarted
CA User Data Volume Does C V4.16.10.20P
Not Match the 2CC and 3CC LTE 60(V3.40.20.1
20170922133939 Statistical Result 0P60)
C V4.16.10.20P
Sleeping Cell Is Detected on LTE 60(V3.40.20.1
20170912102025 an eNodeB 0P60)
R8988 S3500 Cannot Enable C
AISG and Necessary V4.16.10.20P
Information for Dynamic LTE 60(V3.40.20.1
Management Is Missing on the 0P60)
20170829144028 EMS
Sleeping Cell Is Detected on a B V4.16.10.20P
Qcell and No UE Accesses the LTE 60(V3.40.20.1
20170811181731 Cell 0P60)
A V4.16.10.20P
CCE1 Restarts Repeatedly LTE 60(V3.40.20.1
20170726104847 after a Hot Patch Is Installed 0P60)
UE Capability (Supporting for B
4x4 MIMO) Displayed in the V4.16.10.20P
Samsung S8 UE Log Is LTE 60(V3.40.20.1
Different from That of the ZTE 0P60)
20170714002057 eNodeB Log
Incorrect Average Number of B V4.16.10.20P
RRC Connections (Counter LTE 60(V3.40.20.1
20171009231056 C373200030) Is Reported 0P60)
High Type-2 Location B
V4.16.10.20P
Information Report Failure
LTE 60(V3.40.20.1
Rate and Low Location
0P60)
20171017162247 Success Rate
One of Four SpeedTest UEs C
V4.16.10.20P
Has No Data Flow with
LTE 60(V3.40.20.1
SpeedTest Being Enabled on
0P60)
20171019115216 the eNodeB
Handover Prepareration B V4.16.10.20P
Failure in MOCN Network LTE 60(V3.40.20.1
20170926095849 Sharing Site 0P60)

E-RAB Drop Rate Deteriorated B LTE V4.16.10.20P

Significantly after Upgrade to 61(V3.40.20.1
20171106235623 V4.16.10.20P50 0P61)
LTE DL 64QAM Usage is B LTE V4.16.10.20P
20171023094938 Dropped after Upgrade to 61(V3.40.20.1
UR16 0P61)
The iphone Siri Service is C LTE V4.16.10.20P
20171204172423 Abnormal after TCP Proxy is 61(V3.40.20.1
Enabled 0P61)
B LTE V4.16.10.20P
Cell RRC Number and ERAB
20171102034758 61(V3.40.20.1
Number are zero
0P61)
B LTE V4.16.10.20P
RRUs are Reset with the
20171017104554 61(V3.40.20.1
Reason "the watchdog resets"
0P61)
The HTTP Download Speed is B LTE V4.16.10.20P
20171009230453 Low After TCP ACK Split is 61(V3.40.20.1
Enabled 0P61)
QCELL LTE Sites Enter into B LTE V4.16.10.20P
"sleep" Causing Users Unable 61(V3.40.20.1
20170914094904
to Access and Zero Cell 0P61)
Throughput
The Number of B LTE V4.16.10.20P
Re-establishment Requests 61(V3.40.20.1
20170902171018 Due to "Other Reason" on the 0P61)
FDD Sites is Increased
Suddenly
Handover Preparation Failed B LTE V4.16.10.20P
when UE hands over from 70(V3.40.20.1
20171211222411
Normal eNodeB to Sharing 0P70)
eNodeB
RRC Setup Success Rate B LTE V4.16.10.20P
Drops Sharply Because of 70(V3.40.20.1
20171214043047 Number of E-RAB Release 0P70)
Due to Uu Interface Timeout
increasing
Records with a Cell ID of B LTE V4.16.10.20P
20171117091909 65535 Exist in the Cell-level 70(V3.40.20.1
Counters' Statistics 0P70)
After upgrade to B LTE V4.16.10.20P
20171211110050
V3.40.20.10P50, VOLTE call 70(V3.40.20.1

dropped rate increases. 0P70)

After Upgrade to B LTE V4.16.10.20P
V4.16.10.20P50, An Abnormal 70(V3.40.20.1
20171209110551
FDD Product Process Causes 0P70)
the Baseband Board to Reset
The FTP Upload Rate is low B LTE V4.16.10.20P
20171204033111 Because of IPSec Packets 70(V3.40.20.1
Decrypting Abnormal 0P70)
Number of RRC Connection B LTE V4.16.10.20P
Users in Frequency 1.8G and 70(V3.40.20.1
20171205162142 2.6G is unevenly Distributed 0P70)
After the MR Inter-frequency
Measurement is Enabled
B LTE V4.16.10.20P
Parts of pRRUs Have No
20180125214144 70(V3.40.20.1
power for 2.6G QCell Site
0P70)
B LTE V4.16.10.20P
One Cell (CellID = 6) of A Site
20180111005819 70(V3.40.20.1
Setup Failure after Upgrading
0P70)
The AISG inventory C LTE V4.16.10.20P
information reported by the 70(V3.40.20.1
20180205143606 eNodeB is inaccurate 0P70)
LTE V4.16.10.20P
The Call Drop Rate is 80(V3.40.20.1
20180129141023 Deteriorated B 0P80)
LTE V4.16.10.20P
E-RAB Drop Rate is 80(V3.40.20.1
20180327161502 Increased C 0P80)
After One XGW on The LTE V4.16.10.20P
Network Goes Offline, some 80(V3.40.20.1
BS8922 Have Alarms:S1 0P80)
GTP-U path
20180309111551 unavailable(198094466) B
The Success Rate of RRC LTE V4.16.10.20P
Connection Setup Is 80(V3.40.20.1
20180326153047 Decreased C 0P80)

6.4 Solved LTE Issues Description
6.4.1 20160524164447 VoLTE RTP packet loss
Table 6-3 VoLTE RTP packet loss
Issue Name After the RoHC function is enabled, when the RTP SN value changes
from 65535 to 0, RTP packets are often lost at the receiving side and
RTP header decompression often fails.
Defect Number 20160524164447
Failure Level B
Bug Version V3.30.20.00B56
Symptoms The RoHC function is enabled, the VoLTE service is operating for at
least half an hour. Then the UE cannot hear any voice.
Impact The UE cannot hear any voice.
Analysis When the RTP SN changes from 65535 to 0, the eNodeB calculates
the difference between two continuous RTP SN values, which causes
the RTP TS value resolution error.
Solution Add corresponding judgment in the codes. When the RTP SN changes
from 65535 to 0, the difference between two continuous RTP SN
values must be added with 65536.
Verification Enable the RoHC function, and do the VoLTE service for at least half
an hour. The UE does not have the no-voice problem anymore.
Note None
From Operator China Unicom

6.4.2 20160624095904 Optical module alarms on multiple sites after

version upgrade to V3.3
Table 6-4 Optical module alarms on multiple sites after version upgrade to V3.3
Issue Name Optical module alarms on multiple sites after version upgrade to V3.3.
The alarm number is 198097510.
Alarm description: Mismatched optical module rate; Max available rate:
25.5 G, the rate optical module configured: 6G.
Failure Level D
Bug Version V3.30.20.21
Symptoms Information of the optical module cannot be read.
Impact The function and performance of the eNodeB is not affected.

Information of the optical module cannot be read.
Analysis The I2C SDA line is pulled down to GND when the optical module is
reset, causing the information about the optical module unable to be
read. BPN0 does not take protective measures for this exception when
accessing the optical module.
Solution Before the baseband board reads optical module information, make the
optical module forcedly exit bus occupation mode to ensure normal
information reading.
Verification When the equipment is operating, the alarm is not reported any more.
Note None
From Operator Chine Telecom
6.4.3 20160625183337 When an FDD LTE eNodeB is upgraded, the KPI

counter "C373505499 increases greatly
Table 6-5 When an FDD LTE eNodeB is upgraded), the KPI counter increases greatly
Issue Name When an FDD LTE eNodeB is upgraded from V3.20.50.30 P10 to
V3.30.20.11 (V3.30.20.21 _FTL), the KPI counter "C373505499: Num of
Abnormal Release Active E-rab" increases greatly.
Defect 20160625183337

Number
Failure Level C
Symptoms The operator-customized counter "Erab drop rate" increases greatly.
Impact KPI statistics fails, causing the counter C373505499: "Num of Abnormal
Release Active E-rab" to increase.
Analysis The cause values in the context release requests sent among modules
inside the eNodeB are incorrect.
Solution Check the cause values in the user-plane release requests and
configuration requests to ensure that the E-RAB Rel KPI is consistent
with the counter "Abnormal Release Active E-RAB".
Verification After using the new version in which the fault is removed, the counter
“C373505499: Num of Abnormal Release Active E-rab" deceases.
Note None
From Operator China Telecom
6.4.4 20160720085806 Super cell outage on 15 eNodeBs after version

upgrade due to "License limited"
Table 6-6 Super cell outage on 15 eNodeBs after version upgrade due to "License
limited"
Issue Name Supercell outage on 15 eNodeBs after version upgrade due to "License
limited"
Failure Level C
Symptoms After an eNodeB is upgraded, a cell outage alarm (license limited) is

reported. After the license limit is removed, the cell is out of service due
to RRU faults, and the cell outage alarm (license limited) is still
reported.
Impact The eNodeB services are not affected.
Analysis After a super cell reports a cell outage alarm (license limited), the alarm

cause cannot be updated when the cell outage reason is refreshed.
Solution When the cell outage reason is updated, refresh the corresponding
alarm cause and the corresponding alarm time.
Verification First, make a cell be out of service due to license limited and report a
cell alarm (license limited). Second, resolve the license limited problem
but make the RRUs fail. Then the cell alarm reason is refreshed to
RRU failure.
Note None
6.4.5 20160826231938 eSRVCC handover fails, causing abnormal UE

release
Table 6-7 eSRVCC handover fails, causing abnormal UE release
Issue Name eSRVCC handover fails, causing abnormal UE release
Failure Level C
Symptoms During the call process, both uplink and downlink voice packets exist.
At the same time, the UE performs eSRVCC handover, but the
handover fails and the call is released abnormally.
Impact During the call, the eSRVCC handover fails, and the call is abnormally
released.
Analysis Whether bSRVCC is avoided depends on whether there are uplink and
downlink voice packets simultaneously. However, in the call process
with uplink and downlink voice packets exist simultaneously, it also
may cause early termination of bSRVCC limit. Above reason will lead
to premature release restrictions, which triggered a bSRVCC switch,
resulting in switching failure.
Solution Add the threshold of RTP packets, which can be configured. When
there are multiple uplink and downlink voice packets simultaneously,
release the bSRVCC limit.
Verification Use a 4G UE to call a 2G UE. In the call process, perform eSRVCC

handover, and check whether the handover succeeds and whether the

call is released abnormally.
Note bSRVCC is the handover in the call setup process, which the core
network does not support, it makes handover failure; eSRVCC is the
handover in the call process.
From China Unicom

Operator
6.4.6 20160831112249 Downlink retransmission interval is large in the

VoLTE test
Table 6-8 Downlink retransmission interval is large in the VoLTE test
Issue Name Downlink retransmission interval is large in the VoLTE test
Failure Level C
Symptoms In the VoLTE test, the downlink retransmission interval is tens of

milliseconds, larger than 8ms, which is the usual retransmission
interval in the VoLTE test.
Impact The retransmitted data cannot be scheduled in a timely manner.
Analysis The UE does not receive the first Dci0 and enters Sleep mode when
the DRX InactiveTimer is timeout. When DCI0 is retransmitted, it is
considered as a new transmission, the Inactive Timer is started;
however, he UE cannot detect DCI0 because it is in Sleep mode.
Solution Enable the DRX function, make the eNodeB enter Sleep mode when
DTX is detected after DCI0 is receive for consecutive N times. It is
recommended that N is set to 3.
Verification Do VOLTE test, and get UE log. From the UE log analysis, there will be
no tens of ms long retransmission interval, and the user's normal
service is normal with no packet loss, voice card Dayton and other
phenomena.
Note None

6.4.7 20160914192815 In combination mode for the R8863 S2100, the

“Referenced Signal Power of BP Resource” of OMMB cannot be
configured to 18.2 db
Table 6-9 In combination mode for the R8863 S2100, the “Referenced Signal Power of
BP Resource” of OMMB cannot be configured to 18.2 db.
Issue Name In combination mode for the R8863 S2100, the “Referenced Signal
Power of BP Resource” of OMMB cannot be configured to 18.2 db.
Failure Level B
Symptoms When ”RF Unit Application Mode” of ”Baseband Resource” are

configured as ”Combination Mode”, ”Referenced Signal Power of
BP Resource” cannot be configured as the theoretical value18.2 db.
Impact The ”Referenced Signal Power of BP Resource' cannot be

configure to the theoretical value in ”RF Unit Application Mode”
of ”Baseband Resource”.
Analysis In the old project design, ”Real Transmit Power of BP Resource”

uses ”Number of Tx Antenna Port in Cell”, “Number of Tx Antenna
Port in Cell“ is equal to the “Downlink Ant Configure Bitmap“, but in
“Combination Mode“, “Number of Tx Antenna Port in Cell“ is not
equal to “Downlink Ant Configure Bitmap“.
Solution Modify the project design of “Real Transmit Power of BP Resource“,

in “Combination Mode“, use “Downlink Ant Configure Bitmap“ to
calculate “Real Transmit Power of BP Resource“.
Verification 1. Configure the R8863 S2100 in the OMMB.

2. Configure “Baseband Resource”, use the R8863 S2100 for this
record, and set 'RF Unit Application Mode' to ”Combination Mode”.
3. Configure the cell.
4. Check whether “Referenced Signal Power of BP Resource” can
be configured to 18.2 db.
Note None
From Operator None

6.4.8 20160918105816 Specific UEs cannot access the network after

upgrading from V3.20.50.20 P10 to V3.30.20.30
Table 6-10 Specific UEs cannot access the network after upgrading from V3.20.50.20
P10 to V3.30.20.30
Issue Name Specific UEs cannot access the network after upgrading from
V3.20.50.20 P10 to V3.30.20.30

20160916090249
20160928103703
Failure Level B
Symptoms Specific UEs cannot access the network after upgrading from
V3.20.50.20 P10 to V3.30.20.30. The specific UEs are outdated and do
not use Qualcomm chips. Signal strength, eNBID and CellID of the test
site can be learned from the dial-up software. UE has decoded SIB1
and is downlink synchronized, but there is no random access. The UEs
can access the network after version rollback.
Impact Specific UEs cannot access the network.
Analysis Due to R10 protocol upgrade, two Release-10 uplink power control
parameters (deltaF_PUCCH_Format1bCS_r10 and
deltaF_PUCCH_Format3_r10) are added in the upgraded version in
sib2, hand-over request and hand-over reconfiguration. The specific
UEs do not support Release-10 content, and thus after the new
contents in sib are decoded, errors occur and random access is not
initiated.
Solution The eNodeB makes compatibility protection processing, in which a

switch is added to control whether to fulfill the two Release-10 uplink
power control parameters (deltaF_PUCCH_Format1bCS_r10 and
deltaF_PUCCH_Format3_r10).
The switches can be configured flexibly according to specific
requirements of the field.
Verification Modify the configuration of the switches to make the eNodeB not to
fulfill the two Release-10 uplink power control parameters
(deltaF_PUCCH_Format1bCS_r10 and
deltaF_PUCCH_Format3_r10). Check whether it is not filled in sib2, ho

request and ho reconfiguration. Check whether the specific UE can

access the network successfully.
Note None
From Operator Commnet
6.4.9 20160918174531 RRC request rejected due to eNodeB admit failure
Table 6-11 RRC request rejected Due to eNodeB admit failure
Issue Name RRC request rejected Due to eNodeB admit failure
Failure Level B-serious
Symptoms The RRC establishment success rate is extremely low, and the failure
cause is "eNodeB admit failure". The average number of RRC users
does not change obviously. The CPU utilization is not high.
Impact The UE access success rate, incoming handover success rate, and
reestablishment success rate are affected.
Analysis The number of cells and BPx users that the eNodeB maintains is larger
than the actual number of RRC users. It causes that, when a UE
attempts to access the network, perform incoming handover, or
perform reestablishment, the number of RRC users used for
determination is larger than the threshold, restricting the new RRC
establishment.
Solution Modify the error statistics points of the number of cell and BPL RRC
users.
Verification When the real number of RRC users is not large, the "eNodeB admit
fail" alarm is not reported.
Note None

6.4.10 20160923051749 After the system is upgraded to V3.3.20 P40, the

incoming handover failure rates on S1 and X2 increase
Table 6-12 After the system is upgraded to V3.3.20 P40, the incoming handover failure
rates on S1 and X2 interfaces increase
Issue Name After the system is upgraded to V3.3.20 P40, the incoming handover
failure rates on S1 and X2 interfaces increase.
Failure Level B
Symptoms After the system is upgraded to V3.3.20 P40, the incoming handover
failure rates on S1 and X2 interfaces increase.
Impact The handover success rates on S1 and X2 interfaces are low.
Analysis After the magic radio function is enabled at the handover target side,
the bandwidth information carried in the handover ACK message is
incorrect, causing UE reconfiguration failure and handover failure.
Solution After the magic radio function is enabled, re-load the correct bandwidth
to the cell.
Verification Enable the magic radio function, configure different bandwidths, and
check whether handover can succeed.
Note None
From Operator MTN
6.4.11 20160927093722 High call drop rate due to the PERIOD_TA_MEAS

option selected for the MR task
Table 6-13 High dropped call rate due to the PERIOD_TA_MEAS option selected for
the MR task
Issue Name High call drop rate due to the PERIOD_TA_MEAS option selected for
the MR task
Failure Level B

Symptoms The call drop rate increases at some eNodeBs. After clearing the
PERIOD_TA_MEAS option for the MR task, the call drop rate becomes
normal.
Impact The dropped call rates of some eNodeBs are affected.
Analysis Some UEs do not support reporting Rx-Tx time difference. The LTE
V3.3 eNodeB does not judge whether a UE has the capability of
reporting Rx-Tx time difference and directly sends the UE Rx-TX Time
Diff parameter carried by an Rrcconnectionreconfiguration message to
UEs. Thus the UEs that do not have the capability are dropped.
Solution The eNodeBs of LTE V3.4 can judge UE capability. The Rx-TX Time
Diff parameter is issued to UEs that satisfy the following conditions:
The UE version is no later than R11; The UE supports reporting Rx-Tx
time difference.
Verification Verification methods:

1. For UEs that supports reporting Rx-Tx time difference and whose
versions are no later than R11, the Rx-Tx Time Diff parameter carried
by an Rrcconnectionreconfiguration message is sent normally by the
eNodeB, and the UE services are not affected.
2. For UEs that do not support reporting Rx-Tx time difference and
whose versions are no later than R11, the Rx-Tx Time Diff parameter
carried by an Rrcconnectionreconfiguration message is not sent by the
eNodeB, and the UE services are not affected.
3. For UEs that do not support reporting Rx-Tx time difference and
whose versions are no earlier than R10, the Rx-Tx Time Diff parameter
carried by an Rrcconnectionreconfiguration message is not sent
normally by the eNodeB, and the UE services are not affected.
Note None

6.4.12 20161009150741 Large Number of messages indicating context

modification failure due to other causes after system upgrade to
V3.3
Table 6-14 Large number of messages indicating context modification failure due to
other causes after system upgrade to V3.3
Issue Name Large number of messages indicating context modification failure due
to other causes after system upgrade to V3.3
Failure Level B
Symptoms The MME sends messages of context modification request to the

eNodeB, and the messages carry CSFB and AMBR. The eNodeB
reports other cause of UE context modify KPI.
Impact The context modification success rate is reduced.
Analysis The MME sends context modification request messages carrying

CSFB and AMBR to the eNodeB. The eNodeB processes CSFB first
and buffers AMBR. After CSFB is processed successfully, the
eNodeB reports a KPI of context modification success carrying
CSFB; At the same time, the eNodeB reports a KPI of context
modification failure carrying other causes.
Solution After CSFB processing succeeds, the eNodeB only reports the
context modification success messages carrying CSFB.

Trigger the MME to send a message of context modification request
to the eNodeB, the message carrying CSFB and AMBR. The eNodeB
processes the CSFB successfully.
Pass criterion:
The eNodeB only reports context modification requests and context
modification success KPI.
Note None
From Operator Indonesia TSL

6.4.13 20161025110052 Scheduling according to DRX Enabling when Cell

Connect Reestablishment with DRX is disabled
Table 6-15 Scheduling according to DRX Enable when Cell Connect Reestablishment
with DRX is disabled
Issue Name Scheduling according to DRX Enable when Cell Connect

Reestablishment with DRX is disabled
Failure Level C
Bug Version V3.20.50.30B170P33
Symptoms The UL/DL traffic of a UE cannot reach the peak throughput when the
eNodeB is upgraded to V3.20.50.32.
Impact The UL/DL peak throughput is affected when there is only one UE in
the cell.
Analysis The RNLC sends a DRX Reconfiguration with connect reestablishment

message to the baseband, and DRX DrxEnable is zero but other
parameters are not zero. Thus, the baseband starts the DRX on
duration timer.
Solution The baseband receives a reconfiguration message. If DRX DrxEnable

is zero, the master control module sets other DRX parameters to zero.
Verification The UL/DL traffic can reach the cell peak throughput when there is only
one UE in the cell.
Note None
6.4.14 20161101151720 CSFB failure
Table 6-16 CSFB failure
Issue Name CSFB failure
Failure Level B

Symptoms It is complained that the voice service cannot be used and then a
short message indicating a missed call is received. It is found that the
4G CSFB signaling processes are completed, but the voice service is
not started at the 3G site and only a location update operation is
performed. About 20 seconds later, the UE returns to the 4G network.
After disabling or enabling the RIM switch, the voice service becomes
normal. It is diagnosed that the RIM function fails.
Impact Users cannot use voice services properly.
Analysis The RIM cannot resend the RIM initial request due to the aging timer
becoming invalid when the eNodeB is working. But, after the 3G
eNodeB is upgraded, the 3G system information changes and the 3G
eNodeB does not report the changed system information to the 4G
eNodeB because there is no RIM connection. Therefore, the 3G
system information differs from that on the 4G eNodeB. Finally, it
causes the UE to carry error system information in CSFB processes
and the voice service fails.
Solution This problem is a known fault, and can be resolved by using the hotfix
for repairing the problem of RIM aging timer.
Verification Disable the RIM switch, update the hotfix, and enable the RIM Switch.
The CSFB voice service becomes normal.
Note None
From Operator Thailand AIS
6.4.15 20161107045420 BPL1 board reset repeatedly due to more than 64

UTRAN neighbor cells after SDR15 version upgrade
Table 6-17 BPL1 board reset repeatedly due to more than 64 UTRAN neighbor cells
after SDR15 version upgrade
Issue Name BPL1 board reset repeatedly due to more than 64 UTRAN neighbor
cells after SDR15 version upgrade
Failure Level B
Bug Version V3.30.20.30P10
Symptoms After SDR15 is upgraded, the number of UTRAN neighbor cells is more
than 64 for one serving cell, the CC board is reset, causing the BPL

board to reset repeatedly.
Impact The CC board is reset, causing the BPL board to reset repeatedly.
Analysis The array size of the UTRAN neighbor cells defined by eNodeB is 64.
When the number of UTRAN neighbors in a cell exceeds 64, the
UTRAN neighbor array is defined to be overwritten, resulting in BPL1
reset.
Solution The array size of the UTRAN neighbor cells defined by the eNodeB is
expanded to 128
Verification Configure 128 UTRAN neighbor cells for one serving cell, and make a
UE access the cell. The eNodeB does not reset.
Note None
From Operator MTN Group
6.4.16 20161107094430 eNodeB KPI (downlink transmission bandwidth

(megabit/s)) abnormal
Table 6-18 eNodeB KPI (downlink transmission bandwidth (megabit/s)) abnormal
Issue Name eNodeB KPI (downlink transmission bandwidth (megabit/s)) abnormal
Failure Level C
Symptoms For most eNodeBs, the downlink transmission bandwidth (megabit/s)

configuration is 1000 M, but performance statistics indicates that it is
100 M for some CCE1 eNodeBs.
Impact The eNodeB KPI statistics are abnormal.
Analysis The BRS only counts bandwidth configuration information about abis0,
otherwise the statistics value is set to the default value 100 M.
Solution In downlink bandwidth statistics, the BRS does not count the
configuration information about abis0. Instead, the actual bandwidth
value in the BRS module is counted.
Verification Configure 1000 M bandwidth on the abis2 interface, and then check
whether the downlink bandwidth statistics are correct.

Note None
6.4.17 20161107115518 Five cells disconnected and having no msg1
Table 6-19 Five cells disconnected and having no msg1
Issue Name Five cells disconnected and having no msg1
Failure Level B
Symptoms After the license file is loaded, the cell cannot be accessed.
Impact Cells cannot be accessed.
Analysis After the license file is loaded, the MO module is triggered to do data
conversion. The data conversion method is wrong, causing cell adding
and deleting, IQ configuration error, and cell access failure.
Solution Modify the data conversion method for the MO module.
Verification Load the license file repeatedly. No cell is added or deleted.
Note None
6.4.18 20161118091237 GL RRU having parameter configuration error

alarms after system upgrade to V4.15
Table 6-20 GL RRU having parameter configuration error alarms after system upgrade
to V4.15
Issue Name GL RRU having parameter configuration error alarms after system
upgrade to V4.15
Failure Level C

Symptoms On RSU82 (GUL1816), GL mode is used, GSM frequency hopping is

configured on the two channels, and frequency hopping is performed
on the two sides of the LTE band. An alarm “Parameter configuration
error (198098464)” is reported.
Impact This alarm is incorrect, and the services are not affected.
Analysis The software has bugs. For RSU82 (GUL1816), if GL mode is

configured for the two channels and GSM frequency hopping is used, it
is possible for the two channels that frequency hopping is performed
from a GSM carrier to both sides of an LTE carrier (namely, a carrier
may have some FH frequency points larger than LTE frequency points
and some FH frequency points smaller than LTE frequency points.)
Solution Upgrade the hotfix version to

COMMON_HOTPATCH_4.15.10.20P51H02.pkg. After the first
upgrade, for RRUs having the alarm, block and unblock any cell to
trigger the configuration reissuing procedure.
Verification After the alarm is reported, upgrade the hotfix. Then, block and unblock
a cell to trigger the configuration reissuing procedure. No alarm
“Parameter configuration error (198098464)” is reported.
Note None
From Operator MTN
6.4.19 20161122003533 Secondary carrier RB insufficiency in CA handover
Table 6-21 Secondary carrier RB insufficiency in CA handover
Issue Name Secondary carrier RB insufficiency in CA handover
Failure Level B
Symptoms When a UE performs handover from a CA site to a common cell, the

handover and service are normal. When the UE performs handover
from a common cell to a CA site, the signaling is normal but the
secondary carrier traffic is low and the number of scheduled RBs is
only about 20. When repeating the problem, the secondary carrier
traffic is zero, and the MCS and RB amount is almost zero. Then the
UE is still in the CA cell. Lower the signal strength in the secondary

carrier cell, deactivate the secondary carrier, lift the secondary carrier
signal, and activate the secondary carrier. Then, the RB scheduling
becomes normal.
Impact The UE traffic is not enough.
Analysis The original HARQ instance is not released in cell handover, causing
the HARQ instance to hang.
Solution Release the HARQ instance in intra-cell handover.
Verification The secondary carrier traffic in intra-cell handover is normal.
Note None
From Operator Hi3G
6.4.20 20161122112839 Probabilistic call failure due to UE not responding

to Paging messages in reestablishment scenarios for the CSFB test
Table 6-22 Probabilistic call failure due to UE not responding to Paging messages in
reestablishment scenarios for the CSFB test
Issue Name Probabilistic call failure due to UE not responding to Paging messages
in reestablishment scenarios for the CSFB test
Failure Level B-serious
Symptoms After the UE receives a reestablishment complete message, it receives

RLF indication and cs notification messages from the eNodeB
simultaneously. The UE only process the RLF request message and
does not respond to the cs notification message, and does not process
paging messages for a long time.
Impact The paging messages are not processed.
Analysis The eNodeB implementation does not comply with the protocol. SRB1
and SRB2 are suspended in the reestablishment process. According to
protocol, SRB1 is resumed after the RRC reestablish complete
message is received. If the eNodeB receives a downlink NAS message
(CSFB), it should send it to the UE after SRB2 is resumed, but now the
eNodeB sends the message on SRB1. After that, the UE receives a
downlink message, and it does nothing in spite of

SRB2 being resumed.
Solution Send the downlink NAS message after SRB2 is resumed.
Verification If the eNodeB receives a downlink NAS message during

reestablishment, it should buffer the message. When the eNodeB
receives a drb rrc reconfiguration completion message, it sends the
message to the UE.
Note None
6.4.21 20161220114504 Admission failure on eNodeBs with CA function
Table 6-23 Admission failure on eNodeBs with CA function
Issue Name Admission failure on eNodeBs with CA function
Failure Level B
Symptoms In a CA scenario, the number of users of the secondary carrier

increases abnormally in KPI statistics, causing the total number of
users of primary and secondary carriers reaches the board-level
admission threshold. As a result, the subsequent UEs fail to be
admitted.
Impact The KPI statistics are abnormal, and UEs fail to be admitted.
Analysis When the number of users of the secondary carrier is counted, the
abnormal release procedure of the secondary carrier UE instance is not
considered, where the number of users should be decremented by
one.
Solution Consider the abnormal release procedure of the secondary carrier UE

instance, and decrease the number of users by one during the
abnormal release procedure.
Verification Observe KPIs including the number of users of scell and the access
success rate to see whether the KPIs are normal and whether the
access failure problem occurs again.
Note None

6.4.22 20170105095756 eNodeB using a temporary License file in default

state for a moment after system upgrade from V3.3 to V3.4
Table 6-24 eNodeB using a temporary License file in default state for a moment after
system upgrade from V3.3 to V3.4
Issue Name eNodeB using a temporary License file in default state for a moment
after system upgrade from V3.3 to V3.4
Failure Level C
Symptoms Synchronization fails.
Impact The eNodeB cannot get the new configuration for a moment.
Analysis The interface from DBS has some problems when fields are added to
the table, and LMP can just get the first record to use this interface.
Solution Perform handling properly when adding fields to the table.
Verification When the eNodeB is upgraded from V3.3 to V3.4, perform incremental
synchronization, verify if the synchronization is normal.
Note None
6.4.23 20170116100312 No downlink traffic after handover from a ZTE eNB

to a Nokia eNB
Table 6-25 No downlink traffic after handover from a ZTE eNB to a Nokia eNB
Issue Name No downlink traffic after handover from a ZTE eNB to a Nokia eNB

614005678143
Failure Level B

Symptoms The downlink traffic drops to 0 after X2 handover from the ZTE
eNB to the Nokia eNB.
But the downlink traffic is normal after S1 handover.
Impact The downlink traffic is affected.
Analysis The ZTE eNB converts

TS1AP_InitialContextSetupRequest_protocolIEs' s Dl AMBR to
KB to save, and then converts AMBR to BYTE when the UE
performs X2 handover to the Nokia eNB. By AMBR conversion, X2
handover request’s AMBR is different from
TS1AP_InitialContextSetupRequest_protocolIEs's AMBR and
exceed 32bit boundary (from 4294967000 to 4294968000). But
the Nokia eNB only supports 32 bit AMBR and saves AMBR low
32 bit (704), causing downlink traffic to drop to 0.
Solution The ZTE eNB saves the downlink AMBR original value and does
not convert to KB.
Verification Set AMBR to 4294967000, the UE downlink traffic does not

change after X2 handover to the Nokia eNB.
Note None
6.4.24 20170220160622 In six cells with 4 ant mode, one of the cells on
BPL1 setup fail
Table 6-26 In six cells 4 ant mode，one of the cells on BPL1 setup fail
Issue Name In six cells with 4 ant mode, one of the cells on BPL1 setup fail

614005576867
Failure Level C
Bug Version V3.40.10
Symptoms In six cells with 4 ant mode, one of the cells on BPL1 setup fail, and UE
can't attach.
Impact In six cells 4 ant mode, one of the cells on BPL1 setup fail.
Analysis The doorbell receive buffer is not enough.

Issue Name In six cells with 4 ant mode, one of the cells on BPL1 setup fail
Solution Increase the doorbell receive buffer.
Verification In six cell 4 ant mode, make sure all of the cells can be setup success.
Note None
From Operator quanzhou city,fujian province
6.4.25 20170112055252 After activating the speedtest switch, UE executing

speedtest preempts RB resources
Table 6-27 Activate the speedtest switch, UE executing speedtest preempts RB

resources
Issue Name After activating speedtest switch, UE executing speedtest

preempts RB resources
Failure Level B
Symptoms
Activate the speedtest switch at EMS, two CA UEs perform DL
FTP or UDP download simultaneously. One of the two UE
performs the speedtest, its Scell throughput increases and
preempts the RB resources of the other UE who is not performing
the speedtest.
Impact UE executing speedtest preempts RB resources, impacting the

other UEs’ throughput.
Analysis For CR scenario, the version does not support the T3 timer being
set to 1ms, which fails to obtain the expected result.
Solution Set T3 timer to 3ms for CR scenario.

1. Activate the speedtest switch.
2. When two CA UEs perform DL FTP or UDP download
simultaneously, one of the two UE performs the speedtest.
Pass Criterion:

Issue Name After activating speedtest switch, UE executing speedtest

preempts RB resources
For CR scenario, UE executing speedtest does not preempt RB

resources.
Note None
From Operator Austria
6.4.26 20170131000002 The self-defined CSFB failure times are found

minus after upgrading from UR14 to UR15
Table 6-28 The self-defined CSFB failure times are found minus after upgrading from
UR14 to UR15
Issue Name The self-defined CSFB failure times are found minus after
upgrading from UR14 to UR15
Failure Level C
Symptoms The self-defined CSFB failure times are found minus after UR14
upgraded to UR15.
Impact CSFB success rate is reduced.
Analysis UR15 reports the “CSFB carried context modification request” and
“CSFB carried context establishment request” every 2s, which is
later than KPI report of event triggered CSFB re-direction. It
results the former report times are less than the later one.
Solution Modify the CSFB redirection KPI report to periodically report.
Verification Test CSFB process for several times, check whether there is
minus in CSFB KPI statistics.
Note None
From Operator None

6.4.27 20170203111053 C373384345 Average User Number Cat 6 was

reduced after upgrading to 4.15.10.30P30.
Table 6-29 C373384345 Cat3 Average User Number did not change, Cat 6 was
reduced after upgrading to 4.15.10.30P30.
Issue Name C373384345 Average User Number Cat 6 was reduced after
upgrading to 4.15.10.30P30.
Failure Level B
Symptoms C373384345 Cat3 Average User Number did not change, Cat 6
was reduced after upgrading to 4.15.10.30P30.
Impact Cat6 Average User Number is reduced.
Analysis V3.3 upgrades to the R11 protocol. The Cat user number is
reported as Max Cat that UE supports. While the FDD in KPI rule
library does not support Cat 9-11 report. Some Cat6 users
become Cat9, which are not reported. Therefore, Cat6 user
number is reduced.
Solution Modify the KPI rule library; enable FDD to support Cat9-11 report.
Verification Use UE that supports Cat9 to perform test and check whether
Cat9 user number is reported normally.
Note None
From Operator None
6.4.28 20170215060648 UE fails to execute intra-frequency handover for

SRVCC based on signal quality
Table 6-30 UE fails to execute intra-frequency handover for SRVCC based on signal
quality
Issue Name The UE fails to execute intra-frequency handover for SRVCC

based on signal quality

Issue Name The UE fails to execute intra-frequency handover for SRVCC

based on signal quality
Failure Level C
Symptoms The eNodeB initiates the SRVCC procedure based on signal quality
according to the MCS message. The RSRP which is -85 now is very
good. The intra-frequency A3 measurement is deleted from the
reallocation message. As a result, the terminal fails to execute
intra-frequency handover during the period-104＜RSRP＜-85 (the
threshold of B2 serving cell is -104).
Impact Within a certain period of time, handover is not possible unless

there is B2 measurement report. Meanwhile, intra-frequency
handover is not allowed.
Analysis Regarding the SRVCC procedure based on signal quality, the

measurement event already delivered is deleted while sending the
B2 measurement report.
Solution Modify the SRVCC procedure based on signal quality. Do not delete
the measurement event already delivered while sending the B2
measurement report.
Verification Trigger an SRVCC procedure based on signal quality to check the

reallocation message whether the measurement event delivered
has been deleted.
Note None
From Operator None
6.4.29 20170216211458 Signal quality based SRVCC has no protection

mechanism during threshold triggering
Table 6-31 Signal quality based SRVCC has no protection mechanism during threshold
triggering
Issue Name Signal quality based SRVCC has no protection mechanism during
threshold triggering
Failure Level B

Issue Name Signal quality based SRVCC has no protection mechanism during
threshold triggering
Symptoms When the signal quality based SRVCC is performed under the
current version, once MCS or SINR reaches the threshold, the
re-allocation message with B2 included is directly delivered to
activate SRVCC.
Impact SRVCC related features enabling is affected.
Analysis When the signal quality based SRVCC is performed under the
current version, once MCS or SINR reaches the threshold, the
re-allocation message with B2 event included is directly delivered,
making no time to buffer.
Solution When eNB finds that SINR or MCS reaches the threshold, it
enables the timer. If SINR or MCS still reaches the threshold after
the timer expires, eNB delivers the re-allocation message with B2
event included. If the timer does not expire, and SINR does not
reach the threshold, the timer will be stopped and no re-allocation
message with B2 event included is delivered to UE. Such design
aims to prevent the SRVCC re-allocation due to the MCS and
SINR’s sudden change.
Verification When performing signal quality based SRVCC, once MCS or SINR
reaches the threshold, a timer is set to control the time buffering.
The re-allocation message with B2 event included is delivered only
when the timer expires.
Note None
From Operator None
6.4.30 20170214031031 When eNodeB upgrades to a new version, the CDT

data does not contain CT signal
Table 6-32 When eNodeB upgrade to a new version, the CDT data does not contain
CT signal
Failure Level B

Symptoms Send eNodeB-level CDT task only, the CT signaling does not contain
abnormal signal; when sending whole network-level CDT task, the CT
signaling is not reported.
Impact Send eNodeB-level CDT task only or whole network level CDT task,
the CT is not used.
Analysis Send eNodeB-level CDT task only, the signaling after UE is activated
are not buffered. Send whole network-level CDT task, the CT flag of
cell is not set.
Solution Send eNodeB level CDT task, the signals after UE is active are
buffered. Send whole network level CDT task and set the CT flag of
cell.
Verification Send whole network level CDT task to eNodeB and check the integrity
of the CT signal when UE is abnormal.
Note None
6.4.31 20170213205208 After Fast Return to the 1.8G LTE cell in CSFB
procedure, UE handover to higher 2.6 G PCELL frequency, and then
UE can’t receive Modify EPS bearer context request message from
MME
Table 6-33 After FAST RETURN to the 1.8G LTE cell in CSFB procedure, UE handover
to higher 2.6 G PCELL frequency, and then UE can’t receive Modify EPS bearer
context request message from MME
Failure Level B
Symptoms The eNodeB receives ERAB MODIFY REQUEST from MME and
replies E-RAB MODIFY RESPONSE to MME with reason that is
unspecified when the UE handover from the cell with 1.8G to the cell
with 2.6G with higher frequency priority in the scenario of CA PCELL
frequency priority function is enabled.
Impact It will affect the ERAB modifying success rate when CA PCELL
frequency priority function is enabled.

Analysis The eNodeB receives ERAB MODIFY REQUEST from MME and
buffers this message in the process of the blinding-ho timer is running,
after the timer expired, the system will throw HO message into
buffering queue, the HO message will preempt the ERAB MODIFY
REQUEST message that is previously buffered, and this will lead to the
ERAB modify failure.
Solution Separate the blinding-ho timer from the blinding-ho process based CA
PCELL frequency priority function, and start the timer first, then
execute the blinding-ho process, if the eNodeB receives any message
from MME and will handle with it normally while the timer is running.
Verification Enable CA PCELL frequency priority function, then Attach CA UE into

LTE cell with low priority frequency and trigger blind-ho, execute ERAB
MODIFY operation during hand-over process, Observe whether
ERAB MODIFY operation is executed successfully and blind-ho is
processed successfully.
Note
From Operator Austria Hi3G
6.4.32 20170127081650 The load balance UE which has fast return to LTE
cell after CSFB cannot receive the S1 Modify EPS bearer context
request message
Table 6-34 the load balance UE which has fast return to LTE cell after CSFB cannot
receive the S1 Modify EPS bearer context request message

614005694025
Failure Level B
Symptoms The load balance UE which has fast return to LTE cell after CSFB
cannot receive the S1 Modify EPS bearer context request message
Impact The rate of UE cannot be modified to LTE rate.
Analysis After attach LTE network, the UE should wait a moment to handover,
because of the code error, the wait time cannot handle other message.
Solution If UE receive other message in the waiting time, UE can handle.

Verification Configure the EMS, make the UE can load balance to intra eNB cell,
then CSFB the UE, and fast return to LTE net, send Modify EPS
bearer context request to UE and can modify success, then load
balance to the other cell.
Note None
6.4.33 20170303172448 RRC Release After an Initial Message is Sent to the

New MME
Table 6-35 RRC Release After an Initial Message is Sent to the New MME
Issue Name RRC Release After an Initial Message is Sent to the New MME
Defect 20170303172448
Number
Failure Level B
Symptom After the eNodeB connects to a new MME, the RRC connection is
released.
Impact UEs cannot be connected to the new MME successfully.
Analysis After the eNodeB connects to an MME, the relative capability of the
MME is 0. When the relative capability of the MME at the eNodeB side
is 0, new UEs are barred from connecting to it.
Solution Optimize the process at the eNodeB side to ensure that UEs can
connect to it properly when the relative capability of the MME is 0.

Connect the eNodeB to an MME, and verify that the relative capability
of the MME is 0.
Criteria:
The UE can be connected to the MME properly.
Note None
Source FDD overseas; Ecuador office

6.4.34 20170303151948 The eNodeB Name and Cell Name Is Abnormal in

Performance Data Query
Table 6-36 The eNodeB Name and Cell Name Is Abnormal in Performance Data Query
Issue Name The eNodeB Name and Cell Name Is Abnormal in Performance Data
Query
Defect 20170303151948
Number
Failure Level C – Minor
Bug Version V3.2
Symptom The eNodeB keeps reporting the neighbor cell information transmitted
from the X2 interface to the NM server, resulting in a congestion of
messages on the NM server.
Impact This fault affects the normal message processing flow of the NM
server, causing some query functions to be unavailable.
Analysis While reporting updated configuration data to the NM server, the

eNodeB compares the whole neighbor cell PlmnList in the
configuration data between the NM server and the eNodeB, but does
not compare the first PlmnNum number of PLMNs.
Solution While reporting updated configuration data to the NM server, the

eNodeB only compares the first PlmnNum number of PLMNs.
Verification On the NM server, if a cell acts as a neighbor cell, configure two

PLMNs; if a cell acts as a serving cell, configure one PLMN.
After the front-end system reports one configuration parameter update
message to the NM server, it no longer reports this message again. In
addition, cellid and eNodeBid are displayed correctly in the
performance query results.
Note None
Source India Bharti

6.4.35 20170302103414 Decrease of the LTE CSFB SR Indicator from 99.9%

Before Upgrade to 99.4% After Upgrade With a Deterioration Rate of
0.5%
Table 6-37 Decrease of the LTE CSFB SR Indicator from 99.9% Before Upgrade to
99.4% After Upgrade With a Deterioration Rate of 0.5%
Issue Name Decrease of the LTE CSFB SR Indicator from 99.9% Before Upgrade
to 99.4% After Upgrade With a Deterioration Rate of 0.5%
Defect 20170302103414
Number 614005738174
Failure Level B
Symptom During the X2 handover process, after receiving the UE Context

Modification Req message, the eNodeB returns a UE Context
Modification Failure response directly (carrying the reason of
X2HandoverTrigger).
Impact This fault affects the scenario under which the UE Context Modification
Req message is received during the S1 and X2 handover processes.
With this fault, UEs are released directly.
Analysis When the X2 handover destination side is waiting for the EndMarker or
during the initial measurement process, if the received UE Context
Modification Request only carries the CSFB, it is the preemption policy
for the S1/X2 destination side. The preemption policy will terminate the
previous process.
However, if the previous process is not protected, the system proceeds
to the final processing flow. At this time, in an unprotected process, the
eNodeB releases the UE. Before the release, it rejects the UE context
modification request and returns a UE context modification failure to
the CN.
Solution For the scenario in which a UE context modification request carries the
CSFB/AMBR MOD/CSFB AMBR MOD, modify the processing policy at
the destination side of inter-eNodeB handover by changing the policy
of terminate the previous process and caching new messages caching
new messages to caching new messages.

During the X2/S1 handover process, after the target eNodeB sends a

reconfiguration message and before it receives a reconfiguration

complete message, a UE context modification request (carrying CSFB)
is received from the CN side.
Criteria:
The UE is not released. After handover is completed, the eNodeB
processes the UE context modification request.
Note None
Source Peru Bitel
6.4.36 20170301102122 Voices Not Heard Clearly in Some Cases When F7

Mobile Phones Call Samsung Mobile Phones
Table 6-38 Voices Not Heard Clearly in Some Cases When F7 Mobile Phones Call
Samsung Mobile Phones
Issue Name Voices Not Heard Clearly in Some Cases When F7 Mobile Phones Call
Samsung Mobile Phones
Defect 20170301102122
Number
Failure Level B
Symptom When a user uses a MATE7 mobile phone to initiate voice services,
according to the analysis of packets captured at the eNodeB side, it is
found that there is a serious loss of uplink packets due to ROHC
decompression failures.
Impact The quality of voice services is poor.
Analysis If ROHC is enabled, the eNodeB does not notify the UE to change its
mode in a timely manner. As a result, when a decompression failure
occurs on the eNodeB, the UE cannot process the returned status
report properly.
Solution The eNodeB can notify UEs to change the mode in a timely manner.
Verification When MATE7 and other phones call each other, voices can be heard
clearly.
Note None
Source Combodia

6.4.37 20170228092821 Abnormal Value in the KPI Statistical Results of a

Field Site
Table 6-39 Abnormal Value in the KPI Statistical Results of a Field Site
Issue Name Abnormal Value in the KPI Statistical Results of a Field Site
Defect 20170228092821
Number
Failure Level B
Symptom Within the first 15-minute granularity after the eNodeB is restarted, the
cell not-in-service time ("C373230703:Cell BBU Abnormal Time(s)") is
29049, this value is abnormal.
Impact The cell not-in-service time is abnormal.
Analysis After being restarted, the eNodeB fails to obtain the system time until
the 15-minute service protection & compensation mechanism fails.
Solution Optimize the protection & compensation algorithm by replacing the

time acquisition interface to eliminate the impact of exceptionally great
values.
Verification Observe the cell in-service time within the first granularity after the
eNodeB is restarted.
Note None
Source FDD overseas; South Africa MTN
6.4.38 20170224120329 Increased UL IP Throughput After the eNodeB

Upgraded From V3.2 to V3.3
Table 6-40 Increased UL IP Throughput After the eNodeB Upgraded From V3.2 to V3.3
in the LTE Project
Issue Name Increased UL IP Throughput After the eNodeB Version Was Upgraded
From V3.2 to V3.3
Defect 20170224120329
Number
Failure Level B

Symptom The statistics of the UL IP Throughput is greater than the actual value.
Impact The statistics of the UL IP Throughput is inaccurate.
Analysis The statistics of the UL IP Throughput only includes the scheduling

time, but does not include the time of waiting for the scheduling of
packets.
Solution The statistics of the UL IP Throughput includes all service transmission

time.

Connect a UE to the eNodeB and perform the full-scheduling FTP
service test.
Criteria:
Compare the UL IP Throughput with the UE rate, and verify that they
are basically consistent.
Note None
Source Malaysia webe(TM)
6.4.39 20170207222615 Deterioration of the E-RAB Call Drop Rate After the
eNodeB Upgraded from 4.13.10.30P42 to 4.15.10.20P51
Table 6-41 Deterioration of the E-RAB Call Drop Rate After Version Upgrade from
4.13.10.30P42 to 4.15.10.20P51
Issue Name Deterioration of the E-RAB Call Drop Indicator After Version Upgrade
from 4.13.10.30P42 to 4.15.10.20P51
Defect 20161210174505
Number 614005620673
20170207222615
Failure Level B
Bug Version LTE-V3.30.20.51P20
Symptom During the handover of data services, the operation fails and the
corresponding UE is released.
Impact The RRC and ERAB call drop rate are increased.
Analysis The uplink data forward function is not enabled on the eNodeB at the

target handover side. However, the user-plane uplink forward function

is incorrectly configured on the eNodeB at the source handover side.
As a result, the source side returns a failure due to a user-plane
parameter check error, and thereby releases the UE.
Solution When the uplink forward function is not enabled on the eNodeB at the
target handover side, it is not configured for the user plane.
Verification Perform a downlink service and a handover operation. Verify that the
UE is not released abnormally.
Note None
Source Belgium KPN
6.4.40 20170206173525 Active E-RAB Drop Rate Increase After Upgrading

to V3.3
Table 6-42 Active E-RAB Drop Rate Increase After Upgrading to V3.3
Issue Name Active E-RAB Drop Rate Increase After Upgrading to V3.3
Defect 614005692881
Number 20170206173525
Failure Level C
Bug Version NB_V4.15.10.30P30
Symptom The active E-RAB drop rate is increased.
Impact The active E-RAB drop rate is increased.
Analysis After successful handover from the LTE to the UTRAN, when the
E-RAB at the handover source side is released, the carried reason
value is incorrect. As a result, incorrect KPIs are reported during
E-RAB release.
Solution After handover is successful, set the correct reason during E-RAB
release.
Verification Trigger inter-system handover with data services. After handover is

successful, check the E-RAB call drop counter and verify that its value
is 0.
Note None
Source Belgium BASE project

6.4.41 20170206172312 Serious Decrease in the CQI , Equivalent

Throughput and 64QAM After the BPL0 Site Was Upgraded from V3.2
to V3.3
Table 6-43 Serious Decrease in the CQI, Equivalent Throughput and 64QAM After the
BPL0 Site Was Upgraded from V3.2 to V3.3
Issue Name Serious Decrease in the CQI, Equivalent Throughput and 64QAM After
the BPL0 Site Was Upgraded from V3.2 to V3.3
Defect 20170206172312
Number
Failure Level B
Symptom After eNodeB upgrade, in the site with the FDD BPL0 board, the
equivalent throughput and CQI rate are decreased.
Impact The equivalent throughput and CQI rate are decreased.
Analysis The BPL0 only processes the periodical CQI configuration in Msg4.
After the periodical CQI configuration is changed from being sent after
Msg4 to being sent after Msg12 (initial DRB reassignment message),
the CQI processing flow of the BPL0 is affected. As a result, periodical
CQI check fails. If the accuracy of CQI check reported by UEs is
decreased, the equivalent throughput is also decreased.
Solution For the FDD BPL0 board, the system sends periodical CQI
configurations after Msg4.

1. In an FDD site, after a UE is connected to the BPL0 board, check the
message in which the periodical CQI is sent.
2. Compare and observe whether the equivalent throughput and the
CQI are improved.
Criteria:
1. Analyze signaling messages and verify that periodical CQIs are sent
in Msg4.
2. The equivalent throughput and CQI are not deteriorated.
Note None
Source Belgium

6.4.42 20170204102421 Paging Loss in Sites with No Paging Congestion
Table 6-44 Paging Loss in Sites with No Paging Congestion (Especially the BPN
Board)
Issue Name Paging Loss in Sites With No Paging Congestion (Especially the BPN
Board)
Defect 20170204102421
Number
Failure Level B
Symptom Paging messages are discarded in sites with no paging congestion.

This symptom is concentrated on the BPN board.
Impact Paging messages are lost.
Analysis When an instance is deleted from the user-plane subsystem of the

eNodeB, the deletion takes too long time because the instance queue
is long. As a result, the eNodeB fails to read the scheduling result due
to timeout, so the paging message is lost. This problem is very likely to
occur on baseband boards of the BPN type.
Solution Change the way of simultaneously deleting instances and queues to

the way of deleting them separately. In this way, RLC instances can be
released properly, and queue memories are deleted separately. With
the distributed deletion mode, the timeout problem won’t occur.

The paging loss problem does not occur in non-peak traffic hours.
Criteria:
The paging loss problem does not occur in non-peak traffic hours.
Note None
Source None
6.4.43 20170118090200 Falsely High Statistics of the Number of RRC Users
Table 6-45 Falsely High Statistics of the Number of RRC Users
Issue Name Falsely High Statistics of the Number of RRC Users

Defect 20170118090200
Number
Failure Level B
Symptom When an RRC connection is established, the maximum numbers of

users at the cell level, board level, and eNodeB level all increase. After
the cell is blocked, the number of users at the cell level is not 0. UE
access is limited.
Impact When an RRC connection is set up, the related counter values at the
cell level, board level, and eNodeB level are abnormal. After the
number of RRC users at the board level or eNodeB level exceeds the
threshold, UE access is affected.
Analysis The number of RRC users continues to increase abnormally, it is

greater than the real number of UEs. When this value reaches the
threshold of the eNodeB or the board, UE access is limited.
Solution Analyze and modify the data collection point for the number of users, to
ensure that the statistics of the number of RRC users is the same as
the real number of UEs.

1. Verify the solution with large service data.
Criteria:
1. The number of RRC users displayed in KPI statistics is the same as
the real number of users.
Note None
Source Myanmar operator
6.4.44 20160707102904 Statistical Result of "C373505499 Greater Than

P340440
Table 6-46 Statistical Result of "C373505499 Greater Than P340440
Issue Name Number of Activated E-RABs Greater Than Number of Released

E-RABs
Defect 20160707102904
Number 614005418286

Failure Level B
Bug Version LTE-V3.20.50.32
Symptom The statistical result of "C373505499 Number of Abnormal Release

Active E-RAB" greater than "P340440 Number of Dropped E-RABs" in
KPI statistics.
Impact The number of abnormal releases by active E-RABs and the number
call drops on E-RABs are affected.
Analysis After an inter-board cell handover operation fails, the candidate cell in
the measurement report is not cleared. When a UE initiates handover
again after reestablishment, the eNodeB reports the KPI of active
E-RAB releases due to the incorrect candidate cell.
Solution When the UE initiates reestablishment after handover fails, the eNodeB
needs to clear the handover candidate cells of this UE in the
measurement report before reestablishment.

1. Create an inter-board cell handover failure to create the UE to initiate
reestablishment.
Criteria:
1. After reestablishment is successful, the UE no longer hands over
immediately. If the UE hands over again, the handover is successful. In
addition, the number of releases by the active E-RAB is no greater than
the number of dropped calls on the E-RAB.
Note None
Source Thailand True
6.4.45 20160907231755 eNodeB Failing to Select the Correct PLMN to

Return an ACK Message After Receiving RIM information During 2G
RIM Information Exchange in the MOCN Shared Network
Table 6-47 eNodeB Failing to Select the Correct PLMN to Return an ACK Message
After Receiving RIMinformation During 2G RIM Information Exchange in the MOCN
Shared Network
Issue Name eNodeB Failing to Select the Correct PLMN to Return an ACK
Message After Receiving RIMinformation During 2G RIM Information
Exchange in the MOCN Shared Network

Defect 20160907231755
Number
Failure Level Minor
Symptom After receiving the RIMinformation, the eNodeB cannot select the
correct PLMN to return an ACK message.
Impact The RIM process is abnormal.
Analysis When returning the ACK message, the eNodeB selects the S1 link that
is selected during RIM initial connection setup, but does not select the
S1 link that receives the RIM Information.
Solution After receiving the RIM Information, the eNodeB selects the
corresponding S1 link to return an ACK message.

1. Select S1 link 1 during RIM initial connection setup.
2. Send an RIM Information update message on S1 link 2.
Criteria:
1. The ACK response is received on S1 link 2.
Note None
Source Hungary Telenor
6.4.46 20160819184450 No More Than Nine Blackcell Lists Related to

Forbidden TACs
Table 6-48 No More Than Nine Blackcell Lists Related to Forbidden TAC
Issue Name The number of blackcell lists related to forbidden TACs is changed on
V3.3.
Defect 20160819184450
Number
Failure Level B
Source Austria H3G
Symptom T the operator configures over nine forbidden TACs. However, the

existing version only supports up to nine forbidden TACs. When a user

hands over to the neighbor cell of a non-supported forbidden TAC, the
call drop problem occurs.
Impact The call drop problem occurs due to handover failures.
Analysis The eNodeB does not use the context or the HRL sent in the DT
message to update its local HRL.
Solution The eNodeB no longer restricts handover of the destination cell by

sending a blackcell list and based on the measurement report reported
by the UE. Instead, the processing way is modified as follows: the
eNodeB uses the HRL sent in the DT message to update its local HRL.
The handover request carries the latest HRL. An HRL supports up to
512 forbidden TACs.
Verification Create the X2 scenario, dual-CC handover scenario, and

cross-eNodeB reestablishment scenario. Configure more than nine
forbidden TACs.
Criteria:
Verify that the handover request carries the correct HRL and that
handover is successful.
Note Autraia H3G
6.4.47 20160809141629 Increased RRC Call Drop Rate After the Upgrade
Table 6-49 Increased RRC Call Drop Rate After the Upgrade of an eNodeB
Issue Name Increased RRC Call Drop Rate After the Upgrade of an eNodeB
Defect 20160809141629
Number
Failure Level B
Symptom After a certain network is upgraded completely, the RRC call drop rate
of an eNodeB increases to almost 90%.
Impact The RRC call drop rate is increased.
Analysis Before the call drop rate of the faulty eNodeB is increased, due to the
problem with transmission configurations, a large number of E-RAB
establishment failures occur. After transmission configurations are

modified, the problem of E-RAB establishment failures caused by

transmission resources is solved. However, a large number of E-RAB
instances are deactivated, so the call drop rate is increased
dramatically.
Solution The eNodeB implements protection for all abnormal processes.

1. Set the cell E-RAB admission threshold ACTDDLTE.rabThrd to 400.
2. Connect users and set up bearers.
Criteria:
1. When the number of cell E-RABs is equal to or smaller than 400, the
E-RAB establishment success rate is 100%.
2. When the number of cell E-RABs is greater than 400, the E-RAB
establishment success rate is smaller than 100%.
Note None
Source Dominica
6.4.48 20161012160546 Serious Uplink Packet Loss Rate in Random

Distribution With No Top Cell
Table 6-50 Serious Uplink Packet Loss Rate in Random Distribution
Issue Name Serious Uplink Packet Loss Rate in Random Distribution
Defect 20161012160546
Number 614005537687
Failure Level B
Bug Version V3.2
Symptom The cell uplink packet discard rate is serious and in random
distribution.
Impact This fault affects the statistics of the number of discarded uplink
packets.
Analysis During handover, uplink packets sent from the source side to the
destination side are disordered. When the destination side counts the
number of discarded packets, the statistics is abnormal.
Solution The destination side first sorts out the disordered packets that it

receives, and then collects the statistics.

Make UE perform an handover operation with uplink services, Observe
real time 10s KPI data
Pass Criterion:
There is no loss of more than 4000 packets at one time per 10s.
Note None
6.4.49 20161009044205 The Number of Intra-eNB Inter-Frequency

Handovers is Significantly Decreased After DRX Closed
Table 6-51 The Number of Intra-eNB Inter-Frequency Handovers is Significantly

Decreased After DRX Closed
Issue Name The Number of Intra-eNB Inter-Frequency Handovers is Significantly

Decreased After DRX Closed.
Defect 20161009044205
Number 614005545633
Failure Level B
Symptom After DRX is close, the number of intra-eNB inter-frequency handovers

is significantly decreased.
After DRX is enabled, the number of intra-eNB inter-frequency
handovers starts to be increased.
Impact This fault affects the number of intra-eNB inter-frequency handovers.
Analysis The MR periodical measurement function affects the function of load

balancing based on the number of connected RRC users, so the
number of intra-eNodeB blind handovers is abnormal. That is, after
intra-frequency periodical measurement is enabled, during
intra-frequency periodical measurement under initial measurement
reassignment, an intra-frequency periodical measurement report is
reported immediately. Thereby, the load balancing function based on
the number of connected RRC users is terminated by force (that is, the
eNB blind handover timer is killed).
After DRX is enabled, the MR periodical measurement reporting time

may be delayed, so the probability that the load balancing function

based on the number of connected RRX users is reduced. The number
of intra-eNodeB inter-frequency handovers is different when DRX is
enabled or shut down.
Solution The DCM architecture of V3.4 is changed from V3.3. After the
architecture is changed, MR periodical measurement reports won't kill
the eNB blind handover timer, so the load balancing function based on
the number of connected RRC users is not terminated.

1. Enable the MR periodical measurement switch, and trigger the load
balancing function based on the number of connected RRC users.
Verify that the process of this function is normal. In addition, check the
number of intra-eNodeB inter-frequency handovers.
Criteria:
1. After the MR periodical measurement switch is enabled and the load
balancing function based on the number of connected RRC users is
triggered, the process of this function is normal.
2. Before and after the MR periodical measurement switch is enabled,
the number of intra-eNodeB inter-frequency handovers is not changed
greatly.
Note None
Source Austria Hi3G
6.4.50 20161114095807 High VoLTE Call Drop Rate Due to Redirection
Table 6-52 High VoLTE Call Drop Rate Due to Redirection
Issue Name High VoLTE Call Drop Rate Due to Redirection
Defect 20161114095807
Number
Failure Level B
Symptom The counter "C373210502:Number of QCI1 E-RAB Release by ENB

Through E-RAB Release Procedure due to Shut Down or Reset Cell"
has a value, but no cell quits out of services.
Impact The statistical value of the counter "C373210502:Number of QCI1

E-RAB Release by ENB Through E-RAB Release Procedure due to

Shut Down or Reset Cell" is incorrect.
Analysis When a UE makes a VoLTE call, the CN sends a CSFB indication.

Then, the eNodeB implements CSFB redirection, and reports the
counter "C373210502:Number of QCI1 E-RAB Release by ENB
Through E-RAB Release Procedure due to Shut Down or Reset Cell"
instead of the counter "C373210522: Number of QCI1 E-RAB Release
by ENB Through E-RAB Release Procedure due to Redirection". The
wrong counter is reported.
Solution Under the above scenario, the eNodeB reports the counter
"C373210522: Number of QCI1 E-RAB Release by ENB Through
E-RAB Release Procedure due to Redirection".
Verification When a UE makes a VOLTE call, the CN sends a CSFB indication and
then the eNodeB implements CSFB redirection. The counter
"C373210522: Number of QCI1 E-RAB Release by ENB Through
E-RAB Release Procedure due to Redirection" is increased by one, but
the counter "C373210502: Number of QCI1 E-RAB Release by ENB
Through E-RAB Release Procedure due to Shut Down or Reset Cell" is
not increased.
Note None
Source Malaysia DIGI project
6.4.51 20160728180828 Deterioration of the RRC Call Drop Rate and E-RAB
Call Drop Rate After Upgrade to V3.30.20.21
Table 6-53 Deterioration of the RRC Call Drop Rate and E-RAB Call Drop Rate After
Upgrade to V3.30.20.21
Defect 20160728180828
Number
Failure Level B
Symptom Deterioration of the RRC Call Drop Rate and E-RAB Call Drop Rate
After Upgrade to V3.30.20.21
Impact This fault affects the handover success rate and call drop rate.
Analysis In UM mode, the handover command does not carry the PDCP-SN.

However, this element is carried on the existing version, resulting in

reassignment failures during sequance UE handover.
Solution In UM mode, the handover command does not carry the PDCP-SN.
Verification In UM mode, inter-eNodeB handover of sequance terminals can be

completed successfully.
Note This problem is occurs when using UE with the “sequance” chip. Using
the Qualcomm UE, there is no this phenomenon.
Source Indian TIKONALTE
6.4.52 20161008115245 Intra-eNodeB Handover Failure During Migration

(Inverted NAS Sequence)
Table 6-54 Intra-eNodeB Handover Failure (Inverted NAS Sequence)
Issue Name Intra-eNodeB Handover Failure During Migration (Inverted NAS

Sequence)
Defect 20161008115245
Number
Failure Level B
Symptom The paging success rate is decreased and the TAU process fails.
Impact The TAU process fails.
Analysis In the certain core network, after an RRC connection is set up

completely in a TAU process, the eNodeB sends the initial UE
information to the CN, and the CN sends an NAS message – TAU
Accept. The eNodeB carries this message when sending a
reassignment message. The eNodeB continues to query the UE
capability, and if it receives the second NAS message at this time, the
eNodeB sends it to the UE directly. The TAU Accept AS message is
sent later through the reassignment message, so the problem inverted
NAS sequence occurs. The UE does not process this NAS message,
but determines that the access is completed and directly initiates
handover. However, the eNodeB still waits for a response to the TAU
Accept NAS, so it does not process the handover information. As a
result, handover preparation fails.

Solution This fault occurs only when the eNodeB initiates the TAU process of
setting the active flag in idle status. It does not exist if the default bearer
does not need to be set up. Thus, to fix this fault, the TAU process shall
be modified to that way that the eNodeB queries the UE capability in
advance and directly sends a reassignment message after sending the
UE context setup request. In this way, the problem of inverted NAS
sequence won't occur.
Verification Verify the solution with large service data.
Note None
Source Indonesia
6.4.53 20161009150018 Decreased CN Traffic Due to S1 Reset
Table 6-55 Decreased CN Traffic Due to S1 RESET
Issue Name Decreased CN Traffic Due to S1 RESET
Defect 20161009150018
Number 614005526084
Failure Level B
Symptom After UE context setup at the eNodeB side times out, the eNodeB
sends an S1 RESET message to the CN, causing the CN traffic to
decrease.
Impact In field offices, the number of abnormal call drops increases obviously.
Analysis When UE context setup expires, if the eNodeB has received a downlink
NAS message from the CN, it indicates that the eNodeB has already
got the MME UE S1 AP ID (meaning that the CN has the instance of
this UE). In this case, the eNodeB should not send an S1 RESET
message to the CN.
Solution When UE context setup at the eNodeB side expires, if the eNodeB has
received a downlink NAS message from the CN, it sends a context
release request to the CN.

Create the scenario that UE context setup at the eNodeB side expires
the timer in eNodeB and a downlink NAS message is received from the

CN.
Criteria:
The eNodeB sends a context release request to the CN, and the traffic
at the CN side is recovered to normal.
Note None
Source Indonesian
6.4.54 20161104204855 After Version Upgrade, There Are Many Link

Disconnections Due to the S1 Link Error in A Few Sites, but the
SCTP Link Is Disconnected Only Once
Table 6-56 After Version Upgrade, There Are Many Link Disconnections Due to the S1
Link Error in A Few Sites, but the SCTP Link Is Disconnected Only Once
Name After Version Upgrade in South Africa, There Are Many Link
Disconnections Due to the S1 Link Error in A Few Sites, but the SCTP
Link Is Disconnected Only Once
Defect 20161104204855/20161130224633/20161011233022
Number 614005556698
Failure Level B
Bug Version LTE-V3.30.20.00B61
Symptom If there is more than one SCTP link in a cell, after a disconnected S1
link is recovered, newly-connected UEs will be released continuously.
Impact After the S1 link is disconnected transiently only once, even if the fault
is fixed, UEs are released continuously. The call drop rate is affected.
Analysis After the S1 link is disconnected, all UEs that are currently connected
to the SCTP link are released. However, due to a problem with the
code implementation logic, the judgment condition for stopping UE
release is incorrect, UEs will be continuously released.
Solution When the current S1 link is disconnected, attach a label to all UEs so
that only these UEs are released.
Verification On a cell with more than one SCTP links, continuously connect UEs.
Make one SCPT faulty and then recover it immediately. After releasing
UEs for dozens of seconds consecutively, the eNodeB no longer
releases UEs and UEs can be connected to it successfully. The greater

the service traffic of the eNodeB is the longer the release period is.
Note None
Source South Africa MTN
6.4.55 20161222165128 The BPN2 Board Restart Fault
Table 6-57 BPN2 Board Operation Error
Issue Name BPN2 Board Operation Error on the eNodeB in Macedonia
Defect 20161222165128
Number 614005654874
Failure Level B
Symptom The BPN2 board is restarted abnormally.
Impact The board is reset abnormally.
Analysis The board is reset abnormally because a dead cycle occurs when the
user plane deletes a node from the RNC sending queue on the core
RLC layer. The deal cycle is caused because the data chain table of
the RLC sending queue is damaged.
Solution Add the protection when a node is deleted from the sending queue on
the RLC layer. When the number of deleted nodes is greater than the
maximum number of nodes in the RLC sending queue, the eNodeB
directly breaks out from the deleted while cycle.

1. UE attach, do downlink and uplink FTP service.
Criteria:
1. Services operate properly and the board is not reset yet.
Note None
Source Macedonia VIP

6.4.56 20161227172031 Total Number of Abnormal Releases of Eight QCI1s

in Some Cells Is Smaller Than the Value of C373505300
Table 6-58 Total Number of Abnormal Releases of Eight QCI1s in Some Cells Is
Smaller Than the Value of "C373505300
Issue Name Among KPI Counters in the Existing VOLTE Network, the Total
Number of Abnormal Releases of Eight QCI1s in Some Cells Is Smaller
Than the Value of "C373505300:Number of Abnormal Release Active
E-RAB(QCI=1)"
Defect 20161227172031
Number 614005660369
Failure Level B
Symptom According to KPI statistics, the value of "C373505300 Number of

Abnormal Release Active E-RAB(QCI=1)" is greater. The counter for
the eight abnormal releases is "Number of QCI1 E-RAB Release by
ENB Through E-RAB Release Procedure due to Overload Control".
Impact The indicator of the number of abnormal releases of active E-RABs is

poor.
Analysis When the X2 handover target side times out in waiting for the path
switch ack message from the CN, it does not report the KPI of E-RAB
abnormal release, but sets the reason in the release request sent to the
user plane to abnormal release. As a result, the user plane reports an
abnormal release of the active E-RAB.
Solution Sort out the KPI reporting points during abnormal E-RAB releases.
During the process that the KPI of abnormal E-RAB release is not
reported, when the eNodeB sends a release request to the user plane
or configures a request, it does not fill in the reason for the abnormal
release.

1. On the NM server, decrease the timer of waiting for path switch ack
in X2 handover.
2. Create the scenario that the timer of waiting for path switch ack in X2
handover expires, check whether the number of E-RAB abnormal
releases and the number of active E-RAB abnormal releases are
reported.

Criteria:
1. These two counters are not reported: the number of E-RAB
abnormal releases and the number of active E-RAB abnormal
releases.
Note None
Source Malaysia DIGI
6.4.57 20170104042608 The eNodeB Sends an Empty Reconfiguration

Message but the UE Does Not Return an Assignment Complete
Message, so the eNodeB Releases the UE Upon Timeout
Table 6-59 The eNodeB Sends an Empty Reconfiguration Message but the UE Does
Not Return an Assignment Complete Message, so the eNodeB Releases the UE
Upon Timeout
Issue Name The eNodeB Sends an Empty Reconfiguration Message but the UE
Does Not Return an Assignment Complete Message, so the eNodeB
Releases the UE Upon Timeout
Defect 614005665077
Number 20170104042608
20170109094508
Failure Level B
Bug Version NB_V4.15.10.30P30
Symptom Abnormal UE release
Impact Abnormal UE release
Analysis The eNodeB sends an empty Reconfiguration message, but the UE

cannot identify it and thereby does not return a reconfiguration
complete message, so the eNodeB releases the UE after the timer of
waiting for reconfiguration completion expires.
Solution If the reconfiguration message to be sent is empty, the eNodeB does

not send it and it does not wait for reconfiguration completion either.
Verification Verify the solution with large service data.

The KPI of reconfiguration failures because of reconfiguration complete
time out is normal.
Note None

6.4.58 20170329144600 Baseband Reset Problem Due to a Software

Operation Error in CA Sites along the Subway
Table 6-60 Baseband Reset Problem Due to a Software Operation Error in CA Sites
along the Subway
Issue Name There is a baseband reset problem due to a software operation error in
CA sites along the subway
Defect 20170329144600
Number
Failure Level B
Symptom Services are interrupted, UEs cannot find cells, and a software
operation error occurs.
Impact LTE services are interrupted.
Analysis After the A4 measurement report on adding SCell to CA sites is sent,

the decode buffer area of the eNodeB is used twice continuously during
the measurement report decode process and the UE capability decode
process. As a result, a memory error occurs and the eNodeB is reset.
Solution Add an independent buffer area during the second UE capability

decoding process.

Use a terminal that supports the UE-EUTRA-Capability-v9a0-IEs
element and the UE-EUTRA-Capability-v10j0-IEs element to trigger the
A4 measurement report on adding SCell.
Criteria:
The SCell is added properly, and product processes operate properly.
Note None
Source China Unicom

6.4.59 20161008140129 Decreased CSFB Success Rate after the UTRAN

ANR Switch Is Enabled
Table 6-61 Decreased CSFB Success Rate After the UTRAN ANR Switch Is Enabled
Issue Name Decreased CSFB Success Rate After the UTRAN ANR Switch Is
Enabled

614005527480
Failure Level B
Symptom The CSFB success rate is decreased after the UTRAN ANR switch is
enabled.
Impact This fault affects the CSFB success rate.
Analysis When a new neighbor cell is added to the UTRAN, the system does
not read the number of PLMNs, so this number is 0. As a result, no
available frequency point can be output on the eNodeB.
Solution When a new neighbor cell is added to the UTRAN, the system gets
the PLMN correctly.

If the UTRAN ANR switch is enabled, when a temporary neighbor cell
is discovered and after it is changed into an official cell, the serving
cell quits out of service first and then operates properly.
Criteria:
The CSFB function of the eNodeB can output frequency points
properly.
Note None
Source Austria

6.4.60 20161103090911 After the Customized Description Field in AISG

Configuration Is Modified, the AISG Communication Link
Disconnection Alarm will Be Reported during AISG Rescanning
Table 6-62 After the Customized Description Field in AISG Configuration Is Modified,
the AISG Communication Link Disconnection Alarm Is Reported During AISG
Rescanning
Issue Name After the Customized Description Field in AISG Configuration Is

Modified, the AISG Communication Link Disconnection Alarm Is
Reported During AISG Rescanning.
Defect 20161103090911
Number 614005587353
Failure Level C
Symptom After the Customized Description Field in AISG configuration is

modified on OMMB and synchronized, if a dynamic operation on the
AISG device times out and the scanning operation is performed, the
device reports an "External extended device fault(198098468)" alarm
(alarm sub-code: communication link disconnection).
Impact The AISG device cannot be remotely controlled through the OMMB
An "External extended device fault (198098468)" alarm (alarm
sub-code: communication link disconnection) is reported.
Analysis When the Customized Description Field in AISG configuration is

modified on the OMMB and synchronized, due to a problem with the
jumping of the AISG round robin timer (OSS mechanism), the old AISG
device configuration is deleted from inside the RU. However, the new
AISG configuration is not imported yet. As a result, the AISG
configuration inside the RU is missing.
Sixty seconds after AISG scanning is implemented on the OMMB
again, the system detects the links of all AISG devices. The AISG
device with a broken link will report an alarm, so that the link
disconnection alarm is not missing during the scanning process. In this
way, the AISG configuration that is missing inside the RU is reported to
the EMS through the "External extended device fault(198098468)"
alarm.
Solution The OSS process is modified into the following way: after an AISG
deice is deleted, the system returns an AISG high-level deletion

success message only after one round robin cycle, and then the AISG
high level sends the information of the new AISG device. Finally, OSS
reassignment is completed.

On theOMMB, modify the Customized Description Field in AISG
configuration and perform incremental synchronization.
Criteria:
The dynamic operation (for example, querying downtilt angles,
querying device information) is successful. After AISG scanning is
implemented, the "External extended device fault(198098468)" alarm
(alarm sub-code: communication link disconnection) is not reported.
Note None
Source Belgium Telenet
6.4.61 20161018173804 Automatic Reset during RRU Operation
Table 6-63 Automatic Reset during RRU Operation
Issue Name Automatic Reset during RRU Operation
Defect 20161018173804
Number 614005597926
Failure Level C
Bug Version V3.2 and all previous versions
Symptom The RRU is automatically reset during operation in Cameroon.
Impact None
Analysis It is confirmed that the dry connector is interrupted frequently, causing

the watchdog task to be blocked and leading to RRU reset. The
hardware pin of this dry connector is not only used on the dry
connector, but also used on device 485. Each time when the dry
connector is interrupted, device 485 is closed and opened, resulting in
long processing time. When the dry connector alarm is reported
frequently, the watchdog task is blocked.
Solution When the dry connector is interrupted frequently, unnecessary

repeated opening and closing of device 485 should be avoided on the
RRU.


In the existing network, observe whether any dry connector is
interrupted frequently.
Criteria:
No dry connector is interrupted frequently, and the RRU is not reset.
Note None
Source Cameroon
6.4.62 20161022123503 Increased NI Noise After the R8882 S2100 B Is

Upgraded to V4.15
Table 6-64 Increased NI Noise After the R8882 S2100 B Is Upgraded to V4.15
Issue Name Increased NI Noise After the R8882 S2100 B Is Upgraded to V4.15
Defect 20161022123503
Number 614005605060
Failure Level B
Symptom After the R8882 S2100 B is upgraded to V4.15, the NI noise is

increased.
Impact The NI noise is increased.
Analysis Due to a fault with the RRU FPGA version, the ATT/VGA update flag of
the standby chip is not updated at the fixed cycle of 10 ms. As a result,
the ATT/VGA of the standby chip is not transmitted from the
active/standby interface to the active chip, and instead the register
power-on value 0 is transmitted to the active chip. As a result, the
standby chip gain factor that the RRU finally sends to the baseband is
decreased by 31.5 db, and the NI noise is increased by 31.5 db.
Solution On the new RRU FPGA version, the ATT/VGA flag of the slave chip is
updated at the fixed period of 10 ms. This solves the problem that the
gain factor reported to the baseband is decreased by 31.5 db.

This problem does not occur each time but only has a high probability
of occurrence, and it can be recovered after a greater signal is
received. To verify this problem, after the RRU is powered on, check

the NI noise immediately through spectrum scanning. In addition,

power off the RRU for ten times repeatedly, and immediately check the
NI noise each time after it is powered on.
Criteria:
The NI noise is normal.
Note None
6.4.63 20170103083733 Sudden Increase of the CC Board Load From 10%

to 66% in an eNodeB
Table 6-65 Sudden Increase of the CC Board Load From 10% to 66% in an eNodeB
Issue Name Sudden Increase of the CC Board Load From 10% to 66% in an
eNodeB
Defect 20170103083733
Number 20170103114249
Failure Level Minor
Bug Version V3.3
Symptom In an eNodeB, the load of the CC board is suddenly increased from

10% to 66%.
Impact The CPU usage of the CC board is increased.
Analysis The R8881 1T RRU does not support cross diversity, but it is
incorrectly configured. As a result, the RRU reports the wrong antenna
information when reporting its capability to the CC, so the CC fails in
the check and returns a failure response. As a result, the RRU reports
errors at scheduled intervals and the CC processes them frequently,
causing the CPU usage of the CC to increase.
Solution This fault can be fixed in either of the following two ways:
1. Change the wrong configuration on the EMS into normal diversity.
2. Optimize the RRU codes so that the RRU only reports the
capabilities of normal antennas in case of wrong configurations.

1. In solution 1, after the EMS configuration is modified into normal
diversity, check the CPU usage of the CC board.

2. In solution 2, if cross diversity is configured on the R8881, upgrade

to the optimized RRU version and then check the CPU usage of the
CC.
Criteria:
In both of the above solutions, the CPU usage of the CC should be
normal.
Note None
Source None
6.4.64 20170116172728 Low Rate in Indoor Distribution RRU Cascading

Coverage and is Recovered After the Sampling Rate is Modified
Table 6-66 Low Rate in Indoor Distribution RRU Cascading Coverage and Is
Recovered After the Sampling Rate is Modified
Issue Name Low Rate in Indoor Distribution RRU Cascading Coverage and Is
Recovered After the Sampling Rate is Modified
Defect 20170116172728
Number
Failure Level
Bug Version V3.30
Symptom In a super cell with hybrid configuration of single and dual antennas,
when the sampling rate is configured to 0, the downlink rate in the
coverage of some RRUs is low.
Impact This fault affects the speed of a cell and user experience.
Analysis In FDD mode, the number of uplink antennas configured on the

baseband is determined by the uplink antenna capacity on cell level,
but the uplink antenna capacity on cell level in the hybrid antenna
scenario is the maximum value among all CPs. Thereby, the number of
antennas configured to the baseband is different from the actual
number of antennas which causes the abnormal measurement result
and seriously affects system performance.
Solution Modify the way of acquiring the uplink antenna capacity. The system no
longer acquires the cell-level ULAntCapacity, but determines it through
the RF unit application mode and
ECellEquipmentFunction.antMapUlSeq in baseband resources. If the

RF unit application mode is set to Combination Mode or Mergence

Mode 2, the uplink antenna capacity of this baseband resource is set to
the number of "1" in ECellEquipmentFunction.antMapUlSeq multiplied
by 2. In other modes, the uplink antenna capacity of this baseband
resource is set to the number of "1" in
ECellEquipmentFunction.antMapUlSeq.

1. In a super cell with hybrid configuration of single and dual antennas
and multiple CPs, configure the RF unit application mode of each CP in
the super cell to parallel cabinet mode, normal mode, and combined
mode 2 respectively.
Criteria:
1. The uplink antenna capacity configured to each CP is the actual
antenna capacity of this CP.
2. When the sampling rate is set to 0, users can access the uplink and
downlink services of each CP properly, and the traffic is normal.
Note None
Source Tianjin Telecom
6.4.65 20170309164357 Abnormal Handover Indicator
Table 6-67 Abnormal Handover Indicator in Two Sites
Issue Name Abnormal Handover Indicator in Two Sites
Defect 20170309164357
Number
Failure Level B
Bug Version LTE-V3.20
Symptom During KPI query on the EMS, it is found that the value of C373281884
on NE 17005 and the value of C373250984 on NE 17104 were
exceptionally high before.
Impact The C373281884 and C373250984 indicators are abnormal.
Analysis As can be seen from the collected KPI data, the abnormality of each
counter is caused because the highest bit is changed. That is, each
counter is saved in WORD32. In each fault, the highest bit is changed
from 0 to 1. Before the KPI file is generated, all data at the eNodeB side

is copied from the temporary storage area to the history area. The
memory of the history area is applied and released in real time. As can
be seen from the fault reproduction result, the data is abnormal in the
history area. Because the reproduction rate of the fault is not high and
each time it occurs on different counters, certain memory tracking and
locating methods in the lab environment cannot be implemented in field
offices. Thus, the reason for the data error due to bit changes cannot
be accurately located.
Solution Because the memory of the history area that saves KPI data is applied
and released in real time, uncertain factors exist. An avoidance method
is adopted at the eNodeB side to remove the history area so that the
system acquires KPI data directly from the temporary storage area to
generate a file.
Verification Observe all KPI data. Verify that no exceptionally high value exists.
Note None
Source Algeria OTA
6.4.66 20170112163626 Clearance Time of Some History Alarms Earlier

Than Occurrence Time
Table 6-68 Clearance Time of Some History Alarms Earlier Than Occurrence Time
Issue Name Clearance Time of Some History Alarms Earlier Than Occurrence Time
Defect 20170112163626
Number
Failure Level B
Symptom The occurrence time of some history alarms is later than the recovery
time.
Impact Due to this fault, users suspect the accuracy of alarms, affecting user
experience.
Analysis Alarm A exists on the NM server, and the commissioning debugging

mode is enable at the NM side. However, after alarm A is recovered on
the NM server it still exists at the eNodeB side. Then, the eNodeB is
reset, and as a result, alarm A is also recovered at the eNodeB side at
time1 (which is the CC power-on time). After the debugging mode is

disabled at the NM side, alarm A is re-reported to the NM server at

time2 (which is the debugging ending time). Finally, the NM server
initiates current alarm synchronization to the eNodeB. The recovery
time of alarm A on the NM server is modified by the eNodeB to the
time1 (which is the CC power time). However, time1 is earlier than
time2, so the recovery time of alarm A is earlier than the reporting time.
Solution After the link between the eNodeB and the NM server is established,
the NM server initiates current alarm synchronization. It sends the
existing alarms (for example, alarm A) on the NM server to the eNodeB
to be compared. If the eNodeB finds that alarm A does not exist, it
modifies the recovery time of alarm A to the synchronization initiation
time, and reports the recovery of alarm A to the NM server.

1. Create alarm A, for example, the alarm of optical module not in
place.
2. Enable the debugging mode on the NM server.
3. Reset the eNodeB. Recover alarm A before the baseband unit is
initiated.
4. Before the NM initiates alarm synchronization, shut down the
debugging mode.
Criteria:
The reporting time of alarm A is the time when the debugging mode is
shut down on the NM server, and the recovery time is after the
debugging mode is shut down on the NM server.
Note None
Source India Bhadi
6.4.67 20161229093729 Failure to Query Physical Devices in Dynamic

Management
Table 6-69 Failure to Query Physical Devices in Dynamic Management
Issue Name Failure to Query Physical Devices in Dynamic Management
Defect 20161229093729
Number
Failure Level B

Symptom When users query physical-layer devices on the dynamic management

window of the NM server, the query fails and the system returns a
database operation failure.
Impact The operation of querying physical-layer devices fails, so user

experience is affected.
Analysis When CCE1 sets up a link with the NM server through ETH2, the
physical port ID generated by the eNodeB and saved in the Ethernet
table in the database is different from that configured on the NM server.
The former is twice that of the latter. Due to a code error, during
dynamic query, the physical ID sent by the NM server fails to match
that generated by the eNodeB in the Ethernet table, so the query finally
fails.
Solution During dynamic query, the physical port ID sent by the NM server can
successfully match that configured in the Ethernet table on the NM
sever.

Establish a link between the ETH2 port of CCE1 and the NM server. On
the dynamic management window of the NM server, query
physical-layer devices.
Criteria:
The query of physical devices is successful.
Note None
Source Myanmar OG Project
6.4.68 20170419100448 Qcell pRRU Rack Number Cannot Exceed 216
Table 6-70 Qcell pRRU Rack Number Cannot Exceed 216
Issue Name Qcell pRRU Rack No. Cannot Exceed 216
Defect 20170419100448
Number
Failure Level B
Bug Version On all previous versions
Symptom IQ Allocation Failure after the Qcell pRRU Rack No. Exceeds 216,

Causing the Array to Cross the Threshold and Affecting the Global IQ.
At a QCELL site, LTE cell report the alarm the outage cell, the
additional alarm information prompts the TDM IQ allocation failure.
Impact The cell is abnormal and terminals cannot access the network.
Analysis In the program codes at the eNodeB, the variable before the TDM IQ
global variable is an array, in which the number of elements is defined
as 216. The subscript of the array indicates the RRU rack No. If the
RRU rack No. is configured to be greater than 216, the array crosses
threshold. Thereby, the TDM IQ global variable after the array is
abnormal. If the TDM IQ global variable is abnormal, the check fails
during TDM application.
Solution Expand the number of elements in an array to 253.

Configure a cell by setting the rack No. of the RRU associated with the
cell to a value greater than 216, and then perform incremental
synchronization. Verify that the cell status is normal and UEs can
connect to the cell properly.
Criteria:
The cell status is normal and UEs can connect to the cell properly.
Note None
Source Fujian, China
6.4.69 20161012144430 Sleeping Cell Problem
Table 6-71 Sleeping Cell Problem in the India Idea LTE Project
Issue Name Sleeping Cell Problem in the India Idea LTE Project
Defect 20161012144430
Number 614005527480
Failure Level B
Symptom After a cell is reestablished in the LTE network, a sleeping cell occurs.
Impact UEs cannot be connected to the cell successfully.
Analysis During the IQ configuration on the baseband (for example, BPN2) of

the MCS chip: the DPU configuration must arrive first and the IQ
configuration must arrive later. However, on versions where the fault
exist, the DPU configuration is sent to the baseband board by the FDD,
while the IQ configuration is sent to the baseband board by the
platform, so the time sequence cannot be guaranteed. This fault occurs
under the scenario that the IQ configuration of the platform arrives at
the baseband board first and the DPU configuration of the product
arrives at the baseband board later, so the IQ configuration fails and
UEs cannot be connected to the cell.
Solution The DPU configuration is reported by the product to the platform and
then sent by the platform together with the IQ configuration, so the
platform guarantees time sequence.

This fault is caused because the sequence between the product
configuration and the platform configuration is not designed. However,
the time sequence is random, so the same scenario cannot be
guaranteed each time. Thereby, the solution can be verified only
through multiple tests.
1. In a single-mode FDD environment, use the BPN2 as the baseband
board. The BPN2 is cascaded with multiple RRUs (at least three RRUs
in star shape or chain shape). Each RRU is configured with one FDD
cell.
2. Run the script to delete and create multiple cells repeatedly.
3. Check the alarms on the NM server.
Criteria:
1. The alarm of IQ channel resource configuration failure due to a
parameter configuration error is not raised in alarm management.
Note None
Source India IDEA LTE project
6.4.70 20161018173856 Incorrect Counters C373930024 & C373930025
Table 6-72 Abnormal KPI Indicators Due to Errors with Counters C373930024 &
C373930025
Issue Name Abnormal KPI Indicators Due to Errors with Counters C373930024 &
C373930025

Defect 20161018173856
Number 614005542443
Failure Level B
Symptom After the LTE is upgraded to V3.3, the following two counters are
abnormal:
C373930024: Maximum UL Total Throughput on Transport Layer and
maximum receive traffic on the transmission layer
C373930025: Maximum DL Total Throughput on Transport Layer
Impact The transmission-layer traffic KPI indicators, C373930024 &

C373930025, are abnormal.
Analysis Normally, the maximum transmit and receive traffic at the transmission
layer are both within dozens of megabytes. However, when the fault
occurs, the maximum traffic reaches 10 G. The abnormality exists with
the transmit and receive SCTP traffic at the control plane. The SCTP
traffic is abnormal because there are self-established X2 SCTP links in
the existing network. If the previous traffic is not cleared when they are
deleted, the traffic will be exceptionally high.
Solution After the automatic configuration of X2 SCTP links is deleted, the

system needs to re-clear the transmit and receive traffic of X2 SCTP
links. The calculation restarts.

Export KPI data at regular intervals, and filter these two indicator
values for analysis.
Criteria:
These two indicator values are in the range of dozens of megabytes.
There is no exceptionally high traffic value.
Note None
Source Austria Hi3G

6.4.71 20161104104133 After A Broken SCTP Link is Recovered, There Is

No Transmission Power on the RRU and Services are Interrupted;
Services are Recovered After the PA is Disconnected and Enabled
Again
Table 6-73 After A Broken SCTP Link is Recovered, There Is No Transmission Power
on the RRU and Services are Interrupted; Services are Recovered After the PA is
Shut Down and Restarted
Issue Name After A Broken SCTP Link is Recovered, There Is No Transmission

Power on the RRU and Services are Interrupted; Services are
Recovered After the PA is Shut Down and Restarted
Defect 20161104104133
Number 614005599622
Failure Level B
Symptom After a broken SCTP link is recovered, there is no transmission power

on the RRU and services are interrupted; services are recovered after
the PA is shut down and restarted.
Impact Before the PA is shut down and restarted, there is no power on the
RRU and UEs cannot be connected to it.
Analysis 1. Reason why the RRU has no power after the broken link is
recovered:
This is an active/standby environment. Before the RRU link is broken,
an active/standby IQ synchronization operation has been performed.
However, the eNodeB does not correctly use the synchronization
interface, so the IQ configuration is not synchronized after being
changed. The IQ of the active CC is correct, but the IQ of the standby
CC is the old one and is wrong. A subsequent process triggers
active/standby switching. After the switching, the IQ value of the new
active CC is wrong. When the broken RRU link is recovered, it gets an
IQ configuration from the new active CC again. At this time, the IQ
configuration obtained by the RR is wrong, so there is no power on the
RRU.
The usage of the synchronization interface is described as follows:
Operation code 0: During the synchronization, the system compares
the last synchronization contents. If the first 24K, last 24K, and
message length are consistent, the system does not initiate

synchronization.
Operation code 6: During the synchronization, the system does not
compare but synchronizes the contents directly.
When the fault occurs at the eNodeB, operation code 0 is used, and it
meets the comparison condition. However, some parts in the middle
are actually changed.
2. Analysis of service recovery after PA shutdown and restart:

After the PA is shut down and restarted, the product re-reports the IQ
configuration to the platform to be calculated. The active CC gets the
correct new IQ configuration and sends it to the RRU. After the RRU
gets the new IQ configuration, services are recovered.
Solution When the faulty program code at the eNodeB invokes the
synchronization interface, the correct operation code 6 is used to
ensure that IQ synchronization is successful. In this way, the correct IQ
configurations exist on the active and standby CCs.

1. In an active/standby environment, configure a GSM or UMTS cell.
The cell operates properly.
2. Perform active/standby switchover.
3. Remove the optical fiber between the RRU and the BBU. Reconnect
it after three seconds.
4. Observe the power of the RRU.
Criteria:
1. The power of the RRU is normal.
Note None
Source Malaysia UM
6.4.72 20161116110433 Repeated Reset of the CC Board at a Site
Table 6-74 Repeated Reset of the CC Board at a Site
Issue Name Repeated Reset of the CC Board at a Site
Defect 20161116110433
Number 614005621344
Failure Level B

Bug Version V3.2
Symptom The CC board is reset repeatedly.
Impact The eNodeB is reset.
Analysis According to the protocol, packet 1588 does not exceed 100 bytes.
Thus, the copy buffer area is set to 200 bytes, and the system copies
contents to the buffer area to be processed according to the packet
length indication field of packet 1588. In case of very few exceptions,
the length field of the received packet 1588 is wrong and exceeds 200
bytes, result in array copy cross-threshold.
Solution Before copying packet contents, the system checks the packet first.
Packet 1588 whose length exceeds 200 bytes is an illegal packet and
is discarded directly.

1. Use an instrument to modify the length field of packet 1588 to a
value greater than 200 byes, and then send the packet.
Criteria:
1. According to the statistics on the BBU, the length of packet 1588
increases incorrectly.
2. The eNodeB is not reset.
Note None
Source Indonesia TSL
6.4.73 20161215133123 Average CPU Usage of the CC Board on the

eNodeB Is Greater Than 100% and Displayed As 3000%
Table 6-75 Average CPU Usage of the CC Board on the eNodeB Is Greater Than 100%
and Displayed As 3000%
Issue Name Average CPU Usage of the CC Board on the eNodeB Is Greater Than
100% and Displayed As 3000%
Defect 20161215133123
Number 614005628978
Failure Level B

Symptom On the EMS, the query result of the performance counter

(C370010001, Ratio of Average CPU Usage) is displayed as 2000%,
which is far greater than 100%.
Impact Ratio of Average CPU Usage (C370010001) is abnormal.
Analysis KPI data saved inside the eNodeB uses the Ping-Pong mechanism,
and the eNodeB reports KPI data to the NM server at fixed time points.
When the time of the eNodeB changes, the fixed time point of reporting
KPI data might be skipped. At this time, the data area will be inverted
twice. Because the inversion interval is very short, one clearing
operation is omitted. As a result, residual values remain in the average
value counter, and it is displayed abnormally.
Solution Bind the clearance and inversion of data areas. Before inverting the
data area, the system clears it first to ensure that the current write data
area is a clear area with no residual data.

Change the time of the eNodeB, and check the Ratio of Average CPU
Usage counter (C370010001).
Criteria:
The Ratio of Average CPU Usage counter (C370010001) is normal
and it does not exceed 100%.
Note None
6.4.74 20161202070358 Frequent Disconnection of the OMC Link After

FST+OMC+IPSec Configurations Are Added on the UR15 eNodeB
Version
Table 6-76 Frequent Disconnection of the OMC Link After FST+OMC+IPSec

Configurations Are Added on the UR15 eNodeB Version
Issue Name Frequent Disconnection of the OMC Link After FST+OMC+IPSec

Configurations Are Added on the UR15 eNodeB Version
Defect 614005603510
Number
Failure Level B

Symptom In the IPSEC IKEv1 scenario, the byte lifecycle configured on the
security gateway (0) is different from that configured on the eNodeB (a
value other than 0), so the OMCB channel between the eNodeB and
EMS systems is broken at irregular intervals.
Impact The OMCB channel between the eNodeB and EMS system is broken
at irregular intervals.
Analysis If the lifecycle configuration is inconsistent between the security

gateway and the eNodeB, when it is set to 0 on the security gateway
and the eNodeB acts as party R, the eNodeB cannot send packets
successfully. As a result, the link between the eNodeB and EMS
systems is broken.
Solution If the byte lifecycle is set to 0 on the security gateway but set to a
different value on the eNodeB, add the processing on the eNodeB for
the scenario when the security gateway is set to 0.

If the byte lifecycle is different between the security gateway and the
eNodeB (including the cases when the byte lifecycle is set to 0 on the
security gateway and when it is not used), verify the negotiation
between them when the eNodeB acts as party I and party R
respectively. In addition, also verify the scenario when the eNodeB acts
as party I and party R in case of rekey.
Criteria:
After the configurations are made in accordance with the verification
methods, the communication between the eNodeB and EMS systems
is normal.
Note None
Source Belgium
6.4.75 20161209161221 Supporting Automatic Update of the Summer Time

and Summer Time Start/End Time Format of Month-Week-Day
Table 6-77 Supporting Automatic Update of the Summer Time and Summer Time
Start/End Time Format of Month-Week-Day
Issue Name The summer time setting of the eNodeB does not support the
"Month-Week-Day" format.
Defect 20161209161221

Number
Failure Level B
Symptom The task in the tool does not take effect due to a great difference
between the time of the main-control board and that of the baseband
board.
Impact The time of the baseband board is in the year 2000, which is abnormal.
Analysis When the main-control board sets the time of peripheral boards, it
sends time in the format of "month-week-day". However, the bottom
layer of peripheral boards only supports the setting in the format of
"year-month-day". As a result, time setting of peripheral boards fails.
Solution When the main-control board sets the time of peripheral boards, the
system first transfers time into the format of "year-month-day", which is
supported by the bottom layer of peripheral boards, and then transfers
the setting to the bottom layer of peripheral boards.

Modify the summer time setting to the "Month-Week-Day" format, and
check whether the time of the baseband board is the same as that of
the main-control board.
Criteria:
The time of the baseband board is the same as that of the main-control
board.
Note None
Source France
6.4.76 20170105091354 Maximum Throughput (Mbps) of DL Received Data

of the eNodeB Exceeds 1Gbps in Actual Statistics
Table 6-78 Maximum Throughput (Mbps) of DL Received Data of the eNodeB

Exceeds1Gbps in Actual Statistics
Issue Name Maximum Throughput (Mbps) of DL Received Data of the eNodeB

Exceeds 1Gbps in Actual Statistics
Defect 20170105091354
Number

Failure Level B
Symptom The maximum throughput (Mbps) of DL received data of the eNodeB

exceeds 1 Gbps in actual statistics.
Impact In KPI statistics on the EMS, the maximum throughput of DL received

data of the eNodeB is abnormal, but the actual traffic is correct.
Analysis The abnormal value is caused because it is inverted during KPI

statistics.
Solution Optimize the existing flow in the following way:

Before reporting data, the system optimizes the traffic of the control
plane. If only one high traffic value occurs (the traffic value is greater
than twice of the average value and greater than the threshold value),
the reported value is changed to the value reported the last time. If high
traffic values occur for more than once, it is determined that the actual
traffic statistics is high. At this time, if the high traffic value is increasing,
the reported traffic value also increases within the scope of the average
value and the greater value. If the high traffic value no longer
increases, it is reported. In addition, the system records various
statistical results when high traffic values occur, to facilitate subsequent
analysis.

Perform traffic tests for a long period of time. Check KPI statistics to
see whether the maximum throughput of DL received data of the
eNodeB is normal.
Criteria:
KPI statistics are normal.
Note None
Source None
6.4.77 20161207095523 No Power on the RRU During Query
Table 6-79 No Power on the RRU During Query
Issue Name No Power on the RRU
Defect 20161207095523
Number

614005631402
Failure Level C
Symptom There is no power on the RRU. A CRC alarm is reported on the RRU,
and the RRU ID is 254.
Impact This fault affects the access of cells.
Analysis Due to an overflow problem with the buffer area used in the serdes of
RRU FPGA, cross-clock data receiving is abnormal. However, this
problem is processed at the bottom layer. The system performs
resynchronization after the overflow problem occurs. Thus, no los/lof
problem occurs. However, the CRF alarm is still reported. In the CRC
alarm, the RRU_ID is shielded, so the message is incorrectly received
by the RRU.
Solution Add the monitoring upon the overflow status of the buffer area. After
the buffer area overflows for several times, the system resets it to
ensure that the serdes kernel operates properly.

Reset the RRU for several times, and observe its status.
Criteria:
No CRC alarm is reported on the RRU, and the transmission power of
the RRU is normal.
Note None
Source Hangzhou Telecom, China
6.4.78 20170110013514 Repeated Printing of UDT Signaling Messages
Table 6-80 Repeated Printing of UDT Signaling Messages
Issue Name Repeated Printing of UDT Signaling Messages
Defect 20170110013514
Number
Failure Level B
Symptom In UE-level cell signaling tracing tasks, some signaling messages are

displayed repeatedly.
Impact This fault affects the UDT signaling trace function. Because data is
reported repeatedly, the troubleshooting process of other faults is
affected.
Analysis When a UE is in connected status, EMS synchronizes the UDT signaling

trace task. The eNodeB does not process the signaling cache flag
correctly. As a result, the UE is released during the synchronization
task, and the eNodeB reports the signaling message cached the last
time again.
Solution The eNodeB optimizes the processing of the signaling cache flag to
ensure that the signaling message is reported only once in the scenario
that a synchronization task and UE release are performed
simultaneously.

Synchronize task and release UE simultaneously when UE is in
connected status. The signaling message displayed on the EMS is
correct and not repeated.
Criteria:
Synchronize task and release UE simultaneously when UE is in
connected status. The signaling message displayed on the EMS is
correct and not repeated.
Note None
Source South Africa MTN FDD
6.4.79 20160729141028 UDT Decodes noncriticalextension in Error
Table 6-81 UDT Decodes noncriticalextension in Error
Issue Name UDT (Unified Data Trace) Decodes noncriticalextension in Error
Defect 20160729141028
Number
Failure Level B
Bug Version LTE-V3.20.50.32;V12.14.30P40;
Symptom UDT Decodes noncriticalextension in Error
Impact Signaling messages cannot be correctly displayed on the EMS.

Analysis The EMS server fails to decode the signaling messages because the
64bit decoding library is not developed on the eNodeB.
Solution The eNodeB supports signaling reporting to the 64bit decoding library.
Signaling messages can be correctly displayed on the EMS.

1. Install the EMS on a 64bit computer, and send an UDT signaling
trace task to perform the test.
Criteria:
1. On the 64bit computer, the EMS client can correctly decode the
contents of signaling messages.
Note None
Source Austria
6.4.80 20160811171346 MTS Data Fail to Display IMSI on the EMS
Table 6-82 MTS Data Fail to Display IMSI on the EMS
Issue Name MTS Data Fail to Display IMSI on the EMS
Defect 20160811171346
Number 614005448710
Failure Level B
Symptom After a UE-level cell MTS task is enabled on the eNodeB, the IMSI
information of UEs cannot be displayed on the EMS.
Impact In field scenarios such as road tests, when the MTS is used to trace
traffic of UEs, the MTS fails to obtain the IMSI numbers of UEs. As a
result, the faulty UE or road test UE cannot be located.
Analysis Because the TraceID reported in MTS data is inconsistent with the
trace ID carried in the S1CellTraffic message sent to the CN, the EMS
cannot associate these two TraceIDs, so IMSI numbers cannot be
displayed correctly.
Solution On the eNodeB, modify the TraceID reported in MTS data to be the
same as that carried in the S1CellTraffic message sent to the CN in the
MTS task, so that the EMS can correctly associate and display the
reported IMSI information.


1. EMS synchronizes a cell-level MTS task. The IMSI number of the
corresponding UE can be displayed on the MTS window of the EMS.
Criteria:
1. EMS synchronize a cell-level MTS task. The IMSI numbers of UEs
that are already in connected status cannot be displayed on the EMS,
because these UEs need to attach again to complete the IMSI
acquisition process.
2. EMS synchronize a cell-level MTS task. The IMSI numbers of UEs
that attach later can be displayed on the EMS.
Note None
Source USA office J100
6.4.81 20161114223551 Time is Six Hours Later Than the Local Time After
Northbound Trace Decoding
Table 6-83 Time is Six Hours Later Than the Local Time After Northbound Trace
Decoding
Issue Name Time is Six Hours Later Than the Local Time After Northbound Trace
Decoding
Defect 20161114223551
Number
Failure Level B
Bug Version
Symptom The time is six hours later than the local time after northbound Trace
decoding, so the time of the Trace file is inconsistent with the local
time.
Impact The time of the Trace file is inconsistent with the local time, which
affects its use and analysis.
Analysis There is a defect with the third-party library function invoked by the
NDS while decoding the Trace file. This problem is triggered because
the NDS obtains the wrong "hour" information.
Solution When decoding the Trace file, the NDS invokes the correct time
decoding function to ensure that time decoding is accurate.


1. Check the file of the Trace file to see whether it is consistent with the
local time.
Criteria:
1. The time of the Trace file is the same as the local time.
Note None
6.4.82 20170213175520 High E-RAB Call Drop Rates in Top Sites
Table 6-84 High E-RAB Call Drop Rates in Top Sites
Issue Name High E-RAB Call Drop Rates in Top Sites
Defect 20170213175520
Number
Failure Level B
Symptom In the field sites with top high traffic, the downlink rate was low
previously. After the eNodeB is restarted, the E-RAB indicator is
improved and then rapidly deteriorated. E-RAB call drops are mainly
caused by wireless link failures.
Impact Related KPIs on wireless network side are obviously abnormal, such as
the E-RAB call drop rate, RRC call drop rate, and number of wireless
link failures.
Analysis Because the downlink frequency selection function is not delivered to

commercial use, it is enabled in the commercial network, causing the
timer to be deactivated and resulting in no scheduling resources.
Solution Modify the configuration. On the NM server, modify the downlink RB

allocation mode to PRB randomness.

1. Disable downlink frequency selection. Check the E-RAB call drop
rate.
2. Test the downlink rate.
Criteria:
1. If the number of users exceeds 100, observe the E-RAB call drop

rate and the RRC call drop rate for a long period of time. Verify that the
E-RAB call drop rate, the RRC call drop rate, and the number of
wireless link failures are all normal.
Note None
Source Pakistan CMPAK project
6.4.83 20170121120334 Traffic of CA Terminals Lower Than Traffic of

Non-CA Terminals in Speed Tests
Table 6-85 Traffic of CA Terminals Lower Than Traffic of Non-CA Terminals in Speed
Tests
Issue Name Traffic of CA Terminals Lower Than Traffic of Non-CA Terminals in

Speed Tests
Defect 20170121120334
Number
Failure Level B
Symptom When a CA user starts to perform the speed test, the traffic is obviously
lower than that of non-CA users.
Impact The traffic and service experience of CA users are affected.
Analysis When the DRX function is disabled, under some scenarios (for
example, UE reassignment or reestablishment in CA scenarios), in the
reassignment message sent by the high layer to the baseband board,
DRX-related timers are set to invalid values such as 255. However, the
baseband board makes a wrong judgment and determines that the UE
is enabled with the DRX function, and thus enters the DRX status. As a
result, the number of reported scheduling messages is reduced, and
service traffic is affected.
Solution In the scenario when the DRX is disabled, the eNodeB also follows the
processing flow for disabled DRX function, to ensure that the DRX
status is the same as that at the UE side.
Verification If the DRX function is disabled, the traffic of CA users complies with the
theoretical traffic.
Note None

6.4.84 20170112082841 Increase of Prach Average NI by 30 dB or Above

After UL CoMP Deployment
Table 6-86 Increase of Prach Average NI by 30 dB or Above After UL Comp

Deployment
Issue Name Increase of Prach Average NI by 30 dB or Above After UL Comp

Deployment
Defect 20170112082841
Number
Failure Level B
Symptom After UL comp is deployed, the PRACH Average NI value of all cells is
increased by 30 dB or above, but the RB level is not increased greatly.
Impact This fault only affects the reported NI. The reported NI is higher.
Analysis In FDD mode 0, the system does not obtain the VGA values of all cells
for RACH NI calculation, but only obtains the VGA values of some
cells. As a result, the reported NI value is incorrect.
Solution The eNodeB correctly obtains the VGA values of all cells and use them
in PRACH NI calculation to ensure that the reported KPI value is
correct.
Verification In FDD configuration mode 0, observe the PRACH Max NI value. The
NI value is in the normal range.
Note None
6.4.85 20170328171015 NI Is -120 In Case of Bypass and Is -70 In Case of

Non-Bypass after Tower-Mounted Amplifiers Are Added to the RRU
Table 6-87 NI Is -120 In Case of Bypass and Is -70 In Case of Non-Bypass After
Tower-Mounted Amplifiers Are Added to the RRU
Issue Name Higher NI Statistics (-70) After Tower-Mounted Amplifiers Are Added to

the RRU
Defect 20170328171015
Number
Failure Level B
Symptom After tower-mounted amplifiers are added to the RRU, the NI value is
-120 in case of bypass and increases abnormally to -70 in case of
non-bypass.
Impact This fault only affects the dB value of the reported NI in KPI statistics.
Analysis The constraint of the maximum VGA value of the BBU is different from
that of the RRU. The value range of the RRU exceeds that of the BBU,
resulting in data overflow. The VGA factor is changed to a negative
value. As a result, the reported data is displayed as an abnormal value.
Solution Modify the VGA interface on the BBU to ensure that the constraint on
the BBU is the same as that on the RRU.
Verification After tower-mounted amplifiers are added to the RRU, the correct NI
value is reported.
Note None
Source Hungary
6.4.86 20160627194034 After BPN2 Replaces BPL1, the Minimum Power of

a Cell Is Increased, the Minimum Power of Another Cell Is Reduced,
and the Power of 0 mW Occurs Before and After Replacement
Table 6-88 After BPN2 Replaces BPL1, the Minimum Power of one Cell Is Increased,
the Minimum Power of Another Cell Is Reduced, and the Power of 0 mW Occurs
Before and After Replacement
Issue Name After BPN2 Replaces BPL1, the Minimum Power of cell10 at 120024
Site Is Increased, the Minimum Power of cell12 at 120156 Site Is
Reduced, and the Power of 0 mW Occurs Before and After
Replacement
Defect 20160627194034
Number 614005399536
Failure Level B

Symptom After BPN2 replaces BPN1, the minimum power of cell10 at 120024
site is increased, and the minimum power of cell12 at 120156 site is
reduced.
Impact In KPI statistics, the minimum transmit power is inaccurate.
Analysis In case of kernel timeout, the downlink PRB of a cell is not updated
properly, so the minimum power in KPI statistics is inaccurate.
Solution In case of kernel timeout, the downlink PRB statistics are updated
correctly to ensure that the statistical value reported in KPI statistics is
consistent with the PRB in use and the minimum transmission power of
the cell.
Verification In KPI statistics, the minimum transmit power is normal.
Source Austria H3G
6.4.87 20161108143331 Statistical Result of C373414597 (Average NI of

Carrier(dBm)) Inconsistent With the Average Value of PB-Level
Statistics
Table 6-89 Statistical Result of C373414597 (Average NI of Carrier(dBm)) Inconsistent

With the Average Value of PB-Level Statistics
Issue Name Statistical Result of C373414597 (Average NI of Carrier(dBm))

Inconsistent With the Average Value of PB-Level Statistics
Defect 20161108143331
Number 614005572906
Failure Level c
Symptom The statistical result of C373414597 (Average NI of Carrier(dBm)) is

inconsistent with the average value of PB-level statistics.
Impact This fault affects the display of KPI statistics.
Analysis When there are two cells on the same kernel, the average carrier value
of the second cell is accumulated over the statistical value of the first
cell.
Solution When the eNodeB collects the statistics of each cell, the variable is

initiated each time to avoid accumulating historical values.

1. Observe the average carrier value and the average RB value in KPI
statistics for long time.
Criteria:
1. The average carrier value is consistent with the average RB value.
Note None
Source Hungary Telenor
6.4.88 20161104162805 Low Speed at Far Points in CAs in the FDD+TDD

Network
Table 6-90 Low Speed of Far Points in CAs in the FDD+TDD Network
Issue Name Low Speed of Far Points in CAs in the India FDD+TDD Network
Failure Level B
Symptom In the CA scenario in a TDD+FDD network, the speed of a terminal

might be lower than that of a single carrier.
Impact In the carrier aggregate scenario, the downlink speed of terminals is

low.
Analysis On the eNodeB, the read/write time of the HARQ buffer area is
inconsistent, so scheduling fails.
Solution On the eNodeB, modify the data filling sequence of the HARQ buffer
area to ensure that scheduling is correct.
Verification In the CA scenario in a T+F network, use a terminal to perform

downlink FTP services.
Compared with a single carrier, the traffic gains are obvious.
Note None
Source India

6.4.89 20170414182659 RTP Packet Loss Due to Large Downlink

Scheduling Intervals before Handover
Table 6-91 RTP packet loss due to large downlink scheduling intervals before handover
Issue Name RTP packet loss due to large downlink scheduling intervals before
handover
Number 20170414182659
614005828605
Level C
Version V3.40.20.00B86
Symptoms After handover, downlink RTP packet loss occurs on the QCI1.
Impact User experience
Analysis The eNodeB does not send some packets to the UE due to large
scheduling intervals before handover. These packets are not correctly
compressed because their headers are overwritten when the eNodeB
saves them. As a result, a downlink RTP loss occurs due to a
decompression failure at the UE side.
Solution Modify the path where the eNodeB saves the above packets and
ensure that it will not be tampered.

Two UEs perform voice service in the scenario of BPN internal
handover.
Passing Criterion:
In the terminal log, there is no record that shows an RTP packet loss
due to packet decompression failure at the UE side after handover.
Note None
From China Telecom

6.4.90 20170418002209 Inaccurate Average RSRP Value of the

Serving/Target Cell
Table 6-92 Inaccurate average RSRP of the serving cell or target cell
Issue Name Inaccurate average RSRP of the serving cell or target cell
Number 20170418002209
Level B
Version V3.40.20.00B80
Symptoms The average RSRP value of the serving /target cell is abnormal.
Impact The average RSRP value of the serving/ target cell is inaccurate.
Analysis When the KPI statistics for RSRP and RSRQ is reported, there is no
judgment based on the measurement handover.
Solution The eNodeB first determines whether it is a measurement based

handover, and then reports the corresponding RSRP and RSRQ
values.

In the blind handover and measurement based handover scenarios,
check whether the reported RSRP and RSRQ values are normal.
Passing Criterion:
The eNodeB reports corresponding RSRP and RSRQ values only in the
measurement based handover scenario.
Note None
From China Unicom Quanzhou
6.4.91 20170420110700 Lighting Fault of Optical Module for Newly added

R8861
Table 6-93 Lighting fault of Optical module for newly added R8861
Issue Name Lighting fault of Optical module for newly added R8861
Number 20170420110700
Level Critical

Issue Name Lighting fault of Optical module for newly added R8861
Version V3.30.20.51P10
Symptoms A new R8861 has a failure in lighting and the site is abnormal.
Impact New sites have a probability of failed RRU operation and failed
connection with BBUs. The cell to which the RRU belongs fails to be
established (no failure occurs after the RRU powers on normally and
successfully connects the BBU).
Analysis The TRM24B model has restriction on its hardware. There shall be no
write operation to the flash disk before the logical FPGA is loaded.
Otherwise, the file system will be abnormal, causing a Localbus conflict
or file damage in the flash disk (including version files).
The general trace recording feature of the OSS can record the files
under OssLog directories of all flash boards. This may lead to a L2 bus
conflict due to a hardware defect on the TRM24B model or even a
damaged version file.
Solution Cancel the trace recording feature for the TRM24B model.

Tracing the newly added sites. This problem will not occur.
Passing Criterion:
This problem never occurs when the R8861 is used for deployed.
Note None
From China Unicom Zhengzhou
6.4.92 20170420171152 Simultaneous Report of GPS Positioning Alarms

from FDD LTE eNodeBs Failing to Position in Different Areas During
Several Timing Periods
Table 6-94 Simultaneous report of GPS positioning alarms from FDD LTE eNodeBs
failing to position in different areas during several timing periods
Issue Name Simultaneous report of GPS positioning alarms from FDD LTE
eNodeBs failing to position in different areas during several timing
periods
Number 20170420171152
Level Minor

Issue Name Simultaneous report of GPS positioning alarms from FDD LTE
eNodeBs failing to position in different areas during several timing
periods
Symptoms For the FDD LTE network of China Telecom Chengdu Branch,
BS8700s periodically report GNSS positioning faults or antenna feeder
faults. The source of GPS positioning alarms is from the 1.8G BBU that
supports an independent GPS module without any power division. The
1.8G BBU is deployed together with the L800M dual-mode BBU. Their
GPS modules are also deployed together and not shielded. When the
faults occurs, only the 1.8G BBU fails to position but the GPS module
of the L800M BBU works properly. Therefore, the faults are not caused
by interference or too many GPS branches.
There are about 10 such eNodeBs in different areas.
Impact When a GPS positioning alarm occurs, it takes more than 10 hours to
restore it. This makes the target eNodeB out of service.
Analysis There is a short command interval (100 ms) between hardware reset
and soft reset, which makes the receiver work in abnormal state and
have no time to wait for message output.
Solution Change the command interval between hardware reset and soft reset
to 3s.

Use a jammer (interference unit) to make interference on the eNodeB
and stop it when the eNodeB reports a positioning alarm.
Passing Criterion:
The positioning alarm disappears in 15 minutes after the interference
stops.
Note None
From China Telecom Chengdu Branch

6.4.93 20170505094113 Large Changes to Maximum NI and Average NI of

the PRACH after a Version Update to V3.3
Table 6-95 Large changes to maximum NI and average NI of the PRACH after a
Issue Name Large changes to maximum NI and average NI of the PRACH after a
Number 20170505094113
614005360687
Level B
Version V3.3
Symptoms The maximum NI counter of the PRACH reports an abnormal value of

16.
Impact The maximum NI counter and average NI counter of the PRACH report
wrong values.
Analysis The channel for reporting PRSCH NI results is abnormal. As a result,

the PRACH uses the default values when reporting KPIs.
Solution 1. Modify the default value of the PRACH NI to avoid reporting invalid
values
2. Fix the PRACH NI failure in an abnormal case.

Attach the UE and check the average PRACH NI counter and the
maximum PRACH NI counter in the KPI.
Passing Criterion:
For the average and maximum PRACH NI values, the statistical result
has no abnormal value of 16.
Note None
From Digi Malaysia
6.4.94 20170422023728 RRU Disconnections in Some New LTE Sites
Table 6-96 RRU disconnections in some new LTE sites
Issue Name RRU disconnections in some new LTE sites

Issue Name RRU disconnections in some new LTE sites
Number 20170422023728
Level B-Critical
Version V3.30.20.51P30 (V4.16.10.03P30)
Symptoms RRU disconnections occur in some new LTE sites.
Impact Broken RRU connections occur sometimes and cells are out of service
(200 sites, one broken RRU connection every 2 or 3 days).
Analysis The Linux works with a single kernel and the SMP mode is used. A
kernel dead lock may occur if a low-priority task writes data and a
high-priority task reads data.
Solution The kernel uses a lock to solve the deadlock problem that may occur
when a low-priority task writes data and a high-priority task reads data.
Lower the CarrDownLinkSta task priority and change the Linux priority
to 46 (original value: 79).

Observe whether any broken RRU connection occurs. If the connection
cannot be restored, hardware reset or reset by power-off.
Passing Criterion:
The above problem never occurs.
Note None
From Italy
6.4.95 20170418163230 Large Number of Reestablishment Requests

Caused by a Sector Reconfiguration Failure
Table 6-97 Large number of reestablishment requests caused by a sector

reconfiguration failure
Issue Name Large number of reestablishment requests caused by a sector

Number 20170418163230
Level B

Issue Name Large number of reestablishment requests caused by a sector

Version V3.30.20.51p10
Symptoms There is a large number of reestablishment requests caused by a

sector reconfiguration failure.
Impact ERAB establishment success rate is affected.
Analysis In the ATTACH process, UE carries "featureGroupIndicators.

fdd_Add_UE_EUTRA_Capabilities_r9Present = 1" and
"featureGroupIndicators_r9Present = 0". The eNodeB chooses to use
the R9 information, but there is no R9 FGI information. In this case, the
eNodeB considers this feature is supported by default and delivers a
short DRX configuration in an initial DRB reestablishment message.
Solution If the UE carries "fdd_Add_UE_EUTRA_Capabilities_r9Present = 1"

and "featureGroupIndicators_r9Present = 0", use
"featureGroupIndicators" to check whether the short DRX is configured.

Attach the UE. When the UE carries "featureGroupIndicators.
fdd_Add_UE_EUTRA_Capabilities_r9Present = 1" and
"featureGroupIndicators_r9Present = 0", check whether there is any
reestablishment due to a reconfiguration failure.
Passing Criterion:
No reestablishment occurs due to a reconfiguration failure.
Note None
From AIS Thailand
6.4.96 20170412181047 Data Output Existing in the Counter (Based on

Blind Handover) when Load/Measurement Based Load Balance is
Enabled
Table 6-98 Data Output Existing in the Counter (Based on Blind Handover) when
Load/Measurement Based Load Balance is Enabled
Issue Name Data Output Existing in the Counter (Based on Blind Handover)
when Load/Measurement Based Load Balance is Enabled
Number 20170412181047

Issue Name Data Output Existing in the Counter (Based on Blind Handover)
when Load/Measurement Based Load Balance is Enabled
Level C
Symptoms When load based and measurement based load balancing is enabled,
the counter based on blind handover has data output. The customer
complaints that this is unreasonable.
Impact KPI statistics is affected.
Analysis The statistics of counter (C373485193, C373485194, and

C373485195) not only contains the blind handover of LB, but also
contains all Intra-LTE blind handovers.
For the handover of LB, the admit message from a candidate cell
based on LB does not contain whether the handover is a
measurement-based handover or a blind handover. The eNodeB
reports a blind handover by default. As a result, all LB handovers are
counted as blind handovers and the above three counters have data
outputs when the measurement-based LB is open.
Solution Add an identifier to the admit message of the candidate cell based on
LB, identifying if the handover is a measurement-based handover. The
control plane implements measurement-based handover or blind
handover based on this identifier.

Enable the function of measurement-based LB and disable all blind
handover functions. Observe whether the statistics of counters
(C373485193, C373485194, and C373485195) are normal.
Passing Criterion:
The statistics of counters (C373485193, C373485194, and
C373485195) are normal.
Note None
From H3A Austria

6.4.97 20170412122658 Deteriorated KPIs after a New eNodeB-Level

License File is Loaded
Table 6-99 Deteriorated KPIs After a New License Is Loaded
Issue Name Deteriorated KPIs after a new license is loaded
Number 20170412122658
Level B
Symptoms Handover KPIs deteriorate after a new license is loaded.
Impact Handover KPIs deteriorate after a new license is loaded.
Analysis eNodeB-level License file loading initiates the eNodeB to perform

table-level incremental operation. The index of LTE baseband resource
tables is automatically generated by the system. It is recreated during
the incremental process. If the original index is disordered, the new
index will be different. KPIs deteriorate because services are not
registered and the trigger of this increase is not taken into
consideration.
Solution Keep the original index ID when the MO loads a new eNodeB-level
license file.

Load a license.
Passing Criterion:
The KPIs are normal after a license is loaded.
Note None
From Macedonia
6.4.98 20170406100941 CellID Reported as 65535 Sometimes
Table 6-100 CellID reported as 65535 sometimes
Issue Name CellID reported as 65535 sometimes
Number 20170406100941
Level B

Issue Name CellID reported as 65535 sometimes
Symptoms The CellID of a cell KPI is reported as 65535 sometimes.
Impact The KPI statistics has invalid records.
Analysis During a context release process triggered by cell removal, the cell
may reject E-RAB change, setup and release messages or cached
messages. In this case, the CellIDs of reported KPIs are 65535.
Solution Make CellID 65535 not reported.
Verification Check the context release when a cell removes a cell link.
The CellID 65535 does not exist in the cell statistics.
Note None
From Peru
6.4.99 20170405152832 Deteriorated E-RAB Call Drop Rate after the

Netmax-L Is Enabled
Table 6-101 Deteriorated E-RAB call drop rate after the Netmax-L is enabled
Issue Name Deteriorated E-RAB call drop rate after the Netmax-L is enabled
Number 20170405152832
Level B
Symptoms The E-RAB call drop rate deteriorates after the Netmax-L is enabled.
Impact The E-RAB call drop rate deteriorates.
Analysis When the Netmax-L is enabled, the periodic measurement is also

enabled, which increase the number of uplink PDUs. For special
terminals, the probability of integrity protection failure increases.
Solution Enable the integrity protection for only security commands and the
signaling that enables the security and key, and ensure consistent keys
between terminals and eNodeBs.
Verification Enable the periodic measurement. The E-RAB call drop rate never
deteriorates.

Issue Name Deteriorated E-RAB call drop rate after the Netmax-L is enabled
Note None
From Econet Zimbabwe
6.4.100 20170401154539 Some UEs are Released after Load Balancing

Based on RRC User Access and CA are Enabled at the Same Time
Table 6-102 Some UEs are Released after Load Balancing Based on RRC User
Access and CA are Enabled at the Same Time
Issue Name Some UEs are Released after Load Balancing Based on RRC User
Access and CA are Enabled at the Same Time
Number 20170401154539
Level B
Symptoms UEs are released after they are connected.
Impact The RRC call drop rate increases.
Analysis During an access process, the eNodeB caches an internal message

after enabling the LB based on RRC access. This message occupies
the last place of the caching queue. At this time, another message is
delivered due to a CA logic error. As a result, the UE is released
because the queue is full.
Solution Expand the message caching queue. The CA message in the above
case is not allowed to cache.
Verification The UE will not be released after the LB based on RRC access and the
CA are enabled.
Note None
From Austria

6.4.101 20170327102011 Two Sleep Cells in a Single eNodeB
Table 6-103 Two sleep cells in a single eNodeB
Issue Name Two sleep cells in a single eNodeB
Number 20170327102011
Level B
Version V3.30.20.51
Symptoms One site has transmission packet loss. The eNodeB reports "Link
between OMM and NE broken (198099803)" on 22nd 2:16. On 22nd
10:27, its baseband board restarts (no information found in the log).
After that, Cell 1 and Cell 3 have no users and Cell 2 is normal.
Impact The UE access is affected.
Analysis When the BPL1 board is powered on, the OAM address initiation is
probably later than the DSP address configuration request. As a result,
the DSP SRIO parameter is configured to 0.
Solution The OAM verifies whether the address parameter is null when
delivering an address configuration parameter.
The OAM does not deliver the parameter if the address is null. The
DSP continues to request configuration until the address parameter is
initialized and delivered to the DSP.
This ensures that the DSP obtains correct address parameters.

Reset the BPL1 board. After the cell is established, observe whether
the SRIO address parameter is set to 0 and whether any user accesses
the cell.
Passing Criterion:
The user access is normal.
Note None
From UM Malaysia

6.4.102 20160907063911 Uplink BLER is High When Adding and Removing

Secondary Carrier, Affecting UE Uplink throughput
Table 6-104 Uplink Bler is High When Adding and Removing Second Carrier, Affecting
UE Uplink throughput
Issue Name Uplink Bler is High When Adding and Removing Second Carrier,
Affecting UE Uplink throughput
Failure Level B
Symptoms Uplink BLER is high, UE throughput is low
Impact the uplink BLER increase, affecting the UE throughput
Analysis Enable the DL Two-carrier CA, the active state of secondary carrier is
not updated when the secondary carrier is deleted and then added.
Solution When Removing the secondary carrier, make the carrier activation
status be updated correctly.

1. Enable the Two carriers CA, make UE attach and do FTP service.
2. Remove and then add the secondary carrier.
Passing Criterion:
BER is normal and the UE Uplink throughput is consistent with the
theoretical value.
Note None
6.4.103 20170609195530 Low Speed of Some Samsung S8 UEs in the Speed

Test
Table 6-1 Low Speed of Some Samsung S8 UEs in the Speed Test
Fault Name Low speed of some Samsung S8 UEs in the speed test
Fault No. 20170609195530
Fault Level B
Involved Version V4.15.10.30P20, V4.15.10.30P10, and V4.15.10.30P30

Fault Name Low speed of some Samsung S8 UEs in the speed test
Symptom The speed of some Samsung S8 UEs is too low in the speed test.
Impact UEs with CAT15 or above capability level cannot access the network.
Cause Analysis The UE capability level reported by the new version of Samsung S8 is
CAT16, but the eNodeB V4.15 version does not support UEs of. If the
UE capability level configured on the eNodeB is higher than 15, a UE
instance error will occur and affect UE scheduling.
Solution Protection code is added to the eNodeB. When the UE capability level
is higher than or equal to 15, lower the UE capability level is to ensure
proper data scheduling.
External Use a UE with CAT15 or above capability level (for example: Samsung
Verification S8) to perform a speed test.
Method The traffic is normal.
Remarks None
From China Unicom
6.4.104 20170601042826 LTE-UMTS Handover Failure
Table 6-2 LTE-UMTS Handover Failure
Fault Name LTE-UMTS handover failure
Fault No. 20170601042826
Fault Level B
Involved Version V4.15.10.30P30
Symptom LTE-UMTS handover preparation failure instantaneously occurs in a

few cells due to “other causes”.
Impact The LTE-UMTS handover preparation success rate is affected.
Cause Analysis Some UEs carry much LTE and UTRAN capability information, but the
UmtsRrc_ToTargetRNC_Container coding buffer set by the eNodeB is
too small (only 1024 bytes), causing coding failure when the eNodeB
generates LTE-UMTS requests in accordance with UE capability
information.
Solution Expand the UmtsRrc_ToTargetRNC_Container coding buffer to solve

the coding failure.

Fault Name LTE-UMTS handover failure
External Verification method:

Verification Use a UE with a LTE capability size of 1024 bytes, trigger it handover
Method from LTE to UTRAN
Passing Criteria:
Handover from LTE to UTRAN can be normally performed.
Remarks None
From China Unicom
6.4.105 20170526143015 Added E-RAB Setup Successful Rate Drops Greatly

(Even to 30% on Some Sites) After Deploying the MR Feature in the Current
LTE Network
Table 6-3 Added E-RAB Setup Successful Rate Drops Greatly (Even to 30% on Some
Sites) After Deploying the MR Feature in the Current LTE Network
Fault Name Added E-RAB setup successful rate drops greatly (even to 30% on
some sites) after Deploying the MR feature in the current LTE network
Fault No. 20170526143015
Fault Level B
Involved Version
Symptom The "Added E-RAB Setup Success Rate" indicator is degraded. After
the MR measurement feature that is already enabled on NetMax is
disabled, the KPI with the 15 minute granularity is recovered.
Impact The E-RAB setup success rate drops.
Cause Analysis Reconfiguration fails because the UE does not support the
measurement of the difference between reception and transmission
time. After the UE initiates the reestablishment flow for reconfiguration
failure, the reconfiguration fails again, and the reestablishment is
directly rejected. At this moment, the core network initiates the E-RAB
establishment flow, causing the eNodeB to directly return E-RAB
establishment failure and leading to the drop of the E-RAB
establishment success rate.
Solution The capability to determine time difference between UE reception and

Fault Name Added E-RAB setup successful rate drops greatly (even to 30% on
some sites) after Deploying the MR feature in the current LTE network
transmission is added to the eNodeB. The configuration of measuring

time difference between UE reception and transmission is delivered
only when the UE capability clearly supports the measurement.

Verification 1. Use UEs with different capabilities to access the network.
Method Determine whether the configuration of measuring time difference
between UE reception and transmission is delivered.
Passing Criteria:
1. When the UE capability supports time difference between reception
and transmission, the time difference measurement configuration is
delivered. Otherwise, the configuration is not delivered.
Remarks None
From Malaysia DIGI
6.4.106 20170519194516 Number of Inter-Frequency Handover Out Requests

With/Without GAP Changed Greatly
Table 6-4 Number of Inter-Frequency Handover Out Requests With/Without GAP

Changed Greatly
Fault Name Number of inter-frequency handover out requests with/without GAP

changed greatly
Fault No. 20170519194516
Fault Level C
Symptom After the V3.2 version is upgraded to the V3.3 version, the number of
inter-frequency handover out requests with GAP increased, but the
number of inter-frequency handover out requests without GAP
decreased.
Impact GAP handover statistics are not accurate.
Cause Analysis When the number of GAP inter-frequency handover out requests is
reported, the determination condition uses an incorrect field, causing
statistics to be inaccurate. The field of “the activation of Gap” is used,
but in fact, the field of “the current measure report whether or not to

Fault Name Number of inter-frequency handover out requests with/without GAP

changed greatly
bring a GAP measure configuration” should be used.
Solution When the number of inter-frequency handover out requests

with/without GAP is reported, the determination condition is changed
to the field of “the current measure report whether or not to bring a
GAP measure configuration”.

Verification 1. Use a UE that supports GAP.
Method 2. Configure that the neighbor cell band does not support GAP.
3. Perform a large-capacity test.
Passing Criteria:
1. The number of inter-frequency handover out requests with GAP is
not reported.
Remarks None
From Malaysia DIGI
6.4.107 20170515223238 Abnormal RSSI KPI on a Site in the Current Network
Table 6-5 Abnormal RSSI KPI on a Site in the Current Network
Fault Name Abnormal RSSI KPI on a site in the current network
Fault No. 20170515223238
Fault Level C
Symptom RSSI has a maximum value, –15 dBm.
Impact The error probability of RSSI values reported by the network system is
small. The errors only affect RSSI reporting, and do not affect
services.
Cause Analysis The higher layer of the RRU does not determine abnormal RSSI
measurement values returned by the lower layer. When an abnormal
value is higher than the maximum value allowed by the system, –15
dBm, the RRU forcefully sets the value to –15 dBm. Therefore, the –15
dBm RSSI value is reported.
Solution When receiving an RSSI measurement result returned from the lower

Fault Name Abnormal RSSI KPI on a site in the current network
layer, the higher layer of the RRU determines whether the value is
abnormal. If it is abnormal, the higher layer does not report the
measurement result.

Verification Observe RSSI performance reports in the current network and check
Method whether the maximum value –15 dBm exists.
Passing Criteria:
1. The maximum value –15 dBm does not exist in RSSI performance
reports.
Remarks None
From Italy Windtre project overlay
6.4.108 20170523211629 UL throughput in PCC of CA UE continue to drop

below 10M in intra-cell handover process
Table 6-105 UL throughput in PCC of CA UE continue to drop below 10M in intra-cell

handover process
Issue Name UL throughput in PCC of CA UE continue to drop below 10M in intra-cell

handover process
Defect 20170523211629
Number 614005932201
Failure B
Level
Symptoms The CA UE UL throughput of decreases sharply after the UE context

modification process is excuted.
Impact UL throughput in PCC of CA UE.
Analysis The CQI info of SCC has not been configured to CA UE, Which leads to the
UL throughput in PCC of CA UE decreased in the scenario of UE context
modification.
Solution Configure the right CQI info of SCC to CA UE in the scenario of UE context

Issue Name UL throughput in PCC of CA UE continue to drop below 10M in intra-cell

handover process
modification.

1 Add SCells successfully
2 CA UE do UL and DL FTP service
3 Trigger the CA UE context modification and make it do intra-cell
handover.
4 Observe the UL and DL throughput of CA UE.
Passing Criterion:
The UL and DL throughput of CA UE is normal.
Note None
From Austria Hi3G

Operator
6.4.109 20170713144315 When NB-IOT is Enabled on LTE eNodeB, More than 60

Sites Reported Blocking Alarms. 40 Sites Recovered itself, and More than a
Dozen Need Manual Processing
Table 6-106 When NB-IOT is Enabled on LTE eNodeB, More than 60 Sites Reported
Blocking Alarms. 40 Sites Recovered itself, and More than a Dozen Need Manual
Processing
Issue Name In V3.4, When NB-IOT is enabled on the eNodeB, more than 60
sites reported blocking alarms. 40 sites recovered itself, and
more than a dozen need manual processing
Failure Level B
Bug Version V3.20
Symptoms When the LTE sites are converted to a NB and LTE mixed mode,
the “radio” and “funcset” configuration are modified, the baseband
board of some of the sites is in an artificial block state after the
whole table synchronization is performed.
Impact Cell state is abnormal, unbolck baseband board by manual

processing through the dynamic management or MML command.

Issue Name In V3.4, When NB-IOT is enabled on the eNodeB, more than 60
sites reported blocking alarms. 40 sites recovered itself, and
more than a dozen need manual processing
Analysis For some specific scenarios (changes in funcset), make sure IQ

resources between BBU and RRU are deleted completely,
preventing the RRU PA problems caused by misaligned IQ units.
When the cell is setup, eNodeB judges whether the funcset has
changed or not, block the baseband board for 15s when changes
occur. During the blocking of the baseband board, if the CC is reset,
the baseband board is in the state of artificial block all the time and
needs manual recovery.
Solution In the cell setup process, when the funcset changes, the manual
operation field of the baseband board is no longer modified, and
allow a 15s transient cell setup failure.

Modify the baseband board funcset, perform increment or whole
table synchronization.
Pass Criterion:
1. Cell setup is failure in 15s.The baseband board state is not
blocked.
2. Cell setup is successful finally.
Note None
6.4.110 20170725190154 Software Runs abnormal in the CA Use Handover with

SCC Scenario
Table 6-107 Software Runs abnormal in the CA Use Handover with SCC Scenario
Issue Name software runs abnormal in the CA user handover with SCC scenario

614005975545
Failure Level B
Symptoms "software runs abnormal" alarms appear frequently in CA sites

Issue Name software runs abnormal in the CA user handover with SCC scenario
Impact Software runs abnormal and user services are affected.
Analysis When CA user handover with SCC is enabled, during performing CA

UE handover with SCC, eNodeB receives the UE release command
from the core network before delivering RRC reconfiguration
message, which will cause that the PCC is released earlier than the
SCC selected by the target side is released. When SCC is releasing,
it need the PCC information which has been released before, so
there is an invalid reference, resulting in abnormal software
operation.
Solution When SCC is releasing, eNodeB does not get the PCC informaiton.

Enable CA UE handover with SCC feature, trigger CA UE with SCC
handover, and trigger UE release process at the same time.
Pass Criterion:
1 Observe the signal trace, the eNodeB receives the UE release
command from the core network before sending the RRC
reconfiguration message, 2 there are no "software runs abnormal "
alarms alarms.
Note None
6.4.111 20170625105513 Some of the Sites the VoLTE Calls are Dropped
When Using Apple Phone, and the Phone Interface Appeares “Call
Failed”
Table 6-108 Some of the sites the VoLTE calls are dropped when using Apple phone,
and the phone interface appeares “Call Failed”
Issue Name Some of the sites the VoLTE calls are dropped when using
Apple phone, and the phone interface appeares “Call Failed”
Failure Level B
Symptoms Some of the sites the VoLTE calls are dropped when using Apple
phone, and the phone interface appeares “Call Failed”

Issue Name Some of the sites the VoLTE calls are dropped when using
Apple phone, and the phone interface appeares “Call Failed”
Impact VOLTE calls are dropped
Analysis One core of the baseband board processed timed out, and there
was a skip frame, resulting in abnormal operation of the
DRX-related timers, and VoLTE call single-pass.
Solution Reduce and optimize the processing time of the downlink

scheduling core in the following two ways to ensure that the timeout
no longer occurs:
1 Disable the full schedule feature and enable DFS control for RRC
message; or
2 ENodeB performs downlink skip frame optimization.
Verification Do voice call test using the Apple phone, there is no longer appear
single-pass phenomenon and dropped calls.
Note None
6.4.112 20170821161304 VoLTE UE is Released after eNodeB Receiving the

UE Context Modification Request with the CSFB Indication
Table 6-109 VoLTE UE is Released after eNodeB Receiving the UE Context

Modification Request with the CSFB Indication
Issue Name VoLTE UE is Released after eNodeB Receiving the UE Context


20170821161304
Failure Level C
Symptoms VoLTE UE is released after eNodeB receiving the UE context

modification request with the CSFB indication
Impact VoLTE UE is dropped
Analysis When the UE is doing the VoLTE service, the core network sends
the UE context modification request with the CSFB indication to

Issue Name VoLTE UE is Released after eNodeB Receiving the UE Context

eNodeB, the eNodeB initiates the CSFB processing carrying the

redirection information and releases UE.
Solution After eNodeB receives the UE context modification request carrying

the CSFB indication, eNodeB should judge whether the current UE
is a VoLTE user, and if it is a VoLTE user, the CSFB processing is
not performed.

1 UE accesses to the cell, and does VoLTE service.
2 Triggers a UE context modification request that carries the CSFB
indication from the core network.
Pass Criterion:
UE VoLTE service will not be dropped
Note None
From Operator Malaysia DIGI
6.4.113 20170612124416 BPN2 board Resets and Reports Alarm “software

runs abnormal”
Table 6-110 BPN2 board resets and reports alarm “software runs abnormal”
Issue Name BPN2 board resets and reports alarm “software runs
abnormal”
Failure Level B
Bug Version LTE-V3.30.20
Symptoms eNodeB parameter is configured error, resulting in core 10, 13 or 16

of BPN2 baseband board abnormal.
Impact BPN2 board rports aarm “software runs abnormal” nd reset.
Analysis PUCCH Format 1b and Format 3 resoures configured error by

eNodeB are mapped into the same physical RB, resulting in the
PUCCH resoures are processed error and BPN2 resets.
Solution When PUCCH Format 1b and Format 3 resoures configured error

by eNodeB are mapped into the same physical RB, eNodeB does

Issue Name BPN2 board resets and reports alarm “software runs
abnormal”
not process PUCCH to prevent BPN2 reset.

1 Set the parameter "RB number occupied by PUCCH Fmt3" to1
2 Configure downlink CA.
Pass Criterion:
eNodeB runs normal, and BPN2 doesn't reset.
Note None
6.4.114 2017071721244 CSSR Indicators of the Whole Network are

Descreased
Table 6-111 CSSR Indicators of the Whole Network are Descreased
Issue Name CSSR Indicators of the Whole Network are Descreased
Failure Level B
Symptoms The whole network of CSSR indicators are descreased.

When the ERAB SETUP and the handover process occur at the
same time, the ERAB SETUP failure and reports “setup failure,
handover caused” counter.
Impact ERAB SETUP success rate is descreased.
Analysis When the ERAB SETUP and the handover process occur at the
same time, the ERAB will SETUP failure, However, this does not
cause UE drop, so the counter is reported error.
Solution When the ERAB SETUP and the handover process occur at the
same time, the ERAB will SETUP failure, eNodeB report “ERAB
setup success” counter instead of “setup failure, handover caused”
counter.

Trigger the scene that the ERAB SETUP and the handover process

Issue Name CSSR Indicators of the Whole Network are Descreased
occur at the same time.

Pass Criterion:
Observe counters, and the “ERAB setup success” counter is
increased.
Note None
From Operator Malaysia digi
6.4.115 20170906234253 In 3CC CA Test, Throughput is Reduced to Zero and

Reestablishment Occurs
Table 6-112 In 3CC CA Test, Throughput is Reduced to Zero and Reestablishment

Occurs
Issue Name In 3CC CA Test, Throughput is Reduced to Zero and

Failure Level C
Symptoms In 3CC CA test, throughput is reduced to zero and reestablishment

occurs during the cell service peak period.
Impact In 3CC CA test, throughput is reduced to zero and reestablishment

occurs
Analysis The primary carrier assigns a PUCCH format3 resource 0 (TPC is

0)for secondary carrier 1 of UE, and then does not determine
whether the UE has been allocated the PUCCH resource and
assigns another PUCCH format3 resource 1 (TPC is 1)for
secondary carrier 2 of UE. Assigning different PUCCH resources to
the two secondary carriers is not in accordance with the protocol
and this will make the PUCCH resource location is different beween
UE and eNodeB, so it causes a large number of error PUCCH
HARQ feedback.
Solution If a secondary carrier of the UE has been allocated the PUCCH

resource, the other secondary carriers directly use the PUCCH
resource, eNodeB does not need to assign repeatedly .

Issue Name In 3CC CA Test, Throughput is Reduced to Zero and


1 At least five UEs supporting 3CC attach.
2 Do 3CC test.
Pass Criterion:
The throughput is normal.
Note None
FromOperator Austria H3A
6.4.116 20170903184453 KPI statistics of TA distribution are exception
Table 6-113 KPI statistics of TA distribution are exception
Issue Name KPI statistics of TA distribution are exception

614006057290
Failure Level C
Symptoms After upgrading to V3.40.20.10P30 version, the KPI statistics of TA

distribution change greatly.
Impact TA statistical rules are different between V3.30.20.51 and

V3.40.20.10P30, this will causes the judgment on the distance
between the UE and eNodeB is not accurate for OAM users.
Analysis TA statistical rules are different between V3.30.20.51 and

V3.40.20.10P30 version.
Solution Modify the statistical rules for TA distribution to be the same as

V3.30.20.51.

1 UEs access, and Verify KPI statistics of TA distribution.
Pass Criterion:
1 KPI statistics of TA distribution are the same as V3.30.20.51.
For example, when the UE accesses at the near point (TA=1), the
C373556400 statistic is added by one.

Issue Name KPI statistics of TA distribution are exception
Note None
From Operator Austria H3A
6.4.117 20170908155846 One or More Cells Scheduling Capacity Per TTI are
Insufficient for BPN2 with 6 cells
Table 6-114 One or More Cells Scheduling Capacity Per TTI are Insufficient for BPN2
Issue Name For BPN2 with 6 cells, One or More Cells Scheduling Capacity
Per TTI are Insufficient.
Failure Level B
Symptoms When service is busy, the user number of scheduling per TTI
reduces from 7 to a litter more than 1.
Impact Infect the users numbers of UL scheduling.
Analysis When the channel quality is worse, the eNodeB use the
conservative scheduling policy for the UE, and then generates
"minimum number of RBs allocated to the power limited UE" is 0,
resulting in the eNodeB assigns 0 RB to the UE finally.
Solution eNodeB chooses the bigger value from "minimum number of RBs
allocated to the power limited UE " and " minimum number of RBs
allocated in UL " as the minimum number of RBs for power limited
UE.

When service is busy, observe the average number of users per TTI
and the average utilization of uplink PRB.
pass criteria:
1 As the number of users increases, the average number of users
per TTI has not decreased significantly.
2 As the number of users increases, the average utilization of UL
PRB has not decreased significantly.
Note None

Issue Name For BPN2 with 6 cells, One or More Cells Scheduling Capacity
Per TTI are Insufficient.
From Operator None
6.4.118 20170922130010 P10 UE is Released Frequently after Accessing, SCC is

not added and UE can not Do Service in CA Test
Table 6-115 P10 UE is Released Frequently after Accessing, SCC is not added and UE
can not Do Service in CA Test
Issue Name P10 UE is Released Frequently after Accessing, SCC is not

added and UE can not Do Service in CA Test.

614006086789
Failure Level C
Symptoms The UE is released during the primary carrier frequency priority

handover procedure.
Impact UE cannot access, affect the UE service.
Analysis After the UE accesses, in the primary carrier frequency priority

handover process, the eNodeB processes the handover type error,
and the UE is released.
Solution eNodeB modify the handover type in the primary carrier frequency
priority handover process, make sure handover type is right.

UE accesses and do primary carrier frequency priority handover,
observing whether the handover is performed successfully, and
whether the UE is being released abnormally.
Pass Criterion:
The handover is performed successfully.
Note None
From Operator Italy

6.4.119 20171024144305 RRC Connection Reconfiguration for 3CC CA Fails

and UE Starts RRC Connection Reestablishment
Table 5-42 RRC Connection Reconfiguration for 3CC CA Fails and UE Starts RRC
Connection Reestablishment
Issue Name RRC Connection Reconfiguration for 3CC CA Fails and UE

Starts RRC Connection Reestablishment
Failure Level B
Symptoms After adding the secondary carrier, a 3CC CA UE starts RRC

connection reestablishment.
Impact The UE starts RRC connection reestablishment.
Analysis When the eNodeB reconfigures the RRC connection of the UE to

add a secondary carrier, a configuration error occurs on the V10i0
MaxLayersMIMO IE, causing RRC connection reestablishment.
Solution When the eNodeB reconfigures the RRC connection of the 3CC CA
UE to add a secondary carrier, ensure that the V10i0
MaxLayersMIMO IE is correctly configured for the secondary
carrier.

In an adjacent or same-coverage neighbor relation, add or delete a
secondary carrier for a 3CC CA UE.
Criteria:
The secondary carrier is added or deleted successfully.
Note None.
From Operator Italy Wind3

6.4.120 20171022052609 eNodeB Reset Due to BNP2 Reset after LB and Cell
Reselection Priority Are Disabled
Table 5-43 eNodeB Reset Due to BNP2 Reset after LB and Cell Reselection Priority Are
Disabled
Issue Name eNodeB Reset Due to BNP2 Reset after LB and Cell
Reselection Priority Are Disabled
Failure Level B
Bug Version V3.40.20.10p20
Symptoms Enabling LB may introduce another problem if lots of users are

involved. After LB is disabled, logs show that there is no user in the
2.6 GHz cell (cellid=12). Alarms show that software operation errors
occur on the BPN2 board in slot 8 and that core 10 fails.
Impact The UE access service in the cell is affected.
Analysis Because the cell load is high and eNodeB scheduling timer expires,
the demodulation parameters are not delivered in time, and a
random value is used to demodulate signals, causing software
operation errors occurring on the BPN2 board.
Solution Add a parameter error protection mechanism on the eNodeB. When

the scheduling timer expires, the eNodeB discards the data in the
current TTI.

Perform a multi-carrier CA 600 UE load test on an eNodeB.
Criteria:
The eNodeB operates properly in a long time.
Note None.
From Operator Milan, Italy

6.4.121 20171003182210 RRC Call Drop Rate Is Increased and Is Restored

after the CCE Board Is Restarted
Table 5-44 RRC Call Drop Rate Is Increased and Is Restored after the CCE Board Is
Restarted
Issue Name RRC Call Drop Rate Is Increased from 0.01% to 15% and Is
Restored after the CCE Board Is Restarted
Failure Level B
Symptoms The RRC call drop rate is increased, and is restored after the CCE
board Is restarted.
Impact The RRC call drop rate is increased.
Analysis If the CA process is interrupted by RRC connection

reestablishment, the error state of the CA process is saved. When a
UE accesses the cell or is handed over to the cell, the saved CA
process (with errors) is used, causing CA failure. Therefore, the UE
is released, and the RRC call drop rate is increased.
Solution Initialize the process state and abort cause if the CA process fails to
ensure that the CA process can be implemented successfully next
time.

Configure multiple intra-frequency secondary carriers for the
primary carrier. Trigger RRC connection reestablishment during
secondary carrier addition or modification.
Criteria:
Secondary carriers can be added or modified successfully.
Note None.

6.4.122 20170922133939 CA User Data Volume Does Not Match the 2CC and
3CC Statistical Result
Table 5-45 CA User Data Volume Does Not Match the 2CC and 3CC Statistical Result
Issue Name CA User Data Volume Does Not Match the 2CC and 3CC
Statistical Result
Failure Level C
Symptoms 1. Data volume of downlink active CA users is greater than that of

downlink active 2CC+3CC CA users.
2. The number of downlink active CA users is greater than the
number of downlink active 2CC+3CC CA users.
Impact The data volume of active CA users does not match the statistical
result of 2CC+3CC CA users.
Analysis Large-capacity performance optimization causes KPI reporting

errors of the number of active 2CC+3CC CA users.
Solution Roll back the KPI statistical method of the number of active
2CC+3CC CA users.

After software version upgrade, check whether the number of
downlink active CA users matches the number of active 2CC+3CC
CA users.
Criteria:
The number of downlink active CA users is the same as that of
downlink active 2CC+3CC CA users.
Note None.
6.4.123 20170912102025 Sleeping Cell Is Detected on an eNodeB
Table 5-46 Sleeping Cell Is Detected on an eNodeB
Issue Name Sleeping Cell Is Detected on an eNodeB

Issue Name Sleeping Cell Is Detected on an eNodeB

614006057652
Failure Level C
Symptoms A cell is deleted and established due to transient S1 interruption. No

IQ data is being transmitted after the cell is in normal state.
Impact The cell stays in normal state without power.
Analysis When a cell is deleted from the RRU, the RRU returns a cell
deletion success message and then releases resources. In such a
way, the cell deletion and cell establishment procedures are mixed
together, and the eNodeB may release the resources for cell
establishment by mistake. Therefore, the cell does not have power
after being established.
Solution Optimize the cell deletion procedure. When a cell is deleted from
the RRU, the eNodeB deletes the related resources and then
returns a cell deletion success message.

Trigger cell deletion and cell establishment procedures in a
transient S1 interruption scenario.
Criteria:
The cell is established successfully, and outputs power properly.
Note None.
6.4.124 20170829144028 R8988 S3500 Cannot Enable AISG and Necessary

Information for Dynamic Management Is Missing on the EMS
Table 5-47 R8988 S3500 Cannot Enable AISG and Necessary Information for Dynamic
Management Is Missing on the EMS
Issue Name R8988 S3500 Cannot Enable AISG and Necessary Information
for Dynamic Management Is Missing on the EMS
Failure Level C

Issue Name R8988 S3500 Cannot Enable AISG and Necessary Information
for Dynamic Management Is Missing on the EMS
Symptoms The R8988 S3500 can neither enable AISG nor scan an antenna.
Impact The R8988 S3500 cannot scan the RET antenna connected to the
RS485 interface.
Analysis The R8988 is configured to connect an RET antenna through the

CAL interface by default, while most antennas are manufactured to
connect the R485 interface due to the unmatured CAL technology.
Solution Modify the default AISG interface of the R8988 to RS485,

Select an R8988 S3500 eNodeB and scan the RET antenna on the
back end.
Criteria:
The eNodeB can detect the RS485 interface and can configure the
RET antenna.
Note None.
From Operator Bolivia VIVA project
6.4.125 20170811181731 Sleeping Cell Is Detected on a Qcell and No UE

Accesses the Cell
Table 5-48 Sleeping Cell Is Detected on a Qcell and No UE Accesses the Cell
Issue Name Sleeping Cell Is Detected on a Qcell and No UE Accesses the

Cell
Failure Level B
Symptoms A sleeping cell is detected on a Qcell and no UE accesses the cell.
Impact UEs cannot access the cell.
Analysis Antenna connection errors occur on the PG FPGA.

If the LTE cells connected to the uplink optical interface of the
level-1 PB have multiple bandwidth configurations, for example, 20

Issue Name Sleeping Cell Is Detected on a Qcell and No UE Accesses the

Cell
MHz and 10 MHz, the data of the LTE cells are transmitted in
sequence. If the bandwidth of the first LTE cell is different from that
of the fourth LTE cell and the antenna bandwidth parameters of the
fourth LTE cell are configured for the first LTE cell by mistake, an
antenna connection error occur.
Note: 1L refers to 20 MHz/15 MHz/10 MHz/5 MHz 2-antenna
Solution The PB corrects the connection errors. If multiple LTE bandwidth

specifications are used, ensure that the corresponding parameters
are configured correctly.

Observe the Qcell for a long time, and check whether a sleeping cell
can be detected.
Criteria:
No sleeping cell is detected on the Qcell.
Note None.
6.4.126 20170726104847 CCE1 Restarts Repeatedly after a Hot Patch Is

Installed
Table 5-49 CCE1 Restarts Repeatedly after a Hot Patch Is Installed
Issue Name CCE1 Restarts Repeatedly after a Hot Patch Is Installed
Failure Level A-Critical
Symptoms After a hot patch is installed, the CCE1 board restarts repeatedly
when a UE accesses the cell or is handed over to the cell.
Impact The CCE1 board cannot operate properly, and the UE cannot
access the cell.
Analysis Too many functions are used in the hot patch, and some useless
functions are replaced.
Solution Simplify the hot patch. Reserve only the necessary functions to

Issue Name CCE1 Restarts Repeatedly after a Hot Patch Is Installed
reduce risks.

Use the UE to access the cell or trigger a handover to the cell.
Criteria:
1. The UE can access the cell properly and can be handed over to
the cell properly.
2. The CCE1 board is operating properly.
Note None.
6.4.127 20170714002057 UE Capability (Supporting for 4x4 MIMO) Displayed

in the Samsung S8 UE Log Is Different from That of the ZTE eNodeB
Log
Table 5-50 UE Capability (Supporting for 4x4 MIMO) Displayed in the Samsung S8 UE
Log Is Different from That of the ZTE eNodeB Log
Issue Name UE Capability (Supporting for 4x4 MIMO) Displayed in the

Samsung S8 UE Log Is Different from That of the ZTE eNodeB
Log

614005965294
Failure Level B
Symptoms The UE supports 4x4 MIMO, but no 4x4 MIMO field can be traced
from UE signaling messages.
Impact The UE capability (4x4 MIMO) field is missing from eNodeB

signaling trace messages.
Analysis The eNodeB does not implement second decoding on the extended
UE capability field, and the related field cannot be traced from
signaling messages.
Solution Verify that the eNodeB implements second decoding on the

extended UE capability field.

Issue Name UE Capability (Supporting for 4x4 MIMO) Displayed in the

Samsung S8 UE Log Is Different from That of the ZTE eNodeB
Log

Use a 4x4MIMO-supported UE to access the cell.
Criteria:
In signaling trace messages on the eNodeB, the 4x4MIMO field can
be decoded correctly and is the same as that displayed in the UE’s
log.
Note None.
From Operator Italy WT project
6.4.128 20171009231056 Incorrect Average Number of RRC Connections

(Counter C373200030) Is Reported
Table 5-51 Incorrect Average Number of RRC Connections (Counter C373200030) Is

Reported
Issue Name Incorrect Average Number of RRC Connections (Counter

C373200030) Is Reported

20171009231056
Failure Level B
Bug Version V3.50.10.00B07P08
Symptoms When the average number of RRC connections is reported, the

product process on the CC board is reset.
Impact The eNodeB cannot operate properly.
Analysis When the average number of RRC connections is reported, the cell
ID is attached. If the cell ID is an invalid value, the report is regarded
as abnormal statistics, causing reset of the CC product process.
Solution Modify the statistical method of abnormal cell IDs.

Use a UE to access the cell.
Criteria:

Issue Name Incorrect Average Number of RRC Connections (Counter

C373200030) Is Reported
1. Verify that the maximum number of RRC connections and the

average number of RRC connections are reported correctly.
2. The eNodeB is operating properly.
Note C373200030: Average number of RRC connections
From Operator Hungary
6.4.129 20171017162247 High Type-2 Location Information Report Failure

Rate and Low Location Success Rate
Table 5-52 High Type-2 Location Information Report Failure Rate and Low Location
Success Rate
Issue Name High Type-2 Location Information Report Failure Rate and Low
Location Success Rate
Failure Level B
Symptoms Based on operators’ requirements, eNodeBs should report

measurement results in the following three scenarios:
1. The serving cell has two or more intra-frequency neighbor cells.
2. The serving cell has only one intra-frequency cell.
3. The serving cell has no intra-frequency cell.
In this version, eNodeBs do not report measurement results in
scenarios 2 and 3.
Impact The location report failure rate is high.
Analysis The location server developed by ZTE requires at least three points
to determine the UE location. If the measurement results do not
satisfy the condition, no measurement result is reported. Therefore,
the location information report failure rate is high, and the location
success rate is low. The solution cannot satisfy operators’
requirements.
Solution Modify the configuration to ensure that an eNodeB can report the

Issue Name High Type-2 Location Information Report Failure Rate and Low
Location Success Rate
RSRP, RSRQ, and TA of the serving cell and neighbor cells in

scenarios 2 and 3 if the location server requests the eNodeB to
report measurement results.

Move the UE to a serving cell having only one intra-frequency
neighbor cell or no intra-frequency neighbor cell, and delivers an
E-CID Type2 location task to the UE.
Criteria:
1. The eNodeB reports the RSRP, RSRQ, and TA.
2. The location success rate in a time period is increased.
Note None.
From Operator Italy WT project
6.4.130 20171019115216 One of Four SpeedTest UEs Has No Data Flow with
SpeedTest Being Enabled on the eNodeB
Table 5-53 One of Four SpeedTest UEs Has No Data Flow with SpeedTest Being
Enabled on the eNodeB
Issue Name One of Four SpeedTest UEs Has No Data Flow with SpeedTest
Being Enabled on the eNodeB
Failure Level C
Symptoms SpeedTest is enabled on the eNodeB. Four SpeedTest UEs are

running data services at the same time, but at least one UE has no
data flow.
Impact The SpeedTest result in a commercial network is affected, and the

test data rate is decreased.
Analysis Because the SpeedTest feature of the commercial international

server changes, the eNodeB cannot identify the rate-test software.
Solution Modify the rate-test software identification method on the eNodeB.

Issue Name One of Four SpeedTest UEs Has No Data Flow with SpeedTest
Being Enabled on the eNodeB

Enable SpeedTest on the eNodeB, and use four SpeedTest UEs to
run data services at the same time.
Criteria:
The four UEs have much the same data volume.
Note None.
From Operator Malaysia
6.4.131 20170926095849 Handover Prepareration Failure in MOCN Network

Sharing Site
Table 6-116 Handover Prepareration Failure in MOCN Network Sharing Site
Issue Name Handover Prepareration Failure in MOCN Network Sharing Site
Failure Level B
Symptoms UE reports a cell measurement report of PCI1, but eNodeB initiates

a handover to cell of PCI2 for the UE, leading to handover
prepareration failure and handover success rate decreased.
Impact Handover prepareration failure and handover success rate

decreased.
Analysis 1 When receiving the X2 Setup and eNB Configuration update

messages from the eNB2 and updating the PCI and frequency
information of the local neighbor configuration, the eNB1 does not
compare the PLMNs carrying in the local and X2 interfaces, and
updates the neighboring cell information of the PCI2 to PCI1
neighborhood information errorly.
2 Meanwhile, after receiving the measurement report of the PCI1
from the UE, the eNodeB matches to the PCI2 and initiates a
handover to the cell. The core network receives a HANDOVER
REQUIRED message, determines that the TAI is incorrect, and the
handover preparation fails.

Issue Name Handover Prepareration Failure in MOCN Network Sharing Site
Solution When matching the neighbor cell in the X2 and the neighbor cell
locally, the ECGI is directly used instead of the CellId.
Verification Verification：
1 eNB1: The primary PLMN of the eNB1 is PLMN1, and the cell3
(PCI3) is configured.
2 eNB2: The eNodeBID is eNodeBID1, the main PLMN of the eNB2
is PLMN2, and cell1 (PCI1) is configured.
3 eNB3: The eNodeBID is eNodeBID1, the main PLMN of the eNB3
is PLMN1, and Cell1 (PCI2) is configured.
4 eNB1 and eNB2 are configured with X2 and no neighbor
relationship exists.
5 eNB1 and eNB3 have no X2 and have the neighbor relationship.
6 The UE accesses to the eNB1, and the UE reports a
measurement report of the PCI1 to eNB1.
Pass conditions:
Handover will not be initiated for the UE.
Note None
From Operator Hungary Telenor
6.4.132 20171106235623 E-RAB Drop Rate Deteriorated Significantly after

Upgrade to V4.16.10.20P50
Table 6-117 E-RAB Drop Rate Deteriorated Significantly after Upgrade to

V4.16.10.20P50
Issue Name E-RAB drop rate deteriorated significantly after upgrade to

V4.16.10.20P50
Failure Level B
Bug Version V4.15.10.30P60(LTE eNodeB: V3.30.20.51P60)
Symptoms Before be upgraded to V4.16.10.20P50, the number of KPIs such as the

number of RRC connected users and the number of ERABs in the cell is
high, so it looks like that the E-RAB drop rate is deteriorated significantly
after upgrade.
Impact The number of RRC Connection user, the E-RAB number are incorrect

Issue Name E-RAB drop rate deteriorated significantly after upgrade to

V4.16.10.20P50
before upgrade.
Analysis In V4.15.10.30P60 the number of RRC Connection user,average and

maximum E-RAB number are not reset to zero when cell status is
abnormal, and when cell status return to normal,the new data is add to old
dirty data, so the number is higher than actual data, the V4.16.10.20P50 the
bug is fix.
Before the eNodeB is upgraded, when the cell is out of service, the number
of RRC connected users and the ERAB number are not cleared. After the
cell status is normal, the new data continues to accumulate on the old data,
causing that the number of RRC connected users and the ERAB number are
higher than the actual value.
Solution When cell status is out of service, the number of RRC connected users and
the ERAB number should be set to zero.

Trigger the cell out of service ,and observe the counters below :
C373240827 Maximum Number of RRC Connection User
C373200030 Mean Number of RRC Connection User
C373240827 Average E-RAB Number
C373240829 Maximum E-RAB Number
Pass Criterion:
The counters above are 0.
Note None
From Operator India Barti
6.4.133 20171023094938 LTE DL 64QAM Usage is Dropped after Upgrade to

UR16
Table 6-118 LTE DL 64QAM Usage is Dropped after Upgrade to UR16
Issue Name LTE DL 64QAM Usage is Dropped after Upgrade to UR16

Issue Name LTE DL 64QAM Usage is Dropped after Upgrade to UR16
Failure Level B
Symptoms After upgrading to V3.40.20.10P60, the TM4 DL 64QAM usage is

dropped.
Impact Affect the throughput, average MCS indicators and so on.
Analysis There are some optimizations as follows for TM4 in V3.40.20.10P60,

which affects the TM4 DL 64QAM usage.
(1) CQI/RI pairing process
(2) RI filtering algorithm
(3) Transmission scheme selection when retransmission is mixed
Solution For the above optimization, the related rollback is performed to keep the
same with V3.3.

1 UEs access, and do FTP / UDP service.
2 Observe the TM4 DL 64QAM usage.
Pass Criterion:
The TM4 DL 64QAM usage is basically the same as V3.3.
Note None
From Operator Indonesia
6.4.134 20171204172423 The iphone Siri Service is Abnormal after TCP

Proxy is Enabled
Table 6-119 The iphone Siri Service is Abnormal after TCP Proxy is Enabled
Issue Name The iphone Siri Service is Abnormal after TCP Proxy is Enabled
Failure Level C
Symptoms After the TCP proxy is enabled, the iphone siri service is abnormal, it can
not be respond to the input voice normally.
Impact Impact the iphone siri service.

Issue Name The iphone Siri Service is Abnormal after TCP Proxy is Enabled
Analysis The Siri service uses the Multipath option in the TCP protocol. This option
is not supported by the TCP proxy. The TCP ACK sent to the server does
not carry this option, causing the server to not reply with voice data
normally.
Solution During the three-times handshake, delete the Multipath option, and then
eNodeB do not carry this option when the TCP ACK is sent to the server,
the server can reply the voice data normally.

Enable and Disable TCP proxy feature, do siri service with iphone.
Pass Criterion:
The iphone siri service is normal whether TCP proxy feature is enabled or
disabled.
Note None
From Operator Malaysia UMobile
6.4.135 20171102034758 Cell RRC Number and ERAB Number are zero
Table 6-120 Cell RRC Number and ERAB Number are zero
Issue Name Cell RRC Number and ERAB Number are zero
Failure Level B
Bug Version V4.16.10.20P30(LTE eNodeB:V3.40.20.10P30.0803)
Symptoms When S1 link is broken，sometimes Cell RRC number and ERAB number
can not be reported rightly, they are always zero.
Impact For some cells，the number of RRC Connection User can not be reported
rightly, they are always zero.
Analysis When S1 link is broken, the Cell id is obtained incorrectly. When the
counters are reported, they can't be find the right Cell id, resulting in the
reported values are zero.
Solution When S1 link is breken, make sure the Cell id is right.

1 Configure two cells with continus Cell ID, for example, Cell ID =5 and

Issue Name Cell RRC Number and ERAB Number are zero
Cell ID =6
2 Configure two S1 with different PLMNs separately for Cell ID =5 .
3 Do enable/disable operations for one S1 of Cell ID =5 ON OMC .
2 Observe the counters below of the two cells if they can be reported
rightly.
C373200029 Maximum Number of RRC Connection User
C373200030 Mean Number of RRC Connection User
C373240827 Average E-RAB Number
C373240829 Maximum E-RAB Number
Passing Criterion:
The counters above of the two cells are all reported rightly, and there is no
counters reported with Cell ID =0.
Note None
6.4.136 20171017104554 RRUs are Reset with the Reason "the watchdog
resets"
Table 6-121 RRUs are Reset with the Reason "the watchdog resets"
Issue Name RRUs are Reset Sometimes with the Reason "the watchdog resets"
Failure Level B
Bug Version ALL
Symptoms When AISG scanning is initiated, some RRUs are reset.
Impact RRUs are reset, the service of the sites is affected.
Analysis When AISG scanning is initiated, the RRU saves scan results using array
and the array is out of bounds.
Solution When the RRU saves scan results, RRU adds array out of bounds
protection.

Do AISG scanning.
Pass Criterion:

Issue Name RRUs are Reset Sometimes with the Reason "the watchdog resets"
The scan results is reported normally and RRU is not reset yet.
Note None
From Operator ShanDong Unicom
6.4.137 20171009230453 The HTTP Download Speed is Low After TCP ACK
Split is Enabled
Table 6-122 The HTTP Download Speed is Low After TCP ACK Split is Enabled
Issue Name The HTTP Download Speed is Low After TCP ACK Split is Enabled
Failure Level B
Symptoms The HTTP download speed is lower when TCP ACK split is enabled than
the feature is disabled.
Impact Affects HTTP download speed and user experience.
Analysis When TCP data is out of order, the split ACK repeatedly acknowledges
the previously acknowledged packets, causing the packets to be
retransmitted. The server sending window becomes small, resulting in a
low HTTP download rate.
Solution When TCP data is out of order, eNode does not do TCP ACK split.

In TCP out of order scenarios, enabled and disabled TCP ACK split
function respectively, do HTTP download.
Pass Criterion:
Whether enabled or disabled TCP ACK split function, HTTP download
speed is normal and is basically the same.
Note None
From Operator JiLin Unicom

6.4.138 20170914094904 QCELL LTE Sites Enter into "sleep" Causing Users
Unable to Access and Zero Cell Throughput
Table 6-123 QCELL LTE Sites Enter into "sleep" Causing Users Unable to Access and
Zero Cell Throughput
Issue Name QCELL LTE Sites Enter into "sleep" Causing Users Unable to
Access and Zero Cell Throughput.
Failure Level B
Symptoms For four PB cascade, each cascaded cell is not merged scene, the second
level PB is reset due to the external power. When the second level PB
setup, QCELL LTE cells are out of service and enter into "sleep".
Impact QCELL LTE cells are out of service and enter into "sleep", all services of
the cells are interrupted.
Analysis In version V3.40.20.10, the optical resource allocation for the PB cascade
scene is allocated dynamically . When the second-level PB is powered off,
the cascaded optical resources of the first-level and second-level PBs are
re-allocated which is inconsistent with other levels of PB, so sleep cells
occur.
Solution The optical resource allocation for the PB cascade scene is changed from
dynamic allocation to fixed allocation.

1 Three-level PB cascade, PB configure two LTE cells for each level PB,
cells are not merged.
2 Reset the second level PB.
Pass Criterion:
After the second level PB is powered on, all six LTE cells terminals can
access and cells are all normal .
Note None
From Operator Hunan Telecom

6.4.139 20170902171018 The Number of Re-establishment Requests Due to

"Other Reason" on the FDD Sites is Increased Suddenly
Table 6-124 The Number of Re-establishment Requests Due to "Other Reason" on the
FDD Sites is Increased Suddenly
Issue Name The Number of Re-establishment Requests Due to "Other Reason" on

the FDD Sites is Increased Suddenly.
Failure Level B
Symptoms The number of re-establishment requests triggered by "other reason" on

the FDD sites is increased to 30000 times/day suddenly.
Impact There are more rejections in re-establishment triggered by "other reason".
Analysis There are abnormal terminals in the existing network (the UE capability
itself supports the FDD band, but the reported UE capability does not
support), resulting in deterioration of the reestablishment relevant
indicators.
Solution The eNodeB conforms to the protocol and only performs specail process
to the abnormal terminal, that is the eNodeB considers the UE capability
supports the primary band of the accessed cell.

Select abnormal indicator sites, open the switch, observe the
re-establishment of relevant indicators.
Pass Criterion:
Indicators return to normal.
Note None
From Operator China Mobile of Zhejiang Jiaxing

6.4.140 20171211222411 Handover Preparation Failed when UE hands over from

Normal eNodeB to Sharing eNodeB
Table 6-125 Handover Preparation Failed when UE hands over from Normal eNodeB
to Sharing eNodeB
Issue Name Handover Preparation Failed when UE hands over from Normal
eNodeB to Sharing eNodeB.
Failure Level B
Symptoms Handover preparing is failed with other reason when UE hands over
from Normal eNodeB to Sharing eNodeB.
Impact The number of handover preparation failure increases rapidly and

the success rate of handover drops.
Analysis After receiving the ENB CONFIGURATION UPDATE from sharing

eNodeB, the Non-Sharing eNodeB stores the main PLMN of the
neighbouring cell error, resulting in the switching path failure and
the handover preparation failure.
Solution Obtain the primary PLMN of the neighboring cell directly instead of
Obtaining the primary PLMN of the neighboring eNodeB as the
primary PLMN of the neighboring cell.

1 Select the hybrid networ including the Non-Sharing eNodeB
(China Unicom) and Sharing eNodeB (Main Plmn is China Unicom).
2 Trigger the sharing eNB to send ENB CONFIGURATION, and the
first cell carried in the message is Telecom cell.
3 UE hands over to sharing eNB from Non-Sharing eNodeB.
Pass Criterion:
Handover is success.
Note None
From Operator China Telecom in Hainan

6.4.141 20171214043047 RRC Setup Success Rate Drops Sharply Because of

Number of E-RAB Release Due to Uu Interface Timeout increasing
Table 6-126 RRC setup success rate drops sharply because of Number of E-RAB
Release due to Uu interface Timeout increasing
Issue Name RRC setup success rate drops sharply because of Number of
E-RAB Release due to Uu interface Timeout increase.
Failure Level B
Symptoms RRC setup success rate drops sharply because of Number of

E-RAB Release due to Uu interface Timeout increases.
Impact RRC setup success rate drops.
Analysis When SRIO speed configured by the software is far bigger than the
interrupt response speed, the pointer updated may not take effect in
time, then when the software configures a new set of SRIO data
transmission, the old pointer will be used, which will lead to
resource list confusion and the BD resource exhausted.
Solution When eNodeB maintains BD resources, adds mandatory

synchronization to ensure the maintenance correct for resource list.

3CC CA scenarios, UEs access and do service.
Pass Criterion:
UE service is normal, RRC setup success rate becomes normal.
"C373210392: Number of E-RAB Release due to Uu interface
Timeout" is normal.
Note None
From Operator Italy WT

6.4.142 20171117091909 Records with a Cell ID of 65535 Exist in the Cell-level

Counters' Statistics
Table 6-127 Records with a Cell ID of 65535 Exist in the Cell-level Counters' Statistics
Issue Name Records with a Cell ID of 65535 Exist in the Cell-level Counters'
Statistics
Failure Level B
Symptoms There are records with a Cell ID of 65535 in the cell-level counters'
statistics on some sites.
Impact KPI statistics have invalid records.
Analysis During context release procedure triggered by cell deletion, If there

exists a message of rejection or buffer is rejected after receiving a
message such as E-RAB modification, establishment, release,
eNodeB will report the KPI with Cell ID of 65535.
Solution When a Cell ID of 65535 appears, the statistics are not reported.

Delete the cell, trigger the context release procedure.
Pass Criterion:
There is no record of Cell ID 65535 in cell-level counters' statistics.
Note None
From Operator Malay DIGI
6.4.143 20171211110050 After upgrade to V3.40.20.10P50, VOLTE call dropped

rate increases.
Table 6-128 After upgrade to V3.40.20.10P50, VOLTE call dropped rate increases.
Issue Name After upgrade to V3.40.20.10P50, VOLTE call dropped rate

increases.

614006203805

Issue Name After upgrade to V3.40.20.10P50, VOLTE call dropped rate

increases.
Failure Level B
Symptoms After upgrade to V3.40.20.10P50, VOLTE call dropped rate

increases 0.5%.
Impact VOLTE call dropped rate increases and "C373210258Number of

Additional QCI1 E-RAB Setup Failures due to Parameter Error"
increases.
Analysis Downlink retransmission In continuous DTX scenario, the

retransmission RB should be consistent with the new transmission
RB, a decision is made whether a retransmission RB contains a
special RBG.
When QCI1 is retransmitted, when it is judged whether the
retransmitted RB contains a special RBG, processing errors results
in failure of retransmission RB allocation. After the retransmission
scheduling fails, the downlink HARQ resources of the UE are not
released in time, resulting in exhaustion of the downlink HARQ
resources of the UE, so as to cause VoLTE calls drop.
Solution 1.Modify the judgment process of whether special RBG is used

when new transmission.
2.HARQ is released in time after the scheduling failure in a
continuous DTX scenario to prevent the HARQ resources
exhausted and VoLTE calls drop.

1 configure 10M bandwidth, disable 5 RBs at both ends of the band.
Do the downlink VoLTE QCI1 service.
2 Move the UE to the edge of the cell and trigger the downlink
retransmission.
Pass Criterion:
1 VOLTE call dropped rate is normal.
2 "C373210258 Number of Additional QCI1 E-RAB Setup Failures
due to Parameter Error" is normal.
Note None
From Operator Thailand True

6.4.144 20171209110551 After Upgrade to V4.16.10.20P50, An Abnormal FDD

Product Process Causes the Baseband Board to Reset
Table 6-129 After upgrade to V4.16.10.20P50, an abnormal FDD product process

causes the baseband board to reset
Issue Name After upgrade to V4.16.10.20P50, an abnormal FDD product

process causes the baseband board to reset.
Failure Level B
Bug Version NBV4.16.10.20P50
Symptoms After upgrade to V4.16.10.20P50, an abnormal FDD product

process causes the baseband board to reset.
Impact eNodeB resets frequently, affecting the UE services.
Analysis FDD CC16 + BPL0 configuration, In the cross-process scenario, the

measurement report is buffered after it is received. When buffering,
the eNodeB will have a one-byte error handling in the the specific
measurement report whose sixth byte is 0. When this measurement
report is processed again, it will cause the product process
abnormal.
Solution When the measurement report is buffered, modify the one-byte

error-handling in the specific measurement report to ensure correct
processing.

Construction measurement report is cached scenario. For example,
when a handover triggered measurement report is received and the
eNodeB is processing other flows, the measurement report will be
cached.
Pass Criterion:
FDD product process is normal and the eNodeB does not reset yet.
Note None
From Operator Namibia

6.4.145 20171204033111 The FTP Upload Rate is low Because of IPSec Packets Decrypting
Abnormal
Table 6-130 The FTP upload rate is low because of IPSec packets decrypting
abnormal.
Issue Name The FTP upload rate is low because of IPSec packets
decrypting abnormal.

614006200681
Failure Level C
Symptoms The eNodeB (CCE1 is used) is connected through IPSec, FTP

upload rate is only 5Mbps to 8Mbps, worse than non-IPSec
scenario with 40Mbps, and the uplink UE TCP window is slowly
expanded and dropped rapidly after the expansion of the window,
which causes uplink throughput.
Impact In IPSec networking scenario, the uplink throughput is low.
Analysis In IPSec networking, the uplink packets from the UE, after adding
the GTPU header and the IPSec header, will exceed the MTU 1500
byte. In this way, the encrypted packets sent by the eNodeB are
fragmented. However, the peer security gateway has performance
bottlenecks to process the packets that need to be reassembled
and then decrypted, and this may result in packet loss or out of
order and the uplink throughput is low.
Solution In IPSec networking, eNodeB enables the Jumbo frame function,

that is, the MTU size under IPSec can be configured according to
the OMC. And then increase the MTU size so as to ensure that the
encrypted packets sent by the uplink are not fragmented.

1 Connect the eNodeB to EPC through IPSec network and
configure the eNodeB MTU size to 1700 byte.
2 Do FTP upload test, check the FTP uplink throughput.
Pass Criterion:
FTP uplink throughput is the same as non-IPSec senario.
Note None

Issue Name The FTP upload rate is low because of IPSec packets
decrypting abnormal.
From Operator Belgium TELENET
6.4.146 20171205162142 Number of RRC Connection Users in Frequency 1.8G

and 2.6G is unevenly Distributed After the MR Inter-frequency Measurement is
Enabled
Table 6-131 Number of RRC Connection Users in Frequency 1.8G and 2.6G is
unevenly Distributed After the MR Inter-frequency Measurement is Enabled
Issue Name Number of RRC Connection Users in frequency 1.8G and 2.6G
is unevenly distributed After the MR inter-frequency
measurement is enabled.
Failure Level B
Bug Version V3.40.20.10.P60
Symptoms Number of RRC Connection Users in frequency 1.8G and 2.6G is

unevenly distributed After the MR inter-frequency measurement is
enabled.
1 The number of RRC connection users in frequency 1.8G
increases, and the PRB utilization increases. The number of RRC
access users in frequency 2.6G decreases and the PRB utilization
decreases.
2 In frequency 2.6G, the handover success rate rises, the uplink /
downlink IP throughput is improved and the uplink / downlink IP
delay is reduced.
In frequency 1.8G, the handover success rate deteriorates, the
uplink / downlink IP throughput decreases, and the uplink / downlink
IP time delay increases.
Impact Number of RRC Connection Users in frequency 1.8G and 2.6G is

unevenly distributed
Analysis When the MR inter-frequency measurement is sent, the frequency

offset of the measurement object is incorrectly set due to the
initialization error of the variable (Actually it is set to the wrong value
of LBInterFreqOfn instead of offsetFreq), resulting in the distribution

Issue Name Number of RRC Connection Users in frequency 1.8G and 2.6G
is unevenly distributed After the MR inter-frequency
measurement is enabled.
of the number of users in 1.8G and 2.6G frequency

Inhomogeneous.
Solution The variable is initialized when it is defined and make sure that the
initialization is correct.

1 Enable the inter-frequency period measurement, configure the
inter-frequency neighboring cell, and send MR measurement tasks.
Set the normal offsetFreq and LBInterFreqOfn to different values in
the measurement object.
2 After UE accessing, observe whether the frequency offset carried
in the inter-frequency measurement object delivered by the initial
measurement is offsetFreq.
Pass Criterion:
Number of RRC Connection Users in frequency 1.8G and 2.6G is
evenly distributed, and the indicators in frequency 1.8G and 2.6G
are normal.
Note None
From Operator Malaysia UM
6.4.147 20180125214144 Parts of pRRUs Have No power for 2.6G QCell Site
Table 6-132 Parts of pRRUs Have No power for 2.6G QCell Site
Issue Name Parts of pRRUs Have No power For 2.6G QCell Site.

614006274529
Failure Level B
Symptoms Part of pRRUs have no power for 2.6G QCell site, UEs can not
access suddenly.
Impact The UEs can not access.
Analysis If there is a problem such as the eNodeB has a high network port bit

Issue Name Parts of pRRUs Have No power For 2.6G QCell Site.
error rate connection to the pRRU, it will trigger frequent cells

deletion and frequently IQ configuration procedure. At the same
time due to the abnormal status of message configuring procedure,
the IQ configuration of the part pRRU is incorrect, resulting in some
pRRUs have no power.
Solution Modify message configuring procedure, make sure the procedure

status runs correctly.

Do cells deleting/setup frequently. For example, by
blocking/unblocking the baseband board 50 times (operation
interval is 1 minute).
Pass Criterion:
1 All the pRRUs have normal power.
2 UEs can access all the time.
Note None
6.4.148 20180111005819 One Cell (CellID = 6) of A Site Setup Failure after

Upgrading
Table 6-133 One Cell (CellID = 6) of A Site Setup Failure After Upgrading
Issue Name One Cell (CellID = 6) of A Site Setup Failure After Upgrading.
Failure Level B

V4.16.10.20P61
Symptoms After upgrading from version V4.16.10.20P20 to version

V4.16.10.20P61, some cell of the site set up failure.
Impact UE cannot access to the failure cell.
Analysis The write access to the task PID routing table does not have the
mutual exclusion mechanism, when multiple tasks write the routing
table content at the same time, task PID routing table information is
chaos-written and some information will never be queried, and this

Issue Name One Cell (CellID = 6) of A Site Setup Failure After Upgrading.
causes the problem to happen.
Solution The write access to the task PID routing table write use the
semaphore to achieve mutually exclusive access.

The eNodeB upgrades from version V4.16.10.20P20 to version
V4.16.10.20P61
Pass Criterion:
All the cells setup success and UE accesses normally.
Note None
From Operator Linkem project in Milan
6.4.149 20180205143606 The AISG Inventory Information Reported by the

eNodeB is Inaccurate
Table 6-134 The AISG inventory information reported by the eNodeB is inaccurate
Issue Name The AISG inventory information reported by the eNodeB is

inaccurate, resulting in the inaccurate northbound inventory
information.
Failure Level C
Symptoms The AISG inventory information reported by the eNodeB is

information.
Impact Only affect the AISG inventory information.
Analysis To improve the AISG inventory query time, the eNodeB adopts the
following scheme: The AISG is collected when the RRU is powered
on and saved to the RRU locally. RRU directly reports the saved
value when querying by NMS.
However, the scenario fails to take into account the query failure
during power on. Therefore, if the query fails during power on, it will
cause the inaccurate northbound inventory information.

Issue Name The AISG inventory information reported by the eNodeB is

information.
Solution Optimize RRU AISG collection scheme: Every night from 23:00 to
23:16, RRU periodically queries AISG devices that have not
obtained the device type, updates the acquired information locally,
and when NMS queries the information, RRU reports the latest local
data.

View northbound inventory information, determine if AISG inventory
is accurate.
Pass Criterion:
The Northbound AISG inventory information is accurate.
Note None
From Operator Italy WT
6.4.150 20180129141023 The Call Drop Rate is Deteriorated
Table 6-135 the call drop rate is deteriorated
Issue Name The call drop rate is deteriorated.
Failure Level B
Symptoms When the load balancing based on the number of RRC users
feature is enabled, the number of dropped calls due to "other
reason in the ENB" increases, and the call drop rate is
deteriorated.
Impact The number of dropped calls due to "other reason in the ENB"
increases, and the call drop rate is deteriorating.
Analysis When the load balancing based on the number of RRC users
feature is enabled, the handover type parameter is set error,

this causes that the process is abnormal and the eNodeB

releases the UE.
Solution Ensure the handover type parameter is set to the right value.

1 Enable load balancing based on the number of RRC users
feature, configure measurement based.
2 Observe the call drop rate.
Pass Criterion:
The call drop rate is normal.
Note None
From Operator Tianjin Unicom
6.4.151 20180327161502 E-RAB Drop Rate is Increased
Table 6-136 E-RAB drop rate is increased
Issue Name E-RAB drop rate is increased.
Failure Level C
Symptoms Scanning of the long link list causes CPU load becomes higher
and the E-RAB call drop rate is increased.
Impact The E-RAB call drop rate is increased.
Analysis Because the link list is too long to be deleted, every message is
scanned once causes the CPU load becomes higher and the
E-RAB call drop rate is increased.
Solution Make all the link list operation is correct.


1 Observe the CPU load of Core 0
Pass Criteria:
1 The CPU load of Core 0 is normal,
2 There is no timeout in user plane configuration procedure.
Note None
From Operator Indonesia
6.4.152 20180309111551 After One XGW on The Network Goes Offline, some
BS8922 Have Alarms: S1 GTP-U path unavailable (198094466)
Table 6-137 After one XGW on the network goes offline, some BS8922 have alarms:
S1 GTP-U path unavailable (198094466)
Issue Name After one XGW on the network goes offline, some BS8922 have
alarms: S1 GTP-U path unavailable (198094466).
Failure Level B
Symptoms Some BS8922 have alarms: S1 GTP-U path unavailable

(198094466).
Impact Some BS8922 have alarms: S1 GTP-U path unavailable

(198094466).
Analysis Function 1 first applies for a timer T1, when T1 times out, kills
timer T1, puts timer T1 back in the Free list, but does not set the
handle to the timer to null, causing the timer T1 will be released
again when function 1 to apply for a timer again . Therefore, the
timer T1 is assigned to the GTPU path aging function and
function 1, and the function is abnormal, causing the alarms.

Solution Check all timers to ensure that:

1 Timer handle is initialized.
2 When Killing the timer, eNodeB sets the handle to the timer to
null.
3 When timer is timeout for One-time timers, eNodeB sets the
handle to the timer to null.

1 UE attach to BS8922.
2 Configure two IPv6 transmission links on the EMS. Link 1 is
used for IPv6 FTP services by default, and services are normal.
3 Delete the static route of link 1, and the EMS reports the S1
GTP-U path unavailable alarm.
4 Select link 2 to resume IPv6 FTP traffic and wait for the aging
of the path (six hours).
Pass Criterion:
Six hours later, S1 GTP-U path unavailable alarm is recovery.
Note None
From Operator Malay DIGI
6.4.153 20180326153047 The Success Rate of RRC Connection Setup Is

Decreased
Table 6-138 the success rate of RRC Connection Setup is decreased
Issue Name The success rate of RRC Connection Setup is decreased.
Failure Level C

V4.15.10.30P51
Symptoms When the eNodeB CPU load is high, the success rate of RRC
Connection Setup is decreased.

Impact The success rate of RRC connection setup is decreased.
Analysis When the CPU load is high, a large number of attach process
may be fail. And then, an MAP resource is not released in time
due to eNodeB processing error.
When the RRC setup procedure other than the last
retransmission fails, it is also counted in the RRC connection
setup success rate, this cause the success rate of RRC
connection setup is decreases.
Usually, only the last retransmission result of the RRC setup
procedure needs to be counted in the RRC connection setup
success rate.
Solution In any scenario, after the RRC connection setup is completed or

the setup fails, the eNodeB deletes the records in the MAP that
records the retransmission RRC connection setup request and
releases the resources in time.

Make multiple UEs access at the cell edge frequently, triggering
a large number of retransmission of RRC connection setup
during the access process.
Pass Criteria:
The success rate of RRC Connection Setup is normal all the
time.
Note None
7 Left-Behind Defects
Null

8 Version Restrictions and Things to be

Noticed
8.1 Macro-NodeB Version Restrictions
8.1.1 Version Package Download Restriction
Table 8-1 Version package download restriction
Item Version package download restriction

Restrictions 1. Download in incremental mode; if the downloaded version has the same
version number as the running version, you need to reset the NodeB
manually.
2. If main control board configuration is inconsistent, you are not allowed to
download specification package.
Reason 1. The current running version has the same version number, so that NodeB
auto-reset function is not executed.
2. As hybrid GU required, you are not allowed to download specification
package if main control board configuration is inconsistent.
Scenario 1. After successful download operation, NodeB doesn’t run the latest
specification package
2. CC16 and CC0 are mixed, which causes inconsistent configuration of main
control board.
Onsite Version package fails to be downloaded.
influence
Elusion 1. Manually reset NodeB.
measure 2. Avoid inconsistent master/slave configuration with real board.
Mode GU
8.1.2 Restriction on Version Package Pre-Activation, Taking Effect After

Activation Operation
Table 8-2 Restriction on version package pre-activation, taking effect after activation
operation

Item Restriction on version package pre-activation, taking effect after activation

operation
Restrictions 1. Inter-platform version upgrade requires operation on both platform and
product versions.
2. Version package activation must be associated to configuration data.
3. Pre-activation BBU platform and product version packages shouldn’t be done
separately (After pre-activating a BBU specification package, you are not
allowed to pre-activating another BBU specification package without letting
the previous one to be taken into effect)
Reason 1. Platform and product versions have compatibility problem
2. It is required by users to reduce wrong operation.
3. Pre-activation carries configuration data.
Scenario 1. Only upgrade product version
2. Pre-activate BBU package, not select configuration data
3. Not select both version package & pre-activation
Onsite Product process may run improperly.
influence
Elusion If both platform and product version packages need upgrading, Select
measure simultaneous upgrade operation (pre-activation, taking effect after activation)
Mode GU
8.1.3 Activation Effective, Activation Cancellation Operations Aiming at all

Version Packages
Table 8-3 Activation effective, activation cancellation operations aiming at all version
packages
Item Activation effective, activation cancellation operations aiming at all version

packages
Restrictions Activation effective, activation cancellation operations aiming at all version
packages
Reason Shorten upgrading time, reduce complexity
Scenario Select a version package to perform taking effect after activation, cancel activation
operations
Onsite Select a version package to perform taking effect after activation or cancel
influence activation operations; later all activated version packages are taken into effect or
become slave version package state.
Elusion No
measure
Mode GU

8.1.4 Version Package Deletion Restriction
Table 8-4 Version package deletion restriction
Item Version package deletion restriction

Restrictions Except for activated version package, running BBU version package, running RRU
version package, other versions can be deleted.
Reason VMP frame has such requirement
Scenario Delete hot patch package
Onsite Hot patch becomes invalid
influence
Elusion No
measure
Mode GU
8.1.5 To Configure Ultra Cell UL Enhancement Cell, AI_TIMING of All Cells

Must be 1 and Cell Radius Must Be ≤10KM
Table 8-5 To configure Ultra Cell UL Enhancement cell, AI_TIMING of all cells must be
1 and cell radius must be ≤10KM
Item To configure Ultra Cell UL Enhancement cell, AI_TIMING of all cells must
be 1 and cell radius must be ≤10KM
Restrictions To configure Ultra Cell UL Enhancement cell on BPK board, AI_TIMING of
all cells controlled by this BPK must be 1 and cell radius must be ≤10KM
Reason Hardware process has such restriction
Scenario Use Ultra Cell UL Enhancement cell, and Ultra-cell Dl Power & HSDPA
Code Multiplexing Functions at the same time.
Onsite If disobeying this restriction, PRACH common transmission setup may fail,
influence AITIMING configuration may be wrong.
Elusion If there is Ultra Cell UL Enhancement cell, AI_TIMING of all cells
measure controlled by the BPK must be 1 and cell radius must be ≤10KM
Mode UMTS
8.1.6 Super-far Cell Restriction
Table 8-6 Super-far cell restriction

Item Super-far cell restriction

Restrictions Super-far cell (cell radius ≥ 80km) only supports AI_Timing=1; 240km cell
only supports one, AI_Timing=1, and PRACH sub-channel half staggered,
e.g. [0 2 4 6 8 10] or [1 3 5 7 9 11]
Reason Hardware process has such restriction
Scenario Super-far cell
Onsite If disobeying this restriction, PRACH common transmission setup may fail,
influence searching window resource may be sufficient, and software process time
may be sufficient.
Elusion 1. Super-far cell AITIMNG=1; 2. 240km cell, PRACH sub-channel half
measure staggered
Mode UMTS
8.1.7 If Ultra Cell UL Enhancement and Ultra-cell Dl Power & HSDPA Code
Multiplexing Functions Change, All BPK Boards Will Reset
Table 8-7 If ultra cell UL enhancement and ultra-cell Dl Power & HSDPA code
multiplexing functions change, all BPK boards will reset
Item If ultra cell UL enhancement and ultra-cell Dl Power & HSDPA code
Restrictions If ultra cell UL enhancement and ultra-cell Dl Power & HSDPA code

Reason High layer, FPGA IQ allocation and baseband don’t support dynamic change, so
they require reset and initialization.
Scenario If ultra cell UL enhancement and ultra-cell Dl Power & HSDPA code
multiplexing functions change, all BPK boards will reset.
Onsite After the change of the above two functions, all BPK boards in a NodeB
influence will reset. Services will be interrupted.
Elusion
No
measure
Mode UMTS
8.1.8 CS Over HSPA Function
Table 8-8 CS Over HSPA function

Item CS Over HSPA function

Restrictions To use the CS Over HSPA function, you must configure DiscardTimer 100ms and
GBR 38800 bps in HLR server; otherwise, it is not VOIP service.
Reason To activate the CS Over HSPA function, you must configure DiscardTimer
100ms and GBR 38800 bps in HLR server; otherwise, it is not VOIP
service.
Scenario No
Onsite
No
influence
Elusion
No
measure
Mode UMTS
8.1.9 In Hybrid GU configuration, there is an STSR cell that is built with RSU82
GUL9016, RSU82 GUL1816 and other RRU, which is connected to BBU with a
super-long optical fiber. Supposed that the distance from RSU82 to BBU is L1,
the distance from the RRU to BBU is L2. A Restriction is that L2 shouldn’t be
longer than L1 for more than 25Km
Table 8-9 In Hybrid GU configuration, there is an STSR cell that is built with RSU82
super-long optical fiber. Supposed that the distance from RSU82 to BBU is L1, the
distance from the RRU to BBU is L2. A Restriction is that L2 shouldn’t be longer than
L1 for more than 25Km
Item In Hybrid GU configuration, there is an STSR cell that is built with RSU82
distance from the RRU to BBU is L2. A Restriction is that L2 shouldn’t be longer
than L1 for more than 25Km.
Restrictions In Hybrid GU configuration, there is an STSR cell that is built with RSU82
distance from the RRU to BBU is L2. A Restriction is that L2 shouldn’t be longer
than L1 for more than 25Km
Reason RSU82 GUL9016 and RSU82 GUL1816 can provide limited FPGA hardware
resource, but GU hybrid configuration requires more resources, this means buffer
space is insufficient. For this reason, RSU82 GUL9016 and RSU82 GUL1816 are
unable to buffer IQ data with more than 25Km long-distance delay.

Scenario 1. RSU82 GUL9016, RSU82 GUL1816

2. GU hybrid configuration
3. Build an STSR cell with RSU82 and other type of RRU
4. Other type of RRU is connected with a super-long optical fiber
5. The super-long optical fiber is longer than the optical fiber, connected to
RSU82, for more than 25Km.
Onsite
No.
influence
Elusion
No.
measure
Mode UMTS
8.1.10 1T RRU (R8881) Optical Rate Restriction
Table 8-10 1T RRU (R8881) optical rate restriction
Item 1T RRU (R8881) optical rate restriction

Restrictions 1T RRU (R8881) optical rate is configured to be 1.25G
Reason 1T RRU (R8881) software allows two kinds of optical port configuration: 1.25G
and 2.5G. But the delivered 1T RRU supports 1.25G optical rate in default. If you
configure 2.5G optical rate, it cannot work properly. Thus the Field environment
requires the restriction of 1.25G optical rate.
Scenario All scenarios
Onsite Configure optical rate according to requirement
influence
Elusion If 2.5G optical rate is specially required, configure the corresponding optical
measure module before it is delivered.
Mode GU
8.1.11 1T RRU (R8881, RSU60E, RSU40) Only Supports 22V High Class of AISG
and NSBT
Table 8-11 1T RRU (R8881, RSU60E, RSU40) only supports 22V high class of AISG
and NSBT
Item 1T RRU (R8881, RSU60E, RSU40) only supports 22V high class of AISG and
NSBT
Restrictions 1T RRU (R8881, RSU60E, RSU40) only supports 22V high class of AISG and
NSBT, not supporting 14V low class. When other devices work together with 1T

RRU, do not select 14V low class devices.

Reason AISG and NSBT of 1T RRU (R8881, RSU60E, RSU40) only support 22V output
voltage, not supporting 14V low class. If an external device only allows 14V and
the background configuration is also 14V, the AISG or NSBT doesn’t output
voltage. As a result, the external device cannot work properly. Thus 14V
external device cannot be connected.
Scenario External device is connected to AISG or NSBT port of 1T RRU
Onsite Type of external device is restrained.
influence
Elusion If macro base station has such requirement, take other measures to avoid this
measure restriction. NSBT has no avoidance measure.
Mode GU
8.1.12 HSSCCH Code Restriction
Table 8-12 HSSCCH code restriction
Item HSSCCH code restriction

Restrictions Add a restriction so that at most 4 HSSCCH codes can be configured in a cell
(because at most 4 HSDPA UEs can be supported in cell in 2ms TTI, it is
enough to configure 4 HSSCCH codes in a cell. If more than 4 HSSCCH codes
are configured, the code resources will be wasted.)
Reason If configuring more than 4 HSSCCH codes, system controlled codes will be
wasted.
Scenario HSPA service
Onsite Waste codes, downlink HSDPA rate will reduce
influence
Elusion Change parameter configuration in network management system
measure
Mode UMTS
8.1.13 Ultra-cell Dl Power & HSDPA Code Multiplexing Function Restriction
Table 8-13 Ultra-cell Dl Power & HSDPA Code Multiplexing function restriction
Item Ultra-cell Dl Power & HSDPA Code Multiplexing function restriction

Restrictions Ultra-cell Dl Power & HSDPA Code Multiplexing dispatching switch is on,
power-sharing function cannot be supported.
Ultra-cell Dl Power & HSDPA Code Multiplexing dispatching switch is on,
OCNS test mode 5 and 6 function is not supported.

Reason Not support it for the moment

Scenario Use Ultra-cell Dl Power & HSDPA Code Multiplexing
Onsite Note support such scenario
influence
Elusion Change parameter configuration in network management system
measure
Mode UMTS
8.1.14 Restriction on RRU if it is Connected to BS8912 U2100
Table 8-14 Restriction on RRU if it is Connected to BS8912 U2100
Item Restriction on RRU if it is connected to BS8912 U2100

Restrictions If BS8912 U2100 is connected to external RRU, currently only R8840 or R8881
is supported. The optical port rate is fixed at 1.2288G.
Reason BS8912 software only supports such rate at Ir port.
Scenario BS8912 is connected to external RRU
Onsite
Disobeying this restriction may cause RRU link interruption
influence
Elusion
Configure optical port rate to be 1.2288G
measure
Mode UMTS
8.1.15 Configure One Detection Mode for Static Route Table
Table 8-15 Configure One Detection Mode for Static Route Table
Item Data configuration restriction is incorrect. Static route table only allows one kind
of detection mode. If several detection modes are configured, database table
conversion must be wrong, causing transmission impassable.
Restrictions Static route table allows only one kind of detection mode to maintain the status of
route table: BFD, ICMP or ARP. If several modes are configured, for example,
BFD and ICMP, database table conversion must be wrong, causing transmission
impassable.
Reason Data configuration restriction is incorrect. Improper configuration mode is
allowed.
Scenario In the scenario of static multiple routes, several detection modes are wrongly
configured.
Onsite
Disobeying this restriction may cause transmission impassable.
influence

Elusion In the scenario of static multiple routes, configure only one kinds of detection
measure mode to maintain static route. BFD detection is recommended. Currently the
scenario of static multiple routes is rare, it is often protected by transmission
device itself.
Mode GU
8.1.16 Restriction on the Number of Remote Racks
Table 8-16 Restriction on the Number of Remote Racks
Item Remote rack configuration

Restrictions The number of remote racks should not exceed 37; otherwise, configuration
must fail.
Reason Software code has such restriction.
Scenario More than 37 remote racks are configured.
Onsite
Disobeying this restriction will cause configuration failure
influence
Elusion
Reduce the number of configured remote racks
measure
Mode GU
8.1.17 FS5 Configuration Requirement at Background
Table 8-17 FS5 Configuration Requirement at Background
Item FS5 configuration requirement at background

Restrictions Configure correct type of FS5, including logical board and physical board, at
background
Reason In the situation of hybrid insertion of FS3 and FS, NodeB performs TDM rate
conversion according to the configured type of physical board. In default, it
deems the board type to be FS0 and FS3.
Scenario NodeB uses FS5
Onsite If FS5 board is used, correct configuration must be ensured at background.
influence
Elusion Correct it if wrong configuration is found.
measure
Mode GU

8.1.18 Bearer Pre-Configuration Function Only Supports IP Transmission, It

Neither Supports ATM+IP Dual-stack nor ATM Transmission
Table 8-18 Bearer Pre-configuration function only supports IP transmission, it neither

supports ATM+IP dual stack nor ATM transmission
Item Bearer Pre-configuration function only supports IP transmission, it

neither supports ATM+IP dual stack nor ATM transmission
Restrictions Currently, RNC and NodeB versions do not support bearer pre-configuration
function in ATM transmission.
Reason Currently, bearer pre-configuration function is not supported in ATM+IP dual-stack
and ATM transmission according to RNC’s and NodeB’s planning scheme.
Scenario 1. ATM transmission
2. ATM+IP dual-stack transmission
Onsite If ATM or ATM+IP transmission is configured, do not activate this bearer
influence pre-configuration function.
Elusion
Do not activate this bearer pre-configuration function.
measure
Radio mode UMTS
8.1.19 Restriction on Hybrid Scenario While Upgrading CCA to CCC
Table 8-19 Restriction on hybrid scenario while upgrading CCA to CCC
Item Restriction on hybrid scenario while upgrading CCA to CCC

Restrictions In hybrid scenario, elusion measure should be obeyed strictly.
Reason In hybrid scenario, data synchronization must be done. If upgrading steps are
wrong, data synchronization may not be carried out correctly.
Scenario CCA environment is constructed into CCC. In hybrid scenario, you must follow the
steps.
Onsite During upgrading process from CCA to CCC, wrong steps may slow down
influence upgrading progress, even causing upgrade failure.
Elusion 1. Configure CC16 at OMMB and initiate data synchronization.
measure 2. Download version package (platform and product)
3. Insert CC16.
Radio mode UMTS

8.1.20 CC0/CC2 not Support IPV6 Due to its Chip Limit
Table 8-20 CC0/CC2 not support IPV6 due to its chip limit
Item CC0/CC2 not support IPV6 due to its chip limit

Restrictions If CC0 or CC2 is configured in ZXSDR B8200 GU360, the system does not
support IPV6.
Reason Because CC0 and CC2 belong to 1st generation main control board, used in
ZXSDR B8200 GU360 system. CPU chip is MPC8360. The QE/IW of this chip
does not support IPV6.
Scenario 1. ZXSDR B8200 GU360 system
2. CC0 or CC2 is configured.
3. IPV6 is required
Onsite
Currently, there is no such field application.
influence
Elusion
Replace CC0 or CC2 board with CC16 or CC17.
measure
Radio mode GU
8.1.21 Restriction on BPK_d Configuration
Table 8-21 Restriction on BPK_d configuration
Item Restriction on BPK_d configuration

Restrictions 1. Automatically allocate baseband resource mode:
1) When FS adopts FS0/FS3 type, BPK_d can support up to 6 cells. There is no
such restriction for external FS3A/FS5.
2) When BPK_d is inserted to slot 5, BPK_d can support up to 6 cells regardless of
FS type.
2. Manually allocate baseband resource mode:
1) In above two configuration scenarios, BPK_d can support up to twelve 1T1R
cells or six 1T2R cells.
Reason 1. In auto-allocation baseband resource mode, when FS adopts FS0/FS3 type,
backplane board has a limit so that BPK_d can only provide 12 IQ channels.
2. In auto-allocation baseband resource mode, when BPK_d is inserted to slot 5,
BPK_d can only provide 12 IQ channels regardless FS type.
3. In manual-allocation baseband resource mode, BPK_d can only provide 12 IQ
channels in the above scenarios.
Scenario 1. FS adopts FS0/FS3 (regardless of which slot where BPK_d is inserted)
2. BPK_d is inserted to slot 5

Onsite
Because of the above restriction, BPK_d cannot support 12 cells.
influence
Elusion
No
measure
Radio mode UMTS
8.1.22 Maximum 4 Levels of Cascading Connection of 1T RRU (R8881, RSU60E,

R8861) and Old 1T RRU (RTR, RTR2, DTR, ADTR)
Table 8-22 Maximum 4 levels of cascading connection of 1T(R8881, RSU60E, R8861)

and old 1T RRU (RTR, RTR2, DTR, ADTR)
Item Maximum 4 levels of cascading connection of 1T RRU (R8881, RSU60E, R8861)

Restrictions Maximum 4 levels of cascading connection of 1T RRU (R8881, RSU60E, R8861)
Reason 1T RRU (R8881, R8861) can support 6 levels of cascading connection. But old
1T only allows 4 levels of cascading connection. Thus in hybrid connection,
maximum 4 levels of cascading connection can be supported.
Scenario Cascading connection scenario
Onsite Cascading connection restriction
influence
Elusion No
measure
8.1.23 Things to be Noticed When RSU82 GUL1816 Uses Cross Diversity and
Primary & Diversity Detection
Table 8-23 Things to be noticed when RSU82 GUL1816 uses cross diversity and primary
& diversity detection
Item Things to be noticed when RSU82 GUL1816 uses cross diversity and
primary & diversity detection
Restrictions RSU82 GUL1816 is configured to be cross diversity, channel 1 is not
configured with a carrier. In this situation, if detection switches of primary
and secondary channels are on, primary & diversity reception unbalanced
alarm cannot be detected. Please pay attention to it.

Reason In cross diversity configuration, only one channel is used to collect RSSI
data as unbalanced alarm sample. Only channel 1 detection switch is on. If
there is no traffic over channel 1, but there is traffic over channel 2, invalid
RSSI will be collected. In this case, detection function doesn’t work.
Scenario In cross diversity configuration, only channel 1 detection switch is on. If there
is no traffic over channel 1, but there is traffic over channel 2, invalid RSSI
will be collected. In this case, unbalanced detection function doesn’t work.
Onsite influence Cross diversity switch is configured, channel 1 unbalanced detection switch
is on, there is no traffic over channel 1, but there is traffic over channel 2. In
such scenario, unbalanced detection function doesn’t work.
Elusion measure In cross diversity configuration, if only channel 2 is configured with a carrier,
set channel 2 unbalanced detection switch to be on.
8.1.24 Things to be noticed when RSU82 GUL1816 starts manual frequency

scanning function via OMMB
Table 8-24 Things to be noticed when RSU82 GUL1816 starts manual frequency
scanning function via OMMB
Item Things to be noticed when RSU82 GUL1816 starts manual frequency scanning
function via OMMB
Restrictions If RSU82 GUL1816 starts manual frequency scanning function via OMMB, you must
manually reset RSU82 after the scanning operation.
Reason After RSU82 GUL1816 starts manual frequency scanning function via OMMB, the
system has a defect -- it wrongly judges activating/deactivating PA tag.
Consequently, after RRU power is re-calibrated, PA cannot be enabled any more.
Scenario RSU82 GUL1816 starts manual frequency scanning function via OMMB
Onsite influence After RSU82 GUL1816 starts manual frequency scanning function via OMMB, RRU
power re-calibration causes PA to be disabled. As a result, services over this channel
are interrupted.
Elusion measure If you start manual frequency scanning function via OMMB, you must manually reset
RSU82 after the scanning operation.

8.1.25 In the situation that new 1T RU runs frequency scanning function and
PA is enabled, Tx frequency is not the configured one. This may bring
interference to non-configured frequency point.
Table 8-25 In the situation that new 1T RU runs frequency scanning function and PA is
enabled, Tx frequency is not configured one. This may bring interference to
non-configured frequency point.
Item In the situation that new 1T RU runs frequency scanning function and PA is enabled,
Tx frequency is not configured one. This may bring interference to non-configured
frequency point.
Restrictions In the situation that new 1T RU runs frequency scanning function and PA is enabled,
Tx frequency is not configured one. This may bring interference to non-configured
frequency point.
Reason In the situation that new 1T RU runs frequency scanning function and PA is enabled,
Tx frequency is not configured one. The problem is that RU scans frequency over the
whole bandwidth with a certain step size. This may bring interference to
non-configured frequency point.
Scenario RU runs frequency scanning function
Onsite influence This may bring interference to non-configured frequency point for a short time.
Elusion measure No
8.1.26 During the process that new 1T RU runs frequency scanning function,
manually activating/deactivating PA operation should be avoided unless there
is a special reason
Table 8-26 During the process that new 1T RU runs frequency scanning function,
manually activating/deactivating PA operation should be avoided unless there is a
special reason.
Item During the process that new 1T RU runs frequency scanning function, manually
reason.
Restrictions During the process that new 1T RU runs frequency scanning function, manually
reason.
Reason During the process that new 1T RU runs frequency scanning function, RU can still
give response to OMMB about manually activating/deactivating PA operation. If there
is no special reason, please do not perform activating/deactivating PA operation

because it may affect frequency scanning result. Otherwise, the scanned result may
be different from real situation. If this operation must be done for a special reason,
please re-start frequency scanning function after the operation. The purpose is to
ensure correct scanning result.
Scenario RU runs frequency scanning function
Onsite influence RU frequency scanning function and manually activating/deactivating PA
Elusion measure If there is no special reason, please do not perform activating/deactivating PA
operation because it may affect frequency scanning result. Otherwise, the scanned
result may be different from real situation. If this operation must be done for a special
reason, please re-start frequency scanning function after the operation. The purpose
is to ensure correct scanning result.
8.1.27 Number of Cells, Number of Carriers Supported by CC0/CC2
Table 8-27 Number of cells and number of carriers supported by CC0/CC2
Item Number of cells and number of carriers supported by CC0/CC2

Restrictions Currently, CC0/CC2 only supports 54 cells (original 108), 120 carriers (original
216)
Reason CC0/CC2 uses less memory
Scenario Use CC0/CC2
Onsite When using CC0/CC2, GSM can be configured to support up to 54 cells
influence and 120 carriers.
Elusion
Be careful to configure this item
measure
8.1.28 Restriction on Cell Entire Frequency Band Scanning Function
Table 8-28 Restriction on cell entire frequency band scanning function
Item Restriction on cell entire frequency band scanning function

Restrictions 1. RU should be configured to be single GSM mode
2. The cell associated RRU should support the function to report duplexer
working range to GSM; otherwise cell entire frequency band scanning
function cannot be used properly.
Reason RU should support it
Scenario Use this function

Onsite If RU should support the function to report duplexer working range to

influence GSM; otherwise the scanned result may be wrong.
Elusion
No
measure
8.1.29 Restriction on Air-interface Soft Synchronization Function
Table 8-29 Restriction on air-interface soft synchronization function
Item Restriction on air-interface soft synchronization function

Restrictions 1. When this function is activated, partial handsets may have drop call
problem.
2. Please select small traffic period to start clock adjustment.
3. RU type is DTR,R8882, OP adjustment period is recommended to be
30s.
4. Do not start periodical adjustment.
Reason System scheme restriction
Scenario This function is used
Onsite influence Drop call problem may occur.
Elusion measure Be alert to use it.
8.1.30 Things to be Noticed in UBPG3 Configuration
Table 8-30 Things to be noticed in UBPG3 configuration
Item Things to be noticed in UBPG3 configuration

Restrictions 1. When FS0 board is configured in a NodeB site and this site doesn’t
only support GSM, UBPG3 can only support 12 carriers.
2. In a situation that FS0 board is configured in a NodeB site and this
site only supports GSM, if FS0 functional mode is set to be GSM 36
carriers, UBPG3 can support 24 carriers; if FS0 functional mode is set
to be others, UBPG3 can support 12 carriers.
3. When FS0 board is not configured in a NodeB site, UBPG3 can
support 24 carriers.
Reason FS0 default version can only support 12-carrier IQ exchange of UBPG3. If
it is configured in a site that only supports GSM, FS0 can be set to be
GSM 36 carriers. In this configuration, it can support 24-carrier IQ
exchange of UBPG3.

Scenario UBPG3 is used

Onsite influence When FS0 board is configured in a site, UBPG3 is able to support 12
carriers in the above mentioned situation.
Elusion measure In a situation that UBPG3 and FS0 are configured in a NodeB site and this
site doesn’t only support GSM, if you expect UBPG3 to support more than
12 carriers, please replace the FS0 board with FS3 or FS5.
8.1.31 Restriction on Smart Power-on/off Function
Table 8-31 Restriction on smart power-on/off function
Item Restriction on smart power-on/off function

Restrictions BSC V3 does not support smart power-on/off function if more than 24 cells
are configured
Reason Not support
Scenario BSC adopts V3 and more than 24 cells are configured in a site.
Onsite influence Not support
Elusion measure Upgrade BSC version or configure 23 cells or less in a site.
8.1.32 Restriction on GU Power-sharing Function
Table 8-32 Restriction on GU power-sharing function
Item Restriction on GU power-sharing function

Restrictions 1. Because it is impossible to obtain U configuration power, the maximum
available power for GSM is the sum of GSM configuration power + U
offered power. However, the power, not contained in GU configuration
power, i.e. residual power, cannot be allocated.
2. If a baseband process board is configured with hopping frequency, GU
power-sharing function is not supported.
3. In multi-carrier jointing configuration, GU power-sharing function is not
supported.
4. If carriers on PA are borne on different baseband process boards, GU
power-sharing function is not supported.
Reason Not support
Scenario 1. Some power, called residual power, is not configured by GU
2. Baseband hopping frequency configuration
3. Multi-carrier jointing configuration

4. Carriers on PA borne on different baseband process boards

Elusion measure No
8.1.33 Restriction on DBB Hotpatch Loading
Table 8-33 Restriction on DBB hotpatch loading
Item Restriction on DBB hotpatch loading

Restrictions If DBB hotpatch has been loaded, first view hotpatch running version
information in OMMB, then delete it. Note that the DBB hotpatch must be
offloaded and deleted. After that, load new hotpatch. If you do not follow
the operation steps, a hotpatch loading failure alarm will be given. In this
case, you need to download the hotpatch again.
Reason It is so designed
Scenario DBB hotpatch has been loaded.
Onsite influence A hotpatch loading failure alarm is given.
Elusion measure Follow the restriction description.
8.1.34 Restriction on Local Switch
Table 8-34 Restriction on local switch
Item Restriction on local switch

Restrictions 1. CC0/2 does not support inter-site local switch in the situation of BSC
V4.
2. While using CS/PS user plane multi-address function in E1
transmission, inter-site local exchange is not supported.
3. Local switch does not support UDP compression function.
4. In E1FE hybrid network, local switch is not supported within BTS
cluster.
5. Local switch does not support E1 ByPass.
6. Local switch does not support IPV6 related requirement for the
moment.
7. One local switch group include 100 carriers at most.
8. CC0/BS8908 doesn’t support inter-site local switch with
iBSC6.30/6.50 version.
Reason Not support for the moment
Scenario Configuration scenario in restriction description


Elusion measure No
8.1.35 Restriction on BCCH Changeover Function
Table 8-35 Restriction on BCCH changeover function
Item Restriction on BCCH changeover function

Restrictions 1. If RRU is configured in GU/GL hybrid mode, this function is not
supported.
2. Boundary frequency of RRU bandwidth should not be involved in
changeover.
3. In multi-carrier jointing configuration, BCCH changeover is not
supported.
Reason It is so designed.
Scenario 1. RRU in GU/GL hybrid configuration
2. The frequency involved in changeover is boundary frequency of RRU
bandwidth.
3. Multi-carrier jointing configuration
Elusion measure No
8.1.36 Super NodeB not Support IPV6 (IPOE1 not Support IPV6)
Table 8-36 Super NodeB not support IPV6 (IPOE1 not support IPV6)
Item Super NodeB does not support IPV6 (IPOE1 does not support IPV6)
Restrictions Super NodeB does not support IPV6 (IPOE1 does not support IPV6)
Scenario IPV6
Elusion measure No
8.1.37 IPV6 OMCB Channel not Support IPV6 IN IPV6
Table 8-37 IPV6 OMCB channel not support IPV6 IN IPV6
Item IPV6 OMCB channel does not support IPV6 IN IPV6

Restrictions IPV6 OMCB channel only supports IPV4 IN IPV6, but does not support
IPV6 IN IPV6
Scenario IPV6 IN IPV6
Elusion measure No
8.1.38 Restriction on EVA Function
Table 8-38 Restriction on EVA function
Item Restriction on EVA function

Restrictions If activating EVA function, DBB load may be affected. There is additional
3% overhead. Currently, EVA function is only valid for FR/EFR/HR.
Scenario Not FR/EFR/HR configuration
Elusion measure Configure FR/EFR/HR
8.1.39 Restriction on GL Power Sharing
Table 8-39 Restriction on GL power sharing
Item Restriction on GL power sharing

Restrictions
1. RRU must be dual-PA configuration.
2. GSM carrier smart power-off function must be activated.
3. G shares its idle power with L, but L does not share its power with G.
Scenario RRU is in single PA configuration, or GSM carrier smart power-off function
is not activated.
Elusion measure Configure dual PAs for RRU, activate GSM carrier smart power-off
function
8.1.40 Restriction on UL Adaptive Filter
Table 8-40 Restriction on UL adaptive filter

Item Restriction on UL adaptive filter

Restrictions 1. Currently only ADTR supports UL adaptive filter function.
2. UL adaptive filter is enabled in the scenario that
same-/adjacent-frequency interference is serious in a cell. Activating this
function in all cells is not recommended.
3. If activating UL adaptive filter, UBPG DSP does not support 12-carrier
service, UBPG3 DSP does not support 24-carrier service. About 15%
load performance is reduced.
Scenario UL adaptive filter function is enabled
Onsite influence UBPG DSP load is affected
Elusion measure No
8.1.41 VAMOS (Voice services over Adaptive Multiuser channels on One Slot) Capability Limit
Table 8-41 VAMOS capability limit
Item VAMOS capability limit

Restrictions 1. Currently, FR+2HR work in pair. But there is a bug when 2 HRs have
different SCPIR (Subchannel Power Imbalance Ratio) requirements. It
needs to be solved.
2. Power-sharing is not supported.
3. Currently, BSC provides power allocation function and NodeB also
provides power allocation function. The system takes NodeB allocated
power as reference, but NodeB does not inform BSC about the allocated
power.
4. VAMOS has a problem in the situation of 1FR + 2HR. In this situation,
because of the restriction on total power and step size, 2 HRs do not have
the same power. Currently, only DL codes are developed. Later UL codes
must be developed too. Furthermore, other problems such as power rising
should be considered in later solution.
Scenario VAMOS function is activated in the configuration scenario as mentioned in
restriction description.
Elusion measure No

8.1.42 In the Configuration of Single-UMTS RUs, the Configured Antenna

Unbalanced Alarm Parameter (AntDetectorU) May be Invalid
Table 8-42 In the configuration of single-UMTS RUs, the configured antenna

unbalanced alarm parameter (AntDetectorU) may be invalid
Item In the configuration of single-UMTS RUs, the configured antenna unbalanced

alarm parameter (AntDetectorU) may be invalid.
Restrictions In the configuration of single-UMTS RUs, the configured antenna unbalanced
alarm parameter (AntDetectorU) may be invalid. But there is no such problem in
the configuration of single-GSM or hybrid-GU RUs.
Reason In the configuration of single-UMTS RUs, only the 1st channel can use the value
of this parameter configured at OMMB as a threshold, sometimes the other
channels cannot use it. Consequently, the other RU channels, except for the 1 st
channel, cannot detect and report primary/secondary channel unbalanced alarm
according to the configured threshold.
Scenario In the configuration of single-UMTS RUs, each RU channel has its default value
of AntDetectorU. If you change the antenna unbalanced alarm parameter with a
new threshold via OMMB for the 1st channel, but not for all the other channels, it
means some channels still use default AntDetectorU. Because of this defect,
some RU channels will use the default threshold to make detection. As a result,
the other channels, except for the 1st channel, cannot detect and report
primary/secondary channel unbalanced alarm according to the configured
threshold.
Onsite In the configuration of single-UMTS RUs, the other RU channels, except for the
influence 1st RU channel, cannot report primary/secondary channel unbalanced alarm
according to the configured threshold.
Elusion
measure
8.1.43 UBPG0 Does not Support NCC Extended Channel
Table 8-43 UBPG0 does not support NCC extended channel
Item UBPG0 does not support NCC extended channel

Restrictions 1. If only UBPG0 is configured in a site, deactivating NCC function is
suggested.
2. In a situation that NCC is enabled, if UBPG0 is configured, only UBPG0
normal channel can be used to coordinate with adjacent cells. The

UBPG0 does not support extended channel.

Reason It is so designed.
Scenario Enable NCC function
Onsite influence No
Elusion measure No
8.1.44 Cross Diversity is not Supported in R8882/RSU82 UL Hybrid Scenario
Table 8-44 Cross diversity is not supported in R8882/RSU82 UL hybrid scenario
Item Cross diversity is not supported in R8882/RSU82 UL hybrid scenario

Restrictions Cross diversity is not supported in R8882/RSU82 UL hybrid scenario. Do
not set cross diversity switch on in OMMB configuration.
Reason In the R8882/RSU82 UL hybrid scenario, FPGA only supports 2T2R. It is
effective to be used as general diversity configuration, not supporting
cross diversity.
Scenario In the R8882/RSU82 UL hybrid scenario, OMMB does not forbid a user to
set the cross diversity switch on. Once the cross diversity switch is on,
UMTS NodeB carrier becomes abnormal.
Onsite influence In V4.12, cross diversity switch is not used. If setting this switch on, there
is no any alarm. In V4.13 or above version, UMTS carrier has a RTWP
abnormal alarm when cross diversity switch is on in the R8882/RSU82
UL hybrid scenario.
Elusion measure Set R8882/RSU82 cross diversity switch to off.
8.1.45 Cell Deletion/Addition Due to the Change of Interference Cancellation

(IC) Switch
Table 8-45 Cell deletion/addition due to the change of IC switch
Item Cell deletion/addition due to the change of IC switch

Restrictions As IC switch changes, the service & board selection rule in the corresponding
cell also changes. The previous board does not meet IC condition. For this
reason, cell deletion/addition is required.
Reason IC affects board selection rule. Cell deletion/addition can guarantee that all
services can be borne on the board, which meets IC condition.
Scenario Configure IC scenario
Onsite
As IC switch changes, the corresponding cell may be deleted/added.
influence

Elusion
Null
measure
Radio mode UMTS
8.1.46 If Changing DC Relation via OMMB, the Corresponding Cell May be

Deleted/Added
Table 8-46 If changing DC relation via OMMB, the corresponding cell may be
deleted/added
Item If changing DC relation via OMMB, the corresponding cell may be deleted/added
Restrictions If changing DC relation of local cell via OMMB, the corresponding cell may be
deleted, then added.
Reason If cell is not deleted after changing DC relation, DC service may be affected.
Scenario Change DC relation of local cell via OMMB
Onsite
Cell is deleted and added
influence
Elusion
Do not change the DC relation of local cell
measure
Radio mode UMTS
8.1.47 Constraints When Both FS and BPN2 Provide Optical Ports in GSM System
Table 8-47 Constraints when both FS and BPN2 provide optical ports in GSM system
Item Constraints when both FS and BPN2 provide optical ports in GSM system
Restrictions 1) If carriers belong to the same baseband frequency hopping group, GSM does
not support the two situations: both FS and BPN2 provide optical ports, different
BPN2 boards provide optical ports.
2) If multiple carriers form a joint group and these carriers belong to several
RRUs, GSM does not support the two situations: both FS and BPN2 provide
optical ports, different BPN2 boards provide optical ports.
3) If two R8863s are involved in combined baseband cabinets, GSM does not
support the two situations: both FS and BPN2 provide optical ports, different
BPN2 boards provide optical ports.
Reason It is designed this way.
Scenario Both FS and BPN2 provide optical ports in GSM system.

Onsite
No
influence
Elusion
No
measure
Radio mode GSM
8.1.48 Constraints When CR0 is Inserted to Slot 4
Table 8-48 Constraints when CR0 is inserted to slot 4
Item Constraints when CR0 is inserted to slot 4

Restrictions When CR0 is inserted to slot 4, BP board cannot be automatically allocated to a
UMTS cell.
Reason It is designed this way.
Scenario CR0 is inserted at slot 4, NodeB supports UMTS mode.
Onsite A site supports UMTS mode. BP board cannot be automatically allocated to a
influence UMTS cell.
Elusion CR0 is inserted to slot 4. NodeB supports UMTS mode. Allocate BP board to a
measure UMTS cell manually. The UMTS cell is associated to one BP board.
Radio mode UMTS
8.1.49 The CC0/2 board can only support 72 GSM carriers
Table 8-49 The CC0/2 board can only support 72 carriers
Item The CC0/2 board can only support 72 carriers

Restrictions The CC0/2 board can only support 72 carriers
Reason The CC0/2 board has no enough memory space.
Scenario The CC board type is CC0/CC2.
Onsite
The site has more than 72 GSM carriers.
influence
Elusion
Change the CC board with CC16 boad or others.
measure
Radio mode GSM
8.1.50 Configuration restriction on access distance compensation
Table 8-49 Configuration restriction on access distance compensation

Item Configuration restrictions on access distance compensation

Restrictions Parameter configuration restrictions:
1) To activate access distance compensation feature in a site, all
cells in this site must obey these configuration rules: AITiming = 1,
UlocalCell.2msGain ≤ 200.
2) If there are more than 3 super-far cells (80km radius), set
UlocalCell.2msGain to 0 or null.
3) If there are 2 super-far cells (80Km radius),UlocalCell.2msGain
≤ 160.
4) To configure a 120km/240km super-far cell, set
UlocalCell.2msGain to 0 or null.
Do not activate this feature unless active devices in an antenna

system truly generate additional delay difference. Before activating
this feature, you must set the parameter to a suitable value. After
activating this feature, observe access delay relatedcounter. Make
sure the value is kept within a normal range.
Reason 1) Air-interface delay is restricted.

2) Cell edge should not be far from a site. The acceptable distance
(240Km) is declared in 3GPP specifications.
Scenario The application scenarios are described in restriction description

Onsite After activating this feature, cell coverage area is kept within a
influence normal range. UE can be accessed as long as it stays within the
range defined by UlocalCell.2msGain
Elusion
Always obey the above restrictions.
measure
Radio mode UMTS
8.2 Restrictions on QCELL Version
8.2.1 A Group of Cascaded PBs with 10G Optical Port Can Support Up to
UMTS UL/DL 20 IQ Channels

Table 8-49 A Group of Cascaded PBs with 10G Optical Port Can Support Up to UMTS
UL/DL 20 IQ Channels
Item A Group of Cascaded PBs with 10G Optical Port Can Support Up to UMTS
Restrictions A Group of Cascaded PBs with 10G Optical Port Can Support Up to UMTS
Reason 10G optical rate restriction
Scenario UMTS QCELL cell configuration
Onsite
In the case of more than 20 IQ channels, CC reports IQ over-threshold alarm.
influence
Elusion
Reduce cell configuration
measure
Radio mode UMTS
8.2.2 QCELL System Does not Support 6G Optical Port
Table 8-50 QCELL System Does not Support 6G Optical Port
Item QCELL System Does not Support 6G Optical Port

Restrictions QCELL System Does not Support 6G Optical Port
Reason It is not implemented in this version.
Scenario In QCELL system, optical port of FS is configured to be 6G rate.
Onsite
UMTS service becomes abnormal.
influence
Elusion
Change the configuration to be 10G rate
measure
Radio mode UL
8.2.3 The Bandwidth of UMTS Local Cell Supports 5M\4.8M\4.6M
Table 8-51 The Bandwidth of UMTS Local Cell Supports 5M\4.8M\4.6M
Item The Bandwidth of UMTS Local Cell Supports 5M\4.8M\4.6M

Restrictions The Bandwidth of UMTS Local Cell Supports 5M\4.8M\4.6M
Reason RRU does not support other bandwidth configuration
Scenario Select bandwidth when configuring a UMTS local cell.
Onsite UMTS service becomes abnormal.

influence
Elusion
Change bandwidth configuration.
measure
Radio mode UMTS
8.2.4 CC0\CC2 Does not Support QCELL Configuration Scenario
Table 8-52 CC0\CC2 Does not Support QCELL Configuration Scenario
Item CC0\CC2 Does not Support QCELL Configuration Scenario

Restrictions CC0\CC2 Does not Support QCELL Configuration Scenario
Reason It is not implemented in this version.
Scenario CC0/CC2 is configured in QCELL sites
Onsite
UMTS\LTE service becomes abnormal
influence
Elusion
Replace CC0\CC2
measure
Radio mode UL
8.2.5 In QCELL Networking Scenario, LTE Baseband Resource Should be

Configured to be PB Mode
Table 8-53 In QCELL Network scenario, LTE Baseband Resource Should be Configured
to be PB Mode
Item In QCELL Network scenario, LTE Baseband Resource Should be Configured to

be PB Mode
Restrictions In QCELL Network scenario, LTE Baseband Resource Should be Configured to
be PB Mode
Reason In QCELL networking scenario, delay compensation at baseband side of LTE
should rely on PB mode. The purpose of this configuration is to distinguish
macro-site scenario.
Scenario In QCELL networking scenario, configure LTE baseband resource in OMMB.
Select PB mode.
Onsite
In QCELL networking scenario, this configuration is related to LTE service.
influence
Elusion No

measure
8.2.6 Port 2 and 3 of PB1000 are Unavailable for the Moment, Not Supporting
Relevant Function
Table 8-54 Port 2 and 3 of PB1000 are Unavailable for the Moment, Not Supporting
Relevant Function
Item Port 2 and 3 of PB1000 are Unavailable for the Moment, Not Supporting
Relevant Function
Restrictions Port 2 and 3 of PB1000 are Unavailable for the Moment, Not Supporting
Relevant Function
Reason 4 optical ports are designed for PB1000 hardware to implement future expansion
requirement. Currently, only port 1 and 4 are used.
Scenario To connect PB1000 topology or configure PB1000 topology, only port 1 and 4
can be used. Port 1 and 4 are used for upward and downward connection,
respectively. Port 2 and 3 are not used.
Onsite
Do not use port 2 o 3 of PB1000. They do not support relevant function.
influence
Elusion
No
measure
8.2.7 The Range of PB Rack Number is 3-201; the Range of PRRU Rack
Number is 3-201. 214-251
Table 8-55 The Range of PB Rack Number is 3-201; the Range of PRRU Rack Number
is 3-201. 214-251
Item The Range of PB Rack Number is 3-201; the Range of PRRU Rack Number is
3-201. 214-251
Restrictions The Range of PB Rack Number is 3-201; the Range of PRRU Rack Number is
3-201. 214-251
Reason If rack number is 2, it conflicts with the range declared in 3GPP specifications.
Thus, rack number 2 should not be used. 202~213 are used by macro-sites to
auto-detect RRU, so they cannot be used, too. PB original version does not
support the configuration of above 201. Otherwise, the link connected to PB will
be disconnected and PB cannot be managed. Thus, PB rack number should be

configured to be above.
Scenario Configure available rack number for PB and PRRU.
Onsite
Configure available rack number for PB and PRRU.
influence
Elusion
No
measure
8.2.8 Support Up to 24 PBs, 192 PRRUs
Table 8-56 Support Up to 24 PBs, 192 PRRUs
Item Support Up to 24 PBs, 192 PRRUs

Restrictions Support Up to 24 PBs, 192 PRRUs
Reason System capacity has a limit so the numbers of PBs and PRRUs are constrained.
24 PBs are connected to 6 optical ports in 4-levels cascading connection.192
PRRUs are connected to electrical ports of 24 PBs. Each PB is configured with 8
electrical ports.
Scenario Configure acceptable PBs and PRRUs.
Onsite
Configure acceptable PBs and PRRUs.
influence
Elusion
No
measure
8.2.9 Previous PB Reset Will Affect the PRRU, Connected to Next PB
Table 8-57 Previous PB Reset Will Affect the PRRU, Connected to Next PB
Item Previous PB Reset Will Affect the PRRU, Connected to Next PB

Restrictions Previous PB Reset Will Affect the PRRU, Connected to Next PB
Reason If previous PB resets, the PRRU, connected to next PB, will be disconnected
from BBU. During link disconnection period, if LTE detects that RRU link is
disconnected for a long time, the relevant cell will be deleted and added. Thus,
LTE service is affected.
Scenario If a PB resets, it will affect PRRU service. Indeed, the PRRU, connected to next
PB, will be affected.
Onsite If a PB resets, it will affect PRRU service. Indeed, the PRRU, connected to next
influence PB, will be affected.

Elusion
No
measure
8.2.10 PRRU Does not Support the LTE FDD Cells From Different Baseband
Process Boards
Table 8-58 PRRU Does not Support the LTE FDD Cells From Different Baseband
Process Boards
Item PRRU Does not Support the LTE FDD Cells From Different Baseband Process
Boards
Restrictions PRRU Does not Support the LTE FDD Cells From Different Baseband Process
Boards
Reason RRU gives delay compensation for single LTE.The value is unique, depending
on a factor – LTE cell service is processed by a baseband process board, does
it pass FS board? If the cell service of PRRU in LTE FDD mode comes from
different baseband process boards, RRU should provide different values for
delay compensation. This conflicts with the condition that one PRRU only has
one compensation value.
Scenario During service configuration, two cells of one PRRU should not come from
different baseband resources.
Onsite PRRU Does not Support the LTE FDD Cells From Different Baseband Process
influence Boards.
Elusion PRRU Does not Support the LTE FDD Cells From Different Baseband Process
measure Boards
8.2.11 QCELL System Supports Up to 4-level Cascading Connection and Total

length of 4-level Optical Fiber should not Exceeds 10KM
Table 8-59 QCELL System Supports Up to 4-level Cascading Connection and Total
length of 4-level Optical Fiber should not Exceeds 10KM
Item QCELL System Supports Up to 4-level Cascading Connection and Total length
of 4-level Optical Fiber should not Exceeds 10KM. TA value is 140us for UMTS,
150us for other radio systems. TA value for LTE should not use 100us any
longer.
Restrictions QCELL System Supports Up to 4-level Cascading Connection and Total

length of 4-level Optical Fiber should not Exceeds 10KM. TA value is 140us
for UMTS, 150us for other radio systems.
Reason In QCELL system, PB and PRRU are adopted. The boards generate long
delay. Because of this, the delay caused by optical fiber is constrained so
that the total length of 4-level optical fiber should not exceed 10KM.
Scenario When long optical fiber is used to connect RRU, the total length of cascaded
optical fiber should not exceed 10KM.
Onsite Delay cannot be delivered. UE cannot be registered, therefore, services are
influence affected.
Elusion When long optical fiber is used to connect RRU, the total length of 4-level
measure cascaded optical fiber should not exceed 10KM. TA value is 140us for
UMTS, 150us for other radio systems.
8.2.12 Previous PB1000 Boot Version Cannot Cooperate With EPLD Version C5
or Above. Otherwise, the Device Keeps Staying at BOOT State After Powered
on.
Table 8-60 Previous PB1000 Boot Version Cannot Cooperate With EPLD Version C5 or
Above
Item Previous PB1000 Boot Version Cannot Cooperate With EPLD Version C5 or
Above.
Restrictions PB1000 boot version V1.02.34. The V1.02.33 cannot cooperate with the
lasted EPLD (version No. 0xC5). Furthermore, it cannot cooperate with
EPLD version 0xC5 or above.
Reason
Scenario Previous PB1000 Boot Version tries to cooperate with EPLD version C5 or
above
Onsite Device Keeps Staying at BOOT State After Powered on. PB cannot work
influence properly.
Elusion No
measure

8.3 Version Restrictions of LTE
8.4 NB-IoT Version Restrictions and Left-Behind Defects

1. LN does not support incremental download operation (relevant version download)
Avoiding measure: To replace a NB version, first delete standby version, then re-download and
activate a new version.
2. Left-Behind defects:
1) NB does not support multi-operator function, all the NB cells in the site need to be
configured with the same PLMN, can not be configured differently.
2) Don’t configure two antennas with the same PCI in the inband configuration, there is a
certain probability that UE solve cell pci will fail.
8.5 Other Issues

Null

ZTE SDR Software Release Notes (V4 16 10 20P83) - V1 0

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ZTE SDR Software Release Notes (V4 16 10 20P83) - V1 0

Hochgeladen von

Copyright:

Verfügbare Formate

ZTE SDR Software Release

ZTE SDR Software Release Notes

© 2018 ZTE Corporation. All rights reserved.

ZTE Confidential & Proprietary 1

ZTE SDR Software Release Notes..................................................................................... 1

1 About This Document ................................................................................................... 28

2 Brief Description ........................................................................................................... 28

Table 2-4 Supported upgrade path ............................................................................... 29

3 Change of Device Capacity and Performance Index .................................................. 30

4 Change of Operation & Maintenance ........................................................................... 30

2 ZTE Confidential & Proprietary

5.2.7 Adaptive HSDPA Retransmission .............................................................................. 43

ZTE Confidential & Proprietary 3

4 ZTE Confidential & Proprietary

5.8.14 Support 3.75k/15k ACK Channel ........................................................................... 155

ZTE Confidential & Proprietary 5

6 Solved Defects ............................................................................................................ 196

6 ZTE Confidential & Proprietary

ZTE Confidential & Proprietary 7

8 ZTE Confidential & Proprietary

ZTE Confidential & Proprietary 9

6.4.58 20170329144600 Baseband Reset Problem Due to a Software Operation Error in CA

10 ZTE Confidential & Proprietary

6.4.84 20170112082841 Increase of Prach Average NI by 30 dB or Above After UL CoMP

ZTE Confidential & Proprietary 11

12 ZTE Confidential & Proprietary

6.4.132 20171106235623 E-RAB Drop Rate Deteriorated Significantly after Upgrade to

7 Left-Behind Defects .................................................................................................... 385

Null .................................................................................................................................. 385

8 Version Restrictions and Things to be Noticed ........................................................ 386

ZTE Confidential & Proprietary 13

8.1.1 Version Package Download Restriction ................................................................... 386

14 ZTE Confidential & Proprietary

ZTE Confidential & Proprietary 15

Table 8-56 Support Up to 24 PBs, 192 PRRUs ............................................................. 415

16 ZTE Confidential & Proprietary

Table 2-1 Release upgrading information .............................................................................29

ZTE Confidential & Proprietary 17

18 ZTE Confidential & Proprietary

Table 5-49 UDC ...............................................................................................................119

ZTE Confidential & Proprietary 19

20 ZTE Confidential & Proprietary

ZTE Confidential & Proprietary 21

22 ZTE Confidential & Proprietary

ZTE Confidential & Proprietary 23

Table 6-96 RRU disconnections in some new LTE sites ..................................................333

24 ZTE Confidential & Proprietary

ZTE Confidential & Proprietary 25

26 ZTE Confidential & Proprietary

ZTE Confidential & Proprietary 27

28 ZTE Confidential & Proprietary

1 About This Document

2.1 Release Notes

2.2.1 Change of Hardware Support

2.2.2 Supportable Hardware Board

2.3 Associated NEs’ Version

Table 2-2 Associated NEs’ Version

RNC V3.16.10.xx/ V4.16.10.xx

ZTE Confidential & Proprietary 29

2.4 NEs’ Version Compatibility

Table 2-3 RNC version compatibility

SDR Compatible Compatible Compatible OMMB

2.5 Supported Upgrade Path