Speech Quality Supervision

GERAN Network Impact
Report
UR13
GERAN Network Impact Report

Version Date Author Reviewer Notes
Gu Yuhui, Zhang
V1.0 2014/7/31 Fu Liping First Release
Mingjing
2014 ZTE Corporation. All rights reserved.

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

TABLE OF CONTENTS
1 About This Document ..................................................................................... 13

1.1 Purpose ............................................................................................................. 13
1.2 Intended Audience ............................................................................................. 13
1.3 Change History .................................................................................................. 13
1.4 Document Versions ............................................................................................ 13
2 General Impact ................................................................................................ 14

2.1 Version Requirements ........................................................................................ 14
2.2 Capacity and Performance................................................................................. 14
2.2.1 BSC ................................................................................................................... 14
2.2.2 SDR ................................................................................................................... 16
2.2.3 NetNumen.......................................................................................................... 16
2.3 Hardware ........................................................................................................... 16
2.3.1 BSC ................................................................................................................... 16
2.3.2 SDR ................................................................................................................... 18
2.3.3 NetNumen.......................................................................................................... 19
2.4 Implementation .................................................................................................. 19
2.4.1 Upgrade Path..................................................................................................... 19
2.4.2 Upgrade from UR12 to UR13 ............................................................................. 19
2.5 License .............................................................................................................. 20
2.5.1 Changes in License Control Items ..................................................................... 20
2.5.2 Changes in License Control Modes ................................................................... 34
2.6 Inter-NE Interfaces ............................................................................................. 34
2.7 Operation and Maintenance ............................................................................... 35
2.8 Other NEs .......................................................................................................... 35
3 Summary of Feature Impacts ......................................................................... 35
4 Impacts of UR13 Features on UR12 ............................................................... 37

4.1 ZGO-01-02-010 Flexible TBF Multiplexing ......................................................... 37
4.1.1 Description ......................................................................................................... 37
4.1.2 Capacity and Performance................................................................................. 38
4.1.3 Impact on NEs ................................................................................................... 38
4.1.4 Hardware ........................................................................................................... 38
4.1.5 Inter-NE Interfaces ............................................................................................. 38
4.1.6 Operation and Maintenance ............................................................................... 39
4.1.7 Impact on Other Features .................................................................................. 40
4.2 ZGO-01-02-014 Cooperative Service Optimization ............................................ 40
4.2.1 Description ......................................................................................................... 40
2 ZTE Confidential & Proprietary


4.2.3 Impact on NEs ................................................................................................... 41
4.2.4 Hardware ........................................................................................................... 41
4.3 ZGO-01-02-015 PS Service Acceleration based on Traffic ................................ 43
4.3.1 Description ......................................................................................................... 43
4.3.3 Impact on NEs ................................................................................................... 43
4.3.4 Hardware ........................................................................................................... 44
4.4 ZGO-02-03-015 Subscriber Profile ID (SPID) ..................................................... 47
4.4.1 Description ......................................................................................................... 47
4.4.3 Impact on NEs ................................................................................................... 48
4.4.4 Hardware ........................................................................................................... 48
4.5 ZGO-02-03-016 SRVCC from LTE to GSM ........................................................ 50
4.5.1 Description ......................................................................................................... 50
4.5.3 Impact on NEs ................................................................................................... 51
4.5.4 Hardware ........................................................................................................... 51
4.6 ZGO-02-03-017 NCCR from GSM to LTE .......................................................... 52
4.6.1 Description ......................................................................................................... 52
4.6.3 Impact on NEs ................................................................................................... 53
4.6.4 Hardware ........................................................................................................... 53
4.7 ZGO-02-03-019 CSFB from LTE to GSM ........................................................... 55
4.7.1 Description ......................................................................................................... 55
4.7.3 Impact on NEs ................................................................................................... 56

4.7.4 Hardware ........................................................................................................... 56

4.8 ZGO-02-03-021 GSM/LTE Load Sharing ........................................................... 58
4.8.1 Description ......................................................................................................... 58
4.8.3 Impact on NEs ................................................................................................... 58
4.8.4 Hardware ........................................................................................................... 59
4.9 ZGO-03-01-005 Priority Based PS Congestion Control ...................................... 61
4.9.1 Description ......................................................................................................... 61
4.9.3 Impact on NEs ................................................................................................... 62
4.9.4 Hardware ........................................................................................................... 62
4.9.5 Inter-NE Interface............................................................................................... 62
4.10 ZGO-03-02-016 Dynamic Multiple CCCHs ......................................................... 64
4.10.1 Description ......................................................................................................... 64
4.10.3 Impact on NEs ................................................................................................... 65
4.10.4 Hardware ........................................................................................................... 65
4.11 ZGO-03-05-009 Early TBF Establishment Uplink ............................................... 69
4.11.1 Description ......................................................................................................... 69
4.11.3 Impact on NEs ................................................................................................... 69
4.11.4 Hardware ........................................................................................................... 70
4.12 ZGO-03-07-006 MOCN Network Sharing ........................................................... 72
4.12.1 Description ......................................................................................................... 72
4.12.3 Impact on NEs ................................................................................................... 72
4.12.4 Hardware ........................................................................................................... 73
4.12.5 Inter-NE Interface............................................................................................... 73


4.13 ZGO-04-01-012 Uplink Neighbor Cell Coordination ........................................... 75
4.13.1 Description ......................................................................................................... 75
4.13.3 Impact on NEs ................................................................................................... 77
4.13.4 Hardware ........................................................................................................... 77
4.14 ZGO-04-03-008 Dynamic Frequency Allocation ................................................. 80
4.14.1 Description ......................................................................................................... 80
4.14.3 Impact on NEs ................................................................................................... 81
4.14.4 Hardware ........................................................................................................... 81
4.15 ZGO-05-04-030 IP Anti-DoS Attack ................................................................... 87
4.15.1 Description ......................................................................................................... 87
4.15.3 Impact on NEs ................................................................................................... 88
4.15.4 Hardware ........................................................................................................... 88
4.15.7 Impact on Other Features ................................................................................ 100
4.16 ZGO-05-04-031 802.3x Based Flow Control .................................................... 100
4.16.1 Description ....................................................................................................... 100
4.16.2 Capacity and Performance............................................................................... 101
4.16.3 Impact on NEs ................................................................................................. 101
4.16.4 Hardware ......................................................................................................... 101
4.16.5 Inter-NE Interfaces ........................................................................................... 101
4.16.6 Operation and Maintenance ............................................................................. 101
4.17 ZGO-06-02-005 Enhanced Encryption Mechanism .......................................... 103
4.17.1 Description ....................................................................................................... 103
4.17.3 Impact on NEs ................................................................................................. 104
4.17.4 Hardware ......................................................................................................... 104

4.18 ZGO-01-03-004 Cell Broadcast Service ........................................................... 106

4.18.1 Description ....................................................................................................... 106
4.18.3 Impact on NEs ................................................................................................. 109
4.18.4 Hardware ......................................................................................................... 109
4.19 ZGO-01-03-005 Dual Transfer Mode ............................................................... 111
4.19.1 Description ....................................................................................................... 111
4.19.3 Impact on NEs ................................................................................................. 113
4.19.4 Hardware ......................................................................................................... 113
4.20 ZGO-02-03-014 Fast Return from GSM to LTE ................................................ 114
4.20.1 Description ....................................................................................................... 114
4.20.3 Impact on NEs ................................................................................................. 116
4.20.4 Hardware ......................................................................................................... 116
4.21 ZGO-04-02-006 TFO ....................................................................................... 118
4.21.1 Description ....................................................................................................... 118
4.21.3 Impact on NEs ................................................................................................. 119
4.21.4 Hardware ......................................................................................................... 120
4.21.5 Inter-NE Interface............................................................................................. 120
4.22 ZGO-04-03-007 Intelligent Frequency Timeslot Allocation (IFTA) .................... 126
4.22.1 Description ....................................................................................................... 126
4.22.3 Impact on NEs ................................................................................................. 128
4.22.4 Hardware ......................................................................................................... 128
4.23 ZGO-05-04-002 Gb over IP.............................................................................. 146
4.23.1 Description ....................................................................................................... 146


4.23.3 Impact on NEs ................................................................................................. 146
4.23.4 Hardware ......................................................................................................... 147
4.24 ZGO-05-04-005 IP SLA Monitoring .................................................................. 148
4.24.1 Description ....................................................................................................... 148
4.24.3 Impact on NEs ................................................................................................. 149
4.24.4 Hardware ......................................................................................................... 149
4.25 ZGO-05-04-013 IP Traffic Shaping .................................................................. 150
4.25.1 Description ....................................................................................................... 150
4.25.3 Impact on NEs ................................................................................................. 151
4.25.4 Hardware ......................................................................................................... 151
4.26 ZGO-05-04-025 IPv6 ....................................................................................... 152
4.26.1 Description ....................................................................................................... 152
4.26.3 Impact on NEs ................................................................................................. 154
4.26.4 Hardware ......................................................................................................... 154
4.27 ZGO-05-05-001 BSC Local Switch .................................................................. 184
4.27.1 Description ....................................................................................................... 184
4.27.3 Impact on NEs ................................................................................................. 185
4.27.4 Hardware ......................................................................................................... 185
4.28 ZGO-05-05-002 BTS Cluster Local Switch ....................................................... 191
4.28.1 Description ....................................................................................................... 191
4.28.3 Impact on NEs ................................................................................................. 192

4.28.4 Hardware ......................................................................................................... 192

4.29 ZGO-05-05-003 BTS Local switch ................................................................... 197
4.29.1 Description ....................................................................................................... 197
4.29.3 Impact on NEs ................................................................................................. 198
4.29.4 Hardware ......................................................................................................... 198
4.30 ZGO-06-01-002 Speech Quality Supervision ................................................... 203
4.30.1 Description ....................................................................................................... 203
4.30.3 Impact on NES ................................................................................................. 204
4.30.4 Hardware ......................................................................................................... 204
4.31 ZGO-06-01-020 Super Signaling Trace............................................................ 207
4.31.1 Description ....................................................................................................... 207
4.31.3 Impact on NES ................................................................................................. 208
4.31.4 Hardware ......................................................................................................... 208
4.32 Other Enhancements ....................................................................................... 211
4.32.1 FACCH Enhancement ..................................................................................... 211
4.32.2 Packet Loss Compensation ............................................................................. 213
4.32.3 Dynamic TRX License ..................................................................................... 213
4.32.4 DL Small Data Reducing Code Sending .......................................................... 215

FIGURES
Figure 4-1 Uplink Neighbor Cell Coordination ....................................................................76

Figure 4-2 Deployment of Built-in CB SMS ......................................................................107
Figure 4-3 Deployment of Stand-alone CBC (via OMCR) ................................................108
Figure 4-4 Deployment of Stand-alone CBC (BSC-CBC direct interface) ........................108
Figure 4-5 Dual-Transfer-Mode ........................................................................................112

Figure 4-6 BSC Local Switch ...........................................................................................184
Figure 4-7 BTS Cluster Local Switch ...............................................................................191
Figure 4-8 BTS Local Switch............................................................................................197
TABLES
Table 2-1 Product Versions Required for UR13 .................................................................14

Table 2-2 Capacity of iBSC ................................................................................................14
Table 2-3 Capacity of ZXUR9000 GSM BSC (Hardware Version: ZXUR9000 H1.0) ..........15
Table 2-4 Capacity of ZXUR9000 GSM BSC (Hardware version: ZXUR9000 H2.0) ..........15
Table 2-5 ZTE Traffic Model for BHCA...............................................................................16
Table 2-6 ZTE traffic model for voice call ...........................................................................16
Table 2-7 New Boards of ZXG10 iBSC ..............................................................................17
Table 2-8 New Boards of ZXUR9000 GSM BSC ................................................................17
Table 2-9 New Boards of SDR ...........................................................................................18
Table 2-10 New Modules of SDR .......................................................................................18
Table 2-11 License Control Items Deleted from UR13 .......................................................20
Table 2-12 License Control Items Added for UR13 New Features .....................................20
Table 2-13 License Control Items Added for Former Optional Features Before UR13 .......21
Table 2-14 License Control Items Added for Capacity Related in UR13 ............................34

Table 3-1 Impact Severity of New/Optional Features in UR13 ...........................................36

Table 3-2 Impact Severity of Enhanced/ Optional Features in UR13 ..................................36
Table 4-1 Flexible TBF Multiplexing License Description ...................................................39
Table 4-2 Parameters Related to This Feature ..................................................................39
Table 4-3 Counters Related to This Feature ......................................................................39
Table 4-4 Cooperative Service Optimization License Description ......................................41
Table 4-7 Counters Related to This Feature ......................................................................46
Table 4-8 Subscriber Profile ID (SPID) License Description ...............................................49
Table 4-10 Counters Related to This Feature ....................................................................49
Table 4-12 GSM/LTE NCCR License Description ..............................................................53
Table 4-13 Parameters Related to This Feature ................................................................54
Table 4-15 CSFB from LTE to GSM License Description ...................................................57
Table 4-16 GSM/LTE Load Sharing License Description ...................................................59
Table 4-18 Priority Based PS Congestion Control License Description ..............................62
Table 4-19 New Parameters Related to This Feature ........................................................63
Table 4-20 New Counters Related to This Feature ............................................................63
Table 4-21 Dynamic Multiple CCCHs License Description .................................................66
Table 4-24 Early TBF Establishment Uplink License Description .......................................70
Table 4-27 MOCN Network Sharing License Description ...................................................73


Table 4-30 Uplink Neighbor Cell Coordination License Control Description .......................77
Table 4-32 New counters Related to This Feature .............................................................78
Table 4-33 Dynamic Frequency Allocation License Description .........................................81
Table 4-36 Parameters Related to This Feature for iBSC ..................................................89
Table 4-37 Parameters Related to This Feature for ZXUR9000 .........................................93
Table 4-38 New Counters Related to This Feature for iBSC ..............................................98
Table 4-39 New Counters Related to This Feature for ZXUR9000 .....................................99
Table 4-40 802.3x Based Flow Control License Description ............................................101
Table 4-41 Parameters Related to This Feature for iBSC ................................................102
Table 4-42 Parameters Related to This Feature for ZXUR9000 .......................................102
Table 4-43 Enhanced Encryption Mechanism License Description ..................................104
Table 4-44 Parameters Related to This Feature ..............................................................105
Table 4-45 New Counters Related to This Feature ..........................................................105
Table 4-46 Cell Broadcast Service License Description ...................................................110
Table 4-48 Counters Related to This Feature ..................................................................110
Table 4-49 Dual Transfer Mode License Description........................................................113
Table 4-50 Parameters Related to Enhancement of This Feature ....................................113
Table 4-51 Fast Return from GSM to LTE License Description ........................................116
Table 4-53 TFO License Description................................................................................120
Table 4-55 Counters related to this feature ......................................................................122
Table 4-56 C/I Thresholds................................................................................................127
Table 4-57 Intelligent Frequency Timeslot Allocation License Description .......................128


Table 4-60 Gb over IP License Description ......................................................................147
Table 4-61 Parameters Related to the Enhancement of This Feature ..............................147
Table 4-62 IP SLA Monitoring License Description ..........................................................149
Table 4-63 IP Traffic Shaping License Description ...........................................................152
Table 4-64 IPv6 License Description................................................................................154
Table 4-67 BSC Local Switch License Description ...........................................................186
Table 4-70 BTS Cluster Local Switch License Description .............................................193
Table 4-75 Speech Quality Supervision License Description ...........................................205
Table 4-84 Parameters Related to This Enhancement .....................................................215

1 About This Document
1.1 Purpose
This document describes the impacts of new and enhanced UR13 features imposed on
UR12 and provides the information that network planning personnel and operation and
maintenance (O&M) personnel required to prepare for upgrades to UR13.
Information in this document is for the reference only and is subject to change during the
development of this new release.
1.2 Intended Audience
This document intends for:
Network planning engineers
System engineers
Network operators
1.3 Change History
Changes between document versions are cumulative. The latest document version
contains all the changes in earlier versions.
2014-07-31:
New document
1.4 Document Versions
V1.00 (2014-07-31)

2 General Impact
2.1 Version Requirements
Table 2-1 lists the products versions required for UR13.
Table 2-1 Product Versions Required for UR13
Product Version
BSC ZXG10 iBSC V6.30.20
ZXUR9000 GSM BSC V6.50.20
BTS SDR V4.13.xx
OMMR OMMRV12.13.1x
OMMB OMMB V12.13.4x
NetNumen U31 V12.13.5x
2.2 Capacity and Performance
2.2.1 BSC
The BSC models for UR13 are ZXG10 iBSC and ZXUR9000 GSM BSC. The equipment
capacity and performance of UR13 for ZXG10 iBSC and ZXUR9000 GSM BSC
(hardware version H1.0) are the same as those of UR12s.The UR13 supports
ZXUR9000 GSM BSC (hardware version H2.0) that has capacity and performance
improvement.
ZXG10 iBSC
Table 2-2 Capacity of iBSC
Max number of TRXs 3,072
Max number of cells 1,536
Max number of sites 1,536

BHCA 4,200K
Maximum Erl (Voice call) 15,000 Erl
Maximum PS Data Throughput 2,800 (basic module)

(MCS9 PDCH number) 12,000 (enhanced module)
ZXUR9000 GSM BSC
Table 2-3 Capacity of ZXUR9000 GSM BSC (Hardware Version: ZXUR9000 H1.0)
TDM A/Built-in
TC remote IP A/Without TC
TC
Max number of TRXs 5,600 12,000 12,250
Max number of cells 5,600 5,600 5,600
Max number of sites 2,800 2,800 2,800
BHCA 8,400K 16,800K 16,800K
Maximum Erl (Voice call) 33,600Erl 72,000Erl 73,500 Erl
Maximum PS Data
Throughput (MCS9 PDCH 19,600 42,000 42,800
number)
Table 2-4 Capacity of ZXUR9000 GSM BSC (Hardware version: ZXUR9000 H2.0)
TDM A/Built-in
TC remote IP A/Without TC
TC
Max number of TRXs 8,000 16,000 16,000
Max number of cells 8,000 8,000 8,000
Max number of sites 4,000 4,000 4,000
BHCA 11,200K 22,400K 22,400K
Maximum Erl (Voice call) 48,000 Erl 96,000 Erl 96,000 Erl
Maximum PS data
throughput (MCS9 PDCH 28,000 56,000 56,000
number)
Notes:
In Table 2-2, Table 2-3 and Table 2-4 :

BHCA can be achieved only in the ZTE traffic model for BHCA as show in Table2-4.
Table 2-5 ZTE Traffic Model for BHCA
Average call hold on time(s) 5
MO Call percentage 70%
CS traffic volume can be achieved only in the ZTE traffic model for voice call show
in Table 2-6.
Table 2-6 ZTE traffic model for voice call
Average call hold on time(s) 45
MO call percentage 50%
Handover attempts (times/call) 1.5
Location update attempts (times/call) 2
Short messages (times/call) 1
2.2.2 SDR
The capacity and performance specifications of UR13 are the same as those of UR12.
2.2.3 NetNumen
The capacity and performance specifications of UR13 are the same as those of UR12.
2.3 Hardware
2.3.1 BSC
ZXG10 iBSC
Compared with UR12 iBSC, UR13 iBSC introduces five new boards, as described in
Table 2-7.

Table 2-7 New Boards of ZXG10 iBSC
Board Board Full Name Function

Type Name
Universal Interface Module Switching of data and

Switch UIMC2
for Control Plane 2 signaling
Complete the Ethernet

Giga bit User Interface switch and TDM switch
Switch GUIM3
Module 3 function between user and
control plane
Interface SDTB3 Sonnet Digital Trunk Board 3 Provide 2 CSTM-1
Interface DTB3 Digital Trunk Board 3 32 E1/T1 digital trunk
TC, PCU, or RTP

Resource GUP3 GSM Universal Processing
processing
ZXUR9000 GSM BSC
Compared with UR12 ZXUR9000 GMS BSC, UR13 introduces one new board for
ZXUR9000 H1.0 and supports new hardware ZXUR9000 H2.0, as described in Table 2-8
Table 2-8 New Boards of ZXUR9000 GSM BSC
Board Type Board Full Name Function

Name
Interface Enhanced XGE Process Provides the IP 10GE

EXGB1b
ZXUR9000 H1.0 Board 1b interface
Process Universal Service Fulfills service processing

USP2a
ZXUR9000 H2.0 Process board function
Switch Enhanced GE Base The switch board of

EGBS2a
ZXUR9000 H2.0 Switch board control plane
Switch Enhanced GE Fabric The switch board of user

EXFS1a
ZXUR9000 H2.0 Switch board plane
Interface Enhanced Digital Trunk Provides the TDM E1

EDTT2a
ZXUR9000 H2.0 board TDM version interface
Enhanced SDH Digital

Interface Provides the TDM CSTM1
ESDTT2a Trunk board TDM
ZXUR9000 H2.0 interface
version

Board Type Board Full Name Function

Name
Enhanced SDH Digital

Interface Provides the TDM CSTM1
ESDTG2a Trunk board GSM
ZXUR9000 H2.0 interface
version
Interface Enhanced Digital Trunk Provides the IP E1

EDTI2a
ZXUR9000 H2.0 board IP version interface
Interface Enhanced SDH Digital Provides the IP CSTM1

ESDTI2a
ZXUR9000 H2.0 Trunk board IP version interface
Interface Enhanced GE Process Provides the IP GE/FE

EGPB2a
ZXUR9000 H2.0 Board interface
Interface Enhanced XGE Process Provides the IP 10GE

EXGB1a
ZXUR9000 H2.0 Board 1b interface
2.3.2 SDR
UR13 SDR includes the following hardware changes:
Adds some new boards, as listed in Table 2-9
Adds and Updated some SDR models, as listed in Table 2-10
No new hardware model
Table 2-9 New Boards of SDR
Change Type Board Type Board Name

New Fabric Switch Unit FS5C
New Control & Clock Module CCE1
Table 2-10 New Modules of SDR
Change Type Module Type Module Name Notes
New RRU R8862 S1800(B6A/B6B)
New RRU R8862A S1800(B6A/B6B)
Update RRU R8861 S1800(B8B/B8C) Support GL
Update RRU R8862 S9000(A6A/A6B) Support GL

and GUL

Change Type Module Type Module Name Notes
Update RRU R8882 S1800(B) Support GL
Update RRU R8882 S1800(B6C) Support GL

35MHz
Update RSU RSU82 S1800(B8A) Support GL
Update RSU RSU82 GUL1816 Support GL

35MHz
2.3.3 NetNumen
The server hardware and the hard disk capacity of UR13 are the same as those of UR12
2.4 Implementation
2.4.1 Upgrade Path
In a live network, UR11 and UR12 can be upgraded to UR13.
Versions earlier than UR11 must be upgraded to UR11 before being upgraded to UR13.
2.4.2 Upgrade from UR12 to UR13
Before upgrading from UR12 toUR13, ensure that all required hardware has been
installed and licenses that allow the required network capacity have been obtained.
Then perform the upgrade in the following order:
1. Upgrade the NetNumen to U31 V12.13.5x.
2. Upgrade the OMMR to V12.13.1x.
3. Upgrade the ZXG10 iBSC to V6.30.20 or ZXUR9000 GSM BSC to V6.50.20.
4. Upgrade the OMMB to V12.13.4x.

5. Upgrade the base stations to SDR V4.13.xx.
2.5 License
2.5.1 Changes in License Control Items
Compared with UR12, UR13 incorporates the following changes in license control items:
Deleted the license control items as described in Table 2-11.
Table 2-11 License Control Items Deleted from UR13
Feature ID Feature Name License Control Item License Change
None PCU Resources This item is deleted

support (per PS slave) because of the slave
configuration of CS and
PS has been incorporated
in UR13 version.
The added license control items for the UR13 new features as described in Table
2-12.
Table 2-12 License Control Items Added for UR13 New Features
Configured License Control Sales

Feature ID Feature Name
NE Item Unit
ZGO-01-02-010 Flexible TBF BSC Flexible TBF per

Multiplex Multiplex (per PDCH) PDCH
ZGO-01-02-014 Cooperative BSC Cooperative Service per

Service Optimization (per PDCH
Optimization PDCH)
ZGO-02-03-015 Mobility BSC Mobility Management per TRX

Management based SPID (per
based SPID TRX)
ZGO-02-03-017 GSM/LTE BSC NCCR from GSM to per TRX

NCCR LTE (per TRX)


NE Item Unit
ZGO-02-03-021 GSM/LTE Load BSC GSM/LTE Load per TRX

Sharing Sharing (per TRX)
ZGO-03-02-016 Dynamic BSC Dynamic Multiple per Cell

Multiple CCCHs (per Cell)
CCCHs
ZGO-03-05-009 Early TBF BSC Early TBF per

Establishment Establishment (per PDCH
PDCH)
ZGO-03-07-006 MOCN Network BSC MOCN Network per TRX

ZGO-04-01-012 Neighbor Cell BSC Neighbour Cell per TRX

Cooperation(N Cooperation(NCC)
CC) (per TRX)
ZGO-04-03-008 Dynamic BSC Dynamic Frequency per TRX

Frequency Allocation (per TRX)
Allocation
ZGO-05-04-032 802.3x Based BSC 802.3x Based Flow per TRX

Flow Control Control (per TRX)
ZGO-06-02-005 Enhanced A5/1 BSC Enhanced A5/1 (per per TRX

TRX)
The added license control items for old optional features before UR13 as described
in Table 2-13.
Table 2-13 License Control Items Added for Former Optional Features Before UR13

NE Item Unit
ZGO-01-01-002 Enhanced Full BSC Enhanced Full per TRX

Rate (EFR) Rate (EFR)
Speech Codec Speech Codec
(per TRX)


NE Item Unit
ZGO-01-01-005 Call BSC Call per TRX

Re-establishment Re-establishment
(per TRX)
ZGO-01-02-001 Support ARP in BSC Support ARP in per

Packet Scheduling Packet PDCH
Scheduling (per
PDCH)
ZGO-01-02-002 C/I based Packet BSC C/I based Packet per

Scheduling Scheduling (per PDCH
PDCH)
ZGO-01-02-004 Streaming Service BSC Streaming Service per

Policies Policies (per PDCH
PDCH)
ZGO-01-02-005 Flexible EGPRS BSC Flexible EGPRS per

scheduling priority scheduling priority PDCH
(per PDCH)
ZGO-01-03-001 eMLPP BSC eMLPP (per Cell) per Cell
ZGO-01-03-004 Cell Broadcast BSC Cell Broadcast per TRX

Service Service (per TRX)
ZGO-01-03-005 Dual Transfer BSC Dual Transfer per TRX

Mode Mode (per TRX)
ZGO-02-02-001 Handover BSC Handover per TRX

Between Macro- Between Macro-
and Micro-cells and Micro-cells
(per TRX)
ZGO-02-02-002 Dynamic BSC Dynamic per TRX

Handover Priority Handover Priority
Algorithm Algorithm (per
TRX)
ZGO-02-02-003 Directed-Shift BSC Directed-Shift per TRX

Handover Handover (per
TRX)


NE Item Unit
ZGO-02-02-004 SDCCH/SDCCH BSC SDCCH/SDCCH per TRX

TRX)
ZGO-02-02-006 Handover Based BSC Handover Based per TRX

on Uplink Level on Uplink Level
Fast Fading Fast Fading (per
TRX)
ZGO-02-02-007 Traffic Based BSC Traffic Based per TRX

TRX)
ZGO-02-02-010 Network-assisted BSC Network-assisted per

Cell Change Cell Change (per PDCH
PDCH)
ZGO-02-02-011 Inter-BSC NACC BSC Inter-BSC NACC per TRX

(per TRX)
ZGO-02-02-012 Network BSC Network per

Controlled Cell Controlled Cell PDCH
Reselection Reselection (per
PDCH)
ZGO-02-02-013 Different Cell BSC Different Cell per

Reselection Reselection PDCH
Parameters for Parameters for
IDLE and ACTIVE IDLE and ACTIVE
Status Status (per
PDCH)
ZGO-02-02-016 PS Handover BSC PS Handover (per per

PDCH) PDCH
ZGO-02-02-019 Handover BSC Handover per TRX

Command Power Command Power
Boost Boost (per TRX)
ZGO-02-02-020 Power BSC Power per TRX

Optimization After Optimization After
TRX)


NE Item Unit
ZGO-02-02-021 Handover Based BSC Handover Based per TRX

on Neighboring on Neighboring
Cells Level Ratio Cells Level Ratio
(per TRX)
ZGO-02-02-023 Enhanced BSC Enhanced per TRX

Measurement Measurement
Report Report (per TRX)
ZGO-02-03-001 GSM/TD-SCDMA BSC GSM/TD-SCDMA per TRX

Cell Reselection Cell Reselection
and CS Handover and CS Handover
(per TRX)
ZGO-02-03-002 GSM/WCDMA Cell BSC GSM/WCDMA per TRX

Reselection and Cell Reselection
CS Handover and CS Handover
(per TRX)
ZGO-02-03-003 GERAN/UTRAN BSC GERAN/UTRAN per TRX

Load Sharing Load Sharing (per
TRX)
ZGO-02-03-004 NCCR from GSM BSC NCCR from GSM per TRX
to 3G to 3G (per TRX)
ZGO-02-03-005 GSM/TD-SCDMA BSC GSM/TD-SCDMA per TRX

Interworking on Interworking on
Iur-g Interface Iur-g Interface (per
TRX)
ZGO-02-03-006 GSM/WCDMA BSC GSM/WCDMA per TRX

Interworking on Interworking on
Iur-g Interface Iur-g Interface (per
TRX)
ZGO-02-03-007 Fast Return from BSC Fast Return from per TRX
GSM to GSM to
TD-SCDMA TD-SCDMA (per
TRX)
ZGO-02-03-009 Fast Return from BSC Fast Return from per TRX
GSM to WCDMA GSM to WCDMA
(per TRX)


NE Item Unit
ZGO-02-03-011 Service Indicator in BSC Service Indicator per TRX

Handover and in Handover and
Reselection Reselection (per
TRX)
ZGO-02-03-019 CSFB from LTE to BSC CSFB from LTE to per TRX
GSM GSM (per TRX)
ZGB-03-01-005 Transmission BSC Transmission per TRX

Based Congestion Based Congestion
Control Control (per TRX)
ZGO-03-01-002 Transmission BSC Transmission per TRX

Based CAC Based CAC (A)
(per TRX)

Based CAC Based CAC (Abis)
(per TRX)
ZGO-03-01-003 Packet Channel BSC Packet Channel per TRX

Requesting Flow Requesting Flow
ZGO-03-01-004 SDCCH BSC SDCCH per TRX

Congestion Congestion
ZGO-03-02-004 HR Concentration BSC HR Concentration per TRX

(per TRX)
ZGO-03-02-006 Independent BSC Independent per TRX

Threshold for Threshold for
Dynamic AMR Dynamic AMR
HR/FR Conversion HR/FR
Conversion (per
TRX)
ZGO-03-02-007 MAC Extended BSC MAC Extended per

Dynamic Dynamic PDCH
Allocation Allocation (per
PDCH)


NE Item Unit
ZGO-03-02-008 EGPRS on BSC EGPRS on per

BCCH-TRX BCCH-TRX PDCH
Configurable Configurable (per
PDCH)
ZGO-03-02-009 Flexible Priority BSC Flexible Priority per

Handling of Packet Handling of PDCH
Data Channel Packet Data
Channel (per
PDCH)
ZGO-03-02-010 GPRS and BSC GPRS and per

EGPRS Channels EGPRS Channels PDCH
Allocated Allocated
Separately Separately (per
PDCH)
ZGO-03-02-011 Channel BSC Channel per

Repacking Repacking (per PDCH
PDCH)
ZGO-03-03-004 Transparent BSC Transparent per TRX

Channel Channel (per
TRX)
ZGO-03-03-005 N*64K High speed BSC N*64K High speed per TRX
Signaling Link Signaling Link (per
TRX)
ZGO-03-04-001 Automatic BCCH BSC Automatic BCCH per TRX

Recovery Recovery (per
TRX)
ZGO-03-04-002 Abis Link Backup BSC Abis Link Backup per BTS
(per BTS)
ZGO-03-04-002 Abis Link Backup SDR Abis Link Backup per BTS
(per BTS)
ZGO-03-04-003 BTS Main Control SDR BTS Main Control per BTS
Board Backup Board Backup
(per BTS)


NE Item Unit
ZGO-03-04-005 Baseband BSC Baseband per TRX

Resource Dynamic Resource
Sharing Dynamic Sharing
(per TRX)
ZGO-03-05-001 Modulation and BSC Modulation and per

Coding Scheme Coding Scheme PDCH
#1~#9 #1~#9 (per
PDCH)
ZGO-03-05-002 EGPRS Link BSC EGPRS Link per

Adaptation Adaptation (per PDCH
PDCH)
ZGO-03-05-006 Incremental BSC Incremental per

Redundancy in UL Redundancy in UL PDCH
(per PDCH)
ZGO-03-05-010 Early TBF BSC Early TBF per

Establishment Establishment PDCH
Downlink Downlink (per
PDCH)
ZGO-03-07-001 Basic BSS Sharing BSC Basic BSS per TRX

for Multiple Sharing for
Operators Multiple Operators
(per TRX)

Sharing on Abis Sharing on Abis
Interface for Interface for
Multiple Operators Multiple Operators
(per TRX)
ZGO-03-07-005 PCU Resource BSC PCU Resource per

Flexible Sharing Flexible Sharing PDCH
for Multiple for Multiple
Operators Operators (per
PDCH)
ZGO-04-01-002 Delay Diversity SDR Delay Diversity per RU

Transmission Transmission
(DDT) (DDT) (per RU)


NE Item Unit
ZGO-04-01-004 Four Way Diversity SDR Four Way per RU

Receiving(FWDR) Diversity
Receiving(FWDR)
(per RU)
ZGO-04-01-005 Interference BSC Interference per TRX

Rejection Rejection
Combining (IRC) Combining (IRC)
(per TRX)
ZGO-04-01-006 Static Power SDR Static Power per TRX

ZGO-04-01-007 Dynamic Power BSC Dynamic Power per TRX

ZGO-04-01-008 Multi Timeslot BSC Multi Timeslot per TRX

Supported in Supported in
Extended Cell Extended Cell (per
TRX)
ZGO-04-01-010 Power Congestion BSC Power Congestion per TRX

ZGO-04-02-001 Dynamic BTS BSC Dynamic BTS per TRX

Power Control Power Control
(per TRX)
ZGO-04-02-002 Dynamic MS BSC Dynamic MS per TRX

(per TRX)
ZGO-04-02-003 Discontinuous BSC Discontinuous per TRX

Downlink Downlink (per
TRX)
ZGO-04-02-004 Discontinuous BSC Discontinuous per TRX

Uplink Uplink (per TRX)
ZGO-04-02-005 Co-BCCH BSC Co-BCCH (per per TRX

TRX)
ZGO-04-02-006 TFO BSC TFO (per TRX) per TRX


NE Item Unit
ZGO-04-02-009 Repeated BSC Repeated per TRX

FACCH/SACCH FACCH/SACCH
(per TRX)
ZGO-04-02-010 Automatic Level BSC Automatic Level per TRX

Control (ALC) Control (ALC) (per
TRX)
ZGO-04-02-011 Automatic Noise BSC Automatic Noise per TRX

Reduction (ANR) Reduction (ANR)
(per TRX)
ZGO-04-02-012 Acoustic Echo BSC Acoustic Echo per TRX

Cancellation Cancellation
(AEC) (AEC) (per TRX)
ZGO-04-02-014 Extended uplink BSC Extended uplink per TRX

TBF mode TBF mode (per
TRX)
ZGO-04-02-015 Intelligent UL/DL BSC Intelligent UL/DL per TRX

timeslot timeslot
adjustment adjustment (per
TRX)
ZGO-04-02-017 Downlink Rapid BSC Downlink Rapid per TRX

(per TRX)
ZGO-04-02-025 Power BSC Power per TRX

Optimization After Optimization After
Access Access (per TRX)
ZGO-04-03-001 Synthesized BSC Synthesized per TRX

Frequency Frequency
Hopping Hopping (per
TRX)
ZGO-04-03-002 Support of 64 BSC Support of 64 per TRX

Frequencies Frequencies
TRX)


NE Item Unit
ZGO-04-03-004 Baseband BSC Baseband per TRX

Frequency Frequency
TRX)
ZGO-04-03-005 Antenna Hopping SDR Antenna Hopping per RU

(per RU)
ZGO-04-03-007 Intelligent BSC Intelligent per TRX

Frequency Frequency
Timeslot Timeslot
Allocation(IFTA) Allocation(IFTA)
(per TRX)
ZGO-04-04-003 Intelligent Timeslot BSC Intelligent per TRX

Shutdown Timeslot
Shutdown (per
TRX)
ZGO-04-04-008 Intelligent BCCH BSC Intelligent BCCH per TRX

Power Reduction Power Reduction
(per TRX)
ZGO-04-04-010 Intelligent SDR Intelligent per BTS

Baseband Baseband
Shutdown Shutdown (per
BTS)
ZGO-04-05-007 Detection of BSC Detection of per TRX

Mute-SAIC Mobile Mute-SAIC Mobile
Stations Stations (per TRX)
ZGO-04-05-008 Detection of SAIC BSC Detection of SAIC per TRX

Mobile Stations Mobile Stations
with AFC Problem with AFC Problem
(per TRX)
ZGO-04-05-009 Shift SACCH BSC Shift SACCH (per per TRX

TRX)
ZGO-04-05-010 Downlink Signaling BSC Downlink per TRX

Signaling (per
TRX)


NE Item Unit
ZGO-05-01-001 Abis Interface over BSC Abis Interface per TRX

Satellite over Satellite (per
TRX)
ZGO-05-01-003 Gb Interface over BSC Gb Interface over per TRX

Satellite Satellite (per TRX)
ZGO-05-02-002 EGSM Frequency BSC EGSM Frequency per TRX

Band Support Band Support (per
TRX)
ZGO-05-02-003 Multiple Cells BSC Multiple Cells per TRX

Support Support (per TRX)
ZGO-05-02-009 Concentric Circle BSC Concentric Circle per TRX

Technology Technology (per
TRX)
ZGO-05-02-013 BBU Chain SDR BBU Chain per BTS

Networking Networking (per
BTS)
ZGO-05-02-016 BSC Backup SDR BSC Backup (per per BTS

BTS)
ZGO-05-02-018 RRU Chain SDR RRU Chain per BTS

Networking Networking (per
BTS)
ZGO-05-02-019 BBU cascading SDR BBU cascading per BTS

(per BTS)
ZGO-05-03-005 Network Wide BSC Network Wide per Cell

Synchronization Synchronization
on GPS on GPS (per Cell)
ZGO-05-03-005 Network Wide SDR Network Wide per BTS

Synchronization Synchronization
on GPS on GPS (per BTS)
ZGO-05-04-001 Abis over IP BSC Abis over IP (per per TRX

TRX)
ZGO-05-04-002 Gb over IP BSC Gb over IP (per per TRX

TRX)


NE Item Unit
ZGO-05-04-003 A over IP BSC A over IP (per per TRX

TRX)
ZGO-05-04-004 Enhanced IP Abis BSC Enhanced IP Abis per TRX

(per TRX)
ZGO-05-04-005 IP SLA Monitoring BSC IP SLA Monitoring per TRX

(per TRX)
ZGO-05-04-006 IP Connectivity BSC IP Connectivity per TRX

Check Check (per TRX)
ZGO-05-04-008 802.3ah Based BSC 802.3ah Based per TRX

Ethernet OAM Ethernet OAM
(per TRX)
ZGO-05-04-008 802.3ah Based SDR 802.3ah Based per BTS

(per BTS)
ZGO-05-04-009 802.1P/Q Based BSC 802.1P/Q Based per TRX

QoS QoS (per TRX)
ZGO-05-04-009 802.1P/Q Based SDR 802.1P/Q Based per BTS

QoS QoS (per BTS)
ZGO-05-04-010 Ethernet Link BSC Ethernet Link per TRX

Aggregation Aggregation (per
TRX)
ZGO-05-04-011 Bidirectional BSC Bidirectional per TRX

Forwarding Forwarding
Detection Detection (per
TRX)
ZGO-05-04-011 Bidirectional SDR Bidirectional per BTS

Forwarding Forwarding
Detection Detection (per
BTS)
ZGO-05-04-012 Path Protection BSC Path Protection per TRX

(per TRX)
ZGO-05-04-013 IP Traffic Shaping BSC IP Traffic Shaping per TRX

(per TRX)


NE Item Unit
ZGO-05-04-014 ARP Checking BSC ARP Checking per TRX

(per TRX)
ZGO-05-04-015 Synchronous BSC Synchronous per TRX

Ethernet Ethernet (per
TRX)
ZGO-05-04-016 Y.1731 Based BSC Y.1731 Based per TRX

Ethernet Ethernet
Performance Performance (per
TRX)
ZGO-05-04-017 802.1ag Based BSC 802.1ag Based per TRX

(per TRX)
ZGO-05-04-018 OSPF BSC OSPF (per TRX) per TRX
ZGO-05-04-025 IPv6 BSC IPv6 (per TRX) per TRX
ZGO-05-04-029 VRF BSC VRF (per TRX) per TRX
ZGO-05-05-004 Abis Triggered BSC Abis Triggered per TRX

FR/HR Adaptation FR/HR Adaptation
(per TRX)
ZGO-06-01-002 Speech Quality BSC Speech Quality per TRX

Supervision Supervision (per
TRX)
ZGO-06-01-007 DHCP BSC DHCP (per TRX) per TRX
ZGO-06-01-008 Call Detail BSC Call Detail per TRX

Trace(CDT) Data Trace(CDT) Data
Report Report (per TRX)
ZGO-06-01-011 Uplink Spectrum SDR Spectrum Scan per

Online Scan OMMB
ZGO-06-01-013 Base Station Auto SDR Base Station Auto per BTS
Provision Provision (per
BTS)
ZGO-06-01-016 VSWR Position SDR VSWR Location per

Detection Measurement OMMB


NE Item Unit
ZGO-06-01-017 Antenna Feeder SDR Passive Inter per

Passive Modulation OMMB
Inter-modulation Detection
Detection
ZGO-06-02-001 A5/3 Ciphering BSC A5/3 Ciphering per TRX

Algorithm Algorithm (per
TRX)
ZGO-06-02-002 Random Fill Bits BSC Random Fill Bits per TRX
(per TRX)
ZGO-06-02-003 Access Control BSC Access Control per TRX

List List (per TRX)
The added license control items for capacity related in UR13 described in Table
2-14
Table 2-14 License Control Items Added for Capacity Related in UR13
Configured Sales
Feature ID Feature Name License Control Item
NE Unit
ZGO-05-04- BSC IP Gb flow control (per 64kbps

Gb over IP
002 kbps)
2.5.2 Changes in License Control Modes
None.
2.6 Inter-NE Interfaces
In UR13, interfaces between each BSC and other NEs and between each BTS and UEs
comply with the 3rd Generation Partnership Project (3GPP) Release 10 and are
backward compatible with 3GPP Releases 9, 8, 7, 6, 5, 4, and 99. These interfaces are A,
Gb, Lb, Abis, and Um.

For the impacts of each feature imposed on these interfaces, see Chapter 4 "Impacts of
UR13 Features on UR12.
2.7 Operation and Maintenance
The UR13 introduces new and enhanced features and internal system optimizations.
Therefore, MML commands, parameters, performance counters, alarm and Informs, and
licenses have changed. For the impacts of each new and enhanced feature on operation
and maintenance, see Chapter 4 "Impacts of UR13 Features on UR12." The operation
and maintenance changes for the BSC and BTS are closely related to the software
version. For detailed changes in a specific software version, see the following change
documents in the BSC and BTS release documentations:
MML command changes
Parameter changes
Performance counter changes
Alarm and Inform changes
License changes
2.8 Other NEs
For the impacts of each new and enhanced feature imposed on other NEs, see Chapter
4 "Impacts of UR13 Features on UR12."
3 Summary of Feature Impacts

The Table 3-1 and Table 3-2 list the impact severity of new and enhanced features in
UR13.
For details about the impacts of each new and enhanced feature, see Chapter 4 "Impacts
of UR13 Features on UR12".

Feature impacts are categorized as "Major" when either of the following conditions is
met:
The feature requires the new or additional hardware.
The feature impacts UR13 features or NEs.
All other impacts are categorized as "Minor."
Table 3-1 Impact Severity of New/Optional Features in UR13
Feature ID Feature Name Impact Severity

ZGO-01-02-010 Flexible TBF Multiplexing Minor
ZGO-01-02-014 Cooperative Service Optimization Minor
ZGO-01-02-015 PS Service Acceleration based on Traffic Minor
ZGO-02-03-015 Subscriber Profile ID(SPID) Minor
ZGO-02-03-016 GSM/LTE SRVCC Minor
ZGO-02-03-017 GSM/LTE NCCR Minor
ZGO-02-03-019 CSFB from LTE to GSM Minor
ZGO-02-03-021 GSM/LTE Load Sharing Minor
ZGO-03-01-005 Priority Based PS Congestion Control Minor
ZGO-03-02-016 Dynamic Multiple CCCHs Minor
ZGO-03-05-009 Early TBF Establishment Uplink Minor
ZGO-03-07-006 MOCN Network Sharing Major

ZGO-04-01-012 Uplink Neighbor Cell Coordination Major
ZGO-04-03-008 Dynamic Frequency Allocation Major
ZGO-05-04-031 802.3x Based Flow Control Minor
ZGO-05-04-030 IP Anti-DoS Attack Minor
ZGO-06-02-005 Enhanced Encryption Mechanism Minor
ZGO-06-01-020 Super Signaling Trace Major
Table 3-2 Impact Severity of Enhanced/ Optional Features in UR13

ZGO-01-03-004 Cell Broadcast Service Minor


ZGO-01-03-005 Dual Transfer Mode Minor
ZGO-02-03-014 Fast Return from GSM to E-UTRAN Minor
ZGO-04-02-006 TFO Minor
ZGO-04-03-007 Intelligent Frequency Timeslot Allocation(IFTA) Minor
ZGO-05-04-002 Gb over IP Minor
ZGO-05-04-005 IP SLA Monitoring Minor
ZGO-05-04-013 IP Traffic Shaping Minor
ZGO-05-04-025 IPv6 Major
ZGO-05-05-001 BSC Local Switch Major
ZGO-05-05-002 BTS Cluster Local Switch Minor
ZGO-05-05-003 BTS Local switch Minor
ZGO-06-01-002 Speech Quality Supervision Minor
4 Impacts of UR13 Features on UR12
4.1 ZGO-01-02-010 Flexible TBF Multiplexing
4.1.1 Description
TBFs of multiple PS users can be multiplexed onto one PDCH. The actual data traffic of
these TBFs may vary according to the different applications that they bear. When there
are a lot of frequent small packet applications in the network, a lot of TBFs thus are in
releasing delay state, which do not transfer the user data, but they are still counted in
TBF multiplexing. As a result, when new PS services are accessing, it is more likely that
new established TBFs cannot be multiplexed onto the occupied PDCHs, but another new
group of PDCHs is needed to allocate, which is inefficient.
With Flexible TBF Multiplexing feature enabled, the BSS identifies active TBFs (TBFs
with user data on transfer) and inactive TBFs (TBFs with no user data on transfer). When
the BSS calculates the TBF multiplex number at TBF allocation and release, only active

TBFs are counted, while inactive TBFs are neglected. By this way, more TBFs can be
multiplexed onto one PDCH.
With this feature enabled, the PDCH efficiency is greatly improved when there are large
numbers of frequent small packet applications in the network.
4.1.2 Capacity and Performance
System Capacity
This feature brings higher TBF Multiplexing on one PDCH, which increases system
capacity.
Network Performance
This feature imposes the following impacts on the network performance
In general, the PDCHs occupied by users in cell are expected to decrease by about
10%-20% but packet service payload will be effected less, which improves basic KPI
TBF Multiplexing by about 10%-15% and makes the PDCH transmission more efficient;
For PDCH congestion, if this feature is activated, the PDCH congestion in the cells will
decrease or be solved;
Normally this feature brings slight deterioration to KPIs such as UL or DL TBF drop rate.
4.1.3 Impact on NEs
This feature is implemented on BSC and OMC.
4.1.4 Hardware
No impact
4.1.5 Inter-NE Interfaces
No impact.

4.1.6 Operation and Maintenance
License
This feature is under the license control.
Table 4-1 Flexible TBF Multiplexing License Description

NE Item Unit
Flexible TBF
Flexible TBF per
ZGO-01-02-010 BSC Multiplexing (per
Multiplexing PDCH
PDCH)
Configuration Management
Table 4-2 Parameters Related to This Feature
Change Type Parameter Name Description
New support TBF This parameter enables or disables

multiplexing of active-TBF-based TBF multiplexing.
active TBF
Performance Management
This feature affects basic KPI TBF Multiplexing which is defined as C900040138/
C900040140.
Table 4-3 Counters Related to This Feature
Counter ID Counter Name Description
C900040138 Average number of total This counter counts the sum of PDCHs
PDCH used by all TBF used by all TBF
C900040140 Average number of used This counter counts the average number
PDCH of used PDCHs in serving cell
Fault Management

No impact.
4.1.7 Impact on Other Features
Prerequisite Features
No impact.
Mutually Exclusive Features
No impact.
Impacted Features
No impact.
4.2 ZGO-01-02-014 Cooperative Service Optimization
4.2.1 Description
Some Over the Top (OTT) service cooperates with wireless network operators, or pays
extra fee to get better services. Here, these service providers are called cooperative
customers, and their services are called cooperative services.
With Cooperative Service Optimization feature enabled, network operators can configure
the IP addresses, domain names and priority level of the servers of cooperative services.
When a PS service is set up, the BSS matches the IP addresses and domain names with
configuration, identifies the cooperative services, and adjusts the resource schedule
priority of the service according to the configured priorities. This feature schedules more
radio resources for cooperative services and improves the service quality.
This feature does not require any modification of the CN or UE.
System Capacity

No impact
Network Performance
This feature enables the wireless network operator to provide more resources for
cooperative services or self-operated services, which leads to better service quality.
4.2.3 Impact on NEs
4.2.4 Hardware
No impact
No impact
License
Table 4-4 Cooperative Service Optimization License Description

NE Item Unit
Cooperative Cooperative Service

per
ZGO-01-02-014 Service BSC Optimization (per
PDCH
Optimization PDCH)

New PartnerIndex The number is the unique Index of

Partner.
New PartnerDomainName Domain Name of Partner for Internet.
New Priority Added The priority increment for Partner. The

Amount higher the value, the greater the priority
increment.
New Used PLMN Group The list contains up to 4 PLMN IDs,

indicates which operators support the
function "Cooperative Service
Optimization".
New Partner IP Length The length of IP address of partner,

support IPv4 and IPv6.
New Partner IP Addr IP address of partner.
No impact
Fault Management
No impact
No Impact
No impact
Impacted Features
No impact

4.3 ZGO-01-02-015 PS Service Acceleration based on

Traffic
4.3.1 Description
TBFs of multiple PS users can be multiplexed onto one PDCH. The BSS gives
scheduling priority weights to TBFs according to QoS parameters from the CN and the
radio environment conditions. Usually, the BSS does not give a higher scheduling priority
to high-traffic TBFs.
With this feature enabled, high-traffic service thresholds and scheduling priority
enhancements can be configured on the BSS. The BSS counts the LLC frame bytes of
each TBF. When the high-traffic service threshold is met, the related TBF is given a
higher scheduling priority. As a result, high-traffic PS services get a higher data rate and
better user experience.
System Capacity
No impact.
Network Performance
This feature provides the following benefits on the network performance:
The service throughput in network will be increased by 3%-10%.
In some scenario, the wireless operators ask for KPI improvement such as ratio of high
speed users with high traffic service, which usually are HTTP, WAP or FTP users. This
feature improves the ratio by 20%-80%.
4.3.3 Impact on NEs

4.3.4 Hardware
No impact.
No impact.
License
This feature is not under the license control.
New This parameter indicates whether rate

control is enabled for large throughput
Rate control of large services. This switch is enabled if rate
throughput service control is needed when the throughput
exceeds the threshold specified by the
parameter LargeTPEnhanceThrs.
New This parameter indicates the expected

Expected rate
stable rate during the rate control.
New This parameter indicates the

amplification step of scheduling factor
Adaptive rate for increasing the rate to the expected
adjustment amplifier value. The amplification precision is
step 0.01. The factor amplification is
calculated according to the formula:
factor step/100.

New This parameter indicates the minification

step of scheduling factor for decreasing
Adaptive rate
the rate to the expected value. The
adjustment minification
minification precision is 0.01. The factor
step
minification is calculated according to
the formula: factor step/100.
New This parameter determines the schedule

for triggering adaptive rate adjustment. If
Adaptive rate the parameter is set to 0, rate control is
adjustment periodic triggered when the throughput meets
execution schedule the threshold. If the parameter is set to
1, rate control is triggered when the
timer AdptSchedTime expires.
New This parameter indicates the adaptive

rate adjustment period. It is effective
only when AdptSched is set to 1. After
the adaptive rate adjustment is triggered
by threshold crossing throughput, the
rate is adjusted periodically according to
Adaptive rate
this period. At expiry of this timer, rate
adjustment period
adjustment is performed no matter
whether the throughput exceeds the
threshold, unless the number of
adjustment times reaches the maximum
number of adjustment times or the rate
reaches the expected value.
New This parameter indicates the large

throughput threshold that determines
whether the rate needs to be enhanced.
The large throughput
If LargeTPRateCtrl is set to 1 and the
traffic enhance
downlink throughput exceeds this
threshold
threshold, the adaptive rate adjustment
is performed to achieve the expected
rate.
New This parameter indicates the resource

Matched HTTP IP adjustment threshold for services of the
resource adjustment server with the matched IP address
threshold when the HTTP rate enhancement or
partner service optimization is enabled.

New This parameter indicates the rate

threshold that determines whether rate
enhancement is triggered. If the traffic
reaches the corresponding threshold
and the service rate is lower than this
Adaptive start rate
threshold, rate adjustment is triggered to
enhance the service rate.
AdptStartRate must be smaller than the
difference between ExptRate and
AdptAllowRateUpDown.
New This parameter indicates the allowable

fluctuation range of the expected rate.
The rate adjustment is completed if the
Adaptive rate allowed
rate is between the value
up and down
(ExptRate-AdptAllowRateUpDown) and
the value
(ExptRate+AdptAllowRateUpDown).
New This parameter indicates whether rate

reduction is allowed. If the initial rate of
Indication of drop rate
a TBF is high, the rate can be reduced
only when AllowDropRate is set to 1.
This feature will increase the basic KPI as following:
GPRS Downlink LLC throughput (single user): C901020074*8/C901020033
EGPRS Downlink LLC throughput (single user): C901020076*8/C901020043

C901020074 Accumulated throughput This counter counts the total downlink
of downlink GPRS TBF GPRS throughput in a cell.
C901020033 Total bytes carried by This counter counts total bytes of LLC
GPRS downlink data frame sent by BSC on GPRS TBF and
TBF LLC frame acknowledged by MS successfully.

C901020076 Accumulated throughput This counter counts the total downlink

of downlink EGPRS TBF EGPRS throughput in a cell.
C901020043 Total bytes carried by This counter counts total bytes of LLC
EGPRS downlink data frame sent by BSC on EGPRS TBF and
TBF LLC frame acknowledged by MS successfully.
Fault Management
No impact.
No impact.
No impact.
Impacted Features
No impact.
4.4 ZGO-02-03-015 Subscriber Profile ID (SPID)
4.4.1 Description
Subscriber Profile ID (SPID) is introduced in 3GPP R8 protocol for automatic cell

reselection, that is, the inter-RAT cell reselection based on priorities. These priorities are
recorded in HLR through the subscriber profile, which are called individual priorities for
special users. Special users have individual priorities, which means the public priorities
broadcast by System Information are invaild. The process is described as follows. First of
all, the SGSN transfers SPID to the BSS. The BSS maps the SPID with the individual
priorities, and then informs individual priorities to special terminals through Packet Cell
Change Order (PCCO) or Packet Measurement Order (PMO). Finally terminals replace

public priorities with individual priorities, and determine the cell reselection strategy with
updated priorities.
The ZTE GSM supports cell reselection based on SPID. This feature controls terminals
automatic cell reselection according to operators strategy configured. In the protocol
36.300, three SPID values are defined to map to inter-RAT priorities, which is shown in
the following table:
SPID values E-UTRAN UTRAN GERAN
256 high medium Low
255 low high Medium
254 low medium High
System Capacity
No impact.
Network Performance
This feature helps effectively to control the inter-RAT cell reselection according to the
subscriber profile, which shortens the cell reselection duration to improve users
experience eventually.
4.4.3 Impact on NEs
4.4.4 Hardware
No impact.
No impact.

License
Table 4-8 Subscriber Profile ID (SPID) License Description

NE Item Unit
Subscriber Subscriber Profile

ZGO-01-02-010 BSC per TRX
Profile ID(SPID) ID(SPID) (per TRX)
New SPID based inter-RAT This parameter indicates whether the

cell reselection priority cell supports SPID-based inter-RAT cell
reselection priorities.
New T3230 This parameter indicates the valid

duration of the independent priority.

C901160037 Number of packet This counter counts the number of
measurement order including packet measurement order
individual priorities including individual priorities
Fault Management
No impact.

No impact.
No impact.
Impacted Features
No impact.
4.5 ZGO-02-03-016 SRVCC from LTE to GSM
4.5.1 Description
Single Radio Voice Call Continuity (SRVCC) is a classical Voice over LTE continuity
solution to guarantee smooth handover between IP Multimedia Subsystem (IMS)
controlled Voice over IP and CS, which is introduced in 3GPP R8. When users prepare to
apply CS voice in the LTE network and they move to the area where LTE signal is weak
but GSM signal is strong, it is necessary to hand over to GSM through SRVCC from LTE
to ensure users voice continuity
The ZTE GSM supports SRVCC handover from LTE to GSM. Since handover process is
reused with the existing process of inter-system handover, only the BSS should support
handover statistics to monitor SRVCC handover from LTE to GSM.
System Capacity
No impact.
Network Performance

If IMS is deployed, the LTE network can provide seamless handovers for VoIP calls
between the PS domain and the CS domain through SRVCC when LTE VoIP users
move from LTE to 2G/3G.
4.5.3 Impact on NEs
This feature is implemented on the BTS, BSC and OMC.
4.5.4 Hardware
No impact.
MME/IMS/MSC must be configured to support this feature.
License
No impact.
C902500019 Number of SRVCC This counter counts the number of

handover attempts SRVCC handover attempts

handover SRVCC handover

handover success SRVCC handover success

Fault Management
No impact.
No impact.
No impact.
Impacted Features
No impact.
4.6 ZGO-02-03-017 NCCR from GSM to LTE
4.6.1 Description
NCCR from GSM to LTE means NC2 network control mode from GSM to LTE. The
network demands the MS to send measurement reports, and the procedure is controlled
by the network. In order to support NC2 from GSM to LTE, the BSS should support
neighbor cell configuration of LTE, and then send cell information and measurement of
different systems through PACKET MEASUREMENT ORDER (PMO) to the MS.
Meanwhile, the MS should support LTE and NC2 from GSM to LTE at packed transfer
mode.
When the BSS achieves NC2 from GSM to LTE, the BSS triggers NC2 from GSM to LTE
based on coverage when the GSM serving cells receiving level is lower than lever
threshold, according to measurement reports and systems configuration. And then the
BSS determines the priority strategy to select a suitable target cell to achieve NC2
according to Service E-UTRAN CCO from SGSN and the BSS configuration, including
LTE cells preferred, GSM cells preferred and LTE cells not allowed.

System Capacity
No impact.
Network Performance
This feature helps effectively to achieve packet service balance between the GSM and
LTE networks, which decreases GSM network traffic and achieves efficient operation
and maintenance of GSM and LTE networks as well.
4.6.3 Impact on NEs
4.6.4 Hardware
No impact.
SGSN/MME must be configured to support this feature.
Table 4-12 GSM/LTE NCCR License Description

NE Item Unit
Cell Reselection to
GSM/LTE
ZGO-01-02-010 BSC LTE with NCCR (per per TRX
NCCR
TRX)

New Support GSM to LTE NC2 This parameter indicates whether

network-controlled cell reselection
from GSM to LTE is supported.
This feature can be used with
between 2G cells, but cannot be
used with network-controlled cell
reselection between 2/3G cells.
New Service E-UTRAN CCO This parameter indicates the

preferred policy of
from GSM to E-UTRAN. The
policy contains E-UTRAN
preferred, GSM preferred, and
E-UTEAN not allowed. The cell
change order may be based on
the Service E-UTRAN CCO of the
SGSN or the preferred policy
configured on the BSC.
C901160034 Number of packet cell This counter counts the number of

change notification to packet cell change notification to
E-UTRAN E-UTRAN

change order to packet cell change order to E-UTRAN
E-UTRAN

change failure to packet cell change failure to E-UTRAN
E-UTRAN
Fault Management

No impact.
ZGO-02-02-012 Network Controlled Cell Reselection
This feature conflicts over NC2 feature in 2G/3G, restricted through OMM configuration.
No impact.
Impacted Features
No impact.
4.7 ZGO-02-03-019 CSFB from LTE to GSM
4.7.1 Description
Circuit Switched Fallback (CSFB) is a typical CS solution when users reside in the LTE
network, which was introduced in 3GPP R8. When users prepare to apply for CS in the
LTE network but the IP Multimedia Subsystem is not deloyed yet, which means the LTE
network is not capable of providing CS directly, LTE shifts them to the GSM network to
continue CS through CSFB. The LTE network initially informs the MS to release the link
with LTE, and then the MS begins to search and finally reselects the GSM cell
successfully. This function is enhanced in 3GPP R9 to transfer the GSM cell system
information in the LTE network when informing the MS to release the LTE link, which
speeds up the reselection procedure and thus reduces the establishment delay of CS.
The ZTE GSM supports CSFB from LTE to GSM. For the BSC, the R8 CSFB access
procedure is reused together with the existing CS access procedure. The R9 CSFB
access procedure is also reused together with the exisiting RIM procedure, which means
the LTE cell gets the GSM cells system information through the RAN Information
Request and the BSC reports the changes of the GSM cells system information to the

LTE cell through the RAN Information Send to shorten the time delay caused by cell
reselection.
This feature requires the support from the GSM/LTE terminal, LTE and CN.
System Capacity
No impact.
Network Performance
Time of CSFB call setup is influenced by some optional procedures configured in LTE
and GSM network sides, such as authentication/cipher mode/TMSI reallocation
procedure etc. In some commercial networks, the time is about 4s-9s or more.
4.7.3 Impact on NEs
4.7.4 Hardware
No impact.
MME/MSC must be configured to support this feature.
License

Table 4-15 CSFB from LTE to GSM License Description
Feature ID Feature Name Configured License Sales

NE Control Item Unit
ZGO-02-03-019 CSFB from LTE to BSC CSFB from TRX

GSM LTE to GSM
No parameters.
No impact.
Fault Management
No impact.
No impact.
No impact.
Impacted Features
No impact.

4.8 ZGO-02-03-021 GSM/LTE Load Sharing
4.8.1 Description
The RAN Information Management (RIM) procedure of SON Transfer Application type is
introduced to 3GPP R9 protocol for cell load transferring between different Radio Access
Technologies. Utilizing the existing RIM procedure of Gb interface, when the BSS
receives RAN Information Request from the CN and then decides the Application Type is
SON Transfer and SON Transfer Application Identity is Cell Load Reporting, the BSS
transfers the target GSM cells load to the LTE network. The GSM cell load transferring
includes single cell load transferring and multi-cells load transferring.The ZTE GSM is
capable of transferring the load of as many as 75 GSM cells to the LTE through the RIM
procedure mentioned above, which balances the load from LTE to GSM effectively. In
addition to that, the BSS triggers NC2 from GSM to LTE based on the load when the
GSM serving cells load is higher than the load threshold, which balances the load from
GSM to LTE precisely.
System Capacity
No impact.
Network Performance
ZTE GSM products support transferring the load up to 75 GSM cells to an LTE network
through the RIM SON Transfer procedure for load sharing between LTE and GSM. In
addition, if the BSS determines that GSM cell load is higher than the threshold, it triggers
load-based NC2 reselection from GSM to LTE to achieve the load sharing between GSM
and LTE.
4.8.3 Impact on NEs

4.8.4 Hardware
No impact.
SGSN/MME must be configured to support this feature.
License
Table 4-16 GSM/LTE Load Sharing License Description
Feature ID Feature Name License Configured Sales

Control Item NE Unit
ZGO-02-03-021 GSM/LTE Load GSM/LTE BSC TRX

Sharing Load Sharing

New This parameter indicates whether the BSC

supports SON transfer applications. The
SON transfer application is implemented by
an RIM procedure. Therefore, the RIM
support must be enabled for the SON
Support of SON transfer application. When both the RIM
Transfer support and the SON transfer application
Application are enabled, the BSC can respond to the
requests for GSM cell load from an external
UTRAN or E-UTRAN through the RIM
procedure on the Gb interface, and
synchronize the load with the external
network.
No impact.
Fault Management
No impact.
ZGO-02-03-013 Inter-RAT NACC
The RIM procedure used by this feature is the same as that of inter-RAT NACC. The only
difference is that SON Transfer is added in information elements.
No impact.
Impacted Features
No impact.

4.9 ZGO-03-01-005 Priority Based PS Congestion

Control
4.9.1 Description
With this feature activated, the network operator can configure which types of users and
applications can be reduced in timeslot numbers or can be released in case of PS traffic
congestion.
The BSC calculates the PS traffic of each cell in real time. When the PS traffic exceeds a
configured threshold, the BSC reduces the timeslots occupied by some users and
applications. According to the configuration, some users and applications at low priority
are reduced in the timeslot numbers, and some users and applications are released by
force. As a result, more high-priority users and applications can access the network, and
their user experience is improved.
User priority of a PS connection together with other QoS information is passed from the
core network.
Application types of a PS connection are identified by the BSC via the Deep Packet
Inspection (DPI) function, or passed from the core network when the BSC is not
deployed with the DPI function.
If the BSC is neither able to acquire the application types by DPI nor by the core network,
the BSC only cuts the timeslot numbers of those PS connections whose timeslot
numbers have exceeded the configured threshold in case of PS traffic congestion. No
forced release is carried out.
System Capacity
This feature makes the CMP load growth of about 1%.
Network Performance

This feature provides the following impacts on network performance in access

congestion scenario:
High priority users and applications access success rate can be improved in the
scenario where the high priority users and applications are needed to be protected when
network is congested.
4.9.3 Impact on NEs
This feature is implemented on the BSC and OMC.
4.9.4 Hardware
No impact.
4.9.5 Inter-NE Interface
No impact.
License
Table 4-18 Priority Based PS Congestion Control License Description

NE Item Unit
Priority Based
Priority Based PS
ZGO-03-01-005 PS Congestion BSC TRX
Congestion Control
Control

Table 4-19 New Parameters Related to This Feature
New Traffic control This parameter indicates whether

based on service priority-based PS service flow control is
priority enabled. If the function is enabled, specific
services are processed accordingly based
on the TimeSlotOff and ForceRel
configurations when the system is in
congestion state.
New Allowed TimeSlot If the system cannot identify the service type
Number and user class and TrafficPrioCtr is enabled,
TimeSlotOff is allowed only when the
number of the current occupied time slots is
greater than or equal to a threshold. This
parameter indicates this threshold.
New TimeSlot off based This parameter indicates whether time slot
on service and reduction is allowed. This parameter is set
subscriber based on the service type and user class.
New Force release This parameter indicates whether forced

based on service service release is allowed. This parameter is
and subscriber set based on the service type and user
class. If both TimeSlotOff and ForceRel are
enabled, ForceRel is preferred.
Table 4-20 New Counters Related to This Feature
C901170073 Number of downlink This counter counts the number of

GPRS TBF release owing downlink GPRS TBF release owing to
to the traffic control by the traffic control by service priority.
service priority
C901180075 Number of downlink This counter counts the number of

EGPRS TBF release downlink EGPRS TBF release owing to
owing to the traffic control the traffic control by service priority.
by service priority

C901190105 Number of uplink GPRS This counter counts the number of

TBF release owing to the uplink GPRS TBF release owing to the
traffic control by service traffic control by service priority.
priority
C901200107 Number of uplink EGPRS This counter counts the number of

TBF release owing to the uplink EGPRS TBF release owing to
traffic control by service the traffic control by service priority.
priority
Fault Management
No impact.
No impact.
No impact.
Impacted Features
No impact.
4.10 ZGO-03-02-016 Dynamic Multiple CCCHs
4.10.1 Description
Currently, the adjustment of the configuration of CCCH channel is made by manual

operation only, which leads to the poor timeliness, high maintenance workload and low
efficiency.
With this feature activated, the system is capable of automatically adjusting the CCCH
channel configuration according to the network load. The traffic capacity and signaling

capacity can be balanced in real-time. This feature improves the channel utilization while
reduces the manual maintenance workload.
System Capacity
No impact.
Network Performance
If too many paging demands come, the dynamic MCCCHs help to improve the paging
successful rate. System uses TCH change to CCCH dynamically. Therefore, when the
paging passed, the dynamic MCCCH changes back to TCH.
We suggest to lower the priority of BCCH TRX so as to avoid the timeslot 2, 4, 6 being
occupied by TCH.
4.10.3 Impact on NEs
4.10.4 Hardware
No impact.
No impact.
License

Table 4-21 Dynamic Multiple CCCHs License Description

NE Item Unit
Dynamic Dynamic Multiple

ZGO-03-02-016 CELL CELL
Multiple CCCHs CCCHs (per CELL)
Change Parameter Name Description

Type
New This parameter controls whether the

dynamic MCCCH function is enabled.
When the system paging load is
strongly fluctuated, this function is
Dynamic configuration CCCH enabled. With other related
parameters set, the paging channel
quantity on the BCCH carrier can be
dynamically adjusted based on actual
paging load.
New This parameter indicates the paging

load threshold over which the CCCH
channel capacity should be
increased. Paging load = the number
of paging blocks in the buffer / the
maximum number of paging blocks
available on the current paging
PCH threshold For CCCH channels
Expand The default value is obtained in
specific cases, and is only for
reference. This parameter should be
adjusted according to actual paging
message loss. If many paging
messages are lost with this parameter
set to the default value, the threshold
should be decreased accordingly.


Type
New This parameter indicates the paging

PCH threshold For CCCH load threshold below which the CCCH
Restore channel capacity should be
decreased.
New When paging load is higher than

DynMccchHighThs and the duration
Hysteresis For CCCH Expand is longer than a threshold, the CCCH
capacity is increased. This parameter
indicates the threshold.
New When paging load is lower than

DynMccchLowThs and the duration is
Hysteresis For CCCH Restore longer than a threshold, the CCCH
capacity is decreased. This
parameter indicates the threshold.

Maximum Timeslot Number
maximum number of TSs that can be
For CCCH Expand
converted to the CCCH.

Minimum Tch reserved for minimum number of free TCHs
dynamic MCCCH reserved in a cell when the CCCH
capacity is increased.

Number of attempt from This counter counts the number of
C901080078 TCH to CCCH when attempt from TCH to CCCH when
dynamic MCCCH validate dynamic MCCCH is applied.
Number of success covert This counter counts the number of

C901080079 from TCH to CCCH when success covert from TCH to CCCH
dynamic MCCCH validate when dynamic MCCCH validates
Number of attempt from This counter counts the number of

C901080080 CCCH to TCH when attempt from CCCH to TCH when
dynamic MCCCH validate dynamic MCCCH is applied.

Number of success covert This counter counts the number of

C901080081 from CCCH to TCH when success covert from CCCH to TCH
dynamic MCCCH validate when dynamic MCCCH validates
Average Number of This counter counts the average

C901080082
dynamic CCCH number of dynamic CCCH
Maximum Number of This counter counts the maximum

C901080091
dynamic CCCH number of dynamic CCCH
Total time of dynamic This counter counts the total time of

C901080092
CCCH occupied dynamic CCCH occupied
Message Number of This counter counts the Message

C901280125
ABIS_CCCH_EXPAND Number of ABIS_CCCH_EXPAND
Handover attempt number This counter counts the handover

C901060112 of TCH/F when dynamic attempt number of TCH/F when
MCCCH validate dynamic MCCCH validates
Handover attempt number This counter counts the handover

C901060113 of TCH/H when dynamic attempt number of TCH/H when
MCCCH validate dynamic MCCCH validates
Fault Management
No impact.
No impact.
When ZGO-04-03-004 Baseband Frequency Hopping is enabled on BCCH TRX, this

feature could not be used.
Impacted Features
The timeslots 2, 4, 6 of BCCH TRX could not be used for SDCCH enlarge, when
ZGB-03-02-003 Dynamic SDCCH feature activates.

4.11 ZGO-03-05-009 Early TBF Establishment Uplink
4.11.1 Description
Usually, the MS applies for uplink TBF resources only when it has data to send. The BSC
then starts the TBF allocation process.
With the early TBF establishment feature, when the BSC has established a downlink
TBF for the MS, and the MS has no uplink TBF, the uplink TBF resource allocation is
triggered. The BSC allocates the uplink TBF resources for the MS and sets the TBF to
inactive state. In a specified period, the MS can send uplink data directly without
establishing an uplink TBF. If no uplink data is sent, the BSC releases the uplink TBF
after the specified period.
With the early TBF establishment feature activated, the delay of the uplink data is
decreased by hundreds of milliseconds (about the time for TBF establishment). This
improves the user experience of the session services such as the PoC service, VoIP
service and IM service.
This feature is introduced in 3GPP Release 7 and requires the support of MS.
System Capacity
No impact.
Network Performance
This feature reduces the delay time of uplink data transfer by about 40ms-80ms, which
improves the user experience of the session services such as the PoC service, VoIP
service and IM service.
This feature brings little PDCH congestion in uplink direction in the scenario where cells
have insufficient PDCHs.

4.11.4 Hardware
No impact.
No impact.
License
Table 4-24 Early TBF Establishment Uplink License Description

NE Item Unit
Early TBF Early TBF

per
ZGO-03-05-009 Establishment BSC Establishment
PDCH
Uplink Uplink (per PDCH)
New support uplink tbf This parameter indicates a switch that

early controls whether to support the uplink
establishment pre-established TBF function.

C901010096 Number of request for This counter is incremented by one when

early establishing uplink the BSC receives an early TBF
TBF establishment request if the early TBF
establishment function is enabled. When
the BSC receives a Packet Resource
Request message or (EGPRS) Packet
Downlink Ack/Nack message, if the
EARLY_TBF_ESTABLISHMENT field is
included and its value is 1, this request is
considered as an early TBF
establishment request.
C901010097 Number of success for When the BSC receives a Packet

early establishing uplink Resource Request message or
TBF (EGPRS) Packet Downlink Ack/Nack
message, if the
EARLY_TBF_ESTABLISHMENT field is
included and its value is 1, this request is
considered as an early TBF
establishment request. After the radio
resource is assigned to the MS and the
uplink TBF is established, this counter is
incremented by one if the early TBF
establishment function is enabled.
Fault Management
No impact.
No impact.
No impact.
Impacted Features

No impact.
4.12 ZGO-03-07-006 MOCN Network Sharing
4.12.1 Description
Multi-Operator Core Network in GSM network, which is introduced to 3GPP R10 protocol,
is a classical network sharing mode that mulitple operators share the same wireless
resources but their Core Networks (CN) are independent. Since the same GSM cell is
shared by multiple operators, the common PLMN is broadcast in this GSM cell.
When the MS conducts LA/RA update or attaches in the sharing area for the first time,
the BSS tries to access one of the multiple operators CNs according to certain accessing
proportion, which can be configured on the OMCR. If the access attempt fails, the CN will
make the BSS try to access another operators CN, that is reroute. When the CN asks for
the coordination of CS and PS, that is CS and PS of the same user should access the
same operators CN, the BSS selects one operators CN to access the user according to
MSs IMSI. In addition, the BSS controls the user to hand over in one operators cells due
to the current operator of UE.
This feature requires the support of the CN.
System Capacity
No impact.
Network Performance
This feature provides the following benefits on network performance:
Helps effectively to enable multiple operators share the same GSM cell, saving
network investment.
This feature is implemented on the BSC and OMC, requiring the support of the CN.

4.12.4 Hardware
No impact.
No impact.
License
Table 4-27 MOCN Network Sharing License Description

NE Item Unit
MOCN Network MOCN Network

ZGO-03-07-006 BSC TRX
Sharing Sharing(per TRX)
New This parameter indicates a referred PLMN

GPLMN DN
DN, that is, the public operator's PLMN.
New This parameter indicates a shared area DN,
GMocnArea DN that is, a shared area defined in
GMocnArea.
New This parameter indicates the attribute of an
MOCN shared area. It indicates whether the
Mocn Area Attribute
MOCN shared area is in this BSC or other
BSCs.
New This parameter indicates a referred
PlmnGroup DN PlmnGroup DN, that is, the PLMN in the
shared area.

New This parameter indicates a referred GPLMN

GPLMN DN DN, that is, the PLMN in the internal shared
area.
New This parameter indicates the service
distribution ratio of shared operators. It
Service Distribute
should be configured based on the
Ratio
distribution ratio of actual services. The
default value is rarely used.
New This parameter indicates the BCC level
Support Mocn switch that controls whether to support
MOCN.
New This parameter indicates a timer for waiting
for the MSC response after the BSC initiates
Wait reroute
a rerouting procedure and attempts to
respond timer of CS
access the MSC during an MOCN
implementation.

C902730001 Number of select this These counter counts the number of
PLMN by paging source selecting this PLMN by paging source
for CS for CS access when the network
supports MOCN.

PLMN not by paging selecting this PLMN not by paging
source for CS source for CS access when the
network supports MOCN.
C902730003 Number of PS select this These counter counts the number of

PLMN by CS PS selecting this PLMN by CS,
including this PLMN selected by
sending SUSPEND/RESUME and
GTTP message, when the network
supports MOCN.


PLMN by paging source selecting this PLMN by paging source
for PS for PS access when the network
supports MOCN.
PLMN not by paging selecting this PLMN not by paging
source for PS source for PS access when the network
supports MOCN.
Fault Management
No impact.
No impact.
No impact.
Impacted Features
No impact.
4.13 ZGO-04-01-012 Uplink Neighbor Cell Coordination
4.13.1 Description
The GSM system adopts the cellular structure to handle the conflicts between traffic
demands and the limited frequency resources. But inevitably, the frequency multiplexing
accompanying with the cellular structure will cause a lot of interferences, together with
other kinds of interferences, making the GSM network easily interfered. When the MS is
on the edge of a cell, the long distance to the BTS makes it particularly easy to be
interfered. The weaker the signal, the stronger the interference is. Consequently, the

uplink receiving Signal to Noise Ratio of the BTS is lower, making the uplink performance
of the users on the cells edge worse.
The uplink signals of the MS on the cells edge are very likely to be received by its
adjacent cells as well. For the common BTS, the uplink signals before the MSs handover
to the adjacent cell are merely the interfering signals. But for the SDR-based BTS, the
baseband resources can be integrated and shared, which indicates that the uplink
signals of the serving cell and of the adjacent cell can be processed together in a
baseband resource pool; the IQ signals from multiple ways are combined, which turns
the interfering signals into useful signals; therefore, the speech quality is good and
handover is more precise through these interferences.
Figure 4-1 Uplink Neighbor Cell Coordination
After the MS has established the radio connection to the BTS, the BSS decides whether
the MS is on the edge of the cell (or in the area overlapped with one neighbor cell) and
decides its corresponding neighbor cell through the measurement data (including
measurement reports, TA, etc.) of the MS and the serving cell.
If the MS is in an overlapped area, and meanwhile there are adjacent cells which share a
BBU resource pool with the serving cell, select a proper adjacent cell and inform the
adjacent cell of the MSs current frequency point, timeslot, frequency hopping, etc. The
adjacent cell selected receives the MSs uplink signals. The BBU combines the signals
received by the adjacent cell and the serving cell.
In other words, this feature enables the uplink diversity receiving through the adjacent

cell, which brings extra diversity gain.
System Capacity
No impact.
Network Performance
It benefits the uplink RQ(0-4) ratio when NCC is enabled.
This feature is implemented on the BTS and OMC.
4.13.4 Hardware
SDR series base stations support this feature.
No impact.
License
Table 4-30 Uplink Neighbor Cell Coordination License Control Description

NE Item Unit
Neighbour Cell Neighbour Cell

ZGO-04-01-012 Cooperation(NC BSC Cooperation TRX
C) (NCC)(per TRX)


Type
New NCC Config Parameter The neighbor cell coordination feature

allows the serving cell to use free RU
resources and BP resources, and idle
optical ports of a neighbor cell. In addition, it
supports four receiving channels in uplink by
combining the antennas in the neighbor cell,
and allows the neighbor cell to receive
uplink signals of MSs in the serving cell.
This feature improves the uplink
performance.
New RxQual Threshold This parameter indicates the uplink RQ
threshold that determines whether to enable
the neighbor cell coordination. When the
uplink RQ is lower than this threshold, the
neighbor cell coordination is enabled.
Table 4-32 New counters Related to This Feature

C370900000 NCC_Attempt_Number The attempt number of cell NCC
The cell NCC failure number because of
C370900001 NCC_Failure_Number_No_BP
no BP resources
C370900002 NCC_Failure_Number_No_RU
no RU resources
C370900003 NCC_Failure_Number_No_FS
no FS resources
NCC_Failure_Number_Electrical_ The cell NCC failure number because of
C370900004
level electrical level
C370900005 NCC_Request_Number The request number of cell NCC
C370900006 NCC_ACK_Number The ACK number of cell NCC
C370900007 NCC_NACK_Number The NACK number of cell NCC


The cell NCC release number because
C370900008 NCC_Channel_Release_Number
of Channel Release
C370900009 NCC_DBB_Release_Number
of DBB release
C370900010 NCC_GSPS_Release_Number
of GSPS release
This counter counts the duration of

C370900011 NCC_Duration
cell NCC
As a Ncc Cell,The NCC

This counter counts the number of
C370900012 release number because of
cell NCC supply
Channel Release
As a Ncc Cell,The NCC This counter counts the NCC

C370900013 release number because of release number because of
DBB release Channel Release
This counter counts the NCC

The number of NCC IQ config
C370900014 release number because of DBB
times
release
The number of NCC IQ delete This counter counts the number of

C370900015
times NCC IQ config times
The number of NCC resource This counter counts the number of

C370900016
supplied by Neighbor Cell NCC IQ delete times
Neighbor Cell's NCC release This counter counts the number of

C370910000 number because of Channel NCC resource supplied by Neighbor
Release Cell
Neighbor Cell's NCC release This counter counts the Neighbor

C370910001 number because of DBB Cell's NCC release number
release because of Channel Release
Neighbor Cell's NCC release This counter counts the Neighbor

C370910002 number because of DBB Cell's NCC release number
release because of DBB release
Fault Management
No impact.

No impact.
No impact.
Impacted Features
No impact.
4.14 ZGO-04-03-008 Dynamic Frequency Allocation
4.14.1 Description
Normally TRX and frequency resources are planned and configured based on the max
cell traffic load in the traditional GSM network planning and construction. But generally
different cells in the network fail to achieve the traffic peak at the same time, then the max
traffic load of the network will be much lower than the sum of the max traffic load of all
cells in the network, which is the so-called the tide phenomenon of traffic load.
This feature can dynamically allocate and release cells frequency resources in the area
with tide phenomenon of traffic load. The system releases the frequency resources of
suitable dynamic TRX when the cells traffic load is lower than the threshold configured,
and allocates the suitable frequency to suitable dynamic TRX when the cells traffic load
is higher than the threshold configured.
In network with this feature enabled, several dynamic TRXs and several static TRXs are
configured in cells. Static TRXs include BCCH TRX and part of the high priority TCH
TRXs. Dynamic TRXs do not support frequency hopping while static TCH TRX does.
System Capacity
No impact.

Network Performance
By reducing the number of activated carrier frequency, dynamic frequency planning

can effectively improve the channel utilization and the spectral efficiency, but may
impose a negative effect on the uplink and downlink RQ.
4.14.4 Hardware
No impact.
License
Table 4-33 Dynamic Frequency Allocation License Description
Configu Sales
red NE Unit
ZGO-04-03-008 Dynamic Frequency Dynamic Frequency

BSC TRX
Allocation Allocation (per TRX)


New Support Dynamic This parameter is a BSC-level switch
Frequency Allocate controlling dynamic frequency allocation.
New Observe upLink This parameter indicates whether uplink
Interference when interferences are considered before
allocate frequency dynamic frequency allocation is enabled.
New This parameter indicates whether
Observe downLink
downlink interferences are considered
Interference when
before dynamic frequency allocation is
allocate frequency
enabled.
Observe other trx
interferences on other corresponding
Interference when
carriers are also considered before
allocate frequency
dynamic frequency allocation is enabled.
New This parameter indicates whether both
Observe traffic when interferences and traffic load on the
allocate frequency carrier are considered before dynamic
frequency allocation is enabled.
Observe Interference
adjacent-channel interferences are also
of neighbor
considered besides co-channel
frequency when
interferences before dynamic frequency
allocate frequency
allocation is enabled.
New This parameter indicates the traffic
statistic period when both interferences
Statistic period of
and traffic load on the carrier are
traffic on trx
considered for dynamic frequency
allocation.
New This parameter specifies the attenuation
Reduce of neighbor
used for calculating the uplink
frequency uplink
adjacent-channel interference before
Interference
dynamic frequency allocation is started.
New This parameter specifies the attenuation
Reduce of neighbor
used for calculating the downlink
frequency Downlink
adjacent-channel interference before
Interference
dynamic frequency allocation is started.


New Use neighbour This parameter indicates whether the
frequency in cell adjacent frequencies can be allocated to
permitted the dynamic carrier to be started.
New This parameter indicates whether an
interference threshold is used when
frequencies are allocated to the dynamic
Use interference
carrier to be started. If an interference
threshold
threshold is used, when the interference
exceeds the threshold InterfThres,
frequencies cannot be allocated.
New This parameter indicates the interference
threshold used when frequencies are
allocated to the dynamic carrier to be
Interference
started. If UseInterfThres is set to 1, when
threshold
the interference exceeds the threshold
InterfThres, frequencies cannot be
allocated.
New This parameter specifies whether the
Forbid TRX due
poor-quality carriers are disabled if
quality
dynamic frequency allocation is enabled.
New This parameter specifies the uplink quality
UplinkThreshold of
threshold over which poor-quality carriers
Forbid TRX due
are disabled if dynamic frequency
quality
New This parameter specifies the downlink
Downlink Threshold
quality threshold over which poor-quality
of Forbid TRX due
carriers are disabled if dynamic frequency
quality
New This parameter specifies the minimum
Mimimum Quality quality samples required to disable
Sample poor-quality carriers if dynamic frequency
New This parameter indicates the power level
difference between sub-cells when
Level difference of
interferences are estimated for dynamic
Subcell1 and
frequency allocation. With this power level
Subcell2
difference, interferences can be estimated
more accurately in sub-cells.


New This parameter indicates the frequency
Frequency Band band that the frequencies in the dynamic
frequency pool belong to.
New This parameter indicates the frequency
list in the dynamic frequency pool. The
Arfcn List
frequencies are used for dynamic
allocation.
carrier is a dynamic carrier. A dynamic
carrier is allocated with a frequency only
Dynamic Trx
when the traffic volume is high and the
dynamic frequency allocation function is
enabled.

C901080085 When attempting to enable a
dynamic TRX, CMP requires OMP
to allocate a frequency, if OMP
Start using dynamic TRX failure
fails to allocate the frequency and
due to OMP assign ARFCN fail
returns a failure to CMP, the
counter will be incremented by
one.
dynamic TRX, CMP requires OMP
Start using dynamic TRX failure
to allocate a frequency, if theres
due to OMP assign ARFCN
no response from OMP within a
timeout
certain time, the counter will be
incremented by one.
dynamic TRX, after getting the
Start using dynamic TRX failure frequency from OMP, CMP will set
due to Set ARFCN to BTS fail the frequency to BTS. If BTS
returns a failure, the counter will
be incremented by one.


dynamic TRX, after getting the
Start using dynamic TRX failure frequency from OMP, CMP will set
due to Set ARFCN to BTS the frequency to BTS. If theres no
timeout response from BTS within a
certain time, the counter will be
incremented by one.
Start using dynamic TRX failure dynamic TRX, if BTS is on data
due to conflict with data config configuration, the activation will
procedure fail and the counter will be
incremented by one.
dynamic TRX, if for any other
Start using dynamic TRX failure reason except for the reason that
due to other reason have separated counters lead to
failure, the counter will be
incremented by one.
C901230144 When the cell traffic turns high,
Number of start using dynamic dynamic TRX will be enabled, if
TRX successfully, the counter will be
incremented by one.
C901230145 When the uplink quality of
dynamic TRX is worse than a
Number of forbid dynamic TRX
certain threshold, the TRX will be
due to bad uplink quality
disabled and the counter will be
incremented by one.
C901230146 When the downlink quality of
dynamic TRX is worse than a
Number of forbid dynamic TRX
certain threshold, the TRX will be
due to bad downlink quality
disabled and the counter will be
incremented by one.
C901230147 When the statistical period arrives,
Duration of dynamic TRX in use accumulate the total seconds that
dynamic TRX has been enabled.
C901230148 When the statistical period arrives,
Frequency used by dynamic
query the frequency that dynamic
TRX
TRX uses from database.


C901010098 During PS service, if GPRS uplink
Number of GPRS uplink TBF
TBF is released due to dynamic
release due to forbid dynamic
TRX is disabled, this counter will
TRX
be incremented by one.
C901010099 During PS service, if EGPRS
Number of EGPRS uplink TBF uplink TBF is released due to
release due to forbid dynamic dynamic TRX is disabled, this
TRX counter will be incremented by
one.
C901000102 During PS service, if GPRS
Number of GPRS downlink TBF downlink TBF is released due to
release due to forbid dynamic dynamic TRX is disabled, this
TRX counter will be incremented by
one.
C901000103 During PS service, if EGPRS
Number of EGPRS downlink downlink TBF is released due to
TBF release due to forbid dynamic TRX is disabled, this
dynamic TRX counter will be incremented by
one.
C901060125 If dynamic TRX is disabled, BSC
will try to handover service to
Number of TCH/F intra-cell
other TRX in the same cell or
handover attempts due to forbid
other cell, this counter counts the
dynamic TRX
TCH/F intra-cell handover
attempts.
Number of TCH/H intra-cell
dynamic TRX
TCH/H intra-cell handover
attempts.
Number of TCH/F inter-cell
dynamic TRX
TCH/F inter-cell handover
attempts.


Number of TCH/H inter-cell
dynamic TRX
TCH/H inter-cell handover
attempts.
Fault Management
No impact.
No impact.
ZGO-04-03-001 Synthesized Frequency Hopping
ZGO-04-03-004 Baseband Hopping
ZGO-04-03-007 Intelligent Frequency Timeslot Allocation (IFTA)
Impacted Features
No impact.
4.15 ZGO-05-04-030 IP Anti-DoS Attack
4.15.1 Description
Denial of Service (DoS), could be a method to attack a computer or network so that it

cannot provide normal services. The most common DoS attack against a computer
network bandwidth and connectivity attacks.

Since UR13, BSC supports anti-DoS attacks, including the following functions.
1. Abnormal packets discard
Discards unknown VLAN packet, unknown Ethertype packet, and unknown IP

protocol packet.
Detects and discards IP packets of abnormal packet length, abnormal ICMP

packet length, and abnormal IP packet fragment.
Detects and discards those ICMP/UDP packets with source address being
broadcast address.
2. Abnormal packets suppression
Detects and suppresses broadcast packets, unknown multicast packets and

unknown unicast packets.
Detects and suppresses those IP packets with same IP address of source and
destination.
3. Anti-DoS protection
Protects RNC from ICMP Flood, UDP Flood, SYN Flood, ACK Flood and those
high volume packets attacks.
System Capacity
No impact.
Network Performance
No impact.
4.15.4 Hardware
GIPI4, EGPB or EGPB2 board.

No impact.
License
Table 4-36 Parameters Related to This Feature for iBSC

Type
This parameter specifies the

high threshold of rate limit for
non-service packets.
When packets received on the
user plane require relatively
complex processing, they need
to be forwarded to the control
plane for processing. To
reduce the impact on the
control plane, the rate at which
the user plane forwards these
Non business message general
New packets to the control plane
speed limit
should be limited.
Non-service packets that
require rate limit include
relatively unimportant packets
related to network protocols,
for example, broadcast
packets, multicast packets,
ICMP packets, and slow
protocol packets. Packets that
use the high threshold include
ARP, ND and IKE.


Type

length of the timer for IP
reassembly. When fragmented
IP packets are reassembled,
local resources are occupied. If
a fragment of an original IP
packet does not arrive for a
long period of time, the
fragments already received
have to be cached locally and
cannot be released. If this case
frequently occurs, local
resources are greatly
IP recombination timeout
New consumed and even
threshold
exhausted when the situation
gets more serious, resulting in
that the subsequent packets
cannot be processed in time.
length of wait time since the
first fragment is received. If not
all the fragments of an original
IP packet arrive within the time
set here, the IP reassembly
expires and the fragments
already received are
discarded.


Type

separate threshold for
limitation of NoArp packets.
This parameter is set similarly
to the Unit.ArpMsgGenSpLmt
configuration with the
New ARP failed message speed limit difference that
Unit.ArpMsgGenSpLmt is an
accumulative threshold value
of all packets while
Unit.ArpMsgSpLmt is a
threshold value specific to a
single entry.

global threshold for limitation of
NoArp packets. When an
Ethernet interface board sends
out an IP packet, it looks up in
the ARP table (for IPv4
packets) based on the
next-hop address. If it does not
ARP failed message general find the corresponding
New
speed limit information, it forwards the IP
packet to the control plane to
initiate ARP learning.
total number (accumulative
value) of packets that are
forwarded to the control plane
per second due to ARP lookup
failures by the user plane.


Type

limitation of NoArp packets.
This parameter is set similarly
to the Unit.PortMsgGenSpLmt
New Port failed message speed limit difference that
Unit.PortMsgGenSpLmt is an
of all packets while
Unit.PortMsgSpLmt is a
threshold value specific to a
single entry.

NoOutput packets. The
Ethernet interface board needs
to look up the actual egress
port for a packet to be
transmitted on an aggregate
port. If the lookup fails, these
Port failed message general
New packets should be sent to the
speed limit
control plane for processing.
per second due to Output
lookup failures by the user
plane.


Type

NoOutput packets. The
Ethernet interface board needs
to look up SA for a packet that
requires IPSEC processing. If
the lookup fails, these packets
New SA failed message speed limit should be sent to the control
plane for processing.
per second due to SA lookup
failures by the user plane.
Table 4-37 Parameters Related to This Feature for ZXUR9000

Type


Type
New This parameter specifies the

high threshold of rate limit for
High threshold for non-service
packets to the control plane
packets
should be limited.
Non-service packets that
require rate limit include
relatively unimportant packets
related to network protocols,
for example, broadcast
packets, multicast packets,
ICMP packets, and slow
protocol packets. Packets that
use the high threshold include
ARP, ND and IKE.


Type

low threshold of rate limit for
packets to the control plane
should be limited. Non-service
Low threshold for non-service
New packets that require rate limit
packets
include relatively unimportant
packets related to network
protocols, for example,
broadcast packets, multicast
packets, ICMP packets, and
slow protocol packets. Packets
that use the low threshold
include broadcast packets,
multicast packets, RARP
packets, ICMP packets, and
non-service bearer IP packets
other than those that use the
high threshold.


Type

length of the timer for IP
reassembly. When fragmented
IP packets are reassembled,
local resources are occupied. If
a fragment of an original IP
packet does not arrive for a
long period of time, the
fragments already received
have to be cached locally and
cannot be released. If this case
frequently occurs, local
resources are greatly
New Timer length for IP reassembly consumed and even
exhausted when the situation
gets more serious, resulting in
that the subsequent packets
cannot be processed in time.
length of wait time since the
first fragment is received. If not
all the fragments of an original
IP packet arrive within the time
set here, the IP reassembly
expires and the fragments
already received are
discarded.


Type

packets including NoArp,
NoND, NoSa and NoOutput.
When an Ethernet interface
board sends out an IP packet,
it looks up in the ARP table (for
IPv4 packets) or the ND table
(for IPv6 packets) based on
the next-hop address. If it does
not find the corresponding
information, it forwards the IP
packet to the control plane to
initiate ARP or ND learning.
Global threshold for limitation of Similarly, the Ethernet
New the packets such as: NoArp, interface board needs to look
NoND, NoSa, NoOutput up the actual egress port for a
packet to be transmitted on an
aggregate port, and SA for a
packet that requires IPSEC
processing. If the lookup fails,
these packets should be sent
to the control plane for
processing.
per second due to ARP, ND,
Output and SA lookup failures
by the user plane.


Type

limitation of packets including
NoArp, NoND, NoSa and
NoOutput. This parameter is
set similarly to the
Separated threshold for limitation
BMcsUnitAttr.GlobalThrd
New of the packets such as: NoArp,
NoND, NoSa, NoOutput
difference that
BMcsUnitAttr.GlobalThrd is an
of all packets while this
parameter is a threshold value
specific to a single entry.
Table 4-38 New Counters Related to This Feature for iBSC
Number of packets This counter counts the number of

C905020001 discarded from media core packets discarded from media core to
to control core control core

C905020002 discarded for packets discarded for
noarp/nond/nooutport/nosa noarp/nond/nooutport/nosa

C905020003 discarded for reassemble packets discarded for reassemble
timeout timeout
Number of fragmented This counter counts the number of

C905020004 packets discarded for fragmented packets discarded for
teardrop attach teardrop attach
Number of broadcast This counter counts the number of

C905020005 packets discarded for high broadcast packets discarded for high
CPU use ratio CPU use ratio

Number of multicast This counter counts the number of

C905020006 packets discarded for high multicast packets discarded for high
Number of ICMP packets This counter counts the number of

C905020007 discarded for high CPU ICMP packets discarded for high CPU
use ratio use ratio
Number of IPv4 packets This counter counts the number of

C905020008 discarded for high CPU IPv4 packets discarded for high CPU
use ratio use ratio

C905020009 discarded for high CPU IPv6 packets discarded for high
use ratio CPU use ratio
Table 4-39 New Counters Related to This Feature for ZXUR9000

C380780001 discarded from media core packets discarded from media core to
to control core control core

C380780002 discarded for packets discarded for
noarp/nond/nooutport/nosa noarp/nond/nooutport/nosa

C380780003 discarded for reassemble packets discarded for reassemble
timeout timeout
Number of fragmented This counter counts the number of

C380780004 packets discarded for fragmented packets discarded for
teardrop attach teardrop attach
Number of broadcast This counter counts the number of

C380780005 packets discarded for high broadcast packets discarded for high
Number of multicast This counter counts the number of

C380780006 packets discarded for high multicast packets discarded for high
Number of ICMP packets This counter counts the number of

C380780007 discarded for high CPU ICMP packets discarded for high CPU
use ratio use ratio


use ratio use ratio

use ratio use ratio
Fault Management
No impact.
No impact.
No impact.
Impacted Features
No impact.
4.16 ZGO-05-04-031 802.3x Based Flow Control
4.16.1 Description
IEEE 802.3x is a data link level flow control method used in the Ethernet in full duplex
mode, in which when one end or client detects the system or network congestion, it
sends PAUSE frame to indicate the other end or the server to stop sending the Ethernet
frame in order not to make the network worse.
The ZTE BSC supporting 802.3x based flow control enables the BSC to notify the
congestion status of itself or network to the networking node, like switches or routers or

vice versa; and then the switches or routers send PAUSE frame to the BSC to indicate its
congestion, thus making the whole BSS system more stably to provide service.
System Capacity
No impact.
Network Performance
When the peer side supports the PAUSE frame, which can pause data transmission
when receiving PAUSE frame, it reduces the Ethernet packet loss caused by Ethernet
congestion, accordingly improves the network QoS.
4.16.4 Hardware
No impact.
No impact.
License
Table 4-40 802.3x Based Flow Control License Description

NE Item Unit

ZGO-05-04-032 802.3x Based BSC 802.3x Based Flow per TRX

Flow Control Control (per TRX)
Table 4-41 Parameters Related to This Feature for iBSC
New It is the switch of 8023X function. When it is

Ethernet Port set to open, if the flow on receiving direction
PAUSE Flag exceed threshold on external port, RNC will
send PAUSE frame to sender.
New If the flow on receiving direction is below low

PAUSE frame low
threshold on external port, RNC will stop
threshold
sending PAUSE frame to sender.
New PAUSE frame If the flow on receiving direction exceed high

threshold on external port, RNC will send
high threshold PAUSE frame to sender.
Table 4-42 Parameters Related to This Feature for ZXUR9000
It is the switch of 8023X function.

When it is set to open, if the flow rate
New Flow Control on receiving direction exceed
threshold on external port, RNC will
send PAUSE frame to sender.
If the flow rate on receiving direction is
below the threshold on external port,
RNC will stop sending PAUSE frame
New Flow Rate to sender. If the flow rate on receiving
direction exceeds the threshold on
external port, RNC will send PAUSE
frame to sender.
No impact.
Fault Management
No impact.

No impact.
No impact.
Impacted Features
No impact.
4.17 ZGO-06-02-005 Enhanced Encryption Mechanism
4.17.1 Description
A5/1, which is widely adopted by the GSM system, is easy to break down. To further
enhance the GSM security, this feature includes the following mechanisms.
Supports the early SDCCH handover, which means when receiving cipher
command from the core network, the BSC indicates the MS to perform SDCCH
handover before entering ciphering mode in order to make it difficult for the intruder
to attack;
Supports neighbour cell description change; the BSC changes the content of the
Neighbour Cell Description information element by including ARFCNs not in a
frequency band supported by the MS when changing the ciphering mode from not
ciphered to ciphered with algorithm A5/1;
Supports random fit fitting in SI6, e.g. in SI6 Rest Octets.
System Capacity
No impact.
Network Performance

The optimization of this feature has the following impacts on network performance in
Enhanced Encryption Mechanism:
SDCCH occupation duration increases.
SDCCH congestion probability increases for the sites where SDCCH resources are
insufficient.
SDCCH handover times increases.
4.17.4 Hardware
No impact.
License
Table 4-43 Enhanced Encryption Mechanism License Description

NE Item Unit
ZGO-06-02-005 Enhanced A5/1 BSC Enhanced A5/1 per

(per TRX) TRX


New Support SDCCH This parameter indicates whether an
handover before SDCCH handover is triggered before A5/1
A5/1 ciphering encryption.
New Support modify This parameter indicates whether the

NCell ARFCNS neighbor cell list is modified after the A5/1
after A5/1 encryption algorithm is successfully
ciphering executed.
New Support Sys Info This parameter indicates whether system

6 fill bits random information 6, sent to the MSs who use
after A5/1 A5/1, supports random filling bits instead of
ciphering fixed bits.
C901060116 Number of SDCCH This counter counts the number of

handover attempts due to SDCCH handover attempts due to A51
A51

handover success due to SDCCH handover success due to A51
A51

handover failure due to SDCCH handover failure due to A51
A51
C901060119 Number of TCH/F This counter counts the number of

handover attempts due to TCH/F handover attempts due to A51
A51

handover success due to TCH/F handover success due to A51
A51

handover failure due to TCH/F handover failure due to A51
A51

C901060122 Number of TCH/H This counter counts the number of

handover attempts due to TCH/H handover attempts due to A51
A51

handover success due to TCH/H handover success due to A51
A51

handover failure due to TCH/H handover failure due to A51
A51
Fault Management
No impact.
No impact.
No impact.
Impacted Features
No impact.
4.18 ZGO-01-03-004 Cell Broadcast Service
4.18.1 Description
Cell broadcast SMS is a kind of point to multi-point SMS service to a specified area,
which could be one or multiple cells. The short message content is from the operator or
other information service providers. MSs receive all messages from cell broadcast center
or select the kind of message to be received.

Usually, the function is implemented by the CBE, CBC, BSS and MS.
The CBE is the source of the content of short messages.
The CBC decides the broadcast area, broadcast start time, end time, repeat interval, and
sends this information to the BSS. One CBC connects to multiple CBEs and multiple
BSSs.
The BSS sends the short message to the appointed cells. One BSS connects to only one
CBC. The BSS uses CBCHs to send cell broadcast short messages. Each CBCH
occupies a DCCH on the Um interface.
The ZTE BSS supports both built-in CBC and stand-alone CBC.
To deploy the built-in CB SMS function, only the BSS software needs to upgrade.
Hardware modification is not necessary. The deployment of the built-in CB SMS is shown
as follows.
Figure 4-2 Deployment of Built-in CB SMS
BTS
BSC
CBC
OMCR
BTS MS
BSC
To deploy the CB SMS function with stand-alone CBC, not only the BSS software needs
to upgrade, the CBC and CBE equipment also need to be added. The BSC supports
direct interface with CBC since UR13. The deployment of the CB SMS function with
stand-alone CBC is shown as follows.

Figure 4-3 Deployment of Stand-alone CBC (via OMCR)
BTS
CBEs
BSC
CBC
OMCR
MS
BTS
BSC
Figure 4-4 Deployment of Stand-alone CBC (BSC-CBC direct interface)
OMCR
BTS
CBEs
BSC
CBC
MS
BTS
BSC
The BSC supports direct interface to CBC since UR13.
System Capacity
In GSM, SMS-CB messages are broadcast over an air interface on a special signaling
channel, Cell Broadcast Channel (CBCH). CBCH reuses one of SDCCH sub channel.
There can be only one CBCH in each cell. The table below shows the impact of taking

one SDCCH sub channel as CBCH in a cell. The less the capacity of the cell, the more
impact will take on the traffic that SDCCH can hold, but as the growth of SDCCH capacity,
the impact can be ignored.
Number of CBCH channel 1 1 1 1 1
Total number of SDCCH sub 4 12 16 24 32

channels
Total number of SDCCH sub 3 11 15 23 31

channels taking out of CBCH
channel
SDCCH reduction rate 25% 8.3% 6.3% 4.2% 3.1%
Network Performance
No impact.
4.18.4 Hardware
No impact.
No impact.
License

Table 4-46 Cell Broadcast Service License Description
Configu Sales
red NE Unit
ZGO-01-03-004 Cell Broadcast Cell Broadcast SMS (per

BSC TRX
SMS TRX)
The Cell Broadcast (CBC) service is an

important service provided by a mobile
communication system, which sends
information to the MSs in specified
geographical areas. Different from a
point-to-point short message that sends
Old CBC support information to a specified subscriber, a cell
broadcast short message sends information
to all the subscribers in a specified
geographical area, including the subscribers
roaming to this area.
This parameter indicates whether this cell
supports the CBC service.
Number of This counter counts the number of

C901280041 ABIS_SMS_BROADCAST_REQ ABIS_SMS_BROADCAST_REQ
messages messages sent by BSC.
Number of This counter counts the number of

C901280042 ABIS_SMS_BROADCAST_CMD ABIS_SMS_BROADCAST_CMD
messages messages sent by BSC.
Fault Management

No impact.
No impact.
No impact.
Impacted Features
No impact.
4.19 ZGO-01-03-005 Dual Transfer Mode
4.19.1 Description
The DTM was introduced in 3GPP Rel-4. TCH and PDCH are allocated to the same MS
simultaneously. This opens up the possibility for a wide range of services including
interactive games, sending pictures and web browsing while maintaining an ongoing
speech connection. The function of Class A MS is implemented by software, so the cost
of MS is decreased.
The DTM enables the MS to be connected to the CS domain (used for transferring
speech) as well as to be allocated with radio resources on one or more Packet Data
Channels (PDCHs). The DTM figure is shown as below.

Figure 4-5 Dual-Transfer-Mode
An MS is able to enter the DTM through the establishment of PS connection only when
the dedicated CS mode exists. An MS working in the PS transmission mode must
release the Temporary Block Flow (TBF), and it has to go into the dedicated CS mode
before the TBF is established again, and then enters the DTM.
V10R1 supports DTM multi-slot class 11; maximum 2 PDCHs can be allocated to one
MS.
UR13 supports High Multi-slot class DTM, that is, class 31, class 32, and class 33;
maximum 3 PDCHs can be allocated to one MS.
System Capacity
No impact.
Network Performance
User can have voice and data services concurrently, which improves users satisfaction.
To use DTM service the CS and PS channels need to be adjacent, to satisfy the channel
allocation requirement, some of the users have to handover to other channel. Hence the
handover times can be increased. When the handover fails, call drop may occur, which
cause the rise of the call drop rate.

This feature is implemented on the BTS, BSC, MSC, SGSN and OMC.
4.19.4 Hardware
No impact.
No impact.
License
Table 4-49 Dual Transfer Mode License Description
Configu Sales
red NE Unit
ZGO-01-03-005 Dual Transfer Mode Dual Transfer Mode(per

BSC TRX
TRX)
Table 4-50 Parameters Related to Enhancement of This Feature

Old This parameter indicates whether a cell supports
the Dual Transfer Mode (DTM). This parameter is
broadcast to MSs through the GPRS Cell options
DTM support
in SI13 and PSI13. If the DTM is supported,
category-A MSs are allowed to initialize a packet
request procedure in dedicated mode.


New This parameter indicates a switch that controls
Support DTM high
whether to support the DTM31-33 multi-slot
Multislot
capability.
No impact.
Fault Management
No impact.
ZGO-03-02-002 enhanced CS channel allocation
ZGO-03-02-003 enhanced PS channel allocation
No impact.
Impacted Features
No impact.
4.20 ZGO-02-03-014 Fast Return from GSM to LTE
4.20.1 Description
In the case of LTE network overlaid with GSM network, the UE might prefer to camp on
LTE. When the UE is switched to GSM from LTE, such as triggered by mobility, there are
two location registration procedures after a call is released. One is LAU in GSM after the
UE returns to IDLE. The other is TA update when the UE goes back to LTE. Such
frequent operation increases the signaling load, and also increases the probability of

paging failure. If the redirect to LTE in Channel Release message is provided, LAU in
GSM is eliminated. It accelerates the UEs return to LTE.
For the UE capable of both GSM and LTE, when it ends a voice call in the GSM network,
the BSC sends the message Channel Release to it, and the list of LTE neighbor cells is
included in the indicator Cell selection indicator after release of all TCH and SDCCH;
consequently, the UE is able to choose a suitable LTE cell to camp, instead of returning
to the GSM network first and then reselecting to the LTE network.
In UR12, the operator determines whether a suitable LTE neighbor cell for a terminal to
fast return based on measurement reports. If a terminal reports multiple acceptable LTE
neighbor cells, the BSS selects the cell at the highest level among all the acceptable LTE
neighbor cells and sends the cell information to the terminal. Meanwhile, the BSS sets
cell reselection parameters specified for fast return to LTE, which are independent of cell
reselection parameters from GSM to LTE in IDLE state. This enhanced feature needs to
be supported by GSM/LTE dual-mode terminals.
In UR13, the operator determines whether the fast return is performed from GSM to LTE.
But it only applies to Circuit Switched Fallback (CSFB) calls. If this feature applies to
CSFB only, the BSC triggers fast return from GSM to LTE based on the CSFB indicator
in a Clear Command message sent from the MSC, and enables the terminals with CSFB
calls to fast return from GSM to LTE after the calls end. For non-CSFB calls, fast return
from GSM to LTE is not performed. This enhanced feature needs to be supported by the
core network.
System Capacity
No impact.
Network Performance
When this feature is activated, terminals can perform the fast return to LTE after
completing CS services in GSM, and users experience is improved. The data of
Chongqing verification, delay latency of from GSM RR channel release to LTE TAU
Request is reduced about 150ms.

4.20.4 Hardware
No impact.
License
Table 4-51 Fast Return from GSM to LTE License Description
Configur License Control Sales

ed NE Item Unit
ZGO-02-03--014 Fast Return from Fast Return from

GSM to LTE BSC GSM to LTE (per TRX
TRX)
After completing a call in a GSM network, a

GSM/LTE dual-mode terminal must return to
the LTE network as soon as possible. As
New FastReturn to LTE specified in the 3GPP specification, the "Cell
selection indicator after release of all TCH and
SDCCH" IE in the Channel Release message
can carry LTE neighbor cell information to


guide the terminal to the LTE network. This
parameter determines whether the IE carries
LTE neighbor cell information.
This parameter indicates whether the LTE

neighbor cell is only used for fast return. The
protocol specifies that a system message or
measurement report can contain eight LTE
frequencies, but does not specify the
This neighbour cell is
New maximum number of frequencies in a Channel
Only for FastReturn
Release message used for fast return. Some
operators require a maximum of 16
frequencies used for fast return. This
parameter is used to specify a special LTE
neighbor cell for fast return.
No impact.
Fault Management
No impact.
ZGO-02-03-008 GSM/LTE Cell Reselection.
No impact.
Impacted Features
ZGO-02-03-019 CSFB from LTE to GSM
If the CSFB feature is activated, it is recommended to enable this feature at the same
time.

4.21 ZGO-04-02-006 TFO
4.21.1 Description
Tandem Free Operation (TFO) is used for mobile-to-mobile speech calls. By activating
the TFO, 4 voice frames of uplink and downlink can make up of a 64K multiplex frame
with identity frame after being identified, which is convenient for the terminal identification.
Mobile terminals must use the same speech codec in order to enjoy the TFO feature,
otherwise the TFO cannot be established and the call has to be handled in the non-TFO
mode.
For the ZTE GERAN facility, only software upgrade is required to activate the TFO
function. There is no more modification on the other network elements. By enhancing the
coding efficiency, the speech quality can be improved. According to the 3GPP TS 48.060
and 48.061, the TFO is activated and controlled by the Transcoder Units, and all the
mobile-to-mobile calls can hand over to the TFO mode when the coding rate adaptation
has been completed in the call set-up phase.
In the GSM system, the voice data of a mobile-to-mobile speech call is transcoded from
TRAU frames to PCM frames at one side and then is transcoded from PCM frames to
TRAU frames at the other side. This twice transcoding is called Tandem Operation.
Tandem Operation degrades the quality of voice data.
When this feature is activated, the above mentioned Tandem Operation is avoided if the
two MSs of one same call use the same codec type. Thus the quality of voice data is
improved.
According to the 3GPP TS 48.060 and 48.061, the TFOTandem Free Operation is
negotiated and set up via in-band signaling by transcoders of both sides after the call is
set up. If the two MSs cannot use the same codec type, this call continues using Tandem
Operation.
In UR12, the AMR TFO algorithm is enhanced.

In IP Abis, the system uses redundant bits of speech frames instead of TFO
configuration frames to transmit TFO configuration parameters, which improves the voice
quality.
The system reduces the number of RTD frames in A interface, improving the voice
quality.
In UR13, codec matching after a TFO setup failure can improve the success rate of TFO
call establishment. The TFO setup fails because two MSs in a call are using the
unmatched codec mode; the TRAU interacts the codec mode set supported by the two
MSs to decide whether there is codec mode which can establish the TFO; if any, TRAU
reports the codec mode to BSC, then BSC triggers a handover procedure. After
handover, TRAU will start a new TFO negotiation procedure to set up a TFO call.
The UR13 version supports TFO between 2G/3G. This function requires UTRAN to
support UMTS_AMR2 codec. UMTS_AMR2 2 adopts source coding mode every 40 ms
on the uplink and every 20 ms on the downlink.
System Capacity
No impact
Network Performance
The optimization of this feature imposes the following impacts on network performance:
The TFO established success rate can be improved.
If the TRAU implements the mismatch negotiation, BSC allocates the channel
resource based on priority voice algorithm, so it can impact the assignment of voice
algorithm.
This feature is implemented on the BSC, BTS and OMC.

4.21.4 Hardware
No impact
No impact
License
Table 4-53 TFO License Description

NE Item Unit
ZGO-04-02-006 TFO BSC TFO(per TRX) per TRX

Old TFO Enable This parameter is one of TFO control

parameters, which determines whether to
enable TFO.
Options:
0: No
1: Yes
When TFO is disabled, which means to set
TFOControl_0 to "0", other related functions
are also disabled. This means that
TFOControl_1, TFOControl_2 and
TFOControl_3 are set to 0.
TFO is an in-band protocol. The TCs on
both sides use this protocol to negotiate the
encoding and decoding after a call is set up.
The decoder of the sender and the coder of
the receiver are bypassed, and the voice
frames used over the air interface are
directly sent to the receiver to improve voice
quality.
If the speech version supported by the cell
is not AMR, TFO can be set up if the speech
versions supported by two cells are the
same. If the speech version is AMR, TFO
can be set up if the supported speech codec
types are also the same. Otherwise, TFO
cannot be set up.
If IPA is configured, the speech coding
negotiation is performed on the CN side.
New Mismatch Resolved When the TFO function is enabled, if a TFO

cannot be established due to mismatched
voice versions, this parameter is enabled.
This function is used to search for a
preferential voice version from the voice
algorithms supported by the MS by
changing the MS mode or changing the
current voice version to the preferential one.

Table 4-55 Counters related to this feature
C902420001 Number of first try to This counter is incremented each time

contact distant partner when the TRAU attempts to negotiate
after TFO being TFO for the first time. It reflects the
enabled (Times) capability that the TRAU attempts to
negotiate TFO by sending a TFO
message when TFO is enabled.
Sampling point: This counter is
incremented each time the TRAU sends
the TFO_REQ/ACK message for the first
time.
C902420002 Number of retrying to This counter is incremented each time

contact distant partner when a TFO renegotiation attempt is
after being interrupted initiated due to different reasons after the
first TFO negotiation. It reflects the TFO
renegotiation capability in different
cases, such as loss of TFO interaction
synchronization, and configuration
change after handover. Sampling
point::This counter is incremented each
time the TRAU resends a TFO_REQ(_L)
message.
This counter is incremented each time

when the first TFO negotiation attempt is
successful. It reflects the number of
times that the first attempt for TFO
Number of TFO
negotiation succeeds. Sampling
contacting with distant
C902420003 point::This counter is incremented each
partner after first
time the TRAU receives the TFO_ACK
try(Times)
message or the TFO frame from the
remote party after sending the
TFO_REQ/ACK message for the first
time.


when the TFO renegotiation attempt
initiated by the TRAU is successful. It
Number of TFO
reflects the number of successful
recontacting with
attempts for TFO renegotiation.
C902420004 distant partner after
Sampling point: This counter is
TFO being
incremented each time the TRAU
interrupted(Times)
receives a TFO_ACK(_L) message from
the remote party after resending the
TFO_REQ(_L) message.

when a TFO is established after the first
attempt for TFO
negotiation succeeds. It reflects the
Number of TFO
result of TFO establishment after the first
C902420005 establishment after first
attempt for
try(Times)
TFO negotiation succeeds. Sampling
point: This counter is incremented each
time the TFO is established after the
TRAU receives and uses the TFO frame.

when TFO is reestablished after
successful TFO renegotiation attempt. It
Number of TFO
reflects the result of TFO
reestablishment after
C902420006 reestablishment after successful attempt
being
for TFO renegotiation. Sampling point:
interrupted(Times)
the TFO is established after the TRAU
receives and uses the TFO frame.


when TFO is interrupted due to the loss
of synchronization at A interface. It
reflects the loss of synchronization at A
interface after TFO interaction, and TFO
establishment failure or TFO interruption
Number of
caused by the loss of TFO
synchronization lost at
C902420007 synchronization. Sampling point: This
A-interface resulting in
counter is incremented each time the
TFO off(Times)
TFO establishment fails because the
TFO message responded by the remote
party is interrupted or the local party
does not receive the TFO frame from the
remote party during the process of TFO
negotiation and establishment.

when TFO establishment fails due to the
Number of codec type
mismatch of encoding/decoding
C902420008 mismatch resulting in
algorithm. It reflects the influence of
TFO off(Times)
algorithm mismatch on TFO
establishment.

when the rate control fails during TFO
establishment when the MS uses the
Number of rate control
Adaptive Multi-Rate (AMR) algorithm. It
failure resulting in TFO
C902420009 reflects the situation that TFO cannot be
off when using AMR
successfully established because the
codec type(Times)
adjusted rate does not meet the TFO
establishment condition when the AMR
algorithm is used.
Number of mode This counter counts the number of mode

changes for changes for establishing TFO. This
C902420010
establishing counter is not used in this version.
TFO(Times)
Number of mode This counter counts the number of mode

C902420011 changes for optimizing changes for optimizing TFO.
TFO(Times) This counter is not used in this version.

Number of active This counter counts the number of active

collection changes for collection changes for establishing TFO.
C902420012
establishing This counter is not used in this version
TFO(Times)
Number of active This counter counts the number of active

C902420013 collection changes for collection changes for optimizing TFO.
optimizing TFO(Times) This counter is not used in this version.
Number of TFO
This counter counts the number of TFO
reestablished for
C902420014 reestablished for mismatch resolved
mismatch
(Times)
resolved(Times)
number of TFO Off for

C902420015 channel
Off for channel mismatch (Times)
mismatch(Times)
number of TFO Off for

C902420016 AMR ACS
Off for AMR ACS incompatible (Times)
incompatible(Times)
number of mode modify This counter counts the number of mode

C902420017 attempts for TFO modify attempts for TFO mismatch
mismatch(Times) (Times)
number of mode modify This counter counts the number of mode

C902420018 success for TFO modify success for TFO mismatch
number of mode modify

This counter counts the number of mode
C902420019 failure for TFO
modify failure for TFO mismatch (Times)
mismatch(Times)
number of handover This counter counts the number of

C902420020 attempts when TFO handover attempts when TFO mismatch
number of handover
mismatch resolved
C902420021 handover mismatch resolved when TFO
when TFO
mismatch (Times)
mismatch(Times)
number of handover
mismatch unresolved
C902420022 handover mismatch unresolved when
when TFO
TFO mismatch (Times)
mismatch(Times)

Fault Management
No impact.
E1A
ZGO-05-05-001 BSC Local Switch
ZGO-04-02-010 Automatic Loudness Control (ALC)
ZGO-04-02-011 Automatic Noise Restrain (ANR)
ZGO-04-02-012 Acoustic Echo Control (AEC)
Impacted Features
No impact
4.22 ZGO-04-03-007 Intelligent Frequency Timeslot

Allocation (IFTA)
4.22.1 Description
Reducing interference in radio network improves service quality, network performance

and network capacity. It is one of the major tasks of BSS implementation to minimize the
network interference.
In legacy network planning, frequencies are allocated to TRXs and timeslots statically, or
by means of predefined frequency hopping parameters (MA, MAIO, and HSN).
Meanwhile during channel assignment procedure the BSC only takes into account the
uplink interference band information of the idle timeslots, not considering the downlink

interference level. These legacy methods do not make full use of all the information that
the BSS can obtain to reduce interference.
Intelligent Frequency Timeslot Allocation is a new feature that uses real-time timeslot
occupation states, statistical interference levels, MS measurement reports, power control
information together with rate and codec type information to select a channel for voice
call in order to cause as less interference as possible. The selected channel is defined by
MA, MAIO, TS and TSC.
Before channel assignment, Intelligent Frequency Timeslot Allocation calculates the C/Is
for the new service and existing services for all candidate timeslots. If the C/Is are lower
than certain thresholds (configurable), then that candidate timeslot will not be chosen.
The C/I thresholds for different rates and codecs are configurable; the following table
shows an example.
Table 4-56 C/I Thresholds
Rate and Codec Target C/I Lowest C/I
FR/EFR 15dB 10dB
HR 18dB 12dB
AMR FR 9dB 4dB
AMR HR 15dB 10dB
Intelligent Frequency Timeslot Allocation can be used together with other interference
reducing features, for example SAIC (Single Antenna Interference Cancellation). BSS
can allocate channels with relatively lower C/I to SAIC terminals and allocate channels
with relatively higher C/I to legacy terminals, so as to improve overall network
performance.
In order to apply Intelligent Frequency Timeslot Allocation in multiple BSSs coverage

area, timeslot occupation states, MS measurement reports and power control
information are transferred between neighboring BSCs via BSC-BSC interface beard on
IP.
UR13 ZXUR9000 supports this feature.

System Capacity
No impact.
Network Performance
The IFTA application enhances network capacity under certain frequency resources.
The CPU loading increases due to the large amount of computation when allocating
channels.
The IFTA depends on GPS clock for synchronization. The GPS clock-related alarms
should be concerned in daily maintenance.
4.22.4 Hardware
No impact.
License
Table 4-57 Intelligent Frequency Timeslot Allocation License Description
Configur Sales
ed NE Unit

ZGO-04-03-007 Intelligent
Intelligent Frequency
Frequency
BSC Timeslot Allocation (per TRX
Timeslot
TRX)
Allocation

Type
New This parameter is a BSC-level switch that

controls whether IFTA is supported.
Support IFTA Intelligent Frequency Timeslot Allocation
(IFTA) is a C/I-based dynamic channel
allocation technology.
New This parameter indicates whether to initiate
Perform IFTA channel a check procedure to another RRM module
check (CMP or BSC) after an IFTA channel is
allocated.
New After attempting to allocate an IFTA
channel, the RRM module may receive a
failure response after sending a check
Retry allocation Times
request to another RRM module (CMP or
after IFTA channel check
BSC), which means that the IFTA allocation
fail
fails. This parameter specifies the number
of times that the BSC attempts to reallocate
IFTA channels.
New This parameter indicates an uplink
threshold for sending interference data. If
Uplink Threshold of send the uplink CIR variation exceeds the value
interference information of this parameter, the RRM module sends
the interference data to other RRM modules
immediately.
New This parameter indicates a downlink
threshold for sending interference data. If
Downlink Threshold of
the downlink CIR variation exceeds the
send interference
value of this parameter, the RRM module
information
sends the interference data to other RRM
modules immediately.


Type
New When the IFTA function is enabled, the

measurement report for interference data
Period for IFTA must be regularly updated. The update
measurement report period is an integral multiple of the
process measurement report period. This parameter
indicates the period for updating the
interference data.
New When the IFTA function is enabled, the
measurement report must be sent to other
RRM modules including the CMP inside the
Period for IFTA transfer
BSC and other BSCs. The sending period is
measurement
an integral multiple of the measurement
information to other RRM
report period. This parameter indicates the
period for sending the measurement report
to other RRM modules.
New This parameter specifies the duration for
the RRM module to wait for an IFTA check
IFTA channel check timer response sent from other RRM modules
after allocating an IFTA channel and
initiating a check.
New This parameter indicates the confidence
probability when the historical
measurement records are updated, that is,
History measurement
a probability that the actual level in the
record confidence
interference neighbor cell is lower than the
probability
estimated value. If the actual level is lower
than the estimated value, the allocated
channels are in good quality.
New This parameter indicates the period for
updating the historical measurement
records. When the period expires, the level
History measurement
in the interference cell is re-estimated. The
record Update period
new estimated level value is used in
subsequent measurement in case that no
interference cell is detected.
New This parameter indicates the update factor
History measurement of historical measurement records, that is,
record Update factor the proportion of new estimated value in
calculating the historical interference.


Type
New This parameter indicates the protective

period for historical measurement records,
History measurement
that is, the period to keep historical
record Guard Period
interference data even if the interference
cell has no measurement data.
New If this parameter is set to 1 (Yes), it means
Report IFTA channel info the IFTA channel information is tracked and
output through the Abis signaling.
New If this parameter is set to 1 (Yes), it means
Report IFTA info of
the IFTA channel information is tracked and
IMSI
output through the IMSI signaling.
New This parameter specifies the time delay of
GPS state change. When the GPS clock
state is changed from the synchronization
to loss state, or from the loss to
GPS State Delay synchronization state, only if the new state
keeps for a certain time longer than this
parameter, the state change is confirmed,
avoiding the negative effects due to state
misjudgment and repeated handovers.
New This parameter indicates the uplink noise
value in IFTA channel allocations. It is set to
UpLink Noise Level ensure that the uplink signal level of an
allocated IFTA channel is a certain value
higher than the noise level.
New This parameter indicates the downlink noise
value in IFTA channel allocations. It is set to
DownLink Noise Level ensure that the downlink signal level of an
allocated IFTA channel is a certain value
higher than the noise level.


Type
New When the IFTA function is enabled, the BSC

needs to receive a measurement report with
neighbor cell measurement data to estimate
interference before allocating TCH
channels. However, in some cases, if the
BSC does not receive a measurement
IFTA Wait Measurement
report with neighbor cell measurement data
Report Timer
after receiving an assignment command
from the MSC, it needs to wait for a certain
time to receive the measurement report.
The BSC can be set to wait for several
times. This parameter specifies how long
the BSC waits in each time.
New When the IFTA function is enabled, the BSC
needs to receive a measurement report with
neighbor cell measurement data to estimate
interferences before allocating TCH
channels. However in some cases, if the
BSC does not receive the measurement
IFTA Wait Measurement
report with neighbor cell measurement data
Report Retries
after receiving an assignment command
from the MSC, it needs to wait for a certain
time to receive the measurement report.
The BSC can be set to wait for several
times. This parameter specifies number of
times that the BSC waits for.
New During an IFTA allocation procedure, the
system estimates the uplink co-channel
interference and adjacent frequency
interference. The adjacent frequency
Uplink Neighbour
interference has minor effect therefore
Frequence Reduce
attenuation is used during calculation. This
parameter indicates the attenuation in
calculating the uplink adjacent frequency
interference.


Type
New During an IFTA allocation procedure, the

system estimates the downlink co-channel
interference and adjacent frequency
interference. The adjacent frequency
Downlink Neighbour
interference has minor effects therefore
Frequence Reduce
attenuation is used during calculation. This
parameter indicates the attenuation in
calculating the downlink adjacent frequency
interference.
New This parameter indicates two methods for
handling other subscribers during IFTA
channel allocations. Method 1: all the
Method for deal other subscribers' CIR must be higher than the
user when IFTA allocate CIR threshold, but it may easily lead to an
Channel allocation failure. Method 2: some
subscriber CIRs are allowed to be lower
than the CIR threshold, to make the
allocations easier to be successful.
New This parameter indicates the permitted
Permitted Uplink CIR uplink CIR reduction of other subscribers
Reduce of other user during IFTA channel allocations. This
parameter works when OtherUserCtrl is set
to Method 2.
New This parameter indicates the permitted
downlink CIR reduction of other subscribers
Permitted downlink Cir
during IFTA channel allocations. This
Reduce of other user
parameter works when OtherUserCtrl is set
to Method 2.
New This parameter indicates the uplink
Interference difference of interference difference between the same
Uplink Same TSC and TSC and different TSC during IFTA channel
different TSC allocations. If the TSCs are the same, the
interference has bigger effect.
Downlink Same TSC and TSC and different TSC when the MS
different TSC for SAIC supports SAIC during IFTA channel
MS allocations. If the TSCs are the same, the


Type

Downlink Same TSC and TSC and different TSC when the MS does
different TSC for NON not support SAIC during IFTA channel
SAIC MS allocations. If the TSCs are the same, the
New This parameter indicates the historical
record threshold for interference statistics.
History Record
When the number of samples in the last
Threshold
period is lower than this threshold, the
historical interference record is not updated.
New This parameter indicates a switch that
controls whether to use the last
Use Last Measurement
measurement values if the measurement
Report
values of the interference neighbor cells are
not reported.


Type
New This parameter indicates the uplink CIR

difference of a Half Rate (HR) channel.
When the HR channels are allocated,
sub-timeslot 1 of the even-number slot and
sub-timeslot 0 of the odd-number slot are
allocated first.
Channels that meet the lowest CIR are
selected through calculation and then
allocated. There are two rules for allocating
the channels that meet the target CIR. Rule
1: the channel with the highest CIR is
allocated first. For sub-timeslot 1 of the
even-number slot and sub-timeslot 0 of the
odd-number slot, the UL CIR is increased
by R_BSCIFTA.UlHrCirDiff1, and the DL
CIR is increased by
R_BSCIFTA.DlHrCirDiff1. Channels are
queued based on the increased or
Uplink Cir difference1 of
decreased CIR and then allocated
HR
preferentially. Rule 2: The channel with the
lowest CIR is allocated first. For
sub-timeslot 0 of the odd-number slot, the
UL CIR is decreased by
R_BSCIFTA.UlHrCirDiff1, and the DL CIR is
decreased by R_BSCIFTA.DlHrCirDiff1.
Channels are queued based on the
increased or decreased CIR and then
allocated preferentially.
During allocation of the channels that meet
the lowest CIR but fail to meet the target
CIR, for sub-timeslot 1 of the even-number
slot and sub-timeslot 0 of the odd-number
slot, the UL CIR is increased by
increased by R_BSCIFTA.DlHrCirDiff2,
aiming to allocate these channels first.


Type

allocated first.
CIR is increased by
Downlink Cir difference1
of HR


Type

allocated first.
CIR is increased by
Uplink Cir difference2 of
HR


Type

allocated first.
CIR is increased by
Downlink Cir difference2
of HR


Type
New This parameter indicates the low level in a

neighbor cell for calculating historical
interference. If a neighbor cell does not
Use Low Level of
report the measurement value, this
neighbour cell
parameter controls whether to fill in a
relatively low level for historical interference
evaluation.
New This parameter indicates the threshold for
Threshold for IFTA
ignoring interference when IFTA channels
ignore interference
are allocated.
IFTA channel adopt controls whether to use uplink initial power
uplink power optimize optimization when IFTA channels are
allocated.
IFTA channel adopt controls whether to use downlink initial
downlink power optimize power optimization when IFTA channels are
allocated.
New CIR allowance for IFTA
channel uplink power This parameter indicates the CIR margin
optimize reserved for IFTA uplink power optimization.
New CIR allowance for IFTA This parameter indicates the CIR margin
channel downlink power reserved for IFTA downlink power
optimize optimization.
New This parameter indicates whether to
Method for IFTA channel
optimize the uplink IFTA channel power
uplink power optimize
based on ordinary power optimization.
Method for IFTA channel
optimize the IFTA channel downlink power
downlink power optimize
based on the ordinary power optimization.
New This parameter indicates the TSCs used by
TscS Used by IFTA
IFTA in this cell.
New This parameter indicates the number of
Time of use last times for using the last measurement value
Measurement report when the interference cell does not report
any measurement value.


Type
New This parameter indicates the searching

IFTA Channel Search order of IFTA channels. Different searching
Order orders are selected for the different cells to
reduce the conflicts.
New This parameter indicates the window for
calculating the average interference cell
Interf Cell Average level. If this parameter is not 1, it means the
Window neighbor cell interferences are calculated
by using the average value of multiple
measurements.
New This parameter indicates IFTA channel
preference, that is, find a channel that
IFTA Channel Priority meets the target CIR, or a channel with the
highest or lowest CIR from channels that
meets the target CIR.
New This parameter indicates the IFTAMa DN
DN of IftaMa for this cell
for this cell.
preferentially allocate IFTA channels or
Prefer IFTA channel
non-IFTA channels when a cell allocates
TCH channels.
New This parameter indicates the target uplink
CIR.
Uplink Target CIR The element 0 to 6 corresponds to FR,
EFR, HR, AMRFR, AMR HR, and DATA
respectively.
New This parameter indicates the minimum
uplink CIR.
Uplink Minimum CIR The element 0 to 6 corresponds to FR,
EFR, HR, AMRFR, AMR HR, and DATA
respectively.
New This parameter indicates the target
downlink CIR.
BYTE[0] to BYTE[11] indicates six encoding
Downlink Target CIR modes: FR, EFR, HR, AMR FR, AMRHR,
and DATA, each of which includes two
cases: supporting SAIC and not supporting
SAIC.


Type
New This parameter indicates the minimum

downlink CIR.
BYTE[0] to BYTE[11] indicates six encoding
Downlink Minimum CIR modes: FR, EFR, HR, AMR FR, AMRHR,
and DATA, each of which includes two
cases: supporting SAIC and not supporting
SAIC.
controls whether to start IFTA allocation in a
Use IFTA cell. If the value is set to 1, the cell starts to
allocate IFTA channels; otherwise, no IFTA
channels are allocated.
Exchange IFTA
perform IFTA information interaction with
information with this
the interference cell and calculate the
interfere cell
interferences.
New This parameter indicates the default value
of the downlink signal level of the
Default Rx level of this
interference cell measured by this cell. It
interfere cell
can be used when no historical
measurement data is obtained.
New This parameter indicates the default value
of downlink signal level of this cell
Default Rx level from this
measured by the interference cell. It can be
interfere cell
used when no historical measurement data
is obtained.
New If an interference message does not report
any measurement value, a low level is filled
Low Level of Neighbour
in the message for calculating the historical
Cell
interference. This parameter indicates the
value of this level.
New Frequency Band of This parameter specifies the frequency
IftaMa band that IFTAMA frequencies belong to.
Frequency hopping IFTAMa use no frequency hopping or cyclic
hopping.


Type
New This parameter indicates a frequency list

that consists of a set of frequencies in a
Frequency List
same frequency band, which are used for
IFTA.
New The BTS calculates a frame number from
the GPS time during GPS synchronization.
The frame number is used for
Gps Frame Offset synchronization in various cells, so it must
have an offset due to time delay. This
parameter indicates an offset of the GPS
frame number.
New This parameter indicates whether this TRX
is an IFTA TRX. When the IFTA function is
enabled, some TRXs of a cell are
IFTA TRX
configured as IFTA TRXs where the
intelligent frequency timeslot allocations are
implemented.
New This parameter indicates whether to use
IFTA TRXs when IFTA is offline.
Use When IFTA Not With the limited frequency resource, the
Online network capacity decreases if IFTA is not
used, therefore, some TRXs can be
disabled when IFTA is offline.
Number of seizure voice This counter counts the number of

C901260160 TCH/F IFTA channel seizure voice TCH/F IFTA channel
success for assignment success for assignment
Number of seizure data This counter counts the number of

C901260161 TCH/F IFTA channel seizure data TCH/F IFTA channel
success for handover success for handover

success for handover success for handover


TCH/F IFTA channel seizure data TCH/F IFTA channel
C901260163
failure due to uplink failure due to uplink softblock for
softblock for assignment assignment

TCH/F IFTA channel seizure voice TCH/F IFTA channel
C901260164

C901260165
softblock for handover handover

C901260166

C901260167
failure due to downlink failure due to downlink softblock for

C901260168

C901260169

C901260170
Number of TCH/F IFTA

channel check failure for
C901260171 TCH/F IFTA channel check failure for
assignment(speech
assignment(speech version1)
version1)


handover(speech
handover(speech version1)
version1)

assignment(speech
version2)

handover(speech
version2)

assignment(speech
version3)

handover(speech
version3)
Number of TCH/F IFTA This counter counts the number of

C901260177 channel check failure for TCH/F IFTA channel check failure for
assignment(data) assignment(data)

C901260178 channel check failure for TCH/F IFTA channel check failure for
handover(data) handover(data)

C901260179
channel check timeout TCH/F IFTA channel check timeout

C901260180 channel first check TCH/F IFTA channel first check
success success

C901260181 channel second check TCH/F IFTA channel second check
success success

C901260182 channel third check TCH/F IFTA channel third check
success success


C901260183 channel same frequency TCH/F IFTA channel same frequency
allocate same TSC allocate same TSC

success for assignment success for assignment
Fault Management
No impact.
ZGO-05-03-005 Network Wide Synchronization on GPS
ZGO-04-03-001 Synthesized Frequency Hopping
ZGO-03-02-004 HR Concentration
ZGO-04-01-001 Extended Cell Coverage
ZGO-04-01-007 Dynamic Power Sharing
ZGO-04-02-005 Co-BCCH
ZGO-04-03-004 Baseband Hopping
Impacted Features
No impact.

4.23 ZGO-05-04-002 Gb over IP
4.23.1 Description
This feature changes the BSC in Gb interface from TDM/FR based bearing into the IP
based bearing, which means from the original BSSGP/NSVC/FR/TDM into
BSSGP/NSVC/UDP/IP. In this case, the original meaning of NSVC changes to the
concept of IP address and port.
NSVC, a channel for user data between the BSC/PCU and the SGSN, becomes the
IP/Port pair. In Gb over IP, an NS-VC is composed of IP endpoint addresses (UDP/IP
addresses), that is, one IP endpoint address on the BSS and another IP endpoint
address on the SGSN.
Gb over IP is more suitable for bearing burst data services. Furthermore, Gb over IP
helps GSM evolve to All IP architecture.
For Gb over IP, only Gb over IP over Ethernet is supported.
In UR13, MTU is enhanced to 1730 bytes.
System Capacity
The performance of interface board may degrade.
Network Performance
The efficiency of the transmission network is improved.

4.23.4 Hardware
No impact.
License
Table 4-60 Gb over IP License Description

NE Item Unit
ZGO-05-04-002 Gb over IP BSC Gb over IP (per per

64kbps) 64kbps
Table 4-61 Parameters Related to the Enhancement of This Feature
Change MO Class Name Parameter Name Description

Type
Ethernet IP Mtu for interface Maxim MTU size

Old
Interface
Super Vlan IP Mtu for interface Maxim MTU size

Old
Interface
Ethernet Channel Mtu for interface Maxim MTU size

Old
IP Interface
Ethernet IP Sub Mtu for interface Maxim MTU size

Old
Interface
Ethernet Channel Mtu for interface Maxim MTU size

Old
IP Sub Interface

No impact.
Fault Management
No impact.
No impact.
No impact.
Impacted Features
No impact.
4.24 ZGO-05-04-005 IP SLA Monitoring
4.24.1 Description
The BSC implements IP SLA monitoring by sending testing ICMP or UDP packets of
user-defined length to test objects (such as base station), collects response packets and
calculates to get the transmission delay, jitter, packet loss, and reports the result to the
OMM regularly.
The BSC supports the manual launch of SLA and periodical SLA testing. For manually
launched SLA test, test results are immediately presented to the user. For periodic tests,
SLA test results are periodically reported to the OMM by the BSC.
For periodic SLA test, different interfaces use different ways. For the A/Gb interface, the
test task continuously sends test packets and regularly feeds back the measurement
results to the OMM. For Abis interface, a smarter way is used. The BSC starts SLA test

task when the BTS is powered on and establishes Abis link with the BSC; and stops SLA
test when Abis link is broken thus adding no unnecessary network traffic.
In UR13, IP SLA supports that one test target can be tested by at most 4 QoS classes
simultaneously via manual launched instant test.
System Capacity
No impact.
Network Performance
No impact.
4.24.4 Hardware
No impact.
License
Table 4-62 IP SLA Monitoring License Description

NE Item Unit

ZGO-05-04-005 IP SLA Monitoring BSC IP SLA Monitoring per TRX

(per TRX)
No impact.
No impact.
Fault Management
No impact.
No impact.
No impact.
Impacted Features
No impact.
4.25 ZGO-05-04-013 IP Traffic Shaping
4.25.1 Description
For the IP BSC, there is data transmission from Abis to A and Gb, and data transmission
from A and Gb to Abis; besides, there may be synchronously transmitted data, signaling
and O&M information, which requires being treated distinctively. When IP packets are too
overabundant to be transmitted, the BSC is required to control by means of definite
congestion control algorithm. This function provides IP traffic shaping based on the

priority queue mechanism.
This feature provides IP traffic shaping to different service of IP ports in transmission,

which is mainly based on the priority queue forwarding mechanism, and deploys
impartial Weighted Round Robin (WRR) scheduling to provide different control to
different services.
Since UR13, ZXUR9000 BSC supports IP traffic shaping.
System Capacity
No impact.
Network Performance
No impact.
4.25.4 Hardware
No impact.
License

Table 4-63 IP Traffic Shaping License Description

NE Item Unit
ZGO-05-04-013 IP Traffic Shaping BSC IP Traffic Shaping per TRX

(per TRX)
No impact.
No impact.
Fault Management
No impact.
No impact.
No impact.
Impacted Features
No impact.
4.26 ZGO-05-04-025 IPv6
4.26.1 Description
IPv6 is the acronym for Internet Protocol Version 6. IPv6, designed by Internet
Engineering Task Force (IETF), is a next-generation IP protocol used to replace the

current version of IP protocol (IPv4).
The biggest problem of IPv4 is the limited network addresses; in theory, the IPv4
addressing scheme provides the capability of addressing 16 million networks and four
billion hosts. Using class A/B/C, three types of addressing modes, the number of
available network and host addresses are greatly reduced, and the IP addresses are
almost exhausted now. IPv6 has an address capacity of 2 ^ 128, approximately 8 10 ^
28 times bigger than that of the IPv4. This not only solves the network address problem,
but also removes the restriction on the quantity of equipment connected to the Internet.
With the evolution of ALL IP network and the IPv6 technology, the IP RAN also needs to
support IPv6-based network, so as to comprehensively evolve to IPv6. The IP RAN
supports the IPv6-based applications and IPv6-based RAN networking.
The IP RAN supports the IPv6-based applications, that is, terminals can use the IPv6
address to access the Internet for IPv6 services. The IP RAN supports the IPv6-based
networking, that is, base stations and BSC support networking based on the IPv6
technology; in addition, the IPv6-based Abis/A/Gb interfaces are provided to support
sending, receiving, and routing of IPv6 packets, as well as the following features.
ICMPv6
ND
IPv6 static routing
SCTP over IPv6
UDP over IPv6
In UR13, IPv6 function is enhanced based on UR12 in the following aspects,
IEEE1588 over IPv6

IP SLA over IPv6
BFD over IPv6
These enhancements are only for ZXUR 9000.
System Capacity
No impact.

Network Performance
IPv6 has more IP head bytes than IPv4, using IPv6 transmission efficiency is slightly
lower than using IPV4.
4.26.4 Hardware
Need SDR series base stations and ZXUR9000 BSC.
All NE support IPV6.
License
Table 4-64 IPv6 License Description

NE Item Unit
ZGO-05-04-025 IPv6 BSC IPv6 (per TRX) per TRX
Chan MO Class Name Parameter Name Description

ge
Type
Dynamic The Local IP address 1 of the
New Local Ip1
Association Association.


ge
Type

New Local Ip2

New Local Ip3

New Local Ip4
This parameter indicates the

Bearing Protocol bearing protocol used by the IP
IP Channel
New Of Adjacent channel detection task to send
Detection Task
NetElement detecting packets, for example,
UDP or ICMP.
This parameter indicates the local

IP address 1 of the SCTP
New Association Local Ip1 association.
The eight IP addresses must be
unique unless the addresses are 0.

New Association Local Ip2 IP address 2 of the SCTP
association.

association.

association.
This parameter indicates the remote

New Association Remote Ip1 IP address 1 of the SCTP
association.

association.

association.


ge
Type

association.
Ethernet IP Address IP1 on the port. Default

New IP Address 1
Interface (IPv6) value 0 represents not configured.
Subnet Mask Mask of address IP1 on the port.

Ethernet IP
New Default value 0 represents not
Interface (IPv6)
Length 1 configured.

New IP Address 2

Ethernet IP
Interface (IPv6)

New IP Address 3

Ethernet IP
Interface (IPv6)

New IP Address 4

Ethernet IP
Interface (IPv6)
Maximum Transmission Unit (MTU)

refers to the maximum size of
MTU for packets that can pass on a layer of
Ethernet IP
New a communications protocol (units:
Interface (IPv6)
interface bytes). When the default value is 0,
if MTU needs to be configured, brs
is automatically set to 1500.


ge
Type
This parameter specifies the local

address of a link. The linklocal
address is used for local link
communication, for example,
automatic address configuration,
neighbor discovery, or addressing
of the single link that does not have
any routers. It replaces the private
address in IPv4 addressing. IPv6
Local Address of
Ethernet IP does not affect the protocols and
New
Interface (IPv6) architectures of other layers than
Link
the network layer. A router cannot
forward any packet carrying
linklocal source address or
destination address to other links.
FE80 + EUI-64 represents the local
address of a link. For a linklocal
address, the highest byte must be
0xFE and the second highest byte
must be 0x80.

counter for IPv6 ND Duplicated
Address Detection (DAD). DAD is
used to detect whether a newly
added address already exists in the
Ethernet IP local link. The counter is decreased
New ND DAD counts
Interface (IPv6) by 1 each time when a DAD request
is initiated. If the counter is
decreased to 0 and no DAD
response packet is received, this
address is treated as a valid
address.


ge
Type
This parameter indicates whether to

enable the Neighbor Discovery (ND)
Switch of ND
Ethernet IP entry detection function. If this
New
Interface (IPv6) parameter is set to 1, neighbor
entry detection
unreachability detection is
performed to an ND entry.

number of times that ND
unreachability detection fails. It
Times of ND indicates the threshold of
determining whether an entry is
Ethernet IP
New entry detection unreachable. When the number of
Interface (IPv6)
times that ND unreachability
timeout detection fails is equal to or greater
than the value set here, an alarm is
raised to notify the user that the ND
entry is unreachable.
This parameter specifies the period

ND entry
of sending ND entry unreachability
Ethernet IP packets. It indicates that each time
New detection
Interface (IPv6) when the period set here expires,
an ND entry unreachability packet is
timeout
sent.

managed address configuration
flag. This parameter is used for
automatic configuration of the host
Flag of managed address. After a host receives a
Ethernet IP
New router advertisement packet, it
Interface (IPv6)
address determines the status of automatic
address configuration according to
the managed address configuration
flag, the other stateful configuration
flag and the prefix of the router.


ge
Type
This parameter indicates the other

stateful configuration flag. It is used
for automatic configuration of the
host address. After a host receives
Flag of other
Ethernet IP a router advertisement packet, it
New
Interface (IPv6) determines the status of automatic
status

of sending router advertisement
Interval of
packets. A router periodically sends
router advertisement packets and
Sending
Ethernet IP responds to the router request
New
Interface (IPv6) packets that it receives. A router
non-Router
advertisement packet contains the
information required by a host. This
Asking
information is used to determine the
prefix and MTU of a link.

"Router
lifespan of a router. It corresponds
Ethernet IP to the Router Lifetime field in a
New Lifetime" in
Interface (IPv6) router advertisement packet. This
parameter indicates the lifespan of a
Router Asking
router acting as a default router.

reachable time. It corresponds to
the Reachable Time field in a router
"Reachable
advertisement packet. The
Ethernet IP reachable time indicates the
New Time" in Router
Interface (IPv6) duration during which a node
considers a neighbor as reachable
Asking
after it receives an
acknowledgement of neighbor
reachability.


ge
Type

retransmission timer. It corresponds
"Retransmit to the Retransmit Time field in a
Ethernet IP router advertisement packet. This
New
Interface (IPv6) time" in Router parameter indicates the time
interval for re-sending a request
Asking
packet by a neighbor (unit:
milliseconds).

enable the function of sending
ICMPV6 ICMPV6 unreachability error
packets.
Ethernet IP
New unreacheable Options include:
Interface (IPv6)
0: This function is disabled.
flag 1: This function is enabled. ICMPV6
unreachability error packets can be
sent.

ICMPV6 redirection error packets.
ICMPV6 redirect
Ethernet IP Options include:
New
Interface (IPv6) 0: This function is disabled.
flag
1: This function is enabled. ICMPV6
redirection error packets can be
sent.
Super Vlan IP Address IP1 on the port. Default

New IP Address 1

Super Vlan IP
Interface (IPv6)

New IP Address 2


ge
Type

Super Vlan IP
Interface (IPv6)

New IP Address 3

Super Vlan IP
Interface (IPv6)

New IP Address 4

Super Vlan IP
Interface (IPv6)

Super Vlan IP
Interface (IPv6)


ge
Type

Local Address of
Super Vlan IP does not affect the protocols and
New
Link
must be 0x80.

Flag of managed address. After a host receives a
Super Vlan IP
Interface (IPv6)
address determines the status of automatic


ge
Type

Flag of other address. After a host receives a
Super Vlan IP
Interface (IPv6)
status determines the status of automatic

Interval of
Sending
Super Vlan IP responds to the router request
New
non-Router
Asking

"Router
Super Vlan IP to the Router Lifetime field in a
New Lifetime" in
Router Asking

"Reachable
Super Vlan IP reachable time indicates the
New Time" in Router
Asking
reachability.


ge
Type

Super Vlan IP router advertisement packet. This
New
Interface (IPv6) time" in Router parameter indicates the time
Asking
milliseconds).

packets.
Super Vlan IP
New unreacheable Options include:
Interface (IPv6)
sent.
I This parameter indicates whether

to enable the function of sending
ICMPV6 redirect
Super Vlan IP Options include:
New
Interface (IPv6) 0: This function is disabled.
flag
sent.
Ethernet Channel
Address IP1 on the port. Default
New IP Interface IP Address 1
value 0 represents not configured.
(IPv6)
Ethernet Channel Subnet Mask Mask of address IP1 on the port.

New IP Interface Default value 0 represents not
(IPv6) Length 1 configured.
Ethernet Channel
(IPv6)


ge
Type

Ethernet Channel
(IPv6)

Ethernet Channel
(IPv6)


Ethernet Channel MTU for packets that can pass on a layer of
New IP Interface a communications protocol (units:
(IPv6) interface bytes). When the default value is 0,


ge
Type

Ethernet Channel Local Address of
does not affect the protocols and
New IP Interface
architectures of other layers than
(IPv6) Link
must be 0x80.

Ethernet Channel Flag of managed address. After a host receives a
New IP Interface router advertisement packet, it
(IPv6) address determines the status of automatic


ge
Type

Ethernet Channel Flag of other address. After a host receives a
New IP Interface router advertisement packet, it
(IPv6) status determines the status of automatic

Interval of
Ethernet Channel Sending
responds to the router request
New IP Interface
packets that it receives. A router
(IPv6) non-Router
Asking

"Router
Ethernet Channel
to the Router Lifetime field in a
New IP Interface Lifetime" in
router advertisement packet. This
(IPv6)
Router Asking

"Reachable
Ethernet Channel
reachable time indicates the
New IP Interface Time" in Router
duration during which a node
(IPv6)
Asking
reachability.


ge
Type

Ethernet Channel
New IP Interface
time" in Router parameter indicates the time
(IPv6)
Asking
milliseconds).

Ethernet Channel packets.
New IP Interface unreacheable Options include:
(IPv6) 0: This function is disabled.
sent.

Ethernet Channel ICMPV6 redirect
Options include:
New IP Interface
(IPv6) flag
sent.
Ethernet Sub Address IP1 on the port. Default

New IP Address 1

Ethernet Sub
Interface (IPv6)

New IP Address 2


ge
Type

Ethernet Sub
Interface (IPv6)

New IP Address 3

Ethernet Sub
Interface (IPv6)

New IP Address 4

Ethernet Sub
Interface (IPv6)

Ethernet Sub
Interface (IPv6)


ge
Type

Local Address of
Ethernet Sub does not affect the protocols and
New
Link
must be 0x80.

address. After a host receives a
Ethernet Sub
New ND DAD counts router advertisement packet, it
Interface (IPv6)
determines the status of automatic


ge
Type

Switch of ND address. After a host receives a
Ethernet Sub
Interface (IPv6)
entry detection determines the status of automatic

Times of ND
Ethernet Sub responds to the router request
New entry detection
timeout

ND entry
Ethernet Sub to the Router Lifetime field in a
New detection
timeout

Interval of
Sending
Ethernet Sub reachable time indicates the
New
non-Router
Asking
reachability.


ge
Type

"Router
to the Retransmit Time field in a
Ethernet Sub router advertisement packet. This
New Lifetime" in
Interface (IPv6) parameter indicates the time
Router Asking
milliseconds).

"Reachable ICMPV6 unreachability error
packets.
Ethernet Sub
New Time" in Router Options include:
Interface (IPv6)
Asking 1: This function is enabled. ICMPV6
sent.

"Retransmit ICMPV6 redirection error packets.
Ethernet Sub Options include:
New
Interface (IPv6) time" in Router 0: This function is disabled.
Asking
sent.
ICMPV6
Ethernet Channel
New Sub Interface unreacheable
(IPv6)
flag
Ethernet Channel ICMPV6 redirect Mask of address IP1 on the port.

New Sub Interface Default value 0 represents not
(IPv6) flag configured.


ge
Type
Ethernet Channel
New Sub Interface IP Address 2
(IPv6)

Ethernet Channel
(IPv6)

Ethernet Channel
(IPv6)


Ethernet Channel MTU for packets that can pass on a layer of
New Sub Interface a communications protocol (units:
(IPv6) interface bytes). When the default value is 0,


ge
Type

Ethernet Channel Local Address of
does not affect the protocols and
New Sub Interface
architectures of other layers than
(IPv6) Link
must be 0x80.

Ethernet Channel Flag of managed address. After a host receives a
New Sub Interface router advertisement packet, it
(IPv6) address determines the status of automatic


ge
Type

Ethernet Channel Flag of other address. After a host receives a
New Sub Interface router advertisement packet, it
(IPv6) status determines the status of automatic

Interval of
Ethernet Channel Sending
responds to the router request
New Sub Interface
packets that it receives. A router
(IPv6) non-Router
Asking

"Router
Ethernet Channel
to the Router Lifetime field in a
New Sub Interface Lifetime" in
(IPv6)
Router Asking

"Reachable
Ethernet Channel
reachable time indicates the
New Sub Interface Time" in Router
duration during which a node
(IPv6)
Asking
reachability.


ge
Type

Ethernet Channel
New Sub Interface
time" in Router parameter indicates the time
(IPv6)
Asking
milliseconds).

Ethernet Channel packets.
New Sub Interface unreacheable Options include:
(IPv6) 0: This function is disabled.
sent.

Ethernet Channel ICMPV6 redirect
Options include:
New Sub Interface
(IPv6) flag
sent.
Local IP
BFD IPv6 This parameter indicates the local
New
Session IPv6 address of the BFD session.
Address(IPv6)
This parameter indicates the IPv6

Peer IP address of the BFD session on the
BFD IPv6
New peer end. It should be filled out
Session
Address(IPv6) according to the practical address of
the peer device.


ge
Type

desired minimum time interval of
The minimum sending packets on the local. There
BFD IPv6
New is no value range for modification in
Session
sending interval the script, which is for upgrade to
make it be compatible with the old
configuration.

minimum time interval of receiving
packets supported on the local.
The minimum
BFD IPv6 There is no value range for
New
Session modification in the script, which is
receiving interval
for upgrade to make it be
compatible with the old
configuration.
The minimum
This parameter can only be 0.
BFD IPv6
New receiving Echo Please do not configure it because
Session
Echo is not supported now.
interval

detection time accumulator. There
Detecting time
BFD IPv6 is no value range for modification in
New
Session the script, which is for upgrade to
counter
make it be compatible with the old
configuration.
BFD IPv6
New BFD Mode 0 represents asynchronous mode
Session
BFD IPv6
New Used BfdAuth Configuration for auth in BFDV6
Session


ge
Type
This parameter indicates that

whether damping is enabled for the
BFD session.
When damping is enabled, and the
link oscillation is frequent (i.e., the
status is changed between UP and
DOWN frequently), the BFD session
enters the status of damping
suppression. At this time, even link
BFD IPv6
New Damp Indication and port status recover from
Session
DOWN, BFD detection failure
cannot recover to avoid the frequent
change of BFD detection results
caused by the frequent link
oscillation.
0 indicates that damping is not
enabled for the BFD session, and 1
indicates that damping is enabled
for the BFD session.
This parameter indicates the delay

time of sending new authentication
packets by the BFD session.
0 is to send the new authentication
The delay time
packets immediately after
authentication configuration.
of sending
Other values mean that new
BFD IPv6 authentication is used to send
New packet with new
Session packets after DELAYTIME
milliseconds after authentication
authentication
configuration.
If the new authentication packets
key
are received from the peer end or
the board of the session is restarted
within the delay time, the new
authentication takes effect.
BFD IPv6 VPN that BFDV6 IP address

New Used VPN VRF
Session belongs to.


ge
Type
Static route This parameter specifies the

Static
New destination address of an IPv6
Route(IPV6)
network prefix route.
Static route
I This parameter specifies the length
Static
New network mask of destination subnet of an IPv6
Route(IPV6)
route.
length
Static Nexthop type, values:

New nexthop Type
Route(IPV6) 0: Nexthop is IP address
When the next-hop type of a static

Route nexthop
Static route is set to IP address, this
New
Route(IPV6) parameter specifies the next-hop IP
address
address.

administrative distance of a static
route.
The administrative distance
Static
New Route distance specifies the priority of a routing
Route(IPV6)
protocol. The smaller the value of
this parameter is, the higher the
priority of using the route advertised
by this routing protocol is.

enable Bidirectional Forwarding
Detection (BFD) or ICMP Path
Static Detection (IPD) on a specified route.
New Route BFD flag
Route(IPV6) Options:
0: BFD or IPD on this route is
disabled.
1: BFD on this route is enabled.
When the next hop of an IPv6 route

Static
New Used IpUnIntf is set to egress port, this parameter
Route(IPV6)
specifies logic address of the port.


ge
Type
When the next hop of an IPv6 route

Static is set to egress tunnel, this
New Used TunnelTp
Route(IPV6) parameter specifies logic address of
the tunnel.
Used Ethernet IP
New Static ND Entry Ethernet port of Static ND.
Interface (IPv6)
Used Ethernet
New Static ND Entry Sub Interface Ethernet sub-port of Static ND.
(IPv6)
Destination address of a packet

New Static ND Entry IPv6 address
sent by the local end.
New Static ND Entry Mac address Remote-end MAC address.
Length of
This parameter indicates the service
New Static ND Entry Service IP IP address length and the IP
address type (IPv4 or IPv6).
address
Length of IP This parameter indicates the IP

Loopback IP
New address length and the IP address
Interface
Address type (IPv4 or IPv6).
Loopback IP Address IP1 on the port. Default

New IP Address 1
Interface value 0 represents not configured.

Loopback IP
Interface


ge
Type

New IP Address 2

Loopback IP
Interface

New IP Address 3

Loopback IP
Interface

New IP Address 4

Loopback IP
Interface
Loopback IP VPN that BFDV6 IP address

New Used VPN VRF
Interface belongs to.
Length of IP
Virtual IP Length of the IP address used to
New
Interface distinguish IPV4 and IPV6
Address
Virtual IP Address IP1 on the port. Default

New IP Address 1

Virtual IP
Interface

New IP Address 2


ge
Type

Virtual IP
Interface

New IP Address 3

Virtual IP
Interface

New IP Address 4

Virtual IP
Interface
Virtual IP VPN that BFDV6 IP address

New Used VPN VRF
Interface belongs to.
Total Received IPv6 Packet This counter counts the total

C380460007
Count Received IPv6 Packet Count
This counter counts the total

Total Received IPv6 Packet
C380460008 Received IPv6 Packet
Bytes(High 32bit)
Bytes(High 32bit)

Total Received IPv6 Packet
C380460009 Received IPv6 Packet
Bytes(Low 32bit)
Bytes(Low 32bit)
Total Transmitted IPv6 Packet This counter counts the total

C380460010
Count Transmitted IPv6 Packet Count


Total Transmitted IPv6 Packet
C380460011 Transmitted IPv6 Packet
Bytes(High 32bit)
Bytes(High 32bit)

Total Transmitted IPv6 Packet
C380460012 Transmitted IPv6 Packet
Bytes(Low 32bit)
Bytes(Low 32bit)
This counter counts the received

Count of received extern IPV6
C380760007 extern IPV6 fragments to be
fragments to be reassembled
reassembled
This counter counts the

Count of discarded extern IPV6
C380760008 discarded extern IPV6 packets
packets for offset error
for offset error

packets for table collision
for table collision

packets for reassembly time out
for reassembly time out
Count of successfully This counter counts the

C380760011 reassembled extern IPV6 successfully reassembled extern
packets(after reassembly) IPV6 packets(after reassembly)
Fault Management
No impact.
No impact.
No impact.
Impacted Features

No impact.
4.27 ZGO-05-05-001 BSC Local Switch
4.27.1 Description
When this feature is activated, if the calling party and the called party of a voice call are
within the coverage of the same BSS, and the two MSs are using the same codec mode,
then the voice data is not sent to the CN via Ater/A interface, but is looped back in the
BSC, as shown in the figure below. The blue arrows stand for voice data path without
BSC Local Switch, while the red dashed line stands for voice data path with BSC Local
Switch.
Figure 4-6 BSC Local Switch
Um Abis Ater A
BTS2
MS1
BTS1 BSC TC CN
BTS3
MS2
The two MSs using the same codec mode means that they both use FR, or HR, or EFR.
Or, they both use AMR-FR with the same ACS, or they both use AMR-HR with the same
ACS.
At each call setup or handover, the BSS decides whether the BSC local switch can be set
up, or needs to be released and changed back to the CN switch.
The non-3GPP local switch cannot be supported when IP A is used, while 3GPP local
switch supports both TDM A and IP A.
The 3GPP based local switch involves the modification on the CN, while the non-3GPP

local switch doesnt depend on the CN.
System Capacity
In the case of remote transcoder deployment, this feature saves Ater interface
transmission resources.
This feature has similar effect as the TrFO feature provided by the CN. So in case that
the CN does not have the TrFO feature, this feature also saves the TC resources and
improves the voice quality.
When the 3GPP based local switch is adopted, the IP A transmission resources can also
be saved.
Network Performance
The optimization of this feature imposes the following impacts on network performance in
BSC local switch:
MOS increases.
Voice quality improves.
4.27.4 Hardware
No impact
Only work on E1 A.

License
Table 4-67 BSC Local Switch License Description

NE Item Unit
ZGO-05-05-001 BSC Local Switch BSC BSC LCLS per

support (per TRX
TRX)

controls whether to support establishing
Local Switch
local switching during a voice call. It also
Protocol
indicates the supported local switching
protocol.
BSCLclsSupport
BSC local switching. It is valid when
LocalSwitchSup is enabled.
New When local switching without changing A
interface is supported, this parameter
LSMonitorSwitch indicates a switch that controls whether to
support call monitoring during local
switching.

C902130001 The request number of This counter counts the number of

local switch establish requests of local switch establishment
(inside BSC) inside BSC received by the service
module from the local switch
management module.

local switch release normal calls returned from the local
(return normal call) switch after the service module
receives the request message. This
measurement is performed at two
measurement points. The first
measurement point: After handover is
performed, if the local switch cannot be
held, the local switch management
module sends the request of local
switch establishment to reestablish the
voice channel that passes TC. After the
RANCS module receives the request
message, the counter counts. The
second measurement point: If the local
switch cannot be held due to various
abnormalities, the local switch
management module sends the
request of local switch termination.
After the RANCS module receives the
termination request, the counter
counts.
C902130005 The failure number of This counter counts the number of

establishing local failures of local switch establishment
switch(inside inside BSC, and
BSC/connect fail) the failure is due to connection failure.

establishing local failures of local switch establishment
switch(inside BSC/other inside BSC, and
reason fail) the failure is due to other causes
except for connection failure.


returning normal call (Abis failures of the local switch returning the
unavailable) normal call, and the failure is due to
Abis resource unavailable. When the
local switch is inside the site or the site
group, the corresponding Abis resource
is not required after the local switch is
established, thus the resource is
released. However, when the local
switch returns the normal call, the Abis
resource should be requested again. If
the database module returns that the
Abis resource request fails, the counter
increments.

returning normal call failures of the local switch returning the
(connect fail) normal call, and the failure is due to
connection failure. When the local
resource and the TC resource (for
external TC, it is Ater resource) should
be connected again.

returning normal call (Ater failures of the local switch returning the
Ater resource unavailable. When BSC
is configured as TC being external, the
corresponding Ater resource is not
required after the local switch is
switch returns the normal call, the Ater
iTC returns that the Ater resource
request fails (Ater_ResrcReqNegAck),
the counter increments.
C902130016 The Number of Local The Number of Local Switch Establish

Switch Establish (In Call (In Call Setup)
Setup)

C902130017 The Number of Local Call The Number of Local Call Used 3GPP
Used 3GPP Protocol Protocol
C902130018 The Number of The Number of Establishing Local

Establishing Local Switch because of Handover In BSC
Switch because of
Handover In BSC
C902130019 The Number of Releasing The Number of Releasing Local Switch

Local Switch because of because of Handover In BSC
Handover In BSC
C902130020 The Number of Keeping The Number of Keeping Local Switch

Local Switch because of because of Handover In BSC
Handover In BSC
C902130021 The Number of Releasing The Number of Releasing Local Switch

Local Switch because of because of Handover between BSC
Handover between BSC
C902130022 The Number of The Number of Establishing Local

Establishing Local Switch because of Handover
Switch because of between BSC
Handover between BSC
C902130023 The Request Number of The Request Number of Releasing

Releasing Local Switch by Local Switch by BSC
BSC
C902130024 The Request Number of The Request Number of Establishing

Establishing Local Switch Local Switch by MSC
by MSC
C902130025 The Successful Number of The Successful Number of Establishing

by MSC
C902130026 The Failure Number of The Failure Number of Establishing

by MSC
C902130027 The Request Number of The Request Number of Releasing

Releasing Local Switch by Local Switch by MSC
MSC
C902130028 The Successful Number of The Successful Number of Releasing

Releasing Local Switch by Local Switch by MSC
MSC

C902130029 The Request Number of The Request Number of Changing

Changing Local Switch Local Switch configuration by MSC
configuration by MSC
C902130030 The Successful Number of The Successful Number of Changing

Changing Local Switch Local Switch configuration by MSC
configuration by MSC
C902130031 The Total Call Time of The Total Call Time of Local Switch In
Local Switch In BSC BSC
C901070118 Call Drop by Releasing This counter counts the number of call
Local Switch drops due to failure in releasing local
switch.
C901060084 Attempts of handover on The counter counts when the local

TCH/F caused by local switch initiates FR service handover.
switch

TCH/H caused by local switch initiates HR service handover.
switch
Fault Management
No impact.
No impact.
ZGO-04-02-006 TFO
ZGO-04-02-010 Automatic Level Control (ALC)
ZGO-04-02-011 Automatic Noise Reduction (ANR)
ZGO-04-02-012 Acoustic Echo Cancellation (AEC)

Impacted Features
No impact.
4.28 ZGO-05-05-002 BTS Cluster Local Switch
4.28.1 Description
within the coverage of the same BTS group, and the two MSs use the same codec type,
then the voice data is not sent to the BSC via Abis interface, but is looped back in this
BTS group, as shown in the figure below. The blue arrows stand for voice data path
without BTS cluster Local Switch, while the red dashed line stands for voice data path
with BTS cluster Local Switch.
Figure 4-7 BTS Cluster Local Switch
Um Abis Ater A
BTS2
MS1
BTS1 BSC TC CN
BTS3
MS2
Here the BTS cluster refers to a group of BTSs among which every two BTSs can
exchange user data directly. A BTS cluster may be multiple BTSs connected to the same
hub-BTS, or multiple BTSs in the same IP routing area.
The two MSs using the same codec type means that they both use FR, or HR, or EFR.
ACS.
At each call setup or handover, the BSS decides whether BTS cluster local switch can be

set up, or needs to be released and changed back to the CN switch.
Non 3GPP local call local switch cannot be supported when IP A is used, while 3GPP
local call local switch supports both TDM A and IP A.
3GPP based local call local switch involves the modification on the CN, while non 3GPP
local call local switch doesnt depend on the CN.
System Capacity
This feature has the similar effect to the TrFO feature provided by the CN. So in case that
Network Performance
The optimization of this feature imposes the following impacts on network performance
in BSC local switch:
MOS increases.
4.28.4 Hardware
No impact.
Only work on E1 A, and there are straight path between the BTS.

License
Table 4-70 BTS Cluster Local Switch License Description
Configured License Sales

ZGO-05-05-002 BTS Cluster Local BSC BTS Group per

Switch LCLS support TRX
(per TRX)

Local Switch
Protocol
protocol.
Old This parameter indicates the No. of the
Used Site Group of local switch group that the BTS belongs
Local Switch to. It's possible that a BTS doesn't belong
to any local switch group.
Old This parameter indicates the No. of the
local switch group that the BTS belongs
SiteGroupId
to. It's possible that a BTS doesn't belong
to any local switch group.
Old This parameter indicates whether the BTS
supports two calls to set up a local
Site group local switch
switching link through the BTS equipment
support
only when the calls are located under any
two BTSs of the group in question.

C902130003 The Request Number of This counter counts the number of

Local Switch Establish requests of local switch establishment
(Inside Site Group) inside BSC received by the service
module from the local switch
management module.

local switch release normal calls returned from the local
(return normal call) switch after the service module
counts.
C902130008 The Failure Number of This counter counts the number of

Establishing Local Switch failures of local switch establishment
(Inside Site Group/Fail inside the site
Returned by Site) group, and the failure is due to
response failure of the site.

(Inside Site Group/No inside the site group, and the failure is
answer from Site) due to that the site's responding time
expires.


(Inside Site Group/Other inside the site group, and the failure is
Reason Fail) due to other causes except for that the
site fails to respond and the site's
responding time expires.

Returning Normal Call failures of the local switch returning the
(Abis unavailable) normal call, and the failure is due to
increments.

be connected again.


C902130033 The Total Call Time of

Local Switch In Site Group
C901070118 Call Drop by Releasing This counter counts the number of call
Local Switch drops due to failure in releasing local
switch.

TCH/F caused by local switch initiates FR service handover.
switch

switch
Fault Management
No impact.
No impact.
ZGO-04-02-006 TFO

Impacted Features
No impact.
4.29 ZGO-05-05-003 BTS Local switch
4.29.1 Description
within the coverage of the same BTS, and the two MSs use the same codec type, then
the voice data is not sent to the BSC via Abis interface, but is looped back in this BTS, as
shown in the figure below. The blue arrows stand for voice data path without BTS Local
Switch, while the red dashed line stands for voice data path with BTS Local Switch.
Figure 4-8 BTS Local Switch
Um Abis Ater A
MS1
BTS2
MS2
BTS1 BSC TC CN
BTS3
MS3
The two MSs using the same codec type means that they both use FR, or HR, or EFR.
ACS.
At each call setup or handover, the BSS decides whether BTS local switch can be set up,

or needs to be released and changed back to the CN switch.
Non 3GPP local call local switch cannot be supported when IP A is used, while 3GPP
local call local switch supports both TDM A and IP A.
3GPP based local call local switch involves the modification on the CN, while non 3GPP
local call local switch doesnt depend on the CN.
System Capacity
This feature has the similar effect to the TrFO feature provided by the CN. So in case that
Network Performance
The optimization of this feature has the following impacts on network performance in
BSC local switch:
MOS increases.
4.29.4 Hardware
No impact.
Only work on E1 A.

License
Configured License Sales

ZGO-05-05-003 BTS Local Switch BSC BTS LCLS per

support (per TRX
TRX)

Local Switch
Protocol
protocol.
Old Site local switch This parameter indicates whether the BTS
support supports two calls under this BTS to set up a
local switching link through the BTS
equipment only.


C902130002 The Request Number of This counter counts the number of
Local Switch Establish requests of local switch establishment
(Inside Site) inside BSC
received by the service module from
the local switch management module.
C902130004 The request number of local This counter counts the number of
switch release (return normal normal calls returned from the local
call) switch after the service module
counts.
(Inside Site/Fail Returned by inside the site, and the failure is due to
Site) response failure of the site.
(Inside Site/No answer from inside the site, and the failure is due to
Site) that the site's responding time expires.


(Inside Site/Other Reason inside the site, and the failure is due to
Fail) other causes except for that the site
fails to respond and the site's
responding time expires.
Returning Normal Call (Abis failures of the local switch returning the
increments.
be connected again.


C902130032 The Total Call Time of Local
Switch In Site
C901070118 Call Drop by Releasing Local This counter counts the number of call
Switch drops due to failure in releasing local
switch.
TCH/F caused by local switch switch initiates FR service handover.
switch
Fault Management
No impact.
No impact.
ZGO-04-02-006 TFO

Impacted Features
No impact.
4.30 ZGO-06-01-002 Speech Quality Supervision
4.30.1 Description
Speech Quality Supervision (SQS) bridges a relation between the speech quality and a
range of factors including radio transmission performance, Abis transmission
performance, DTX and handover events. This relation enables us to visually measure the
impact of these factors on the speech quality.
SQS is classified into five levels in networks, as listed in the following table.
SQS Level User Satisfaction
Excellent Very clear speech, very small delay, smooth communication
Good Clear speech, small delay, unsmooth communication, a little bit noise
Fair Not so clear speech, large delay, tardy communication
Poor Poor speech quality, very large delay, repetitive communication
Very poor speech quality, intolerably large delay, discontinuous

Bad
communication
The BSS evaluates the speech quality of the channel with the projection of the algorithm,
BER, FER, handover numbers, DTX and transmission error ratio of the Abis interface.
The BSS can analyze the SQS of a dedicated cell or the whole network, and give the
statistical report of the call numbers and proportion for each level. These reports also
work as the reference for the network maintenance and optimization.
The UR13 optimizes the SQS algorithm and increases the data interface to the CDT
system. If CDT is activated, the BSC could send the parameters that influence the SQS

and SQS value to the CDT server. Then system maintainers could use the CDT tools to
analyze and monitor the speech quality of the system.
The UR13 could estimate the MOS of a call. The system specifies up to two users,
tracking users and estimates the MOS values of the call.
System Capacity
No impact
Network Performance
This feature provides the following benefits on the network performance:
The EMI statistical information is added to measurement report, so the uplink flow
increases.
4.30.3 Impact on NES
This feature is implemented on the BSC and BTS.
4.30.4 Hardware
No impact
No impact
License
This feature is under the license control

Table 4-75 Speech Quality Supervision License Description

NE Item Unit
ZGO-06-01-002 Speech quality BSC Speech quality TRX(per

supervision supervision (per TRX)
TRX)
old Report voice quality This parameter is used by the BTS to

determine whether to carry speech
quality related parameters in the
measurement report and during
measurement report preprocessing
and enhanced measurement report
preprocessing.
new EMI information on This parameter controls whether the
single-user report MOS calculation result is reported.
new EMI Control This parameter indicates how to
process compatibility between the EMI
and BTS.
C901120195 Number of uplink voice This counter counts the number of

quality DMOS grade1 uplink voice quality DMOS grade1



Number of uplink voice This counter counts the number of

C901120198

C901120199

C901120200

C901120201

C901120202

C901120203

C901120204

Number of downlink voice
C901120205 downlink voice quality DMOS
quality DMOS grade1
grade1

quality DMOS grade2
grade2

quality DMOS grade3
grade3

quality DMOS grade4
grade4

quality DMOS grade5
grade5

quality DMOS grade6
grade6

quality DMOS grade7
grade7


quality DMOS grade8
grade8

quality DMOS grade9
grade9

quality DMOS grade10
grade10
Fault Management
No impact.
No impact
No impact
Impacted Features
No impact
4.31 ZGO-06-01-020 Super Signaling Trace
4.31.1 Description
Super Signaling Trace achieves all UEs wireless layer signaling collection and reports in
the home RNC&BSC of 3G/2G. Concerning the data types, in addition to the signaling
collection of standard protocol interface such as A/IU, Abis/IUB, UM/UU and IUR, the
specified internal event information can be customized. By the offline or online analysis

on these signaling and events, this feature provides the foundation for UE monitoring,
network maintenance, fault location, network planning and optimization.
System Capacity
Enabling this feature improves the DMP CPU by 5%.
Network Performance
No impact
4.31.3 Impact on NES
4.31.4 Hardware
Need ZXUR 9000 with specific UMP.
No impact
License
This feature is not under the license control

Type


Type
This parameter indicates the destination IP

Inner IP address of Log address of FST (Signalling trace for full
New
Server for FST. RNC) data sent by the system, meaning the
IP address of the FST server.
This parameter indicates the IP address of

IP address of Log the FST (Signalling trace for full RNC)
New
Server-FST to OMM. server from which the OMM server obtains
the FST data.
This parameter indicates the IP address of

IP address of Log the FST (Signalling trace for full RNC)
New
Server-FST to NDS or AS server from which the NDS server obtains
the FST data files.
This parameter is an index number,

New Index No indicating the policy-associated ID of a
traced cell.
This parameter indicates whether standard

IU Interface Signal
New IU signaling messages are submitted in full
Protocol Switch
signaling tracing.

IUB Interface Signal
New IUB signaling messages are submitted in full
Protocol Switch
signaling tracing.

IUR Interface Signal
New IUR signaling messages are submitted in
Protocol Switch
full signaling tracing.

UU Interface Signal
New UU signaling messages are submitted in full
Protocol Switch
signaling tracing.
This parameter indicates whether vendor

Vendor Specific Signal
New specific signaling messages are submitted
Protocol Switch
in full signaling tracing.
This parameter indicates the start date,

Start Date
New which means the year, month, day when full
(Year-Month-Day)
signaling tracing starts.
This parameter indicates the start date,

Stop Date
New which means the year, month, day when full
(Year-Month-Day)
signaling tracing stops.


Type
This parameter indicates the number of

New Time Segment per Day valid time segments for signaling tracing in a
day.
Start Time per Day This parameter indicates the time (hour and
New
(Hour:Min) minute) when full signaling tracing starts.
Stop Time per Day This parameter indicates the time (hour and
New
(Hour:Min) minute) when full signaling tracing stops.
This parameter indicates whether full

New All Access Cell signaling tracing is performed for UEs
accessed through all the cells.
The Number of UE
Signalling Trace Data This parameter indicates the number of
New
Collection Configuration configuration indexes of UE signaling.
Index Related to Cell
UE Signalling Trace Data This parameter indicates the configuration

New Collection Configuration index of UE signaling trace data collection
Index Related to Cell related to a cell.
This parameter indicates the FTP type,

New FTP Type
which includes FTP and SFTP.
This parameter indicates the IP version

New ILength of IP Address (IPv4 or IPv6) of the IP connection
corresponding to LogService.
This parameter indicates the FTP IP

New IP Address of NDS or AS address of the NDS (Network Data Server)
or AS (Analysis Server).
This parameter indicates the FTP port of the

New FTP Port NDS (Network Data Server) or AS (Analysis
Server).
This parameter indicates the FTP user

FTP User Name of NDS
New name of the NDS (Network Data Server) or
or AS
AS (Analysis Server).
This parameter indicates the FTP password

FTP User Password of
New of the NDS (Network Data Server) or AS
DNS or AS
(Analysis Server).

199105046 The log files on LogService This counter counts the log files on
board are unavailable. LogService board are unavailable.
199105047 The FTP link for full signal This counter counts t The FTP link
tracing is exceptional. for full signal tracing is
exceptional.
Fault Management
No impact.
No impact
No impact
Impacted Features
No impact
4.32 Other Enhancements
4.32.1 FACCH Enhancement
Add a decision condition when enabling the FACCH switch: The TCH load threshold of
the home cell. On the condition that the home cell TCH has some idle load, the FACCH
can be used during the immediate assignment, speeding up the call connection.
Otherwise, the FACCH switch is unavailable.
The latency that a call establishment borrows FACCH is very short, but it speeds up the
call connection for 1-2 sec, which features the high effectiveness. If the system resources

are allowable, it can improve the call establishment latency of the calling service inside
the cell.
This optimization about the paging preemption mechanism is controlled by following

parameters:

Old FACCH Enhance This parameter indicates a switch that
controls whether to enhance the FACCH.
Old the TCH load This parameter indicates a load threshold

threshold of for enhancing the FACCH. After the FACCH
FACCH enhance enhancement switch is enabled, when the
cell load (load of subcell 1 if has subcells) is
less than or equal to the value of this
threshold, services can be carried on the
FACCH.
The formula for calculating the load: number
of busy CS channels*100 / (number of busy
CS channels + number of idle CS channels)
The following counters will be influenced by this feature:

C901050060 Number of attempts of The channel type requested by the

mode modification for MSC assignment matches with channel
assignment type that is currently occupied, but the
mode must be changed with the
speech version. This counter counts
the number of mode modification
attempts during assignment.
C901050061 Number of successes of This counter counts the number of

mode modification for times that a mode modify is
assignment successfully performed in assignment.
4.32.2 Packet Loss Compensation
The voice decoding algorithm compensates the packet loss when there is no message. A
compensation algorithm has already existed before. The compensation this time is the
aggregation version of latest developed results based on the multi-media algorithm. The
latest version packet loss compensation does not improve the MOS average value much,
but it makes some improvements in low segment. UR13 combines the AMR packet loss
compensation.
The optimization of this feature imposes the following impacts on network performance:
The PESQ MOS can be improved.
ZGO-04-02-006 TFO
ZGO-05-05-001 BSC Local Switch
4.32.3 Dynamic TRX License

Traffic tides appear because of different coverage of cell. And this traffic tides occurs
inconsistently in one BSC or between BSCs. According to the statistical data of
commercial network, the TRX license could be allocated dynamically in BSC or between
BSCs. The TRX license can be adjusted between different cells or between BSCs. By
using this function, the number of TRX license can be decreased. Also the investment of

operator will reduce.
This feature also reduces the work of network engineer. If the traffic has been transferred
between different cells or different BSCs, the TRX license could be adjusted
automatically from cell to cell or from BSC to BSC, without intervention by changing
configuration.
This feature is implemented on BSC and EMS.
This feature is controlled by following parameters:
New Cell load Threshold If the load of a cell exceeds this threshold,
of TRX license this cell is deemed as a heavy-load cell
increase and more TRX licenses are required.
New Threshold of the If the load of a cell is lower than this

Cell expected load threshold during TRX license adjustment,
this cell can release part TRX licenses to
other busy cells.
C901080096 Number of TRXs having Count the number of TRXs which

license have license.
C901080097 Number of no license TRXs Count the number of TRXs which

don't have license.
C901080098 Number of failed TRX license When cell request TRX license
request urgently, if the number of trx
license reached the maximum or
the other cells can not release
TRX, then count this counter.

4.32.4 DL Small Data Reducing Code Sending
The radio block at air interface bears different size data by different levels coding
methods. High level coding method requires high quality wireless environment. If the
data does not full the radio block, reduces the current coding to full the block, improving
the transmission reliability.
This feature enhancement is controlled by following parameter:
Table 4-84 Parameters Related to This Enhancement

New Optimizing of A radio block can carry data in different
sending downlink sizes by using coding schemes in different
small data levels. The coding scheme in the higher
level requires better radio quality. If the radio
block is not fully filled with data, you can
lower the current coding scheme level until it
is fully filled, to increase the transmission
reliability of this data block.
The enhancement has the following impacts:
This feature facilitates the reliable transmission of small data in poor wireless
environment, especially for signaling TBF data such as Attach, PDP activation and so
on.
This feature brings small deterioration to KPI such as ratio of high coding scheme due to
the increase of low coding scheme data blocks such as CS1 or MCS1.

Speech Quality Supervision

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Speech Quality Supervision

Uploaded by

Copyright:

Available Formats

GERAN Network Impact

GERAN Network Impact Report

2014 ZTE Corporation. All rights reserved.

ZTE Confidential & Proprietary 1

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

2 General Impact ................................................................................................ 14

3 Summary of Feature Impacts ......................................................................... 35

4 Impacts of UR13 Features on UR12 ............................................................... 37

2 ZTE Confidential & Proprietary

4.2.2 Capacity and Performance................................................................................. 40

ZTE Confidential & Proprietary 3

4.7.4 Hardware ........................................................................................................... 56

4 ZTE Confidential & Proprietary

4.12.6 Operation and Maintenance ............................................................................... 73

ZTE Confidential & Proprietary 5

4.18 ZGO-01-03-004 Cell Broadcast Service ........................................................... 106

6 ZTE Confidential & Proprietary

4.23.2 Capacity and Performance............................................................................... 146

ZTE Confidential & Proprietary 7

4.28.4 Hardware ......................................................................................................... 192

8 ZTE Confidential & Proprietary

Figure 4-1 Uplink Neighbor Cell Coordination ....................................................................76

Figure 4-4 Deployment of Stand-alone CBC (BSC-CBC direct interface) ........................108

Figure 4-5 Dual-Transfer-Mode ........................................................................................112

Table 2-1 Product Versions Required for UR13 .................................................................14

ZTE Confidential & Proprietary 9

Table 3-1 Impact Severity of New/Optional Features in UR13 ...........................................36

10 ZTE Confidential & Proprietary

Table 4-29 New Counters Related to This Feature ............................................................74

ZTE Confidential & Proprietary 11

Table 4-59 Counters Related to This Feature ..................................................................142

12 ZTE Confidential & Proprietary

1 About This Document

1.2 Intended Audience

This document intends for:

Network planning engineers

1.3 Change History

1.4 Document Versions

ZTE Confidential & Proprietary 13

2.1 Version Requirements

Table 2-1 lists the products versions required for UR13.

Table 2-1 Product Versions Required for UR13

BTS SDR V4.13.xx

OMMB OMMB V12.13.4x

NetNumen U31 V12.13.5x

2.2 Capacity and Performance

Table 2-2 Capacity of iBSC

Max number of TRXs 3,072

Max number of cells 1,536

Max number of sites 1,536

14 ZTE Confidential & Proprietary

Maximum Erl (Voice call) 15,000 Erl

Maximum PS Data Throughput 2,800 (basic module)

ZXUR9000 GSM BSC

Max number of TRXs 5,600 12,000 12,250

Max number of cells 5,600 5,600 5,600

Max number of sites 2,800 2,800 2,800

BHCA 8,400K 16,800K 16,800K

Maximum Erl (Voice call) 33,600Erl 72,000Erl 73,500 Erl

Max number of TRXs 8,000 16,000 16,000

Max number of cells 8,000 8,000 8,000

Max number of sites 4,000 4,000 4,000

BHCA 11,200K 22,400K 22,400K

In Table 2-2, Table 2-3 and Table 2-4 :