Impact Documentation For BSC

Impact Documentation for
BSC
Version Number:
[UR14 iBSCV6.50.310r]
Impact Documentation for BSC

Version Date Drafted by Reviewed by Remarks
V1.0 2016-12-30 Lu Jingming
2017 ZTE Corporation. All rights reserved.

2017 ZTE Corporation. All rights reserved.
ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed
or used without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document is
subjected to changer writt
All Rights reserved, No Spreading abroad without Permission of ZTE 2

5.3.16 ZMF02-11-012 G/L Dynamic Bandwidth Expansion ............................................46

5.3.17 ZGO-01-01-005 Call Re-establishment ...............................................................47
5.3.18 ZGO-01-01-004 Adaptive Multirate Wideband (AMR-WB) Speech
Encoding.............................................................................................................49
5.3.19 ZGO-05-03-002 IEEE1588 V2 IP Clock Synchronization ....................................50
5.4 Other Change Descriptions .................................................................................51
5.4.1 PCU Adjustment Return Failure If Not Being Executed .......................................51
5.4.2 Neighbor Cell Configuration Missing Found ................................

6.2.12 [Overseas Site] Frequent Reset of the CRP Board After the Half-rate
Dual-threshold Function Is Enabled in Pakistan ..................................................75
6.2.13 [Overseas Site] [Belarus] OMCB Site Link Disconnection After
Active/Standby OMP Board Switchover ..............................................................75
6.2.14 [Overseas Site] [Pakistan Mobilink] Failure of 2G MOCN Handover to
3G MOCN ...........................................................................................................76
6.2.15 [Overseas Site] [Pakistan Mobilink] PS Traffic Retaining 0 Because
Write Lock Is Disabled for r_rrmtrx Writing ..........................................................77
6.2.16 [Overseas Site] Rollback of Modified Codes on EC Sites in Ukraine ...................77
6.2.17 [Overseas Site] Service Access Failure After TDMA V4BSC Is
Provisioned in China Unicom in Shaanxi ............................................................79
7 Remaining Faults .............................................................................................79
8 Version Restrictions and Precautions ............................................................80

8.1 Version Restriction Descriptions .........................................................................80
8.2 Others.................................................................................................................80

Tables
Table 2-1 Version Information ................................................................................. 9

Table 2-

All Rights reserved, No Spreading abroad without Permission

Table 6-13 [Overseas Site] Frequent Reset of the CRP Board After the Half-rate
Dual-threshold Function Is Enabled in Pakistan ...................................................... 75
Table 6-14 [Overseas Site] [Belarus] OMCB Site Link Disconnection After
Active/Standby OMP Board Switchover................................................................... 75
Table 6-15 [Overseas Site] [Pakistan Mobilink] Failure of 2G MOCN Handover to 3G
MOCN ..................................................................................................................... 76
Table 6-16 [Overseas Site] [Pakistan Mobilink] PS Traffic Retaining 0 Because Write
Lock Is Disabled for r_rrmtrx Writing ....................................................................... 77
Table 6-17 [Overseas Site] Rollback of Modified Codes on EC Sites in Ukraine ... 77
Table 6-18 [Overseas Site] Service Access Failure After TDMA V4BSC Is
Provisioned in China Unicom in Shaanxi ................................................................. 79

Panel Board Functional Board Remarks

1b
UMP1c Universal Management Process board

OMM/ OMP
1c
Universal Management Process board

UMP1d OMP
1d
USP Universal Service Process board CRPCMP+RUP
USP1b Universal Service Process board 1b CRPCMP+RUP
USP2a Universal Service Process board 2a CRPCMP+RUP
EGBS Enhanced GE Base Switch board EGBS
EGBS2a Enhanced GE Base Switch board 2a EGSF
EGFS Enhanced GE Fabric Switch board EGFS
EXFS1a Enhanced XGE Fabric Switch board 1a EGSR
ETCB Enhanced TransCoder Board ETCB
EGPB Enhanced GE Process Board EGPB
EGPB2a Enhanced GE Process Board 2a EGPB
EGPB2c Enhanced GE Process Board 2c EGPB
EGPB2d Enhanced GE Process Board 2d EGPB
EGPB2e Enhanced GE Process Board 2e EGPB
EXGB1a Enhanced XGE Process Board 1a EGPB
EXGB1b Enhanced XGE Process Board 1b EGPB
Enhanced Digital Trunk board Ip

EDTI EDTI /EDGB
Version
Enhanced Digital Trunk board IP

EDTI2a EDTI /EDGB
version 2a
Enhanced Digital Trunk board TDM

EDTT EDAB/EDBB/EDTB
version

EDTT2a EDAB/EDBB/EDTB
version 2a
Enhanced SDH Digital Trunk board IP

ESDTI ESDTI/ESDGB
version

ESDTI2a ESDTI/ESDGB
version 2a

ESDTI2c ESDTI/ESDGB
Version 2c

ESDTT ESDAB
version

Panel Board Functional Board Remarks
Enhanced SDH Digital Trunk board

ESDTT2a ESDAB
TDM version 2a
Enhanced SDH Digital Trunk board ESDBB/ESDTB/ESD

ESDTG
GSM version QB
Enhanced SDH Digital Trunk board ESDBB/ESDTB/ESD

ESDTG2a
GSM version 2a QB
EMPR Enhanced Main Process Rear Board
EMPR1b Enhanced Main Process Rear Board 1b
2.3 Associated Version Descriptions
Table 2-3 BSC UR15 Versions Associated With BSC UR15
OMMR OMMR(R4) V12.15.30P40
RCT RCT-GUTV3.00.700c
NDS NDS V16.30.10
iCS DBEAPPV2.00.00.02
iCS PLAT V2.00.00.08
2.4 NE Version Compatibility Descriptions
Table 2-4 BSC UR15 Compatibility
BSC SDR Version BTSV3 BTSV2 iTC OMMR

Version Version Version Version
V4.12.10.15 V6.20.240p V5.96.541a V6.10.400 V12.15.40
V4.12.10.23 V6.20.281a
V4.13.10.xx
V6.50.310
4.13.15.XX
V4.14.10.xx
V4.15.10.xx

2.5 Versions Available for Upgrade
For the versions that can be upgraded to iBSCV6.50.310r, refer to the following
table.
Table 2-5 Upgrade Paths
Path Version Number
UR12 BSCV6.50.10x
UR13 BSCV6.50.20x
UR14 BSCV6.50.30x
UR15 BSCV6.50.310q
3 Descriptions of Device Capacity and

Performance Indicator Changes
The device capacity and performance indicators are not changed.
4 O&M Change Descriptions
4.1 Parameter Changes
For the parameter changes in this version, refer to the appendix.
4.2 Internal Parameter Changes (Internal Only)
For the internal parameter changes in this version, refer to the appendix.
4.3 Alarm Changes
For the alarm changes in this version, refer to the appendix.

4.4 Performance Counter Changes
For the changes in the performance counters and KPIs in this version, refer to
the appendix.
Table 4-1 Change History
Is the
Change
Relate
Change Reason Included Change
d Change
(Detailed Descriptions in Catego ID
Produc Type
Are Required) Version ry
t
Release
Notes
English descriptions on
counters C901110041 to C90111004
C901110082 and 1 to
GSM No Modified Counter
descriptions on sampling C90111008
points need to be 2
modified.
To meet the requirement

for a CSSR formula in the
office in South Africa, C90125008
counters C901250080 0 and
GSM Yes Added Counter
and C901250081 need to C90125008
be added for 1
measurement on the
SDCCH.
English names of C90250000

counters C902500001 to 1 to
C902500006 need to be C90250000
modified. 6
Counters C902740001 C90274000

and C902740002 need to 1 and
be modified for the C90274000
MOCN function. 2
The NMS does not divide

the value of the counter
C905000001 is not C90500000
GSM No Modified Counter
divided by 100 by the 1
NMS, and therefore
needs to be changed to

Relate
Change Reason
d
(Detailed Descriptions
Produc
Are Required)
t

Suppo
Requ
New Def rted
ired
or ault Relate Hardw
Feature ID Feature Name or
Enha Stat d NE are
Optio
nced us Platfor
nal
m
Fast Return from GSM Off All
ZGO-02-03-009 to WCDMA Enhan Option
OMMR
ZGO-02-03-007 Fast Return from GSM ced al
to TD-SCDMA
Inter-system carrier Disa Option

ZMF02-10-003 New LTE V3/V4
shutdown bled al
MOCN network Enhan Disa Option

ZGO-03-07-006 NA V3/V4
sharing ced bled al
Dynamic channel Enhan Disa Option

ZGB-03-02-006 NA
management ced bled al V3/V4
Voice quality Enhan Option V4

ZGO-06-01-002 NA NA
monitoring ced al
Enhanced CS channel Enhan Option V3/V4

ZGO-03-02-002 NA NA
assignment ced al
Enhan Disa Option V3/V4

ZGO-04-02-005 Dual-band shared cell NA
ced bled al
Enhanced IP Abis Enhan Disa Option Base V3/V4

ZGO-05-04-004
interface ced bled al station
Enhan Disa Option Core

ZGO-05-04-003 IP A interface V3/V4
ced bled al network
G/L dynamic Enhan Disa Option

ZMF02-11-012 iCS V3/V4
bandwidth expansion ced bled al
GSM/LTE collaborated Enhan Disa Option

ZMF02-11-011 NA V3/V4
spectrum scheduling ced bled al
Intelligent cell Enhan Disa Option

ZGO-04-04-007 NA V3/V4
shutdown ced bled al
PCU Adjustment All

Enhan Option
Return Failure If Not OMMR
ced al
being Executed
Neighbor Cell All
Enhan Option
Configuration Missing OMMR
ced al
Found
Improvement of the Enhan Option NA V3/V4

NA
BSC continuous query ced al

Suppo
Requ
New Def rted
ired
or ault Relate Hardw
Feature ID Feature Name or
Enha Stat d NE are
Optio
nced us Platfor
nal
m
and listening tool
Network priority and Option NA V3/V4

frequency priority Enhan Disa al
policy for 2G-to-3G ced bled
handover
New statistical Option NA V3/V4

functions for call al
Enhan
access and call NA
ced
establishment
duration
Abnormally released Option NA V3/V4

TBFs are counted in Enhan al
NA
the LLC throughput ced
indicator
BSC/RNC supporting Option NA

alarms of 16 dry New NA al V4
contacts
IMEI Blacklist Enhan Option V3/V4

NA NA
Exporting ced al
Changing the V3/V4

Maximum Value of the
Enhan Disa Option Base
Timer
ced bled al station
"ForbidRelHoMargin"
From 10s To 245s
Adding the Number of Option
SDCCH Assignment al
Enhan Disa
Attempts/Successful iCS V3/V4
ced bled
SDCCH Assignments
(Voice)

5.2 New Feature Descriptions
5.2.1 ZMF02-10-003 Inter-System Carrier Shutdown
Table 5-2 ZMF02-10-003 Inter-System Carrier Shutdown
According to the distribution of power consumption of equipment in the

entire mobile network, the power consumption of base station equipment
occupies 90% while that of other equipment (including CN equipment
and NM equipment) occupies less than 10%. In the current phase, most
operators build their UMTS and FDD LTE networks on the basis of the
existing GSM network. If the system supports inter-mode carrier
shutdown when the GSM, UMTS, and LTE networks have the same
coverage, the carrier shutdown function can be enabled under a greatly
increasing number of scenarios, bringing about better energy saving
results. This feature aims to achieve the following three objectives:
Feature Description
1) After receiving a load request from the peer end (UMTS network or
LTE network) within the energy saving period, the system can return the
load and capacity information about the required cell. The GSM network
can use the information as the reference for determining whether to
accept users of the peer network after it is shut down.
2) If the load of the service cell that supports inter-system energy saving
crosses the threshold, the system can notify the peer end to activate
carrier frequencies of the corresponding cell.
3) After receiving a neighbor cell status indicator from the peer end, the
system can update the record immediately.
Feature ID ZMF02-10-003
Impact on None
Equipment
Performance
Impact on Network None

Performance
Required Hardware The GSM network and the LTE network cannot share the same RRU.
Impact on Related None

NE Interfaces
License Control None

R_3GHORS. NCEnergySavingInd
R_3GHORS. NCEnergySavingState
R_LTERS. NCEnergySavingInd
R_LTERS. NCEnergySavingState
Related Parameters
R_BSCOAM. InterRATEnergySaving
R_BSCOAM. InterRATEgSavingTime
R_BSCOAM. InterRATLoadThrs
R_BSCOAM. InterRATActInd
Related Counters None.
Related Alarms and None.

Notifications
1. Verify the various methods of providing load to a different system,
including reporting the load of a single event, reporting the load of a
single cell, reporting the load of multiple events, and reporting the load of
multiple cells. The reporting modes comply with the 36.413 protocol.
Verification Method
2. Simulate the scenario of service cell congestion. When a service cell is
and Pass Criteria
congested, the system can activate another cell in a different system.
3. Set the high load threshold and simulate the scenario of high load for a
service cell. When a service cell is on a high load, the system can
activate another cell in a different system.
When the load of a service cell crosses the threshold, to activate the
power-off carrier frequencies of the cell, the system needs to first check
Impact on Other
whether the intra-system carrier frequencies of the cell are powered off. If
Features
yes, it first activates intra-system carrier frequencies and then activates
different-system carrier frequencies.
Precautions The GSM network and the LTE network cannot share the same RRU.

5.3 Feature Enhancement Descriptions
5.3.1 ZGB-02-02-001 Basic Handover
Table 5-3 ZGB-02-02-001 Basic Handover
The Indian operator requires us to fulfill the TA limitation access

feature. The details are as following:
1. TA has to be less than TA MAX when call is initiated.

2. If TA exceeds TA MAX during calling, the call should be
Feature Description dropped.
3. The emergency handover is occurred before TA exceeds TA

MAX.
4. TA has to be less than TA MAX for data service. If not, the data
service should be interrupted.
Feature ID ZGB-02-02-001
Impact on None
Equipment
Performance

Performance
Required Hardware None
Default Status Off

NE Interfaces
License Control Yes
GGsmCell. TaForceRel Force release the Call when TA exceed

TaAllowed
Related Parameters
GGsmCell. TaAllowedN TA excess release call value N
GGsmCell. TaAllowedP TA excess release call value P

C901070250 Number of SDCCH force releases due to TA

C901070251 Number of TCH/F force releases due to TA
C901070252 Number of TCH/H force releases due to TA
C910080146 Number of TCH/F force releases due to TA (VGS
talker)
C910080147 Number of TCH/F force releases due to TA (VBS
talker)
C901000120 Number of DL GPRS TBF force releases due to
TA
C901000121 Number of DL EGPRS TBF force releases due to
TA
Related Counters C901000122 Number of DL GPRS TBF establish fail due to TA
forbid
C901000123 Number of DL EGPRS TBF establish fail due to
TA forbid
C901010112 Number of UL GPRS TBF force releases due to
TA
C901010113 Number of UL EGPRS TBF force releases due to
TA
C901100112 Number of invalid access by channel request due
to TA forbid
C901200114 Number of invalid access by EGPRS channel
request due to TA forbid
Related Alarms and None

Notifications
If TA exceeds TA MAX during calling, the call should be dropped

in force.
Verification Method
If TA exceeds TaAllowed, the PS initial access is limited.
and Criteria
During PS service, if TA exceeds TaAllowed, check whether the
PS services are released in force.
Impact on Other None
Features
Note None
5.3.2 ZGO-06-01-018 Silent Call Detection
Table 5-4 ZGO-06-01-018 Silent Call Detection
Add CIC information at A/Ater interface in the silent detect

Feature Description
notification.


Performance
Required Hardware The iCS is required for co-work.
Default Status Off
Impact on Related Only the interface message with iCS is added.

NE Interfaces
iCSConfigIntfCell: Whether to support iCS configuration for

Related Parameters
interference cell
Related Counters None

Notifications
Perform on iCS to get the handover neighbor cell data, then

Verification Method generate the interference neighbor cell and send it to BSC. Check
and Criteria the BSC data by dynamic management to confirm whether the
interference neighbor cell is generated.
Features
Note None
Table 5-6 ZGO-04-03-008 Dynamic Frequency Allocation
In the CoBCCH sub-cell scenario, when DFA is enabled, 15m

granularity intelligent power on/off load is calculated by sub-cell.
Feature Description The intelligent power off is performed in terms of sub-cell. If two
sub-cells loads are going high, the sub-cell 1 takes prior to be


Notifications
1. The emergency power on/off due to 15m granularity

performance data are computed by sub-cells respectively. When
two sub-cells loads are high, the sub-cell 1 takes prior to power
Verification Method on.
and Criteria 2. The premise of BCCH power off is that all other TRXs are
powered off besides the BCCH.
3. The emergency power on is performed on the sub-cell where
the current TRXs reside in.
Features
Note None
5.3.4 ZMF02-11-012 GL Dynamic Bandwidth Extension
Table 5-7 ZMF02-11-012 GL Dynamic Bandwidth Extension
In the CoBCCH sub-cell scenario, when DBE is enabled, 15m

granularity performance data calculates the load by sharing
Feature Description sub-cell. If both the two sub-cells are in the sharing frequency
pool, the sharing becomes unavailable, The channel congestion
times only conts the TRXs in the sharing sub-cell.
Impact on None
Equipment
Performance

Performance
Default Status On

NE Interfaces
Related Parameters None

Notifications

Verification Method Pm15m load is computed by sharing sub-cell, and the congestion
and Criteria and high load times are counted by sharing sub-cell.
Features
If the DBE is enabled under CoBccH scenario, the sharing

frequency has to be on the one sub-cell. When two sub-cells
Note
frequencies are all on the sharing frequency pool, the sharing is
unavailable.
5.3.5 ZGO-04-05-00x VAMOS
Table 5-8 ZGO-04-05-00x VAMOS
Feature Description
Te obeser( t)79(he)4( )-10Vt(pa)79(i)5(r)-3(i)5(n)-9(gmb)-19(es)-3(s)-5angd sn

mPsshunnel irmVoi-5(e)-9w ofpyni-5(c)-5 deaa( )] TJETQq252.89 495.43 291
AC1: Query when there is no VAMOS pairing.

Given: RNC and BTS work normally, services are going
normally, and the call can be made successfully.
When: Query time slot observation.
Then: OMMR displays correctly.
AC2: Query when 2 FRs are paired.

Given: RNC and BTS work normally, services are going normally,
and the call can be made successfully.
AC3: Query when 2 FRs are paired and 1 HR is in idle mode.

AC4: Query when 2 HRs and 2 HRs are paired.

Verification Method and the call can be made successfully.
and Criteria When: Query time slot observation.
AC5: Query when 1 FR and 2 HRs are paired.

AC6: Query when 2 HRs are paired and 1 HR single user is

occupied.

5.3.6 ZGO-02-03-009, ZGO-02-03-007, Fast Return from GSM to

WCDMA, Fast Return from GSM to TD-SCDMA
Table 5-9 ZGO-02-03-009, ZGO-02-03-007, Fast Return from GSM to

WCDMA, Fast Return from GSM to TD-SCDMA
For Fast Return from GSM to UTRAN, the 3G frequency filling by

configuration is added. The following 2 parts have to be modified.
1. Add RelUtranStrategy parameter to define the control
method: by measurement or by configuration.
Switch values:
0: only by measurement
1: only by configuration
2: Measurement is prior.
Feature Description 2. For the above conditions, the following requirements have to
be satisfied.
(1) Only TCH channel carries 3G neighbor cell message.
(2) Only 3G frequency messages are carried, no scrambling
codes message.
(3) FDD and TDD selection uses 3G handover parameter
fddTddPrio(R_3GHOC table). If FDD is handed over first, the
FDD parameters are carried; so does TDD. If there is only one
mode, the configured parameters are used. The original
measurement based keeps unchanged.
Feature ID ZGO-02-03-009 ZGO-02-03-007
Impact on None
Equipment
Performance

Related Counters C901110113 : Times of FASTRETURN to UTRAN

Notifications
Verification Method Modify RelUtranStrategy parameter; the test keeps accordance
and Criteria with feature modification by configuration. Counter is available.
Features
Note None
5.3.7 ZGO-03-07-006 MOCN Network Sharing
Table 5-10 ZGO-03-07-006 MOCN Network Sharing
Due to the restriction of conditions, some virtual operators and small

operators can only rent equipment to operate services. This mode is
called network sharing. There are two network sharing modes:
Network sharing in independent carrier f1.48 Tm[(P)1quency mode: Different cells
belong to different operatorTms, and a mobile phone selects its cell
according to the operTmator inforTmmation stored in the SIM card. In this
sharing mode, basically the BSC and CN do not need to be modified, but
only need to configure the cor Tm[(P)1sponding data. This mode is already
Feature Description supported in previous versions.
Network sharing in shared carrier frequency mode: The same cell can be
shared by several operators. This is resource sharing of a deeper
degree, which is also called complete network sharing. In this sharing
mode, the BSC and CN need to implement related protocols and
upgrade the software. Because the CN Tmmay not support the MOCN
feature, this sharing mode is greatly restricted. This version implements
the MOCN feature that does not rely on the CN. Here, add the principle
of the MOCN feature not relying on the CN.
Feature ID ZGO-03-07-006
Impact on None
Equipment
Performance

Performance
Impact on Related Network management parameters arTme involved.

NE Interfaces
License Control None.

Related Parameters R_BSC.CNIndepMocnSupp: MOCN feature that does not rely on the CN

Notifications
In a network where the CN side does not support the MOCN feature, the
Verification Method
BSC can assist mobile phones to implement the MOCN feature when
and Pass Criteria
they access the network.

Features
Precautions

GPsChannelSchedule.SC1PDLIMIT (DynamicTCHF to PDCH limit for

SubCell 1): upper limit for converting dynamic TCHF channels of sub-cell
1 into PDTCH channels.
GPsChannelSchedule.SC2PDLIMIT (DynamicTCHF to PDCH limit for
Related Parameters
SubCell 2): upper limit for converting dynamic TCHF channels of sub-cell
2 into PDTCH channels.
GPsChannelSchedule.PDLIMITSUP (PDTCH limit support): whether to


C901260026 Number of TCH/F allocation attempts for

assignment(speech version1)
C901260050 Number of TCH/F allocation attempts by BSC for
C901260226 Number of TCH/F voice allocation failure for
assignment
C902510001 Number of TCH/F allocation failure due to apply IPA
board failure for assignment(speech)
C902510002 Number of TCH/F allocation failure due to apply
inner-TC board failure for assignment(speech)
C902510003 Number of TCH/F pre-apply connection failure first
time for assignment(speech)
Related Counters
C902510004 Number of TCH/F pre-apply connection failure
second time for assignment(speech)
C902510005 Number of TCH/F allocation failure due to pre-apply
connection failure third time for assignment(speech)
Abis resource failure for assignment (speech version1)
C902510014 Number of TCH/F allocation failure due to apply A
resource failure for assignment (speech version1)


C901270026 Number of TCH/H allocation attempts for
assignment by BSC(speech version1)
assignment (speech version3)
assignment by BSC(speech version4)
C901270200 Number of TCH/H voice allocation failure for
assignment
C902520001 Number of TCH/H allocation failure due to apply IPA
board failure for assignment(speech)
C902520002 Number of TCH/H allocation failure due to apply
inner-TC board failure for assignment(speech)
C902520003 Number of TCH/H pre-apply connection failure first
time for assignment(speech)
C902520004 Number of TCH/H pre-apply connection failure
second time for assignment(speech)
C902520005 Number of TCH/H allocation failure due to pre-apply
connection failure third time for assignment(speech)
C902520014 Number of TCH/H allocation failure due to apply A

Notifications
During wireless re-assignment, if a pre-application or acceptance

Verification Method
fails during the second channel application, the system does not
and Pass Criteria
include it in the number of TCH assignment attempts of failures.


Features
Precautions None
5.3.10 ZGO-04-02-005 Dual-Band Shared Cell
Table 5-13 ZGO-04-02-005 Dual-Band Shared Cell
This feature includes three optimization points:

1. Independent control during handover into the COBCCH internal circle
The handover bounce-back function in the previous version is controlled
by a unified switch, which is disabled by default. The on-site office has
the requirement for independent control of the handover bounce-back
function during handover into the COBCCH internal circle. A new switch
is added only for this scenario, while the handover bounce-back function
under other scenarios is still controlled by the original switch.
2. Optimization of the handover quality in the COBCCH internal circle
According to the handover algorithm in previous versions, when a mobile
phone is in the COBCCH internal circle, if quality handover is triggered
due to poor RQ, the system actually triggers inter-cell handover. If the
neighbor cell does not meet the conditions, call drop may occur after
handover fails due to poor quality of the mobile phone. Thus, system
processing is optimized in the following way: When a mobile phone
initiates quality handover inside the COBCCH internal circle, if the
Feature Description
neighbor cell meets the conditions, the mobile phone is handed over to
the neighbor cell. If no appropriate neighbor cell is found, the system
checks whether the external circle meets the conditions (the electrical
level of the external circle must be greater than a certain threshold, and
the external circle must include a certain number of idle channels), and
hands over the mobile phone to the external circle if yes. The system
adds a switch to implement the control.
3. Punishment for frequent handover between internal and external
circles
In on-site offices, sometimes there is frequent continuous handover
between internal and external circles, so a punishment mechanism
needs to be added to forbid handover between internal and external
circles during a period. The on-site office also has the requirement of
controlling mobile phones in the external circle or internal circle. A switch
is added to control whether a mobile phone resides in the external circle
or internal circle within the punishment period after frequent handover.

Impact on None
Equipment
Performance

Performance

NE Interfaces
R_BCELL. HoInSC2HoBack CoBCCH Inner Circle Handover Back

Independent Control
R_HOC2. CobQualHoOpt Optimization switch for COBCCH quality
handover
R_HOC2. CobQualHoOptMargin MIN threshold of signal level for
Related Parameters
COBCCH quality handover Optimization
R_HOC2. SubcellPingPangCtrl Control number for continual subcell
pingpang handover
R_HOC2. PingPangCampSubcell Camp Subcell after continual subcell
pingpang handover

Notifications

1. Independent control during handover into the COBCCH internal circle

1) When a mobile phone initiates an inter-cell handover to sub-cell 2 on
the CoBCCH, if the new R_BCELL.HoInSC2HoBack parameter is set to
1, the channel activation message of the target cell carries the handover
bounce-back parameter (the parameter is sent correctly), and the system
does not care whether the mobile phone is bounced back.
the CoBCCH, if the new R_BCELL.HoInSC2HoBack parameter is set to
2, the channel activation message of the target cell does not carry the
handover bounce-back parameter.
Verification Method
and Pass Criteria
the CoBCCH, if the R_BCELL.HoInSC2HoBack parameter is set to 0,
the original handover bounce-back switch is used.
4) For other cells not within the CoBCCH internal circle, the original
handover bounce-back switch is used.
2. Optimization of the handover quality in the COBCCH internal circle
When the call initiated by a mobile phone is inside the internal circle of a
CoBCCH cell, if no appropriate neighbor cell is found (do not configure
neighbor cells during the test) during quality handover triggered by
uplink/downlink BERs, the system can initiate handover to the external
circle.
If SubCell2MeasureBcch is disabled, the mobile phone cannot be

handed over to the external circle.
If inter-cell handover is not triggered due to quality handover, the mobile
phone cannot be handed over to the external circle.
If the electrical level of the external circle does not meet the conditions,
the mobile phone cannot be handed over to the external circle.
If the external circle does not have sufficient channels, the mobile phone
cannot be handed over to the external circle.
3. Punishment for frequent handover between internal and external
circles
Simulate the symptom of frequent handover between the internal and
external CoBCCH circles. Check whether the new switches can perform
their functions correctly.

Features
Precautions None

5.3.11 ZGO-05-04-004 Enhanced IP Abis Interface
Table 5-14 ZGO-05-04-004 Enhanced IP Abis Interface
In IP Abis networking mode, there are independent switches for UDP

multiplexing and de-multiplexing at the BSC side and the base station
side respectively. The switches must be set consistent between the two
sides. Otherwise, the problem of one-way voice calls occurs. The
optimized solution is as follows:
The UDP packet multiplexing flow at the Abis interface between the BSC
side and base station side is controlled through a switch. The
de-multiplexing flow of multiplexed UDP packets is self-adaptable. Even
if the UDP multiplexing configuration is different between the BSC side
and the base station side, uplink and downlink packets at the Abis
interface can be processed properly.
1. Processing of downlink packets at the Abis interface:
Feature Description
The multiplexing flow at the BSC side keeps the current mode, that is,
the multiplexing function is controlled through a switch. The BTS
automatically checks whether an Abis downlink packet is a multiplexed
packet, and automatically de-multiplexes it if yes.
2. Processing of uplink packets at the Abis interface:
The current mode of the UDP multiplexing flow at the BTS side is kept,
that is, the multiplexing flow of UDP packets is controlled through a
switch. The BTS automatically checks whether a packet is a multiplexed
packet, and automatically de-multiplexes it if yes.
The UDP multiplexing flow at the Abis interface is controlled through a
switch, and the de-multiplexing flow is self-adaptable between the front
end and the back end.
Impact on None
Equipment
Performance

Performance

NE Interfaces

R_NeInfo.DeMuxUdpSwitch (UDP/RTP MUX de-multiplexing switch):

the default value is modified to 1.
Related Parameters
By default, the de-multiplexing switch is enabled. The upgrade script sets
this field to 1 by force.

Notifications
1) Test the UDP multiplexing switches of the BSC and the BTS. Whether
or not the UDP multiplexing configuration is consistent between the two
Verification Method sides, the Abis interface can process packets normally and services are
and Pass Criteria not affected.
2) After version upgrade at the BSC side, the UDP de-multiplexing switch
of the BSC must be enabled by default.

Features
Precautions None
5.3.12 ZGO-05-04-003 IP A Interface
Table 5-15 ZGO-05-04-003 IP A Interface
The IPA handover inquiry function has been implemented in the protocol.
On previous BSC versions of ZTE, the implementation of the IPA
Feature Description
handover inquiry function is not complete. This function provides the
complete implementation of this function according to the protocol.

C902800001 Number of Internal Handover Enquiry

C902800002 Number of Internal Handover Enquiry Reject due to
data service adjustment unsupported
A interface type unsupported
code type unsupported
Related Counters C902800005 Number of Internal Handover Enquiry Reject due to
no radio channel
other reason
C902800008 Number of intra cell handover due to Internal
Handover Enquiry
C902800009 Number of intra cell handover success due to
Internal Handover Enquiry

Notifications
Enable the IPA handover inquiry function at the CN side.
Verification Method Initiate a service under the BSC. Perform one handover for the calling
and Pass Criteria party through the new IPA handover flow. At this time, for the called party,
the CN triggers the IPA handover inquiry flow.

Features
Precautions None

5.3.13 ZMF02-11-012 GSM/LTE Dynamic Bandwidth Expansion
Table 5-16 ZMF02-11-012 GSM/LTE Dynamic Bandwidth Expansion

(Cross-BSC DBE)
In the DBE function on previous versions, one sharing area only includes
cells under one BSC. However, because the management scope of one
BSC is small, the application of the DBE function is restricted. Through
this enhancement, one sharing area in the DBE function can cross
several BSCs. At present, the system supports four BSCs.
Only the iCS mode supports the cross-BSC scenario in the sharing area,
and the CSON mode keeps the previous support for non-cross-BSC
scenario in the sharing area. On the new version, the check for spectrum
sharing and recycling is performed on the iCS, which is still compatible
with the previous BSC determination mode on previous versions. Under
the scenario of cross-BSC in the sharing area, on the iCS, the
determination threshold needs to be configured by the sharing area. In
addition, the BSCs related to this sharing area also need to be
configured for the system to determine whether data is collected
completely. For a sharing area that is restricted to one BSC, the sharing
area does not need to be configured on the iCS. Instead, the system
uses the determination threshold of the BSC, so that user experience is
Feature Description consistent in the non-cross-BSC sharing area.
The BSC does not know whether the sharing area crosses BSCs, so it
always sends related parameters to the iCS. If the iCS determines that it
is a cross-BSC scenario, it checks the determination threshold
configured on the iCS. Otherwise, the iCS uses the determination
threshold sent by the BSC. The ID of the sharing area must be globally
unique, so that multiple BSCs can be associated. To determine spectrum
sharing and recycling, some previous parameters of the BSC still need to
be configured on the iCS, and some parameters are still configured on
BSCs but must be consistent between BSCs. The following parameters
involving the configuration mode need to be changed or are required:
GL spectrum sharing area ID: ID of the sharing area. It must be unique
and the same for all BSCs.
Time bitmap for GL spectrum sharing (Sunday): uses the configuration
on the iCS if the sharing area crosses BSCs.
Time bitmap for GL spectrum sharing (Monday): uses the configuration

Time bitmap for GL spectrum sharing (Tuesday): uses the configuration

Time bitmap for GL spectrum sharing (Wednesday): uses the
configuration on the iCS if the sharing area crosses BSCs.
Time bitmap for GL spectrum sharing (Thursday): uses the configuration
Time bitmap for GL spectrum sharing (Friday): uses the configuration on
the iCS if the sharing area crosses BSCs.
Time bitmap for GL spectrum sharing (Saturday): uses the configuration
Number of cells whose load can be higher than the threshold: This
parameter needs to be configured on the iCS if the sharing area crosses
BSCs.
Whether to support GL spectrum sharing: This parameter is still
configured on BSCs and must be consistent between BSCs.
Number of cells with high loads during emergency spectrum recycling:
This parameter needs to be configured on the iCS if the sharing area
crosses BSCs.
Number of cells with high loads during frequency point recycling: This
parameter needs to be configured on the iCS if the sharing area crosses
BSCs.
EARFCN of the EUTRAN downlink central frequency point: This
parameter is configured on the BSC and must be consistent between
BSCs.
EUTARN downlink bandwidth: This parameter is configured on BSCs
and must be consistent between BSCs.
Maximum EUTARN downlink bandwidth: This parameter is configured
on the BSC and must be consistent between BSCs.
Negative bandwidth of 5M: This parameter is configured on BSCs and
must be consistent between BSCs.
E-UTRAN FDD cell DN: This parameter is configured on BSCs and
combined on the iCS.

Interval of GL spectrum sharing: This parameter is configured on the iCS

if the sharing area crosses BSCs.
Service flow:
(1) Sharing/recycling triggered by performance measurement
After the BSC gets the counter every 15 minutes, it calculates the load
and reports the result (including the number of cells that need to be
recycled, meet or fail to meet the sharing conditions in each phase) to the
iCS. After the iCS summaries and checks the data, if the
sharing/recycling status needs to be change, the iCS notifies each BSC.
Each BSC transfers the corresponding services, and reports to the iCS
after service transfer is finished. The iCS then notifies each eNodeB to
share/recycle spectrums.
The sharing/recycling determination mode is the same as that of the BSC
on previous versions. In case of spectrum sharing, the system checks
whether the number of cells failing to meet the sharing conditions is less
than the threshold. In case of spectrum recycling, the system checks
whether the number of cells to be recycled is greater than the threshold.
Because the iCS determines spectrum sharing/recycling only after data
reported by all BSCs is collected, the clocks of BSCs must be consistent.
To achieve this purpose, the BSCs can be connected to the clock source
through the NTP.
(2) Recycling triggered by emergency load increase
The iCS collects emergency recycling requirements from each BSC and
determines whether to recycle the sharing area. If a sharing area needs
to be recycled, the iCS first notifies each BSC and then notifies the
corresponding eNodeB.
(3) Recycling triggered by configuration modifications
In case of spectrum resource recycling triggered by configuration
modifications, the BSC initially notifies the iCS, and the iCS notifies other
BSCs and eNodeBs.
Impact on On the OMP, DBE-related processing is a little more complicated than

Equipment that on previous versions, and the CPU load will be slightly increased.
Performance
Impact on Network The impact of the DBE function upon network performance is not
Performance changed as compared with previous versions.
Required Hardware The iCS must be configured to support this feature.
Impact on Related The number of messages between the BSC and the iCS is increased.
NE Interfaces The number of messages with other NEs is not changed.
There is no separate license for the cross-BSC DBE function. The

License Control
license control mode of the DBE function is not changed.


Notifications
On the iCS, configure one sharing area to include cells under multiple
BSCs. On BSCs, perform the same configuration.
If the load of GSM cells in the sharing area is low, meeting the sharing
condition, the system shares spectrum resources to the LTE network.
The LTE network expands the bandwidth and thus increase the user
Verification Method data rate. If the load of GSM cells in the sharing area is high, the system
and Pass Criteria recycles spectrum resources and the LTE network restores the initial
bandwidth.
After spectrum resources are shared to the LTE network, if the outburst
service traffic of GSM cells increases, meeting the recycling condition,
the system recycles spectrum resources and the LTE network restores
the initial bandwidth.

Features
Precautions None

Table 5-17 ZMF02-11-012 GSM/LTE Dynamic Bandwidth Expansion (DBE

Optimization)
Based on the application of the DBE feature in the live network, the
following points are summarized for improvement and optimization:
1. Intra-cell handover triggered at the moment of DBE sharing is not
affected by the existing global intra-cell handover switch, but is
controlled by a DBE intra-cell handover switch.
2. The PS service reassignment flow triggered at the moment of DBE
sharing is not the existing global reassignment flow, but uses a
separate DBE reassignment switch.
3. During load calculation in case of spectrum sharing, recycling, and
emergency recycling of the DBE function, a switch is added to
Feature Description
control whether the load is calculated by an entire cell or by
sub-cells.
4. According to on-test tests, at the moment of spectrum sharing of the
DBE function, a few number of calls always drops. In order not to
affect the call loss indicator, at the moment of spectrum sharing, two
service handovers are triggered.
5. For key information that cannot be shared or must be recycled due
to performance or emergency reasons, syslog is output for users to
locate problems and immediately adjust the threshold in these
situations.
Impact on None
Equipment
Performance

Performance

NE Interfaces
R_BTSSHRAREA. DbeSubCellLoad
Related Parameters R_PSBTSALLOC. SupPdchDbeDelayRel
R_BSCHOC. HoIntraEnableDBE
Related Counters None.
Related Alarms and None.

Notifications

1. Intra-cell handover triggered by the DEB function is controlled only

by the HoIntraEnableDBE parameter.
2. PS reassignment triggered by the DBE function is controlled only by
the SupPdchDbeDelayRel parameter.
3. During spectrum sharing, recycling, and emergency recycling of the
DBE function, the load is calculated according to the
DbeSubCellLoad parameter. If DbeSubCellLoad is set to by an
Verification Method entire cell, the system calculates the load of the entire cell. If
and Pass Criteria DbeSubCellLoad is set to by sub-cells, the system only calculates
the load of the shared sub-cells.
4. During spectrum sharing of the DBE function, after two service
handovers are added, theoretically no call drop should occur.
However, it is still related to the duration of the service timer on the
released carrier frequency after DBE sharing.
5. Important information related to spectrum sharing of the DBE
function should all be recorded in syslog.

Features
Precautions None
5.3.14 ZMF02-11-011 GSM/LTE Collaborated Spectrum Scheduling
Table 5-18 ZMF02-11-011 GSM/LTE Collaborated Spectrum Scheduling
When the CSS feature is enabled, to improve the anti-interference

capability of the GSM network against the LTE network and increase the
handover success ratio, the handover algorithm is optimized. That is,
after the CSS feature is enabled, if the interference of the LTE network to
Feature Description the GSM network is too high to affect the handover success ratio, this
feature is enabled. Then, during handover of the quality type or electrical
level type, the load and layers of the target are no longer considered, so
that a terminal can hand over to a cell with the best electrical level and
quality.
Impact on None
Equipment
Performance

Performance


NE Interfaces
Related Parameters R_HOC. AllLayerSelected

Notifications

License Control No
Related Parameters Non5(o)e
Related Counters C905(o)1080114 (cell inte5(o)rruption time due to5(o) inte5(o)lligent cell shutdown)
Related Alarms and Non5(o)e

Notification5(o)s
The C905(o)1080114 counter can tru5(o)ly reflect the cell interru5(4(p)-3(t)11(i)-4(o)-3
Verification5(o) Method
and Pass Criteria
- lad

In this function, a new IE is added to an existing message, and no

new message is added.
Reporting the configured maximum sharing level
In the configuration message BSC DBE CONFIG V2, an IE for the
maximum sharing level is added to report the configured
maximum sharing level. When the configuration message is sent,
the information about the maximum level should be visible in the
trace file and the level reported should be accurate. When the
configuration is modified to change the level, the level reported to
the iCS should also be changed accordingly.
Reporting information about performance sharing and recovered
cells that fail to meet load requirements
Verification Method When 15-minute performance triggers sharing or recovery, the
and Pass Criteria calculated CGI and load of cells that fail to meet load
requirements need to be reported in the "Cells can not share or
need recovery" IE of the BSC SHARE AREA REPORT message.
A maximum of 10 cells can be reported for each level. The high
load information displayed in the trace file on the iCS side must
be the same as that reported by the BSC.
Reporting information on cells that fail to meet load requirements
and cause emergency recovery
The CGI and load information of high-load cells that need
emergency recovery are reported in a new "Cells need
emergency recovery" IE in the ICS FREQSHARE INFO message.
Likewise, The information displayed in the trace file on the iCS
side must be the same as that reported by the BSC.

Features
Precautions None
5.3.17 ZGO-01-01-005 Call Re-establishment
Table 5-21 ZGO-01-01-005 Call Re-establishment
During call re-establishment, no assignment related counters are

available for observing the call re-establishment. To meet the
Feature Description requirements, two counters are added: Number of assignment
attempts (call re-establishment) and Number of successful
assignments (call re-establishment).
Feature ID

Impact on None
Equipment
Performance

Performance

NE Interfaces

1. C901050096: Number of assignment attempts (call
re-establishment)
Related Counters
2. C901050097: Number of successful assignments (call
re-establishment)
Notifications
1. Create a call re-establishment procedure, and enable the
re-establishment to succeed. Ensure that the values of new
counters Number of assignment attempts (call
re-establishment) and Number of successful assignments
Verification Method (call re-establishment) increase by 1 respectively.
and Pass Criteria 2. Create a call re-establishment procedure, and enable the
re-establishment to fail (enable the old channel to return
assignment failure or enable the T3107 to expire). Ensure
that the value of the new counter Number of assignment
attempts (call re-establishment) increases by 1.
Features
Precautions None

5.3.18 ZGO-01-01-004 Adaptive Multirate Wideband (AMR-WB)

Speech Encoding
Table 5-22 ZGO-01-01-004 AMR-

When both the MSC and the terminal support OFR or OHR
speeches, perform the following verification steps:
1. Verify that messages including the "Codec List (BSS
Supported)" IE do not include OFR or OHR speeches. The
messages are COMPLETE LAYER 3 INFORMATION,
ASSIGNMENT COMPLETE, ASSIGNMENT FAILURE,
HANDOVER REQUEST ACKNOWLEDGE, HANDOVER
COMPLETE, HANDOVER FAILURE, HANDOVER
Verification Method
PERFORMED, VGCS/VBS ASSIGNMENT FAILURE, and
and Pass Criteria
INTERNAL HANDOVER REQUIRED.
2. Verify that "Speech Codec (Chosen)" is not OFR or OHR
in the following A-interface messages: ASSIGNMENT
COMPLETE, HANDOVER REQUEST ACKNOWLEDGE,
HANDOVER COMPLETE, HANDOVER PERFORMED, and
VGCS/VBS ASSIGNMENT RESULT.
3. Verify that OFR and OHR speeches in setup and call
confirm messages of the terminal are recorded in the CDTs.

Features
Precautions None
5.3.19 ZGO-05-03-002 IEEE1588 V2 IP Clock Synchronization
Table 5-23 ZGO-05-03-002 IEEE1588 V2 IP Clock Synchronization
Feature Description Add the alarm report concerning abnormal 1588 clock abnormal
Feature ID None
Impact on None
Equipment
Performance

Performance

NE Interfaces
License Control No

Related Alarms and Alarm Code: 199005804

Notifications Alarm Name: PTP 1588 synchronization lock-lose
Verification Method Verificated maximum value is 245s.

and Pass Criteria

Features
Precautions None
5.4 Other Change Descriptions
5.4.1 PCU Adjustment Return Failure If Not Being Executed
Table 5-24 PCU Adjustment Return Failure If Not Being Executed
An error code 0x47 is added in the cell load adjustment of global

Feature Description PCU resources and operators cell load balance adjustment (the
dynamic adjustment threshold is not involved in this adjustment.).
Feature ID
Impact on None
Equipment
Performance

Performance
Default Status
Impact on Related Modify BSC OMMR dynamic data management interface.
NE Interfaces
Related Parameters r_bscground.PCUDynAdjThs

Notifications

AC1: PCUDynAdjThs is set to the max value, and the global PCU
resources cell load is adjusted.
Given: BSC and BTS work normally. RUP board and PS cells are
configured; multiple cells are bound to different slave.
PCUDynAdjThs is set to the max value.
When: The global PCU resources cell load adjustment is
performed at background.
Then: EMS displays Dynamic adjustment threshold being not
involved in the adjustment.
AC2: PCUDynAdjThs is set to the min value, and the global PCU
resources cell load is adjusted.
GivenBSC and BTS work normally. RUP board and PS cells are
PCUDynAdjThs is set to the min value.
When: The global PCU resources cell load adjustment is
performed at background.
Then: EMS displays the success.
Verification Method
and Criteria
AC3: PCUDynAdjThs is set to the max value, and the operator
cell load balance is adjusted.
PCUDynAdjThs is set to the max value.
When: The operator cell load balance adjustment is performed at
background.
Then: EMS displays Dynamic adjustment threshold being not
involved in the adjustment.
AC3: PCUDynAdjThs is set to the min value, and the operator cell
load balance is adjusted.
PCUDynAdjThs is set to the min value.
When: The operator cell load balance adjustment is performed at
background.
Then: EMS displays the success
Features

1. It doesnt make sense to perform PCU dynamic adjustment

when there is no cell or only one cell in each slave.
2. The operator cell load balance adjustment is applied when
slave belongs to the dedicated operator.
3. During balancing the PCU cell dynamically, when the rate of
two SLAVE/DSP load error reaches PCUDynAdjThs threshold,
the cell is adjusted to achieve the load balance.
Note The load error rate is calculated as follows:
(KeyMax-KeyMin)*200/(KeyMax+KeyMin)
e s k y es. Ce k y e st et t

Features
Note None
5.4.3 Improvement of the BSC Continuous Query and Listening

Tool
Table 5-26 Improvement of the BSC Continuous Query and Listening Tool
1. As for the continuous query function in the dynamic data management
module, it can be performed by TS, IMSI, and IMEI on previous versions.
In this version, this function is enhanced to support continuous query by
ISDN number, A-interface circuit, A-interface IP+UDP port, and TMSI.
2. The continuous query function outputs the IPUDP ports assigned to
RUP/DRTB/AIPB boards, and the IPUDP port of the peer end (the MSC
Feature Description
or the base station).
3. Previously the listening tool only supported querying and listening for
connection relationships by IMSI and ISDN. In this version, it is
enhanced to support querying and listening for connection relationships
through the wireless TS, TMSI, A-interface circuits, and A-interface IP
UDP ports.
Feature ID None
Impact on None
Equipment
Performance

Performance

NE Interfaces

Notifications
Verification Method Make queries on the NMS or by using the listening tool.
and Pass Criteria

Features

All Rights reserved, No Spreading abroad without Permission of ZTE


1. Enable the FDD network preferential policy and configure the

MCC/MNC of the preferential network. On a mobile phone, initiate
handover to the FDD network due to various reasons. Check whether the
network preferential policy functions properly.
Verification Method
2. Enable the frequency band preferential policy and set the preferential
and Pass Criteria
frequency band, RSCP offset/EcNo offset of the preferential frequency
band. On a mobile phone, initiate handover to the FDD network due to
various reasons. Check whether the frequency band policy functions
properly.

Features
This policy is not available for handover from the GSM network to the
Precautions
TD-SCDMA network.
5.4.5 New Statistical Function for Call Access and Call

Establishment Duration
Table 5-28 New Statistical Function for the Call Access Duration and Call
Establishment Duration
For intuitive statistics of the call establishment duration, two counters are
added: average call establishment duration and average call access
duration. These two counters support statistics by BSC and by cell.
The call establishment duration refers to the duration from the time when
Feature Description the BSC receives the CHANNEL REQUIRED message to the time when
the BSC receives the first uplink or downlink ALERTING message.
The call access duration refers to the duration from the time when the
BSC receives the CHANNEL REQUIRED message to the time when the
BSC detects the ASSIGNMENT COMPLETE message.
Feature ID None
Impact on None
Equipment
Performance

Performance

NE Interfaces
License Control No

C901110127 Average time of call setup

C901110128 Average time of call setup counted
Related Counters
C901110129 Average time of call access
C901110130 Average time of call access counted

Notifications
1. Trigger the MS calling flow of normal assignment. The counter has
statistics.
2. Trigger the MS calling flow of redirection attempt. The counter has
statistics.
3. Trigger the MS calling flow of mode modification. The counter has
statistics.
Verification Method
4. Trigger the MS called flow of normal assignment. The counter has
and Pass Criteria
statistics.
5. Trigger the MS called flow of redirection attempt. The counter has
statistics.
6. Trigger the MS called flow of mode modification. The counter has
statistics.
7. Trigger the location update flow. The counter has no statistics.

Features
If internal redirection attempt is performed during the call process, the
Precautions call established duration is counted based on the new cell, while the call
access duration is counted based on the original cell.

5.4.6 Abnormally Released TBFs Are Counted in the LLC

Throughput Indicator
Table 5-29 Abnormally Released TBFs Are Counted in the LLC Throughput
Indicator
Both C901020076 (total throughput of downlink EGPRS) and

C901020043 (total number of bytes in LLC frames carried by EGPRS
downlink TBFs) only collect the statistics of data transmitted by normally
released TBFs, but does not include the statistics of data transmitted by
TBFs that are abnormally released before entering the delay status. The
current statistical mode cannot fully reflect the total data volume,
Feature Description
because the abnormally released TBFs also transmit a large amount of
data.
To make the LLC traffic reflect the real situation, the statistical points of
C901020043 and C901020076 are modified, so that the data transmitted
by TBFs that are abnormally released before entering the delay status is
also counted.
Feature ID None
Impact on None
Equipment
Performance
Impact on Network The statistical values of C901020076 and C901020043 will increase after
Performance version upgrade.

NE Interfaces
License Control No
Related Parameters R_BCELL.LLCThroughputOpt
Related Counters C901020076 and C901020043

Notifications
Verification Method Compare the statistical values of C901020076 and C901020043 before
and Pass Criteria and after version upgrade. The counter values increase after upgrade.

Features
Precautions None

5.4.7 BSC/RNC Supporting Alarms of 16 Dry Contacts
Table 5-30 BSC/RNC Supporting Alarms of 16 Dry Contacts
Feature Description The BSC/RNC supports alarms of 16 dry contacts.
Feature ID None
Impact on None
Equipment
Performance

Performance
Required Hardware The PDUME module is required.

NE Interfaces
Related Alarms and 199025865 access control alarm or third-party monitoring alarm.
Notifications The alarm reasons are modified.
Verification Method The PDUME module can connect to 16 dry contacts, and each dry
contact can report status alarms properly.

Features
Precautions None
5.4.8 IMEI Blacklist Exporting
Table 5-31 IMEI Blacklist Exporting
This feature enables the front end to generate a dynamic table

Feature Description r_pairfalse for the blacklist, and enables a tool provided in the
logservice to export the content of r_pairfalse into a .csv file.
Feature ID None
Impact on None
Equipment
Performance

Performance

andPsCrite

NE Interfaces
License Control No

Notifications
After related configurations are performed by referring to the

Verification Method BuiltinServer(logservice) Manual, run commands in the
and Pass Criteria logservice to export the content of r_pairfalse on all boards from
the front end.

Features
Precautions None
5.4.9 Changing the Maximum Value of the Timer

"ForbidRelHoMargin" From 10s To 245s
Table 5-32 Changing the Maximum Value of the Timer "ForbidRelHoMargin"

From 10s To 245s
This feature is to change the maximum value of the timer

Feature Description
"ForbidRelHoMargin" from 10s to 245s.
Feature ID None
Impact on None
Equipment
Performance

Performance

NE Interfaces
License Control No
GBssHandoverControl ForbidRelHo: Handover is not allowed

Related Parameters
when the service is released.

Notifications

Verification Method Verify that the maximum value of the timer is 245s.
and Pass Criteria

Features
Precautions None
5.4.10 Adding the Number of SDCCH Assignment

Attempts/Successful SDCCH Assignments (Voice)
Table 5-33 Adding the Number of SDCCH Assignment Attempts/Successful

SDCCH Assignments (Voice)
According to the office in South Africa, counters related to voice

services are required for calculating the CSSR indicator.
However, some terminals are abnormal on the sites in South
Africa. Consequently, SDCCH assignment related measurement
performed based on access reasons is extremely poor. To get rid
of the impact from the abnormal terminals, two new counters are
added:
Number of SDCCH Assignment Attempts (Voice): includes
Number of SDCCH Assignment Attempts Number of
SDCCH Assignment Attempts (LOC) (EstCause is 0xE*,
Feature Description
the number of 0xF* access attempts)
Number of Successful SDCCH Assignments (Voice):
includes Number of Successful SDCCH Assignments
Number of Successful SDCCH Assignments (LOC)
(EstCause is 0xE*, the number of 0xF* Successful access
attempts)
When the network side does not support NECI, the RA values
reported by the mobile phone are mostly 0xE* or 0xF*. To resolve
this problem, new counters do not filter out RA data when the
network side does not support NECI.
Feature ID None
Impact on There is no impact on equipment performance.
Equipment
Performance

Performance

NE Interfaces


Related Parameters r_btsresel.neci
C901250080: Number of SDCCH Assignment Attempts (Voice)
Related Counters C901250081: Number of Successful SDCCH Assignments
(Voice)

Notifications

6 Fixed Faults
6.1 Fixed Fault List
Table 6-1 Fixed Fault List
No. Symptom Impact Level Relate Rema

d Item rks
1 Answer-Seizure Ratio (ASR) in MSC CN ASR Minor None
Decreases after upgrading BSC. decreases
2 PD Channel Occupation Increases after PD channel Minor None
Upgrading BSC. occupation
excessive
3 Modify the DL Coding Error Faults Due Single path, Major None
to Different Voice Algorithms. noise and
DSP
automatic
reset
4 The Performance Counter C901130011: Sub-cell Minor None
The Sub-Cell 2Intra-Handover Attempts handover
Decrease to 0, and KPI Sub-Cell 2 to success rate
Sub-Cell 1 Handover Success Rate
Decreases by 0.63% after upgrading
BSC.
5 Problem with the TCH availability rate in After the Commo
the intelligent power-off function in RRU n
Pakistan shutdown
function was
enabled, the
TCH
availability
rate
decreased.
6 [Overseas Site] Data Remanence of PS service Modera None
Average Numbers of Users in GPRS te
and EGPS in the UR 14 in Pakistan
7 [EC Rollback] NSVC Link Disconnection PS service Modera None
Caused Due to NSVC Data Remanence te
After the Change Action 614005173482

All Rights reserved, No Spreading abroad without Permission of ZTE

Fault-Introducing V6.50.300q
Version
The IPA internal handover related message increases such as
Symptom
IPA Internal Handover Required. So the ASR in MSC decreases.
Impact The ASR in MSC decreases.
BSC MS is handed in via Iurg by RNC. If intra-BSC handover
occurs before the call is released, IPA internal handover is
Fault Analysis performed, which results in the increase of IPA internal
handover related messages such as IPA Internal Handover
Required.
BSC adds a switch r_bscrsv.reserved20.
Control the BSC MS accessed via Iurg interface.
0: Not perform the IPA internal handover
1: First time IPA internal handover
2: Perform IPA internal handover each time for every
Solution handover
0 is default setting, keeping accordance with 202fP002 version
before updrading in South Africa.
2 is selected for 300q version.
1 is suggested for on-site configuration.
External
Verification
Method

External
Check PD resources statistics, PD occupation decreases and
Verification
reusability increases.
Method
Remarks None
6.2.3 Modify the DL Coding Error Faults Due to Different Voice

Algorithms.
Table 6-4 Modify the DL Coding Error Faults Due to Different Voice
Algorithms.
Fault Bill No.
Fault Level
Fault-Introducing UR12.100a
Version
In E1A, DRTB appears detect error on DSP alarm and DSP

Symptom
resource unavailable alarm. DSP is reset irregularly.
Impact Sinle-path, murmur, noises and DSP automatic reset
When the sub-channel handover occurs on DRTB board, and
the handovers algorithm and channel types are different (one is
IP, and another is TDM). When handover occurs from IP to
TSM, TDM sub-channel is in non-activation state, DRTB board
UL should go into the IP packet receiving process. But if the
TDM sub-channels opposite end BIPB path No. is 0, the
execution will go wrong to start UL TDM packet processing.

Fault Analysis
When IP activated sub-channel sends empty packet, the
activated sub-cell DL will code by wrong algorithm, resulting in
single-path and noises.

Moreover, if the second handover occurs, that is, handover from
IP to TDM, and then from TDM to IP, the IP suc-channel coding
is set to the correct value. The PCM data can be received before
the wrong process starts, the codes are out of control because
the history data is the originally wrong algorithm, resulting in
reset.
Solution TDM UL packet receiving process is added with code protection.

External Enable the UL DTX, perform the different algorithm handover

Verification between IP and E1 sites. Besides, the BIPB board path No. is
Method ensured to be 0 (achieved by board resetting).
Remarks
6.2.4 The Performance Counter C901130011: The Sub-Cell

2Intra-Handover Attempts Decrease to 0, and KPI Sub-Cell 2
to Sub-Cell 1 Handover Success Rate Decreases by 0.63%
after upgrading BSC.
Table 6-5 The Performance Counter C901130011: The Sub-Cell

2Intra-Handover Attempts Decrease to 0, and KPI Sub-Cell 2 to Sub-Cell 1
Handover Success Rate Decreases by 0.63% after upgrading BSC.
Fault Bill No.
Fault Level Minor
Fault-Introducing V6.50.300q
Version
The Performance Counter C901130011: The Sub-Cell
2Intra-Handover Attempts Decrease to 0, and KPI Sub-Cell 2
Symptom
to Sub-Cell 1 Handover Success Rate Decreases by 0.63%
after upgrading BSC.
BSC sub-cells related statistics and sub-cell handover success
Impact
rate decrease.
By performance statistics releated code review and analysis,
there are three unreasonable handover cause for performance
statistics after upgrading.
Fault Analysis 1 RancsDbsFr2HrRutn(): Handover cause is
HO_FRTOHR_LOAD.
2 RancsCsMoveRutn(): Handover cause is byHoCause.
3 RanscDTMAssRutn(): Handover cause is CS_MOVE.
Modify the unreasonable performance statistics to ensure the
Solution
correctness.
External Check whether the sub-cell performance statistics and sub-cell
Verification handover related KPIs keep accordance with on-field
Method circumstances.
Remarks None

6.2.5

6.2.8 [Overseas Site] Data Remanence of Average Numbers of

Users in GPRS and EGPS in the UR 14 in Pakistan
Table 6-9 [Overseas Site] Data Remanence of Average Numbers of Users in

GPRS and EGPS in the UR 14 in Pakistan
Fault Bill No. 614005597428
Fault Level Moderate
Fault-Introducing UR14
Version
The statistics about the average numbers of users in GPRS and
Symptom
EGPS fail to be cleared after system upgrade.
Impact None
Currently, when a user is created on the control panel, global
variables increase by 1, and when the user is released, global
variables decrease by 1, but statistics are not cleared. This may
Analysis
cause a failure in decreasing the numbers of users by 1 in some
cases where the control panel is faulty, and cause statistics data
remanence.
Enable the ranumc to scan ranps instances when reporting
performance data, to find users in server state, and change
Solution
global variables based on the tbf type and cellsq. In addition,
enable the ranumc to clear data before each report.
External Obtain statistics about the average numbers of users in GPRS
Verification and EGPS before dawn. Verify that no abnormal statistics data
Method exists.
Remarks
6.2.9 [EC Rollback] NSVC Link Disconnection Caused Due to NSVC

Data Remanence After the Change Action 614005173482
Table 6-10 [EC Rollback] NSVC Link Disconnection Caused Due to NSVC
Data Remanence After the Change Action 614005173482
Version
NSVC alarms cannot be cleared after dynamic NSVC deletion
Symptom
and NSE re-allocation.
Impact Some DNSVCs become unavailable.

After the NSVC is deleted, an

EV_GDB_PS_IPGBDNSVC_DEL_REQ message is sent to
instruct the IPGBNsctrl module to delete NSVC history. During
the NSVC deletion processing, NSVC initialization processing
NSCtrlNSVCInit is added. Consequently, during deletion of
NSVC links, due to the addition of the NSVC link initialization,
Analysis
the recorded value in gtIPGBNSVCCFG is assigned to the index
position corresponding to the history already deleted from the
gatIPGBVcInfo data that maintains the NSVC history. The
recorded value overlaps with the history not deleted from
gatIPGBVcInfo, except that the indexes in the array are
inconsistent. Consequently, NSVC data remanence occurs.
Delete the NSVC initialization processing NSCtrlNSVCInit
Solution
during the NSVC deletion processing.
External
Verify that NSVC alarms can be cleared after dynamic NSVC
Verification
deletion and NSE re-allocation.
Method
Remarks

After the SNS DELETE and SNS CONFIG messages from the
SGSN are received, add a process of obtaining the SGSN ID
based on the NSEI and IP port information carried in the Gb
Solution interface messages. In this way, the SGSN information can be
obtained accurately, the failure in sending SNS interaction
information is prevented, and NSVC link disconnection does not
occur.
External
Verify that no NSVCs become unavailable after Gb interface
Verification
configuration data is modified.
Method
Remarks
6.2.11 [EC Rollback] SGSN Office Direction Inaccessible During

External
Verify that no NSVC links become disconnected and unavailable
Verification
after Gb interface configuration data is modified.
Method
Remarks
6.2.12 [Overseas Site] Frequent Reset of the CRP Board After the
Half-rate Dual-threshold Function Is Enabled in Pakistan
Table 6-13 [Overseas Site] Frequent Reset of the CRP Board After the
Half-rate Dual-threshold Function Is Enabled in Pakistan
Fault Level Severe
Fault-Introducing
UR15
Version
The CRP board is reset frequently after the dynamic half-rate
Symptom
dual-threshold function is enabled.
Impact The base station is disconnected and cannot access services.
In a cell where the half-rate dual-threshold function is enabled,
stack overflow and reset occur when the number of carriers in
the cell exceeds a specific value. The reason is that
Analysis
approximately 49 KB local variables are used in the 32 KB
process space. When the data is written back to the 4 KB guard
band, the system detects that the CRP board is reset.
Solution Define the type of local variables as static.
External Verify that no reset occurs when 60 carriers are configured

Verification (some may be configured virtually) under a cell where the
Method half-rate dual-threshold function is enabled.
Remarks None
6.2.13 [Overseas Site] [Belarus] OMCB Site Link Disconnection After

Active/Standby OMP Board Switchover
Table 6-14 [Overseas Site] [Belarus] OMCB Site Link Disconnection After
Active/Standby OMP Board Switchover

Version
Link disconnection occurs on the OMCB site after the
Symptom
active/standby OMP boards are switched over.
Impact OMCB links become abnormal.
When services are switched from the standby OMP board to the
active OMP board, the MCSAPP_TRANS process has not been
Analysis switched from the standby OMP board to the active OMP board
when socket is set up. Consequently, the setup of socket fails,
causing OMCB link disconnection.
Modify the code to enable the MCSAPP_TRANS process to set
Solution up the socket after being switched from the standby OMP board
to the active OMP board.
External
Verify that both socket and OMCB function properly after the
Verification
active/standby OMP switchover.
Method
Remarks
6.2.14 [Overseas Site] [Pakistan Mobilink] Failure of 2G MOCN

Handover to 3G MOCN
Table 6-15 [Overseas Site] [Pakistan Mobilink] Failure of 2G MOCN Handover

to 3G MOCN
Version
After the MOCN function is enabled, mobile phones in 2G
Symptom
MOCN cells cannot be handed over to 3G MOCN cells.
Mobile phones in 2G MOCN cells cannot be handed over to 3G
Impact
MOCN cells.
Whether 2G MOCN cells and 3G MOCN cells have identical
network numbers is mistakenly processed. Consequently, it is
Analysis always determined that 2G MOCN cells and 3G MOCN cells do
not have identical network numbers. Therefore, the handover
between 2G MOCN cells and 3G MOCN cells fails.
Modify the code to enable accurate determining on whether 2G
Solution MOCN cells and 3G MOCN cells have identical network
numbers.

External Configure a 2G MOCN cell and a 3G MOCN cell to have

Verification identical network numbers. Use the probe to view whether the
Method plmnbitmap field under r_d3ghocell is accurate.
Remarks
6.2.15 [Overseas Site] [Pakistan Mobilink] PS Traffic Retaining 0

Because Write Lock Is Disabled for r_rrmtrx Writing
Table 6-16 [Overseas Site] [Pakistan Mobilink] PS Traffic Retaining 0 Because

Write Lock Is Disabled for r_rrmtrx Writing
Version
The PS traffic of some cells is 0. When carriers are queried
Symptom
dynamically, BCCH carriers fail to be queried.
Impact The PS traffic of some cells is 0.
During performance data reporting, data is written to the
r_rrmtrx table with the write lock disabled. Therefore, when the
r_rrmtrx table is written with the write lock enabled during the
Analysis
service flow, the unlocked BCCH history to be written to the
table overwrites the memory, resulting in a PS channel
allocation failure.
Enable the write lock when writing data to the r_rrmtrx table
Solution
during performance data reporting.
External
Collect statistics on heavy PS traffic for a long time. Verify that
Verification
no PS traffic is 0.
Method
Remarks
6.2.16 [Overseas Site] Rollback of Modified Codes on EC Sites in

Ukraine
t3 0.

The call drop rates on uplink and downlink TBFs increase after
Symptom
upgrade.
Impact Users' Internet access experience is adversely affected.
Analysis
Fault-Introducing
UR12 and later
Version
When the TDMA V4BSC is provisioned and A-interface PCM is
blocked, according to the indicator, no block message is sent to
Symptom
the core network, and the circuit status is inconsistent between
the core network and the BSC.
The core network may assign A-interface circuits blocked by the
Impact
BSC, and then causes a service access failure.
The MSC monitor process controls the BSC to sent circuit
maintenance messages to specified office directions. However,
Analysis the MSC monitor process is not notified of the new E1A office
direction. Consequently, the BSC does not send circuit
maintenance messages to the new office direction.
After a new office direction is added, send a configuration
Solution
change message to the MSC monitor process.
External
Verification
Method

6.2.17 [Overseas Site] Service Access Failure After TDMA V4BSC Is

Provisioned in China Unicom in Shaanxi
Table 6-18 [Overseas Site] Service Access Failure After TDMA V4BSC Is
Provisioned in China Unicom in Shaanxi
Fault-Introducing
UR12 and later
Version
When the TDMA V4BSC is provisioned and A-interface PCM is
blocked, according to the indicator, no block message is sent to
Symptom
the core network, and the circuit status is inconsistent between
the core network and the BSC.
The core network may assign A-interface circuits blocked by the
Impact
BSC, and then causes a service access failure.
The MSC monitor process controls the BSC to sent circuit
maintenance messages to specified office directions. However,
Analysis the MSC monitor process is not notified of the new E1A office
direction. Consequently, the BSC does not send circuit
maintenance messages to the new office direction.
After a new office direction is added, send a configuration
Solution
change message to the MSC monitor process.
External Add an E1A office direction, and manually block the A-interface
Verification relay circuits in dynamic management. Verify that the circuit
Method status is consistent between the core network and the BSC.
Remarks None
7 Remaining Faults
None

8 Version Restrictions and

Precautions
8.1 Version Restriction Descriptions
8.2 Others
None

Impact Documentation For BSC

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Impact Documentation For BSC

Diunggah oleh

Hak Cipta:

Format Tersedia

Impact Documentation for

Impact Documentation for BSC

V1.0 2016-12-30 Lu Jingming

2017 ZTE Corporation. All rights reserved.

All Rights reserved, No Spreading abroad without Permission of ZTE 2

5.3.16 ZMF02-11-012 G/L Dynamic Bandwidth Expansion ............................................46

All Rights reserved, No Spreading abroad without Permission of ZTE 4

7 Remaining Faults .............................................................................................79

8 Version Restrictions and Precautions ............................................................80

All Rights reserved, No Spreading abroad without Permission of ZTE 5

Table 2-1 Version Information ................................................................................. 9

All Rights reserved, No Spreading abroad without Permission of ZTE 6

All Rights reserved, No Spreading abroad without Permission

All Rights reserved, No Spreading abroad without Permission of ZTE 8

Panel Board Functional Board Remarks

UMP1c Universal Management Process board

Universal Management Process board

USP Universal Service Process board CRPCMP+RUP

USP1b Universal Service Process board 1b CRPCMP+RUP

USP2a Universal Service Process board 2a CRPCMP+RUP

EGBS Enhanced GE Base Switch board EGBS

EGBS2a Enhanced GE Base Switch board 2a EGSF

EGFS Enhanced GE Fabric Switch board EGFS

EXFS1a Enhanced XGE Fabric Switch board 1a EGSR

ETCB Enhanced TransCoder Board ETCB

EGPB Enhanced GE Process Board EGPB

EGPB2a Enhanced GE Process Board 2a EGPB

EGPB2c Enhanced GE Process Board 2c EGPB

EGPB2d Enhanced GE Process Board 2d EGPB

EGPB2e Enhanced GE Process Board 2e EGPB

EXGB1a Enhanced XGE Process Board 1a EGPB

EXGB1b Enhanced XGE Process Board 1b EGPB

Enhanced Digital Trunk board Ip

Enhanced Digital Trunk board IP

Enhanced Digital Trunk board TDM

Enhanced Digital Trunk board TDM

Enhanced SDH Digital Trunk board IP

Enhanced SDH Digital Trunk board IP

Enhanced SDH Digital Trunk board IP

Enhanced Digital Trunk board TDM

All Rights reserved, No Spreading abroad without Permission of ZTE 10

Panel Board Functional Board Remarks

Enhanced SDH Digital Trunk board

Enhanced SDH Digital Trunk board ESDBB/ESDTB/ESD

Enhanced SDH Digital Trunk board ESDBB/ESDTB/ESD

EMPR Enhanced Main Process Rear Board

EMPR1b Enhanced Main Process Rear Board 1b

2.3 Associated Version Descriptions

Table 2-3 BSC UR15 Versions Associated With BSC UR15

OMMR OMMR(R4) V12.15.30P40

NDS NDS V16.30.10

2.4 NE Version Compatibility Descriptions

Table 2-4 BSC UR15 Compatibility

BSC SDR Version BTSV3 BTSV2 iTC OMMR

V4.12.10.15 V6.20.240p V5.96.541a V6.10.400 V12.15.40

All Rights reserved, No Spreading abroad without Permission of ZTE 11

2.5 Versions Available for Upgrade

Table 2-5 Upgrade Paths

Path Version Number

3 Descriptions of Device Capacity and

4 O&M Change Descriptions

4.1 Parameter Changes

For the parameter changes in this version, refer to the appendix.