Professional Documents
Culture Documents
V900R014C00SPC500
Release Notes
Issue
01
Date
2012-04-26
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.
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 01 (2012-04-26)
Date
2012-04-05
Reviewed
by
Date
2012-04-08
Tested by
Fu Xuedong
Date
2012-04-10
Approved
by
Zou Yu
Date
2012-04-26
Change History
Issu
e
Date
Author
Description
01
2012-04-26
First issue
Issue 01 (2012-04-26)
ii
Contents
Contents
1 Version Requirements...................................................................1
1.1 Product Version..................................................................................................................................................1
1.2 Software Versions..............................................................................................................................................1
1.3 Hardware Versions.............................................................................................................................................1
1.4 Related Product Versions...................................................................................................................................4
1.5 OS and Database Versions.................................................................................................................................7
1.6 Virus Scan Result...............................................................................................................................................7
2 Version Compatibility....................................................................9
2.1 Compatibility with Earlier Product Versions.....................................................................................................9
2.2 Compatibility with Earlier Board Software Versions........................................................................................9
3 Important Notes.......................................................................... 12
4 Changes from V900R014C00SPC300 to V900R014C00SPC500........13
4.1 What's New......................................................................................................................................................13
4.1.1 Feature Updates......................................................................................................................................13
4.1.2 Hardware Updates..................................................................................................................................37
4.1.3 Command Line Updates.........................................................................................................................37
4.1.4 Parameter Updates..................................................................................................................................37
4.1.5 Alarm Updates........................................................................................................................................37
4.1.6 Event Updates.........................................................................................................................................38
4.1.7 Counter Updates.....................................................................................................................................38
4.1.8 License Updates......................................................................................................................................38
4.2 Resolved Issues................................................................................................................................................38
4.3 Known Issues...................................................................................................................................................76
Issue 01 (2012-04-26)
iii
Contents
8 Related Documentation.............................................................396
8.1 V900R014C00 Documentation......................................................................................................................396
8.2 Updates to Related Documentation...............................................................................................................396
8.2.1 Changes from V900R014C00SPC300 to V900R014C00SPC500.......................................................396
8.2.2 Changes from V900R014C00SPC200 to V900R014C00SPC300.......................................................397
8.2.3 Changes from V900R013C00SPC500 to V900R014C00SPC200.......................................................397
8.2.4 Changes from V900R012C01SPC500 to V900R014C00SPC200.......................................................397
8.3 Obtaining Documentation..............................................................................................................................397
8.3.1 Support Website....................................................................................................................................397
Issue 01 (2012-04-26)
iv
Version Requirements
Product Model
Product Version
V900R014C00SPC500
Software Version
LMT
V900R014C00SPC500
OMU
V900R014C00SPC500
M2000 mediation
iManagerM2000_BSC6900GSM_MATCH_ENG_V200R012C
00SPC500
Logical
Board
Name
Bar Code
Label
PCB
Version
BIOS/Extended
BIOS Version
BootROM
Upgrade
Required
(Yes/No)
SCUa
SCUa
WP11PSCUa
Ver.D
258
Yes
SCUb
SCUb
WP11SCUb
Ver.B
117
Yes
Issue 01 (2012-04-26)
Physica
l Board
Name
Logical
Board
Name
Bar Code
Label
PCB
Version
BIOS/Extended
BIOS Version
BootROM
Upgrade
Required
(Yes/No)
GCUa
GCUa
WP11GCUa
Ver.B
224
Yes
224
Yes
224
Yes
257
Yes
224
Yes
Ver.C
Ver.F
GCGa
GCGa
WP11GCGa
Ver.B
Ver.C
Ver.F
TNUa
TNUa
WP11PTSUa
Ver.A
Ver.B
Ver.C
XPUa
XPUa/GCP
WP11XPUa
XPUa/RGCP
Ver.B
Ver.C
XPUa/MCP
DPUa
DPUa/GTC
WP11DPUa
Ver.A
Ver.B
Ver.C
DPUb
DPUb/GTC
WP11DPUb
Ver.C
224
Yes
DPUb/GPCU
DPUc
DPUc/GTC
WP11DPUc
Ver.C
224
Yes
DPUd
DPUd/GPCU
WP11DPUd
Ver.C
224
Yes
DPUf
DPUf
WP11PVCU
Ver.B
117
Yes
DPUg
DPUg
WP11DPUg
Ver.B
120
Yes
Ver.C
Ver.E
PEUa
PEUa/FR
WP11PEUa
Ver.A
120
Yes
PEUa/HDLC
PEUa/IP
PEUa/Abis_IP
POUa
POUa/IP
WP11POUa
Ver.A
120
Yes
FG2a
FG2a/GbIP
WP11FG2a
Ver.A
120
Yes
WP11GOUa
Ver.A
120
Yes
FG2a/IP
GOUa
GOUa/IP
Issue 01 (2012-04-26)
Physica
l Board
Name
Logical
Board
Name
Bar Code
Label
PCB
Version
BIOS/Extended
BIOS Version
BootROM
Upgrade
Required
(Yes/No)
EIUa
EIUa/Abis
WP11EIUa
Ver.A
255
Yes
255
Yes
120
Yes
120
Yes
120
Yes
120
Yes
EIUa/Ater
Ver.B
EIUa/Pb
EIUa/A
OIUa
OIUa/Abis
WP11OIUa
OIUa/Ater
Ver.A
Ver.B
OIUa/Pb
OIUa/A
XPUb
XPUb/GCP
WP11XPUb
Ver.B
XPUb/RGCP
Ver.C
XPUb/MCP
Ver.D
Ver.E
POUc
POUc/TDM
WP11POUc
POUc/IP
Ver.B
Ver.C
Ver.E
FG2c
FG2c/IP
WP11FG2c
Ver.B
Ver.C
Ver.E
GOUc
GOUc/IP
WP11GOUc
Ver.B
Ver.C
Ver.E
FG2d
FG2d/IP
WP11FG2d
Ver.E
120
Yes
GOUd
GOUd/IP
WP11GOUd
Ver.E
120
Yes
OMUa
OMUa
WP11OMUa
OMUb
OMUb
WP11OMUb
OMUc
OMUc
WP11OMUc
Ver.B
025
Yes
DPUe
DPUe
WP11DPUe
Ver.B
120
Yes
Ver.C
Ver.E
NIUa
NIUa
WP11PNIUa
Ver.E
120
Yes
FG2d
FG2d/IP
WP11FG2d
Ver.B
120
Yes
Ver.C
Ver.E
Issue 01 (2012-04-26)
Physica
l Board
Name
Logical
Board
Name
Bar Code
Label
PCB
Version
BIOS/Extended
BIOS Version
BootROM
Upgrade
Required
(Yes/No)
GOUd
GOUd/IP
WP11GOUd
Ver.B
120
Yes
Ver.C
Ver.E
Product Model
Product Version
CBC
CBC
CBC V300R001B02D001
(recommended)
MSC
G9
MSC9880
MSOFTX3000V100R005C01
(recommended among the earlier
versions, which are compatible with
the current version of the BSC, in
cases other than IP transport on the
A interface)
Remarks
G6
MSC9880
MSOFTX3000V200R008C03
Developed on the
ATCA platform
MSCV620R004C02B027
(recommended for China Mobile)
NA
MSCV600R004B03D103
(recommended for China Unicom)
MSCV610R002B12D004
(recommended for other telecom
operators)
Issue 01 (2012-04-26)
Product
Name
Product Model
Product Version
Remarks
G3
MSCV300R005B04D005
(recommended for deployment in
China)
NA
MSCV330R006B08D004
(recommended for deployment in
regions out of China)
UMG
UMG
NA
SGSN
SGSN9810 V800R009C01
(recommended)
GGSN
GGSN9811 V900R007C01
(recommended)
M2000-II
iManager M2000
V200R012C00SPC200 or later
CME
CME
iManager M2000-CME
V200R012C00SPC200 or later
VNP
VNP
V100R001C00SPC301 or later
INSIGHT
SHARP
INSIGHT SHARP
INSIGHT SHARP
V100R002C00SPC500
NASTAR
NASTAR
iManager Nastar
V600R010C00SPC200 or later
MBTS
MBTS
BTS3900V100R007C00SPC200 or
later
SRAN7.0
BTS3900 V100R004C00SPC100 or
later
SRAN6.0
BTS3900 V100R003C00SPC200 or
later
SRAN5.0
BTS3900 V100R002C00SPC120 or
later
SRAN3.0
Issue 01 (2012-04-26)
Product
Name
Product Model
Product Version
Remarks
BTS
BTS3900 series
(including the BTS3900,
BTS3900A, BTS3900L,
and DBS3900)
BTS3000V100R014C00SPC006 or
later
BSS14.0
BTS3000V100R0013C00SPC003 or
later
BSS13.0
BTS3000V100R0012C00SPC025 or
later
BSS12.0
BTS3900 V100R009C00SPC058 or
later
BSS9.0
BTS3900 V100R009C00SPC081 or
later (required for Abis over IP)
BTS3000V100R008C11SPC003 or
later
BSS8.1
BTS3000V600R013C00 or later
BSS13.0
BTS3000V100R008C12SPC008 or
later
BSS8.1
BTS3012 series
(including the BTS3012,
BTS3012AE, BTS3012II,
BTS3006C, and
BTS3002E)
BTS3000V200R0013C00 or later
BSS13.0
BTS3000V200R0012C00 or later
BSS12.0
BTS3000V200R009C00SPC002 or
later
BSS9.0
BTS3000V100R008C11SPC026 or
later
BSS8.1
BSS7.0
BSS7.0
PCU
BTS2X series
Not supported
NA
PCU35
V300R008C03SPH008(recommende
d), compatible with all
V300R008C03 versions
NA
PCU6000
V300R008C11SPH003(recommende
d), compatible with V300R008C03
and later
NA
Issue 01 (2012-04-26)
Database Version
Remarks
mysql 5.0
Patch package:
Win2k3ENx862011Basic
Patches
1. Access
http://support.huawei.com.
2. After a successful login,
choose Software Center >
Version Software > Wireless
Product Line> SingleRAN >
SRAN O&M tools.
3. Download
Win2k3ENx862011Basic and
the detailed information about
the patch is listed in the
document 2011Basic Patches
information list_20120104.xls.
Suse Linux 9
mysql 5.0
Dopra Linux
V100R001C03
mysql 5.0
Dopra Linux
V200R003C02
McAfee
Antivirus
Software
Version
ver.8.7.0i
Virus
Database
Version
6603
Scanning Date
2012-5-2
Issue 01 (2012-04-26)
Scanning
Result
Issue 01 (2012-04-26)
Normal
Version Compatibility
BSC6000V900R008
C12
BSC6000V900R008
C01
SCUa
GCUa
TNUa
XPUa
DPUa
DPUc
DPUd
PEUa
FG2a
Issue 01 (2012-04-26)
Board
Name
BSC6000V900R008
C12
BSC6000V900R008
C01
GOUa
EIUa
OIUa
OMUb
BSC6900V9
00R011
BSC6900V9
00R012C01
BSC6900V
900R013C0
0
SCUa
SCUb
GCUa
TNUa
XPUa
DPUa
DPUc
DPUd
DPUf
DPUg
PEUa
FG2a
GOUa
EIUa
OIUa
OMUb
GOUc
XPUb
FG2c
POUc
GCGa
POUa
Issue 01 (2012-04-26)
10
Board
Name
BSC6900V9
00R011
BSC6900V9
00R012C01
BSC6900V
900R013C0
0
OMUa
OMUc
DPUe
NIUa
FG2d
GOUd
Issue 01 (2012-04-26)
11
Important Notes
Item
Description
Time
No restriction.
Area/Site
None.
Others
Issue 01 (2012-04-26)
12
Changes from
V900R014C00SPC300 to
V900R014C00SPC500
4.1 What's New
4.1.1 Feature Updates
New Features
1.
Issue 01 (2012-04-26)
13
Description
This function forcibly applies the Secure Sockets Layer (SSL) protocol to
the communication between a BSC6900 and external devices.
External devices include peripherals that interconnect with the BSC6900,
for example, the Vendor Network Probe (VNP), and devices that remotely
manage the BSC6900, for example, the M2000.
Benefit
Implementatio This function is enabled when the CONNTYPE parameter in the SET
CONNTYPE command is set to ONLY_SSL(Only SSL Connection).
n
Before this function is enabled, a root certificate file, a certificate file, and
a private key file must be added to the BSC6900.
After this function is enabled, the following must be done:
Related
Operations
The BSC6900 must automatically shut down all the non-SSL ports used
for communication with external devices.
2.
Issue 01 (2012-04-26)
None
14
Description
Benefit
Implementat 1.
ion
Run the DSP BRDVER command to obtain the current version number of
the rule library. Check whether the rule library is of the desired version.
2.
If the version of the current rule library is different from the desired
version, upload the desired rule library file to the OMU active
workspace/bam/version_x/bin/fam directory through FTP.
3.
Run the LOD BRD command to load the file to the NIUa. Then, run the
RST BRD command to reset the NIUa.
The active OMU does not check the rule library file during the integrity check.
The standby OMU automatically synchronizes the rule library file with the
active OMU.
The CMP BRDVER command no longer checks the rule library file, avoiding
false alarm reporting.
Related
Operations
1.
To query the version number of the current rule library, run the DSP
BRDVER command. The following is an example:
To load the rule library file to the NIUa, run the LOD BRD command. The
following is an example:
To enable the new rule library to take effect on the NIUa, run the RST
BRD command to reset the NIUa. The following is an example:
CR GU01245b
Feature ID
None
3.
Issue 01 (2012-04-26)
15
Description
Benefit
The optimization prevents MSs whose SIM cards do not register with
the UMTS network from failing to access the network.
Related
Operations
4.
Issue 01 (2012-04-26)
GBFD-114325
16
Description
Benefit
Implementati
on
In LLC PDU data blocks, the first two segments of the server IP
address is set to 0XFF and IP addresses of MSs are encrypted. All
GMM signaling messages are traced.
PS Um tracing
Only RLC/MAC headers are reserved in RLC data blocks. All control
signaling messages are traced.
PS Abis tracing
PS recording
PS CHR
In the PS CHR, the first two segments of the server IP address is set
to 0XFF, and IP addresses, IMSIs, and IMEIs of MSs are encrypted.
Related
Operations
None
Trouble
Ticket
Number
DTS2012010402091
Feature ID
None
5.
Issue 01 (2012-04-26)
17
Description
Benefit
Implementati
on
Related
Operations
1. Set the cipher key and enable the function of anonymizing user
identity information in tracing messages and log files by
performing the following operations:
On the M2000, choose Monitor > Signaling Trace >
Anonymous Policy Management.
In the displayed dialog box, select Change Cipher Key, type the
cipher key in Cipher Key and Confirm Cipher Key. Then, click
OK. Select the Anonymous Policy option and click Enable
Anonymous Policy. Then, click OK.
2. Run the LST USERIDANONSWITCH command to check
whether the function of anonymizing user identity information in
tracing messages and log files is enabled.
Trouble
Ticket
Number
DTS2012022004903
Feature ID
None
6.
Issue 01 (2012-04-26)
Setting the Value of SI2Quater Indicator in the SI3 Message to TRUE in the NC1 or NC2
Mode
18
Description
The condition for setting the SI2Quater indicator in the SI3 message is
modified. This modification allows that the value of the SI2Quater
indicator in the SI3 message can be set to TRUE, instructing an MS to
parse the SI2Quater message, when the Network Control Mode
parameter is not set to NC0(NC0).
Benefit
If the interval specified in the 2Quater message is longer than 3.84s, the
values of the preceding counters decrease.
Implementati The value of SI2Quater indicator is set to TRUE if the Support Sent
2QUATER parameter is set to YES(Yes) and the Network Control Mode
on
parameter is set to NC1(NC1) or NC2(NC2).
Related
Operations
Trouble
Ticket
Number
GU01038
Feature ID
GBFD-111101
7.
Issue 01 (2012-04-26)
19
Description
This feature is optimized to ensure that a proper IBCA priority is set and
dynamic PDCH conversion is allowed when the IBCA algorithm is
enabled. Before the optimization, when the dynamic mobile allocation
index offset (MAIO) allocated to the PDCH is inconsistent with that
allocated to the TCH, the CS call occupying the TCH must be handed
over to another TCH, increasing the number of CS handovers. In
addition, the CS call may not be allocated to an optimal TCH due to an
improper IBCA priority.
Benefit
The optimization decreases the CS call drop rate and increases the
handover success rate and the value of the high quality indicator (HQI).
However, it also increases the TBF abnormal release rate.
Implementati 1. For the cells that participate in both radio frequency (RF) frequency
hopping (FH) and cyclic FH and are enabled with the IBCA
on
algorithm:
If the Enhanced IBCA PDCH Dynamic Conversion parameter is
set to ON(On) and the Target CIR for IBCA MAIO Configured
on TRX parameter is set to 255, TCHs in the cells cannot be
converted to dynamic PDCHs. In other situations, TCHs in the cells
can be converted to dynamic PDCHs. In addition, only the MAIOs
allocated to the PDCHs can be used. If the ongoing CS calls using
the allocated MAIOs experience soft blocking, TCH-to-PDCH
conversion cannot be performed until the timer specified by the
IBCA PDCH Dynamic Convert Penalty Timer parameter expires.
2. The Enhanced IBCA PDCH Dynamic Conversion parameter is
set to ON(On) when the BSC evaluates interference on TCHs. In
this situation, the BSC updates the IBCA priority by accumulating
the interference on TCHs, PDCHs, and SDCCHs.
Related
Operations
Trouble
Ticket
Number
GU1494
Feature ID
GBFD-117002
8.
Issue 01 (2012-04-26)
20
Description
Benefit
The platform is unified and VLAN polices for different products are
consistent.
Implementa
tion
Related
Operations
Trouble
Ticket
Number
DTS2012020601415
Feature ID
GBFD-118601
Modified Features
1.
Issue 01 (2012-04-26)
21
Description
The mechanism for masking the cause of ALM-21581 Path Fault has
been optimized.
Benefit
Implementati
on
If multiple faults cause a path fault, the BSC6900 reports ALM21581 Path Fault with the highest-priority cause.
The alarm causes are listed in descending order of priority: bearing
port not configured, bearing board fault, bearing port unavailable,
path unavailability notified by OM, and ping failure.
If ALM-21581 Path Fault with the cause "ping failure" has been
reported before a bearing port not configured fault is detected, the
BSC6900 clears the alarm and reports ALM-21581 Path Fault with
the cause "bearing port not configured".
If ALM-21581 Path Fault with the cause "ping failure" has been
reported before a bearing port unavailable fault is detected, the
BSC6900 clears the alarm.
Related
Operations
Trouble
Ticket
Number
DTS2012032006218
Feature ID
None
2.
Issue 01 (2012-04-26)
VAMOS
22
Description
Benefit
The downlink receive level of the new call is higher than or equal to
the sum of DL Rx Lev. Thres. of VAMOS Calls, Rx Lev. Thres.
Offset During Assignment, and OL Multiplexing Rx Level Thres.
Offset.
The uplink and downlink receive signal quality, AdapTive Cell Border
(ATCB), and P/N criterion meets specified conditions.
The downlink receive signal level of the established call is higher than
or equal to the sum of DL Rx Lev. Thres. of VAMOS Calls and OL
Multiplexing Rx Level Thres. Offset.
The uplink and downlink receive signal quality, ATCB, and P/N
criterion meets specified conditions.
Issue 01 (2012-04-26)
The uplink receive signal quality of the new call is smaller than or
equal to UL Rx Qual. Thres. of Established Calls minus Channel
Multiplex Rx Qual. Thres. Offset in Asgmt. and OL Multiplexing
Rx Quality Thres. Offset.
Downlink receive signal quality of the new call is smaller than or equal
to DL Rx Qual. Thres. of Established Calls minus
VamosAssUlQualThdOffset and Channel Multiplex Rx Qual.
Thres. Offset in Asgmt.
The downlink receive level of the new call, ATCB, and P/N criterion
meet specified conditions.
23
The uplink receive signal quality of the established call is smaller than
or equal to UL Rx Qual. Thres. of Established Calls minus OL
Multiplexing Rx Quality Thres. Offset.
The downlink receive signal level of the established call, ATCB, and
P/N criterion meet specified conditions.
Related
Operations
The uplink receive signal quality of the VAMOS call in the overlaid
subcell is higher than or equal to UL RX Bad Qual. Demultiplex
Thres. minus OL BQ Demultiplexing Rx Quality Thres. Offset.
The downlink receive signal quality of the VAMOS call in the overlaid
subcell is higher than or equal to DL RX Bad Qual. Demultiplex
Thres. minus OL BQ Demultiplexing Rx Quality Thres. Offset.
Trouble
Ticket
Number
CR GU01369
Feature ID
GBFD-115830
3.
Issue 01 (2012-04-26)
Setting Power Control Parameters for Overlaid and Underlaid Subcells Independently
24
Description
Benefit
Implementati
on
Related
Operations
4.
Issue 01 (2012-04-26)
GBFD-113201
HUAWEI I Handover
25
Description
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
CR GU1490
Feature ID
GBFD-110601
5.
Issue 01 (2012-04-26)
26
Description
Benefit
Implementati
on
Related
Operations
None
Trouble
Ticket
Number
CR GU00954
Feature ID
GBFD-118602
6.
Description
Benefit
Implementat
ion
Related
Operations
Trouble
Ticket
Number
CR GU01365
Feature ID
GBFD-118602
7.
Issue 01 (2012-04-26)
Enhanced TFO
27
Description
Benefit
Implementat
ion
Related
Operations
None
Trouble
Ticket
Number
CR GU1541
Feature ID
GBFD-115701
8.
Description
Benefit
The BSC supports TFO establishment for the MS (in another BSC)
that adopts the codec type UMTS_AMR_2 during inter-MSC calls or
2G-3G calls.
Implementat
ion
The TFO feature enables the BSC to process Tandem Free Operation
(TFO) messages and frames where the codec type is UMTS_AMR_2.
Related
Operations
None
Trouble
Ticket
Number
CR GU1518
Feature ID
GBFD-115701
9.
Issue 01 (2012-04-26)
28
Description
The policies for handling license control items have been optimized for
the following features during an upgrade:
Extended BCCH
Implementati For users who have not used the following features, the corresponding
license control items are added. For users who have used the following
on
features, the corresponding license control items remain unchanged.
Extended BCCH
For users who have used the preceding features, the upgrade tool
determines whether the licenses for the new version are sufficient
based on the current configuration data during an upgrade. If the
configuration data exceeds the license capacity, users are prompted to
delete the extra data within 60 days after the upgrade or to apply for a
new license that meets the requirements of the configuration data and
activate the license. Otherwise, the alarm ALM-20743 Insufficient
License Resources is reported every day within the period, and the
configuration on the BSC will be limited after 60 days.
Related
Operations
Trouble
Ticket
Number
DTS2012032301499
Feature ID
None
Issue 01 (2012-04-26)
29
Issue 01 (2012-04-26)
30
Description
Benefit
This feature helps users quickly and accurately identify faults about
simplified cell broadcast.
Implementati
on
Issue 01 (2012-04-26)
31
Trouble
Ticket
Number
DTS2011041401983
Feature ID
GBFD-113602
Benefit
Implementati The DTM Combined Update Optimize Type parameter has been added
to specify whether to optimize DTM combined update.
on
If this parameter is set to RAU_ACC_SEND_DELAY, the BSC sends
the Routing Area Updating Accept message to an MS in the packet
immediate assignment procedure after an SDCCH is released.
If this parameter is set to SDCCH_REL_DELAY, the BSC sends the
downlink GPRS Information message instead of the Routing Area
Updating Accept message to an MS. If the BSC receives a DTM Request
message on an SDCCH, the BSC delays releasing the SDCCH.
If this parameter is set to NO_DELAY, the BSC does not optimize DTM
combined update.
Related
Operations
GBFD-114151
Issue 01 (2012-04-26)
32
Description
Benefit
Implementatio The Ignore LAC parameter is added to the ADD SHALAMAP and
MOD SHALAMAP commands. If this parameter is set to ON(On),
n
the neighboring cell whose PLMN is consistent with that in the
mapping between handover sharing areas and location areas can be
considered as the target cell for handovers. If this parameter is set to
OFF(Off), the neighboring cell whose PLMN and LAC are consistent
with those in the mapping between handover sharing areas and location
areas can be considered as the target cell for handovers.
Related
Operations
GBFD-118702
13. Strategy for Selecting Speech Versions Based on the Speech Version Priorities Carried in
the Message from the MSC
Issue 01 (2012-04-26)
33
Description
Benefit
Related
Operations
Channel assignment
Intra-BSC handovers
GBFD-115701
Issue 01 (2012-04-26)
34
Description
Benefit
Trouble Ticket
Number
CR GU00957
Feature ID
None
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
CR GU01040
Feature ID
None
Issue 01 (2012-04-26)
35
Description
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
CR GU00943
Feature ID
None
Issue 01 (2012-04-26)
36
Description
Benefit
When an upper-level BTS is powered off, its lower-level BTSs that are
cascaded in the same link can still work properly.
Implementatio The BTS bypass function can be used in IP over E1 transmission mode.
n
The restriction on local IP addresses is removed. Specifically, when
local IP addresses of PPP links or ML PPP link groups on cascaded
BTSs are all 0s, these IP addresses can be configured in the same
network segment.
The restrictions on scenarios where this feature is used are as follows:
Related
Operations
The BTS bypass function is not supported when two or more E1 are
used.
The BTS bypass function is effective only when at least one PPP link
or ML PPP link is configured on port 0.
GBFD-116601
Issue 01 (2012-04-26)
37
Description
Benefit
The BSC can work with BTSs configured with RRU3922Es (a new
MRRU type).
ADD BTSRXUBRD
MOD BTSRXUBRD
Trouble Ticket
Number
CR GU01307
Feature ID
None
Benefit
Implementa
tion
Related
Operations
None
Trouble
Ticket
Number
CR GU1489
Feature ID
None
Deleted Features
None.
Issue 01 (2012-04-26)
38
Modified Hardware
None.
Removed Hardware
None.
Issue 01 (2012-04-26)
39
The EIUa or OIUa board that serves as an Abis interface board may reset
when you perform any of the following operations:
Adding a BTS
Removing a BTS
Activating a cell
Deactivating a cell
Severity
Minor
Root Cause
Solution
Solution
Impact
None
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC500_001
2.
Failed Communication Between the OMU Board and BSC6900 Boards After a NonPhysical-Layer Fault Occurs on the Link Connecting the OMU Board and the SCU Board
The panel on the LMT shows that all BSC6900 boards are faulty or not
detected.
Severity
Minor
Root Cause
Solution
A function has been added to detect faults on the links between the OMU
board and SCU board. After such a fault is detected, ALM-20223
Communication Between GE Switching Board and OMU Faulty is still
reported. However, the BSC6900 will automatically block the faulty link
so that the SCU board can communicate with the OMU board by using a
functional link.
Solution
Impact
None
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC500_002
Issue 01 (2012-04-26)
40
3.
The BSC increases the flow control level over the A interface when the
flow control level should be decreased.
Severity
Minor
Root Cause
When the BSC converts unsigned long data to unsigned char data,
precision loss occurs if the unsigned long data exceeds 256.
Solution
The BSC now checks whether the unsigned long data to be converted
exceeds 256. If the data exceeds 256, the BSC provides protection for
the data. This prevents precision loss.
Solution
Impact
None
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC500_500
4.
The BSC does not record the information about discarded paging messages
The BSC discards excessive paging messages and records related logs,
but does not provide counters indicating information about discarded
paging messages.
Severity
Minor
Root Cause
Solution
The maximum number of buffered IMSIs has been increased. If the BSC
discards excessive paging messages, it now records system faults in
logs.
Solution
Impact
None
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC500_501
5.
Issue 01 (2012-04-26)
The statistical value of the AR3555A: Rate of TCHs in Busy State counter is greater than
the actual value.
41
Severity
Minor
Root Cause
The AR3555A: Rate of TCHs in Busy State counter provides the rate of
occupied TCHs to available TCHs in a cell in a measurement period.
The statistical value of available TCHs is smaller than the actual value,
and therefore the statistical value of the AR3555A: Rate of TCHs in
Busy State counter is greater than the actual value.
Solution
Solution
Impact
After the solution is used, the values of the following counters decrease:
Test Case ID
6.
Issue 01 (2012-04-26)
CASE_Commercial_PR_Regression_V9R14C00SPC500_502
The BSC configured with an external PCU does not measure the CR3001-Number of
Initially Configured Channels (Static PDCH) counter.
42
The BSC configured with an external PCU does not measure the
CR3001-Number of Initially Configured Channels (Static PDCH)
counter.
Severity
Minor
Root Cause
Solution
The BSC configured with an external PCU now measures the CR3001Number of Initially Configured Channels (Static PDCH) counter.
Solution
Impact
After this solution is used for the BSC configured with an external PCU,
the values of the following counters increase:
After this solution is used for the BSC configured with a built-in PCU,
the values of the following counters decrease:
Test Case ID
7.
Issue 01 (2012-04-26)
CASE_Commercial_PR_Regression_V9R14C00SPC500_503
The value of the TK3104: Traffic Volume on TCH Carrying Traffic in One Location
Group counter is doubled after the MR.Preprocessing parameter is set to
BSC_Preprocessing(BSC preprocessing).
43
Trouble
Ticket
Number
DTS2012040300561
Description
Severity
Major
Root Cause
Solution
The BSC now measures the number of MRs based on the number of
original MRs. Specifically, if the Sent Freq.of preprocessed MR parameter
is set to Once_ps(Once every second), the number of MRs is incremented
by two each time the BTS reports an MR. In this way, the BSC measures
the TK3104:Traffic Volume on TCH Carrying Traffic in One Location
Group counter based on the number of original MRs instead of the setting
of the Sent Freq.of preprocessed MR parameter.
Solution
Impact
8.
Issue 01 (2012-04-26)
CASE_Commercial_PR_Regression_V9R14C00SPC500_504
44
Trouble
Ticket
Number
DTS2012022005028
Description
Severity
Suggestion
Root Cause
When AMRC is enabled, the BSC sends different AMR sets to the BTS
and the TC subrack.
Solution
Solution
Impact
None
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC500_505
9.
Issue 01 (2012-04-26)
45
Trouble
Ticket
Number
DTS2011120900137
Description
Severity
Suggestion
Root Cause
The formulas used for calculating the values of the Failed Outgoing
Inter-Cell Handovers and Outgoing Inter-Cell Handover Commands
counters do not include directed retry-related counters.
Solution
Solution
Impact
Issue 01 (2012-04-26)
46
CASE_Commercial_PR_Regression_V9R14C00SPC500_506
10. The measured values of some counters related to inter-concentric cell handovers are
incorrect.
Issue 01 (2012-04-26)
47
Severity
Major
Root Cause
Solution
Solution
Impact
After this solution is used, the values of the following counters may
fluctuate:
Issue 01 (2012-04-26)
48
CASE_Commercial_PR_Regression_V9R14C00SPC500_507
11. Background service-related counters are incorrectly measured after the PFC function is
enabled.
Trouble
Ticket
Number
DTS2012021506256
Description
Severity
Minor
Root Cause
Solution
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC500_508
Issue 01 (2012-04-26)
49
Trouble
Ticket
Number
DTS2012022406780
Description
Severity
Suggestion
Root Cause
Solution
Solution
Impact
After this solution is used, the values of the following counters increase if
an MS hangs up after a handover is triggered:
Issue 01 (2012-04-26)
50
Trouble
Ticket
Number
DTS2012031507936
Description
Severity
Minor
Root Cause
The BSC does not perform penalty on the filtering algorithm in the
source cell after a quick handover. In addition, the Quick Handover
Offset parameter is set to 0.
Solution
The BSC now performs penalty on the filtering algorithm in the source
cell after a quick handover.
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC500_510
Issue 01 (2012-04-26)
51
Trouble
Ticket
Number
DTS2011111403773
Description
Severity
Warning
Root Cause
Solution
Solution
Impact
Changes have been made to display counter units correctly on the M2000
and PRS, facilitating the understanding these counters.
For example, a counter value has changed from 7.84 to 7.84% on the
M2000.
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC500_511
15. The session ID of a user that has logged in to the web LMT may be stolen.
Issue 01 (2012-04-26)
52
Trouble
Ticket
Number
DTS2012030600835
Description
The web LMT manages the status and data of login users through the
session mechanism. After a user logs in to the web LMT, the web
browser sends a Hypertext Transfer Protocol (HTTP) request to the
LMT server. The uniform resource locator (URL) in the request includes
the user session ID. If the _sid parameter is intercepted, an attacker can
forge a similar URL on another PC and send the URL to the server to
perform unauthorized operations.
Severity
Minor
Root Cause
Solution
The security loophole of the web LMT system has been closed.
The web LMT now does not consider the user session ID as a common
HTTP request parameter any longer. Instead, it stores the user session ID
in the cookies of the web browser. The cookies are automatically sent to
the web LMT server with the HTTP request and become invalid after a
user closes the web browser. The web LMT server checks whether the
request is valid by verifying the user session ID contained in the HTTP
request cookies.
In this way, the cookies and the client web browser are bound.
Therefore, attackers cannot intercept user session IDs to perform
unauthorized operations.
Solution
Impact
User session IDs are saved in the cookies of the web browser to ensure
security. However, this brings about the following impacts:
1.
The web LMT requires that the web browser allow cookies. If the
cookies are blocked, users will fail to log in to the web LMT.
2.
Issue 01 (2012-04-26)
53
page does not share the same session ID with the old pages, and
therefore multiple web LMTs can be opened for one NE.
Another cause for the preceding error is that the user session ID saved in
the cookies remains valid after a user logs out of the LMT unexpectedly.
In this case, Internet Explorer 6/Internet Explorer 7 users need to close
the web LMT page; Internet Explorer 8/Internet Explorer 9 and Firefox
users need to close all opened pages to invalidate the old user session
ID, restart the web browser, and log in to the web LMT again.
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC500_512
16. Some PS counters deteriorate when the Start Flex MAIO Switch parameter is set to
ON(On).
Issue 01 (2012-04-26)
54
Trouble
Ticket
Number
DTS2012020101920
Description
Before the GBSS is upgraded to a version earlier than 14.0, the Start
Flex MAIO Switch parameter is set to ON(On) and dynamic channel
conversion messages are sent and received over operation and
maintenance links (OMLs). After the upgrade, dynamic channel
conversion messages are sent and received over radio signaling links
(RSLs). As a result, the uplink and downlink TBF establishment success
rates decrease and the downlink call drop rate increases on the entire
network. The involved counters are as follows:
Severity
Major
Root Cause
The BSC does not send mobile allocation index offsets (MAIOs) to the
BTS during dynamic TCH-to-PDCH conversions. As a result, the
MAIOs saved on the BSC are inconsistent with those saved on the BTS.
Solution
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC500_513
Issue 01 (2012-04-26)
55
Trouble
Ticket
Number
DTS2012030606514
Description
Severity
Major
Root Cause
Solution
The preceding counters are not used now. Instead, the following counters
are added:
A3408:CELL.TRAU.TFO.HO.REQ.TIMES.INCOMP
A3409:CELL.TRAU.TFO.HO.CMD.TIMES.INCOMP
A3410:CELL.TRAU.TFO.HO.FAIL.TIMES.INCOMP
RA3408:CELL.TRAU.TFO.HO.SUCC.RATE.INCOMP
The A3408 counter measures the number of handover requests during
internal intra- and inter-cell handovers due to TFO speech version
incompatibility.
The A3409 counter measures the number of handover commands during
internal intra- and inter-cell handovers due to TFO speech version
incompatibility.
The A3410 counter measures the number of failed internal intra- and
inter-cell handovers due to TFO speech version incompatibility.
Issue 01 (2012-04-26)
56
The RA3408 counter measures the success rate of internal intra- and
inter-cell handovers due to TFO speech version incompatibility.
Solution
Impact
After this solution is used, the original eight counters become ineffective.
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC500_514
18. The BSC does not measure discarded CS pagings when paging message packaging is
enabled and the LAPD link is faulty.
Issue 01 (2012-04-26)
57
Severity
Minor
Root Cause
The cell once functioned properly before the upgrade, and therefore the
BSC obtained information about the cell's paging message packaging
capability from the BTS. However, the cell is faulty before and after the
upgrade, and therefore the BSC fails to obtain such information. As a
result, the BSC measures the A531: CS Pagings Discarded on LAPD
Link counter, which is the way the BSC processes this counter when the
paging message packaging function is disabled for the cell. Actually, the
BSC does not measure this counter when the paging message packaging
function is enabled.
Solution
When the LAPD link is faulty, the BSC now measures the A531: CS
Pagings Discarded on LAPD Link counter regardless of whether the
paging message packaging function is enabled.
Solution
Impact
After this solution is used, the values of the following counters change:
The following table lists the specific changes of the preceding counters.
Issue 01 (2012-04-26)
Whether
the
Paging
Message
Packagin
g
Function
Is
Enabled
Before
the
Upgrade
Whether
the
Paging
Message
Packagin
g
Function
Is
Enabled
After the
Upgrade
A531: CS
Pagings
Discarded
on LAPD
Link
A532: PS
Pagings
Discarded
on LAPD
Link
A530: SM
Pagings
Discarded
on LAPD
Link
Enable
Enable
Increase
Increase
Remain
unchanged
Enable
Disable
Increase
Increase
Increase
Disable
Enable
Increase
Increase
Decrease
58
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC500_516
19. The BSC does not provide counters to record information about paging messages
discarded over the A interface due to flow control.
Trouble
Ticket
Number
DTS2011062402553
Description
The BSC does not provide counters to record information about paging
messages discarded over the A interface due to flow control. This causes
difficulties in analyzing flow control.
Severity
Major
Root Cause
The paging messages discarded over the A interface due to flow control
can only be queried by using the DSP PAGINGNUM command.
However, the BSC does not provide any counters to record information
about such paging messages.
Solution
Solution
Impact
None
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC500_517
20. The BSC incorrectly measures the counters under the MR.Iterf.TRX_LOCGRP
measurement unit.
Issue 01 (2012-04-26)
59
Trouble
Ticket
Number
DTS2012022401937
Description
Severity
Major
Root Cause
The BSC does not initialize the message buffer upon receiving the RF
RESOURCE IND message from the BTS and does not determine
whether message reading is complete based on the message length when
parsing the message. As a result, invalid bytes of the previous message in
the message buffer are parsed as subsite information.
Solution
The BSC now initializes the message buffer upon receiving the RF
RESOURCE IND message from the BTS and determines whether
message reading is complete based on the message length when parsing
the message.
Solution
Impact
If the BTS is not configured with subsites, the BSC does not measure the
counters under the MR.Iterf.TRX_LOCGRP measurement unit. And the
measured value of the MR.Iterf.TRX_LOCGRP will be 0.
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC500_518
21. The interference level and quality calculated by the BSC are incorrect.
Issue 01 (2012-04-26)
60
Trouble Ticket
Number
DTS2011112406503
Description
The interference level and quality calculated by the BSC are incorrect.
Severity
Minor
Root Cause
Solution
The BSC now uses a correct value to calculate the interference level and
quality.
Solution Impact
DTS2012013104326
CASE_Commercial_PR_Regression_V9R14C00SPC500_519
22. The fast cell reselection between GSM and LTE networks becomes ineffective.
Issue 01 (2012-04-26)
61
Trouble Ticket
Number
DTS2012041202430
Description
Severity
Major
Root Cause
Solution
Solution Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC500_520
23. The uplink packet immediate assignment success rate is low when BCCH+CBCH is
configured on the BCCH TRX.
Issue 01 (2012-04-26)
62
Trouble Ticket
Number
DTS2012041906581
Description
Severity
Minor
Root Cause
Solution
Solution Impact
Test Case ID
When the traffic on the BCCH TRX is heavy, the value for the
counter Number of Successful Uplink PS Immediate Assignments
increases.
CASE_Commercial_PR_Regression_V9R14C00SPC500_521
24. The values of counters related to the number of abnormal TBF releases due to N3103
overflow increase if Not Send Dummy Message with Extended Uplink TBF is set to
NOTSEND(NOTSEND).
Issue 01 (2012-04-26)
63
Trouble Ticket
Number
DTS2012042408277
Description
Severity
Minor
Root Cause
Solution
The BSC does not measure the counters related to the number of
abnormal TBF releases due to N3103 overflow when the following
conditions are met:
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC500_522
25. The values for the counters of Receive Quality Measurement per TRX Location
Group are smaller than the actual values
Issue 01 (2012-04-26)
64
Trouble Ticket
Number
DTS2012033100252
Description
The values for the counters of Receive Quality Measurement per TRX
Location Group measurement is lower than the actual values
Severity
Minor
Root Cause
Solution
Solution Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC500_523
26. The BSC does not send an assignment failure message to the MSC
Trouble Ticket
Number
DTS2012020304776
Description
After the BSC initiates a directed retry, it starts the dual transfer mode
(DTM) assignment procedure. If the directed retry fails, the BSC does
not send an assignment failure message to the MSC. The call release is
delayed
Severity
Major
Root Cause
Solution
The BSC now does not perform the DTM assignment procedure after
initiating a directed retry.
Solution Impact
Test Case ID
Issue 01 (2012-04-26)
CASE_Commercial_PR_Regression_V9R13C00SPH556_102
65
27. The value for the counter Number of VAMOS Call Handover Attempts (Demultiplexing)
is greater than the actual value
Trouble Ticket
Number
DTS2012010505169
Description
After the Voice services over Adaptive Multi-user channels on One Slot
(VAMOS) function is enabled, The value for the counter Number of
VAMOS Call Handover Attempts (Demultiplexing) is greater than the
actual value.
Severity
Minor
Root Cause
Solution
The BSC now uses a correct formula to calculate the number of channel
pairs to be demultiplexed.
Solution Impact
The value for the counter Number of VAMOS Call Handover Attempts
(Demultiplexing) will decrease.
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPH552_102
28. The value for the counter Number of Successful VAMOS Candidate Call Decisions
(Intra-Cell Handover) is greater than the actual value
Trouble
Ticket
Number
DTS2011120602349/DTS2011120603070
Description
After the VAMOS function is enabled, The value for the counter
Number of Successful VAMOS Candidate Call Decisions (Intra-Cell
Handover) is greater than the actual value.
Severity
Minor
Root Cause
When the BSC makes VAMOS candidate call decisions, it does not
filter out the calls initiated by MSs that support Single Antenna
Interference Cancellation (SAIC) but not VAMOS multiplexing and the
calls initiated by MSs that do not meet the P/N criterion.
Solution
When the BSC makes VAMOS candidate call decisions, it now filters
out the calls initiated by MSs that support SAIC but not VAMOS
multiplexing and the calls initiated by MSs that do not meet the P/N
criterion.
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPH552_103
CASE_Commercial_PR_Regression_V9R13C00SPH552_104
Issue 01 (2012-04-26)
66
DTS2011122206290
Description
Severity
Minor
Root Cause
Solution
After the directed retry by a low-priority MS times out, the BSC now
correctly sets the MS priority when reallocating TCHs to the MS.
Solution Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPH552_106
30. The value for the counter Failed Assignments (A Interface Failure) increases
Trouble Ticket
Number
DTS2011122802896
Description
The call fails to access the target cell and returns to the original cell
for TCH reassignment when the BSC preferentially selects a better
cell for the call.
The call fails because the BSC fails in TCH assignment, and The value
for the counter Failed Assignments (A Interface Failure) increases.
Severity
Minor
Root Cause
Solution
The BSC now does not repeatedly request CICs over the A interface for
the call during TCH reassignment.
Solution Impact
The value for the counter Failed Assignments (A Interface Failure) may
decrease.
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPH552_107
31. The measured numbers of available PDCHs of certain types are inaccurate
Issue 01 (2012-04-26)
67
Trouble Ticket
Number
DTS2011122803411
Description
Severity
Minor
Root Cause
Solution
The BSC now measures the number of available PDCHs only when all
measurement conditions are met.
Solution Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPH552_108
32. The value for the counter Number of Unsuccessful Application Attempts of Abis
Timeslot Because of no Idle Timeslot is incorrect
Trouble Ticket
Number
DTS2011122601217
Description
Severity
Warning
Root Cause
If the BTS works on the reverse ring in Abis over TDM mode and idle
Abis timeslots are insufficient, the BSC measures the counter Number
of Application Attempts of Abis Timeslot but not the number of failed
applications for Abis timeslots due to a BSC internal software defect.
Solution
The BSC software defect has been rectified. If there is no idle Abis
timeslot, the BSC now measures the counter Number of Unsuccessful
Application Attempts of Abis Timeslot Because of no Idle Timeslot
once.
Solution Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPH552_118
Issue 01 (2012-04-26)
68
33. The signaling BVC remains faulty for an extended duration after active/standby SGSN
boards are switched over
Trouble Ticket
Number
DTS2012011005975
Description
Severity
Major
Root Cause
After SGSN boards are switched over, the network service virtual links
(NSVLs) over the Gb interface become temporarily faulty. If the
downlink NSVLs (detected by the SGSN) recover prior to the uplink
NSVLs (detected by the BSC), the SGSN initiates a Signaling BVCRESET procedure. Upon receiving the Signaling BVC-RESET
message from the SGSN, the BSC responds with a Signaling BVCRESET-ACK. Because the uplink NSVLs are still faulty, the network
service (NS) module discards the Signaling BVC-RESET-ACK
message. However, the network management (NM) module assumes
that the Signaling BVC-RESET-ACK has been successfully sent to the
SGSN and updates the Signaling BVC status to normal. As a result, the
Signaling BVC status is inconsistent on the BSC and SGSN sides.
Solution
After the BSC receives a Signaling BVC-RESET from the SGSN, the
BSC now does not forward the Signaling BVC-RESET message to the
NM module if the NS module does not finish rectifying the NSVL
fault.
Solution Impact
None.
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPH552_119
34. The value for the counter Number of Failed VAMOS Channel Multiplexing Attempts
(Assignment) is incorrect
Issue 01 (2012-04-26)
69
Trouble Ticket
Number
DTS2011101302252
Description
Severity
Minor
Root Cause
Solution
Solution Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC550_108
35. Configuring 32 neighboring GSM cells with 32 frequencies is not allowed in an MOCN
shared cell on a single telecom operator's network
Issue 01 (2012-04-26)
70
Trouble Ticket
Number
DTS2011090505160
Description
Severity
Minor
Root Cause
Solution
Solution Impact
None.
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC550_110
Issue 01 (2012-04-26)
71
Trouble Ticket
Number
DTS2011091402431
Description
Severity
Minor
Root Cause
Solution
Solution Impact
None.
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC550_111
37. The multiplexing rate is low during peak hours after the VAMOS feature is enabled
Trouble Ticket
Number
DTS2011112101189
Description
The multiplexing rate is low during peak hours after the Voice services
over Adaptive Multi-user channels on One Slot (VAMOS) feature is
enabled. Ongoing services are not affected, but channel usage decreases.
Severity
Minor
Root Cause
Solution
The capabilities of MSs that support the VAMOS feature are now
updated correctly.
Solution Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC550_116
Issue 01 (2012-04-26)
72
38. The values of Downlink Interference Indication Messages (TCH) and Downlink
Interference Indication Messages (SDCCH) increase greatly after a BSC is upgraded to
BSC6900 V900R014C00SPC500
Trouble
Ticket
Number
DTS2011102005359
Description
Severity
Minor
Root Cause
Solution
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC550_120
39. BSC incorrectly determines the value of CCCH Load Indication Period
Issue 01 (2012-04-26)
73
Trouble Ticket
Number
DTS2011071901469
Description
Severity
Minor
Root Cause
Solution
The BSC software errors are corrected so that the BSC determines that
CCCH Load Indication Period is valid when CCCH Load
Indication Period ranges from 0 to 255.
Solution Impact
Test Case ID
Counter
Impact
Decrease
Decrease
CASE_Commercial_PR_Regression_V9R13C00SPC550_133
40. The incoming BSC signaling channel handovers fail in certain scenarios
Issue 01 (2012-04-26)
74
Trouble Ticket
Number
DTS2011101806330
Description
Severity
Minor
Root Cause
Solution
Solution Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPH532_103
An MS that has not been defined in the 3G network encounters 2G/3G ping-pong cell
reselections in NC2 mode.
In NC2 mode, after the BSC instructs an MS that has not defined in the
3G network to reselect a 3G cell, the MS cannot process PS services in
the 3G cell and encounters ping-pong cell reselections.
Severity
Suggestion
Workaround
None
Progress
The cause of this issue has been found and the issue will be resolved in
a later version.
Issue 01 (2012-04-26)
75
Issue 01 (2012-04-26)
76
Changes from
V900R014C00SPC200 to
V900R014C00SPC300
5.1 What's New
5.1.1 Feature Updates
New Features
1.
Issue 01 (2012-04-26)
77
Description
Benefit
NodeB OM packets
802.1ag packets
Implementati This function differentiates packets according to their protocol types and
captures the packets in compliance with a certain protocol.
on
Related
Operations
Trouble
Ticket
Number
CR GU00583
Feature ID
MRFD-210801
2.
Issue 01 (2012-04-26)
78
Description
Benefit
Implementati For a traffic-carrying link, the BTS checks the link status using the
on
LAPD link status check function.
For a non-traffic-carrying link, the BTS checks the link status using a
loopback mechanism. The BTS sends UDP ping packets to the BSC
through the link. Upon detecting the UDP ping packets, the BSC loops
back the packets to the BTS. If the BTS receives the UDP ping packets,
the link is normal. Otherwise, the link is faulty.
If the BTS finds that the primary link is faulty, the BTS automatically
switches ongoing services over to the backup link. When the primary
link is recovered, the BTS automatically switches the services back to
the primary link.
Related
Operations
During the switchover, ongoing services are interrupted for less than one
minute.
Changing the value of the Wait Time Before Link Switchover parameter
affects the service interruption duration.
Both the primary and backup links are configured with an IP path. Services
can only be assigned to the IP path that corresponds to the traffic-carrying link.
Issue 01 (2012-04-26)
79
None
Feature ID
GBFD-117803
3.
Issue 01 (2012-04-26)
80
Description
Benefit
Implementati
on
Issue 01 (2012-04-26)
The ratio of request failures to total requests is zero, and the total
number of requests is greater than or equal to 10.
81
Related
Operations
Trouble
Ticket
Number
CR GU00821
Feature ID
None
4.
Issue 01 (2012-04-26)
82
Description
With the WLAN Hot Spot Notification feature, the BSC sends WLAN
access information configured by operators to the MSs supporting
WLAN Hot Spot Notification through the GSM network.
Benefit
Implementati After MSs supporting the WLAN Hot Spot Notification feature send
WLAN registration requests to the BSC, the BSC will send WLAN
on
access information configured by operators to MSs through the GSM
network if the following conditions are met:
The BSC has been configured with the service set identifier
(SSID).
The BSC will measure counters related to the success rate and failure
causes for WLAN load distribution.
Related
Operations
Trouble
Ticket
Number
OR201109095277
Feature ID
GBFD-511608
5.
Issue 01 (2012-04-26)
83
Description
The GPRS Packet Fast Transmission feature extends the size of the
downlink GPRS sending window to a value greater than 64 and
reduces the probability of downlink window stop-and-wait.
Benefit
This feature increases the rate for sending downlink GPRS data.
Trouble
Ticket
Number
None
Feature ID
GBFD-119509
6.
LLC Acceleration
Description
With the LLC Acceleration feature, the BSC reorders LLC PDUs
whose N-PDU numbers are in random order before sending them to
MSs. The random is generally caused by transmission faults or faults in
the CN.
Benefit
The BSC sends LLC PDUs in a correct order to MSs, avoiding data
packet retransmission by the CN.
Implementati The BSC checks N-PDU numbers for downlink LLC PDUs. If the NPDU numbers are in random order, the BSC buffers and reorders the
on
downlink LLC PDUs. The BSC then sends downlink LLC PDUs in a
correct order to MSs within a specified time.
Related
Operations
Trouble
Ticket
Number
None
Feature ID
GBFD-117706
Modified Features
1.
Issue 01 (2012-04-26)
84
Description
Benefit
Port 443 must be open on all the network elements (NEs) managed by the LMT
before the HTTPS protocol is enabled.
Opening the LMT login window using HTTPS is slightly slower than using HTTP.
When a user logs in to the LMT using HTTPS, the web browser displays a security
warning, which does not affect operation of the LMT and can be ignored.
Enhances security for data transmission between the LMT and NEs
Minimizes malicious attacks on the NEs
Implementa Users can run the SET WEBLOGINPOLICY command to change the
value for POLICY.
tion
Note: An upgrade to RAN14.0 does not change the value for POLICY.
Related
Operations
1.Run the following command to set POLICY to the new default value:
SET WEBLOGINPOLICY: POLICY=LOGIN_HTTPS_ONLY;
Run the following command to reset the LMT:
RST OMUMODULE:TG=ACTIVE, MNAME=weblmt;
2.Run the LST WEBLOGINPOLICY command to check whether the
new default value is used.
The preceding steps are not required for new sites because the new default value is
used by default.
Trouble
Ticket
Number
None
Feature ID
None
2.
Issue 01 (2012-04-26)
85
Description This feature incorporates the method for calculating cell load based on the
proportion of idle timeslots.
Benefit
This feature helps reduce cell load because the optimization increases the
probability for the BSC to trigger load-based handovers and TCHH
allocations when optimizing intra-cell handovers is enabled. For the
standard traffic model, enabling this feature increases the CPU usage of the
XPU board by 2% to 3%.
NOTE
Optimizing intra-cell handovers includes optimizing intra-cell TCHFTCHH handovers, intra-concentric cell handovers, and intra-cell TCHH
integration.
HALFRATEREPACKING(TCHH Integration)
HALFRATEASSIGNMENT(TCHH Assignment)
Setting Load Calculation Optimization to ON(On) takes effect only for Huawei
handover algorithm II if Load Type is set to any of the preceding values except
HALFRATEASSIGNMENT(TCHH Assignment).
Related
Operations
Trouble
Ticket
Number
CR GU01417
Feature ID
GBFD-111004
3.
Issue 01 (2012-04-26)
86
Description
Benefit
This feature increases the high quality indicator (HQI) and reduces
interference, increasing the success rate of quality-based handovers and
decreasing the number of quality-based handovers.
Implementati
on
Issue 01 (2012-04-26)
87
Related
Operations
When both target channels have the same frequency set as that used by
the source channel or channels that do not participate in FH share the
same frequency set with the source channel:
When two target channels have a frequency set which is different from
that of the source channel:
Trouble
Ticket
Number
CR GU01398
Feature ID
GBFD-113201
GBFD-510501
GBFD-111004
4.
Issue 01 (2012-04-26)
HUAWEI I Handover
88
Description
Benefit
Implementati
on
Issue 01 (2012-04-26)
89
Related
Operations
CR GU01396
Feature ID
GBFD-113201
CR GU01398
GBFD-110601
5.
Issue 01 (2012-04-26)
HUAWEI II Handover
90
Description
Benefit
Implementati
on
Issue 01 (2012-04-26)
The value of the Call Drop Rate on TCH per BSC counter
remains unchanged or decreases slightly.
For the standard traffic model, enabling this feature increases the
CPU usage of the XPU board by 0.5% to 1%.
91
Issue 01 (2012-04-26)
92
Related
Operations
Trouble
Ticket
Number
CR GU01396
CR GU01421
CR GU01422
CR GU01425
Feature ID
6.
Issue 01 (2012-04-26)
GBFD-510501
93
Description
This feature enables the BSC to consider PDCH allocation continuity and
inherits the existing interference band information during channel
conversion. This ensures that the interference preference accurately
indicates the interference on channels.
Benefit
Issue 01 (2012-04-26)
GBFD-111004
94
7.
Description
Benefit
When the CPU usage for all XPU subsystems in the BSC exceeds
75% (the default value of the Share in CPU Rate parameter), calls
are not forwarded, and therefore the CPU usage does not increase.
Implementatio
n
Related
Operations
None
8.
Issue 01 (2012-04-26)
None
95
Description
Benefit
Improves the efficiency for planning the PDCH channel priority type on
the live network.
Implementatio
n
96
9.
Issue 01 (2012-04-26)
GBFD-113101
97
Description
Benefit
NOTE
With this optimization, most PDCHs are distributed on certain TRXs
after PDCH conversion. For example, if a maximum of nine TCHs can
be converted to PDCHs in a cell, PDCHs may be distributed as follows
after PDCH conversion:
Eight PDCHs are distributed on a TRX, and the remaining one is
distributed on another TRX.
Such a distribution decreases the multislot satisfaction rate and singleuser throughput.
Implementatio The PDCH Management Optimization parameter is added to the SET
GCELLPSCHM command.
n
During PDCH allocation, if this parameter is set to ON(On), the
weight for the total number of continuous PDCHs on a TRX is added
to the channel allocation weight table. This ensures the PDCH
continuity.
98
Operations
GBFD-113101
10. Optimization of License Usage Measurement for Certain License Control Items
Issue 01 (2012-04-26)
99
Description
The names of some license control items have been changed. The license
usage measurement for these license control items has been optimized.
In addition, the configuration data for some of these license control items
will be checked during an upgrade.
Benefit
Implementatio
n
LLC Acceleration
For users who have not used the preceding features, the corresponding
license control items are added. For users who have used the preceding
features, the license usage measurement of the corresponding license
control items is based on the number of TRXs on which a specific
feature is enabled (Licenses for the RACH Storm Filtration feature are
calculated based on the number of cells).
The upgrade tool will check the new license capacity when users
who have used the following features implement an upgrade:
Issue 01 (2012-04-26)
LLC Acceleration
100
To query the current usage of each license control item, run the
following command:
DSP LICUSAGE: TYPE=Current;
None
Deleted Features
None.
Modified Hardware
None.
Removed Hardware
None.
Issue 01 (2012-04-26)
101
Trouble
Ticket
Number
DTS2010082401462
Description
Severity
Minor
Root Cause
Solution
The active board sums up the amount of data processed on both the active
and the standby boards and then reports the summed-up values.
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC300_500
2.
Issue 01 (2012-04-26)
The BSC releases calls made by low-priority MSs with the release cause "OM
intervention" if low-priority MSs fail to perform forced handovers.
102
Trouble
Ticket
Number
DTS2012022308171
Description
Severity
Minor
Root Cause
After low-priority MSs fail to perform forced handovers, the BSC releases
calls made by low-priority MSs with an incorrect release cause.
Solution
The BSC now releases calls made by low-priority MSs with the release
cause "preemption" if low-priority MSs fail to perform forced handovers.
Solution
Impact
3.
The unit of FE or GE BER in the output of the DSP BTSIPPM command is inconsistent
with the unit of FE or GE BER reported by BTSs.
Trouble
Ticket
Number
iCare: none
Description
Severity
Minor
Root Cause
Solution
Solution
Impact
None
DTS2012021304359
4.
Issue 01 (2012-04-26)
The measured value for the counter Number of VAMOS Call Handover Attempts
(Demultiplexing) is greater than the actual value
103
Trouble
Ticket
Number
DTS2012022002267
Description
After the Voice services over Adaptive Multi-user channels on One Slot
(VAMOS) function is enabled, the measured value for the counter
Number of VAMOS Call Handover Attempts (Demultiplexing) is
greater than the actual value.
Severity
Minor
Root Cause
Solution
The BSC now uses a correct formula to calculate the number of channel
pairs to be demultiplexed.
Solution
Impact
The measured value for the counter Number of VAMOS Call Handover
Attempts (Demultiplexing) will decrease.
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC300_503
5.
The call drop rate increases during handovers after the DTM function is enabled.
After the Dual Transfer Mode (DTM) function is enabled, the call drop
rate increases during handovers.
Severity
Minor
Root Cause
Solution
Solution
Impact
Test Case ID
Issue 01 (2012-04-26)
CASE_Commercial_PR_Regression_V9R14C00SPC300_504
104
6.
The measured values for TFO-related counters are incorrect after an inter-cell handover
occurs.
Trouble
Ticket
Number
iCare: none
Description
Severity
Minor
Root Cause
Solution
The TFO-related counters have been measured for the cell where an MS
is currently located.
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC300_505
7.
Issue 01 (2012-04-26)
DTS2012010601642
105
Trouble
Ticket
Number
BB4D51791
Description
After sending data blocks whose final block indicators (FBIs) are set to
1, the BSC uses a high-rate coding scheme to send unacknowledged
data blocks. In this scenario, the number of abnormal downlink EGPRS
TBF releases increases.
Severity
Minor
Root Cause
When the signal quality deteriorates, if the BSC uses a high-rate coding
scheme to send unacknowledged data blocks, mobile stations (MSs)
may fail to receive the data blocks.
Additionally, after receiving the EGPRS Packet Downlink Ack/Nack
message that indicates a poor signal quality, the BSC cannot decrease
the coding scheme in a timely manner.
Solution
After sending data blocks whose FBIs are set to 1, the BSC splits and
resends unacknowledged data blocks.
For example, if the BSC uses MCS6 to send an unacknowledged data
block but MSs fail to receive the data block, the BSC splits the data
block and uses MCS3 to resend it.
NOTE
This problem has been resolved in BSC6900 V900R012C00.
Solution
Impact
Test Case ID
8.
Issue 01 (2012-04-26)
Counter
Impact
Increased
Decreased
Decreased
Decreased
Decreased
CASE_Commercial_PR_Regression_V9R14C00SPC300_506
106
Trouble
Ticket
Number
iCare: none
Description
DTS2011112100004
Downlink refers to the direction from the media gateway (MGW) to the BSC.
Severity
Minor
Root Cause
Solution
The BSC fills the MUX field with a correct value in UDP MUX packets
sent to the MGW.
Solution
Impact
None.
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC300_507
9.
Issue 01 (2012-04-26)
The counters related to abnormal TBF releases due to CS handovers are incorrectly
measured in DTM mode.
107
Trouble
Ticket
Number
DTS2012031405972
Description
Severity
Suggestion
Root Cause
Solution
Solution
Impact
CASE_Commercial_PR_Regression_V9R14C00SPC300_508
Issue 01 (2012-04-26)
108
Trouble
Ticket
Number
DTS2011110400936
Description
Severity
Minor
Root Cause
Delay Jitter at Local End of IP Path: The measurement unit for this
counter is millisecond (ms) but its calculation precision is 20 ms.
RTT at Local End of IP Path: Only certain sampled values are
measured.
Solution
Solution
Impact
None.
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC300_509
The communication between the OMU and host boards is interrupted when a nonphysical-layer fault occurs on the links between the OMU and the SCU boards
Description
Trigger
Condition
Impact
Severity
Minor
Workaround
None
Issue 01 (2012-04-26)
109
Issue 01 (2012-04-26)
110
Changes from
V900R013C00SPC500 to
V900R014C00SPC200
6.1 What's New
6.1.1 Feature Updates
New Features
1.
Support for Informing Users that a Configuration Command Does not Take Effect in
Subracks in Non-effective Mode
Description
Benefit
Implementati
on
Related
Operations
N/A
Trouble
Ticket
Number
CR-GU01048
Feature ID
MRFD-210301
2.
Issue 01 (2012-04-26)
Permanent&Temporary License
111
Description
Benefit
Implementati
on
Issue 01 (2012-04-26)
ACT BTS
ACT GCELL
ACT GTRX
ADD GCELLFREQ
MOD GCELL
RMV GCELLFREQ
112
Related
Operations
1.
2.
3.
Trouble
Ticket
Number
GBSC-OR-010
Feature ID
MRFD-210403
3.
Description
Benefit
If the POUc board fails to extract clock signals from the SGSN, PS
services carried by that board will be affected. The reporting of the
alarm helps operators to handle the problem in time.
Implementati
on
Related
Operations
None.
Trouble
Ticket
Number
MBSCV9R14C00-CR-GU00696
Feature ID
MRFD-210304
4.
Issue 01 (2012-04-26)
Support for Hot Patch Status Consistency Check Between the OMU and Host Boards
113
Description
Benefit
Implementati
on
Related
Operations
To check the hot patch status consistency, run the CMP BRDVER
command. The following is an example:
CMP BRDVER: SRN=0;
Trouble
Ticket
Number
MBSCV9R14C00-CR-GU00711
Feature ID
MRFD-210401
5.
Description
Benefit
Implementati
on
The DPU core detects heartbeat packets between the DPU core and
each DSP. If an error heartbeat packet is detected, the DPU core
sends the heartbeat packet again.
Related
Operations
None
Trouble
Ticket
Number
None
Feature ID
None
6.
Issue 01 (2012-04-26)
Support for Checking the Physical Memory and Logical CPU of the OMU Board
114
Description
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
CR GU00759
Feature ID
None
7.
Description
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
None
Feature ID
None
Issue 01 (2012-04-26)
115
8.
Description
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
CR GU00153
Feature ID
MRFD-210305
9.
Issue 01 (2012-04-26)
Specifying a Data Port Range for the FTP Server (for M2000)
116
Description
Benefit
Implementati
on
After users run the LST FTPSSRV command, the lower and upper
limits of the data port range for the FTP server in passive mode are
displayed.
3. If users specify a port for the FTP server to listen to before the
mechanism is changed, the external and internal networks listen to
both the default port (port 21) and the user-defined port. If users
specify a port for the FTP server to listen to after the mechanism is
changed, the external network listens only to the user-defined port
and the internal network listens only to the default port (port 21). In
addition, after users change the listening port, the change takes effect
immediately. Users no longer need to restart the FTP server for the
change to take effect.
Related
Operations
1. Run the following command to add the information about the FTP
server. In this example, set ServerIP to 0.0.0.0 and Port to 8021.
ADD FTPSCLTDPORT: ServerIP="0.0.0.0", Port= 8021;
2. Run the following command to specify the data port range for the
FTP server in passive mode:
SET FTPSSRV:
DFTPORTSWT=DEFAULTPORT,ACDPORTLWLT=25001,
ACDPORTUPLT=30000;
Issue 01 (2012-04-26)
117
OR-353
Feature ID
MRFD-210305
10. Support for Filtering Events with Special Alarm Flag on the M2000
Description
Benefit
Implementati
on
Related
Operations
To query all the events from NEs working in maintenance mode, run
the following command:
LST ALMLOG: ALMTP=evt, SPCALMFLG=ALL_SPECIAL;
Trouble
Ticket
Number
N/A
Feature ID
MRFD-210304
Issue 01 (2012-04-26)
118
Description
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
CR GU01005
Feature ID
None
Issue 01 (2012-04-26)
119
Description
Benefit
Implementati
on
Related
Operations
KPIs
Fault causes
Operation logs
Trouble
Ticket
Number
None
Feature ID
MRFD-210304
Issue 01 (2012-04-26)
120
Description
The RNC now checks the OMU software integrity periodically and
reports an alarm if any OMU software file is lost or damaged.
Benefit
Implementa
tion
The OMU software integrity is checked once every 12 hours, and the
ALM-20723 File Loss or Damage is reported if any file is lost or
damaged.
Related
Operations
Trouble
Ticket
Number
MBSC-OR-122
Feature ID
MRFD-210305
14. Support for the FTP Client Authenticating the FTP Server
Description
The FTP client now can authenticate the FTP server when they both
are using the SSL encryption mode for transmission.
Benefit
Implementati
on
The FTP client authenticates the FTP server by using the root
certificate issued by the M2000.
Related
Operations
Trouble
Ticket
Number
DTS2011081704367
Feature ID
MRFD-210305
15. SSL Encryption Function Supported by the Tool for Preparing Data on the USB Storage
Device and Upgrade Tool
Issue 01 (2012-04-26)
121
Description
The tool for preparing data on the USB storage device can now be
connected to the BSC in SSL-encrypted mode and the upgrade tool
can now upgrade the BSC in SSL-encrypted mode.
Benefit
The compatibility and security of the tool for preparing data on the
USB storage device and the upgrade tool are improved.
Implementati
on
Related
Operations
1. Before using the tool for preparing data on the USB storage device
or the upgrade tool, log in to the LMT and run the LST SSLCONF
command to obtain the secure transmission information of the BSC
to be upgraded.
2. Select the required secure transmission type on the Add NE Dialog
Box of the tool for preparing data on the USB storage device or on
the Input Step 1 window of the upgrade tool client.
Trouble
Ticket
Number
CR GU00967
Feature ID
MRFD-210305
16. Support for Setting the IEEE 802.1ag Standard Version Used by the Ethernet Ports on
the BSC6900
Issue 01 (2012-04-26)
122
Description
Benefit
Implementati
on
Related
Operations
DTS2011041801702
Feature ID
GBFD-118630
Issue 01 (2012-04-26)
123
Description
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
None
Feature ID
GBFD-118601/GBFD-118602/GBFD-118603
Issue 01 (2012-04-26)
124
Description
Benefit
Implementati
on
The flow control on the packets transmitted over the FG2c, FG2d,
GOUc and GOUd boards is improved to prevent conflicts between
different ports or between different types of packets in the same
priority queue.
Users can query statistics about the packets transmitted over a port
on an FG2c, FG2d, GOUc or GOUd board or over the entire
board.
125
Operations
Trouble
Ticket
Number
OR-224
Feature ID
MRFD-210305
19. Support for Querying the Route based on the Source IP Address
Issue 01 (2012-04-26)
126
Description
The source route function has been added to the FG2c, GOUc, FG2d
and GOUd boards, enabling these two boards to query the route used
for transmission based on the source IP address of a data packet.
The source IP address can be an ETHIP, ETHTRKIP, or DEVIP.
When the source IP address is an ETHIP or ETHTRKIP, only one
port on the FG2c, GOUc, FG2d or GOUd board can be configured as
the outgoing port. When the source IP address is a DEVIP, two ports,
one active and the other standby, can be configured as the outgoing
ports.
Benefit
Implementati
on
Related
Operations
Issue 01 (2012-04-26)
127
N/A
Feature ID
GBFD-118631
Issue 01 (2012-04-26)
128
Description
With this function, users can clear incorrect dynamic ARP entries on
the BSC6900 when there is an exception on a BSC6900 interface
board or the interconnected transmission equipment of the board.
Then, the BSC6900 can learn the ARP entries again without waiting
for 20 minutes (ARP table aging time).
Benefit
Implementati
on
Related
Operations
1.To clear ARP entries by port, run the CLR ARP command. The
following is an example:
CLR ARP: SRN=0, SN=14, CLRTYPE=CLRPORT,
PORTTYPE=ETHER, PN=2;
2.To clear ARP entries by IP address, run the CLR ARP command.
The following is an example:
CLR ARP: SRN=0, SN=14, CLRTYPE=CLRIP,
IPADDR="11.11.11.2";
Trouble
Ticket
Number
DTS2011041801609
Feature ID
GBFD-118601/GBFD-118602/GBFD-118603
This feature enables users to view the bit error rate (BER) on an
E1/T1 port in real time. This helps to quickly locate transmission
problems on the E1/T1 link.
Benefit
Without this feature, users can only view bit error seconds on the
LMT in real time and perform BER monitoring in E1/T1 loopback
scenarios. With this feature, users can view the BER of E1/T1 links
in real time.
Implementati
on
Related
Operations
None
Trouble
Ticket
Number
CR GU00703
Feature ID
MRFD-210801
Issue 01 (2012-04-26)
129
22. Support for Cross Connection Detection Between a BSC and a Transmission Device
When They Work in MSP Mode
Issue 01 (2012-04-26)
130
Description
This feature enables the BSC to detect optical fiber cross connections
of the protection channels and working channels between the BSC
and a transmission device (for example, OSN), which work in
Multiplex Section Protection (MSP) mode. The following figure
shows the correct connection:
Issue 01 (2012-04-26)
131
Benefit
Implementati
on
After this feature is enabled, the BSC sends SDH frames with the
MS-AIS field over the standby optical port and determines whether
the connections are correct based on received frames.
Related
Operations
Trouble
Ticket
Number
CR GU00792
Feature ID
MRFD-210304
Issue 01 (2012-04-26)
132
Description
Benefit
Users can customize the VLAN priority and DSCP value of packets.
Implementati
on
Related
Operations
To set the VLAN priority and DSCP value, perform the following
operations on the BSC6900 LMT:
To set the DSCP value of Trace Route packets, run the TRC
IPADDR command with the DSCP parameter set to an
appropriate value. The following is an example:
TRC IPADDR: SRN=2, SN=24, DESTIP="23.23.23.2",
DSCP=30;
To set the DSCP value of BFD packets, run the STR IPCHK
command with the DSCP parameter set to an appropriate value.
The following is an example:
STR IPCHK: SRN=2, SN=24, CHKTYPE=SBFD,
CARRYT=ETHPORT, PN=3,
MODE=CHECK_ON_PRIMARY_PORT,
PEERIP="23.23.23.2", WHETHERAFFECTSWAP=NO,
DSCP=50;
Issue 01 (2012-04-26)
To set the DSCP value of DHCP packets and the VLAN priority of
133
DTS2011042802673
Feature ID
None
24. 5-Minute Measurement of the Highest Transmit and Receive Rates in the Transport
Network
Issue 01 (2012-04-26)
134
Description
Benefit
Users can query the highest transmit and receive rates sampled every
5 minutes within a specified measurement period.
Implementati
on
Related
Operations
None
Trouble
Ticket
Number
CR-2198
Feature ID
MRFD-210302
25. Support for the ALM-21522 Low SCCP Connection Setup Success Rate
Issue 01 (2012-04-26)
135
Description
If the SCCP connection setup success rate is smaller than the value
of Threshold of Low SCCP Setup Success Rate and the number of
Connection Request (CR) messages is larger than the value of
Minimum number of CR, the alarm ALM-21522 Low SCCP
Connection Setup Success Rate is reported.
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
CR GU00367
Feature ID
None
Issue 01 (2012-04-26)
136
Description
Benefit
When the CPU load of all MPU subsystems in the BSC6900 reaches
or exceeds the load balancing threshold, more MPU subsystems can
be added to reduce the CPU load of the existing MPU subsystems.
In versions earlier than BSC6900V900R014, the CPU load of an
MPU subsystem is distributed among the interface boards bound to
the MPU subsystem.
In BSC6900V900R014, the CPU load of an MPU subsystem is
distributed among the CPUS subsystems bound to the MPU
subsystem. In the BSC6900, the number of CPUS subsystems is
always larger than the number of interface boards. Also, the CPUS
subsystems are more evenly bound to MPU subsystems than the
interface boards.
Therefore, after an upgrade to BSC6900V900R014, the CPU load of
MPU subsystems is better balanced in the scenario where traffic load
is evenly distributed among the base stations that are managed by the
MPU subsystems.
After the CPU load balancing among MPU subsystem is enabled, the
CPU load of a multi-core interface board (AOUc, POUc, UOIc,
FG2c, or GOUc) increases by 3%.
If a maximum of 24 MPU subsystems are configured in the
BSC6900V900R014, the CPU load of each MPU subsystem
increases by 2% when there is no traffic compared with the same
configuration in the BSC6900 of an earlier version.
However, in BSC6900V900R014, the CPU load caused by a single
user is less than that in an earlier version. Therefore,
BSC6900V900R014 outperforms its earlier versions when the
average CPU load of the MPU subsystems is equal to or higher than
40%.
If only one SPU board is configured with an MPU subsystem, the
CPU usage of the MPU subsystem increases by about 3% after the
BSC6900 is upgraded to BSC6900V900R014. However, this
increase does not have any significant impact on the BSC6900
capacity, MPU performance is not a system bottleneck.
Implementati
on
Issue 01 (2012-04-26)
137
Trouble
Ticket
Number
IR-RAN14.0-019-SR-01-AR-01
Feature ID
GBFD-110003
Issue 01 (2012-04-26)
138
Feature
Descriptio
n
Improveme
nt
This function helps the BSC make efficient use of radio resources
by dynamically adjusting radio resources based on service types that
are identified by the CN.
Implement
ation
After identifying a service type, the GGSN adds the service type to
the extension field of a GTP-U packet header. Then, the GGSN
sends this GTP-U packet to the SGSN.
The SGSN adds this service type to the extension field of a BSSGP
packet header after successfully interpreting the service type. Then,
the SGSN sends this BSSGP packet to the BSC.
After receiving the BSSGP packet, the BSC interprets the service
type contained in the extension field of the BSSGP packet header.
Then, the BSC dynamically allocates radio resources based on the
interpreted service type.
Currently, only QQ services are supported.
Related
Operations
PR Number
FF-034
Feature ID
N/A
28. Support for synchronization and Co-BCCH between BTS3900 and BTS3012
Issue 01 (2012-04-26)
139
Feature
Description
BTS3012 + BTS3900L
BTS3012II + BTS3900L
Improvement
Implementati
on
Related
Operations
Issue 01 (2012-04-26)
140
FF-001
Feature ID
N/A
29. Support for the U-TDOA positioning method over the Lb interface
Issue 01 (2012-04-26)
141
Description
Improvement U-TDOA is more precise than CELL ID+TA and supports more
subscribers than A-GPS.
Without introduction of this feature, Huawei BSS supports CELL
ID+TA and A-GPS. However, CELL ID+TA cannot meet operators'
requirements for precise positioning. A-GPS is the most precise, but is
available only to GPS-capable MSs.
With this feature, U-TDOA meets operators' requirements for precise
positioning and has no special requirement for MS capability. This helps
operators support more subscribers.
Implementati U-TDOA requires the cooperation between the Location Measurement
Unit (LMU) and the Serving Mobile Location Center (SMLC). The
on
LMU is provided by a third-party vendor. The BSC does not manage the
LMU or process messages between the LMU and the SMLC. It only
provides transparent channels between the LMU and SMLC. Physically,
the LMU sets up a transparent channel using transmission resources over
the Abis interface, and the SMLC sets up a transparent channel using
transmission resources over the Lb interface. Then, the BSC
interconnects the two transparent channels. The Abis and Lb interfaces
must use the same transmission mode. Currently, only the
AbisTDM+LbTDM and AbisIP+LbIP transmission modes are
supported.
In AbisTDM+LbTDM mode, the BSC is configured with a semipermanent link between the LMU and the SMLC. This semi-permanent
link transparently transmits messages between the LMU and the SMLC.
In AbisIP+LbIP mode, the LMU and the SMLC exchange messages with
each other directly through a router, not through the BSC.
The signaling process for U-TDOA over the Lb interface is as follows:
BSC
MSC
SMLC
U-TDOA Request
U-TDOA Reponse
Issue 01 (2012-04-26)
142
FF-011
Feature ID
GBFD-115404
Issue 01 (2012-04-26)
143
Feature
Description
Improvement
Implementati
on
Related
Operations
Run the SET GCELLPSOTHERPARA command with GSMto-TD Cell Reselection Allowed set to FORCENC2(Force NC2
Mode).
Run the SET GCELLRESELECTUTRANTDD command with
TDD_MULTIRAT_REPORTING set to a value other than 0.
Run the ADD IMEIGRP command with IMEI Group Index,
Start IMEI, and End IMEI set to appropriate values.
PR Number
FF-035
Feature ID
GBFD-511405
31. Support for geographic display of hot spots and terminals for GSM PS services
Issue 01 (2012-04-26)
144
Description
Improvemen
t
Implementat
ion
Exception information, including uplink and downlink LLClayer transmission interruptions, uplink and downlink TBF
establishment failures, and uplink and downlink abnormal TBF
releases
Service types information, including uplink and downlink LLClayer traffic, uplink and downlink RLC-layer traffic, uplink and
downlink PS service channel usage, uplink and downlink TBF
duration, and uplink and downlink TBF establishment intervals
Issue 01 (2012-04-26)
145
Related
Operation
PS CHR Switch
Event Information
Exception Information
IMEI Information
Feature ID
GBFD-118614
Issue 01 (2012-04-26)
146
Feature
Description
Improvement
Implementati
on
1. HSCSD services are classified into transparent and nontransparent services. The GBSS allocates TCHs to an HSCSD
service according to the required number of TCHs.
2. A transparent HSCSD service can be set up only at a specified
rate. In a congested cell, a transparent HSCSD service cannot be
set up because the service cannot be allocated sufficient
continuous idle TCHs.
3. A non-transparent HSCSD service supports a variable rate.
When a cell is congested, the GBSS allocates as many continuous
idle TCHs as possible to a non-transparent HSCSD service (in
this case, the actual transmission rate may be lower than the
requested rate). When the cell has sufficient channel resources,
the GBSS allocates more idle TCHs to the service to meet the call
rate request.
4. Huawei GBSS can handle requests for increasing or decreasing
TCHs from MSs that are performing non-transparent HSCSD
services.
5. In an extended cell, an HSCSD service can be allocated only
one TCH. Therefore, an MS performing a non-transparent
HSCSD service can be handed over to an extended cell; however,
an MS performing a transparent HSCSD service cannot be
handed over to an extended cell.
Related
Operations
PR Number
FF-027
Feature ID
GBFD-119406
Issue 01 (2012-04-26)
147
Description
Improvement
Implementati
on
High jitter in the delay: The jitter in the delay for satellite
transmission increases to 300 ms.
Related
Operations
FULL_RATE_VER1
HALF_RATE_VER3
4_75KBIT/S
148
FF-039
Feature ID
N/A
Issue 01 (2012-04-26)
149
Description
Run the LST MSP command for a specific optical port to check
whether the value of Backup mode is MODE2(1+1 Single End).
If the value is MODE2(1+1 Single End), no further action is
required.
If the value is not MODE2(1+1 Single End), go to the next step.
Run the SET MSP command for the port with Backup mode set
to MODE2(1+1 Single End).
PR Number
DTS2011050300306
Feature ID
N/A
Issue 01 (2012-04-26)
150
Description
1.To add a GBBP board (to slot 1 or slot 2 of a BBU), run the
following command:
ADD BTSBRD: IDTYPE=BYID, CN=0, BTSID=1003, SRN=0,
SN=1, BT=GBBP;
2. To set the GSM baseband work mode of a BTS (Baseband Work
Mode = Baseband Extension Adjusting), run the following
command:
SET BTSBBMODE: IDTYPE=BYID, BTSID=1003,
BBMODE=BBEXTADJ, CN=0, SRN=0, SN=1;
3. Move the CPRI chains from a GTMU to the GBBP.
4. To move all the RXU chains and rings on a GTMU to the same
port of the GBBP, run the following command:
MOV BTSBRDRXUCHAIN: IDTYPE=BYID, BTSID=1003,
CN=0, SRN=0, SN=6, DCN=0, DSRN=0, DSN=1;
5. To set the GSM baseband work mode of a BTS (Baseband Work
Mode = Whole Baseband Extension), run the following
command:
SET BTSBBMODE: IDTYPE=BYID, BTSID=1003,
BBMODE=BBEXT, BBENHRAP=REASSCHK,
TRXDECRAP=REASSCHK, BBAIDPOLICY=AIDIMM,
BBRECPOLICY=RECCHK, BBAVAILTRXTHD=75;
6. To query the information of BTS board baseband, run the
following command:
DSP BTSBRDBBINFO: IDTYPE=BYID, BTSID=1003, CN=0,
Issue 01 (2012-04-26)
151
SRN=0, SN=1;
PR Number
FF-003
Feature ID
GBFD-111202
Issue 01 (2012-04-26)
152
Description
The data on the user plane, control plane, and maintenance plane
of a GBTS is transmitted by different IP addresses of a physical
GBTS port.
Improvement
Issue 01 (2012-04-26)
153
BSCCPIP="10.161.99.1", BTSUPIP="10.10.11.10",
BSCUPIP="10.161.99.2";
3. To query BTS IP addresses, run the following command:
LST BTSDEVIP: IDTYPE=BYID, BTSID=1020;
4. To query the IP addresses used by an IP-based BTS, run the
following command:
LST BTSIP: IDTYPE=BYID, BTSID=1020;
PR Number
FF-030
Feature ID
GBFD-118613
37. Support for Checking the BA2 list of GSM cells When the Neighboring 3G Cell
Measurement Starts
Description
The BA2 list of GSM cells is checked when the neighboring 3G cell
measurement starts.
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
DTS2011080501287
Feature ID
GBFD-510901
Issue 01 (2012-04-26)
154
Description
Benefit
Implementati
on
Related
Operations
To set the logical function type of a DPUe board to GPCU, run the
following command:
ADD BRD: SRN=0, BRDCLASS=DPU, BRDTYPE=DPUe,
LGCAPPTYPE=GPCU, SN=8, MPUSUBRACK=0, MPUSLOT=0;
Trouble
Ticket
Number
MBSCV9R14C00-CR-GU00946
Feature ID
GBFD-110003
39. Installing Any Board Except SCUa/SCUb, GCUa, and GCGa in Slots 4 and 5
Description
The restriction that only TNUa boards can be installed in slots 4 and
5 is now lifted. In all-IP networking mode, no TNUa board is
needed. Therefore, the preceding restriction is changed as follows:
All boards except SCUa/SCUb, GCUa, and GCGa can be installed in
slots 4 and 5.
Benefit
Implementati
on
The restriction that only TNUa boards can be installed in slots 4 and
5 has been removed from the configuration restriction of the ADD
BRD command.
Related
Operations
You can run the ADD BRD command to add any board except
SCUa/SCUb, GCUa, and GCGa in slots 4 and 5. The following is an
example:
ADD BRD: SRN=0, BRDCLASS=DPU, BRDTYPE=DPUb,
LGCAPPTYPE=GTC, SN=4, ISTCBRD=NO, MPUSUBRACK=0,
MPUSLOT=0;
Trouble
Ticket
Number
MBSCV9R14C00-CR-GU01008
Feature ID
GBFD-110003
Issue 01 (2012-04-26)
155
Description
Benefit
Higher maintainability
Related
Operations
1.
2.
3.
Issue 01 (2012-04-26)
156
5.
6.
7.
Trouble
Ticket
Number
IR-RAN14.0-124-SR-01-AR-01
Feature ID
GBFD-118631
41. Support for Separation of the Communication Data Flow Between the BSC and VNP
from that Between the BSC and EMS/LMT
Issue 01 (2012-04-26)
157
Description
With this function, the communication data flow between the BSC
and Vendor Network Probe (VNP) is separated from that between the
BSC and EMS/LMT.
Benefit
Implementati
on
Related
Operations
1.Run the following command to query the BSC local IP address and
VLAN IDs:
LST GVNPLOCALIP:;
2. Use the omutool to query the BSC local IP address and VLAN IDs
for communication with the VNP. For details, see section "Changing
IP Addresses and Subnet Masks of the OMU Ethernet Adapters" in
the BSC6900 GSM OMU Administration Guide.
3. Use the omutool to modify the BSC local IP address and VLAN
IDs for communication with the VNP. For details, see section
"Configuring Radio Measurement Data Interface for Navigation" in
the GBSS Feature Activation Guide.
Trouble
Ticket
Number
DTS2011110205014
Feature ID
GBFD-511701
Issue 01 (2012-04-26)
158
Description
With the BSC supporting Blind Search feature, users only need to
configure 3G frequencies instead of neighboring 3G cells when 2Gto-3G cell reselection is enabled. Based on the configured 3G
frequencies, an MS automatically reselects an appropriate
neighboring 3G cell.
Benefit
Implementati
on
Related
Operations
1.
2.
3.
4.
Trouble
Ticket
Number
G-OR-BLIND-SEARCH
Feature ID
GBFD-511110
Issue 01 (2012-04-26)
159
Description
Benefit
Implementati
on
Related
Operations
2.
3.
4.
In the Start Loop dialog box, set the required parameters and
click OK.
2.
3.
4.
In the Stop Loop dialog box, set the required parameters and
click OK.
Issue 01 (2012-04-26)
160
Trouble
Ticket
Number
None
Feature ID
None
Issue 01 (2012-04-26)
161
Description
Benefit
Implementati
on
Item
Specifications
Number of TRXs
8192
Traffic volume
45,000 (Erlang)
11,000,000
Number of users
2,200,000
61,440
32,768
PS traffic throughput
3072 (Mbit/s)
1536
When TDM is used over the Abis interface, a DPUg board still supports a
maximum of 1024 PDCHs.
Increases the number of MSs per BSC without affecting the voice
quality.
Issue 01 (2012-04-26)
162
Related
Operations
1.
2.
3.
Run the ADD GTRX command to add 8192 TRXs. Then, run
ACT BTS, ACT GCELL, or ACT GTRX to activate these
TRXs.
Purchase the Packet Service Hardware Capacity license to use improved
DPUg specifications. The license specifies the number of additional PDCHs.
Trouble
Ticket
Number
None
Feature ID
GBFD-113706
Issue 01 (2012-04-26)
163
Description
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
G-OR-TBFALLOCATE
Feature ID
GBFD-119407
Issue 01 (2012-04-26)
164
Description
Benefit
Implementati
on
Issue 01 (2012-04-26)
If the current channel is an idle TCH, the BSC converts the TCH
into a CCCH.
When the TCH becomes idle, the BSC converts the TCH into a
CCCH.
When the TCH is still occupied (If the handover fails, the BSC
releases the call except a call initiated by a VIP user or an
emergency call.), the BSC fails to convert the TCH to a CCCH.
When the PDCH is released, the BSC converts the channel into a
CCCH.
When the PDCH is not released, the BSC fail to convert the PDCH
into a CCCH.
165
CCCHs are added one by one in the order of timeslot 2, 4, and then
6, whereas they are removed one by one in the order of timeslot 6, 4,
and then 2.
Related
Operations
Trouble
Ticket
Number
MBSC-OR-033
Feature ID
GBFD-511503
Issue 01 (2012-04-26)
166
Description
Benefit
Implementati
on
An NIU board is added for the BSC to support DPI, which identifies
the PS service class based on configured mapping between protocol
ID and service class.
The BSC allocates PDCHs to users based on user priority and
service class during channel allocation.
When MAC Scheduling Type is set to BUDGET(Scheduling
Based On Budget) or PFSCHEDULE(Proportion Fair
Scheduling), the BSC uses different weights to schedule services
with different user priorities and service classes.
The BSC uses different downlink TBF release delays for services
with different service classes.
Related
Operations
1.
2.
3.
4.
5.
Trouble
Ticket
Number
G-OR-PSDIFFERENT
Feature ID
GBFD-511603
GBFD-511604
GBFD-511605
GBFD-511606
GBFD-511607
48. PS AFC
Issue 01 (2012-04-26)
167
Description
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
G-OR-PSULAFC
Feature ID
GBFD-510105
49. Support for electronic label of an alternating current (AC) power module on an MRRU
or GRRU board in V3 RRU
Issue 01 (2012-04-26)
168
Description
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
None
Feature ID
GBFD-111202
Issue 01 (2012-04-26)
169
Description
Benefit
Implementati
on
Related
Operations
1.
2.
3.
Issue 01 (2012-04-26)
1.
2.
170
Trouble
Ticket
Number
G-OR-BTSIPHC
Feature ID
GBFD-118612
Issue 01 (2012-04-26)
171
Description
This feature encrypts data transmitted between a BTS and a BSC that
are connected to the network through an external security gateway.
This ensures data confidentiality, integrity, and non-repeated
transmission and provides operators with a secure end-to-end
network.
Benefit
Implementati
on
Related
Operations
1.
2.
3.
4.
5.
6.
7.
8.
9.
Trouble
Ticket
Number
OR-GBTS14-002
Feature ID
GBFD-113524, MRFD-211602
Issue 01 (2012-04-26)
172
Description
Benefit
Implementati
on
Related
Operations
1.
2.
3.
4.
5.
6.
7.
8.
Trouble
Ticket
Number
OR-GBTS14-005
Feature ID
GBFD-113526
Issue 01 (2012-04-26)
173
Description
Benefit
The built-in firewall filters out illegal data flows and malicious
packets to ensure that the BTS functions properly.
Implementati
on
Related
Operations
Trouble
Ticket
Number
OR-GBTS14-006
Feature ID
None
Issue 01 (2012-04-26)
174
Description
2.
3.
Benefit
Implementati
on
Related
Operations
1.
2.
Trouble
Ticket
Number
OR-GBTS14-046
Feature ID
None
Issue 01 (2012-04-26)
175
Description
Benefit
This feature prevents service interruption caused by the alarm ALM26529 RF Unit VSWR Threshold Crossed, improves network
stability, and reduces the operational expenditure of operators.
Implementati
on
To avoid resetting or replacing the faulty TRX module at the site and
service interruption caused by the alarm ALM-26529 RF Unit
VSWR Threshold Crossed, operators can determine whether to shut
down the power amplifier on a TRX module by setting the Serious
VSWR Alarm Post-processing Mode parameter of the SET
BTSRXUBP command.
If the power amplifier is not shut down, the TRX module can be
used. If the power amplifier is shut down, the TRX module must be
reset or replaced when the alarm is reported.
Related
Operations
Trouble
Ticket
Number
OR-GBTS18-088
Feature ID
None
Issue 01 (2012-04-26)
176
Description
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
OR-GBTS14-033
Feature ID
None
Issue 01 (2012-04-26)
177
Description
The One BBU Supporting 126 TRXs feature increases the maximum
number of TRXs supported by a single baseband unit (BBU) from 72
to 126 in TDM transmission mode. With this feature, more TRXs can
be configured without increasing the number of BTSs.
Benefit
Implementati
on
Related
Operations
None
Trouble
Ticket
Number
OR-GBTS14-008
Feature ID
None
Benefit
Implementati
on
The main control board checks whether the target and source
versions are consistent for a board. If they are consistent, the BTS
does not download files. If they are inconsistent, the BTS downloads
files from the BSC.
Related
Operations
None
Trouble
Ticket
Number
OR-GBTS14-023
Feature ID
None
Issue 01 (2012-04-26)
178
Description
Benefit
In scenarios where RRUs and BBUs are spaced far apart, this
feature:
Implementati
on
Related
Operations
1.
2.
Trouble
Ticket
Number
OR-GBTS14-024
Feature ID
None
Issue 01 (2012-04-26)
179
Description
Benefit
Implementati
on
Related
Operations
Run the DSP BTSPWR command to verify that the value for
Battery Intelligent Management Capability is Support and the
value for Battery Intelligent Management Switch is ON(On) in
the command output.
Trouble
Ticket
Issue 01 (2012-04-26)
G-OR-BTSBATIM
180
Number
Feature ID
GBFD-510710
Displays the alarm status for the receive and transmit ports of the
RRU, GTMU, GBBP, and UBRI optical/electrical module in the
Main Topology window of the M2000.
Queries and sets the threshold of the bit error rate (BER) at the
physical layer by running MML commands.
Benefit
This feature improves the efficiency of locating CPRI link and port
problems, enhancing BTS maintainability.
Implementati
on
1.
2.
The BTS supports the function of displaying the alarm status for
the receive and transmit ports of the RRU, GTMU, GBBP, and
UBRI optical/electrical module in the Main Topology window
of the M2000. If alarms are reported by the optical module, the
alarm indicator next to the optical port displays the status of
only the alarm with the highest severity.
3.
The BTS supports the function of setting and querying the BER
threshold at the physical layer by running MML commands.
The threshold can be set based on individual needs or left as the
default value.
Related
Operations
Trouble
Ticket
Number
OR-GBTS14-040
Feature ID
None
Issue 01 (2012-04-26)
181
Description
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
MBSC-OR-065
Feature ID
MRFD-211803
63. Support for GUI Components Used for Activating and Deactivating a Cell
Issue 01 (2012-04-26)
182
Description
Graphical user interface (GUI) components are added for activating and
deactivating a cell.
Benefit
Implementati In the Device Navigation Tree on the LMT, the options Activate Cell
and Deactivate Cell are added to the shortcut menu of every cell node.
on
Related
Operations
Activating a cell
To activate a cell, right-click the cell in the Device Navigation Tree on
the LMT and choose Activate Cell from the shortcut menu.
Deactivating a cell
To deactivate a cell, right-click the cell in the Device Navigation Tree
Issue 01 (2012-04-26)
183
on the LMT and choose Deactivate Cell from the shortcut menu.
Trouble
Ticket
Number
None
Feature ID
None
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
FF-002
Feature ID
MRFD-210304
Issue 01 (2012-04-26)
184
Description
Benefit
This feature locates and rectifies crossed pairs that are not detected
when a BTS is deployed and eliminates potential risks, improving
the network quality.
This feature enhances the delivery efficiency and quality and reduces
the delivery cost by decreasing reworking.
Implementati
on
Related
Operations
Trouble
Ticket
Number
CR GU01042
Feature ID
GBFD-111202
Issue 01 (2012-04-26)
185
Description
Benefit
Implementati
on
The BSC only sends GSM PS dummy frames that carry the Uplink
State Flag (USF) to BTSs. However, the BTSs still send dummy
blocks to MSs over the Um interface.
The BSC compresses GSM PS dummy frames that carry the USF.
Related
Operations
Trouble
Ticket
Number
CR GU01028
Feature ID
GBFD-117705
Issue 01 (2012-04-26)
186
Description
Benefit
Implementati
on
Related
Operations
In A over TDM mode, run the MOD OPC command to change the
OPC. The following is shown as an example:
MOD OPC: SPX=1, SPCBITS=BIT14, SPDF=WNF, SPC=101;
In A over IP mode or TDM/IP dual-stack mode, change an OPC as
follows:
To query whether the OPC to be changed is used by any M3LE, run
the LST M3LE command.
If the OPC is used by one M3LE, run the MOD OPC command to
change the OPC. The following is shown as an example:
MOD OPC: SPX=1, SPCBITS=BIT14, SPDF=WNF, SPC=101;
If the OPC is used by two or more M3LEs, do as follows to change
the OPC:
Run the following command to set all subracks to ineffective mode:
SET CFGDATAINEFFECTIVE:
Run the MOD OPC command to change the OPC. The following is
shown as an example:
MOD OPC: SPX=1, SPCBITS=BIT14, SPDF=WNF, SPC=101;
Run the SET CFGDATAEFFECTIVE command to set all subracks
to effective mode.
Run the FMT DATA command to generate a data configuration file.
Run the RST BSC command to reset the BSC6900. The following is
shown as an example:
RST BSC: BSCID=0;
Trouble
Ticket
Issue 01 (2012-04-26)
GBSC-OR-085
187
Number
Feature ID
None
Modified Features
1.
Support for Quick Identification of Single-user Tracing Files and Quick Entry of an
IMSI/TMSI/IMEI/MSISDN/TLLI
Description
This function helps users quickly identify the tracing file about a
specific user from a great number of tracing files.
This function also enables the LMT to display the latest five IMSIs,
TMSIs, IMEIs, MSISDNs, or TLLIs when users initiate one of the
following functions on the LMT:
Benefit
Without this feature, user tracing files are named in the same
format. To find a tracing file, users need to open all tracing files and
search for key information elements (IEs).
With this feature, users can quickly find specific tracing files for
individual users from a great number of tracing files. In addition,
when initiating any of the previously-mentioned functions on the
LMT, users are prompted with the latest five IMSIs, TMSIs, IMEIs,
MSISDNs, or TLLIs for quick entry.
Implementati
on
Related
Operations
N/A
Trouble
Ticket
Number
G-OR-TRACE
Feature ID
MRFD-210802
2.
Issue 01 (2012-04-26)
188
Description
Key information has been added into operation logs for tracing and
monitoring tasks.
Benefit
Implementati
on
Key information (for example, Cell ID, IMSI, Link No.) has been
added into operation logs for tracing and monitoring tasks.
Related
Operations
None.
Trouble
Ticket
Number
MBSC-OR-122
Feature ID
MRFD-210801/MRFD-210802
3.
Description
There is no plain text password for the operator user, FTP user, and
database of the BSC and BSC-related tools.
Improvement
The security of the operator user, FTP user, and database is enhanced.
Implementatio The plain text password for the BSC and BSC-related tools are
removed.
n
Related
Operations
N/A
PR Number
FF-024
Feature ID
MRFD-210305
4.
Description
Improvement
N/A
PR Number
FF-017
Feature ID
MRFD-210305
5.
Issue 01 (2012-04-26)
189
Description
Improvement
N/A
PR Number
FF-015
Feature ID
MRFD-210305
6.
Description
Benefit
The IP address in a file name helps users identify the source of the
file.
OMU hard disk space increases because all files in .txt format are
deleted.
Implementati
on
Related
Operations
Trouble
Ticket
Number
CR GU00856, CR GU00864
Feature ID
MRFD-210301
7.
Issue 01 (2012-04-26)
190
Description
For an OMU whose hard disk space is 146 GB, the maximum space
for storing binary logs is expanded from 9 GB to 16.4 GB and the
maximum number of the logs is increased from 12,000 to 30,000. If
the maximum space or number is reached, a new log replaces the
earliest log.
Benefit
The utilization of the OMU hard disk space is improved, and binary
logs can be kept for a longer time.
Implementati
on
The OMU is monitoring its hard disk space for storing binary logs
and the number of the logs. The maximum space and number are
16.4 GB and 30,000, respectively.
Related
Operations
None.
Trouble
Ticket
Number
CR GU01104
Feature ID
None.
8.
Description
Benefit
Implementati
on
When a user runs the ADD CCG or RMV CCG command, the
following information is recorded in the security log: Operator name,
Event Type, Event Level, Operation time, Detail Event, and IP
address.
Related
Operations
N/A
Trouble
Ticket
Number
MBSC-OR-314
Feature ID
MRFD-210305
9.
Issue 01 (2012-04-26)
191
Description
Benefit
Implementati
on
Related
Operations
Users can run MML commands on the M2000 or LMT to set the
maintenance mode for an NE.
Issue 01 (2012-04-26)
192
2011_10_19";
The maintenance mode of a BTS can be set to EXPAND or TESTING by
BTS ID or BTS name. If neither BTS ID nor BTS name is set, all the BTSs
are set to work in EXPAND or TESTING mode.
MBSC-OR-100
Feature ID
MRFD-210304
During the period that the OMU is reset or the active and standby
OMUs are switched over, performance statistics collected by the
OMU from the host are not saved as a result file. With the optimized
OMU performance measurement mechanism, the OMU will save the
statistics into a result file after the reset or switchover.
Benefit
Implementati
on
After the OMU is reset or the active and standby OMUs are switched
over, the OMU will check the performance statistics of the last
measurement period. If the statistics have not been saved into a result
file, the OMU will save them into a result file and report it to the
M2000.
Related
Operations
N/A
Trouble
Ticket
Number
MBSCSH-880
Feature ID
MRFD-210302
Issue 01 (2012-04-26)
193
Issue 01 (2012-04-26)
194
Description
Benefit
Implementati
on
The Route associated flag parameter has been added to the STR
IPCHK command. When the parameter is set to SBFD, the Route
associated flag parameter is set to YES by default.
When the Route associated flag parameter is set to YES and the
SBFD detection of an IP address fails, the BSC6900 automatically
isolates the route that uses the IP address as its next hop. When the
parameter is set to NO and the SBFD detection fails, the BSC6900
does not perform such an action.
Related
Operations
Run the STR IPCHK command. When Check type is set to SBFD,
set Route associated flag to an appropriate value. The following is
an example:
STR IPCHK: SRN=0, SN=26, CHKTYPE=SBFD,
CARRYT=ETHPORT, PN=0,
MODE=CHECK_ON_PRIMARY_PORT, PEERIP="99.9.9.100",
WHETHERAFFECTSWAP=YES,
ROUTEASSOCIATEDFLAG=NO;
Run the LST IPCHK command to query the value of Route
associated flag. The following is an example:
%%LST IPCHK: SRN=0, SN=14, CHKN=0,
LstFormat=VERTICAL;%%
RETCODE = 0 Execution succeeded.
List IP Connectible Check
------------------------Subrack No.
Subrack name
Slot No.
Check Index
Check type
Carry port type
Port No.
Trunk group work mode
Trunk group No.
Check mode
=
=
=
=
=
=
=
=
=
=
0
MPS
14
0
SBFD
ETHPORT
0
<NULL>
<NULL>
Check on Active
=
=
=
=
=
=
=
=
<NULL>
<NULL>
<NULL>
183.23.95.5
2
YES
100
100
Port
Issue 01 (2012-04-26)
195
Trouble
Ticket
Number
DTS2011041801780
Feature ID
GBFD-118601/GBFD-118602/GBFD-118603
=
=
=
=
=
3
<NULL>
<NULL>
YES
56
Issue 01 (2012-04-26)
196
Description
Benefit
Implementati
on
Related
Operations
Issue 01 (2012-04-26)
197
SOR-235
Feature ID
MRFD-210103
Issue 01 (2012-04-26)
198
Description
Benefit
Implementati
on
Related
Operations
To activate the IPPM function, run the ACT IPPM command. The
following is an example:
ACT IPPM: ANI=0, PATHID=1, ISQOSPATH=NO,
LOSTPKTDETECTSW=OFF;
Start a task of link performance monitoring to observe the link status
in real time, as shown in the following figure:
Trouble
Ticket
Number
CR GU00173
Feature ID
GBFD-118607
Issue 01 (2012-04-26)
199
Description
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
DTS2011050300195
Feature ID
GBFD-118601/GBFD-118602/GBFD-118603
Issue 01 (2012-04-26)
200
Description
Benefit
When the BSC6900 receives an AIS or RDI cell but the F5 entity is
not activated, the BSC6900 performs the following operations:
Sets both the permanent virtual connection (PVC) and the path
carried by the PVC to the unavailable state to isolate services from
the faulty path
Related
Operations
Trouble
Ticket
Number
DTS2011053000640
Feature ID
None
16. Support for the Modified Power Unit for Optical Ports
Issue 01 (2012-04-26)
201
Description
The transmit and receive power unit for optical ports is mW, but the
power unit for other transmission equipment is dBm. This difference
imposes difficulties in the deployment and routine maintenance. To
solve the problem, the transmit and receive power unit for optical
ports is changed to dBm in BSC6900 V900R014.
Benefit
The power unit is now uniform. This facilitates the deployment and
routine maintenance.
Implementati
on
The power value in the unit of mW is converted into the power value
in the unit of dBm with the following formula:
1 dBm = 10 x log(1 mW)
Related
Operations
Run the DSP OPT command to query the transmit and receive power
of an optical port. The following is an example:
DSP OPT: SRN=2, SN=14, BT=AOUc, PFMT=GROUP;
Trouble
Ticket
Number
CR GU00768
Feature ID
MRFD-210301
Issue 01 (2012-04-26)
202
Description
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
GU00945
Feature ID
MRFD-210305
Issue 01 (2012-04-26)
203
Description
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
DTS2011061303417
Feature ID
GBFD-110003
204
Description
Benefit
Implementati
on
Related
Operations
None
Trouble
Ticket
Number
None
Feature ID
GBFD-110003
Issue 01 (2012-04-26)
205
Description
Benefit
1. There are fewer message exchanges between the SPU and MPU
subsystems during RRC connection setups. This improves the MPU
subsystem performance.
2. The values of the VS.ANI.IP.Conn.Modify.Att and
VS.ANI.IP.Conn.Modify.Succ counters decrease because they are
measured on the MPU subsystem.
Implementati
on
Related
Operations
None
Trouble
Ticket
Number
DTS2011102606661
Feature ID
None
Benefit
Implementati
on
Related
Operations
None
Trouble
Ticket
Number
CR GU00797
Feature ID
None
Issue 01 (2012-04-26)
206
Description
PR Number
DTS2010080401370
Feature ID
GBFD-117002/ GBFD-114151
Issue 01 (2012-04-26)
207
Description
PR Number
FF-10
Feature ID
GBFD-115830/ GBFD-117002
Issue 01 (2012-04-26)
208
Description
Improvement
Implementatio After sending a Mute SAIC identification request, the BSC starts a
timer during which interference handover, bad quality handover, and
n
TCHF-TCHH handover are disabled. The timer value is calculated as
follows:
(MuteSaicIdeTotalTime x MuteSaicIdeOnePrdTime +1) x 1s
Related
Operations
N/A
PR Number
DTS2011070401933
Feature ID
GBFD-115831
Issue 01 (2012-04-26)
209
Description
This feature enables concentric cells to use the Voice Service over
Adaptive Multi-user channels on One Slot (VAMOS) function. The
following mechanisms have been modified for concentric cells: candidate
VAMOS user decision and VAMOS channel multiplexing decision.
The following condition for the downlink receive level has been added
for candidate VAMOS users:
The following condition for the downlink receive level has been added
for candidate VAMOS users:
Issue 01 (2012-04-26)
210
Related
Operations
DTS2011070401919
Feature ID
GBFD-115830
Issue 01 (2012-04-26)
211
Description
This feature increases the capacity for a multi-site cell and meets
the BTS capacity requirement of high-speed railways and indoor
coverage.
Implementati
on
The maximum number of subsites is increased to 30 in a multisite cell, and the maximum number of carriers per subsite is
increased to 12.
Trouble
Ticket
Number
G-OR-PSLOCGRP
Feature ID
GBFD-510104
Issue 01 (2012-04-26)
212
Description
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
CR GU00879
Feature ID
GBFD-115501
GBFD-115502
GBFD-115507
GBFD-110502
Issue 01 (2012-04-26)
213
Description
Benefit
Implementati
on
1.
2.
1.
Related
Operations
3.
Trouble
Ticket
Number
CR-GU00796
Feature ID
GBFD-111705
Issue 01 (2012-04-26)
214
Description
Benefit
Implementati
on
FDD_MULTIRAT_REPORTING
FDD_REPORTING_OFFSET
FDD_REPORTING_THRESHOLD
FDD_REPORTING_THRESHOLD_2
Issue 01 (2012-04-26)
215
S-OR-OSYSHOPARAOPT
Feature ID
GBFD-116201
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
CR GU01013
Feature ID
GBFD-114101
31. Adding Counters Related to the Number of Dummy Blocks with USF
Issue 01 (2012-04-26)
216
Description
Benefit
Implementati
on
The two counters are collected separately when the BSC schedules
downlink dummy blocks.
Related
Operations
Trouble
Ticket
Number
CR GU01031
Feature ID
GBFD-114101
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
G-OR-PSLOCGRP
Feature ID
GBFD-510104
Issue 01 (2012-04-26)
217
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
GBSS14.0-IR-0111
Feature ID
GBFD-510601
GBFD-510701
Issue 01 (2012-04-26)
218
Description
The GSM Flow Control feature incorporates the Ater radio signaling
link (RSL) flow control function. This function applies to Ater over
TDM when the BSC is configured in BM/TC separated mode. With
this function, the BSC performs flow control for optional services
when the RSL bandwidth is insufficient.
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
MBSC-OR-075
Feature ID
GBFD-111705
Issue 01 (2012-04-26)
219
Description
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
None
Feature ID
GBFD-510901
Issue 01 (2012-04-26)
220
Description
Benefit
Implementati
on
Based on the cause value carried in the CREF message from the
MSC, the BSC determines whether the MSC is congested. If the
MSC is congested, the BSC increases the flow control level for
signaling over the A interface, which increases the number of service
requests to be flow controlled.
The settings of the following parameters are invalidated:
Related
Operations
To activate signaling flow control over the A interface, run the SET
BSCFCPARA command with Allow Flow Control Upon A
Interface Signaling Congestion set to YES(Yes).
To adjust the effect of signaling flow control over the A interface,
run the SET BSCFCPARA command with Lower Threshold of
Messages Discarded on A Interface set to an appropriate value. A
larger value for this parameter indicates that more service requests
will be discarded due to flow control.
Trouble
Ticket
Number
MBSC-OR-015
Feature ID
GBFD-111705
Issue 01 (2012-04-26)
221
Implementati
on
Related
Operations
Run the SET GCELLHOFITPEN command to enable loadbased handover penalty inheritance. The following is an
example:
SET GCELLHOFITPEN: IDTYPE=BYID, CELLID=0,
LoadHoPunishInheritSwitch=ON;
Issue 01 (2012-04-26)
222
following is an example:
SET GCELLHOBASIC: IDTYPE=BYID, CELLID=0,
HOCTRLSWITCH=HOALGORITHM2,
INTRACELLHOEN=YES,
AMRFULLTOHALFHOQUALTHRESH=6,
NOAMRHALFTOFULLHOQUALTHRESH=2,
AMRF2HHOQUALTHFINE=9,
NOAMRH2FHOQUALFINE=1;
Trouble
Ticket
Number
MBSC-OR-017
Feature ID
GBFD-510501
CR GU01130
GBFD-510102
Issue 01 (2012-04-26)
223
Description
Benefit
Implementati
on
Decreases the call drop rate and increases the handover success
rate for intra-cell handovers using the HUAWEI I Handover
feature.
If the cell load is heavy and the call quality is higher than or equal to
the preset threshold, some MSs using TCHFs are allocated TCHHs.
If the cell load is light or the call quality is lower than the preset
threshold, some MSs using TCHHs are allocated TCHFs.
The Quick PBGT Handover Enable parameter is added to control
whether quick PBGT handovers are allowed when triggering
conditions are met. If Quick PBGT Handover Enable is set to
YES(Yes), quick PBGT handovers are allowed when triggering
conditions are met. If Quick PBGT Handover Enable is set to
NO(No), quick PBGT handovers are not allowed even when
triggering conditions are met.
The neighboring cell-level parameter Quick Handover Offset for
Neighbor Cell is added to allow different level offsets for a cell
serving as a neighboring cell for two cells at the same time. The
value of this parameter is used as an offset against the value for
Quick Handover Offset during quick PBGT handover decision.
The Bad Quality Handover Optimization Allowed parameter is
added. If this parameter is set to YES(Yes), only inter-cell BQ
handovers are allowed. If this parameter is set to NO(No), both intraand inter-cell BQ handovers are allowed.
The Interference Handover Optimization Allowed parameter is
added. If this parameter is set to YES(Yes), only intra-cell
interference handovers are allowed, and the priority for deciding
such handovers is lower than AMR TCHF-TCHH handovers. That is,
the priority for interference handovers is degraded from urgent to
Issue 01 (2012-04-26)
224
Trouble
Ticket
Number
MBSC-OR-051
Feature ID
GBFD-110601
CR GU01130
CR GU01265
GBFD-115522
GBFD-510102
Issue 01 (2012-04-26)
225
Benefit
Implementatio
n
Related
Operations
Trouble
Ticket
Number
CR GU00721
Feature ID
GBFD-111705
Issue 01 (2012-04-26)
226
Description
Benefit
Implementati
on
Also, users can browse and analyze saved tracing results offline.
Related
Operations
1.
2.
3.
4.
Click Submit.
Trouble
Ticket
Number
IR-GBSS14-NSTRACE-022
Feature ID
None
Issue 01 (2012-04-26)
227
Description
The AEC feature recognizes and processes acoustic echoes but has
low detection accuracy. To enhance the detection accuracy, this
release optimizes the echo detection algorithm for AEC and adds
AEC performance measurement.
Benefit
Implementati
on
Related
Operations
Run the SET TCPARA command. In this step, set AEC Switch to
ON(On) and specify AEC Mode for the DPU board.
None
Feature ID
GBFD-115602
Issue 01 (2012-04-26)
228
Description
Benefit
Implementat
ion
Related
Operations
Run the SET TCPARA command. In this step, set ALC Switch to
ON(On), ALC Mode to FIXEDLEVEL(Fixed level mode), and
ALC Fix Target Level to the recommended value for the DPU
board.
Run the SET TCPARA command. In this step, set ALC Switch to
ON(On), ALC Mode to FIXEDGAIN(Fixed gain mode), and ALC
Fix Gain to the recommended value for the DPU board.
Run the SET TCPARA command. In this step, set ALC Switch to
ON(On), ALC Mode to ADAPTIVE(Adaptive mode), and ALC
Max Target Level and ALC Min Target Level to the recommended
values for the DPU board.
None
Feature ID
GBFD-115601
Issue 01 (2012-04-26)
229
Description
During a voice call, the ANR feature decreases the noise level and
increases the signal-to-noise ratio, but does not effectively restrain
non-stationary noises. To address this problem, this release optimizes
the noise detection algorithm for ANR and adds ANR performance
measurement.
Benefit
Implementati
on
Related
Operations
Run the SET TCPARA command. In this step, set ANR Switch to
UPLINK(On for uplink) or DOWNLINK(On for dnlink), Noise
Suppression Algorithm Switch to MODE1(Optimized version),
and Noise Attenuation Mode, Noise Suppression Mode, and
Transparent Transmit Thresh of Noise Lev to appropriate values
for the DPU board.
None
Feature ID
GBFD-115603
Issue 01 (2012-04-26)
230
Description
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
None
Feature ID
GBFD-115703
Issue 01 (2012-04-26)
231
Description
Benefit
Implementat
ion
Based on the uplink measurement reports from the BTS, the BSC
dynamically adjusts the uplink transmit power of an MS performing
EGPRS services. With the uplink EGPRS closed-loop power control
function, the BSC decreases the MS transmit power without
compromising the MS uplink transmission performance.
Slow scheduling of uplink dummy blocks
The uplink extended TBFs during inactive periods are scheduled less
frequently, and the number of uplink dummy blocks sent by MSs is
reduced.
Related
Operations
Issue 01 (2012-04-26)
232
MBSC-OR-008
Feature ID
GBFD-119504
Issue 01 (2012-04-26)
233
Description
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
CR GU00831
Feature ID
GBFD-114301
Issue 01 (2012-04-26)
234
Description
Benefit
New MSs accessing the network are not allocated to any MSCs in
the offload state.
Implementati
on
Related
Operations
1.
2.
Trouble
Ticket
Number
G-OR-MSCPOOLREALLOC
Feature ID
GBFD-117401
Issue 01 (2012-04-26)
235
Benefit
Implementatio
n
Related
Operations
None
49. Optimizing the Measurement of Counters Related to Incoming BSC Handover Failures
and Counters Related to Call Drops
Issue 01 (2012-04-26)
236
Description
Benefit
Implementati
on
Issue 01 (2012-04-26)
237
CR GU00756
Feature ID
GBFD-110501
50. TFO
Description
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
None
Feature ID
GBFD-115701
51. VAMOS
Issue 01 (2012-04-26)
238
Description
Benefit
This reduces the VAMOS call drop rate and increases the handover
success rate, and saves transmission resources.
Implementati
on
Related
Operations
Trouble
Ticket
Number
MBSC-OR-032
Feature ID
GBFD-115830
CR GU01119
Issue 01 (2012-04-26)
239
Description
Benefit
Implementati
on
2.
3.
4.
The M2000 obtains the MML scripts and combines them into a
single MML script.
5.
The M2000 delivers this MML script to the target BSCs using
FTP.
6.
The M2000 instructs the target BSCs to run the received MML
script.
If SAIC capability identification is required, local switching and TFO cannot
be enabled. As a result, the numbers of local switchings and TFOs decrease.
After SAIC capability identification is disabled, the numbers of local
switchings and TFOs return to normal.
Related
Operations
Trouble
Ticket
Number
MBSC-OR-032
Feature ID
GBFD-115831
GBFD-115832
Issue 01 (2012-04-26)
240
Description
Benefit
Implementati
on
Encryption Algorithm 1
Encryption Algorithm 2
Encryption Algorithm 3
Encryption Algorithm 4
Encryption Algorithm 5
Encryption Algorithm 6
Encryption Algorithm 7
Trouble
Ticket
Number
CR GU00724
Feature ID
GBFD-113501
GBFD-113503
GBFD-113521
Issue 01 (2012-04-26)
241
Description
Benefit
Implementati
on
Related
Operations
Issue 01 (2012-04-26)
If the overlaid subcell load is lower than the value for Threshold
for OL Load with AMR HR Preferred, the BSC allocates
TCHFs to MSs. Otherwise, the BSC allocates TCHHs to MSs.
If the underlaid subcell load is lower than the value for Threshold
for UL Load with AMR HR Preferred, the BSC allocates
TCHFs to MSs. Otherwise, the BSC allocates TCHHs to MSs.
242
MBSC-OR-016
Feature ID
GBFD-113402
Issue 01 (2012-04-26)
243
Description
Benefit
Implementati
on
For 2 dB-step power control, the power control levels during two
consecutive power control periods are the same.
For 0.2 dB-step power control, the power control levels during two
consecutive power control periods are different.
1.
2.
Trouble
Ticket
Number
MBSC-OR-028
Feature ID
GBFD-117601
Issue 01 (2012-04-26)
244
Description
Benefit
2.
Reduces the call drop rate and increases the assignment and
handover success rates.
Related
Operations
The formula for calculating the path loss in active power control is
optimized to ensure that dynamic power boost technology (PBT)
gain is taken into account during calculation of path loss and
power level.
The BSC sends the value for Active Power Control Algorithm
Optimize to the BTS to ensure that the BTS correctly determines
the status of active power control.
Trouble
Ticket
Number
MBSC-OR-026
Feature ID
GBFD-117602
Issue 01 (2012-04-26)
245
Description
This feature allows users to maintain and monitor voice group call
service (VGCS)/voice broadcast service (VBS) calls as follows:
Benefit
Implementati
on
During a VGCS or VBS call, the BSC records the index of the cell
where the VGCS or VBS call is initiated and the resources occupied
by the VGCS or VBS speaker. After the DSP GRPCALLCELL and
DSP GRPCALLRES commands are executed with VGCS/VBS
No. and Service Type set to appropriate values, the information is
displayed on the LMT.
After the REL GRPCALL command is executed with VGCS/VBS
No., Service Type, and Release Mode set to appropriate values, the
BSC control connection sends a CLEAR REQUEST or UPLINK
RELEASE INDICATION message to the MSC. In this way, the
VGCS/VBS call or the VGCS/VBS speaker under the BSC is
released.
If VGCS Uplink Check Switch is set to ON(ON), the BSC checks
whether any uplink channels are occupied by VGCS calls. If the
uplink channels are abnormal, the BSC requests the MSC to release
these channels and updates the corresponding information.
Related
Operations
CR GU00877
Feature ID
GBFD-510301
Issue 01 (2012-04-26)
246
GBFD-510302
58. Adding Counters Related to DSP CPU and Resource Usage in the CS User Plane
Description
Benefit
The new counters enable users to better evaluate the operating status
of the TC DSP, facilitating network optimization.
Note that this feature increases the value for the following counters:
Implementati
on
Related
Operations
Trouble
Ticket
Number
CR GU00962
Feature ID
GBFD-111705
Issue 01 (2012-04-26)
247
Description
Benefit
Implementati
on
Related
Operations
Trouble
Ticket
Number
CR GU01130
Feature ID
GBFD-510102
Issue 01 (2012-04-26)
248
Description
The 16Kbit RSL and OML on A-bis Interface feature optimizes the
counter measurement method to resolve the following problem:
The number of call drops due to BTS port faults is counted into the
counter M3330A-Call Drops due to Abis Link Failures in Stable Local
Switch State. In normal cases, M3330A is used to count the number of
link establishment failures in Flex Abis mode.
With the optimization, the number of call drops due to BTS port faults
is now counted into the counter CM333-Call Drops due to Abis
Terrestrial Link Failure (Traffic Channel).
Benefit
Implementatio The Abis Territorial Link Fault Call Drop Stat parameter is added to
specify whether the number of call drops due to BTS port faults is
n
counted into the counter CM333. If this parameter is set to ON(On), the
number of call drops due to BTS port faults is counted into the counter
CM333.
By default, this parameter is set to ON(On) for newly-deployed sites
and to OFF(Off) for upgrade scenarios.
Related
Operations
GBFD-116701
61. Shortening Service Interruption Duration Due to Handovers in Local Switching When
the Abis Interface Uses Satellite Transmission
Issue 01 (2012-04-26)
249
Description
The BSC Local Switch and BTS Local Switch features are optimized.
The optimization shortens the service interruption for calls that meet the
following conditions during local switching:
Benefit
Implementatio The procedure for initiating a handover for a call using AMR speech
versions is simplified. In this way, the number of messages transmitted
n
over the Abis interface decreases, shortening the service interruption
duration.
Related
Operations
None
GBFD-117701
GBFD-117702
Issue 01 (2012-04-26)
250
Description
Benefit
The BTS allows the threshold for the IP PM Excessive Lost Packets
alarm to be configured.
The BTS collects IP PM-related statistical data and reports the data to
the BSC.
Implementatio
n
Related
Operations
When LAGs work in active and standby mode, the BSC starts IP PM.
If the active and standby LAGs are switched over, the BSC restarts IP
PM and clears the previously measured counters.
The BTS allows the threshold for the IP PM Excessive Lost Packets
alarm to be set. The default threshold is the same as that set on the
BSC side.
To activate BTS IP PM, run the ACT BTSIPPM command with its
parameters set as follows:
GBFD-118607
63. Optimization of License Usage Measurement for Certain License Control Items
Issue 01 (2012-04-26)
251
Description
The names of some license control items have been changed. The
license usage measurement for these license control items has been
optimized. In addition, the configuration data for some of these
license control items will be checked during an upgrade.
Benefit
Implementati
on
AMR HR Resource
DTM Resource
EICC Resource
ICC Resource
For users who have not used the preceding features, the
corresponding license control items are added. For users who have
used the preceding features, the license usage measurement of the
corresponding license control items is based on the number of TRXs
on which a specific feature is enabled.
The upgrade tool will check the new license capacity when users
who have used the following features implement an upgrade:
ICC Resource
Multiple CCCH
Issue 01 (2012-04-26)
252
License Resources will be reported every day within 60 days, and the
configuration on the system will be limited after 60 days.
Related
Operations
To query the current usage of each license control item, run the
following command:
DSP LICUSAGE: TYPE=Current;
Trouble
Ticket
Number
G-OR-SALE
Feature ID
None
Deleted Features
None.
Description
FG2d
GOUd
NIUa
Modified Hardware
None.
Removed Hardware
None.
Issue 01 (2012-04-26)
253
The BSC6900 cannot enter the emergency license state after a non-commercial license is
activated.
Trouble
Ticket
Number
DTS2011072200648
Description
Severity
Minor
Root Cause
Solution
Solution
Impact
N/A
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_001
2.
Issue 01 (2012-04-26)
In the command output of the LST OMUIPRT command, the automatically and
manually added IP routes to the OMU are not differentiated.
254
Trouble
Ticket
Number
DTS2011100802839
Description
Severity
Minor
Root Cause
Solution
The Is Service Route field has been added to the LST OMUIPRT
command. If an IP route to the OMU is added by running the ADD
OMUIPRT command, the value of this field is NO. If an IP route to
the OMU is added automatically when service data is configured, the
value of this field is YES.
Solution
Impact
None.
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_002
3.
Issue 01 (2012-04-26)
The ALM-20736 Data Inconsistency Between OMU and Host is reported too frequently.
255
Trouble
Ticket
Number
CR GU01206
Description
Severity
Suggestion
Root Cause
Solution
Solution
Impact
None.
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_003
4.
Reliability of some counters is shown as Unreliable when the DST offset is an integer
multiple of the measurement periods of these counters.
Trouble
Ticket
Number
DTS2011053000795
Description
Severity
Suggestion
Root Cause
Solution
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_005
Issue 01 (2012-04-26)
256
5.
The BSC6900 becomes out of service after an interface board is logically inhibited.
Trouble
Ticket
Number
DTS2011120505237
Description
Severity
Suggestion
Root Cause
Solution
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_006
6.
Issue 01 (2012-04-26)
257
Trouble
Ticket
Number
N/A
Description
Severity
Minor
Root Cause
The BSC6900 does not check the status of the standby destination IP
address for the SCTP link.
Solution
Solution
Impact
N/A
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_007
7.
Issue 01 (2012-04-26)
258
Trouble
Ticket
Number
iCare: none
Description
Severity
Minor
Root Cause
DTS2011082203465
None
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_401
8.
Issue 01 (2012-04-26)
The call drop rate increases in the process of replacing a transmission board or
disconnecting some of its cables.
259
Trouble
Ticket
Number
N/A
Description
Severity
Minor
Root Cause
Solution
Solution
Impact
N/A
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_011
9.
Issue 01 (2012-04-26)
260
Trouble
Ticket
Number
DTS2011051601792
Description
Severity
Minor
Root Cause
Solution
Solution
Impact
None
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_015
10. The performance measurement for the IP path ping process is inaccurate.
Trouble
Ticket
Number
DTS2011111706164
Description
Severity
Minor
Root Cause
Solution
Solution
Impact
None
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_016
Issue 01 (2012-04-26)
261
Issue 01 (2012-04-26)
262
Trouble
Ticket
Number
DTS2011112103224
Description
The severities defined for some alarms do not accurately reflect the
impacts of the reported issues.
Severity
Minor
Root Cause
Solution
In the alarm help, the severities of the alarms have been changed.
The severities of the following alarms are changed from "Warning"
to "Minor":
Solution
Issue 01 (2012-04-26)
None
263
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_018
DTS2011082502980
Description
The counter
VS.AAL2PATH.PVCLAYER.DROPFORTXOVERFLOWCELLS is
measured incorrectly for the AEUa, AOUa, and UOIa boards.
Severity
Minor
Root Cause
Solution
Solution
Impact
None
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_019
13. The configuration mode of the LMT login policy is not easy to use and poses security
risks.
Issue 01 (2012-04-26)
264
Trouble
Ticket
Number
MBSC-OR-122
Description
Severity
Minor
Root Cause
Solution
Solution
Impact
Reconfigure the LMT login policy after old versions are upgraded to
the current version because the original one becomes invalid after the
upgrade. The new LMT login policy will be inherited during later
upgrades.
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_020
14. The file manager on the LMT has defects in terms of user rights management and
security management.
Issue 01 (2012-04-26)
265
Trouble
Ticket
Number
MBSC-OR-122
Description
Severity
Minor
Root Cause
Solution
1.
Issue 01 (2012-04-26)
266
2.
All the file download, upload, and deletion operations in the file
manager will be recorded in operation logs.
Solution
Impact
None
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_021
DTS2011101200055
Description
Severity
Minor
Root Cause
Solution
The preceding alarm is reported only when the BSC6900 does not
receive ACT_ACK packets during IPPM activation.
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_022
16. Solving the problem that the CPU load has a sharp increase for a short period when the
system is in stable operation.
Issue 01 (2012-04-26)
267
Trouble
Ticket
Number
DTS2011072900852
Description
The CPU load has a sharp increase for a short period when the
system is in stable operation.
Severity
Minor
Root Cause
Solution
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_023
17. CS users fail to access the network due to a lack of LVDS resources.
Issue 01 (2012-04-26)
268
Trouble
Ticket
Number
N/A
Description
Severity
Minor
Root Cause
Solution
The CS user access algorithm has been optimized. CS users can now
preempt the LVDS resources of PS users when the LVDS resources
on the backplane are insufficient. In this way, access success rate for
CS users are not affected. However, access success rate for PS users
decreases while call drop rate and congestion rate for PS users
increase.
The ENPREEMPTABISLVDSADMT parameter has been added to
the SET BSCBASIC command. This parameter specifies the
preemption function.
The preemption function is enabled for new sites by default. For
exiting sites, whether this function is enabled depends on parameter
settings. The settings remain unchanged before and after an upgrade.
Run the following command to disable the preemption function:
SET BSCBASIC: ENPREEMPTABISLVDSADMT=OFF;
Run the following command to enable this function:
SET BSCBASIC: ENPREEMPTABISLVDSADMT=ON;
The preemption function is enabled by default.
Solution
Impact
N/A
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_009
18. The IP path cannot be changed on the BSC side when the IP address assigned by the
MGW changes in A over IP scenarios.
Issue 01 (2012-04-26)
269
Trouble
Ticket
Number
CR GU00504
Description
Severity
Major
Root Cause
The BSC uses the new IP address without updating the IP path.
Therefore, the BSC is connected to the old MGW by using the old IP
path.
Solution
If the new IP address assigned by the MGW is different from the old
one during the handover of a CS service, a pair of messages is added
in the BSC to request a new IP path. The new IP path must be
configured with the same local IP address and User Datagram
Protocol (UDP) port as the old one.
The response message of the newly added messages contains the old
IP path under any of the following conditions:
On the BSC side, the new and old local IP addresses are different.
The new IP address assigned by the MGW and the old one are on
the same network segment.
Solution
Impact
None
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_013
Issue 01 (2012-04-26)
270
Trouble
Ticket
Number
CR GU00794
Description
Severity
Minor
Root Cause
Solution
Now a DSP reports its CPU usage as well as the CPU usage step and
number of activated paths to the MPU. The MPU determines
whether to continue to allocate this DSP to new users based on the
reported information and the number of assigned paths on each DSP,
which is saved on the MPU. This helps to prevent DSPs from
becoming overloaded.
A DSP rejects new users if its CPU usage exceeds 95%.
Solution
Impact
N/A
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_012
20. The downlink TBF establishment success rate is lower than the actual value.
Issue 01 (2012-04-26)
271
Trouble
Ticket
Number
iCare: none
Description
The BSC does not properly measure the counters related to the
downlink TBF establishment success rate. As a result, the downlink
TBF establishment success rate is lower than the actual value.
Severity
Major
Root Cause
DTS2011092800528
Each time the downlink TBF establishment retry fails, the BSC
measures one TBF establishment attempt and one TBF
establishment failure.
1.
Issue 01 (2012-04-26)
If the first several downlink TBF establishments fail but the last
downlink TBF establishment initiated by the same PDU is
successful, the BSC measures one TBF establishment attempt and
one successful TBF establishment.
2.
272
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_403
21. CIC allocation fails because of repeated allocations of a CIC over the A interface.
Trouble
Ticket
Number
iCare: 166539
Description
Severity
Critical
Root Cause
DTS2011061702076
Because the BSC does not receive a GPRS Resume Ack message
from the PCU within a specified time, the BSC does not release the
CIC occupied by the current call upon receiving a Clear Command
message from the MSC. The MSC then requests the BSC to allocate
the CIC to another call.
In remote TC subrack configuration mode, the MSC requests the
BSC to reallocate a CIC if resource allocation fails over the Um
interface. Because the time sequence is reversed, the BSC may
allocate the CIC occupied by the current call again before releasing
it.
Solution
Upon receiving a Clear Command message from the MSC, the BSC
releases the CIC without waiting for the GPRS Resume Ack message
from the PCU.
The BSC does not reallocate the CIC if resource allocation fails over
the Um interface and the CIC to be allocated is the same as that
occupied by the current call.
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_404
Issue 01 (2012-04-26)
273
Trouble Ticket
Number
iCare: 337622
Description
Severity
Major
Root Cause
Solution
DTS2011090202243
Issue 01 (2012-04-26)
CASE_Commercial_PR_Regression_V9R14C00SPC200_405
274
23. The priority for a PS user to apply for an Abis link is incorrectly filled.
Trouble
Ticket
Number
iCare: none
Description
The priority for a PS user to apply for an Abis link is incorrectly filled.
This adversely affects the PS call drop rate and CS access success rate
when Abis links are congested.
Severity
Major
Root Cause
Solution
DTS2011090702169
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_406
Issue 01 (2012-04-26)
275
Trouble
Ticket
Number
iCare: none
Description
DTS2011101101795
Severity
Minor
Root Cause
Solution
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_407
25. Handovers due to TFO speech version incompatibility are incorrectly measured.
Issue 01 (2012-04-26)
276
Trouble
Ticket
Number
iCare: 121408
Description
If the speech versions used by the calling and called MSs are
incompatible at a site enabled with Tandem Free Operation (TFO),
the BSC hands over one of the MSs to another channel to make the
speech versions compatible. However, this type of handover
(handover due to TFO speech version incompatibility) is incorrectly
measured in the counters related to wideband AMR handovers.
Severity
Major
Root Cause
Solution
DTS2011061702141
Solution
Impact
None
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_408
26. The counter Number of Failed VAMOS Channel Multiplexing Attempts (Assignment) is
incorrectly measured.
Issue 01 (2012-04-26)
277
Trouble
Ticket
Number
iCare: none
Description
Severity
Minor
Root Cause
Due to a code defect, the BSC does not measure this counter.
Solution
The code defect has been rectified for the BSC to measure this counter
in the preceding scenario.
Solution
Impact
None
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_409
DTS2011071903442
27. The counter Number of Call Detect Messages Originated during Local Switching is
incorrectly measured.
Trouble
Ticket
Number
iCare: none
Description
Severity
Minor
Root Cause
Due to a code defect, the BSC does not measure this counter.
Solution
The code defect has been rectified to add the following measurement
point:
DTS2011070401771
None
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_410
28. The counters related to outgoing BSC handover failures are incorrectly measured.
Issue 01 (2012-04-26)
278
Trouble
Ticket
Number
iCare: none
Description
Severity
Minor
Root Cause
Due to a code defect, the BSC does not measure these counters.
Solution
DTS2011072801936
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_411
29. The counters Successful Outgoing Inter-Cell Handovers (Downlink Strength) and
Successful Outgoing Inter-Cell Handovers (Load) are incorrectly measured.
Trouble
Ticket
Number
iCare: none
Description
DTS2011092004536
Severity
Minor
Root Cause
The BSC uses the CURR method instead of the SUM method to
measure the two counters.
Solution
The method for measuring the two counters has been changed to
SUM.
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_412
30. The counters related to inter-BSC outgoing cell handovers are incorrectly measured.
Issue 01 (2012-04-26)
279
Trouble
Ticket
Number
iCare: none
Description
Severity
Minor
Root Cause
Due to a code defect, the BSC does not measure these counters.
Solution
The CSD Outgoing BSC HO Failure Stat. parameter has been added
to the SET OTHSOFTPARA command to rectify the code defect.
DTS2011081101695
If this parameter is set to NO(No), the BSC does not measure any of
the preceding counters.
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_413
Issue 01 (2012-04-26)
280
Trouble Ticket
Number
iCare: none
Description
Severity
Minor
Root Cause
The method for measuring the Call Drops on Traffic Channel counter
is incorrect.
Solution
The Equipment Fail Call Drop Stat. Optimize parameter has been
added to the SET OTHSOFTPARA command.
DTS2011052703759
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_414
32. The value for the P0 field in the packet assignment message is incorrect.
Trouble
Ticket
Number
iCare: none
Description
Severity
Minor
Root Cause
Solution
Solution
Impact
DTS2011111202255
The uplink TBF call drop rate and high quality indicator (HQI)
decrease by less than 1%.
Issue 01 (2012-04-26)
CASE_Commercial_PR_Regression_V9R14C00SPC200_415
281
33. The counter Number of Preferable Selections of TCHH in a Cell (Abis Resource
Congestion) is incorrectly measured.
Trouble
Ticket
Number
iCare: none
Description
DTS2011081802853
Not all the related networking modes are provided in the description of
this counter.
Severity
Minor
Cause
Solution
Impact
None
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_416
34. Inter-RAT load-based handovers fail on some MSs in the access state.
Issue 01 (2012-04-26)
282
Trouble
Ticket
Number
iCare: none
Description
Severity
Major
Root Cause
Solution
The Inter-RAT Directed Retry Timer parameter has been added for
users to customize the length of the inter-RAT directed retry timer.
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_417
DTS2011033104542
35. The number of successful Intra-BSC handovers is greater than the number of detected
intra-BSC handovers.
Issue 01 (2012-04-26)
283
Trouble
Ticket
Number
iCare: none
Description
Severity
Minor
Root Cause
Solution
The measurement method has been optimized for the BSC to measure
both the number of successful and detected intra-BSC handovers in
the preceding scenario.
Solution
Impact
DTS2011102803522
The value for the counter Call Drop Rate on TCH per cell (Including
Handover) decreases.
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_418
During inter-cell handovers for voice group call service (VGCS) calls,
the calculated value for the counter Rate of VGCS TCH Uplink Call
Drop exceeds 100%.
Severity
Minor
Root Cause
The denominator of the formula for calculating the counter does not
include the numbers of successful intra- and inter-BSC incoming VGCS
handovers.
Solution
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_419
37. The number of successful incoming BSC handovers is greater than the number of
detected incoming BSC handovers.
Issue 01 (2012-04-26)
284
Trouble
Ticket
Number
iCare: none
Description
DTS2011060400104
The BSC receives a Clear Command message with the cause value
Call Control before receiving a Handover Detect message.
In BSC Clear Command Statistics Opt Sw is set to ON(On).
Severity
Minor
Root Cause
Solution
The measurement method has been optimized for the BSC to measure
both the number of successful and detected incoming BSC handovers
in the preceding scenario.
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_420
38. The value for the counter Success Rate of Radio Handover exceeds 100%.
Trouble Ticket
Number
iCare: none
Description
The value for the counter Success Rate of Radio Handover exceeds
100% when the following conditions are met:
DTS2011041402150
Minor
Root Cause
The BSC does not measure the number of handover commands, but
incorrectly measures the number of successful handovers.
Solution
The BSC measures neither the number of handover commands nor the
number of successful handovers in the preceding scenario.
Solution
Impact
None
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_421
Issue 01 (2012-04-26)
285
iCare: none
Description
Severity
Minor
Root Cause
Solution
DTS2011070101833
1.
Test Case ID
2.
CASE_Commercial_PR_Regression_V9R14C00SPC200_422
Issue 01 (2012-04-26)
286
Trouble
Ticket
Number
iCare: 61358
Description
DTS2011061702165
Major
Root Cause
Solution
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_423
iCare: none
Description
Severity
Minor
Root Cause
Solution
Solution
Impact
The value for this counter will increase after the BSC is upgraded to
V900R014.
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_424
DTS2011110904012
42. Three counters in the measurement object IPPATH.RTP are incorrectly measured.
Issue 01 (2012-04-26)
287
Trouble
Ticket
Number
iCare: 504615
Description
DTS2011100901650
Major
Root Cause
Solution
Solution
Impact
The values for these counters may increase or decrease after the BSC
is upgraded to V900R014.
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_425
43. Call drops occur and too early handovers occur frequently because of pessimistic
interpolation.
Issue 01 (2012-04-26)
288
Trouble
Ticket
Number
iCare: none
Description
DTS2011090502764
Minor
Root Cause
Solution
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_426
44. The phase of a PCM code stream changes after A-law compression and decompression.
Issue 01 (2012-04-26)
289
Trouble
Ticket
Number
iCare: none
Description
Severity
Major
Root Cause
Solution
DTS2011111700519
If user data is transmitted over a TCH, do not enable the voice quality
enhancement functions (such as automatic noise reduction and anti-clip) or
the tandem free operation (TFO) function.
Solution
Impact
None
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_427
45. Call access fails because of incorrect processing of channel allocation policy.
Trouble
Ticket
Number
iCare: none
Description
Severity
Minor
Root Cause
Solution
Solution
Impact
DTS2011072503077
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_428
290
Trouble
Ticket
Number
iCare: none
Description
The BSC records an incorrect cause value for a handover failure due to
an incorrect IP address in A over IP mode.
Severity
Minor
Root Cause
Solution
The BSC records the cause value for such a failure as "MSC message
error".
Solution
Impact
The handover failures as "MSC message error" will increase and the
handover failures as equipment failure will decrease.
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_429
DTS2011072903749
47. The TFO codec type optimization function is occasionally ineffective in A over TDM
and BM/TC separated modes.
Trouble
Ticket
Number
iCare: none
Description
In A over TDM and BM/TC separated modes, the TFO codec type
optimization cannot reach the expected effect occasionally, leading to
a tandem free operation (TFO) connection setup failure.
Severity
Minor
Root Cause
Solution
Solution
Impact
None
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_430
DTS2011081205908
48. The DPUf fails to report counters under the measurement unit Measurement related to
RTP flux in IPPATH(IPPATH.RTP) in A over IP Mode.
Issue 01 (2012-04-26)
291
Trouble
Ticket
Number
iCare: none
Description
Severity
Minor
Root Cause
Solution
The DSP software module on the DPUf now uses a correct ID for an
IP path.
Solution
Impact
None
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_431
DTS2011092304664
49. The ALM-20243 Board Hardware Fault is generated on the DPUc or DPUa when AMRWB voice services are processed.
Trouble
Ticket
Number
iCare: none
Description
Severity
Major
Root Cause
Solution
The solution provided by the DSP chip vendor has been used to
solve this problem.
Solution
Impact
None
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_432
DTS2011121306363
Issue 01 (2012-04-26)
292
Reserved Parameter 8
Reserved Parameter 20
Reserved Parameter 21
Reserved Parameter 22
Minor
Root Cause
Solution
Issue 01 (2012-04-26)
Bit 8 of Reserved Parameter 8 has been converted to the PDCH-toTCH Adjustment parameter.
Bit 2 of Reserved Parameter 22 has been converted to the Call Resetup Timeout Call Drop Stat. Optimize parameter.
293
After conversion, external parameters inherit the settings from the bits
of the original reserved parameters. Therefore, the specified functions
continue to work properly after a BSC is upgraded to BSC6900
V900R014.
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_433
Severity
Minor
Root Cause
Solution
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_434
52. An invalid destination IP Address can be configured when the ADD BTSBFD command
is executed.
Issue 01 (2012-04-26)
294
Trouble
Ticket
Number
iCare: none
Description
Severity
Major
Root Cause
Solution
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_435
DTS2011121205162
53. Low-priority MSs occupy idle TCHs reserved for high-priority MSs.
Trouble Ticket iCare: none
Number
DTS2011102702318
Description
If there are idle TCHs reserved for high-priority MSs in a serving cell,
low-priority MSs that have failed in performing directed retry in the
serving cell can occupy these reserved TCHs.
Severity
Minor
Root Cause
Solution
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_436
Issue 01 (2012-04-26)
295
Severity
Minor
Root Cause
Solution
The BSC now does not allow the MS to wait in a queue again.
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_437
55. The BSC fails to transmit downlink DTMF signals after being upgraded.
Trouble Ticket iCare: none
Number
DTS2011112102692
Description
Severity
Minor
Root Cause
The DTMF Downlink Message Filter feature has been available since
BSC6900 V900R012C01. During an upgrade from
BSC6000V900R008C12 or BSC6900 V900R011C00 to BSC6900
V900R012C01, some configuration data is found to be abnormal. As a
result, the Downlink DTMF Signaling Processing Allowed parameter
is set to OPEN(Open) after the upgrade. When this occurs, the BSC
voice processing module filters downlink DTMF signals.
Solution
Solution
Impact
None
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_438
56. The CPU usage on the XPU increases and transmission resources are wasted in Flex
Abis mode.
Issue 01 (2012-04-26)
296
Severity
Major
Root Cause
Solution
Solution
Impact
Issue 01 (2012-04-26)
Impact
Decrease
Decrease
Impact
Decrease
297
Test Case ID
Decrease
Increase
Increase
CASE_Commercial_PR_Regression_V9R14C00SPC200_439
Severity
Minor
Root Cause
Solution
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_441
Issue 01 (2012-04-26)
298
Severity
Minor
Root Cause
Solution
Solution
Impact
Test Case ID
CASE_Commercial_PR_Regression_V9R14C00SPC200_442
59. Solving the problem that configuring a large number of PS cells across subracks lowers
the assignment success rate for CS services
Issue 01 (2012-04-26)
299
Trouble Ticket
Number
DTS2010111103425
Description
Severity
Major
Root Cause
Solution
CASE_Commercial_PR_Regression_ V9R14C00SPC200_443
Issue 01 (2012-04-26)
The communication between the OMU and host boards is interrupted when a nonphysical-layer fault occurs on the links between the OMU and the SCU boards
300
Description
Trigger
Condition
Impact
Severity
Minor
Workaround
None
Issue 01 (2012-04-26)
301
Changes from
V900R012C01SPC500 to
V900R014C00SPC200
Feature updates from V900R013C00SPC500 to V900R014C00SPC200, refer to 6.1.1Feature
Updates.
Feature updates from V900R012C01SPC500 to V900R013C00SPC500:
Issue 01 (2012-04-26)
302
Description
Some channels in a cell can always be reserved for VIP users, which
ensures the service quality for VIP users.
Improvement VIP channels in a cell are dedicated to VIP users, which ensure a high
access success rate for them. If the cell is congested, VIP users can still
quickly access the cell, but congestion may deteriorate because non-VIP
users cannot use VIP channels.
Implementati The parameters Reserved Channel Use Allow and Reserve Channel
have been added to the commands ADD VIPUSR and SET
on
GTRXCHAN, respectively.
Reserved Channel Use Allow specifies whether to allow a VIP user to
occupy VIP channels, and Reserve Channel specifies whether a channel
is reserved for VIP users.
Reserve Channel is valid only for traffic channels (TCHs), because VIP
users cannot occupy other types of channels.
A channel for which Reserve Channel is set to YES cannot be occupied
by a non-VIP user or by a VIP user for whom Reserved Channel Use
Allow is set to NO. This channel remains reserved and is not affected by
services on other channels.
After Reserve Channel is changed to YES for this channel and this
channel is occupied by an ordinary call, the serving BSC attempts to
transfer the service to a channel for which Reserve Channel is changed
to NO. If the target channel is occupied by a PS service, the serving BSC
releases the PS service.
When a user is handed over between two BSCs, the user's Reserved
Channel Use Allow value is recorded so that the user can occupy VIP
channels under the target BSC.
Related
Operations
PR Number
DTS2010110204358
Feature ID
GBFD-116001
2.
Issue 01 (2012-04-26)
303
Description
RRU3029
RRU3929
RRU3928
GRFU_V3
GRFUe
GRFU_V2a
MRFUe
MRFUd
MRFU_V2a
PR Number
SOR-70
Feature ID
None
3.
Issue 01 (2012-04-26)
Support for bit error detection and signaling link reliability improvement
304
Description
The bit error detection function is provided for signaling messages over
the Ater interface to optimize the data transmitting mechanism for
signaling links.
1.
2.
3.
To check whether this function has been enabled, run the following
command:
LST ATERSL: ATERSLID=0;
Send the signaling messages in the buffer of the faulty link over
another signaling link:
1.
2.
3.
To check whether this function has been enabled, run the following
command:
LST TNSOFTPARA: LstFormat=VERTICAL;
PR Number
OR 201003260376
Feature ID
GBFD-111203
4.
Issue 01 (2012-04-26)
305
Description
The Radio Measurement Data Interface for Navigation feature is used for
real-time navigation on high ways. With this feature, a VNP can collect
real-time measurement data for navigation.
Improveme
nt
Implement
ation
IP transmission is used between the BSC and the VNP. The BSC, which
provides TCP port 6200, reports MS-related application events to the
VNP through TCP/IP connections. The VNP then sends the measurement
data to a third-party server for calculation.
This feature can be enabled by setting the BSC-level Event Report
Switch parameter to ON.
The VNP IP Address parameter is used to set a valid VNP connection.
Negotiation with the VNP side is required to ensure correct configuration
of the Category Version, BSC Protocol Version No., and BSC
Application Version No. parameters.
The cell-level parameter Real-Time Event Report Switch is used to
specify whether a cell supports this feature.
Related
Operation
PR Number
SOR-020
Feature ID
GBFD-511701
5.
Issue 01 (2012-04-26)
306
Description
Improveme
nt
With this solution, call drops no longer occur when the MS with AFC
defects is multiplexed with another MS on an HR channel. This increases
network capacity and guarantees continuity of service.
Implement
ation
Related
Operation
PR Number
MBSCV9R13C00-OR-15
Feature ID
GBFD-115832
6.
Description
Improvemen The SCUb board provides the BSC6900 a high inter-subrack switching
capacity.
t
Implementa The SCUb hardware is added and its configuration data can be added by
using the ADD BRD command.
tion
If the SCUa board is configured for each subrack, the star topology is used
for inter-subrack connections. If the SCUb board is configured for each
subrack, the chain topology is used for inter-subrack connections.
Related
Operation
PR Number
MBSCV9R13C00-OR-1037
Feature ID
None
Issue 01 (2012-04-26)
307
7.
Description
Improvemen The OMUc board occupies only one slot and is much lighter than the
OMUa and OMUb boards. Compared with the OMUa and OMUb boards,
t
the OMUc board is designed with much lower power consumption and
larger memory and hard disk capacities.
Implementa The OMUc hardware is added and its configuration data can be added by
using the ADD BRD command.
tion
Related
Operation
PR Number
MBSCV9R13C00-OR-2110
Feature ID
None
8.
Description
The Data Processing Unit REV:f (DPUf) board is added. The DPUf board
processes GSM voice services and has a much higher service processing
capacity than the DPUa, DPUb, and DPUc boards.
The DPUf board has the following service processing capacities:
1920 TC channels
7680 interworking function flows in all-IP networking mode
3840 interworking function flows in Abis over TDM or Ater over TDM
mode
Improvemen When the BSC6900 uses DPUf boards, the service processing capacity of
the TC boards in the BSC is improved.
t
Implementa The DPUf hardware is added and its configuration data can be added by
using the ADD BRD command.
tion
Related
Operation
PR Number
MBSCV9R13C00-OR-160
Feature ID
None
Issue 01 (2012-04-26)
308
9.
Description
The Data Processing Unit REV:g (DPUg) board is added. The DPUg board
processes PS services of GSM. Compared with the DPUb and DPUd
boards, the DPUg board has a much higher PS service processing capacity
(maximum number of subscribers that can be processed by the board
simultaneously) though it supports the same amount of activated PDCHs.
The DPUg board supports a maximum of active 1024 PDCHs at an MCS9
rate.
Improvemen The DPUg hardware is added and its configuration data can be added by
using the ADD BRD command.
t
Implementa The DPUf hardware is added and its configuration data can be added by
using the ADD BRD command.
tion
Related
Operation
PR Number
MBSCV9R13C00-OR-68
Feature ID
None
Issue 01 (2012-04-26)
309
Description IP attack defense involves invalid packet check and ARP flooding attack.
Improveme
nt
Invalid packet check takes statistics about received invalid packets. When
detecting that the number of received invalid packets has exceeded a
specified invalid packet alarm threshold, invalid packet check reports
Invalid Packets Exceeding alarms (alarm ID: 21388) and records
information about attack sources. Users can obtain the information about
attack sources by viewing logs or running query commands. The
information assists users in updating system security policies against
attacks.
Invalid packet check enables users to check a network for invalid packets
and to obtain information about attack sources.
Implement The FG2c, GOUc, FG2d and GOUd support invalid packet check. The
FG2c, GOUc, FG2d, GOUd, FG2a, and GOUa support ARP flooding attack.
ation
The SET IPGUARD command is used to enable invalid packet check on the
FG2c, GOUc, FG2d and GOUd and to set Invalid Packet Alarm Threshold
and Invalid Packet Alarm Clearance Threshold.
The SET IPGUARD command is used to enable ARP learning strict on the
FG2c, GOUc, FG2d, GOUd, FG2a, and GOUa.
Related
Operation
Run the SET IPGUARD command to enable invalid packet check, with
Invalid Packet Alarm Threshold and Invalid Packet Alarm Clearance
Threshold set to the default values.
SET IPGUARD: SRN=2, SN=22, BRDTYPE=FG2c,
VALIDPKTCHKSW=ON;
Run the DSP INVALIDPKTINFO command to query information of the
invalid packet.
DSP INVALIDPKTINFO: SRN=2, SN=22;
Run the SET IPGUARD command to enable ARP learning strict.
SET IPGUARD: SRN=2, SN=20, BRDTYPE=GOUa,
ARPLRNSTRICTSW=ON;
PR Number MBSCV9R13C00-OR-1010
Feature ID None
Issue 01 (2012-04-26)
310
Description
To enable this feature, enable UDP ping detection on the BTS side, and
perform the following operations on the BSC6900 side:
Run the following command to enable UDP ping detection for the IP
path whose adjacent node ID is 100 and IP path ID is 0:
MOD IPPATH: ANI=101, PATHID=1, ITFT=ABIS,
PATHCHK=ENABLED, ECHOIP="11.11.11.11", CHECKT=UDP;
Run the following command to disable UDP ping detection for the IP
path whose adjacent node ID is 100 and IP path ID is 0:
MOD IPPATH: ANI=101, PATHID=1, ITFT=ABIS,
PATHCHK=DISABLED;
PR Number
MBSCV9R13C00-OR-2118
Feature ID
GBFD-118601
Issue 01 (2012-04-26)
311
Description
Improveme
nt
Implement
ation
VAMOS affects the voice quality of multiplexed voice users and causes
interference to the network. Therefore, in the load control algorithm,
VAMOS is enabled to expand network capacity only when the system
experiences channel resource congestion. When network load becomes
light, VAMOS is disabled to improve the voice quality of multiplexed
voice users.
Related
Operation
PR Number
MBSCV9R13C00-OR-15
Feature ID
GBFD-115830
Issue 01 (2012-04-26)
312
Description
Improveme
nt
This feature correctly identifies MS capabilities to ensure that SAICcapable MSs are paired with VAMOS. This increases the existing number
of MSs paired with VAMOS and expands network capacity.
Implement
ation
Related
Operation
PR Number
MBSCV9R13C00-OR-15
Feature ID
GBFD-115831
Improveme
nt
In the process of flow control, the priorities of MOCs and MTCs can be
configured.
Implement
ation
The MOC Access CPU Rate and MTC Access CPU Rate values
determine the priorities of calling and called users.
If the MOC Access CPU Rate value is greater than the MTC Access CPU
Rate value, calling users take precedence over called users. Therefore,
flow control is preferentially enabled for called users.
Related
Operation
Run the SET BSCFCPARA command to set MOC Access CPU Rate
and MTC Access CPU Rate. If the MOC Access CPU Rate value is
greater than the MTC Access CPU Rate value, calling users take
precedence over called users.
PR Number
MBSCV9R13C00-OR-190
Feature ID
GBFD-511003
Issue 01 (2012-04-26)
313
Description
During traffic bursts, the BSC adopts different flow control policies for
users based on enhanced Multi-Level Precedence and Preemption
(eMLPP) user priorities during flow control. This ensures high-priority
users enjoy services preferentially.
Improveme
nt
Implement
ation
Related
Operation
PR Number
MBSCV9R13C00-OR-191
Feature ID
GBFD-115003
Issue 01 (2012-04-26)
314
Description
Improveme
nt
Implement
ation
Related
Operation
PR Number
MBSCV9R13C00-OR-222
Feature ID
GBFD-511313
Improvem
ent
Implemen
tation
Related
Operation
PR
Number
MBSCV9R13C00-OR-172
Feature ID
GBFD-119506
Issue 01 (2012-04-26)
315
Descriptio
n
Improvem
ent
Implemen
tation
The first paging message is sent only to the last cell on which active PS
users camp and to its neighboring cells.
If the first paging fails and the cell paging policy is set to First precise
paging, the base station controller (BSC) sends paging messages to paging
areas specified by the core network (CN). If the cell paging policy is set to
Always precise paging, the BSC continues to send paging messages only
to the last cell on which the active PS users camp and to its neighboring
cells.
Related
Operation
PR
Number
CR GU00325
Feature ID
GBFD-511502
The earlier voice activity detection (VAD) algorithms may consider soft
music as silence and mistakenly encode it in the downlink. This affects
user experience.
Based on Huawei patented algorithm, the enhanced voice activity detector
(EVAD) enhances music recognition accuracy, significantly reducing the
probability that music is mistakenly considered as silence.
Improvem
ent
Implemen
tation
Related
Operation
Run the SET TCPARA command with EVAD Switch set to ON.
PR
Number
MBSCV9R13C00-OR-119
Feature ID
GBFD-115711
Issue 01 (2012-04-26)
316
MBSCV9R13C00-OR-78
Feature ID GBFD-117701
Issue 01 (2012-04-26)
317
Descriptio BTS3900B preconfiguration data such as the shared key of the IPsec tunnel
between the BTS3900B and the security gateway can be remotely modified
n
in batches on the BSC.
Improvem In versions earlier than V900R013C00, BTS3900B preconfiguration data is
first stored in a USB storage device and then imported into the BTS3900B
ent
through the USB storage device for data modification. This leads to a heavy
workload. In addition, most BTS3900Bs are deployed at homes. This makes
site maintenance inconvenient. Therefore, remote modification of BTS3900B
preconfiguration data in batches is required, which is implemented in
V900R013C00.
Implement Users update preconfiguration data on the BSC, and then BTS3900Bs save
the updated data to their memories. Then, the BSC activates the BTS3900Bs
ation
in batches on the BSC.
Related
To import BTS networking configuration data, run the IMP BTSNETPARA
Operation command.
To export BTS networking configuration data, run the EXP BTSNETPARA
command.
To import basic BTS IKE configuration data, run the IMP BTSIKECFG
command.
To export basic BTS IKE configuration data, run the EXP BTSIKECFG
command.
To import BTS IKEPEER configuration data, run the IMP BTSIKEPEER
command.
To export BTS IKEPEER configuration data, run the EXP BTSIKEPEER
command.
To activate imported BTS configuration data, run the ACT BTSIMPDATA
command.
For example,
Import BTS networking configuration data by running the following
command:
IMP BTSNETPARA: IDTYPE=BYID, BTSID=900,
IPSECSWITCH=ENABLE, BTSIP="10.10.12.13",
MASK="255.255.255.0", BTSGATEWAYIP="10.10.12.14",
BTSDNSIP="10.10.12.15", ADDRTYPE=BYIP, PSEGWIP="10.10.12.16",
M2000IP="10.10.12.17";
Import basic BTS IKE configuration data by running the following
command:
IMP BTSIKECFG: IDTYPE=BYID, BTSID=900,
LOCALNAME="admin", KEEPALIVEINTERVAL=20,
KEEPALIVETIMEOUT=28800;
Import BTS IKEPEER configuration data by running the following
command:
IMP BTSIKEPEER: IMP BTSIKEPEER: IDTYPE=BYID, BTSID=900,
GWTYPE=PSEGW, PEERNAME="admin", IKEVERSION=IKE_V2,
LOCALIDTYPE=IP, REMOTEIP="10.10.12.13", DPDSW=PERIODIC,
DPDIDLETIME=15, DPDRETRYITV=16, DPDRETRYCNT=10;
Activate imported BTS configuration data by running the following
command:
Issue 01 (2012-04-26)
318
MBSCV9R13C00-OR-180
Feature ID None
MBSCV9R13C00-OR-197
Feature ID None
Issue 01 (2012-04-26)
319
Descriptio In IP over E1/T1 transmission mode, a typical small IP packet, such as speech
packet, over the Abis interface takes only 50% to 60% payload. In this case,
n
the transmission efficiency is low. By using the IP header compression
(IPHC) function, IP/UDP packet headers are compressed to increase the data
payload, saving IP transmission resources.
Improvem By using IPHC over the Abis interface, the IP header of the data packet is
compressed over the Abis interface, saving transmission resources. For
ent
example, the typical full-rate speech data packet is shortened from 72 bytes to
48 bytes, saving more than 30% transmission resources.
Implement Add the IP Header Compression parameter to the ADD BTSPPPLNK and
ADD MPGRP commands and set this parameter to ENABLE. In this way, the
ation
BTS supports IP/UDP header compression and the BSC can parse the
compressed packet.
Related
Run the ADD BTSPPPLNK/MOD BTSPPPLNK or ADD
Operation BTSMPGRP/MOD BTSMPGRP command to set IP Header Compression
to ENABLE or DISABLE.
Run the LST BTSPPPLNK or LST BTSMPGRP command to query
whether the IPHC function is enabled.
Run the DSP BTSPPPLNK or DSP BTSMPGRP command to query
whether the IPHC function takes Improvement on the BTS side.
PR
Number
MBSCV9R13C00-OR-10
Feature ID GBFD-118612
24. Support for creation, deletion, and query of a task for tracing a single GSM user by using
MML commands
Issue 01 (2012-04-26)
320
Description A task for tracing a single GSM user can be created by using an MML
command.
Improveme
nt
The tracing of a single GSM user can be created and deleted by using
MML commands.
This helps operators to conduct signaling tracing of a VIP user and analyze
traced signaling, which improves the user experience of VIP users.
Implementa A task for tracing a single GSM user can be created, deleted, and queried
by using the related MML commands.
tion
Related
Operation
PR Number
DTS2010102502035
Feature ID
GBFD-116401
25. Support for the BSC obtaining clock signals from the Abis interface in TDM mode
Issue 01 (2012-04-26)
321
Description The BSC can obtain clock signals from the Abis interface in TDM mode.
Improveme When the A interface is in IP over E1 mode, the BSC can obtain clock
signals from the A interface. When the A interface is in IP over Ethernet
nt
mode, and the Abis interface is in TDM mode, the BSC can obtain clock
signals from the Abis interface to ensure the frequency synchronization
between the BSC and BTS.
Implement The GCUa or GCGa obtains the line clock signals from the Abis interface
and then distributes the signals to other boards in the BSC through the
ation
backplane. This achieves the clock synchronization between the BSC and
BTS.
Related
Operation
PR Number None
Feature ID
SOR-82
26. Support for IP port backup of the BTS and access of monitoring devices through IP ports
Issue 01 (2012-04-26)
322
Description IP port backup of the BTS and access of monitoring devices through IP ports
are supported as follows:
A BTS working in IP over FE mode has an Ethernet optical port and an
electrical port. The ports can work simultaneously or in active/standby mode
for BTSs working under BSC6900 V900R013C00. If one port is faulty,
services are quickly switched to the other port. This improves transmission
reliability.
Third-party monitoring devices can be connected over IP ports to a BTS
working under BSC6900 V900R013C00.
Improveme
nt
Issue 01 (2012-04-26)
323
PR Number
MBSCV9R13C00-OR-7
Feature ID
None
27. Support for BTS transmission maintainability and testability in IP network mode
Description The state of Ethernet ports, Address Resolution Protocol (ARP) attributes,
and E1/T1 attributes of a BTS can be queried.
Improveme Transmission faults can be located and the network quality can be detected
in IP network mode.
nt
Implementa The state of Ethernet ports, ARP attributes, and E1/T1 attributes of a BTS
can be queried by running the DSP BTSETHPORT, DSP BTSARP, and DSP
tion
BTSE1T1 commands respectively.
Related
Operation
To query the E1/T1 attributes of a single port of a BTS, run the following
command:
DSP BTSE1T1: IDTYPE=BYID, BTSID=0, CN=0, SRN=0, SN=6,
PS=SINGLEPORT, PN=0, LSTFORMAT=VERTICAL;
To query the state of an Ethernet port of a BTS, run the following command:
DSP BTSETHPORT: IDTYPE=BYID, BTSID=0, CN=0, SRN=0, SN=6,
PN=0, LSTFORMAT=VERTICAL;
To query the ARP attributes of a BTS, run the following command:
DSP BTSARP: IDTYPE=BYID, BTSID=0, CN=0, SRN=0,
SN=6,LSTFORMAT=VERTICAL;
PR Number
MBSCV9R13C00-OR-1011
Feature ID
None
28. Support for RF maintenance and test over the air interface
Issue 01 (2012-04-26)
324
Description This function helps improve the capability of locating RF-related problems
over the air interface. It is applicable to the following scenarios:
1. RF counter test under site deployment
2. RF intermodulation detection in routine operation and maintenance (OM)
3. Obtaining frequency spectrum remotely (with capacity loss)
4. Obtaining frequency spectrum locally (with capacity loss)
5. Obtaining frequency spectrum remotely (without capacity loss)
6. Interference identification and cancellation
Improveme A spectrum analyzer is a bottleneck of improving the capability of identifying
and canceling RF interferences. This function moves part of the common
nt
functions of the spectrum analyzer to the BSC, thereby reducing OPEX and
improving OM efficiency.
Implement
ation
Issue 01 (2012-04-26)
RF
count
er test
under
site
deplo
ymen
t
RF
inter
modu
lation
detect
ion in
routin
e
opera
tion
and
maint
enanc
e
Obtaini
ng
frequen
cy
spectru
m
remotel
y (with
capacity
loss)
Obtaini
ng
frequen
cy
spectru
m
locally
(with
capacit
y loss)
Obtaini
ng
frequen
cy
spectru
m
remotel
y
(withou
t
capacit
y loss)
Interf
erenc
e
identi
ficati
on
and
cance
llatio
n
Remote offline
RF counter test
Local offline
RF counter test
Online antenna
passive
intermodulation
test
Remote
spectrum
scanning
Local spectrum
scanning
Y
-
325
Related
Operation
Online
spectrum
scanning
CDMA
interference test
PR Number MBSCV9R13C00-OR-91
Feature ID
None
To enable this function, run the following command with Whether to Enable
Energy Consumption Measurement set to YES and Energy Consumption
Measurement Point to AC:
SET BTSOTHPARA: IDTYPE=BYID, BTSID=0, SPRECM=YES,
ECMP=AC;
PR Number MBSCV9R13C00-OR-63
Feature ID None
30. Support for 12-level static power control for the BTS3900B.
Issue 01 (2012-04-26)
326
Run the SET GRXDEV command to configure static power levels for the
BTS3900B.
For example, to configure the static power control level to 11, run the SET
GTRXDEV command with Power Level set to 11.
SET GTRXDEV: TRXID=123, POWL=11;
PR Number DTS2011010800192
Feature ID None
Run the SET BTSTRXBACKUP command to configure TRX backup for the
BTS3900B.
Run the SWP GTRX command to manually swap backup TRXs.
For example, to enable TRX backup for the BTS3900B, run the SET
BTSTRXBACKUP command with TRX Backup Switch set to ON.
SET BTSTRXBACKUP: IDTYPE=BYID, BTSID=123, TRXBPSW=ON;
To manually swap backup TRXs, run the SWP GTRX command.
SWP GTRX: IDTYPE=BYID, BTSID=123;
PR Number DTS2011010800192
Feature ID None
Issue 01 (2012-04-26)
327
Run the SET BTSUSERPWD command to change SMT user names and
passwords.
For example, to change SMT user names and passwords based on cell
identifiers and location area codes (LACs), run the SET BTSUSERPWD
command with Username and Password Type set to By Cell CI and LAC.
SET BTSUSERPWD: IDTYPE=BYID, BTSID=123, UPTYPE=CI_LAC;
PR Number DTS2011010800192
Feature ID None
Issue 01 (2012-04-26)
328
Descriptio The base station (BS) clock is remotely maintained based on location
information, which is provided by the BS clock module on the LMT.
n
Improveme Network jitter and phase discrimination data is collected to identify BS clock
faults.
nt
Implement Tasks are added on the LMT for monitoring the BS clock module and
obtaining location information. Monitoring results are displayed on the LMT.
ation
Related
Operation
On the LMT, choose Monitor > GSM Monitoring > Clock Test.
Set Monitor Item, Site, and Duration, and then click Start.
View results.
Issue 01 (2012-04-26)
329
PR Number MBSCV9R13C00-OR-52
Feature ID None
34. Support for isolation of E1/T1 ports on the POUc_TDM, EIUa, and OIUa when the BER
exceeds a specified threshold
Issue 01 (2012-04-26)
330
Description When the BER of an E1/T1 link exceeds a specified threshold, the BSC
automatically blocks the E1/T1 link. A blocked E1/T1 link does not carry
any services. When detecting that the BER of a blocked E1/T1 link is lower
than a specified threshold, the BSC automatically unblocks the E1/T1 link.
Then, the E1/T1 link continues to carry services.
Improveme When detecting that the BER of an E1/T1 link has exceeded a specified
threshold, the POUc_TDM, EIUa, and OIUa automatically block the E1/T1
nt
link and isolate its services.
User experience is improved by preventing time division multiplexing
(TDM) microwave transmission from being disconnected intermittently for
a long period of time.
Implement 1. The SET E1T1 command is used to enable isolation of E1/T1 ports on
the POUc_TDM, EIUa, and OIUa and to set an isolation threshold.
ation
2. When detecting that the BER of an E1/T1 link has exceeded the specified
threshold, the POUc_TDM, EIUa, and OIUa automatically block the E1/T1
link, isolate its services, and report E1/T1 Excessive Bit Error Rate alarms
(alarm ID: 21207). When detecting that the BER of a blocked E1/T1 link is
lower than the specified threshold, the POUc_TDM, EIUa, and OIUa
automatically unblock the blocked E1/T1 link and clear E1/T1 Excessive Bit
Error Rate alarms (alarm ID: 21207).
Related
Operation
1. Run the SET E1T1 command to enable isolation of E1/T1 ports on the
POUc_TDM, EIUa, and OIUa and to set an isolation threshold.
SET E1T1: SRN=0, SN=18, BT=POUc, PS=SINGLE, PN=0,
BERAUTOISOSW=ON, BERAUTOISOTHRD=O1E3_R5E4;
2. Run the LST E1T1 command to query execution results.
LST E1T1: SRN=0, SN=18, BT=POUc, PN=0, LstFormat=VERTICAL;
PR Number MBSCV9R13C00-OR-152
Feature ID None
35. Support for query of electronic labels of EMUs, cabinets, and optical modules using
MML commands
Issue 01 (2012-04-26)
331
MBSCV9R13C00-OR-175
Feature ID MRFD-210303
CMM: BB4D41262
Feature ID None
Issue 01 (2012-04-26)
332
MBSCV9R13C00-OR-1050
Feature ID MRFD-210305
Issue 01 (2012-04-26)
333
MBSCV9R13C00-OR-1048
Feature
ID
MRFD-210305
Issue 01 (2012-04-26)
334
Descriptio In versions earlier than V900R013C00, after the upgrade client is started
using the M2000, the M2000 does not trace the upgrade operations and the
n
upgrade client performs the upgrade operations.
In V900R013C00, this function enables users to create an upgrade task and to
query the process, progress, and status of the upgrade task on the M2000
client. This function also enables users to save and view an upgrade report on
the M2000 client after the upgrade is complete.
Improvem The effects of this function are as follows:
ent
A task of upgrading a base station controller is created on the M2000 client.
The interface of creating this task is the same as that of creating a task of
upgrading other types of network elements (NEs) on the M2000 client.
Users can query the upgrade progress, upgrade status, and upgrade result on
different M2000 clients.
After the upgrade is complete, the upgrade report is saved on the M2000
server. Users can view the upgrade report at any time after the upgrade is
complete.
Operation Type no longer needs to be specified when an NE is upgraded,
reducing misoperations. In addition, the password for user admin no longer
needs to be entered, omitting redundant authentication, when the BSC6810 or
BSC6900 products earlier than V900R013C0 are upgraded to BSC6900
V900R013C00.
Implement When an NE is upgraded using the M2000, the M2000 provides the upgrade
type as well as the IP address and account information of the FTP server for
ation
the NE. During the upgrade, the upgrade client uploads the information of the
upgrade progress and upgrade status to the FTP server so that the information
is displayed on the M2000 client. After the upgrade is complete, the NE
uploads the upgrade report to the FTP server. Then, the M2000 saves the
upgrade report so that users can view it at any time.
Related
Upgrade and roll back an NE by using the M2000.
Operation
PR
Number
MBSCV9R13C00-OR-1014
Feature ID GBFD-111213
40. Support for automatic dialing test on the A interface for the slave BSC in the TC pool
scenario
Issue 01 (2012-04-26)
335
Description The automatic A-interface dialing test is supported for the slave BSC in the
TC pool scenario.
Improveme The A-interface dialing test is mandatory after a BSC in BM/TC separated
mode is deployed. After the A-interface dialing test is supported, the dialing
nt
test can be performed automatically, improving the working efficiency.
Implement The dialing test on the A interface aims to check whether CICs on the A
interface are normal. During a dialing test, the BSC tests the CICs one by one.
ation
It identifies the MSISDN of the MS that is used for the dialing test and blocks
the CIC used by the test call after the call is released so that a CIC will not be
repeatedly tested. To enable the A interface dialing test on the slave BSC in a
TC pool scenario, the dialing test switch must be turned on at both the
primary BSC and the slave BSC.
This function can only be used by maintenance personnel during site
deployment because a large amount of A-interface CICs will be blocked after
this function is enabled. After performing dialing tests, disable this function to
unblock the CICs.
Related
Operation
To enable this function, run the following command on the primary and slave
BSCs respectively:
SET ATESTPARA: AINTFTESTENABLE=YES,
AINTFTESTMSISDN1="13511486327",
AINTFTESTBLOCKCICENABLE=YES,
AINTFTESTSAMPLINGENABLE=YES,
AINTFTESTSAMPLINGNUMBER=6, ATESTBSCID=5;
In this command,
MSISDN1 in A Interface Test is the MSISDN of the MS used for the test;
A Interface Block CIC and A Interface Sampling Test must be set to YES;
To disable this function, run the following command on the primary and
slave BSCs separately:
41. Support for automatic detection of the connection between TNU boards in different
subracks
Issue 01 (2012-04-26)
336
Descriptio The BSC checks the connection between the TNU boards in different
subracks, and reports an alarm "Inter-Subrack Connection Resources exist
n
fault alarm" (ID: 21601) if a fault is detected. If a fault is detected on a link
that connects two active TNU boards, that link is isolated.
Improvem The inter-subrack connections are checked periodically and an alarm is
reported if any fault is detected. In addition, the faulty link is isolated to
ent
avoid the one-way audio or no audio problem caused by the link fault.
Implement The BSC periodically sends check data on the links between TNU boards in
different subracks.
ation
Related
This function is enabled by default.
Operation To disable this feature, run the following command on the primary and slave
BSCs separately:
SET TNSOFTPARA: SrConPathCheckSwitch=OFF;
To enable this function again, run the following command on the primary and
slave BSCs separately:
SET TNSOFTPARA: SrConPathCheckSwitch=ON;
PR
Number
MBSCV9R13C00-OR-209
Feature ID None
Issue 01 (2012-04-26)
337
Description The two links in a Link Aggregation Group (LAG) in active and standby
mode have different priorities. When the high-priority link is functional, the
data stream carried by the LAG is transmitted only over the high-priority
link. When the high-priority link is faulty, the data stream is transmitted
over the low-priority link.
Improveme In addition to the LAG in load sharing mode, the LAG in active and standby
mode is added to achieve flexible transmission networking.
nt
Implement 1. The Trunk group work mode and Revertive type parameters are added to
the MML command ADD ETHTRK so that the LAG can work in either
ation
load sharing mode (LOAD_SHARING) or active and standby mode
(ACTIVE_STANDBY), and the LAG can be of the revertive
(REVERTIVE) or non-revertive type (NON-REVERTIVE).
If the LAG in active and standby mode is set as the revertive type, the data
stream carried by the LAG will be switched back to the high-priority link
when the faulty high-priority link is recovered.
If the LAG in active and standby mode is set as the non-revertive type, the
data stream carried by the LAG will still be transmitted over the lowpriority link when the faulty high-priority link is recovered.
2. The Trunk group work mode and Port priority parameters are added to the
MML command ADD ETHTRKLNK so that links in the LAG can work in
either load sharing mode or active and standby mode and can be prioritized.
Related
Operation
1. To add an LAG in active and standby mode and of the non-revertive type,
with the negotiation mode of static LACP, run the following command:
ADD ETHTRK: SRN=0, SN=18, TRKN=0,
WORKMODE=ACTIVE_STANDBY, LACPMODE=STATIC_LACP,
FLOWCTRLSWITCH=ON;
2. To add two links with priorities 80 and 100 in an LAG in active and
standby mode, run the following command:
ADD ETHTRKLNK: SRN=0, SN=18, TRKN=0, TRKLNKSN=18,
TRKLNKPN=0, WORKMODE=ACTIVE_STANDBY, PORTPRI=80;
ADD ETHTRKLNK: SRN=0, SN=18, TRKN=0, TRKLNKSN=18,
TRKLNKPN=1, WORKMODE=ACTIVE_STANDBY, PORTPRI=100;
3. To query the status information about the LAG in active and standby
mode, run the following command:
DSP ETHTRK: SRN=0, SN=18, TRKN=0;
4. To query the status information about a link in the LAG in active and
standby mode, run the following command:
DSP ETHTRKLNK: SRN=0, TRKLNKSN=18, TRKLNKPN=1;
PR Number None
Feature ID
MRFD-210103
43. Support for activating or deactivating the light emission function of a single optical port
Issue 01 (2012-04-26)
338
Description
The light emission function of a specific optical port on the POUc board
can be activated or deactivated by running the ACT OPTPORT or DEA
OPTPORT command respectively.
Improvemen
t
Users can deactivate the light emission function of idle optical ports on
the POUc boards by running the DEA OPTPORT command on the
LMT. This reduces the power consumption of optical ports.
Implementat
ion
Related
Operation
To deactivate the light emission function of a specific optical port, run the
following command:
DEA OPTPORT: SRN=0, SN=18, PN=0;
To activate the light emission function of a specific optical port, run the
following command:
ACT OPTPORT: SRN=0, SN=18, PN=0;
PR Number
None
Feature ID
MRFD-210301
44. Support for setting the generation threshold for B3 signal failure and B3 signal
degradation to IE-3 for an OIUa board
Issue 01 (2012-04-26)
339
Description
For an OIUa board, users can run the SET OPT command to set the
generation threshold for B3 signal failure and B3 signal degradation to IE3 and the corresponding recovery threshold to IE-4.
Improvemen The enumeration values of the generation threshold for B3 signal failure
and for B3 signal degradation of the OIUa board are changed from [1E-9,
t
1E-8, 1E-7, 1E-6, 1E-5, 1E-4] to [1E-9, 1E-8, 1E-7, 1E-6, 1E-5, 1E-4, IE3]. This expands the value range, thereby improving the transmission
compatibility.
Implementa The B3 signal fail threshold and B3 signal degraded threshold parameters
are added with an enumeration value O1E3_R1E4.
tion
Related
Operation
To set the generation threshold for B3 signal failure to IE-3 and the
recovery threshold for B3 signal failure to IE-4, run the following
command:
SET OPT: SRN=0, SN=18, BT=OIUa, B3SFTHRD=O1E3_R1E4;
To set the generation threshold for B3 signal degradation to IE-3 and the
recovery threshold for B3 signal degradation to IE-4, run the following
command:
SET OPT: SRN=0, SN=18, BT=OIUa, B3SDTHRD=O1E3_R1E4;
PR Number
None
Feature ID
MRFD-210304
Click Lockup Setting on the LMT. The Lockup Setting dialog box is
displayed. Select Auto lockup and set the duration.
Enter the password again to log in to the LMT after the LMT screen is
locked.
SET OPT: SRN=0, SN=18, BT=OIUa, B3SDTHRD=O1E3_R1E4;
PR Number
None
Feature ID
None
Issue 01 (2012-04-26)
340
46. Support for OMU database can be backed up and restored on the LMT
Description
Improvemen The OMU database can be backed up and restored in a fast, complete, and
secure manner.
t
Implementa The Device Maintenance tab page on the LMT provides users with a
graphical user interface (GUI), on which the OMU data is backed up and
tion
restored.
Related
Operation
To start the function of data backup and restore on the LMT, do as follows:
On the Device Navigation Tree tab page, right-click BSC and choose
Backup Data or Restore Data. Alternatively, on the BSC Maintenance tab
page, unfold BSC Maintenance and click Backup Data or Restore Data.
To back up data, do as follows:
On the Backup Data tab page, click Backup. Enter a file name to back up
the current data as a file with the name. Click OK. The Progress dialog box
is displayed, showing the backup progress.
If file name is left blank, the current data is backed up as a file with the default name.
None
Feature ID
None
Issue 01 (2012-04-26)
341
Description
Improvemen The bandwidth usage for PPP links and MP groups is displayed in the realtime performance monitoring window on the LMT.
t
The formulas for calculating the bandwidth-related counters about PPP
links, MP groups, and logical ports are optimized to ensure uniform and
accurate bandwidth calculation.
Implementat The bandwidth usage for PPP links and MP groups is calculated based on
the used bandwidth and displayed in a chart and numerically in the realion
time performance monitoring window on the LMT.
The header, payload, flag field, and cyclic redundancy check (CRC) field
are added to the formulas for calculating the bandwidth-related counters
about PPP links, MP groups, and logical ports.
Related
Operation
None
PR Number
None
Feature ID
None
Modified Features
1.
Issue 01 (2012-04-26)
342
Description
Improveme
nt
Implement
ation
Related
Operation
PR Number
DTS2011030100089
Feature ID
None
2.
Issue 01 (2012-04-26)
343
Description
Improvemen
t
Standby interface boards now support flow control. The details are as
follows:
1.
2.
3.
1.
2.
Implementat
ion
Flow control takes effect after a flow control threshold is set for each
controlled item. When the CPU usage of a standby interface board
reaches a flow control threshold, a flow control event (ID: 22835) is
reported stating that the interface board is under flow control. When
the CPU usage of the interface board drops below this flow control
threshold, another flow control event (ID: 22835) is reported stating
that the interface board is in the normal state.
Related
Operation
PR Number
DTS2011021604423
Feature ID
GBFD-111705
3.
Issue 01 (2012-04-26)
344
Descriptio
n
Improveme
nt
Implement
ation
The resource control item of the license for the Extended BCCH feature
is configured using MML commands. When the license is insufficient,
the parameters 2Quater Message Transmission Channel and Channel
of Sending SI13 Message cannot be set to BCCHExt.
If the SI2Quater and SI13 messages are sent on an extended BCCH in
versions earlier than V900R013C00, a new license is required or the
Extended BCCH feature must be disabled before a BSC is upgraded to
V900R013C00 or later.
Related
Operations
PR Number
N/A
Feature ID
GBFD-511403
4.
Issue 01 (2012-04-26)
345
Issue 01 (2012-04-26)
346
5.
GBFD-118704
Description Single Radio Voice Call Continuity (SRVCC) ensures that voice services are
smoothly handed over from an LTE network to a GERAN network, with the
help of VoIP service routing, control, and triggering provided by the IP
Multimedia Subsystem (IMS) and handover control provided by the Mobile
Management Entity (MME).
Unlike CSFB, SRVCC is a real LTE VoIP technique because voice services
are implemented in the LTE network. UEs access the IMS through the CS
domain in the GERAN network or through the LTE network. As a result,
continuity of voice services is ensured based on the IMS and UEs can be
handed over from the LTE network to the GERAN network.
SRVCC is applicable only to scenarios where the GERAN and LTE
networks cover the same area. In addition, SRVCC in Dual Transfer Mode
(DTM) is not supported.
Improveme Continuity of voice services is ensured when the GERAN and LTE
networks cover the same area during the evolution from GERAN to LTE.
nt
Implement In SRVCC, the source MSC (which is connected to the MME) interprets the
PS-to-CS handover as an inter-MSC PS-to-CS handover, and then sends a
ation
Prepare Handover Request message to the target MSC. The target MSC
assigns a default Service Area Identifier (SAI) as the ID of the source cell.
This SAI must be different from the one used by the UTRAN so that the
BSC can identify SRVCC handover requests.
Related
Operation
PR Number MBSCV9R13C00-OR-111
Feature ID
Issue 01 (2012-04-26)
GBFD-511309
347
6.
Descriptio
n
AMR can be used together with BSC local switch. Based on the AMR rate
sets and protocol-specified preferred rate sets of both the calling and called
parties under different BTSs, the BSC calculates a new rate adjustment
threshold. The purpose is to select the best AMR codec scheme for both
the calling and called parties under BSC local switch.
Improvem
ent
Implemen
tation
For AMR calling and called parties with the same rate type but different
rate sets, the codec rate sets are changed to the protocol-specified preferred
rate sets, respectively, through the robust AMR traffic synchronization
procedure. Then, BSC local switch is performed. If the calling party
occupies an AMR TCHF and the called party occupies an AMR TCHH, or
the other way round, the party that occupies an AMR TCHH is switched to
an AMR TCHF, and then the BSC adjusts the AMR codec rates of both
parties before BSC local switch is enabled.
Related
Operation
PR
Number
MBSCV9R13C00-OR-9
Feature ID
GBFD-117701
7.
Issue 01 (2012-04-26)
348
Descriptio
n
AMR can be used together with BTS local switch. Based on the AMR rate
sets and protocol-specified preferred rate sets of both the calling and called
parties under a BTS, the BSC calculates a new rate adjustment threshold.
The purpose is to select the best AMR codec scheme for both the calling
and called parties under BTS local switch.
Improvem
ent
Implemen
tation
For AMR calling and called parties with the same rate type but different
rate sets, the codec rate sets are changed to the protocol-specified preferred
rate sets, respectively, through the robust AMR traffic synchronization
procedure. Then, BTS local switch is performed. If the calling party
occupies an AMR TCHF and the called party occupies an AMR TCHH, or
the other way round, the party that occupies an AMR TCHH is switched to
an AMR TCHF, and then the BSC adjusts the AMR codec rates of both
parties before BTS local switch is enabled.
Related
Operation
PR
Number
MBSCV9R13C00-OR-9
Feature ID
GBFD-117702
8.
Run the SET TCPARA command with Coding Mode set to Enhanced code
mode.
PR Number MBSCV9R13C00-OR-119
Feature ID
9.
Issue 01 (2012-04-26)
GBFD-115501
349
Run the SET TCPARA command with Coding Mode set to Enhanced code
mode.
PR Number MBSCV9R13C00-OR-119
Feature ID
GBFD-115502
Run the SET TCPARA command with Coding Mode set to Enhanced
code mode.
PR Number MBSCV9R13C00-OR-119
Feature ID
GBFD-113301
Issue 01 (2012-04-26)
350
Descriptio EPLC recovers and compensates for lost speech frames. This, to a certain
extent, solves the problem of speech frame loss during transmission in a poor
n
radio environment, hence improving voice quality, network performance, and
customer satisfaction. The packet loss prediction algorithm is optimized in
BSC6900 V900R013C00 so that received voice gets closer to the original
voice in fidelity, improving user experience.
Improvem In the case of packet loss of various severity levels, the MOS can be
increased by 0.1 to 0.2.
ent
Implement If packet loss occurs in the uplink on the Um or Abis interface, the AMR
decoder that is configured with EPLC recovers AMR code streams to obtain a
ation
better voice waveform. This feature is applicable to A over TDM scenarios.
Related
Run the SET TCPARA command with EPLC Switch set to ON.
Operation
PR
Number
MBSCV9R13C00-OR-119
Feature ID GBFD-115704
Issue 01 (2012-04-26)
351
Description Based on the original SCTP Link Trace functions, the following functions
are added:
SCTP link tracing on interface boards
Improveme SCTP Link Trace functions, retained on the XPU board, are also added to
interface boards to help locate lost or erroneous packets in a faulty or
nt
congested SCTP link on the interface board.
Implement When SCTP Link Trace are started on the LMT, the OMU sends the
signaling messages to be traced to the XPU and interface board where the
ation
SCTP links are located.
After receiving the tracing command, the XPU and interface board start
tracing the messages and then send the traced data to the OMU.
The OMU parses the traced data and sends them to the LMT so that users
can view the traced data.
Related
Operation
Issue 01 (2012-04-26)
352
3. The traced data contains messages over the XPU and interface board,
which helps locate faults in the links by parsing the traced messages.
Issue 01 (2012-04-26)
353
Descriptio Users can query the detailed failure cause of a specified BTS on the LMT.
n
Improvem This function facilitates fault location, thereby reducing the OPEX.
ent
Implemen An interface is added to the LMT, on which the detailed failure cause of a
specified BTS can be queried.
tation
Related
On the BTS Maintenance tab page in the left pane of the Device Maintenance
Operation window, expand the BTS Maintenance node. Click Query Failure Cause of
Config Alarm. Query the detailed failure cause of a specified BTS on the
displayed window.
PR
Number
DTS2010102501766
Feature ID None
Issue 01 (2012-04-26)
354
GRRU
MRRU
GRFU
MRFU
BTS390
0E
RXU
Specific
ation
After
the
Upgrade
Is
Complet
e
RRU30
08_V2
RRU39
08_V2
GRFU_
V2
MRFU_
V2
BTS390
0E_V1
The RXU Specification parameter is checked and updated after the upgrade
is complete.
Related
Run the ADD BTSRXUBRD command on the LMT with RXU
Operation Specification set to an appropriate value.
PR
Number
None
Feature ID None
Issue 01 (2012-04-26)
355
Descriptio
n
Improveme The ESN of a non-IP-based BTS can be queried at the BSC when the BTS is
working normally. This improves the efficiency of transforming a TDMnt
based network to an IP-based network.
Implement The DSP BTSESNINFO command is added.
ation
Related
Operation
PR Number None
Feature ID None
Improveme If a BTS is configured with at least two E1s and OML backup is enabled,
cells are not out of service even if some of the E1s are disconnected
nt
Implement When OML backup is enabled, the TRX timeslots are evenly distributed
among all the input E1 ports on a BTS. The idle timeslots in TDM mode are
ation
evenly distributed among all the input E1 ports on the BTS.
Related
Operation
Run the following command with Configure Backup OML set to YES and
TRX Timeslot Allocate Mode to Share Among all Ports:
SET BTSOMLBACKUP: IDTYPE=BYID, BTSID=0, OMLBKUP=YES,
TRXTSALLOC=ALL_PORT;
PR Number DTS2010091402060
Feature ID None
Issue 01 (2012-04-26)
356
Run the MML command ADD/MOD ADJNODE with the adjacent node
name set to a maximum of 64 characters.
PR Number DTS2010102201736
Feature ID None
Effect
Implement
ation
Related
Operations
None
Trouble
Ticket
Number
MBSCV9R13C00-OR-79
Feature ID
GBFD-110030
Deleted Features
None
Issue 01 (2012-04-26)
357
Description
FG2d
GOUd
Modified Hardware
None.
Removed Hardware
None.
Issue 01 (2012-04-26)
358
1.
Solving the problem that the MML command RMV LICENSE is falsely contained in
command group G0
Description
Cause
Impact
Severity
Minor
Solution
PR Number
CMM: DTS2010121504124
GCRMS: 4966654
Test Case ID
2.
T13-0121
Solving the problem that the MML command RMV LOGRST is falsely contained in
command group G_2
Description
Cause
Impact
Severity
Minor
Solution
PR Number
CMM: DTS2010121504124
GCRMS: 4966654
Test Case ID
3.
Issue 01 (2012-04-26)
T13-0122
Solving the problem that the MML command SET SLFSLVSW is falsely contained in
command group G_1/G_8
359
Description
Cause
Impact
Severity
Minor
Solution
The command has been removed from command group G_1/G_8 and
added to command group G_9.
PR Number
CMM: DTS2010121504124
GCRMS: 4966654
Test Case ID
4.
T13-0123
Solving the problem that a BTS cannot ping its controlling BSC after IP paths are
removed from and then added to the BTS
Description
A BTS under the BSC cannot ping the BSC after users perform the
following operations:
1.
2.
3.
Cause
Impact
The BSC can ping the BTS but the BTS cannot ping the BSC. This
problem does not affect BSC services.
Severity
Minor
Solution
PR Number
DTS2011071400098
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC200_003
5.
Issue 01 (2012-04-26)
Solving the problem that the assignment success rate drops when the Real-time Transport
Control Protocol (RTCP) is enabled
360
Description
Cause
Impact
Severity
Major
Solution
The software has been improved so that the internal resource consumption
meets the designed specifications.
PR Number
DTS2011032500923
6.
Issue 01 (2012-04-26)
Solving the problem that some bandwidth-related performance counters may not be
accurately measured
361
Description
When the configured bandwidth and the traffic volume are both high,
bandwidth-related performance counters may not be accurately measured,
for example, the average forward bandwidth allocated to logical ports
(VS.LGCPRT.Alloced.Ave.Fwd) and the average backward bandwidth
allocated to logical ports (VS.LGCPRT.Alloced.Ave.Bwd).
Cause
The measurement period of the raw counters for this type of performance
counters is 60 minutes. If the traffic volume exceeds 18 Mbit/s, the value
of the accumulated bandwidth within 15 seconds exceeds 32 digits when
converted to a binary number. The calculation is as follows:
18 x 1024 x 1024 x (60 x 60/15) = 10E000000
The corresponding variable on the equipment allows for only 32 binary
digits. When the value of the accumulated bandwidth exceeds 32 binary
digits, it is reset to 0. As a result, the average bandwidth values cannot be
accurately calculated.
Impact
Severity
Warning
Solution
The number of binary digits in the variable on the equipment has been
increased to accommodate the digits in the value of the accumulated
bandwidth.
PR Number
DTS2011022804634
7.
Solving the problem that an alarm is not reported after the IP route for an IP path is
removed
Description
After the RMV IPRT command is run to remove the IP route for an IP
path, the IP path has no carrying port and experiences a disconnection on
the physical link. When this occurs, an alarm about an IP path fault is
supposed to be reported, but it is not reported.
Cause
Impact
Severity
Minor
Solution
The mechanism for processing IP path faults has been improved. This
ensures that an alarm is reported when an IP path fault occurs due to the
lack of carrying port configuration.
PR Number
DTS2010082002619
8.
Issue 01 (2012-04-26)
Solving the problem that the help information on the LMT does not include the
specifications for IP paths on the FG2a, GOUa, or UOIa (IP)
362
Description
Cause
The specifications for IP paths on the FG2a, GOUa, and UOIa (IP) are
missing from the help information on the LMT.
Impact
Severity
Warning
Solution
The following content has been added to the help information for the ADD
IPPATH command:
For FG2a, GOUa, and UOIa(IP) board, because of the limit of the board's
capacity, the SCTP link, NodeBIP and IPPATH numbers on one board
should obey the following rules: (the number of SCTP link + NodeBIP +
No-Qos IPPATH + 14*Qos IPPATH) <= 2048.
PR Number
DTS2011033103758
9.
Solving the problem that the alarm ALM-20715 OMU File Synchronization Failure
cannot be cleared automatically
Problem
Description
Cause
Impact
Severity
Minor
Solution
PR Number
DTS2011030401967
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_531
10. Solving the problem that the performance counter PEAK.BSC.PROC.SPEED is not
accurately measured
Issue 01 (2012-04-26)
363
Description
When the standby board in an active/standby pair provides the active port,
the value of the performance counter PEAK.BSC.PROC.SPEED is smaller
than what it should be.
Cause
In earlier versions, statistics are not collected for data received and sent by
standby boards. When the standby board in an active/standby pair provides
the active port, only traffic over the standby port provided by the active
board is reported to the service layer.
Impact
After the version is upgraded, traffic over the active port provided by the
standby board in an active/standby pair is also reported to the service
layer, and the amount of data received over this port is greater than the
amount of data sent over this port. As a result, the value of this counter
increases manifold compared to the value before the upgrade.
Severity
Minor
Solution
Measures have been taken so that statistics are collected for traffic over
ports provided by both active and standby boards.
PR Number
DTS2010082401462
11. Solving the problem that errors exist in the calculation of performance counters
measuring MTP2 bandwidth utilization efficiency
Description
Cause
The values of these counters are percentages, but decimals are reported.
Since the calculation formulas do not multiply decimal calculation results
by 100 to obtain percentages, the displayed values are one-hundredth of
what they should be.
Impact
Severity
Minor
Solution
The calculation formulas for these two performance counters have been
corrected.
PR Number
DTS2010070702110
12. Solving the problem that an RNC does not receive any response from the BSC at the
peer end after sending common measurement initiation requests
Issue 01 (2012-04-26)
364
Description
The connection between the RNC and the BSC is broken for 15 to 20
seconds due to a transmission interruption on the Iur-g interface. Then, the
BSC discards all the common measurement initiation requests from the
RNC without responding.
Cause
The value of the Anti DPC Intermittent Disconnect Timer on the Iur-g
interface is 15 seconds on the BSC side and the value of this timer on the
Iur-g interface is 20 seconds on the RNC side. This timer is
unconfigurable.
When the timer on the BSC expires and the timer on the RNC does not
expire, the BSC releases application-layer data for the Signaling
Connection Control Part (SCCP) link.
After being reconnected to the BSC, the RNC continues sending common
measurement initiation requests to the BSC over the SCCP link. After
receiving these requests, the BSC fails to interpret them because it has
released the application-layer data for the SCCP link. Then, the BSC
discards these requests without responding.
Impact
Severity
Minor
Solution
The value of the timer on the BSC side has been changed to 20 seconds.
PR Number
DTS2011042801298
13. Solving the problem that MTP2 links are disconnected and cannot be reestablished
Description
Cause
The time division multiplexing (TDM) switching chip of the EIUa, OIUa,
or POUc board in the TC subrack encounters a soft error, leading to failure
in TDM transmission.
Impact
Severity
Major
Solution
The RNC checks the TDM switching chip of the EIUa, OIUa, or POUc
board in the TC subrack when MTP2 links are disconnected. If a soft error
is found, the RNC reports an alarm and resets the board.
PR Number
DTS2011021700229
14. Solving the problem that the CPU usage of the active GOUa board reaches 100% in
heavy traffic
Issue 01 (2012-04-26)
365
Description
The CPU usage of the active GOUa board reaches 100% in heavy traffic.
Cause
Impact
Packets are lost during transmission and some cells are unavailable.
Severity
Minor
Solution
The flow control algorithm of the GOUa board has been optimized to
ensure that the traffic load on the GOUa board will not exceed the service
processing capability of the GOUa board.
PR Number
DTS2011011104459
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_029
15. Solving the problem that the XPUa or XPUb board is reset after one-way audio detection
is enabled
Description
Cause
After one-way audio detection is enabled, the OMU logs every detected
one-way audio problem. Currently, a log for the one-way audio problem
allows a maximum of 1024 bytes. The one-way audio log for a call that
occupies resources of two BM subracks in a BSC, however, may exceed
1024 bytes. If this happens, the stack memory will be damaged and
therefore the XPUa or XPUb board will be reset.
Impact
Severity
Major
Solution
The space allowed for a one-way audio log is expanded to 1536 bytes.
PR Number
DTS2011032503992
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_029
16. Solving the problem that the cell broadcast and the simple cell broadcast functions
become unavailable after XPU boards are reset
Issue 01 (2012-04-26)
366
Description
Cause
The data of the XPU boards will be reloaded after the boards are reset.
Due to a software bug, the BSC fails to reload the data for the two
functions.
Impact
Severity
Minor
Solution
The bug has been fixed so that the BSC successfully reloads the data for
the two functions.
PR Number
DTS2011032501949
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_030
17. Solving the problem that some counters related to random access are incorrectly
measured
Issue 01 (2012-04-26)
367
Description
Cause
Impact
The value of the counter Success Rate of Random Access is greater than
100%, and the values of the counters Immediate Assignment Commands
(SDCCH), Immediate Assignment Commands (TCHF), Immediate
Assignment Commands (TCHH), and Immediate Assignment
Commands (Circuit Service) are greater than the actual values.
Severity
Minor
Solution
PR Number
DTS2011021403650
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_031
18. Solving the problem that the value of the counter Success Rate of Radio Handover is
greater than 100%
Issue 01 (2012-04-26)
368
Description
In A over IP mode, there is a low probability that the value of the counter
Success Rate of Radio Handover is greater than 100%.
Cause
Impact
The value of the counter Success Rate of Radio Handover is greater than
100%.
Severity
Minor
Solution
The software bug has been fixed so that the number of unsuccessful
handovers is measured when the CN sends an A interface connection
release indication to release the call.
PR Number
DTS2010090801821
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_032
19. Solving the problem that a small number of MSs process AMR services on TCHHs in a
cell
Issue 01 (2012-04-26)
369
Description
Cause
Impact
Severity
Minor
Solution
PR Number
DTS2010090601492
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_033
20. Solving the problem that the value of the counter Call Drops on Traffic Channel is not
equal to the sum of related counter values
Description
When call drops occur because of Abis link disconnection, the value of
the counter Call Drops on Traffic Channel is not equal to the sum of the
following counters:
Cause
Due to a software bug, the counter Call Drops on Traffic Channel is not
updated with the preceding counters.
Impact
Severity
Minor
Solution
PR Number
DTS2011022304167
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_034
Issue 01 (2012-04-26)
370
21. Solving the problem that the counter Channel Conversion Requests (TCHF-TCHH) and
the other 15 counters are incremented
Description
Cause
Due to a software bug, the preceding 16 counters are updated along with
the counter Number of Available Channels During Spectrum Sharing.
Impact
Severity
Minor
Solution
The bug has been fixed so that the preceding 16 counters are not updated
along with the counter Number of Available Channels During Spectrum
Sharing.
PR Number
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_035
22. Solving the problem that the counters of call drops on SDCCHs are incorrectly measured
Description
The following counters are incorrectly measured when call drops occur
on TCHs carrying signaling data:
Cause
Impact
The values of the preceding counters increase when call drops occur on
TCHs carrying signaling data.
Severity
Minor
Solution
The bug has been fixed so that the preceding counters are correctly
measured.
PR Number
DTS2010122801862
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_036
Issue 01 (2012-04-26)
371
23. Solving the problem that the TCHH usage increases with the PDCH usage in busy hours
Description
The TCHH usage increases with the PDCH usage in busy hours.
Cause
When the TCH usage reaches the TCH traffic busy threshold specified
by TCH Traffic Busy Threshold in the SET GCELLCHMGAD
command, TCHHs are preferentially assigned to guarantee network
capacity.
The formula for calculating the TCH usage is as follows:
TCH usage = (Occupied TCHFs in busy hours + Occupied TCHHs in
busy hours/2)/(Available TCHFs + Available TCHHs/2) x 100%
The BSC assigns a fixed number of traffic channels to a cell, including
TCHFs, TCHHs, and PDCHs. According to the preceding formula, the
TCH usage increases with the PDCH usage because assigned TCHFs
may have been converted into PDCHs. As a result, the TCHH usage
increases.
Impact
Severity
Minor
Solution
PR Number
DTS2011011304140
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_037
24. Solving the problem that the MCPA algorithm is defective in channel allocation when the
power for an overloaded timeslot is higher than a specific threshold
Issue 01 (2012-04-26)
372
Description
Cause
The MCPA algorithm is defective and does not consider whether the
power for an overloaded timeslot is higher than the threshold.
Impact
Severity
Minor
Solution
PR Number
DTS2011031804435
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_038
25. Solving the problem that the handover algorithm leads to ping-pong handovers and the
power control algorithm leads to inaccurate power control
Issue 01 (2012-04-26)
373
Description
Cause
In this scenario, an MS hops onto the BCCH TRX and the TCH TRX in
different timeslots. The TCH TRX will perform power control when the
BCCH TRX operates at full power. The MS samples the signal levels on
the BCCH TRX and TCH TRX, calculates its power based on the
sampling result, and reports the calculated value to the BSC.
Currently, the BSC uses different methods for compensating for signal
level loss caused by power control and handovers.
If the CANPC parameter is set to NO, the BSC only considers the
signal level of the MS on the TCH TRX to compensate for signal level
loss caused by power control. This leads to overcompensation and an
extended step for power control. Compensation for signal level loss
caused by handovers is correct in this case.
If the CANPC parameter is set to YES, the BSC compensates less for
signal loss caused by handovers than for signal loss caused by power
control. This leads to ping-pong handovers. Compensation for signal
level loss caused by power control is correct in this case.
In other words, the compensation method for cases where CANPC is set
to NO is used when CANPC is set to YES, and the compensation
method to be used when CANPC is set to YES is used when CANPC is
set to NO.
Impact
Severity
Minor
Solution
The Power Control and Handover CMP CON Sw parameter has been
added to the SET GCELLOTHEXT command. When this parameter is
set to YES, the BSC uses the same method for compensating for signal
level loss caused by power control and handovers. An example use is as
follows:
SET GCELLOTHEXT: IDTYPE=BYID, CELLID=0,
PCHOCMPCON=YES;
Details about the BSC using the same compensation method are as
follows:
When a call is occupying the BCCH TRX:
Issue 01 (2012-04-26)
374
DTS2011012405110
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_039
26. Solving the problem that no channels are available for trunk services
Description
When trunk services are enabled over a public network, no channels are
available for trunk services in a cell if both the following conditions are
met:
The cell load is heavy.
All channels are occupied.
Cause
Impact
Trunk-service users cannot use any channels and fail to access the
network.
Severity
Minor
Solution
PR Number
DTS2011021001284
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_040
Issue 01 (2012-04-26)
375
27. Solving the problem that the values of some counters are small when full-rate speech
version 5 is used
Description
When full-rate speech version 5 is used, the following counters are not
measured:
RQI (TA = N)
Cause
Impact
Severity
Minor
Solution
PR Number
DTS2011030800077
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_041
28. Solving the problem that the TFO function is disabled when an MS is handed over again
Issue 01 (2012-04-26)
376
Description
Cause
The BSC uses an incorrect cause value for the initial handover because
this cause value does not require the setting of a TFO flag. However,
when the MS is handed over again, the BSC must determine whether to
change speech versions based on the setting of the TFO flag. As a result,
the BSC changes speech versions because the TFO flag is not set, and
the TFO function is disabled.
Impact
Severity
Minor
Solution
The BSC uses correct handover cause values to set TFO flags.
PR Number
DTS2011022601750
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_042
29. Solving the problem that the downlink path loss calculated by handover algorithm II is
small
Description
Cause
Impact
Severity
Minor
Solution
PR Number
DTS2010091902879
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_043
Issue 01 (2012-04-26)
377
Description
Cause
Impact
Severity
Minor
Solution
PR Number
DTS2011030300502
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_044
31. Solving the problem that the counter TO314: Failed Outgoing Inter-Cell Handovers in
One Location Group is measured in a non-location group cell
Description
Cause
Impact
Severity
Minor
Solution
The mechanism for measuring this counter was rectified so that correct
location group information is used during the measurement.
PR Number
DTS2011042800519
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_045
32. Solving the problem that the co-cell location group measurement objects can measure
only a maximum of six location groups
Issue 01 (2012-04-26)
378
Description
Cause
Impact
Severity
Minor
Solution
PR Number
DTS2011042800645
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_046
33. Solving the problem that the BSC does not promptly report the values of some counters
in a measurement period
Issue 01 (2012-04-26)
379
Description
The BSC does not promptly report the values of the following counters
in a measurement period:
As a result, the value of the counter HM300: Number of Bursts in HighOrder Modulation Scheme is smaller than the sum of the preceding
counter values.
Cause
There are two mechanisms available for reporting the counter values.
One mechanism operates in the following way:
When 30 counters are successfully measured, the BSC reports the values
of the 30 counters.
The other mechanism operates in the following way:
The BSC reports a certain number of counter values at an interval of 100
ms.
When the former mechanism is used, the BSC has to report the values of
some counters in the next measurement period. Due to a software bug,
the BSC does not check all TRXs and cells when the latter mechanism is
used.
Impact
Severity
Minor
Solution
The bug has been fixed so that the BSC checks all TRXs and cells when
the latter mechanism is used.
PR Number
DTS2010091403128
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_047
Issue 01 (2012-04-26)
380
34. Solving the problem that the BSC fails to initiate handovers for MSs that support only
full-rate speech version 1 when Speech Version Protocol Expand is set to YES(Yes)
Description
In A over IP mode, the BSC fails to initiate handovers for MSs that
support only full-rate speech version 1 when Speech Version Protocol
Expand in the SET AITFOTHPARA command is set to YES(Yes).
Cause
Impact
In A over IP mode, the BSC cannot initiate handovers for MSs that
support only full-rate speech version 1 when Speech Version Protocol
Expand is set to YES(Yes).
Severity
Minor
Solution
PR Number
DTS2011032502118
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_048
35. Solving the problem that the counter Mean Number of Messages in the BSC Message
Library should not have been measured when simple cell broadcast is enabled
Description
Cause
Impact
Severity
Minor
Solution
The bug has been fixed so that the counter Mean Number of Messages
in the BSC Message Library is measured only when standard cell
broadcast is enabled.
PR Number
DTS2011040602578
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_049
36. Solving the problem that the value of the counter Distance Between MS and BTS
remains 0
Issue 01 (2012-04-26)
381
Description
Cause
The BSC does not measure the maximum distance between an MS and a
BTS if measurement reports are pre-processed by the BTS.
Impact
Severity
Minor
Solution
PR Number
DTS2011030800077
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_050
37. Solving the problem that the values of RQI-related counters greatly decrease after an
upgrade
Issue 01 (2012-04-26)
382
Description
RQI (TA = N)
Cause
Impact
Severity
Minor
Solution
The bug has been fixed so that the preceding RQI-related counters are
measured correctly.
PR Number
DTS2011040702674
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_051
38. Solving the problem that requests for handing over MSs from TCHFs to TCHHs
decrease in A over IP mode
Issue 01 (2012-04-26)
383
Description
Half-rate VER 1
Half-rate VER 2
Half-rate VER 3
Called party
MSC
Called party
MSC
Requests for handing over MSs from TCHFs to TCHHs decrease, which
may result in a higher congestion rate in a congested cell.
Severity
Major
Issue 01 (2012-04-26)
384
Solution
The bug at the MSC has been fixed. The bug at the BSC has also been
fixed so that the IE Speech Version is used in the TCHF-to-TCHH
handover decision procedure.
PR Number
DTS2011040604984
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_052
39. Solving the problem that the counter Site Serving Normal Period is incorrectly measured
Description
Cause
Due to a software bug, the values of this counter are not summed.
Instead, the minimum one in these values is obtained.
Impact
Severity
Minor
Solution
PR Number
DTS2010121801998
Test Case ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_053
40. Solving the problem that two counters are incorrectly measured
Issue 01 (2012-04-26)
385
Description
Cause
Due to a software bug, the values of the two counters are not summed.
Instead, the values are averaged.
Impact
Severity
Minor
Solution
PR Number
DTS2011042104113
41. Solving the problem that counters related to Mean Bep are incorrectly measured
Description
Cause
Impact
Severity
Minor
Solution
PR Number
BB4D50809
42. Solving the problem that PTRAU performance counters are incorrectly measured
Issue 01 (2012-04-26)
386
Descriptio
n
Cause
Impact
Counter Name
RX.PACKETS
TX.PACKETS
UPLINK.DISCARD.PACKETS
DISORDER.PACKETS
Severity
Minor
Solution
PR Number
DTS2011050904261
Test Case
ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_056
43. Solving the problem that the usage of advanced coding schemes and the throughput at
the RLC layer are slightly low
Issue 01 (2012-04-26)
387
Descriptio
n
In scenarios with high signal quality over the Um interface, the BSC
does not immediately use advanced coding schemes to raise the service
data rate.
Cause
Impact
The usage of advanced coding schemes and the throughput at the RLC
layer are slightly low.
Severity
Minor
Solution
PR Number
DTS2011011001091
Test Case
ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_057
44. Solving the problem that the downlink TBF retransmission rate at the RLC layer is
slightly high
Issue 01 (2012-04-26)
388
Descriptio
n
MSs inform the BSC in the Packet Downlink Ack messages that some
data blocks are missing and the BSC repeatedly retransmits the data
blocks. As a result, the downlink TBF retransmission rate at the RLC
layer is slightly high.
Cause
Impact
The downlink TBF retransmission rate at the RLC layer is slightly high.
Severity
Minor
Solution
A mechanism has been added to check whether data blocks have been
transmitted. With this mechanism, the BSC will retransmit only the data
blocks that have not been transmitted.
PR Number
DTS2011011001091
Test Case
ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_058
45. Solving the problem that uplink TBFs fail to be released in time because uplink GPRS
data blocks use incorrect coding schemes
Description After scheduling data blocks for an uplink GPRS TBF, the BSC fails to
release the uplink TBF in time if it receives the blocks using coding schemes
other than CS1 to CS4.
Cause
The BSC considers coding schemes other than CS1 to CS4 incorrect and
discards the uplink data blocks that use these coding schemes in an uplink
GPRS TBF. The counter N3101 is not incremented by one for this TBF due
to a software defect.
Impact
Severity
Minor
Solution
PR Number DTS2011031600207
Test Case
ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_537
46. Solving the problem that the measured value of Number of Initially Configured Channels
(SDCCH) is incorrect
Issue 01 (2012-04-26)
389
Impact
Severity
Minor
Solution
PR Number DTS2011022802840
Test Case
ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_539
47. Solving the problem that Ater resources are insufficient if more than 7168 timeslots are
configured on a POUc board with a logical function type of TDM
Description In BM/TC separated mode, if a POUc board with a logical function type of
TDM is configured as the Ater interface board, the assignment success rate
decreases when more than 7168 timeslots for 16-kbit/s services are
configured on the board.
Cause
Impact
Severity
Warning
Solution
The BSC now provides a check mechanism so that the configuration fails if
more than 7168 timeslots for 16-kbit/s services over the Ater interface are
configured on a POUc board.
PR Number DTS2011060802218
Test Case
ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_540
48. Solving the problem that the ALM-21801 GSM Cell out of Service alarm is not reported
when it should have been
Issue 01 (2012-04-26)
390
Description The radio signaling link (RSL) corresponding to the BCCH carrier is faulty,
but the ALM-21801 GSM Cell out of Service alarm is not reported.
Cause
When the RSL corresponding to the BCCH carrier is faulty, the data link
layer still receives data from the service layer to minimize the impact of
intermittent disconnection on services. As a result, the RSL may be faulty
and congested. The data link layer reports only the congested state to the
service layer, which then considers the data link layer as normal and does not
report the preceding alarm.
Impact
The preceding alarm is not reported when the RSL corresponding to the
BCCH carrier is faulty.
Severity
Minor
Solution
The fault reporting mechanism of the data link layer is optimized so that the
data link layer notifies the service layer of the fault when the link is faulty
and congested.
PR Number DTS2011071304957
Test Case
ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_541
49. Solving the problem that an MS becomes muted during an intra-BSC handover
Issue 01 (2012-04-26)
391
Impact
Severity
Minor
Solution
Now, the BSC does not instruct the BTS to deactivate the SACCH that is
mapped onto the same physical channel as the original TCH after receiving
an Error Indication, Connection Failure, or Release Indication message over
the original TCH.
This solution may increase the counters Call Drops in TCH Handovers (Traffic
Channel) and Call Drop Rate on TCH per cell(including Handover) and decrease the
counter Handover Success Rate if the signal quality is poor on the Um interface.
However, the call drops caused by this solution do not affect user experience because
the calls are muted.
PR Number DTS2011011903233
Test Case
ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_542
50. Solving the problem that the counters Total Bytes of Uplink EGPRS Users LLC PDUs
and Total Bytes of Uplink GPRS Users LLC PDUs are incorrectly measured
Issue 01 (2012-04-26)
392
Description The counters Total Bytes of Uplink EGPRS Users LLC PDUs and Total
Bytes of Uplink GPRS Users LLC PDUs are incorrectly measured.
Cause
Upon receiving an uplink data block from an MS, the BSC determines
whether the MS supports EGPRS based on the MS context. If the MS
supports EGPRS, the counter Total Bytes of Uplink EGPRS Users LLC
PDUs is incremented by one. If the MS does not support EGPRS, the
counter Total Bytes of Uplink GPRS Users LLC PDUs is incremented by
one.
However, when the BSC receives the first uplink data block from an MS
supporting EGPRS, the BSC fails to determine whether the MS supports
EGPRS because the MS context has not been set up. As a result, the counter
Total Bytes of Uplink EGPRS Users LLC PDUs is mistakenly measured as
the counter Total Bytes of Uplink GPRS Users LLC PDUs.
Impact
The counters Total Bytes of Uplink GPRS Users LLC PDUs and Throughput
of Uplink GPRS Users LLC PDU are greater than actual.
The counters Total Bytes of Uplink EGPRS Users LLC PDUs and
Throughput of Uplink EGPRS Users LLC PDU are less than actual.
Severity
Minor
Solution
The BSC sets up the MS context and records the MS EGPRS capability
before receiving the first uplink data block. If the MS supports EGPRS, the
counter Total Bytes of Uplink EGPRS Users LLC PDUs is incremented by
one.
PR Number DTS2011082505713
Test Case
ID
CASE_Commercial_PR_Regression_V9R13C00SPC500_543
51. Solving the problem that the CS assignment success rate decreases
Description Some CS calls cannot obtain inter-subrack timeslots in TDM mode.
Cause
The BSC does not preferentially distribute a PS cell to the digital signal
processor (DSP) that is located in the same subrack as the Abis interface
board in the BTS serving the cell. As a result, PS services occupy too many
inter-subrack timeslots in TDM mode.
Impact
Severity
Warning
Solution
The BSC preferentially distributes a PS cell to the DSP in the same subrack
as the Abis interface board in the BTS serving the cell. In this way, CS calls
can occupy certain inter-subrack timeslots.
With this solution, cell distribution will change when a BSC is upgraded.
PR Number DTS2011053104822
Test Case
ID
Issue 01 (2012-04-26)
CASE_Commercial_PR_Regression_V9R13C00SPC500_544
393
52. Solving the problem that radio resource usage does not increase after TCH PreConversion into SDCCH Switch is turned on
Issue 01 (2012-04-26)
394
Descriptio
n
The radio resource usage does not increase after TCH Pre-Conversion
into SDCCH Switch is set to ON.
Cause
The BSC does not consider the TCHs that can be converted into SDCCHs
in the cell and therefore the collected value of Number of Initially
Configured Channels (TCH) is greater than the actual number.
Radio resource usage is calculated by using the following formula:
Radio resource usage = (K3014 + AR9311)/(CR300B + CR3002 +
CR3001) x K
Where,
K3014 : Traffic Volume on TCH
AR9311: Average Number of Occupied PDCHs
CR300B: Number of Initially Configured Channels (TCH)
CR3002: Number of Initially Configured Channels (Dynamic PDCH)
CR3001: Number of Initially Configured Channels (Static PDCH)
K varies according to the actual condition
Impact
Severity
Minor
Solution
DTS2011100902085
Test Case
CASE_Commercial_PR_Regression_V9R13C00SPC500_545
Issue 01 (2012-04-26)
395
ID
53. Solving the problem that the TFO function fails to be enabled
Descriptio The Tandem Free Operation (TFO) function fails to be enabled when the
following conditions are met:
n
1. The Time Division Multiplexing (TDM) technique is used on the A
interface.
2. Huawei BSC6900 is interconnected with devices provided by other
vendors.
3. The adaptive multirate (AMR) codec version applied to Huawei BSC6900
is FR_AMR, and the AMR codec version applied to the interconnected
devices is HR_AMR.
Cause
Impact
Severity
Minor
Solution
PR
Number
Test Case
ID
DTS2011011301963
T13-0201
54. Solving the problem that four parameters in the SET GCELLHOFITPEN command have
the same names as four parameters in the SET GCELLCHMGAD command
Issue 01 (2012-04-26)
396
Descriptio Four parameters in the SET GCELLHOFITPEN command have the same
n
names as four parameters in the SET GCELLCHMGAD command.
Cause
Adequate care was not taken to ensure that each parameter in the SET
GCELLCHMGAD command has a unique name.
Impact
BSC functions are not affected. However, the user experience is affected.
Severity
Major
Solution
PR
Number
Test Case
ID
CMM: DTS2011011800693
T13-0101
55. Solving the problem that a handover fails if an MS sends a new measurement report to
the BSC when handover attempts are still initiated to original candidate cells
Issue 01 (2012-04-26)
397
Description
Cause
Impact
Severity
Major
Solution
PR Number
DTS201008060130
Test Case ID
T13-0111
Issue 01 (2012-04-26)
398
Related Documentation
Product
Version
Documentation
Version
Website
GBSS14.0
BSC6900V900R
014C00SPC500
(For Customer)BSC6900
GSM Product
Documentation
(V900R014C00_01)
(HDX)-EN
Documentation>
Wireless>SingleRAN>
MBSC>BSC6900
GSM>V900R014C00
GBSS13.0
BSC6900V900R
013C00SPC500
(For Customer)BSC6900
GSM Product
Documentation
(V900R013C00_02)
(HDX)-EN
http://support.huawei.co
m/support/pages/kbcent
er/view/product.do?
actionFlag=detailProduc
tSimple&web_doc_id=S
E0000519720&doc_typ
e=ProductManual
Update Reason
Documentation Version
The GBSS
Troubleshooting
Guide has been
added.
Issue 01 (2012-04-26)
399
Update Reason
Documentation Version
The BSC6900
Communication
Matrix has been
added.
Update Reason
Documentation Version
The BSC6900
Communication
Matrix has been
added.
The BSC6900
GSM Spare Parts
Catalog has been
added.
Issue 01 (2012-04-26)
400
Step 2 Click Register, and follow the instructions to complete the registration process.
If your registration is successful, you will be informed of your user name and password within
two or three working days.
----End
You can also enter the product name in the Product Name text box on the home page of
http://support.huawei.com to search for documents specific to a product.
If the file name extension of a documentation package is .hdx, use HedEx Lite to view the
documents. You can obtain the software from Huawei customer service engineers.
----End
Issue 01 (2012-04-26)
401
Figure 1.1
Acronyms and
Abbreviations
A
AAL2
ABIS
ABIS Interface
ABISPC
AICP
APC
ASUBPC
ATM
B
BER
BHCA
BOOTP
Bootstrap Protocol
BCC
BIOS
BSC
BSSGP
BSSGP instance
BTS
BTSM
BTS Management
C
CBC
CCP
Issue 01 (2012-04-26)
402
CDT
CoRRM
CPLD
CRC
E
EDGE
F
FE
Fast Ethernet
FP
Frame Protocol
FR
Frame Relay
G
GBPC
GCC
GCP
GE
Gigabit Ethernet
GERAN
GPRS
GPS
GSM
GTP-U
H
HARQ
HDLC
HSDPA
HS-DSCH
HSUPA
Issue 01 (2012-04-26)
403
IDC
IGWLC
IMA
IP
Internet Protocol
IPoA
L
LAN
LAPD
LBIP
Lb Interface Processing
LMT
LRM
M
MAC
MBMS
MIMO
MOCN
MSIC
MS Instance Control
MSIP
MS Instance Process
MSP
MTLS
MTP
MTSS
N
NS
NS instance
NSEP
NS Entity Processing
P
PARC
Issue 01 (2012-04-26)
404
PBIP
Pb Interface Processing
PBLC
PB Link Control
PBPC
PCU
PDCP
PRR
PGC
Paging Control
PPP
Point-to-Point Protocol
PSLC
PS Link Control
PVC
R
RBSC
RBTS
RDLC
RESC
RGCP
RLC
RLC instance
RLCC
RRM
Q
QoS
Quality of Service
S
SAAL
SABP
SCCP
SCP
SCTP
SIGPC
SPCC
Issue 01 (2012-04-26)
405
SRAP
SRCP
SRP
T
TC
TC instance
TCC
TC resource Control
TDM
TDMC
TRAU
TRAU instance
TRX
Transceiver
U
UE
User Equipment
UMTS
UNI
User-Network Interface
UP
User Plane
V
VLAN
VoIP
Voice over IP
W
WCDMA
Issue 01 (2012-04-26)
406