ZXUN USPP Load Balancing

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: 800@zte.com.cn
ZTE Confidential Proprietary © 2016 ZTE Corporation. All rights reserved. II

Version Date Author Approved By Remarks
V1.00 2012-06-20 Not open to the Third Party
V1.01 2012-12-20 Not open to the Third Party
© 2016 ZTE Corporation. All rights reserved.

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

TABLE OF CONTENTS
1 Introduction ................................................................................................................ 5
1.1 General Description ................................................................................................... 5
1.2 Involved Net Elements .............................................................................................. 5
1.3 Included Features ...................................................................................................... 6
2 Functionality Description and Scenarios ................................................................ 6

2.1 Load Balancing on Signaling access layer ............................................................. 6
2.2 Load Balancing on Service processing layer ......................................................... 7
2.3 Load Balancing on Partitioning layer ...................................................................... 9
2.4 Load Balancing on Storage layer ........................................................................... 10
3 Functional Description ............................................................................................ 10

3.1 Load Balancing on Signaling access layer for SS7 ............................................. 10
3.1.1 Configuration Parameters .......................................................................................... 11
3.1.2 Provision Parameters ................................................................................................ 20
3.2 Load Balancing on Signaling access layer for SIGTRAN .................................... 20
3.3 Load Balancing on Service processing layer ....................................................... 32
3.4 Load balancing on partitioning layer ..................................................................... 34
3.5 Load Balancing on Storage layer ........................................................................... 52
3.6 Statistics ................................................................................................................... 63
3.7 Alarms ....................................................................................................................... 66
3.8 Capacity .................................................................................................................... 66

4 Restrictions. .............................................................................................................. 66
5 Related Features ...................................................................................................... 66
6 Definitions and Abbreviations ................................................................................ 67
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 14 parameters description for UAGW .................................................................................. 40

Table 15 parameters description for dispatcher rule ...................................................................... 41

Table 16 parameters description for IDSA ..................................................................................... 43
Table 17 parameters description for IDSA cluster ......................................................................... 45
Table 18 parameters description for IDSA cluster member ........................................................... 46
Table 19 parameters description for creating IDSA Group member .............................................. 48
Table 20 parameters description for granting mapping code to IDSA cluster ............................... 49
Table 21 parameters description for granting physical identities to IDSA cluster .......................... 50
Table 22 parameters description for granting logical identities to IDSA cluster............................. 51
Table 24 parameters description for creating PDSA...................................................................... 56
Table 25 parameters description for creating PDSA cluster .......................................................... 58
Table 26 parameters description for creating PDSA cluster members .......................................... 60
Table 27 parameters description for creating PDSA group members ........................................... 62
Table 28 parameters description for granting physical identities to PDSA group .......................... 62
Table 29 statistics counter in signaling access level ........................................................................ 63
Table 30 statistics counter in service processing level ..................................................................... 64
Table 31 statistics counter on BE ..................................................................................................... 65

1 Introduction
1.1 General Description
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.
ZXUN USPP provides four layers load-balance mechanism:
 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.
 Service processing layer: Signaling interface board assigns the signaling

message to the SMP equally, to realize the service processing balance.
 Partitioning layer: IDSA cluster includes multi-nodes to store the same ID

routing data information. All the nodes send the working state
(master/slave) and load state (CPU Usage) to the SMP periodically, and SMP
adjusts the assign ratio of messages according the working state and load
state of the nodes, to realize the load balance of data routing.
 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
1.2 Involved Net Elements

Table 1 involved network elements
Net Element Interface Related Messages
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.

UDS Ud LDAP Search, Add, Modify and compound.
1.3 Included Features
This specification include following features:
 ZWF-10-42-008 Load Balancing
2 Functionality Description and Scenarios
2.1 Load Balancing on Signaling access layer
The load sharing on signaling access layer is based on the association

configuration for Singtran/SS7 Link configuration for SS7 and dispatch rules on
opposite network elements such as MSC/VLR and SGSN.
When MSC/VLR or SGSN connects with HLR, signaling channels shall be

configured at first, with different physical transmission media type and used
protocol the signaling links could be SCTP link for Sigtran or MTP link for SS7.
In order to achieve redundancy on signaling network, a signaling channel (or link)

shall be assigned to one and only one link aggregation group and any signaling
link from same link group has the same destination in network and work in
active mode. As shown in following figure:
Figure 1 signaling link and link aggregation group

USPP
Interface Unit Interface Unit
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.
For messaes originated by MSC/VLR or SGSN, it is the responsibility for MSC/VLR

or SGSN to implement load-sharing on links layer.
For messages originated by HLR, it is the responsibility for HLR to implement

load-sharing on links layer.
2.2 Load Balancing on Service processing layer
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..
 SMP module is responsible for protocol processing, including

MTP3/SCCP/SIGTRAN.

 Interface unit is responsible for forwarding signaling message which is

received from or sending out through physical GE port or E1 port.
The different modules topology is referred to the following：

Figure 2 modules topology in service processing layer
CMP1 CMP2 CMP3 CMP4 CMP5 CMP n
Round-Robin
SMP1 SMP2 SMP3 SMP n
Round-Robin
interface Unit interface Unit
Signaling Link Signaling Link
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

CMP1 CMP2 CMP3 CMP4
1 2 3 4
Round-Robin
SMP
2.3 Load Balancing on Partitioning layer
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.
The proportion of traffic for each eligible candidate is mainly based on

pre-configured dispatching ratio and the utilization of CPU for each instance is
also considered to adjust the volume in order to avoid overload protection.
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%.
2.4 Load Balancing on Storage layer
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
3.1 Load Balancing on Signaling access layer for SS7
The hierarchical structure of signaling configuration for SS7 is:
Routing configuration for destination
|_______signaling routing path configuration (note1)
|_______signaling link group (note2)
|_______Configuration of signaling link

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:
Figure 5 Message flow for HLR originating message
Interface Unit
MSC/VLR/SGSN SMP CMP
(E1 Port)
Selects one SMP by

round-robin way
Outgoing signaling
1) Select signaling group by

checking routing configuration
Outgoing message with destination address
2) dispatch message intra the
Outgoing message signaling group
In order to route signaling message to right destination and achieve load

balancing intra the signaling group, USPP shall:
 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.
3.1.1 Configuration Parameters

As constructing a building, we shall configure the signaling configuration from
the bottom up:

 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 all signaling links towards destination network elements (MSC/VLR,

SGSN).
 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.
 Create routing configuration to destination, in this step, the relationships

between destination and routing path are created.
Detailed information for create signaling related configuration as listed in the
following part:
1. Create signaling link group
 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
OFCID Office ID from the SHOW ADJOFC command execution results,
range: 1-65534.
OFCNM Alias of the associated adjacent office, range: 0-50 characters.
For signaling link sets based on E1/T1 connection, you can select:
 64K Narrowband Linkset
 N*64K Narrowband Linkset
TYPE  2M Narrowband Linkset
 Broadband Linkset
 M2PA Linkset
64 K means that the narrowband signaling links in the signaling link

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 n serial time slots (8≤n≤25) on one E1/T1 line.
2 M 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
unavailable), with the bandwidth of 1.984 Mbps. ZXUN USPP (HLR)
does not use other types at present.
This parameter must be consistent on the two ends.
Signaling link set ID, range: 1-1024, numbered from 1, globally unique.
ID
It is recommended to be consistent with the adjacent office ID.
NAME Alias of the signaling link set, range: 1-50 characters
Basic Error Revision: By using non-compelled, positive/negative
acknowledgement and error correction through retransmission control

methods, the message signal units can be transferred on the signaling link
orderly without duplication and errors can be corrected through
retransmission control when they are found.
Preventive Cyclic Retransmission: By using non-compelled, positive
acknowledgement and cyclic retransmission error correction method,the

message signal units stored in the retransmission buffer without any
LECM
positive acknowledgements are retransmitted automatically when there
are not any new message signal units or link status signal units to be
transferred. If there is a new signal unit, retransmission cycle is paused and
the signal unit is transferred first.
When the link transmission delay is less than 15 ms, Basic Error Revision
(default) is used. In addition, when the link transmission
delay is more than 15 ms, Preventive Cyclic Retransmission is adopted. This

parameter must be consistent on the two ends. Select a method according
to the requirements of the network operator and the actual link

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
Global serial number of this signaling link (the link numbers of the links in
ID different link groups are all unrepeatable), range: 1-5000.
Set it in accordance with the networking plan.

NAME User–defined name of this TDM signaling link, range: 1-50 characters
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 code (SLC), range: 0-15.
SLC A signaling link set has 16 narrowband signaling links at most.
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.

CPU number of the narrow-band signaling processing board (SLB), range:

1-4. The four CPU numbers correspond to the four CPU subcards of the
MTP2UNIT
SLB.
Name of the SLB that processes this link, range: 0-50 characters.
MTP2UNITNAME
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.
Name of the SLI where the E1 line corresponding to this link is

ACCESSUNITNAME located, range: 0-50 characters.
MASDEVIENO Range: 0-254. Set it to 0.
ID of the E1 link, range: 1-32. The 32 subordinate device numbers

SUBDEVICENO correspond to L1 to L32 indicators on the panel of the SLB.
The starting timeslot on the SLI E1 subunit occupied by the outgoing E1

signaling link.
E1TS
For the 64 Kbps signaling link, the value range is 1-31. This parameter must
be consistent on both ends of the interconnection.
The amount of consecutive time slots on SLI E1 subunit occupied by the

outgoing E1 signaling link.
TSNUM
For 64 Kbps signaling links, this parameter is fixed to 1. This
parameter must be consistent on both ends of the interconnection.
LOOP There is no self loop normally. Select Not Self Loop(NO).
INFO Select Support E1 (E1).

Determines whether this link supports E1 or T1. Options:
 Support E1
 Support T1-64k Normal Code
 Support T1-64k Inverted Code
 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
The first signaling link set used by the route.
LKSID1 Select one set from the existing Linkset IDs from the SHOW N7LKS
command execution results.
Value range: 0-1024; default value: 0.
LKSNM1 Alias of the first signaling link set used by the route, range: 0-50 characters.

The second signaling link set used by the route.
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.
Value range: 0-1024.
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.
NAME Alias of the signaling route, range: 1-50 characters
Mode of link arrangement between signaling link sets.
Options:
 Random Order
 Selected On SLS_BIT0
LPM  Selected On SLS_BIT3
 Selected On SLS_BIT0-1
Recommended value: Random Order.
In this configuration, the SLCs on both ends must be identical.
Otherwise, links may be blocked.
Mode of link arrangement in a signaling link set.

LPMIN Options:
 Random Order

 Selected On SLS_BIT0-1-2
 Selected On SLS_BIT1-2-3
 Cyclic Selected On Link No.
Recommended value: Random Order
Determines whether signaling links are sorted manually, default:

MANUAL
Need Not Manual.
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"
4. Create routing configuration to destination

 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
ID ID of the signaling destination office, which is also the adjacent office ID in

the result of the SHOW ADJOFC command, range: 1-65534.
OFCNM Alias of the signaling destination office, range: 0-50 characters
NAME Alias of the signaling office, range: 1-50 characters.
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
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.
3.1.2 Provision Parameters

These configurations are not related to subscribers’ subscription. It is not
applicable for provision interface.
3.2 Load Balancing on Signaling access layer for SIGTRAN

The hierarchical structure of signaling configuration for Sigtran is:
Routing configuration for destination (SIO locate AS configuration)
|_______M3UA routing configuration (notes 1)
|_______ AS configuration
|_______ASP configuration
|_______SCTP association configuration.
|_______define the HLR SMP
module in system
Note1:
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.
Load balancing on signaling access layer is achieved by sender party. Message

flow for HLR originating message is portrayed in following figure:
Figure 6 Message flow for HLR originating message

Interface Unit
MSC/VLR/SGSN SMP CMP
(GE)
Selects one SMP by

round-robin way
Outgoing signaling
1) Select AS by checking M3UA

routing configuration with
Outgoing message destination address
2) dispatch message inter AS in
Outgoing message the selected MU3A routing Path
In order to route traffic message to right destination and achieve load balancing
intra the signaling group, USPP shall:
 Locate the M3UA routing configuration by destination address.
 Since each M3UA could supports up to 4 AS connection, USPP could achieve

load balancing by equally dispatching message to 4 AS connection.
 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.

As constructing a building, we shall configure the Sigtran configuration from the
bottom up:
 Define HLR SMP module in system
 Create SCTP associations.
 Create ASP configuration.
 Create AS configuration, the relationship between ASP and AS are builded in

this step. For the concern of system availability, for each AS, there shall be
at least two ASPs , two link groups could work in load-sharing mode or
active standby mode .
 Create M3UA routing configuration, at most 4 AS are bound to same M3UA

routing path, all AS in same M3UA routing path work in load-sharing mode.

 Create SIO locate AS Configuration (routing configuration for destination), in

this step, the relationships between destination and M3UA routing path are
created.
following part:
1. Create module
 Command
ADD
MODULE:LOC=,MTYPE=,[MODULE=],[BTYPE=],[BKMODE=],[NENO=],[NA
ME=],[DESC=];
 Parameters
Table 6 parameters description for creating module
Location of the module in the system
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).
iii. Click Add.
iv. Click OK.
Module Type
Refer to the Module Type dialog box that appears by clicking the text
MTYPE
box for available options.
ID of the module, unique in the NE, range: 1-65534.

MODULE
Type of the board where the module is located, options:

BTYPE l Data Processing Blade A (DPBA) : (Default) Select this option
when the DPBA2 blade is used.

l Data Processing Blade B (DPBB): Select this option when the
DPBBx blade is used.
l PC: In general, it is not used.
Backup mode of this module, option: Without Backup and One

BKMODE Plus One Backup

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.
User-defined short description of the module, range: 0-512

DESC
characters.
 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
Global number of the SCTP link, range: 1-2048.

ID

NAME Alias of the M3UA SCTP link, range: 1-50 characters
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.
Two application attributes are available: as Server or as Client.
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).
[Port No.]+[IP Address] constitute a link. Different links should be

configured with different port numbers without any conflicts. IP
LOCADDR
address of the local end of the link, which is also the opposite-end IP
address of the remote office. Enter the IP address of the local-end loopback
port according to the networking plan
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
IP address of the opposite end of the link, which is also the
REMADDR local-end IP address of the remote office.
Enter the IP address of the opposite-end loopback port 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.
Stream is a unidirectional logical channel in the link. Data on the same

INSTRM stream can be transmitted in a certain order. It should be consulted by
technical personnel on the two ends. Range: 1-17, default: 16
(recommended).
Stream is a unidirectional logical channel in the link. Data on the same

OUTSTRM stream can be transmitted in a certain order. It should be consulted by
technical personnel on the two ends. Range: 1-17, default: 16

(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
technical personnel on the two ends. Range: 1-10, default : 5
(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,
The initial time-out value of the retransmission timer, range:

INITRTO
10-3000, default: 100 (recommended).
The SCTP end point sends the HEARTBEAT block periodically
HB to monitor the accessibility of the idle destined transmission
address on the remote end. This parameter sets the interval for sending
the HEARTBEAT block. Range: 10-6000, default: 500 (recommended).
FIXNH Default: Nonsupport and unfix next hop (recommended).
Controls the maximum retrying times of SCTP association on all channels.

SCTPMAXRTRYNUM When this value is exceeded, SCTP association stops and transmission
failure is reported. Range: 1-20, default: 10(recommended).
The length of the acknowledgment delay timer, range: 0-20,

DELAYACK
MAXBURST Range: 1-127. The default value 4 is recommended.
PRIMARYPATH Options include:

 Remote IP 1 (default and 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.
Set it in accordance with your networking plan.
Range: 0-15, default: 3.

BREAKTIME
When the count of message retransmissions reaches this
threshold, the SCTP fast trace detection for this path is initiated.
PDTHRESH
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.
Set it in accordance with your networking plan.

PLTIMER

MPPLTHRD
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.

CB
Options include:
 NULL (default)
QOSTYPE  DSCP
 TOS
QOSVALUE Range: 0-255. Set it in accordance with your networking plan.
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

Table 8 parameters description for creating ASP configuration

ASP ID, It is numbered from 1. It is recommended to use the same ID with

ID
SCTP. Range: 1- 2048.
NAME User-defined name of this ASP, range: 1-50 characters
Associated with SCTP ID specified in the Adding an M3UA

ASSOCID
SCTP Link section, range: 1-2048.
Used to set whether the ASP has a self-loop. The self-loop

ISLOOP setting is used in system test. The default value Not Self Loop is
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
A unique ID of the AS. It is recommended to use the same ID with

ID
ASP, which is easy to remember. Range: 1-640.
NAME User-defined name of this AS, such as AS1, range: 0-50 characters
ASPID Associated with the ASP ID specified in Adding an M3UA

ASP, range: 1-2048.
Determines whether the routing context exists. The default value

EXISTCTX
Routing Context Doesn't Exist is recommended.
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
but it must be consistent on two ends. Range: 0-4294967295.
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
to SGP and the other office is set to ASP.

ASTAG If the upper signaling messages carried by the AS are only
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
IPSP Client. In this case, the client/server configuration must be
consistent with that in M3UA SCTP association configuration.
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
configured according to the current network protocol type
A supported service mode. Options include Over-ride mode and
Load Share mode.
In the override mode, it is only required to set one ASP in the

ASMD activated status.
In the load sharing mode, it is required to set N ASPs in activated
status and other K ASPs in deactivated (backup) status. For more
details about N and K, refer to RFC4666 1.4.4.1

The number of ASPs in the activated status when the system works
in the load sharing mode, range: 0-16.

NVAL
It should be less than the actual number of ASPs. It is recommended
to set it to the default value 1.
 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
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.
The AS corresponding to the ASP that is in the activated status, identifies

ASID1 the first AS when there are multiple Application Servers, range: 1-640,
selected from the existing AS IDs.
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

no configuration when the third AS does not exist
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
accordance with the networking plan.
 Example
ADD M3UART:ID=1,ASID1=90;
One M3UA routing record with ID=1 is created; it only uses one AS as
routing path.
6. SIO locate AS Configuration
 Command
ADD SIOLOCAS:NAME=,OFCID=,SIO=,[OPOFCID=],RT1=,[RT2=];
 Parameters
Table 111 parameters description for creating SIO locate AS configuration
NAME User-defined name of this configuration item, such as SIOLOCAS, range:

1-50 characters.
The adjacent office ID corresponding to the destination signaling point of

M3UA, range: 1-65534.
OFCID
It is required to associate it with Office ID specified in Adjacent
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.
Office ID corresponding to the originating signaling point of M3UA, range:

0-65534. It is 65534 by default. If it is set to 0 (local office), then the
OPOFCID message starts from the local office. At this time, the routing context
selects routes according to DPC+NET+OPC+SIO.
RT1 M3UA static route of the located AS, associated with M3UA Static Route ID
in Create M3UA Static Route Configuration, range: 1-640.
RT2 Range: 0 to 640. It is 0 by default, which means there is no M3UA Static

Route 2.
 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.

3.3 Load Balancing on Service processing layer

Load balancing on service processing layer is achieved by SMP for received
messages and by CMP for HLR originating messages.
For received message, SMP receives signaling message from physical media and
checks the configuration of module to fetch the list of all HLR CMP modules.
With the list of HLR CMP module, SMP uses round-robin mechanism to
dispatches message to each CMP with equal quantity.
For HLR originating messages, HLR CMP uses configuration of module to fetch
the list of all HLR SMP modules. With the list of HLR SMP module, HLR CMP
dispatches message to SMP by using round-robin mechanism.
During load balancing procedure, the only configuration SMP and CMP needs

are configuration of module.

Detailed information for create module in USPP system is :
1. Create module
 Command
ADD
ME=],[DESC=];
 Parameters
iii. Click Add.
iv. Click OK.
Module Type
MTYPE Refer to the Module Type dialog box that appears by clicking the text box
for available options.

MODULE
 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.

 PC: In general, it is not used.
Backup mode of this module, option: Without Backup and One Plus One
BKMODE Backup

DESC
characters.
 Example
ADD MODULE:LOC=1-2-3,MTYPE="CMP_HLR",MODULE=3;
The application going to running on this module is HLR CMP, the
module number is 3.

These configurations are not related with subscribers’ subscription. It is not
3.4 Load balancing on partitioning layer

All functions of Partition layer resides on UAGW and IDSA module. For 3rd FE, its
request is sent to UAGW, and UAGW invoke IDSA to process the 3rd FE request.
For USPP FE, its request is sent to IDSA directly. Thus load balancing service
logics include:
1. Service logic for 3rd FE to select UAGW instance.
After UAGW instance is created, UAGW instance is automatically ready to share
traffic load from 3rd FE. An Dispatcher receive request from 3rd FE and apply the
service logic to dispatch request to appropriate UAGW instance. Details are
shown in “ZXUN UDS Data Access Feature Guide.docx” (Single-point Access).
Related configuration parameters are listed:

UAGW instance configuration

|_______ Module configuration
Dispatch of Single-point Access Configuration
The meaning of upper configuration is
 UAGW instance configuration

This configuration defines the parameters used by UAGW instance such as IP
address, etc. UAGW instance provides the third party FE access, routing and
external data source access functions. When the third party FE needs to
access UDS data or the external data source is to be accessed, there is a
need to add UAGW instance.
 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.
 Dispatch of Single-point Access configuration:

Configure the dispatch rule of single-point access which UAGW instances are
able to process request from 3rd FE.
2. Service logic for UAGW and USPP FE to select IDSA instance.
After IDSA instance is created and added into IDSA cluster, IDSA instance is
automatically ready to share traffic load dispatched to current IDSA cluster.
When IDSA is alive it will report its’ running state(able or unable for data
processing , master or slave and CPU utilization) to all connected USPP Fes and
UAGWs for each time interval, or IDSA will immediately broadcast its running
state after its state is changed.
In the view of USPP FE and USPP, checks the configuration of UDS:
 Locate the IDSA group by subscriber identities.
 Fetch the IDSA cluster included in IDSA Group.
 Locate the IDSA cluster by checking subscriber distribution plan inner IDSA
group by user identities

 Before UAGW or USPP FE routes traffic message to IDSA instances, UAGW

or USPP FE shall know the running state (normal or abnormal) and CPU
utilization for IDSA instances. If any IDSA instance is dead or unable to
process traffic, FE shall remove them from eligible list.
UAGW and USPP FE shall repeat upper procedure to remove all unavailable IDSA
instances in the IDSA cluster.
When UAGW or USPP FE dispatches traffic messages to eligible IDSA instances,
it shall follow these rules:
 Write operation must be routed to primary instance, if there is no primary

instance, the process shall be ended with the result code set to database
error.
 Read operation could be dispatched to all available IDSA instances. The

proportion for each IDSA instance is mainly based on pre-configured
dispatching ratio for each IDSA instance and utilization of CPU is also used
by sender party to make fine-tune on dispatching. UAGW or USPP FEs will
dispatch message by strictly following ratio. If there are two IDSA instances
with dispatching ratio is 1:2 , then 33.3% volume shall be routed to instance
1, and others 66.6% shall be routed to instance2. When CPU utilization is
included, UAGWs or USPP FEs launch regulation to avoid overload
protection by decreasing the volume to IDSA instance with higher CPU
utilization and increasing volume to IDSA instance with lower CPU
utilization.
With the DSA instance and cluster configuration, the state broadcast function on
DSA (PDSA, IDSA) and sender load balancing function on UAGW and USPP FE are
automatically activated.
IDSA group configuration
|_______DSA cluster configuration
| |_______DSA instance configuration
| |_______Module configuration
|_______ Identities routing resource distribution plan on IDSA group
|_______ Routing information distribution plan intra IDSA group
The meaning of upper configuration is
 IDSA group configuration:

IDSA group is the aggregation of IDSA cluster. All IDSA cluster in same IDSA
group has routing information for different subscribers.
 Identities routing resource distribution plan on IDSA group:

Each group is assigned with a group of identities resource. The identities
could be subscribers’ logical number such as MSISDN or physical number
such as IMSI. There is no DSA groups sharing the same identities resource,
with configured information above FEs are able to locate the IDSA group by
using given identity.
 Routing information distribution plan intra IDSA group

One IDSA group may include several IDSA cluster, this configuration
determines that how subscribers routing information is distributed between
IDSA clusters: one IDSA cluster is assigned with a set of mapping code
(derived from subscribers’ identities, usually it is the last 3 digit of
identities).
With given identities type and identity, FE and UAGW (for third party access)
can derive mapping code, and then fetch the IDSA cluster by this
configuration.
 DSA cluster configuration

DSA cluster configuration defines the DSA cluster and DSA cluster members
(DSA instance)
DSA instance configuration
This configuration defines the parameters used by DSA instance such as DSA
type (IDSA or PDSA), IP address, etc.
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.

the bottom up:

 Create Module
 Create UAGW instance and couple the instance with module number.
 Configuring the Dispatch of Single-point Access.
 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
 Grant mapping code information to each IDSA cluster.
 Grant identities resource to IDSA group

following part:
1. Create module
 Command
ADD
ME=],[DESC=];
 Parameters
iii. Click Add.
iv. Click OK.
MTYPE Module Type


MODULE
 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.
 PC: In general, it is not used.


DESC
characters.
 Example
module number is 3.
2. Create UAGW instance
 Command
ADD UAGW: UAGWNODEID=, BNO=, MODULE=, INTIP=, [INTPORT=],
IPTYPE=, EXTIP=, [EXTPORT=], NAMINGCONTEXTS=, SMALLPAGESIZE=,

SMALLPAGENUM=, BIGPAGESIZE=, BIGPAGENUM=, [MAXMSGNUM=],

[SOAPPORT=], [NAME=];
 Parameters
Table 144 parameters description for UAGW
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.
Module No. corresponding to this UAGW node, range: 130 to 300,

MODULE
consistent with the module No. corresponding to the DSA node.
The IP address used for this UAGW node to communicate with each
INTIP
module in the office.
Internal port No. of this UAGW node in the office, default: 5057, range:
INTPORT
1024-65535.
The IP address type used by this UAGW node for inter-office
IPTYPE
communication, options: IPv4 (default) and IPv6, recommended: IPv4.
The IP address used by this UAGW node for inter-office communication.
EXTIP In the intra-office networking mode, the external IP should be the same
with the internal IP.
EXTPORT External port No. of this UAGW node, default: 5057, range: 1024-65535.
The root node on the DIT tree, range; 1-39 characters.
NAMINGCONTEXT If the BaseDN is set to dc=zte,de=com, the Root is
dc=zte,de=com.
SMALLPAGESIZE The size of the small page in the memory pool, range: 1-16, default: 4.
The number of small pages during creation of the memory pool,
SMALLPAGENUM determined according to the processing capability of the system, range:
1-10000, default: 5000.
BIGPAGESIZE The size of the big page in the memory pool, range: 32-128, default: 64.
The number of big pages during creation of the memory pool, determined
BIGPAGENUM according to the processing capability of the system, range: 1-1000,
default: 500.
The maximum number of messages that the directory service is allowed to
MAXMSGNUM process, range: 0-10000, default: 5000.
If this value is exceeded, the system returns an error message.
The port that the system uses to receive the SOAP messages. The system
SOAPPORT
intercepts the SOAP messages on this port. Range: 0-65535.
Alias of this UAGW node, indicates the use of the node so as for easy
NAME
recognition during maintenance, range: 0-50 characters
 Example

ADD UAGW: UAGWNODEID=11040, BNO=11, MODULE=40,

INTIP="192.168.1.2", INTPORT=60040, EXTIP="10.10.1.2",
EXTPORT=50040, NAMINGCONTEXTS="dc=zte,dc=com",
SMALLPAGESIZE=4, SMALLPAGENUM=4000, BIGPAGESIZE=32,
BIGPAGENUM=1000, SOAPPORT=10080;
3. Configuring the Dispatch of Single-point Access
 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
IP address of the opposite-end interface, IPV4 type

NETPRE
Network mask of the opposite-end interface, IPV4 type, for example,

MASK 255.255.0.0.
Interface IP address of the SIPI unit in the local office, IPV4 type.
NEXTHOP
Parameter format: Subsystem No.-Module No. –Unit No.-Sub-Unit No.-Port

INTERFACE No.
Range: 1-1024.
TUNNELID The default value (null) is recommended.
PPINTERFACE Parameter format: Subsystem No.-Module No. –Unit No.-Sub-Unit No.-Port

No.
Parameter format: Subsystem No.-Module No. –Unit No.-Sub-Unit No.-Port

MPINTERFACE No.
It represents the reliability of a route protocol. The smaller the distance

value, the higher the reliability. In case of two or more routes of different
route protocols to a same destination, the router selects an optimal route
according to the management distance.
DISTANCE
Range: 1-254.
The default value is recommended.
Default: No.
Because the static route has no detection mechanism, administrator

BFDDETECT intervention is required when a fault occurs in the network. Enabling the
EFD detection can detect the link where the static route is located by using
the BFD session. The route management system determines whether the
static route is available according to the BFD session status.
Name of VRF table, range: 0-30 characters.

VRFNAME The default value is recommended.
 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

remote port range is 65535; module number and times is 130-1.

4. Create IDSA instance
 Command
ADD
DSANODE:DSANODEID=,BNO=,MODULE=,MODULETYPE=,[INTIP=],[INTP
ORT=],[IPTYPE=],[EXTIP=],[EXTPORT=],[NAME=];
 Parameters
Table 166 parameters description for IDSA
ID of the DSA node to create, range: 1-65000.
The ID of each DSA node on all the offices in ZXUN USPP (HLR) is unique.
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
DSANODEID 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
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
PDSA: Profile DSA node

SAVE: DST 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
In general, it is equal to 60000+module number.
IP address type of this DSA node for inter-office communication, options:

IPTYPE IPV4 or IPV6.
IP address of this DSA node for inter-office communication. Set it in

EXTIP
In case of the intra-office networking solution, the external IP address
should be identical with the internal IP address.
Port No. of this DSA node for external access, default: 5057, range:
1024-65535.

EXTPORT
In case of the intra-office networking solution, the external port No. should
be identical with the internal port No.
Alias of this DSA node, range: 0-50 characters.

NAME For convenience of understanding, the alias may be set in the
OfficeID-DSA node type-ModuleID format, for example, 29-pdsa-3.
 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.

5. Create IDSA cluster
 Command
ADD
DSA:DSAID=,NAME=,DSATYPE=,[IDTYPE=],[BNO=],[BNO2=],[NOELECT=];
 Parameters
Table 177 parameters description for IDSA cluster
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.
The ID of the DSA cluster is composed of the No. 1 home office ID (1 to 2

DSAID
digits) and the smallest module No. of the node in the DSA cluster in the
home office (three digits, if the number is less than three digits, leading
zeros are added.) The value range of the home office ID is as same as the
one of the deployed office ID.
NAME Alias of this DSA cluster, range: 1-50 characters.
Type of the DSA cluster, options:
 Identity DSA (IDSA)
 Profile DSA (PDSA)

DSATYPE
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.
Required if this is an IDSA cluster.
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 primary home office, whose monitoring center (DMCC) manages

this DSA cluster, range: 0-254. For data backup or disaster recovery, the
nodes in the same DSA cluster are distributed in different offices. The DSA
cluster selects an active node through the DMCC during startup. This
configuration item determines to which office's monitoring center the DSA
BNO cluster initiates the selection upon startup
of the DSA cluster.
In most cases, this ID is configured to the ID of the office where the

expected active node is located. Set it in accordance with the networking
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
Whether to allow the monitoring center to select a new primary node in

NOELECT case of failure in the primary node. It must be set to Allow to elect PDS by
DMCC or Allow to elect by the First DMCC only. Forbid to elect PDS by
DMCC is only used to locate faults
 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

ID of the DSA node in the DSA, range: 1-65000.
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.
For two DSA nodes of a DSA cluster that is working in a load-sharing or

NODELEV
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.
Distribution proportion of messages, i.e. percentage of messages

distributed to this DSA node, range: 1-100
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.

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 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
ID of an IDSA cluster belonging to the IDSA group to be created, range:

1-65000.
DSAID Select it from the IDs of the existing DSA clusters whose type is set to IDSA
in DSA cluster creation.
ID of the IDSA group to be created, range: 1-65000.

DSAGRPID
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
ID of this distribution configuration item, range: 1 to 65535.

SN
Type of the number segments to be distributed to the IDSA cluster.
Multiple number segments of different types may be distributed to one

NUMTYPE IDSA cluster.
Refer to the drop-down list for available options.
Beginning mapping code of a mapping code section to be distributed to the

BEGIN IDSA cluster, range: 0 to 999, default: 0.
Ending mapping code of a mapping code section to be distributed to the

IDSA cluster, range: 0 to 999, default: 999.
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.
Alias of this number distribution configuration item for easy

NAME
recognition, string type, 0 to 50 characters

 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
ID of this physical number segment, range: 0 to 65535.

SN
In general, it starts from 1.
Type of the physical number segment.

NUMTYPE Select one type from the drop-down list. Set it in accordance
The beginning number of the physical number segment, string
type, range: 1 to 31 digits.

BEGIN
The number segment must not overlap an existing number
segment. Set it in accordance with the networking plan
The ending number of the physical number segment of the
administrative domain, string type, range: 1 to 31 digits.

END
segment. Its length must be identical with the one of the
beginning number. Set it in accordance with the networking
plan.
ID of the IDSA group that the physical number segment is
distributed to, range: 1 to 65000.

DSAGRPID
Select it from the existing IDSA group IDs configured in
IDSA Group Configuration. Set it in accordance with the

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
ID of this physical number segment, range: 0 to 65535.

SN

The beginning number of the physical number segment, string

BEGIN
segment. Set it in accordance with the networking plan
The ending number of the physical number segment of the
administrative domain, string type, range: 1 to 31 digits.

END
segment. Its length must be identical with the one of the

beginning number. Set it in accordance with the networking
plan.
ID of the IDSA group that the physical number segment is

DSAGRPID Select it from the existing IDSA group IDs configured in
IDSA Group Configuration. Set it in accordance with the
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.

3.5 Load Balancing on Storage layer

All functions of storage layer reside on PDSA module. After PDSA instance is
created and added into PDSA cluster, PDSA instance is automatically ready to
share traffic load dispatched to current PDSA cluster.
When PDSA is alive it will report its’ running state(able or unable for data
processing , master or slave and CPU utilization) to all connected IDSA instances
for each time interval, or PDSA will immediately broadcast it running state after
its’ state is changed.
In the view of IDSA instance, IDSA instance checks the configuration of UDS:
 Locates PDSA cluster by routing information in current IDSA database, this

routing information is created after subscribers is added into database.

 Fetch all PDSA cluster members by checking DSA cluster configuration.
 Before FE route traffic message to PDSA instances, IDSA instance shall

knows the running state (normal or abnormal) and CPU utilization for IDSA
instance. If any PDSA instance is dead or unable to process traffic, IDSA
instance shall remove them from eligible list.
Sender IDSA instance shall repeat upper procedure to remove all unavailable
PDSA instances in the PDSA cluster.
When IDSA instance dispatch traffic messages to eligible PDSA instances, it shall
follow these rules:
 Write operation must be routed to primary instance, if there is no primary

instance, the process shall be ended with the result code set to database
error.
 Read operation could be dispatched to all available PDSA instances. The

portion for each PDSA instance is mainly based on pre-configured
dispatching ratio for each PDSA instance and utilization of CPU is also used
by sender party to make fine-tune on dispatching. IDSA instances will
dispatch message by strictly following ratio. If there are two PDSA instance
with dispatching ratio is 1:2 , then 33.3% volume shall be routed to instance
1, and others 66.6% shall be routed to instance2. When CPU utilization is
included, FEs launch regulation to avoid overload protection by decreasing
the volume to IDSA instance with higher CPU utilization and increasing
volume to IDSA instance with lower CPU utilization.
With the DSA instance and cluster configuration, the state broadcast function on
DSA (PDSA, IDSA) and sender load balancing function on IDSA are automatically
switched on.
DSA group configuration
|_______DSA cluster configuration
| |_______DSA instance configuration
| |_______Module configuration
|_______ Identities resource distribution plan on PDSA group
The meaning of configuration is :
 DSA group configuration:

PDSA group is the aggregation of PDSA cluster. All PDSA cluster in same
PDSA group has profile information for different subscribers.
 Identities resource distribution plan on PDSA group:

Each group is assigned with a group of identities resource. The identities
could be subscribers’ logical number such as MSISDN or physical number
such as IMSI. There is no DSA groups share same identities resource. With
this information, IDSA instances will has the ability to locate the PDSA group
by using given identity during add subscriber procedure.
 DSA cluster configuration

DSA cluster configuration defines the DSA cluster and DSA cluster members
(DSA instance)
 DSA instance configuration

This configuration defines the parameters used by DSA instance such as DSA
type (IDSA or PDSA), IP address, etc.
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.

the bottom up:
 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
 Grant identities resource to IDSA group

following part:

1. Create module
 Command
ADD
ME=],[DESC=];
 Parameters
iii. Click Add.
iv. Click OK.
Module Type
MTYPE

MODULE
l Data Processing Blade A (DPBA) : (Default) Select this option
when the DPBA2 blade is used.

BTYPE l Data Processing Blade B (DPBB): Select this option when the
DPBBx blade is used.
l PC: In general, it is not used.



DESC
characters.
 Example
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
ID of the DSA node to create, range: 1-65000.
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
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,
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.
IDSA: Identity DSA node

MODULETYPE
PDSA: Profile DSA node
SAVE: DST node
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
IP address type of this DSA node for inter-office communication,

IPTYPE
options: IPV4 or IPV6.

IP address of this DSA node for inter-office communication. Set it in

EXTIP
In case of the intra-office networking solution, the external IP address
should be identical with the internal IP address.
Port No. of this DSA node for external access, default: 5057, range:
1024-65535.

EXTPORT
In case of the intra-office networking solution, the external port No.
should be identical with the internal port No.
Alias of this DSA node, range: 0-50 characters.

NAME For convenience of understanding, the alias may be set in the
OfficeID-DSA node type-ModuleID format, for example, 29-pdsa-3.
 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
DSAID 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.
The ID of the DSA cluster is composed of the No. 1 home office ID (1 to 2

digits) and the smallest module No. of the node in the DSA cluster in the
home office (three digits, if the number is less than three digits, leading
zeros are added.) The value range of the home office ID is as same as the
one of the deployed office ID.
NAME Alias of this DSA cluster, range: 1-50 characters.
Type of the DSA cluster, options:
 Identity DSA (IDSA)
 Profile DSA (PDSA)

DSATYPE
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.
Required if this is an IDSA cluster.
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
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 primary home office, whose monitoring center (DMCC) manages

this DSA cluster, range: 0-254. For data backup or disaster recovery, the
nodes in the same DSA cluster are distributed in different offices. The DSA
cluster selects an active node through the DMCC during startup. This
BNO configuration item determines to which office's monitoring center the DSA
cluster initiates the selection upon startup
of the DSA cluster.
In most cases, this ID is configured to the ID of the office where the

expected active node is located. Set it in accordance with the networking

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
Whether to allow the monitoring center to select a new primary node in

NOELECT case of failure in the primary node. It must be set to Allow to elect PDS by
DMCC or Allow to elect by the First DMCC only. Forbid to elect PDS by
DMCC is only used to locate faults
 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
ID of the DSA node in the DSA, range: 1-65000.
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.
Distribution proportion of messages, i.e. percentage of messages

distributed to this DSA node, range: 1-100
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.
Alias of this DSA member for easy recognition, 0-50 characters.
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

ADD IDDSAGRP: DSAID=,DSAGRPID=,[NAME=];
 Parameters
Table 287 parameters description for creating PDSA group members
ID of an IDSA cluster belonging to the IDSA group to be created, range:

1-65000.
DSAID Select it from the IDs of the existing DSA clusters whose type is set to IDSA
in DSA cluster creation.
ID of the IDSA group to be created, range: 1-65000.

DSAGRPID
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
Serial number of this physical number segment, range: 0 to 65535.

SPNID

with the networking plan
BEGIN The beginning number of the physical number segment, string

segment. Set it in accordance with the networking plan.
The ending number of the physical number segment of the administrative

domain, string type, range: 1 to 31 digits.
END The number segment must not overlap an existing number
segment. Its length must be identical with that of the beginning
number. Set it in accordance with the networking plan.
ID of the PDSA group that the physical number segment is

DSAGRPID
Select it from the existing PDSA group IDs specified by the ADD DSAGRP
command (for details, refer to 4.5.3 Adding a
PDSA Group). Set it in accordance with the networking plan.
NAME Alias of the configuration item, range: 0 to 50 characters
 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.

These configurations are not related with subscribers’ subscription. It is not
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
 Service processing level

Table 310 statistics counter in service processing level
SN NAME Description
1 Times of Attempted Request for Count of routing attempts.
Routing Information
2 Times of Attempted Providing Count of service requests
Roaming MAP_PROVIDE_ROAMING_NUMBER that HLR sends
to VLR.
3 Times of Attempted Location Count of location update attempts.
Update
4 Times of Attempted CancelLocation Count of location cancellation attempts.
Request
5 Times of Attempted Inserting Count of attempts to insert subscriber data.
Subscriber Data
6 Times of Attempted Delete Count of attempts to delete a subscriber’s data.
Subscriber Data
7 Times of attempted sending Count of attempts to send authentication
authentication information information.
8 Times of Attempted Request for Count of requests for MS purge.
MS Purge
9 Times of Successful Retrying The number of times that the CSFB receives a reply
Providing Roaming after resending a PRN request in a
Number statistical measurement period.
10 Times of Attempted Sending Count of attempts for location service routing.
Routing Information for
LCS
11 Times of Attempted Any Time Count of attempts for interrogation at any time.
Interrogation

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.
 Partition layer & storage layer

Table 321 statistics counter on BE
SN NAME Description
1 Count of LDAP Add Action Count of LDAP add messages received by IDSA.

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

6 Definitions and Abbreviations

Abbreviations used in this document are listed in below.
Abbreviations Full Characteristics

AS Application Server
ASP Application Server Process
HLR Home Location Register
MSC Mobile Switching Centre
MTP3 Message Transfer part level3
SCTP Stream Control Transmission Protocol
SGSN Serving GPRS Support Node
Sigtran Signaling transport
SS7 Signaling system #7
VLR Visitor Location Register

ZXUN USPP Load Balancing

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

ZXUN USPP Load Balancing

Încărcat de

Drepturi de autor:

Formate disponibile

Load Balancing

ZTE Confidential Proprietary © 2016 ZTE Corporation. All rights reserved. II

Version Date Author Approved By Remarks

V1.00 2012-06-20 Not open to the Third Party

V1.01 2012-12-20 Not open to the Third Party

© 2016 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary © 2016 ZTE Corporation. All rights reserved. 1

2 Functionality Description and Scenarios ................................................................ 6

3 Functional Description ............................................................................................ 10

ZTE Confidential Proprietary © 2016 ZTE Corporation. All rights reserved. 2

5 Related Features ...................................................................................................... 66

6 Definitions and Abbreviations ................................................................................ 67

ZTE Confidential Proprietary © 2016 ZTE Corporation. All rights reserved. 3

Table 15 parameters description for dispatcher rule ...................................................................... 41

ZTE Confidential Proprietary © 2016 ZTE Corporation. All rights reserved. 4

1.1 General Description

ZXUN USPP provides four layers load-balance mechanism:

 Service processing layer: Signaling interface board assigns the signaling

 Partitioning layer: IDSA cluster includes multi-nodes to store the same ID

1.2 Involved Net Elements

Net Element Interface Related Messages

ZTE Confidential Proprietary © 2016 ZTE Corporation. All rights reserved. 5

UDS Ud LDAP Search, Add, Modify and compound.

1.3 Included Features

This specification include following features:

 ZWF-10-42-008 Load Balancing

2 Functionality Description and Scenarios

2.1 Load Balancing on Signaling access layer

The load sharing on signaling access layer is based on the association

When MSC/VLR or SGSN connects with HLR, signaling channels shall be

In order to achieve redundancy on signaling network, a signaling channel (or link)

ZTE Confidential Proprietary © 2016 ZTE Corporation. All rights reserved. 6

Interface Unit Interface Unit

For messaes originated by MSC/VLR or SGSN, it is the responsibility for MSC/VLR

For messages originated by HLR, it is the responsibility for HLR to implement

2.2 Load Balancing on Service processing layer

 SMP module is responsible for protocol processing, including

ZTE Confidential Proprietary © 2016 ZTE Corporation. All rights reserved. 7

 Interface unit is responsible for forwarding signaling message which is

The different modules topology is referred to the following：

CMP1 CMP2 CMP3 CMP4 CMP5 CMP n

SMP1 SMP2 SMP3 SMP n

interface Unit interface Unit

Signaling Link Signaling Link

ZTE Confidential Proprietary © 2016 ZTE Corporation. All rights reserved. 8

CMP1 CMP2 CMP3 CMP4

2.3 Load Balancing on Partitioning layer

ZTE Confidential Proprietary © 2016 ZTE Corporation. All rights reserved. 9

The proportion of traffic for each eligible candidate is mainly based on

2.4 Load Balancing on Storage layer

3.1 Load Balancing on Signaling access layer for SS7

The hierarchical structure of signaling configuration for SS7 is:

Routing configuration for destination

|_______signaling routing path configuration (note1)

|_______signaling link group (note2)

|_______Configuration of signaling link

ZTE Confidential Proprietary © 2016 ZTE Corporation. All rights reserved. 10

Figure 5 Message flow for HLR originating message

Selects one SMP by

1) Select signaling group by

In order to route signaling message to right destination and achieve load

3.1.1 Configuration Parameters

ZTE Confidential Proprietary © 2016 ZTE Corporation. All rights reserved. 11

 Create all signaling links towards destination network elements (MSC/VLR,