bsc ur12.3 release notes 0924

GSM BSC Software Release Notes

Version: [UR12.3]


LEGAL INFORMATION

By accepting this certain document of ZTE CORPORATION you agree to the following terms. If you do not agree to the following terms, please notice that you are not allowed to use this document.

Copyright © 2023 ZTE CORPORATION. Any rights not expressly granted herein are reserved. This document contains proprietary information of ZTE CORPORATION. Any reproduction, transfer, distribution, use or disclosure of this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPORATION is prohibited.

and are registered trademarks of ZTE CORPORATION. ZTE’s company name, logo and product names referenced herein are either trademarks or registered trademarks of ZTE CORPORATION. Other product and company names mentioned herein may be trademarks or trade names of their respective owners. Without the prior written consent of ZTE CORPORATION or the third party owner thereof, anyone’s access to this document should not be construed as granting, by implication, estopped or otherwise, any license or right to use any marks appearing in the document.

The design of this product complies with requirements of environmental protection and personal security. This product shall be stored, used or discarded in accordance with product manual, relevant contract or laws and regulations in relevant country (countries).

This document is provided “as is” and “as available”. Information contained in this document is subject to continuous update without further notice due to improvement and update of ZTE CORPORATION’s products and technologies.

ZTE CORPORATION

Address:

Address: NO. 55Hi-tech Road SouthShenZhenP.R.China518057

Website:

http://dms.zte.com.cn

Email: [email protected]

ZTE Confidential Proprietary © ZTE CORPORATION. All rights reserved.


Revision History

Product Version Document Version Serial Number Reason for Revision

R1.0 First published

Author

Date Document Version Prepared by Reviewed by Approved by

2013-09-07 R1.0 Wang Wenyi

II ©2023ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary


TABLE OF CONTENTS

1 About This Document.......................................................................................1

2 Brief Description................................................................................................22.1 Release Background...........................................................................................22.2 Hardware.............................................................................................................22.2.1 Supported Hardware Changes............................................................................22.2.2 Supported Hardware Boards...............................................................................22.3 Correlated Versions.............................................................................................42.4 Compatibility with NEs.........................................................................................42.5 Supported Development Roadmap.....................................................................5

3 Device Capacity & KPI Changes......................................................................6

4 O&M Changes....................................................................................................74.1 Parameter Changes............................................................................................74.2 Internal Parameter Changes (Not open to the External).....................................74.3 Alarm Changes....................................................................................................74.4 Counter Changes................................................................................................74.5 License Control Changes....................................................................................7

5 Feature Changes...............................................................................................85.1 List of Feature Changes......................................................................................85.2 New Features....................................................................................................165.2.1 ZGO-05-03-007 Soft Synchronization...............................................................165.2.2 ZGO-06-01-018 Single-Pass Detection.............................................................205.2.3 ZGO-01-01-006 TCH Re-Assignment...............................................................215.2.4 ZGO-06-02-004 A5/4 Ciphering Algorithm........................................................245.2.5 ZGO-01-02-011Intelligent TCP Traffic Management........................................255.2.6 ZGO-03-01-004 SDCCH Congestion Control.................................................265.2.7 ZGO-03-05-010 Early TBF Establishment Downlink.........................................285.2.8 ZGO-02-02-024 Handover Command Lost Optimization..................................295.3 Enhanced Functions..........................................................................................315.3.1 ZGO-01-01-005 Call Reestablishment..............................................................315.3.2 ZGO-04-02-024 Related Dual-Band Network...................................................325.3.3 ZGO-02-02-007 Traffic Based Handover..........................................................355.3.4 ZGO-02-02-002 Dynamic Handover Priority Algorithm.....................................395.3.5 ZGO-04-02-006 TFO.........................................................................................415.3.6 ZGB-03-02-003 Dynamic Configuration of SDCCH..........................................425.3.7 ZGO-04-02-005 Co-BCCH................................................................................455.3.8 ZGB-02-02-001 Basic Handover.......................................................................485.3.9 ZGO-04-04-002 Load Dependent Intelligent TRX Shutdown............................545.3.10 ZGO-04-04-007 Intelligent Cell Shutdown........................................................575.3.11 ZGO-01-02-009 Traffic Based PDCH Expansion..............................................585.3.12 ZGO-01-03-005 Dual Transfer Mode................................................................595.3.13 ZGO-02-03-008 GSM/LTE Cell Reselection.....................................................61



5.3.14 ZGO-04-02-016 PS Power Control...................................................................625.3.15 ZGO-02-02-004 SDCCH/SDCCH Handover.....................................................645.3.16 ZGO-04-01-011 Power Boost for 8PSK............................................................655.3.17 ZGO-03-02-012 PS Channel Extension............................................................665.3.18 ZGO-04-05-003 VAMOS Pairing and De-Pairing..............................................685.3.19 ZGB-03-02-006 Dynamic Channel Management..............................................705.3.20 ZGO-04-01-007 Dynamic Power Sharing.........................................................725.3.21 ZGO-03-02-003 Enhancement on PS Channel Allocation................................745.4 Other Improvements & Optimization.................................................................765.4.1 New Counters....................................................................................................765.4.2 Changes to Performance Counters.................................................................1035.4.3 Service Performance Improved.......................................................................1155.4.4 Optimizing Configuration Parameter...............................................................1225.4.5 New and Optimized Functions for OMM.........................................................1315.4.6 New and Optimized Functions Related to BTS...............................................1335.5 Other Performance Improvement....................................................................1445.5.1 Enhanced TCH Availability..............................................................................144

IV ©2023ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary


TABLES

Table 2-1 Released Versions...................................................................................................2

Table 2-2 Supported Hardware Boards (IBSC V3)..................................................................2

Table 2-3 Supported Hardware Boards (IBSC V4)..................................................................3

Table 2-4 BSC UR12.2 Compatibility.......................................................................................4

Table 2-5 Development Roadmap............................................................................................4

Table 5-1 List of Feature Changes...........................................................................................7

Table 5-2 Soft Synchronization..............................................................................................12

Table 5-3 Single-Pass Detection............................................................................................16

Table 5-4 TCH Re-Assignment..............................................................................................17

Table 5-5 A5/4 Ciphering Algorithm.......................................................................................18

Table 5-6 Intelligent TCP Traffic Management.......................................................................19

Table 5-7 SDCCH Congestion Control..................................................................................21

Table 5-8 Early TBF Establishment Downlink........................................................................22

Table 5-9 Handover Command Lost Optimization.................................................................23

Table 5-10 Call Reestablishment...........................................................................................24

Table 5-11 Related Dual-Band Network.................................................................................25

Table 5-12 Traffic Based Handover.......................................................................................28

Table 5-13 Dynamic Handover Priority Algorithm..................................................................31

Table 5-14 TFO......................................................................................................................33

Table 5-15 Dynamic Configuration of SDCCH.......................................................................34

Table 5-16 Co-BCCH.............................................................................................................36

Table 5-17 Basic Handover...................................................................................................38

Table 5-18 Load Dependent Intelligent TRX Shutdown.........................................................44

Table 5-19 Intelligent Cell Shutdown......................................................................................46

Table 5-20 Traffic Based PDCH Expansion...........................................................................47

Table 5-21 Dual Transfer Mode..............................................................................................48

Table 5-22 GSM/LTE Cell Reselection..................................................................................49

Table 5-23 PS Power Control.................................................................................................50

Table 5-24 SDCCH/SDCCH Handover..................................................................................51

Table 5-25 Power Boost for 8PSK.........................................................................................52

Table 5-26 PS Channel Extension.........................................................................................54



Table 5-27 VAMOS Pairing and De-Pairing...........................................................................55

Table 5-28 Dynamic Channel Management...........................................................................57

Table 5-29 Dynamic Power Sharing.......................................................................................58

Table 5-30 Enhancement on PS Channel Allocation.............................................................59

Table 5-31 Separate Counters for Collecting Assignment Failure Statistics..........................60

Table 5-32 Improvement on Collection of Adjacent Cell Relation Measurement Statistics. . .62

Table 5-33 Handover Type-based Classification of Counters for Call Drops due to Handover Failures....................................................................................................................................63

Table 5-34 Optimization of Statistics Collection of Call Drops due to Handovers..................65

Table 5-35 Statistics Collection of Call Drops per Handover Causes....................................67

Table 5-36 Adding Collection of Assignment Attempt/Success/Failure Statistics for CN Secondary Assignment in iBSC...............................................................................................69

Table 5-37 Adding Statistics Collection of Releases Initiated by Users between Assignment/Handover Attempt and Assignment/Handover Implementation...........................70

Table 5-38 Adding Counter for Directed Retry.......................................................................71

Table 5-39 Counter for Statistics of Paging Message in Smaller Granularity........................72

Table 5-40 Counter for Statistics of Paging Message Overflow in Cell..................................73

Table 5-41 Counter for the Number of Dynamic SD Translation Times.................................74

Table 5-42 Collecting UL/DL RQ per RRU for Scenario of Multiple RRUs Sharing One Cell 75

Table 5-43 Adding Counters for Peaks/Averages of Buffer...................................................77

Table 5-44 Separate Statistics Collection of PS Channel Types...........................................78

Table 5-45 Adding Counters for Average No. of PDCH Allocated to TBF.............................79

Table 5-46 Adding Collection of PDTCH Congestion Ratio of Unsatisfied MS Multi-timeslot Processing Ability....................................................................................................................80

Table 5-47 Change to Congestion Duration Counter.............................................................81

Table 5-48 PDused Statistics Counting Method Improved.....................................................82

Table 5-49 PDCH Multiplexing Improved...............................................................................84

Table 5-50 Dummy Block Counting Method Modified............................................................86

Table 5-51 Link Establishment Counting on Downlink CCCH Improved................................87

Table 5-52 TBF Release Not Counted in Paging Coordination..............................................88

Table 5-53 Measurement Result Discarded After Reception of Clear CMD..........................89

Table 5-54 CS Service Performance Improved......................................................................91

Table 5-55 Wireless Transmission of PS Service..................................................................94

Table 5-56 AMR Handover Parameter...................................................................................97

Table 5-57 Independent Setting of T3111 and T3109 Timers on TCH and SDCCH...........101

Table 5-58 PS Service Parameter Modification...................................................................102

VI ©2023ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary


Table 5-59 Signaling Trace..................................................................................................104

Table 5-60 New Functions Related to BTS..........................................................................106

Table 5-61 Power Control Optimization...............................................................................107

Table 5-62 RRU With Eight TRXs........................................................................................109

Table 5-63 Paging Occupancy.............................................................................................110

Table 5-64 Downlink Dual-Coding........................................................................................111

Table 5-65 Number of V3 BSC CMP Modules Added to 10.................................................111

Table 5-66 CS/PS Service Access Prohibited During A/Gb Interface Disconnection..........113

Table 5-67 The ICMP-based Fast Rerouting Function.........................................................114



1 About This Document

The BSC UR12.3 is the first software version simultaneously released by the V3 and V4

platforms. The UR11.2 is an enhanced version of the BSC UR11.2. It involves some new

features such as Soft Synchronization, enhanced VAMOS, and enhanced dual-band

network and so on; and it includes the optimization on the voice, packet service, and etc,

greatly improving the performance. This document describes the new and modified

features and performance made on the basis of BSC UR12.3.



2 Brief Description

2.1 Release Background

This commercial software release is released by ZTE. It inherits the previous BSC

UR11.2 version, adds some new features and modifies some features. In addition, the

bugs in BSC UR11.2 are fixed.

Table 2-1 Released Versions

Current Version Previous Version

iBSCV6.50.103dP001 iBSCV6.50.100fP002

iBSCV6.30.102dP002 iBSCV6.20.713d

2.2 Hardware

2.2.1 Supported Hardware Changes

This software version does not involve any new supported hardware boards. The

supported hardware is identical to that of V3 iBSCV6.20.713d and V4 iBSCV6.50.100f.

2.2.2 Supported Hardware Boards

Table 2-2 Supported Hardware Boards (IBSC V3)

Functional Board Name Physical Board Name Remark

CHUB CHUB

PSN PSN4V

PSN PSN4V/2

DTB DTEC

GLI GLI/4

2 © 2023ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary


GLIQV

GLIQV/ 2

DRTB2/UPPB2/TIPB2/

BIPB2/AIPB2VTCD/2

DRTB/TIPB/BIPB/AIPBVTCD

UPPB

EUIP

MNIC/2RUIB

The previous IP interface

boards IPAB/IPGB/IPBB/IPI

are assembled to RUIB.

RUIBMNIC/3

The previous IP interface

boards IPAB/IPGB/IPBB/IPI

are assembled to RUIB.

EUIP

GUIM GUIM

GUIM2 GUIM/2

ICM/ CLKG ICM

OMPMPX86/2

CMP

OMP2MPX/4

CMP2

SDTB2 SDTB/2

SDTB SDTB

LAPD/SPB/GIPB SPB

LAPD2/SPB2/GIPB2 SPB/2

UIMC UIM/2

UIMU UIM/2

SBCX SBCX/2

SBCX SBCX

Table 2-3 Supported Hardware Boards (IBSC V4)

Functional Board Name Physical Board Name Remark



OMM UMP_B

OMP UMP1b

CMP/RUP USP_D

EGBS EGBS

EGFS EGFS

ETCB ETCB

EGPB EGPB

EDTI /EDGB EDTI

EDAB/EDBB/EDTB EDTT

ESDTI/ESDGB ESDTI

ESDAB ESDTT

ESDBB/ESDTB/ESDQB ESDTG

2.3 Correlated Versions

OMMROMMR(R3)V12.12.47

OMMR(R4)V12.12.47

RCT GUTV 3.00.400h

NDS NDS 13.2

NETMAX NetMAX-GUV 13.2

2.4 Compatibility with NEs

Table 2-4 BSC UR12.3 Compatibility

BSCCompatible

with SDR

Compatible

with BTSV3

Compatible with

BTSV2

Compatible

with iTC

UR12.3 V4.12.10.20 -

V4.12.10.24



2.5 Supported Development Roadmap

The following versions are supported to develop to

iBSCV6.50.103dP001/OMMR(R4)V12.12.47

Table 2-5 Development Roadmap

Roadmap Detailed Version

UR11.2 iBSCV6.50.100fP002/OMMR(R4)V12.11.40P05

iBSCV6.20.713d/iOMCRV6.20.713e



3 Device Capacity & KPI Changes

Compared with the BSC UR11.2, the BSC UR12.3 does not have any changes in terms

of the device capacity or KPI.



4 O&M Changes

4.1 Parameter Changes

Please refer to Annex I.

4.2 Internal Parameter Changes (Not open to the

External)

Please refer to Annex V.

4.3 Alarm Changes

Please refer to Annex II for the alarm/notification changes from iBSCV6.20.713d to

iBSCV6.30.103d.

Please refer to Annex II for the alarm/notification changes from iBSCV6.50.100f to

iBSCV6.50.103dp001.

4.4 Counter Changes

Please refer to Annex III.

4.5 License Control Changes

Please refer to Annex IV.



5 Feature Changes

5.1 List of Feature Changes

Table 5-6 List of Feature Changes

Feature ID Feature Name

New

Feature

s or

Enhanc

ed

Feature

s

Default

Status

Basic/

Optional

Correlati

on with

Other

NEs

ZGO-05-03-

007

Soft

SynchronizationNew

Disable

dOptional SDR

ZGO-06-01-

018

Single-Pass

DetectionNew

Disable

dOptional None

ZGO-01-01-

006

TCH Re-

AssignmentNew

Disable

dOptional None

ZGO-06-02-

004

A5/4 Ciphering

AlgorithmNew

Disable

dOptional SDR

ZGO-01-02-

011

Intelligent TCP

Traffic

Management

NewDisable

dOptional None

ZGO-01-02-

006

MTC Device

Access ControlNew

Disable

dOptional SDR

ZGO-03-01-

004

SDCCH

Congestion ControlNew

Disable

dOptional SDR

ZGO-03-05-

010

Early TBF

Establishment

Downlink

NewDisable

dOptional None

ZGO-02-02-

024

Handover

Command Lost

Optimization

NewDisable

dOptional None



ZGB-01-03-

003

Short Message

Service (SMS)

Enhance

d

Disable

dOptional None

ZGB-01-03-

002

Data Traffic

Channels

Enhance

d

Disable

dOptional None

ZGO-01-01-

005

Call Re-

Establishment

Enhance

d

Disable

dOptional None

ZGO-04-02-

024

Related Dual-Band

Network

Enhance

d

Disable

dOptional None

ZGO-02-02-

013

Different Cell

Reselection

Parameters for

IDLE and ACTIVE

Status

Enhance

d

Disable

dOptional None

ZGO-02-02-

007

Traffic Based

Handover

Enhance

d

Disable

dOptional None

ZGO-02-02-

002

Dynamic Handover

Priority Algorithm

Enhance

d

Disable

dOptional None

ZGO-04-03-

001

Synthesized

Frequency

Hopping

Enhance

d

Disable

dOptional SDR

ZGO-04-02-

006TFO

Enhance

d

Enable

dBasic None

ZGO-01-01-

003

Adaptive Multi-

Rate Codec (AMR)

Enhance

d

Enable

dBasic None

ZGO-02-02-

018

Fast Handover

Based on Downlink

Level

Enhance

d

Disable

dOptional None

ZGB-03-02-

003

Dynamic

Configuration of

SDCCH

Enhance

d

Disable

dOptional None

ZGO-04-02-

005Co-BCCH

Enhance

d

Disable

dOptional None

ZGB-02-02-

001Basic handover

Enhance

d

Disable

dOptional None

ZGO-04-04-

002

Load Dependent

Intelligent TRX

Enhance

d

Disable

d

Optional None



Shutdown

ZGO-04-04-

007

Intelligent Cell

Shutdown

Enhance

d

Disable

dOptional None

ZGO-06-01-

005

Measurement

Report (MR) Data

Report

Enhance

d

Disable

dOptional None

ZGO-02-03-

009

Fast Return from

GSM to WCDMA

Enhance

d

Disable

dOptional None

ZGO-02-02-

010

Network-Assisted

Cell Change

(NACC)

Enhance

d

Disable

dOptional None

ZGO-02-02-

012

Network Controlled

Cell Reselection

Enhance

d

Disable

dOptional None

ZGO-01-02-

009

Traffic Based

PDCH Expansion

Enhance

d

Disable

dOptional None

ZGB-03-05-

002

Initial Coding

Scheme per Cell

Settable

Enhance

d

Disable

dOptional None

ZGO-01-03-

005

Dual Transfer

Mode

Enhance

d

Disable

dOptional None

ZGO-02-03-

008

GSM/LTE Cell

Reselection

Enhance

d

Disable

dOptional None

ZGO-04-02-

016PS Power Control

Enhance

d

Disable

dOptional BTS

ZGO-02-02-

004

SDCCH/SDCCH

Handover

Enhance

d

Disable

dOptional None

ZGO-04-01-

011

Power Boost for

8PSK

Enhance

d

Disable

dOptional None

ZGO-03-02-

012

PS Channel

Extension

Enhance

d

Disable

dOptional None

ZGO-01-02-

007

Radio Resource

Management

Based on User

Priority and

Service Type

Enhance

d

Disable

dOptional

ZGO-04-05- VAMOS Pairing Enhance Disable Optional SDR



003 and De-Pairing d d

ZGO-06-01-

008

Call Detail Trace

(CDT) Data Report

Enhance

d

Disable

dOptional None

ZGB-03-02-

006

Dynamic Channel

Management

Enhance

d

Disable

dOptional None

ZGO-04-01-

007

Dynamic Power

Sharing

Enhance

d

Disable

dOptional None

ZGB-03-04-

001BSC Load Control

Enhance

d

Disable

dOptional None

ZGO-03-02-

003

Enhancement on

PS Channel

Allocation

Enhance

d

Disable

dOptional None

ZGO-06-01-

001

Automatic

Adjusting of BA

List

Enhance

d

Disable

dOptional None

Separate Statistics

of Assignment

Failure Counter

NewEnable

dNone

Statistics of

Improving Adjacent

Cell Relationship

Measurement

NewEnable

dNone

Call Drop Counter

due to Handover

Failure Classified

by Handover Type

NewEnable

dNone

Statistics

Optimization of

Call Drop due to

Handover

NewEnable

dNone

Statistics of Call

Drop by Handover

Reason

NewEnable

dNone

Add Statistics of

Assignment

Attempt, Success

and Failure when

New Enable

d

None



Assigning for a

Second Time by

iBSC

Add Statistics due

to User’s Active

Release during

Assignment

(Handover)

Attempt and

Execution

NewEnable

dNone

Add Counters of

Directed RetryNew

Enable

dNone

Counters of

Smaller Granularity

about Paging

Delivery Times

NewEnable

dNone

Add Statistics of

Cell-Level Paging

Overflow

NewEnable

dNone

Add Statistics of

Dynamic SD

Conversion Times

NewEnable

dNone

Statistics of UL/DL

RQ by RRU when

Multi-RRU Co-Cell

NewEnable

dNone

Add Statistics of

UPPB Cache Peak

Value/Average

Value

NewEnable

dNone

Classified

Statistics of PS

Channel Type

NewEnable

dNone

Add Statistics of

Average PDCH

Occupied by TBF

NewEnable

dNone

Statistics of

PDTCH

New Enable

d

None



Congestion Rate

when MS’s Multi-

Timeslot Capability

Not Satisfied

Modification on

Statistics of

Congestion Length

Enhance

d

Enable

dNone

Optimization on

Dynamic SD

Enhance

d

Disable

dOptional None

Optimization on

PDUsed Statistics

Method

Enhance

d

Enable

dNone

Improved PDCH

Multiplexing

Enhance

d

Disable

dOptional None

Modification on

Dummy Block

Statistics Method

Enhance

d

Disable

dOptional None

Statistics

Optimization on DL

CCCH

Establishment

Enhance

d

Disable

dOptional None

Statistics

Excluding TBF

Release due to

Joint Paging

Enhance

d

Disable

dOptional None

Discard

Measurement

Report after

Receiving Clear

CMD

Enhance

d

Disable

dOptional None

Optimization on

CS Service

Performance

Enhance

d

Disable

dOptional None

Optimization on PS

Service Radio

Transmission

Performance

Enhance

d

Disable

dOptional None



Optimization on

Attach Success

Rate

Enhance

d

Disable

dOptional None

Optimization on

PTCCH Flow

Enhance

d

Disable

dOptional None

AMR Handover

Parameters

Enhance

d

Enable

dOptional None

Separate

Configuration of

T3111 and T3109

Enhance

d

Enable

dBasic None

Independent

Control due to Any

Call Drop Reason

Enhance

d

Enable

dOptional None

Modification of PS

Service

Parameters

Enhance

d

Enable

dOptional None

Signaling TraceEnhance

d

Disable

dOptional None

BSS Invoke Trace NewDisable

dOptional None

Speech MonitorEnhance

d

Disable

dOptional None

CPU Realtime

MonitorNew

Disable

dOptional None

Support BTS New

FeaturesNew

Disable

dOptional SDR

Power Control

Optimization

Enhance

d

Disable

dOptional SDR

Support 8-Carrier

RRUNew

Disable

dOptional SDR

Paging PreemptionEnhance

d

Disable

dOptional SDR

Measurement

Report Cyclic

Parameters

Configurable

Enhance

d

Disable

dOptional SDR



Support P563

MOS

Enhancement

Enhance

d

Disable

dOptional None

DL Dual CodingEnhance

d

Enable

dOptional None

Enhance VIP User

and Test User’

Service

Experience

Optimization

NewDisable

dOptional None

V3 BSC CMP

Module Number

Increased to 10

Enhance

d

Disable

dOptional None

Control PS

Channel Numbers

by Slave

Enhance

d

Enable

dBasic None

Support CellBar

when A/Gb Not

accessible

NewDisable

dOptional None

EUIP Dual Hang-

upNew

Disable

dOptional SDR

Rapid Re-Routing

Based on ICMPNew

Disable

dOptional None

5.2 New Features

5.2.1 ZGO-05-03-007 Soft Synchronization

Table 5-7 Soft Synchronization

Description This feature adjusts the frame number and offset through the

software to make the BTSs use the identical frame number and

offset. The soft synchronous sub-system has the following

functions: Collects the soft synchronous offset information,

adjusts the soft synchronous offset time, and configures the

parameters related to the soft synchronous sub-system, and so



on. The soft synchronous offset information can be collected by

MTD method (carried in the handover complete message) and

by AB method (both the source BTS and target BTS actively

detect the AB pulse during the handover). The soft

synchronous offset adjustment supports the complete

adjustment of frame numbers and intra-frame offset

adjustment. The functions mentioned above can be controlled

through the parameters configured on the OMCR.

Feature Num ZGO-05-03-007

Impact on

Equipment

Performance

At the start of the offset information synchronization, the load

calculated by the OMP will have some rise.

Impact on

Network

There will be extra intra-cell handover by AB method. Some

idle TRXs will be used to for measurement, which influences

the normal use of these idle TRXs.

At the start of the offset information synchronization, the load

calculated by the OMP will have some rise.

During the offset information synchronization, the BTSs that

perform the frame synchronization have their offset frequently

adjusted, resulting in the decrease of the voice quality.

After the BTSs are synchronized, the application of the

technologies such as the IRC, MRC, and EIRC will be

improved.

Hardware

RequirementNone

Impact on other

SystemNew parameters are configured on the OMMR.

License Control None

Relative

Parameter

GUmsyn:UmSynSupport: Um soft Synchronous Support

GUmsyn:SynMeasBaseAB: Soft Synchronous Measure Base

AB

GUmsyn:SynMeasBaseMTD: Soft Synchronous Measure Base

MTD

GUmsyn:BaseABSynMeasSTh: Soft Synchronous Measure

Base AB Start Time(hour)

GUmsyn:BaseABSynMeasSTm: Soft Synchronous Measure

Base AB Start Time(minute)



GUmsyn:BaseABSynMeasDur: Soft Synchronous Measure

Base AB Duration

GUmsyn:SynFrameAdjuestSTh: Soft Synchronous Clock

Adjust Start Time(hour)

GUmsyn:SynFrameAdjuestSTm: Soft Synchronous Clock

Adjust Start Time(minute)

GUmsyn:SynFrameAdjustDur: Soft Synchronous Clock Adjust

Duration(minute)

GUmsyn:BaseMTDSynMeasSTh: Soft Synchronous Measure

Base MTD Start Time(hour)

GUmsyn:BaseMTDSynMeasSTm: Soft Synchronous Measure

Base MTD Start Time(minute)

GUmsyn:BaseMTDSynMeasDur: Soft Synchronous Measure

Base MTD Duration

GUmsyn:DetrimentAdjust: Allow Detriment Adjust

GUmsyn:BaseABSynMeasWeek0: Soft Synchronous Measure

Base AB(Sunday)


Base AB(Monday)


Base AB(Tuesday)


Base AB(Wednesday)


Base AB(Thursday)


Base AB(Friday)


Base AB(Saturday)

GUmsyn:BaseMTDSynMeasWeek0: Soft Synchronous

Measure Base MTD(Sunday)


Measure Base MTD(Monday)


Measure Base MTD(Tuesday)


Measure Base MTD(Wednesday)

GUmsyn:BaseMTDSynMeasWeek4: /Soft Synchronous



Measure Base MTD(Thursday)


Measure Base MTD(Friday)


Measure Base MTD(Saturday)

GUmsyn:SynFrameAdjustWeek0: Soft Synchronous Clock

Adjust(Sunday)


Adjust(Monday)


Adjust(Tuesday)


Adjust(Wednesday)


Adjust(Thursday)


Adjust(Friday)


Adjust(Saturday)

GUmsyn:LevelDiffThs: Level Difference Threshold of Ncell and

Serving Cell

GUmsyn:SynMeasHoStartThs: Synchronous Measure

handover Start Threshold

GUmsyn:SynMeasTrxMax: Max Number Synchronous

Measure TRX Per Site

GUmsyn:InterBSCSynMeasSupp: InterBSC Soft Synchronous

Measure Support

GUmsyn.IsAdjustFrameNo: Whether to adjust frame number

GUmsyn.IsCycleAdjust: Cycle adjustment

vsDataGBtsSiteManager.BenchmarkSite: Benchmark Site

vsDataGGsmCell.UmSynSupport: Um soft Synchronous

Support

vsDataGExternalGsmCell.UmSynSupport: Um soft

Synchronous Support

Relative Counter C901100058 The maximum of frame offset by AB method

C901100059 The sum of frame offset by AB method



C901100060 Number of sample by AB method

C901100061 Number of measure TRX request

C901100062 Number of measure TRX request failure


with busy


with non-TRX

C901100065 Number of measure TRX request success

C901100066 Number of clock syn-measure handover

attempt

C901100067 Number of syn-measure requests

C901100068 Number of invalid syn-measure handover

perform

C901100069 Number of invalid syn-measure handover

success

C901100070 Number of valid syn-measure handover

perform

C901100071 Number of valid syn-measure handover

success

C901100072 Number of valid syn-measure data

C902620001 Number of non-detriment adjust attempt

C902620002 Number of non-detriment adjust perform

C902620003 Number of non-detriment adjust success

C902620004 Number of non-detriment adjust failure

C902620005 Number of detriment adjust attempt

C902620006 Number of detriment adjust perform

C902620007 Number of detriment adjust success

C902620008 Number of detriment adjust failure

C902620009 Number of cycle adjust attempt

C902620010 Number of cycle adjust perform

Relative Alarm

198087500: Radio Interface Synchronization ARF emendate

Successfully

198087501: Radio Interface Synchronization ARF emendate

Failed

VerificationAfter the synchronization information is adjusted, each BTS

satisfies the requirement of synchronization.



Impact on other

featureNone

Note Supported by SDR 4.12

5.2.2 ZGO-06-01-018 Single-Pass Detection

Table 5-8 Single-Pass Detection

Description

This feature detects where there is a path by means of the user

plane IP message rules. In other words, detect where there are

discontinuous messages within T period (configurable on the

OMMR); if yes, report the information that the service is likely

to have sent a single-pass process. The detection is usually

performed on the TC board, RUP board, E1 interface board

and Ater interface board over Abis, Ater and A.

[TRAU frame detection is improved] This version has modified

the TRAU detection over the E1 interface. Statistics of the

reported alarm notifications are made, but call drops are not

handled.


Impact on

Equipment

Performance

None

Impact on Network

This feature detects whether there is single-pass in the

network. In addition, related data analysis further improves the

network maintenance quality.

Hardware

RequirementNone

Impact on other



Relative Parameter

vsDataGBssFunction.MuteCallDetSupport: If support mute call

detect

GBssFunctionTimer.MuteCallDetTimer: Mute call detect timer

Relative Counter None

Relative Alarm 198087516(V3)199087516(V4): Mute call detect



198087434: Cannot detect up or down TRAU notification

Verification

Open the single-pass detection switch and set the time to start

the detection

Create some single-pass detection faults over IP Abis or IPA

Check on the OMMR to find whether the single-pass detection

is reported and whether the related information is correct

Impact on other

featureNone

Note

The single-pass detected by this feature is only of statistical

meaning. It does not mean the single-pass actually exists. For

cells, TRXs and processing units where multiple single-passes

are detected, try other ways to confirm.

5.2.3 ZGO-01-01-006 TCH Re-Assignment

Table 5-9 TCH Re-Assignment

Description

This feature indicates that the BSC reinitiates the TCH

assignment procedure when the MS returns to the previous

channel due to the assignment failure or handover failure

(directed retry) or the BSC reinitiates the TCH assignment

procedure before the assignment timer T3107 expires and

before the protective time of A interface. Directed retry to other

cells is preferred.


Impact on

Equipment

Performance

None

Impact on Network This feature enhances the assignment success rate.

Hardware

RequirementNone

Impact on other



Relative Parameter GBssFunctionOption.reassignenable: Reassign enable

GBssFunctionOption.reassignprotect: Protective time for



reassigning procedure

GBssFunctionOption.reassignmax: Max times of reassign

GBssFunctionOption.reassignlevths: Reassign level threshold

Relative Counter

C901050093 Number of reassignment attempts

C901050094 Number of reassignment success

C901050095 Number of reassignment failure

C901070194 Number of drop call on TCH/F due to reassign fail

C901070212 Number of drop call on TCH/H due to reassign

fail

Relative Alarm None

Verification Open the TCH re-assignment switch on the OMMR, set the

protective time of A interface, max times of re-assignment and

re-assignment level threshold, and open the directed retry

switch.

Configure adjacent cells of sufficient available channels. Make

the air interface assignment fail or T3107 expire when

assigning. If the adjacent cells’ level is higher than

reassignlevths, execute the directed retry procedure and check

whether the related counters succeed;

Do not configure any adjacent cells. Configure multiple TRXs

for the cell and each TRX has sufficient available channels.

Make the air interface assignment fail or T3107 expire when

assigning. Re-assign on another TRX and check whether the

related counters succeed;

Do not configure any adjacent cells. Configure one TRX of

sufficient available channels for the cell. Make the air interface

assignment fail or T3107 expire when assigning. Re-assign on

another timeslot of the TRX and check whether the related

counters succeed;


assigning. If the number of failures has reached the max times

of re-assignment, return an assignment fault to the CN and

check whether the related counters succeed;


assigning. If the protective time of A interface is out when re-

assigning, return an assignment fault to the CN and check

whether the related counters succeed;

If the target cell replies the resources are unavailable when re-



assigning, the re-assignment judgment procedure restarts after

two seconds.

Impact on other

featureNone

Note None

5.2.4 ZGO-06-02-004 A5/4 Ciphering Algorithm

Table 5-10 A5/4 Ciphering Algorithm

Description

Compared with A5/1, A5/2 and A5/3, the key length of A5/4 is

enlarged from the 64bit to 128bit, which ensures higher

security. This feature supports the A5/4 ciphering algorithm,

which also requires the support from the CN, BTS and UE.


Impact on

Equipment

Performance

After this feature is supported, the related control signaling

between the BSC and BTS are increased by 18 bytes, resulting

in more signaling load. Keep an eye on the influence on the

direct signaling bandwidth between the BSC and BTS.

Impact on Network None

Hardware

RequirementNone

Impact on other

System

There are new A5/4 values on the interface connecting to the

BTS; there is no new structure or new parameters.

License ControlYes; the total number of TRXs that support the A5/4 ciphering

is controlled by the license.

Relative Parameter

vsDataGGsmCell.cipherModePrio1: Cipher mode priority 1








Relative Alarm None



Verification

Configure the A5/4 ciphering algorithm on the OMMR;

Make a call to check the signaling trace; content about the A5/4

can be seen in the signaling;

Configure the cell not to support the A5/4 ciphering algorithm

on the OMMR;

Make a call to check the signaling trace; content about the A5/4

cannot be seen in the signaling.

Impact on other

featureNone

Note Keep an eye on the signaling link load on the Abis interface.

5.2.5 ZGO-01-02-011Intelligent TCP Traffic Management

Table 5-11 Intelligent TCP Traffic Management

Description

TCP is a transmission protocol designed for fixed hosts and

wired networks. For the wired network, the network congestion

is the main cause for packet loss since its BER is quite low.

When TCP is applied in the wireless environment, packet

transmission disorder, high rate of packet loss, long RTT are

the problems that can’t be handled well by the traditional TCP

protocol. That reduces the data throughput of services borne

on TCP. The BSC can join the TCP semantics interaction to

enhance the data throughput of a single TCP downloading.

This feature achieves the splitting uplink tcp ack datagram,

copying uplink tcp ack datagram and discarding duplicate

uplink tcp ack datagram, improving the reliability of the radio

TCP transmission.

This feature enhances the TCP procedure in wireless

environment by taking part in the TCP protocol interaction

between MS and Internet application server, and increases the

data throughput of a single TCP connection.

Feature Num MktR-PE-20110708-0063

Impact on

Equipment

Performance

None

Impact on Network The tests show that the copying ack datagram improves the



downloading rate when packet loss occurs. But the test results

of splitting ack datagram and discarding duplicate ack

datagram are not good enough.

Hardware

RequirementNone

Impact on other



Relative Parameter

Parameters in terms of A2 are added on R_PSBTS:

GCellPs.SuppTcpAckSplit: Support splitting uplink tcp ack

datagram

GCellPs.SuppTcpAckCopy: Support copying uplink tcp ack

datagram

GCellPs.SuppDupTcpAckDisc: Support discarding duplicate

uplink tcp ack datagram


Relative Alarm None

Verification

1. When the copying ack datagram is enabled, the ping

packets, web browsing, and ftp uploading/download are

normal;

2. Enabling the copying ack datagram for ftp downloading

when there are few packet losses will make a higher

downloading speed compared with the rate when the copying

ack datagram is disabled.

Impact on other

featureNone

Note

The test results when the splitting ack datagram and discarding

duplicate ack datagram are enabled are not good enough.

Therefore, they are not suggested to be enabled.

5.2.6 ZGO-03-01-004 SDCCH Congestion Control

Table 5-12 SDCCH Congestion Control

Description The dynamic SDCCH functionality expands the SDCCH to

relieve the SDCCH congestion. In some abnormal cases, all



the SDCCHs are busy, which makes it difficult to make a call in

the cell. Some measures must be taken to control the RACH

requests. Set the SDCCH overload threshold and duration

threshold. When the traffic on the SDCCH exceeds the two

thresholds, control the RACH traffic. To control the RACH

traffic, discard the MTC, MOC, and LOC requests according to

the proportion configured on the OMMR. When the traffic on

the SDCCH no longer overloads and the duration exceeds the

threshold, stop the RACH traffic control.


Impact on

Equipment

Performance

None

Impact on NetworkWhen busy, the RACH requests are discarded according to the

configuration on the OMMR.

Hardware

RequirementNone

Impact on other



Relative Parameter

Parameters of Type B:

GCellOption.RACHFlowControl RACH RACH Flow Control

Enable

GCellOption.SDCCHbusyThreshold SDCCH Busy Threshold

GCellOption.SDCCHBusyDuration SDCCH Busy Duration

GCellOption.MTCfilterRatio Filter Ratio of MTC

GCellOption.MOCfilterRatio Filter Ratio of MOC

GCellOption.LOCfilterRatio Filter Ratio of LOC

GCellOption.EmCallRatio Filter Ratio of Emergency Call

GCellOption.ReestCallRatio Filter Ratio of Call Re-

establishment

GCellOption.PSFilterRatio Filter Ratio of Packet Access

GCellOption.OtherCallRatio Filter Ratio of Other Access

Relative Counter C901640022 Number of MTC Channel REQ filtered

C901640023 Number of MOC Channel REQ filtered

C901640024 Number of LOC Channel REQ filtered



C901640025 Number of EMC Channel REQ filtered

C901640026 Number of CALLREEST Channel REQ filtered

C901640027 Number of PS Channel REQ filtered

C901640028 Number of Other Channel REQ filtered

C901640029 Number of immediate assignments be delayed

Relative Alarm None

Verification

When this feature is enabled and the thresholds of congestion

are satisfied, the RACH requests can be controlled according

to the configuration on the OMMR.

Impact on other

featureNone

Note None

5.2.7 ZGO-03-05-010 Early TBF Establishment Downlink

Table 5-13 Early TBF Establishment Downlink

Description

After an uplink TBF is established, apply for downlink

resources and send packet timeslot re-assignment message in

advance to establish a downlink TBF without receiving an

actual downlink PDU.


Impact on

Equipment

Performance

None

Impact on Network

This feature reduces the delay of the ping’s first packet under

two-phase access, which may influence the TBF establishment

success rate.

Hardware

RequirementNone

Impact on other



Relative Parameter GCellPs.EarlyDlTBFEstSupp Downlink TBF pre-establish

support




GCellOption.DlEarlyEstWaitTimer Wait timer of downlink

early establishmentl R_PSBTSUPOPT

Existing Parameters of Type B:

GCellOption.InitUlAckSendPrio Initial Packet uplink ack

priority to send


Relative Alarm None

Verification

When this feature is enabled, the delay of the ping’s first

packet under two-phase access is reduced;

When this feature is enabled, all the PS signaling and data

services such as attach, PDP activation, website browsing, and

ftp downloading and so on are normal.

Impact on other

featureNone

Note

Both the Initial Packet uplink ack priority to send and this

feature should be enabled to ensure the normal PS services

under one-phase access.

5.2.8 ZGO-02-02-024 Handover Command Lost Optimization

Table 5-14 Handover Command Lost Optimization

Description

The BSC has already sent the handover command, but the MS

fails to receive it or the handover command is lost due to the

congestion on the Abis interface. To handle these problems, the

BSS designs a handover command lost optimization solution.

The BSS first determines where the handover command is lost.

If the handover command is lost on the Abis interface, the BSC

sends the next handover timely; if it is lost on the Um interface,

the BTS resends the handover command. This feature aims to

reduce the call drops caused by the handover command lost.


Impact on

Equipment

Performance

None

Impact on Network This feature reduces the call drops caused by handover and



improves call drop KPI.

Hardware

RequirementNone

Impact on other



Relative

Parameter


GBssFunctionOption.HoCmdLostOpt Optimize when handover

command lost

GBssFunctionOption.TDelayAftHoCmdOptThe delay after

handover command when optimize

Relative CounterC902500009 Number of Handover Cmd Lost optimize when

handover

Relative Alarm None

Verification

Enable this feature to verify:

The call holds when the handover command is lost on the Abis

interface and the measurement results contain the

measurement report;

The call drops when the handover command is lost on the Abis

interface and the measurement results does not contain the

measurement report;

Reset the handover protection timer when the handover

command is lost on the Um interface and the measurement

results contain the measurement report; the call holds if the

handover succeeds before the timer expires; otherwise, the call

drops if the timer expires again;

The call drops when the handover command is lost on the Um

interface and the measurement results does not contain the

measurement report.

Impact on other

featureNone

Note The SDRV4.11.15 must support this feature;

When enabling this feature, ensure the value of

TDelayAftHoCmdOpt should be greater than T200*(N200+1);

When enabling this feature, adjust the timers related with the

handover on the BSC and ensure the length of the timers

greater than TDelayAftHoCmdOpt;



The timers related with the handover on the BSC include

RmsT3107 (intra-cell handover), RmsT3103 (intra-BSC inter-

cell handover), RmsT8 (outgoing handover to 2G cells),

RmsT3121 (incoming handover to 3G cells) and RmsT1 (wait

for access).

5.3 Enhanced Functions

5.3.1 ZGO-01-01-005 Call Reestablishment

Table 5-15 Call Reestablishment

Description

[GBssFunctionOption.CallReEstCheckImsi] In the call

reestablishment process, the switch on OMMR can be used to

control whether to perform IMSI conflict check, and determine

whether to send the clear req message and whether to count it

into the total number of call drops.


Impact on

Equipment

Performance

None

Impact on NetworkThe Call Drop Rate index can be improved if this function is

enabled.

Hardware

Requirement

None

Impact on other

System

New configuration parameters are added on OMMR.


Relative Parameter

Class-B Parameters:

GBssFunctionOption.CallReEstCheckImsi: Call Re-

establishment Check IMSI

GBssFunctionOption.IMSIConflictInclude IMSI: Drop call

because of IMSI Conflict included in total drops

GBssFunctionOption.IMSIConflictMargin IMSI: Timer of Clear

Request delayed because of IMSI Conflict




Relative Alarm None

Verification

Disable the newly-added switch, start call reestablishment, and the

system does not perform IMSI conflict check.

2. Enable the newly-added switch, start call reestablishment, and

the system performs IMSI conflict check.

Impact on other

feature

None

Note None

5.3.2 ZGO-04-02-024 Related Dual-Band Network

Table 5-16 Related Dual-Band Network

Description

This feature configures the related cells consisting of two

independent physical cells, which correspond to different bands

(900MHz and 1800MHz) cells respectively. During the service

establishment and service processes, balance the load

between the two cells to relieve the congestion and improve

the resource utilization.

This feature enables the traffic handover and traffic-based

directed retry between the two related cells. The PS service

has its load balanced through NC2.


Impact on

Equipment

Performance

None

Impact on NetworkThis feature improves the resource utilization in the related

cells.

Hardware

RequirementNone

Impact on other


License Control Yes

Relative Parameter vsDataGGsmCell .IsDualFreqSup: (Is Enhanced Dual-

Frequency Network Support)



vsDataGGsmCell.DualFreqNetTchThs: (TCH Allocation

Threshold For Dual-Frequency Network)

vsDataGGsmRelation .IsDualFreqRltCell : (Is The Related Cell

In dual- Frequency Network)

GHandoverControl .DualFreqHoSup: (Is Dual-Frequency

Traffic Handover Support)

GHandoverControl .DualFreqHoN: (Dual-Frequency Handover

Parameter N)

GHandoverControl .DualFreqHoP: (Dual-Frequency Handover

Parameter P)

GHandoverControl .DualFreqHoTAThs: (Dual-Frequency

Handover TA Threshold)

GHandoverControl .DualFreqHoDLThs: (Dual-Frequency

Handover RxLevel Threshold)

GHandoverControl .DualFreqOverLoadThs: (Dual-Frequency

Traffic Handover Threshold)

GCellPsNc2. DualFreqNC2Sup: ( Is Dual-Frequency NC2

Support)

GCellPsNc2.DualFreqNC2N: (Dual-Frequency NC2 Parameter

N)

GCellPsNc2.DualFreqNC2P: (Dual-Frequency NC2 Parameter

P)

GCellPsNc2. DualFreqNC2TAThr: (Dual-Frequency NC2 TA

Threshold)

GCellPsNc2.DualCellPsChanThr:(Dual-Frequency NC2 load

Threshold)

Relative Counter

C902500010 Number of Dual Frequence Traffic handover

attempts



success


attempts on TCH/F


attempts on TCH/H

C901070232 Number of HO drops due Dual Frequence Traffic

Relative Alarm None



Verification

Open the dual-band network switch (IsDualFreqSup);

Perform the handover and reselect the related cell configured

in the adjacent cell in the dual-frequency network

(IsDualFreqRltCell);

Configure a proper TCH Allocation Threshold For Dual-

Frequency Network (DualFreqNetTchThs);

Initiate service; observe whether the service will be handed

over to the related cell through the directed retry after the

current cell’s load exceeds the TCH Allocation Threshold For

Dual-Frequency Network;

Open the Dual-Frequency Traffic Handover Support switch

(DualFreqHoSup);

Configure the dual-frequency traffic handover parameters

(DualFreqHoN, DualFreqHoP, DualFreqHoTAThs,

DualFreqHoDLThs and DualFreqOverLoadThs);

Initiate voice service; observe whether the service will be

handed over to the related cell through the dual-frequency

traffic handover after the current cell’s load exceeds the Dual-

Frequency Traffic Handover Threshold;

Set the 900M cell’s load threshold to 0 and 1800M cell’s load

threshold to 100; make the MS access the 900M cell for PS

service, and observe the reselection to the 1800M adjacent

cell;

Set the 1800M cell’s load threshold to 0 and 900M cell’s load

threshold to 100; make the MS access the 1800M cell for PS

service, and observe the reselection to the 900M adjacent cell.

Impact on other

featureNone

NoteThe parameters in terms of handover and NC2 should be

configured according to the related cells’ coverage.

5.3.3 ZGO-02-02-007 Traffic Based Handover

Table 5-17 Traffic Based Handover

Description [Supports the traffic-based handover from HR to FR] This kind

of handover is based on the traffic in the current cell. When the

cell’s load is lower than the HR-FR traffic-based handover



threshold, the subscribers using HR channels will be handed

over to FR channels, improving the call quality.

[Quality-based and level-based HR/FR handover]

For the handover from FR to HR due to load: A call under the

circumstance of good quality but poor level is likely to drop in

case of a handover; to avoid the call drop, ehnhance the level

threshold for a call, and there are thresholds on the uplink and

downlink respectively;

For the handover from HR to FR due to quality: A call under the

circumstance of poor quality or poor level is likely to drop in

case of a handover; to avoid the call drop, ehnhance the quality

threshold and level threshold for a call, and there are

thresholds on the uplink and downlink respectively;

For the handover from HR to FR due to load: A call under the

circumstance of poor quality or poor level is likely to drop in

case of a handover; to avoid the call drop, ehnhance the quality

threshold and level threshold for a call, and there are

thresholds on the uplink and downlink respectively.


Impact on

Equipment

Performance

None

Impact on Network

This feature improves the call quality, but it increases the intra-

cell handover; it reduces the call drops caused by the quality-

based or traffic-based HR/FR handover.

Hardware

RequirementNone

Impact on other



Relative Parameter GFhHandoverControl.HRTFRHOSupport2 Support handover

from HR to FR due to low load

GFhHandoverControl.HrToFrHoLoadThr The load of HO from

HR (V1) to FR

GFhHandoverControl.AmrHrToFrHoLoadThr The load of HO

from HR (V3) to FR

GScHandoverControl.HrToFrHoLoadThrSC2 The load of HO



from HR (V1) to FR for Subcell2

GScHandoverControl.AmrHrToFrHoLoadThSC2 The load of

HO from HR (V3) to FR for Subcell2

GFhHandoverControl.FrLoadHoUlQuaThr The uplink quality of

HO from FR to HR load HO

GFhHandoverControl.FrLoadHoDlQuaThr The downlink quality

of FR to HR load HO

GFhHandoverControl.FrLoadHoUlLevThr The uplink level of

FR to HR load HO

GFhHandoverControl.FrLoadHoDlLevThr The downlink level

of FR to HR load HO

GFhHandoverControl.HrQualHoUlQuaLowThr The uplink

quality low threshold of HO from HR(V1) to FR quality HO

GFhHandoverControl.HrQualHoUlQuaHighThr The uplink

quality High threshold of HR(V1) to FR quality HO

GFhHandoverControl.HrQualHoDlQuaLowThr The downlink

quality low threshold of HR(V1) to FR quality HO

GFhHandoverControl.HrQualHoDlQuaHighThr The downlink

quality high threshold of HR(V1) to FR quality HO

GFhHandoverControl.AmrHrQualHoUlQuaLowThr The uplink

receive quality low threshold of HO from HR(V3) to FR quality

HO

GFhHandoverControl.AmrHrQualHoUlQuaHighThr The uplink

receive quality high threshold of HR(V3) to FR quality HO

GFhHandoverControl.AmrHrQualHoDlQuaLowThr The

downlink receive quality low threshold of HR(V3) to FR quality

HO

GFhHandoverControl.AmrHrQualHoDlQuaHighThr The

downlink receive quality high threshold of HR(V3) to FR quality

HO

GFhHandoverControl.HrQualHoUlLevThr The uplink level of

HR to FR quality HO

GFhHandoverControl.HrQualHoDlLevThr The downlink level

of HR to FR quality HO

GFhHandoverControl.loadandqualhop P value of load and

quality handover

GFhHandoverControl.loadandqualhon N value of load and

quality handover



GFhHandoverControl.HrToFrHoLoadThr HR(V1)-> FR The

load of HO from HR (V1) to FR

GFhHandoverControl.AmrHrToFrHoLoadThr HR(V3)-> FR

The load of HO from HR (V3) to FR

GFhHandoverControl.HrLoadHoUlQuaThr HR ->FR The uplink

quality of HR to FR load HO

GFhHandoverControl.HrLoadHoDlQuaThr HR ->FR The

downlink quality of HR to FR load HO

GFhHandoverControl.HrLoadHoUlLevThr HR ->FR The uplink

level of HR to FR load HO

GFhHandoverControl.HrLoadHoDlLevThr HR ->FR The

downlink level of HR to FR load HO

Relative Counter

C902500001 Number of handover attempt from HR(V1) to FR

due to high load

C902500002 Number of handover from HR(V1) to FR due to

high load

C902500003 Number of handover success from HR(V1) to FR

due to high load


due to high load


high load


due to high load


due to high load in Subcell2


high load in Subcell2






high load in Subcell2



Relative Alarm None



Verification

Supports the traffic-based handover from HR to FR:

Open the HRTFRHOSupport2 switch, and set the

HrToFrHoLoadThr and AmrHrToFrHoLoadThr properly;

If the current cell’s load is lower than HrToFrHoLoadThr, the

system will pick the subscribers whose speech version is HR

(V1) to perform the intra-cell handover from HR to FR; the

corresponding counters have values;

If the current cell’s load is lower than

AmrHrToFrHoLoadThSC2, the system will pick the subscribers

whose speech version is HR (V1) or HR (V3) to perform the

intra-cell handover from HR to FR, and the HR (V1)

subscribers have a higher priority; the corresponding counters

have values;

The system configures sub-cells. Perform the same test as

described above to verify the handover from HR to FR in sub-

cell 2.

Quality-based and level-based HR/FR handover:

Set the parameters and open the switches;

Block some channels to trigger the traffic-based handover from

FR to HR; if the instances selected are allowed for handover as

long as they satisfy the quality and level requirements or not

allowed for handover as long as they fail to satisfy the quality

and level requirements, they are considered to have passed

the test;

For the quality-based handover from HR to FR, if the instances

selected are allowed for handover as long as they satisfy the

quality and level requirements or not allowed for handover as

long as they fail to satisfy the quality and level requirements,

they are considered to have passed the test;

After making an HR call, adjust the load threshold of the

handover from HR to FR to trigger the handover; if the

instances selected are allowed for handover as long as they

satisfy the quality and level requirements or not allowed for

handover as long as they fail to satisfy the quality and level

requirements, they are considered to have passed the test.

Impact on other

featureNone

Note None



5.3.4 ZGO-02-02-002 Dynamic Handover Priority Algorithm

Table 5-18 Dynamic Handover Priority Algorithm

Description

[Enhanced dynamic priority algorithm]

In the drive tests, sometimes the handover did not occur

though the adjacent cell was strong enough or the handover

did not occur in the strongest adjacent cell. The algorithm

solves those problems.

The modification deals with the followings:

1. The dynamic priority switch controls the emergency

handover and non emergency handover respectively;

2. For the non emergency handover, there is a new

parameter Filter Exceed Traffic threshold NCell;

3. A new parameter - VIP user use Dynamic Priority;

4. When VIP user is performing non emergency handover,

there is a new parameter - VIP user Filter Exceed Traffic

threshold NCell;

5. When calculating the adjacent cell’s dynamic priority, use

a new parameter - Dynamic Priority NCell Traffic

Threshold; when the adjacent cell’s traffic exceeds the

threshold, calculate its dynamic priority according to its

traffic; otherwise its dynamic priority equals its static

priority.


Impact on

Equipment

Performance

None

Impact on

NetworkThis feature improves the handover success rate.

Hardware

RequirementNone

Impact on other



Relative

Parameter

1. vsDataGGsmCell.NonEmergHoDynPrio Non

Emergency Handover use Dynamic Priority

2. vsDataGGsmCell.EmergHoDynPrio Emergency



Handover use Dynamic Priority

3. vsDataGGsmCell.FiltExcdThsNCell Filter Exceed Traffic

threshold NCell

Parameters of type B:

1. GCellOption.DynPrioNCellTrafThs Dynamic Priority

NCell Traffic Threshold

2. GVipImsi.VIPHoDynPrio VIP user use Dynamic Priority

3. GVipImsi.VIPFiltExcdThsNCell VIP user Filter Exceed

Traffic threshold NCell


Relative Alarm None

Verification

Configure parameters Non Emergency Handover use Dynamic

Priority and Emergency Handover use Dynamic Priority; initiate

non emergency handover and emergency handover to verify

whether the switch controls correctly;

1. Configure parameters Filter Exceed Traffic threshold NCell

and Traffic Threshold; initiate non emergency handover to

verify whether the switch controls correctly;

2. Configure parameter VIP user use Dynamic Priority to

verify whether the switch controls correctly.

Impact on other

featureNone

Note None

5.3.5 ZGO-04-02-006 TFO

Table 5-19 TFO

Description [Improvement on the processing of stealing frames during AMR

TFO] During an AMR TFO process, the BTS interacts with the

TC in terms of some configuration information which is

completed by frames. During the interaction, some rate sets

steal the frames due to the insufficient information of the TFO

frame/TRAU frame bit, which influences the voice quality a lot.

To handle this problem, try to reduce the number of frames

stolen or avoid the stealing, which can be achieved through

reducing the frequency of sending the configuration information



or having the information sent by speech frames.


Impact on

Equipment

Performance

None


Hardware

RequirementNone

Impact on other

SystemNone


Relative Parameter None


Relative Alarm None

Verification Enable the AMR TFO, and test the MOS.

Impact on other

featureNone

Note None

5.3.6 ZGB-03-02-003 Dynamic Configuration of SDCCH

Table 5-20 Dynamic Configuration of SDCCH

Description [Dynamic SDCCH Conversion Algorithm Improved] When

SDCCH is converted back to dynamic TCH after dynamic

SDCCH conversion ends, whether SDCCCH channel is released

is not taken into account. And the forced SDCCH release

operated will cause call setup failure, and thus needs to be

improved.

Because SDCCH conversion takes a shorter period, the timeslot

blocking will be delayed. When dynamic SDCCH needs to be

converted back, the system will block the timeslot first and check

whether there are services. If there are no services, the system

will request the base station to perform SDCCH conversion. If

there are services, the system will set SDCCH check timer. After

the timer is time-out, the system checks again whether there are



services. After the timer is time-out for three times, the services

and the timer will be released forcefully. If the time is time-out

and there are no services, the system will trigger SDCCH

conversion. Otherwise, the conversion will end.

[Allocate Static SDCCH in Priority after Dynamic SDCCH is

Enabled] After dynamic SDCCH is enabled, when SDCCH is

allocated to new users, static SDCCH and dynamic SDCCH (the

SDCCH converted from TCH) are in the same priority, this will

affect the efficiency of converting SDCCH back to TCH. Besides,

because the current forced release is due to timeout, more

abnormal events may occur.

If static SDCCH is allocated in priority in the channel allocation

process, SDCCH will become idle first when SDCCH traffic

decreases, and thus the influence to users can be reduced in the

conversion process and the conversion efficiency can be

improved.

Above all, in the channel allocation process, static SDCCH

should be allocated first before the allocation of SDCCH.

Feature Num ZGB-03-02-003

Impact on

Equipment

Performance

None

Impact on Network

The Call Drop Rate due to forced SDCCH release can be

reduced and the efficiency of converting SDCCH back to TCH

can be improved.

Hardware

Requirement

None

Impact on other

System



Relative Parameter

GBssFunctionOption.DynSdCheckDelay: Dynamic sdcch check

delay

GBssFunctionOption.TsRel: Delay of TS forcible release


Relative Alarm None

Verification Dynamic SDCCH Conversion Algorithm Improved

Enable the SDCCH conversion switch, and set the DynSdCheckDelay



timer and the TsRel timer.

(1) Occupy SDCCH (long messages or location update) with a

mobile, create the conditions for SDCCH-to-TCH conversion

(the number of idle SDCCHs is greater than the sum of

minimum number of idle SDCCHs and threshold of TCH-to-

SDCCH conversion in the cell), and observe whether the

system will trigger forced service release and request

SDCCH conversion after the DynSdCheckDelay timer is

time-out. Set lower values for DynSdCheckDelay and TsRel

to create the time-out phenomenon for both timers, and

observe whether a conversion takes place.

Allocate static SDCCH in priority after dynamic SDCCH is enabled:

Enable the dynamic SDCCH conversion switch. Configure static

SDCCH in the cell.

Block SDCCH or modify the dynamic SDCCH conversion threshold,

and trigger dynamic SDCCH conversion to switch TCHF to SDCCH.

The users request channels. When there are both idle dynamic

SDCCH and idle static SDCCH in the cell, check whether the

allocated SDCCH is static SDCCH or dynamic SDCCH.

Verification Criteria: When idle static SDCCH and dynamic

SDCCH exist in a cell at the same time, SDCCH is allocated first.

Impact on other

feature

None

Note None

5.3.7 ZGO-04-02-005 Co-BCCH

Table 5-21 Co-BCCH

Description [Improved Co-BCCH]

In Co-BCCH cells, some control parameters are necessary when

the traffic balance or migration between the two subcells cannot

be achieved according to the actual situation. In this way,

different strategies in terms of the balance and migration can be

applied during the service establishment or the service process.

To better control the traffic balance and migration between the

subcells, the handover decision parameters N and P are

separately configured for SubCell1 and SubCell2. Use some new



parameters - SubCell Channel Allocation Control, Traffic

Threshold of Handover in SubCell1 and Traffic Threshold of

Handover out SubCell1. To avoid the blind handover from

SubCell 2 to SubCell1, use a new parameter - SubCell2 To

SubCell1 Handover Threshold.

For Co-BCCH cells, the parameter SubCell Channel Allocation

Control configured on the OMMR controls the subcells’ traffic

during the assignment. During the service process, the traffic

between the two subcells is balanced by the parameters - Traffic

Threshold of Handover in SubCell1 and Traffic Threshold of

Handover out SubCell1.

[A new switch to control the direct assignment from SubCell1’s

SDCCH to SubCell2’s TCH in the access phase]

When the Co-BCCH is applied on sites, there are usually fewer

channels in SubCell1; therefore try to keep the subscribers in

SubCell2. If the path loss/TA requirements are satisfied, directly

assign to SubCell2. The measurement made on SubCell1’s

SDCCH shows the signal of SubCell1; sometimes it’s not correct

enough to estimate the path loss for assignment based on that

signal, which influences the assignment success rate. Hence,

there is one more countermeasure – assign in SubCell1 only,

which is applied to the SubCell1 of abundant channels and

requires higher assignment success rate; after the assignment

completes, transfer the subscribers to SubCell2 through

handover.


Impact on

Equipment

Performance

None

Impact on NetworkThis feature reduces the unnecessary inter-subcell handover to

balance the traffic.

Hardware

RequirementNone

Impact on other



Relative Parameter The following parameters are deleted:

GScHandoverControl.SubCellN;



GScHandoverControl.SubCellP.

The followings are the new parameters:

GScHandoverControl.SubCell1N: Handover Parameter N of

SubCell1

GScHandoverControl.SubCell1P: Handover Parameter P of

SubCell1

GScHandoverControl.SubCell2N: Handover Parameter N of

SubCell2

GScHandoverControl.SubCell2P: Handover Parameter P of

SubCell2

GScHandoverControl.SubCellHoDLThs: SubCell2 To SubCell1

Handover Threshold

GScHandoverControl.SC1LoadThs1: Traffic Threshold of

Handover in SubCell1

GScHandoverControl.SC1LoadThs2: Traffic Threshold of

Handover out SubCell1

vsDataGGsmCell.CSAllocSC: SubCell Channel Allocation

Control

vsDataGGsmCell.SubCellAssign: Assign strategy for Cobcch


Relative Alarm None

Verification

Improvement on the Co-BCCH feature:

Configure the parameter SubCell Channel Allocation Control on

the OMMR (CSAllocSC: ‘0’ indicates allocation in SubCell2 is of

a higher priority; ‘1’ indicates allocation in SubCell1 is of a higher

priority);

1. Configure Traffic Threshold of Handover in SubCell1

(SC1LoadThs1) and Traffic Threshold of Handover out

SubCell1 (SC1LoadThs2);

2. Initiate the service; verify whether the MS is directly assigned

to the related subcell according to the parameter SubCell

Channel Allocation Control;

3. Verify whether the traffic between the subcells is balanced

through the inter-subcell handover according to the subcells’

load;

4. Open the BCCH measurement switch of SubCell2, and set

SubCellHoDLThs to different values; verify whether the

handover in SubCell1 does not occur unless the SubCell1’s



level measured is greater than the threshold;

5. A new switch to control the direct assignment from

SubCell1’s SDCCH to SubCell2’s TCH in the access phase:

In the Co-BCCH cell, set SubCellAssign to Assignment to

SubCell1 only; initiate a call; the call is assigned to

SubCell1’s channel only regardless of whether the path

loss/TA satisfies the requirements of assignment to SubCell2.

Impact on other

featureNone

Note None

5.3.8 ZGB-02-02-001 Basic Handover

Table 5-22 Basic Handover

Description [Improvement on the synchronous handover]

If the parameter Synchronism is set to No, no synchronous

handover occurs.

[Supports handover from HR to FR under IPA]

After the 3GPP IPA is supported, the algorithm has been modified

to achieve the TrFO. The speech version before and after the

handover does not change. This leads to a situation that handover

to the FR channel after the HR channel is used will not occur

during the inter-cell handover, which results in an HR traffic and

occupation burst. What’s more, to make an inter-cell handover

from HR to FR, first perform an inter-cell handover from HR to HR,

and then the intra-cell handover from HR to FR. This process

shows one more handover is performed. The inter-cell handover

from HR to FR can solve the above two problems.

[Power control to compensate for the PBGT handover]

Perform the power control to compensate for the downlink level in

every measurement report. The previous version makes the last

power control value on the window as the compensation after the

downlink levels are averaged. The improved version makes the

downlink value more accurate. Enabling the power control reduces

the unnecessary PBGT handover, enhancing the MOS.

[Improvement on the cell’s interference algorithm]

Introduce the parameter InterfBandforHo to the intra-cell handover



caused by the uplink/downlink interference. When the intra-cell

handover is triggered and channel is being requested in the

database, it is also necessary to decide whether the target

channel’s interference band satisfies the interference band

requirements. Actually, when the intra-cell uplink/downlink

interference handover conditions are met, other channels in the

cell usually do not have good interference. Deciding the

InterfBandforHo when requesting channels in the database will

likely to cause the channels are not available for the allocation,

which causes congestion and more invalid intra-cell handovers.

More parameters are used to control the decision of the target

cell’s interference band.

[At the successful handover, the BTS does not send more DISC

frames]

When the LAPDM is under the multi-frame establishment status,

the SDR will send more DISC frames to the MS after the BSC has

sent the RF Channel Release message so that the MS can be

released normally. In the meantime, the SDR starts a 400ms timer

to wait for the response from the MS. If the MS is handed over to

the new channel successfully, it is definite that the SDR will never

receive the MS’s response in the source channel; the channel will

not be released until the timer expires, which is a waste of the

channel resources.

Aiming at this situation, the BSC informs the BTS of the successful

handover through the new cell Noneed Disc carried in the RF

Channel Release message, which means no more DISC frames

are necessary.

[Handover due to good level but poor quality]

Under the current algorithm, when the serving cell’s uplink or

downlink level is good but quality is poor and the signal of the

adjacent cell is not as strong as that of the serving cell, continuous

poor voice quality or call drops are likely to occur due to the timely

handover out failure. The improvement on this algorithm

guarantees the users can be handed over to a better cell when the

level is good but quality is poor, enhancing the call quality and

continuity.

[Back to the source cell when handover]

The BSC carries an RSSI value A and a C/I when the handover

target channel is being activated. After the BTS has received the

handover in pulse of the MS, if either the RSSI or the C/I detected



fails to satisfy the threshold, it will not send the physical context to

the MS so that the MS returns to the source channel after the

handover failure.

Feature Num ZGB-02-02-001

Impact on

Equipment

Performance

None

Impact on Network

This feature enhances the handover success rate;

Reduces the occupation of HR;

Reduces unnecessary PBGT handovers;

The improved intra-cell interference handover algorithm relieves

the congestion regardless of the target cell’s interference band,

but it might influence the voice quality after the handover;

At the successful handover, the BTS does not send more DISC

frames, which shortens the occupation period of the TCH and

relieves the congestion;

The handover due to good level but poor quality reduces the call

drop rate and enhances the user experience, but the handover

success rate might be influence;

Back to the source cell when handover reduces the call drop rate,

but the handover success rate might be decreased, too.

Hardware

RequirementNone

Impact on other

System

New parameters are configured on the OMMR.

There is new cell in the RF Channel Release message/channel

activation message on the Abis interface.


Relative Parameter

1. GHandoverControl.hoSyncInd Synchronism

2. GBssHandoverControl.ipabschotype the policy of choosing

speech version in 3GPP IPA BSC handover

3. GHandoverControl.GoodLevBadRQHoEnable:

GHandoverControl .GoodLevBadRQHoDLLev

4. GSdHandoverControl .GoodLevBadRQHoEnable

5. GSdHandoverControl .GoodLevBadRQHoDLLev

6. vsDataGGsmRelation .GoodLevBadRQoffSet[5]

7. GHandoverControl.HoAccessReqCI HoAccess Require CI

8. GHandoverControl.PBGTHoBacktoSource PBGT Back to



Source Cell when PBGT Handover

9. GHandoverControl.OtherHoBacktoSource Back to Source

Cell when Other Handover

10. GHandoverControl.HoAccessReqLevOffset HoAccess

Require Rxlevel offset

11. GHandoverControl.OtherHoAccessLevSel HoAccess

Require Rxlevel Select Strategy when Other Handover

12. GHandoverControl.MSCHoInHoBack2Source Back to

Source Cell when MSC Controlled Incoming Handover

13. GSdHandoverControl.PBGTHoBacktoSource Back to

Source Cell when PBGT Handover

14. GSdHandoverControl.OtherHoBacktoSource Back to

Source Cell when Other Handover

15. GSdHandoverControl.HoAccessReqLevOffset HoAccess

Require Rxlevel offset

16. GSdHandoverControl.OtherHoAccessLevSel HoAccess

Require Rxlevel Select Strategy when Other Handover

17. GSdHandoverControl.MSCHoInHoBack2Source Back to

Source Cell when MSC Controlled Incoming Handover

Parameter of type B:

GBssFunctionOption.HoInterfBandFilter Interference band

Filter of Interference handover

Relative Counter

1. C902000050 Number of Error Indications due to Handover

Access CI Low (On SDCCH)


Access CI Low (On TCH/F)


Access CI Low (On TCH/H)

4. C902500007 Number of back to Source cell successful when

handover (On SDCCH)

5. C902500008 Number of back to Source cell failure when

handover(On SDCCH)


handover (On TCH/F)


handover(On TCH/F)


handover (On TCH/H)




handover(On TCH/H)


Access Level Low(On SDCCH)


Access Level Low(On TCH/F)


Access Level Low(On TCH/H)


Access CI Low (On SDCCH)


Access CI Low (On TCH/F)


Access CI Low (On TCH/H)

Relative Alarm None

Verification

Improvement on the synchronous handover:

Set the parameter Synchronism to No;

1. Observe whether the synchronous handover does not occur

in the cell.

Supports handover from HR to FR under IPA:

Set the A interface to IP; set ipabschotype to a default value ‘0’

and configure the related priority strategies, which indicates the

HR speech version 3 is allocated after a call goes through; initiate

the inter-cell handover (there are enough available channels on

the OMMR); HR channels are allocated after the handover;

Set ipabschotype to a default value ‘1’; the channel rate and type

in the assignment request prefers the FR (it is allowed to be

changed when necessary), but there are no available FR

channels when assigning; allocate HR channels after a call goes

through; assuming the speech version 1, initiate the inter-cell

handover (there are enough available FR channels on the

OMMR); FR channels are allocated after the handover;

Set ipabschotype to a default value ‘1’; HR speech version 1 is

allocated after a call is made; initiate the inter-cell handover

(there are enough available FR channels on the OMMR); HR

channels are allocated after the handover;

1. Set ipabschotype to a default value ‘2’; the channel rate and

type in the assignment request prefers the FR (it is allowed to

be changed when necessary), but there are no available FR

channels when assigning; allocate HR channels after a call



goes through; assuming the speech version 1, initiate the

inter-cell handover (there are enough available FR channels

on the OMMR); FR channels are allocated after the

handover.

Power control to compensate for the PBGT handover:

After the downlink power control is enabled, compare the

number of PBGT handovers before and after the updating

through the KPI for an identical period of time. Normally,

there are fewer PBGT handovers after the updating.

Improvement on the intra-cell interference handover algorithm:

1. Open the interference band filter, and trigger the intra-cell

handover; the channels whose interference band exceeds the

threshold are not allocated;

2. Close the interference band filter, and trigger the intra-cell

handover; the channels whose interference band exceeds the

threshold can be allocated;

At the successful handover, the BTS does not send more DISC

frames:

After the MS initiates a call, the handover is triggered; after

the handover is completed, observe the new cell Noneed

Disc carried in the RF Channel Release message through the

signaling trace; the SDR returns the response after several

ms, no more delay.

Handover due to good level but poor quality:

1. Create a radio environment where the level is good but

quality is poor, and the signal of the adjacent cell is weaker

than that of the serving cell;

2. Close the switch; the quality-based handover decision

succeeds but target cell selecting fails;

3. Open the switch; the quality-based handover succeeds.

Back to the source cell when handover:

1. When handover, the BSC carries the C/I threshold to the BTS

through the channel activation;

2. After the BTS has received the handover in pulse of the MS,

the BTS will not send the physical context message to the

MS as long as the C/I detected does not reach the threshold;

the handover of the MS then fails and returns to the source

channel, and reports an Error IND to the BSC for it to make



statistics.

Impact on other

featureNone

Note None

5.3.9 ZGO-04-04-002 Load Dependent Intelligent TRX Shutdown

Table 5-23 Load Dependent Intelligent TRX Shutdown

Description

[Improvement on the load dependent intelligent TRX shutdown]

Trigger the emergency power-on after the intelligent TRX

shutdown. The TRX already shut down will be powered on

according to the priority, which might lead to a situation that the

TRX powered on is still insufficient for the service. For example,

the PS channel request failure triggers the emergency power-on;

if there are no PS channels on the TRX selected according to the

priority, it does not make sense. The emergency power-on

should not only consider the TRX priority but also the reason.

The TRX status should be taken into consideration when the

TRX is shut down or powered on. The faulty TRX should be shut

down first and powered on last.

The CBC channel configured on the TRX of low priority will be

shut down, which influences the service such as broadcasting

short messages, and so on. Some restriction should be

configured on the OMMR: The priority of the TRX where the

CBCH is located must be smaller than or equal to 2.

[Unconditional TRX shutdown]

The cell’s TRX is configured to be shut down at a specific time

regardless of the traffic. To avoid influencing the user experience,

the users on the TRX already shut down should be handed over

to other cells. In addition, it can be configured that the traffic is

handed over to a specific cell when the TRX is shut down.


Impact on

Equipment

Performance

None

Impact on Network The unconditional TRX shutdown will cause the inter-cell



handover. If there is no suitable adjacent cell, the traffic will be

released within two minutes. There is no service accessed during

the BCCH TRX shutdown.

Hardware

RequirementNone

Impact on other



Relative Parameter

1. vsDataGGsmCell.PwDownLoadInd: Cell shuttingdown

based on traffic load

2. vsDataGGsmRelation.PwDownHoPriInd: Handover Priority

Indication when serve cell shuttingdown

3. Restriction: The priority of the TRX where the CBCH is

located must be smaller than or equal to 2.


Relative Alarm None

Verification

Improvement on the load dependent intelligent TRX shutdown:

1. Configure on the OMMR to make the cell support the

intelligent TRX shutdown; tick off the power shutdown time

bitmap; after some TRXs are intelligently shut down,

create the following scenarios to observe whether the

TRXs are powered on according to the reasons;

a) The SD channel request failure triggers the emergency

power-on; select the TCHF that is under shutdown

block only and has SD channel or supports dynamic

SD conversion for the TRX power-on;

b) The TCH channel request fails; when the emergency

power-on threshold is reached so that the emergency

power-on is triggered or the performance triggers the

power-on, select the TRX that is under shutdown block

only and has TCHF/TCHH channels for the TRX

power-on;

c) The PS channel request failure triggers the emergency

power-on; select the TRX that is under shutdown block

only and has dynamic TCHF or static PD channels for

the TRX power-on.

2. Configure on the OMMR to make the cell support the

intelligent TRX shutdown; tick off the power shutdown time



bitmap, and make some TRX failure by means of manual

block. Select the powered-down TRXs every 15 minutes

and check whether the blocked TRXs are powered down

first.

3. Configure the CBCH on the OMMR; modify the priority of

the TRX where it is located and check whether the

restriction exists: The priority of the TRX where the CBCH

is located must be smaller than or equal to 2.

Unconditional TRX shutdown

1. Configure on the OMMR to enable the cell to support the

CSL shutdown, that is, tick off the time bitmap; open the

TRX shutdown and cell shutdown switches; properly

configure Cell shuttingdown based on traffic load and

Handover Priority Indication when serve cell

shuttingdown;

2. There is no traffic in the cell; the 15min performance

granularity times out, shut down the TRX;

3. There is traffic in the cell; the 15min performance

granularity times out, shut down the TRX and the traffic

performs the inter-cell handover; if there exists the

adjacent cell whose Handover Priority Indication when

serve cell shuttingdown is set to Yes, the traffic will be

handed over to that cell with priority; if no proper adjacent

cells are found, the traffic will be released two minutes

after the shutdown.

Impact on other

featureNone

Note None

5.3.10 ZGO-04-04-007 Intelligent Cell Shutdown

Table 5-24 Intelligent Cell Shutdown

Description

[Improvement on the intelligent cell shutdown]

Configure upperlayer and lowerlayer cells. The lowerlayer cell

enables the intelligent cell shutdown. When there is congestion in

the upperlayer cell, if its power shutdown bitmap is not within the

lowerlayer cell’s power shutdown time bitmap, the lowerlayer



cell’s power-on will not be triggered. This feature modifies it - the

lowerlayer cell’s power-on will be triggered as long as there is

upperlayer cell congestion.


Impact on

Equipment

Performance

None


Hardware

RequirementNone

Impact on other

SystemNone




Relative Alarm None

Verification

The lowerlayer cell is configured a power shutdown time. In case

of the congestion in the upperlayer cell during the period that the

lowerlayer cell’s power is shut down, the lowerlayer cell’s power-

on will be triggered.

Impact on other

featureNone

Note None

5.3.11 ZGO-01-02-009 Traffic Based PDCH Expansion

Table 5-25 Traffic Based PDCH Expansion

Description

[Improvement on the uplink initial channel allocation algorithm]

The default configuration is that one timeslot is initially allocated

on the uplink. Multiple timeslots can be allocated when the uplink

rate requires to be boosted. This feature is applied to the

scenarios where the uplink rate is required to be tested. Multiple

timeslots are allocated at the service establishement.




Impact on

Equipment

Performance

None

Impact on Network

This feature is not suitable for the service which focuses on the

downlink. The period of resource adjustment can be configured.

When the period is shortened, a priority can be configured to the

downlink service. The default configuration is the downlink

service enjoys the priority. The switch can be open for testing.

Hardware

RequirementNone

Impact on other



Relative ParameterGPsChannelSchedule.InitMultiSlotPriDir: Initial piority direction of

multislot capability


Relative Alarm None

Verification

1. Set the InitMultiSlotPriDir in the R_PSBTSALLOC table to 0;

2. Use the MS to upload; verify whether multiple uplink multislot

timeslots are initially allocated;

3. Set the InitMultiSlotPriDir in the R_PSBTSALLOC table to 0;

4. Use the MS to upload; verify whether the number of uplink

timeslot initially allocated is 1.

Impact on other

featureNone

NoteThis feature is usually not enabled, but the related performance

tests can be enabled.

5.3.12 ZGO-01-03-005 Dual Transfer Mode

Table 5-26 Dual Transfer Mode

Description

[Improvement on the DTM]

This enhanced feature supports the DTM multislot Class 11

extended dynamic assignment, which improves the uplink

transmission performance. This feature supports the statistics of



DTM-mode voice traffic proportion and PS traffic proportion.


Impact on

Equipment

Performance

None

Impact on Network

This enhanced feature supports the DTM multislot Class 11

extended dynamic assignment, which improves the uplink

transmission performance.

Hardware

RequirementNone

Impact on other



Relative ParameterGCellPs.DTM11EDASup: DTM MultiSlot Class 11 extended

dynamic assign

Relative Counter

C901080072: DTM TCH/F busy time

C901080073: DTM TCH/H busy time

C901080074: Maximum number of busy DTM TCH/Fs

C901080075: Maximum number of busy DTM TCH/Hs

C901080076: Average number of busy DTM TCH/Fs

C901080077: Average number of busy DTM TCH/Hs

C901020093: Number of Bytes carried by UL LLC frames in

GPRS DTM mode

C901020094: Number of Bytes carried by DL LLC frames in

GPRS DTM mode

C901020095: Number of Bytes carried by UL LLC frames in

EGPRS DTM mode

C901020096: Number of Bytes carried by DL LLC frames in

EGPRS DTM mode

Relative Alarm None

Verification 1. Use the UE that is capable of DTM multislot Class 11 and

capable of higher order to initiate the voice service first, and

then upload the data;

2. Observe whether the timeslots assignment is UL3+DL2;

3. Use the DTM capable UE to initiate the DTM service;

4. Observe whether the voice service busy time and the



number of bytes carried by LLC frames in DTM-mode data

service conform to the servie property.

Impact on other

featureNone

Note None

5.3.13 ZGO-02-03-008 GSM/LTE Cell Reselection

Table 5-27 GSM/LTE Cell Reselection

Description

[Cell reselection estimation based on the E-UTRANRF quality]

When GSM/LTE networking, according to the R8 protocol, the

selection and reselection of the E-UTRAN cell depends on the

Reference Signal Receiving Power (RSRP) measurement.

But the RSRP does not reflect the interference on the cell. As a

result, in some cells of serious interference, the E-UTRAN cell

selected according to the RSRP is not proper for the UE to

reside. The 3GPP R9 enhances the E-UTRAN cell reselection;

in other words, the RSRQ is the reference for the E-UTRAN

cell selection and reselection. The GSM also imports the

corresponding CR.


Impact on

Equipment

Performance

None


Hardware

RequirementNone

Impact on other



Relative Parameter GPriorityResel.EUtranHighThreshQ: High RSRQ thresholds for

EUtran reselection

GPriorityResel.EUtranLowThreshQ: Low RSRQ thresholds for

EUtran reselection

GPriorityResel.EUtranQQUALMIN: Minimum RSRQ for EUtran



cells

GPriorityResel.EUtranQMIN: Minimum RSRQ for EUtran cells

based on RSRP

GPriorityResel.EutranRSRPMIN: Minimum RSRP RX level for

EUtran cells

GPriorityResel.EnhancedResParaInd: Enhanced Cell

Reselection Parameters Indication


Relative Alarm None

Verification

With this feature enabled, the BSC carries the enhanced E-

UTRAN cell reselection parameter in the system message

2Quater; when the UE reselects from the GSM cell to the E-

UTRAN cell, the RSRQ of the E-UTRAN cell is estimated;

when the RSRQ satisfies the cell reselection requirement, the

UE reselects the E-UTRAN cell.

Impact on other

featureNone

Note None

5.3.14 ZGO-04-02-016 PS Power Control

Table 5-28 PS Power Control

Description [Supports the PS power control on V3 BTSs]

The PS power control aims to reduce the power consumption

of the BTS and MS and to decrease the interference to other

subscribers in the network. The downlink closeloop power

control judges whether the current receiving signal quality is

within the expected range according to the receiving signal

level and quality, on the basis of which it decides whether

power control should be applied to the current receiving signal.

The previous versions support the downlink control on the

SDR-based BTS only; this version supports the downlink

control on V3 BTSs, the control strategy of which is identical to

that of the SDR-based BTS.

[Power control is preferred, and then the codec rate

adjustment]



The downlink adaptive codec algorithm controls the codec

method adjustment through continuously adjusting the times

threshold upward and downward. With the downlink PS power

control enabled, when the radio quality is good, the value range

of the parameter for continuous upward adjustment should be

expanded in order to try the power reduction first and then the

codec method adjustment.

Feature Num None

Impact on

Equipment

Performance

None

Impact on NetworkThis feature improves the RQ; the proportion of MCS9

decreases.

Hardware

RequirementNone

Impact on other

SystemNone




Relative Alarm None

Verification

Supports the PS power control on V3 BTSs:

Enable the downlink PS power control; initiate the PS service;

make the radio environment quality fluctuate to trigger the

power control decision; the downlink PCU frame of PF3 format

carries the related power control indicator; the BTS controls the

transmit power of the radio block according to this indicator; the

counter makes the statistics.

Power control is preferred, and then the codec rate adjustment:

Set the power minus downlink strength and quality N/P value to

2, which means 2 downlink acknowledgement makes a power

reduction decision;

Enable the downlink adaptive codec algorithm; set the times of

upward adjustment to 7, which means 7 downlink

acknowledgement makes a codec method adjustment decision;

Set the initial codec method to non MCS9; when the radio

quality is very good, decision can be made for several times



before the codec method adjustment rises; set a proper step

length; reduce the power to the bottom and then make the

codec method rise.

Impact on other

featureNone

Note This feature requires the support from V2 and V3 BTSs.

5.3.15 ZGO-02-02-004 SDCCH/SDCCH Handover

Table 5-29 SDCCH/SDCCH Handover

Description

[Improvement on the handover of short messages on the SD]

The handover during the process of sending short messages

used to double the call drop rate. This version improves this

feature. There is a switch to control whether the short

messages are allowed to perform the handover on the SD.


Impact on

Equipment

Performance

None

Impact on NetworkEnabling this switch effectively controls the call drop rate on the

SD.

Hardware

RequirementNone

Impact on other



Relative ParameterGBssFunctionOption.SMSHoOnSDForbid: Short Message

Handover on Sdcch Forbid


Relative Alarm None

Verification Open the smshoonsdforbid and SD handover switch on the

OMMR;

Adjust the related handover thresholds to make the handover

easier;



Create a long message and send;

No handover occurs during sending the message on the SD,

which indicates it has passed the test.

Impact on other

featureNone

Note None

5.3.16 ZGO-04-01-011 Power Boost for 8PSK

Table 5-30 Power Boost for 8PSK

Description

[Improvement on the conditions of power boost for 8PSK]

According to the previous version, when the static power level

is 0, the 8PSK power will not be boosted unless there is GMSK

power surplus on the same timeslot and the surplus should be

enough for boosting the 8PSK power by 2dB. Now, this feature

is enhanced. As long as the surplus is enough for boosting the

8PSK power by at least 0.5dB (by 2dB at most).


Impact on

Equipment

Performance

None

Impact on Network This feature enhances the EDGE service performance.

Hardware

RequirementNone

Impact on other

SystemNone


Relative Parameter vsDataGBssFunctio. PwrDynShareSupport: Enable power

dynamic sharing

GPwShare .PwrDynShare: Cell enable power dynamic sharing

or not

GPwShare/Inc8PskPwrThs: Threshold for Increase 8PSK

Power

GPwShare/Inc8PskPwrHys: Hysteresis for Increase 8PSK

Power



GPwShare/Inc8PskPwrDelay: Delay for Increase 8PSK Power

Relative Counter

C901940017: The count of 8PSK power increase due to power

enough

C901940018: Time of 8PSK power increase due to power

enough

Relative Alarm None

Verification

Make the power enough: Decrease the maximum transmit

power (the reference power) of the TRX or increase the

Threshold for Increase 8PSK Power or Hysteresis for Increase

8PSK Power;

The MS initiates the PS service in the EDGE cell;

Make the power on the RRU lower than the Threshold for

Increase 8PSK Power; verify whether the power is boosted by

2dB, 1.5 dB, 1dB and 0.5dB in turns;

Make the power on the RRU greater than the Threshold for

Increase 8PSK Power + Hysteresis for Increase 8PSK Power

(increase the maximum transmit power of the TRX or decrease

the Threshold for Increase 8PSK Power and Hysteresis for

Increase 8PSK Power);

The MS initiates the PS service in the EDGE cell;

Observe the OAM signaling in the signaling trace; observe the

RRU’s power reported by the SDR.

Criteria of passing:

When the power is enough, the 8PSK power is boosted by

0.5dB to 2dB in turns (corresponding to level 0 to level 4); the

channel power is enhanced as well; the power is no longer

boosted after it is boosted by level 4;

When the power is not enough, the 8PSK power is not boosted

and the power boost level is 0.

Impact on other

featureNone

Note None



5.3.17 ZGO-03-02-012 PS Channel Extension

Table 5-31 PS Channel Extension

Description

[PS channel extension based on the realtime traffic]

The BSC allocates one channel to the MS first; later, it

allocates multiple channels to the MS according to the traffic on

the uplink/downlink within a period (the period can be set on

the OMMR); when the timeslots allocated are not sufficient for

the MS’s multi-timeslot capability, the Resource adjust times

are modified to be configurable.


Impact on

Equipment

Performance

None

Impact on Network If the adjust time length is set to too short, the traffic might rise.

Hardware

RequirementNone

Impact on other



Relative Parameter

Parameters of type B:

GCellOption.RscAdjTimes: Resource adjust times

GCellOption.RscAdjTimeLen: Resource adjust time length


Relative Alarm None

Verification

Set the Resource adjust time length to different values. The

adjust time length from the initial single channel to the later

multiple channels is identical to the parameter configured;

when the timeslots allocated are not sufficient for the MS’s

multi-timeslot capability, the Resource adjust times are

identical to the parameter configured.

Impact on other

featureNone

Note None



5.3.18 ZGO-04-05-003 VAMOS Pairing and De-Pairing

Table 5-32 VAMOS Pairing and De-Pairing

Description

There is more processing aiming at the VAMOS II cellphones.

Under the pairing mode, inform the cellphones to go into the

VAMOS mode or quit the VAMOS mode after the pairing ends

through the signaling. This enables the cellphones to go into

their best working state under any mode.

Regarding the China Mobile’s test regulations, the pairing of

the assignment process is added, which enables the system to

support the assignment pairing and handover pairing

simultaneously. Moreover, handover from FR VAMOS to HR

VAMOS is added, which enables more users to be admitted

though the load is rising to a certain degree.

There is a new pair release quality algorithm to make the

pairing algorithm more proper. Initiate a pair release process as

fast as possible after the pair subscribers’s uplink or downlink

quality gets worse, which avoides the call drop.

There are some new parameters for the BTS, which enables

the power control & detection algorithm and pair release

algorithm of the BTS more flexible under the pairing mode.

There is a new IMEI solution, detecting the cellphones of the

same type as one capability. This solution reduces the number

of tests and reduces the influence on the network performance.

The system supports the IMEI solution and IMSI solution

simultaneously, providing operators with more choices.

Adjust the pairing priority for various kinds of cellphones

according to the test results, further improving the pairing and

system performance.

There are some new VAMOS counters to record the VAMOS

pairing and pair release processes and conditions of the

cellphones.


Impact on

Equipment

Performance

None

Impact on Network This feature enhances the VAMOS pairing success rate; it

enlarges the network capacity; but the pairing might influence



the network KPI.

Hardware

RequirementNone

Impact on other


License Control TRX

Relative Parameter

GVamos.PairReleaseLoadThr: The load of VAMOS pair

release

GVamos.SupportVamosHO: Support handover from VAMOS

FR to VAMOS HR

GVamos.PairRelUlQuaThr: Uplink receive quality of pair-

release threshold

GVamos.PairRelDlQuaThr: Downlink receive quality of pair-

release threshold

GVamos.PairRelUlQualP: P value of pair-release uplink quality

GVamos.PairRelUlQualN: N value of pair-release uplink quality

GVamos.PairRelDlQualP: P value of pair-release downlink

quality

GVamos.PairRelDlQualN: N value of pair-release downlink

quality

GVamos.PairOfFrAndHr: Pair of FR with HR

The R_BSC table has new parameters of type A2:

vsDataGBssFunction.MuteSaicDetNumP: P value of MUTE

SAIC MS capability detection

vsDataGBssFunction.MuteSaicDetNumN: N value of MUTE

SAIC MS capability detection

vsDataGBssFunction.SaicAfcDetNumP: P value of SAIC AFC

MS capability detection

vsDataGBssFunction.SaicAfcDetNumN: N value of SAIC AFC

MS capability detection

Relative Counter C902210017~C902210095

Relative Alarm None

Verification

Perform the pairing with a VAMOS II cellphone; verify whether

the cellphone is informed to change its channel mode through

the assignment command or mode change command sent

before and after the pairing;



Test according to the China Mobile’s test regulations;

Analyze the signaling during the pairing to verify whether pair

release occurs when the quality gets worse;

Test with a variety of cellphones to verify their capability; verify

whether the capability listed in the database IMEI is correct or

not;

Verify whether the network KPI is enhanced after the

optimization;

Verify whether the counters recorded are enough.

Impact on other

featureNone

Note None

5.3.19 ZGB-03-02-006 Dynamic Channel Management

Table 5-33 Dynamic Channel Management

Description

[Improvement on the CS’s preempting PS]

CS preempts PS. The weight after the preemption is modified,

which makes the PS continuity best after the preemption. CS

prefers to preempt the non-TA timeslot PS channel, which

reduces the PS service interruption.

Feature Num None

Impact on

Equipment

Performance

None

Impact on Network

This feature improves the PS service performance; each PS

subscriber is allocated more channels; the PS service

interruption is relieved.

Hardware

RequirementNone

Impact on other

System


Relative ParameterGPsChannelSchedule.CSPreemptPSOpti : Support CS

preempt PS optimization




Relative Alarm None

Verification

Make CS preempt one dynamic channel from PS successfully.

After this channel is preempted, the PS continuity is the best

compared with the condition that other channels are

preempted. The non-TA timeslot PS channel is preempted first.

Impact on other

featureNone

Note None

5.3.20 ZGO-04-01-007 Dynamic Power Sharing

Table 5-34 Dynamic Power Sharing

Description [Enhanced dynamic power sharing]

The previous version uses PwrAdmitThreshold to decide

whether the power on the timeslots is sufficient or not when

allocating channels. PwrAdmitThreshold indicates the

proportion of available power to the total power. But some on-

site application shows this parameter is not proper enough

since it is hard to set a definite value. Subscribers’ power

increase is achieved by the power control. And the power

increase is adjusted by the unit ‘dB’, which fails to correspond

to this parameter. What’s more, the power congestion is likely

to occur in some scenarios. For the reasons described above,

PwrAdmitThreshold is no longer used to decide the power

admission, PwrPres is used instead. Preserve some power (it

can be set according to the power control step length) for the

online subscribers. When calculating the timeslot’s power, add

the preserved power to the online CS users’ power, and

preserve some power for the newly accessed subscribers;

verify whether the total power exceeds the RRU’s power, which

decides whether channels can be allocated.

In terms of the power sharing, the BCCH and TCH are

expected to use their maximum transmit power. But actually,

there is another situation, that is, the BCCH power does not

rise but the TCH power rises when necessary (such as in some

areas of poor coverage). When the initial power optimization is



enabled, the initial downlink power can be estimated; when the

initial power optimization is not enabled, the maximum power of

the TRX is used currently, which is not proper enough. It’s

better to use the same transmit power as that of the BCCH.

Currently, the channel is not activated by the unit ‘0.5dB’ but by

the unit ‘2dB’ instead. In actual application, the BCCH power is

usually lower than that of the BCCH by 2dB. When the initial

power optimization is not enabled, decrease the transmit power

by 2dB if the maximum power of the TCH is higher than that of

the BCCH.


Impact on

Equipment

Performance

None

Impact on Network This feature relieves the channel congestion.

Hardware

RequirementNone

Impact on other

SystemNone


Relative Parameter

The following parameters are deleted:

GPwShare.PWRADMITTHRESHOLD

GPwShare.PWRADMITTHRLDPUNISH

GPwShare.PWRADMITPUNISHTIME

The following is the new parameter:

GPwShare. PdPwrResumeDelay: Delay for Resume PDTCH

Power


Relative Alarm None

Verification

Enable the dynamic power sharing; observe the power

admission on a single timeslot to verify whether it conforms to

what this feature describes; when the initial power optimization

is not enabled, the setting of the initial power conforms to what

this feature describes.

Impact on other

featureNone



Note None

5.3.21 ZGO-03-02-003 Enhancement on PS Channel Allocation

Table 5-35 Enhancement on PS Channel Allocation

Description

[Supports the discontinuous PDTCH allocation]

In the previous versions, when allocating the multi-timeslot PS

channels, only the continuous PDCHs or idle dynamic channels

are allocated. When abundant dynamic channels are

configured, discontinuous PDCHs and discontinuous idle

dynamic channels are common. When allocating PS channels,

no timeslot combination of multi-timeslot can be formed. This

feature enables to allocate more PDTCHs though the PS

channels or the idle dynamic channels are discontinuous. With

the multi-timeslot capability ensured, only the busy CS

channels are excluded.


Impact on

Equipment

Performance

None

Impact on Network

This feature enhances the PS service transmission. With more

timeslots allocated to each subscriber, the total number of

subscribers accessed decreases, which causes heavier PS

channel congestion and higher PS drop rate.

Hardware

RequirementNone

Impact on other

SystemNone


Relative ParameterGPsChannelSchedule.DisContinuAllocSup Support the

discontinuous PDTCH allocation


Relative Alarm None

Verification Configure the timeslots 1/3/4 to PS channels on the TRX;

Close the Support the discontinuous PDTCH allocation switch;



have the PS service accessed; observe whether all the 1/3/4

timeslots are allocated; the negative result is a normal result;

Open the Support the discontinuous PDTCH allocation switch;

have the PS service accessed; observe whether all the 1/3/4

timeslots are allocated; the positive result is a normal result.

Impact on other

featureNone

Note Keep an eye on the PS channel congestion and other KPIs.

5.4 Other Improvements & Optimization

5.4.1 New Counters

5.4.1.1 Separate Counters for Collecting Assignment Failure Statistics

Table 5-36 Separate Counters for Collecting Assignment Failure Statistics

Function

Description

In the TCH/F and TCH/H measurement, the statistics of

handover failures are collected on different counters per the

failures with/without handover failure message returned, in the

classifications of signaling, speech, and data messages; but

the statistics collection of assignment failures are not divided in

this way. Therefore, an improvement is made to separate the

statistics collection of assignment failures per the failures

with/without failure message returned.

The counters for the signaling/speech/data TCH assignment

failures with/without failure message returned are added; the

immediate assignment failures (signaling) are all collected as

the failures without failure message returned. As for the MSC-

triggered assignments, the method for distinguishing the

assignment failures with/without failure message returned is

the same as that for handover failures; if the assignment failure

message is received on the same channel, it is regarded as a

failure with failure message returned; for other cases, including

T3107 expiration, forced disconnection, abnormal release, etc.,

they are all collected as the failure without failure message



returned; in application, the failure focuses on T3107

expiration.

For SDCCH, no new counter is added, because the SDCCH

assignments are basically all immediate assignments.

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

Performance

None

Hardware

Dependence None

Influence on

Associated NE

Interface

None


Associated

ParametersNone

Associated

Counters

C902510133 Number of signaling TCH/F assignment failure

with the assignment failure message returned from MS

C902510134 Number of signaling TCH/F assignment failure

without the assignment failure message returned from MS

C902510135 Number of voice TCH/F assignment failure with

the assignment failure message returned from MS

C902510136 Number of voice TCH/F assignment failure


C902510137 Number of data TCH/F assignment failure with


C902510138 Number of data TCH/F assignment failure


C902520115 Number of signaling TCH/H assignment failure

with the assignment failure message returned from MS

C902520116 Number of signaling TCH/H assignment failure


C902520117 Number of voice TCH/H assignment failure with




C902520118 Number of voice TCH/H assignment failure


C902520119 Number of data TCH/H assignment failure with


C902520120 Number of data TCH/H assignment failure


Associated Alarms

& NotificationsNone

Verification Plan &

Criteria

Create the measurement task in OMCB performance

measurement.

Create the signaling channel of immediate assignment, but the

MS fails to access the channel; send TCH assignment of

CS/PS service, but the MS returns the failure message on the

same channel or loses connection; and observe the

corresponding counters, which can collect the statistics

accurately.

Influence on Other

FunctionsNone

Matters for

Attention None

5.4.1.2 Improvement on Collection of Adjacent Cell Relation Measurement

Statistics

Table 5-37 Improvement on Collection of Adjacent Cell Relation Measurement Statistics

Function

Description

Counters are added to view the number of handover failure

with MS returned to the original channel/cell.

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

Performance

None

Hardware None



Dependence

Influence on

Associated NE

Interface

None


Associated

ParametersNone

Associated

Counters

C901100044 Number of handover failure to the adjacent cell

lead to return

C901090267 Number of handover failure to the adjacent cell

lead to return

Associated Alarms

& NotificationsNone

Verification Plan &

Criteria

1. Close the new switch and start location update, MR is not

reported.

2. Open the new switch and start location update, MR is

reported.

Influence on Other

FunctionsNone

Matters for

AttentionNone

5.4.1.3 Handover Type-based Classification of Counters for Call Drops due to

Handover Failures

Table 5-38 Handover Type-based Classification of Counters for Call Drops due to

Handover Failures

Function

Description

New counters classified per handover types are added; we can

view the counters in the case of call drops caused by handover

failures.

Function SN. None

Influence on

Equipment

Performance

None

Influence on None



Network

Performance

Hardware

DependenceNone

Influence on

Associated NE

Interface

None


Associated

ParametersNone

Associated

Counters

C901070136 Number of SDCCH drops due to intra-cell

handover failure

C901070137 Number of Speech TCH/F drops due to intra-cell

handover failure

C901070138 Number of Data TCH/F drops due to intra-cell

handover failure

C901070139 Number of signaling TCH/F drops due to intra-cell

handover failure

C901070140 Number of Speech TCH/H drops due to intra-cell

handover failure

C901070141 Number of Data TCH/H drops due to intra-cell

handover failure

C901070142 Number of signaling TCH/H drops due to intra-

cell handover failure

C901070143 Number of SDCCH drops due to inter-cell

handover failure

C901070144 Number of Speech TCH/F drops due to inter-cell

handover failure

C901070145 Number of Data TCH/F drops due to inter-cell

handover failure

C901070146 Number of signaling TCH/F drops due to inter-cell

handover failure

C901070147 Number of Speech TCH/H drops due to inter-cell

handover failure

C901070148 Number of Data TCH/H drops due to inter-cell

handover failure

C901070149 Number of signaling TCH/H drops due to inter-



cell handover failure

C901070150 Number of SDCCH drops due to outgoing

handover failure

C901070151 Number of Speech TCH/F drops due to outgoing

handover failure

C901070152 Number of Data TCH/F drops due to outgoing

handover failure

C901070153 Number of signaling TCH/F drops due to outgoing

handover failure

C901070154 Number of Speech TCH/H drops due to outgoing

handover failure

C901070155 Number of Data TCH/H drops due to outgoing

handover failure

C901070156 Number of signaling TCH/H drops due to

outgoing handover failure

Associated Alarms

& NotificationsNone

Verification Plan &

Criteria

Start CS/PS service, and create call drops caused by intra-cell,

inter-cell, and outgoing handovers on SDCCH/TCHF/TCHH

respectively, and check whether the relevant counters are

accurate.

Influence on Other

FunctionsNone

Matters for

AttentionNone

5.4.1.4 Optimization of Statistics Collection of Call Drops due to Handovers

Table 5-39 Optimization of Statistics Collection of Call Drops due to Handovers

Function

Description

The current statistics collection mechanism of the call drops due to

handovers collects the statistics of call drop due to intra-cell handover

failure, call drop due to intra-BSC handover failure, and call drop due

to inter-BSC handover failure in one counter. Now the call drops are

subdivided per handover types. The statistics of call drops due to

intra-cell handovers in CoBCCH cell are classified per channel types

(SDCCH, TCH/F, TCH/H) and channel mode (speech, data,



signaling).

For the convenience of troubleshooting and network planning &

optimization, the counter for call drops due to inter-cell handover

failure is added in the adjacent cell handover measurement.

Function

SN.None

Influence on

Equipment

Performanc

e

None

Influence on

Network

Performanc

e

None

Hardware

DependenceNone

Influence on

Associated

NE Interface

None

License

ControlNone

Associated

ParametersNone

Associated

Counters

C901070157 Number of Speech TCH/F drops due to subcell1 to

subcell2 handover failure

C901070158 Number of Data TCH/F drops due to subcell1 to subcell2

handover failure

C901070159 Number of Signal TCH/F drops due to subcell1 to


C901070160 Number of Speech TCH/H drops due to subcell1 to


C901070161 Number of Data TCH/H drops due to subcell1 to


C901070162 Number of Signal TCH/H drops due to subcell1 to


C901070163 Number of Speech TCH/F drops due to subcell2 to




C901070164 Number of Data TCH/F drops due to subcell2to subcell1

handover failure

C901070165 Number of Signal TCH/F drops due to subcell2 to


C901070166 Number of Speech TCH/H drops due to subcell2 to


C901070167 Number of Data TCH/H drops due to subcell2 to


C901070168 Number of Signal TCH/H drops due to subcell2 to


C901070169 Number of TCH/F drops due to InterCell handover to

subcell1 failure

C901070170 Number of TCH/F drops due to InterCell handover to

subcell2 failure

C901070171 Number of TCH/H drops due to InterCell handover to

subcell1 failure

C901070174 Number of TCH/H drops due to InterCell handover to

subcell2 failure

C901100048 Number of SDCCH drops due to handover failure to this

cell

C901100049 Number of Speech TCH drops due to handover failure to

this cell

C901100050 Number of Data TCH drops due to handover failure to

this cell

C901100051 Number of Signal TCH drops due to handover failure to

this cell

C901100052 Number of Speech TCH/F drops due to handover failure

to this cell

C901100053 Number of Data TCH/F drops due to handover failure to

this cell

C901100054 Number of Signal TCH/F drops due to handover failure

to this cell

C901100055 Number of Speech TCH/H drops due to handover failure

to this cell

C901100056 Number of Data TCH/H drops due to handover failure to

this cell

C901100057 Number of Signal TCH/H drops due to handover failure

to this cell



Associated

Alarms &

Notifications

None

Verification

Plan &

Criteria

Create the handover from sub-cell1 to sub-cell2, and make the call

drop through interference, and observe whether the counter is

accurate is not.

Create the handover from sub-cell2 to sub-cell1, and make the call

drop through interference, and observe whether the counter is

accurate is not.

Create inter-cell handover within one BSC with the target cell to be a

CoBCCH cell, and make the call drop through interference, and

observe whether the counter is accurate or not.

Create inter-cell handover, and make the call drop through

interference, and observe whether the counter is accurate or not.

Influence on

Other

Functions

None

Instructions None

5.4.1.5 Statistics Collection of Call Drops per Handover Causes

Table 5-40 Statistics Collection of Call Drops per Handover Causes

Function

Description

About 1/3 of the call drops in the current network are HO call

drops. There are various causes of handover, but there is only

one counter of call drop due to handover failure in the call drop

measurement, which makes it impossible to evaluate the

handovers in details or for the R&D engineers to further

research the call drops due to handover failure. In order to

solve this kind of problem, the function of distinguishing the

handovers according to their causes is added in BSC.

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

It will be convenient for the user and R&D engineers to check

the causes of HO call drops.



Performance

Hardware

DependenceNone

Influence on

Associated NE

Interface

None


Associated

ParametersNone

Associated

Counters

C901070216 Number of HO drops due Interf UL

C901070217 Number of HO drops due Interf DL

C901070218 Number of HO drops due QUAL UL

C901070219 Number of HO drops due QUAL DL

C901070220 Number of HO drops due LEVEL UL

C901070221 Number of HO drops due LEVEL DL

C901070222 Number of HO drops due RAPID UL

C901070223 Number of HO drops due PBGT

C901070224 Number of HO drops due MICRO to MICRO

C901070225 Number of HO drops due SUB Cell1 to SUB Cell2

C901070226 Number of HO drops due SUB Cell2 to SUB Cell1

C901070227 Number of HO drops due PREEMPT

C901070228 Number of HO drops due TRAFFIC

C901070229 Number of HO drops due DLRAPID

C901070230 Number of HO drops due HRFR

C901070231 Number of HO drops due RAPIDQUAL

C901070232 Number of HO drops due Dual Frequency Traffic

C901070233 Number of HO drops due Downlink Signal Quality

C901070234 Number of HO drops due Long Distance between

MS and Network

C901070235 Number of HO drops due Directed Retry

C901070236 Number of HO drops due Enquired Handover

Candidate

C901070237 Number of HO drops due Directed Force Move

C901070238 Number of drop call on SDCCH due to syn meas

Trx

C901070239 Number of drop call on TCH/F due to syn meas



Trx

C901070240 Number of drop call on TCH/H due to syn meas

Trx

Associated Alarms

& NotificationsNone

Verification Plan &

Criteria

Start a call and make the call drop, and check whether the

counter for call drop due to the cause is accurate or not.

Influence on Other

FunctionsNone

Matters for

AttentionNone

5.4.1.6 Adding Collection of Assignment Attempt/Success/Failure Statistics for

CN Secondary Assignment in iBSC

Table 5-41 Adding Collection of Assignment Attempt/Success/Failure Statistics for CN

Secondary Assignment in iBSC

Function

Description

New counters are added. When the secondary assignment

function is enabled in CN, we can view the assignment

attempt/success/failure statistics of the secondary assignment.

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

Performance

None

Hardware

DependenceNone

Influence on

Associated NE

Interface

None


Associated

ParametersNone



Associated

Counters

C901050078 Number of voice TCH/F second assignment

attempts


success


failure

C901050081 Number of data TCH/F second assignment

attempts


success


failure

C901050084 Number of voice TCH/H second assignment

attempts


success


failure

C901050087 Number of data TCH/H second assignment

attempts


success


failure

Associated Alarms

& NotificationsNone

Verification Plan &

Criteria

Start the secondary assignments, including CS and PS service,

on TCHF and TCHH respectively, and check whether the

relevant counters are accurate.

Influence on Other

FunctionsNone

Matters for

AttentionNone



5.4.1.7 Adding Statistics Collection of Releases Initiated by Users between

Assignment/Handover Attempt and Assignment/Handover Implementation

Table 5-42 Adding Statistics Collection of Releases Initiated by Users between

Assignment/Handover Attempt and Assignment/Handover Implementation

Function

Description

New counters are added. We can view the statistics of releases

initiated by users between assignment/handover attempt and

assignment/handover implementation.

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

Performance

None

Hardware

DependenceNone

Influence on

Associated NE

Interface

None


Associated

ParametersNone

Associated

Counters

C901050074 User/MSC release Number during voice TCH/F

assignment

C901050075 User/MSC release Number during data TCH/F

assignment

C901050076 User/MSC release Number during voice TCH/H

assignment

C901050077 User/MSC release Number during data TCH/H

assignment

C901090268 User/MSC release Number during BSC-

controlled inter-cell incoming handover

C901090269 User/MSC release Number of MSC-controlled

outgoing handover

Associated Alarms None



& Notifications

Verification Plan &

Criteria

Start CS/PS service, and hang up the call during the

assignment process. Check whether the relevant counter is

accurate or not.

Start CS/PS service, perform intra-cell handover or outgoing

handover, and hang up the call during the handover process.

Check whether the relevant counter is accurate or not.

Influence on Other

FunctionsNone

Matters for

AttentionNone

5.4.1.8 Adding Counters for Directed Retry

Table 5-43 Adding Counter for Directed Retry

Function

Description

The existing counters for directed retry are improved and new

counters are added, so that the consistency of statistics

collected is guaranteed. The principle of statistics collection is

that the statistics of both directed retry success and failure are

only collected in the original cell; and one directed retry

process is counted only once (even when there are multiple

target cells contained in the process), and the target cell is not

counted repeatedly in statistics.

Based on the causes, directed retry can be divided into forced

directed retry and normal directed retry. Based on the types,

directed retry can be divided into internal directed retry and

external directed retry. The more detailed statistics collection

of directed retry in different types can provide the data support

for improving call quality and reducing call drops on site.

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

Performance

None



Hardware

DependenceNone

Influence on

Associated NE

Interface

None


Associated

ParametersNone

Associated

Counters

C902460001—C902460070

C901050090 Number of voice assignment failure for directed

retry

C901050091 Number of data assignment failure for directed

retry)

C901100045 Number of directed retry attempts from adjacent

cell to the selected cell

C901100046 Number of directed retry from adjacent cell to the

selected cell

C901100047 Number of directed retry success from adjacent

cell to the selected cell

Associated Alarms

& NotificationsNone

Verification Plan &

Criteria

Enable and start the directed retry, and check whether the

relevant counter is accurate or not.

Influence on Other

FunctionsNone

Matters for

AttentionNone

5.4.1.9 Counter for Statistics of Paging Message in Smaller Granularity

Table 5-44 Counter for Statistics of Paging Message in Smaller Granularity

Function

Description

This function is used to locate the problem caused by the burst

of paging messages. BSC provides the statistics of peak

values of the number of paging messages sent by CN during a

statistics collection cycle, which means the minimum unit (1s)



of time granularity that can be configured.

Function SN. None

Influence on

Equipment

Performance

When the statistics collection cycle is smaller than the default,

the statistics of peak values collected during the smaller

granularity are more accurate, but the CPU load is increased

accordingly. It is recommended that the engineers on site

should make adjustments according to the actual situations.

Influence on

Network

Performance

None

Hardware

DependenceNone

Influence on

Associated NE

Interface

OMMR configuration parameters are added.


Associated

Parameters

Class-B Parameters:

GBssFunctionOption.pagingcapacity: paging capacity

GBssFunctionOption.pagingpeakcycle: Statistical Cycle of

Paging Peak

Associated

Counters

C901280105 peak of CS Paging messages from CN

C901280106 peak of CS Paging messages from SGSN

C901280107 peak of PS Paging messages from SGSN

C901280108 peak of Paging messages

C901280109 Timer of Paging reached the threshold

Associated

Alarms &

Notifications

None

Verification Plan

& Criteria

Configure the pagingcapacity and pagingpeakcycle parameter

in OMMR, and synchronize the configuration to iBSC.

Send paging messages, and check the signaling trace and

performance statistics.

The statistics collected on counters are consistent with the

actual situations.

Influence on

Other FunctionsNone



Matters for

AttentionNone

5.4.1.10 Adding Counter for Statistics of Paging Message Overflow in Cell

Table 5-45 Counter for Statistics of Paging Message Overflow in Cell

Function

Description

The BTS reports the statistics of discarded paging messages in

cell.

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

Performance

None

Hardware

DependenceNone

Influence on

Associated NE

Interface

None


Associated

ParametersNone

Associated

Counters

C902630001 Number of PS paging message

discarded

C902630002 Number of CS paging message

discarded

Associated

Alarms &

Notifications

None

Verification Plan

& CriteriaNone

Influence on

Other FunctionsNone

Matters for None



Attention

5.4.1.11 Adding Counter for the Number of Dynamic SD Translation Times

Table 5-46 Counter for the Number of Dynamic SD Translation Times

Function

Description

The counters for the statistics of dynamic SD translation, including

the statistics of available/unavailable/idle dynamic/static SD

channels, are added, which is convenient for the evaluation of the

use of SD channels.

Function

SN.None

Influence on

Equipment

Performanc

e

None

Influence on

Network

Performanc

e

None

Hardware

DependenceNone

Influence on

Associated

NE Interface

None

License

ControlNone

Associated

ParametersNone

Associated

Counters

C901080065 Number of translating TCH to SDCCH

C901080066 Number of translating SDCCH to TCH

C901080067 Average number of idle SDCCHs

C901080068 Average number of idle defined SDCCHs

C901080069 Average number of available dynamic

SDCCHs

C901080070 Average number of idle dynamic SDCCHs



C901080071 Average number of dynamic SDCCHs not

available

Associated

Alarms &

Notifications

None

Verification

Plan &

Criteria

Support the dynamic SD function through configuration.

Start CS services in a large amount to trigger the dynamic SD

translation, and observe the accuracy of the counters.

Influence on

Other

Functions

None

Matters for

AttentionNone

5.4.1.12 Collecting UL/DL RQ per RRU for Scenario of Multiple RRUs Sharing One

Cell

Table 5-47 Collecting UL/DL RQ per RRU for Scenario of Multiple RRUs Sharing One

Cell

Function

Description

For the convenience of analyzing performance per RRU in the

case of multi-carrier combination, report of RRU information is

added in some Abis interface UL messages. In this way, the

corresponding RQ statistics can be collected per the PA

channel No. of RRU.

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

Performance

None

Hardware

DependenceNone

Influence on

Associated NE

None



Interface


Associated

ParametersNone

Associated

Counters

C902450001 Number of samples with UL RQ = 0

on SDCCH


on SDCCH


on SDCCH


on SDCCH


on SDCCH


on SDCCH


on SDCCH


on SDCCH

C902450009 Number of samples with DL RQ = 0

on SDCCH


on SDCCH


on SDCCH


on SDCCH


on SDCCH


on SDCCH


on SDCCH


on SDCCH




on TCH


on TCH


on TCH


on TCH


on TCH


on TCH


on TCH

C902450024 Number of samples with UL RQ = 7 on TCH

C902450025 Number of samples with DL RQ = 0 on TCH








Associated

Alarms &

Notifications

None

Verification Plan

& Criteria

Configure multi-carrier combination for SDR, and open the RQ

measurement task. Check for the RQ measurement data

collected per the PA channel No. of RRU.

Influence on

Other FunctionsNone

Matters for

AttentionNone



5.4.1.13 Adding Counters for Peaks/Averages of UPPB Buffer

Table 5-48 Adding Counters for Peaks/Averages of Buffer

Function

Description

New counters for the peaks and averages of UPPB buffer are

added. With the statistics of peaks and averages collected on

the counters, we can adjust the configured number of LLC

frames allowed to be cached and transferred by each BSSGP

instance.

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

Performance

None

Hardware

DependenceNone

Influence on

Associated NE

Interface

None


Associated

ParametersNone

Associated

Counters

C901020085 Maximum number of LLC Store In

Bssgp

C901020086 Sum of LLC Store In Bssgp

C901020087 Sample of BSSGP Inst

C901020088 Sum of Max LLC Store In Bssgp

C901020089 Maximum number of LLC Trans In

Bssgp

C901020090 Sum of Max LLC Trans In Bssgp

C901020091 Sample of BSSGP Trans

C901020092 Sum of number due to LLC Trans

reach MAX

Associated

Alarms &

None



Notifications

Verification Plan

& Criteria

Perform a test on LLC frame transfer, and check whether the

above counters are accurate.

Influence on

Other FunctionsNone

Matters for

AttentionNone

5.4.1.14 Separate Statistics Collection of PS Channel Types

Table 5-49 Separate Statistics Collection of PS Channel Types

Function

Description

The counters for the use of PS resources are added in cell for

the convenience of collecting and analyzing PS resources and

optimizing network performance.

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

Performance

None

Hardware

DependenceNone

Influence on

Associated NE

Interface

None


Associated

ParametersNone

Associated

Counters

C901040098 Number of available no preferred

static PDCH

C901040099 Number of available gprs preferred

static PDCH

C901040100 Number of available egprs preferred

static PDCH



C901040101 Number of available only egprs

static PDCH

C901040102 Number of unavailable no preferred

static PDCH

C901040103 Number of unavailable gprs

preferred static PDCH

C901040104 Number of unavailable egprs

preferred static PDCH

C901040105 Number of unavailable only egprs

static PDCH

C901040106 Number of available no preferred

dynamic PDCH

C901040107 Number of available gprs preferred

dynamic PDCH

C901040108 Number of available egprs preferred

dynamic PDCH

C901040109 Number of unavailable no preferred

dynamic PDCH

C901040110 Number of unavailable gprs

preferred dynamic PDCH

C901040111 Number of unavailable egprs

preferred dynamic PDCH

Associated

Alarms &

Notifications

None

Verification Plan

& Criteria

Modify the service preference type of timeslot and perform PS

service, and check whether the above counters are accurate.

Influence on

Other FunctionsNone

Matters for

AttentionNone

5.4.1.15 Adding Counters for Average No. of PDCH Allocated to TBF

Table 5-50 Adding Counters for Average No. of PDCH Allocated to TBF

Function This function collects the average number of PDCH allocated



Description to each UL/DL TBF.

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

Performance

None

Hardware

DependenceNone

Influence on

Associated NE

Interface

None


Associated

ParametersNone

Associated

Counters

C901044301 Average number of PDCH allocated

per UL TBF

C901044303 Average number of PDCH allocated

per DL TBF

Associated

Alarms &

Notifications

None

Verification Plan

& Criteria

Perform services of different types, and observe whether the

above counters are accurate.

Influence on

Other FunctionsNone

Matters for

AttentionNone



5.4.1.16 Adding Collection of PDTCH Congestion Ratio of Unsatisfied MS Multi-

timeslot Processing Ability

Table 5-51 Adding Collection of PDTCH Congestion Ratio of Unsatisfied MS Multi-

timeslot Processing Ability

Function

Description

This function collects the number of UL/DL requests for PDCH

and the number of allocated channels failing to satisfy the

multi-timeslot processing ability, and calculates the ratio of the

latter to the former.

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

Performance

None

Hardware

DependenceNone

Influence on

Associated NE

Interface

None


Associated

ParametersNone

Associated

Counters

C901040089 UL Request PDCH Times

C901040090 UL unsatisfied PDCH Times

C901040091 DL Request PDCH Times

C901040092 DL unsatisfied PDCH Times

Associated

Alarms &

Notifications

None

Verification Plan

& Criteria

Configure the number of available channels to satisfy/unsatisfy

the MS multi-timeslot processing ability.

Perform services under the two circumstances above, and

observe the values of UL Request PDCH Times, UL unsatisfied

PDCH Times, DL Request PDCH Times, and DL unsatisfied



PDCH Times under each situation.

The results on counters are consistent with the facts.

Influence on

Other FunctionsNone

Matters for

AttentionNone

5.4.2 Changes to Performance Counters

5.4.2.1 Change to Congestion Duration Counter

Table 5-52 Change to Congestion Duration Counter

Function

Description

For the previous mechanism of collecting the channel

congestion duration, if the cell is not congested before it is

blocked, then there won’t be channel application failure or

congestion after the cell is blocked. If the cell is congested

before it is blocked, then the cell cannot clear the congestion

through applying for channels after it is blocked, and it will

remain congested. Therefore, the cell congestion is decided by

the cell status before it is blocked, which is random and

unreasonable. A change is made that SDCCH/TCHF/TCHH

channels are not collected in the congestion statistics after the

cell is blocked. Here the cell block is regarded as the BCCH

block. Other situations like CCCH congestion alone are not

considered.

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

Performance

The channel congestion duration collected in abnormal

circumstance is reduced.

Hardware

DependenceNone

Influence on

Associated NE None



Interface


Associated

ParametersNone

Associated

Counters

C901080006 SDCCH congestion time

C901080018 TCH/H congestion time

C901080027 TCH/F congestion time

Associated

Alarms &

Notifications

None

Verification Plan

& Criteria

When cell fails to apply for channel and causes congestion

(SDCCH/TCHF/TCHH), block the cell and check the relevant

counters. The congestion time is no longer collected on the

counters.

Influence on

Other FunctionsNone

Matters for

AttentionNone

5.4.2.2 PDused Statistics Counting Method Improved

Table 5-53 PDused Statistics Counting Method Improved

Function

Description

Modify the related switches to modify the value of the following

counters:

C901040017 Average number of used PDCH

C901040058 Average used number of uplink PDCH

C901040059 Average used number of downlink

PDCH

When the related switches are enabled, the above three

counters counts the time from channel release to channel

refreshing.

Function SN. None

Influence on

Equipment

Performance

None



Influence on

Network

Performance

The number of used channels is increased.

Hardware

Dependence None

Influence on

Associated NE

Interface

None

License Control Yes

Associated

Parameters

Class-B Parameters:

GBssFunctionOption.pdusedmeactrl: (for both

uplink and downlink) Pdch Used Measure Control

GBssFunctionOption.PDUsedMeaCtrlUl: (for

uplink) Pdch Used Measure Control for uplink

GBssFunctionOption.PDUsedMeaCtrlDl: (for

downlink) Pdch Used Measure Control for

downlink

Associated

Counters

C901040058: Average used number of uplink

PDCH

C901040059: Average used number of downlink

PDCH

C901040017: Average number of used PDCH

Associated

Alarms &

Notifications

None

Verification Plan

& Criteria

Perform different services (with several mobiles), modify the

values of the switches, and observe whether the values of the

counters are correct.

Influence on

Other FunctionsNone

Matters for

Attention None



5.4.2.3 PDCH Multiplexing Improved

Table 5-54 PDCH Multiplexing Improved

Function

Description

Collect TBF multiplexing related statistics more accurately.

1. Controlled by a switch

C901040008 Total number of PDCH used by all

TBF C901040017 Average number of used PDCH

C901040065 Average number of all TBF used

total downlink PDCH

C901040059 AV num used downlink PDCH

2. In the counting process, whether to multiply the following

counters by 100 times is controlled by a switch to make

sure the error is controlled within 0.01.


TBF



total uplink PDCH


total downlink

C901040058 AV num used uplink PDCH


3. Modify the following counters to accumulate by time.

C901040054 Total number of uplink PDCH used by

all TBF


total uplink PDCH

C901040058 AV num used uplink PDCH

C901040055 Total number of downlink PDCH used

by all TBF


total downlink PDCH



TBF


Function SN. None

Influence on None



Equipment

Performance

Influence on

Network

Performance

The preciseness of PDCH multiplexing is improved.

Hardware

Dependence None

Influence on

Associated NE

Interface

None

License Control Yes

Associated

Parameters

Class-B Parameters:

1. GBssFunctionOption.pdchrpfprecspromote:

Promotion of PDCH RPF Precision

2. GBssFunctionOption.pdchrpfopt: Optimization

of PDCH RPF

Associated

Counters

C901040058: Average used number of uplink

PDCH

C901040059: Average used number of downlink

PDCH

1. C901040017: Average number of used PDCH

2. C901040056: Sample number of uplink PDCH

used by all TBF


used by all TBF


used by all TBF

5. C901040065: Average number of total

downlink PDCH used by all TBF

Associated

Alarms &

Notifications

None

Verification Plan

& Criteria

Perform different services (with several mobiles), modify the

values of the switches, and observe whether the values of the

counters are correct.

Influence on

Other FunctionsNone



Matters for

Attention None

5.4.2.4 Dummy Block Counting Method Modified

Table 5-55 Dummy Block Counting Method Modified

Function

Description

In the RLC NEW BLOCK statistics of the current version, the

percent of CS1 and MCS7 is too high because of the following

points: the delayed/released dummy blocks are counted as RLC

NEW BLOCK, the dummy blocks under GPRS TBF are sent by

CS1 coding fixedly and are counted as CS1, and the dummy

blocks under EDGE TBF are sent by MCS5 coding fixedly and

are counted as MCS7. Now the following modifications are

made:

For GPRS dummy blocks, add a switch on BSC. This switch has

two values, i.e., uncounted and counted as CS1.

For EDGE dummy blocks, add a switch on BSC. This switch has three

values, i.e., uncounted, counted as CS1, and counted as MCS7.

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

Performance

High-order coding rate and throughput will be affected.

Hardware

Dependence

None

Influence on

Associated NE

Interface



Associated

Parameters

Class-B Parameters:

1. GBssFunctionOption.GprsDummyBlkCtrl: Gprs

Dummy Block Control

2. GBssFunctionOption.EgprsDummyBlkCtrl: Egprs

Dummy Block Control



Associated

Counters

None

Associated Alarms

& Notifications

None

Verification Plan &

Criteria

In GPRS service, when dummy blocks are sent, modify the value

of the switch to “1” and see whether the number of the DUMMY

counter in RLC will keep increasing. Then, modify the value to “0”

and see whether the increased number is consistent with that in

packet capturing.

In the transmission of dummy blocks in EGPRS service, modify

the value of the switch to “0.” The current coding mode is MCS5,

which is counted as MCS7. When the value is modified to “1,”

MCS5 is counted as MCS5. When it is modified to “2,” MCS5 will

not be counted. Capture packets to see whether the counter is

consistent with what is expected.

Influence on Other

Functions

None

Matters for

Attention

None

5.4.2.5 Link Establishment Counting on Downlink CCCH Improved

Table 5-56 Link Establishment Counting on Downlink CCCH Improved

Function

Description

In earlier versions, when TBF is established on downlink

CCCH, if the link establishment fails, one request and one

failure will be counted on the CCCH. If cache-state link

reestablishment function is supported, BSC will initiate a

second TBF establishment flow on CCCH. When the link

reestablishment succeeds, the counter will counts one request

and one successful establishment on CCCH. If it fails, no

counting will be performed. From the perspective of users, they

initiate only one request, and it will either succeed or fail. By

the current counting method, if the link establishment succeeds

directly, the counter will count one request and one successful

establishment. If it fails while cache-state reestablishment

succeeds, the counter will count two requests and one

successful establishment. If both direct link establishment and



cache-state link reestablishment fail, the counter will count one

request and one establishment failure. For successful cache-

state reestablishment, the counter actually counts one more

request, which reduces downlink TBF link establishment rate.

Therefore, if link establishment fails directly while cache-state

link reestablishment succeeds, it is not necessary to count one

request again.

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

Performance

When cache-state link reestablishment is enabled, downlink

TBF link establishment success rate can be improved.

Hardware

DependenceNone

Influence on

Associated NE

Interface



Associated

Parameters

Class-B Parameters:

GCellOption.DlCCCHEstStaOpt: Optimizing statistics of

downlink ccch establishment

Associated

Counters None

Associated

Alarms &

Notifications

None

Verification Plan

& Criteria

Enable the cache-status link reestablishment and the

optimization functions, and observe whether the downlink TBF

link establishment success rate is increased.

Influence on

Other FunctionsNone

Matters for

Attention None



5.4.2.6 TBF Release Not Counted in Paging Coordination

Table 5-57 TBF Release Not Counted in Paging Coordination

Function

Description

When paging coordination function is enabled, CS paging of the

called party will be sent from PS channels. After this, the

abnormal release of PS service will be regarded as normal state

and will not be counted as an abnormal release.

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

Performance

TBF Drop Rate is reduced.

Hardware

Dependence

None

Influence on

Associated NE

Interface

None


Associated

Parameters

None

Associated

Counters

None

Associated Alarms

& Notifications

None

Verification Plan &

Criteria

Enable paging coordination, initiate a call to the mobile in the PS

service, and observe whether the PS service interruption will be

counted.

Influence on Other

Functions

None

Matters for

Attention

None



5.4.2.7 Measurement Result Discarded After Reception of Clear CMD

Table 5-58 Measurement Result Discarded After Reception of Clear CMD

Function

Description

In the calling process, after the service instance sends Channel

Release message when it receives the Clear CMD message from

CN, it still counts the measurement results reported by MS, but

because the Deactivate SACCH message has been sent, the RQ

in the measurement result reported by MS will become very bad.

In abnormal release flow, MS may report several measurement

results after Channel Release is sent. In this case, RQ will be

affected. This can act as an objective of RQ improvement.

After BSC sends Channel Release to MS when

AClearDropMeasRpt is enabled, the measurement result is not

saved but is discarded directly. After BSC sends Channel

Release to MS when AClearDropMeasRpt is disabled, the

measurement result is saved as before and RQ statistics are

collected.

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

Performance

Downlink RQ performance is improved.

Hardware

Dependence

None

Influence on

Associated NE

Interface



Associated

Parameters

Class-B Parameters:

GBssFunctionOption.AClearDropMeasRpt: Whether the

processing of measurement report after A Clear Command

received

Associated

Counters

None

Associated Alarms None



& Notifications

Verification Plan &

Criteria

1. Disable the AClearDropMeasRpt switch, record the statistics

of the counters, and check signaling tracing in the calling

process.

2. After the CS service is released after the reception of the

Clear CMD message, check whether the number of RQ

samplings collected by the counter is consistent with the

number received by signaling tracing.

3. Enable the AClearDropMeasRpt switch, record the statistics

of the counters, and check signaling tracing in the calling

process.

4. After the CS service is released after the reception of the

Clear CMD message, check the number of RQ samplings

collected by the counter and the number of measurement

result samplings received by signaling tracing. The former

should be equal to or smaller the latter.

5. Enable AClearDropMeasRpt, record the statistics of the

counter, make calls, and perform signaling tracing. When CS

service is released abnormally, check the number of RQ

samplings collected by the counter and the number of

measurement result samplings received by signaling tracing.

The former should be equal to or smaller the latter.

Influence on Other

Functions

None

Matters for

Attention

None

5.4.3 Service Performance Improved

5.4.3.1 CS Service Performance Improved

Table 5-59 CS Service Performance Improved

Function

Description

[BSC sends “Disconnect” message to MS] In the assignment

process, if BSC receives the assignment failure message from

MS and the GBssFunctionOption.DiscSendCtrl switch is enabled,

BSC will form a “Disconnect” message and send it to CN at the

frequency of GBssFunctionOption.DiscSendRate configured on



OMM. This function aims mainly to improve assignment success

rate.

[New assignment failure in CS service release state] It takes

some time for BSC to send assignment message to the Um

interface after it receives A-interface assignment request. Usually

this period will not last long, but in special situations, such as,

wait from measure result after the reception of assignment

request in CoBCCH cell and queuing for resources due to lack of

TCH channel, this period will be prolonged. In this case, BSC will

receive A-interface assignment request first, and then perform

Un-interface assignment during or after layer-three release

process, which will cause Un-interface assignment failure. In this

case, when BSC parses layer-three release message and makes

a mark in the instance data area, the system judges that layer-

three release has started, and thus Um-interface assignment will

not be performed.

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

Performance

The GBssFunctionOption.DiscSendCtrl function can improve

assignment success rate.

The modification to new assignment failure in CS service release

state can reduce assignment failure rate.

Hardware

Dependence

None

Influence on

Associated NE

Interface

None

License Control No

Associated

Parameters

Class-B Parameters:

1. GBssFunctionOption.DiscSendCtrl: Disconnect

Send Control

2. GBssFunctionOption.DiscSendRate: The rate of

Send Disconnect

3. GBssFunctionOption.ForbidAssInRel: Forbid

Assignment during releasing



Associated

Counters

C901050092: The Number of forbid sending Assignment

command during releasing

Associated Alarms

& Notifications

None

Verification Plan &

Criteria

BSC sends “Disconnect” message to MS:

Enable the GBssFunctionOption.DiscSendCtrl switch, and set

the corresponding sending percent. Then, perform the following

test:

1. In the assignment process, create Um-interface assignment

failure and check whether the mantissa of the random value

generated in the print is smaller than

GBssFunctionOption.DiscSendRate set on OMM. If it is,

there will be a “disconnect” message sent from BSC to CN in

signaling tracing.

2. In the assignment process, create T3107 timeout and check

whether the mantissa of the random value generated in the

print is smaller than GBssFunctionOption.DiscSendRate set

on OMM. If it is, there will be a “disconnect” message sent

from BSC to CN in signaling tracing.

3. In the BSS reassignment process, create Um-interface

assignment failure with maximum reassignment attempts,

and check whether the mantissa of the random value

generated in the print is smaller than



signaling tracing.

4. In the directed retry process, create T3103 timeout and

check whether the mantissa of the random value generated

in the print is smaller than



signaling tracing.

5. In the BSS reassignment process, create directed retry Um-

interface handover failure with maximum reassignment

attempts, and check whether the mantissa of the random

value generated in the print is smaller than



signaling tracing.



Modification to new assignment failure in CS service release

state

1. Enable the ForbidAssInRel switch.

2. Block the TCH of the current cell, create a queuing process,

and release services in the queuing process to see whether

Um-interface assignment can be performed after the

release.

Influence on Other

Functions

When Um-interface assignment or Um-interface handover during

directed retry fails during the assignment process, only when the

reassignment functions is enabled and fails can this function be

started.

When T3107 is time-out in the assignment process or T3103 is

time-out during directed retry, enable the switch of the function to

start the function, i.e., this function is not subject to the wireless

assignment function switch.

Matters for

Attention

None

5.4.3.2 Wireless Transmission of PS Service Improved

Table 5-60 Wireless Transmission of PS Service

Function

Description

[RLC BLOCK retransmission coding selection algorithm

improved] In downlink data transmission, when there is block

retransmission due to poor wireless environment, to improve

wireless block transmission rate, degrade the coding level and

performing puncturing for the retransmitted blocks with higher

coding level than that of the TBF.

[DOWNLINK ACK block loss processing method improved] The

modification to downlink EGPRS TBF coding mode is triggered

by the EGPRS DOWNLINK ACK message carrying

measurement result. If EGPRS DOWNLINK ACK is lost, there

will be no trigger source. The signaling block loss means the

existing wireless environment may be worsened. If the coding

mode is not modified timely, continuous downlink blocks may fail

to be decoded by MS. This function is used to form a

measurement result manually to trigger coding mode

modification decision when EGPRS TBF receives the

DOWNLINK ACK message.



[Reduce number of downlink PENDING blocks transmitted] In the

current version, when DRLC is in transmission state, if no NEW

blocks and NACK blocks are sent, PENDING blocks will be sent

in RRBP timeslots. In this case, the PENDING blocks are

transmitted too frequently, which is more obvious after the last

NEW block is sent and waits for the ACK message. Make a

modification to this, i.e., when DRLC is in transmission state,

send PENDING blocks only in RRBP timeslots and only when

RRBP blocks need to be allocated.

[Improve downlink DUMMY block transmission] In previous

versions, the data will go into delay state after the downlink TBF

transmission is completed, and dummy blocks will be transmitted

at the fixed interval indicated in the RRBP interval block numbers

of downlink TBF. Thus, the DOWNLINK ACK can carry channel

request immediately after there is uplink TBF establishment, but

the interval of DUMMY block transmission is short. In this case,

set the interval of dummy blocks transmission as modifiable, and

thus the dummy blocks to be transmitted can be reduced by

setting a larger interval when necessary.

[Improve downlink DUMMY block transmission]

[Uplink/downlink RLC window size expansion] The uplink and

downlink RLC windows can be set as the average window size

and maximum window size supported by multi-slot according to

the switch.

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

Performance

The influences upon network performance are as listed below:

Raising retransmission rate in poor wireless rate can improve

network performance.

Avoid great coding change due to ACK block loss: improve the

stability of the coding mode.

Transmit valid blocks more frequently, and optimize the

performance when two or more users share the blocks.

Reduce the number of dummy blocks to be transmitted. This can

reduce the percent of MCS7 blocks statistics, but do not set it as

a very large number, otherwise, actual service performance will

be affected.

Big window can reduce the frequency of window inactivity, and



improve transmission rate, but it can also cause retransmission

delay and increase retransmission rate.

Hardware

Dependence

None

Influence on

Associated NE

Interface

There are newly added fields on OMM.


Associated

Parameters

1. GCellPs.RLCMaxWinInd EGPRS: Indicate Uplink

and　Downlink RLC Window Size value

Class-B Parameters:

1. GCellOption.DlNackCodeMode: Downlink Nack

block code mode drop

2. GCellOption.DlPendingCodeMode: Downlink

Pending block code mode drop

3. GCellOption.McsDiffClass: Different mcs

class according to radio

4. GCellOption.DropMcsP1P2P3: Drop mcs after

using all puncturing scheme

5. GCellOption.DlAckLostBepOpt: compensate

measure report when losing downlink ack

6. GCellOption.DlDummySendOpt: Optimize dummy

block in downlink delay state

7. GCellOption.DlDummySendIntTime: Times of

interval that send downlink dummy block

8. GCellOption.TransPendingOpt: Optimize

pending block in downlink transfer state

Associated

Counters

None

Associated Alarms

& Notifications

None

Verification Plan &

Criteria

Enable the function on site and perform DT test

Influence on Other

Functions

None

Matters for

Attention

Pay attention to the changes in KPIs.



5.4.4 Optimizing Configuration Parameter

5.4.4.1 AMR Handover Parameter

Table 5-61 AMR Handover Parameter

Function

Description

[New AMR Handover Parameter] AMR uses an independent set of

handover parameter.

[Modified default AMR value] Modify the default AMR value according

to the onsite experience.

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

Performance

None

Hardware

Dependence

None

Influence on

Associated NE

Interface

New configuration parameter is added in OMMR, and the default

value is modified.

License

Control

None

Associated

Parameters

1. GAmrHandoverControl.HoUlQualThsForAmrFr /Uplink

receive quality for AMR-FR Threshold

2. GAmrHandoverControl.HoUlQualAmrFrN /Uplink

receive quality for AMR-FR Value N

3. GAmrHandoverControl.HoUlQualAmrFrP /Uplink

receive quality for AMR-FR Value P

4. GAmrHandoverControl.HoUlQualThsForAmrHr AMR-HR

/Uplink receive quality for AMR-HR Threshold

5. GAmrHandoverControl.HoUlQualAmrHrN AMR-HR

/Uplink receive quality for AMR-HR Value N

6. GAmrHandoverControl.HoUlQualAmrHrP AMR-HR

/Uplink receive quality for AMR-HR Value P

7. GAmrHandoverControl.HoDlQualThsForAmrFr



/Downlink receive quality for AMR-FR Threshold

8. GAmrHandoverControl.HoDlQualAmrFrN /Downlink

receive quality for AMR-FR Value N

9. GAmrHandoverControl.HoDlQualAmrFrP /Downlink

receive quality for AMR-FR Value P

10. GAmrHandoverControl.HoDlQualThsForAmrHr AMR-HR

/Downlink receive quality for AMR-HR Threshold

11. GAmrHandoverControl.HoDlQualAmrHrN /Downlink

receive quality for AMR-HR Value N

12. GAmrHandoverControl.HoDlQualAmrHrP /Downlink

receive quality for AMR-HR Value P

13. GAmrHandoverControl.HoUlLevThsForAmrFr /Uplink

receive level for AMR-FR Threshold

14. GAmrHandoverControl.HoUlLevAmrFrN /Uplink

receive level for AMR-FR Value N

15. GAmrHandoverControl.HoUlLevAmrFrP /Uplink

receive level for AMR-FR Value P

16. GAmrHandoverControl.HoUlLevThsForAmrHr /Uplink

receive level for AMR-HR Threshold

17. GAmrHandoverControl.HoUlLevAmrHrN /Uplink

receive level for AMR-HR Value N

18. GAmrHandoverControl.HoUlLevAmrHrP /Uplink

receive level for AMR-HR Value P

19. GAmrHandoverControl.HoDlLevThsForAmrFr /Downlink

receive level for AMR-FR Threshold

20. GAmrHandoverControl.HoDlLevAmrFrN /Downlink

receive level for AMR-FR Value N

21. GAmrHandoverControl.HoDlLevAmrFrP /Downlink

receive level for AMR-FR Value P

22. GAmrHandoverControl.HoDlLevThsForAmrHr /Downlink

receive level for AMR-HR Threshold

23. GAmrHandoverControl.HoDlLevAmrHrN /Downlink

receive level for AMR-HR Value N

24. GAmrHandoverControl.HoDlLevAmrHrP /Downlink

receive level for AMR-HR Value P

Default values of the following parameters are modified:

1. vsDataGBssFunction.amrFullAcs1 /AMR full Active

Codec Set(4.75kbps)


Codec Set(5.15kbps)




Codec Set(5.9kbps)


Codec Set(6.7kbps)


Codec Set(7.4kbps)


Codec Set(7.95kbps)


Codec Set(10.2kbps)


Codec Set(12.2kbps)

9. vsDataGBssFunction.amrHalfAcs1 /AMR Half Active

Codec Set(4.75kbps)


Codec Set(5.15kbps)


Codec Set(5.9kbps)


Codec Set(6.7kbps)


Codec Set(7.4kbps)

14. vsDataGBssFunction.amrFrThresholds1 /Thresholds

of AMR FR 1


of AMR FR 2


of AMR FR 3


of AMR FR 4


of AMR FR 5


of AMR FR 6


of AMR FR 7

21. vsDataGBssFunction.amrHrThresholds1 /Thresholds

of AMR HR 1




of AMR HR 2


of AMR HR 3


of AMR HR 4


of AMR HR 5

26. vsDataGBssFunction.amrFrHysteresis1 /Hysteresis

of AMR FR 1


of AMR FR 2


of AMR FR 3


of AMR FR 4


of AMR FR 5


of AMR FR 6


of AMR FR 7

33. vsDataGBssFunction.amrHrHysteresis1 /Hysteresis

of AMR HR 1


of AMR HR 2


of AMR HR 3


of AMR HR 4


of AMR HR 5

38. vsDataGBssFunction.amrFrStartMode /AMR FR Start

mode

39. GCellAmr.amrFullAcs1 /AMR full Active Codec

Set(4.75kbps)


Set(5.15kbps)




Set(5.9kbps)


Set(6.7kbps)


Set(7.4kbps)


Set(7.95kbps)


Set(10.2kbps)


Set(12.2kbps)

47. GCellAmr.amrHalfAcs1 /AMR Half Active Codec

Set(4.75kbps)


Set(5.15kbps)


Set(5.9kbps)


Set(6.7kbps)


Set(7.4kbps)


Set(7.95kbps)

53. GCellAmr.amrFrThresholds1 /Thresholds of AMR FR

1


2


3


4


5


6


7



60. GCellAmr.amrHrThresholds1 /Thresholds of AMR HR

1


2


3


4


5

65. GCellAmr.amrFrHysteresis1 /Hysteresis of AMR FR

1


2


3


4


5


6


7

72. GCellAmr.amrHrHysteresis1 /Hysteresis of AMR HR

1


2


3


4


5

77. GCellAmr.amrHrStartMode /AMR HR Start mode

Associated

Counters

None



Associated

Alarms &

Notifications

None

Verification

Plan & Criteria

Initiate AMR voice call and trigger service handover. The handover

condition depends on the new parameter threshold. The original

handover parameter is invalid to the AMR voice service.

Influence on

Other

Functions

None

Matters for

Attention

None

5.4.4.2 Independent Setting of T3111 and T3109 Timers on TCH and SDCCH

Table 5-62 Independent Setting of T3111 and T3109 Timers on TCH and SDCCH

Function

Description

In the previous versions, TCH and SDCCH use the same T3111

and T3109 timers. Now T3111 and T3109 are allocated to

TCH, and a new set of timers is added for SDCCH, including

TSDRelPeriod and TSDDeactDelay.

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

Performance

None

Hardware

Dependence

None

Influence on

Associated NE

Interface

OMMR configuration parameters are added.


Associated

Parameters

1. GBssFunctionTimer.TSDRelPeriod /SDCCH

Channel release period

2. GBssFunctionTimer.TSDDeactDelay /SDCCH



Channel deactivation delay

Associated

Counters

None

Associated Alarms

& Notifications

None

Verification Plan &

Criteria

SDCCH uses the newly-added timer parameters, and TCH uses

the original timer parameters.

Influence on Other

Functions

None

Matters for

Attention

None

5.4.4.3 PS Service Parameter Modification

Table 5-63 PS Service Parameter Modification

Function

Description

[GPRS coding mode adjustment parameters Cn/Xn/Nn are set

at the cell level.] Cn/Xn/Nn is modified from the previous BSC

parameters to the cell parameters for the convenience of onsite

adjustment according to different radio environment of each cell.

[The default value of CCNSupport is modified to 1.] The default

value of the CCNSupport parameter of neighbor cells is modified

from 0 to 1, and NACC is enabled by default.

[The delay duration for signaling TBF is set with a different

value.] Set different values for the delay duration timers of data

TBF and signaling TBF. Make the value of signaling TBF

duration timer shorter to increase the usage rate of radio module.

[The TrxPSBusyThs parameter is modified to the cell level.]

PSBusyThs is modified from the previous BSC parameter to the

cell parameter, and can be adjusted according to the channel

occupation status of each cell.

[Four IP addresses are set in advance.] The IP addresses pre-set for the

server at the network side can enhance the upload and download

service rate in this IP address, so that the specific KPI can be improved.

There is only one pre-set IP address in the previous version, but there

are four IP addresses in this version.

[Number of RLC instance breakdown leak can be configured in

OMM.] The parameter used to be set with a fixed value, but it



can be configured in this version to meet the onsite requirement

for the improvement of PS call drop rate.

[Re-creation of cache status can be controlled by corresponding

parameters.] Parameters are added to control the cache status

re-creation for once or multiple times.

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

Performance

None

Hardware

Dependence

None

Influence on

Associated NE

Interface



Associated

Parameters

1. GCellPs.Cn /Cn

2. GCellPs.Nn /Nn

3. GCellPs.Xn /Xn

4. GCellPs.DlSigDelayTime /Downlink Delay

Signal TBF Time

5. GCellPs.ExtUlSigTBFTime /Extended uplink

Signal TBF time

6. GPsChannelSchedule.psBusyThs /PS busy

threshold

7. GBBssFunction.PriorityIp /PriorityIp

Default values of the following parameters are modified:

1. vsDataGGsmRelation.CCNSUPPORT /CCN support

Class-B Parameters:

1. GBBssFunction.EnlargementFactor

/EnlargementFactor

2. GCellOption.NackReSendThrd /DRLC Nack Block

Resend Threshold

3. GBssFunctionOption.DwBufRetryNum /Retry

number in downlink buffer state



Associated

Counters

None

Associated Alarms

& Notifications

None

Verification Plan &

Criteria

None

Influence on Other

Functions

None

Matters for

Attention

None

5.4.5 New and Optimized Functions for OMM

5.4.5.1 Signaling Trace

Table 5-64 Signaling Trace

Function

Description

[Signaling trace on RRU level] In MCUM mode, in order to observe the

current RRU through the signaling on the Abis interface, add RRU

indications and weight in the uplink signaling on the Abis interface in the

measurement report, etc. RRU indications are composed of RRU Rack

No. and RRU PA Channel No., weight indicates the proportion of RRU

in all the uplink bursts within the measurement period.

Add RRU indications and weight in the 12 pieces of signaling in

SDR: Measurement Result, Pre-processed

Measurement Result, Enhanced Pre-processed

Measurement Result, ESTABLISH INDICATION,

ESTABLISH CONFIRM, RELEASE INDICATION, RELEASE

CONFIRM, DATA INDICATION, UNIT DATA INDICATION,

HANDOVER DETECTION, ERROR INDICATION, and

CHANNEL REQUIRED.

[IUR-G signaling trace] The cell capacity and load information can be

notified to the BSCs in different systems through the Iur-g interface, and

quick re-location can also be achieved among different systems through

this interface. The signaling trace on the IUR-G interface is available in

this version for monitoring and testing.

[Signaling trace on the Um interface] The signaling on the Um

interface can be traced in the IMSI trace in the UE type. The



signaling is reported through the base station.

[Multiple cell trace] In the signaling trace on the Abis interface,

multiple cells can be traced in one task.

[TRX and TS No. is added in the signaling trace on the Abis

interface] The information of TRX and TS No. is added in the

display contents.

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

Performance

None

Hardware

Dependence

None

Influence on

Associated NE

Interface

Modification is performed on the interface with SDR.


Associated

Parameters

None

Associated

Counters

None

Associated Alarms

& Notifications

None

Verification Plan &

Criteria

None

Influence on Other

Functions

None

Matters for

Attention

None



5.4.5.2 CPU Real-Time Monitoring

5.4.6 New and Optimized Functions Related to BTS

5.4.6.1 New Functions Related to BTS

Table 5-65 New Functions Related to BTS

Function

Description

[Joint Source-Controlled Channel Decoding] Use

multiple receiving signals for decoding to enhance the uplink

decoding success rate.

[Uplink NCC] If the service cell of the handset and a neighbor cell are

under the same BTS, NCC can receive and process the signals in the

combination mode, and optimize the conversation quality.

[Power compression and compensation of a specific frequency

point during frequency jump] If GSM and UMTS are in the same

900M frequency band and share the same RRU module, UMTS

frequency points use the middle frequency band, and GSM

points use the frequency band close to the two sides. When

UMTS bandwidth is 3.8 or 4.2 MHz, the interference of GSM

neighbor frequency on UMTS makes the downlink performance

greatly reduced. To minimize the influence, according to the

features of GSM frequency jump and interleaving, compress the

Burst Tx power of neighbor frequency points at both sides of

UMTS frequency band based on the power control, and

compensate the compressed power to the burst of the other

frequency points in the interleaving module.

[Maximum TRX protection] When the TRXs of a cell is configured

in multiple PAs, but one PA is damaged, if the bandwidth and

power allows, the maximum working TRXs can still be provided

to the cell.

Function SN. None

Influence on

Equipment

Performance

There is no influence on BSC.

Influence on

Network

Performance

Refer to the corresponding function description for the base

station.



Hardware

Dependence

None

Influence on

Associated NE

Interface



Associated

Parameters

1. vsDataGGsmCell.JSCCDSwitch /Joint Source-

Controlled Channel Decoding

2. vsDataGGsmCell.JSCCD /Joint Source-

Controlled Channel Decoding

3. vsDataGGsmCell.NccCfgPara /NCC Config

Parameter

4. vsDataGGsmCell.RQThreshold /RxQual

Threshlod

5. vsDataGGsmCell.SupportArfPwrReduce /Arf

power reduce function switchding Switch

6. vsDataGGsmCell.AVGPromPower /Prom power step

7. vsDataGGsmCell.StopPwrReduceThs /Stop power

Reduce Level Threshold

8. vsDataGGsmCell.PowerReduceARFCN /Reduce

Power Arfcn

9. vsDataGGsmCell.ReducePower /Reduce Power

Step

10. vsDataGGsmCell.SupportBtsBcchExchg

/SupportBtsBcchExchg

Associated

Counters

None

Associated Alarms

& Notifications

None

Verification Plan &

Criteria


station.

Influence on Other

Functions


station.

Matters for

Attention

None



5.4.6.2 Power Control Optimization

Table 5-66 Power Control Optimization

Function

Description

[SDR/BTS uniform power control] SDR and BTSV3 use the same set of

power control parameters and algorithm. BTSV2 is not involved.

[Power control algorithm improvement] In order to improve the filtering

algorithm of the power control indicators, improve the solution in SDR to

add power control compensation, modify filtering method, remove the N,

P judgment and nine-grid pattern judgment, and add new power control

judgment.

[Power control rescue] The downlink power control rescue function is a

kind of quick downlink power control. Only in some extreme condition

(downlink RX level is low and RX quality is poor), power control rescue

will be triggered to improve the TX power of the base station. The

prerequisite of this function is that the normal downlink power control is

enabled.

[Power control for high level and poor quality] The original power control

policy is designed to improve the power. When the level is high and the

quality is poor, the power control policy should be changed to keep the

original power instead of improving it, so that the interference will not be

strengthened.

[Independent threshold of downlink SAIC power control] Due to the high

TX performance of SAIC MS and higher sensitivity compared with the

normal MS, the downlink power control threshold can be lower than

normal MS. In this condition, the network interference can be reduced,

and network quality can be improved. Set a special power control

threshold for SAIC MS.

Function SN. None

Influence on

Equipment

Performance

There is no influence on BSC.

Influence on

Network

Performance


station.

Hardware

Dependence

None

Influence on

Associated NE




Interface


Associated

Parameters

Associated

Counters

1. C901320070 Number of BTS power increase due

to power rescue

2. C901320071 Number of channel active BTS

power change due to power dynamic share

Associated Alarms

& Notifications

None

Verification Plan &

Criteria


station.

Influence on Other

Functions


station.

Matters for

Attention

None

5.4.6.3 RRU With Eight TRXs

Table 5-67 RRU With Eight TRXs

Function

Description

RRU 8881 with single-channel eight TRXs are added in SDR.

Corresponding modification should be performed in BSC to

support intelligent shutdown and power sharing functions.

Function SN. None

Influence on

Equipment

PerformanceNone

Influence on

Network

Performance

None

Hardware

Dependence

None

Influence on None



Associated NE

Interface


Associated

Parameters

None

Associated

Counters

None

Associated Alarms

& Notifications

None

Verification Plan &

Criteria

Configure eight TRXs on RRU 8881 and test whether the

intelligent shutdown and power sharing functions are normal. In

OMCR Dynamic Management, query the TRXs corresponding to

the RRU, and make sure the display information is correct.

Influence on Other

Functions

None

Matters for

Attention

None

5.4.6.4 Paging Occupancy

Table 5-68 Paging Occupancy

Function

Description

Delay the immediate assignment message to reduce the

occupancy of PCH by immediate assignment to improve the

paging success rate.

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

Performance


station.

Hardware

Dependence

None

Influence on

Associated NE




Interface


Associated

Parameters

1. vsDataGGsmCell.PCHOccupyOpt /Immediate

assignment occupy PCH option

2. vsDataGGsmCell.IAMAXDelayTimes /Immediate

assignment maximum delay times

Associated

Counters

None

Associated Alarms

& Notifications

None

Verification Plan &

Criteria


station.

Influence on Other

Functions


station.

Matters for

Attention

None

5.4.6.5 Downlink Dual-Coding

Table 5-69 Downlink Dual-Coding

Function

Description

During the handover between different speech versions,

downlink coding is performed in their own link establishment rate

until the old link is disconnected. Downlink data is sent to both

sub-channels before and after the handover. When the load is

high, downlink dual-coding should be stopped automatically.

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

Performance

Reduce the conversation interruption duration during the

handover and improve MOS.

Hardware

Dependence

It is supported by BSC V3 on 100M/1000M platform and BSC V4

platform.

Influence on New configuration parameters are added on OMMR.



Associated NE

Interface


Associated

Parameters

None

Associated

Counters

None

Associated Alarms

& Notifications

None

Verification Plan &

Criteria

Test the conversation interruption duration and MOS during the

handover between different speech versions.

Influence on Other

Functions

None

Matters for

Attention

None

5.4.6.6 Number of V3 BSC CMP Modules Added to 10

Table 5-70 Number of V3 BSC CMP Modules Added to 10

Function

Description

In the onsite V3 BSC, the problem of high CMP load often

occurs. Currently the only proper solution is to move the site. In

this version, two pairs of CMP boards can be added to share the

CMP load.

Function SN. None

Influence on

Equipment

Performance

CMP load can be reduced.

Influence on

Network

Performance

None

Hardware

Dependence

None

Influence on

Associated NE

None



Interface


Associated

Parameters

Associated

Counters

None

Associated Alarms

& Notifications

None

Verification Plan &

Criteria

1. When three pairs of CMP boards are configured, add

another two pairs of CMP modules.

2. Configure the site on the new CMP modules, and perform

service verification.

Influence on Other

Functions

None

Matters for

Attention

Generally three pairs of CMP boards are configured. The

expansion is only performed when the CMP load needs to be

reduced.

According to the board configuration in the rack, add one pair or

two pairs of CMP boards.

5.4.6.7 CS/PS Service Access Prohibited During A/Gb Interface Disconnection

Table 5-71 CS/PS Service Access Prohibited During A/Gb Interface Disconnection

Function

Description

When the A-interface link is disconnected, MS still stays in the

cell with problem and keeps initiating service attempts. Under the

current multi-network (2G/3G/4G) coverage, the operator hopes

the MS can migrate to 3G or 4G network, so that services can be

performed normally.

This function is used to judge network operation status through

upper-level services:

1. Counts the number of times for sending immediate

assignment rejections by PLMN, the base number is 200

times. For every 100 times of immediate assignment

rejection, the waiting time will be added by 5s, the time after

the addition of the waiting time shall not exceed the

WaitTimeMax.

2. Counts the number of times for querying office information



failures or T9105 timeout by PLMN. When it exceeds the

threshold configured on OMM, judge whether the A interface

is disconnected. If it is, request the system message module

to send the system message for cell access prohibition. After

cell access is prohibited, check A-interface status. If the A

interface is connected in three consecutive checks, the

system will resend normal system messages.

The mechanism used when the Gb interface is disconnected is

the same as that of the A interface. When the Gb interface is

disconnected, the system will rebroadcast system info 13 to

prohibit PS service access.

Function SN. None

Influence on

Equipment

Performance

The system load during A-interface/Gb-interface disconnection

can be relieved.

Influence on

Network

Performance

None

Hardware

Dependence

None

Influence on

Associated NE

Interface



Associated

Parameters

1. vsDataGBssFunction.CellSeleBarADown: Cell

Bar when A break

Class-B Parameters:

1. GBssFunctionOption.OfficeLinkBreakMax: MSC

Office breaking num

2. GBssFunctionOption.TScanPLMNAStatus: A PLMN

scan timer

3. GBssFunctionOption.WaitTimeMax: Max of Wait

timer

4. GBssFunctionOption.TScanPLMNGbStatus: Gb

PLMN scan timer

Associated

Counters

None



Associated Alarms

& Notifications

None

Verification Plan &

Criteria

1. Enable the CellBar switch on the A interface, and set

OfficeLinkBreakMax and TScanPLMNAStatus.

2. Create A-interface disconnection on the A interface.

3. Initiate services continuously. When the number of service

failures exceeds the value of OfficeLinkBreakMax and

see whether the system message of cell access prohibition

can be sent.

4. Block the SDCCH of the cell and initiate services

continuously. When the number of immediate assignment

rejections exceeds 200, check whether the waiting time

carried in the immediate assignment rejection is consistent

with the expected time, and whether it will exceeds the

WaitTimeMax configured on OMM.

5. Restore the A interface and check it for three times. If all

these checks show that it is normal, check whether the

system messages are sent normally.

Influence on Other

Functions

None

Matters for

Attention

This function will affect the system greatly. Please check

carefully before enabling this function.

5.4.6.8 The ICMP-based Fast Rerouting Function

Table 5-72 The ICMP-based Fast Rerouting Function

Function

Description

When the peer-end equipment does not support BFD or 802.3ah,

BSC supports the use of ICMP (instead of BFD) in detecting the

next-hop accessibility of static route. The advantages of using

ICMP instead of BFD include: the IOT problem between

equipment from different suppliers does not exist; it can provide

all the additional functions that are equivalent to BFD (triggering

the switch of master/slave board). The ICMP-based fast rerouting

function is called IPD in short, which can be applied in detecting

the point-to-point direct GE link in the L3 networking.

The detection mechanism is to detect the route accessibility

through sending the ICMP Echo Request message and receiving



the Echo Reply message from the peer end. As the substitute of

the BFD function, IPD can be enabled by the switch of static

route (BfdSet).

Function SN. None

Influence on

Equipment

Performance

None

Influence on

Network

Performance

None

Hardware

Dependence

The function is only supported on the Ethernet interface boards,

including GIPI/GIPI3/GIPI4/EGPB.

Influence on

Associated NE

Interface


Associated

Parameters

1. IpdSession.LocalIpAddr /Local IP

Address(IPV4)

2. IpdSession.PeerIpAddr /Peer IP Address(IPV4)

3. IpdSession.refVpnVrf /Used VRF Attributes

Configuration Object

4. IpdSession.TxInterval /The sending interval

5. IpdSession.DetectTime /The detection time

6. IpdSession.DampInd /Damping function switch

StaticRoute.BfdSet / Route BFD/IPD flag

Associated

Counters

Associated Alarms

& Notifications

None

Verification Plan &

Criteria

Configure static route and make it associated with the IPD

detection; pull out the TX terminal of the GE fiber. Check the

route table in DDM. If the static route item is unavailable, it

means the verification is successful.

Influence on Other

Functions

None

Matters for

Attention

None



Note None

5.5 Other Performance Improvement

5.5.1 Enhanced TCH Availability

表 5-1 Enhanced TCH Availability

Description

Currently, the statistics of the available and unavailable channels is

made every 15 minutes. An instantaneous value is taken as a sample.

But this value does not properly reflect the average availability of a 15-

minute period. To improve it, update the statistics of the available and

unavailable channels according to the cell interruption duration. The

updated algorithm is: Number of unavailable channels = Number of total

channels * (cell interruption duration/15 minutes); number of available

channels = number of total channels – number of unavailable channels.

Feature Num None

Impact on Equipment

PerformanceNone

Impact on Network This feature improves the calculation of available channels.

Hardware

RequirementNone

Default State None

Impact on System None



Relative Counter 1. C901080069 Average number of available dynamic SDCCHs

2. C901080001 Average number of available SDCCHs

3. C901130001 Number of available TCH/Fs in the second subcell

4. C901130003 Number of available TCH/Hs in the second subcell

5. C901080007 Average number of available defined SDCCHs

6. C901080028 Number of available static TCH/Fs

7. C901080019 Number of available static TCH/Hs

8. C901040005 Number of available static PDCH

9. C901080009 Average number of available dynamic radio



channel

10. C901040098 Number of available no prefered static PDCH

11. C901040099 Number of available gprs prefered static PDCH

12. C901040100 Number of available egprs prefered static PDCH

13. C901040101 Number of available only egprs static PDCH

14. C901040106 Number of available no prefered dynamic PDCH

15. C901040107 Number of available gprs prefered dynamic PDCH

16. C901040108 Number of available egprs prefered dynamic

PDCH

17. C901040116 Number of available PDTCH in subcell2

18. C901040118 Number of available fixed PDTCH in subcell2

19. C901040003 Average number of available PDCH

20. C901080071 Average number of dynamic SDCCHs not available

21. C901080002 Average number of unavailable SDCCHs

22. C901130002 Number of unavailable TCH/Fs in the second

subcell

23. C901130004 Number of unavailable TCH/Hs in the second

subcell

24. C901080008 Average number of defined SDCCHs not available

25. C901080029 Number of unavailable defined TCH/Fs

26. C901080020 Number of unavailable defined TCH/Hs

27. C901040006 Number of unavailable static PDCH

28. C901080010 Average number of unavailable dynamic radio

channel

29. C901040102 Number of unavailable no prefered static PDCH

30. C901040103 Number of unavailable gprs prefered static PDCH

31. C901040104 Number of unavailable egprs prefered static PDCH

32. C901040105 Number of unavailable only egprs static PDCH

33. C901040109 Number of unavailable no prefered dynamic PDCH

34. C901040110 Number of unavailable gprs prefered dynamic

PDCH

35. C901040111 Number of unavailable egprs prefered dynamic

PDCH

36. C901040117 Number of unavailable PDTCH in subcell2

37. C901040119 Number of unavailable fixed PDTCH in subcell2

38. C901040004 Average number of unavailable PDCH

Relative Alarm None

Verification 1. Manually block the cell and links, which makes the BTS

malfunction. Check whether the statistics of the available and



unavailable channels is correct;

2. The counters of the available and unavailable channels change

with the cell interruption.

Impact on other

featureNone

Note None


bsc ur12.3 release notes 0924

Documents

zte corporation address

product names

product manual

parameter changes74

release background22

counter changes74

alarm changes74

company names