ZXUN USPP Load Balancing
ZXUN USPP Load Balancing
ZXUN USPP Load Balancing
ZXUN USPP
Feature Specification
ZXUN USPP Load Balancing
LEGAL INFORMATION
By accepting this certain document of ZTE CORPORATION you agree to the following terms. If you do
not agree to the following terms, please notice that you are not allowed to use this document.
Copyright © 2016 ZTE CORPORATION. Any rights not expressly granted herein are reserved. This
document contains proprietary information of ZTE CORPORATION. Any reproduction, transfer,
distribution, use or disclosure of this document or any portion of this document, in any form by any
means, without the prior written consent of ZTE CORPORATION is prohibited.
is registered trademarks of ZTE CORPORATION. ZTE’s company name, logo and product
names referenced herein are either trademarks or registered trademarks of ZTE CORPORATION.
Other product and company names mentioned herein may be trademarks or trade names of their
respective owners. Without the prior written consent of ZTE CORPORATION or the third party owner
thereof, anyone’s access to this document should not be construed as granting, by implication,
estoppel or otherwise, any license or right to use any marks appearing in the document.
The design of this product complies with requirements of environmental protection and personal
security. This product shall be stored, used or discarded in accordance with product manual, relevant
contract or laws and regulations in relevant country (countries).
This document is provided “as is” and “as available”. Information contained in this document is subject
to continuous update without further notice due to improvement and update of ZTE CORPORATION’s
products and technologies.
ZTE CORPORATION
Address: NO. 55
Hi-tech Road South
ShenZhen
P.R.China
518057
Website: http://support.zte.com.cn
Email: [email protected]
TABLE OF CONTENTS
1 Introduction ................................................................................................................ 5
1.1 General Description ................................................................................................... 5
1.2 Involved Net Elements .............................................................................................. 5
1.3 Included Features ...................................................................................................... 6
4 Restrictions. .............................................................................................................. 66
FIGURES
Figure 1 signaling link and link aggregation group ........................................................................... 6
Figure 2 modules topology in service processing layer ................................................................... 8
Figure 3 traffic dispatching rule between CMP&SMP ...................................................................... 8
Figure 4 Load Balancing on Partitioning layer ................................................................................. 9
Figure 5 Message flow for HLR originating message .................................................................... 11
Figure 6 Message flow for HLR originating message .................................................................... 20
TABLES
Table 1 involved network elements .................................................................................................. 5
Table 2 parameters description for creating signaling group ......................................................... 12
Table 3 parameters description for creating signaling link ............................................................. 14
Table 4 parameters description for creating routing path .............................................................. 16
Table 5 parameters description for routing configuration to destination ........................................ 19
Table 6 parameters description for creating module...................................................................... 22
Table 7 parameters description for creating SCTP association ..................................................... 23
Table 8 parameters description for creating ASP configuration .................................................... 28
Table 9 parameters description for creating AS configuration ....................................................... 28
Table 10 parameters description for creating M3UA configuration ................................................ 30
Table 11 parameters description for creating SIO locate AS configuration ................................... 31
Table 12 parameters description for creating module.................................................................... 33
Table 13 parameters description for creating module.................................................................... 38
Table 14 parameters description for UAGW .................................................................................. 40
1 Introduction
ZXUN USPP load balance solution assigns the request message to the modules
equally to keep the load balance of the modules. When new modules are added,
the system will adjust the load balance within the existing modules and new
modules, to keep the same load balance for all the modules.
Signaling access layer: Assign the signaling link to the signaling interface
board equally, to realize the static load balance of No.7 and Sigtran
signaling.
Storage layer: PDSA cluster includes multi-nodes to store the same profiles
of users. All the nodes send the working state (master/slave) and load state
(CPU Usage) to the IDSA periodically, and IDSA adjusts the assign ratio of
messages according the working state and load state of the nodes, to
realize the load balance of data routing
MSC/VLR C/D All MAP messages related with HLR as defined in 3GPP TS
29.002.
SGSN Gr All MAP messages related with HLR as defined in 3GPP TS
29.002.
USPP
Link Aggregation
Group
Signaling Link Signaling Link
MSC/VLR
Interface Unit Interface Unit
SGSN
Load-sharing is deployed on link group, since all links in same link group are
active, when sender network elements send traffic to receiver, they shall launch
load-sharing on links in same link group, it means that round-robin mechanism
shall be used to guarantee each link from same group share same traffic load.
DPBB board has CMP, SMP and SIPI logic function in ZXUN USPP.
CMP module is responsible for MAP process, i.e., call handle, location
update, short message service processing etc..
Round-Robin
Round-Robin
After the SMP board processing the MTP3/SCCP/Sigtran, the CMP will be
assigned to process the services of call-related, LU, SMS etc.. The SMP will
deliver the signaling message to the CMP alternately.
Figure 3 traffic dispatching rule between CMP&SMP
1 2 3 4
Round-Robin
SMP
All functions of Partition layer reside on UAGW and IDSA module. As shown in
the following figure, in order to achieve high availability:
There are several UAGW instances, and each UAGW instance provides the
same service.
Each IDSA cluster includes several IDSA instances, all IDSA instances in same
IDSA cluster share same routing information.
Figure 4 Load Balancing on Partitioning layer
When 3rd FE accesses UDS to fetch the subscriber’s profile, the Dispatcher
choose appropriate UAGW to process request from 3rd FE according to status
and load of UAGW. Then UAGW access IDSA to fetch the subscriber’s profile.
Since all IDSA instances in one IDSA cluster have same copy of routing
information, when USPP FE or UAGW accesses the subscribers’ profile, it means
that any IDSA instance could be a candidate. The selection for an eligible
candidate is based on the running state of IDSA instance, each IDSA instance
broadcasts running state to UAGW and USPP FE, if an UAGW or USPP FE
confirms that one IDSA instance is abnormal, this IDSA instance shall be
removed from the candidate list.
For example, there are 4 IDSA instances in one IDSA cluster, if all boards are the
same, with pre-configured dispatching ratio : 1:1:1:2 , the volume of messages
to each IDSA instance are 20%, 20%,20%,40%.
All functions of storage layer reside on PDSA module. The load balancing
mechanism on storage layer is the same as it on partitioning layer.
3 Functional Description
Note1:
Signaling routing path configuration: it includes 2 signaling link groups (load-sharing), load balancing for
HLR originating message on routing level could be done by this step.
Note2:
Signaling link group: each link group includes several signaling links. load balancing for HLR originating
message on signaling link level is done in this step.
Load balancing on signaling access layer is achieved by sender party. Message flow for HLR originating
message is portrayed in following figure:
Interface Unit
MSC/VLR/SGSN SMP CMP
(E1 Port)
Outgoing signaling
Locate the right signaling group which connect right destination by checking
the routing configuration with destination address. USPP achieves load
balancing by dispatching traffic to 2 link groups.
With the signaling group configuration, system could get the signaling links
for current link group, and launch the round-robin dispatching rule intra
signaling group.
Create signaling group and put signaling links into signaling group. For the
concern of system availability, for each destination network elements, there
shall be two signaling group, two link groups work in load-sharing mode.
Create routing path configuration, couple the routing path and signaling link
group. In this step, for the link groups we created in previous step, they
works in load-sharing mode.
Command
ADD N7LKS:[OFCID=],[OFCNM=],TYPE=,ID=,NAME=,[LECM=];
Parameters
Table 2 parameters description for creating signaling group
Parameters Description
Associated adjacent office ID of the signaling link set, using the desired
range: 1-65534.
For signaling link sets based on E1/T1 connection, you can select:
Broadband Linkset
M2PA Linkset
set only occupy one time slot on one E1/T1 line, with the bandwidth
of 64 Kbps.
n*64 K means that the narrowband signaling links in the signaling link
set occupy all of 31 time slots on one E1/T1 line (the time slot 0 is
Signaling link set ID, range: 1-1024, numbered from 1, globally unique.
ID
It is recommended to be consistent with the adjacent office ID.
When the link transmission delay is less than 15 ms, Basic Error Revision
(default) is used. In addition, when the link transmission
transmission delay.
Example
ADD N7LKS:OFCID=220,TYPE="N2M",ID=1,NAME="STP",LECM="BASIC";
Create one signaling link group, its’ ID number is 1, it is used by HLR to
connect with office which ID number in HLR is 220, the media type is
2M E1 cable.
2. Create SS7 signaling link
Command
ADD
TDMN7LNK:ID=,NAME=,[LKSID=],[LKSNM=],[SLC=],[MODULE=],[MODUL
ENAME=],[MTP2UNIT=],[MTP2UNITNAME=],[MTP2CPU=],[ACCESSUNIT
=],[ACCESSUNITNAME=],MASDEVICENO=,SUBDEVICENO=,[E1TS=],[TSN
UM=],[LOOP=],[INFO=],[FCPLTHR=];
Parameters
Table 3 parameters description for creating signaling link
Parameters Description
Global serial number of this signaling link (the link numbers of the links in
ID different link groups are all unrepeatable), range: 1-5000.
LKSID Linkset id, it indicates that which signaling link group, this link belongs to
ID of the signaling link set to which the signaling link belongs, range:
LKSNM 1-1024.
Signaling link codes in the same signaling link set cannot be the same,
which must be consistent with those on the peer-end office.
MODULE Serial number of the module that the signaling link belongs to, range:
1-65534.
MODULENAME Name of the module that this link belongs to, range: 0-50 characters.
Name of the SLB that processes this link, range: 0-50 characters.
MTP2UNITNAME
Set it in accordance with the networking plan.
Unit number of the SLB that processes this link, range: 1-65534.
MTP2CPU
Set it in accordance with the networking plan
Unit number of the SLI where the E1 line corresponding to this link is
ACCESSUNIT located, range: 1-65534.
Support E1
Support T1-56K
Select the value in accordance with the networking plan. In general, select
E1
Load sharing ratio (%) of this link, range: 0-100, or 255 (indicating
FCPLTHR
invalid), default: 255.
Example
ADD TDMN7LNK:
ID=2,NAME="2",LKSID=1,SLC=2,MODULE=3,MTP2UNIT=14,MTP2CPU=1
,ACCESSUNIT=14,MASDEVICENO=0,SUBDEVICENO=4,E1TS=1,TSNUM=3
1;
Create one signaling link, its’ ID number is 2, it belongs to link group 2,
SMP3 is reserved for process signaling message for this link.
3. Create Routing path configuration
Command
ADD
N7ROUTE:[LKSID1=],[LKSNM1=],[LKSID2=],[LKSNM2=],ID=,NAME=,[LPM
=],[LPMIN=],[MANUAL=],[LINKS=],[SLS8BIT=];
Parameters
Table 4 parameters description for creating routing path
Parameters Description
LKSID1 Select one set from the existing Linkset IDs from the SHOW N7LKS
command execution results.
LKSNM1 Alias of the first signaling link set used by the route, range: 0-50 characters.
Normally, the route to an office uses only the signaling link set to this
office, and an associated adjacent office can only be configured with one
signaling link set. Therefore, for a route to an associated office, this
LKSID2 parameter is set to 0 (default value).
If there are two STPs between the local office and the quasi-associated
office, then Linkset1 and Linkset2 refer to the two signaling link sets to the
two STPs.
LKSNM2 Alias of the second signaling link set used by the route, range: 0-50
characters.
ID Global ID of the signaling route, used for selecting the signaling route in
ADD ADJOFC command execution, range: 1-2000.
Options:
Random Order
Selected On SLS_BIT0
Selected On SLS_BIT1
Selected On SLS_BIT2
LPM Selected On SLS_BIT3
Selected On SLS_BIT0-1
Selected On SLS_BIT1-2
Selected On SLS_BIT2-3
Random Order
Selected On SLS_BIT0
Selected On SLS_BIT1
Selected On SLS_BIT2
Selected On SLS_BIT3
Selected On SLS_BIT0-1
Selected On SLS_BIT1-2
Selected On SLS_BIT2-3
Selected On SLS_BIT0-1-2
Selected On SLS_BIT1-2-3
Sort the links manually. The link list is composed of indices and link
numbers.
LINKS Index: Index of the link, which is combined with the link No. to compose
the link list; value range: 1-32
Link No.: Serial No. of the link, which is combined with the link index to
compose the link list; value range: 1-5000
SLS8BIT Whether the system supports 8BIT SLS route. Default: No.
Example
HLR directly connects with STP, so HLR create one signaling routing
record, the ID of routing record is 1, the first link group for current
routing record is link group1, and the second link group is not
configured because the ID is 0.
ADD N7ROUTE:LKSID1=1,LKSID2=0,ID=1,NAME="STP"
Command
ADD
N7OFC:[ID=],[OFCNM=],NAME=,[RT1=],[RTNM1=],[RT2=],[RTNM2=],[RT
3=],[RTNM3=],[RT4=],[RTNM4=];
Parameters
Table 5 parameters description for routing configuration to destination
Parameters Description
ID of the first optional route which may be used in case that the normal
RT1 route is not available, selected from the existing Signaling Route IDs in the
result of the SHOW N7ROUTE command, range: 0-2000, default: 0.
RTNM1 Alias of the first round route in sending the signaling messages to the
destination office, range: 0-50 characters.
ID of the second optional route which may be used in case that the first
optional route is also not available, selected from the existing
RT2
Signaling Route IDs in the result of the SHOW N7ROUTE command, range:
0-2000, default value: 0.
RTNM2 Alias of the second round route in sending the signaling messages to the
destination office, range: 0-50 characters
ID of the third optional route which may be used in case that the second
RT3 optional route is also not available, selected from the existing Signaling
Route IDs in the result of the SHOW N7ROUTE command, range: 0-2000,
default value: 0.
RTNM3 Alias of the third round route in sending the signaling messages to the
destination office, range: 0-50 characters.
ID of the third optional route which may be used in case that the second
RT4 optional route is also not available, selected from the existing Signaling
Route IDs in the result of the SHOW N7ROUTE command, range: 0-2000,
default value: 0.
RTNM4 Alias of the third round route in sending the signaling messages to the
Example
ADD N7OFC:ID=220,NAME="AA",RT1=1,RT2=2
For destination network element which ID number in HLR is 220 , name
is AA, there are two routing records is configured in HLR towards AA :
this first routing choice for HLR is routing record1, when first routing is
dead, HLR could used second routing record2.
Each routing can includes at most 4 Ass. All ASs in one M3UA work in load-sharing mode. Load balance for
HLR originating message is done in this step.
Interface Unit
MSC/VLR/SGSN SMP CMP
(GE)
Outgoing signaling
In order to route traffic message to right destination and achieve load balancing
intra the signaling group, USPP shall:
With the AS, ASP and SCTP association configuration, system could get the
all SCTP associations by AS ID, and launch the round-robin dispatching rule
between SCTP associations in same AS.
Command
ADD
MODULE:LOC=,MTYPE=,[MODULE=],[BTYPE=],[BKMODE=],[NENO=],[NA
ME=],[DESC=];
Parameters
Table 6 parameters description for creating module
Parameters Description
i. Click the Location text box. The Location dialog box is displayed.
ii. Enter Rack No. (range: 1-15), Shelf No. (range: 1-3), and Slot
LOC No. (range: 1-14).
Module Type
Refer to the Module Type dialog box that appears by clicking the text
MTYPE
box for available options.
Example
ADD MODULE:LOC=1-2-3,MTYPE="SMP_HLR",MODULE=3;
Create one module on system with the location: rack1, shelf2 and slot 3.
The application going to running on this module is HLR SMP, the module
number is 3.
2. Create SCTP association
Command
ADD
M3UASCTP:ID=,NAME=,MODULE=,OFCID=,ROLE=,LOCADDR=,LOCPORT
=,REMADDR=,REMPORT=,[INSTRM=],[OUTSTRM=],[MAXRTRY=],[MAXRT
O=],[MINRTO=],[INITRTO=],[HB=],[FIXNH=],[SCTPMAXRTRYNUM=],[DEL
AYACK=],[MAXBURST=],[PRIMARYPATH=],[PMTU=],[BREAKTIME=],[PDTH
RESH=],[MINCWND=],[PLTIMER=],[MPPLTHRD=],[DPLEN=],[CB=],[QOSTY
PE=],[QOSVALUE=],[CHECKSUM=];
Parameters
Table 7 parameters description for creating SCTP association
Parameters Description
Signaling module number that the SCTP link belongs to. This link is
MODULE maintained by the bearer and signaling on this module. Select the SMP
module number, range: 1-65534
OFCID ID of the adjacent office that connects to the link directly, range: 1-65534.
Set it according to actual connection.
The link establishment is originated by the client. The both ends of the link
ROLE
have different application attributes. Normally, the opposite-end office is
set to Client (Apply SCTP To Client) and ZXUN USPP (HLR) is set to Server
(Apply SCTP To Server).
SCTP port number of the link on the local office, which is also the
LOCPORT opposite-end port number of the remote office, range: 1-65535.
Enter the local SCTP port number according to the networking plan
SCTP port number of the link on the remote office, which is also the
REMPORT local-end port number of the remote office, range: 1-65535.
Enter the remote SCTP port number according to the networking plan.
(recommended).
When a signaling message is sent from one end of the IP channel to the
other end, the transmitting end will wait for the reception
acknowledgement from the receiving end by using a timer. If the
acknowledgement is received from the peer end, then data are transmitted
successfully. If the timer expires, then message is lost or long congestion
delay occurs. The transmitting end retransmits this message using the
MAXRTRY backup IP address to ensure that the receiving end can receive this
message quickly. When the times of continuous data transmission failure
on an IP channel reaches the set Max Retransmission Times of Path Data,
then this IP channel is marked as an unavailable one, and all data messages
are taken over by other IP channels. It should be consulted by
(recommended).
MAXRTO The maximum time-out value of the retransmission timer, range: 10-3000,
default: 500 (recommended).
MINRTO The minimum time-out value of the retransmission timer, range: 10-1000,
default: 50 (recommended).
address on the remote end. This parameter sets the interval for sending
the HEARTBEAT block. Range: 10-6000, default: 500 (recommended).
Remote IP 2
Remote IP 3
Remote IP 4.
The SCTP packet length should meet the requirements of the path MTU.
PMTU Range: 0-127, default: 0.
threshold, the SCTP fast trace detection for this path is initiated.
PDTHRESH
Range: 0-10, default: 3.
The congestion window aims at each destination address. Its size varies
according to the network condition. When the length of the message that
is sent to the destination address but has not been acknowledged exceeds
MINCWND
the size of its corresponding congestion window, the end point stops
sending data to this address. Range: 0-255, default: 0.
Options include:
1 MTU (default)
DPLEN 1/2 MTU
1/4 MTU
1/8 MTU
MTU refers to the Maximum Transfer Unit of the path. Set it in accordance
with the networking plan.
Options include:
NULL (default)
QOSTYPE DSCP
TOS
Options include:
Adaptive (default)
CHECKSUM CRC32
ADLER32
Example
ADD
M3UASCTP:MODULE=3,OFCID=90,ROLE="SVR",LOCADDR=IPv4-0-"192.1
68.65.1"&IPv4-0-"192.168.65.2",LOCPORT=8003,REMADDR=IPv4-0-"19
2.168.90.100"&IPv4-0-"192.168.90.101",REMPORT=8003,NAME="90-1"
,ID=3;
One STCP association with unique ID=3 is created to connect to
destination which internal id in HLR is 90. HLR works as Server side; it
uses IP address 192.168.65.1 and 192.168.65.2. The remote IP of
office90 is 192.168.90.100 and 192.168.90.101.
3. ASP configuration
Command
ADD M3UAASP:ID=,NAME=,ASSOCID=,[ISLOOP=],[ISLOCK=];
Parameters
recommended.
Used to set whether the ASP is in the locked status during startup.
ISLOCK The locked setting is used for management. The default value Not
locked is recommended.
Example
ADD M3UAASP:ASSOCID=2,ID=3;
One ASP is created, the ID of ASP is 2 , the SCTP association is 3.
4. AS configuration
Command
ADD
M3UAAS:ID=,NAME=,ASPID=,[EXISTCTX=],[CTXID=],[ASTAG=],[ASUP=],[
ASMD=],[NVAL=];
Parameters
Table 9 parameters description for creating AS configuration
Parameters Description
NAME User-defined name of this AS, such as AS1, range: 0-50 characters
A field that is negotiated on the local office and its adjacent office and
CTXID identifies an AS uniquely. This value can be configured as required
For all AS usage tags, in the case of ASP and SGP used for the two
end offices of the AS, when one office is a signaling gateway of the
other office, then the office acting as the signaling gateway is set
transmitted between the two offices, the IPSP mode is used. One
end is set to IPSP Server (default) and the other end is set to
The upper layer protocol type supported by AS, which defines the
type of the upper layer users using the AS. Refer to the User Types
ASUP dialog box that appears by clicking the text box for available options.
For ZXUN USPP (HLR), ISUP and SCCP are often selected. It is
The number of ASPs in the activated status when the system works
Example
ADD M3UAAS:ID=90,ASPID=3&4
One Application Server (AS) is created, the ID of AS is 90, and it includes
2 ASP: ASP3 and ASP4. As the default setting, two ASPs work in
load-sharing mode.
5. M3UA routing configuration
Command
ADD
M3UART:ID=,NAME=,ASID1=,[ASID2=],[ASID3=],[ASID4=],[RANGEMODE
=],[SLS8BIT=],[[ASPID=];
Parameters
Table 100 parameters description for creating M3UA configuration
Parameters Description
ID ID of this M3UA static route to add, range: 1-640.
NAME User-defined name of this M3UA static route, range: 0-50 characters.
ID of the second AS, range: 0-640, selected from the existing AS IDs,
ASID2
needs no configuration when the second AS does not exist.
ID of the third AS, range: 0-640, selected from the existing AS IDs, needs
ASID3
no configuration when the third AS does not exist
ASID4 ID of the third AS, range: 0-640, selected from the existing AS IDs, needs
Options include By Turns (default), Manual and Nature. The default value
RANGEMODE
is recommended.
SLS8BIT Whether the system supports 8BIT SLS route. Default: No.
When Route Array Mode is set to Manual, you need to manually specify
the set of ASPs for sorting. Click the text box and set the ASP list on
ASPID
the ASP List dialog box that appears. Value range: 1-2048. Set it in
Example
ADD M3UART:ID=1,ASID1=90;
One M3UA routing record with ID=1 is created; it only uses one AS as
routing path.
Command
ADD SIOLOCAS:NAME=,OFCID=,SIO=,[OPOFCID=],RT1=,[RT2=];
Parameters
Table 111 parameters description for creating SIO locate AS configuration
Parameters Description
Office Configuration.
Used to identify the upper layer protocol type that the transferred message
SIO belongs to. Various upper layer protocol types can be located to a same AS
with the prerequisite that the AS supports these upper layer protocol
types.
Create the SCCP and ISUP service indications for each adjacent office to
support MAP and ISUP protocols.
RT1 M3UA static route of the located AS, associated with M3UA Static Route ID
in Create M3UA Static Route Configuration, range: 1-640.
Example
ADD SIOLOCAS:OFCID=90,SIO="SCCP",RT1=90;
Create one routing record towards destination network element who’s
ID in HLR is 90. The M3UA routing path configuration used by this
routing rule is 90. The protocol over SCTP association is SCCP.
Command
ADD
MODULE:LOC=,MTYPE=,[MODULE=],[BTYPE=],[BKMODE=],[NENO=],[NA
ME=],[DESC=];
Parameters
Table 122 parameters description for creating module
Parameters Description
i. Click the Location text box. The Location dialog box is displayed.
ii. Enter Rack No. (range: 1-15), Shelf No. (range: 1-3), and Slot
LOC No. (range: 1-14).
Module Type
MTYPE Refer to the Module Type dialog box that appears by clicking the text box
for available options.
Data Processing Blade A (DPBA) : (Default) Select this option when the
BTYPE DPBA2 blade is used.
Data Processing Blade B (DPBB): Select this option when the DPBBx
blade is used.
Backup mode of this module, option: Without Backup and One Plus One
BKMODE Backup
NENO ID of the network entity which the module belongs to, range: 0-254
Example
ADD MODULE:LOC=1-2-3,MTYPE="CMP_HLR",MODULE=3;
Create one module on system with the location: rack1, shelf2 and slot 3.
The application going to running on this module is HLR CMP, the
module number is 3.
Module configuration
This configuration defines the modules existing in system, it includes
physical location information and with module information system could
know where the modules are and establish internal communication
between them. Module information is the base for all application instances,
before defining a UAGW instance; we shall assign a module number to an
instance at first.
Locate the IDSA cluster by checking subscriber distribution plan inner IDSA
group by user identities
IDSA group is the aggregation of IDSA cluster. All IDSA cluster in same IDSA
group has routing information for different subscribers.
Module configuration
This configuration defines the modules existing in system, it includes
physical location information and with module information system could
know where the modules are and establish internal communication
between them. Module information is the base for all application instances,
before defining a DSA instance; we shall assign a module number to an
instance at first.
Create Module
Create UAGW instance and couple the instance with module number.
Create IDSA instance and couple the instance with module number.
Create IDSA cluster and put IDSA instance into IDSA cluster
Create IDSA group and put IDSA cluster into IDSA group
Command
ADD
MODULE:LOC=,MTYPE=,[MODULE=],[BTYPE=],[BKMODE=],[NENO=],[NA
ME=],[DESC=];
Parameters
Table 133 parameters description for creating module
Parameters Description
i. Click the Location text box. The Location dialog box is displayed.
ii. Enter Rack No. (range: 1-15), Shelf No. (range: 1-3), and Slot
LOC No. (range: 1-14).
Refer to the Module Type dialog box that appears by clicking the text
Data Processing Blade A (DPBA) : (Default) Select this option when the
DPBA2 blade is used.
BTYPE Data Processing Blade B (DPBB): Select this option when the DPBBx
blade is used.
NENO ID of the network entity which the module belongs to, range: 0-254
Example
ADD MODULE:LOC=1-2-3,MTYPE="CMP_HLR",MODULE=3;
Create one module on system with the location: rack1, shelf2 and slot 3.
The application going to running on this module is HLR CMP, the
module number is 3.
2. Create UAGW instance
Command
ADD UAGW: UAGWNODEID=, BNO=, MODULE=, INTIP=, [INTPORT=],
IPTYPE=, EXTIP=, [EXTPORT=], NAMINGCONTEXTS=, SMALLPAGESIZE=,
Parameters
Table 144 parameters description for UAGW
Parameters Description
UAGWNODEID The ID of each UAGW node is unique, range: 1-65000.
BNO The ID of the physical office that this UAGW node belongs to, range: 1-254.
Example
Command
ADD IPV4DISP:
INDEX = <INDEX>, LOCALIP = <LOCALIP>, REMOTEMASK =
<REMOTEMASK>, REMOTEIP = <REMOTEIP>, PROTOCOL = <PROTOCOL>
[, LOCALPORTRANGEMIN = < LOCALPORTRANGEMIN >] [,
LOCALPORTRANGEMAX = < LOCALPORTRANGEMAX >] [,
REMPORTRANGEMIN = < REMPORTRANGEMIN >] [,
REMPORTRANGEMAX = < REMPORTRANGEMAX >] [, MODTIMERS = <
MODTIMERS >] [,VPN=<VPN>] [,NAME=<NAME>];
Parameters
Table 155 parameters description for dispatcher rule
Parameters Description
Interface IP address of the SIPI unit in the local office, IPV4 type.
NEXTHOP
Set it in accordance with the networking plan.
Range: 1-1024.
TUNNELID The default value (null) is recommended.
No.
Default: No.
Example
ADD IPV4DISP: INDEX=6130, LOCALIP="168.168.231.168",
REMOTEMASK="0.0.0.0", REMOTEIP="0.0.0.0", PROTOCOL="TCP",
LOCALPORTRANGEMIN=3130, LOCALPORTRANGEMAX=3130,
REMPORTRANGEMIN=1, REMPORTRANGEMAX=65535,
MODTIMERS=130-1;
Add an IPV4 dispatch: index number is 6130; local IP address is
"168.168.231.168"; remote IP address mask code is "0.0.0.0"; remote IP
address is "0.0.0.0"; protocol number is "TCP"; the minimum value of
local port range is 3130; the maximum value of local port range is 3130;
the minimum value of remote port range is 1; the maximum value of
Command
ADD
DSANODE:DSANODEID=,BNO=,MODULE=,MODULETYPE=,[INTIP=],[INTP
ORT=],[IPTYPE=],[EXTIP=],[EXTPORT=],[NAME=];
Parameters
Table 166 parameters description for IDSA
Parameters Description
The ID of each DSA node on all the offices in ZXUN USPP (HLR) is unique.
If the number of the deployed office (the office where the DSA node is
located) is between 1 and 64, the ID of the deployed office is equal to the
deployed office number. Otherwise, the deployed office IDs are allocated
again in the USPP. The deployed office IDs starts from 1, and each of them
is unique in the same USPP.
ID of the deployed office that the DSA node belongs to, integer type, range:
BNO 1-254.
Module No. of this DSA node, range: 1-1024, consistent with the one set in
MODULE the OMM.
Module type of this DSA node. Set it in accordance with the networking
plan.
MODULETYPE
IDSA: Identity DSA node
IP address of this DSA node for communicating with all modules (the DSA
INTIP node of the local office included) of the local office.
Port No. of this DSA node for internal access, default: 5057, range;
1024–65535.
INTPORT
Set it in accordance with the networking plan.
Port No. of this DSA node for external access, default: 5057, range:
1024-65535.
Example
ADD
DSANODE:DSANODEID=1,BNO=2,MODULE=3,MODULETYPE="IDSA";
Create one IDSA instance, its ID is 1 , it going to running on office2
module3.
Command
ADD
DSA:DSAID=,NAME=,DSATYPE=,[IDTYPE=],[BNO=],[BNO2=],[NOELECT=];
Parameters
Table 177 parameters description for IDSA cluster
Parameters Description
ID of the DSA cluster, range: 1-65000. The ID of each DSA cluster should be
unique. Set it in accordance with the networking plan.
All the DSA nodes in a DSA cluster must have the same type as this cluster.
For example, if the DSA type is PDSA, all the nodes in this DSA cluster must
be of the PDSA type.
It indicates whether it is the IDSA cluster for IMSIs, DNs or other types of
numbers.
An IDSA cluster may have numbers of more than one types. Set it in
IDTYPE accordance with the networking plan.
When modifying the IDSA number type, you can only add but not delete
the number types. The modification of the number type of the DSA cluster
takes effect only after you transfer the changed table and restart the UDS.
Note that restarting the UDS may cause service interruption so perform
this operation under the guidance of the professional maintenance
personnel.
ID of the secondary home office of this DSA cluster, integer type, range:
0-254.
In case of failures on the monitoring center of the primary home office, the
BNO2 monitoring center of the secondary home office will take over this DSA
cluster. Set it in accordance with the networking plan.
If the UDS belongs to only one office, it is not required to configure this
parameter
Example
ADD DSA:DSAID=1,NAME="dsa1",DSATYPE="IDSA";
Create one IDSA cluster DSA1, its ID is 1.
6. Create IDSA cluster members
Command
ADD DSACLU:DSANODEID=,DSAID=,[NODELEV=],
[SERVRATE=] ,[NAME=];
Parameters
Table 188 parameters description for IDSA cluster member
Parameters Description
The DSA node must be the one created by the ADD DSANODE
DSANODEID
command. A DSA node can belong to only one DSA cluster.
ID of the DSA cluster that this DSA node belongs to, range: 1–65000.
The DSA cluster must be the one created by the ADD DSA command.
DSAID
A DSA cluster can contain several DSA nodes that have the same type as
the DSA client, such as PDSA.
Level of this DSA node, options: level 1 and level 2, default: level 1 A
level–1 DSA node keeps real-time data synchronous with the main node. In
case of a failure in the main node, the monitoring center prefers to select a
level-1 node as the new main node. In general, level-1 nodes are deployed
at a same place with the main node.
When the main node is working, it does not need to wait for the response
from level-2 nodes.
The sum of the percentages of message distribution on all the DSA nodes in
a DSA cluster should not exceed 100.
SERVRATE It is suggested to adjust the value when the load sharing is abnormal, the
machine configuration is much different, or the distance between nodes is
different as well as other special requirements. Adjusting the message
distribution proportions helps to improve the processing capability of the
DSA cluster.
NAME Alias of this DSA member for easy recognition, 0-50 characters.
Example
ADD DSACLU: DSANODEID=1,DSAID=1;
Put IDSA instance 1 into IDSA cluster 1.
7. Create IDSA group and put IDSA cluster into IDSA group
Command
ADD IDDSAGRP: DSAID=,DSAGRPID=,[NAME=];
Parameters
Table 199 parameters description for creating IDSA Group member
Parameters Description
NAME Alias of this configuration record for easy recognition, range: 0-50
characters
Example
ADD IDDSAGRP:DSAID=1,DSAGRPID=1;
Put IDSA 1 into DSA Group1.
8. Grant mapping code information to each IDSA cluster.
Command
ADD IDSAMAP:[SN=],NUMTYPE=,BEGIN=,END=,DSAID=,[NAME=];
Parameters
Table 200 parameters description for granting mapping code to IDSA cluster
Parameters Description
For all the clusters in a group, the mapping code sections for the same type
of number segments must occupy the full range of 0 to 999 without an
overlap.
For example, for three IMSI IDSA clusters having the hardware performance
END similar to each other, the mapping code sections can respectively be 0 to
333, 334 to 666, and 667 to 999.
For another example, for the IMSI number segments, if a mapping code
section 0 to 500 is allocated to DSA cluster11 and a mapping code section
501 to 999 is allocated to DSA cluster12, the number 460000000000001 is
allocated to DSA cluster11 when the DSA cluster processes the data.
It must be selected from the IDs of the existing DSA clusters whose type is
DSAID set to IDSA in DSA cluster creation. Range: 1 to 65000.
Example
ADD IDSAMAP:SN=1,NUMTYPE="IMSI",BEGIN=1,END=9,DSAID=1;
Grant the mapping code for IMSI identity from 0 to 9 on IDSA1 .
9. Grant physical identities resource to IDSA group.
Command
ADD IDSAGSPN:[SN=],NUMTYPE=,BEGIN=,END=,DSAGRPID=,[NAME=];
Parameters
Table 211 parameters description for granting physical identities to IDSA cluster
Parameters Description
plan.
networking plan.
NAME Alias of the configuration item, range: 0 to 50 characters.
Example
ADD
IDSAGSPN:SN=1,NUMTYPE="IMSI",BEGIN="000000000000001",END="0
00000000000100",DSAGRPID=1;
Grant the IMSI identity resource from 000000000000001 to
000000000000100 to IDSA group1.
10. Grant logical identities resource to IDSA group.
Command
ADD IDSAGSLN:[SN=],NUMTYPE=,BEGIN=,END=,DSAGRPID=,[NAME=];
Parameters
Table 2223 parameters description for granting logical identities to IDSA cluster
Parameters Description
plan.
networking plan.
NAME Alias of the configuration item, range: 0 to 50 characters.
Example
ADD
IDSAGSLN:SN=1,NUMTYPE="DN",BEGIN="000000001",END="00000010
0",DSAGRPID=1,NAME="1";
Grant the MSISDN identity resource from 000000001to 000000100 to
IDSA group1.
PDSA group is the aggregation of PDSA cluster. All PDSA cluster in same
PDSA group has profile information for different subscribers.
Module configuration
This configuration defines the modules exist in system, it includes physical
location information with information, system could knows that where the
module is and establish internal communication with it. Module information
is the base for all application instances, before defines a DSA instance, we
shall give the instance a module number at first.
Create Module
Create PDSA instance and couple the instance with module number.
Create PDSA cluster and put PDSA instance into PDSA cluster
Create PDSA group and put PDSA cluster into PDSA group
1. Create module
Command
ADD
MODULE:LOC=,MTYPE=,[MODULE=],[BTYPE=],[BKMODE=],[NENO=],[NA
ME=],[DESC=];
Parameters
Table 243 parameters description for creating module
Parameters Description
i. Click the Location text box. The Location dialog box is displayed.
ii. Enter Rack No. (range: 1-15), Shelf No. (range: 1-3), and Slot
LOC No. (range: 1-14).
Module Type
Refer to the Module Type dialog box that appears by clicking the text
MTYPE
box for available options.
NENO ID of the network entity which the module belongs to, range: 0-254
NAME User-defined name of the module, range: 0-50 characters.
Example
ADD MODULE:LOC=1-2-3,MTYPE="CMP_HLR",MODULE=3;
Create one module on system with the location: rack1, shelf2 and slot 3.
The application going to running on this module is HLR CMP, the
module number is 3.
2. Create PDSA instance
Command
ADD
DSANODE:DSANODEID=,BNO=,MODULE=,MODULETYPE=,[INTIP=],[INTP
ORT=],[IPTYPE=],[EXTIP=],[EXTPORT]=,[NAME=];
Parameters
Table 254 parameters description for creating PDSA
Parameters Description
The ID of each DSA node on all the offices in ZXUN USPP (HLR) is
unique.
DSANODEID
In general, it is composed of the ID (one to two digits) of the deployed
office and the module number (leading zeros are added if the module
number is less than three digits). For example, suppose that the office
ID is 11 and the module number of the DSA node is 60. The DSA node
ID is 11060.
If the number of the deployed office (the office where the DSA node is
the deployed office number. Otherwise, the deployed office IDs are
allocated again in the USPP. The deployed office IDs starts from 1, and
ID of the deployed office that the DSA node belongs to, integer type,
BNO range: 1-254.
Module No. of this DSA node, range: 1-1024, consistent with the one
MODULE set in the OMM.
Module type of this DSA node. Set it in accordance with the networking
plan.
IP address of this DSA node for communicating with all modules (the
INTIP DSA node of the local office included) of the local office.
Port No. of this DSA node for internal access, default: 5057, range;
1024–65535.
INTPORT
Set it in accordance with the networking plan.
Port No. of this DSA node for external access, default: 5057, range:
1024-65535.
Example
ADD
DSANODE:DSANODEID=1,BNO=2,MODULE=3,MODULETYPE="PDSA";
Create one PDSA instance, its ID is 1 , it going to running on office2
module3.
3. Create PDSA cluster
Command
ADD
DSA:DSAID=,NAME=,DSATYPE=,[IDTYPE=],[BNO=],[BNO2=],[NOELECT=],
;
Parameters
Table 265 parameters description for creating PDSA cluster
Parameters Description
DSAID ID of the DSA cluster, range: 1-65000. The ID of each DSA cluster should be
All the DSA nodes in a DSA cluster must have the same type as this cluster.
For example, if the DSA type is PDSA, all the nodes in this DSA cluster must
be of the PDSA type.
It indicates whether it is the IDSA cluster for IMSIs, DNs or other types of
numbers.
An IDSA cluster may have numbers of more than one types. Set it in
accordance with the networking plan.
IDTYPE
When modifying the IDSA number type, you can only add but not delete
the number types. The modification of the number type of the DSA cluster
takes effect only after you transfer the changed table and restart the UDS.
Note that restarting the UDS may cause service interruption so perform
this operation under the guidance of the professional maintenance
personnel.
plan.
ID of the secondary home office of this DSA cluster, integer type, range:
0-254.
In case of failures on the monitoring center of the primary home office, the
BNO2 monitoring center of the secondary home office will take over this DSA
cluster. Set it in accordance with the networking plan.
If the UDS belongs to only one office, it is not required to configure this
parameter
Example
ADD DSA:DSAID=1,NAME="dsa1",DSATYPE="PDSA";
Create one PDSA cluster DSA1, its ID is 1.
4. Create PDSA cluster members
Command
ADD DSACLU:DSANODEID=,DSAID=,[NODELEV=],
[SERVRATE=] ,[NAME=];
Parameters
Table 276 parameters description for creating PDSA cluster members
Parameters Description
The DSA node must be the one created by the ADD DSANODE
DSANODEID
command. A DSA node can belong to only one DSA cluster.
ID of the DSA cluster that this DSA node belongs to, range: 1–65000.
DSAID The DSA cluster must be the one created by the ADD DSA command.
A DSA cluster can contain several DSA nodes that have the same type as
the DSA client, such as PDSA.
Level of this DSA node, options: level 1 and level 2, default: level 1 A
level–1 DSA node keeps real-time data synchronous with the main node. In
case of a failure in the main node, the monitoring center prefers to select a
level-1 node as the new main node. In general, level-1 nodes are deployed
at a same place with the main node.
NODELEV For two DSA nodes of a DSA cluster that is working in a load-sharing or
mutual-backup mode, they should be both set as level-1 nodes. For two
DSA nodes of a DSA cluster that is working in an active/standby mode, one
node may be set as a level-2 node by considering the time delay.
When the main node is working, it does not need to wait for the response
from level-2 nodes.
Set it in accordance with the networking plan.
The sum of the percentages of message distribution on all the DSA nodes in
a DSA cluster should not exceed 100.
SERVRATE It is suggested to adjust the value when the load sharing is abnormal, the
machine configuration is much different, or the distance between nodes is
different as well as other special requirements. Adjusting
NAME General format: DSA node number-DSA node type-DSA number. For
example, 3-PDSA-2 means the No.3 PDSA node belonging to the No.2 DSA
cluster
Example
ADD DSACLU: DSANODEID=1,DSAID=1;
Put PDSA instance 1 into IDSA cluster 1.
5. Create PDSA group and put PDSA cluster into PDSA group
Command
Parameters
Table 287 parameters description for creating PDSA group members
Parameters Description
NAME Alias of this configuration record for easy recognition, range: 0-50
characters
Example
ADD IDDSAGRP:DSAID=1,DSAGRPID=1;
Put PDSA 1 into DSA Group1.
6. Grant physical identities resource to PDSA group.
Command
ADD
DSAGRPSPN:SPNID=,NUMTYPE=,BEGIN=,END=,DSAGRPID=,[NAME=];
Parameters
Table 298 parameters description for granting physical identities to PDSA group
Parameters Description
Example
ADD
DSAGRPSPN:SPNID=1,NUMTYPE="IMSI",BEGIN="000000000000001",E
ND="000000000000100",DSAGRPID=1;
Grant the IMSI identity resource from 000000000000001 to
000000000000100 to PDSA group1.
3.6 Statistics
The following counters are introduced by the load balancing.
Signaling access level
Table 30 statistics counter in signaling access level
SN NAME Description
1 Number of Received SCCP Message Count of the SCCP messages received from the
Signal Unit layer-2 link.
2 Number of Sent SCCP Message Count of the SCCP messages sent from the layer-2
Signal Unit link.
3 Number of DATA Message Sent Count of sent data messages.
4 Number of DATA Message Count of received data messages.
Received
5 Times of Business Message Sent Count of upper-layer user messages that M3UA’s AS
sends.
6 Times of Business Message Count of messages to an upper-layer user that
Received M3UA's AS receives
12 Times of Attempted Any Time Count of attempts for subscriber information query
Subscription Interrogation at any time.
13 Times of Attempted Any Time Count of attempts for modification at any time.
Modification
14 Times of Attempted Request for Count of times of attempted request for INAP
INAP Retrieve retrieve
15 Times of Attempted Register Count of attempts to register supplementary
Supplementary Service services.
16 Times of Attempted Erasing Count of attempts to delete a supplementary
Supplementary Service service.
17 Times of Attempted Activating Count of attempts to activate supplementary
Supplementary Service services.
18 Times of Attempted Deactivating Count of attempts to deactivate supplementary
Supplementary services.
Service
19 Times of Attempted Processing Count of attempts to handle non-structured
Unstructured supplementary service requests.
Supplementary Service Request
20 Times of Attempted Unstructured Count of attempts for non-structured supplementary
Supplementary service requests.
Service Request
21 Times of Attempted Unstructured Count of attempts for non-structured supplementary
Supplementary service requests.
Service Notification
22 Times of Attempted Sending Count of GPRS called-party routing attempts.
Routing Information for
GPRS
23 Times of Attempted Updating GPRS Count of GPRS location update attempts.
Location
24 Times of Attempted Inserting Count of attempts to insert subscriber GPRS data.
Subscriber's GPRS Data
25 Times of Attempted Sending Count of short message called-party routing
Routing Information for attempts.
Short Messages
26 Times of Alerting Short Message Count of times of alerting Short Message Service
Service Centre Centre.
2 Count of DSP Add Action Count of DSP add messages received by PDSA.
3 Count of LDAP Delete Action Count of LDAP delete messages received by IDSA.
4 Count of DSP Delete Action Count of DSP delete messages received by PDSA.
5 Count of LDAP modify Action Count of LDAP modify messages received by IDSA.
6 Count of DSP Modify Action Count of DSP modify messages received by PDSA.
7 Count of LDAP Search Action Count of LDAP search messages received by IDSA.
8 Count of DSP Search Action Count of DSP search messages received by PDSA.
9 Count of LDAP Execute Action Count of LDAP execute messages received by IDSA.
10 Count of DSP Execute Action Count of DSP execute messages received by PDSA.
11 Count of LDAP Compound Action Count of LDAP compound messages received by
IDSA.
12 Count of DSP Compound Action Count of DSP compound messages received by
PDSA.
3.7 Alarms
No.
3.8 Capacity
No Applicable.
4 Restrictions .
The load balancing function is automatically switched on; there is no software
license on it. But it has software limitation on:
The maximal SCTP association supported for each site is 2048
For 2M E1 connection, the maximal connection for each site is 480.
The maximal module number is 1024
The maximal DSA instance number is 1024.
5 Related Features
No