SJ-20100211152857-009-ZXWN MSCS (V3.09.21) MSC Server Traffic and Load Control

ZXWN MSCS
MSC Server
Traffic and Load Control

Version 3.09.21
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2010 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of
this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATION
or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the
information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject
matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,
the user of this document shall not acquire any license to the subject matter herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No.
Revision Date
Revision Reason
R1.0
Feb. 28, 2010
First edition
Serial Number: SJ-20100211152857-009
Contents
About This Manual............................................. I

Declaration of RoHS Compliance ....................... I
Traffic Control Principle.....................................1
Flexible Traffic Control ..................................................... 1
Traffic Control Subsystem ................................................ 1
Traffic Control Configuration .............................5

Traffic Control Commands ................................................ 5
Incoming/Outgoing Destination Code Control ................. 5
Outgoing Trunk Group Control ...................................... 8
Configuraitons on MML Termainal.....................................12
Creating Traffic Control on Destination Code..................12
Creating Outgoing Trunk Traffic Control ........................16
Creating a Number Prefix Object..................................19
Creating Dynamic Traffic Control..................................20
Load Control Concepts and Principles.............. 23

Load Control Concepts ...................................................23
Service Control .........................................................24
Congestion Control ....................................................24
Service Control Principles ...............................................25
Service Control Concepts ............................................25
Service Control Principle .............................................25
Function Implementation ............................................26
Congestion Control Principles ..........................................27
Interface Congestion Control .......................................27
Congestion Level Mechanism ..............................27
Congestion Control on Mc Interface .....................28
Congestion Control on NNI Interface....................28
Congestion Control on A/Iu Interface ...................28
Link Congestion Control..............................................28
Calcualation on SMP Congestion Level..................28
Calculation on Link Congestion Level ...................29
Confidential and Proprietary Information of ZTE CORPORATION
ZXWN MSCS Traffic and Load Control
Link Congestion Control Policy ............................29

Adjacent Office Congestion Control ..............................29
RNC/BSC Adjacent Office Congestion Control .........29
MGW Adjacent Office Congestion Control..............29
MSC Adjacent Office Congestion Control...............30
Service Control Configuration.......................... 31

Service Control Configurations.........................................31
Service Control Configuration Based on Total Traffic ...........31
Configuring Service Control Cycle ................................33
Setting the Equivalent CPU Consumption ......................34
Modifying MSC Service Capability Limit .........................35
Service Control Configuration Based on Single Incoming
Service ................................................................36
Service Control Configuration Based on Single Outgoing
Service ................................................................37
Enabling the Function of only Controlling Location
Update to HLR...................................................39
Creating GT Group Control Template ............................40
Creating Destination Home GT Group ...........................41
Congestion Control Configuration.................... 43

Congestion Control Configurations ...................................43
Configuration Methods for Congestion Control on Each
Interface ..............................................................43
Basic Configuration ........................................................44
Configuring the Cycle of MP Load Statistics ...................44
Configuring CMP Congestion Control Threshold ..............45
Configuring Minimum Guaranteed Passing Number of
Each Service In Case of CMP Congested................46
Configuring Subscriber Priorities ..................................47
Configuration for Adjacent Office Congestion Control ..........48
Load Control on NNI Interface .....................................48
Modifying the ISUP/BICC-Starting-ACL Function
for Adjacent Office .................................50
Configuring Overload Control Threshold for Trunk
Groups .................................................51
Configuring Thresholds for Automatic Congestion
Control .................................................52
Configuring a Hold Time for the Congestion Level
of An Adjacent Office ..............................54
II
Configuring Whether to Send a REJECT Message

in Case of Service Overload .....................55
Configuring Variable Control ...............................56
Configuring Call Level of Incoming Call
Subscribers (Incoming Office)..................57
Subscribers (Number Analysis) ................58
Congestion Control on Mc Interface..............................60
Configuring Adjacent Office Congestion Control
on Mc Interface .....................................60
Configuring Congestion Reporting Capability .........61
Configuring Gateway Overload ............................62
Configuring MGW RTP Congestion Control.............66
Congestion Control on A/Iu Interface ...........................67
Configuration on Adjacent Office Congestion
Control on A/Iu Interface ........................68
Configuring MP Predefined Timer.........................68
Configuring Variable Control ...............................69
Configuring Performance Statistics of MSCS Load
Control.................................................................70
Link Congestion Control..................................................73
Enabling SCCP Congestion Control ...............................74
Configuring Transmission Load and Traffic Control ..........75
Setting an MTP link for congestion control ....................76
Configuration on Threshold for SMP Load Congestion
Control.............................................................77
Configuring the Minimum Guaranteed Passing
Number of Incoming Services When SMP Is
Congested ........................................................77
Setting Receiving Flow Control ....................................78
Applications of Traffic and Load Control .......... 81

Application Introduction .................................................81
Application of Traffic Control............................................81
Application of Load Control .............................................83
Relevant Alarm Information about Load Control .............83
Processing Flow of Load Control...................................84
Figure.............................................................. 87
Table ............................................................... 89
Index .............................................................. 91
III
This page is intentionally blank.
IV
About This Manual

Purpose
At first, thank you for choosing ZXWN wireless core network system of ZTE Corporation!
ZXWN system is the 3G mobile communication system developed
based on the UMTS technology. ZXWN system boasts powerful
service processing capability in both CS domain and PS domain,
providing more abundant service contents. Comparing with the
GSM, ZXWN provides telecommunication services in wider range,
capable of transmitting sound, data, graphics and other multi-media services. In addition, ZXWN has higher speed and resource utilization rate. ZXWN wireless core network system supports both
2G and 3G subscriber access, and provides various services related with the 3G core network.
The ZXWN MSCS system is designed for the UMTS system at the
core network control level. It supports the GSM core network,
UMTS protocols in the R99/R4/R5 stage and relevant functions at
the same time, and provides the carriers with an overall solution
to the evolution from the GSM core network to the 3GPP R99 and
then to the 3GPP R5.
The ZXWN MSCS system completes the functions of the Mobile
Switching Center Server and the Visitor Location Register (VLR)
together, and provides the Service Switching Point (SSP) functions
of intelligent calls. The ZXWN MSCS system supports the MGCF
function, and the coexistence of the MGCF and GMSCS. It also can
smoothly upgrade to the MGCF.
This manual describes the traffic and load control of ZWWN MSCS
for protecting the system from the impact of large traffic and exchange overload during the routine maintenance.
Intended
Audience
This manual is intended for engineers and technicians who perform

maintenance activities on the ZXWN MSC Server.
Prerequisite Skill
and Knowledge
To use this manual effectively, users should have a general understanding of wireless telecommunications technology. Familiarity
with the following is helpful.
What Is in This
Manual
ZXWN system and its various components
Local maintenance procedures.
This manual contains the following chapters:

Chapter
Summary
Chapter 1, Traffic Control Principle
This chapter describes the

principle of traffic-control system.
Chapter 2, Traffic Control

Configuration

configuration methods related to
traffic control.
Chapter 3, Load Control Concepts

and Principles
This chapter introduces some

concepts and principles about the
load control.
FCC Compliance
Statement
Chapter
Summary
Chapter 4, Service Control

Configuration
This chapter introduces the

service control configuration.
Chapter 5, Congestion Control

Configuration
This chapter introduces the

congestion control configuration.
Chapter 6, Applications of Traffic

and Load Control

applications of traffic control and
load control.
This device complies with part 15 of the FCC Rules. Operation is

subject to the following two conditions.
1. This device may not cause harmful interference.
2. This device must accept any interference received, including
interference that may cause undesired operation.
Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate
the equipment.
Conventions
ZTE documents employ the following typographical conventions.

Typeface
Meaning
Italics
References to other Manuals and documents.
Quotes
Links on screens.
Bold
Menus, menu options, function names, input fields,

radio button names, check boxes, drop-down lists,
dialog box names, window names.
CAPS
Keys on the keyboard and buttons on screens and

company name.
Note: Provides additional information about a certain
topic.
Checkpoint: Indicates that a particular step needs to
be checked before proceeding further.
Tip: Indicates a suggestion or hint to make things
easier or more productive for the reader.
Mouse operation conventions are listed as follows:
II
Typeface
Meaning
Click
Refers to clicking the primary mouse button (usually the

left mouse button) once.
Doubleclick
Refers to quickly clicking the primary mouse button

(usually the left mouse button) twice.
Right-click
Refers to clicking the secondary mouse button (usually

the right mouse button) once.
Declaration of RoHS
Compliance
To minimize the environmental impact and take more responsibility
to the earth we live, this document shall serve as formal declaration that ZXWN MSCS manufactured by ZTE CORPORATION are in
compliance with the Directive 2002/95/EC of the European Parliament - RoHS (Restriction of Hazardous Substances) with respect
to the following substances:
Lead (Pb)
Mercury (Hg)
Cadmium (Cd)
Hexavalent Chromium (Cr (VI))
PolyBrominated Biphenyls (PBBs)
PolyBrominated Diphenyl Ethers (PBDEs)
The ZXWN MSCS manufactured by ZTE CORPORATION meet

the requirements of EU 2002/95/EC; however, some assemblies
are customized to client specifications. Addition of specialized,
customer-specified materials or processes which do not meet the
requirements of EU 2002/95/EC may negate RoHS compliance of the
assembly. To guarantee compliance of the assembly, the need for
compliant product must be communicated to ZTE CORPORATION in
written form. This declaration is issued based on our current level
of knowledge. Since conditions of use are outside our control, ZTE
CORPORATION makes no warranties, express or implied, and assumes
no liability in connection with the use of this information.
II
Chapter
Traffic Control Principle

Table of Contents
Flexible Traffic Control ......................................................... 1
Traffic Control Subsystem .................................................... 1
Flexible Traffic Control

Flexible traffic control is responsible for analyzing traffic statistical
data and equipment running status, manually or automatically setting corresponding traffic control instructions on the background
under the predefined conditions or regulations, and transmitting
data to the foreground. The foreground implements the traffic
control according to traffic control instructions, to dredge normal
traffic effectively and alleviate the impact of excess traffic on the
network.
Traffic Control Subsystem

Overview
The traffic control subsystem consists of the foreground modules

and background system. The background system comprises the
traffic statistical information subsystem and traffic-control instruction-generation subsystem. The traffic foreground comprises the
traffic-control instruction receiving subsystem, and traffic-control
instruction executing subsystem.
Figure 1 shows the detailed structure.
FIGURE 1 STRUCTURE
Structure
OF
TRAFFIC CONTROL SUBSYSTEM
1. Traffic statistical information subsystem

It consists of various functional modules, including the EMF
side, server side, and client side.
The performance client provides the interface of traffic control
for setting the destination code and parameters of traffic control.
The performance server is responsible for accessing and updating the traffic-control structure. After the client side sends the
request for querying the traffic control mechanism, the server
obtains the corresponding offices traffic control mechanism
and traffic-control destination code, and then sends them to
the foreground.
The EMF side judges the conditions of traffic control based on
the latest data from the data table within five minutes. It sends
the destination code of arrival condition and the traffic-control
condition to the foreground, and judges the ongoing destination code. If the traffic-control condition has been released,
then it sends the release command.
2. Traffic-control instruction-generation subsystem
It coordinates with the traffic-control receiving subsystem to
complete the dynamic setting and cancellation of traffic-control
instructions.
3. Traffic-control instruction receiving subsystem
It is responsible for modifying the related traffic-control data
tables after receiving the traffic-control instructions sent from
the background.
4. Traffic control instruction executing subsystem
It is responsible for executing the corresponding traffic-control
instructions to implement their functions by invoking the corresponding interfaces.
The traffic control can be performed on both the incoming side
and outgoing sides, so the traffic of both originated call and
terminated call can be controlled flexibly. The traffic control
of outgoing trunk can only be performed on the outgoing side,
Chapter 1 Traffic Control Principle
while the traffic control of incoming/outgoing destination code

can be performed on both sides, except the temporary alternative routing that can only be performed on the outgoing side.
And the traffic control of terminated calls of local office and
transit calls is performed on the incoming side, while the originated calls of local office are processed on the outgoing side.
The traffic of incoming calls whose trunk group ID is 0 can only
be processed on the outgoing side.
Chapter
Traffic Control
Configuration
Table of Contents
Traffic Control Commands .................................................... 5
Configuraitons on MML Termainal.........................................12
Traffic Control Commands

Traffic control commands are divided into two types:
Incoming/outgoing destination code control
Outgoing trunk control
The combination of incoming trunk group, calling number, and subscriber category can be added to control a certain outgoing call.
Traffic control commands are implemented by the configuration
modules and executed on the MML Terminal window of the NetNumen M30 window.
Incoming/Outgoing Destination Code

Control
Overview
Destination Code
Control
The incoming/outgoing destination code control falls into the following five modes.
Destination code control
Temporary alternative routing
Special announcement
Call gapping control
The destination code control is responsible for restricting the traffic

of incoming calls from specified incoming trunk group to specific
destination code on a percentage basis. The restricted destination
code can be the country code, toll zone code, subscriber number, or special service number, with up to 32 digits at present. It
is available to specify the subscriber category, and to adjust the
restriction scale value with consecutive numbers. The RC_CODEBLOCK_DST failure code is returned when a failure occurs.
The destination code control can be configured on the command

terminal, and implemented by executing the ADD DSTNUMCTRL
command.
The parameters involved are as follows:
Restricted incoming trunk group ID
Restricted calling category
Restricted calling number
Restricted destination code
Start/end executing time of the command
Restriction percentage
For example, the destination code restriction is implemented on

the calls from trunk group 1 of local incoming trunk module 2.
The conditions are as follows:
Restricted destination code is 0208888.
Restricted calling category is ordinary subscriber.
Restricted calling number is 130.
The command is executed from 8:00 to 10:00.
Restricted percentage is 75%, indicating that 75 of 100 calls meeting the above-mentioned conditions are denied.
Temporary
Alternative
Routing
It is used to specify several idle but irregular trunk groups as temporary alternative route for the specified destination code. Meanwhile, it specifies the percentage of traffic overflowing to the temporary alternative route. The system selects the route according to
the specified principle after this command is input. It is available to
specify the restricted incoming trunk group number and restricted
subscriber category. The restriction number can be adjusted with
consecutive numbers. The RC_CODEBLOCK_TMP failure code is
returned when a failure occurs
The temporary alternative route control can be configured on the
command terminal, and implemented by executing the ADD DSTN
UMCTRL command. The parameters involved are as follows:
Restricted destination code type
Temporary alternative route number
The percentage of traffic restricted to entering the temporary

alternative route
For example, the temporary alternative routing is implemented on

the calls from trunk group 1 of local incoming trunk module 2. The
conditions are as follows:
Restricted destination code is 0208888.
Restricted calling category is ordinary subscriber.
Chapter 2 Traffic Control Configuration
Special Recorded
Announcement
The percentage of traffic restricted to enter the temporary alternative route is 75%, indicating that 25 of 100 calls overflow
to the temporary alternative routes.
The sequence of temporary routes is route 6, route 7, route

8, and route 9. The temporary alternative route can only be
selected when all of the normal routes are not available. The
temporary alternative route is selected by the order of 6, 7, 8,
and 9.
According to the destination code and trunk group number of

the call, the system sends special recorded announcement to the
attendant and/or subscriber, requesting to defer the call. The
RC_CODEBLOCK_ANN failure code is returned when a failure
occurs.
Special recorded announcement is configured on the command
terminal, and implemented by executing the ADD DSTNUMCTRL
command. The parameters involved are as follows:
Recorded announcement category.
For example, the special announcement is implemented on the

trunk group 1 of local incoming trunk module 2. The conditions
are as follows:
The restricted destination code is 0208888.
The restricted calling category is ordinary subscriber.
The restricted calling number is 130.
The system does not allow the calls meeting the above-mentioned
conditions, but plays special announcement to ask them to defer the call. After subscribers of recorded announcement category
select a tone, the background fills the corresponding TONEID into
this field. When a call is restricted due to the special recorded announcement, the RC_CODEBLOCK_ANN failure code is returned.
The service uses returned TONEID to play tone while judging this
failure code.
Call Gapping
Control
It is responsible for specifying the maximum attempts of a call

from specified incoming trunk group routing to specific destination code in a certain period of time. This control ensures that the
number of call attempts that are routed will never exceed the specified number. It is available to specify the subscriber category, and
to adjust the restriction number with consecutive numbers. The
RC_CODEBLOCK_INT failure code is returned when a failure occurs.
The call gapping control is configured on the command terminal, and implemented by executing the ADD DSTNUMCTRL command. The parameters involved are as follows:
Maximum attempts that are allowed to select a route
Interval.
For example, the call gapping control is implemented on the call

from trunk group 1 of local incoming trunk module 2. The conditions are as follows.
The restricted destination code is 0208888.
The restricted calling number is 130.
There are up to 20 attempts allowed within five minutes.
The call meeting the above-mentioned conditions is not allowed to

select a route when its attempts have exceeded 20 times until the
next interval.
Outgoing Trunk Group Control

Overview
Direct Route
Traffic Control
The outgoing trunk group control falls into the following six modes.
Direct route traffic control
Circuit orientation
Circuit (trunk) turndown/busy/blocked
Alternative route traffic control
Trunk reservation
Skipping.
It is responsible for controlling the direct route traffic of incoming

call from specified incoming trunk group and through control outgoing trunk group on a percentage basis. It is available to specify
the subscriber category, and to adjust the restriction number with
consecutive numbers. There are two kinds of control modes.
Restricting the input of direct route traffic (RSTRIN)

Restrict the direct route traffic into the controlled trunk group
on a percentage basis.
Restricting the direct route traffic overflow (RSTROF)

Restrict the direct route traffic overflow from the controlled
trunk group on a percentage basis.
The direct route traffic control can be configured on the command

terminal, and implemented by executing the ADD TGCTL command. The parameters involved are as follows.
Restricted outgoing trunk group number
Control type (RSTRIN or RSTROF)
For example, restrict the traffic on the direct route from trunk
group 1 of incoming trunk module 2 to trunk group 2 of outgoing trunk module 3. Conditions are as follows:
The restricted calling category is priority subscriber.
The restriction percentage is 75%.
If the RSTRIN is adopted for a call from priority subscriber, then 25

of 100 calls take the direct route to trunk group 2 of trunk module
3, and other 75 calls take other route.
If the RSTROF is adopted for this call, it takes the direct route
without overflowing to trunk group 2 of trunk module 3; if the
route overflows, then 75 of 100 calls take the direct route to trunk
group 2 of trunk module 3 to restrict the overflow (This call may fail
because the overflow has already occurred), and the other 25 calls
take other routes to continue searching outgoing CIC according to
existing flow. If there is no other route available, the call fails.
Because the restricted calling category is priority subscriber, the
call from ordinary subscriber will not be restricted.
The RC_TRKBLOCK_DIR failure code is returned when a failure
occurs.
Circuit Orientation
It is responsible for converting the dual-running circuit (trunk) to

incoming-running circuit (trunk), and controlling the circuit on a
percentage basis. The orientation percentage can be adjusted with
consecutive numbers. The RC_TRKBLOCK_OGB failure code is
returned when a failure occurs.
Execute the ADD TGCTL command on the command terminal to
implement the circuit orientation. The parameters involved are as
follows.
For example, implement circuit orientation control on the local

dual-directional trunk group 1 of trunk module 2. Conditions are
as follows:
Then, 75 percent of the circuits on this trunk group are orientated

to incoming calls only, not to outgoing calls.
This command does not restrict incoming calls.
Circuit (Trunk)
Turndown/
Busy/Blocked
It is responsible for temporarily turning down single and/or dual

running circuit (trunk) to control the circuit on a percentage basis.
The specified percentage can be adjusted with consecutive num-
bers. The RC_TRKBLOCK_HLT failure code is returned when a

failure occurs.
To execute the ADD TGCTL command on the command terminal,
the parameters involved are as follows.
For example, implement circuit (trunk) turndown/busy/blocked

control on the local dual-directional trunk group 1 of trunk module
2. Conditions are as follows.
Then, 75% of circuits on this trunk group are blocked up temporarily.

Alternative Route
Traffic Control
It is responsible for controlling the alternative route traffic of calls

from specified incoming trunk group and through controlled outgoing trunk group on a percentage basis. It is available to specify
the subscriber category, and to adjust the restriction number with
consecutive numbers. The RC_TRKBLOCK_CAN failure code is
returned when a failure occurs. There are two control modes.
Restricting the input of alternative route traffic (RSTRIN)

Restrict the alternative route traffic into the controlled trunk
group on a percentage basis.
Restricting the alternative route traffic overflow (RSTROF)

Restrict the alternative route traffic overflow from the controlled trunk group on a percentage basis.
To execute the ADD TGCTL command on the command terminal

to implement the alternative route traffic control, the parameters
involved are as follows.
Control type (RSTRIN or RSTROF)
For example, to restrict the traffic on alternative route from trunkgroup 1 of incoming-trunk-module 2 to trunk-group 2 of outgoingtrunk-module 3, conditions are as follows.
The restricted calling category is priority subscriber.
The prerequisite for this command is that the direct route has overflowed to the alternative route of trunk group 2 of module 3. If
the RSTRIN is adopted for a call from priority subscriber, then 25
of 100 calls take the alternative route to trunk group 2 of trunk
10
module 3, the other 75 calls take other route. If there is no alternative route available, the call fails.
If the RSTROF is adopted, and the trunk group 2 of trunk module
3 does not overflow, it takes this alternative route. If the trunk
group 2 of trunk module 3 overflows, then 75 of 100 calls take the
alternative route to prevent the traffic from overflowing (This call
may fail because the overflow has already occurred), and the other
25 calls overflow to other routes to continue searching outgoing
CIC according to existing flow. If there is no other alternative route
available, the call fails.
Because the restricted calling category is priority subscriber, the
call from ordinary subscriber will not be restricted.
Trunk Reservation
It is responsible for reserving the trunk circuits for traffic on a

percentage basis or by specified circuit (trunk) number. When the
number of idle circuits in the circuit group is less than or equal
to the specified, the controlled traffic is rejected. It is available
to specify restricted incoming trunk group number and restricted
subscriber category, and to adjust the specified percentage with
consecutive numbers. The RC_TRKBLOCK_RSV failure code is
to implement the trunk reservation, the parameters involved are
as follows.
Controlled percentage
For example, to reserve the trunk for the direct route traffic that
is from trunk group 1 of incoming trunk module 2 and is to trunk
group 2 of outgoing trunk module 3, the conditions are as follows.
When the number of idle circuits of the direct-route circuit group

is less than or equal to 70%, the traffic from ordinary subscribers
is rejected, but that from priority subscribers is allowed.
Skipping
It is to let the traffic routing to skip the controlled trunk group on

a percentage basis and advance to the next trunk group in the
normal routing selection order. The controlled traffic can be the
direct route traffic and/or alternative route traffic. It is available to
specify the restricted incoming trunk group number and restricted
subscriber category. The restriction number can be adjusted with
consecutive numbers. The RC_TRKBLOCK_OVR failure code is
for skipping, the parameters involved are as follows.
11
Controlled types, including direct route traffic, alternative route

traffic, and direct/alternative route traffic
For example, to implement skipping for the traffic on the direct

route between trunk group 1 of incoming trunk module 2 and trunk
group 2 of outgoing trunk module 3, conditions are as follows.
Then, 75% of the traffic advances to the next trunk group in the
normal routing selection sequence.
Configuraitons on MML
Termainal
Creating Traffic Control on
Destination Code
Prerequisites
Before the operation, it is required to confirm:
The MML Terminal window is opened.
The data configuration of MSCS exchange is complete.
Context
Perform this procedure to implement call control on specific destination code according to predefined conditions.
Steps
1. If no exchange is specified, execute command SET on the MML

Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 30 from the
system tree.
SET:NEID=30;
2. Create traffic control on destination code, the command is ADD
DSTNUMCTL.
Table 1 describes the chief parameters in the ADD DSTNUM
CTL command.
12
TABLE 1 PARAMETER DESCRIPTION

COMMAND
Parameter
Name
NAME
ID
Parameter
scription
OF THE
De-
ADD DSTNUMCTL
Instructions
Alias
It is used to describe a
destination-code traffic
control for identification.
The maximum length is 50
bytes.
Serial number
It is used to identify
the serial number of a
destination-code traffic
control for quick search.
The maximum value is
65535.
It is used to describe the
type of a destination-code
command. The
enumerated values are
as follows:
Type of destination
code command
TYPE
Restricted incoming
trunk group
INTG
DEST (Destination
control)
INTERVAL (Call
gapping control)
TAR (Temporary
alternative routing)
PRMPT (Special
recorded
announcement)

incoming trunk group of
traffic control. This trunk
group must exist in the
trunk group configuration
It is used to describe
the calling type. The
enumerated values are as
follows:
OPCAT
OPN
Restricted calling
category
Restricted calling
number
CMMN (Ordinary
subscribers)
PRIOR (Priority
subscriber)
ALL (All the

subscribers)

calling number section to
which the traffic control is
implemented. A number
section can contain at most
32 numbers.
13
Parameter
Name
De-
Instructions
DPN
Restricted called
number

called number section to
which the traffic control is
implemented. A number
section can contain at most
32 numbers.
Start
Start time

start time of traffic control
End time

end time of traffic control.
If both start time and end
time are 00:00, the traffic
control is implemented
whole day.
END
DSTTYPE
PER
The type
of restricted
destination code
Restriction
percentage
the type of the
destination-code of traffic
control. The enumerated
values are as follows:
LOG (Logic number)
PHY (Physical number)
the percentage of calls
restricted by the traffic
control. If it is valued as
25, 25 of 100 calls will be
restricted, and the rest will
be put through.
According to the value
of Type field, the Percent
field is applied to two
commands, the destination
code control and the
temporary alternative
route.
CTIME
Maximum attempts
allowed to select a
route

attempts allowed to select
a route, which it controlled
by the call gapping, and
is valid when TYPE =
INTERVAL.
INTERVAL
The duration of an
interval (second)

duration of an interval
controlled by the call
gapping. It is valid when
TYPE=INTERVAL.
Temporary
alternative route
the temporary alternative
route used by the traffic
control. The selected route
must exist in the routing
configuration, or it is valid
when TYPE = TAR.
TAR
14
Parameter
scription
Parameter
Name
Parameter
scription
PRMPT
Recorded
announcement
category

recorded announcement
type of the calls controlled
by the traffic control, which
is valid when TYP = PRMPT.
CAUSE
Cause value

cause of the call failure.
PT
De-
Playing tones
Instructions
whether to play tones for
the calls controlled by
the traffic control. The
enumerated values are as
follows:
NO (Not playing tones)
YES (Playing tones)
To add destination-code-type traffic control, the conditions are

as follows.
Restricted incoming trunk group ID: 25
Calling restriction type: restricting all
Restricted calling number section: 133025
Restricted called number section: 130035
Start time: 00:00, End time: 12:00
Restricted number type: logical number
Restricted percentage: 50%
Attempts allowed to select a route: 0
Attempt interval: 0
Temporarily alternative route: Not configured
Recorded announcement type: 0
Cause value: 2
Playing type: Not playing.
The command is as follows.

ADD DSTNUMCTL:NAME="DSTNUMCTRL1",ID=1,TYPE=D
EST,INTG=25,OPCAT=ALL,OPN="133025",DPN="130035
",START="00:00",END="12:00",DSTTYPE=LOG,PER=50,C
TIME=0,INTERVAL=0,TAR="0"-"0"-"0"-"0",PRMPT=0,CA
USE=2,PT=NO;
END OF STEPS
Result
The system can correctly report the call loss, make performance
statistics, or play tone.
15
Postrequisite
Transfer data tables.
Creating Outgoing Trunk Traffic

Control
Prerequisites
Before the operation, it is required to confirm that the MML Terminal window is opened.
Context
Perform this procedure to implement route control on specific trunk

group according to predefined conditions.
Steps

system tree.
SET:NEID=30;
2. Creat outgoing trunk traffic control, the command is ADD
TGCTL.
Table 2 describes the chief parameters in the ADD TGCTL command.
Parameter
Name
NAME
OTG
ID
16
OF THE
ADD TGCTL COMMAND
Parameter Description
Instruction
Alias
a traffic control on
outgoing trunk for
identification. The
maximum length is 50
bytes.
Restricted outgoing
trunk group

outgoing trunk group
on which the traffic
control is implemented.
This trunk group must
exist in the trunk group
configuration
SN
It is used to identify
the serial number of an
outgoing traffic control
for quick search. The
maximum value is
65535.
Parameter
Name
Instruction
the type of an outgoing
trunk group command.
The enumerated values
are as follows:
Command type of
trunk group
TYPE
START
END
PER
INTG
DRTRF (Direct route

traffic control)
CCTDIR (Circuit
orientation
TRKNA (Circuit
(trunk) Turndow
n/Busy/Blocked)
ARRESTRIC
(Alternative route
traffic control
TRKRSV (Trunk
reservation)
SKIP (Skip)
Start time
the start time of traffic
control
End time
the end time of traffic
control. If both start
time and end time are
00:00, the traffic control
is implemented whole
day.
the percentage of calls
restricted by the traffic
control. If it is valued as
25, 25 of 100 calls will
be restricted, and the
rest will be put through.
According to the value
of Type field, the Percent
field is applied to
two commands, the
destination code control
and the temporary
alternative route.
Restricted incoming
trunk group

incoming trunk group
on which the traffic
control is implemented.
This trunk group must
exist in the trunk group
configuration
17
Parameter
Name
Instruction
the calling type. The
as follows:
OPCAT
RTCTL1
Restricted calling
category
Route control mode 1
CMMN (Ordinary
subscribers)
PRIOR (Priority
subscriber)
ALL (All the

subscribers)

routing control mode 1
of the outgoing trunk
traffic control. The
as follows:
RSTRIN (Entry
restricted)
RSTROF (Overflow
restricted)

routing control mode 2
of the outgoing trunk
traffic control. The
as follows:
RTCTL2
OVERDIR (Skipping
over the direct route
traffic)
OVERALT (Skipping
over the alternative
route traffic)
OVERBOTH
(Skipping over
both direct and
alternative route
traffic)
Route control mode 2
Add an outgoing trunk traffic control, with an alias as Trunk

Group:
The type of the trunk group command: DRTRF (0, directrouting traffic restriction)
Start time: 00:00
End time: 00:00
Restriction percentage: 50%
Restricted incoming trunk group: 5
18
The serial number of the trunk group: 2
The category of restricted calling number: CMMN (common

subscriber)
Routing control mode 1: RSTRIN (access restricted)
Routing control mode 2: OVERDIR (skipping over direct

traffic).

ADD
TGCTL:NAME="TGCTL1",OTG=1,ID=2,TYPE=DRTR
F,START="00:00",END="00:00",PER=50,INTG=5,OPCAT
=CMMN,RTCTL1=RSTRIN,RTCTL2=OVERDIR;
END OF STEPS
Result
Postrequisite
The system can correctly report the call loss, make performance
statistics, or play tones. The performance statistics includes one
time switch device congestion in basic traffic statistics, and one
time incoming/outgoing flexible traffic control in the MSCS load
control statistics.
Creating a Number Prefix Object

Prerequisites
Context
Perform this procedure to add a number prefix object, preparing

for dynamic traffic control.
Steps

system tree.
SET:NEID=11;
2. Create a number prefix object. The command is ADD PRECO
DE.
Table 3 describes the main parameters in the ADD PRECODE
command.
Parameter
Name
ID
CODE
OF THE
ADD PRECODE COMMAND
Parameter
Description
Instruction
Number prefix ID
It is an optional parameter,
indicating the serial number
of the number prefix object.
Type an integer ranging from
1 to 4294967295.
Number prefix
It is a mandatory parameter,
indicating the prefix of calling
or called number. Type a
number with a length ranging
from 1 to 31 digits. This
number only contains the
numbers 0-9.
19
Parameter
Name
NAME
Parameter
Description
Instruction
Alias
It is a mandatory parameter,
designating the name of the
number prefix object. It is
a character string, with a
length ranging from 1 to 250
characters.
Create a number prefix object with the following requirements.
ID: 1
Number prefix: 139
Alias: 139.
The specific command is as follows.

ADD PRECODE:ID=1,CODE="139",NAME="139";
END OF STEPS
Result
Postrequisite
The number prefix object 139 is created.

Creating Dynamic Traffic Control

Prerequisites
Context
Perform this procedure to set a traffic control on the client, including setting the destination code on which the traffic control has
to be performed, and parameters of traffic control. All the traffic
destination codes can be controlled on a percentage basis or an
interval.
Steps

system tree.
SET:NEID=11;
2. Create the dynamic traffic control. The command is ADD TRAF
CTRL.
Table 4 describes the main parameters in the ADD TRAFCTRL
command.
20

Parameter
Name
Parameter
scription
OF THE
De-
ADD TRAFCTL COMMAND
Instructions
CODE
Number prefix
It only contains numbers,

and uses the number prefix
configured in the ADD
PRECODE command.
BTM
Traffic control
begin time
It may be later than the Traffic

Control End Time, indicating
that the traffic control crosses
a day boundary. The default
value is 00:00
ETM
Traffic control end

time
The default value is 23:59

You can only select either
one, for these two modes are
mutual exclusive.
CTRLMD
Traffic control
mode, including
two options, PCNT
(percent) and
INTVL (Interval)
If the PCNT (percent) option

is selected, you must type the
Restriction Percent (%)
parameter.
If selecting the INTVL
(Interval) option, you
must type the Control
Interval (min) and
Control Attempted Calls
parameters.
Max attempted
call
It is one of the triggering

conditions for traffic control.
When the number of
attempted calls is greater
than this value, the traffic
control is triggered. The
default value is 0.
MINANSRT
Min answer ratio

(%)
It is one of the triggering

conditions for traffic control.
When the answer ratio is less
than this value, the traffic
control is triggered. The
default value is 0.
PCNT
Restriction
percentage
It is valid when the traffic

control mode is PCNT
(Percent), with a default of
0.
CTRLINTVL
Control interval
(min.)

control mode is INTVL
(Interval), with a default of
5.
ATCL
Controlled
attempted calls

control mode is INTVL
(Interval), with a default of
300.
MAXATCL
21
Parameter
Name
Parameter
scription
De-
CSVL
Cause Value
A cause value, with a default

of 0
PLTN
Play tone, with two

options available,
YES and No
It is an optional and
enumerated parameter,
with a default of No.
Instructions
Add the dynamic traffic control with the following requirements.
Number prefix: 139
Monitoring duration: 1 day
Traffic control mode: PCNT (percent)
Maximum attempted call: 100
Minimum answer ratio (%): 50%
Restriction percent (%): 20%.

ADD TRAFCTRL:CODE="139",BTM=00:00,ETM=23:59,CT
RLMD=PCNT,MAXATCL=100,MINANSRT=50,PCNT=20,CS
VL=0,PLTN=NO;
Add the dynamic traffic control with the following requirements.
Number prefix: 139
Monitoring duration: 1 day
Traffic control mode: INTVL (interval)
Maximum attempted call: 100
Minimum answer ratio (%): 50%
Control interval (min.): 5
Control attempted calls: 50.

ADD TRAFCTRL:CODE="139",BTM=00:00,ETM=23:59,CT
RLMD=INTVL,MAXATCL=100,MINANSRT=50,CTRLINTVL
=5,ATCL=50,CSVL=0,PLTN=NO;
END OF STEPS
Result
Postrequisite
22
The system can correctly reports the call loss, make performance
statistics, or play tone. Where, the performance statistics includes
one time of switch device congestion in basic traffic statistics, and
one time of incoming/outgoing flexible traffic control in MSCS load
control statistics.
Chapter
Load Control Concepts

and Principles
Table of Contents
Load Control Concepts .......................................................23
Service Control Principles ...................................................25
Congestion Control Principles ..............................................27
Load Control Concepts

Concepts
When unexpected traffic abruptness occurs, load control is responsible for discarding partial traffic beyond the system processing
capability so as to avoid the breakdown of modules or even entire
system. By reducing the system load, the system can run safely
and stably to protect the services from interruption.
Category
Based on different load types, the load control function of ZXWN

MSCS are as follows.
Control
Mechanism
Service control (based on service traffic)
Congestion control
Figure 2 shows the control mechanisms of MSCS. Traffic control

(total), traffic control (single), MP congestion control, single service traffic control, and other NE congestion control, these five
control mechanisms are all running on the CMP. The link congestion control mechanism is running on the SMP. Because there is
no service running on the OMP, the OMP is not responsible for load
control.
FIGURE 2 MSCS LOAD CONTROL MECHANISM
23
Service Control
Overview
Service control (based on traffic control) is a process of controlling the service overload condition during the service cycle. It is
attained by setting the traffic allowed to flow in a time unit. By
dividing the systems entire running time into several equivalent
time slices, one time slice is the service cycle.
Service overload means that the number of service processing
units exceeds a fixed threshold in a time unit (or a service cycle). This threshold is calculated synthetically based on fixed traffic model with reference to the capacity configuration of system
office. Service control is mainly used to ensure the system stability of the CN when it suffers the impact from burst and large
capacity service traffic.
Incoming
Service Control
Mechanisms
Traffic control (total)

It specifies the total service traffic that is allowed to pass with a
service cycle (two seconds). You may set this service cycle as
required. This method may ensure the security of MSCS. This
mechanism is not optimized in this version. We just change
the original weight coefficient setting to equivalent CPU consumption.
Traffic control (single)

Due to the total traffic control, services may borrow resources
mutually. To ensure that some burst service will not bring great
influence on other services (for example, burst short messages
may affect call service). You may set the passing times per
second of different services. Passing times of single service
Equivalent CPU consumption of each service Total CPU
resources of total traffic control
Outgoing
Service Control
Mechanism
Single service traffic control

It provides a method to control the times of a single service going to HLR, SMC and SCP to alleviate the impact of burst traffic to
other NE. This mechanism can not only control the times of services going to HLR, SMC and SCP, but also control the times of
services going to a specific target based on the GT configuration.
The purpose of this method is to protect other NEs.
Congestion Control
Overview
Incoming
Congestion
Control
Congestion control includes incoming congestion control and outgoing congestion control.
MP congestion control
When CMP is congested, the system will restrict the accessed
services.
Link congestion control

The incoming link congestion control is to restrict the accessed
services when SMP is congested so as to alleviate the congestion conditions of SMP. It mainly controls the CR messages at
A/Iu interface and the TC_BEGIN_REQ messages at TCAP.
24
Chapter 3 Load Control Concepts and Principles
Outgoing
Congestion
Control
Congestion control of other NEs

When the system finds that other NE is congested, it will control
the services to this NE.
Link congestion control

Outgoing link congestion control is to release the over-load
condition of outgoing associations and links. It contains the
congestion control under the conditions of SMP over-load and
association/link over-load.
Service Control Principles

Service load is the sum of the products of each service processing load and the CPU consumption of corresponding service processing unit under certain office attributes. The service-load-control process adds the total number of the current receiving-service-processing units to the corresponding CPU consumption after
receiving one service (processing unit). When the total number of
processing units received in a time unit is greater than the rated
maximum service load of this module, the message is discarded
to release the system load till the next service load control cycle.
Service Control Concepts

Service Cycle
It is calculated by dividing the systems entire running time into

several equivalent time slices, for example, two seconds.
Service Overload
It means that the number of service processing units exceeds a

fixed threshold in a time unit (or a service cycle). This threshold
is calculated by a fixed traffic model with reference to capacity
configuration of system office.
Service
Processing Unit
CPU Consumption
of Service
Processing Unit
It is the combination of a message and its subsequent message.

It indicates the load cost by this type of service processing unit at
a time, which is determined by the CPU usage of each service.
Service Control Principle

The service-load-control process adds the total number of the current receiving-service-processing units to its corresponding CPU
consumption after receiving one service (processing unit). When
the total number of processing units received within a time unit is
greater than the rated maximum service load of this module, the
message is discarded to release the system load till the next service load control cycle. Specifically, the A/Iu/NNI/MAP interface
invokes the Over Load (OL) interface to control the service overload after receiving a service request message. The first message
that triggers off this service (processing unit) is the control point.
25
Function Implementation
Implementing
1. The OL module obtains the current time. If the difference between the current time and the start time of traffic control cycle
is greater than the value of 60 configuration service cycle,
then all the statistics (total traffic and single traffic) are cleared,
and the current time is regarded as the start time of a traffic
control cycle.
2. Judge whether the total traffic is greater than the value of Total
traffic allowed to flow in a second configured service cycle.
If it is greater, the control on current traffic is necessary. For
the SMS, it needs to check whether the single traffic of MT/MO
SMS is greater than Total traffic allowed to flow in a second
Allowed percentage of MT/MO SMS in the total traffic Configured service cycle.
Classification
of Service
Processing Units
26
The principle of classifying service processing units must be in

the same module, and the service processing units can cover
most of services through combination.
The service processing units are as follows.
Location update
Authentication
MO/MT SMS
Ordinary originating call (2G/3G)
Ordinary terminating call (2G/3G)
GMSC service
CAMEL service
ISUP/TUP incoming/outgoing call
BICC (CMN) incoming/outgoing call
BICC (TSN) incoming/outgoing call
SIP incoming/outgoing call
CAS incoming/outgoing call
PRI incoming/outgoing call
Intra-office handover
Inter-office handover in/out
BSSAP service request
BSSAP circuit request
BSSAP location update
BSSAP handover
BCBM
MCF
USSD
LCS
Congestion Control
Principles
Interface Congestion Control
Congestion Level Mechanism
Overview
If the load control module detects that the CPU usage is too high
during the service processing, it will reduce the allowed throughput
based on an algorithm. On the contrary, if the module detects that
the CPU usage returns to normal, it increases the allowed throughput on an algorithm to maintain the CPU usage finally about the
CPU threshold.
Function
Implementing
CPU load level algorithm, local office load level algorithm, and adjacent office congestion level algorithm (the calculation method for
the parameters required by the congestion control) are as follows.
1. On the Professional Maintenance > Variable Control tab
of the NetNumen M30 window, compare the current CPU occupancy with Threshold of CPU slight overload (%) and
Threshold of CPU severe overload (%). Calculate separately the CPU load level, as shown in Figure 3.
FIGURE 3 CPU LOAD LEVEL
2. The system calculates the CPU load according to the following

method. CPU load divides into two levels, as shown in Figure
4.
FIGURE 4 DIAGRAM
OF
CPU LOAD LEVEL
AND
RESOURCE LOAD LEVEL
27
Control Policy
No control is imposed in the non-overload area. When the services

enter the overload area, it is necessary to enable the load control
mechanism. A service period is two seconds, which is configurable.
When the service throughput within a service period exceeds the
allowed one, the load control is imposed.
Congestion Control on Mc Interface

If the MGW detects the congestion, it will notify the MSCS with a
congestion packet, in which the MGW requires the MSCS to reduce
the delivered messages by a specific percentage.
In the next period, the number of the Add messages delivered
by the MSCS is the number of the Add message delivered in the
previous period multiplied by a certain percentage, until the MGW
releases the congestion.
Congestion Control on NNI Interface

The congestion control is implemented according to the congestion
conditions of the adjacent office when the NNI is requesting an
outgoing route.
The system automatically reduces the times of circuit selections
to this office if the RELEASE message of the ISUP/BICC signaling
carries the automatic congestion level.
Congestion Control on A/Iu Interface

The MSCS records the congestion levels of the RNC and the BSC.
When the congestion occurs, the MSCS enables the congestion
mechanism, and reduces the allowed throughput based on an algorithm. When the MSCS detects that the congestion is released,
it increases the allowed throughput based on an algorithm.
Link Congestion Control

When finding that the congestion occurs in the bottom link
(MTP3/MTP3B/M3UA/SCTP) of adjacent office, the upper-level
service should record the corresponding office's congestion condition, and reduce the services to this office by a certain percentage,
thus to maintain the safe running of the system.
This function is implemented through the calculation of the link
congestion level and the congestion control performed by different
services based on the congestion level and the throughput rate
configuration.
Calcualation on SMP Congestion Level

The CPU usage is an index to assess the SMP congestion.
28
Calculation on Link Congestion Level

Whether the signaling is congested is decided by the variable control configured on the background. This ERL threshold serves as
a control standard for all the links. If a link is configured with the
ERL congestion threshold, the global configuration is not used for
decision.
Whether an association link is congested is decided according to
the occupation rate of the sending buffer.
Link Congestion Control Policy

Link congestion is not controlled in a hierarchical manner. If the
threshold is exceeded, the system considers that the congestion
occurs. The flow control is activated upon the congestion. The flow
control is implemented through self-learning, which is the same
as that of the CMP congestion control. When the threshold is not
exceeded and messages are not discarded, the flow control is terminated.
Adjacent Office Congestion Control

To implement the load control and the Mc interface control
through outgoing messages, it needs to know the congestion
condition of the adjacent office, and to save the congestion levels
of RNC/BSC/MGW adjacent office and MSC adjacent office to the
corresponding database table.
RNC/BSC Adjacent Office Congestion Control

When the congestion occurs on the RNC/BSC, the system adds 1
to the congestion level of the corresponding level when receiving
a RANAP/BSSAP-OVERLOAD message, and activates long timer
and short timers. The system does not process other overload
messages until the short timer times out. When the short timer
times out, the system adds 1 to the overload level when receiving
a RANAP/BSSAP-OVERLOAD message, and restarts two timers.
The highest overload level is 16. When no congestion occurs on the
RNC/BSC, and the long timer does not receive a RANAP/BSSAPOVERLOAD message after timing out, the system subtracts 1 from
the overload level until the level is 0.
MGW Adjacent Office Congestion Control

When the congestion occurs, the MGW reports the congestion rejection rate to the MSCS through the corresponding message. The
MSCS records this congestion rejection rate in the corresponding
database table as MGWs congestion level after dividing the rate
into 10. Due to the requirements of Mc interface control and RTP
29
congestion control, the MGW is capable of two kinds of congestion

reporting mode.
Standard reporting mode

When adopting the standard reporting mode, MSCS records
the MGWs CPU congestion level to the corresponding database
table.
Custom reporting mode

When adopting the custom reporting mode, MSCS records the
CPU or RTP congestion level of MGW to the corresponding database table according to the message packets reported by MGW.
The reporting mode choice depends on the MGW congestion reporting mode configured in the topological node of the server. This
reporting mode configured on the MSCS is sent to the MGW. The
MGW reports the corresponding message to the MSCS when the
congestion occurs.
MGWs congestion level and its corresponding rejection rate are
configured in MGWs gateway overload configuration. The congestion level algorithm of the MGW is similar to that of the MSCS.
MSC Adjacent Office Congestion Control

The MSC adjacent office has two congestion levels, which are carried with the REL message sent by the opposite-end office. Each
congestion level controls the load by an individual percentage (that
is, the threshold %).
When the congestion occurs, the outgoing CIC to the adjacent office is controlled by this percentage. When the NNI searches the
outgoing route outside the office, and finds that the corresponding
adjacent office is congested, it checks the status of the CIC to this
office. If the percentage of CIC circuits to this office is greater than
the control percentage of the corresponding congestion level, this
outgoing service is restricted; otherwise, this service is not controlled.
30
Chapter
Service Control
Configuration
Table of Contents
Service Control Configurations ............................................31
Service Control Configuration Based on Total Traffic ...............31
Service Control Configuration Based on Single Incoming Service .................................................................................36
Service Control Configuration Based on Single Outgoing Service .................................................................................37
Service Control
Configurations
There are the following service control configurations.
Service control configuration based on total traffic
Service control configuration based on single incoming service
Service control configuration based on single outgoing service.
Service Control
Configuration Based on
Total Traffic
Description
The service control based on total service traffic requires setting

the equivalent CPU consumption and maximum passing services
for each service processing unit in the Variables Control. The
equivalent CPU consumption is determined by the module performance, while the maximum number of passing services is determined by the specific traffic model and equivalent CPU consumption.
You may set the number of passing services per second and equivalent CPU consumption of services, including call service, location
31
update, SMS, handover, LCS service, and PRBT service, for calculating the total traffic of passing services. When the system is
running, the load-control module calculates the total traffic of services in the current service cycle (2 seconds, by default), and the
supplementary service traffic and the SMS traffic. When the system receives a new service request, this module will judge whether
the total traffic of equivalent CPU consumption in the current service cycle excesses the specified value. If it does, the system will
reject or discard this message.
Application
Scenarios
The total traffic control enables the system to reduce the system
load by adjusting the total traffic during the running process. When
the system suffers the impact of burst traffic, and the auto congestion control mechanism becomes invalid, it provides an emergency
intervention method to adjust the overall service passing number
to ensure the system security.
Configuration
Examples
The following examples describe the methods of configuring the

total number control of service load. The parameter settings in
these examples are only used as reference.
Suppose the one office's traffic model is as follows.
The calls between the ISUP/TUP and the BICC occupy 60%.
The calls between the ISUP/TUP and ISUP/TUP occupy 40%.
The TUP occupies 20% of the ISUP/TUP.
The MP uses X86-2.
The equivalent CPU consumption is determined by the CPU performance of service processing unit module and the CPU resource
depletion of various services. In this case, each services CPU consumption is as follows.
ISUP/TUP outgoing call service: 2
ISUP/TUP incoming call service: 1
BICC (CMN) outgoing call service: 2
BICC (CMN) incoming call service: 1.
Suppose there is only one CMP, and the switch starts to control the
load when the CPU occupancy is about 80%. By calculation, there
are total 120 ISUP/TUP MO/MT calls and 52 BICC MO/MT calls that
are allowed to pass in a second. According to the equivalent CPU
consumption, the total number is: 1203+523=516.
According to the call model, equivalent CPU consumption, and CPU
performance mentioned above, there are 516 traffic allowed to
pass through the module in a second.
MSCS judges in real time whether the total load of services received and transmitted on the current module overloads. The
switch implements the service load control only when the total
number overloads.
Configuration
Flow
32
The service control configuration method based on total service

traffic is described in Table 5.
Chapter 4 Service Control Configuration
TABLE 5 SERVICE CONTROL CONFIGURATION FLOW BASED

SERVICE TRAFFIC
ON
TOTAL
No.
Operation Purpose
Reference
Configuring service
control cycle
Configuring Service Control Cycle
Setting the equivalent

CPU consumption
Setting the Equivalent CPU

Consumption
Modifying MSC service

capability limit
Modifying MSC Service Capability

Limit
Configuring Service Control Cycle

Prerequisites
Context
Steps
The NetNumen (TM) M30 window is opened.
The exchange configuration is complete.
Perform this procedure to configure the service control cycle.

1. On the NetNumen (TM) M30 window, select Views >
Professional Maintenance > MSCS > Variables Control
> MSC, VLR, GSMC, MSCServer Service Overload Control
to pop up the MSC Service Overload Control tab.
2. On the MSC, VLR, GSMC, MSCServer Service Overload
Control tab, select Period of Service over load(s). Click
on the sub-toolbar to enter the editing status, as shown in
Figure 5. Type the value of the service control cycle. Currently,
the default value is 2.
FIGURE 5 SERVICE CONTROL CYCLE
3. Click the
button on the sub-toolbar to save the modification.
END OF STEPS
33
Setting the Equivalent CPU

Consumption
Prerequisites
The NetNumen (TM) M30 window is opened.
Context
This section introduces how to set the percentage of the equivalent

CPU consumption.
Steps
1. On the NetNumen (TM) M30 window, select Views > Professional Maintenance > MSCS > MSC, VLR, GSMC, MSCServer Service Overload Control to pop up the MSC, VLR,
GSMC, MSCServer Service Overload Control tab.
2. On the MSC, VLR, GSMC, MSCServer Overload Control tab,
on
select Equivalent CPU of ISUP/TUP Incoming. Click
the sub-toolbar to enter the editing status. Type the equivalent
CPU consumption value, as shown in Figure 6. The method of
setting other equivalent CPU consumption values is as same as
that of this step.
FIGURE 6 EQUIVALENT CPU CONSUMPTION CONFIGURATION
VARIABLES CONTROL
IN
Note:
The total incoming traffic is related with the settings of equivalent CPU consumption of each service. But in most cases, you
need not to modify it.
34
3. Click
on the sub-toolbar to save the result.
END OF STEPS
Modifying MSC Service Capability

Limit
Prerequisites
Context
Before operating, please confirm that:
The NetNumen M30 window is opened.
Perform this procedure to enable the restriction on the MSC service

capability.
Note:
The specific configuration value of single service control function
needs to be adjusted depending on actual amount of traffic. Otherwise, the service may be rejected falsely due to the controlled
traffic of single service is set too low.
Steps

system tree.
SET:NEID=11;
2. Modify the MSC service capability limit. The command is ADD
MSCSRVLMT.
Table 6 describes the chief parameters in the ADD MSCSRV
LMT command.
TABLE 6 PARAMETERS
IN THE
ADD MSCSRVLMT COMMAND
Parameters
Name
Parameters
Description
Instructions
CALLNUM
Calls per second
Calls per second
LUNUM
Times of location
updates per
second
Times of location updates per

second
SMSNUM
Short messages
per second
Short messages per second
HONUM
Times of
handover per
second
Times of handover per second
35
Parameters
Name
Parameters
Description
Instructions
USSDNUM
USSD Times Per

Second
Times of USSD per second
LCSNUM
Times of LCS per

second
Times of LCS per second
PBRTNUM
Times of PBRT
per second
Times of PBRT per second
ALLSRVNUM
Amount of
passed traffic
per second
Amount of passed traffic per

second
DSMSNUM
Times of
delivering short
messages per
second
Specifies the tTimes of

delivering short messages
per second, ranging from
0 to 65535. The default is
65535, without being limited
by LICENSE
For example, modify the calls per second restriction to be 2000.

The specific command is as follow.
SET MSCSRVLMT:CALLNUM=2000;
END OF STEPS
Service Control
Single Incoming Service
Description
You may restrict the times of single incoming service under the
following conditions.
Call service
Location update
SMS
Handover service
USSD service
LCS mobile originated call
PRBT service.
Due to the total traffic control, services may borrow resources mutually. To ensure that some burst service will not bring great influence on other services (for example, burst short messages may
affect call service). You may set the times of different passed services per second. The formula is: Times of single passed service
36
Equivalent CPU consumption of each service Total CPU resources

of total traffic control.
Note:
The value of single incoming service is controled by license. Configure it according to license configuration.
Application
Scenarios
The system may implement traffic control on incoming call service, location update, SMS, handover service, LCS service, and
PRBT service, which is to configure the times of these passed services per second. This function is only enabled when you need to
restrict the traffic amount of some services for definite requirements. For example, limit the short message traffic to N pieces/s
to ensure the call service is stable on an important holiday. Limit
the location update requests to N pieces/s to let the subscriber update location progressively, thus to prevent the system from the
impact of the location update upon restart. Limit the services to
HLR to N pieces/s to prevent HLR from the impact of the services
to it. The specific value of N is configured according to the actual
requirements.
Notice that the N pieces/s mentioned above refers to the number of
service passing a single module. For 2G BSC and inter-office services, if the circuits are not evenly configured on the CMP, the total
number of passed location updates, calls and handover is related
to the number of modules configured to the terrestrial circuits.
And the total number of passed inter-office services is related to
the number of CMPs configured to the inter-office circuits.
Configuration
Flow
The single service control configuration method based on incoming

traffic is listed in Table 7.
TABLE 7 SINGLE SERVICE CONTROL CONFIGURATION FLOW BASED
INCOMING TRAFFIC
ON
No.
Operation Purpose
Reference
Setting the number of single

passed services per second
of each module
Modifying MSC Service

Capability Limit
Service Control
Single Outgoing Service
Description
You may set the outgoing service control under the following four
conditions.
The services to the HLR
The services to the Short Message Center (SMC)
The services to the SCP
37
The location update service to the HLR
Due to the total traffic control, services may borrow resources mutually. To ensure that some burst service will not bring great influence on other services (for example, burst short messages may
affect call service). You may set the passing times per second of
different services. The formula is:
Passing times of single service Equivalent CPU consumption of
each service Total CPU resources of total traffic control
Application
Scenarios
Configuration
Principles
The system may implement traffic control on these four kinds of

outgoing services, which is to configure the passing times of these
services in a second. This function is only enabled when you need
to restrict some services traffic for definite requirements.
1. In general, the default configuration is adopted.
2. To let the number of single services going to all HLRs, SCs or
SCPs not be greater than N, restrict the number of this single
services sent by this module to all offices, and then adjust the
passing number of this service per second as: N/The number
of VLR CMPs of local office. Keep the default passing number
of other single services.
3. To let the number of single services going to some HLR, SC or
SCP not be greater than N, set the passing number separately
according to different GTs. And adjust the passing number
of this service per second as: N/The number of VLR CMPs of
local office. Keep the default passing number of other single
services.
4. If the handling capacity of some HLR/SC/SCP is limited, or the
links to some HLR/SC/SCP is limited, set the passing number
of single services separately according to different GTs. Then,
calculate the tolerable traffic N to this GT according to the service traffic. Finally, adjust the passing number of this service
per second as: N/The number of VLR CMPs of local office.
Configuration
Flow
The procedure for configuring the outgoing single service control

is described in Table 8.
TABLE 8 SINGLE SERVICE CONTROL CONFIGURATION FLOW BASED
OUTGOING TRAFFIC
38
ON
No.
Operation
Purpose
Related Command
Reference
Enabling the
function of
only controlling
location update
service to HLR
Enabling the Function

of only Controlling
Location Update to
HLR
Creating GT
group control
template
ADD GTLOADTM
PLT
Creating GT Group
Control Template
Creating
destination
home GT group
ADD GTGROUP
Creating Destination
Home GT Group
Enabling the Function of only

Controlling Location Update to HLR
Prerequisites
Context
To only control the location update service to the HLR, set the Only
Control Location Update to HLR variable to YES. To control all
the service to HLR, set this parameter to NO. The specific configuration value of single service control function needs to be adjusted
depending on actual amount of traffic. Otherwise, the service may
be rejected falsely due to the controlled traffic of single service is
set too low.
This topic introduces the method of enabling the function of only
controlling the location update service to the HLR in the variables
control.
Steps
1. On the NetNumen M30 window, select Views > Professional Maintenance > MSCS > Variables Control > MSC,
VLR, GSMC, MSCServer Service Overload Control. The
MSC, VLR, GSMC, MSCServer Service Overload Control
tab pops up.
Control tab, select the Only control Location update to
on the sub-toolbar to enter the
HLR variable, and click
editing status. Select the check box labeled YES, as shown in
Figure 7.
FIGURE 7 ENABLING
UPDATE TO HLR
THE
VARIABLE
OF
ONLY CONTROL LOCATION
39
3. Click the
button on the sub-toolbar.
END OF STEPS
Creating GT Group Control Template

Prerequisites
The single service control is enabled.
Whether to control the location update service to the HLR is

configured.
Context
Perform this procedure to configure the GT group control template

for setting the passing number of services by GT numbers.
Steps

system tree.
SET:NEID=11;
2. Create the GT group control template. The command is ADD
GTLOADTMPLT.
Table 9 describes the main parameters in the ADD GTLOADT
MPLT command.
TABLE 9 PARAMETERS
IN THE
ADD GTLOADTMPLT COMMAND
Parameter
Name
Instruction
GTGROUP
Home GT group
ID
Types an integer ranging from

1 to 1,000 according to the
actual conditions.
NUMPERSECHLR
Times of the
service allowed
to HLR per
second

actual conditions.
NUMPERSECSMS
Times of the
service allowed
to the SMC per
second

actual conditions.
NUMPERSECSCP
Times of the
service allowed
to SCP per
second

actual conditions.
Create a GT group control template with the following requirements.
40
GT group ID: 1
Times of the service allowed to HLR per second: 100
Times of the service allowed to the SMC: 100
Times of the service allowed to the SCP: 100.

ADD GTLOADTMPLT:GTGROUP=1,NUMPERSECHLR=10
0,NUMPERSECSMS=100,NUMPERSECSCP=100;
END OF STEPS
Postrequisite
Creating Destination Home GT Group

Prerequisites
Context
Steps
The single service control is enabled.
The GT group control template is configured.
Perform this procedure to configure the home GT group.

system tree.
SET:NEID=11;
2. Create the destination home GT group. The command is ADD
GTGROUP.
Table 10 describes the main parameters in the ADD GTGROUP
command.
TABLE 10 PARAMETERS
IN THE
ADD GTGROUP COMMAND
Parameter
Name
Parameter
Description
Instruction
GT
GT number
Type an integer ranging from 1

to 1,000 according to the actual
conditions.
GTGROUP
Home GT
group ID
Type the group ID configured in the

ADD GTLOADTMPLT command.
To create a destination home GT group, with the GT number

as 86159000 and the GT group ID as 1, the command is as
follows.
41
ADD GTGROUP:GT="86159000",GTGROUP=1;
END OF STEPS
Postrequisite
42
Chapter
Congestion Control
Configuration
Table of Contents
Congestion Control Configurations .......................................43
Configuration Methods for Congestion Control on Each Interface .................................................................................43
Basic Configuration ............................................................44
Configuration for Adjacent Office Congestion Control ..............48
Configuring Performance Statistics of MSCS Load Control .........70
Link Congestion Control......................................................73
Congestion Control
Configurations
There are the following congestion control configurations.
Configuration for CMP congestion control
Configuration for adjacent office congestion control
Configuration for link congestion control.
Configuration Methods for

Congestion Control on Each
Interface
Description
This section introduces the settings on CMP congestion control and

the configuration methods for adjacent office congestion control.
Where, the CMP congestion control configurations provide parameters for each interface in the system proceeding the congestion
control.
Parameter
Description
Generally, congestion control parameters are configured in the default mode.
43
Basic Configuration
Overview
This section describes the methods of configuring corresponding

variable control, providing parameters for the interfaces in the system to perform the congestion control.
Configuration
Flow
The CMP congestion control configuration flow is listed in Table 11.

The variable control configured through steps 1~3 provides parameters for the system to calculate the congestion level.
Configuring subscriber priority ensures that this part of subscribers
can pass preferentially. These subscribers are only controlled in
the high overload area of the CMP.
TABLE 11 CMP CONGESTION CONTROL CONFIGURATION FLOW
No.
Operation Purpose
Reference
Configuring the cycle of MP load

statistics
Configuring the Cycle of

MP Load Statistics
Configuring CMP congestion control

threshold
Configuring CMP
Congestion Control
Threshold
Configuring minimum guaranteed

passing number of each service in
case of CMP congested
Configuring Minimum
Guaranteed Passing
Number of Each
Service In Case of
CMP Congested
Configuring subscriber priorities
Configuring Subscriber
Priorities
Configuring the Cycle of MP Load

Statistics
Prerequisites
The service control cycle is set.
Context
Perform this procedure to set this parameter for the system, thus
to query the CPU occupancy and resource occupancy at this interval.
Steps
1. On the NetNumen M30 window, select Views > Professional Maintenance > MSCS > Variables Control > Overload Control Parameter to enter the Overload Control Parameter tab.
2. On the Overload Control Parameter tab, click Multiple of
MP CPU evaluate interval dividing service overload control interval, and click
on the sub-toolbar to enter the editing status, as shown in Figure 8.
44
Chapter 5 Congestion Control Configuration
FIGURE 8 CONFIGURING
THE
CYCLE
OF
MP LOAD STATISTICS
3. Type a value as required. The default is 3.

4. Click
END OF STEPS
Configuring CMP Congestion Control

Threshold
Prerequisites
Context
Perform this procedure to configure different CPU load thresholds

and CMP congestion control thresholds for calculating system congestion levels. The system calculates the load level of different
interfaces of local office. If this result is inconsistent with the previous one, the system synchronizes the local load condition to all
the CMPs. The OL process on the CMP saves the load condition of
corresponding local interface after receiving the synchronization
message from the OL process on the OMP for the CMP to control
the module load.
For the NNI interface, the CPU load level serves as the only evaluating indicator.
Steps
2. On the Overload Control Parameter tab, click Threshold of
on the sub-toolbar to enter
CPU slight overload, and click
the editing status, as shown in Figure 9.
45
FIGURE 9 CONFIGURING CPU LOAD THRESHOLD
3. Type a value as required. The default is 65. The procedure for

configuring other thresholds is the same as this step.
4. Click
END OF STEPS
Configuring Minimum Guaranteed

Passing Number of Each Service In
Case of CMP Congested
Prerequisites
Context
Perform this procedure to guarantee the lowest passing number of

each service per second when the CMP is congested.
Steps
2. On the Overload Control Parameter tab, click Minimum
guarantee number of SS per second when CMP congest,
on the sub-toolbar to enter the editing status, as
and click
shown in Figure 10.
46
FIGURE 10 CONFIGURING THE MINIMUM ASSURED

OF EACH SERVICE WHEN CMP IS CONGESTED
PASSING NUMBER
3. Type a value as required. The default is 5. The procedure for

configuring other thresholds is the same as this step.
4. Click
END OF STEPS
Configuring Subscriber Priorities

Prerequisites
Context
Steps
Perform this procedure to configure subscriber priorities.

VLR, GSMC, MSCServer Service Overload Control to show
the MSC, VLR, GSMC, MSCServer Service Overload Control tab.
2. On the MSC, VLR, GSMC, MSCServer Overload Control tab,
button on
select Priority of user by category 0. Click the
the sub-toolbar to enter the editing status. Set the subscribers
of this category to Normal User or Preferential User, as
shown in Figure 11. The default value is Normal User. The
method of setting the load control priorities for other subscribers is the same as this step.
47
PRIORITIES
3. Click the
THE
VARIABLES CONTROL
OF
SUBSCRIBER
END OF STEPS
Configuration for Adjacent

Office Congestion Control
The congestion control mechanism for adjacent office is disabled
by default.
The congestion control mechanism for adjacent office covers the
congestion control on the adjacent offices at A/Iu, NNI, and Mc
interfaces.
Load Control on NNI Interface
48
Description
MSCS reduces the times of circuit selections to an adjacent office

if the RELEASE message carries the information of automatic congestion level of this adjacent office that uses ISUP/BICC signaling.
Function
Description
Once congestion occurs on the adjacent office, the local office is

informed immediately by carrying ACL parameter in the REL message. The congestion has two levels, that is, ACL1 and ACL2. Local
office can control its outgoing calls to this adjacent office by traffic
percentage according to the congestion level and configured control thresholds, thus to reduce the traffic to this adjacent office so
as to recover this adjacent office from the congestion.
When an exchange receives the congestion level ACL1 or ACL2
from its adjacent nodes, it starts the congestion control timer T,
and reduces the traffic to the congested node according to the
configuration rules. The percentage of traffic to be reduced can
be configuration as required. Congestion level is decreased if the
congestion indication with the same level is not received in the
duration regulated by the timer. Or, the timer is set again when
the congestion indication with the same level is received. Or, the
congestion level is changed when the congestion indication with a
new level is received.
Configuration
Flow
Automatic outgoing congestion control on adjacent office, as described in Table 12.

TABLE 12 PROCEDURE
NNI INTERFACE
OF
CONFIGURING CONGESTION CONTROL
No.
Purpose
Modifying the
ISUP/BICC-startingACL function for
adjacent office
ON THE
Related
Command
Reference
SET OFCAPP
Modifying the
ISUP/BICC-StartingACL Function for
Adjacent Office
Configuring overload
control threshold for
trunk groups
SET TG
Configuring
Overload Control
Threshold for Trunk
Groups
Configuring thresholds
for automatic
congestion control
SET ACCTHD
Configuring
Thresholds
for Automatic
Congestion Control
Configuring a hold
time for the congestion
level of an adjacent
office
SET MDEFPRE
TMR
Configuring a
Hold Time for the
Congestion Level of
An Adjacent Office
Table 13 lists the procedure of configuring incoming congestion

control on an adjacent office.
Steps 1 and 2 in Table 13 are to configure the REL message (carrying congestion level) sent to the adjacent office and the congestion
level in case of local office congestion.
49
TABLE 13 PROCEDURE OF
ON THE NNI INTERFACE
CONFIGURING INCOMING CONGESTION CONTROL
No.
Purpose
Related
Command
Reference
Configuring whether
to send a REJECT
message in case of
service overload
Configuring Whether
to Send a REJECT
Message in Case of
Service Overload
Configuring Variable
Control
Control
Configuring call level

for incoming call
subscribers (incoming
office)
SET OFCAPP
Configuring Call
Level of Incoming
Call Subscribers
(Incoming Office)
Configuring call level

for incoming call
subscribers (number
analysis)
ADD TPDNAL
Configuring Call
Level of Incoming
Call Subscribers
(Number Analysis)
Note:
Allowed traffic of different services is obtained through self-learning mechanism. This control is implemented by the following
methods.
Different service types: All service types are controlled simultaneously in overload status, except location update, which is
only controlled in the high overload area of CMP.
Different subscriber levels: The services of preferential subscribers are only controlled in the high overload area of CMP.
Different call types: High-level call services are only controlled

in the high overload area of CMP.
Modifying the ISUP/BICC-Starting-ACL Function

for Adjacent Office
Prerequisites
Context
Steps
Modify the ISUP/BICC-starting-ACL function for adjacent office.

system tree.
SET:NEID=11;
50
2. Modify the adjacent office configuration to tell ISUP/BICC to

start ACL. The command is SET OFCAPP.
For the parameter descriptions of the SET OFCAPP command,
refer to Table 14.
TABLE 14 PARAMETERS
IN THE
SET ADJOFC COMMAND
Parameter
Name
Parameter
Description
Instructions
OFCID
Adjacent office ID
Identifier of an adjacent
office, ranging from 1 to
3,000
ISUP/BICCstartingACL function, including

two options:
LEVFLAG
NO: Not start ACL

function
YES: Start ACL

function
Select YES.
For example, modify the configuration of adjacent office 1 to

tell ISUP/BICC to start ACL. The command is as follows.
SET OFCAPP:OFCID=1,LEVFLAG=YES;
END OF STEPS
Postrequisite
Configuring Overload Control Threshold for Trunk

Groups
Prerequisites
Context
After ISUP/BICC enables the ACL function and MSCS receives a

REL message carrying congestion level from an adjacent office,
the system will control the ISUP/BICC traffic to this adjacent office
in the period of being congested.
This control includes traffic percentage and idle circuit percentage
control. These two percentages are determined by two configuration items, overload control threshold on outgoing trunk groups
and automatic congestion control threshold.
For example, the overload control threshold on an trunk group is
set to 100, the threshold of automatic congestion control level 1 is
set to 80, and the threshold of automatic congestion control level
2 is set to 60. When the adjacent office is in congestion-level-1
status, 80% ISUP/BICC traffic are allowed to pass this adjacent
office (100%80%) , and up to 80% (100%80%) circuits to the
trunk group of this adjacent office can be seized.
51
This part introduces the method of configuring the overload control threshold of trunk groups. For the method of configuring automatic congestion control threshold, refer to Configuring Thresholds for Automatic Congestion Control.
Steps

system tree.
SET:NEID=11;
2. Configure the overload control threshold for trunk groups. The
command is SET TG.
For the parameters in the SET TG command, refer to Table 15.
TABLE 15 PARAMETERS
Parameter
Name
TG
THD
IN THE
SET TG COMMAND
Parameter
Description
Instructions
Trunk group
number
The number of the trunk

group to be modified. In
this case, only ISUP or
BICC trunk group can be
selected. It ranges from 1
to 4,000.
Overload control
threshold
This configuration value

is effective when the
congestion level is reached
and overload control is
required. Overload control
and automatic congestion
control thresholds both
affect the ACL function.
When ACL function is not
enabled, this threshold
is used to control the
percentage of the circuits
that can be occupied on this
trunk group. Generally, the
default 100 is adopted.
For example, set the overload control threshold of trunk group

1 to 100, the command is:
SET TG:TG=1,THD=100;
END OF STEPS
Configuring Thresholds for Automatic Congestion

Control
Prerequisites
52
Context
After ISUP/BICC enables the ACL function and MSCS receives a

REL message carrying congestion level from an adjacent office,
the system will control the ISUP/BICC traffic to this adjacent office
in the period of being congested.
This control includes traffic percentage and idle circuit percentage
control. These two percentages are determined by two configuration items, one is overload control threshold on outgoing trunk
groups, and the other is automatic congestion control threshold.
For example, the overload control threshold on an trunk group is
set to 100, the threshold of automatic congestion control level 1 is
set to 80, and the threshold of automatic congestion control level
2 is set to 60. When the adjacent office is in congestion level1
status, 80% ISUP/BICC traffic are allowed to pass this adjacent
office (100%80%), and up to 80% (100%80%) circuits to the
trunk group of this adjacent office can be seized.
This section introduces the method of configuring the threshold for
automatic congestion control. For the method of configuring the
overload control thresholds for outgoing trunk group, refer to the
topic Configuring Overload Control Threshold for Trunk Groups.
Steps

system tree.
SET:NEID=11;
2. Configure the threshold for automatic congestion control. The
command is SET ACCTHD.
Table 16 describes parameter descriptions in the SET ACCTHD
command.
TABLE 16 PARAMETERS
Parameter
Name
LVL
THD
NAME
IN THE
SET ACCTHD COMMAND
Parameter
Description
Instructions
Congestion Level
Congestion level. The lowest

level is 1 and the highest
level is 2. The data type of
this parameter is integer.
Threshold (%)
The threshold for automatic

congestion control of a
congestion level. The
minimum is 1 and the
maximum is 100. The data
type of this parameter is
integer.
Alias
It is a character string, used

to describe a threshold for
automatic congestion control
for easy identification. Its
maximum length is 50 bytes.
53
For example, configure the threshold for automatic congestion

control, with the threshold of level 1 as 80%. The command
is:
SET ACCTHD:LVL="1",THD=80,NAME="LVL1";
For example, configure the threshold for automatic congestion
control, with the threshold of level 2 as 60%. The command
is:
SET ACCTHD:LVL="2",THD=60,NAME="LVL2";
END OF STEPS
Postrequisite
Configuring a Hold Time for the Congestion Level

of An Adjacent Office
Prerequisites
Context
Timer 12032 is used to ensure the hold time of a congestion level.

After a REL message containing congestion level is received, this
timer starts. The congestion level of an adjacent office automatically decreases after this timer times out.
This topic introduces the method of configuring the hold time for
the congestion level of an adjacent office.
Steps

system tree.
SET:NEID=11;
2. Configure the hold time for the congestion level of an adjacent
office. The command is SET MDEFPRETMR.
Table 17 describes the parameter descriptions in the SET
MDEFPRETMR command.
TABLE 17 PARAMETERS
Parameter
Name
IN THE
SET MDEFPRETMR COMMAND
Parameter
Description
Instructions
Module types,
including:
MT_3G_SYSTEM: All modules except RPU
MT_3G_RPU:
RPU module
MODTYPE
54
In this case, select

MT_3G_SYSTEM.
Parameter
Name
Parameter
Description
Instructions
TIMER
Macro value of the

timer
The macro value of this

timer. In this case, type
12032.
NAME
Timer Name
The name of the

timer. It is an
optional character-type
parameter, with a length
from 0 to 31 characters.
Timer name can only
be composed of letters,
numbers, underlines or
spaces.
CURINTERVAL
Current timing
length (ms)
The default timing length

of timer 12032 is 5000
ms.
For example, configure the hold time of the congestion level

of an adjacent office. The module type is MT_3G_SYSTEM.
The macro value of the timer is 12032. The timer name is
isupAutoCgstCtrl. The current timing length of the timer is
5000 ms. The command is as follows.
SET MDEFPRETMR:MODTYPE=MT_3G_SYSTEM,TIMER=12
032,NAME="isupAutoCgstCtrl",CURINTERVAL=5000;
END OF STEPS
Configuring Whether to Send a REJECT Message

in Case of Service Overload
Prerequisites
Context
This topic introduces the method of configuring whether to send a

REJECT message in case of service overload.
Steps
VLR, GSMC, MSCServer Service Overload Control. The
MSC, VLR, GSMC, MSCServer Service Overload Control
tab pops up.
Control tab, select the Whether to send Reject Message
When Reject Message Because MSC Service Overload
on the sub-toolbar to enter the editing
variable, and click
status. Select the check box labeled YES, as shown in Figure
12.
55
FIGURE 12 CONFIGURING VARIABLE CONTROL
3. Click the
END OF STEPS
Configuring Variable Control

Prerequisites
Context
When the local office is overloaded and rejects incoming calls, it

sends a REL message carrying the congestion level that is related
to the following variable control configuration.
Weighting coefficient of the most congested module
Lower limit of CPU low overload
Lower limit of CPU high overload
Size of CPU congestion buffer
"Lower limit of CPU low overload", "lower limit of CPU high overload", and "size of CPU congestion buffer" are used to determine
the current congestion level. "Weighting coefficient of the most
congested module" and module congestion level are both used for
calculating the congestion level of local office. The congestion level
carried by the REL message is the congestion level of this office.
Generally, use the default value.
This topic introduces the method of configuring the above-mentioned variables.
Steps
1. On the OMM client, select Views > Professional Maintenance > MSCS > Variables Control > Overload Control
Parameter. The Overload Control Parameter tab pops up.
2. On the Overload Control Parameter tab, select the Max
Congest Module Weighted Ratio variable. Click
on the
56
sub-toolbar to enter the editing status. Type a value. Usually,

use the default value. The configuration of other variables is
similar to this, as shown in Figure 13.
FIGURE 13 CONFIGURING VARIABLE CONTROL
3. Click the
END OF STEPS

Subscribers (Incoming Office)
Prerequisites
Context
Perform this procedure to configure the call level of subscribers,

thus to control the incoming services.
Steps

system tree.
SET:NEID=11;
2. Configure the priorities of the incoming office on the adjacent
office. The command is SET OFCAPP.
57
Table 18 shows the parameters in the SET OFCAPP command.

TABLE 18 PARAMETERS
IN THE
SET OFCAPP COMMAND
Parameter Name
Parameter
Description
Instructions
OFCID
Adjacent office ID
Identifier of an
adjacent office,
ranging from 1 to
3,000
Office service
level, including the
following options:
OFCSERVLVL
INVALID: Invalid
L1: Level 1
L2: Level 2
L3: Level 3
L4: Level 4
If this parameter
is not INVALID, the
office service default
level is the value set
here, and the service
level is modified
automatically
according to the
AutoCgstLevel in the
REL message sent
by the peer end.
For example, set the office service level of adjacent office 1 to

level 1. The command is as follows.
SET OFCAPP:OFCID=1,OFCSERVLVL=L1;
END OF STEPS
Postrequisite

Subscribers (Number Analysis)
Prerequisites
Context
Perform this procedure to configure the call level of subscribers,

thus to control the incoming services.
Steps

system tree.
SET:NEID=11;
2. Configure the priorities of each call type in the number analysis.
The command is ADD TPDNAL.
Table 19 describess the parameters in the ADD TPDNAL command.
58
TABLE 19 PARAMETERS
Parameter Name
ENTR
DIGIT
IN THE
ADD TPDNAL COMMAND
Parameter
Description
Instructions
Number analyzer
entry
It is a mandatory
parameter, which
is an integer,
ranging from 1
to 1000. Select
the corresponding
analyzer entry
of the analyzed
number prefix. For
local calls, select
the corresponding
analyzer entry of
the local number
analyzer
Analyzer number
It is a mandatory
parameter,
consisting of 1~20
digits. Input the
prefix of the called
number, whose
length must make
it be distinguished
in the local office.
For intra-office calls,
it is required to
configure both the
prefix of the called
number and that
of the local-office
roaming number
Call type priority,

including:
INVALID: The call
priority is invalid.
HIGHEST: The call
has the highest
priority.
CALLSERVPRILVL
HIGHER: The call

has a priority one
level lower than the
highest priority.
NORMAL: The call
has a priority one
level lower than the
higher priority.
LOW: The call has
the lowest priority
It is used to specify
the call priority.
The system adopts
INVALID by default.
The call priority has
two functions. In
one case, in the
softswitch office in
the toll softswitch
network, the voice
coding format can be
dynamically selected
according to the
call priority and
the load on the IP
bearer network. In
another case, based
on the combined
information of office
ID and priority
configured in the
number analysis
configuration, the
final priority of a call
is got to perform
load control
59
For example, set 075526770000 to the highest priority. The

command is as follows.
ADD TPDNAL:ENTR=1,DIGIT="075526770000",SPECRST
=0,SPECIDX=0,CAT=LOL,RST1=1,RST2=0,RST3=0,CHA
INAL=0,RNLEN=0,MINLEN=3,MAXLEN=20,OVLYPRI=N
O,REL=NO,NET=1,NAT=DEF,OPDDICONT=NO,TPDDICON
T=NO,OPDDI=0,TPDDI=0,OPDLYDDI=0,TPDLYDDI=0,D
DIOVERB=0,IWVIDEO=LSUP,TIMELMT=0,AUXDAS=0,A
6=0,PFXLEN=0,INSRV=INM,FAXIDX=0,AVIDX=0,DVIDX
=0,ADATAIDX=0,DDATAIDX=0,DDCPLAY=NONE,VAD=I
NVALID,CALLSERVPRILVL=HIGHEST,RERTS=0,INCHAIN
=NO,BICT=NO,ICT=0,ICTT=10,GNM=NORMAL,STBILL=IN
VALID,HOPDAS=0,MCA=NO,IVVR=NO,WANTL=0,IMSCEN
TR=NO;
END OF STEPS
Postrequisite
Congestion Control on Mc Interface

Overview
The congestion control on Mc interface includes configuring the

reporting capability on MSCS, the CPU congestion level on MGW,
and the RTP congestion level.
Configuration
Flow
The congestion control configuration flow of the Mc interface is

described in Table 20.
TABLE 20 CONGESTION CONTROL CONFIGURATION FLOW
INTERFACE
OF THE
MC
No.
Operation
Purpose
Related
Command
Reference
Configuring
adjacent office
congestion control
on Mc interface
Configuring
Adjacent Office
Congestion Control
on Mc Interface
Configuring
congestion
reporting capability
SET TOPO
Configuring
Congestion
Reporting
Capability
Configuring
gateway overload
ADD MGWOL
Configuring
Gateway Overload
Configuring MGW
RTP congestion
control
Configuring MGW
RTP Congestion
Control
Configuring Adjacent Office Congestion Control

on Mc Interface
Prerequisites
60
Context
Perform this procedure to enable the adjacent office congestion

control function on Mc Interface.
Steps
2. On the Overload Control Parameter tab, select Whether
to control downlink message according to the congest
level of RNC/BSC/MGW. Click
the editing status. Check the Yes check box to enable this
function, as shown in Figure 14.
ON MC INTERFACE
3. Click
THE
ADJACENT OFFICE CONGESTION CONTROL
on the toolbar to save the result.
END OF STEPS
Configuring Congestion Reporting Capability

Prerequisites
Context
Perform this procedure to configure the MGW congestion reporting

capability on MSCS. The reporting capability includes the standard
reporting capability and custom reporting capability. The former
one can only control the CPU congestion, while the latter one can
control both the CPU congestion control and RTP congestion control.
Steps

61

system tree.
SET:NEID=11;
2. Configuring congestion reporting capability, the command is
SET TOPO.
Table 21 describes the parameter descriptions in the SET
TOPO command.
TABLE 21 PARAMETERS
IN THE
SET TOPO COMMAND
Parameter
Name
Parameter
tion
ID
Topology Node ID
Descrip-
MGW congestion
reporting capability,
including the following
options:
MGWCON
SMGWCON:
Standard MGW
congestion event
CMGWCON: Custom
MGW congestion
event
Instruction
Select the MGW TOPO
node ID to be configured
When the standard
congestion capability
is adopted, the MSC
records the CPU
congestion level of
the MGW. When the
custom congestion
capability is adopted,
the MSC records the
CPU congestion level
and RTP congestion
level of the MGW.
For example, set MGW congestion reporting capability to standard MGW congestion event. The MGW topo ID is 101. The
command is as follows.
SET TOPO:ID=101,MGWCON=SMGWCON;
END OF STEPS
Postrequisite
Configuring Gateway Overload

Prerequisites
The No. of the exchange to be configured is known.
The MGW congestion report capability is configured on the MSC

Server.
Context
Perform this procedure to define the threshold of each congestion

level of MGW.
Steps

Example: Select the MGW exchange with ID as 31 from the
system tree.
SET:NEID=31;
62
2. Configure the gateway overload.

MGWOL.
The command is ADD
Table 22 describes the main parameters of the ADD MGWOL

command.
TABLE 22 PARAMETERS
Parameter
Name
IN THE
ADD MGWOL COMMAND
Parameter
Description
Instructions
CPUOL1
Inferior limit of CPU

usage triggering
level-1 congestion
It is an optional
parameter, ranging
from 0 to 100. The
inferior limit of level-1
CPU congestion should
be less than or equal
to that of level-2 CPU
congestion.
CPUOL2
Inferior limit
of CPU usage
triggering level-2
CPU congestion
It is an optional
parameter, ranging from
0 to 100. The inferior
limit of level-2 CPU
congestion should be
less than or equal to that
of level-3 congestion.
Inferior limit
of CPU usage
triggering level-3
CPU congestion
It is an optional
parameter, ranging
from 0 to 100. The
congestion.
CPUOL4
Inferior limit
of CPU usage
triggering level-4
CPU congestion
It is an optional
parameter, ranging
from 0 to 100. The
congestion.
CPUOL5
Inferior limit
of CPU usage
triggering level-5
CPU congestion
It is an optional
parameter, ranging
from 0 to 100.
Inferior limit of
memory usage
triggering level-1
memory congestion
It is an optional
limit of level-1 memory
less than or equal to
that of level-2 memory
congestion.
CPUOL3
MEMOL1
63
Parameter
Name
Parameter
Description
Instructions
Inferior limit of
memory usage
triggering level-2
memory congestion
It is an optional
of the level-3 memory
congestion.
Inferior limit of
memory usage
triggering level-3
memory congestion
It is an optional
of level-4 congestion.
MEMOL4
Inferior limit of
memory usage
triggering level-4
memory congestion
It is an optional
of the level-5 memory
congestion.
MEMOL5
Inferior limit of
memory usage
when level-5
congestion occurs
It is an optional
parameter, ranging
from 0 to 100.
REJOL1
Ratio of calls being

rejected when
level-1 module
congestion occurs
It is an optional
parameter, ranging
from 0 to 100.
REJOL2

rejected when
level-2 module
congestion occurs
It is an optional
parameter, ranging
from 0 to 100.
REJOL3

rejected when
level-3 module
congestion occurs
It is an optional
parameter, ranging
from 0 to 100.
REJOL4

rejected when
level-4 module
congestion occurs
It is an optional
parameter, ranging
from 0 to 100.
RTPOL1
Inferior limit of
usage when level1
RTP congestion
occur
It is an optional
parameter, ranging
from 0 to 100.
RTPOL2
Inferior limit of
usage when level-2
RTP congestion
occurs
It is an optional
parameter, ranging
from 0 to 100.
MEMOL2
MEMOL3
64
Parameter
Name
Parameter
Description
Instructions
RTPOL3
Inferior limit of
usage when level-3
RTP congestion
occurs
It is an optional
parameter, ranging
from 0 to 100.
RTPOL4
Inferior limit of
usage when level-4
RTP congestion
occurs
It is an optional
parameter, ranging
from 0 to 100.
RTPOL5
Inferior limit of
usage when level-5
RTP congestion
occurs
It is an optional
parameter, ranging
from 0 to 100.
RTPREJOL1
Ratio of calls
being rejected
when level-1 RTP
congestion occurs
It is an optional
parameter, ranging
from 0 to 100.
RTPREJOL2
Ratio of calls
being rejected
when level-2 RTP
congestion occurs
It is an optional
parameter, ranging
from 0 to 100.
RTPREJOL3
Ratio of calls
being rejected
when level-3 RTP
congestion occurs
It is an optional
parameter, ranging
from 0 to 100.
RTPREJOL4
Ratio of calls
being rejected
when level-4 RTP
congestion occurs
It is an optional
parameter, ranging
from 0 to 100.
CALLLMT
Call bared by
gateway actively
It is an optional
parameter, selecting YES
(limit) or NO (limitless).
QUERYTIMER
Duration of query
timer in MGW
It is an optional
parameter, ranging
from 0 to 60,000. Its
unit is ms.
NAME
Alias
It is an optional
parameter, consisting
of 0~50 characters.
TABLE 23 DEFAULT INFERIOR LIMIT
OF
EACH CPU CONGESTION LEVEL
Parameter
Value
CPU congest level 1
75
CPU congest level 2
80
CPU congest level 3
85
65
Parameter
Value
CPU congest level 4
90
CPU congest level 5
95
For example, configure the gateway overload.
The each inferior limit of levels 1~5 CPU congestion is 75,

80, 85, 90 and 95.
The each inferior limit of levels 1~5 memory congestion is
75, 80, 85, 90 and 95.
Each ratio of calls being rejected when levels 1~4 module
congestion occur is 0, 30, 50, and 75.
The each inferior limit of levels 1~5 CPU congestion is 75,
80, 85, 90 and 95.
Each ratio of calls being rejected when levels 1~4 RTP congestion occur is 0, 30, 50, and 75.
The gateway actively bares calls.
The alias is MGWOL1.
The duration of query timer in MGW is 1,000 ms.

ADD MGWOL:CPUOL1=75,CPUOL2=80,CPUOL3=85,CPU
OL4=90,CPUOL5=95,MEMOL1=75,MEMOL2=80,MEMOL3
=85,MEMOL4=90,MEMOL5=95,REJOL1=0,REJOL2=30,R
EJOL3=50,REJOL4=75,RTPOL1=75,RTPOL2=80,RTPOL3
=85,RTPOL4=90,RTPOL5=95,RTPREJOL1=0,RTPREJOL2
=30,RTPREJOL3=50,RTPREJOL4=75,CALLLMT=YES,QUE
RYTIMER=1000,NAME="MGWOL1";
END OF STEPS
Configuring MGW RTP Congestion Control

Prerequisites
The RTP congestion control is enabled, and that the custom

reporting congestion event is adopted on the MSC server.
Context
Perform this procedure to distribute the traffic while applying for

RTP resources.
Steps
2. On the Overload Control Parameter tab, click Diffluent ratio of RTP Bearer at Congestion Level 1 (%), and click
on the sub-toolbar to enter the editing status, as shown in
66
Figure 15. The procedure of configuring the traffic distribution

ratio of other congestion levels is as same as this step.
FIGURE 15 SETTING
CONGESTION
3. Click
THE
TRAFFIC DISTRIBUTION
OF
RTP BEARER
END OF STEPS
Postrequisite
Congestion Control on A/Iu Interface

Procedure of
Congestion
Control on A/Iu
Interface
Configuration
Procedure
The method of calculating the congestion level of the A/Iu interface

is as follows.
1 is added to the congestion level of this office when A/Iu interface receives an OVERLOAD message. At the same time,
the long and short timers are set.
The system ignores it when the A/Iu interface receives an

OVERLOAD message again during the duration of the short
timer.
1 is subtracted from the office congestion level when the A/Iu

interface does not receive an OVERLOAD message during the
duration of the long timer. In addition, the long and short
timers are set again until the office congestion level changes
to 0.
If the A/Iu interface receives an OVERLOAD message during

the duration of the long timer or in case of the long timer timing
out, 1 is added to the office congest level. At the same time,
the long and short timers are set again.
Table 24 describes the procedure of configuring the downlink congestion control on the A/Iu interface.
67
TABLE 24 CONFIGURATION PROCEDURE

CONTROL ON THE A/IU INTERFACE
OF
DOWNLINK CONGESTION
No.
Procedure
Related
Command
Reference
Configuring adjacent
office congestion
control on A/Iu
interface
Configuration on
Adjacent Office
Congestion Control
on A/Iu Interface
Configuring
Predefined Timer
of MP
SET MDEFPR
ETMR
Configuring MP
Predefined Timer
Control
Control
Configuration on Adjacent Office Congestion

Control on A/Iu Interface
Perform this procedure to enable the adjacent office congestion
control function on A/Iu Interface.
For the configuration procedure, refer to Configuring Adjacent Office Congestion Control on Mc Interface.
Configuring MP Predefined Timer

Prerequisites
Context
Perform this procedure to configure the predefined timer of MP, and

to modify relevant long/short timer for the system to calculate the
congestion level of A/Iu interface internally. This timer adopts the
system default value. The default values of long and short timer
of RNC/BSC are 10 seconds and 3 seconds respectively. Generally,
these timers need not to be configured.
Steps

system tree.
SET:NEID=11;
2. Configure the long and short timer in the MP default timers
that is predefined. The command is SET MDEFPRETMR.
Table 25 describes the parameters in the SET MDEFPRETMR
command.
68
TABLE 25 PARAMETERS
Parameter
Name
IN THE
Parameter
scription
SET MDEFPRETMR
De-
COMMAND
Instructions
MODETYPE
Module type
MT_3G_SYSTEM indicates
all modules except the RPU
module, and MT_3G_RPU
indicates the RPU module.
TIMER
Timer macro value
Type the macro value of this

timer.
NAME
Timer Name
Input the name of a timer
CURINTERVAL
Current duration of
a timer
Type the duration (ms) of the

current timer.
Table 26 lists the relationship between the timer and relevant

timer macro value.
TABLE 26 RELATIONSHIP
BETWEEN A
TIMER
AND
ITS MACRO VALUE
Timer Macro Value
Timer
12114
BSSAP Congest Short
12115
BSSAP Congest Long
12138
RANAP CS Congest Ignore
12140
RANAP CS Congest Weaken
For example, modify the current duration of Timer 12114 to

1,200 ms, the command is as follows.
SET MDEFPRETMR: MODTYPE= MT_3G_SYSTEM, TIIMER=
12114, CURIINTERV AL= 1200;
END OF STEPS
Postrequisite
Configuring Variable Control

Prerequisites
Context
Perform this procedure to enable the downlink-message control

function.
Steps
69
2. On the Overload Control Parameter tab, select Whether

to control downlink message according to the congest
level of RNC/BSC/MGW. Click
the editing status. Check the Yes check box to enable this
function. The default value is No.
3. On the Overload Control Parameter tab, configure the passing number of messages over the A/Iu interface when the adjacent office is congested. Select the Minimum guarantee
number of A/Iu Page per second when signal congest
button on the sub-toolbar to enterparameter, and click the
ing the editing status, as shown in Figure 16. Type a value as
required. The method of configuring the Minimum guarantee number of A/Iu CR per second when office congestion parameter is the same as this step.
FIGURE 16 CONFIGURING THE MINIMUM GUARANTEED NUMBER
DOWNLINK MESSAGES PASSING THROUGH A/IU INTERFACE
4. Click
END OF STEPS
Configuring Performance
Statistics of MSCS Load
Control
Prerequisites
70
OF
Context
MSCS provides the complete performance statistics function to calculate the number of received and rejected messages. Through
these statistical values, you may know the current congestion condition of the system.
Steps
1. On the NetNumen M30 window, select Views > Performance Management to enter the Performance Management window.
2. On the Performance Management window, double-click the
NE to be modified in the Performance Management tree to
expand the measured object types.
3. Right-click MSCS, select the Create Measurement Job
from the shortcut menu to show the Measurement Job
dialog box.
4. Specify relevant parameters in the General Information tab,
as shown in Figure 17.
FIGURE 17 CREATING
MEASUREMENT JOB
5. Select the NE to be measured in the Location Information

tab, as shown in Figure 18.
71
FIGURE 18 SPECIFYING LOCATION INFORMATION
6. Select the Measurement Type Information tab.

7. In the MSCS tree, double-click Special Operation > Load
Control, and select the check box followed by MSCS Load
Control.
8. In the right pane, specify duration from the Collection Granularity pull-down list, as shown Figure 19.
FIGURE 19 SPECIFYING MEASUREMENT TYPE INFORMATION
9. Click OK to complete the creation of measurement job.

END OF STEPS
72
Link Congestion Control

Background
Outgoing congestion control is to release the overload on outgoing associations and links, and the overload on SMP. Therefore,
the outgoing congestion control involves the congestion control
when SMP is overloaded and when associations and links are overloaded. Outgoing congestion control should be implemented both
on MSCS and on MGW. By default, outgoing congestion control is
not enabled.
Incoming congestion control is to limit accessing services when
SMP is congested so as to release the congestion on SMP. It
mainly controls the CR messages of A/Iu interface and the TC_BEGIN_REQ messages of TCAP. Incoming congestion control is only
implemented on MSCS. There is no incoming signaling congestion
control on the SMP of MGW. The incoming congestion control is
enabled all the time.
Configuration
Flow
The configuration of the link congestion control involves the following aspects.
The preparation for configuring the signaling congestion control is
described in Table 27.
TABLE 27 PREPARATION
CONTROL
No.
FOR
Operation
Purpose
Enabling the
SCCP congestion
control
CONFIGURING
THE
SIGNALING CONGESTION
Related Command
Reference
ADD PLATINFO
Enabling SCCP
Congestion Control
The procedure of configuring outgoing singling congestion control

on MSCS is described in Table 28.
TABLE 28 PROCEDURE
CONTROL ON MSCS
No.
OF
Operation
Purpose
CONFIGURING OUTGOING SINGLING CONGESTION
Related Command
Reference
Enabling the
outgoing
congestion
control function
for signaling
congestion
SET SENDFC
Configuring
Transmission Load
and Traffic Control
Setting an
MTP link for
congestion
control
SET N7LNKE1
Setting an MTP
link for congestion
control
73
Note:
Since association links have no ERL statistics, and the lower-layer
determines the congestion conditions of links, the load threshold
configuration is not necessary. If the outgoing congestion control
of signaling congestion is required enabling on MGW, the configurations involves are the same as that on MSCS. On MGW, the transmitting traffic and load control configuration and the load threshold
(ERL) configuration of SPB and DTB access links are also required.
The procedure of configuring incoming singling congestion control
on MSCS is described in Table 29.
TABLE 29 PROCEDURE
CONTROL ON MSCS
No.
OF
CONFIGURING INCOMING SINGLING CONGESTION
Operation Purpose
Reference
Configuring the SMP load threshold
Different from the SMP load threshold

used in outgoing congestion control,
it uses the CPU load threshold, which
is also used by CMP. Therefore, the
service control cycle and the SMP
CPU load threshold are the same as
those configured in the CMP congestion
control.
Configuration on
Threshold for SMP
Load Congestion
Control
Configuring the Minimum guaranteed

number of incoming service per second
when SMP congest variable
Configuring the
Minimum Guaranteed
Passing Number of
Incoming Services
When SMP Is
Congested
Enable the receiving flow control when

the interface processing ability is much
higher than the MP precessing ability
Setting Receiving
Flow Control
Enabling SCCP Congestion Control

Prerequisites
Context
Perform this procedure to enable the link congestion control function of the BSSAP/RANAP/TCAP.
Steps

system tree.
SET:NEID=11;
74
2. Enable the link congestion control function of

BSSAP/RANAP/TCAP. The command is SET PLATINFO.
the
Set the value of 121-type variable to 1. The command line is

as follows.
SET PLATINFO:TYPE=121,INFO=1;
END OF STEPS
Postrequisite
Configuring Transmission Load and

Traffic Control
Prerequisites
Context
Perform this procedure to enable the outgoing congestion control

for the signaling congestion, and to configure the CPU load threshold of CMP and link congestion standards.
Steps

system tree.
SET:NEID=11;
2. Enable the transmission load and traffic control function. The
command is SET SENDFC.
Table 30 lists the description of main parameters in the SET
SENDFC command.
TABLE 30 PARAMETERS
IN THE
SET SENDFC COMMAND
Parameter
Name
Parameter
Description
Instructions
FCFLAG
Flow control
switch
By default, this switch is closed.

Open this switch when the outgoing
control for signaling congestion is
enabled.
FCPLTHR
Link load
threshold
(ERL)
It is an optional parameter, ranging

from 0 to 255.
FCPLCUSHION
Link load
buffer (ERL)

from 0 to 100.
The link load buffer must be

no more than the link load
threshold.
75
Parameter
Name
Parameter
Description
Instructions
The link load buffer must be

no more than the threshold
configured for the load of SPB
and DTB access signaling links.
FCCPUTHR
CPU
occupancy
threshold (%)

from 0 to 100.
FCCPUCUSHION
CPU
occupancy
buffer (%)

from 0 to 100. The CPU occupancy
buffer must be no more than the
CPU occupancy threshold.
LOWESTPASS
Lowest
number
of passing
messages

from 5 to 5,000.
CTRLPRD
Control period
(s)

from 1 to 30.
EVALUATEPRD
Evaluate
period (s)

from 1 to 30.
Turn on the switch of the transmission load and traffic control,

and set the load threshold of all the links of the local office is
10 Erl. The specific command is as follows.
SET SENDFC:FCFLAG=OPEN,FCPLTHR=10;
END OF STEPS
Postrequisite
Setting an MTP link for congestion

control
Prerequisites
Context
Perform this procedure to open an MTP link for applying the special
outgoing congestion control standard.
Steps

system tree.
SET:NEID=11;
76
2. Set an MTP link for congestion control. The command is SET

N7LNKE1.
Table 31 describes the main parameter description in the SET
N7LNKE1 command.
TABLE 31 PARAMETERS
Parameter
Name
IN THE
Parameter
scription
SET N7LNKE1 COMMAND

De-
Instruction
ID
Link No.
Describes the number of the

link set comprising the link.
This parameter is required
and is defined as an integer
within 1~5000.
FCPLTHR
Link load threshold
An integer ranged in 0~100

or 255 (invalid), which is
optional
For example, set MTP link 1 for congestion control.

SET N7LNKE1:ID=1,FCPLTHR=20;
END OF STEPS
Postrequisite
Configuration on Threshold for SMP

Load Congestion Control
The SMP load threshold configured in the incoming link congestion
control is the same as the CPU load threshold of CMP. Therefore,
the service control cycle and the CPU load threshold of SMP are
the same as those configured in the CMP congestion control. For
details, refer to Configuring CMP Congestion Control Threshold and
Configuring Minimum Guaranteed Passing Number of Each Service
In Case of CMP Congested.
Configuring the Minimum Guaranteed

Passing Number of Incoming
Services When SMP Is Congested
Prerequisites
Context
Perform this procedure to configure the minimum assured passing

number of incoming services when SMP is congested.
77
Steps
2. On the Overload Control Parameter tab, click Minimum
guarantee number of incoming service per second when
SMP congest, and click on the sub-toolbar to enter the editing status, as shown in Figure 20.
FIGURE 20 SETTING VARIABLES
3. Type a value as required. The default is 30.

4. Click
on the sub-toolbar.
END OF STEPS
Setting Receiving Flow Control

Prerequisites
Context
Perform this procedure to enable the receiving flow control when

the interface processing ability is much higher than the MP precessing ability.
Note:
When the receiving flow control is enabled at local end, the peer
end should enable the link congestion control function.
Steps

system tree.
SET:NEID=11;
2. Set receiving flow control, the command is SET RECVFC.
78
Table 32 describes the main parameter description in the SET

RECVFC command.
TABLE 32 PARAMETERS
Parameter
Name
IN THE
SET N7LNKE1 COMMAND
Parameter
tion
Descrip-
Instructions
Flow control switch,

options:
FCFLAG
CLOSE: disable load

flow control function
OPEN: enable load

Select OPEN
Load flow control,

options:
PLFCFLAG
CLOSE: disable load

OPEN: enable load

Select OPEN
For example, set receiving flow control, enable the flow control
switch and load flow control. The command is as follows.
SET RECVFC:FCFLAG=OPEN,PLFCFLAG=OPEN;
END OF STEPS
79
80
Chapter
Applications of Traffic
and Load Control
Table of Contents
Application Introduction .....................................................81
Application of Traffic Control................................................81
Application of Load Control .................................................83
Application Introduction
The traffic is unbalanced during the running of the network, especially in different periods of time. For example, at the peak
traffic on holiday, large traffic takes place on the office with relatively large capacity and higher network position, such as the
exchange with large capacity, gateway exchange, and tandem exchange. During this period, the exchange load is much heavier
than that at ordinary time, accompanying with high CPU occupancy and a large number of CDR. With extremely large traffic,
the traffic overflow and congestion may occur. To ensure safe and
stable running of system and the smooth communication of network when large traffic occurs, the necessary traffic control and
load control should be implemented based on the actual condition
of each exchange so as to dredge the traffic equitably.
Traffic and load control are widely adopted towards the impact of
large traffic on holiday. Two control methods can protect the safe
running of system effectively when larger traffic occurs. The difference lies in that the traffic control aims to bring the processing
capability of the network into full play, put through, and dredge
the traffic under the basic condition of protecting the equipment
safety. While the load control aims to control the system load under the impact of large traffic so as to protect the system safety.
Application of Traffic Control

Description
The traffic control features the following aspects.
Effectively utilizing network resources and optimizing the direction of network traffic.
81
Effectively reducing invalid occupancy of the equipment by unreachable calls so as to improve equipment usage.
Effectively protecting the safe running of network equipment

under the impact of sudden large traffic.
Bringing maximum economic benefits to carriers.
Therefore, traffic control is widely adopted for preventing the impact of large traffic on holiday.
The traffic control falls into two categories.
Call Destination
Code
Management control on trunk resources
Traffic control on call destination
Destination code control

Restrict the traffic of incoming calls from specified incoming
trunk group to specific destination code on a percentage basis.
Temporary alternative routing

For specified destination code, specify some unconventional
trunk groups with idle allowance as temporary alternative route
to distribute the traffic.
Special announcement control

Within a specified periodthe system does not get through the
calls from specified incoming trunk group to specific destination
code. The system requests to postpone the call by playing a
special announcement to the operator and/or the subscriber.
Call gapping control

Within a specified period, set the maximum attempts that are
allowed to select a route for the call from specified incoming
trunk group to specific destination code, to make the attempts
not to exceed this value.
Outgoing Trunk
Resources
Traffic control on direct route

Perform the traffic control on the direct route of incoming calls
from specified incoming trunk group and through control outgoing trunk group on a percentage basis.
Circuit orientation
Convert the dual-running circuit (trunk) to incoming-running
circuit (trunk), and control the circuit on a percentage basis.
Circuit (trunk) turndown/busy/blocked

Temporarily turn down single or dual-running circuit (trunk) to
control the circuit on a percentage basis.
Traffic control on alternative route

Perform traffic control on alternative route of incoming call
from specified incoming trunk group and through controlled
outgoing trunk group on a percentage basis.
Trunk Reservation
Reserve the trunk circuit for some traffic on a percentage basis or by a specified circuit (trunk) number. When the number
of idle circuits in the circuit group is less than or equal to the
specified, the controlled traffic is rejected. It is available to
82
Chapter 6 Applications of Traffic and Load Control
specify the incoming trunk group number and restricted subscriber category of the controlled traffic.
Skip
The traffic skips over the controlled trunk group on a percentage basis, and enters the next trunk group of the normal route
selection in advance. The controlled traffic can be direct route
traffic or alternative route traffic.
Key Points for

Traffic Control
By mastering the network structure as well as the flow direction of traffic, and analyzing history traffic data, find out the
target of traffic control, such as call type, control method, and
control strength (percentage), to design a clear project of traffic control aiming at the target.
Select the most suitable functional type for traffic control based
on possible traffic condition.
After starting the traffic control, pay attention to the running

of the system. If any exception occurs in the exchange after
the traffic control starts, turn off the traffic control as soon as
possible.
For the best result of traffic control, the coordination between

different nodes on the network is necessary.
Application of Load Control

The traffic of various services processed by the switch will increase
dramatically in a short period on holiday. Under the impact of large
traffic, the systems CPU occupancy is higher than that at ordinary
time. Even the intermittent link disconnection and the decrease of
call completion ratio appear. Therefore, the engineer should pay
attention to the running status of the system on holiday, and perform relevant load control configuration for the impending traffic,
to protect the system from the impact of traffic peak safely and
stably.
Relevant Alarm Information about

Load Control
Overview
When the system is overloaded, it will prompt the corresponding

alarm information. And the call congestion of corresponding interface can be queried through the failure observation.
Information
from Failure
Observation
The module of the BSSAP/RANAP/TCAP/NNI interface will report

the call congestion, which indicates that the system is overloaded.
Check the alarm information to make sure detailed condition.
Alarm Information
When system is overloaded, two kinds of alarms possibly appear,

indicating which kind of load control mechanism takes effect.
1. When services are overloaded, the corresponding service overload alarm is MSCS service overload (33575463)
83
Handling suggestion: Increase the maximum service throughput rate of a module per second of MSC traffic load control
parameters. If short messages take a high proportion, reduce
the maximum proportion of allowed short messages to all messages. Meanwhile, make sure whether the traffic is really large
through performance statistics.
2. When the system is congested, the corresponding interface
congestion alarms are as follows.
MSC A interface overload (33610267).
MSC Iu interface overload (33610273).
Handling suggestion: Check the CPU occupancy of CMPs

through Performance Statistics. Move some associations/signaling links or inter-office circuits onto other modules with
lower CPU occupancy. If the CPU occupancy of all the other
modules is also very high, add more CMPs.
3. When the link is congested, the MTP3 link congestion alarm
(8400131) and broadband link congestion alarm (8399104)
appear in the fault management system.
Handling suggestion: Consider adding links to the adjacent
office mentioned in the alarm message.
4. When CMP is overloaded, the CMP Overload (33575466)
alarm appears in the fault management system.
Handling suggestion: Check the CPU occupancy of other CMPs
through performance statistics. If some of them have lower
CPU occupancy, move some associations/signaling-links or terrestrial circuits onto these modules. If other modules also have
high CPU occupancy, add more CMPs. Meanwhile, make sure
whether the traffic is really heavy through performance statistics.
For detailed contents of the above-mentioned alarms, refer to
ZXWN MSCS MSC Server Alarm Rerefence and ZXWN MSCS MSC
Server Notification Rerefence.
Processing Flow of Load Control

Judgment on
Overload
You may acquire the overload condition of MSCS by viewing relevant data of fault management, failure observation, and performance statistics on the OMM client.
If the system shows related alarm, or the call congestion occurs
on some interfaces by querying the failure observation, the system
is overloaded. For detailed contents about the alarm information
and the failure observation, refer to Relevant Alarm Information
about Load Control.
Processing Flow
84
Figure 21 shows the flow of processing MSCS overload through the

load control.
Chapter 6 Applications of Traffic and Load Control
FIGURE 21 HANDLING LARGE TRAFFIC FAULT
Flow Description
When the overload occurs during the running of soft-switch system, perform the service control first, and then the congestion
control. If the problem still remains, consider the emergency expansion.
1. Service control
i. Confirm the CPU performance statistics of alarming module. If the average value of CPU occupancy is far less than
80% when the alarm occurs, the configured flow value is
unreasonable. Configure it again.
Refer to the related sections about the detailed configuration method of service overload control.
ii. If the CPU occupancy of the alarming module is actually
over 80%, check other relevant modules to see whether
the load is balanced. If the load is balanced in general,
consider expanding the MP capacity immediately.
iii. If the load of other modules is not balanced, move a part of
associations, links and circuits that are configured on the
alarming module to other modules with relatively low CPU
occupancy.
iv. Adjust the flow threshold for various services
The system divides various accessed services into different
service processing units. The system overload is solved by
restricting the ratio of passing number and the total traffic
of these units. When the service is overloaded, the call
service is protected first. The SMS and the supplementary
services can be turned off when necessary.
Refer to the related sections about the detailed configuration method of service overload control.
2. Congestion control
85
i. Confirm the CPU performance statistics of the alarming

module. If the average value of CPU performance is far
less than the alarming threshold when the alarm occurs, or
the CPU peak value does not exceed the threshold, it indicates there are some problems with the load control. Set
the threshold of different levels as 100, and contact the
ZTE engineer for processing.
Refer to the related sections about the detailed configuration method of congestion control.
ii. If the CPU occupancy of the alarming module is actually
over 80%, check other relevant modules to see whether
the load is balanced. If the load is balanced in general,
considering expanding the MP capacity immediately is necessary.
iii. If the load of other modules is not balanced, move a part
of associations, links and circuits that are configured with
the alarming module to other modules with relatively low
CPU occupancy.
iv. Adjust the discarding policy of congestion control.
The congestion control performs the overload control on
A interface, Iu interface, MAP interface, and NNI interface
according to predefined discarding policy. The module determines whether and how to control the load according to
its resource usage, which is independent from other modules.
Refer to the related sections about the detailed configuration method of congestion control.
86
Figure
Figure 1 Structure of Traffic Control Subsystem ...................... 2

Figure 2 MSCS Load Control Mechanism ...............................23
Figure 3 CPU Load Level .....................................................27
Figure 4 Diagram of CPU Load Level and Resource Load Level...27
Figure 5 Service Control Cycle .............................................33
Figure 6 Equivalent CPU Consumption Configuration in
Variables Control ...............................................34
Figure 7 Enabling the Variable of Only Control Location
Update to HLR...................................................39
Figure 8 Configuring the Cycle of MP Load Statistics ...............45
Figure 9 Configuring CPU Load Threshold..............................46
Figure 10 Configuring the Minimum Assured Passing Number
of Each Service When CMP is Congested ...............47
Figure 11 Configuring the Variables Control of Subscriber
Priorities...........................................................48
Figure 12 Configuring Variable Control..................................56
Figure 13 Configuring Variable Control..................................57
Figure 14 Configuring the Adjacent Office Congestion Control
on Mc Interface .................................................61
Figure 15 Setting the Traffic Distribution of RTP Bearer
Congestion .......................................................67
Figure 16 Configuring the Minimum Guaranteed Number
of Downlink messages passing through A/Iu
interface...........................................................70
Figure 17 Creating a Measurement Job .................................71
Figure 18 Specifying Location Information.............................72
Figure 19 Specifying Measurement Type Information ..............72
Figure 20 Setting Variables .................................................78
Figure 21 Handling Large Traffic Fault...................................85
87
88
Table
Table 1 Parameter Description of the ADD DSTNUMCTL

Command.........................................................13
Table 2 Parameter Description of the ADD TGCTL Command...16
Table 3 Parameter Description of the ADD PRECODE
Command.........................................................19
Table 4 Parameter Description of the ADD TRAFCTL
Command.........................................................21
Table 5 Service Control Configuration Flow Based on Total
Service Traffic ...................................................33
Table 6 Parameters in the ADD MSCSRVLMT Command.........35
Table 7 Single Service Control Configuration Flow Based on
Incoming Traffic ................................................37
Table 8 Single Service Control Configuration Flow Based on
Outgoing Traffic.................................................38
Table 9 Parameters in the ADD GTLOADTMPLT Command .....40
Table 10 Parameters in the ADD GTGROUP Command...........41
Table 11 CMP Congestion Control Configuration Flow ..............44
Table 12 Procedure of Configuring Congestion Control on the
NNI Interface ....................................................49
Table 13 Procedure of Configuring Incoming Congestion
Control on the NNI Interface ...............................50
Table 14 Parameters in the SET ADJOFC Command...............51
Table 15 Parameters in the SET TG Command.......................52
Table 16 Parameters in the SET ACCTHD Command ..............53
Table 17 Parameters in the SET MDEFPRETMR Command......54
Table 18 Parameters in the SET OFCAPP Command...............58
Table 19 Parameters in the ADD TPDNAL Command .............59
Table 20 Congestion Control Configuration Flow of the Mc
Interface ..........................................................60
Table 21 Parameters in the SET TOPO Command ..................62
Table 22 Parameters in the ADD MGWOL Command ..............63
Table 23 Default Inferior Limit of Each CPU Congestion Level ...65
Table 24 Configuration Procedure of Downlink Congestion
Control on the A/Iu Interface ..............................68
89
Table 25 Parameters in the SET MDEFPRETMR command ......69

Table 26 Relationship between a Timer and Its Macro Value.....69
Table 27 Preparation for Configuring the Signaling Congestion
Control.............................................................73
Table 28 Procedure of Configuring Outgoing Singling
Congestion Control on MSCS ...............................73
Table 29 Procedure of Configuring Incoming Singling
Congestion Control on MSCS ...............................74
Table 30 Parameters in the SET SENDFC Command...............75
Table 31 Parameters in the SET N7LNKE1 Command ............77
Table 32 Parameters in the SET N7LNKE1 Command ............79
90
Index
A
Adjacent office .................. 48
C
Call congestion.................. 83
Call gapping control .............5
Congestion control....... 23, 43
Congestion level ................ 48
D
Data configuration ............. 12
Destination code control .......5
Dynamic traffic control ....... 19
F
Failure observation ............ 83
L
Link congestion level.......... 28
Local office ................... 3, 48
N
Number prefix................... 19
Number section ................. 15
S
Service control .................. 23
Special announcement .........5
T
Temporary alternative
routing .............................5
Traffic control......................1
Traffic control command .......5
Trunk group configuration ................................ 17
91

SJ-20100211152857-009-ZXWN MSCS (V3.09.21) MSC Server Traffic and Load Control

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

SJ-20100211152857-009-ZXWN MSCS (V3.09.21) MSC Server Traffic and Load Control

Caricato da

Copyright:

Formati disponibili

ZXWN MSCS

Traffic and Load Control

Feb. 28, 2010

Serial Number: SJ-20100211152857-009

About This Manual............................................. I

Traffic Control Configuration .............................5

Load Control Concepts and Principles.............. 23

Confidential and Proprietary Information of ZTE CORPORATION

ZXWN MSCS Traffic and Load Control

Link Congestion Control Policy ............................29

Service Control Configuration.......................... 31

Congestion Control Configuration.................... 43

Confidential and Proprietary Information of ZTE CORPORATION

Configuring Whether to Send a REJECT Message

Applications of Traffic and Load Control .......... 81

Confidential and Proprietary Information of ZTE CORPORATION

ZXWN MSCS Traffic and Load Control

This page is intentionally blank.

Confidential and Proprietary Information of ZTE CORPORATION

About This Manual

This manual is intended for engineers and technicians who perform

ZXWN system and its various components

Local maintenance procedures.

This manual contains the following chapters:

Chapter 1, Traffic Control Principle

This chapter describes the

Chapter 2, Traffic Control

This chapter describes the

Chapter 3, Load Control Concepts

This chapter introduces some

Confidential and Proprietary Information of ZTE CORPORATION

ZXWN MSCS Traffic and Load Control

Chapter 4, Service Control

This chapter introduces the

Chapter 5, Congestion Control

This chapter introduces the

Chapter 6, Applications of Traffic

This chapter describes the

This device complies with part 15 of the FCC Rules. Operation is

ZTE documents employ the following typographical conventions.

References to other Manuals and documents.

Menus, menu options, function names, input fields,

Keys on the keyboard and buttons on screens and

Mouse operation conventions are listed as follows:

Refers to clicking the primary mouse button (usually the

Refers to quickly clicking the primary mouse button

Refers to clicking the secondary mouse button (usually

Confidential and Proprietary Information of ZTE CORPORATION

Hexavalent Chromium (Cr (VI))

PolyBrominated Biphenyls (PBBs)

PolyBrominated Diphenyl Ethers (PBDEs)

The ZXWN MSCS manufactured by ZTE CORPORATION meet

Confidential and Proprietary Information of ZTE CORPORATION

ZXWN MSCS Traffic and Load Control

This page is intentionally blank.

Confidential and Proprietary Information of ZTE CORPORATION

Traffic Control Principle

Flexible Traffic Control

Traffic Control Subsystem

The traffic control subsystem consists of the foreground modules

Confidential and Proprietary Information of ZTE CORPORATION

ZXWN MSCS Traffic and Load Control

TRAFFIC CONTROL SUBSYSTEM

1. Traffic statistical information subsystem