Feature Changes in BTS3900

Feature Changes
in BTS3900 V100R008C00SPC220 Compared with

V100R005C00SPC390 (eNodeB, FDD)
Issue
01
Date
2014-01-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 01 (2014-01-30)
Huawei Proprietary and Confidential Copyright

BTS3900 Feature Changes
1 Feature Updates
Feature Updates
1.1 New Features

1.
Number of Paging Messages Sent over the Uu Interface Configurable
Description
Users can now configure the number of paging messages sent from an
eNodeB to a UE over the Uu interface.
Paging reliability is usually guaranteed by the core network. This
function assists the core network to improve paging reliability.
Implementati
on
The PagingSentNum parameter has been added to the PCCHCFG

MO.
Impact
Impact on capacity and performance

When the PagingSentNum parameter is set to a value greater than
1, an eNodeB sends more than one paging message over the Uu
interface to page a UE. This increases the probability that the UE
receives the paging messages. The value of the performance
counter L.Paging.UU.Succ may increase. However, this also
increases radio resource consumption on the Uu interface. A large
number of paging messages sent by the eNodeB would require a
significant amount of radio resources.
Services on cells are interrupted if paging parameters in the
PCCHCFG MO are reconfigured. In the case of the
PagingSentNum parameter, cells will be deactivated and then
reactivated, causing key performance indicators (KPIs) to
fluctuate.
Impact on NEs
None
Impact on hardware
None
Impact on inter-NE interfaces

None
Impact on operation and maintenance

Impact on license: This function is not license-controlled.
Issue 01 (2014-01-30)

1 Feature Updates
Impact on configuration management: The PagingSentNum

parameter has been added.
Impact on performance management: none
Impact on fault management: none
Impact on other features

None
Related
Operations
Run the MOD PCCHCFG command with the PagingSentNum

parameter set to 1, 2, or 3.
Trouble
Ticket
Number
IR-0000120585
Feature ID
LBFD-002011
2.
MME Selection Based on MME Priorities
Description
Users can configure MME priorities on an eNodeB to enable

location-based MME backup for disaster tolerance.
To facilitate location-based MME backup, MMEs in the same area as
an eNodeB are configured with high priorities and those in other
areas are configured with low priorities. The eNodeB sets up S1MME connections to the MME with the highest priority in the same
area. When all MMEs in this area are unavailable, the eNodeB sets up
S1-MME connections to an available MME in other areas.
Implementati
on
1. The Priority parameter has been added to S1 and S1Interface

MOs.
2. After users configure MME priorities in S1 and S1Interface
MOs on an eNodeB, the eNodeB selects an available MME
with the highest priority for UE access.
Impact

None
Impact on NEs
None
Impact on hardware
None

None

Impact on license: This function is an enhancement for S1-flex
that is under control of an eNodeB-level license.
Impact on configuration management: The Priority parameter has
been added to S1 and S1Interface MOs.
Issue 01 (2014-01-30)

1 Feature Updates

MME selection based on MME priorities has the following impact
on the MME selection based on the network topology/MME
capacities/loads and load balancing functions:
If MMEs in an MME pool are configured with different
priorities, MME priorities take precedence over MME
capacities during MME selection. The eNodeB may select an
MME with a lower capacity as long as the MME priority is
high.
If MMEs in an MME pool are configured with different
priorities, the eNodeB still selects MMEs based on their
priorities after UEs reinitiate RRC connection requests
(carrying no MME information) for load balancing. In this
situation, users are advised to reduce the priority of the MME
that needs to be offloaded.
Related
Operations
Run the following commands to set the Priority parameter to a

value within the range of 0 to 255:
ADD S1
MOD S1
ADD S1INTERFACE
MOD S1INTERFACE
Run the following commands to query the Priority value:

DSP S1
LST S1
DSP S1INTERFACE
Trouble
Ticket
Number
IR-0000093593
Feature ID
LOFD-001018
3.
Dual Carriers Supported by the RRU3201, RRU3220 and RRU3222
Description
The RRU3201 with an intermediate frequency (IF) processing

bandwidth of 30 MHz supports dual carriers of 15 MHz+15 MHz and
20 MHz+10 MHz. The RRU3220 and RRU3222 with an IF
processing bandwidth of 20 MHz support dual carriers of 10 MHz+10
MHz.
Implementati
on
The software enables dual-carrier signal filtering, and the

configuration and checking of dual-carrier frequencies.
Impact

System capacity increases because operators can make full use of
their spectrum resources.
Issue 01 (2014-01-30)
Impact on NEs

1 Feature Updates
None
Impact on hardware
None

None

Impact on configuration management: none

None
Related
Operations
None
Trouble
Ticket
Number
IR-0000109308
Feature ID
None
4.
Cell Outage Detection Triggered by Internal Audit Exceptions
Description
eNodeBs can now detect cell outages when internal audit exceptions
occur. This facilitates quick cell outage detection, which improves
network performance and therefore, user experience.
Implementati
on
An eNodeB determines that an internal audit exception occurs when

related conditions are met in two consecutive audit periods (5 minutes
for each).
Impact

None
Impact on NEs
This function is implemented on the eNodeB and M2000.
Impact on hardware
None

Internal audit exception events and recovery events have been
added. They are transmitted over an internal interface between the
eNodeB and M2000.

Issue 01 (2014-01-30)

1 Feature Updates

None
Related
Operations
None
Trouble
Ticket
Number
IREQ00000033
Feature ID
LOFD-002012
5.
eNodeB/P-GW Joint Congestion Control and Service Differentiation
Description
eNodeB/P-GW Joint Congestion Control

This function enables the eNodeB to report cell congestion status
to the PDN gateway (P-GW). The P-GW performs flow control
based on service types, subscriber classes, and subscription status.
This prevents the eNodeB from being congested for a long time.
eNodeB/P-GW Joint Service Differentiation

This function enables the eNodeB to resolve GPRS Tunneling
Protocol-User plane (GTP-U) headers of packets sent from the PGW to obtain flow priority indications (FPIs) of service types
(such as HTTP and P2P). The eNodeB can then apply FPI-based
service differentiation.
Implementati
on

Cells can be in normal, congested, or overloaded state, which is
indicated by the buffer at the radio link layer (RLC). The eNodeB
includes cell status information in headers of packets sent to the PGW only if cell status changes at the end of a cell status reporting
period. If the cell status information indicates that cells are in
normal state, the P-GW does not perform flow control. Otherwise,
the P-GW performs flow control.

The P-GW uses a service sense unit to detect service types of
packets sent from the eNodeB and includes FPIs of service
types in GTP-U headers of packets sent to the eNodeB.
If the service differentiation switch is turned on, the eNodeB
resolves GTP-U headers at the Packet Data Convergence
Protocol (PDCP) layer to obtain FPIs. The eNodeB then
schedules different types of services based on FPIs.
Impact

None
Impact on NEs
The P-GW must support eNodeB/P-GW Joint Congestion Control.
Issue 01 (2014-01-30)
Impact on hardware

1 Feature Updates
None

The eNodeB sends cell congestion information in extended GTPU headers to the P-GW.

Impact on configuration management: The
CellConStaReportSwitch option has been added to the
ServiceDiffSwitch parameter in the CellServiceDiffCfg MO.

This function postpones the time when the eNodeB's flow control
mechanism (back-pressure) takes effect.

Each downlink packet carries 8 more bytes of FPI information.
For example, if the average packet length is 630 bytes, this
function increases a packet overhead of 1.2% (8/630 x 100%).
Impact on NEs
The P-GW must support eNodeB/P-GW Joint Service
Differentiation.
Impact on hardware
None

The P-GW sends FPI information in extended GTP-U headers to
the eNodeB.

Impact on configuration management:
The FPIGTPUSwitch option has been added to the
ServiceDiffSwitch parameter in the CellServiceDiffCfg MO.
The QueueServiceWeight0, QueueServiceWeight1,
QueueServiceWeight2, QueueServiceWeight3,
QueueServiceWeight4, QueueServiceWeight5, and
QueueServiceWeight6 parameters have been added to the
CellServiceDiffCfg MO.

None
Related
Operations
Issue 01 (2014-01-30)

Run the MOD CELLSERVICEDIFFCFG command with the
CellConStaReportSwitch option selected under the

1 Feature Updates
ServiceDiffSwitch parameter.

Run the MOD CELLSERVICEDIFFCFG command with the
FPIGTPUSwitch option selected under the ServiceDiffSwitch
parameter.
Trouble
Ticket
Number
IREQ00000022
Feature ID
None
6.
IREQ00000023
LBBPc and LBBPd Sharing Topologies on the CPRI Interface
Description
This function enables the LBBPc and LBBPd in a BBU to share

topologies on the common public radio interface (CPRI) by
exchanging CPRI data through the backplane in the BBU.
If an eNodeB is equipped with the LBBPc, LBBPd, and multi-carriercapable RF modules, the LBBPc and LBBPd can transmit CPRI data
of multiple cells to the same RF module through the same CPRI port
or to multiple RF modules through multiple CPRI ports on either the
LBBPc or LBBPd. This function improves the eNodeB topology
capability when the LBBPc and LBBPd coexist.
This function has special requirements for RF modules. For details,
see section "LBBP" in 3900 series base station hardware description.
Implementati
on
In topologies on the CPRI interface, the eNodeB forwards CPRI data

between the LBBPc and LBBPd through the backplane in the BBU.
Impact

None
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
Issue 01 (2014-01-30)
Examples of parameter settings are as follows:
3. Run the ADD BASEBANDEQM command with the

basebandEqmId, basebandEqmType, sn1, sn2 and

1 Feature Updates
UMTSDEMMODE parameters set to 0, ULDL, 2, 3 and

NULL respectively.
4. Run the ADD CELL command with the LocalCellId
parameter set to 0.
5. Run the ADD EUCELLSECTOREQM command with all the
LocalCellId, basebandEqmId and SectorEqmId parameters
set to 0.
Trouble
Ticket
Number
IR-0000105123
Feature ID
None
7.
UE-level Intra-Frequency MRO
Description
This is a mobility robustness optimization (MRO) function that

enables the eNodeB to automatically detect a UE that experiences
ping-pong intra-frequency handovers. The eNodeB then delivers
dedicated handover parameters to reduce ping-pong intra-frequency
handovers on the UE.
Implementati
on
The UeMroSwitch option has been added to the MroSwitch

parameter in the ENODEBALGOSWITCH MO, and the
UePingPongNumThd parameter has been added to the MRO MO.
Impact

This function is disabled by default.
When enabled, this function reduces ping-pong intra-frequency
handovers, improves service continuity on UEs, and reduces
signaling, without hindering normal handovers or prolonging the
handover delay.
Impact on NEs
None
Impact on hardware
None

None

Impact on configuration management: The UeMroSwitch option
and the UePingPongNumThd parameter have been added.

The lower limit of the cell individual offset (CIO) value range for
UE-level MRO can be 1 or 2 dB less than that for cell-level intrafrequency MRO.
Issue 01 (2014-01-30)

1 Feature Updates
Related
Operations
6. Run the MOD ENODEBALGOSWITCH command with the

UEMroSwitch option selected under the MroSwitch
parameter.
7. Run the MOD MRO command with the
UePingPongNumThd parameter set to an appropriate value (5
by default).
Trouble
Ticket
Number
IREQ00000060
Feature ID
None
8.
Target Downlink IBLER Adaptation
Description
Currently, the downlink channel quality indicator (CQI) adjustment

algorithm adjusts the CQI values based on hybrid automatic repeat
request (HARQ) feedback from UEs to enable the initial block error
rate (IBLER) to converge to a fixed target value. However, one fixed
target IBLER cannot achieve the optimal throughput in all scenarios.
The target downlink IBLER adaptation function increases downlink
throughput.
Implementati
on
The DlVarIBLERtargetSwitch parameter has been added to the

CELLALGOSWITCH MO. If this parameter is set to OFF, the
target IBLER is 10%. If this parameter is set to ON, the target IBLER
is an adaptive value.
Impact

Downlink throughput, especially downlink throughput for cell
edge users (CEUs), increases.
Impact on NEs
None
Impact on hardware
None

None

DlVarIBLERtargetSwitch parameter has been added.

None
Related
Operations
Run the MOD CELLALGOSWITCH command with the

DlVarIBLERtargetSwitch parameter set to ON.
Trouble
IR-0000121925
Issue 01 (2014-01-30)

10
1 Feature Updates
Ticket
Number
Feature ID
9.
None
eNodeB Always-Online
Description
This function enables an eNodeB to reset its neighboring eNodeB

that is disconnected from the M2000 through the X2 interface. This
function applies based on the following assumptions: the transport
network operates properly, the operation and maintenance (OM)
channel between the disconnected eNodeB and the M2000 is
unavailable, but the service channel to the disconnected eNodeB is
available. With this function, an eNodeB disconnected from the
M2000 can be reset remotely, and users do not need to visit sites to
reset an eNodeB.
Implementati
on
When a normal eNodeB receives a command for resetting an

abnormal eNodeB from the M2000, the normal eNodeB sends a reset
message to the abnormal eNodeB through the X2 interface. After
receiving the message, the abnormal eNodeB resets and sends a
response message to the normal eNodeB. The normal eNodeB returns
the operation result to the M2000.
Impact

None
Impact on NEs
None
Impact on hardware
None

This function is implemented over Huawei proprietary X2
interface. This interface is used to exchange non-standard
signaling between Huawei eNodeBs to implement extended
features that are not specified in 3GPP specifications.

Impact on configuration management: The RST NBRENODEB
command has been added.

None
Related
Operations
8. On the M2000, check whether the alarm ALM-301 NE Is

Disconnected is generated.
If yes, go to step 2.
9. On the M2000, perform the following operations to check
whether an available X2 interface to the disconnected eNodeB
Issue 01 (2014-01-30)

11
1 Feature Updates
exists:
a. In the main window of the M2000, choose Configuration >
MIT Browser.
The MIT Browser window is displayed.
b. Locate the disconnected eNodeB and expand its MO tree.
c. Check the EutranExternalCell MO configuration on the
disconnected eNodeB for peer eNodeB IDs (The key
parameters in the EutranExternalCell MO are Mcc, Mnc,
eNodeB ID, and CellId.)
If the EutranExternalCell MO is not configured or incorrectly configured for
the disconnected eNodeB, users cannot locate peer eNodeBs.
d. Check the eNodeBFunction and CnOperator MO

configurations on the disconnected eNodeB for its ID and
PLMN. The eNodeB ID is identified by the eNodeB ID
parameter in the eNodeBFunction MO and the PLMN is
identified by the Mobile country code and Mobile network
code parameters in the CnOperator MO.
e. Run the DSP X2INTERFACE command on a peer eNodeB
located in step 2.c.
If the command output indicates that the neighboring eNodeB ID
and PLMN of the peer eNodeB are the same as the ID and PLMN
of the disconnected eNodeB, an available X2 interface to the
disconnected eNodeB exists. Go to step 3.
10.On the LMT, run the RST NBRENODEB command for the
peer eNodeB to reset the disconnected eNodeB.
Users are advised to run the RST NBRENODEB command with the
ResetMode parameter set to NormalReset. If the command does not take
effect, run the RST NBRENODEB command with the ResetMode
parameter set to PoweroffReset.
The NbrENodeBId parameter in the RST NBRENODEB command must

be set to the ID of the disconnected eNodeB.
Trouble
Ticket
Number
IREQ00000077
Feature ID
None
10. Dedicated Cell-Reselection Priorities Specific to the Operator IDs of the Local Cell
Description
Issue 01 (2014-01-30)
In RAN sharing in common carrier scenarios, users can configure

dedicated cell-reselection priorities for intra- and inter-RAT
neighboring frequencies (or frequency groups) based on the operator
IDs of the local cell. This enables UEs of different operators to
achieve different camping policies in idle mode and prevents UEs
from being redirected to frequencies on which these UEs cannot
operate.

12
1 Feature Updates
Implementati
on
After users configure dedicated cell-reselection priorities based on the

operator IDs of the local cell, an eNodeB includes operator-specific
cell-reselection priorities in the IE IMMCI of the RRC Connection
Release message sent to a UE.
Impact

This function is disabled by default.
When enabled, this function prolongs the standby time of a UE by
preventing the UE from performing cell measurements and
camping attempts on frequencies on which the UE cannot operate.
Impact on NEs
This function is implemented on the eNodeB, CME, and M2000.
Impact on hardware
None

None

Impact on license: The cell-level license MOCN Flexible Priority
Based Camping has been added.
Impact on configuration management: The CnOperatorID and
CellReselDediPri parameters have been added to the
EUTRANNFREQSCELLOP, UTRANNFREQSCELLOP, and
GERANNFGROUPSCELLOP MOs. In addition, the
CnOperatorID, Cdma1XrttCellReselDediPri, and
HrpdCellReselDediPri parameters have been added to the
CDMA2000BCSCELLOP MO.

Dedicated cell-reselection priorities based on the operator IDs of
the local cell does not work with dedicated cell-reselection
priorities based on the operator IDs of the neighboring frequency.
Related
Operations
Issue 01 (2014-01-30)
To configure dedicated cell-reselection priorities for neighboring EUTRAN frequencies based on the operator IDs of the local cell, run
the MOD EUTRANNFREQSCELLOP command with the
CnOperatorID, DlEarfcn, and CellReselDediPri parameters set
to appropriate values.
To configure dedicated cell-reselection priorities for neighboring

UTRAN frequencies based on the operator IDs of the local cell, run
the MOD UTRANNFREQSCELLOP command with the
CnOperatorID, UtranDlArfcn, and CellReselDediPri parameters
set to appropriate values.

GERAN carrier frequency groups based on the operator IDs of the
local cell, run the MOD GERANNFGROUPSCELLOP
command with the CnOperatorID, BcchGroupId, and
CellReselDediPri parameters set to appropriate values.

13
1 Feature Updates
CDMA2000 band classes based on the operator IDs of the local

cell, run the MOD CDMA2000BCSCELLOP command with the
CnOperatorID, BandClass, Cdma1XrttCellReselDediPri, and
HrpdCellReselDediPri parameters set to appropriate values.
Trouble
Ticket
Number
DTS2012071802573
Feature ID
LOFD-001112
11. Base Stations Supporting Security Performance Counters

Description
Base stations now support security performance counters. These

counters can indicate whether a base station is functioning properly
and whether the base station is under malicious attacks.
Implementati
on
Among these security performance counters:
Some performance counters calculate the number of IPsec packets

received by or transmitted from a base station. You can locate faults
by comparing the values of these counters with the number of IPsec
packets actually received by or transmitted from the base station in
question.
Some performance counters calculate the number of packets

filtered by the firewall. With these counters, you can determine
whether a base station is under malicious attacks or has received a
large number of invalid packets
Some performance counters calculate the number of the errors that

occur during IKE negotiation. You can locate faults by comparing
the values of these counters with the actual IKE configurations.
IPsec stands for Internet Protocol Security (IPsec) and IKE stands for
Internet Key Exchange.
On the M2000, some counters have been added.
Impact

None
Impact on NEs
Specific versions of the M2000 support the counters listed in the
Implementation.
Impact on hardware
None

The MML command DSP INVALIDPKTINFO has been added.
The counters listed in the Implementation have been added to the
M2000.

Impact on license: none
Issue 01 (2014-01-30)

14
1 Feature Updates
Impact on performance management

Some security performance counters have been added.

This feature depends on the WRFD-050402 IP Transmission
Introduction on Iub Interface feature.
Related
Operations
Run the DSP INVALIDPKTINFO command to query information

about packets discarded by the packet filter, flood defend, or IPsec
anti-replay function.
Log in to the M2000 to query the values of the newly added counters.
Trouble
Ticket
Number
IR-SRAN80-SAF-005
Feature ID
None
12. Base Stations Supporting TLS of Version 1.2

Description
The Transport Layer Security (TLS) of version 1.2 is the latest TLS
that the Secure Sockets Layer (SSL) supports. The TLS of version 1.2
prevents packets transmitted over operation and maintenance (O&M)
channels from being listened to or tampered with.
Compared with the TLS of version 1.1 (also called SSL3.0), the TLS
of version 1.2 provides better security performance.
Implementati
on
The parameters and related parameter settings of the TLS of version

1.2 do not change compared with the TLS of version 1.1. In
SRAN8.0, a base station informs the peer end that it supports the TLS
of version 1.2 when negotiating the TLS version with the peer end.
Impact
None
Impact on NEs
None
Impact on hardware
None
None

Impact on fault management
In ALM-25950 Base Station Being Attacked, the SSL
Renegotiation Attack value has been added to the Specific
Problem parameter. This value indicates that the base station in
Issue 01 (2014-01-30)

15
1 Feature Updates
question is under an SSL renegotiation attack.

None
Related
Operations
None
Trouble
Ticket
Number
IR-SRAN80-SAF-010
Feature ID
None
13. SSL Certificate Sharing During PNP Base Station Deployment

Description
The eGBTS, NodeB, and eNodeB support SSL certificate sharing

during plug and play (PNP) base station deployment.
Implementati
on
During PNP base station deployment, Subcode 52 in the Options43

field of a DHCP offer packet from the M2000 to a base station carries
the cabinet, subrack, and slot numbers of the certificate required for
SSL authentication.
Upon receiving a DHCP offer packet, a board checks whether the
certificate required for SSL authentication is located on itself based
on the cabinet, subrack, and slot numbers of the certificate. If yes, the
board uses the local certificate for SSL authentication. If no, the
board regards the local certificate as invalid and then the base station
uses the certificate configured for the board specified by the
preceding cabinet, subrack, and slot numbers.
Certificates configured for boards may be issued by operators or
Huawei. However, certificates issued by operators take precedence
over those issued by Huawei.
Certificate sharing is a dynamic process and does not cause base
stations to restart.
Impact

None
Impact on NEs
This feature works with specific versions of the M2000.
Impact on hardware
None

None

Issue 01 (2014-01-30)

16
1 Feature Updates

None
Related
Operations
None
Trouble
Ticket
Number
CR20120907017
Feature ID
None
14. Enhanced Transmission Resource Pool

Description
Base stations where the IP over E1 transmission scheme is applied

can now use the transmission resource pool feature now.
Implementati
on
User-plane end points of the base station where the IP over E1

transmission scheme is applied can use the IP addresses of Point-toPoint Protocol (PPP) links or Multilink PPP groups (MPGRPs).
Impact

None
Impact on NEs
This feature works with specific versions of the CME.
Impact on hardware
None

None


None
Related
Operations
Run the ADD USERPLANEHOST command and set the locIpV4

parameter to the IP address of a specific PPP link or MPGRP.
Trouble
Ticket
Number
IR-SRAN80-TRAN-070
Feature ID
None
15. Base Stations Supporting the End Point Configuration Method

Description
Issue 01 (2014-01-30)
The end point configuration method is now supported by the user

17
1 Feature Updates
plane of the eGBTS/NodeB and the user and control planes of the
eNodeB. With this configuration method, transmission links can be
automatically set up between base stations and peer NEs, thereby
simplifying transmission configuration and adjustment.
Implementati
on
In self-setup scenarios, users only need to configure local end points.

Transmission links are automatically set up between the local and
peer ends based on UE access information.
In other scenarios, users need to configure local and peer end points
and set the mapping between these end points for the two ends. Then,
each local end point negotiates with the corresponding peer end point
about parameter settings to set up a transmission link.
Impact

On the user plane of the eGBTS and NodeB, 96 transmission links
can be automatically set up.
On the control plane of the eNodeB, 80 transmission links can be
automatically set up using IPv4 and 48 transmission links can be
automatically set up using IPv6. On the user plane of the eNodeB,
384 transmission links can be automatically set up using IPv4 and
IPv6.
Impact on NEs
This configuration method works with specific versions of the
CME, M2000, and LMT.
Impact on hardware
None

The southbound and northbound interfaces must be modified to
support this configuration method.

For details, see changes in the northbound interface.
For eNodeBs, the mechanism for X2 self-setup over the M2000
has been modified. If X2 self-setup is enabled on an eNodeB,
control-plane local port numbers must be set to the same value on
the local and neighboring eNodeBs to ensure successful X2 selfsetup.
The following counters have been added:
Issue 01 (2014-01-30)
VS.UserPlaneHostIP.TxPkts
VS.UserPlaneHostIP.RxPkts
VS.UserPlaneHostIP.TxBytes
VS.UserPlaneHostIP.RxBytes
VS.UserPlaneHostIP.TxMaxSpeed
VS.UserPlaneHostIP.TxMeanSpeed
VS.UserPlaneHostIP.RxMaxSpeed

18
1 Feature Updates
VS.UserPlaneHostIP.RxMeanSpeed

ALM-25952 User Plane Path Fault has been added.
For eNodeBs, managed objects (MOs) X2SigIP, X2ServIP,
X2eNodeB, S1SigIP, MME, S1ServIP, and SGW in earlier
versions have been removed. A smooth upgrade mechanism has
been added for end point configurations. If a combination of
X2SigIP, X2ServIP, and X2eNodeB, of S1SigIP and MME, or
of S1ServIP and SGW have been configured on an eNodeB
before the upgrade, the eNodeB checks whether the IP paths or
SCTP links exist after the upgrade. If they do not exist, the
eNodeB sets up the IP paths or SCTP links automatically. If the IP
paths or SCTP links are disconnected, an alarm of ALM-25888
SCTP Link fault, or user-plane path fault is reported. The upgrade
risk check package provides the configuration check. If the
configuration fails the check, rectify faults according to the
handling suggestions provided by the package.

None
Related
Operations
For the user plane:
11.Run the ADD EPGROUP command to add an end point

group.
12.Run the ADD USERPLANEHOST command to add a userplane local end point.
13.(Optional) Run the ADD USERPLANEPEER command to
add a user-plane peer end point. If you do not run this
command, a user-plane peer end point will still be
automatically created.
14.Configure objects that use end points:
For the eGBTS, run the ADD ABIS command to add an Abis
object that uses user-plane end points.
For the NodeB, run the ADD IUB command to add an Iub
object that uses user-plane end points.
For the eNodeB, run the ADD S1 command to add an S1
object that uses user-plane end points. Then, run the ADD X2
command to add the X2 object that uses user-plane end points.
For the control plane (supported only by the eNodeB):
Run the ADD EPGROUP command to add an end point group.
Run the ADD SCTPTEMPLATE command to add a local SCTP
object.
Run the ADD SCTPHOST command to add a peer SCTP object.
Run the ADD SCTPPEER command to add an SCTP parameter
template.
Run the ADD S1 command to add the S1 object that uses controlplane end points. Then, run the ADD X2 command to add the X2
object that uses control-plane end points.
Issue 01 (2014-01-30)

19
1 Feature Updates
Trouble
Ticket
Number
CR-MBTS18-135
Feature ID
None
16. Enhanced IUANT Tracing

Description
The IUANT tracing function for the NodeB has been enhanced. The
enhanced function traces not only messages that are transmitted when
all the involved procedures are running properly but also messages
that are transmitted when errors occur in some procedures. The
enhanced IUANT tracing function is now available to the eGBTS and
eNodeB.
Implementati
on
This function traces messages transmitted between antennas and radio

frequency (RF) modules by node and saves tracing results into a
specified directory.
Impact

The enhanced IUANT tracing function now traces erroneous
messages, and therefore the CPU usage of the NodeB, eGBTS,
and eNodeB may increase. However, when this function is
enabled, the CPU usage is monitored in real time. Once a
specified threshold is reached or exceeded, this function is
automatically disabled to prevent the NodeB, eGBTS, or eNodeB
from being negatively affected.
Impact on NEs
The function works with specific versions of the LMT.
Impact on hardware
None

None


None
Related
Operations
Log in to the LMT and choose Trace > Trace > Common Services >
IUANT Trace. In the displayed IUANT Trace dialog box, specify
the Node No. parameter.
Trouble
Ticket
Number
IR-SRAN80-DFX-009-SR02
Feature ID
None
Issue 01 (2014-01-30)

20
1 Feature Updates
17. Enhanced MAC Message Measurement

Description
For the Media Access Control (MAC) message measurement

function, the following filter criteria have been added to the IP layer:
protocol type, IP address, port number, GTP-U tunnel ID, and
differentiated services code point (DSCP). With these filter criteria,
MAC messages can be measured more efficiently.
Implementati
on
The filter criteria for the MAC message measurement function have
been expanded.
Impact

After the filter criteria for the function are expanded, MAC
messages can be measured efficiently.
Impact on NEs
This function works with specific versions of the LMT, M2000,
and SMT.
Impact on hardware
None

The following ports or interfaces must be modified:
Southbound interfaces between the LMT

or M2000 and base stations
Binary message ports between the SMT
and GBTS
Binary message ports between the GBTS
and BSC
Note that such modifications are invisible to users.


None
Issue 01 (2014-01-30)

21
Related
Operations
1 Feature Updates
On the LMT, M2000, SMT, and BSC, the following parameters have
been added to the IP-layer message filter criteria for the MAC Trace
tab page:
Expand Switch
Protocol Type
Local IP Address
Peer IP Address
Local Port
Peer Port
GTPU Tunnel ID (for the eNodeB only)
DSCP
Trouble
Ticket
Number
IR-SRAN80-TDFT-006
Feature ID
None
18. Base Stations Supporting CPRI MUX

Description
The CPRI MUX feature works as follows:

A board serving mode A sends the data of mode A to another board serving mode B
through the BBU backplane data bus. The board serving mode B then multiplexes the
data of modes A and B onto one CPRI link, enabling physical CPRI bandwidth sharing.
Implementati
on
In the downlink:
A board serving mode A sends the data of mode A to another board serving mode B
through the BBU backplane data bus. After multiplexing the data of modes A and B, the
board serving mode B sends the multiplexed data to RF modules using CPRI links.
In the uplink:
RF modules send the data of modes A and B to the board serving mode B using CPRI
links. The board then, using the BBU backplane data bus, separates the data and sends the
data of mode A to the board serving mode A.
Issue 01 (2014-01-30)

22
Impact
1 Feature Updates

When CPRI MUX is applied, the minimum CPRI data rate on the converging party is
2.5 Gbit/s.
Issue 01 (2014-01-30)
CPRI Data Rate on the Converging Party
GU
Maximum Number of Carriers/Cells Supported by a CPRI Link on the Converging Party
Maximum Number of Carriers/Cells Supported by the Baseband Signal Processing Board

on the Converging Party



In separate- and co-MPT scenarios, the converging capabilities of a multimode base

station depend on CPRI data rates of the converging party and specifications of the
converging party's baseband signal processing boards. The following table lists the
data rate on a CPRI link of the converging party and the specifications of the
converging party's baseband signal processing boards.
2.5
Gbit/s
G16
+ U4
G96
+
U24
G16 +
L1 x
10
MHz
G96 +
L6 x
10
MHz
U4 +
L1 x
10
MHz
U24 +
L6 x
10
MHz
G6 +
U2 +
L1 x
10
MHz
G36 +
U12 +
L6 x 10
MHz
4.9
Gbit/s
G32
+ U8
G126
+
U24
G32 +
L1 x
20
G126
+ L4 x
20
MHz
U8 +
L1 x
20
MHz
U24 +
L4 x
20
MHz
G12 +
U4 +
L1 x
10
MHz
G72 +
U24 +
L4 x 10
MHz
GL
UL
GUL

23
1 Feature Updates
In the preceding table, the LTE employs a 2T2R configuration.
Impact on NEs
The CPRI MUX feature works with specific versions of the BSC, M2000, and CME.
Impact on hardware
The following table provides restrictions for the converging and converged parties.
Issue 01 (2014-01-30)
Scenar Main
Mode Board of
io
Control that a the
Board CPRI Convergi
Port ng Party
Serve
s
Slot of
Mode
the
that the
Convergin Converg
g Party
ed Party
Serves
Board and
Slot
Restrictio
ns for the
Converge
d Party
Separate- LMPT or UL
MPT
UMPT_L
+ WMPT
or
UMPT_U
WBBPf
2 or 3
LTE
The
converged
party must use
an LBBPd
and the
LBBPd must
be installed in
slot 2 or 3.
LBBPd
2 or 3
UMTS
A WBBPf
must be
installed in
slot 2 or 3.
WMPT or GU
UMPT_U
+ GTMUb
WBBPf
2 or 3
GSM
A GTMUb
must be
installed in
slot 6.
LMPT or GL
UMPT_L
+ GTMUb
LBBPd
2 or 3
GSM
A GTMUb
must be
installed in
slot 6.
Co-MPT UMPT_U UL
L
WBBPf
2 or 3
LTE
The
converged
party must use
an LBBPd
and the
LBBPd must
be installed in
slot 2 or 3.
LBBPd
2 or 3
UMTS
A WBBPf
must be
installed in
slot 2 or 3.

24
1 Feature Updates
Scenar Main
Mode Board of
io
Control that a the
Board CPRI Convergi
Port ng Party
Serve
s
Slot of
Mode
the
that the
Convergin Converg
g Party
ed Party
Serves
Board and
Slot
Restrictio
ns for the
Converge
d Party
UMPT_G GU
U
UBRIb
0 or 1
UMTS
A WBBPf
must be
installed in
slot 2 or 3.
UMPT_G GL
L
UBRIb
LTE
The
converged
party must use
an LBBPd
and the
LBBPd must
be installed in
slot 2 or 3.
UMPT_G GUL
UL
UBRIb
UMTS or
LTE
A WBBPf and
an LBBPd
must be
installed in
slots 2 and 3,
respectively.
On the
eNodeB side,
the converged
party must use
an LBBPd.

None

If the CPRI MUX feature is to be activated in separate-MPT multimode base stations,
it can be configured only on the converged party.
For the GBTS:
The AT parameter has been added to the ADD BTSRXUCHAIN and MOD
BTSRXUCHAIN commands and this parameter must be set to PEERPORT(peer
port). In addition, the values of the parameters HCN, HSRN, HSN, and HPN in the
two commands must be consistent with those on the converging party's RXU chain or
ring.
For the NodeB and eNodeB:
The AT parameter is added to the ADD RRUCHAIN and MOD RRUCHAIN
commands and this parameter must be set to PEERPORT(peer port). In addition, the
values of the parameters HCN, HSRN, HSN, and HPN must be consistent with those
for the RXU chain or ring on the converging party.
Issue 01 (2014-01-30)

25
1 Feature Updates


In separate-MPT scenarios, the GBFD-510104 Multi-site Cell feature is not
supported.
In co-MPT scenarios, baseband frequency hopping and the GBFD-510104 Multisite Cell feature cannot take effect between the GTMUb and UBRIb if the UBRIb
is installed in slot 0 or 1.
Related
Operations
If the CPRI MUX feature is to be activated in separate-MPT multimode base stations, it

can be configured only on the converged party.
On a GBTS, when running the ADD BTSRXUCHAIN or MOD BTSRXUCHAIN
command to add an RXU chain or ring, set the AT parameter to PEERPORT(peer port)
and ensure that the values of the parameters HCN, HSRN, HSN, and HPN in the two
commands are consistent with those on the converging party's RXU chain or ring.
On a NodeB or eNodeB, when running the ADD RRUCHAIN or MOD RRUCHAIN
command to add an RXU chain or ring, set the AT parameter to PEERPORT(peer port)
and ensure that the values of the parameters HCN, HSRN, HSN, and HPN in the two
commands are consistent with those on the converging party's RXU chain or ring.
If the CPRI MUX feature is to be activated in co-MPT multimode base stations, no
special operations are required.
Trouble
Ticket
Number
IR-SRAN80-UMPT-006
Feature ID
None
IR-SRAN80-BBU-002
19. OMBs Supporting 100 A Output Power

Description
OMBs now support 100 A output power (Previously, it was 15 A.)

and therefore can work with high-power MRFU V3 modules.
Implementati
on
The power system in the OMB has been changed.
Impact
In the original OMB, the PMU, PSU2, and PSU1 are installed in the
power subrack's slots 0 through 2, respectively. In the new OMB, the
PMU, PSU1, and PSU2 are installed in the power subrack's slots 0
through 2, respectively.
None
Impact on NEs
The OMB with 100 A output power works with specific versions
of the BSC, CME, LMT, and M2000.
Impact on hardware
To support 100 A output power, the PMU must use the power
system of the ETP48100 type and work with a PSU using a 2x50
A configuration.
Issue 01 (2014-01-30)

26
1 Feature Updates
None


None
Related
Operations
None
Trouble
Ticket
Number
IR-SRAN80-SITE-003
Feature ID
None
20. Temperature Curve Selectable

Description
When working in default mode, the fan quietly provides good heat
dissipation performance. However, the default mode does not work
well in all geographical areas. For example, the fan speed may need
to be increased in warm areas but decreased in cold areas. Users can
select the appropriate optimal temperature curve by using the
temperature curve selectable function. Should questions arise when
using this function, contact local Huawei technical support personnel.
Implementati
on
Users can run MML commands to select an optimal temperature

curve.
Impact

None
Impact on NEs
None
Impact on hardware
The following cabinets support this function:
BTS3900A cabinets of version D,

including modified cabinets
OMB cabinets of version C
BTS3900 cabinets of version D,

BTS3900L cabinets of version D,

BTS3900AL
TP48600A

None
Issue 01 (2014-01-30)

27
1 Feature Updates


None
Related
Operations
For the GBTS, run the SET BTSFMUABP command to select an

optimal temperature curve.
For the eGBTS, NodeB, and eNodeB, run the MOD FMU command
to select an optimal temperature curve.
Trouble
Ticket
Number
IR-SRAN80-SITE-005
Feature ID
None
21. Modified BTS3012 and BTS3012AE

Description
After being modified into BTS3900 Ver.D series base stations,

double-transceiver GSM base stations now support 2 BBUs, 6 RFUs,
9 RRUs, and MRFU V3 modules.
Implementati
on
After being modified, the BTS3012 and BTS3012II support the base
station type BTS3900 and the cabinet types BTS3012_SRAN and
BTS3012II_SRAN. The modified BTS3012 and BTS3012II can now
be configured with 2 BBUs and a maximum of 3 PSUs. The modified
BTS3012 and BTS3012II are configured with the FMU (previously
the NFCB), EMU (previously the DEMU), and EPS4890 power
system of the ETP48150 hardware type. In addition, the modified
BTS3012 and BTS3012II can now work with high-power MRFU V3
modules.
After being modified, the BTS3012AE supports the base station type
BTS3900A and the cabinet type BTS3012AE_SRAN. The modified
BTS3012AE can now be configured with 2 BBUs and a maximum of
5 PSUs. The modified BTS3012AE is configured with the FMU
(previously the NFCB), EMU (previously the DEMU), APM30
power system of the ETP48250 hardware type, and DHEU (which
remains unchanged). In addition, the modified BTS3012AE can now
work with high-power MRFU V3 modules.
Impact

None
Impact on NEs
None
Impact on hardware
None
Issue 01 (2014-01-30)

28
1 Feature Updates
None


None
Related
Operations
None
Trouble
Ticket
Number
CR-SRAN80-SITE-X01
Feature ID
None
22. Graphical Displays of Optical Module Information

Description
Optical module information can be graphically displayed on the

Topology tab page of the M2000.
Implementati
on
The Topology tab page graphically displays information about BBU

or RRU optical ports, such as optical module status, wave length, and
power. There is a newly added alarm indicator beside each optical
port that indicates optical module status. When an optical module is
functioning properly, the alarm indicator is green. If the optical
module fails, the alarm indicator may be red, orange, yellow, or blue.
Note that different colors indicate alarms of different severity.
Impact

None
Impact on NEs
None
Impact on hardware
None

A message interface has been added to base stations to report
alarm severities of faults on optical modules.


None
Issue 01 (2014-01-30)

29
1 Feature Updates
Related
Operations
On the Topology tab page of the M2000, right-click a base station

and select Device Panel. In the displayed Device Panel window,
double-click
Information.
and right-click Display CPRI Port
Trouble
Ticket
Number
CR-SRAN80-OM-X03
Feature ID
None
23. Signaling Resource Pool for Co-MPT Multimode Base Stations

Description
When co-MPT is applied, the GSM, UMTS, and LTE modes can
dynamically share signaling processing modules (SCTP and TRM
modules) on the UMPT. Now, more UMPTs can be configured for
base stations to improve their signaling processing capacity. (SCTP
stands for Signaling Control Transmission Protocol and TRM stands
for transport resource management.)
Implementati
on
During capacity expansion or mode transition, a second UMPT can

be configured for base stations.
Impact

One UMPT can be configured for a GO or UO single-mode base
station; one or two UMPTs can be configured for an LO singlemode base station or a co-MPT multimode base station. When two
UMPTs are installed in the BBU and one UMPT is faulty or
resets, the signaling processing capability of the entire base station
is degraded; in addition, ongoing services on the problem UMPT
are affected or may even be interrupted.
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
Issue 01 (2014-01-30)
None

30
1 Feature Updates
Trouble
Ticket
Number
IR-SRAN80-UMPT-003
Feature ID
None
24. Enhanced O&M Channel Restoration

Description
When an O&M channel connecting a base station to the M2000 fails,

O&M personnel need go to sites to restore the O&M channel.
However, there are a large number of sites in service, and therefore
maintenance and repairing costs are high. With this function, O&M
personnel do not need to frequently go to sites to restore failed O&M
channels. This function helps reduce maintenance costs and board
repairing rates and improve device and network reliability.
Implementati
on
When a base station's O&M channel fails and the base station's
services are interrupted, this function enables the base station to reset,
aiming to restore the failed O&M channel and prevent frequent site
visiting. If the base station can still properly process services, O&M
personnel can run MML commands to restore the failed O&M
channel.
If an internal maintenance link of a base station fails, this function
enables BBU boards or RF modules to restore the failed link. If the
function is unsuccessful, O&M personnel can run MML commands to
manually restore the link. Such internal maintenance links include
maintenance links between:
Impact
Main control boards and RF modules
Main control boards and other BBU boards
Baseband signal processing boards and RF modules

None
Impact on NEs
This feature works with specific versions of the BSC, M2000, and
LMT.
Impact on hardware
None

Proprietary messages transmitted over the X2 interface between
two Huawei eNodeBs are used to support Huawei proprietary
features that are not specified in the related protocol.

The MML command RST NBRENODEB has been added to the
eNodeB.
Issue 01 (2014-01-30)

31
1 Feature Updates

None
Related
Operations
Based on onsite conditions, run the BSC MML command RST BTS
to reset a GBTS or eGBTS and run the RNC MML command RST
UNODEB command to reset a NodeB.
Based on onsite conditions, run the eNodeB MML command RST
NBRENODEB on a neighboring eNodeB to reset the problem
eNodeB. When necessary, run the MML command RST
BRDPWROFF, RST CANBUS, SET DHCPSW, or SET
TLFRSWITCH on the base station.
Trouble
Ticket
Number
IR-SRAN80-DFX-006
Feature ID
None
25. Intermodulation Detection and VSWR Testing

Description
The configuration data-based intermodulation detection function

works between GSM, UMTS, or LTE signals. This function enables
online detection. During detection, call drops will not occur and new
UEs can access networks.
The single-tone-signal-based intermodulation detection function
works between GSM, UMTS, or LTE signals without an
intermodulation detector. This function enables offline detection.
During detection, ongoing services will be interrupted.
The inter-RAT intermodulation detection function works between
GSM, UMTS, and LTE signals. This function applies to multimode
base stations and enables online detection. Compared with the
configuration data-based intermodulation detection function, the
inter-RAT intermodulation detection function can improve the
intermodulation detection efficiency for multimode base stations.
The multi-frequency VSWR testing function is introduced. Compared
with the single-frequency VSWR testing function, the multifrequency VSWR testing function can accurately and quickly reflect
cable connection problems on the antenna system because standing
waves vary according to frequencies.
Implementati
on
The GBTS supports the configuration data-based intermodulation

detection function since SRAN7.0 and the eGBTS supports this
function in SRAN8.0. It operates in the same way on both.
The NodeB and eNodeB also support this function in SRAN8.0
where it compares the received total wideband power (RTWP) of an
RF channel when the channel works with the maximum power
specifications with the RTWP of the channel when it does not. Based
on the comparison results, this function determines whether severe
intermodulation exists.
The single-tone-signal-based intermodulation detection function
transmits two single-tone signals that operate at two different
Issue 01 (2014-01-30)

32
1 Feature Updates
frequencies (F1 and F2) from the same RF channel using the same
transit power. When the generated intermodulation products of order
3, 5, 7, or higher are received by the uplink frequencies (F3 and F4)
of the involved base station, this function checks the changes to the
receive level of the base station to determine whether intermodulation
is severe.
The inter-RAT intermodulation detection function compares the
RTWP of an RF module for each mode involved when the module
works with the maximum power specifications with the RTWP of the
module when it does not. Based on the comparison results, this
function determines whether severe intermodulation exists between
these modes.
In SRAN8.0, the eGBTS, UMTS, and eNodeB support not only the
single-frequency VSWR testing function, but also the multifrequency VSWR testing function. The GBTS supports the multifrequency VSWR testing function from SRAN7.0 onwards.
Impact

None
Impact on NEs
The inter-RAT intermodulation detection function is implemented
on the M2000.
Impact on hardware
To support the single-tone-signal-based intermodulation detection
function, the NodeB and eNodeB must use MRFU V3 modules;
the GBTS and eGBTS must use MRFU V1, MRFU V2, or MRFU
V3 modules.

For the inter-RAT intermodulation detection function, the
following internal MML commands have been added:
STR SIMLOADM
STP SIMLOADM
STR MEAM
STP MEAM
STR MEAREPORTM


None
Related
Operations
To enable the configuration data-based intermodulation detection

function, run the STR RFTEST command and set TSTTYPE to
PIMONTRAFFIC_ONLINE.
To enable the inter-RAT intermodulation detection function, log in to
the M2000 and choose Trace and Maintenance > Maintenance >
Issue 01 (2014-01-30)

33
1 Feature Updates
RF Performance Test > Interference Measurement > Multimode

Base Station Intermodulation Detection.
Trouble
Ticket
Number
IR-SRAN80-DFX-002
Feature ID
None
26. AAU3901 Supporting RF Channel Failure Processing

Description
If some RF channels in an AAU3901 working in UMTS mode fail,

the specifications of the cells served by the AAU3901 are
automatically reduced. For example, specifications are reduced from
2T to 1T. If all the RF channels in the AAU3901 fail, the served cells
drop out of service.
Implementati
on
If some RF channels in an AAU3901 working in UMTS mode fail,

cells that were served by the AAU3901 are set up again.
Impact

If some RF channels in an AAU3901 working in UMTS mode
fail, the specifications of the cells served by the AAU3901 are
automatically reduced.
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
IR-SRAN80-AAS-002
Feature ID
None
27. Smooth Upgrade from SRAN7.0 (eRAN3.0) to SRAN8.0 (eRAN6.0) Supported by the
AAU3901
Issue 01 (2014-01-30)

34
1 Feature Updates
Description
In SRAN7.0, the managed object (MO) for the AAU3901 is MAAU.

In SRAN8.0, the MOs for the AAU3901 are AAS and AARU, and the
AAMU object is automatically created when you configure the
AAU3901. If you have configured an AAU3901 in SRAN7.0, you do
not need to configure the AAU3901 again after an upgrade to the
SRAN8.0.
Implementati
on
After an upgrade from SRAN7.0 to SRAN8.0, the AAS and AARU

MOs and the AARU object are automatically created for the
AAU3901 that has been configured in SRAN7.0, and the AAU3901
is automatically configured in SRAN8.0. The slot number for the
AAMU is 0 and the slot number for the AARU is 1.
Impact

None
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
IR-SRAN80-AAS-003
Feature ID
None
28. AAU3901 Supporting RRU/RFU Maintenance Functions

Description
Issue 01 (2014-01-30)
As a new type of RF module, the AAU3901 supports the following

RRU/RFU maintenance functions:
Temperature reporting
Output power testing
Offline intermodulation and interference testing
Online high-precision frequency spectrum scanning
Online broad frequency spectrum scanning
Offline broad frequency spectrum scanning

35
1 Feature Updates
Frequency scanning
Cell-level RTWP reporting
RF channel-level RTWP reporting
Implementati
on
The AAU3901 supports the RRU/RFU maintenance functions.
Impact

None
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
IR-SRAN80-AAS-013
Feature ID
None
29. Three Sectors with Two RRU3942 Modules

Description
Three sectors are served by two RRU3942 modules that operate in

the 850 MHz and 1900 MHz frequency bands. The power
specifications of these sectors are 1x80 W, 2x40 W, and 1x80 W. A
maximum of 16 carriers can be configured for these sectors.
Implementati
on
No new configuration is required for NodeBs and eNodeBs.
Issue 01 (2014-01-30)
The restrictions for the three sectors served by two RRU3942

modules are as follows:
The three sectors support a maximum of 16 carriers.
The two RRU3942 modules cannot be installed far away from each
other.
You must modify settings and reconfigure the data for the related
base station if you upgrade the power specifications of these three
sectors to 1x120 W. The modification and reconfiguration require

36
1 Feature Updates
high workload.
Impact

None
Impact on NEs
If two RRU3942 modules are used to serve three sectors, specific
versions of the CME and BSC must be used.
Impact on hardware
None

None

For the GBTS:
The SndRcvMode2 parameter in the SET BTSRXUBP
command for two RRU3942 modules must be set to
FOURDOUBLEFOUR_ANTENNA(Four Feeder[2TX +
4RX]).
For the NodeB:
Two RRU3942 modules must be interconnected and two
interconnection cables are required.

None
Related
Operations
None
Trouble
Ticket
Number
CR-SRAN80-IRF-X06
Feature ID
None
30. RRU3821E Working in UL Mode

Description
Issue 01 (2014-01-30)
The RRU3821E is used in Huawei indoor distributed UMTS or LTE

base stations. The product type of the RRU3821E is pico RRU
(pRRU for short). The RRU3821E works in UL mode and supports
the CPRI MUX topology applied to separate-MPT UL dual-mode
base stations. The RRU3821E is generally used in tunnels or
subways. The following figure shows RRU3821E specification.

37
1 Feature Updates
Implementati
on
Impact
The RRU3821E has the following restrictions:
The RRU3821E works only with the BBU3900.
The RRU3821E is subject to the restrictions of the CPRI MUX

topology applied to separate-MPT multimode base stations.
The RRU3821E supports the CPRI MUX topology applied to

separate-MPT UL dual-mode base stations. The RRU3821E does
not support the CPRI MUX and dual-star topologies applied to coor hybrid-MPT multimode base stations.
The RRU3821E does not support the SRAN8.0 feature

Intermodulation Detection and VSWR Testing.

None
Impact on NEs
The RRU3821E works with specific versions of the CME.
Impact on hardware
None

None

If the CPRI MUX feature is to be activated in separate-MPT
multimode base stations, it can be configured only on the
converged party.
For the GBTS:
The AT parameter has been added to the ADD BTSRXUCHAIN
and MOD BTSRXUCHAIN commands and this parameter must
be set to PEERPORT(peer port). In addition, the values of the
parameters HCN, HSRN, HSN, and HPN in the two commands
must be consistent with those on the converging party's RXU
Issue 01 (2014-01-30)

38
1 Feature Updates
chain or ring.
For the NodeB and eNodeB:
The AT parameter has been added to the ADD RRUCHAIN and
MOD RRUCHAIN commands and this parameter must be set to
PEERPORT(peer port). In addition, the values of the parameters
HCN, HSRN, HSN, and HPN in the two commands must be
consistent with those on the converging party's RXU chain or ring.
For the RRU3821E, the RT and RS parameters in the ADD RRU
command must be set to PRRU and UL(UMTS_LTE),
respectively.

None
Related
Operations
None
Trouble
Ticket
Number
CR-MBTS18-290
Feature ID
None
31. MRFUd (900 MHz and 1800 MHz) Supporting New Power Specifications
Description
The MRFUd operating in the 900 MHz and 1800 MHz frequency
bands supports the power specifications shown in the following
figure.
Implementati
on
The MRFUd operating in the 900 MHz and 1800 MHz frequency
bands supports the power specifications shown in the preceding
figure.
Impact

None
Impact on NEs
This MRFUd works with specific versions of the CME.
Impact on hardware
None

None
Issue 01 (2014-01-30)

39
1 Feature Updates


None
Related
Operations
None
Trouble
Ticket
Number
CR-SRAN80-IRF-X12
Feature ID
None
32. Base Stations Supporting OAM Functions Specified in ITU-T Y.1731

Description
The GBTS, eGBTS, NodeB, and eNodeB now support OAM

functions specified in both the IEEE 802.1ag and ITU-T Y.1731
standards. OAM stands for operations, administration, and
maintenance.
The OAM functions specified in ITU-T Y.1731 include:
For Layer 2 network connectivity checking: Ethernet Continuity

Check (ETH-CC), Ethernet Loopback (ETH-LB), and Ethernet
Link Trace (ETH-LT)
For Layer 2 network connectivity fault management: Ethernet

Alarm Indication Signal (ETH-AIS) and Ethernet Remote Defect
Indication (ETH-RDI)
For Layer 2 network end-to-end performance monitoring: Frame

Loss Management (ETH-LM) and Frame Delay Management
(ETH-DM)
Implementati
on
The GBTS, eGBTS, NodeB, and eNodeB cannot support OAM

functions specified in IEEE 802.1ag and those functions specified in
ITU-T Y.1731 at the same time because the two standards work with
the same MOs. However, the GBTS, eGBTS, NodeB, and eNodeB
can switch standards when required.
Impact

If the ETH-LM function is enabled, the forwarding performance
of boards in target base stations deteriorates.
Impact on NEs
OAM functions specified in ITU-T Y.1731 work with specific
versions of the LMT, M2000, SMT, and BSC.
Impact on hardware
In the GBTS, only the UTRPc supports OAM functions specified
in ITU-T Y.1731.
In the eGBTS, only the UMPT and UTRPc support OAM
Issue 01 (2014-01-30)

40
1 Feature Updates
functions specified in ITU-T Y.1731.

In the NodeB, only the UMPT and UTRPc support OAM
In the eNodeB, only the LMPT, UMPT, and UTRPc support OAM

The following MML commands have been added:
Setting standards for OAM functions:

eGBTS/NodeB/eNodeB: SET ETHOAM
GBTS: SET BTSETHOAM
Querying standards of OAM functions:

eGBTS/NodeB/eNodeB: LST ETHOAM
GBTS: LST BTSETHOAM
Enabling the ETH-LM function:

eGBTS/NodeB/eNodeB: ACT ETHLM
GBTS: ACT BTSETHLM
Disabling the ETH-LM function:

eGBTS/NodeB/eNodeB: DEA ETHLM
GBTS: DEA BTSETHLM
Querying the frame loss situation at a specific time:

eGBTS/NodeB/eNodeB: DSP ETHLM
GBTS: DSP BTSETHLM
Enabling the ETH-DM function:

eGBTS/NodeB/eNodeB: ACT ETHDM
GBTS: ACT BTSETHDM
Disabling the ETH-DM function:

eGBTS/NodeB/eNodeB: DEA ETHDM
GBTS: DEA BTSETHDM
Querying the delay variation at a specific time:

eGBTS/NodeB/eNodeB: DSP ETHDM
GBTS: DSP BTSETHDM
For the GBTS, the following parameters have been added:
In the ADD BTSETHMA command: VLANSWITCH,

VLANPRI, and CCMINTERNAL
In the ADD BTSETHRMMEP command: MAC
In the PING BTSCFM and TRC BTSCFM commands:

DSTTYPE and MAC
No new MOs are added for the ITU-T Y.1731 standard and this
standard works with the MOs that have been allocated to the
IEEE 802.1ag standard. Real-time monitoring items of OAM
functions are expanded.

Issue 01 (2014-01-30)

41
1 Feature Updates

In ALM-25880 Ethernet Link Fault, the CCM LOS Fault, AIS
Fault, and RDI Fault values have been added to the Specific
Problem parameter.
In ALM-25895 Ethernet Trunk Group Fault, the CCM LOS
Fault, AIS Fault, and RDI Fault values have been added to the
Specific Problem parameter.

None
Related
Operations
None
Trouble
Ticket
Number
IR-SRAN80-TRAN-005
Feature ID
None
33. Base Stations Supporting Reporting LLDP Information to the M2000 in Layer 2
Networking
Description
Base stations support reporting Link Layer Discovery Protocol

(LLDP) information to the M2000 in Layer 2 networking. The LLDP
information is used for fault sectionalization on the TranSight.
A new switch has been introduced on the base station side to specify
whether LLDP packets are periodically sent to the M2000.
Implementati
on
Two parameters NOTIFYSW and NOTIFYINTERVAL have been

added to the SET LLDPGLOBALINFO command. When
NOTIFYSW is turned on, the base station sends LLDP packets to the
M2000 once the configuration of the base station or its neighboring
node has changed. The M2000 updates the Layer 2 network topology
accordingly.
Impact

None
Impact on NEs
Reporting LLDP information to the M2000 works with specific
versions of the M2000.
Impact on hardware
None

Two parameters NOTIFYSW and NOTIFYINTERVAL have
been added to the SET LLDPGLOBALINFO command.

Issue 01 (2014-01-30)

42
1 Feature Updates
Impact on configuration management: Two parameters have been

added.

None
Related
Operations
None
Trouble
Ticket
Number
CR-MBTS18-227
Feature ID
None
34. Command Authority Management Scheme

Description
Implementati
on
Impact
Non-MML commands for base stations are granted different

operation authorities.
Defining command groups has been enhanced.
A command navigation tree, which consists of MML commands

and non-MML commands, is provided. The command navigation
tree facilitates command authorization.
Non-MML commands are classified into different groups based on

function items. Command authorization can be performed by
function item.

None
Impact on NEs
The command authority management scheme works with specific
versions of the M2000 and LMT.
Impact on hardware
None

None


None
Related
Operations
Issue 01 (2014-01-30)
Related operations are available on the command authorization

interface on the M2000.

43
1 Feature Updates
Trouble
Ticket
Number
CR-MBTS18-222
Feature ID
None
35. Risky Command List

Description
A list of risky commands has been added to MML Command

Reference. Risky commands are those that may cause service
interruption during execution. With this command list, operators can
quickly determine whether a command is a risky command.
Therefore, the possibility of misoperations is reduced.
Implementati
on
A list of risky commands has been added to MML Command

Reference.
Impact

None
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
CR-MBTS18-042
Feature ID
None
36. Optimized Description of the Parameter Relationship Field in eNodeB Parameter

Reference
Description
Issue 01 (2014-01-30)
The description of the Parameter Relationship field in eNodeB

Parameter Reference has been optimized, improving the document
readability.

44
1 Feature Updates
Implementati
on
The description of the Parameter Relationship field in eNodeB

Parameter Reference has been optimized so that this field covers the
following relationships and situations:
Mutual constraints
If two parameters are mutually constrained, this relationship needs
to be described in both parameters.
Dependencies
When the setting of a parameter depends on the values of one or
more other parameters, the dependency needs to be described in
the dependent parameter. The following is an example:
When RacCfgInd is set to CFG, Rac must be configured. When
RacCfgInd is set to NOT_CFG, Rac does not need to be
configured.
Different default values for different scenarios

When a parameter (X) is constrained by a parameter (Y) in
another command, the default value of parameter X may vary
depending on the setting of parameter Y. In this situation, all the
default values need to be described.
Impact

None
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
CR-MBTS18-084
Feature ID
None
37. Standardized MML Command Navigation Trees for BTSs, NodeBs, and eNodeBs
Description
Issue 01 (2014-01-30)
The MML command navigation trees for BTSs, NodeBs, and

45
1 Feature Updates
eNodeBs have been standardized.

Implementati
on
The MML command navigation trees for BTSs, NodeBs, and

eNodeBs have been standardized. The standardized MML command
navigation trees for NodeBs and eNodeBs differ from those in
SRAN7.0.
Impact

None
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
CR-MBTS18-347
Feature ID
None
38. Standardized SingleRAN Software Version Number for the BTS, NodeB, and eNodeB in
a GSM/UMTS/LTE Multimode Base Station
Description
The BTS, NodeB, and eNodeB in a GSM/UMTS/LTE multimode

base station now have a standardized SingleRAN software version
number: BTS3900 V100R008C00SPCXXX. This facilitates software
version management.
Implementati
on
A standardized SingleRAN software version number has been added.

The LST VER command displays both the single-mode (for example,
eNodeB version V100R006C00SPCXXX or multimode base station
version BTS3900 V100R008C00SPCXXX) and SingleRAN software
versions (for example, BTS3900 V100R008C00SPCXXX) of a base
station.
The LST SOFTWARE command displays only the SingleRAN
software version of a base station.
Impact
Issue 01 (2014-01-30)

46
1 Feature Updates
None
Impact on NEs
The standardized software version for the BTS, NodeB, and
eNodeB works with specific versions of the M2000.
Impact on hardware
None

None


None
Related
Operations
Run the LST VER command to query the single-mode and

SingleRAN software versions of a base station.
Run the LST SOFTWARE command to query the SingleRAN
software version of a base station.
Trouble
Ticket
Number
IR-SRAN80-UMPT-002-SR03-SAR01
Feature ID
None
39. Added the Function of Checking Whether UEs Undetect DCI 0

Description
In earlier versions, the eNodeB does not check whether UEs undetect
downlink control information (DCI) 0.
In the current version, if the eNodeB finds out that a UE undetects DCI
0, the eNodeB adjusts the PDCCH aggregation level, uplink scheduling,
and uplink SINR to reduce the impact on system performance.
Implementatio If the eNodeB finds out that a UE undetects DCI 0, the eNodeB
performs the following operations:
n
1. Adaptively adjusts the PDCCH aggregation level of DCI 0.

2. Performs uplink scheduling again for the initial transmission.
3. Excludes uplink CRC errors due to DCI 0 undetection from the
inputs to SINR adjustment.
Impact

In scenarios where UEs undetect DCI 0:
Shortens uplink delays and increase perceptive rates.
Increases uplink spectral efficiency.
Issue 01 (2014-01-30)
Impact on NEs

47
1 Feature Updates
None
Impact on hardware
None

None

Impact on license: This feature is not license-controlled.

None
Related
Operations

UlSchSwitch parameter set to PuschDtxSwitch:On.
Trouble Ticket DTS2012091905049

Number
Feature ID
None
40. IP Layer Measurement for a Local User-Plane IP Address
Issue 01 (2014-01-30)

48
Description
1 Feature Updates
eNodeBs now support the IP layer measurement for a local user-plane

IP address.
Implementatio The receive and transmit rates of the local user-plane IP address at the
IP layer are sampled per second. At the end of a measurement period,
n
the maximum and average sampling results are reported. The eNodeB
counts the IP header and payload of each packet.
Impact

IP layer measurement can be performed on a maximum of 20 local
user-plane IP addresses at the same time.
Impact on NEs
The CME, M2000 and LMT versions that match the eNodeB
version are required.
Impact on hardware
None

None

Impact on configuration management: For details about the
parameter, MO, or MML command changes, see the corresponding
appendix.
Impact on performance management:
The UserPlaneHostIP object type has been added. For this object
type,
-
The function subset Measurement related to

UserPlaneHostIP has been added to measure the traffic
volume at the local user-plane IP addresses.
The counters in the function subset Measurement related to

UserPlaneHostIP have been added to measure the receive and
transmit rates of a local user-plane IP address at the IP layer
within a measurement period. The rates indicate the IP-layer
load status of the IP address.

None
Related
Operations
Perform the following steps to configure a user-plane link and measure

the performance of the local user-plane IP address:
4. Run the ADD EPGROUP command to add an end point group.

5. Run the ADD USERPLANEHOST command to add a userplane host.
6. (Optional) Run the ADD USERPLANEPEER command to add
a user-plane peer. If users do not run this command to manually
add a user-plane peer, the eNodeB automatically creates such an
object.
7. Configure the object that references the preceding transport
Issue 01 (2014-01-30)

49
1 Feature Updates
resources.
Run the ADD S1 or ADD X2 command to add an S1 or X2 MO,
respectively, that references the transport resources.
The eNodeB automatically sets up the user-plane link.
8. On the M2000, start the IP layer measurement for the local userplane IP address set in step 2.
Trouble Ticket None
Number
Feature ID
CR-MBTS18-135
AR-MBTS18-UMPT-160-SR001-002
41. Performance Measurement Related to Automatically Created User-Plane Transmission

Links
Issue 01 (2014-01-30)

50
Description
1 Feature Updates
In V100R005, during transmission link self-setup, the eNodeB

automatically creates IPPATH MOs for user-plane transmission. Users
can use the counters in the measurement unit Measurement related to
IP path to observe the performance of the automatically created IP
path between each pair of local and peer IP addresses.
In the current version, the MO design has been changed and the
eNodeB does not automatically create IPPATH MOs during
transmission link self-setup. The eNodeB cannot use the counters in the
function subset Measurement related to IP path to observe the
performance of the automatically created user-plane links any more.
The function subset Measurement related to UserPlaneHostIP is
now added to support the IP layer measurement for a local user-plane
IP address. This function subset indicates the performance of the
automatically created user-plane links with the local IP address, which
may communicate with multiple peer IP addresses.
Implementatio The receive and transmit rates of the local user-plane IP address at the
IP layer are sampled per second. At the end of a measurement period,
n
the maximum and average sampling results are reported. The eNodeB
counts the IP header and payload of each packet.
Impact

A total of 384 IPv4 and IPv6 transmission links can be
automatically set up. IP layer measurement can be performed on a
maximum of 20 local user-plane IP addresses at the same time.
Impact on NEs
The CME, M2000 and LMT versions that match the eNodeB
version are required.
Impact on hardware
None

None

Impact on configuration management: For details about the
parameter, MO, or MML command changes, see the corresponding
appendix.
Impact on performance management: The function subset
Measurement related to UserPlaneHostIP has been added to
measure the receive and transmit rates of a local user-plane IP
address at the IP layer within a measurement period. The rates
indicate the IP-layer load status of the IP address.

None
Related
Operations
Perform the following steps to configure a user-plane link and measure

the performance of the local user-plane IP address:
9. Run the ADD EPGROUP command to add an end point group.

10.Run the ADD USERPLANEHOST command to add a userIssue 01 (2014-01-30)

51
1 Feature Updates
plane host.
11.(Optional) Run the ADD USERPLANEPEER command to add
a user-plane peer. If users do not run this command to manually
add a user-plane peer, the eNodeB automatically creates such an
object.
12.Configure the object that references the preceding transport
resources.
Run the ADD S1 or ADD X2 command to add an S1 or X2 MO,
respectively, that references the transport resources.
The eNodeB automatically sets up the user-plane link.
13.On the M2000, start the IP layer measurement for the local userplane IP address set in step 2.
Trouble Ticket None
Number
Feature ID
CR-MBTS18-135
AR-MBTS18-UMPT-160-SR001-002
42. Configurable Capacity Factor for Uplink and Downlink EPF Scheduling
Issue 01 (2014-01-30)

52
1 Feature Updates
Description
Enhanced proportional fair (EPF) scheduling allocates uplink and

downlink physical resources to UEs based on their channel
conditions.
A large value for the Uplink EPF capacity factor or Downlink EPF
capacity factor parameter increases the resources allocated to cell
center users (CCUs), decreases the resources allocated to cell edge
users (CEUs), and increases the cell throughput. A small value for the
Uplink EPF capacity factor or Downlink EPF capacity factor
parameter increases the resources allocated to CEUs, decreases the
resources allocated to CCUs, and decreases the cell throughput.
Implementati
on
When the eNodeB uses the EPF scheduling algorithm to calculate

uplink and downlink scheduling priorities for UEs, capacity factors
are considered as well as the spectral efficiency of UEs. By this
means, UEs under different channel conditions are allocated a
different amount of uplink and downlink physical resources, and
therefore cell capacity and coverage are adjusted. The larger the
capacity factor value, the more resources are allocated to UEs under
good channel conditions.
Impact

If the Uplink EPF capacity factor or Downlink EPF
capacity factor parameter is set to the default value 1, cell
capacity and performance are not affected after an upgrade.
capacity factor parameter is set to a value greater than 1, the
uplink or downlink scheduling priorities for CCUs are higher
and uplink or downlink cell throughput may increase after an
upgrade.
capacity factor parameter is set to a value less than 1, the
uplink or downlink scheduling priorities for CEUs are higher
and uplink or downlink cell throughput may decrease after an
upgrade.
Impact on NEs
None
Impact on hardware
None

None

The Uplink EPF capacity factor is added in the
CELLULSCHALGO MO and the Downlink EPF capacity
factor parameter is added in the CellDlschAlgo MO to configure
the capacity factor for uplink and downlink EPF scheduling,
respectively.
The Uplink EPF capacity factor parameter is added in
V100R006 and can be set to the following six values:
Issue 01 (2014-01-30)

53
1 Feature Updates
EPF_CAPC_FACTOR_1(1),
EPF_CAPC_FACTOR_0DOT01(0.01),
EPF_CAPC_FACTOR_2(2), EPF_CAPC_FACTOR_3(3), and
EPF_CAPC_FACTOR_4(4).
The Uplink EPF capacity factor parameter is valid if the Uplink
scheduling Strategy parameter is set to
ULSCH_STRATEGY_EPF(EPF).
The Downlink EPF capacity factor parameter is valid if the
Downlink scheduling Strategy parameter is set to
DLSCH_PRI_TYPE_EPF(EPF).
In V100R005, the Downlink EPF capacity factor parameter is a
reserved parameter and can be set to 0.01, 0.5, 1, 2, 3, 4, or 5. In
V100R006C00, this parameter can be set to the following six
values: EPF_CAPC_FACTOR_1(1),
EPF_CAPC_FACTOR_2(2), EPF_CAPC_FACTOR_3(3), and
If the Downlink EPF capacity factor parameter is set to 5 in
V100R005, this value automatically maps to
EPF_CAPC_FACTOR_4(4) after an upgrade to V100R006C00.
If this parameter is set to a value other than 5, the parameter value
does not change after an upgrade from V100R005 to
V100R006C00.

None
Related
Operations
Run the MOD CELLDLSCHALGO command with the Downlink

EPF capacity factor parameter set to EPF_CAPC_FACTOR_1(1),
EPF_CAPC_FACTOR_2(2), EPF_CAPC_FACTOR_3(3), or
Run the MOD CELLULSCHALGO command with the Uplink
EPF capacity factor parameter set to EPF_CAPC_FACTOR_1(1),
EPF_CAPC_FACTOR_2(2), EPF_CAPC_FACTOR_3(3), or
Trouble
Ticket
Number
DTS2012112306973
Feature ID
LOFD-001015
43. Inter-PLMN Handover to a Cell of an Equivalent PLMN
Issue 01 (2014-01-30)

54
1 Feature Updates
Description
The equivalent public land mobile network (PLMN) information is

delivered from the mobility management element (MME) to a UE.
The UE then can initiate an inter-PLMN handover to a cell of an
equivalent PLMN. Therefore, the handover configuration is
simplified and the handover success rate increases.
Implementati
on
When the eNodeB selects a target cell for the UE during a handover,
a cell of an equivalent PLMN is added to the candidate target cell list.
Impact

This feature increases the number of candidate target cells for
handovers and therefore increases the handover success rate.
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
IREQ00000073
Feature ID
LBFD-002018
44. LCS-triggered SRVCC to Another System for CSFB

Description
When an LTE network supports voice over Internet Protocol (VoIP)

services but does not support location service (LCS), the MME
delivers a circuit switched fallback (CSFB) indicator to instruct the
UE to fall back to an inter-RAT system. In addition to an inter-RAT
PS handover, the LTE network also supports an SRVCC procedure
for CSFB. A new switch is added to control whether a PS handover
or SRVCC procedure is used for CSFB.
Implementati
on
In the EnodeBAlgoSwitch MO, the

LcsSrvccSwitch(LcsSrvccSwitch) option is added to the
HoModeSwitch parameter. The LcsSrvccSwitch(LcsSrvccSwitch)
option is used to control the CSFB method. If the
LcsSrvccSwitch(LcsSrvccSwitch) option of the HoModeSwitch
Issue 01 (2014-01-30)

55
1 Feature Updates
parameter is selected, the eNodeB performs SRVCC for CSFB.

Impact

This feature may affect the values of the L.CSFB.PrepAtt and
L.CSFB.PrepSucc counters. If the
LcsSrvccSwitch(LcsSrvccSwitch) option of the HoModeSwitch
parameter is selected and services with QCI 1 exist in the
network, the values of both the counters are smaller than those
measured in versions earlier than V100R008C00.
Impact on NEs
None
Impact on hardware
None

None

Impact on the configuration management: The
LcsSrvccSwitch(LcsSrvccSwitch) option is added to the
HoModeSwitch parameter in the EnodeBAlgoSwitch MO.

None
Related
Operations
Run the MOD ENODEBALGOSWITCH command with the

LcsSrvccSwitch(LcsSrvccSwitch) check box selected under the
HoModeSwitch parameter.
Trouble
Ticket
Number
None
Feature ID
LOFD-001033
LOFD-001034
45. Release Mode of Base Station Software Package

Description
The software packages for single-mode and multimode base stations

are released together, and you can obtain a specific software package
for each site as required.
Implementati
on
Each SRAN8.0 release contains four software packages at

http://support.huawei.com/, which are used for MBTS, GBTS,
NodeB, and eNodeB, respectively. They have a normalized software
version number BTS3900 V100R008SPCXXX or BTS3900
V100R008SPHXXX. For example, BTS3900
V100R008C00SPC100.zip, BTS3900
V100R008C00SPC100_GBTS.zip, BTS3900
V100R008C00SPC100_NodeB.zip, and BTS3900
Issue 01 (2014-01-30)

56
1 Feature Updates
V100R008C00SPC100_eNodeB.zip.
Impact

None
Impact on NEs
This feature works with specific versions of the M2000.
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
CR-MBTS18-330
Feature ID
None
CR-MBTS18-378
46. Base Station Supporting Disabled USB Port

Description
USB ports of a base station are enabled by default. When USB ports
are not required, you can disable them to improve base station
security.
This feature applies only to USB ports used for software loading.
Implementati
on
You can enable or disable a USB port by running an MML command.

After a USB port is disabled, the base station will not read the USB
flash drive when it is inserted.
After a USB port is enabled, the base station will read the USB flash
drive and start software loading.
When a USB port is enabled or disabled, EVT-26843 USB Port State
Changed is reported.
Impact

None
Impact on NEs
This feature works with specific versions of the CME.
Issue 01 (2014-01-30)
Impact on hardware

57
1 Feature Updates
None

The MML command SET LOCALUSBPORT is added.

Impact on configuration management: The SWITCH parameter is
added. To enable a USB port, set this parameter to 1. To disable a
USB port, set this parameter to 0.
Impact on fault management: EVT-26843 USB Port State
Changed is added.

None
Related
Operations
Run the SET LOCALUSBPORT command to enable or disable a

USB port.
Trouble
Ticket
Number
CR-MBTS18-306
Feature ID
None
47. LMT Rights Management Solution

Description
Users are authorized by function item on the LMT. In this way, the
problem of excessive authorization is solved.
Implementati
on
14.A command navigation tree is provided to facilitate user

authorization.
15.Users are authorized by function item.
16.Commands related to function items can be queried in the
command list.
17.Binary commands are classified into different command groups
by function item.
For details, see 3900 Series Base Station LMT User Guide.
Impact

None
Impact on NEs
This feature works with specific versions of the LMT.
Impact on hardware
None

None

Issue 01 (2014-01-30)

58
1 Feature Updates


None
Related
Operations
Users are authorized by function item on the LMT.
Trouble
Ticket
Number
CR-MBTS18-222
Feature ID
None
48. Normalized Names of Fields with the Same Content in Southbound and Northbound
Documentation
Description
Names of fields with the same content are normalized in southbound

and northbound documentation.
Implementati
on
18.The Performance Counter Reference Summary field in

BTS3900 V100R008C00SPC100 (eNodeB) Performance
Counter Reference is changed to Performance Counter List,
which is the same as that in the northbound documentation.
19.The BTS3900 V100R008C00SPC100 (eNodeB) Performance
Counter Changes template is updated and field names in this
template are changed to the same as those in the northbound
documentation.
Impact

None
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
Issue 01 (2014-01-30)
None

59
1 Feature Updates
Trouble
Ticket
Number
CR-MBTS18-205
Feature ID
None
1.2 Modified Features

1.
Optimized Blind Redirection When Neighbor Relationships Are Not Configured or

Neighboring Cells for Blind Handovers Are Not Specified
Description
In V100R005C00, blind redirection can be performed only when

correct neighbor relationships have been configured and cells for
blind handovers have been specified. In V100R008C00, blind
redirection can now be performed when neighbor relationships are
not configured or cells for blind handovers are not specified. This
helps reduce O&M costs for operators.
Implementati
on
eNodeBs do not check neighboring cell configurations before

triggering redirection. Before delivering a blind-redirection
command, an eNodeB selects the frequency with the highest priority
for RRC_CONNECTED UEs as the target frequency and includes the
frequency in the command.
Impact
Impact on performance
The feature modification does not affect the networks where
correct neighbor relationships have been configured. Network
performance is not affected after an upgrade to the current release.
In a new network where neighbor relationships are not configured
or cells for blind handovers are not specified, eNodeBs can trigger
blind redirection procedures. If inter-RAT neighboring cells are
not configured, however, an eNodeB cannot send RAN
information management (RIM) requests to such cells to
implement fast redirection or flash circuit switched fallback
(CSFB). Delay in redirection or CSFB in this case is longer than
that in fast redirection or flash CSFB.
Impact on NEs
None
Impact on hardware
None

None

Neighbor relationship configurations are not required on eNodeBs
where only redirection is enabled. This reduces the workload of
neighboring cell management. The new parameter
ConnFreqPriority must be configured. The PLMNs that share a
Issue 01 (2014-01-30)

60
1 Feature Updates
neighboring frequency must be set in EutranNFreqRanShare,

UtranRanShare, or GeranRanShare MOs.

If inter-RAT neighboring cells are not configured, the eNodeB
cannot trigger RIM procedures. Therefore, the RIM-related
features such as LOFD-001052 Flash CS Fallback to UTRAN and
LOFD-001053 Flash CS Fallback to GERAN cannot be used. In
addition, handover and Single Radio Voice Call Continuity
(SRVCC) do not work, and the features LOFD-001022 SRVCC to
UTRAN and LOFD-001023 SRVCC to GERAN cannot be used.
Related
Operations
When neighboring cells are not configured, you must set the PLMN
attributes for frequencies as follows:
For E-UTRAN frequencies, run the MML command MOD

EUTRANRANSHARE with Mcc and Mnc set to proper
values.
For UTRAN frequencies, run the MML command MOD

UTRANRANSHARE with Mcc and Mnc set to proper
values.
For GERAN frequencies, run the MML command MOD

GERANRANSHARE with Mcc and Mnc set to proper
values.
Assign the priority for RRC_CONNECTED UEs to frequencies as

follows:
For E-UTRAN frequencies, run the MML command MOD

EUTRANINTERNFREQ with ConnFreqPriority set to a
proper value.
For UTRAN frequencies, run the MML command MOD

UTRANNFREQ with ConnFreqPriority set to a proper
value.
For GERAN frequencies, run the MML command MOD

GERANINTERNFREQ with ConnFreqPriority set to a
proper value.
Trouble
Ticket
Number
IR-0000091355
Feature ID
None
2.
Number of Used Downlink PRBs in the TM1 Scenario Now Measured in the Counter
L.ChMeas.MIMO.PRB.OL.Rank1
Description
The counter L.ChMeas.MIMO.PRB.OL.Rank1 can now measure the

number of used downlink physical resource blocks (PRBs) in
transmission mode 1 (TM1). Transmit diversity is used in this
scenario.
This counter is used to measure the total number of used downlink
PRBs in open-loop rank 1 mode.
Implementati
Issue 01 (2014-01-30)
The number of used downlink PRBs in the TM1 scenario is included

61
1 Feature Updates
on
in the counter L.ChMeas.MIMO.PRB.OL.Rank1, whose counter ID

is 1526727393.
Impact

None
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
DTS2012080800913
Feature ID
None
3.
More Operator-specific Counters Added for RAN Sharing Situations
Description
More operator-specific counters have been added in V100R008C00.

The counters measure the maximum number of users and outgoing
handovers, including intra-frequency, inter-frequency, inter-RAT, and
X2-based handovers.
The addition of operator-specific counters facilitates fault location
and proportion adjustment for resource allocation between operators.
Implementati
on
Operator-specific counters have been added.
Impact

None
Impact on NEs
This feature is implemented on the eNodeB and M2000.
Impact on hardware
None
Issue 01 (2014-01-30)

62
1 Feature Updates
None

Impact on license: The existing cell-level license for this feature is
still applicable. The enhancement of this feature has no impact on
the license.
The following 34 operator-specific counters have been added:
Measurement related to the number of User for the Operator
(Traffic.User.Cell.Operator)
L.Traffic.User.Max.PLMN
Measurement related to Intra eRan HOOUT for the operator
(HO.eRAN.Out.Cell.Operator)
L.HHO.IntraeNB.IntraFreq.PrepAttOut.PLMN
L.HHO.IntraeNB.InterFreq.PrepAttOut.PLMN
L.HHO.IntraeNB.IntraFreq.ExecAttOut.PLMN
L.HHO.IntraeNB.InterFreq.ExecAttOut.PLMN
L.HHO.IntraeNB.IntraFreq.ExecSuccOut.PLMN
L.HHO.IntraeNB.InterFreq.ExecSuccOut.PLMN
L.HHO.IntereNB.IntraFreq.PrepAttOut.PLMN
L.HHO.IntereNB.InterFreq.PrepAttOut.PLMN
L.HHO.IntereNB.IntraFreq.ExecAttOut.PLMN
L.HHO.IntereNB.InterFreq.ExecAttOut.PLMN
L.HHO.IntereNB.IntraFreq.ExecSuccOut.PLMN
L.HHO.IntereNB.InterFreq.ExecSuccOut.PLMN
L.HHO.BlindHO.PrepAttOut.PLMN
L.HHO.BlindHO.ExecAttOut.PLMN
L.HHO.BlindHO.ExecSuccOut.PLMN
L.HHO.X2.IntraFreq.PrepAttOut.PLMN
L.HHO.X2.InterFreq.PrepAttOut.PLMN
L.HHO.X2.IntraFreq.ExecAttOut.PLMN
L.HHO.X2.InterFreq.ExecAttOut.PLMN
L.HHO.X2.IntraFreq.ExecSuccOut.PLMN
L.HHO.X2.InterFreq.ExecSuccOut.PLMN
Measurement related to IRATHOOUT for the operator

(HO.IRAT.Out.Cell.Operator)
L.IRATHO.E2W.PrepAttOut.PLMN
L.IRATHO.E2W.ExecAttOut.PLMN
L.IRATHO.E2W.ExecSuccOut.PLMN
L.IRATHO.E2G.PrepAttOut.PLMN
L.IRATHO.E2G.ExecAttOut.PLMN
L.IRATHO.E2G.ExecSuccOut.PLMN
Issue 01 (2014-01-30)

63
1 Feature Updates
L.IRATHO.BlindHO.E2W.PrepAttOut.PLMN
L.IRATHO.BlindHO.E2G.PrepAttOut.PLMN
L.IRATHO.BlindHO.E2W.ExecAttOut.PLMN
L.IRATHO.BlindHO.E2W.ExecSuccOut.PLMN
L.IRATHO.BlindHO.E2G.ExecAttOut.PLMN
L.IRATHO.BlindHO.E2G.ExecSuccOut.PLMN

None
Related
Operations
None
Trouble
Ticket
Number
IR-0000097993
Feature ID
LOFD-001036
LOFD-001037
4.
One-Minute Real-time Monitoring for More Counters
Description
More counters can now be monitored in real time for one minute in
V100R008C00, compared with V100R005. These counters mainly
relate to access, mobility, retainability, and traffic volume. In
addition, seven redundant counters have been removed.
Implementati
on
85 counters have been added for one-minute real-time monitoring on

the M2000. Seven redundant counters have been removed.
Impact

This feature affects network performance because of the short
reporting period and large amount of data. The system
specifications allow a maximum of 25 counters to be monitored in
real time for one minute for each eNodeB.
Impact on NEs
This feature is implemented on the eNodeB and M2000.
Impact on hardware
None

None

Issue 01 (2014-01-30)
The following 85 counters that support 1-minute real-time

monitoring have been added:

64
1 Feature Updates
L.RRC.ConnReq.Msg
L.RRC.ConnReq.Att
L.RRC.ConnSetup
L.RRC.ConnReq.Succ
L.RRC.SetupFail.Rej
L.RRC.ReEst.Att
L.RRC.ReEst.Succ
L.RRC.ReEstFail.Rej
L.E-RAB.SuccEst
L.E-RAB.AttEst
L.S1Sig.ConnEst.Att
L.S1Sig.ConnEst.Succ
L.E-RAB.InitAttEst
L.E-RAB.InitSuccEst
L.E-RAB.AbnormRel
L.E-RAB.NormRel
L.E-RAB.AbnormRel.Radio
L.E-RAB.AbnormRel.TNL
L.E-RAB.AbnormRel.Cong
L.E-RAB.AbnormRel.HOFailure
L.E-RAB.AbnormRel.MME
L.E-RAB.AbnormRel.eNBTot
L.E-RAB.FailEst.NoReply
L.E-RAB.FailEst.MME
L.E-RAB.FailEst.TNL
L.E-RAB.FailEst.RNL
L.E-RAB.FailEst.NoRadioRes
L.E-RAB.FailEst.SecurModeFail
L.Traffic.DRB
L.Thrp.bits.UL
L.Thrp.Time.UL
L.Thrp.bits.DL
L.Thrp.Time.DL
L.Thrp.bits.UL.Max
L.Thrp.bits.DL.Max
L.Thrp.bits.DL.SRB
L.Thrp.bits.UL.SRB
L.Thrp.Time.Cell.DL
L.Thrp.Time.Cell.UL
L.E-RAB.SessionTime.UE
L.Paging.S1.Rx
Issue 01 (2014-01-30)

65
1 Feature Updates
L.Paging.UU.Att
L.Paging.UU.Succ
L.Paging.Dis.Num
L.Paging.UU.SIUpdate
L.SecurMode.S1.Rx
L.SecurMode.Cmd
L.SecurMode.Cmp
L.SecurMode.Fail
L.RA.GrpA.Att
L.RA.GrpA.Resp
L.RA.GrpB.Att
L.RA.GrpB.Resp
L.RA.Dedicate.Att
L.RA.Dedicate.Resp
L.DLPwr.Max
L.DLPwr.Avg
L.UL.Interference.Max
L.UL.Interference.Avg
L.Traffic.User.Avg
L.Traffic.User.Max
L.Traffic.CEU.Avg
L.Traffic.CEU.Max
L.Traffic.User.ULData.Avg
L.Traffic.User.ULData.Max
L.Traffic.User.DLData.Avg
L.Traffic.User.DLData.Max
L.Traffic.User.Ulsync.Avg
L.Traffic.User.Data.Max
L.Traffic.User.Data.Avg
L.HHO.IntraeNB.IntraFreq.PrepAttOut
L.HHO.IntraeNB.IntraFreq.ExecAttOut
L.HHO.IntraeNB.IntraFreq.ExecSuccOut
L.HHO.IntraeNB.InterFreq.PrepAttOut
L.HHO.IntraeNB.InterFreq.ExecAttOut
L.HHO.IntraeNB.InterFreq.ExecSuccOut
L.HHO.IntereNB.IntraFreq.PrepAttOut
L.HHO.IntereNB.IntraFreq.ExecAttOut
L.HHO.IntereNB.IntraFreq.ExecSuccOut
L.HHO.IntereNB.InterFreq.PrepAttOut
L.HHO.IntereNB.InterFreq.ExecAttOut
L.HHO.IntereNB.InterFreq.ExecSuccOut
Issue 01 (2014-01-30)

66
1 Feature Updates
L.HHO.Prep.FailOut.MME
L.HHO.Prep.FailOut.NoReply
L.HHO.Prep.FailOut.PrepFailure
The following counters have been exited because they can be

substituted with or calculated from the new counters:
Service RRC Connect Success Rate
E-RAB Establish Success Rate
Intra-frequency Handover Success Rate
Inter-frequency Handover Success Rate
Handover from E-UTRAN to CDMA2000 Success Rate
Handover from E-UTRAN to WCDMA Success Rate
Handover from E-UTRAN to GERAN Success Rate

None
Related
Operations
None
Trouble
Ticket
Number
IREQ00000095
Feature ID
None
5.
PLMN Broadcast in RR Mode Enhanced for RAN Sharing Situations
Description
PLMN broadcast in round robin (RR) mode has been available since
V100R003C00. Before, users could only set the PLMN broadcast
period, but users can now set the start time for broadcast as well.
With this enhancement, a PLMN ID broadcast sequence at a certain
time can be synchronized between certain cells.
Implementati
on
When the BroadcastMode parameter in the CellAccess MO is set to

RR_MODE(Round Robin Mode), the eNodeB broadcasts PLMN
IDs in the cell based on the current eNodeB time, start time for
broadcast, and broadcast period.
Impact

None
Impact on NEs
This feature is implemented on the eNodeB and CME.
Impact on hardware
None

None
Issue 01 (2014-01-30)

67
1 Feature Updates

the license.
Impact on configuration management: A new parameter
RoundActionTime parameter has been added to the CellAccess
MO. Year, month, day, and hour in this parameter can be set to
non-zero values, and minute and second in this parameter must be
set to zeros.

None
Related
Operations
Run the MML command MOD CELLACCESS with

RoundActionTime set to an appropriate value.
Trouble
Ticket
Number
IR-0000121898
Feature ID
LOFD-001036
6.
PLMN Information Indicated in Traced User-level Messages over the Uu, S1, and X2
Interfaces
Description
In versions earlier than V100R008C00, the PLMN ID in traced X2

messages identifies the PLMN of the primary operator, and traced S1
and Uu messages do not indicate any PLMN information. In
V100R008C00, traced user-level Uu, S1, and X2 messages indicate
the PLMN information about each user. In this way, user signaling
procedures can be observed on a per PLMN basis. The limitations of
this function are as follows:
Cell-level messages (such as paging and broadcast messages) and

eNodeB-level messages do not indicate the PLMN information
because such messages are not PLMN-specific.
User-level messages are not buffered so that the messages are

always transmitted in real time. The first message after an incoming
S1- or X2-based handover does not indicate the PLMN information
about the user. Operators can learn the PLMN information from
other messages with the same CALLID.
Implementati
on
The eNodeB identifies the PLMN information about each user during
Uu, S1, or X2 interface tracing. The eNodeB then binds the PLMN
information with the CALLID so that the PLMN information can be
indicated in the traced user-level messages.
Impact

None
Impact on NEs
A column has been added to indicate the PLMN information for
S1, X2, and Uu interface tracing on the M2000 client.
Issue 01 (2014-01-30)

68
1 Feature Updates
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
IR-00000092
Feature ID
LBFD-004001
7.
Enhanced ANR Between LTE and CDMA2000 1xRTT or HRPD
Description
The automatic neighbor relation (ANR) function between LTE and

CDMA2000 1xRTT or high rate packet data (HRPD) has been
enhanced as follows:
eNodeBs can detect new CDMA2000 cells based on measurement

reports sent by UEs and automatically add the cells to neighboring
cell lists (NCLs) and neighboring relation tables (NRTs).
Neighboring CDMA2000 cells can be automatically removed from

eNodeBs.
ANR between LTE and CDMA2000 can be configured and queried

on the GUI.
The self-organizing network (SON) logs for ANR between LTE and
CDMA2000 can be recorded, queried, and exported.
A confirmation mechanism has been introduced to ANR for adding

or removing entries to or from NRTs.
These enhancements reduce the workload of manually managing

neighbor relationships.
Implementati
on
Issue 01 (2014-01-30)
Switches and parameters for ANR between LTE and CDMA2000

can be set and queried by running eNodeB MML commands.
An eNodeB issues ANR-related measurement configurations to

UEs that support measurement of CDMA2000 cells. If the eNodeB
detects new CDMA2000 cells, it instructs the UEs to report the
global cell identities (GCIs) of the cells. The eNodeB then
automatically adds the CDMA2000 cells to the NCLs and NRTs.
Using ANR, eNodeBs can automatically remove outdated

69
1 Feature Updates
neighboring CDMA2000 cells.
Impact
The M2000 is used to query or export the SON logs for ANR.
Suggestions for adding or removing entries to or from NRTs are

reported to the M2000. Neighboring cells can be added or removed
only after operators accept the suggestions.

This enhancement is disabled by default, and therefore it does not
affect network upgrades.
The overall impact of this enhancement is minor. The service drop
rate may increase at the beginning, but is expected to decrease
after neighboring cells are added. The throughput may decrease
because inter-RAT measurement is required.
Impact on NEs
This enhancement is implemented on the eNodeB and M2000.
UEs must support the measurement of neighboring CDMA2000
cells.
Impact on hardware
None

None

Impact on license: The existing eNodeB-level license for this
feature is still applicable. The enhancement of this feature has no
impact on the license.
Impact on configuration management: A new switch
CdmaEventAnrSwitch(CdmaEventAnrSwitch) has been added
to the AnrSwitch parameter in the ENodeBAlgoSwitch MO.

None
Related
Operations
Run the MML command MOD ENODEBALGOSWITCH with the

CdmaEventAnrSwitch(CdmaEventAnrSwitch) check box selected
under the AnrSwitch parameter.
Trouble
Ticket
Number
IR-0000107833
Feature ID
None
8.
Parameters for Specifying UMTS Cells Changed for Consistency
Description
Issue 01 (2014-01-30)
Parameters for specifying UMTS cells have been changed so that the
parameter names are the same as those in the RNC MML commands.
This facilitates the maintenance of UMTS cells and improves user

70
1 Feature Updates
experience.
Implementati
on
Impact
The UtranCellId parameter has been changed into parameters

CellId and RncId in the UtranExternalCell, UtranNCell, and
UtranExternalCellPlmn MOs.
The ANR management interface on the M2000 client has been

modified to support UMTS cell query after the parameter change.

None
Impact on NEs
This feature is implemented on the eNodeB, M2000, and CME.
Impact on hardware
None

None

Impact on configuration management: The UtranCellId
parameter has been changed into parameters CellId and RncId in
the UtranExternalCell, UtranNCell, and
UtranExternalCellPlmn MOs.

None
Related
Operations
Run the MML command ADD UTRANEXTERNALCELL with

RncId and CellId set to appropriate values.
Run the MML command ADD UTRANNCELL with RncId and

CellId set to appropriate values.
Run the MML command ADD

UTRANEXTERNALCELLPLMN with RncId and CellId set to
appropriate values.
Trouble
Ticket
Number
IR-0000102240
Feature ID
None
9.
A New MO Added for Setting Handover Policies for CSFB
Description
The handover policy for CSFB can now be specified by a new

parameter. Therefore, operators can separately set handover policies
for PS services and CSFB.
Implementati
on
A new MO CSFallBackPolicyCfg has been added. All handover

methods are enabled for CSFB services by default.
Issue 01 (2014-01-30)

71
1 Feature Updates
Impact

None
Impact on NEs
This feature is implemented on the eNodeB and CME.
Impact on hardware
None

None

Impact on configuration management: A new MO
CSFallBackPolicyCfg has been added.

None
Related
Operations
Run the MML command MOD CSFALLBACKPOLICYCFG with

CsfbHoPolicyCfg set to an appropriate value.
Trouble
Ticket
Number
IREQ00000101
Feature ID
None
10. Enhanced PCI Automated Configuration

Description
Automated configuration of physical cell identities (PCIs) provided

by the CME assigns appropriate PCIs to LTE cells. PCI automated
configuration has been enhanced in V100R008C00 as follows:
Antenna information can be obtained from the engineering

parameter data file. Therefore, PCI automated configuration is
applicable even when remote electrical tilt (RET) antennas are not
deployed or the antenna information cannot be obtained from the
NE configurations.
If the antenna information is obtained from the engineering

parameter data file or NE configurations, PCI automated
configuration enables the DL reference signal (RS) of neighboring
cells to be transmitted at different frequency-domain locations
whenever possible. This improves DL RS quality when system load
is low.
The frequency-domain location of DL RS in a cell is determined by the PCI of
the cell and other factors.
Implementati
on
Issue 01 (2014-01-30)
NE engineering parameters are imported to the CME as a data file.

The parameters include eNodeB coordinates of latitude and

72
1 Feature Updates
longitude, antenna azimuth, and antenna beamwidth. PCI

automated configuration preferentially obtains antenna information
from the engineering parameter data file. If no required information
can be found, PCI automated configuration attempts to obtain the
information from the NE configurations.
Impact
If the antenna information still cannot be obtained from the NE

configurations, PCI automated configuration assigns the LTE cell a
PCI that does not cause PCI collision or confusion. In this case, PCI
automated configuration does not ensure that the DL RS of the cell
is transmitted at a different frequency-domain location than
neighboring cells.

None
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
Users can import a data file that contains antenna engineering

parameters to the CME.
Trouble
Ticket
Number
IR-0000080892
Feature ID
None
11. Higher Spectrum Scan Efficiency

Description
Spectrum scan collects uplink spectrum data from specified radio

frequency (RF) modules. By analyzing the collected data, users can
preliminarily determine whether there is uplink interference and, if
there is interference, determine the interference pattern. This
enhancement in V100R008C00 improves the spectrum scan
efficiency in the case of multi-RAT or multi-channel RF modules.
Implementati
on
Users can specify the channel and RAT when performing a spectrum
scan. Only the data related to the specified channel or RAT will be
reported.
Issue 01 (2014-01-30)

73
1 Feature Updates
Impact

None
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
IR-0000115777
Feature ID
None
12. Enhanced Inter-Frequency Load Balancing

Description
The amount of cell load to be transferred between cells within a load

balancing period has been increased for inter-frequency load
balancing. A heavily loaded cell can quickly reduce its load by
transferring a large amount of load to another cell.
Implementati
on
A new parameter LoadTransferFactor has been added to the

CellMLB MO. The value of this parameter determines the increased
amount of cell load that can be transferred within a load balancing
period.
Impact

This enhancement is disabled by default (the
LoadTransferFactor parameter is set to 0), and therefore does
not affect network upgrades.
A larger value of the LoadTransferFactor parameter results in a
larger amount of load being transferred and faster cell load
reduction, but leads to a weaker resistance to load fluctuations and
therefore a higher probability of ping-pong handovers. A smaller
value has opposite effects.
Impact on NEs
None
Issue 01 (2014-01-30)

74
1 Feature Updates
Impact on hardware
None

None

the license.
LoadTransferFactor has been added to the CellMLB MO.

None
Related
Operations
Run the MML command MOD CELLMLB with

LoadTransferFactor set to an appropriate value.
Trouble
Ticket
Number
IREQ00000108
Feature ID
LOFD-001032
13. Optimized Parameter Display for Setting Forced Entry into Lower Power Consumption
Mode
Description
The feature LOFD-001040 Low Power Consumption Mode enables

eNodeBs to enter low power consumption mode when the mains
power supply is disconnected. In low power consumption mode,
channels on RF modules are shut down and certain cells go out of
service to help extend the in-service time of an eNodeB powered by
batteries. With V100R005C00, users can enable forced entry into low
power consumption mode by setting the LowPwrOrder parameter to
ON(On). The eNodeB then does not consider the StartTime and
StopTime parameter values. Therefore, these parameters do not need
to be configured. In V100R008C00, the parameters StartTime and
StopTime are no longer displayed when the LowPwrOrder
parameter is set to ON(On). This prevents user confusion by
StartTime and StopTime.
Implementati
on
A checking mechanism has been introduced so that the parameters

StartTime and StopTime are not displayed when the LowPwrOrder
parameter is set to ON(On).
Impact

None
Impact on NEs
None
Issue 01 (2014-01-30)
Impact on hardware

75
1 Feature Updates
None

This enhancement requires modifications on the CME.

the license.

None
Related
Operations
Run the MML command MOD CELLLOWPOWER with

LowPwrOrder set to ON(On). The parameters StartTime and
StopTime are not displayed, and therefore, users do not need to
specify them.
Trouble
Ticket
Number
DTS2012091103519
Feature ID
LOFD-001040
DTS2012083005216
14. Enhanced Emergency Redirection

Description
In V100R005C00, emergency redirection transfers UEs to inter-RAT

cells to prevent service drops when the signal quality of the serving
cell quickly deteriorates. In V100R008C00, the target cell for a
redirection can also be an inter-frequency LTE cell. The thresholds
for triggering a redirection must be set to the same values in
V100R008C00 and V100R005C00.
Implementati
on
The parameters BlindHoA1A2ThdRsrq and

BlindHoA1A2ThdRsrp in the CellHoParaCfg MO have been
introduced to specify the RSRQ and RSRP thresholds, respectively,
for triggering a redirection. Other triggering conditions are specified
by parameters InterRatHoA1A2Hyst and
InterRatHoA1A2TimeToTrig.
Impact

Two A1 measurement reports are added for UEs that have newly
accessed, been handed over to, or reestablished RRC connections
to a cell.
Impact on NEs
None
Impact on hardware
None
Issue 01 (2014-01-30)

76
1 Feature Updates
None

Impact on performance management: This enhancement affects
the following counters:
Number of Redirections in the E-UTRAN
L.RRCRedirection.IntraLTE
Number of Inter-RAT Redirections from E-UTRAN to Another
System
L.RRCRedirection.E2W
L.RRCRedirection.E2G

None
Related
Operations
Run the MML command MOD CELLHOPARACFG with

BlindHoA1A2ThdRsrq and BlindHoA1A2ThdRsrp set to
appropriate values.
Trouble
Ticket
Number
None
Feature ID
LBFD-002018
15. Optimized GUI for MLB Monitoring

Description
Users can monitor mobility load balancing (MLB) on the M2000 by

specifying the information about the local cell and neighboring cells.
In V100R008C00, the GUI for MLB monitoring has been optimized
so that the information about the local cell and each neighboring cell
to be specified is displayed in separate group boxes. If there are any
null values in the MLB monitoring results, the null values will be
displayed as N/A.
Implementati
on
Code for the M2000 GUI has been modified so that the information
about the local cell and each neighboring cell can be specified in
separate group boxes.
In the MLB monitoring results, any null values are displayed as

N/A. This may occur when incorrect information has been entered,
the specified cell is abnormal, or MLB is disabled.
Impact
None
Impact on NEs
None
Issue 01 (2014-01-30)

77
1 Feature Updates
Impact on hardware
None

None

Impact on license: The existing user-level license for this feature
is still applicable. The enhancement of this feature has no impact
on the license.

None
Related
Operations
None
Trouble
Ticket
Number
DTS2012072302749
Feature ID
LOFD-001032
LOFD-001044
LOFD-001045
16. Standalone BS-SMARTT

Description
The RF test function in the LMT is now provided by a standalone tool

Base Station Statics Maintenance Advanced RF Test Tool (BSSMARTT). Using this tool reduces the possible risks, such as
hardware damage, caused by misoperations.
Implementati
on
Users can download this tool from http://support.huawei.com to test

downlink transmit power. Contact Huawei technical support if you
need to obtain other RF performance indicators.
Impact

None
Impact on NEs
None
Impact on hardware
None

None

Issue 01 (2014-01-30)

78
1 Feature Updates


None
Related
Operations
None
Trouble
Ticket
Number
DTS2013010602833
Feature ID
None
17. Optimized MCS Selection for Downlink Services with QCI 5

Description
3GPP TS 23.203 suggests that QoS class identifier (QCI) 5 be used

for IP multimedia subsystem (IMS) signaling. In V100R008C00, the
modulation and coding scheme (MCS) selection is optimized for
services with QCI 5. The optimization increases the number of UEs
that can simultaneously process voice over IP (VoIP) services. Note
that Huawei suggests that IMS signaling use only QCI 5.
Implementati
on
Services with QCI 5 have the highest scheduling priority among

data services.
The MCS index for downlink services with QCI 5 is no longer

fixed to 1. The MCS selection is now determined by the CQI
reported by UEs and the CQI adjustment.
Impact
The number of UEs that can simultaneously process VoIP services

has been increased.
If data services with QCI 5 coexist with services with other QCIs
in a network, the QoS requirements of the services with other
QCIs may not be fulfilled because the services with QCI 5 have
the highest scheduling priority.
Impact on NEs
None
Impact on hardware
None

None

Issue 01 (2014-01-30)

79
1 Feature Updates
The initial block error rate (IBER) of IMS signaling will increase.
As a result, the establishment delay of VoIP services will also
increase, but this does not affect the VoIP service reliability.
Related
Operations
None
Trouble
Ticket
Number
IREQ00000068
Feature ID
LOFD-00101502
18. Smart Preallocation

Description
Compared with normal preallocation, smart preallocation decreases

uplink delay and increases downlink throughput if discontinuous
reception (DRX) is enabled. This feature also reduces uplink
interference and UE power consumption if DRX is disabled. Smart
preallocation automatically starts if there is data transmission in the
downlink.
Implementati
on
A new option SmartPreAllocationSwitch has been added to the

UlSchSwitch parameter in the CellAlgoSwitch MO, and a new
parameter SmartPreAllocationDuration has been added to the
CellUlschAlgo MO.
Smart preallocation automatically starts once there is data

transmission in the downlink. The preallocation lasts for a duration
specified by the SmartPreAllocationDuration parameter.
Impact on performance
Impact

When the SmartPreAllocationSwitch check box under the
UlSchSwitch parameter is selected and the
SmartPreAllocationDuration parameter is set to a value larger
than zero, this enhancement has the following impact:
If DRX is enabled, preallocation is now supported and the
uplink delay decreases. When the Transmission Control
Protocol (TCP) window is small, the downlink throughput
(especially the downlink peak rate) increases. However, the
uplink throughput may drop because of increased interference
in the uplink.
If DRX is disabled, the uplink throughput increases because of
decreased interference in the uplink. However, the
preallocation duration is prolonged and the uplink delay
increases slightly.
Impact on NEs
None
Impact on hardware
None
Issue 01 (2014-01-30)

80
1 Feature Updates

None

Impact on configuration management: A new option
SmartPreAllocationSwitch has been added to the UlSchSwitch
parameter in the CellAlgoSwitch MO, and a new parameter
SmartPreAllocationDuration has been added to the
CellUlschAlgo MO.

Smart preallocation takes effect only when preallocation is
enabled.
Related
Operations
Run the MML command MOD CELLALGOSWITCH with the

SmartPreAllocationSwitch check box under the UlSchSwitch
parameter selected. Run the MML command MOD
CELLULSCHALGO with SmartPreAllocationDuration set to a
value larger than zero.
Trouble
Ticket
Number
IR-0000101846
Feature ID
LOFD-001015
19. ROHC Applicable Only to Services with QCI 1

Description
Robust header compression (ROHC) reduces the data volume

transmitted over the Uu interface by compressing the Real-Time
Transport Protocol (RTP), User Datagram Protocol (UDP), and
Internet Protocol (IP) packet headers. ROHC helps improve network
coverage and capacity for VoIP services.
ROHC can only be used for VoIP services. In V100R005C00,
however, whether ROHC needs to be performed is not decided based
on the QCI of a service. The decision is made based on the sampled
packet type, packet length, and number of packets transmitted per
second. In V100R008C00, ROHC applies only to services with QCI
1, that is, VoIP services.
Implementati
on
The conditions for starting ROHC have been simplified. When a

service is established, the eNodeB checks the QCI of that service.
ROHC is performed only when the service has a QCI of 1.
Impact

None
Impact on NEs
None
Issue 01 (2014-01-30)
Impact on hardware

81
1 Feature Updates
None

None

Impact on license: The existing user-level license for this feature
is still applicable. The enhancement of this feature has no impact
on the license.

None
Related
Operations
None
Trouble
Ticket
Number
DTS2012102207951
Feature ID
LOFD-001017
20. Transmission Performance Counter Values Truncated

Description
In V100R005C00, eNodeBs round the values of transmission performance counters to the

nearest integers or decimals when calculating mean values or variances. In
V100R008C00, eNodeBs now truncate counter values rather than round them.
Implementati
on
eNodeBs perform truncation on the values of transmission performance counters.
Impact

None
Impact on NEs
None
Impact on hardware
None

None

Impact on performance management: Error ranges of 18 counters have been changed
as shown in the following table.
Issue 01 (2014-01-30)

82
1 Feature Updates
No.
Counter Name
Error
Range Was
Error
Range Is
VS.FEGE.TxMeanSpeed
0.5 bit/s
0-1 bit/s
RscGroup.TxMeanSpeed
0.5 bit/s
0-1 bit/s
VS.IPPM.Bits.MeansTx
0.5 bit/s
0-1 bit/s
VS.IPPM.Pkts.MeansTx
0.5 bit/s
0-1 bit/s
VS.IPPM.Peer.Bits.MeansRx
0.5 bit/s
0-1 bit/s
VS.IPPM.Forword.DropMeans
0.0005%
0-0.001%
VS.IPPM.Forword.Peak.DropRates
0.0005%
0-0.001%
VS.IPPM.Forward.JitterStandardDeviation
0.5
0-1
VS.IPPM.Back.JitterStandardDeviation
0.5
0-1
10
VS.IPPM.Rtt.Means
0.5 ms
0-1 ms
11
VS.Sctp.RxMeanSpeed
0.5 bit/s
0-1 bit/s
12
VS.Sctp.TxMeanSpeed
0.5 bit/s
0-1 bit/s
13
VS.PPP.TxMeanSpeed
0.5 bit/s
0-1 bit/s
14
VS.PPP.RxMeanSpeed
0.5 bit/s
0-1 bit/s
15
VS.MP.TxMeanSpeed
0.5 bit/s
0-1 bit/s
16
VS.MP.RxMeanSpeed
0.5 bit/s
0-1 bit/s
17
VS.TUNNEL.TxMeanSpeed
0.5 bit/s
0-1 bit/s
18
VS.TUNNEL.RxMeanSpeed
0.5 bit/s
0-1 bit/s

None
Related
Operations
None
Trouble
Ticket
Number
DTS2013010502816
Feature ID
None
21. VLAN Scan Disabled by Default
Issue 01 (2014-01-30)

83
1 Feature Updates
Description
Virtual local area network (VLAN) scan assists an eNodeB to obtain

VLAN IDs when the eNodeB is being deployed on a network with a
security gateway (SeGW). During eNodeB deployment, VLAN scan
enables the eNodeB to periodically send Dynamic Host Configuration
Protocol (DHCP) messages. In some cases, this may lead to intermittent
transport network disconnections. To address this issue, VLAN scan is
now disabled by default.
Implementatio In earlier versions, VLAN scan is enabled by default. Now, VLAN scan
is disabled by default. After an eNodeB is upgraded from an earlier
n
version to the current version, VLAN scan remains enabled. Users can
run SET DHCPSW to enable or disable VLAN scan.
Impact

None
Impact on NEs
None
Impact on hardware
None

None


This enhancement affects eNodeB deployment in plug and play
(PnP) mode. Users need to locally enable VLAN scan for an eNodeB
if VLAN scan is required during eNodeB deployment on a network
with an SeGW.
Related
Operations
To enable VLAN scan, run the SET DHCPSW command with

VLANSCANSW set to ENABLE(Enable).
To disable VLAN scan, run the SET DHCPSW command with

VLANSCANSW set to DISABLE(Disable).

Number
Feature ID
NA
22. Value Null Not Accepted for Character-String-Type Parameters

Description
Users are no longer allowed to set character-string-type parameters in

MML commands to NULL or <NULL>.
Implementati
on
If a character-string-type parameter is set to NULL or <NULL>, the

command execution will fail. Users will be notified that the
parameter value is invalid.
Issue 01 (2014-01-30)

84
1 Feature Updates
Impact

None
Impact on NEs
None
Impact on hardware
None

None

Impact on configuration management: If a character-string-type
parameter is set to NULL or <NULL>, the command execution
will fail. Users will be notified that the parameter value is invalid.

None
Related
Operations
None
Trouble
Ticket
Number
DTS2013010405571
Feature ID
None
23. Optimized Mechanism for Delivering Uplink Timing Advance Commands

Description
The mechanism for delivering uplink timing advance commands has

been optimized.
When the TimeAlignmentTimer parameter is set to SF5120(5120
subframes), SF10240(10240 subframes), or INFINITY(Infinity),
Implementati
on
The number of unnecessary uplink timing advance commands

delivered to motionless or low-mobility UEs can be reduced to save
air interface resources and reduce the power consumption of UEs in
DRX mode.
The high uplink time alignment performance can be ensured,

especially for high-mobility UEs.
A new parameter TimingAdvCmdOptSwitch has been added to the

TimeAlignmentTimer MO. When the TimeAlignmentTimer
parameter is set to SF5120(5120 subframes) or a larger value,
turning on TimingAdvCmdOptSwitch shortens the uplink time
alignment adjustment period and reduces the number of uplink timing
advance commands with a timing advance of 0.
When TimingAdvCmdOptSwitch is set to ON(On), the setting of
the TimeAlignmentTimer parameter no longer affects the setting of
Issue 01 (2014-01-30)

85
1 Feature Updates
the LongDrxCycle parameter in the DrxParaGroup MO.

TimingAdvCmdOptSwitch is set to OFF(Off) by default.
Impact

When the TimeAlignmentTimer parameter is set to
SF5120(5120 subframes) or a larger value, turning on
TimingAdvCmdOptSwitch has the following impacts:
It enables prompt uplink time alignment for high-mobility UEs.
This ensures uplink time alignment accuracy, and therefore
increases user throughput and cell capacity.
The number of unnecessary uplink timing advance commands
delivered to motionless or low-mobility UEs can be reduced to
save air interface resources and reduce the power consumption of
UEs in DRX mode.
Impact on NEs
None
Impact on hardware
None

None

TimingAdvCmdOptSwitch has been added to the
TimeAlignmentTimer MO.

None
Related
Operations
Run the MML command MOD TATIMER with

TimingAdvCmdOptSwitch set to ON(On) and
TimeAlignmentTimer to SF10240(10240 subframes).
Trouble
Ticket
Number
DTS2012120507897
Feature ID
None
24. Enhanced LMT GUI and Functions

Description
Issue 01 (2014-01-30)
Enhanced LMT GUI and functions are as follows:
The batch processing module has been enhanced as follows: The

batch processing assistant and syntax checking function have been
added. Users now can set the interval for batch processing.
The device panel can be displayed and refreshed on the LMT.
Changes have been made to the LMT login page and the tracing,

86
1 Feature Updates
monitoring, software management, eNodeB maintenance, and

overall maintenance functions. For details, see 3900 Series Base
Station LMT User Guide.
The LMT now provides more maintenance functions.
Implementati
on
The LMT provides maintenance functions for eNodeBs.
Impact

None
Impact on NEs
None
Impact on hardware
None

None

The LMT no longer supports Internet Explorer 6. Users are
advised to use Internet Explorer 8 to log in to the LMT.
Users are advised to upgrade Java Runtime Environment (JRE) on
their PCs to 1.6.0.26. The previously recommended version
1.6.0.11 is still supported.

None
Related
Operations
Log in to the LMT to perform operations.
Trouble
Ticket
Number
DTS2012110203215
Feature ID
None
25. Automatic Removal of X2 Configurations

Description
With this enhancement, an eNodeB checks whether it has any

neighbor cell relationship with a peer eNodeB. If not, the eNodeB
starts a timer specified by the X2SonDeleteTimer parameter and
removes the X2 configurations when the timer expires. This reduces
the workload of manually managing X2 configurations.
Implementati
on
A new parameter X2SonDeleteTimer has been added to the

GlobalProcSwitch MO. When this parameter is set to 0, automatic
X2 configuration removal is disabled. Automatic X2 configuration
Issue 01 (2014-01-30)

87
1 Feature Updates
removal takes effect when this parameter is set to a non-zero value.

Impact

With this enhancement, configurations of outdated X2 interfaces
can be automatically detected and removed.
Impact on NEs
None
Impact on hardware
None

None

X2SonDeleteTimer has been added to the GlobalProcSwitch
MO.

None
Related
Operations
Run the MML command MOD GLOBALPROCSWITCH with

X2SonDeleteTimer set to an appropriate value. Set this parameter to
0 to disable automatic X2 configuration removal. You are advised to
set this parameter to 10080 if automatic X2 configuration removal is
required.
Trouble
Ticket
Number
IR-0000153803
Feature ID
None
26. Enhanced GERAN Frequency Selection

Description
In interoperability from EUTRAN to GERAN, eNodeBs now check

the frequency validity before selecting frequencies from suitable
GERAN frequency groups. The frequencies are used for UE
measurement or redirection. This reduces invalid signaling over the
Uu interface and saves the Uu resources.
Implementati
on
eNodeBs now select frequencies from suitable GERAN frequency

groups based on the UE capability, PLMN information of the
frequencies, and whether neighboring cells exist under the
frequencies. eNodeBs send only the selected frequencies to UEs.
Issue 01 (2014-01-30)

88
1 Feature Updates
Impact

None
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
IR-0000097969
Feature ID
LOFD-001034
LOFD-001053
LOFD-001069
LOFD-001020
LOFD-001045
LOFD-001046
LOFD-001073
27. Optimized Measurement Mechanism for Counters Related to the Service Drop Rate in
Multi-Bearer Scenarios
Description
In versions earlier than V100R008C00, when multiple E-UTRAN

radio access bearers (E-RABs) have been established for a UE and
one E-RAB is abnormal during a UE context release, the eNodeB
counts all the E-RABs as abnormally released E-RABs.
In V100R008C00, the optimized measurement mechanism separately
determines whether each E-RAB is released abnormally. Therefore,
the values of the counters related to abnormal releases in multi-bearer
scenarios are more accurate.
Implementati
on
Issue 01 (2014-01-30)
When an eNodeB triggers an E-RAB release or UE context release,

the eNodeB determines the service status of each E-RAB and gathers

89
1 Feature Updates
statistics based on the service status and release cause of each ERAB.
Impact

The values of the counters related to abnormal releases in multibearer scenarios decrease.
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
IREQ00000098
Feature ID
LBFD-002007
LBFD-002008
28. New Switch for Blind Handovers Triggered by Load Balancing

Description
A parameter has been added to control whether to enable blind

handovers for inter-frequency and inter-RAT load balancing.
Handover policies for load balancing are now more flexible.
Implementati
on
The MlbHoMode parameter has been added to the CellAlgoSwitch

managed object (MO). The
InterFreqMlbBlindHo(InterFreqMlbBlindHo) and
InterRatMlbBlindHo(InterRatMlbBlindHo) options of this
parameter control whether to enable blind handovers for interfrequency and inter-RAT load balancing, respectively.
BlindHoSwitch(BlindHoSwitch) under the HoModeSwitch
parameter no longer controls whether to enable blind handovers for
inter-frequency and inter-RAT load balancing.
Impact

InterRatMlbBlindHo(InterRatMlbBlindHo) are not selected by
Issue 01 (2014-01-30)

90
1 Feature Updates
default. Under the default setting, the load balancing algorithm

triggers only measurement-based inter-frequency and inter-RAT
handovers. Measurement-based handovers increase interfrequency and inter-RAT handover success rates. The gap-assisted
measurements for inter-frequency or inter-RAT handovers
consume radio resources.
Impact on NEs
None
Impact on hardware
None

None

the license.
Impact on configuration management: The MlbHoMode
parameter has been added to the CellAlgoSwitch MO. This
parameter has two values:
InterRatMlbBlindHo(InterRatMlbBlindHo).

None
Related
Operations
Run the MOD CELLALGOSWITCH command with

InterRatMlbBlindHo(InterRatMlbBlindHo) selected under the
MlbHoMode parameter to enable blind handovers for interfrequency and inter-RAT load balancing, respectively.
Trouble
Ticket
Number
DTS2013020105859
Feature ID
None
29. Optimized UE Context Setup Procedure When the Number of UEs Reaches the Licensed
Limit
Description
In versions earlier than V100R008C00, if the number of UEs has

reached the licensed limit, an eNodeB still sets up the context of a
new UE but then releases the UE. The counter of normal E-UTRAN
radio access bearer (E-RAB) releases, rather than the counter of ERAB setup failures, increases by one.
In V100R008C00 and later, if the number of UEs has reached the
licensed limit, initial context setup fails for a new UE and the counter
of E-RAB setup failures increases by one. The UE access procedure
Issue 01 (2014-01-30)

91
1 Feature Updates
has been optimized, and the values of counters are more accurate.
Implementati
on
The eNodeB now checks whether the number of UEs has reached the
licensed limit before an initial context setup procedure. If the eNodeB
determines that the number of UEs has reached the licensed limit and
the UE cannot access the network, the initial context setup fails and
the counter of E-RAB setup failures increases by one.
Impact

When the number of UEs has reached the licensed limit, the
access success rate and E-RAB setup success rate decrease.
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
iCare: 1666131
Feature ID
LBFD-001001
DTS: DTS2013013108538
LBFD-002023
LBFD-002024
LOFD-00102901
30. Batch Configuration

Description
Base stations support using a batch configuration file to perform

batch configuration.
Implementati
on
The existing XML batch configuration file is still used, and the MML
batch configuration file is no longer used.
The PRA BATCHFILE command now only checks whether the
format of the XML batch configuration file is valid. It no longer
checks the validity of the file content.
Impact
Issue 01 (2014-01-30)

92
1 Feature Updates
None
Impact on NEs
None
Impact on hardware
None

The DLD BATCHFILE command no longer supports MML
batch configuration files.
The PRA BATCHFILE command now only checks whether the
format of the XML batch configuration file is valid. It no longer
checks the validity of the file content.

The value range of the SRCF parameter for the DLD
BATCHFILE command has been reduced.
The function of the PRA BATCHFILE command has been
changed.

None
Related
Operations
Run the following commands one by one on the base station side:
20.STR BATCHFILESN
21.DLD BATCHFILE
22.PRA BATCHFILE
23.ACT BATCHFILE
24.END BATCHFILESN
Trouble
Ticket
Number
CR-MBTS18-340
Feature ID
None
31. Base Station Deployment by USB

Description
To make a Universal Serial Bus (USB) flash drive used for base
station deployment, the USB Making and Protection Tool can use a
site deployment list exported from the CME.
Implementati
on
To support co-MPT BTS3900s, a multimode base station directory

has been added to the USB flash drive for storing co-MPT BTS3900
software and configuration data. The directories for storing NodeB
and eNodeB software and configuration data have been moved to the
multimode base station directory.
Issue 01 (2014-01-30)

93
Impact
1 Feature Updates

None
Impact on NEs
The USB Making and Protection Tool works with specific
versions of the M2000 and CME.
Impact on hardware
None

None


None
Related
Operations
25.Export a site deployment list on the CME.

26.Start the USB Making and Protection Tool, and then import the
site deployment list and required files into the tool.
27.Select the base stations to be deployed by USB, and then finish
making the USB flash drive used for base station deployment.
Trouble
Ticket
Number
DTS2012070900773
Feature ID
None
32. Optimized Transmission QoS Policies in GSM/UMTS/LTE Co-MPT Mode
Issue 01 (2014-01-30)

94
Description
1 Feature Updates
GSM/UMTS/LTE co-MPT is introduced in SRAN8.0 (V100R008C00).

The standardized transmission QoS operation and maintenance
(O&M), default bandwidth configuration, and flow control in co-MPT
mode improve O&M experience and the fairness of uplink and
downlink flow control among GSM, UMTS, and LTE, and simplify the
O&M interface.
Implementatio The following mechanisms have been standardized:

n
Transmission QoS O&M, including transmission resource
configuration and mapping
Impact
Default configurations related to transmission QoS and bandwidth,

including the default configurations of multimode and cascading
base stations
Flow control, including port congestion control and end-to-end flow

control

The default differentiated services code point (DSCP) value of
Signaling Control Transmission Protocol (SCTP) signaling has been
increased from 46 to 48. This raises the priority for sending SCTP
signaling information and reduces the probability of packet loss in
the case of transmission congestion.
The default DSCP value of services with QCI 2 and QCI 4 has been
increased to the value of services with QCI 3. If the transmission
equipment is congested, rates of services with QCI 3 may decrease
while rates of services with QCI 2 and QCI 4 may increase.
The default DSCP value of services with QCI 8 has been increased
to the value of services with QCI 6 and QCI 7. If the transmission
equipment is congested, rates of services with QCI 6 and QCI 7
may decrease while rates of services with QCI 8 may increase.
Impact on NEs
The implementation of this feature requires the support of CME.
Impact on hardware
None

None

Impact on license: The existing base-station-level license for this

None
Related
Operations
Issue 01 (2014-01-30)
None

95
1 Feature Updates
Trouble Ticket IR-SRAN80-TRAN-030

Number
Feature ID
None
33. Increased Downlink GBR for Services with QCI 1

Description
The downlink guaranteed bit rate (GBR) for services with QoS class
identifier 1 (QCI 1) is increased to better fulfill the downlink delay
requirements of these services.
Implementati
on
In versions earlier than V100R008C00, the actual downlink GBR for

services with QCI 1 equals the GBR configured on the eNodeB.
In V100R008C00, the actual downlink GBR for services with QCI 1
is twice the GBR configured on the eNodeB.
Impact

The increased downlink GBR reduces the probability that the
downlink delay requirements for bearers with QCI 1 are not
fulfilled and, in addition, increases downlink data rates.
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
DTS2013010804115
Feature ID
None
34. Optimized Cell-specific Frequency-Domain SRS Resource Allocation

Description
Issue 01 (2014-01-30)
When uplink (UL) coordinated multi-point (CoMP) is enabled,

frequency-domain starting positions of sounding reference signals
(SRSs) are now different in a pair of neighboring cells for a CoMP

96
1 Feature Updates
UE. This reduces the impact of SRS interference on timing advance

(TA) and decreases the UL throughput fluctuation of the CoMP UE.
Implementati
on
The eNodeB searches for SRS resources to allocate to a UE based on

the following relationships between frequency-domain starting
positions and cell IDs:
If the cell ID modulo 4 is 0, the eNodeB searches for SRS resources

on subcarriers with transmissionComb of 0 and then on subcarriers
with transmissionComb of 1 from the low end of the cell frequency
band. (The transmissionComb information element [IE] is defined
in 3GPP specifications. It indicates odd- or even-numbered
subcarriers.)

with transmissionComb of 1 from the high end of the cell frequency
band.

with transmissionComb0 from the low end of the cell frequency
band.

with transmissionComb of 0 from the high end of the cell frequency
band.
If the search is successful, the eNodeB allocates SRS resources and

sends an RRC message to the UE. If the search fails, the eNodeB
does not allocate any SRS resources to the UE. To allocate SRS
resources to the UE again, the eNodeB uses the same rules.
Impact

When cells serve only a few UEs, this feature decreases the UL
throughput fluctuation of CoMP UEs.
Impact on NEs
None
Impact on hardware
None

The SoundingRS-UL-Config IE contained in a Uu signaling
message is changed as follows:
For UEs that access different cells in the same sequence, each of
them now has different settings of the freqDomainPosition and
transmissionComb IEs. (The freqDomainPosition IE is defined in
3GPP specifications. It indicates the UE-specific frequencydomain starting position of SRS.)

Issue 01 (2014-01-30)

97
1 Feature Updates

None
Related
Operations
None
Trouble
Ticket
Number
DTS2012111505102
Feature ID
LBFD-002003
35. Fewer Constraints on PLMN-specific Dedicated Cell-Reselection Priority

Configurations of UTRAN and GERAN Frequencies
Description
For PLMN-specific dedicated cell-reselection priority configurations

of UTRAN and GERAN frequencies, the eNodeB no longer imposes
PLMN ID constraints between either of the following:
Implementati
on
Impact
Neighbor relationships with UTRAN cells and operators that share

the operating frequency of the UTRAN cells
Neighbor relationships with GERAN cells and operators that share

the operating carrier frequency group of the GERAN cells
If a local cell has been configured with UtranNCell and

UtranRanShare managed objects (MOs), before adding or
removing a UtranRanShare MO or adding a UtranNCell MO, the
eNodeB no longer checks whether the Mobile country code and
Mobile network code parameter values in the existing UtranNCell
MOs are the same as those in the existing UtranRanShare MOs.
If a local cell has been configured with GeranNcell and

GeranRanShare MOs, before adding or removing a
GeranRanShare MO or adding a GeranNcell MO, the eNodeB no
longer checks whether the Mobile country code and Mobile
network code parameter values in the existing GeranRanShare
MOs are the same as those in the existing GeranNcell MOs.
UtranNCell represents the neighbor relationship with a UTRAN cell.
UtranRanShare contains information about an operator that shares a

UTRAN frequency with other operators.
GeranNcell represents the neighbor relationship with a GERAN cell.
GeranRanShare contains information about an operator that shares a

GERAN carrier frequency group with other operators.

None
Impact on NEs
None
Impact on hardware
None
Issue 01 (2014-01-30)

98
1 Feature Updates
None


None
Related
Operations
Run the ADD UTRANRANSHARE command to add a

UtranRanShare MO.
Run the RMV UTRANRANSHARE command to remove a

UtranRanShare MO.
Run the ADD GERANRANSHARE command to add a

GeranRanShare MO.
Run the RMV GERANRANSHARE command to remove a

GeranRanShare MO.
Run the ADD UTRANNCELL command to add a UtranNCell

MO.
Run the ADD GERANNCELL command to add a GeranNcell

MO.
Trouble
Ticket
Number
DTS2013012604431
Feature ID
None
36. Optimized ANR and DRX Configurations

Description
Issue 01 (2014-01-30)
In V100R008C00 and later, the discontinuous reception (DRX)

configurations delivered by an eNodeB to UEs have been optimized
as follows:
When a UE performs cell global identification (CGI) measurements

for automatic neighbor relation (ANR), the eNodeB sets the IE
simultaneousAckNackAndCQI to false instead of true. In addition,
the eNodeB sets the IE DRX-Config in the
RRCConnectionReconfiguration message for triggering a handover
to release, which enables the UE to exit DRX mode during ANR.
Then, the target eNodeB of the handover determines whether to
enable the UE to enter common DRX mode.
The eNodeB no longer includes the IE DRX-Config with a value of

release in the RRCConnectionSetup message. This reduces
signaling overhead on the air interface and also enhances the
compatibility of non-DRX-supporting UEs.
After the resynchronization between the eNodeB and the UE

succeeds, the eNodeB no longer instructs the UE to reconfigure the
DRX-Config IE if the DRX configuration does not change. This
reduces signaling overhead on the air interface.

99
1 Feature Updates
Implementati
on
Impact
An eNodeB with ANR enabled now sets the IE

simultaneousAckNackAndCQI to false if the eNodeB determines
that the IE cqi-Mask-r9 is not required. In addition, the eNodeB
with ANR enabled sets the IE DRX-Config in the
RRCConnectionReconfiguration message for triggering a handover
to release.
An eNodeB no longer includes the IE DRX-Config with a value of

release in the RRCConnectionSetup message.
After the resynchronization between the eNodeB and the UE

succeeds, the eNodeB no longer includes the DRX-Config IE in the
RRCConnectionReconfiguration message to the UE if the DRX
configuration does not change.

None
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
DTS2013030509864
Feature ID
LOFD-002001
DTS2012090504532
LBFD-002017
37. Support for UE Capability Identification According to CR895 and CR897 of 3GPP TS
36.331
Issue 01 (2014-01-30)

100
Description
1 Feature Updates
CR895 and CR897 of 3GPP TS 36.331 have been incorporated into the
eNodeB.
According to CR895 of 3GPP TS 36.331, an LTE FDD/TDD dualmode UE can use different information elements (IEs) to indicate UE
capabilities in LTE FDD and LTE TDD modes.
According to CR897 of 3GPP TS 36.331, new bits are introduced to
the FGI IE for ANR and inter-RAT measurements.
Implementatio The eNodeB stores the UE capabilities in LTE FDD and LTE TDD
modes and considers the UE capabilities when implementing features.
n
The eNodeB stores the information in the new FGI bits and considers
them during ANR procedures. ANR with cells of a specific RAT takes
effect only for UEs that support this type of ANR.
Impact

The eNodeB can enable functions for LTE FDD/TDD dual-mode
UEs based on UE capabilities in LTE FDD and LTE TDD modes.
The eNodeB does not enable ANR with cells of a specific RAT for
UEs that do not support this type of ANR.
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None

Number
Feature ID
LOFD-001022
LOFD-001023
LOFD-001033
LOFD-001034
LOFD-001019
LOFD-001020
LOFD-002001
LOFD-002002
Issue 01 (2014-01-30)

101
1 Feature Updates
LOFD-001048
LBFD-002017
LOFD-001001
LOFD-001003
LOFD-001060
LBFD-002025
LBFD-002008
LBFD-00201802
38. New CCE Ratio for Cells with a 5 MHz Bandwidth
Issue 01 (2014-01-30)

102
1 Feature Updates
Description
The CCE ratio is a ratio of the number of uplink CCEs to the number
of downlink CCEs. This ratio for cells with a 5 MHz bandwidth has
been changed from 1:2 to 2:3.
Implementati
on
If the CCE ratio is 1:2, a minimum of 7 CCEs are available for the
uplink. When the 13 CCEs available for the downlink are all used,
the eNodeB cannot transmit the PDCCH of DCI 0 with CCE
aggregation level 8. Therefore, cell-edge users (CEUs) cannot access
the network.
After the CCE ratio is changed to 2:3, a minimum of 8 CCEs are
available for the uplink. As a result, more CEUs can access the
network.
Impact

The minimum number of CCEs available for the uplink
increases. Therefore, the access success rate for CEUs
increases.
The number of CCEs available for the downlink decreases
from 13 to 12. Therefore, the DL scheduling delay may
slightly increase.
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
DTS2012121903272
Feature ID
LBFD-002003
39. Changed the RRU Channel Cross Connection Under MIMO Feature from Optional to
Basic
Issue 01 (2014-01-30)

103
Description
1 Feature Updates
In V100R008C00, the RRU Channel Cross Connection Under MIMO

feature is changed from an optional feature to a basic feature.
Implementatio 1. The sector configuration module is simplified.

n
The SectorMode parameter is removed from the Sector MO, and the
antenna mode of 2T2R in combined RRUs networking mode is used by
default in RRU channel cross connection under MIMO mode.
2. The RRU Channel Cross Connection Under MIMO(FDD) license is
removed.
Impact

None
Impact on NEs
None
Impact on hardware
None

None

Impact on license: Users no longer need to purchase the RRU
Channel Cross Connection Under MIMO(FDD) license for this
feature.
Impact on configuration management: The SectorMode parameter
is removed from the Sector MO.
None
Related
Operations
To configure RRU channel cross connection under MIMO for a cell,

perform the following operations:
1. Run the ADD SECTOR command to configure two antennas that
are connected to different RF modules, and set Create Default Sector
Equipment to TRUE(TRUE).
2. Run the ADD CELL command with Cell transmission and
reception mode set to 2T2R.
3. Run the ADD EUCELLSECTOREQM command to configure
sector equipment for the cell.
4. Run the ACT CELL command to activate the cell.

Number
Feature ID
Issue 01 (2014-01-30)
LOFD-001038

104
1 Feature Updates
40. Removed the DLITFCALG MO

The DLITFCALG MO enables transmission modules to implement
flow control on the internal downlink channel. With this function, the
system will run properly and certain traffic will be ensured even if the
downlink traffic exceeds a specific threshold. The internal downlink
channel is the service channel between the main control board and the
baseband board.
The DLITFCALG MO has two parameters: Bit Congestion Down
Link Internal Flow Control Switch and Packet Congestion Down
Link Internal Flow Control Switch. They indicate whether to limit
S1 interface downlink rate measured in bit per second (bps) and in
packet per second (pps) in case of LBBP CPU overload, respectively.
In this version, the switches are removed, and the functions are enabled
by default.
Implementatio The DLITFCALG MO is removed, and flow control on the internal
downlink channel is enabled by default.
n
Description
Impact

None
Impact on NEs
None
Impact on hardware
None

None

Impact on configuration management: Users can no longer set the
DLITFCALG MO.
None
Related
Operations
None
Trouble Ticket CR-MBTS18-152

Number
Feature ID
None
41. If the Number of E-RABs Carried in the Handover Request Message Is Greater than the
Number of E-RABs Supported by the eNodeB, the eNodeB Responds with a Handover
Failure Message and Does Not Count the Handover Request in
L.HHO.IntereNB.PrepAttIn.
Issue 01 (2014-01-30)

105
Description
1 Feature Updates
In versions earlier than V100R008C00, the eNodeB cannot identify the

error when the number of E-RABs carried in the Handover Request
message from the MME is greater than the number of E-RABs
supported by the eNodeB, and therefore the handover request is
counted in L.HHO.IntereNB.PrepAttIn. In V100R008C00, the eNodeB
can identify the error, and the handover request is not counted in
Implementatio In V100R008C00, if the number of E-RABs carried in the Handover

Request message from the MME is greater than the number of E-RABs
n
supported by the eNodeB, the eNodeB responds with a Handover
Failure message and does not count the handover request in
Impact

The value of the L.HHO.IntereNB.PrepAttIn counter decreases.
Impact on NEs
None
Impact on hardware
None

None

None
Related
Operations
None

Number
Feature ID
LBFD-00201801
LBFD-00201802
TDLBFD-00201801
TDLBFD-00201802
42. If the Value of ARP in the E-RAB Level QoS Parameters IE Is 0 in the S1-based
Handover Request, the eNodeB Responds with a Handover Failure Message and Does
Not Count the Handover Request in L.HHO.IntereNB.PrepAttIn.
Issue 01 (2014-01-30)

106
Description
1 Feature Updates
In versions earlier than V100R008C00, the eNodeB cannot identify the

error when the value of ARP in the E-RAB Level QoS Parameters IE is
0 in an S1-based handover request, and therefore the handover request
is counted in L.HHO.IntereNB.PrepAttIn. In V100R008C00, the
eNodeB can identify the error, and the handover request is not counted
in L.HHO.IntereNB.PrepAttIn.
Implementatio In V100R008C00, if the value of ARP in the E-RAB Level QoS

Parameters IE is 0 in an S1-based handover request, the eNodeB
n
responds with a Handover Failure message and does not count the
handover request in L.HHO.IntereNB.PrepAttIn.
Impact

The value of the L.HHO.IntereNB.PrepAttIn counter decreases.
Impact on NEs
None
Impact on hardware
None

None

None
Related
Operations
None

Number
Feature ID
LBFD-00201801
LBFD-00201802
TDLBFD-00201801
TDLBFD-00201802
43. Added a Counter to Count the Number of Times that a UE Fails to Access the Cell due to
Flow Control
Issue 01 (2014-01-30)

107
Description
1 Feature Updates
In versions earlier than V100R008C00, the number of times that a UE

fails to access the cell due to flow control is counted in
L.RRC.SetupFail.ResFail. In V100R008C00, that number is counted in
L.RRC.SetupFail.Rej.FlowCtrl, which can reflect the cause of access
failures.
Implementatio The L.RRC.SetupFail.Rej.FlowCtrl counter is added in V100R008C00.

n
Impact

The number of times that a UE fails to access the cell due to flow
control is counted in L.RRC.SetupFail.Rej.FlowCtrl, and the value
of L.RRC.SetupFail.ResFail decreases.
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None

Number
Feature ID
None
44. Optimized the BS Updating Mechanism
Issue 01 (2014-01-30)

108
Description
1 Feature Updates
When receiving a scheduling request (SR), the eNodeB estimates the

scheduling resources based on "SR_data + BS", where SR_data is
adaptively adjusted based on the buffer state report (BSR), and BS is
the data amount in the UE buffer maintained in the eNodeB. In
versions earlier than V100R008C00, if data transmission fails even
after the maximum number of HARQ retransmissions is reached, the
eNodeB updates the BS by adding the scheduled transport block size
(TBS) to the original BS. This leads to a larger BS, and therefore
wastes RB resources, increases interference on neighboring cells, and
decreases cell throughput. In V100R008C00, the BS updating
mechanism is optimized so that scheduling resources can increase
reasonably in the preceding condition.
Implementatio In V100R008C00, the BS updating mechanism is optimized as follows:

n
After resource scheduling, BS and Data_fail are updated as follows:
BS = max(BS TBS, 0); Data_fail = min(TBS, BS)
When the maximum number of HARQ retransmissions is reached, BS
is updated as follows:
BS = BS + Data_fail
where,
TBS is the scheduled transport block size, and Data_fail is the data
amount that should be added to BS in the preceding condition.
Impact

This optimization has effect only when DRX is enabled and the
uplink traffic is light. With this optimization, scheduling resources
increase reasonably, RB resource waste and interference on
neighboring cells decrease, and the cell throughput increases.
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble Ticket None

Number
Feature ID
Issue 01 (2014-01-30)
LBFD-002025, LOFD-00101502

109
1 Feature Updates
45. Optimized the Counting Mechanism of User-Number-Related Counters to Decrease

System Load
Issue 01 (2014-01-30)

110
Description
1 Feature Updates
In versions earlier than V100R008C00, user-number-related counters

are counted in real time. This greatly increases the system load if the
user state changes frequently, the number of user states increases, or the
number of users increases.
In V100R008C00, the counters related to the number of CA UEs in a
cell and the number of UEs configured with Sounding Reference
Signal (SRS) resources in a cell are added. To reduce the system load,
the eNodeB changes the counting mechanism of counters from realtime-based to every second because the eNodeB reports counter values
to the M2000 every second.
Implementatio The eNodeB changes the counting mechanism of counters from realtime-based to every second.
n
Impact

The counters cannot reflect the number of users in real time. This
decreases the statistic accuracy, but does not affect the overall user
data statistics in the long run. The following counters are involved:
L.Traffic.User.Avg
L.Traffic.User.Max
L.Traffic.CEU.Avg
L.Traffic.CEU.Max
L.Traffic.User.Avg.PLMN
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None

Number
Feature ID
Issue 01 (2014-01-30)
None

111
1 Feature Updates
46. Added the L.E-RAB.FailEst.NoRadioRes Counter for E-RAB-related Measurement

After the eNodeB Receives PATH SWITCH REQUEST FAILURE and INITIAL
CONTEXT SETUP REQUEST from the MME
Description
Consider the following scenario:
1. The eNodeB receives a PATH SWITCH REQUEST FAILURE

message from the MME.
2. The MME sends an INITIAL CONTEXT SETUP REQUEST
message (instead of an UE release command) to the eNodeB.
3. The eNodeB attempts but fails to set up the initial context
because the eNodeB has had the UE context and cannot be
allocated more RB resources for the initial context setup.
In versions earlier than V100R008C00, the eNodeB then counts only
the E-RAB setup attempts. In V100R008C00 and later versions, the
eNodeB also counts the E-RAB setup failures due to no radio resource.
Implementatio The L.E-RAB.FailEst.NoRadioRes counter is added to measure the
number of E-RAB setup failures due to no radio resource.
n
Impact

The number of E-RAB setup failures due to no radio resource is
now measured by the L.E-RAB.FailEst.NoRadioRes counter. The
measured E-RAB setup success rate remains unchanged.
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None

Number
Feature ID
None
47. Support for the setting of the command sending interval during batch configuration on
the LMT.
Issue 01 (2014-01-30)

112
1 Feature Updates
Description
The interval for sending commands during batch configuration can

now be specified on the LMT.
Benefit
The command sending interval during batch configuration now can

be specified.
Implementati
on
The Command send interval parameter has been added to the

Settings dialog box. After this parameter is specified, the batch
commands are executed one by one with the interval specified by this
parameter on the LMT.
Related
Operations
To set the command sending interval, click Settings on the Batch tab
page, specify Command send interval in the displayed Settings
dialog box, and click OK.
Trouble
Ticket
Number
DTS2013041804922
Feature ID
None
48. Optimized Procedure for Determining Whether Bearers Have Been Activated During the
Measurement of Counters Related to E-RAB Release
Description
In an E-RAB release procedure or a UE context release procedure

initiated by the eNodeB, the counters related to abnormal releases of
activated E-RABs are measured if the cause value indicates an
abnormal release and the eNodeB determines that the corresponding
bearers have been activated.
In versions earlier than V100R008C00, the service status of UEs can
be obtained only in the UE context release procedures initiated by
the eNodeB. The eNodeB determines whether the bearers have been
activated based on the service status of UEs.
In V100R008C00, the eNodeB can obtain the information about
whether the bearers are carrying data in both E-RAB release and UE
context release procedures.
Implementati
on
In E-RAB or UE context release procedures initiated by the eNodeB,

the eNodeB collects the information about whether the bearers have
been activated. Based on the information and the release cause
value, the corresponding counters increase.
Impact

The values of counters related to abnormal releases of activated
E-RABs decrease.
Impact on NEs
None
Impact on hardware
None

None
Issue 01 (2014-01-30)

113
1 Feature Updates

Related
Operations
None
Trouble Ticket
Number
IREQ00000098
Feature ID
LBFD-002007
LBFD-002008
49. Modified Conditions for a Cell to Enter and Exit Intelligent Carrier Power-off Mode
Description
When there are only a few UEs on a carrier, the carrier (known as
the source carrier) transfers these UEs to another carrier (known as
the target carrier) and then the source carrier is powered off for
energy conservation.
Before modification, the thresholds for a cell to enter and exit
intelligent carrier power-off mode are the same, and therefore a
carrier may be powered off and on too frequently.
After modification, two separate thresholds are available to prevent
frequent carrier power-on and power-off.
Implementati
on
Impact
A non-basic cell enters intelligent carrier power-off mode if all the

following conditions are met:
The period for a cell to enter intelligent carrier power-off mode

starts. This period is determined by the Start time and Stop time
parameters in the CellShutdown MO.
The sum of the uplink PRB usage of the serving cell and the PRB
usage of each neighboring basic cell is less than the value of
Carrier UL Intelligent Power-Off Close Threshold (A1) of the
serving cell.
The sum of the downlink PRB usage of the serving cell and the
downlink PRB usage of each neighboring basic cell is less than the
value of Carrier DL Intelligent Power-Off Close Threshold
(A2) of the serving cell.

This modification prevents cells from frequently entering and
exiting intelligent carrier power-off mode.
After the modification, the default value for Carrier DL/UL
Intelligent Power-Off Open Threshold (B) changes from 40%
to 20%. The default value of 20% makes it more difficult for a
cell to enter intelligent carrier power-off mode.
Issue 01 (2014-01-30)
Impact on NEs

114
1 Feature Updates
None
Impact on hardware
None

None

Impact on license: Impact on license: The existing base-stationlevel license for this feature is still applicable. The enhancement
of this feature has no impact on the license.

None
Related
Operations
Perform the following steps to configure intelligent carrier power-off

mode:
4. Run the ADD EUTRANINTERNFREQ command to

configure a neighboring E-UTRAN frequency.
5. Run the ADD EUTRANINTERFREQNCELL command to
configure an inter-frequency neighboring cell.
6. Run the MOD CELLSHUTDOWN command to configure
the feature for the two cells (one as a basic cell and the other
as a non-basic cell). In this step, set the Intelligent power-off
of carriers switch parameter to ON(On), set Uplink PRB
threshold or Downlink PRB threshold to 0 for the basic cell,
and specify the intelligent power-off thresholds for the nonbasic cell.
Trouble Ticket
Number
DTS2013032705112
Feature ID
LOFD-001042
50. Enhanced Function of Supporting Two Carriers by the RRU3201

Description
An RRU3201 supports the intermediate frequency bandwidth of 30

MHz. Before the upgrade, an RRU3201 supports two carriers with
the bandwidth combinations of 15 MHz + 15 MHz and 20 MHz + 10
MHz. After the upgrade, an RRU3201 supports a new combination
of two consecutive 10 MHz bandwidths.
Implementati
on
An RRU3201 supports functions such as dual-carrier filtering and

dual-carrier frequency configuration and check.
Impact

The network capacity increases.
Issue 01 (2014-01-30)
Impact on NEs

115
1 Feature Updates
None
Impact on hardware
None

None


After the function is added, the logical resource usage increases
and the RRU power consumption increases by 3 to 5 W. The
RRU consumption after the increase must meet the requirements
of original RRU specifications.
Related
Operations
None
Trouble Ticket
Number
DTS2013032005922
Feature ID
None
DTS2013111404286
51. Increased Maximum Number of Neighboring UTRAN Cells for Each eNodeB Cell
Description
The upper limit of neighboring UTRAN cells that each eNodeB cell
supports has been changed from 64 to 128.
Implementati
on
The specifications for the upper limit of neighboring UTRAN cells

that each eNodeB cell supports have been changed from 64 to 128.
Impact
Impact on capacity and performance: Each eNodeB cell now

supports up to 128 neighboring UTRAN cells.
Impact on NEs
None
Impact on hardware
None

None

Issue 01 (2014-01-30)

116
1 Feature Updates
None
Related
Operations
Run the ADD UTRANNCELL or ADD

UTRANEXTERNALCELL command to configure neighboring
UTRAN cells.
Trouble Ticket
Number
DTS2012091905049
Feature ID
None
52. Support for the Use of Imperial Units to Configure MOs

Description
eNodeBs now allow users to configure length and temperature using

imperial units. The items that can be configured in imperial units
include:
Cell
Antenna port
Time of day (TOD) clock
GPS clock
BBU fan board
Optical or electrical module
Board temperature
Environment monitoring unit
Fan monitoring unit
Temperature control unit
Power monitoring unit
Fuel level of a diesel generator
Battery
Distance-based handover
Location information
Implementat
ion
After users set the imperial unit conversion rule on the M2000, the
eNodeB converts length and temperature into imperial units when
users run related MML commands.
Impact

None
Impact on NEs
None
Impact on hardware
None

None

Issue 01 (2014-01-30)

117
1 Feature Updates

Related
Operations
Impact on other features: none
7. Set the unit conversion rule on the M2000 client. For detailed
operations, see iManager M2000 Measurement System
Conversion Guide.
8. Run related MML commands to set items related to length and
temperature.
Trouble
Ticket
Number
DTS2012091905049
Feature ID
None
53. Support for Band 25

Description
eNodeBs now support network access, data transmission, and

handovers under cells operating in band 25.
Implementat
ion
Users can run MML commands to configure local cells, intrafrequency neighboring cells, and inter-frequency neighboring cells
that operate in band 25.
Impact

None
Impact on NEs
The CME must be able to check the configurations related to band
25.
Impact on hardware
None

None

Related
Operations
9. Run the ADD CELL or MOD CELL command to add or

modify the configuration of a cell operating in band 25.
10.Run the ADD EUTRANINTRAFREQNCELL or MOD
EUTRANINTRAFREQNCELL command to configure or
modify the intra-frequency neighboring cell configuration for a
cell operating in band 25.
Issue 01 (2014-01-30)

118
1 Feature Updates
11.Run the ADD EUTRANINTERFREQNCELL or MOD

EUTRANINTERFREQNCELL command to configure or
modify the inter-frequency neighboring cell configuration for a
cell operating in band 25.
Trouble
Ticket
Number
DTS2012042500141
Feature ID
None
54. Support for Real-time Monitoring on eNodeB Uplink RSRP

Description
The M2000 now monitors real-time eNodeB uplink reference signal

received power (RSRP) obtained by calculating demodulation
reference signal (DMRS).
Implementat
ion
The UL DMRS RSRP item is added to Quality of Channel

Monitoring on the M2000 client.
Impact

None
Impact on NEs
None
Impact on hardware
None

None

Impact on performance management: Users can subscribe to uplink
DMRS RSRP on the M2000 client. This helps users view real-time
channel quality and improves problem locating and network
quality analysis efficiency.

None
Related
Operations
Perform the following operations on the M2000 client:
12.Choose Monitor > Signaling Trace > Signaling Trace

Management.
13.In the displayed window, choose Trace Type > LTE > User
Performance Monitoring > Quality of Channel Monitoring
to create a monitoring task and observe the values for UL
DMRS RSRP.
Trouble
Ticket
Issue 01 (2014-01-30)
DTS2013061805982

119
1 Feature Updates
Number
Feature ID
LBFD-002025
55. Optimized the Load-based Redirection Function

Description
Before the optimization

In a scenario in which a load-based redirection is triggered because
of GBR service release, the eNodeB releases the user performing
GBR services if the frequency for redirection is unavailable.
After the optimization
In the preceding scenario, the eNodeB now releases GBR services
instead of the user so that the user can continue to perform non-GBR
service. This optimization effectively reduces call drop rate.
Implementati
on
Impact
When the only GBR bearer for an online user fails to be admitted, is
preempted, or is released because of congestion, the eNodeB
attempts to find frequency for redirection if LoadBasedSwitch is
turned on. The eNodeB then performs as follows:
If there is frequency available for redirection, the eNodeB releases

the user and sends an RRC Connection Release message, which
carries the frequency.
If there is no frequency available for redirection, specifically, no

frequency or no inter-frequency neighboring cell is configured, the
eNodeB rejects the GBR bearer setup request or releases the GBR
bearer. However, the GBR user is not released.

If there is no frequency available for redirection, specifically, no
frequency or no inter-frequency neighboring cell is configured,
the GBR service fails to be admitted, is preempted, or is released
because of congestion. However, this will not cause redirection
but will decrease the call drop rate of non-GBR services. The
values of the following counters will decrease:
L.E-RAB.AbnormRel.QCI.5
L.E-RAB.AbnormRel
L.E-RAB.AbnormRel.eNBTot
L.E-RAB.AbnormRel.Cong
Impact on NEs
None
Impact on hardware
None
Issue 01 (2014-01-30)

120
1 Feature Updates

None

Related
Operations
None
Trouble
Ticket
Number
DTS2013032705867
Feature ID
LBFD-002023
LBFD-002024
LOFD-00102901
56. Optimized S1/X2 Link Fault Location Information

Description
The SCTPLNK and USERPLANEPEER MOs are created during

the S1/X2 self-setup procedure.
In versions earlier than V100R008C00, the configurations of
SCTPLNK and IPPATH in the two MOs cannot explicitly identify
whether an object is related to the S1 or X2 interface.
In V100R008C00, the eNodeBs automatically fill in
USERPLANEPEER.UserLabel and SCTPLNK.DESCRI fields.
The information explicitly identifies whether an object is related to
the S1 or X2 interface, which facilitates troubleshooting S1 and X2
interface faults.
Implementati
on
S1-C link
For the S1-C link, the SCTPLNK MO is automatically created
based on SCTPPEER (manually configured) and SCTPHOST.
During the creation, the eNodeB copies the
SCTPPEER.USERLABEL field to the SCTPLNK.DESCRI
field.
S1-U link
If the USERPLANEPEER MO is automatically created for the
S1-U link, the service layer encapsulates the "SGW:MCC_xxx
MNC_xx" message during the auto-creation. The service layer
then sends the message to the transport layer, which fills the
message in the USERPLANEPEER.USERLABEL field.
X2-C link
If the SCTPPEER MO is manually created for the X2-C link,
users copy the USERLABEL field in the SCTPPEER MO to the
DESCRIPTION field in the SCTPLNK MO. If the SCTPPEER
Issue 01 (2014-01-30)

121
1 Feature Updates
MO is automatically created for the X2-C link, the service layer

encapsulates the "eNB:MCC_xxx MNC_xxx GlobaleNBId_xxxxxx-xxxxxxx" message during the auto-creation. The service
layer then sends the message to the transport layer, which fills the
message in the SCTPPEER.USERLABEL field. During the
SCTPLNK creation, the eNodeB copies the
SCTPPEER.USERLABEL field to the SCTPLNK.DESCRI
field.
X2-U link
If the USERPLANEPEER MO is automatically created for the
X2-U link, the service layer encapsulates the "eNB:MCC_xxx
MNC_xxx GlobaleNBId_xxx-xxx-xxxxxxx" message during the
auto-creation. The service layer then sends the message to the
transport layer, which fills the message in the
USERPLANEPEER.USERLABEL field.
Impact

None
Impact on NEs
None
Impact on hardware
None

None

Impact on fault management: Currently, SCTP link alarms
account for the majority of control plane alarms in the transport
layer. SCTP link alarms carry the DESCRIPTION field, and
bearer fault alarms of the user plane carry the
USERPLANEPEER.USERLABEL field. Alarm location
information is now automatically added to related fields, which
facilitates troubleshooting S1 and X2 interface faults.
f. If the SCTPLNK MO is automatically created for the S1
interface, SCTP link alarms will carry information filled
during the auto-creation.
g. If the SCTPLNK MO is automatically created for the X2
interface, SCTP link alarms will carry the
"eNodeB:MCC_XXX MNC_XXX eNodeBId_XXXXX"
message, which was sent by the service layer to the transport
layer during X2 interface setup. If the X2 interface setup fails,
SCTP link alarms will carry the DESCRIPTION field.
h. For the S1 and X2 user planes, bearer fault alarms of the user
planes carry the USERPLANEPEER.USERLABEL field.

None
Issue 01 (2014-01-30)

122
1 Feature Updates
Related
Operations
None
Trouble
Ticket
Number
IR-0000081841
Feature ID
None
57. Increase in the Number of IP Paths Supported by eNodeBs

Description
The upper limit of IP paths supported by eNodeBs has been changed

from 128 to 320. This means an eNodeB can simultaneously set up IP
path connections with up to 320 S-GWs.
Implementat
ion
The IP path memory specifications are added for both eNodeBs and SGWs.
Impact

An eNodeB can simultaneously set up IP path connections with up
to 320 S-GWs.
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
Run the ADD IPPATH command to set the number of IP paths to 320.
Trouble
Ticket
Number
DTS2012111303367
Feature ID
None
58. Optimized the Mechanism for Creating an ACL Rule During IPSec Tunnel Negotiation
in PnP-based eNodeB Deployment When the SeGW is Deployed on the Network
Description
Issue 01 (2014-01-30)
When an eNodeB is deployed using plug and play (PnP), the eNodeB
automatically negotiates the IPSec tunnel with the security gateway

123
1 Feature Updates
(SeGW) after communicating with the DHCP server provided by the

M2000. The negotiated IPSec tunnel is used to protect the operation
and maintenance channel (OMCH) for the eNodeB.
In V100R005C00, the eNodeB uses two access control list (ACL)
rules, one for packets transmitted from the eNodeB's OM IP address to
any IP address and the other for packets transmitted from the
eNodeB's OM IP address to the M2000's IP address, to negotiate two
pairs of IPSec security associations (SAs) with the SeGW.
In V100R008C00, the eNodeB uses one ACL rule, which applies to
packets transmitted from the eNodeB's OM IP address to any IP
address, to negotiate one pair of IPSec SAs with the SeGW.
Using only one ACL rule in V100R008C00 prevents the SeGW of
some vendors from selecting an incorrect pair of IPSec SAs for
forwarding data when more than one pair of IPSec SAs is available.
Implementat
ion
In PnP-based eNodeB deployment, the eNodeB uses one ACL rule to

negotiate one pair of IPSec SAs with the SeGW after communicating
with the DHCP server provided by the M2000. The ACL rule applies
to the packets transmitted from the eNodeB's OM IP address to any IP
address.
Impact

None
Impact on NEs
None
Impact on hardware
None

In the IPSec security policy on the SeGW, the bound ACL rule
must include the rule that applies to the packets from any IP
address to the eNodeB's OM IP address.


None
Related
Operations
None
Trouble
Ticket
Number
DTS2013040801214
Feature ID
LOFD-003009
Issue 01 (2014-01-30)

124
1 Feature Updates
59. Optimized License Control Mechanism and Methods for Querying and Checking
License Control Items
Description
In versions earlier than V100R008C00, LTE FDD and TDD use the
same license control items. When a user queries or checks a license
control item for either mode, the operation takes effect for both
modes.
In V100R008C00, the license control mechanism has been optimized
as follows:
Implementati
on
Impact
Each common license control item for LTE FDD and TDD has been
split into two items to control features in FDD and TDD modes
separately. FDD uses the original common items and TDD uses
newly added items.
The query result now shows the license control items of only the
specified mode.
The check result now shows whether the license control items of
only the specified mode are consistent with the configuration data.
Each common license control item is split into two items to control
features in FDD and TDD modes separately. One with an FDD
identity in the name and the other with a TDD identity. In addition,
the eNodeB checks the duplex mode of the current cell
automatically and uses the corresponding license control items
during cell setup.
During license query or check, the eNodeB matches the duplex

mode of the current cell with the FDD or TDD identity in the name
of the license control item and queries or checks the corresponding
license control item.

None
Impact on NEs
None
Impact on hardware
None

None

Impact on license:
The output of the DSP LICENSE command changes. That is,
only the license control items of the corresponding duplex mode
are displayed and the name of each common license control item
is added with a TDD or FDD identity.
After the CHK DATA2LIC command is executed, only the
license control items of the corresponding duplex mode are
checked.
Issue 01 (2014-01-30)

125
1 Feature Updates

None
Related
Operations
Run the DSP LICENSE command to query license control items.
Run the CHK DATA2LIC command to check whether license

control items are consistent with configuration data.
Trouble
Ticket
Number
DTS2013041602596
Feature ID
None
60. Optimized Measurement Method for QoS Satisfaction Rates of VoIP Services
Description
In versions earlier than V100R008C00, the quality of service (QoS)

satisfaction rate of voice over Internet Protocol (VoIP) services is
represented by the ratio of VoIP services whose QoS requirements are
satisfied in a cell to all VoIP services in the cell. When the accessed
VoIP services reach the cell's capacity limit, the QoS satisfaction rate
fluctuates significantly before optimization. In this case, the cell
frequently enters and exits admission and congestion control mode.
In V100R008C00, the QoS satisfaction rate of VoIP services is
represented by the average satisfaction rate in a cell, that is, the ratio
of the sum of the satisfaction rates of all VoIP services in a cell to the
total number of VoIP services in the cell. When the accessed VoIP
services reach the cell's capacity limit, the QoS satisfaction rate does
not fluctuate significantly. In this case, the cell does not frequently
enter or exit admission and congestion control mode.
Implementati
on
Impact
The uplink and downlink QoS satisfaction rates of VoIP services are
measured using the following methods:
Downlink QoS satisfaction rate is represented by the ratio of the

sum of downlink satisfaction rates of all VoIP services in a cell to
the total number of VoIP services in the cell.
Uplink QoS satisfaction rate is represented by the ratio of the sum

of uplink satisfaction rates of all VoIP services in a cell to the total
number of VoIP services in the cell.

When the accessed VoIP services reach the cell's capacity limit,
the QoS satisfaction rate does not fluctuate significantly after
optimization. The cell does not frequently enter or exit admission
and congestion control mode.
Impact on NEs
None
Impact on hardware
None

None
Issue 01 (2014-01-30)

126
1 Feature Updates

Impact on performance management: QoS satisfaction rates of
VoIP services can be monitored using the DL QCI1 Satisfaction
rate of Service and UL QCI1 Satisfaction rate of Service test
items.

None
Related
Operations
None
Trouble
Ticket
Number
DTS2013032300108
Feature ID
LBFD-002023
LBFD-002024
61. Optimized Priority for Data Flow Selecting Transport Resource Group
Description
In V100R008C00, the priority for selecting the transport resource

group for a data flow is changed as follows:
The priority of the transport resource group for an end point is higher
than that for an end point group. For self-setup transmission links,
users can set the RSCGRP MOs separately for some end points. The
RSCGRP MOs are associated with the EP2RSCGRP MOs for the
associated end points. Other end points can be configured as an end
point group with the same RSCGRP MO. The RSCGRP MO is
associated with the EP2RSCGRP MO for the associated end point
group.
Implementati
on
In V100R008C00, the EP2RSCGRP MO associated with an end

point take precedence over the EP2RSCGRP MO associated with an
end point group.
Impact

The RSCGRP MOs selected with priority by self-setup user-plane
links in V100R003C00 and V100R008C00 are different. The
transport resource groups selected with priority by the data flow
are different in these two versions.
Impact on NEs
None
Impact on hardware
None

None
Issue 01 (2014-01-30)

127
1 Feature Updates


None
Related
Operations
In V100R003C00, if some end points are configured with one

NODETORSCGRP MO and some end points are configured with
their own NODETORSCGRP MOs, run the RMV
NODETORSCGRP command to remove the NODETORSCGRP
MOs with IsAllMatch set to NO(No) before an upgrade from
V100R003C00 to V100R008C00. This will prevent changes to the
transport resource group selected by the data flow.
In V100R008C00, run the ADD EP2RSCGRP command to add an

EP2RSCGRP MO with Mapping Type set to
ENDPOINT_NODE(EndPoint Node).
Trouble
Ticket
Number
DTS2013032701032
Feature ID
LOFD-002004
62. Optimized Handover Parameter Selection for Coverage-based Inter-Frequency

Handovers
Description
Bearers with different QoS class identifiers (QCIs) can be configured

with different inter-frequency handover parameters. When a UE is
performing multiple types of services with different QCIs, multiple
sets of handover parameters can be applied to these services.
In versions earlier than V100R008C00, the handover parameters that
include the lowest handover threshold among multiple handover
parameters apply to coverage-based inter-frequency handovers.
However, UEs performing voice services have higher target cell
requirements. In this handover parameter selection mechanism, UEs
performing voice services do not take precedence over UEs
performing data services to initiate inter-frequency handovers.
In V100R008C00, the eNodeB selects the handover parameters based
on the QCI priorities during a coverage-based inter-frequency
handover. This handover parameter selection mechanism ensures that
UEs performing voice services take precedence over UEs performing
data services to initiate inter-frequency handovers. User experience in
voice services is therefore improved.
Implementati
on
In a coverage-based inter-frequency handover, the inter-frequency

handover threshold is determined based on QCI priorities of multiple
types of services.
Impact
Issue 01 (2014-01-30)

128
1 Feature Updates
UEs performing voice services have a high priority to initiate

inter-frequency handovers, and therefore the handover success
rate of these UEs increases. User experience is improved.
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
IREQ00000073
Feature ID
LBFD-00201802
63. Optimized Procedure for Updating Handover Measurement Configuration

Description
Bearers with different QoS class identifiers (QCIs) can be configured

with different inter-frequency handover parameters. When a UE is
performing multiple types of services with different QCIs, multiple
sets of handover parameters apply to these services. In versions
earlier than V100R008C00, when the handover parameters change
because of a change in service during a service-based inter-RAT
handover or SPID-based handover to the home public land mobile
network (HPLMN), the eNodeB starts a procedure for updating
handover measurement configuration. (SPID is short for subscriber
profile ID.) However, because of the update, the handover may not be
performed in a timely manner.
In V100R008C00, the eNodeB does not initiate handover
measurement configuration update to ensure that handovers are
performed in a timely manner.
Implementati
on
In a service-based inter-RAT handover and SPID-based handover to

the HPLMN, the measurement configurations are not updated.
Impact

The number of signaling messages over the air interface
decreases.
Issue 01 (2014-01-30)

129
1 Feature Updates
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
IREQ00000073
Feature ID
LOFD-00105401
LOFD-001043
LOFD-001046
64. Optimized Interoperation Between EUTRAN and GERAN

Description
During interoperation between E-UTRAN and GERAN, the

measurement configurations and redirection signaling messages that
the eNodeB sends to a UE contain the GERAN carrier group
information.
In versions earlier than V100R008C00, the lowest GERAN carrier
frequency in the carrier group is not filtered based on UE capabilities.
The eNodeB may send the measurement configurations and
redirection signaling messages to a UE that does not support the
lowest GERAN carrier frequency. Therefore, air interface resources
are wasted.
In V100R008C00, the eNodeB only sends the measurement
configurations and redirection signaling messages to a UE that
supports the lowest GERAN carrier frequency in the frequency
group. Therefore, the efficiency of air interface resources increases.
Implementati
on
During interoperation between E-UTRAN and GERAN, the eNodeB

filters the GERAN carrier frequencies based on UE capabilities and
only sends the measurement configurations and signaling messages to
the UE that supports the lowest GERAN carrier frequency in the
GERAN carrier frequency group.
Impact
Issue 01 (2014-01-30)

130
1 Feature Updates
The number of signaling messages over the air interface

decreases.
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
IREQ00000073
Feature ID
LOFD-001034
LOFD-001020
LOFD-001046
LOFD-001073
65. Optimized Cell Selection Mechanism During Handovers Triggered for Reasons Other
Than Signal Quality
Description
Handovers triggered for reasons other than signal quality include

service-based and SPID-based handovers. (SPID is short for
subscriber profile ID.) If the measurement report from a UE contains
multiple cells, these cells are arranged by their signal strength.
In versions earlier than V100R008C00, if the cell with the best signal
quality rejects the handover request, the eNodeB hands the UE over to
the cell with the second best signal quality. After the handover is
complete, an intra-frequency handover may be triggered again for the
UE in the new cell. This negatively impacts user experience and
wastes radio resources.
In V100R008C00, the eNodeB only attempts to hand the UE over to
the cell with the best signal quality. If the cell rejects the handover
request, the eNodeB does not select the cell with the second best
signal quality as the target cell.
Implementat
ion
Issue 01 (2014-01-30)
During a handover triggered for a reason other than signal quality, the
eNodeB only attempts to hand the UE over to the cell with the best

131
1 Feature Updates
signal quality.
Impact

The number of handovers decreases.
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
IREQ00000073
Feature ID
LBFD-00201805
LOFD-00105401
LOFD-001043
LOFD-001046
66. Optimized Admission Control When Load Balancing Is Executed

Description
In versions earlier than V100R008C00, if mobility load balancing

(MLB) is enabled for a local cell, the eNodeB processes services of
UEs that are handed over to the cell normally when load balancing is
executed. If a large number of UEs are handed over to the local cell
from neighboring cells for optimization, the load of the local cell
increases. If the load of the local cell is heavy for a long time, user
experience is negatively affected.
In V100R008C00, if MLB is enabled for the local cell, the cell rejects
handover requests triggered for optimization.
Implementat
ion
The cause of service-based, SPID-based, and frequency-priority-based

handover requests is "Resource optimisation handover." When MLB is
enabled for the local cell and load balancing is executed, the eNodeB
checks the cause of a handover request. If the cause is "Resource
optimisation handover", the eNodeB rejects the handover request.
Impact
Issue 01 (2014-01-30)

132
1 Feature Updates
The number of handovers decreases and the number of handover

preparation failures increases.
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
IREQ00000073
Feature ID
LOFD-001032
LOFD-001044
LOFD-001045
67. Optimized Decision on Whether to Delivery A1 and A2 Measurement Configuration in

Coverage-based and Frequency-Priority-based Handovers
Description
During a coverage-based or frequency-priority-based handover, an

eNodeB first delivers intra-frequency A1 and A2 measurement
configurations to a UE. After the UE reports the A1 and A2
measurement reports, the eNodeB delivers inter-frequency and interRAT measurement configurations.
In versions earlier than V100R008C00, the eNodeB does not
determine the availability of inter-frequency and inter-RAT
neighboring cells before delivering A1 and A2 measurement
configurations. If no inter-frequency or inter-RAT neighboring cell is
available but the eNodeB still delivers A1 and A2 measurement
configurations for these cells, radio resources are wasted.
In V100R008C00, the eNodeB delivers intra-frequency A1 and A2
measurement configurations only when inter-frequency and inter-RAT
neighboring cells are available.
Implementat
ion
Issue 01 (2014-01-30)
During a coverage-based or frequency-priority-based handover, the

eNodeB filters inter-frequency and inter-RAT neighboring cells based
on the PLMN information, no handover indicator, and activation status
of neighboring cells. If all inter-frequency and inter-RAT neighboring
133
1 Feature Updates
cell are filtered out, the eNodeB does not deliver A1 and A2
measurement configurations.
Impact

The number of invalid A1 and A2 measurement configurations
decreases, which saves radio resources. Key performance
indicators (KPIs) remain unchanged.
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
IREQ00000073
Feature ID
LBFD-002018
68. Optimized Flash Redirection

Description
During a flash redirection procedure, an eNodeB sends a UE the

system information of cells operating on the target frequency to
shorten the redirection delay. A large amount of system information
sent to the UE leads to a high probability of decreased redirection
delay and increased air interface overheads.
In versions earlier than V100R008C00, the eNodeB determines the
number of cells whose system information is sent to the UE. In
V100R008C00, this number is configurable.
Implementat
ion
The parameters CellInfoMaxGeranCellNum and

CellInfoMaxUtranCellNum are added to specify the number of
neighboring GERAN and UTRAN cells whose system information is
sent to the UE. The value range for CellInfoMaxGeranCellNum is 1
to 32, and the value range for CellInfoMaxUtranCellNum is 1 to 16.
Impact

A large amount of system information sent to the UE leads to a
high probability of decreased redirection delay and increased air
Issue 01 (2014-01-30)

134
1 Feature Updates
interface overheads.
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
Run the MOD INTERRATHOCOMM command to set the number

of UTRAN and GERAN cells whose system information is sent to a
UE during a flash redirection procedure. In this step, set the
CellInfoMaxUtranCellNum and CellInfoMaxGeranCellNum
parameters.
Run the MOD INTERRATHOCOMM command to set the number

of UTRAN and GERAN cells whose system information is sent to a
UE during a flash redirection procedure triggered for an emergency
call. In this step, set the UtranCellNumForEmcRedirect and
GeranCellNumForEmcRedirect parameters.
Trouble
Ticket
Number
DTS2012112307344
Feature ID
LBFD-002018
69. Optimized CSFB-based Inter-RAT Handover

Description
If the public land mobile network (PLMN) ID of the target cell is

different from that contained in the location area identity (LAI) of the
UE during a CSFB-based inter-RAT handover, a routing area update
(RAU) procedure is required after the UE accesses the target cell. This
RAU procedure increases the circuit switched fallback (CSFB) delay.
During a CSFB-based inter-RAT handover in V100R008C00, an
eNodeB preferentially hands the UE over to a cell with the same
PLMN as that contained in the LAI of the UE to decrease the CSFB
delay.
Implementat
ion
Issue 01 (2014-01-30)
If the evolved packet core (EPC) notifies the eNodeB of the PLMN
contained in the LAI of the UE during a CSFB procedure, the eNodeB
considers the cell in the PLMN as the highest-priority candidate target
cell. This ensures that the eNodeB preferentially hands the UE over to
a cell in the same PLMN as that contained in the LAI.

135
1 Feature Updates
Impact

The CSFB delay decreases.
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
IREQ00000073
Feature ID
LOFD-001068
LOFD-001069
70. Optimized License Control Methods for Dual-Mode Sectors Served by RF Modules that
Supports Multiple Frequency Bands
Description
With the introduction of the RRU3961, one RF module can support

two frequency bands. Therefore, the control methods for the
GSM/LTE Dual Mode license, UMTS/LTE Dual Mode license, and
CDMA/LTE Dual Mode license are changed as follows in
V100R008C00: If two modes use the same frequency band, a dualmode license is required; if two modes use different frequency bands,
a dual-mode license is not required.
Implementati
on
A license requirement has been added. When a dual-mode sector is

activated, the RF module that serves this sector is checked:
Impact
If the RF module supports a single frequency band, a dual-mode

license is required.
If the RF module supports multiple frequency bands, a dual-mode

license is required only when the two modes use the same
frequency band.

The CSFB delay decreases.
Issue 01 (2014-01-30)
Impact on NEs

136
1 Feature Updates
None
Impact on hardware
None

None

Impact on license: A dual-mode license is required only when two
modes work in the same frequency band.

None
Related
Operations
None
Trouble
Ticket
Number
DTS2013032608915
Feature ID
None
71. Enhanced Uplink Frequency Selective Scheduling

Description
This feature is an enhancement to uplink frequency selective

scheduling. With this feature, more users can be involved in uplink
frequency selective scheduling and therefore the throughput
increases.
Implementati
on
Both the number of admitted users and the number of users for
scheduling are considered in the triggering conditions for frequency
selective scheduling. In addition, a switch for enhanced frequency
selective scheduling is added to ensure smooth version upgrade.
Impact

The switch for enhanced frequency selective scheduling is turned
off by default, and therefore this feature has no impact on the
system after an upgrade. If this switch is turned on, the uplink
modulation order increases and the UE throughput increases.
The values of counters related to the number of MCS selections
for scheduling on the PUSCH may decrease.
Impact on NEs
None
Impact on hardware
None

None
Issue 01 (2014-01-30)

137
1 Feature Updates

Impact on configuration management: In the
CELLALGOSWITCH MO, an option UlEnhancedFssSwitch is
added to the UlSchSwitch parameter to control whether to enable
enhanced uplink frequency selective scheduling.

None
Related
Operations
To enable enhanced uplink frequency selective scheduling, run the

MOD CELLALGOSWITCH command with the
UlEnhancedFssSwitch check box selected under the UlSchSwitch
parameter.
To disable enhanced uplink frequency selective scheduling, run the
MOD CELLALGOSWITCH command with the
UlEnhancedFssSwitch checked box cleared under the UlSchSwitch
parameter.
Trouble
Ticket
Number
DTS2013041704221
Feature ID
None
72. Optimized LED Indications for eNodeB Deployment/Upgrades Using a USB Flash
Drive
Issue 01 (2014-01-30)

138
Description
1 Feature Updates
A new method is now available for indicating the status of loading

software and data configuration files onto an eNodeB from a USB
flash drive.
In versions earlier than V100R008C00, the light emitting diode
(LED) on the USB flash drive is used to indicate loading status. An
illuminated light indicates successful loading, while no light indicates
that an interruption has occurred.
In V100R008C00, the RUN indicator on the main control board is
now the main LED used to indicate loading status. The LED on the
USB flash drive is a secondary indicator, which blinks during
loading.
Implementati
on
The following table describes the state of the RUN indicator on the
main control board.
Scenario
RUN Indicator State
Successfully
loaded
Slow blinking (1s on and 1s off)
Loading
Fast blinking (0.125s on and 0.125s off)
Loading failed
Steady on when the USB flash drive is

connected to the main control board
If the RUN indicator on the main control board is steady on when the
USB flash drive is connected to the board but begins to blink slowly
when the USB flash drive is disconnected from the board, loading has
failed. If the RUN indicator remains steady on when the USB flash
drive is disconnected from the board, check whether the board is
faulty, for example, by observing the ALM indicator.
Impact

None
Impact on NEs
This feature has the following requirements:
- The USB flash drive is ready.
- The eNodeB is correctly installed and powered on.
- A USB port on the main control board is available.
Impact on hardware
None

None

Issue 01 (2014-01-30)

139
1 Feature Updates
None
1.
Related
Operations
2.
Connect the USB flash drive to the USB port on the main
control board.
Wait for the eNodeB to restart after it automatically downloads
and activates software and data configuration files. Then,
observe the RUN indicator on the main control board to
determine loading status.
For a single-mode base station, the wait time is about 15
minutes. For a multimode base station, the wait time can be
about 25 to 30 minutes.
3.
If the software and data configuration files are successfully

loaded, remove the USB flash drive. If a post-upgrade check
finds that the loaded software version is incorrect, solve the
problem according to the instructions in section "How to Handle
the Incorrect Software Version" in 3900 Series Base Station
Commissioning Guide.
Trouble
Ticket
Number
CR20120705029
Feature ID
None
73. Optimized Scheduling for Paging Messages

Description
Scheduling for paging messages has been optimized.
Implementati When allocating resources for system information (SI) and paging
messages, the eNodeB uses a higher coding rate if the number of required
on
RBs that is calculated based on the default coding rate is greater than the
maximum number of RBs that can be allocated in a TTI.
In addition, a limitation has been imposed on the maximum number of UEs
that can be paged in a TTI in a cell with 1.4 MHz or 3 MHz bandwidth. If
the number of UEs to be paged in a TTI exceeds the limit, the eNodeB
sends the paging messages to some UEs in the next paging cycle.
Impact

The success rate of mobile-terminated VoIP call setups increases
when there are a great number of UEs to be paged.
There is a low probability that the delay for paging messages to some
VoIP UEs increases in a cell with 1.4 MHz or 3 MHz bandwidth. This
occurs only when there are a great number of UEs in the cell.
Impact on NEs
None
Impact on hardware
None

None
Issue 01 (2014-01-30)

140
1 Feature Updates


None
Related
Operations
None

Number
Feature ID
LOFD-00101502
74. Optimized Measurement of Counters Related to EPC-initiated Abnormal E-RAB

Releases
Issue 01 (2014-01-30)

141
Description
1 Feature Updates
When measuring counters L.E-RAB.AbnormRel.MME and L.ERAB.AbnormRel.MME.PLMN, the eNodeB does not check whether the
E-UTRAN radio access bearer (E-RAB) that the EPC instructs the
eNodeB to release is carrying data. Therefore, normally released ERABs may be mistakenly counted in these counters. To address this
issue, the measurement of counters related to EPC-initiated abnormal
releases has been optimized. (EPC is short for evolved packet core.)
Implementati In EPC-initiated E-RAB or UE context releases, the values of L.Eon

RAB.AbnormRel.MME and L.E-RAB.AbnormRel.MME.PLMN
increase only if the E-RAB to be released is carrying data and the release
cause is not any of the following:
Normal Release
Detach
User Inactivity
cs fallback triggered
UE Not Available For PS Service
Inter-RAT redirection
Successful Handover
Two counters L.E-RAB.AbnormRel.MMETot and L.ERAB.AbnormRel.MMETot.PLMN have been added to count the total
number of EPC-initiated E-RAB releases for causes other than the
preceding ones.
Impact

None
Impact on NEs
None
Impact on hardware
None

None

Impact on performance management: The values of L.ERAB.AbnormRel.MME and L.E-RAB.AbnormRel.MME.PLMN will
decrease.

None
Issue 01 (2014-01-30)

142
1 Feature Updates
Related
Operations
14.Log in to the M2000.
Trouble
Ticket
Number
DTS2013061906087
Feature ID
LBFD-002008
15.Choose Performance > Measurement Management, and select

the following counters to create a tracing task for these counters:
L.E-RAB.AbnormRel.MME
L.E-RAB.AbnormRel.MME.PLMN
L.E-RAB.AbnormRel.MMETot
L.E-RAB.AbnormRel.MMETot.PLMN
16.Check the values of the counters after the tracing task is
completed.
75. Optimized Cooperation Between Uplink Scheduler and Power Control Module
Description
According to 3GPP TS 36.213, the transmit power for UEs is controlled

by both transmit power control (TPC) commands of the power control
module and the number of resource blocks (RBs) allocated by the uplink
scheduler. Before the optimization, the number of RBs allocated by the
uplink scheduler cannot exceed the maximum number specified by the
power control module. As a result, power and RB resources may not be
fully utilized.
Now, the maximum number of RBs specified by the power control
module no longer takes effect. The number of RBs allocated by the
uplink scheduler may exceed the maximum number. As a result, power
and RB resources are better utilized.
Implementati Within each transmission time interval (TTI), the uplink scheduler
determines the number of RBs to be allocated to a UE based on the traffic
on
volume of the UE and distance between the UE and the eNodeB. The
scheduling ensures appropriate use of RB resources and fairness among
UEs. The uplink scheduler then calculates the received power spectral
density of the UE based on the number of RBs allocated to the UE,
compute the signal to interference plus noise ratio (SINR), and selects a
modulation and coding scheme (MCS) for the UE. The selected MCS
helps ensure link adaptation performance.
Impact

When the network is lightly or medium loaded, uplink throughput
increases by approximately 5% for UEs.
When the network is heavily loaded, there is little impact on the uplink
throughput for UEs.
In drive tests, the uplink throughput increases by 5% to 10% for UEs at
far or medium distances from the cell center.
Impact on NEs
None
Issue 01 (2014-01-30)

143
1 Feature Updates
Impact on hardware
None

None


SchedulerCtrlPowerSwitch(SchedulerCtrlPowerSwitch) option has
been added to the UlSchSwitch parameter in the CellAlgoSwitch
MO.

None
Related
Operations
To enable optimized cooperation between uplink scheduler and power

control module, run the MOD CELLALGOSWITCH command with
the SchedulerCtrlPowerSwitch(SchedulerCtrlPowerSwitch) check
box selected under the UlSchSwitch parameter.
To disable optimized cooperation between uplink scheduler and power

control module, run the MOD CELLALGOSWITCH command with
the SchedulerCtrlPowerSwitch(SchedulerCtrlPowerSwitch) check
box cleared under the UlSchSwitch parameter.
Trouble
Ticket
Number
DTS2013062001103
Feature ID
LOFD-00101502
76. Enhanced Aperiodic CQI Reporting
Issue 01 (2014-01-30)

144
Description
1 Feature Updates
An eNodeB learns downlink channel quality based on periodic and

aperiodic channel quality indicator (CQI) reports from UEs. As a
supplementary of periodic CQI reports, aperiodic CQI reports help the
eNodeB to learn downlink channel quality more promptly, increasing
downlink spectral efficiency.
Aperiodic CQI reporting has been optimized.
Implementati The eNodeB triggers aperiodic CQI reporting based on downlink services
of UEs if both of the following conditions are met:
on
The interval between periodic CQI reports is long.
Downlink frequency selective scheduling is disabled, or the channel

condition for UEs does not meet the requirements for downlink
frequency selective scheduling.
The eNodeB does not trigger aperiodic CQI reporting for a UE that does
not perform downlink services.
If downlink frequency selective scheduling is enabled and the channel
condition for UEs meets the requirements for downlink frequency
selective scheduling, the number of UEs in a cell sending aperiodic CQI
reports to the eNodeB is no longer controlled, so that more UEs can be
scheduled in frequency selective mode.
Impact

Enabling enhanced aperiodic CQI reporting increases the spectral
efficiency in downlink data transmission but consumes more control
channel elements (CCEs) if both the following conditions are met:
The interval between periodic CQI reports is long.
Downlink frequency selective scheduling is disabled, or the

channel condition for UEs does not meet the requirements for
downlink frequency selective scheduling.
It is recommended that the PdcchSymNumSwitch parameter in the

CellPdcchAlgo MO be set to ECfiAdaptionON to decrease the
number of CCEs consumed by aperiodic CQI reporting.
If downlink frequency selective scheduling is enabled and the channel
condition for UEs meets the requirements for downlink frequency
selective scheduling, the number of UEs in a cell sending aperiodic
CQI reports to the eNodeB is no longer controlled, so that more UEs
can be scheduled in frequency selective mode. In addition, aperiodic
CQI reporting mode adaptation between Mode3-0 and Mode2-0 has
been changed to reporting in Mode3-0, and adaptation between Mode31 and Mode2-1 has been changed to reporting in Mode3-1. Therefore,
signaling overheads for aperiodic CQI reporting mode reconfiguration
decrease.
Impact on NEs
None
Impact on hardware
None

None
Issue 01 (2014-01-30)

145
1 Feature Updates
Impact on configuration management: The EnAperiodicCqiRptSwitch

option has been added to the DlSchSwitch parameter in the
CellAlgoSwitch MO.

None
Related
Operations
None
Trouble
Ticket
Number
None
Feature ID
LBFD-002031
77. Enhanced ANR for Adding Neighboring Cells for MLB and CSFB
Issue 01 (2014-01-30)

146
Description
Implementati
on
1 Feature Updates
The automatic neighbor relation (ANR) function can now add

neighboring cells for mobility load balancing (MLB) and circuit
switched fallback (CSFB).
In inter-frequency MLB, MLB to UTRAN, or MLB to GERAN, if the

eNodeB detects inter-frequency cells, UTRAN cells, or GERAN cells
based on measurement results reported by UEs, the eNodeB adds the
detected cells to the associated neighboring relation table (NRT).
Fast ANR adds the detected strongest inter-frequency cell, UTRAN

cell, or GERAN cell to the associated NRT for MLB and CSFB.
The new parameter MlbBasedEventAnrSwitch specifies whether to

enable MLB-based event-triggered ANR.
If MLB-based event-triggered ANR is enabled, the eNodeB detects
inter-frequency cells, UTRAN cells, or GERAN cells based on
measurement results reported by UEs during inter-frequency MLB,
MLB to UTRAN, or MLB to GERAN, respectively. Then, the eNodeB
adds the detected cells to the associated NRT.
Impact
The new parameter FastAnrMode specifies the policy that the

eNodeB takes when adding neighboring cells for MLB and CSFB
during fast ANR.
If this parameter is set to NCL_MODE, the eNodeB adds the

detected cells only to the associated neighboring cell list (NCL).
If this parameter is set to NCL_NRT_MODE, the eNodeB adds

the detected cells to the associated NCL. In addition, if the
detected strongest cell is an inter-frequency cell, UTRAN cell, or
GERAN cell, the eNodeB adds it to the associated NRT. If the
detected strongest cell is an intra-frequency cell or CDMA2000
cell, the eNodeB does not add it to any NRT.

If MLB-based event-triggered ANR is enabled, the MLB success rate
increases, but cell global identification (CGI) reading during ANR
causes lower UE throughput and longer handover delay.
Different settings of the FastAnrMode parameter have different fast
ANR effects. Compared with the parameter value NCL_MODE, the
parameter value NCL_NRT_MODE results in more neighbor
relationships added to NRTs, a larger number of handovers, and a
higher success rate of handovers. However, the parameter value
NCL_NRT_MODE leads to a higher probability of adding redundant
neighboring cells, which has no negative impact on KPIs.
Impact on NEs
None
Impact on hardware
None

None

Impact on license: This feature is an enhancement for ANR that is under
control by eNodeB-level licenses "Automatic Neighbour Relation

(ANR)(FDD)" and "Inter-RAT ANR(FDD)."
Issue 01 (2014-01-30)

147
1 Feature Updates

MlbBasedEventAnrSwitch and FastAnrMode parameters have been
added to the ENodeBAlgoSwitch and ANR MOs, respectively.

None
Related
Operations
To enable MLB-based event-triggered ANR, run the MOD

ENODEBALGOSWITCH command with the
MlbBasedEventAnrSwitch parameter set to ON(On).
To disable MLB-based event-triggered ANR, run the MOD

ENODEBALGOSWITCH command with the
MlbBasedEventAnrSwitch parameter set to OFF(Off).
To specify the policy that the eNodeB takes when adding neighboring
cells during fast ANR, run the MOD ANR command with the
FastAnrMode parameter set to NCL_MODE or NCL_NRT_MODE.
Trouble
Ticket
Number
DTS2013070308553
Feature ID
LOFD-002001
LOFD-002002
78. Modification on the Meaning, Unit, GUI Value Range, and Recommended Value of the
InterFreqMlbUeNumThd and MlbUeNumOffset Parameters Used in Inter-Frequency
Blind MLB
Issue 01 (2014-01-30)

148
1 Feature Updates
Description
The InterFreqMlbUeNumThd and MlbUeNumOffset parameters are

used in inter-frequency blind mobility load balancing (MLB) evaluation.
They used to be expressed in percentages but are now expressed in
integers.
Implementati
on
The units of the two parameter values have been changed from "%" to
"Number."
The value ranges of the two parameters have been changed from "1100" to "1-10000."
The recommended value for the InterFreqMlbUeNumThd parameter

has been changed from 25 (that is, 25%) to 100 (that is, 100 UEs).
The recommended value for the MlbUeNumOffset parameter has

been changed from 5 (that is, 5%) to 20 (that is, 20 UEs).
The formula for calculating the threshold used to determine whether to

trigger inter-frequency blind MLB has been changed from formula 1 to
formula 2:
Impact
Formula 1: (InterFreqMlbUeNumThd + MlbUeNumOffset) x

Number of uplink synchronized UEs
Formula 2: InterFreqMlbUeNumThd + MlbUeNumOffset

None
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
DTS2013061904962
Feature ID
LOFD-001032
79. Optimized Adaptation of Periodic CQI Reporting on the PUCCH
Issue 01 (2014-01-30)

149
Description
1 Feature Updates
In optimized adaptation of periodic channel quality indicator (CQI)

reporting on the physical uplink control channel (PUCCH), the number
of resource blocks (RBs) used for periodic CQI reporting now increases
in smaller steps, and the interval between periodic CQI reports has been
extended.
Implementati The interval between periodic CQI reports on the PUCCH has been
extended, and therefore fewer PUCCH RBs are consumed by periodic
on
CQI reporting.
The number of RBs used for periodic CQI reporting increases smoothly.
Impact

Fewer PUCCH RBs are used for periodic CQI reporting, and more
RBs are available for the PUSCH. Therefore, cell throughput increases
in the uplink but decreases in the downlink. It is recommended that the
EnAperiodicCqiRptSwitch option under the DlSchSwitch parameter
in the CellAlgoSwitch MO be selected to compensate for the downlink
performance loss.
Impact on NEs
None
Impact on hardware
None

None

Impact on configuration management: The RsvdSwPara0_bit9 option
under the RsvdSwPara0 parameter is now used to enable or disable
optimized adaptation of periodic CQI reporting on the PUCCH. This
switch is off by default.

None
Related
Operations
To enable optimized adaptation of periodic CQI reporting on the

PUCCH, run the MOD ENBRSVDPARA command with the
RsvdSwPara0_bit9(ReservedSwitchParameter0_bit9) check box
selected under the RsvdSwPara0 parameter in the eNBRsvdPara MO.
All cells under the eNodeB will be reactivated to make the parameter setting take
effect.
Trouble Ticket None

Number
Feature ID
Issue 01 (2014-01-30)
LBFD-002003

150
1 Feature Updates
80. Enhanced Dynamic Adjustment on the Number of OFDM Symbols Occupied by the
PDCCH
Description
The dynamic adjustment on the number of orthogonal frequency

division multiplexing (OFDM) symbols occupied by the physical
downlink control channel (PDCCH) has been enhanced. Frequency
selective scheduling can now be applied when the number of PDCCHoccupied symbols is 1, 2, or 3. (In earlier versions, frequency selective
scheduling can be applied only when this number is 3.)
Implementa
tion
In earlier versions, eNodeBs adjust the number of PDCCH-occupied

symbols only based on whether control channel elements (CCEs) are
successfully allocated in the uplink and downlink.
Now, eNodeBs adjust the number of PDCCH-occupied symbols based
on the uplink and downlink load in addition to the uplink and downlink
CCE allocation results. Therefore, when frequency selective scheduling
is enabled, the eNodeBs can determine an optimal number of PDCCHoccupied symbols.
Impact

Frequency selective scheduling applies in more scenarios, which
increases cell capacity.
Impact on NEs
A switch has been added to the Configuration Management Express
(CME) to control the enhanced dynamic adjustment function.
Impact on hardware
None

None

None

None
Related
Operations
Run the MOD CELLPDCCHALGO command with the

PdcchSymNumSwitch parameter set to
ECfiAdaptionON(ECfiAdaptionON).
Trouble
Ticket
Number
DTS2013051600281
Feature ID
LBFD-002003
81. Optimized SR Handling
Issue 01 (2014-01-30)

151
Description
1 Feature Updates
If an eNodeB with discontinuous reception (DRX) at UEs enabled

falsely detects a scheduling request (SR) from a UE with light uplink
traffic, the DRX state maintained on the UE may be different from that
maintained on the eNodeB. If such a difference occurs, the UE is
unable to demodulate uplink grants, resulting in scheduling failures.
An eNodeB of an earlier version uses the following SR handling
mechanism in DRX-enabled scenarios: If the number of hybrid
automatic repeat request (HARQ) retransmissions scheduled in
response to a falsely detected SR reaches the maximum value but the
response still fails to be sent to the UE, the eNodeB immediately
performs one or two proactive scheduling operations during the active
time for DRX. However, in this situation, the DRX states maintained
on the UE and eNodeB may be different. As a result, the initial
transmissions and retransmissions resulted from these proactive
scheduling operations may all fail, wasting resources and causing a
higher initial block error rate (IBLER) and residual block error rate
(RBLER).
Now, if the scenario mentioned in the preceding paragraph occurs, the
DRX state difference does not cause failures of the initial transmissions
and retransmissions resulted from the proactive scheduling operations.
This decreases the IBLER and RBLER of the cell and achieves better
resource utilization.
Implementa
tion
In DRX-enabled scenarios, if the number of HARQ retransmissions

scheduled in response to a falsely detected SR reaches the maximum
value but the response still fails to be sent to the UE, the eNodeB
performs one or two proactive scheduling operations within the length
of the On Duration Timer for the long DRX cycle. The optimized SR
handling mechanism is controlled by a switch.
Impact

The switch for the optimized SR handling mechanism is turned off
by default. Therefore, capacity and performance are not affected
after the eNodeB is upgraded.
Turning on the switch has an impact only in the following scenario:
Some UEs in a cell have light uplink traffic and the eNodeB
providing the cell has DRX enabled. In this scenario, the IBLER
and RBLER decrease and resource blocks (RBs) are better utilized.
Impact on NEs
None
Impact on hardware
None

None

UlEnhancedSrSchSwitch(UlEnhancedSrSchSwitch) option has
been added to the UlSchSwitch parameter in the
CELLALGOSWITCH MO.
Issue 01 (2014-01-30)

152
1 Feature Updates

None
Related
Operations

UlEnhancedSrSchSwitch(UlEnhancedSrSchSwitch) check box
selected under the UlSchSwitch parameter to enable the optimized
SR handling mechanism.

UlEnhancedSrSchSwitch(UlEnhancedSrSchSwitch) check box
cleared under the UlSchSwitch parameter to disable the optimized
SR handling mechanism.
Trouble
Ticket
Number
DTS2013062001469
Feature ID
LBFD-002025
LOFD-00101502
82. Uplink RB Allocation Policy Configurable

Description
A new uplink resource block (RB) allocation policy has been added.
This policy adaptively switches between frequency selective
scheduling and interference-randomization-based scheduling. When the
network is lightly loaded, different sets of RBs are allocated to
neighboring cells to reduce inter-cell interference and increase user
throughput.
Implementa
tion
The current version supports the new uplink RB allocation policy that
adaptively switches between frequency selective scheduling and
interference-randomization-based scheduling.
Impact

The default value for the UlRbAllocationStrategy parameter is
FS_NONFS_ADAPTIVE. Therefore, capacity and performance
are not affected after the eNodeB is upgraded. If the
UlRbAllocationStrategy parameter is set to
FS_INRANDOM_ADAPTIVE, both the cell edge throughput and
the overall cell throughput increase when the cell is lightly loaded,
and the cell edge throughput increases but the overall cell
throughput may decrease when the cell is heavily loaded.
Impact on NEs
None
Impact on hardware
None

None

Issue 01 (2014-01-30)

153
1 Feature Updates

The UlRbAllocationStrategy parameter has been added to the
CellUlschAlgo MO.
This parameter has two values: FS_NONFS_ADAPTIVE and
FS_INRANDOM_ADAPTIVE. The value
FS_NONFS_ADAPTIVE indicates the RB allocation policy that
adaptively switches between frequency selective scheduling and
non-frequency-selective scheduling, which is the default policy
used in earlier versions. The value FS_INRANDOM_ADAPTIVE
indicates the new policy.

None
Related
Operations
Run the MOD CELLULSCHALGO command with the

UlRbAllocationStrategy parameter set to FS_NONFS_ADAPTIVE
or FS_INRANDOM_ADAPTIVE.
Trouble
Ticket
Number
DTS2013061906354
Feature ID
LOFD-00101502
83. SRS Function Disabling for a Cell on an LBBPc If the Number of Receive Antennas Is
Less Than 4
Issue 01 (2014-01-30)

154
Description
1 Feature Updates
If the number of receive antennas is less than 4 for a cell on an LBBPc,

the eNodeB can now disable the sounding reference signal (SRS)
function by not configuring SRS subframes. As a result, the uplink
throughput of UEs near or at a medium distance from the cell center
increases.
Implementati If the number of receive antennas is less than 4 and the SrsCfgInd
parameter is set to BOOLEAN_FALSE(False) for a cell on an LBBPc,
on
the eNodeB does not configure SRS subframes. When a UE accesses the
network, the eNodeB does not allocate SRS resources but uses
demodulation reference signals (DMRSs) on the PUSCH to measure the
timing advance (TA) for the UE.
However, if the number of receive antennas is equal to or greater than 4,
the eNodeB allocates SRS resources to a UE when the UE accesses the
network, regardless of the SrsCfgInd parameter setting.
Impact

The peak uplink throughput for the only UE in a cell increases by 2-3
Mbit/s, the uplink throughput for a UE near or at a medium distance
from the cell center increases by 5%, the uplink throughput for a UE at
the cell edge slightly decreases, and the number of control channel
elements (CCEs) on the physical downlink control channel (PDCCH)
slightly increases.
Impact on NEs
None
Impact on hardware
None

None

Impact on configuration management: The setting of the SrsCfgInd
parameter in the SRSCfg MO now also takes effect for a cell that is
configured on an LBBPc and has less than four receive antennas.

None
Related
Operations
To disable the SRS function, run the MOD SRSCFG command with the
SrsCfgInd parameter set to BOOLEAN_FALSE(False). You may
disable this function for a cell on an LBBPd or for a cell that is
configured on an LBBPc and has less than four receive antennas.
To enable the SRS function, run the MOD SRSCFG command with the
SrsCfgInd parameter set to BOOLEAN_TRUE(True).
Trouble
Ticket
Number
DTS2013061905393
Feature ID
LBFD-001001
Issue 01 (2014-01-30)

155
1 Feature Updates
LBFD-002003
84. Optimized Levels of Estimated Delay Spread

Description
After delay spread is quantified into different levels, selecting a proper

delay spread level improves channel estimation performance. Some delay
spread on a channel is less than 1 s, which falls into the delay spread
level of 0-3 s in earlier versions. Using 3 s for channel estimation may
cause certain loss. To address this issue, more delay spread levels are now
available.
Implementati The previous lowest level of 0-3 s has been divided into two levels: 0-1
s and 1-3 s.
on
Impact

PUSCH demodulation performance improves and uplink throughput
increases, especially for a channel with little delay spread, such as a
channel of Extended Pedestrian A (EPA) model. The maximum gain
can be 0.45 dB when the number of resource blocks (RBs) is about 10
and the modulation and coding scheme (MCS) index is 5 or 6. If the
number of RBs is less than 3 or the MCS index is greater than 6, the
gain is not noticeable.
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
DTS2013060400803
Feature ID
None
85. Optimized VQI-based Evaluation of Uplink Uu Voice Quality
Issue 01 (2014-01-30)

156
Description
1 Feature Updates
Uplink voice quality indicators (VQIs) are used to evaluate the uplink
voice quality on the Uu interface and calculate the quality level.
In earlier versions, the eNodeB may mistakenly consider normal voice
packets to be lost and underestimate the uplink Uu voice quality. To
address this issue, a new default threshold is now used to evaluate the
impact of uplink delay variations on voice quality during uplink VQI
calculation.
Implementati The default uplink delay variation threshold has been changed to 100 ms.
on
Impact

None
Impact on NEs
None
Impact on hardware
None

None

Impact on performance management:
The proportion of uplink voice services with good quality

increases, whereas the proportion of uplink voice services with
poor quality decreases.
The voice quality monitoring results on the M2000 and call history
records (CHRs) show that the uplink voice quality improves.

None
Related Operati None

ons
Trouble
Ticket
Number
None
Feature ID
None
86. Inter-frequency MLB Without Load Information Exchange
Issue 01 (2014-01-30)

157
Description
1 Feature Updates
eNodeBs now support balancing of physical resource block (PRB) usage

and the number of UEs between inter-frequency cells without load
information exchange. When the PRB usage in a cell is high or the
number of UEs in the cell is large, the eNodeB hands over some UEs to
neighboring cells to reduce the source cell load.
Implementati 1.
on
Impact
The eNodeB determines whether to trigger a blind mobility load

balancing (MLB) procedure in a cell based on the cell load
measurement result.
2.
If blind MLB is triggered, the cell sends handover request messages

with the cause value "Reduce load in serving cell" to its neighboring
cells.
3.
After receiving the handover request messages, the neighboring

cells determine whether to accept the handover requests based on
their own cell load if blind MLB is enabled in the neighboring cells.
4.
The source eNodeB determines whether to transfer cell load to the

neighboring cells according to the response messages sent by the
neighboring cells.
The InterFreqBlindMlbSwitch(InterFreqBlindMlbSwitch)
option has been added to the MlbAlgoSwitch parameter to
determine whether to enable or disable blind MLB. This switch is
off by default, indicating that blind MLB is disabled. In this case,
system capacity and performance are not affected.
After the InterFreqBlindMlbSwitch(InterFreqBlindMlbSwitch)

option is selected, the eNodeB hands over some UEs to
neighboring cells if the load in a cell is high. As a result, the load in
the source cell decreases, whereas the load in the neighboring cells
increases.
The number of handover attempts and the number of handovers

may increase.
Impact on NEs
None
Impact on hardware
None

None

Issue 01 (2014-01-30)
The InterFreqBlindMlbSwitch(InterFreqBlindMlbSwitch)
option has been added to the MlbAlgoSwitch parameter in the
CellAlgoSwitch MO to control blind MLB.
The following parameters have been added to the CellMLB MO.

158
1 Feature Updates
Parameter
Function
MlbTriggerMode
Specifies whether to trigger MLB based on

PRB usage only, the number of UEs only, or
either of them.
InterFreqMlbUeNu
mThd
Specifies the threshold for the number of UEs

used during blind MLB evaluation.
MlbUeNumOffset
Specifies the offset to be used together with

the threshold for the number of UEs during
blind MLB evaluation.
MlbMaxUeNum
Specifies the maximum number of UEs that

can be handed over to other cells during blind
MLB.
MlbUeSelectPrbThd
Specifies the PRB usage threshold used to

select UEs for blind MLB.
The following parameters in the CellMLB MO have been

modified.
Parameter
New Function
InterFreqMlbThd
Specifies the PRB usage threshold used in

blind MLB evaluation.
LoadOffset
Specifies the offset to be used together with

the PRB usage threshold during blind MLB
evaluation.
LoadDiffThd
Specifies the upper limit on the PRB usage

used to select UEs for blind MLB.
The MlbTargetInd parameter has been added to the

EutranInterNFreq MO to specify whether to allow blind MLB to
a neighboring E-UTRAN frequency.


None
Issue 01 (2014-01-30)

159
Related
Operations
1 Feature Updates
To enable blind inter-frequency MLB, run the MOD

CELLALGOSWITCH command with the
InterFreqBlindMlbSwitch(InterFreqBlindMlbSwitch) check box
selected and the InterFreqMlbSwitch(InterFreqMlbSwitch) check
box cleared under the MlbAlgoSwitch parameter.
To modify blind MLB configurations, run the MOD CELLMLB

command with the following parameters set:
MlbTriggerMode
InterFreqMlbUeNumThd
MlbUeNumOffset
MlbMaxUeNum
MlbUeSelectPrbThd
InterFreqMlbThd
LoadOffset
LoadDiffThd
To disable blind MLB to a frequency, run the MOD

EUTRANINTERNFREQ command with MlbTargetInd set to
NOT_ALLOWED(NOT_ALLOWED).
Trouble
Ticket
Number
DTS2013062200445
Feature ID
LOFD-001032
87. Increased Maximum Number of X2 Interfaces
Issue 01 (2014-01-30)

160
Description
1 Feature Updates
The maximum number of X2 interfaces that an eNodeB supports has

been increased from 64 to 96. An eNodeB now can be connected to a
maximum of 96 neighboring eNodeBs at the same time through the X2
interfaces.
Implementati The eNodeB supports more SCTP links for X2 interfaces.

on
Impact

None
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
Run the ADD X2INTERFACE command to add X2 interfaces. A

maximum of 96 X2 interfaces can be configured.
Trouble
Ticket
Number
DTS2013062007984
Feature ID
None
88. Optimized PUCCH Resource Allocation
Issue 01 (2014-01-30)

161
Description
1 Feature Updates
After physical uplink control channel (PUCCH) resource adaption is

enabled, the resources allocated for transmitting channel quality
indicators (CQIs), scheduling request indicators (SRIs), and
acknowledgments (ACKs) vary with the network load status. The
allocated PUCCH resources increase or decrease adaptively.
PUCCH resource allocation for CQIs, SRIs, and ACKs is now optimized
so that the resource blocks (RBs) allocated to the PUCCH increase or
decrease more smoothly.
Implementati The CQI resource adjustment levels are split into more levels, and the
ACK/SRI resource allocation is better designed. As a result, the total
on
number of RBs allocated to the PUCCH is much closer to that of RBs
required for UEs on live networks.
Impact

The number of RBs allocated to the PUCCH increases or decreases
more smoothly and is much closer to that of RBs required for UEs on
live networks. In some scenarios, the number of RBs used by the
PUCCH decreases, and therefore the uplink throughput increases.
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
None
Feature ID
LBFD-002003
Note: Whether to enable PUCCH resource adaption is controlled by the

PucchAlgoSwitch parameter. This function is enabled by default.
89. Optimized Measurement of E-RAB Setup and Modification Failures
Issue 01 (2014-01-30)

162
Description
1 Feature Updates
In versions earlier than V100R008C00SPC200, when an eNodeB

receives an E-RAB SETUP REQUEST message from the MME and
detects that the configurations for GBR bearers indicated in the E-RAB
Guaranteed Bit Rate Downlink or E-RAB Guaranteed Bit Rate Uplink IE
exceed the UE capabilities, the eNodeB sends the MME an E-RAB
SETUP RESPONSE message with the failure cause "Radio resources not
available". Under this condition, the L.E-RAB.FailEst.NoRadioRes and
L.E-RAB.FailEst.RNL counters are incremented. In
V100R008C00SPC200 or later, in the preceding scenario, the eNodeB
sends the MME an E-RAB SETUP RESPONSE message with the failure
cause "Invalid QoS combination" and the L.E-RAB.FailEst.MME
counter is incremented. In this manner, the numbers of E-RAB setup
failures for different causes are measured more precisely.
In versions earlier than V100R008C00SPC200, when an eNodeB
receives an E-RAB MODIFY REQUEST message from the MME and
detects that the configurations for GBR bearers indicated in the E-RAB
Guaranteed Bit Rate Downlink or E-RAB Guaranteed Bit Rate Uplink IE
exceed the UE capabilities, the eNodeB sends the MME an E-RAB
MODIFY RESPONSE message with the failure cause "Radio resources
not available". Under this condition, the L.ERAB.FailModify.NoRadioRes counter is incremented. In
V100R008C00SPC200 or later, in the preceding scenario, the eNodeB
sends the MME an E-RAB MODIFY RESPONSE message with the
failure cause "Invalid QoS combination" and the L.ERAB.FailModify.NoRadioRes counter is not incremented. In this
manner, the numbers of E-RAB modification failures for different causes
are measured more precisely.
Implementati In the preceding scenario, the L.E-RAB.FailEst.MME counter is

incremented when an E-RAB failed to be set up with the failure cause
on
"Invalid QoS combination" sent to the MME and the L.ERAB.FailModify.NoRadioRes counter is not incremented when an ERAB failed to be modified with the failure cause "Invalid QoS
combination" sent to the MME.
Impact

In V100R008C00SPC200, when an E-RAB failed to be set up in the
preceding scenario, the values of the L.E-RAB.FailEst.NoRadioRes
and L.E-RAB.FailEst.RNL counters decrease and the value of the
L.E-RAB.FailEst.MME counter increases. When an E-RAB fails to
be modified in the preceding scenario, the value of the L.ERAB.FailModify.NoRadioRes counter decreases.
Impact on NEs
None
Impact on hardware
None

None

Issue 01 (2014-01-30)

163
1 Feature Updates


None
Related
Operations
None
Trouble
Ticket
Number
DTS2013053006183
Feature ID
None
90. Support for QCI-based Link Release Waiting Duration
Issue 01 (2014-01-30)

164
1 Feature Updates
Description
When an eNodeB detects that a radio link is abnormal, the eNodeB waits
the UE to initiate an RRC connection reestablishment procedure to
restore services. If the waiting duration times out, the eNodeB releases
the services. This feature enables users to set different waiting durations
for services with different QCIs.
Implementation
When the eNodeB detects that a radio link is abnormal, it starts the
waiting timer based on the QCI of the service. If the link carries multiple
services, the shortest timer length among the lengths corresponding to
services is used.
Impact

In conditions where a link that carries multiple services becomes
abnormal, the value of the L.E-RAB.AbnormRel counter may
increase and that of the L.Traffic.User.Avg counter may decrease
because in this case, the timer with the shortest length is used and the
probability of link recovery is lower.
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
Run the MOD CELLSTANDARDQCI or ADD

CELLEXTENDEDQCI/MOD CELLEXTENDEDQCI command and
set the TrafficRelDelay parameter.
Trouble Ticket
Number
DTS2013071007440
Feature ID
None
91. Optimized Triggering Condition for Delivering Inter-RAT Measurement Configurations

During a Coverage-based Inter-RAT Handover
Issue 01 (2014-01-30)

165
Description
1 Feature Updates
An eNodeB delivers measurement configurations to UEs through the

RRC Connection Reconfiguration message. In the case of a coveragebased inter-RAT handover, the eNodeB first delivers inter-RAT event A2
measurement configurations to a UE when the UE accesses the network.
After the UE reports inter-RAT event A2 to the eNodeB, the eNodeB
delivers inter-RAT measurement configurations to the UE. Before the
optimization, the eNodeB delivers the inter-RAT measurement
configurations again when RRC connection reconfiguration is triggered
by other causes (for example, DRX configurations).
Implementati During a coverage-based inter-RAT handover, the eNodeB delivers interRAT measurement configurations to the UE only after the UE reports
on
inter-RAT event A2 to the eNodeB.
Impact

This change does not affect KPIs. It only deceases the number of
times the eNodeB delivers duplicate inter-RAT measurement
configurations.
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
None
Trouble
Ticket
Number
DTS2013051400686
Feature ID
LOFD-001019
LOFD-001020
92. Optimized Cause Value for an E-RAB Release When the Number of Retransmissions at
the RLC Layer Reaches the Maximum
Issue 01 (2014-01-30)

166
Description
1 Feature Updates
When an E-RAB of a UE is released because the number of

retransmissions at the Radio Link Control (RLC) layer reaches the
maximum, the eNodeB sends the MME an E-RAB RELEASE
INDICATION message.
In versions earlier than V100R008C00SPC220, the message carries a

cause value of "Radio resources not available."
In V100R008C00SPC220 or later versions, the message carries a

cause value of "Failure in the Radio Interface Procedure" to reflect
the release cause more correctly.
Implementation
The cause value in the E-RAB RELEASE INDICATION message sent

in the preceding scenario has been changed to "Failure in the Radio
Interface Procedure."
Impact

None
Impact on NEs
None
Impact on hardware
None

None


None
Related Operations None

Trouble Ticket
Number
DTS2013080102428
Feature ID
None
93. Modified Demodulation Position in the PDCCH Search Space for CA UEs
Issue 01 (2014-01-30)

167
Description
1 Feature Updates
Previously, carrier aggregation (CA) UEs demodulate physical downlink

control channels (PDCCHs) in the common search space.
Now, if a CA UE supports cross-carrier scheduling and is assigned a
carrier indicator field (CIF), the UE demodulates PDCCHs in the
common search space. Otherwise, the UE demodulates PDCCHs in the
UE-specific search space.
Implementati In accordance with 3GPP TS 36.213 V10.9.0, bit 3 is added to the

reserved parameter eNBRsvdPara.RsvdSwPara2. This bit controls
on
whether CA UEs regard the overlapping PDCCH candidates of the
common search space and UE-specific search space, which are
transmitted in the PCell, as PDCCH candidates of the common or UEspecific search space.
The modification requires that UEs comply with 3GPP TS 36.213
V10.9.0.
When bit 3 of the eNBRsvdPara.RsvdSwPara2 parameter is set to 1: If
a CA UE supports cross-carrier scheduling and the eNodeB assigns the
UE a CIF by using RRC signaling, the UE decides that the overlapping
PDCCH candidates belong to the common search space. Otherwise, the
UE decides that the overlapping PDCCH candidates belong to the UEspecific search space. Bit 3 of the eNBRsvdPara.RsvdSwPara2
parameter is set to 1 by default.
When bit 3 of the eNBRsvdPara.RsvdSwPara2 parameter is set to 0:
The CA UE always decides that the overlapping PDCCH candidates
belong to the common search space.
Impact

If bit 3 of the eNBRsvdPara.RsvdSwPara2 parameter is set to 1 but
a CA UE does not comply with 3GPP TS 36.213 version 10.9.0
Release 10, this UE may incorrectly demodulate the PDCCHs and
have a lower throughput. Therefore, bit 3 of the
eNBRsvdPara.RsvdSwPara2 parameter must be set to 0 if many
UEs on the network do not comply with this latest 3GPP specification.
Impact on NEs
None
Impact on hardware
None

None


None
Related
Operations
Issue 01 (2014-01-30)
None

168
1 Feature Updates
Trouble
Ticket
Number
DTS2013110409005
Feature ID
LAOFD-001001, LAOFD-001002
1.3 Deleted Features

1.
IP Path Ping
Description
IP path ping is used to check whether an IP path is functioning

correctly.
Benefit
The problem that an IP path disconnection alarm is reported and

services are interrupted because IP path ping packets are filtered out by
routers on the network no longer occurs.
Implementatio IP path ping is replaced with the GTP-U echo function.

n
Related
Operations
The PATHCHK parameter in the IPPATH MO is deleted from MML

commands. This parameter is retained for the northbound interface but
the setting of this parameter does not take effect.
Trouble Ticket None

Number
Feature ID
Issue 01 (2014-01-30)
None

169

Feature Changes in BTS3900

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Feature Changes in BTS3900

Încărcat de

Drepturi de autor:

Formate disponibile

Feature Changes

in BTS3900 V100R008C00SPC220 Compared with

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential Copyright

BTS3900 Feature Changes

1.1 New Features

Number of Paging Messages Sent over the Uu Interface Configurable

The PagingSentNum parameter has been added to the PCCHCFG

Impact on capacity and performance

Impact on inter-NE interfaces

Impact on operation and maintenance

Huawei Proprietary and Confidential Copyright

BTS3900 Feature Changes

Impact on configuration management: The PagingSentNum

Impact on other features

Run the MOD PCCHCFG command with the PagingSentNum

MME Selection Based on MME Priorities

Users can configure MME priorities on an eNodeB to enable

1. The Priority parameter has been added to S1 and S1Interface

Impact on capacity and performance

Impact on inter-NE interfaces

Impact on operation and maintenance

Huawei Proprietary and Confidential Copyright

BTS3900 Feature Changes

Impact on other features

Run the following commands to set the Priority parameter to a

Run the following commands to query the Priority value:

Dual Carriers Supported by the RRU3201, RRU3220 and RRU3222

The RRU3201 with an intermediate frequency (IF) processing

The software enables dual-carrier signal filtering, and the

Impact on capacity and performance

Huawei Proprietary and Confidential Copyright

BTS3900 Feature Changes

Impact on inter-NE interfaces

Impact on operation and maintenance

Impact on other features

Cell Outage Detection Triggered by Internal Audit Exceptions

An eNodeB determines that an internal audit exception occurs when

Impact on capacity and performance

Impact on inter-NE interfaces

Impact on operation and maintenance

Huawei Proprietary and Confidential Copyright

BTS3900 Feature Changes

Impact on other features

eNodeB/P-GW Joint Congestion Control and Service Differentiation

eNodeB/P-GW Joint Congestion Control

eNodeB/P-GW Joint Service Differentiation

eNodeB/P-GW Joint Congestion Control

eNodeB/P-GW Joint Service Differentiation

eNodeB/P-GW Joint Congestion Control

Impact on capacity and performance

Huawei Proprietary and Confidential Copyright

BTS3900 Feature Changes

Impact on inter-NE interfaces

Impact on operation and maintenance

Impact on other features

eNodeB/P-GW Joint Service Differentiation

Impact on capacity and performance

Impact on inter-NE interfaces

Impact on operation and maintenance