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
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.
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.
Parameter Description
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
Result When the License is loaded, the window is as shown in the follow-
ing figure.
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
3. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Parameter Description
4. Click OK.
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.
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
Parameter Description
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
iv. Confirm that the latest version is what has been uploaded.
END OF STEPS
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Parameter Description
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.
Prerequisites You have logged into the EMS network management system.
The EMS network management system is correctly configured
and connected according to your networking plan.
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.
Steps 1. On the NetNumen(TM) M31 main window, select menu
Views > MML Terminal to open the MML Terminal window.
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 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.
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Internal Port Port No. of this DSA node for internal access,
default: 5057
Set it according to your networking plan.
Parameter Description
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.
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Big page Size Size of a big memory page, integer type, range:
(KB) 3264, unit: KB
Parameter Description
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Parameter Description
Prerequisites You have logged into the EMS network management system.
The EMS network management system is correctly configured
and connected according to your networking plan.
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.
Steps 1. On the NetNumen(TM) M31 main window, select menu
Views > MML Terminal to open the MML Terminal window.
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 navigation tree, select MML Com-
mands > UDS Dev Configuration > DSA Configuration
> DSA Configuration > Create DSA Configuration (ADD
DSA) to open the command interface shown in the following
figure.
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Parameter Description
Prerequisites You have logged into the EMS network management system.
The EMS network management system is correctly configured
and connected according to your networking plan.
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.
Steps 1. On the NetNumen(TM) M31 main window, select menu
Views > MML Terminal to open the MML Terminal window.
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 navigation tree, select MML Com-
mands > UDS Dev Configuration > DSA Configuration >
DSA Member Configuration > Create DSA Member Con-
figuration (ADD DSACLU) to open the command interface
shown in the following figure.
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Prerequisites You have logged into the EMS network management system.
The EMS network management system is correctly configured
and connected according to your networking plan.
The DSA member configuration is complete.
Context This topic describes the procedure to modify DSA attributes, for
example, data persistence policy and consistency policy.
Steps 1. On the NetNumen(TM) M31 main window, select menu
Views > MML Terminal to open the MML Terminal window.
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 navigation tree, select MML Com-
mands > UDS Dev Configuration > DSA Configuration >
DSA Option Configuration > Modify DSA Option Configu-
ration (SET DSAOPT) to open the command interface shown
in the following figure.
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Parameter Description
Prerequisites You have logged into the EMS network management system.
The EMS network management system is correctly configured
and connected according to your networking plan.
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.
Steps 1. On the NetNumen(TM) M31 main window, select menu
Views > MML Terminal to open the MML Terminal window.
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Prerequisites You have logged into the EMS network management system.
The EMS network management system is correctly configured
and connected according to your networking plan.
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.
Steps 1. On the NetNumen(TM) M31 main window, select menu
Views > MML Terminal to open the MML Terminal window.
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 > DSA Group Configuration > IDSA
Distributing Configuration > Create IDSA Distributing
Configuration (ADD IDSAMAP) to open the command
interface shown in the following figure.
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Parameter Description
Prerequisites You have logged into the EMS network management system.
The EMS network management system is correctly configured
and connected according to your networking plan.
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.
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
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
Prerequisites You have logged into the EMS network management system.
The EMS network management system is correctly configured
and connected according to your networking plan.
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 UDS parameters.
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Parameter Description
NO: Do not select another SSDS node for
asynchronous replication.
The Weight for Add The weight of Add request messages used
Request for load control, base unit: 1, range: 030,
default: 1
Parameter Description
Prerequisites You have logged into the EMS network management system.
The EMS network management system is correctly configured
and connected according to your networking plan.
The configuration of DSA groups is complete.
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.
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Prerequisites You have logged into the EMS network management system.
The EMS network management system is correctly configured
and connected according to your networking plan.
The configuration of DSA groups is complete.
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.
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Parameter Description
Parameter Description
Parameter Description
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
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.
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.
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Parameter Description
Parameter Description
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Module No. Module No. that the unit attributes to, range:
1127
Set it according to your networking plan.
Parameter Description
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Postrequisite Add units other than UMIC with the ADD UNIT command.
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
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.
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Postrequisite Add the connection between the service server node and the OMM
network management system.
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Parameter Description
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
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.
Parameter Description
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Parameter Description
Parameter Description
Postrequisite If the ATM over E1 access mode is used, perform HSL con-
nection configuration. (See topic .)
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Parameter Description
Parameter Description
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Parameter Description
8.1.3 Adding an AS
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Parameter Description
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Parameter Description
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Parameter Description
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.
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Parameter Description
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.
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Parameter Description
Parameter Description
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Parameter Description
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Parameter Description
Parameter Description
SCCP Encode Type Options: INT or USI. The default value (INT)
is recommended.
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.
The user has logged in to the OMM client and has the right to
perform data configuration.
The OMM system is correctly configured and connected accord-
ing to the network planning.
Offline data configuration and data synchronization is com-
plete.
The connection between the OMM network management sys-
tem and the OMP module is normal.
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.
Steps 1. On the Netnumen(TM) M30 main window, select menu
Views > MML Terminal to open the MML Terminal inter-
face.
2. Select the current working office node under root.
3. On the MML commands navigation tree, select MML Com-
mands > Device Configuration > IP Stack Configuration
> Interface Commands > Enter Interface Mode (INTER-
FACE) to open the interface shown in the following figure.
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Parameter Description
4. Set the parameter. For details about the parameter, see the
following table.
Parameter Description
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
IP IP address
Set according to your networking plan.
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.
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
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.
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
Steps 1. On the Netnumen(TM) M30 main window, select menu
Views > MML Terminal to open the MML Terminal inter-
face.
2. Select the current working office node under root.
3. On the MML commands navigation tree, select MML Com-
mands > Device Configuration > IP Stack Configuration
> IP Route Protocol > Static Route Configuration > Cre-
ate Static Route (ADD IP ROUTE) to open the interface
shown in the following figure.
4. Set the parameters. For details about the parameters, see the
following table.
Parameter Description
Parameter Description
Parameter Description
Parameter Description
Parameter Description
Parameter Description
Parameter Description
Parameter Description
Parameter Description
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.
Parameter Description
Parameter Description
Parameter Description
Parameter Description
Parameter Description
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.
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.
Steps 1. On the Netnumen(TM) M31 main window, select menu
Views > MML Terminal to open the MML Terminal window.
2. Select NetNumen > USPP > Service Configuration > Pub-
lic Service Configuration.
USPP here is a USPP node created by the CREATE USPP com-
mand. See ZXUN USPP Universal Subscriber Profile Platform
UDS Data Configuration for details.
3. On the MML Commands navigation tree, select Agent Re-
source Configuration > Agent Physical Number Segment
Configuration > Create Agent Physical Number Segment
Configuration to open the window as shown in the following
figure.
Parameter Description
Parameter Description
Parameter Description
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.
Parameter Description
Parameter Description
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
WCDMA
Wideband Code Division Multiple Access