ZXUN USPP

ZXUN USPP
Universal Subscriber Profile Platform

Training Manual
Basic Data Configuration
ZTE UNIVERSITY
ZTE University, Dameisha
YanTian District, Shenzhen,
P. R. China
518083
Tel: (86) 755 26778800
Fax: (86) 755 26778999
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2010 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of
this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPO-
RATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATION
or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions are dis-
claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-
fringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the
information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject
matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,
the user of this document shall not acquire any license to the subject matter herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Publishing Date (MONTH/DATE/YEAR) : 08/09/2010

Contents
ZXUN USPP Basic Data Configuration ........................... 1

1 Introduction to UDS Configuration ............................ 2
1.1 UDS Configuration Flow .......................................................... 2
1.2 Uploading Configuration Data on EMS....................................... 3
2 OMM Access Configuration ........................................ 7
2.1 Loading the License File.......................................................... 7
2.2 Creating a USPP .................................................................... 9
2.3 Creating a Network Element Agent..........................................10
2.4 Starting a Network Element Agent ..........................................12
2.5 Updating USPP .....................................................................13
2.6 Validating the License ...........................................................14
2.7 Uploading the License to OMM Server......................................15
2.8 Adding a Network Element on OMM.........................................16
2.9 Adding a USPP Physical Office ................................................18
2.10 Loading the Schema............................................................18
3 UDS Device Configuration........................................ 21
3.1 Adding a Database Node .......................................................21
3.2 DSA Node Configuration ........................................................24
3.2.1 Adding a DSA Node ......................................................24
3.2.2 Setting DSA Node Options .............................................26
3.2.3 Setting DSA Node Storage Configuration .........................28
3.3 DSA Configuration ................................................................30
3.3.1 Adding a DSA ..............................................................30
3.3.2 Adding a DSA Member ..................................................32
3.3.3 Setting DSA Options .....................................................34
3.3.4 Adding Subscriber Table Capacity ...................................35
3.4 DSA Group Configuration .......................................................37
3.4.1 Adding an ID DSA Group ...............................................37
3.4.2 Distributing Numbers to an ID DSA.................................38
3.4.3 Adding a P DSA Group ..................................................40
3.5 UDS Parameters Configuration ...............................................41
3.5.1 Setting UDS Load Control ..............................................41
3.5.2 Setting UDS Parameters ................................................42
3.5.3 Setting the Capacity of a Configuration Table ...................46
3.5.4 Setting the Capacity Scale of a Subscriber Data
Table .............................................................................................47
3.6 Adding a DUA Node ..............................................................49
3.7 Adding a Monitoring Center....................................................50
4 Introduction to Physical Data Configuration............ 53
4.1 Physical Configuration Flow ....................................................53
4.2 Uploading Configuration Data .................................................55
5 Physical Configuration............................................. 57
5.1 Concepts on Physical Configuration .........................................57
5.2 Adding a Rack ......................................................................59
5.3 Adding a Shelf .....................................................................60
5.4 Adding a Unit .......................................................................61
5.5 Adding a Module...................................................................63
5.6 Configuring TCP Transfer for TIPI ............................................65
5.7 Setting the IP of the OMP module ...........................................67
6 Server Node Configuration ...................................... 69
6.1 Adding a DBIO/DSA/DST Node ...............................................69
6.2 Setting the Connection Between a Service Server Node and
the OMM ........................................................................................70
7 Office Configuration................................................. 73
7.1 Creating Signaling Points of the Local Office .............................73
7.2 Configuring the Local Office ...................................................75
7.3 Adding an Adjacent Office......................................................77
8 Signaling Configuration ........................................... 83
8.1 SIGTRAN Configuration .........................................................83
8.1.1 Adding an SCTP Basic Connection ...................................83
8.1.2 Adding an ASP .............................................................87
8.1.3 Adding an AS...............................................................88
8.1.4 Adding an M3UA Static Route.........................................90
8.1.5 Adding an SIO Location AS ............................................91
8.2 MTP Configuration ................................................................93
8.2.1 Adding a Signaling Link Set ...........................................93
8.2.2 Adding an E1 Signaling Link...........................................95
8.2.3 Adding a Signaling Route...............................................98
8.2.4 Adding a Signaling Office............................................. 100
8.3 SCCP Configuration............................................................. 102
8.3.1 SCCP Related Concepts ............................................... 102
8.3.2 Adding a GT Translation Selector .................................. 102
8.3.3 Adding GT Translation Data.......................................... 105
9 IP Stack Configuration ...........................................111
9.1 Checking IPv4 Interface Information ..................................... 111
9.2 Entering Interface Configuration Mode................................... 112
9.3 Entering Loopback Interface Configuration Mode ..................... 114
9.4 Configuring Interface IP Address........................................... 115
9.5 Adding a Group of Active/Standby Interfaces.......................... 117
9.6 Configuring Static Route ...................................................... 118
10 Administration Domain Data Configuration
Flow ..........................................................................123
10.1 Administration Domain Data Configuration ........................... 123
11 Administration Domain Basic Data Configura-
tion ...........................................................................125
11.1 Adding an Administration Domain ....................................... 125
11.2 Configuring Relation Between Administration Domain and
DUA............................................................................................. 128
11.3 Adding Administration Domain Function ............................... 129
11.4 Adding Administration Domain Capacity ............................... 130
12 Subscriber Data Distribution Configuration ..........133
12.1 Configuring Relation Between PDSA Group and Administration
Domain ........................................................................................ 133
12.2 Adding a Physical Number Segment for an Administration
Domain ........................................................................................ 134
12.3 Adding a Logical Number Segment for an Administration
Domain ........................................................................................ 136
12.4 Distributing a Physical Number Segment to an ID DSA
Group .......................................................................................... 137
12.5 Distributing a Logical Number Segment to an ID DSA
Group .......................................................................................... 139
12.6 Distributing a Physical Number Segment to a P DSA
Group .......................................................................................... 140
13 Agent Resource Configuration ..............................143
13.1 Adding an Agent Number Segment Group ............................ 143
13.2 Adding an Agent Physical Number Segment.......................... 144
13.3 Adding an Agent Logical Number Segment ........................... 146
13.4 Adding an Operator Role .................................................... 147
13.5 Adding an Operator........................................................... 149
14 Data Transfer .......................................................151
14.1 Uploading Configuration Data ............................................. 151
Glossary ....................................................................155
USPP_DC001_E1_0
ZXUN USPP Basic Data
Configuration
After you have completed this course, you
will be able to:

>> Master UDS Data Configuration
>> Master Physcal Data Configuration
>> Master Administration Domain Data
Configuration
Confidential and Proprietary Information of ZTE CORPORATION 1

ZXUN USPP Training Manual
Chapter 1 Introduction to UDS

Configuration
After you have completed this chapter, you will know:

>> UDS Configuration Flow
>> Uploading Configuration Data on EMS
1.1 UDS Configuration Flow

The ZXUN USPP configuration flow is shown in the following figure.
FIGURE 1 ZXUN USPP CONFIGURATION FLOW
The recommended UDS configuration flow is shown in the following

figure.
2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Introduction to UDS Configuration
FIGURE 2 UDS CONFIGURATION FLOW
1.2 Uploading Configuration Data

on EMS
Prerequisites The license is validated and uploaded to the OMM network
management system for synchronization.
The EMS network management system is working properly.
The OMM network management system is working properly.
The communication between the EMS and the OMM is normal.
You have logged into the EMS network management system.
Context UDS configuration and administration domain configuration are
performed on EMS. And the configuration data should be uploaded
to the OMM network management system, FE and UDS. This topic
introduces the procedure to upload the data.
You may upload the data immediately after you have made some
data configuration or when you finished all the UDS data configu-
ration.
Steps 1. On the Netnumen(TM) M31 main window, select menu
Views > Daily Maintenance to open the Daily Mainte-
nance window.
2. Select Daily Maintenance > USPP > Data Maintenance >
Data Sync from the navigation tree to open the window shown
in the following figure.

FIGURE 3 DATA SYNC
3. Set the data synchronization parameters by referring to the

following table.
TABLE 1 DATA SYNCHRONIZATION PARAMETERS
Parameter Description
Synchronization type
Changed Tables refer to the tables of configuration data that have
Operate Type
been changed since last synchronization.
All Tables refer to all the tables of configuration data on the EMS.
Sync OMM uploads the configuration data on EMS to the OMM network
management system only.
Sync Option
Sync MP uploads the configuration data on EMS to both the OMM
network management system and the foreground MPs.

Chapter 1 Introduction to UDS Configuration
Save: Whether data are saved at once on each module after the
uploading
Options
Toslave: Whether data are synchronized at once to each backup node
after the uploading
The upload request times out if the front-end processor does not make
Timeout (100ms) any response in this period of time.
Range: 16000, default: 600
4. Select the Sync By Vhlr (sync by administration domain) or

the Sync By Bureau (sync by office) tab, and select the ad-
ministration domains or offices whose configuration data are
to be uploaded.
5. Click the Execute button to upload the data.
6. Click the Sync Process Info tab to check the messages re-
turned during the upload process.
7. Click the Sync Result Info tab to confirm that the upload has
succeeded.
END OF STEPS

This page is intentionally blank.

Chapter 2 OMM Access
Configuration

>> Loading the License File
>> Creating a USPP
>> Creating a Network Element Agent
>> Starting a Network Element Agent
>> Updating USPP
>> Validating the License
>> Uploading the License to OMM Server
>> Adding a Network Element on OMM
>> Adding a USPP Physical Office
>> Loading the Schema
2.1 Loading the License File

Prerequisites The EMS network management system is correctly configured
and connected according to your networking plan.
The OMM network management system working properly.
The License file is ready.
Context Loading the License file onto the EMS server is to save the License
file into the related folder, so that the License may be validated
later.
Steps 1. On the NetnumenTM M31 main window, select menu Views
> License Management to open the License Management
window.
2. On the License tab, select the NetNumen node.
3. On the License Detail Info tabe, click the (Update License
Info) button to open the Please Choose License File dialogue
box as shown in the following figure.

FIGURE 4 CHOOSE LICENSE FILE
4. Select the License file and click Open.

END OF STEPS
Result When the License is loaded, the window is as shown in the follow-
ing figure.
FIGURE 5 LICENSE INFORMATION
But the License can not be validated.

Chapter 2 OMM Access Configuration
Postrequisite Create USPP nodes.
2.2 Creating a USPP

Prerequisites The License file is already loaded.
The EMS network management system is correctly configured
Context This topic describes the procedure to create a USPP according to
the networking plan, that is, to create a network element node on
the EMS.
Steps 1. On the NetNumen(TM) M31 main window, select menu
Views > MML Terminal to open the MML Terminal window.
2. Select the NetNumen node.
3. On the MML commands navigation tree, select USPP CON-
FIGURATION MANAGEMENT > USPP NODE CONFIGURA-
TION MANAGEMENT > CREATE USPP (CREATE USPP) to
open the command interface shown in the following figure.
FIGURE 6 CREATE USPP COMMAND INTERFACE
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 2 CREATE USPP PARAMETERS
TYPE Subtype of the office

Click the to select. The types must be one
that the License supports.
This parameter supports multiple instance, which
can only be added and can not be removed.
USERLABEL Alias of this USPP, range: 050 characters
5. Click the Execute(F5) button or press F5 to execute this com-

mand.
END OF STEPS
Postrequisite Create network element agents.

2.3 Creating a Network Element

Agent
The USPP is already configured.
Context The EMS network management system accesses OMM network
management systems (each appears as a network element agent
on the EMS) through CORBA for integrated management including
topology management, alarm management, report management,
security management, log management, and MML.
This topic describes the procedure to create a network element
agent on the EMS.
> Topology Management to open the Topology Manage-
ment window.
2. On the Physical View tab, right-click the NetNumen node
and then select Create NE Agent from the pop-up menu to
open the Create NE Agent window shown in the following
figure.

FIGURE 7 CREATE NE AGENT
following table.
TABLE 3 PARAMETERS FOR CREATING NE AGENT
Basic Name Name of the OMM server, 050

Attributes characters
Vendor Name of the vendor of the OMM

server, 0100 characters
IP Address IP address of the OMM server, IPv4

type
Version Version of the OMM server, 050

characters
Location Location of the OMM server, 0100

characters
Memo Additional information of the

network element agent, 0200
characters

Extended Port Set it to 21125.

Attributes
Protocol Type Set it to Socket.
FTP Port Set it to 21.
4. Click OK.
END OF STEPS
Postrequisite Start the network element agent.
2.4 Starting a Network Element

Agent
The network element agent is already created.
Context This topic describes the procedure to start a network element
agent so that the OMM is accessed by the EMS.
> Topology Management to open the Topology Manage-
ment window.
2. On the Physical View tab, right-click the NE agent under the
NetNumen node, and then select NE Agent Management >
Start from the pop-up menu.
END OF STEPS
Result After the NE agent has started up, you may see on the Physi-
cal View tab the lower topological levels of this NE. And the link
between the EMS and the NE agent displayed on the right pane
of the Topology Management window is green, as shown in the
following figure.

FIGURE 8 NE AGENT LINK STATE
Postrequisite Update the USPP.
2.5 Updating USPP

The NE agent has started up.
Context Updating USPP is to query and get the latest version of the OMM.
FIGURATION MANAGEMENT > USPP SNO MANAGEMENT
> SHOW USPP SNO to open the SHOW USPPSNO command
interface.
4. Click the Execute(F5) button or press F5 to query the latest
version of the OMM.
FIGURATION MANAGEMENT > USPP SNO MANAGEMENT
> UPDATE USPP to open the command interface shown in the
following figure.

FIGURE 9 UPDATE USPP COMMAND INTERFACE
6. Set SNO (USPP version) to the latest version obtained by the

SHOW USPPSNO command.
mand.
END OF STEPS
Postrequisite Validate the License.
2.6 Validating the License

The USPP have been updated.
The License is already loaded.
Context This topic describes the procedure to validate the License already
loaded onto the EMS server.
Views > License Management to open the License Man-
agement window.
3. On the License Detail Info tab, click the (License Info
Enable) button. The Please be sure the following modifi-
cations become effective window appears, as shown in the
following figure.

FIGURE 10 LICENSE INFORMATION TO VALIDATE
4. Select Show All License Item. If the license information is in

red, it means that the License is not valid. Click OK to validate
the license.
END OF STEPS
Postrequisite Upload the License to the OMM server.
2.7 Uploading the License to OMM

Server
The License is validated on the EMS.
Context This topic describes the procedure to upload the license to the
OMM server so that the license information takes effect on the
OMM server.
Views > License Management to open the License Man-
agement window.

3. On the License Detail Info tab, click the (License Info

Synchronization) button to open the License Info Synchro-
nization window as shown in the following figure.
FIGURE 11 LICENSE INFO SYNCHRONIZATION
4. Select the OMM server from the AMO List and click to move
it to the Preparation synchronized AMO list, and then click
OK.
END OF STEPS
Postrequisite Configure the NE on the OMM.

Configure the USPP physical office on the EMS.
2.8 Adding a Network Element on

OMM
Prerequisites The license on the OMM has been synchronized with the License
on the EMS.
You have logged into the OMM network management system.
Context This topic describes the procedure to add a new NE on the OMM,
which is the first step of data configuration for commissioning. Af-
ter an NE is created, other data configuration can be performed
on this office.
Steps 1. On the NetNumen(TM)M30 main window, select menu

2. Select root from the NetNumen navigation tree.

3. On the MML Commands navigation tree, select System
Maintenance > Net Element Configuration > Create
Management Configuration (ADD NE) to open the com-
mand interface shown in the following figure.
FIGURE 12 ADD NE COMMAND INTERFACE
TABLE 4 PARAMETER DESCRIPTION OF ADD NE COMMAND
Bureau No. Office ID, a unique identification of the office,

range: 1254
Set it according to your networking plan.
Bureau Type Type of the network element,

Click the to select. The types must be one
that the License supports.
This parameter supports multiple instance,
which can only be added and can not be
removed.
Vendor Equipment Vendor

Range: 050 characters
User State User-defined state

Range: 065535
Position Location of the equipment

Optional parameter, range: 150 characters
User Label Alias of this NE, range: 050 characters
4. Set the parameters.

mand.
END OF STEPS

2.9 Adding a USPP Physical Office

Prerequisites The network element is already created on the OMM.
Context This topic describes the procedure to create a physical office on
the USPP.
3. On the MML commands navigation tree, select USPP CONFIG-
URATION MANAGEMENT > USPP NE CONFIGURATION
MANAGEMENT > ADD USPPNE (ADD USPPNE) to open
the command interface shown in the following figure.
FIGURE 13 ADD USPPNE COMMAND INTERFACE
following table.
TABLE 5 ADD USPPNE PARAMETERS
AMO NAME Name of the AMO (the network element managed

by the OMM) that the EMS access. Range: 0100
characters
BNO Office ID of the network element managed by

the OMM, range: 1254

mand.
END OF STEPS
Postrequisite Load the Schema.
2.10 Loading the Schema

Prerequisites You have logged into the EMS network management system.


File mmlbatch.txt for loading Schema is ready.
Context The Schema describes the data stored on UDS, and functions as a
data dictionary in RDBMS.
This topic describes the procedure to upload the UDS data
(Schema) onto the EMS server. The EMS server will then upload
them onto the UDS subsystem through data transfer, so that the
master Schema thread may modify or add memory database
objects according to the new Schema.
2. Select menu Operation > Batch to open the Batch window.
3. Click the (Import File) button to select and import the batch
commands file of Schema, for example, zxver\setup\win-
dows\schema\mmlbatch.txt in the folder of ZXUN USPP in-
stallation files, as shown in the following figure.
FIGURE 14 IMPORTING COMMANDS FOR LOADING SCHEMA
4. Click the (Run Batch) button to execute the commands in

batch.
5. Perform the following operations to confirm the loading.
i. Select NetNumen > USPP > Device Configuration >
Public Device Configuration.
USPP here is a USPP node created by the CREATE USPP
command.

ii. On the MML commands navigation tree, select MML

Commands > UDS Dev Configuration > Show UDS
Dev > Show Schema Version Configuration (SHOW
SCHVER) to open the command interface.
iii. Click the Execute(F5) button or press F5 to execute this
command.
The result is as shown in the following figure.
FIGURE 15 RESULT OF QUERYING SCHEMA VERSION
iv. Confirm that the latest version is what has been uploaded.
END OF STEPS
Postrequisite Add database node.

Chapter 3 UDS Device
Configuration

>> Adding a Database Node
>> DSA Node Configuration
>> DSA Configuration
>> DSA Group Configuration
>> UDS Parameters Configuration
>> Adding a DUA Node
>> Adding a Monitoring Center
3.1 Adding a Database Node

Prerequisites The Schema of a correct version is already loaded.
Context This topic describes the procedure to add a database node for the
UDS subsystem. The database node may be for local storage or
transfer. The database node information is required to connect the
database when DSA nodes are starting up.
2. Select NetNumen > USPP > Device Configuration > Pub-
lic Device Configuration.
USPP here is a USPP node created by the CREATE USPP com-
mand.
3. On the MML commands tree, select MML Commands > UDS
Dev Configuration > Database Node Configuration >
Create Database Node Configuration (ADD DBNODE) to

FIGURE 16 ADD DBNODE COMMAND INTERFACE
following table.
TABLE 6 ADD DBNODE PARAMETERS
DB ID ID of the database node, integer type, range:

165535
For convenience of use, the ID of the DSA or DST
node is recommended to be used as the DB ID.
Database Type Options: Oracle, SQL Server

User Name User name used to access the database, string

type, 120 characters
Password Password of the user name used to access the

database, string type, 120 characters
DB Name Name of the database (generally same as the

database instance), string type, 030 characters
Connection Network service name accessing the database,

Service string type, 035 characters
DB IP IP address of the database server


Chapter 3 UDS Device Configuration
Slave Name of the first backup network service

Connection accessing the database, string type, 035
Service 1 characters
Not required if no standby server
Slave DB IP 1 IP address of the first backup database server

Slave Name of the second backup network service

Connection Backup network service name accessing the
Service 2 database, string type, 035 characters
Slave DB IP 2 IP address of the second backup database server

DBA Password If the database is SQL Server, it is the password

for user sa.
If the database is Oracle, it is the password for
user sys.
String type, 020 characters
SYSTEM Password for user system, valid when the

Password database is Oracle, string type, 020 characters
User Label Alias of this configuration item, string type, 050

characters
Note:
To avoid trouble caused by wrong database parameters, it is
recommended that you test the settings using the tools of the
database before adding the database node.
The local Net service of the database need also be configured
on the computers where the UDS node is on.

mand.
END OF STEPS

Postrequisite Add DSA nodes.
3.2 DSA Node Configuration
3.2.1 Adding a DSA Node
The blade server which the UDS subsystem is to be mounted
on as planed is already installed.
The database node is configured.
Context The UDS subsystem consists of one or more DSAs (DSA clusters,
to be precise). A DSA cluster may consist of 180 DSA nodes.
There are two types of DSAs in a UDS subsystem, Identity DSA
(ID DSA) and Profile DSA (PDSA). For the data of a subscriber, the
referral data are stored on ID DSA, and alias and other subscriber
data are stored on PDSA. The referral data enable the system to
locate by subscriber ID the PDSA where the subscriber data are
stored.
This topic describes the procedure to create a DSA node.
mand.
3. On the MML commands navigation tree, select MML Com-
mands > UDS Dev Configuration > DSA Node Configura-
tion > DSA Node Configuration > Create DSA Node Con-
figuration (ADD DSANODE) to open the command interface
shown in the following figure.

FIGURE 17 ADD DSANODE COMMAND INTERFACE
following table.
TABLE 7 ADD DSANODE PARAMETERS
DSA Node ID ID of the DSA node to create, integer type,

range: 14000
Relating ID of the physical office that the DSA node

Bureau belongs to, integer type, range: 1254
Module Module No. of this DSA node

It should be identical of the module number on
the OMM network management system.
Module Type Module type of this DSA node

IDDSA: Identity DSA
PDSA: Profile DSA
SAVE: DST (transfer node)
IP Type IP address type of this DSA node, options: IPV4,

IPV6
Set it according to the local IP planed for this
DSA node.
Internal IP IP address of this DSA node for internal access

Address Set it according to your networking plan.
Internal Port Port No. of this DSA node for internal access,
default: 5057

External IP IP address of this DSA node for external access

Address In case of intra-office networking, the external
IP address should be identical with the internal
IP address.
External Port Port No. of this DSA node for external access,
default: 5057
In case of intra-office networking, the external
port No. should be identical with the internal port
No.
User Label Alias of this DSA node, string type, range: 050
characters
For convenience of understanding, the alias
may be set in OfficeID-DSA node type-ModuleID
format, for example, 29-pdsa-3.

mand.
END OF STEPS
Postrequisite Set DSA node options.
3.2.2 Setting DSA Node Options
Prerequisites The DSA node configuration is complete.

Context This topic describes the procedure to change DSA node properties,
for example, the paging file size.
mand.
Dev Configuration > DSA Node Configuration > DSA
Node Option Configuration (SET DSANODEOPT) to open
the command interface shown in the following figure.

FIGURE 18 SET DSANODEOPT COMMAND INTERFACE
following table.
TABLE 8 SET DSANODEOPT PARAMETERS
DSA Node ID ID of the DSA whose options are to be modified,

integer type, range: 14000
Run DSA may run on an MP on the foreground or a

Environment server, which may be a blade server.
Small Page Size of a small memory page of the memory pool,

Size (KB) integer type, range: 116, unit: KB
It must be larger than Big page Size.
The memory pool is a memory area for saving
data during the process of LDAP request or DSP
request.
To avoid waste of memory, the system needs to
assign a memory area of proper size according to
the data to be handled. Therefore, Small Page
Size and Big page Size need be set.
Be cautions to change this setting, and consult
ZTE before you change it.
Small Page Number of small memory pages in the memory

Num pool, integer type, range: 010000
It need be set according to the processing
capacity of the system. If you really need to
change the setting, contact ZTE for advice before
doing so.
Big page Size Size of a big memory page, integer type, range:
(KB) 3264, unit: KB
Big Page Num Number of big memory pages in the memory

pool, integer type, range: 11000

Server Thread The number of threads that may parallelly

Num process transactions in directory services.
If the DSA node is running on MP, the number of
directory service threads can only be 1.
If the DSA node is running on server, the number
of directory service threads can be 010.
The total Total number directory transaction data areas,

number of DIR integer type, range: 14000
transaction
data area
The Max Maximum number of messages that this DSA

Number of node can process every second, integer type,
Received range: 065535
Message Per When the DSA node receives one more message
Second than the number, it sends error message to the
DUA.
The Max Maximum number of Check resources, integer

Number type, range: 0127
of Check
Resource

characters

mand.
END OF STEPS
Postrequisite Perform DSA node storage configuration.
3.2.3 Setting DSA Node Storage

Configuration
Prerequisites The DSA node options are correct.

Context A UDS subsystem consists of DSA nodes, a DST node (for data
storage and transfer) and a monitor center. The DST node provides
data persistence for one or more DSA nodes. Data are stored on
the disk array connected to the blade server on which the DST node
is located. The DSA nodes cooperate with the storage subsystem
of the DST node to realize data persistence.
This topic describes the procedure to set the storage mode of DSA
nodes and the transferring of database node information.


mand.
Dev Configuration > DSA Node Configuration > DSA
Node Storage Configuration > Create DSA Node Storage
Configuration (ADD DSANODESAV) to open the command
interface shown in the following figure.
FIGURE 19 ADD DSANODESAV COMMAND INTERFACE
following table.
TABLE 9 ADD DSANODESAV PARAMETERS
DSA Node ID ID of the DSA node that the storage configuration

is for, integer type, range: 14000
Store Type Storage type of this DSA node:

NOSAVE: Select in case that this node does
not need data persistence, and data are only
stored in the memory database.
LOCAL: Select in case that this node writes
data into the physical database.
REMOTE: Select in case that this node uses
the DST node for data persistence.
Generally, for ID DSA and P DSA, this parameter
is set to REMOTE; and for DST it is sent to LOCAL.
Store Style Storage mode of the DSA node:

FILE: Stored in files
DB: Stored in database
Valid only when Store Type is LOCAL.
Store Node ID ID of the DST node

Valid only when Store Type is REMOTE.
Integer type, range: 165535

File Path Path of files for storage purpose

String type, range: 049 characters
Valid only when Store Type is LOCAL and Store
Style is FILE.
DB ID ID of the database for storage purpose

Integer type, range: 165535
Valid only when Store Type is LOCAL and Store
Style is DB.
Backup Time Scheduled time for daily data backup, default:

Every Day 03:00
Valid only when Store Type is LOCAL.

characters

mand.
END OF STEPS
Postrequisite Add DSA.
3.3 DSA Configuration
3.3.1 Adding a DSA
The DSA node storage configuration is complete.
Context The UDS subsystem consists of one or more DSAs (DSA clusters,
to be precise). A DSA cluster may consist of 180 DSA nodes.
This topic describes the procedure to create a DSA.
mand.
mands > UDS Dev Configuration > DSA Configuration
> DSA Configuration > Create DSA Configuration (ADD
DSA) to open the command interface shown in the following
figure.

FIGURE 20 ADD DSA COMMAND INTERFACE
following table.
TABLE 10 ADD DSA PARAMETERS
DSA ID ID of the DSA to create, integer type, range:

1999
DSA Type ID of the DSA to create

A DSA may be of ID DSA, PDSA, or ID
DSAandPDSA type.
DSA nodes of a DSA must be of the same type of
the DSA. Set it according to your networking plan.
ID DSA Required if this is an ID DSA

Number Type An ID DSA may have numbers of more than one
type. Set it according to your networking plan.
Home Bureau ID of the primary home office of this DSA, integer

No. 1 type, range: 1254
In case of intra-office networking, the home
office should be the local office.
In case of intra-office networking, the home
office should be one of the offices.
For a DSA cluster, the home office should be the
office that has the maximum number of primary
nodes.
Home Bureau ID of the secondary home office of this DSA,

No. 2 integer type, range: 1254
In case of failure on the monitoring center of the
primary home office, the monitoring center of the
secondary home office will take over.
The election Wether allow the monitoring center to select a

mode PDS new primary node in case of failure in primary
node, default: Yes

DSA Node ID ID of the master DST node, range: 04000

of Master DST Select one from the DST nodes already configured
according to your networking plan.
User Label Alias of this DSA, string type, range: 150

characters

mand.
END OF STEPS
Postrequisite Add DSA members.
3.3.2 Adding a DSA Member
The DSA configuration is complete.
The Schema has been uploaded, and you have known its ver-
sion.
Context Adding a DSA member is to add a DSA node to a DSA cluster, and
to set the message distribution proportion and node level for this
DSA node.
mand.
mands > UDS Dev Configuration > DSA Configuration >
DSA Member Configuration > Create DSA Member Con-
figuration (ADD DSACLU) to open the command interface
FIGURE 21 ADD DSACLU COMMAND INTERFACE

following table.
TABLE 11 ADD DSACLU PARAMETERS
DSA Node ID ID of the DSA node created by the ADD

DSANODE, integer type, range: 14000
DSA ID ID of the DSA cluster (created by the ADD DSA)

that this DSA node belongs to, integer type,
range: 1999
Schema Schema version of this DSA node, acquired by

Version the SHOW SCHVER command, string type,
range: 19 characters
Node Level Level of this DSA node, options: level 1, leve 2,

default: level 1
A level1 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. Level-1 nodes are generally deployed at a
same place with the main node.
For two DSA nodes of a DSA that to be working in
a load-sharing or inter-backup mode, they should
be both set as level-1 nodes. For two DSA nodes
of a DSA that to be 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.
Dealing Distribution proportion of messages, i.e.

Message percentage of messages distributed to this DSA
Capacity node, integer type, range: 1100
The total of all DSA nodes should be 100. Set it
according to your networking plan.
User Label Alias of this DSA member, string type, 050

characters

mand.
END OF STEPS
Postrequisite Modify DSA options.

3.3.3 Setting DSA Options
The DSA member configuration is complete.
Context This topic describes the procedure to modify DSA attributes, for
example, data persistence policy and consistency policy.
mand.
mands > UDS Dev Configuration > DSA Configuration >
DSA Option Configuration > Modify DSA Option Configu-
ration (SET DSAOPT) to open the command interface shown
FIGURE 22 SET DSAOPT COMMAND INTERFACE
following table.
TABLE 12 SET DSAOPT PARAMETERS
DSA ID ID of the DSA to modify, integer type, range:

1999
Min Sync Num The minimum number of primary nodes

that returns a message notifying real-time
synchronization success, range: 1999
A synchronization operation succeeds only when
at least this number of primary nodes have
returned success.
In case of root node only (no subnode), it must
be set to 0.

Durable Flag Whether the directory service process needs to

For Provision wait for a response message about the data
persistence
The data reliability may be higher if it is set to
Yes.
Durable Policy Data persistency policy

NODUR(No Durable): No data persistency
will be done when a transaction is submitted.
The storage subsystem performs scheduled
data persistency from logs. This policy has
the highest processing capacity.
DUR(Durable): Data persistency is done
when a transaction is submitted. The data
are written into the storage medium. The
transaction fails if the data persistency fails.
FLXDUR(Flexible Durable): Depending on
DUA configuration of data persistency
Consistent Data consistency policy, valid when the DSA has

Policy an SUDS (standby and out-of-sync) node.
SWSUDS(Service When SUDS): Data
query will be done on standby and out-of-sync
nodes also.
OSWSUDS(Out of Service When SUDS):
Data query will not be done on standby and
out-of-sync nodes.

characters

mand.
END OF STEPS
Postrequisite Add subscriber table capacity.
3.3.4 Adding Subscriber Table

Capacity
The DSA member configuration and DSA options configuration
are complete.
Context Subscriber table capacity should be configured on each DSA node
for each type of subscriber that ZXUN USPP supports.


mand.
Dev Configuration > DSA Configuration > DSA Sub-
scriber Capacity Configuration > Create DSA Subscriber
Capacity Configuration to open the command interface
FIGURE 23 ADD CAPSUB COMMAND INTERFACE
following table.
TABLE 13 ADD CAPSUB PARAMETERS
DSA ID ID of the DSA that the subscriber table capacity

is to be created for, integer type, range: 1999
It must be one already created by the ADD DSA
Base Table The subscriber table that this DSA supports. A

Name DSA may support only one type of NE.
Capacity Capacity of the selected table, integer type,

range: 04294967295
The table capacity of a DSA should not exceed
the number of subscribers that the DSA may
handle. The total of all subscriber capacities on
all P DSA nodes should not exceed the limit of
License. The total of all subscriber capacities on
all ID DSA nodes should not exceed the limit of
License either.
User Label Alias of this capacity setting, string type, 050

characters

mand.
END OF STEPS
Postrequisite Configure DSA groups.

3.4 DSA Group Configuration

3.4.1 Adding an ID DSA Group
Prerequisites The DSA member configuration and DSA options configuration

are complete.
Context For the purpose of convenience of management and maintenance,
subscriber data of one application type are saved on DSAs of one
group. For example, if the USPP system includes multiple applica-
tion types and there is no requirement for services integrated by
two or more application types, then it may be so configured that
all subscriber data of an application type are saved on DSAs of a
specific group.
In an administration domain, DSAs containing subscriber data of
the same application type are assigned to one group. And each
DSA group contains all the DSAs containing subscriber data of a
same application type.
This topic describes the procedure to add an ID DSA group.
mand.
Dev Configuration > DSA Group Configuration > IDSA
Group Configuration > Create IDSA Group Configuration
(ADD IDDSAGRP) to open the command interface shown in
the following figure.
FIGURE 24 ADD IDDSAGRP COMMAND INTERFACE
following table.

TABLE 14 ADD IDDSAGRP PARAMETERS
IDSA ID ID of an ID DSA belonging to the ID DSA group

to create, range: 1999
The ID DSA must already exist and must be of ID
DSA or IDDSA&PDSA type.
IDSA Group ID ID of the ID DSA group to create, range: 165535
User Label Alias of this ID DSA group, string type, 050

characters

mand.
END OF STEPS
Postrequisite Configure ID DSA distribution.
3.4.2 Distributing Numbers to an ID

DSA
The ID DSA group is configured.
Context In a UDS subsystem with a large capacity, subscriber data are
distributed on multiple ID DSAs. Each ID DSA saves the subscriber
data of a certain range. The range is defined by the start mapping
code and the end mapping code of IMSI or DN (for example, the
last three digits of IMSI). The system locates the home ID DSA of
a subscriber with the mapping code.
This topic describes the procedure to distribute numbers to ID
DSA(s) by mapping codes.
mand.
Dev Configuration > DSA Group Configuration > IDSA
Distributing Configuration > Create IDSA Distributing
Configuration (ADD IDSAMAP) to open the command

FIGURE 25 ADD IDSAMAP COMMAND INTERFACE
following table.
TABLE 15 ADD IDSAMAP PARAMETERS
Serial No. Serial of this distribution configuration item,

range: 165535
Number Type Type of the numbers to be distributed by this

distribution configuration item. Multiple number
segments of different types (for example IMSI
and DN) may be distributed to one ID DSA.
Begin Mapping Beginning mapping code of a mapping code

Code section to be distributed to the ID DSA, integer
type, range: 0999
You may set one or more mapping code sections
for one DSA.
End Mapping Ending mapping code of a mapping code section

Code to be distributed to the ID DSA, integer type,
range: 0999
You may set one or more mapping code sections
for one DSA.
DSA ID ID of the ID DSA that numbers within the

mapping code section are to be distributed to,
integer type
Select from existing DSAs of the IDDSA or
IDDSA&PDSA type.
User Label Alias of this number distribution configuration

item, string type, 050 characters

mand.
END OF STEPS
Postrequisite Add P DSA group.

3.4.3 Adding a P DSA Group
Prerequisites The ID DSA distribution configuration is complete.

Context This topic describes the procedure to add a P DSA group and to
set the capacity ratio of the DSAs included by the P DSA.
mand.
Dev Configuration > DSA Group Configuration > PDSA
Group Configuration > Create PDSA Group Configuration
(ADD DSAGRP) to open the command interface shown in the
following figure.
FIGURE 26 ADD DSAGRP COMMAND INTERFACE
following table.
TABLE 16 ADD DSAGRP PARAMETERS
Serial No. Serial number of the P DSA group, range:

165535
PDSA Group ID of the P DSA group to create, range: 165535

ID A P DSA group may include multiple P DSAs. And
a P DSA may belong to multiple P DSA groups.
PDSA ID ID of a P DSA belonging to the P DSA group to

create, range: 1999
The P DSA must already exist and must be of P
DSA or IDDSA&PDSA type.

Capacity The ratio of the capacity of the P DSA specified

by the PDSA ID within the P DSA group, range:
0100
The total of capacity of all P DSAs within this
group must 100.
Assigned to Whether data are save on specified DSAs. If yes,

Save Data in the capacity setting is invalid, and data are save
the PDSA on the specified DSA clusters.
User Label Alias of this P DSA group, string type, 050

characters

mand.
END OF STEPS
Postrequisite Configure UDS parameters.
3.5 UDS Parameters Configuration

3.5.1 Setting UDS Load Control
The configuration of DSA groups is complete.
Context When the load of the UDS subsystem exceeds the expected value,
the load control module functions according to the load control
configuration.
Before modifying the load control configuration, check and then
modify the current settings if necessary.
Note:
The default settings are recommended. Be cautions and make
sure you really need to modify the load control configuration.

mand.


Dev Configuration > Load Control Configuration > Mod-
ify Load Control Configuration (SET LOADLEV) to open the
command interface shown in the following figure.
FIGURE 27 SET LOADLEV COMMAND INTERFACE
following table.
TABLE 17 SET LOADLEV PARAMETERS
Load Level The level of load control that the settings are
to be modified, range: 04
CPU Rate CPU load (%) of this load level, range: 0100
Only Read Ratio of read-only messages to be discarded

Discard Message in case of this level overload, range: 0100
Rate(%)
Only Read Ratio of read-only messages to be transferred

Transferring in case of this level overload, range: 0100
Message Rate(%)
Update Discard Ratio of update messages to be discarded in

Message case of this level overload, range: 0100
Rates(%)
User Label Alias of this number distribution configuration

item, string type, 050 characters

mand.
END OF STEPS
3.5.2 Setting UDS Parameters

Context When the load of the UDS subsystem exceeds the expected value,
the load control module functions according to the load control
configuration.
Before modifying the load control configuration, check and then
modify the current settings if necessary.
Note:
The default settings are recommended. Be cautions and make
sure you really need to modify the UDS parameters.

mand.
Dev Configuration > UDS Parameter Configuration >
UDS Parameter Configuration > Modify UDS Parameter
Configuration (SET UDSPARA) to open the command

FIGURE 28 SET UDSPARA COMMAND INTERFACE
following table.
TABLE 18 SET UDSPARA PARAMETERS
Message distribution Not required if this office has no more than

policy one node, options:
Loop Select: Choose a node in turn by
a certain rule, for example, selecting the
node with the lowest load first.
Optimize Select: this node prior
Async redirect Flag Whether redirection for asynchronous

replication is allowed, options:
YES: During asynchronous replication,
if the load on the active node is high
and there is an available SSDS node
(standby synchronization node) in the DSA
cluster, another SSDS node within the DSA
node may be chosen for asynchronous
replication.

NO: Do not select another SSDS node for
asynchronous replication.
Synch replicate Reliability level of synchronous replication,

Reliability Level options:
PMLOW(Max Reliable): Highest
reliability, lowest performance. The
directory service needs to wait for the
response from the subsystem. If a standby
node exists, the main node immediately
sends a Synchronous Replication request
to the standby node.
PMMID(Midium Reliable): Medium
reliability, medium performance. The
directory service does not need to wait
for the response from the subsystem.
If a standby node exists, the main
node immediately sends a Synchronous
Replication request to the standby node.
PMGOD(Min Reliable): Lowest reliability,
highest performance.. The directory service
does not need to wait for the response
from the subsystem. If a standby node
exists, the main node sends on schedule
a Synchronous Replication request to the
standby node.
The Weight for The weight of Search request messages

Search Request used for load control, base unit: 1, range:
030, default: 1
The Weight for Add The weight of Add request messages used
Request for load control, base unit: 1, range: 030,
default: 1
The Weight for The weight of Delete request messages

Delete Request used for load control, base unit: 1, range:
030, default: 1
The Weight for The weight of Modify request messages

Modify Request used for load control, base unit: 1, range:
030, default: 1
The Weight for The weight of AllocGID request messages

AllocGID Request used for load control, base unit: 1, range:
030, default: 1
The Weight for The weight of Compound request messages

Compound Request used for load control, base unit: 1, range:
030, default: 1
The Weight for The weight of Execute request messages

Execute Request used for load control, base unit: 1, range:
030, default: 1
The Thresh of CPU The thresh of CPU load above which

LOAD Above Which signals for checking data consistency are
Check Signal Is discarded.
Discarded(%)

Check Take Effect Whether the data consistency check

Flag function is enabled
The Time of starting Time to start data consistency check every

to check Every Day day, range: 00:0023:59
The time during Maximum duration of data consistency

which UDS check, range: 01439
checking(Min) The check stops if the time expires.
Support Synch Wether the replication data are compressed

Compression before transmission
Intra-Bureau Upper limit of clients supporting concurrent

Concurrent Resume online resume within the office, range:
Limit 0255
Inter-Bureau Upper limit of clients supporting concurrent

Concurrent Resume online resume between offices, range:
Limit 0255
All Concurrent Upper limit of clients supporting concurrent

Resume Limit online resume within and between offices,
range: 0255
Concurrent Resume Upper limit of clients supporting concurrent

Limit In Two Bureaus online resume between two offices, range:
0255
Support Master DST Wether to Master DST function is

valid globally within the UDS, valid for
inter-office deployment and standby/active
DST configuration only, default: No
User Label Alias of this configuration item, string type,

050 characters

mand.
END OF STEPS
3.5.3 Setting the Capacity of a

Configuration Table
Context This topic describes the procedure to modify the capacity of a con-
figuration table.

Note:
The default configuration is recommended. Be cautions and make
sure you really need to modify the capacity of the configuration
table.

mand.
Dev Configuration > UDS Parameter Configuration > CM
Table Capacity Configuration > Modify CM Table Capac-
ity Configuration (SET CAPCFG) to open the command in-
terface shown in the following figure.
FIGURE 29 SET CAPCFG COMMAND INTERFACE
following table.
TABLE 19 SET CAPCFG PARAMETERS
Table ID ID of the table to modify
Table Size Capacity of the table that you want to set

to, range: 04294967295

mand.
END OF STEPS
3.5.4 Setting the Capacity Scale of a

Subscriber Data Table

Context This topic describes the procedure to modify the capacity scale of
a subscriber data table.
The scale (divided by 1000) is a ratio to the capacity of the cor-
responding configuration table. For the setting of the capacity of
the configuration table, see 3.5.3.
For example, if the capacity of the WCN subscriber basic table
(a configuration table) is 200K and the scale is 1100, then the
capacity of this table is 200K*1100/1000=220K.
Note:
The default configuration is recommended. Be cautions and make
sure you really need to modify the capacity ratio of a subscriber
data table.

mand.
Dev Configuration > UDS Parameter Configuration >
Subscriber Table Capacity Scale Configuration > Modify
Subscriber Table Capacity Scale Configuration (SET
CAPSUBSCL) to open the command interface shown in the
following figure.
FIGURE 30 SET CAPSUBSCL COMMAND INTERFACE
following table.
TABLE 20 SET CAPSUBSCL PARAMETERS
Table ID ID of the table to modify
Scale Capacity scale of the table that you want to

set to, range: 14294967295

mand.
END OF STEPS

3.6 Adding a DUA Node

The UDS device configuration is complete.
Context This topic describes the procedure to add a DUA node.
A DUA node, including FE and DBIO, works as an agent of directory
services.
mand. See 2.2 for details.
3. On the MML commands tree, select MML Commands >
FE/Provision Configuration > Create FE/Provision Con-
figuration (ADD DUANODE) to open the command interface
FIGURE 31 ADD DUANODE COMMAND INTERFACE
following table.
TABLE 21 ADD DUANODE PARAMETERS
DUA Node ID ID of the DUA node to create, range:

14000
Relating Bureau ID of the office associated with the DUA

Select one from the offices already created
Module Module ID of the DUA, range: 1300

Module Type Module type of the DUA

IP Type IPV4 or IPV6, default: IPV4
Internal IP Address IP address of the DUA node for internal use
Internal Port Port number of the DUA node for internal

use, range: 065535, default: 5057
External IP Address IP address of the DUA node for external use
External Port Port number of the DUA node for external

use, range: 065535, default: 5057
User Label Alias of this DUA node, range: 050

characters

mand.
END OF STEPS
Postrequisite Configure the monitor center resources.
3.7 Adding a Monitoring Center

The DUA node configuration is complete.
Context This topic describes the procedure to configure resource data of
the distributed monitoring center and GT address of the physical
office in UDS system. The distributed monitoring subsystem sends
messages to the monitoring center of the adjacent office by this
GT address.
In case that a DSA node acts as the monitoring center, this DSA
node cannot be configured as a DSA member.
mand.
3. On the MML commands tree, select MML Commands > CC
Resource Configuration > Create CC Resource Configu-

ration (ADD DMCC) to open the command interface shown

FIGURE 32 ADD DMCC COMMAND INTERFACE
4. Set parameters by referring to the following table.
TABLE 22 ADD DMCC COMMAND PARAMETERS DESCRIPTION
DMCC ID ID of the monitoring center, range: 14000
UDS System The physical office ID where the monitoring

Including Bureau center locates, range: 1254
No.
GT Address GT address of this physical office, range:

116 characters
Code Plan The code plan used by this GT address,

options: E164 and E212
Module No. The module number where the monitoring

center is located, range: 1250, default: 1
IP Type IP address type of the monitoring center,

options: IP V4 and IP V6, default: IP V4
Internal IP Address The internal IP address of the monitoring

center
Internal Port The internal port number of the monitoring

center

External IP Address The external IP address of the monitoring

center, for inter-office communication of the
monitoring center, generally the external
loop-back IP address, IPv4 or IPv6 type,
depending on the IP Type setting. If there
is no inter-office communication, it may be
the same as the internal IP address.
External Port The external port number of the monitoring

center
User Label Alias of this monitoring center, range: 050

characters.

mand.
END OF STEPS
Postrequisite Upload the configuration data.

Chapter 4 Introduction to Physical
Data Configuration

>> Physical Configuration Flow
>> Uploading Configuration Data
4.1 Physical Configuration Flow

The equipment configuration flow that contains the physical con-
figuration flow is shown in the following figure.
FIGURE 33 EQUIPMENT CONFIGURATION FLOW
The recommended physical configuration flow is shown in the fol-

lowing figure.

FIGURE 34 PHYSICAL CONFIGURATION FLOW
The IP stack configuration flow is shown in the following figure.

After the offline data configuration (except IP stack configuration)
is complete, you need to configure the interface IP stack infor-
mation on the OMM when the link between the foreground and
background systems has been established. The IP interface infor-
mation is validated without the synchronization operation. Figure
35 shows the configuration flow.
You need to enter the interface IP configuration mode to configure
the interface IP addresses of the TIPI board and the SIPI board.
You need to enter the loopback interface configuration mode to
configure the interface IP address of the RPU module.

Chapter 4 Introduction to Physical Data Configuration
FIGURE 35 IP STACK CONFIGURATION FLOW

Prerequisites You have logged into the OMM network management system
as user Admin.
The FE subsystem, the UDS subsystem and the Provision Sub-
system are working properly.
Context After data configuration, it is necessary to synchronize the config-
uration data tables made on the OMM subsystem to DBIO, UDS
subsytem and provision subsystem.
You can synchronize all tables or only the changed tables.
Steps 1. On the NetNumen(TM)M30 HLR main window, select menu
2. Select the current working office node under root.
mands > Data Maintenance > Data Transfer > Sync Data
(Only Used By Admin) (SYNA) to open the command inter-
face shown in the following figure.
FIGURE 36 SYNA COMMAND INTERFACE
following table.

TABLE 23 SYNA PARAMETERS
User Name String type, range: 050 characters

Set it to Admin.
Sync Type Synchronization type, options: Changed

Tables, All Tables, default: Changed Tables
Module List Modules that the configuration data are to

be uploaded to. It is all modules by default
if no module is specified.
Response Timeout The upload request times out if the

(100ms) front-end processor does not make any
response in this period of time.
Save When Whether data are saved at once on each

Completed module after the uploading, default: Yes
Sync to Slave When Whether data are synchronized at once

Completed to each backup node after the uploading,
default: Yes
5. Click the Execute button to execute the command.

END OF STEPS

Chapter 5 Physical Configuration
>> Concepts on Physical Configuration
>> Adding a Rack
>> Adding a Shelf
>> Adding a Unit
>> Adding a Module
>> Configuring TCP Transfer for TIPI
>> Setting the IP of the OMP module
5.1 Concepts on Physical

Configuration
Introduction to ZXUN USPP adopts BCTC shelves. BCTC shelves provide control-
Shelf stream interconnection for resource shelves and switching shelves.
A BCTC shelf provides 2 or three fast Ethernet (FE) interfaces for
each slot. The following table shows the number of FE interfaces
available for each slot.
FIGURE 37 FE INTERFACES AVAILABLE FOR EACH SLOT IN A BCTC SHELF
The adaptation of boards to slots in BCTC shelf is as follows.

Slots 9 and 10 (master slots): For UIMC boards only, which
bear the data in the control shelf and control the switching
paths from Ethernet to each slot.
Slots 18 and 11, 12, 17 (general slots): For SMP, SPB, USI,
SIPI and TIPI boards

Slots 13 and 14 (clock slots): For CLKG boards. Also for the
SMP boards when CLKG boards are not needed.
Slots 15 and 16 (control and switch center slots): For THUB or
SMP boards.
Office ID, Rack There are 3 groups of pin switches (4 bits on each pin switch) on
No., and Shelf No. the backplane of the BCTC shelf, marked respectively with TRIBID,
RACKID, SHELFID, which represent respectively office ID, Rack No.
and Shelf No.
Y position of a pin switch indicates a valid bit, and X position indi-
cates an invalid bit for filling purpose only. pin switches are coded
in binary, with the left one as the lowest bit, and the right one as
the highest bit. It indicates ON (0) when the pin is plugged, and
OFF (1) when the pin is removed. The office ID is the value of the
pin switches of the TRIB ID group, while rack No. and shelf No.
are the values of corresponding groups plus 1.
Office ID (TRIB) uses 3 bits: YYYX.
Rack No. (RACKID) uses 4 bits: YYYY.
Shelf No. (SHELFID) uses 2 bits: YYXX.
The following is an example for setting Office ID, Rack No., and
Shelf No.
For Office 3, remove the pins of the left two pins and plug the
third pin, that is, set TRIBID to 110.
For Rack 1, plug all pins, that is, set RACKID to 0000.
For Shelf 2, remove the first pin from the left pin and plug the
second, that is, set SHELFID to 10XX.
Module, Unit, and Module
Subunit
Module is a logical concept defined from a view of control. A
module may be a CPU of an OMP board or an SMP board, which
also means that CPUs of OMP or SMP board realize the functions
of modules. There are currently four types of modulesOMP,
SMP, RPU and CMP.
One CPU of an OMP or SMP board may be configured as one or
more modules.
Unit
Unit is a logical concept corresponding to board. Boards of a
same type may be configured as different units as needed. A
physical board may be configured as one unit only.
Boards of 1+1 redundancyfor example, UIMC boardsare
also taken as one unit. Therefore, a unit may correspond to
one or two boards.
Subunit
A subunit is a part of a unit which is relatively independent
in functions and relates to certain physical entities. A subunit
may be an E1 interface, GE interface, CPU or DSP (ASIC).
Every unit should contain one or more CPU subunits. CPU sub-
units are numbered from 1, while other units are generally
numbered from 9.
Besides CPU subunits, a unit may also contain DSP, ASIC, E1,
GE, FE, or FPGA subunits.

5.2 Adding a Rack

Prerequisites License synchronization is complete.
You have logged in to the OMM network management system
and have the authority for this operation.
The OMM system is correctly configured and connected accord-
ing to the network planning.
The NE is created.
Context This topic describes the procedure to add a logical rack correspond-
ing to the physical rack.
Note:
After an office is added, rack 1 is created automatically. You can
add a rack when necessary. For example, you can add a rack after
the rack deletion operations.

mands > Device Configuration > Physical Configuration
> Rack Configuration > Create Rack (ADD RACK) to open
the window shown in the following figure.
FIGURE 38 ADD RACK COMMAND INTERFACE
following table.
TABLE 24 ADD RACK PARAMETERS
Rack No. Rack number, which can be set by jumpers

on the backplane of the rack, range: 115,
default: 1
It must be 1 if there is only one rack.
Rack Type Select 3G_STANDARD_RACK (ZTE standard

rack) for ZXUN USPP.
Alias Alias of the rack, length: 050 characters


mand.
END OF STEPS
Postrequisite Add shelves.
5.3 Adding a Shelf

Prerequisites The rack is created.
You have the license.
You have logged into the OMM network management system
Context This topic describes the procedure to add a shelf. Shelf 2 on Rack
1 must be configured as a BCTC shelf. When there are multiple
shelves in an office, create other shelves after BCTC shelf is con-
figured.
> Shelf Configuration > Create SHELF (ADD SHELF) to
open the window shown in the following figure.
FIGURE 39 ADD SHELF COMMAND INTERFACE
TABLE 25 ADD SHELF PARAMETERS
Rack No. Rack No. of the shelf, range: 116.
Shelf No. Serial No. of the shelf to create

The shelf number must be consistent with that
set through the DIP switch on the back of the
backplane. Normally, the shelf is numbered as
14 from up to down. The number of the shelf
where OMP board locates must be 2.

Shelf Type The shelf of ZXUN USPP office must be of BCTC

type.
Shelf Version Options: BGSN080600, BGSN060801, invalid

for a BCTC shelf
Alias Alias of this shelf, 050 characters
4. Set the parameters.

mand.
END OF STEPS
Result A default OMP module is created automatically when Shelf 2 in

Rack 1 is created.
Postrequisite Add a UIMC unit with the ADD UNIT command.
5.4 Adding a Unit

To add a UIMC unit, the shelf must be already configured. To
add a unit other than UIMC, the module must be configured.
Context This topic describes the procedure to add units such as UIMC, SPB
(for E1 access), SIPI (for IP access), HSL (for ATM access), USI(
when there is only one physical office) or TIPI (for intra-office or
inter-office communication, or both).
The sequence to create units and modules is as follows.
1. Add the UIMC unit.
2. Add modules other than OMP and RPU.
3. Add units other than UIMC.
> Unit Configuration > Create Unit (ADD UNIT) to open
the window shown in the following figure.

FIGURE 40 ADD UNIT COMMAND INTERFACE
following table.
TABLE 26 ADD UNIT PARAMETERS
Unit Location Location of the unit in the system, format:

RACK-SHELF-SLOT, range: RACK: 116,
SHELF: 14, SLOT: 117
Module No. Module No. that the unit attributes to, range:
1127
Unit No. Unit No. to create, range: 12000

Unit Type Type of the unit to create


Backup Mode Backup Mode adopted by the unit

Backup mode of this module; options include
NO(Without backup), ONEPLUSEONE(One
plus one backup), LOADSHARE(Load share
backup), BACKTOBACK(Back to back
backup), NPLUSONE(N plus one backup)
and ONETOONE(One to one backup).
Backup Unit ID of the backup unit, range: 165535

E1/T1 Attribute Configure it for the units corresponding to

the SPB board and the HSL board. Select
E1 usually. Set the value according to the
networking plan.
Channel Mode Configure it for the unit corresponding to the

TIPI board. Select MODE2 usually. Set the
value according to the networking plan.
Alias Alias of the unit, range: 050 characters

mand.
END OF STEPS
Postrequisite If the module is not created yet, create a module. Refer to

topic for details.
If the module configuration and unit configuration are complte,
set the IP address of the OMP with the SET OMP command.
Refer to topic 5.7 for details.
5.5 Adding a Module

Prerequisites You have the license.
You have logged into the OMM network management system
The UIMC unit is already created.
Context This topic describes the procedure to configure a module, including
OMP, RPU, SMP, CMP_HLR, LIC, HSDB, etc.
OMP and RPU modules are created automatically when a BCTC
shelf is created. So you may just need to add other modules.

> Module Configuration > Create Module (ADD MODULE)

to open the window shown in the following figure.
FIGURE 41 ADD MODULE COMMAND INTERFACE
following table.
TABLE 27 ADD MODULE PARAMETERS
Location Location of the module in the system, format:

RACK-SHELF-SLOT, range: RACK: 116,
SHELF: 14, SLOT 117
Module No. ID of the module to create, unique in the NE,

range: 1127
The OMP module number must be 1 and the
RPU module number must be 2. New modules
are numbered from 3.
Module 1 Type Type of Module 1 on the corresponding board

Module 2 Type Type of Module 2 on the corresponding board

CPU Type CPU type of the module, options: X86,

CENTRINO
Set it according to the specific board.
Backup Mode Backup mode of this module

Module 1 User Alias of Module 1, range: 050 characters

Alias
Module 2 User Alias of Module 2, range: 050 characters

Alias


mand.
END OF STEPS
Postrequisite Add units other than UMIC with the ADD UNIT command.
5.6 Configuring TCP Transfer for

TIPI
The TIPI unit is created.
The Local Office Distribute Style option in global data con-
figuration is set to SIPI.
Context TCP transfer configuration is required for a TIPI unit to realize the
communication between foreground and background and the com-
munication between two offices.
The TCP transfer configuration should follow the following rules.
Only the TCP transfer information of the foreground (including
OMP) of the local office is required.
Each module needs two IP addresses, one for internal use and
the other for external use.
Each internal IP address needs one entry, IP address + server-
end internal port number.
The server-end internal port number should be 60000 + mod-
ule number (1127).
Each external IP address needs two entries, IP address +
client-end external port number, and IP address + server-end
external port number.
The client-end external port number should be 5000 + module
number (1127).
The server-end external port number should be 50000 + mod-
ule number (1127).
> TCP Transmit Configuration > Create TCP Transmit
(ADD TCPTRANS) to open the window shown in the following
figure.

FIGURE 42 ADD TCPTRANS COMMAND INTERFACE
following table.
TABLE 28 ADD TCPTRANS PARAMETERS
ID ID of this TCP transfer configuration item,

range: 1512
Module Module that this TCP transfer configuration

item is for. It is numbered uniformly in the NE
system. Value range: 1-127. Set the value
according to the networking plan.
IP Address Type Options include IPv4 and IPv6. It is generally

set to IPv4. Set it according to your
networking plan.
VPN ID Value range: 0-65535; set it to 0.
IP Address IP address of the foreground module

Port Port number for this IP address, range:

165535
Set it according to your networking plan. The
same setting as in the DSA node configuration
is recommended.
For the recommended port number, refer to
the Context information.
Alias Alias of this TCP transfer configuration item,

length: 050 characters

mand.
END OF STEPS
Postrequisite Add service nodes, including the DBIO, DSA (if deployed on FE)
and DST by using the ADD BACKSVR command. Refer to topic
6.1 for details.

5.7 Setting the IP of the OMP

module
The unit configuration is complete.
Context This topic describes the procedure to set OMP information such as
the IP address that the OMP module uses to communicate with the
OMM.
mands > Device Configuration > Global Data Configura-
tion > Modify Global Data OMP Information (SET OMP)
to open the command interface shown in the following figure.
FIGURE 43 SET OMP COMMAND INTERFACE
following table.
TABLE 29 SET OMP PARAMETERS
OMP Background ip IP address of the OMP for communication

address with the OMM, IPv4 typ, for example,
129.0.31.office ID or 192.168.office ID.1
OMP Background ip Subnet mask of the OMP, IPv4 type, for

mask example, 255.0.0.0
OMP to OMC IP address of the gateway between the OMP

GATEWAY and the OMM, IPv4 typ
OMC SERVER IP address of the OMM server subnet, IPv4

SUBNETWORK type, default: 255.0.0.0
Not required.


mand.
END OF STEPS
Postrequisite Configure time zone.

Chapter 6 Server Node
Configuration

>> Adding a DBIO/DSA/DST Node
>> Setting the Connection Between a Service Server Node and the OMM
6.1 Adding a DBIO/DSA/DST Node

The time zone configuration is complete.
Context This topic describes the procedure to add a service server node (a
logical object), so that the connection between the Front End (FE)
and the BE servers may be established.
Service server nodes include DBIO, IDSA (when deployed in a
server cabinet), PDSA (when deployed in a server cabinet), and
DST.
mands > Device Configuration > Server Node Configura-
tion > Back Server > Create Back Server (ADD BACKSVR)
to open the window shown in the following figure.
FIGURE 44 ADD BACKSVR COMMAND INTERFACE
following table.

TABLE 30 ADD BACKSVR PARAMETERS
Module No. Module No. of the service node to create,

range: 130255
Module Type Type of the service node to create

Necessary modules include DBIO, IDDSA,
PDSA, and SAVE (that is, DST).
IP Address IP address of the service server node to

create, IPv4 address type
Alias User-defined node name, range: 050

characters

mand.
END OF STEPS
Postrequisite Add the connection between the service server node and the OMM
network management system.
6.2 Setting the Connection

Between a Service Server Node
and the OMM
Service nodes including DBIO, DSA and DST are configured.
Context This topic describes the procedure to establish the connection be-
tween the a service node and the OMM so that the service node
may communicate with the OMM. Service nodes include DBIO, DSA
(when deployed in a server cabinet), and DST.
mands > Device Configuration > Server Node Configu-
ration > Back Server Node Configuration > Create Back
Server Node Configuration (ADD HSERV) to open the win-
dow shown in the following figure.

Chapter 6 Server Node Configuration
FIGURE 45 ADD HSERV COMMAND INTERFACE
following table.
TABLE 31 ADD HSERV PARAMETERS
Back Service Module Module No. of the service server node to

No. connect, range: 130250
OMC Module No. Module No. of the network management

system server, range: 129254, default:
129
User Label User-defined name of this connection,

range: 050 characters

mand.
END OF STEPS
Postrequisite Perform office configuration.


Chapter 7 Office Configuration
>> Creating Signaling Points of the Local Office
>> Configuring the Local Office
>> Adding an Adjacent Office
7.1 Creating Signaling Points of

the Local Office
Service nodes including DBIO, DSA and DST are configured.
Context This topic describes the procedure to configure signaling points of
a newly created office.
mands > Office Data Configuration > SP of Local Office
Configuration > Create Local Office Signaling Point (ADD
OPC) to open the window shown in the following figure.

FIGURE 46 ADD OPC COMMAND INTERFACE
following table.
TABLE 32 ADD OPC PARAMETERS
Network Type Sequence number of the local office network

type, range: 1255.
When the local office is in multiple signaling
networks, the signaling network is numbered
in the office. The network type of the local
office must be identical with the adjacent
office.
Alias Alias of this local office, range: 150

characters
Area Code Area code of local office, range: 06 digits,

with no 0 at the beginning
Signaling Point Options: Three decimal digit strings in

Code Format 888/383 format (TRIPLE_DEC), Decimal
digits (DEC), Three Hexadecimal digit strings
in 888/383 format, and Hexadecimal digits
(HEX)
Set it according to Signaling Point Code
provided by the operator. TRIPLE_DEC is
often selected, for example, 3.21.1.
14 bit Signaling Signaling point code of local office, required

Point Code when 14-bit Signaling Point Code is adopted,
ranges of the three sub-codes of hexadecimal
OPC14: 07, 0255 and 07 respectively

24 bit Signaling Signaling point code of local office, required

Point Code when 24-bit Signaling Point Code is adopted,
range: 111
The three-segment signaling code is
separated by a dot character, such as 3.21.1.
Set it according to the format of signaling
point code.
Application Type Set the protocol type supported by the local

office. Set it as required. SCCP user and ISUP
user are often selected.
Dialing Prefix Dialing prefix for an outgoing call, range: 02
Network It is used in M3UA layer. When the local

Appearance signaling point interconnects with the IP
signaling point with the same network type,
their network appearance must be the same if
configured. It is 0 by default, indicating that
the network appearance is not configured.
Info A flag field, options: No use, valid network

appearance, invalid network appearance
Other Attribute Options: INSI (Featuring INSI function),

TRANS (Translation Node)
It is not generally required.
Work Domain Range: 0255

Index The default value (0) is recommended.

mand.
END OF STEPS
Postrequisite Configure the local office.
7.2 Configuring the Local Office

You have logged in to the OMM client and has the right to per-
form equipment configuration.
The local signaling point configuration is complete.
Context This topic describes the procedure to configure basic information,
office type, signaling point type and signaling point restarting of
the local office.


mands > Office Data Configuration > Local Office Con-
figuration > Create Local Office Config (ADD LOFC) to
FIGURE 47 ADD LOFC COMMAND INTERFACE
following table.
TABLE 33 ADD LOFC PARAMETERS
Local Office Type Normally, Local Exchange, National Toll

Exchange and In one Area are selected.
If the International Toll Exchange is
selected, then Local Exchange can not be
selected.
Network Type It must be consistent with the network

type configured in the local office signaling
point configuration.
Sequence In Area Sequence number of the local office in the

signaling network, range: 0-255, default:
0
Test Code Contents in the test message sent by MTP,

range: 015 digits
Signaling Point Type Options include SEP, STP and STEP. If the
local office acts as both signaling end point
and signaling transfer point, then select
"STEP(Signaling end/transfer point)". Set
it according to the signaling function of the
local office in the actual networking.
Local Office Options include Default, French, English,

Language German and Russian. The default value is
recommended.
Reset Time(ms) Range: 0-65535, default: 10000

Signaling Point Set it to YES if the signaling point is needed

Restart to restart.
It is YES by default.
Alias Alias of this local office, range: 0-50

characters

mand.
END OF STEPS
Postrequisite Configure adjacent offices.
7.3 Adding an Adjacent Office

You have logged in to the OMM network management system.
The local office configuration is complete.
Context This topic describes the procedure to add an adjacent office.
mands > Office Data Configuration > Adjacent Office
Configuration > Create Adjacent Office (ADD ADJOFC)
to open the command interface shown in the following figure.

FIGURE 48 ADD ADJOFC COMMAND INTERFACE
following table.
TABLE 34 ADD ADJOFC PARAMETERS
Office ID ID of the adjacent office, range: 1-2048

ID of the adjacent office which supports
broadband connections must be less than 40.
Otherwise, data can not be synchronized to the
foreground. And there is no restriction to the
ID of the adjacent office which does not support
broadband connections. Set it according to the
networking plan.
Alias Alias of this adjacent office, range: 1-50

characters

Network Type Select the signaling network where the adjacent

office signaling point locates. Value range:
1-255. It corresponds to the network type
set in 7.1. Set the value according to the
networking plan.
Office Type Type of the adjacent office

Click to open the Office Type dialog box
and then select a desired value on the dialog
box. Set it according to the networking plan.
Signaling Point Options include Triple decimal numeric

Code Format characters in 888/383 format, Decimal number,
Triple hexadecimal numeric characters in
888/383 format and Hexadecimal number.
Set it according to Signaling Point Code
provided by the operator. The "Triple decimal
numeric characters in 888/383 format" option
is often selected, for example, 3.21.1.
Signaling Point Signaling point code type of the adjacent office.

Code Type Options include 14-bit signaling point code
and 24-bit signaling point code. It is 24-bit
signaling point code in China. Set it according
to the networking plan
Signaling Point Range: 1-11 characters. Set it according

Code to the format of signaling point code. The
three-segment signaling code is separated by
the stop character, such as 3.21.1.
Area Code Area code of the adjacent office, without 0 at

the beginning, range: 0-6 digits
Association Type If there is a direct physical connection between

the adjacent office and the local office, then
select "Direct connection mode". If there are
transfer signaling points, then select "Half
direct connection mode". Set it according to
the current networking mode.
Signaling Point Options include SEP, STP and STEP. If this

Type adjacent office acts as both signaling end point
and signaling transfer point, then select STEP
(Signaling End/Transfer Point. Set it according
to the signaling function of the adjacent office
in the actual networking.
Subservice Options include International signaling point

Function code, International standby signaling point
code, National signaling point code, National
standby signaling point code. It is National
signaling point code by default.
Office Attribute American Standard, no need to configure

it if American Standard is not required.
Options include ISN(Has ISNI Function),
TRANS(Translate Node) and TEST(Need Test
Info:0X02/0X01. Set it according to the actual
networking plan.

Subprotocol The default value is recommended.

Type
Test Flag Set whether the test flag is needed. It is YES

by default.
Broadband If the lower layer of the signaling is MTP2

Attribute link, then set it to NO(Not Support Broadband
Attribute). If the lower layer of the signaling
is ATM or IP link, then set it to YES(Support
Broadband Attribute). When E1/T1 access
mode is adopted, set it to the default value
NO(Not Support Broadband Attribute).
Domain Type If the local office is a signaling point in SCN

domain and connects to the signaling point
in IP domain by SGW, then SGW is set to
DOMAIN_SCN and the quasi-asscociation
signaling point in IP domain is set to
DOMAIN_IP.
If the local office is a signaling point in IP
domain and connects to the signaling point
in SCN domain by SGW, then SGW is set to
DOMAIN_IP and the signaling point in SCN
domain is set to DOMAIN_SCN.
When E1/T1 access mode is adopted, select
DOMAIN_SCN(Office Signaling Point in SCN
Domain).
Protocol Type Options include CHINA, ITU and ANSI. Set it

according to the networking condition.
Cluster ID Range: 0-65535. The default value is

recommended.
Receive CGN Whether to receive the caller number and the

position of the caller, range: 0-39.
The default value is recommended.
Extend Info Options include INKA (Incoming calling number

contains KA) and OUTKA (Outgoing calling
number contains KA). The default value is
recommended.
Office Info The default value (CIC_PCM) is recommended.
Related Office ID Range: 0-2048. The default value is

recommended.
Office Extend Options include MTP (Hongkong MTP standard)

Info and DUPU (Screen DUPU Message). The default
value (null) is recommended.

mand.
END OF STEPS
Postrequisite If the ATM over E1 access mode is used, perform HSL con-
nection configuration. (See topic .)

If the TDM access mode is used, perform signaling link set

configuration. (See topic 8.2.1.)
If the IP access mode is used, perform SCTP link configuration.
(See topic 8.1.1.)


Chapter 8 Signaling Configuration
>> SIGTRAN Configuration
>> MTP Configuration
>> SCCP Configuration
8.1 SIGTRAN Configuration

8.1.1 Adding an SCTP Basic
Connection

The office configuration is complete.
Context This topic describes the procedure to configure basic information
of an SCTP association with an adjacent office in IP-access mode.
mands > Signal Configuration > SIGTRAN Data Configu-
ration > SCTP Configuration > Create SCTP (ADD SCTP-
CONN) to open the command interface shown in the following
figure.

FIGURE 49 ADD SCTPCONN COMMAND INTERFACE
following table.
TABLE 35 ADD SCTPCONN PARAMETERS
Module No. Signaling module number that the SCTP

association attributes to. This association is
maintained by the bearer and signaling on this
module. SMP module number, in the range
of 1-127.
Remote Office ID ID of the adjacent office which connects to

the association directly, range: 0-2048. Set it
according to actual configuration.
Bearer Protocol Used to identify the upper layer protocol

Type type born by this association. Configure it
according to the interface protocol stack in
actual networking. When M3UA/SCTP protocol
stack is used to transfer signaling messages of
upper layer users, select SCTPPROT_M3UA.

Application Association has two application attributes:

Attribute as Server or as Client. The association
establishment is originated by the client. The
two ends of the association have different
application attributes. Normally, MSC(S) is set
to Client and ZXUN USPP is set to Server.
Local IP [Port No.]+[IP Address] constitute an

association link. Different associations should
be configured with different port numbers
without any conflicts. IP address of the local
end of the association, which is also the
peer-end IP address of the remote office. Enter
IP address of the virtual interface on local end.
Local Port SCTP port number of the association on the

local office, which is also the peer-end port
number of the remote office. It is range:
1-65535. Enter local SCTP port number.
Remote IP IP address of the peer end of the association,

which is also the local-end IP address of the
remote office. Enter IP address of the virtual
interface on remote end.
Remote Port SCTP port number of the association on the

remote office, which is also the local-end port
number of the remote office. It is range:
1-65535. Enter remote SCTP port number.
Alias Alias of the SCTP association, range: 1-50

characters.
SCTP ID Global number of SCTP association, range:

1-1024.
MGW Remote ID of the MSCS connected to MGW. Range:

MSCS ID 0-5. The default value 0 is recommended.
Quantity Of Stream is a unidirectional logical channel in the

In-stream association. Data on the same stream can be
transmitted in a certain order, range: 1-17. It
should be consulted by technical personnel on
the two ends. It is recommended to keep the
default value 16.
Quantity Of Stream is a unidirectional logical channel in the

Out-stream association. Data on the same stream can be
transmitted in a certain order, range: 1-17. It
should be consulted by technical personnel on
the two ends. It is recommended to keep the
default value 16.

Data max Retry When a signaling message is sent from one

Times 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 backup IP address
to ensure that the receiving end can receive
this message in time. When the times of
continuous data transmission failure on an IP
channel reaches the set MAXRTRY, then this IP
channel is marked as an unavailable one and
all data messages are taken over by other IP
channels, range: 1-10. It should be consulted
by technical personnel on the two ends. It is
recommended to keep the default value 5.
Maximum Value The maximum time-out value of the timer,

Of RTO (10ms) range: 10-3000. It is 500 by default. The
default value is recommended.
Minimum Value The minimum time-out value of the timer,

Of RTO (10ms) range: 10-1000. It is 50 by default. The
default value is recommended.
Initial Value Of The initial time-out value of the timer, range:

RTO (10ms) 10-3000. It is 100 by default. The default
value is recommended.
Heartbeat SCTP end point sends the HEARTBEAT block

Interval (10ms) periodically 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. It is 500 by default. The default
Next Hop Tag It is NO by default. The default value NO is

Fixed recommended.
SCTP Max Retry Controls the maximum retrying times of SCTP

Times association on all channels. When this value
is exceeded, SCTP association stops and
transmission failure is reported, range: 1-20.
The default value 10 is recommended.
Delay Ack Time The time of the delay acknowledgment

(10ms) timer, range: 0-20. The default value 20 is
recommended.
Maximum Burst Range: 1-127. The default value 4 is

Data Packet recommended.
Primary Path The preferred path, set it according to the

actual networking. The default value (Remote
IP 1) is recommended.


mand.
END OF STEPS
Postrequisite Configure ASPs.
8.1.2 Adding an ASP

The SCTP association configuration is complete.
Context This topic describes the procedure to configure ASP information for
defining the one-to-one correspondence between ASP and SCTP
association.
mands > Signal Configuration > SIGTRAN Data Config-
uration > ASP Configuration > Create ASP (ADD ASP) to
FIGURE 50 ADD ASP COMMAND INTERFACE
following table.
TABLE 36 ADD ASP PARAMETERS
SCTP ID Associated with SCTP ID in SCTP Configuration,

range: 1-1024
Alias Alias of this ASP, range: 1-50 characters
ASP ID It is numbered from 1. It is recommended to use

the same ID with SCTP. Range: 1-1024.

Self-loop Flag Used to set if ASP has self-loop. Self-loop is used

for test. The default value NO is recommended,
indicating that there is no self-loop.
Locked Flag Used to set if ASP is in locked status when

starting. Locked setting is used for management.
The default value NO is recommended, indicating
that ASP is not in locked status.

mand.
END OF STEPS
Postrequisite Configure ASs.
8.1.3 Adding an AS

The ASP configuration is complete.
Context The AS information defines which ASPs compose an AS. An AS is a
logical entity corresponding to a set of routing contexts. This topic
describes the procedure to configure the AS information when IP
access mode is used.
mands > Signal Configuration > SIGTRAN Data Configu-
ration > AS Configuration > Create AS (ADD AS) to open
the interface as shown in the following figure.

FIGURE 51 ADD AS COMMAND INTERFACE
following table.
TABLE 37 ADD AS COMMAND PARAMETERS
Adaptation Layer It should be consistent with that on

Protocol adjacent office. M3UA is recommended.
ASP It is associated with ASP ID in ASP

Configuration, format: 1-xx
Alias Alias of this AS, range: 1-50 characters
AS ID A unique ID of the AS. It is recommended

to use the same ID with ASP for the ease
of memory.
If Routing Context Sets if the routing context exists. The

exists default value is recommended.
Routing Context ID A field which is negotiated by technical

personnel on local office and its adjacent
office and identifies AS uniquely. This value
can be configured as required but it must
be consistent on the two ends.

Usage Tag For all AS usage tags, in the case of ASP

and SGP used for the two end offices of
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. If the
upper signaling messages carried by the
AS are only transmitted between the two
offices, IPSP is used. One end is set to
IPSP_Server and the other end is set to
IPSP_Client. In this case, the Client/Server
configuration must be consistent with that
in SCTP association configuration (8.1.1).
User Type AS supported user type, defining upper

layer user type using AS. There are sever
user types currently: TUP, ISUP, BICC,
H.248, ALCAP, PCA and SCCP. For ZXUN
USPP, ISUP and SCCP are often selected.
It is configured according to the current
network protocol type.
Subsystem Types No need to configure.
Service Mode A supported service mode. Override mode

and load sharing mode. In the override
mode, it is only necessary to set one ASP in
activated status. In the load sharing mode,
it is necessary to set N ASPs in activated
status and K ASPs in deactivated (backup)
status. Note: the sum of N plus K must be
not more than the actual number of ASPs.
N Value of Load Share In the load sharing mode, the number of

Mode ASPs in activated status is recommended
to be set as 1.
K Value of Load Share In the load sharing mode, the number

Mode of ASPs in deactivated (backup) status
is recommended to be set as the total
number of configured ASPs minus N.

mand.
END OF STEPS
Postrequisite Configure M3UA static routes.
8.1.4 Adding an M3UA Static Route


The AS configuration is complete.

Context M3UA static route table is maintained by ASP of AS. When AS is
in activated status, that is, the service is available, the ASP list is
circularly filled by the activated ASPs of AS. M3UA implements the
signaling distribution by maintaining AS status.
uration > M3UA STATIC ROUTE > Create M3UA STATIC
ROUTE (ADD M3UART) to open the command interface
FIGURE 52 ADD M3UART COMMAND INTERFACE
following table.
TABLE 38 ADD M3UART PARAMETERS
M3UA Static ID of this M3UA static route to add, range:

Route ID 1640
AS ID Range: 1-640. It must be an AS ID already

configured .
Route Array Options include By Turns, Local Module First

Mode and Nature. It is By Turns by default, which
is recommended.
Alias Alias of this M3UA static route, range: 1-50

characters

mand.
END OF STEPS
Postrequisite Configure SIO location AS.
8.1.5 Adding an SIO Location AS


The M3UA static route configuration is complete.
Context SIO is the abbreviation of Service Information Octet, which iden-
tifies which protocols such as ISUP, SCCP, BICC and so on are
used on M3UA. Configuring SIO location AS is to locate a service
to M3UA static route. This configuration item describes the routing
information of signaling message. That is, When receiving a sig-
naling message, the product determines to which AS the message
should be sent according to the network type, destination signal-
ing point code, source signaling point code and service indicator.
This topic describes the procedure to add an SIO location AS for
IP-access mode.
uration > SIO Location AS Configuration > Create SIO
Locate AS (ADD SIOLOCAS) to open the command inter-
face shown in the following figure.
FIGURE 53 ADD SIOLOCAS COMMAND INTERFACE
following table.
TABLE 39 ADD SIOLOCAS PARAMETERS
SIO Locate AS ID ID of this SIO location AS, range: 1-2048.

It is recommended to use the same
identification with AS.
Alias Alias of this SIO location AS, range: 1-50

characters, e.g.SIOLOCAS

Service Indication Used to identify user type that the

transferred message belongs to. Various
user types can be located to a same AS with
the prerequisite that the AS supports these
user types.
Create the AS_SIO_SCCP and AS_SIO_ISUP
service indications for each adjacent office
to support MAP and ISUP protocols.
Destination Office The adjacent office ID corresponding to the

ID destination signaling point of M3UA. It is
necessary to associate it with Office ID in
Adjacent Office Configuration. 12048
Origination Office Office ID corresponding to the originating

ID signaling point of M3UA, range: 0-65535.
It is 65535 by default. If it is set to 0
(local office), then the message starts
from the local office. At this time, the
routing context selects routes according
to DPC+NET+OPC+SIO. 65535 indicates
that the OPC field is invalid. In this case,
the routing context only can select routes
according to DPC+NET+SIO. The default
M3UA Static Route M3UA static route of the located AS,

ID 1 associated with M3UA Static Route ID in
M3UA Static Route configuration, range:
1-640
M3UA Static Route Range: 0-640. It is 0 by default, which

ID 2 means no M3UA Static Route 2.

mand.
END OF STEPS
Postrequisite Perform the GT translation selector configuration. Refer to topic

8.3.2 for details.
8.2 MTP Configuration

8.2.1 Adding a Signaling Link Set


The office configuration (TDM access mode ) or ATM PVC con-

figuration ("ATM over E1" access mode) is complete.
Context This topic describes the procedure to configure MTP signaling link
set to the adjacent office. Signaling Link Set is a set of several
signaling links that connect two signaling points. Several signaling
links between the local office and some adjacent office consist of
a signaling link set.
Steps 1. Click Views > Terminal on the menubar of NetNumen(TM)
M30 interface to enter the Terminal interface.
mands > Signal Configuration > MTP Data Configuration
> Signaling Link Group > Create Signaling Linkset (ADD
N7LKS) to open the command interface shown in the follow-
ing figure.
FIGURE 54 ADD N7LKS COMMAND INTERFACE
following table.
TABLE 40 ADD N7LKS PARAMETERS
Office ID Associated adjacent office ID of the signaling

link set, adopting Office ID in Adjacent Office
Configuration.
Linkset Type For signaling link sets based on E1/T1

connection, the following three options can be
selected: 64k narrowband signaling link, n*64k
narrowband signaling link or 2M narrowband
signaling link.
64K 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
64Kbps.
n*64K means that the narrowband signaling
links in the signaling link set occupy n serial
time slots (8n25) on one E1/T1 line.
2M 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.984Mbps.
For the signaling link set based on ATM
connection, select "Broadband Link Set". For

the signaling link set based on IP connection,
select "M2PA Link Set". For the signaling link
set to ZXUN USPP, "64K Narrowband Link Set"
is selected.
This parameter must be consistent at the two
ends.
Linkset ID Signaling link set ID, range: 11024,

numbering from 1. It is globally unique. It
is recommended to be consistent with the
adjacent office ID.
Link Error Basic Error Revision: by using non-compelled,

Revision 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 (PCR):
by using non-compelled, positive
acknowledgement and cyclic retransmission
error correction method, the message signal
units stored in the retransmission buffer
without any positive acknowledgements are
retransmitted automatically when there are not
any new message signaling units or link status
signaling units to be transferred. If there is a
new signal unit, retransmission cycle is paused
and the signaling unit is transferred first.
When the link transmission delay is less than
15ms, Baic Error Revision is adopted. And
when the link transmission delay is more than
15ms, PCR is adopted. This parameter must be
consistent on the two ends. Select a method
according to the requirements of the operator
and the actual link transmission delay.
Alias Alias of the signaling link set, range: 1-50

characters

mand.
END OF STEPS
Postrequisite Configure signaling links.

Adding the E1/T1 signaling link when the TDM access mode is
used. This manual takes the E1 as an example.
Adding the ATM signaling link when the "ATM over E1" access
mode is used.
8.2.2 Adding an E1 Signaling Link



The signaling link set configuration is complete.
Context Signaling links refer to signaling channels between two offices, in-
cluding narrowband signaling links and broadband signaling links.
ZXUN USPP only has narrowband signaling links. This topic de-
scribes the procedure to create signaling links with E1 bearer type.
Steps 1. Click Views > Terminal on the menubar of the NetNu-
men(TM) M30 interface to enter the Terminal interface.
> Signaling Link Configuration > Create SPB Signaling
Link (ADD N7LNKE1) to open the interface as shown in the
following figure.
FIGURE 55 ADD N7LNKE1 COMMAND INTERFACE
following table.
TABLE 41 ADD N7LNKE1 PARAMETERS
Linkset ID ID of the signaling link set to which the

signaling link belongs
SMP Module No. Serial number of the SMP module which

manages the signaling link
One SMP module can be configured with 64
signaling links at most.

Alias Alias of this E1 signaling link, range: 150

characters
Link No. Global number of the signaling link, range:

15000. Link numbers in different link sets
can not be the same. Set it according to your
networking plan. It is recommended to be
consistent with the adjacent office ID at the
peer end.
SPB Unit No. Unit No. of SPB board where the E1 line of
the link is connected. Set it according to Unit
Configuration in Physical Configuration.
SPB CPU SPB CPU No. An SPB board has four CPUs
(subunits). The E1 number of the signaling
link has no fixed relation with SPB subunit
number. One SPB board provides 16 E1 lines
and supports 64 64kbps narrowband links,
so these narrowband links must be allocated
uniformly in the subunit.
SPB E1 SPB board provides 16 E1 lines with numbers

from 9 to 24. E1 line numbers correspond to
E1 lines on the rear board of SPB board. Set
an E1 line number according to the connected
E1 line.
SPB E1 Timeslot The starting timeslot on SPB E1 subunit

Start occupied by the outgoing E1 signaling link.
The numbers of 64Kbps signaling links
are range: 1-31. This parameter must be
consistent on the two ends.
SPB E1 Timeslot The amount of consecutive timeslots on SPB

Amount E1 subunit occupied by the outgoing E1
signaling link. For 64Kbps signaling links, this
parameter is fixed to 1. This parameter must
be consistent on the two ends.
SLC Signaling link code, range: 0-15. A signaling

link set has 16 narrowband signaling links
at most. Signaling link codes in the same
signaling link set can not be the same,
which must be consistent with those on the
peer-end office.
Self Loop There is no self loop normally. Select No.
Link Info The link supports E1 or T1. Select E1.
FCPL Thresh- Load sharing ratio (%) of this link, range:

old(ERL) 0100, or 255 (indicating invalid), default:
255

mand.
END OF STEPS
Postrequisite Configure signaling routes.

8.2.3 Adding a Signaling Route

The TDM (E1/T1) or ATM signaling link configuration is com-
plete.
Context Signaling Route Configuration is used to set which signaling link
set should be chosen and in which way it is chosen as signaling
routing. A signaling route is composed of two signaling link sets
at most.
This topic describes the procedure to create a signaling route when
the TDM/"ATM over E1" access mode is used.
mands > Signal Configuration > MTP Data Configura-
tion > Signaling Route Configuration > Create Signal-
ing Route (ADD N7ROUTE) to open the command interface
FIGURE 56 ADD N7ROUTE COMMAND INTERFACE
following table.
TABLE 42 ADD N7ROUTE PARAMETERS
Alias Alias of the signaling route, range: 1-50

characters.
Linkset1 ID The first signaling link set used by the route

Select one from those in Signaling Link
Group Configuration.
Value range: 0-1024; default value: 0

Linkset2 ID The second signaling link set used by the

route
Normally, the route to an associated 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 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: 01024
Signaling Route ID Global ID of the signaling route, used for

selecting the signaling route in Signaling
Office Configuration, range: 1-2000
Line Mode Among Mode of link arrangement between signaling

Linkset link sets, recommended value: Random
Order
Options:
Random Order: arranged in random
order
SLS0: arranged according to bit0 of the
SLS
SLS
SLS
SLS
SLS01: arranged according to bit0 and
bit1 of the SLS
bit2 of the SLS
bit3 of the SLS
In this configuration, the SLCs at the both
ends SLCs must be identical. Otherwise,
links may be blocked.
Line Mode Mode of link arrangement in a signaling link

In-Linkset set, recommended value: Random Order
Options:
Random Order: arranged in random
order
SLS
SLS
SLS


SLS
bit1 of the SLS
bit2 of the SLS
bit3 of the SLS
Sort Manually Whether signaling links are sorted manually,

default: No
Link List Sort the links manually. The link list is

composed of indices and link numbers.
INDEX: Index of the link, which is combined
with the link No. to compose the link list;
value range: 1-16
LINK: Serial No. of the link, which is
combined with the link index to compose the
link list; value range: 1-5000

mand.
END OF STEPS
Postrequisite Configure signaling offices.
8.2.4 Adding a Signaling Office

The signaling route configuration is complete.
Context This topic describes the procedure to create a signaling office in
the TDM or ATM over E1 access mode.
Signaling office configuration is to set the relationship between a
destination signaling office and a signaling route. Specifically, it is
used to specify signaling routes for all configured associated/quasi-
associated adjacent offices. The adjacent offices communicate
with the local office through common channel signaling.
For a specific destination signaling point, there are four levels of
route: direct route, the first round route, the second round route
and the third round route. Each level of route is composed of
several link groups, with all signaling links that connect the same
level of route working in the load sharing mode.
Steps 1. Click Views > Terminal from the menu bar of the NetNu-
men(TM) M30 main window.


> Signaling Office Configuration > Create Signaling Of-
fice (ADD N7OFC) to open the interface as shown in the fol-
lowing figure.
FIGURE 57 ADD N7OFC COMMAND INTERFACE
following table.
TABLE 43 ADD N7OFC PARAMETERS
Signaling Office ID ID of the signaling destination office, which

is also the adjacent office ID in adjacent
office configuration, range: 1-2048
Direct Route ID ID of the preferred signaling route is in

normal case, range: 12000
1st Round Route ID ID of the first optional route which may be

used in case that the normal route is not
available, range: 0-2000
2nd Round Route ID ID of the second optional route which may

be used in case that the first optional route
is also not available, range: 0-2000, default
value: 0
3rd Round Route ID ID of the third optional route which may be

used in case that the second optional route
is also not available, range: 0-2000, default
value: 0
Alias Alias of the signaling office, range: 1-50

characters.

mand.
END OF STEPS
Postrequisite Configure the GT translation selectors.

8.3 SCCP Configuration

8.3.1 SCCP Related Concepts
GT Translation Selector Configuration and GT Translation Data

Configuration belong to SCCP Data Configuration. SCCP Data
Configuration serves for SCCP routing.
In the Core Network system, MAP signaling messages between
MSC(S)/VLR and ZXUN USPP or other entities in the network are
transferred through SCCP. All entities are interconnected directly
or through Signaling Transfer Point (STP). After receiving mes-
sages from the MAP layer, SCCP sends, receives or transfers these
messages according to route labels in the messages. SCCP pro-
vides two message routing methods: Routing by GT and Routing
by DPC+SSN.
GT and DPC+SSN routing modes are mainly different from han-
dling methods when there is Signaling Transfer Point (STP) be-
tween the source signaling point and destination signaling point.
DPC+SSN routing mode requires that all signaling points in the
network, including the source signaling point, the destination sig-
naling point and STPs, should be able to identify the DPC. After
signaling arrives at an intermediate node, it is directly sent via the
MTP layer instead of the SCCP layer. In this case, More DPC data
are required for the source signaling point and the STP.
The GT routing can be used in the case that the source signaling
point and some STPs do not know the final DPC of this signal-
ing. When signaling is sent to an STP, GT shall be first translated
via SCCP into the DPC of the destination signaling point or next
hop STP before the signaling can be transferred to MTP for further
transmission. When GT routing is adopted, the source signaling
point is only required to send the signaling to the next hop STP of
GT translation according to GT number prefix and STP determines
whether the signaling is sent to the next hop STP or the destina-
tion signaling point. In this case, less DPC data are required for
the source signaling point and the STP.
8.3.2 Adding a GT Translation Selector

The configuration of SIO location AS (connection with the adja-
cent office in IP access mode ) or signaling office configuration
(connection with the adjacent office in TDM or "ATM over E1"
access mode) is complete.
Context This topic describes the procedure to create GT translation selector.
GT translation selector is an entrance corresponding to each GT
translation, which is a part of GT.


mands > Signal Configuration > SCCP Data Configura-
tion > GT Translation Selector > Create GT Translation
Selector (ADD GTT) to open the command interface shown
FIGURE 58 ADD GTT COMMAND INTERFACE
following table.
TABLE 44 ADD GTT PARAMETERS
GT Type Range: 1-4

GTT1 only contains Address Property.
GTT2 only contains Translation Type.
GTT3 only contains Translation Type,
Numbering Plan and Coding Design.
GTT4 only contains Translation Type,
Numbering Plan, Coding Design and
Address Property
The default value (4) is recommended.
Translation Type It is configured when GT Type is set to 2,3

or 4. Range: 0-255.
The value 0 or 128 is recommended.
For example, it is set to 0 when Numbering
Plan is set to E.164.

Numbering Plan Options include NULL, E.164, E.214, RES,

X.121, F.29, E.210 and E.212.
The MSC(S)/VLR, HLR or MNP GT number
etc. adopts the E.164 numbering plan.
ISDNs of the subscribers adopt the E.214
numbering plan. Set it according to the
networking plan
Nature Address property, options include NULL,

SUB, INT, NATRSV, NATSIGN and CAMEL.
INT (International No.) is recommended.
SCCP Route Index ID of SCCP route, range: 0255
GT TransSelector ID ID of this GT translation selector, range:

0-255
Country Code Range: 0-4 characters. It is 86 by default.
Domestic Shortest The shortest length (number of digits) of

Bit the domestic GT number, range: 1-20. It
must be shorter than the length of analyzed
GT number. It is 5 by default.
Domestic Longest The longest length (number of digits) of the

Bit domestic GT number, range: 1-20. It must
be longer than the length of analyzed GT
number. It is 9 by default.
Int'l Shortest Bit The shortest length (number of digits)

of the international GT number, range:
1-20. It must be shorter than the length of
analyzed GT number. It is 2 by default.
Int'l Longest Bit The longest length (number of digits) of the

international GT number, range: 1-20. It
must be longer than the length of analyzed
GT number. It is 5 by default.
GT Translate Options include R_L (Right to Left To Get

Property Largest Match) and L_R (Right to Left To
Get Smallest Match). It is R_L by default,
which is recommended.
Support Calling GT Whether to enable matching the caller GT

Prefix number by prefix, default: NO
Alias Alias of the GT translation selector, range:

1-50 characters.


mand.
END OF STEPS
Postrequisite Configure GT translation data.
8.3.3 Adding GT Translation Data

The GT translation selector configuration is complete.
Context GT translation data defines all GT numbers (including local office
and remote office GT numbers) and the routing mode.
mands > Signal Configuration > SCCP Data Configura-
tion > GT Translation Data Configuration > Create GT
Translation Data(ADD GT) to open the command interface

FIGURE 59 ADD GT COMMAND INTERFACE
following table.
TABLE 45 ADD GT PARAMETERS
Called GT The minimum prefix of GT number configured

in GT translation selector for called numbers
that can identify an office. It is a part of a
GT. For example, local office HLR number,
adjacent office MSC(S) number, adjacent
office SGSN number, MSISDN and so on,
range: 1-20 digits.
Calling GT The minimum prefix of GT number configured

in GT translation selector for calling numbers
that can identify an office, range: 0-20 digits
SCCP may use the calling GT and the called
GT for addressing. If more than one office
has a same GT, messages may be transferred
to the expected office according to the calling
GT.

GT TransSelector ID of the GT translation selector adopted by

ID GT translation, range: 0-255
GTDI Serial number of number conversion,

range: 0-256. It is 0 by default, which is
recommended.
1st OFC-Turn The polling turns and times of signaling

Times List routes to each office for the first office group
when multiple-signaling-point office (or office
grouping) is configured. For example, if you
set it to office 1 twice and office 2 once, then
the routing will be office 1, office 1 and office
2. Office ID is in the range of 0-2048 and
Turn Times is in the range of 1-64. For an
associated office, its ID is set to 1 and the
times is also set to 1.
Office Group Wether office grouping is supported, default:

Support No
If Yes, offices may be divided into 4 groups,
and one group includes 4 offices at most.
If No, maximum 16 offices may be configured,
working in load-sharing mode.
2nd OFC-Turn The polling turns and times of signaling

Times List routes to each office for the second office
group
3rd OFC-Turn The polling turns and times of signaling

Times List routes to each office for the third office group
4th OFC-Turn The polling turns and times of signaling

Times List routes to each office for the fourth office
group
SSN SSN number in GT translation result. It is

NULL by default, indicating that SCCP will
not check the subsystem. The default value
NULL is recommended.
New GT A new GT number in GT translation result,

range: 0-20 digits. The default value is
recommended.
New GT Translator It is configured when the American standard

Type is adopted and there is no need to configure
it when ITUT/CHINA standard is adopted,
range: 0-255. The default value 0 is
recommended.
Include DPC And If DPC, SSN or DPC+SSN is included in GT

SSN translation result. Range: NULL, DPC or SSN.
The default value NULL is recommended.
Routing Mode Options: GT and DPC. Select it according to

the actual usage of GT number.
New GT Attribute Options: NGT, NAI, NTT, NTTES, NTTNAI. It

is NGT by default, which is recommended.

SCCP Encode Type Options: INT or USI. The default value (INT)
is recommended.
MAP Stage MAP protocol release, options: P1, P2, P2+,

R99 and R4. It is R4 by default.
For network elements MGW, MSC(S), GGSN
and SGSN, the MAP Stage is invalid.
Virtual GT Support Wether virtual GT translation is supported,

default: Not Support
TT Translation Wether TT translation is supported, default:

Not Support
Number Plan Flag Whether to enable the numbering plan,

default: No
New Number Plan Options: NULL, E.164, X.121, F.69, E.210,

E.212 and E.214.
Service Type Options: NULL, GSM and CDMA

Alias Alias of this GT translation data item, range:

0-50 characters.
Note the following when you set the parameters.

If you enter a calling GT number, then it is to add calling
GT translation data, or otherwise, it is to add called GT
translation data.
If you are not enabling calling GT, do not enter any calling
GT number.
If virtual GT translation is supported, you need to config-
ure number conversion No. + office ID as the key for the
flexible GT number conversion policy. The office ID refers
to the one from 1 to 16 or the standby office ID.
If the office grouping is not supported, you can configure
at most 16 offices with each office sharing the load.
If the office grouping is supported, you can divide the of-
fices into 4 groups with each group configured with at most
4 offices. Among the 4 groups, the first group has the high-
est priority and the fourth group has the lowest priority.
Each office in the group shares the load.
If office grouping is enabled and the office adopts 1+1 re-
dundancy protection, Group 1 should be configured with
one office (Active), and Group 2 should be configured with
another office (Standby).
If the system supports GT matching by prefix, the selector
may have GT numbers of maximum 6 different lengths.


mand.
END OF STEPS
Postrequisite Perform IP stack configuration.


Chapter 9 IP Stack Configuration
>> Checking IPv4 Interface Information
>> Entering Interface Configuration Mode
>> Entering Loopback Interface Configuration Mode
>> Configuring Interface IP Address
>> Adding a Group of Active/Standby Interfaces
>> Configuring Static Route
9.1 Checking IPv4 Interface

Information
The user has logged in to the OMM client and has the right to
perform data configuration.
The offline data configuration is complete and the configuration
data are uploaded.
The connection between the OMM network management sys-
tem and the OMP module is normal.
Context You may need to check the information of existing IPv4 interfaces
before or after configuring interface addresses of a TIPI or SIPI
board or the loopback address of a RPU module.
This topic describes the procedure to show IPv4 interface informa-
tion.
mands > Device Configuration > IP Stack Configuration
> Interface Commands > Show Interface IPV4 Brief
Info(SHOW IP INTERFACE BRIEF) to open the window
FIGURE 60 SHOW IP INTERFACE BRIEF COMMAND INTERFACE


mand.
The results displayed on the Message Report tab are as
shown in the following figure. You can check the results
according to the corresponding network planning data.
In the first parameter, five parts of digits separated with :
respectively indicate the subsystem No., module No., unit
No., sub-unit No. and port No..
The values of the second and third parameters should be
up.
The fourth parameter should indicate the correct interface
IP address.
The fifth parameter should indicate the correct mask.
FIGURE 61 SHOW IP INTERFACE BRIEF RESULT
5. Check the IPv4 interface information on the Message Report

tab.
END OF STEPS
Postrequisite If the IP addresses are not correct, configure the loopback inter-
face or entering interface configuration mode to configure the in-
terface addresses. Refer to topic 9.2 for procedures to configure
the interface IP address or topic 9.3 for procedures to configure
the loopback interface address.
If the IP addresses are correct, configure the interface group if
necessary. Refer to topic 9.5 for details.
9.2 Entering Interface

Configuration Mode

Offline data configuration and data synchronization is com-
plete.
Context Only when you have entered the interface configuration mode can
you configure on line the interfaces of IP stack for SIPI board and
TIPI board.
Views > MML Terminal to open the MML Terminal inter-
face.
> Interface Commands > Enter Interface Mode (INTER-
FACE) to open the interface shown in the following figure.
FIGURE 62 INTERFACE COMMAND INTERFACE
following table.
TABLE 46 INTERFACE PARAMETERS
Sub-System Serial number of the subsystem that the TIPI or

SIPI unit belongs to, range: 0255, 0 generally
Module Serial number of the MP module that the TIPI

or SIPI unit belongs to, range: 1-65535
Unit Serial number of the TIPI or SIPI unit, range:

1-65535

Sub-Unit Subunit No.

Set it to 1.
Port Port No.

The port No. of the external network interface
on the SIPI or TIPI rear board. Altogether four
interfaces, numbered 14 respectively from up
to down

mand.
END OF STEPS
Result Enter the interface configuration mode.

Postrequisite Configure interface IP addresses of TIPI boards and SIPI boards.
9.3 Entering Loopback Interface

Configuration Mode
Offline data configuration and data synchronization is com-
plete.
Context To configure IP addresses of an RPU module, you need enter the
loopback interface configuration mode first.
face.
> Interface Commands > Create (Enter) Loopback Inter-
face (INTERFACE LOOPBACK) to open the interface shown

FIGURE 63 INTERFACE LOOPBACK COMMAND INTERFACE
4. Set the parameter. For details about the parameter, see the
following table.
TABLE 47 INTERFACE LOOPBACK PARAMETERS
Port Port No. of the RPU module used as the

loopback interface

mand.
END OF STEPS
Result Enter the loopback interface configuration mode.

Postrequisite Configure the IP address of the loopback interface.
9.4 Configuring Interface IP

Address
Prerequisites To configure IP addresses of a TIPI or SIPI board, you need
enter the interface configuration mode first. See 9.2 for refer-
ence.
To configure IP addresses of an RPU module, you need enter
the loopback interface configuration mode first. See 9.3 for
reference.
Context When IP-mode inter-connection is adopted, you need on line con-
figure actual interfaces for SIPI boards, TIPI boards and the RPU
module. This topic describes the procedure to configure an IP ad-
dress.
face.
> Interface Commands > Create IP Address Of Interface
(ADD IP ADDRESS) to open the interface shown in the fol-
lowing figure.

FIGURE 64 ADD IP ADDRESS INTERFACE
following table.
TABLE 48 ADD IP ADDRESS PARAMETERS
IP IP address
Set according to your networking plan.
Subnet Mask Subnet Mask

Set according to your networking plan.
Broadcast Broadcast refers to the information that one

Address computer expects other computers to receive
in the network. Broadcast is used when one
computer does not know to which computer
it should communicate. Configure it as
255.255.255.255 if necessary.
Usually 255.255.255.255, indicating all IPs in
the local network
CORBA ID CORBA ID, range: 1-65535

Set according to your networking plan. It is
generally not required.

mand.
> Save Online Configuration Data (SAVE ONLINEDATA)
to open the interface shown in the following figure.
FIGURE 65 SAVE ONLINEDATA INTERFACE
7. Click the Execute(F5) button or press F5 to save the online

configuration data.
> Exit Mode (EXIT) to open the command interface shown

FIGURE 66 EXIT COMMAND INTERFACE
9. Click the Execute(F5) button or press F5 to exit the interface

configuration mode.
END OF STEPS
Result The system saves settings of the created interface IP address and
exits the interface configuration mode.
Postrequisite When the interface IP address configuration is complete, confirm
that the IPv4 interface information is correct. If the interface IP is
not configured completely, enter the interface configuration mode
to configure the corresponding interface IP.
9.5 Adding a Group of

Active/Standby Interfaces
All offline configuration is complete and uploaded.
Context USI and TIPI boards support redundancy protection of ports. A
rear board has 4 network interfaces, FE1 to FE4. ZXUN USPP uses
FE1 and FE2 only. The two ports may work either independently or
in a redundancy protection mode of 1+1 active/standby backup.
SIPI boards do not support redundancy protection of ports.
This topic describes the procedure to create a group of ac-
tive/standby interfaces.
face.
> Interface Commands > Create Interface Backup Group
(ADD INTERFACE GROUP) to open the interface shown in
the following figure.

FIGURE 67 ADD INTERFACE GROUP INTERFACE
following table.
TABLE 49 ADD INTERFACE GROUP PARAMETERS
Interface1 Complex type, format: Subsystem1mod-

ule1unit1port1
Interface2 Complex type, format: Subsystem2mod-

ule2unit2port2
Backup Mode Select ONEPLUSONE.
Note:
It is no need to specify which port is active and which is
standby. The system assigns automatically. The active port is
generally the one with a larger port number.

mand.
END OF STEPS
9.6 Configuring Static Route

All offline configuration is complete and uploaded.
The IP interfaces, loopback interface, and the group of ac-
tive/standby interfaces have been configured.

Context This topic describes the procedure to create static route for IP in-
terfaces.
For example, Office 14 adopts network segment 190, while Of-
fice 16 adopts network segment 191. And Module 3 of Office 14
(190.168.14.2, port 5003) needs to connect Module 4 of Office 16
(191.168.16.2, port: 50004). The following static routes should
be configured.
Static route for Office 14, net hop IP address: 190.168.14.100
Office 14 sends messages to Office 16 in this way:
190.168.14.2, port 5003 190.168.14.100 (through a TIPI
board in Office 14) 191.168.16.100 (through a TIPI board
in Office 16) 191.168.16.4, port: 50004
Static route for Office 16, net hop IP address: 191.168.16.100
Office 16 sends messages to Office 14 in this way:
191.168.16.4, port 50004 191.168.16.100 (through a TIPI
board in Office 16) 190.168.14.100 (through a TIPI board
in Office 14) 190.168.14.2, port: 5003
face.
> IP Route Protocol > Static Route Configuration > Cre-
ate Static Route (ADD IP ROUTE) to open the interface
FIGURE 68 ADD IP ROUTE INTERFACE
following table.

TABLE 50 ADD IP ROUTE PARAMETERS
Net Prefix IP address of the peer-end interface, IPv4

type
Mask Network mask of the peer-end interface,

IPv4 type, for example, 255.255.0.0
Next Hop IP Next hop IP address, IPv4 type

It is the gateway IP address if there is one
or the IP address of the peer-end virtual
interface if there is no gateway.
Next Hop Interface Next hop interface, format: SUBSYSTEM-

MODULE-UNIT-SUNIT-PORT
Tunnel ID ID of the tunnel interface, range: 1-1024

The default setting (null) is recommended.
Loopback Port ID of the loopback port, range: 1-128

Distance If represents the credibility of a route

protocol. The smaller a distance value is,
the higher credibility is.
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.
Range: 1-254
The default value is recommended.
VRF NAME Name of VRF table, range: 0-30 characters

It is recommended to use the default value.
Set it according to the networking plan.
Global Whether it is a global next hop

If Next Hop IP is the global next-hop IP
address, select YES; otherwise, do not set
it. It is recommended to use the default
value.
CORBA ID CORBA ID, range: 1-65535

Recommended value: null (default)


mand.
END OF STEPS


Chapter 10 Administration Domain
Data Configuration Flow

>> Administration Domain Data Configuration
10.1 Administration Domain Data

Configuration
The flow of administration domain configuration on EMS is shown
FIGURE 69 ADMINISTRATION DOMAIN CONFIGURATION FLOW


Chapter 11 Administration Domain
Basic Data Configuration

>> Adding an Administration Domain
>> Configuring Relation Between Administration Domain and DUA
>> Adding Administration Domain Function
>> Adding Administration Domain Capacity
11.1 Adding an Administration

Domain
Prerequisites The DUA node is configured.
The UDS related configuration is complete. See ZXUN USPP
Universal Subscriber Profile Platform Data Configuration(UDS)
for details.
Context This topic describes the procedure to create USPP administration
domain and to configure the relationship between the administra-
tion domain and physical offices.
2. Select NetNumen > USPP > Service Configuration > Pub-
lic Service Configuration.
mand. See ZXUN USPP Universal Subscriber Profile Platform
Data Configuration(UDS) for details.
mands > AdminDomain Basic Configuration > AdminDo-
main Configuration > Create AdminDomain Configura-
tion(ADD VHLR) to open the window as shown in the follow-
ing figure.

FIGURE 70 ADD VHLR COMMAND INTERFACE
TABLE 51 ADD VHLR COMMAND PARAMETERS DESCRIPTION
AdminDomain ID Administration domain ID, range: 1-128
AdminDomain Sub NE type of the administration domain.

Net Options include CDMA (HLR of CDMA2000),
WCN (HLR of TD-SCDMA or WCDMA) and
some others.
Need Check Logical Whether to check the home logical code

Number Segment segment.
Need Check Physical Whether to check the home physical code

Number Segment segment
AdminDomain Property of the administration domain,

property Master (active) or Slave (standby),
default: Master
Type of Mate Type of the peer-end office, options include

AdminDomain USPP_WCDMA, USPP_CDMA, WCDMA,
CDMA and other.

Chapter 11 Administration Domain Basic Data Configuration
HLRNumber of Mate HLR number of the peer-end, range: 024

HLR characters
Takeover Method Valid for a standby (Slave) administration

domain only
Options include Manual and Auto.
Takeover Check Valid for Auto takeover method, range:

Interval(s) 1900, default: 300
Takeover Check Quantity of traffic for takeover check,

Volume Threshold valid for Auto takeover method, range:
1100000, default: 1000
Allow Boss After Whether BOSS operations are allowed after

Takeover takeover, valid for Auto takeover method,
default: No
Allow DRSync After Whether DRSYNC authority is allowed after

Takeover takeover, valid for Auto takeover method,
default: No
Allow supplemen- Whether the handling of supplementary

tary service after services is allowed after the standby node
takeover has taken over, default: Yes
Allow Basic Service Whether the handling of basic services is

Before Takeover allowed after the standby node has taken
over, default: Yes
Allow Reliable Whether the handling of steady services is

Service After allowed after the standby node has taken
Takeover over, default: Yes
Allow Transient Whether the handling of transient services

Service After is allowed after the standby node has taken
Allow Take Voice Whether the retrieval of voice mailbox is

Mailbox After allowed after the standby node has taken
CDMA DSU Sync Synchronization mode of CDMA dynamic

Mode information, options include DRSYNC mode
(default) and signaling mode
Is Basic Whether the reference administration

AdminDomain for domain is copied, default: No
Copying
User Label Alias of the administration domain, range:

020 characters

mand.
END OF STEPS
Postrequisite Configure relation between administration domain and DUA.

11.2 Configuring Relation Between

Administration Domain and DUA
Prerequisites The administration domain is configured.
Context This topic describes the procedure to configure the relation be-
tween an administration domain and a DUA.
UDS Data Configuration for details.
mands > AdminDomain Basic Configuration > Admin-
Domain Relating DUA Configuration > Create AdminDo-
main Relating DUA Configuration(ADD VDUA) to open the
window as shown in the following figure.
FIGURE 71 ADD VDUA COMMAND INTERFACE
TABLE 52 ADD DSAGRP COMMAND PARAMETERS DESCRIPTION
Serial No. Serial number of the DUA under the administration

domain, range: 1-65535
AdminDo- ID of the administration domain, range: 1128

main ID Select one from the existing administration domain
IDs.
DUA Node ID ID of the DUA node to be assigned to the

administration domain, range: 1-65535
Select one from the existing DUA nodes.
User Label Alias of this administration domain/DUA relation,

range: 0-50 characters


mand.
END OF STEPS
Postrequisite Configure administration domain function.
11.3 Adding Administration

Domain Function
Context Network elements in a USPP system share one set of licenses. One
license on USPP can be used by multiple administration domains.
This topic describes the procedure to configure the administration
domain function for setting a license for an administration domain.
Data Configuration (UDS) for details.
mands > AdminDomain Basic Configuration > Admin-
Domain Function Switch Configuration > Create Admin-
Domain Function Switch Configuration(ADD VHLRLIC) to
open the window as shown in the following figure.
FIGURE 72 ADD VHLRLIC COMMAND INTERFACE

TABLE 53 ADD VHLRLIC COMMAND PARAMETERS DESCRIPTION
AdminDomain ID ID of the administration domain (virtual HLR)

whose License is required to be configured
ITEM ID Select the License corresponding to the

function required by the administration
domain from USPP License items.
User Label Alias of the administration domain function,


mand.
END OF STEPS
Postrequisite Configure administration domain capacity.
11.4 Adding Administration

Domain Capacity
Context In a USPP system, the license controls the number of subscribers
by administration domains. And subscribers are distributed to the
administration domains.
During subscriber data processing, such as adding a subscriber,
if the system finds that a relevant performance statistic value has
changed, it compares the value with the corresponding subscriber-
quantity control setting in the license, and returns a failure mes-
sage if the performance statistic value is larger than the value
defined in the license, or otherwise proceeds to process the sub-
scriber data.
This topic describes the procedure to configure administration do-
main capacity.
mands > AdminDomain Basic Configuration > AdminDo-
main Capacity Configuration > Create AdminDomain Ca-

pacity Configuration(ADD VHLRCAP) to open the window

as shown in the following figure.
FIGURE 73 ADD VHLRCAP COMMAND INTERFACE
TABLE 54 ADD VHLRCAP COMMAND PARAMETERS DESCRIPTION
AdminDomain ID Virtual HLR (administration domain) ID

whose License is to be configured
Select a virtual HLR ID from the existing
ones.
ITEM ID ID of this subscriber capacity item
ITEM Value Value of this subscriber capacity item

The sum of all item values under the same
item ID must not be larger than the total
capacity defined by the license.
User Label Alias of this subscriber capacity item, range:

0-50 characters

mand.
END OF STEPS
Postrequisite For an HSS or SPR network element, create realm names.

For other network elements, perform subscriber data distribu-
tion configuration.


Chapter 12 Subscriber Data
Distribution Configuration

>> Configuring Relation Between PDSA Group and Administration Domain
>> Adding a Physical Number Segment for an Administration Domain
>> Adding a Logical Number Segment for an Administration Domain
>> Distributing a Physical Number Segment to an ID DSA Group
>> Distributing a Logical Number Segment to an ID DSA Group
>> Distributing a Physical Number Segment to a P DSA Group
12.1 Configuring Relation Between

PDSA Group and Administration
Domain
The UDS related configuration is complete.
Context To facilitate management and maintenance, user data of a same
application type should be stored in one P-DSA.
Normally, a DSA group distribution is generated automatically
when a NE under an administration domain is created. Users can
also add DSA group distribution manually. This topic describes the
procedure to configure PDSA group in an administration domain
(VHLR).
mands > Subscriber Data Distributing Configuration >
PDSA GroupAdminDomain Relation Configuration >
Create PDSA GroupAdminDomain Relation Configura-
tion (ADD VDSAGRP) to open the window as shown in the
following table.

FIGURE 74 ADD VDSAGRP COMMAND INTERFACE
TABLE 55 ADD VDSAGRP COMMAND PARAMETERS DESCRIPTION
Serial No. Serial number of this configuration item
PDSA Group ID ID of the PDSA group. Select from the

existing PDSA groups.
A PDSA group may have a relation with
multiple administration domains, but
with only one type of NE.
AdminDomain ID ID of the administration domain to which

the PDSA group is attributed. Select
an administration domain ID from the
existing ones.
PDSA Group Subnet The type of NE corresponding to the

PDSA group. A PDSA group can only
belong to one NE.
User Label Alias of the DSA group distribution,


mand.
END OF STEPS
Postrequisite Add physical number segments for this administration domain.
12.2 Adding a Physical Number

Segment for an Administration
Domain
Prerequisites The administration domain is configured. And the Need Check
Physical Number Segment configuration item of this admin-
istration domain is set to Yes.

Chapter 12 Subscriber Data Distribution Configuration

Context On the agent, numbers are assigned to an administration domain
(virtual HLR) according to the number segment configuration of
physical numbers, such as, IMSI, PSID, MIN or LRN.
This topic describes the procedure to add a physical number seg-
ment in an administration domain.
AdminDomain Physics Number Distributing Configura-
tion > Create AdminDomain Physics Number Distribut-
ing Configuration (ADD VHLRSPN) to open the window as
FIGURE 75 ADD VHLRSPN COMMAND INTERFACE
TABLE 56 ADD VHLRSPN COMMAND PARAMETERS DESCRIPTION
ID ID of the physical number segment of the

Number Segment Type of the physical number segment

Type
Beginning Number The beginning number of the physical

number segment of the administration
domain, string type, range: 131 digits
Ending Number The ending number of the physical number

segment of the administration domain,
string type, range: 131 digits

AdminDomain ID Administration domain ID to which the

physical number segment is attributed,
range: 1128
User Label Alias of the physical number segment in

the administration domain, range: 0-50
characters

mand.
END OF STEPS
Postrequisite Add logical number segments for the administration domain if its
Need Check Logical Number Segment configuration item is set
to Yes. Otherwise, configure the distribution of physical number
segments among ID DSA groups.
12.3 Adding a Logical Number

Segment for an Administration
Domain
Prerequisites The administration domain is configured. And the Need Check
Logical Number Segment configuration item of this admin-
istration domain is set to Yes.
Context This topic describes the procedure to add a logical number seg-
ment (such as those of MSISDN or DN numbers) in an administra-
tion domain.
AdminDomain Logical Number Distributing Configura-
tion > Create AdminDomain Logical Number Distributing
Configuration (ADD VHLRSLN) to open the window as

FIGURE 76 ADD VHLRSLN COMMAND INTERFACE
TABLE 57 ADD VHLRSLN COMMAND PARAMETERS DESCRIPTION
ID ID of the logical number segment of the

Beginning Number The beginning number of the logical number

segment of the administration domain, string
type, range: 131 digits
Ending Number The ending number of the logical number

segment of the administration domain, string
type, range: 131 digits
Its length must be identical with the
beginning number.
AdminDomain ID Administration domain ID to which the logical

number segment is attributed, range: 1128
User Label Alias of the logical number segment in

the administration domain, range: 0-50
characters

mand.
END OF STEPS
Postrequisite Configure the distribution of physical number segments among ID

DSA groups.
12.4 Distributing a Physical

Number Segment to an ID DSA
Group
Prerequisites The UDS configuration is complete.


Context This topic describes the procedure to distribute a physical number
segment to an ID DSA group.
IDSA Group Physics Number Distributing Configuration
> Create IDSA Group Physics Number Distributing Con-
figuration (ADD IDSAGSPN) to open the window as shown
FIGURE 77 ADD IDSAGSPN COMMAND INTERFACE
TABLE 58 ADD IDSAGSPN COMMAND PARAMETERS DESCRIPTION
Serial No. Serial number of this physical number

segment, range: 0-65535
Number Type Type of the physical number segment
Beginning Code The beginning number of the physical

number segment, string type, range: 131
digits
ending Code The ending number of the physical number

IDSA Group ID ID of the IDSA group that the physical

number segment is distributed to, range:
1128
User Label Alias of the configuration item, range:

0-50 characters


mand.
END OF STEPS
Postrequisite Configure the distribution of logical number segments among ID

DSA groups.
12.5 Distributing a Logical Number

Segment to an ID DSA Group
An administration domain is configured.
Context This topic describes the procedure to distribute a logical number
segment to an ID DSA group.
IDSA Group Logical Number Distributing Configuration
> Create IDSA Group Logical Number Distributing Con-
figuration (ADD IDSAGSLN) to open the window as shown
FIGURE 78 ADD IDSAGSLN COMMAND INTERFACE

TABLE 59 ADD IDSAGSLN COMMAND PARAMETERS DESCRIPTION
Serial No. Serial number of this logical number

Number Type Type of the physical number segment: DN
Beginning Code The beginning number of the logical

digits
ending Code The ending number of the logical number

IDSA Group ID ID of the IDSA group that the logical

1128
User Label Alias of the configuration item, range: 0-50

characters

mand.
END OF STEPS
Postrequisite Configure the distribution of physical number segments among P

DSA groups.
12.6 Distributing a Physical

Number Segment to a P DSA
Group
An administration domain is configured.
Context This topic describes the procedure to distribute a physical number
segment to a P DSA group.


PDSA Group Logical Number Distributing Configuration
> Create PDSA Group Logical Number Distributing Con-
figuration (ADD DSAGRPSPN) to open the window as shown
FIGURE 79 ADD DSAGRPSPN COMMAND INTERFACE
TABLE 60 ADD DSAGRPSPN COMMAND PARAMETERS DESCRIPTION
ID Serial number of this physical number

Number Segment Type of the physical number segment:

Type IMSI, PSID, or MIN

digits

PDSA Group ID ID of the PDSA group that the physical

165535
User Label Alias of the configuration item, range: 0-50

characters

mand.
END OF STEPS
Postrequisite Perform agent resource configuration.


Chapter 13 Agent Resource
Configuration

>> Adding an Agent Number Segment Group
>> Adding an Agent Physical Number Segment
>> Adding an Agent Logical Number Segment
>> Adding an Operator Role
>> Adding an Operator
13.1 Adding an Agent Number

Segment Group
The administration domain basic configuration and subscriber
data distribution configuration is complete.
Context An operator may have one or more roles and thus obtain some
operation authorities. The authorities of a role include operating
administration domains, number segment groups in the adminis-
tration domain and operation codes.
The following figure shows the relation between operation author-
ities on number segment groups and roles.
FIGURE 80 ROLES AND AGENT HANDLING AUTHORITIES

This topic describes the procedure to create a number segment

group and assign it to the authorities of an administration domain.
3. On the MML Commands navigation tree, select Agent Re-
source Configuration > Agent Number Group Configura-
tion > Create Agent Number Group Configuration to open
the window as shown in the following figure.
FIGURE 81 ADD NUMGRP COMMAND INTERFACE
TABLE 61 ADD NUMGRP COMMAND PARAMETERS DESCRIPTION
Number Group ID ID of the number segment group, range:

1-65535
AdminDomain ID ID of the administration domain
User Label Alias of the segment group, range: 0-50

characters

mand.
END OF STEPS
Postrequisite Configure agent physical number segments.
13.2 Adding an Agent Physical

Number Segment
Prerequisites The agent number group is configured.

Chapter 13 Agent Resource Configuration
A number segment group may contain multiple number segments.
Within an administration domain, a number segment or a number
can not be contained by or overlaps with another number segment.
For the illustration of the relation between roles and agent author-
ities, refer to 13.1.
This topic describes the procedure to create a physical number
segment and assign it to a number segment group.
source Configuration > Agent Physical Number Segment
Configuration > Create Agent Physical Number Segment
Configuration to open the window as shown in the following
figure.
FIGURE 82 ADD AGENTSPN COMMAND INTERFACE
TABLE 62 ADD AGENTSPN COMMAND PARAMETERS DESCRIPTION
ID ID of this physical number segment,

0-65535.

number segment, range: 131 digits

segment, range: 131 digits

Number Group ID ID of the number group to which the

physical number segment is attributed.
Select a number group ID from the existing
ones.
User Label Alias of the physical number segment,

0-50 characters.

mand.
END OF STEPS
Postrequisite Configure agent logical number segments.
13.3 Adding an Agent Logical

Number Segment
Prerequisites The agent number group is configured.
A number segment group may contain multiple number segments.
Within an administration domain, a number segment or a number
can not be contained by or overlaps with another number segment.
For the illustration of the relation between roles and agent author-
ities, refer to 13.1.
This topic describes the procedure to create a logical number seg-
ment and assign it to a number segment group.
source Configuration > Agent Logical Number Segment
Configuration > Create Agent Logical Number Segment
Configuration to open the window as shown in the following
figure.

FIGURE 83 ADD AGENTSLN COMMAND INTERFACE
TABLE 63 ADD AGENTSLN COMMAND PARAMETERS DESCRIPTION
ID ID of this logical number segment, range:

0-65535.
Beginning Number The beginning number of the logical

number segment, range: 131 digits
Ending Number The ending number of the logical number

segment, range: 131 digits
Number Group ID ID of the number group to which the logical

number segment is attributed. Select a
number group ID from the existing ones.
User Label Alias of the logical number segment, 0-50

characters.

mand.
END OF STEPS
Postrequisite Configure operator roles.
13.4 Adding an Operator Role

Prerequisites The EMS network management system is working properly.
The agent number segments are configured.
Context An operator of a role has all authorities of this role. One operator
can have multiple roles and thus have their authorities.
This topic describes the procedure to add a role.
Views > Security Management to open the Security
Management interface.

2. Select Role Management from the Security Tree.

3. Click the (Create Role) button to open the Create Role
dialog box.
4. On the Basic Information tab, Set Role Name and Role
Description.
5. On the Access Rights tab, select nodes from the Operation
Tree to grand operations to the role and select nodes from the
Resource Tree to grand operation rights to code segments
under administration domains to the role, as shown in the fol-
lowing figure.
FIGURE 84 CREATE ROLE

Note:
In terms of a role, all the selected operation nodes have
the rights to operate the selected resources. If different
operation nodes are required to correspond to different re-
sources, users can configure various roles.
The checks before the nodes from the Operation Tree must
be like instead of . Otherwise, the configuration may
not take effect.
6. Click OK to finish role creation.

END OF STEPS
Postrequisite Add operators.
13.5 Adding an Operator

Prerequisites The role of this operator is created.
Context When an operator having a role has all authorities of this role. One
operator can have multiple roles and thus have their authorities.
This topic describes the procedure to add an operator.
Views > Security Management to open the Security
Management interface.
2. Select User Management from the Security Tree.
3. Click the (Create User) button to open the Create User
dialog box.

FIGURE 85 CREATE USER
4. Set User Name, Full Name, User Password and Verity

Password on the Basic Information tab page.
5. Select the corresponding role of the operator from the Role
Tree on the Role tab page.
6. Click OK to finish user creation.
END OF STEPS
Postrequisite Upload the administration domain configuration data to the related

OMM.

Chapter 14 Data Transfer
>> Uploading Configuration Data

Prerequisites The EMS network management system is working properly.
Context UDS configuration and administration domain configuration are
performed on EMS. And the configuration data should be upload
to the OMM network management system, FE and UDS. This topic
introduces the procedure to upload the data.
Views > Daily Maintenance to open the Daily Mainte-
nance interface.
2. Select Daily Maintenance > USPP > Data Maintenance
> Data Sync from the navigation tree to open the interface

FIGURE 86 DATA SYNC
3. Set the data synchronization parameters by referring to the

following table.
TABLE 64 DATA SYNCHRONIZATION PARAMETERS
Operate Type Synchronization type

Changed Tables refer to the tables of
configuration data that have been changed since
last synchronization.
All Tables refer to all the tables of configuration
data on the EMS.
Sync Option Sync OMM uploads the configuration data on EMS

to the OMM network management system only.
Sync MP uploads the configuration data on EMS
to both the OMM network management system
and the foreground MPs.

Chapter 14 Data Transfer
Options Save: Whether data are saved at once on each

module after the uploading
Toslave: Whether data are synchronized at once
to each backup node after the uploading
Timeout The upload request times out if the front-end

(100ms) processor does not make any response in this
period of time.
Range: 16000, default: 600
4. Select the Sync By Vhlr (sync by administration domain) or

the Sync By Bureau (sync by office) tab, and select the ad-
ministration domains or offices whose configuration data are
to be uploaded.
5. Click the Execute button to upload the data.
6. Click the Sync Process Info tab to check the messages re-
turned during the upload process.
7. Click the Syn Result Info tab to confirm that the upload has
succeeded.
END OF STEPS


Glossary
AS
Application Server
ASIC
Application Specific Integrated Circuit
ASP
Application Server Process
ATM
Asynchronous Transfer Mode
BCTC
Backplane of ConTrol Center
BE
Back End
CMP
Calling Main Processor
CORBA
Common Object Request Broker Architecture
CPU
Central Processing Unit
DBIO
DataBase Input & Output
DN
Directory Number
DPC
Destination signaling Point Code
DSA
Directory System Agent
DSP
Directory System Protocol
DSP
Digital Signal Processor
DST
Data Storage Transfer
DUA
Directory User Agent
EMS
Element Management System
FE
Front End
FE
Fast Ethernet
FPGA
Field Programmable Gate Array

FTP
File Transfer Protocol
GE
Gigabit Ethernet
GT
GSM/TD Dual Mode
HLR
Home Location Register
IDSA
Identity DSA
IMSI
International Mobile Subscriber Identity
IP
Internet Protocol
IPSP
IP Signaling Point
ISUP
ISDN User Part
LDAP
Lightweight Directory Access Protocol
LIC
Lawful Interception Center
LRN
Location Routing Number
M3UA
MTP3-User Adaptation layer protocol
MAP
Mobile Application Part
MGW
Media GateWay
MIN
Mobile station Identification Number
MSCS
Mobile Switching Center Server
MSISDN
Mobile Station International Subscriber Directory Number
MTP
MessageTransfer Part
NE
Network Element
OMC
Operation & Maintenance Center
OMM
Operation & Maintenance Module
PDSA
Profile DSA
PSID

Glossary
Private System Identification

RDBMS
Relational Data Base Management System
RPU
Route Protocol Unit
SCCP
Signaling Connection Control Part
SCN
Switched Circuit Network
SCTP
Stream Control Transmission Protocol
SGP
Signaling Gateway Process
SGSN
Service GPRS Supporting Node
SGW
Signaling GateWay
SIPI
Signaling IP bearer Interface
SMP
Signal Main Processor
SPB
Signaling Processing Board
SSN
Sub-System Number
STP
Signaling Transfer Point
TCP
Transfer Control Protocol
TD-SCDMA
Time Division-Synchronization Code Division Multiple Access
TDM
Time Division Multiplexing
THUB
Trunk HUB
UDS
Universal Directory Server
UIMC
Universal Interface Module for Control plane (BCTC or BPSN)
USI
Universal Service Interface
USPP
Universal Subscriber Profile Platform
VLR
Visitor Location Register
VRF
Virtual Route Forwarding

WCDMA
Wideband Code Division Multiple Access

ZXUN USPP - Basic Data Configuration - Party 2 PDF

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

ZXUN USPP - Basic Data Configuration - Party 2 PDF

Enviado por

Direitos autorais:

Formatos disponíveis

Universal Subscriber Profile Platform

Basic Data Configuration

Copyright 2010 ZTE CORPORATION.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Publishing Date (MONTH/DATE/YEAR) : 08/09/2010

ZXUN USPP Basic Data Configuration ........................... 1

will be able to:

Confidential and Proprietary Information of ZTE CORPORATION 1

Chapter 1 Introduction to UDS

After you have completed this chapter, you will know:

1.1 UDS Configuration Flow

FIGURE 1 ZXUN USPP CONFIGURATION FLOW

The recommended UDS configuration flow is shown in the following

2 Confidential and Proprietary Information of ZTE CORPORATION

FIGURE 2 UDS CONFIGURATION FLOW

1.2 Uploading Configuration Data

Confidential and Proprietary Information of ZTE CORPORATION 3

FIGURE 3 DATA SYNC

3. Set the data synchronization parameters by referring to the

TABLE 1 DATA SYNCHRONIZATION PARAMETERS

4 Confidential and Proprietary Information of ZTE CORPORATION

4. Select the Sync By Vhlr (sync by administration domain) or

Confidential and Proprietary Information of ZTE CORPORATION 5

This page is intentionally blank.

6 Confidential and Proprietary Information of ZTE CORPORATION

After you have completed this chapter, you will know:

2.1 Loading the License File

Confidential and Proprietary Information of ZTE CORPORATION 7

FIGURE 4 CHOOSE LICENSE FILE

4. Select the License file and click Open.

FIGURE 5 LICENSE INFORMATION

But the License can not be validated.

8 Confidential and Proprietary Information of ZTE CORPORATION

Postrequisite Create USPP nodes.

2.2 Creating a USPP

FIGURE 6 CREATE USPP COMMAND INTERFACE

TABLE 2 CREATE USPP PARAMETERS

TYPE Subtype of the office

USERLABEL Alias of this USPP, range: 050 characters

5. Click the Execute(F5) button or press F5 to execute this com-

Postrequisite Create network element agents.

Confidential and Proprietary Information of ZTE CORPORATION 9

2.3 Creating a Network Element

10 Confidential and Proprietary Information of ZTE CORPORATION

FIGURE 7 CREATE NE AGENT

TABLE 3 PARAMETERS FOR CREATING NE AGENT

Basic Name Name of the OMM server, 050

Vendor Name of the vendor of the OMM

IP Address IP address of the OMM server, IPv4

Version Version of the OMM server, 050

Location Location of the OMM server, 0100

Memo Additional information of the

Confidential and Proprietary Information of ZTE CORPORATION 11

Extended Port Set it to 21125.

FTP Port Set it to 21.

Postrequisite Start the network element agent.

2.4 Starting a Network Element

12 Confidential and Proprietary Information of ZTE CORPORATION

FIGURE 8 NE AGENT LINK STATE

Postrequisite Update the USPP.

2.5 Updating USPP

Confidential and Proprietary Information of ZTE CORPORATION 13