Documente Academic
Documente Profesional
Documente Cultură
MSC Server
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
First edition
Contents
II
Figure.............................................................. 87
Table ............................................................... 89
Index .............................................................. 91
III
IV
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
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
Summary
FCC Compliance
Statement
Chapter
Summary
Conventions
Meaning
Italics
Quotes
Links on screens.
Bold
CAPS
II
Typeface
Meaning
Click
Doubleclick
Right-click
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)
II
Chapter
FIGURE 1 STRUCTURE
Structure
OF
Chapter
Traffic Control
Configuration
Table of Contents
Traffic Control Commands .................................................... 5
Configuraitons on MML Termainal.........................................12
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.
Destination Code
Control
The incoming/outgoing destination code control falls into the following five modes.
Special announcement
Restriction percentage
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:
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 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
Interval.
Direct Route
Traffic Control
The outgoing trunk group control falls into the following six modes.
Circuit orientation
Trunk reservation
Skipping.
Restriction percentage
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:
Restriction percentage
Restriction percentage
Restriction percentage
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 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
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.
11
Restriction percentage
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
Context
Perform this procedure to implement call control on specific destination code according to predefined conditions.
Steps
12
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)
OPCAT
OPN
Restricted calling
category
Restricted calling
number
CMMN (Ordinary
subscribers)
PRIOR (Priority
subscriber)
13
Parameter
Name
De-
Instructions
DPN
Restricted called
number
Start
Start time
End time
END
DSTTYPE
PER
The type
of restricted
destination code
Restriction
percentage
It is used to describe
the type of the
destination-code of traffic
control. The enumerated
values are as follows:
It is used to describe
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
INTERVAL
The duration of an
interval (second)
Temporary
alternative route
It is used to describe
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
CAUSE
Cause value
PT
De-
Playing tones
Instructions
It is used to describe
whether to play tones for
the calls controlled by
the traffic control. The
enumerated values are as
follows:
Attempt interval: 0
Cause value: 2
The system can correctly report the call loss, make performance
statistics, or play tone.
15
Postrequisite
Before the operation, it is required to confirm that the MML Terminal window is opened.
Context
Steps
NAME
OTG
ID
16
OF THE
Parameter Description
Instruction
Alias
It is used to describe
a traffic control on
outgoing trunk for
identification. The
maximum length is 50
bytes.
Restricted outgoing
trunk group
SN
It is used to identify
the serial number of an
outgoing traffic control
for quick search. The
maximum value is
65535.
Parameter
Name
Parameter Description
Instruction
It is used to describe
the type of an outgoing
trunk group command.
The enumerated values
are as follows:
Command type of
trunk group
TYPE
START
END
PER
INTG
CCTDIR (Circuit
orientation
TRKNA (Circuit
(trunk) Turndow
n/Busy/Blocked)
ARRESTRIC
(Alternative route
traffic control
TRKRSV (Trunk
reservation)
SKIP (Skip)
Start time
It is used to describe
the start time of traffic
control
End time
It is used to describe
the end time of traffic
control. If both start
time and end time are
00:00, the traffic control
is implemented whole
day.
Restriction percentage
It is used to describe
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
17
Parameter
Name
Parameter Description
Instruction
It is used to describe
the calling type. The
enumerated values are
as follows:
OPCAT
RTCTL1
Restricted calling
category
CMMN (Ordinary
subscribers)
PRIOR (Priority
subscriber)
RSTRIN (Entry
restricted)
RSTROF (Overflow
restricted)
RTCTL2
OVERDIR (Skipping
over the direct route
traffic)
OVERALT (Skipping
over the alternative
route traffic)
OVERBOTH
(Skipping over
both direct and
alternative route
traffic)
The type of the trunk group command: DRTRF (0, directrouting traffic restriction)
18
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.
Transfer data tables.
Before the operation, it is required to confirm that the MML Terminal window is opened.
Context
Steps
ID
CODE
OF THE
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.
ID: 1
Alias: 139.
Before the operation, it is required to confirm that the MML Terminal window is opened.
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
20
Parameter
scription
OF THE
De-
Instructions
CODE
Number prefix
BTM
Traffic control
begin time
ETM
CTRLMD
Traffic control
mode, including
two options, PCNT
(percent) and
INTVL (Interval)
Max attempted
call
MINANSRT
PCNT
Restriction
percentage
CTRLINTVL
Control interval
(min.)
ATCL
Controlled
attempted calls
MAXATCL
21
Parameter
Name
Parameter
scription
De-
CSVL
Cause Value
PLTN
It is an optional and
enumerated parameter,
with a default of No.
Instructions
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.
Transfer data tables.
Chapter
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
Control
Mechanism
Congestion control
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
Outgoing
Service Control
Mechanism
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.
24
Outgoing
Congestion
Control
Service Overload
Service
Processing Unit
CPU Consumption
of Service
Processing Unit
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
Location update
Authentication
MO/MT SMS
GMSC service
CAMEL service
Intra-office handover
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
OF
AND
27
Control Policy
28
29
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.
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
Description
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 calls between the ISUP/TUP and the BICC occupy 60%.
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.
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
ON
TOTAL
No.
Operation Purpose
Reference
Configuring service
control cycle
Context
Steps
3. Click the
END OF STEPS
33
Context
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
END OF STEPS
Context
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
IN THE
Parameters
Name
Parameters
Description
Instructions
CALLNUM
LUNUM
Times of location
updates per
second
SMSNUM
Short messages
per second
HONUM
Times of
handover per
second
35
Parameters
Name
Parameters
Description
Instructions
USSDNUM
LCSNUM
PBRTNUM
Times of PBRT
per second
ALLSRVNUM
Amount of
passed traffic
per second
DSMSNUM
Times of
delivering short
messages per
second
Service Control
Configuration Based on
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
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
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
ON
No.
Operation Purpose
Reference
Service Control
Configuration Based on
Single Outgoing Service
Description
You may set the outgoing service control under the following four
conditions.
37
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
Configuration
Flow
38
ON
No.
Operation
Purpose
Related Command
Reference
Enabling the
function of
only controlling
location update
service 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
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.
2. On the MSC, VLR, GSMC, MSCServer Service Overload
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
39
3. Click the
END OF STEPS
Context
Steps
IN THE
Parameter
Name
Parameter Description
Instruction
GTGROUP
Home GT group
ID
NUMPERSECHLR
Times of the
service allowed
to HLR per
second
NUMPERSECSMS
Times of the
service allowed
to the SMC per
second
NUMPERSECSCP
Times of the
service allowed
to SCP per
second
40
GT group ID: 1
Context
Steps
IN THE
Parameter
Name
Parameter
Description
Instruction
GT
GT number
GTGROUP
Home GT
group ID
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.
Parameter
Description
43
Basic Configuration
Overview
Configuration
Flow
Operation Purpose
Reference
Configuring CMP
Congestion Control
Threshold
Configuring Minimum
Guaranteed Passing
Number of Each
Service In Case of
CMP Congested
Configuring Subscriber
Priorities
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
FIGURE 8 CONFIGURING
THE
CYCLE
OF
MP LOAD STATISTICS
END OF STEPS
Context
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 Threshold of
on the sub-toolbar to enter
CPU slight overload, and click
the editing status, as shown in Figure 9.
45
END OF STEPS
Context
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 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
PASSING NUMBER
END OF STEPS
Context
Steps
47
FIGURE 11 CONFIGURING
PRIORITIES
3. Click the
THE
VARIABLES CONTROL
OF
SUBSCRIBER
END OF STEPS
48
Description
Function
Description
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
OF
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
49
TABLE 13 PROCEDURE OF
ON THE NNI INTERFACE
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
Configuring Variable
Control
SET OFCAPP
Configuring Call
Level of Incoming
Call Subscribers
(Incoming Office)
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.
Context
Steps
50
IN THE
Parameter
Name
Parameter
Description
Instructions
OFCID
Adjacent office ID
Identifier of an adjacent
office, ranging from 1 to
3,000
Select YES.
Context
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
TG
THD
IN THE
SET TG COMMAND
Parameter
Description
Instructions
Trunk group
number
Overload control
threshold
52
Context
Steps
LVL
THD
NAME
IN THE
Parameter
Description
Instructions
Congestion Level
Threshold (%)
Alias
53
Context
Steps
IN THE
Parameter
Description
Instructions
Module types,
including:
MT_3G_RPU:
RPU module
MODTYPE
54
Parameter
Name
Parameter
Description
Instructions
TIMER
NAME
Timer Name
CURINTERVAL
Current timing
length (ms)
Context
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.
2. On the MSC, VLR, GSMC, MSCServer Service Overload
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
3. Click the
END OF STEPS
Context
"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
3. Click the
END OF STEPS
Context
Steps
57
IN THE
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.
Context
Steps
58
TABLE 19 PARAMETERS
Parameter Name
ENTR
DIGIT
IN THE
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
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
Configuration
Flow
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
60
Context
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, select Whether
to control downlink message according to the congest
level of RNC/BSC/MGW. Click
on the sub-toolbar to enter
the editing status. Check the Yes check box to enable this
function, as shown in Figure 14.
FIGURE 14 CONFIGURING
ON MC INTERFACE
3. Click
THE
END OF STEPS
Context
Steps
61
IN THE
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
Context
Steps
62
IN THE
Parameter
Description
Instructions
CPUOL1
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
inferior limit of level-3
CPU congestion should
be less than or equal
to that of level-4 CPU
congestion.
CPUOL4
Inferior limit
of CPU usage
triggering level-4
CPU congestion
It is an optional
parameter, ranging
from 0 to 100. The
inferior limit of level-4
CPU congestion should
be less than or equal
to that of level-5 CPU
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
parameter, ranging from
0 to 100. The inferior
limit of level-1 memory
congestion should be
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
parameter, ranging from
0 to 100. The inferior
limit of level-2 memory
congestion should be
less than or equal to that
of the level-3 memory
congestion.
Inferior limit of
memory usage
triggering level-3
memory congestion
It is an optional
parameter, ranging from
0 to 100. The inferior
limit of level-3 memory
congestion should be
less than or equal to that
of level-4 congestion.
MEMOL4
Inferior limit of
memory usage
triggering level-4
memory congestion
It is an optional
parameter, ranging from
0 to 100. The inferior
limit of level-4 memory
congestion should be
less than or equal to that
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
It is an optional
parameter, ranging
from 0 to 100.
REJOL2
It is an optional
parameter, ranging
from 0 to 100.
REJOL3
It is an optional
parameter, ranging
from 0 to 100.
REJOL4
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.
OF
Parameter
Value
75
80
85
65
Parameter
Value
90
95
Context
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 Diffluent ratio of RTP Bearer at Congestion Level 1 (%), and click
on the sub-toolbar to enter the editing status, as shown in
66
3. Click
THE
TRAFFIC DISTRIBUTION
OF
RTP BEARER
END OF STEPS
Postrequisite
Configuration
Procedure
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.
Table 24 describes the procedure of configuring the downlink congestion control on the A/Iu interface.
67
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
Configuring Variable
Control
Configuring Variable
Control
Context
Steps
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
NAME
Timer Name
CURINTERVAL
Current duration of
a timer
BETWEEN A
TIMER
AND
Timer
12114
12115
12138
12140
Context
Steps
1. On the NetNumen M30 window, select Views > Professional Maintenance > MSCS > Variables Control > Overload Control Parameter to enter the Overload Control Parameter tab.
69
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
71
72
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
OF
Operation
Purpose
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
Operation Purpose
Reference
Configuration on
Threshold for SMP
Load Congestion
Control
Configuring the
Minimum Guaranteed
Passing Number of
Incoming Services
When SMP Is
Congested
Setting Receiving
Flow Control
Context
Perform this procedure to enable the link congestion control function of the BSSAP/RANAP/TCAP.
Steps
74
the
Context
Steps
IN THE
Parameter
Name
Parameter
Description
Instructions
FCFLAG
Flow control
switch
FCPLTHR
Link load
threshold
(ERL)
FCPLCUSHION
Link load
buffer (ERL)
75
Parameter
Name
Parameter
Description
Instructions
FCCPUTHR
CPU
occupancy
threshold (%)
FCCPUCUSHION
CPU
occupancy
buffer (%)
LOWESTPASS
Lowest
number
of passing
messages
CTRLPRD
Control period
(s)
EVALUATEPRD
Evaluate
period (s)
Context
Perform this procedure to open an MTP link for applying the special
outgoing congestion control standard.
Steps
76
IN THE
Parameter
scription
Instruction
ID
Link No.
FCPLTHR
Context
77
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 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
on the sub-toolbar.
END OF STEPS
Context
Note:
When the receiving flow control is enabled at local end, the peer
end should enable the link congestion control function.
Steps
78
IN THE
Parameter
tion
Descrip-
Instructions
Select OPEN
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.
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.
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
Outgoing Trunk
Resources
Circuit orientation
Convert the dual-running circuit (trunk) to incoming-running
circuit (trunk), and control the circuit 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
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.
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.
Information
from Failure
Observation
Alarm Information
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.
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
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
86
Figure
87
88
Table
89
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