You are on page 1of 396

ZXWN MSCS

MSC Server

Data Configuration Guide(MSCS)


Version 3.09.21

ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn

LEGAL INFORMATION
Copyright 2010 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of
this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATION
or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the
information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject
matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,
the user of this document shall not acquire any license to the subject matter herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History
Revision No.

Revision Date

Revision Reason

R1.0

Feb. 28, 2010

First edition

Serial Number: SJ-20100211152857-006

Contents

About This Manual............................................. I


Declaration of RoHS Compliance ....................... I
Data Configuration Overview.............................1
Overall Flow of MSCS Data Configuration ........................... 1
Basic Operations of the OMM System ................................ 3
Logging in the OMM Client ........................................... 3
Entering the MML Terminal........................................... 6
Operations on the MML Terminal ................................... 7
Synchronizing Data..................................................... 8

Data Configuration Principle............................ 11


Overview......................................................................11
Principle of Configuring the IP Address of the
Background ..........................................................12
IP Address Planning of Internal Network of NMS ............13
IP Address Planning of External Network of NMS ............14
IP Address Planning of External Network of Billing
System ............................................................16
IP Address Planning of Internal Network of IP
Management System..........................................16
Principle of Configuring the IP Address of the
Foreground ...........................................................18
Physical Configuration Rules............................................19
Overview..................................................................19
Board Configuration Rules...........................................20
Unit Numbering Rules ................................................21
Module Division Rules.................................................21
Module Numbering Rules ............................................22
SPC Configuration Rules .................................................22
IP Configuration Rules of Interface ...................................24
Service Area Configuration Planning .................................25
Adjacent Office ID Allocation Rule ....................................26

Confidential and Proprietary Information of ZTE CORPORATION

ZXWN MSCS Data Configuration Guide(MSCS)

Local Office Data Configuration ....................... 29


Overview......................................................................30
Local Exchange Configuration ..........................................31
Overview..................................................................31
Creating an Exchange ................................................32
Setting Province and City Information for an
Exchange .........................................................33
Physical Configuration ....................................................34
Overview..................................................................34
Creating a Rack.........................................................36
Creating a Shelf ........................................................37
Creating a UIM Unit ...................................................38
Creating a Module .....................................................40
Creating other Units...................................................42
Creating a CHUB Unit ........................................43
Creating a CLKG Unit.........................................45
Creating an SIPI Unit.........................................46
Creating a USI Unit ...........................................48
Creating an SPB Unit .........................................49
Creating MSCS Background Server...............................51
Capacity and Load-Sharing Configuration..........................52
Overivew..................................................................52
Setting the MSCS Office Capacity.................................52
Setting Service Data Area ...........................................55
Creating IMSI Load Sharing ........................................56
Creating TMSI Load Sharing........................................57
Version Loading.............................................................58
Overview..................................................................58
Creating Version File Directory ....................................60
Creating OMP Boot Files .............................................62
Configuring OMP Running Parameters via Serial
Port .................................................................64
Setting Global Data OMP Information ...........................75
Synchronizing All Tables .............................................76
Loading Version Files..................................................79
Creating MSCS Tones in Batches ......................................82
Office Information Configuration ......................................83
Overview..................................................................83
Creating a Local Signaling Point ...................................84
Creating the Local Exchange .......................................87

II

Confidential and Proprietary Information of ZTE CORPORATION

Creating Mobile Data of Local Office .............................90


Creating the Country Code..........................................95
Creating other MNC of Local Office ...............................96
VLR Configuration..........................................................97
Overview..................................................................97
Creating VLR System Parameters.................................98
Creating VLR System Capacity................................... 100
Creating VLR-supported Services ............................... 104
Creating Roaming Number Prefix ............................... 107
Creating MSRN Load Sharing..................................... 108
Virtual MSC Configuration ............................................. 110
Overview................................................................ 110
Creating Virtual MSC ................................................ 110
Creating Mapping Relationship between MRSN Prefix
and Virtual MSC .............................................. 112

Resource Configuration ................................. 115


Resource Planning ....................................................... 115
Configuring Resource Attributes..................................... 115

MSCS-MGW Interconnection Data


Configuration ................................................ 121
Overview.................................................................... 121
Interface Address Configuration..................................... 123
Overview................................................................ 123
Creating a Loopback Interface ................................... 123
Creating an SIPI Interface Address ............................ 124
BFD Configuration (optional) ......................................... 126
Overview................................................................ 126
Creating a BFD Authentication Entry .......................... 127
Creating a BFD Session ............................................ 128
Creating a Static Route ................................................ 129
Adjacent Office and Topology Configuration ..................... 131
Overview................................................................ 131
Creating an MGW Adjacent Office .............................. 132
Creating an MGW Voice CODEC Template .................... 136
Creating a Topology Node ......................................... 138
Creating an Inter-MGW Bearer Mode .......................... 142
SIGTRAN Configuration ................................................ 145
Overview................................................................ 145
SCTP Planning......................................................... 147
Creating an SCTP .................................................... 147

Confidential and Proprietary Information of ZTE CORPORATION

III

ZXWN MSCS Data Configuration Guide(MSCS)

Creating an ASP ...................................................... 151


Creating an AS ........................................................ 152
Creating an M3UA Static Route .................................. 155
Creating the SIO-Locating-AS ................................... 156
H.248 Configuration..................................................... 158
Overview................................................................ 158
Creating MGC Static Data ......................................... 160
Creating an MGW Static Data Template....................... 161
Creating MGW Static Data ........................................ 163
Creating a TID Analyzer ........................................... 164
Creating a TID Analyzer Entry ................................... 166

MSCS-Other-Exchange Interconnection Data


Configuration ................................................ 169
Networking Mode......................................................... 169
Office Interconnection in IP Domain ............................... 170
Overview................................................................ 170
Direct-Associated Office Configuration in IP
Domain .......................................................... 171
Overview ....................................................... 171
Configuring an Adjacent Office .......................... 172
Creating an MSCS Topology Node ...................... 177
M3UA-Transferred Office Configuration ....................... 180
M2UA-Transferred Office Configuration ....................... 182
Overview ....................................................... 182
Creating an M2UA IP Link................................. 184
TDM Office Interconnection ........................................... 186
Overview................................................................ 186
Creating a Signaling Link Set .................................... 188
Creating an SPB-Accessed Signaling Link .................... 190
Creating a Signaling Route........................................ 193
Creating a Signaling Office........................................ 195

MSCS-Radio-Office Interconnection Data


Configuration ................................................ 197
Interconnection with RNC Office .................................... 197
Overview................................................................ 197
Creating an RNC Adjacent Office................................ 200
Creating RNC Office Direction .................................... 204
Creating an RNC Topology Node ................................ 208

IV

Confidential and Proprietary Information of ZTE CORPORATION

Creating the Topology Relationship between RNC and


MGW ............................................................. 211
Interconnection with BSC Office..................................... 213
Overview................................................................ 213
Creating a BSC Adjacent Office.................................. 216
Creating BSC Office Direction .................................... 220
Creating a BSC Topology Node .................................. 222
Creating the Topology Relationship between BSC and
MGW ............................................................. 225

Basic Service Data Configuration................... 229


Location Update Data Configuration ............................... 229
Access Configuration ................................................ 229
Overview ....................................................... 229
Creating Emergency Call Center ........................ 230
Creating a Special Service Phone Group ............. 232
Creating the Special Service Phone Called
Number Analysis .................................. 235
Creating a LAI Controlled by the Local
Office ................................................. 237
Creating an Adjacent LAI ................................. 241
Creating a Global Cell ...................................... 245
Creating a Service Area ................................... 247
SCCP Data Configuration .......................................... 249
Overview ....................................................... 249
Creating a GT Translation Selector..................... 250
Creating GT Translation Data ............................ 254
Roaming Data Configuration...................................... 260
Overview ....................................................... 260
Creating IMSI Number Analysis......................... 261
Creating a Mobile Service Access Number and
MNC................................................... 263
Creating a Mobile Network ID and Area Code
Mapping ............................................. 265
Call Data Configuration................................................. 266
Number Analysis Configuration .................................. 266
Number Analysis ............................................. 266
Overview ....................................................... 270
Creating a Number Analyzer Entry..................... 271
Creating a DAS ............................................... 273

Confidential and Proprietary Information of ZTE CORPORATION

ZXWN MSCS Data Configuration Guide(MSCS)

Setting the Default DAS Template of the Local


Office ................................................. 275
Creating a DAS Template ................................. 279
Creating the Called Number Analysis ................. 282
Trunk Data Configuration .......................................... 307
Overview ....................................................... 307
Creating a DT Trunk Group ............................... 308
Creating an ATM Trunk Group ........................... 315
Configuring a RTP Trunk Group ......................... 321
Creating a PCM System.................................... 325
Creating a PCM System between MGWs ............. 328
Routing Data Configuration ....................................... 329
Overview ....................................................... 329
Creating an Outgoing Route.............................. 330
Creating an Outgoing Route Group .................... 331
Creating an Outgoing Route Chain..................... 333

Configuration Instance.................................. 337


Overview.................................................................... 337
Local Office Data Configuration...................................... 340
Local Exchange Configuration ................................... 340
Physical Configuration .............................................. 341
Capacity and Load Sharing Configuration .................... 342
Version Loading....................................................... 343
Office Data Configuration.......................................... 343
VLR Configuration.................................................... 344
Resource Attribute Configuration ................................... 345
Adjacent MGW Office Interconnection Data
Configuration ...................................................... 346
Adjacent HLR Office Interconnection Data
Configuration ...................................................... 349
Adjacent RNC Office Interconnection Data
Configuration ...................................................... 350
Location Update Data Configuration ............................... 352
Call Data Configuration................................................. 354
Data Synchronization ................................................... 355
MSCS-MGW Interconnection Debugging Procedure ........... 355
Checking the MGW Office Status................................ 356
Checking the Physical Connection .............................. 356
Debugging the SCTP ................................................ 357
Debugging the M3UA ............................................... 357

VI

Confidential and Proprietary Information of ZTE CORPORATION

Confirming the Working Status of the MGW ................. 358


H.248/SCTP Problem Location Method ........................ 358
M3UA Problem Location Method................................. 359
MSCS-HLR Interconnection Debugging Procedure............. 359
Checking the HLR Office Status ................................. 360
Checking the Physical Connection .............................. 360
Debugging the Narrow-Band Signaling Link ................. 361
Signaling Link Problem Location Method ..................... 365
MSCS-RNC Interconnection Debugging Procedure ............ 365
Checking the RNC Office Status ................................. 366
Basic Service Debugging Procedure................................ 366
Debugging the Location Update Service ...................... 367
Debugging the Local-Office Call ................................. 367

Figure............................................................ 369
Table ............................................................. 373
Index ............................................................ 379

Confidential and Proprietary Information of ZTE CORPORATION

VII

ZXWN MSCS Data Configuration Guide(MSCS)

This page is intentionally blank.

VIII

Confidential and Proprietary Information of ZTE CORPORATION

About This Manual


Purpose

At first, thank you for choosing ZXWN wireless core network system of ZTE Corporation!
ZXWN system is the 3G mobile communication system developed
based on the UMTS technology. ZXWN system boasts powerful
service processing capability in both CS domain and PS domain,
providing more abundant service contents. Comparing with the
GSM, ZXWN provides telecommunication services in wider range,
capable of transmitting sound, data, graphics and other multi-media services. In addition, ZXWN has higher speed and resource utilization rate. ZXWN wireless core network system supports both
2G and 3G subscriber access, and provides various services related with the 3G core network.
The ZXWN MSCS system is designed for the UMTS system at the
core network control level. It supports the GSM core network,
UMTS protocols in the R99/R4/R5 stage and relevant functions at
the same time, and provides the carriers with an overall solution
to the evolution from the GSM core network to the 3GPP R99 and
then to the 3GPP R5.
The ZXWN MSCS system completes the functions of the Mobile
Switching Center Server and the Visitor Location Register (VLR)
together, and provides the Service Switching Point (SSP) functions
of intelligent calls. The ZXWN MSCS system supports the MGCF
function, and the coexistence of the MGCF and GMSCS. It also can
smoothly upgrade to the MGCF.
This purpose of this manual is to let the carrier master the data
configuration method of MGCF.

Intended
Audience

This manual is intended for engineers and technicians who have


mastered the communication principle of the mobile network.

Prerequisite Skill
and Knowledge

To use this document effectively, users should have a general understanding of wireless telecommunications technology. Familiarity with the following is helpful:

What Is in This
Manual

MSCS system and its various components

This manual contains the following chapters:


Chapter

Summary

Chapter 1, Data Configuration


Overview

Describes the overall flow of the


MSCS data configuration and basic
operations of the background
network management (OMM)
system

Chapter 2, Data Configuration


Principle

Describes the data configuration


principle of the MSCS

Chapter 3, Local Office Data


Configuration

Describes the physical


configuration, capacity
configuration, version configuration,

Confidential and Proprietary Information of ZTE CORPORATION

ZXWN MSCS Data Configuration Guide(MSCS)

FCC Compliance
Statement

Chapter

Summary
and office information configuration
of MSCS

Chapter 4, Resource
Configuration

Describes MSCS resource planning


and attribute configuration

Chapter 5, MSCS-MGW
Interconnection Data
Configuration

Describes the signaling interworking


configuration between MSCS and
MGW

Chapter 6, MSCS-OtherExchange Interconnection Data


Configuration

Describes the signaling interworking


configuration between MSCS and
other exchanges at the network
side

Chapter 7, MSCS-Radio-Office
Interconnection Data
Configuration

Describes the signaling interworking


configuration between MSCS and
radio offices

Chapter 8, Basic Service Data


Configuration

Describes the basic data


configuration related with SIP
service and the call service

Chapter 9, Configuration
Instance

Sets MSCS trial office as an example


to describe the data configuration of
the local office and the peer office

This device complies with part 15 of the FCC Rules. Operation is


subject to the following two conditions.
1. This device may not cause harmful interference.
2. This device must accept any interference received, including
interference that may cause undesired operation.
Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate
the equipment.

Conventions

ZTE documents employ the following typographical conventions.


Typeface

Meaning

Italics

References to other Manuals and documents.

Quotes

Links on screens.

Bold

Menus, menu options, function names, input fields,


radio button names, check boxes, drop-down lists,
dialog box names, window names.

CAPS

Keys on the keyboard and buttons on screens and


company name.
Note: Provides additional information about a certain
topic.
Checkpoint: Indicates that a particular step needs to
be checked before proceeding further.
Tip: Indicates a suggestion or hint to make things
easier or more productive for the reader.

II

Confidential and Proprietary Information of ZTE CORPORATION

About This Manual

Mouse operation conventions are listed as follows:


Typeface

Meaning

Click

Refers to clicking the primary mouse button (usually the


left mouse button) once.

Doubleclick

Refers to quickly clicking the primary mouse button


(usually the left mouse button) twice.

Right-click

Refers to clicking the secondary mouse button (usually


the right mouse button) once.

Confidential and Proprietary Information of ZTE CORPORATION

III

ZXWN MSCS Data Configuration Guide(MSCS)

This page is intentionally blank.

IV

Confidential and Proprietary Information of ZTE CORPORATION

Declaration of RoHS
Compliance
To minimize the environmental impact and take more responsibility
to the earth we live, this document shall serve as formal declaration that ZXWN MSCS manufactured by ZTE CORPORATION are in
compliance with the Directive 2002/95/EC of the European Parliament - RoHS (Restriction of Hazardous Substances) with respect
to the following substances:

Lead (Pb)

Mercury (Hg)

Cadmium (Cd)

Hexavalent Chromium (Cr (VI))

PolyBrominated Biphenyls (PBBs)

PolyBrominated Diphenyl Ethers (PBDEs)

The ZXWN MSCS manufactured by ZTE CORPORATION meet


the requirements of EU 2002/95/EC; however, some assemblies
are customized to client specifications. Addition of specialized,
customer-specified materials or processes which do not meet the
requirements of EU 2002/95/EC may negate RoHS compliance of the
assembly. To guarantee compliance of the assembly, the need for
compliant product must be communicated to ZTE CORPORATION in
written form. This declaration is issued based on our current level
of knowledge. Since conditions of use are outside our control, ZTE
CORPORATION makes no warranties, express or implied, and assumes
no liability in connection with the use of this information.

Confidential and Proprietary Information of ZTE CORPORATION

ZXWN MSCS Data Configuration Guide(MSCS)

This page is intentionally blank.

II

Confidential and Proprietary Information of ZTE CORPORATION

Chapter

Data Configuration
Overview
Table of Contents
Overall Flow of MSCS Data Configuration ............................... 1
Basic Operations of the OMM System .................................... 3

Overall Flow of MSCS Data


Configuration
Prerequisites

Before the data configuration, it is required to confirm:

The hardware installation is completed and the cable connections are normal.
The rack , shelves , and boards are all installed. Cables are all
connected well, and the equipment can be normally powered
on.

The background network management system is installed.


The IP addresses of the background OMM server and client are
planned. The LAN is constructed, and the foreground OMP is
connected.
The OMM server software and client software are installed, ensuring that the OMM client can normally log in to the OMM
server. For the installation of the OMM server software and
client software, refer to ZXWN MSCS MSC Server Software Installation.

Configuration
Flow

The overall flow of the MSCS data configuration is shown in Figure


1.

Confidential and Proprietary Information of ZTE CORPORATION

ZXWN MSCS Data Configuration Guide(MSCS)

FIGURE 1 OVERALL FLOW OF THE MSCS DATA CONFIGURATION

Flow Description

The flow description of MSCS data configuration is shown in Table


1.
TABLE 1 MSCS DATA CONFIGURATION FLOW
Steps

Operations

Description

Data
configuration
planning

According to the networking structure,


determine the connection relationship
and bearer type between NEs, plan and
negotiate the configuration data, including
the local office data, interconnection data
with other NEs, location update data, and
call data

Local office data


configuration

Perform physical configuration, capacity


configuration, version configuration, and
office information configuration for the
local office

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Data Configuration Overview

Steps

Operations

Description

MSCS-MGW
interconnection
data
configuration

Configure the Mc-interface signaling


interconnection data

MSCS-other
exchange
interconnection
data
configuration

Configure the signaling interconnection


data with other offices at the network side
except the MGW, such as MSCS, HLR,
PSTN, and SGSN

MSCSradio office
interconnection
data
configuration

Configure the signaling interconnection


data with the RNC or BSC

Basic
service data
configuration

Configure the data related to the location


update and the basic call

Basic Operations of the


OMM System
To perform data configuration , it is required to be familiar with
the basic operations of the OMM system, including the following
operations:
No.

Operations

Logging in to the OMM Client

Entering the MML Terminal

Operations on the MML Terminal

Synchronizing Data

Logging in the OMM Client


Prerequisites

Context

Before the operation, it is required to confirm:

The server and the client of the network management are installed.

The communication between the server and the client is normal.

The purpose of logging in to the OMM client is to perform data configuration and daily maintenance by using the background OMM
software.

Confidential and Proprietary Information of ZTE CORPORATION

ZXWN MSCS Data Configuration Guide(MSCS)

Steps

1. On the OMM server, select Programs > ZXWN-CS (OMM) >


Start Server. the NetNumen (TM) Console window pops
up, displaying the start process of the OMM server, as shown
in Figure 2.
FIGURE 2 START PROCESS OF THE OMM SERVER

2. After the OMM server starts successfully, the prompt messages


are displayed in the Detailed Specification area, as shown in
Figure 3.
FIGURE 3 START INFORMATION OF THE OMM SERVER

3. On the server, click Start > Programs > ZXWN-CS (OMM)


> Start Client , and then the Login dialog box appears, as
shown in Figure 4.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Data Configuration Overview

FIGURE 4 LOGIN WINDOW

4. After entering the login information, click OK.


The parameter description is described in Table 1.
TABLE 1 LOGIN PARAMETER DESCRIPTION
Name

Meaning

Default

User name

Indicates the name of the


subscriber who logs in the
network server. The default
name is admin (system
administrator). If other
subscriber fails to log in the
network management server
for many times (exceeds the
maximum), the subscriber
will be locked automatically.
This subscriber only could be
unlocked by the administrator
or when the locking duration
expires. The login operation
that exceeds the maximum
should be reported to the
network management, so that
the network management could
know the maintenance status of
the equipment in order to avoid
the login of the unauthorized
subscriber and other operation
errors. The maximum login
limitation times in this system
is 3

admin

Password

It indicates the password that is


used to log in the OMM server.
The password of the new
installed network management
is null

Null

Confidential and Proprietary Information of ZTE CORPORATION

ZXWN MSCS Data Configuration Guide(MSCS)

Name

Meaning

Default

Server
address

Indicates the IP address of the


network management server. If
the server and the client are not
installed in the same computer,
it is required to enter the real
IP address of the server. or
else, you can enter the actual
IP address or adopt the default
IP address

127.0.0.1

END OF STEPS
Result

After the login is successful, the main window of the OMM system
pops up, as shown in Figure 5.
FIGURE 5 NETNUMN M30 MSCS/MGW OMM SYSTEM WINDOW

Entering the MML Terminal


Prerequisites

To enter the MML terminal, the following condition must be met:


The user has logged in to the OMM Server successfully.

Context

This topic describes how to enter the command terminal and configure the data.

Steps

1. On the OMM client, select Views > MML Terminalto enter the
MML Terminal window. The left shows the configuration tree,
and the right shows the attribute pane, as shown in Figure 6.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Data Configuration Overview

FIGURE 6 CONFIGURATION & MANAGEMENT MAIN WINDOW

END OF STEPS

Operations on the MML Terminal


Command
Terminal Window

The main operation of the data configuration is to type the command in the MML Terminal window, as shown in Figure 7.
FIGURE 7 MML TERMINAL WINDOW

Confidential and Proprietary Information of ZTE CORPORATION

ZXWN MSCS Data Configuration Guide(MSCS)

On the left pane of the MML Terminal window, the Root node
represents the OMM server node, which is the real root node. The
nodes under the Root node represent the specific NEs to be configured.
Command Typing

The command is typed in the input box at the lower right corner
of the MML Terminal window. For example, type in command
SET:NEID=11;, as shown in Figure 7.
In general, a command is associated with a network element (except the command used to configure an exchange). For example,
create a shelf for MSCS(11) (the ID can be queried with the command SHOW NE;). The following two methods can be used to
perform the conjunction:

Command
Execution

Type the command SET: NEID=11; and click F5 to execute the


command (the method is widely adopted in this document);

Select the network element of which the exchange ID is 11


from the left configuration system tree, such as MSCS 11.

This part describes the procedure of command line operation. Click


F5 to execute the command after it is typed.
After the command is executed, the Command Execute Result
pane shows the result or the information read by this command,
as shown in Figure 8.
FIGURE 8 COMMAND EXECUTION OPERATIONS

Synchronizing Data
Prerequisites

Before the operation, it is required to confirm:

The MML Terminal window is opened.

Some data configuration or all data configuration is completed.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Data Configuration Overview

Context

When configuring the data on the OMM, such as adding data, modifying data or deleting data, the data will be saved to the OMM
Server in the form of data list after executing the F5 button. At
this time, the foreground data are not modified. The data synchronization is to synchronize the data on the OMM Server to the
foreground
The data synchronization operation could be done after finishing
each step or after finishing configuring all the data.

Steps

1. If the exchange is not specified, it is required to use the SET


command on the MML Terminal window or select the network
element from the system tree to specify the exchange to be
configured.
2. Data transfer includes transferring data by using the Admin
user, and transferring data by using the current login user.

Synchronize Admin data. The command is SYNA.

Tip:
This command is used by Admin users to synchronize all table data, no matter whether the tables are locked by other
users.
Table 2 describes the parameters in this command.
TABLE 2 PARAMETERS IN THE SYNA COMMANDS
Parameter
Name

Parameter
Description

Instructions

USERNAME

User name

It consists of 0~50
characters and the
default value is admin.
It includes

STYPE

Sync type

CHG (Single User


Changed Tables)

ALL (All Tables)

ALLCHG (All
Changed Tables)

Module list

It indicates the module


ID in decimal. If there
are many module IDs,
use the symbol & to
connect them.

TIMEOUT

Response timeout
(100ms)

It is an optional
parameter and the
default value is 600.
Adjust the response
timeout according to
the actual requirement.

SAVE

Save when
completed

It is an optional
parameter and the
default value is YES

MODULES

Confidential and Proprietary Information of ZTE CORPORATION

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instructions

TOSLAVE

Sync to slave when


completed

It is an optional
parameter and the
default value is YES

Synchronize the data of currently login user. The command


is SYN.

Tip:
This command is used to synchronize the table data configured by a login user. The table data not configured by
the login user can not be synchronized to the foreground.
Table 3 describes the parameters in this command.
TABLE 3 PARAMETERS IN THE SYN COMMANDS
Parameter
Name

Parameter Description

Instructions

Module List

It indicates the
module ID in
decimal. If there
are many module
IDs, use the symbol
& to connect them.

TIMEOUT

Response timeout
(100ms)

It is an optional
parameter and the
default value is
600. Adjust the
response timeout
according to the
actual requirement.

SAVE

Save when completed

It is an optional
parameter and the
default value is YES

TOSLAVE

Sync to slave when


completed

It is an optional
parameter and the
default value is YES

MODULE

Example: To synchronize all the tables with admin user, the


command is as follows:
SYNA:STYPE=ALL,TIMEOUT=600,SAVE=YES,TOSLAV
E=YES;

Example: To synchronize the data of the current user, the


command is as follows:
SYN:TIMEOUT=600,SAVE=YES,TOSLAVE=YES;

END OF STEPS

10

Confidential and Proprietary Information of ZTE CORPORATION

Chapter

Data Configuration
Principle
Table of Contents
Overview..........................................................................11
Principle of Configuring the IP Address of the Background .........12
Principle of Configuring the IP Address of the Foreground .........18
Physical Configuration Rules................................................19
SPC Configuration Rules .....................................................22
IP Configuration Rules of Interface.......................................24
Service Area Configuration Planning .....................................25
Adjacent Office ID Allocation Rule ........................................26

Overview
Introduction

To correctly and quickly complete data configuration, engineers


need to complete data collection and plan before data configuration. The data to be collected include:

Networking Mode

Equipment configuration, including shelf and board configuration, and links provided by boards

External interface and interconnection negotiation data, including signaling links, IP addresses and IP port No.

Service data

This chapter briefs the data configuration principle of the MSCS.

Confidential and Proprietary Information of ZTE CORPORATION

11

ZXWN MSCS Data Configuration Guide(MSCS)

Principle of Configuring
the IP Address of the
Background
IP Address
Planning of the
Background

Related Concepts

The whole background LAN divides into four parts:


No.

Category

Description

Internal network VLAN of


the Network Management
System (NMS)

Used for the communication


between the background
server and the foreground

External network VLAN of


the NMS

Used for the communication


between the background
server and the client, between
the OMM/EMS server and
other background servers, and
between the OMM/EMS server
and the upper-level network
management system

External network VLAN of


the billing system

Used for the communication


among the billing server, HLR
interface machine, and the
upper-level BOSS system

Internal network VLAN of


the IP management system

Used for the communication


between the OMM/EMS server
and the IP/IT equipment in
the LAN

1. Office number
On the OMM server, it is the number of the newly added exchange.

The office number range is city/region. It cannot be repeated in the same range, and can be repeated in different
ranges.
The office number should be allocated in the ascending order in each range.

2. Base office number


During background networking, since one OMM server may
manage multiple NEs, the concept of base office number is
added.

12

When the OMM server manages one MSCS, the base office
number is the MSCS office number.
When OMM server manages multiple MSCSs, the base office number adopts smallest MSCS office number.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 2 Data Configuration Principle

IP Address Planning of Internal


Network of NMS
The IP address planning principle of the internal network of the
NMS is as follows:
Adopt the mode of class-C private address plus 24-bit mask, and
fix the IP address section to 192.168.Base office number.Node
number/24.
Table 4 shows the office number allocation principle.
TABLE 4 OFFICE NUMBER ALLOCATION PRINCIPLE
NE Type

Office Number Range

HLR

1~10

MSCS

11~30

MGW

31~50

SGSN

51~60

GGSN

61~70

CG

71~80

MG

81~90

If one OMM server manages multiple NEs, (i.e. one internal network of the NMS manages multiple offices), the base office number
in the IP address adopts the smallest office number. Table 5 shows
the IP address allocation principle of the internal network of the
NMS.
TABLE 5 IP ADDRESS ALLOCATION PRINCIPLE OF THE INTERNAL
NETWORK OF THE NMS

Module

Apllied
Range

IP Address/Mask

Remark

1. The OMP is forbidden to

OMP

USI

CS/PS/HLR

CS/PS/HLR

192.168.B
ase office
number.L
ocal office
number/24

192.168.B
ase office
number.100
/24

be configured with the


SMP attribute

2. The local office number


refers to the office number of the NE where the
OMP belongs to

1. If one internal network of


the NMS only manages
one office, the node number of the USI is fixed to
100.

Confidential and Proprietary Information of ZTE CORPORATION

13

ZXWN MSCS Data Configuration Guide(MSCS)

Module

Apllied
Range

IP Address/Mask

Remark

2. If one internal network of


the NMS manages multiple offices, there are multiple USI modules, and
the node number of the
USI begins with 100

OMM
Server

192.168.B
ase office
number.129
/24

192.168.B
ase office
number.134
/24

Used for the local


maintenance terminal

CS/PS/HLR

192.168.B
ase office
number.130
/24
CU/CG
Server

CS/PS

192.168.B
ase office
number.131
/24

192.168.Base office
number.130/24 is a floating
IP

192.168.B
ase office
number.132
/24
DNS
Server

NTP
Server

PS

192.168.B
ase office
number.160
/24

If the dual-server system is


adopted, the node number is
160~162

PS

192.168.B
ase office
number.170
/24

If the dual-server system is


adopted, the node number is
170~172

IP Address Planning of External


Network of NMS
All clients and unified alarm boxes in the same office are all connected to the external network VLAN. The external network of the
NMS is the exclusive channel to communicate with the upper-level
NMS.
The IP address planning principle of the external network of the
NMS is as follows:
Adopt the mode of class-B private address plus 16-bit mask, and
fix the IP address section to 172.16. Base office number.Node
number/16. The base office number of the external network of
the NMS keeps consistent with that of the internal network of the
NMS.

14

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 2 Data Configuration Principle

Table 6 shows the IP address allocation principle of the external


network of the NMS.
TABLE 6 IP ADDRESS ALLOCATION PRINCIPLE OF THE EXTERNAL
NETWORK OF THE NMS

Module

Apllied Range

IP Address/Mask

Remark

OMM Server

CS/PS/HLR

172.16.Base
office
number.129/16

172.16.Base
office
number.130/16
CG/CU Server

CS/PS

172.16.Base
office
number.131/16

172.16.Base
office
number.132/16
Unified alarm
box

CS/PS/HLR

172.16.Base
office
number.250/16

1. The

node
numbers of
the
local
clients are
240~249

Local clients

CS/PS/HLR

172.16.Base
office
number.24*/16

2. The

local
clients include OMM
clients, EMS
clients, billing clients,
and
HLR
agents

1. The

Remote clients

CS/PS/HLR

172.16.Base
office
number.24*/16

node
numbers of
the remote
clients are
240~249

2. The remote
clients include EMS
clients, and
OMM clients

Confidential and Proprietary Information of ZTE CORPORATION

15

ZXWN MSCS Data Configuration Guide(MSCS)

IP Address Planning of External


Network of Billing System
The external network of the billing system is used to communicate
with the upper-level BOSS system, implementing CDR delivery and
BOSS agent interface data delivery.
The IP address planning principle of the external network of the
billing system is as follows:
Adopt the mode of class-B private address plus 16-bit mask, and
fix the IP address section to 172.17.Base office number.Node number/16. The base office number of the external network of the
billing system keeps consistent with that of the internal network
of the NMS.
Table 7 shows the IP address allocation principle of the external
network of the billing system.
TABLE 7 IP ADDRESS ALLOCATION PRINCIPLE OF THE EXTERNAL
NETWORK OF THE NMS
Module

Apllied Range

IP Address/Mask
172.17.Base office
number.130/16

CG/CU Server

CS/PS

172.17.Base office
number.131/16
172.17.Base office
number.132/16

HLR interface machine

HLR

172.17.Base office
number.150/16

IP Address Planning of Internal


Network of IP Management System
The internal network VLAN of the IP management system is used
to monitor and manage all the IP/IT equipment in the same office.
The basic principle of monitoring the IP/IT equipment is as follows:
The IT OMM (generally installed on the OMM Server or EMS Server
of the local office) collects the management information (alarm
and performance data) of the IP/IT equipment through the internal
network of the IP management system (IT-SW), and sends it to
the EMS through the external network of the NMS.
The IP address planning principle of the internal network of the IP
management system is as follows:
Adopt the mode of class-B private address plus 16-bit mask, and
fix the IP address section to 172.18.Base office number.Node number/16. The base office number of the internal network of the IP/IT
equipment management system keeps consistent with that of the
internal network of the NMS.

16

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 2 Data Configuration Principle

Table 8 shows the IP address allocation principle of the internal


network of the IP management system.
TABLE 8 IP ADDRESS ALLOCATION PRINCIPLE OF THE INTERNAL
NETWORK OF THE IP MANAGEMENT SYSTEM

Apllied Range

IP Address/Mask

Remark

CS/PS/HLR

172.18.Base
office
number.129/16

This OMM
Server
concurrently
acts as the IT
OMM

172.18.Base
office
number.1*/16

The Ethernet
interface of
the switch
is directly
connected with
the IT-SW

172.18.Base
office
number.3*/16

The
management
port of the
router is directly
connected with
the IT-SW

CS/PS/HLR

172.18.Base
office
number.4*/16

The
management
port of
the firewall
is directly
connected with
the IT-SW

CS/PS

Using the
internal
network IP of
the NMS

Using the
communication
channel with
the OMM Server

HLR

Using the
internal
network IP of
the NMS

Using the
communication
channel with
the OMM Server

HLR DBIO
Server

HLR

Using the
internal
network IP of
the NMS

Using the
communication
channel with
the OMM Server

HLR interface
machine

HLR

Using the
internal
network IP of
the NMS

Using the
communication
channel with
the OMM Server

Module

OMM Server

Ethernet switch

Router

CS/PS/HLR

CS/PS/HLR

Firewall

CG/CU server

HLR DBE Server

Confidential and Proprietary Information of ZTE CORPORATION

17

ZXWN MSCS Data Configuration Guide(MSCS)

Module

DNS server

NTP Server

Apllied Range

IP Address/Mask

Remark

PS

172.18.Base
office
number.160/16

If there is
an idle FE
interfaces,
it is directly
connected with
the IT-SW

172.18.Base
office
number.170/24

If there is
an idle FE
interfaces,
it is directly
connected with
the IT-SW;
otherwise, the
communication
channel with
the OMM Server
is used

PS

Principle of Configuring
the IP Address of the
Foreground
The boards on the foreground, and the maintenance servers and
maintenance terminals on the background identify and communicate with each other through IP addresses.
Foreground addresses are the IP addresses of boards, which have
three network sections: 128, 129, and 130.
1. Network section 128
Network section 128 is a debugging network section. The CPU
of each board has one IP address in network section 128.The
communication between foreground boards uses this address.
The system calculates this address according to the DIP values
of the rack and shelf, and the slot No. The calculation formula is
as follows. However, the address of the OMP module in network
section 128 is usually 128.0.31.1 or 128.0.31.9.
Suppose the IP address in network section 128 is 128.A.B.C:
A=Office ID16+Rack No.
B=Shelf No.32+Slot No.
C=CPU No.8+1

18

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 2 Data Configuration Principle

Note:
The office ID and shelf No. in the formula are the same with
that in DIPs. However, the so-called office ID refers to the
office ID in DIPs plus 1, and the so-called shelf No. refers to
the shelf No. in DIPs plus 1.
2. Network section 130
In general, the system automatically allocates the IP addresses
in network section 130 to each SMP for communication between SMPs.
3. Network section 129
Network section 129 is usually used for billing networks.
Among the foreground boards, only USI boards have IP
addresses in network section 129, which are usually used as
gateways to implement the communication between the MP
and the billing server.

Physical Configuration Rules


Overview
Introduction

Contents

Physical configuration rules describe the type division of racks,


shelves, boards and modules, board position planning, and numbering methods.
This section contains the following topics.
No.

Rules

Description

Board Configuration
Rules

Including single-rack shelf


configuration, slot restriction
and board position planning of each
board

Unit numbering rules

Introduces the method of numbering


the foreground boards

Module division rules

Introduces the module types and


division principles

Module numbering
rules

Introduces the method of numbering


all MP modules

Confidential and Proprietary Information of ZTE CORPORATION

19

ZXWN MSCS Data Configuration Guide(MSCS)

Board Configuration Rules


Shelf Condition

ZXWN MSCS only uses BCTC shelves. A rack can be inserted with
at most four shelves.
A single BCTC shelf with full configuration is shown in Figure 9.
FIGURE 9 SINGLE BCTC SHELF WITH FULL CONFIGURATION

Configuration
Description

A single rack is numbered 1, and multiple shelves are numbered


from 1.

Shelves are numbered, going top-to-bottom from 1 to 4.

Slots are numbered, going left-to-right from 1 to 17.

BCTC shelf can be configured with the following boards.

20

OMP/RPU board is inserted into slots 11 and 12 on shelf 2 of


rack 1.

UIMC board is inserted into slots 9 and 10.

SMP board is inserted into all slots except for slots 9 and 10.
It is required that signaling MP and service MP boards must be
inserted into each BCTC shelf evenly.

CLKG board is inserted into slots 13 and 14 on shelf 2 of rack


1.

CHUB board is inserted into slots 15 and 16 on shelf 2 of rack


1.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 2 Data Configuration Principle

Board position
planning

USI board is inserted into all slots except for slots 9 and 10. In
general, slots 1 and 2 are selected.

SIPI board is inserted into all slots except for slots 9 and 10.
Slots 1 and 2 are selected preferentially, and then slots 3 and
4 are selected. When SIPI load-sharing networking is adopted,
SIPI boards should be inserted into different BCTC shelves.

SPB board is inserted into all slots except for slots 9 and 10.

The basic principles for planning board positions are as follows.

The slot where the board is inserted is suitable for this board.

The plan conforms to the engineering design and specifications.


Board insertion should be tidy as far as possible to make sure
cable routing reasonable and pleasant.

Slot planning conforms to the load-sharing requirements.

For the purpose of load-sharing, signaling modules and service


modules should be evenly configured in different BCTC shelves.

Unit Numbering Rules


To number the unit is to number the foreground board on the background network management. Numbering rules are as follows.
Unit number=ABCD

AB=Slot number

C=Shelf number

D=Rack number

Slot number ranges from 1 to 17, shelf number ranges from 1 to 4,


and rack number ranges from 1 to 9. The rack number is usually
not greater than 9.
For example, the unit number of the UIMC board located in slot 9,
shelf 2 of rack 1 is 921.

Module Division Rules


Currently, the SMP boards used in MSCS and MGW can divide into
signaling module (SMP), service module (CMP) or signaling and
service mixed module according to different module attributes that
are configured. SMP signaling module and CPM service module are
configured separately during the current commissioning. Therefore, the number of SMP modules and CMP modules need to be
configured.
Basic principles of module division are as follows.

Signaling modules are configured separately from service modules. Interception modules (MSCS) are configured independently. They are distinguished by different module attributes.

Confidential and Proprietary Information of ZTE CORPORATION

21

ZXWN MSCS Data Configuration Guide(MSCS)

Signaling modules and service modules should be configured


in different control shelves for load sharing.

The scale of signaling modules and service modules should be


configured properly. Otherwise, later adjustment to the scale
is relatively complex. In addition, MP must be restarted.

64k and 2M signaling link management modules must be


shared by all the signaling modules for load sharing, with the
consideration that one 2M signaling link can be calculated as
16 64K signaling links. The signaling links of the same office
must be shared by the signaling modules in different slots.

SCTP management modules should be evenly shared by all


the signaling modules. The SCTPs under the same AS must
be shared by the signaling modules in the different slots. Note
that the SCTP load under each AS is different from each other.
In general, the load of associations bearing BSSAP/RANAP>The
load of associations bearing H248>The load of associations
bearing TSUP/TUP.

Module Numbering Rules


All the MP modules in the MSCS are universally numbered from 1
to 128.
Module numbering rules are as follows.

OMP: Its module number is 1.

RPU: Its module number is 2.

SMP/CMP: Its module number is numbered from 3 to 127, allocated to each module in turn.

On the OMP board of the MSCS, module 1 is the OMP module,


and module 2 is the RPU module by default. According to module
attributes, the SMP board can be configured to signaling module
(SMP), service module (CMP), or signaling and service mixed module. In the MSCS, all units home to module 1.

SPC Configuration Rules


SPC Types

Signaling points divide into three basic types according to the type
of the signaling-interconnected office.
1. Signaling point interconnecting to other exchange
This signaling point is used to interconnect with other exchanges in the signaling network, including HSTP/LSTP, HLR,
TMSC, MSC, and other exchanges. 24-bit signaling points are
used in China. 14-bit signaling points are possibly used for
commissioning in other countries.
The basic principles for applying for a Signaling Point Code
(SPC) are as follows.

22

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 2 Data Configuration Principle

The MSCS applies for at least one SPC. If multiple signaling


points are needed, apply for SPCs according to the actual
requirements.
During the dual-homing networking, the active MSCS and
the standby apply for one SPC, the mutually backed-up
MSCSs apply for two SPCs, and N+1 MSCSs apply for at
least N SPCs (it is recommended to apply for N+1 SPCs).

2. Signaling point interconnecting to an radio office


This signaling point is used to interconnect with a radio office,
including BSC and RNC. The basis principles are as follows.

When MGW interconnects with RNC in an ATM bearer mode,


RNC and MGW are directly associated. RNC sends the
RANAP signaling to MSCS through MGW. In this case, MSCS
can use a signaling point being different from that of MGW.
When MGW interconnects with RNC in an IP bearer mode,
RNC and MSCS are directly associated. In this case, MSCS
needs to apply for a signaling point, but MGW does not.
When MGW interconnects with BSC, BSC and MGW are directly associated in most cases. BSC sends the BSSAP signaling to MSCS through MGW. In this case, MSCS and MGW
use a same signaling point, because BSC generally does not
support that MSCS uses the SPC being different from that
of MGW. In China, BSC basically uses 14-bit SPC.

3. Signaling point interconnecting with the Mc interface


The signaling point that is used for MSCS to interconnect with
MGW on the Mc interface only bears the H248 signaling. Since
Mc interface is an internal interface for MSCS to directly connect to MGW, it is recommended to use the customized signaling point.
If it is not available, MGW may use the signaling point of type
1 or type 2 that are mentioned above. But each MGW must
use a different signaling point from each other. And it is recommended that active MSCS uses a signaling point being different from that used by standby MSCS.
Signaling Point
Configuration

The specific configuration of signaling points is decided by the applied signaling points. When performing signaling point configuration on the background OMM system of the MSCS, divide them
according to interconnection modes. The signaling points include
the following types:
1. Signaling points interconnected with the Mc interface, used for
the interconnection between the MSCS and the MGW, and only
bearing H.248 signaling.
2. Signaling points used for the interconnection between the
MSCS and the associated adjacent offices.
3. Signaling points used for the interconnection between the
MSCS and signaling offices (except the BSC and RNC) through
the MGW.
4. Signaling points used for the interconnection between the
MSCS and radio offices (BSC and RNC) through the MGW, or
between the MSCS and the associated radio offices.

Confidential and Proprietary Information of ZTE CORPORATION

23

ZXWN MSCS Data Configuration Guide(MSCS)

IP Configuration Rules of
Interface
Overview

MSCS signaling service IP addresses include the IP address of Mc


interface and that of Nc interface. In addition, adding IP address
of Iu-CS interface is required when this interface adopts the IP
networking mode. The IP address division of Iu-CS interface is
similar to that of Mc interface. It may uses an independent IP
address, or share the IP address with Mc interface.
On the MSCS, the Mc interface and Nc interface can be configured
with two types of IP addresses.

Service Address

Interface Address

The service address is the SCTP processing address, which is configured on the loopback interface of the RPU module. This address
corresponds to the IP address of local end specified in the SCTP
configuration.

At least one IP address is required.

To support SCTP multi-homing configuration, a service address


should be configured with at least two IP addresses.

If the Mc interface or Nc interface does not share service address with other interface, two times of IP addresses should be
configured.

The interface address is configured on the SIPI real interface for


interconnecting with the CE equipment. MNIC is the backplane of
SIPI board, which only externally provides one FE interface. There
are two methods to interconnect with CE.

Active/standby mode
Two SIPI boards are configured, working in active/standby
mode. Virtual Router Redundancy Protocol (VRRP) is enabled
on the CE side. Every two SIPI boards are configured with
one IP address, and the interface of the corresponded CE is
configured with three IP addresses, which are the interface
addresses of router 1 and router 2, and the VRRP address of
router.

Load sharing mode


Two SIPI board are configured, working in No backup mode.
The Bidirectional Forwarding Detection (BFD) protocol is enabled between SIPI and CE. These two SIPI boards are configured with two IP addresses that are in different network sections. And the interface at the corresponded CE side is configured with two IP addresses, too.

Instance

24

Take the IP addresses of Mc interface listed in Table 9 for example,


Figure 10 shows the diagram of signaling service IP configuration.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 2 Data Configuration Principle

FIGURE 10 SIGNALING SERVICE IP CONFIGURATION

TABLE 9 AN INSTANCE OF MC INTERFACE IP ADDRESSES


IP address

Subnet mask

10.0.74.5

255.255.255.255

10.0.74.10

255.255.255.255

SIPI1 (real address)

10.0.74.4

255.255.255.248

SIPI2 (real address)

10.0.74.9

255.255.255.248

CE1 (next hop address)

10.0.74.1

255.255.255.248

CE2 (next hop address)

10.0.74.2

255.255.255.248

Opposite-end address 1

11.11.11.1

255.255.255.0

Opposite-end address 2

11.11.11.2

255.255.255.0

Configuration Position
RPU (loopback interface
address)

Service Area Configuration


Planning
Service area planning means dividing one MSCS into multiple service areas, that is, multiple virtual MSCSs. Therefore, it is required
to configure the data related with virtual MSCSs, and to apply for
multiple MSC/VLR GT numbers and roaming number sections.
In the following two cases, it is required to perform service area
planning.
1. The region-system networking is adopted.
When the region-system networking is adopted, one MSCS
manages multiple service areas (area codes for subscriber access in different service areas are different). Different service
areas usually use different MSC/VLR GT numbers and roaming
number sections.

Confidential and Proprietary Information of ZTE CORPORATION

25

ZXWN MSCS Data Configuration Guide(MSCS)

2. The region-system networking is not adopted, but different


MGWs under the same MSCS need to be configured with different roaming number sections.
When one MSCS manages multiple service areas, although all
the area codes for subscriber access are the same, it is required to allocate different roaming number sections to different MGWs to reduce alternate traffic between MGWs.
Therefore, each service area needs to be set with the corresponding virtual MSC index, i.e., area ID. The area ID ranges
from 1 to 65535 (0 for public area), in the format of Area code
+ Number (the area code is the corresponding area code of
the virtual MSC, and the number is an integer ranging from 1
to 9).

Adjacent Office ID Allocation


Rule
The adjacent office ID is the basis of the office data, which is referred to during signaling configuration and traffic configuration.
Therefore, it is required to make an overall plan about adjacent
offices. Different types of adjacent offices need to be configured
with fixed adjacent office IDs.
For example, one MSCS is divided into 3 service areas, including
the public area, area 1, and area 2, as shown in Figure 11.
FIGURE 11 ADJACENT OFFICE ID ALLOCATION

In the public area, the adjacent offices of the MSCS include the
following types:
1. Adjacent offices (except MGW) associated with the MSCS.
2. Adjacent offices quasi-associated with the MSCS, whose signaling routes pass the above associated adjacent offices.
3. Adjacent offices connected with the MSCS through multiple
MGWs. This type of adjacent offices are relatively special, and
they are shared by all areas, so they are put in the public area.

26

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 2 Data Configuration Principle

In area 1 and area 2, the adjacent offices of the MSCS include the
following types:
1. Adjacent MGW offices associated with the MSCS in the local
area.
2. Adjacent offices quasi-associated with the MSCS, and those
connected with the MSCS through the above MGWs. In
general, the M3UA transfer/agent mode is adopted. In some
cases, the M2UA mode is adopted.

Confidential and Proprietary Information of ZTE CORPORATION

27

ZXWN MSCS Data Configuration Guide(MSCS)

This page is intentionally blank.

28

Confidential and Proprietary Information of ZTE CORPORATION

Chapter

Local Office Data


Configuration
Table of Contents
Overview..........................................................................30
Local Exchange Configuration..............................................31
Physical Configuration ........................................................34
Capacity and Load-Sharing Configuration..............................52
Version Loading.................................................................58
Creating MSCS Tones in Batches..........................................82
Office Information Configuration ..........................................83
VLR Configuration..............................................................97
Virtual MSC Configuration ................................................. 110

Confidential and Proprietary Information of ZTE CORPORATION

29

ZXWN MSCS Data Configuration Guide(MSCS)

Overview
Configuration
Flow

Figure 12 shows the flow of the local office data configuration.


FIGURE 12 THE HOME OFFICE DATA CONFIGURATION FLOW

Flow Description

30

The flow description of the local data configuration is shown in


Table 2.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

TABLE 2 LOCAL DATA CONFIGURATION FLOW


Steps

Operations

Procedures

Local Office
Configuration

Creates MSCS exchange, and


configures the province and city
information of this office

Physical
Configuration

Creates foreground-corresponded
racks, shelves, units, modules and
their attributes on the background
OMM system

Capacity and
Load-sharing
Configuration

Plans the MP table capacity and


IMSI/TMSI load sharing

Version Loading

Loads the version files to the


foreground, which are required
for normal running of different
foreground boards

Creating MSCS Tones


in Batches

Add a batch MSCS tones

Office Information
Configuration

Configures the local office signaling


point, exchange type, country code,
mobile country code, and mobile
network code.

VLR Configuration

Configures VLR capacity, VLR


parameters, and roaming number
prefix.

Virtual MSC
Configuration
(optional)

Virtual MSC is required when service


areas are divided.

Local Exchange
Configuration
Overview
Introduction

Contents

Configuring the local exchange is to define the information of the


local exchange on the OMM system such as its type. It is the first
data configuration in deployment.
The exchange configuration contains the following steps.

Confidential and Proprietary Information of ZTE CORPORATION

31

ZXWN MSCS Data Configuration Guide(MSCS)

Steps

Operations

Instructions

Commands

Creating an
exchange

Create the NE
corresponded by
the exchange on the
background OMM
system

ADD NE

Setting province and


city information for
an exchange

Configure the
provincial and
city codes of the
exchange, thus
to display the
area information
in the Element
Management
System (EMS)

SET PCINFO

Creating an Exchange
Prerequisites

Before the operation, it is required to confirm:


The MML Terminal window is opened.

Context
Steps

Perform this procedure to create the NE corresponded by the exchange on the background OMM system.
1. Create an MSCS exchange with the ADD NE command.
Table 10 describes the main parameters in the ADD NE command.
TABLE 10 PARAMETERS IN THE ADD NE COMMAND
Parameter
Name

32

Parameter Description

Instruction

ID

The unique ID of an
exchange

It is a mandatory
parameter. It ranges
from 11 to 30. It cannot
be modified once it is
created.

TYPE

Type of the exchange to


be created

It is a mandatory
parameter. Select
MSCS.

MESUBTYPE

NE sub-type

It is an optional
parameter. Select
NONE for an end office,
and TMSC1 or TMSC2
for a tandem office.

NAME

Exchange name
customized by user

It is an optional
parameter. With a
length ranging from 0 to
50 characters.

VENDOR

Equipment manufacturer

It is an optional
parameter. Type ZTE,
by default.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

Parameter
Name

Parameter Description

Instruction

STATE

State defined by the


user

It is an optional
parameter. Select 0,
by default.

Location where the


equipment is located

It is an optional
parameter. Type the
location information
of the equipment. It
is recommended to
describe it with letters
or digits.

LOC

Example: Create an MSCS end office with the following requirements.

Office ID: 11

Type: MSCS

Alias: MSCS11

Other parameter: default.

The specific command is as follows.


ADD
NE:ID=11,TYPE=MSCS,MESUBTYPE=NONE,NAME
="MSCS11",VENDOR="ZTE",STATE=0;
END OF STEPS
Result

After the command is executed successfully, the MSCS node is


added under the root node in the OMM client interface. Meanwhile,
the rack is generated, with the rack No. as 1 and the alias as rack
1.

Setting Province and City Information


for an Exchange
Prerequisites

Before the operation, it is required to confirm:

The MSCS exchange is added.

The MML Terminal window is opened.

Context

Perform this procedure to set the provincial and city codes of the
exchange, thus to display the area information in the Element Management System (EMS).

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Set the province and city information of the exchange. The
command is SET PCINFO.

Confidential and Proprietary Information of ZTE CORPORATION

33

ZXWN MSCS Data Configuration Guide(MSCS)

Table 11 describes the main parameters in the SET PCINFO


command.
TABLE 11 PARAMETERS IN THE SET PCINFO COMMAND
Parameter
Name

Parameter
Description

PROVINCE

Provincial code

CITY

Municipal code

Instructions
It is a mandatory
parameter. For
displaying area
information of the
exchange in the EMS.

Example: The exchange is located in Nanjing city of Jiangsu


province. The specific command is as follows.
SET PCINFO:PROVINCE="320000",CITY="320101";
END OF STEPS

Physical Configuration
Overview
Introduction
Flow diagram

34

This section describes the physical configuration .


Figure 13 shows the physical configuration flow.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

FIGURE 13 PHYSICAL CONFIGURATION FLOW

Flow description

The physical configuration contains the following steps.


Steps

Operations

Instructions

Command

Creating a rack

Create a logic rack


on the background
OMM system

ADD RACK

Creating a shelf

Create a logic shelf


on the background
OMM system

ADD SHELF

Creating a UIM unit

Create the UIM


board

ADD UNIT

Confidential and Proprietary Information of ZTE CORPORATION

35

ZXWN MSCS Data Configuration Guide(MSCS)

Steps

Operations

Instructions

Command

Creating a module

When MSCS has


several modules,
it is required to
create SMP board
for BCTC shelf

ADD MODULE

Creating other
units

Create other logic


boards in the BCTC
shelf of MSCS
exchange, except
for UIM unit

ADD UNIT

Creating MSCS
background server

Connect the SMP


with the billing
server

ADD SVRINF

Creating a Rack
Prerequisites

Before the operation, it is required to confirm:

The exchange has been added.

The MML Terminal window is opened.

Context

Perform this procedure to create a logic rack on the background


OMM system. It corresponds to the rack on the foreground. Since
the system automatically creates rack 1 during the exchange creation, you need not to create it again. But you need to create
other racks manually here.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create a rack. The command is ADD RACK.
Table 12 describes the parameters in the ADD RACK command.
TABLE 12 PARAMETERS IN THE ADD RACK COMMAND
Parameter
Name

RACK

36

Parameter
Description

Rack No.

Confidential and Proprietary Information of ZTE CORPORATION

Instructions
It is a mandatory
parameter within 1~15.
Rack 1 is generated during
creating the exchange.
Other racks need to be
added by manual. The
rack No. begins from 2

Chapter 3 Local Office Data Configuration

Parameter
Name

Parameter
Description

Instructions

Rack type, includes

RACKTYPE

NAME

3G_STANDARD_RACK: ZTE
Standard Rack
3G_INTEGRATION_RACK: ZTE
Integration Rack

Alias

It is an optional parameter
and select according to
real situation

It is an optional parameter
and consists of 0~50
strings

Example: Create a ZTE standard rack whose rack No. is 2.


The command is as follows.
ADD RACK:RACK=2,RACKTYPE=3G_STANDARD_RACK,NA
ME="RACK2";
Example: Create a ZTE integration rack whose rack No. is 3.
The command is as follows.
ADD
RACK:RACK=3,RACKTYPE=3G_INTEGRATION_RAC
K,NAME="RACK2";
END OF STEPS
Result

After the command is executed successfully, the rack is created under MGCF11 exchange, and is shown on the Daily Maintenance
> Rackchart Management tab.

Creating a Shelf
Prerequisites

Context

Before the operation, it is required to confirm:

You know the ID of the exchange to be configured.

The rack is configured under the corresponding exchange.

The MML Terminal window is opened.

Perform this procedure to create a logic shelf on the background


OMM system. It corresponds to the shelf on the foreground. MSCS
only adopts BCTC shelf. One rack can be configured with up to four
BCTC shelves.

Note:
Shelf 2 of rack 1 must be configured first, and then other shelves
are configured.
Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.

Confidential and Proprietary Information of ZTE CORPORATION

37

ZXWN MSCS Data Configuration Guide(MSCS)

Example: Select the MSCS exchange with ID as 11 from the


system tree.
SET:NEID=11;
2. Create a shelf. The command is ADD SHELF.
Table 13 describes the parameters in the ADD SHELF command.
TABLE 13 PARAMETERS IN ADD SHELF COMMAND
Parameter
Name

Parameter
Description

Instructions

RACK

Rack No.

It is a mandatory parameter
that is within 1~15

SHELF

Shelf No.

It is a mandatory parameter,
ranging from 1 to 4. Shelf 2
must be configured first.

TYPE

Shelf type

It is a mandatory parameter.
MSCS can only be configured
with BCTC shelf (control
center shelf)

NAME

Alias

It is an optional parameter,
with a length ranging from 0
to 50 characters.

Example: Create a BCTC shelf in rack 1, with the shelf number


as 2 and the name as BCTC. The specific command is as
follows.
ADD
C";

SHELF:RACK=1,SHELF=2,TYPE=BCTC,NAME="BCT

END OF STEPS
Result

After BCTC shelf is created successfully, the OMP module and the
RPU module are created at the same time. And numbers of these
two modules are 1 and 2. Slots 11 and 12 of the rack display the
OMP board.

Creating a UIM Unit


Prerequisites

Context

38

Before the operation, it is required to confirm:

You know the ID of the exchange to be configured.

The BCTC shelf is configured in the corresponding rack.

The MML Terminal window is opened.

Creating the UIM unit is to create the UIM board. In general, UIM
board adopts 1+1 backup mode. It is fixedly inserted into slots 9
and 10 in the BCTC shelf.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

Note:
You must first create the UIMC unit in shelf 2 of rack 1, and then
create the UIMC units in other BCTC shelves.
Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create a UIM Unit. The command is ADD UNIT.
Table 14 describes the parameters in the ADD UNIT command.
TABLE 14 PARAMETERS IN THE ADD UNIT COMMAND
Parameter
Name

Parameter
Description

Instructions
It is a mandatory
parameter and the format
is RACK-SHELF-SLOT.

LOC

The rack No. is within


1~15 and the default
value is 1. This
parameter is defined
by the ADD RACK
command.

The shelf No. is within


1~4. This parameter
is defined by the ADD
SHELF command.

SLOT represents the


slot number. In BCTC
shelf, the UIM slot
number must be 9 and
10

Unit location

MODULE

Module No.

It is a mandatory
parameter. Select 1

UNIT

Unit No.It is an
optional parameter,
ranging from 1 to
2000

It is an optional parameter,
ranging from 1 to 2000

Unit type

It is a mandatory
parameter. Select it
according to the CPU
type of the UIMC board,
including UIM2_GCS_755
and UIM2_GCS_8260.
UIM2_GCS_755 sub-card
is mostly used at present.

TYPE

Confidential and Proprietary Information of ZTE CORPORATION

39

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instructions

BKMODE

Backup mode

It is a mandatory
parameter and the backup
mode is ONEPLUSONE

NAME

Alias

It is an optional parameter
and consists of 0~50
characters.

Example: Create the UIM units with the following requirements.

Rack No.: 1

Shelf No.: 2

Slot No.: 9 and 10

Unit type: UIM2_GCS_755

Backup mode: 1+1 backup

The specific command is as follows.


ADD UNIT:LOC="1"-"2"-"9",MODULE=1,UNIT=921,TYPE
=UIM2_GCS_755,BKMODE=ONEPLUSONE,CLK1=16383,CL
K2=16383;

Note:
After the 1+1 backup mode is selected for the UIM board located in slot 9, the system will automatically configure the UIM
board located in slot 10. In addition, the unit numbers of left
and right slots are consistent.
END OF STEPS
Result

After the UIM unit is created successfully, the active and standby
UIM boards are shown in the corresponding slots of the rack chart.

Creating a Module
Prerequisites

40

Before the operation, it is required to confirm:

You know the ID of the exchange to be configured.

The UIM unit is created under the exchange.

The MML Terminal window is opened.

Context

When MSCS has several modules, it is required to create SMP


board for BCTC shelf. When BCTC has more shelves, SMP and
CMP modules should be allocated to each BCTC shelf equally.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

Example: Select the MSCS exchange with ID as 11 from the


system tree.
SET:NEID=11;
2. Create a module. The command is ADD MODULE.
Table 15 describes the parameters in the ADD MODULE command.
TABLE 15 PARAMETERS IN ADD MODULE COMMAND
Name

Meaning

Instructions

LOC

Location

It is a mandatory parameter. Its


format is RACK-SHELF-SLOT. The
range of RACK is within 1~15 and the
default value is 1. The shelf No. is
within 1~4 and the slot No. is within
1~17.

MODULE

Module No.

It is a mandatory parameter, ranging


from 3 to 127. A new module is
numbered from 3

FUNC1

Module 1 type

It is a mandatory parameter. Select SMP for a signaling module


only, MSCBASECMP for a service module, MSCBASECMP and
VMSC/CMP_GO/CMP_MSCe/CMP_VLR/CMP_G_GMSC for the
service module of an end office, and
LIC/CMP_G_VLR for an interception
module.

FUNC2

Module 2 type

It is an optional parameter. If it is left


blank, its configuration is the same as
that of FUNC1.

CPU type

It is an optional parameter. Two


options available, X86 and
CENTRINO. Select according to
the actual board type.

BKMODE

Backup mode

It is an optional parameter. In general,


select ONEPLUSONE (one plus one
backup) for a service module, and
ONEPLUSONE (one plus one backup)
or No (Without backup) for a signaling
module, which is determined by the
actual configuration.

NAME1

Module 1 user
alias

It is an optional parameter and


consists of 0~50 characters.

NAME2

Module 2 user
alias

It is an optional parameter and


consists of 0~50 characters.

CPUTYPE

Example: Create SMP modules with the following requirements.

Location: Slots 5 and 6 in BCTC shelf 2 of rack 1

Module number: 3 and 4

Confidential and Proprietary Information of ZTE CORPORATION

41

ZXWN MSCS Data Configuration Guide(MSCS)

Module type: SMP

CPU type: CENTRINO

Backup mode: 1+1 backup

Module 1 name: SMP3

Module 2 name: SMP4.

The specific command is as follows.


ADD MODULE:LOC="1"-"2"-"5",MODULE="3"&"4",FUNC1
="SMP",FUNC2="SMP",CPUTYPE=CENTRINO,BKMODE=ON
EPLUSONE,NAME="SMP3",NAME2="SMP4";
Example: Create CMP modules with the following requirements.

Location: Slots 7 and 8 in BCTC shelf 2 of rack 1

Module number: 5 and 6

Module type: CMP

CPU type: CENTRINO

Backup mode: 1+1 backup

Module 1 name: CMP5

Module 2 name: CMP6.

The specific command is as follows.


ADD MODULE:LOC="1"-"2"-"7",MODULE="5"&"6",FUNC1
="MSCBASECMP"&"VMSC/CMP_GO/CMP_MSCe/CMP_VLR/CM
P_G_GMSC",FUNC2="MSCBASECMP"&"VMSC/CMP_GO/CMP_
MSCe/CMP_VLR/CMP_G_GMSC",CPUTYPE=CENTRINO,BKM
ODE=ONEPLUSONE,NAME="CMP5",NAME2="CMP6";
END OF STEPS
Result

After the SMP/CMP module is added successfully, its corresponding


slot in the rack chart displays the SMP board.

Creating other Units


Prerequisites

Context

Before the operation, it is required to confirm:

You know the ID of the exchange to be configured.

The UIM unit is configured.

The MML Terminal window is opened.

Perform this procedure to create other logic boards in the BCTC


shelf of MSCS exchange, except for UIM unit.
Table 16 lists the main boards in MSCS.

42

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

TABLE 16 MSCS BOARD TYPES


Board

Board Type

Backup Mode

UIM2_GCS_755
UIMC

1+1 active/standby backup


UIM2_GCS_8260
SIPI2_IPSEC

SIPI

No backup or 1+1
active/standby backup

SIPI2_NC
SIPI_NC
SPB_8260_8260C4

SPB

No backup
SPB_8250_85XXC2
USI2_NC

USI

1+1 active/standby backup


USI_NC

Steps

CHUB

CHUB

1+1 active/standby backup

CLKG

CLKG

1+1 active/standby backup

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create other units. The command is ADD UNIT.
Steps

Operations

Creating a CHUB unit

Creating a CLKG unit

Creating an SIPI unit

Creating a USI Unit

Creating an SPB unit

END OF STEPS

Creating a CHUB Unit


Prerequisites

Before the operation, it is required to confirm:

You know the ID of the exchange to be configured.

The UIM unit is created.

The MML Terminal window is opened.

Confidential and Proprietary Information of ZTE CORPORATION

43

ZXWN MSCS Data Configuration Guide(MSCS)

Context

Perform this procedure to create the CHUB logic board corresponding to that in the foreground BCTC shelf of MSCS exchange.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create a CHUB unit. The command is ADD UNIT.
Table 17 describes the main parameters in the ADD UNIT command.
TABLE 17 PARAMETERS IN THE ADD UNIT COMMAND
Parameter
Name

Parameter
Description

Instructions
It is a mandatory
parameter, with a format
of RACK-SHELF-SLOT

LOC

Location of the unit


in the system

RACK represents the rack


number, ranging from 1
to 15. In general, it is
configured as 1

SHELF represents the shelf


number, ranging from 1 to
4

SLOT represents the slot


number.

CHUB boards are fixedly


inserted into slots 15 and 16 in
shelf 2 of rack 1
MODULE

Module number of
the unit

It is a mandatory parameter.
Select 1

UNIT

Unit number of the


board

It is an optional parameter
ranging from 1 to 2000

TYPE

Logic unit type of


the board

Select CHUB

BKMODE

Backup mode of
the unit

1+1 active/standby backup

Example: Create CHUB boards with the following requirements.


Location: Slots 15 and 16 of shelf 2 in rack 1
Unit type: CHUB
Backup mode: 1+1 active/standby backup
Other parameters: default.
The specific command is as follows.

44

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

ADD UNIT:LOC="1"-"2"-"15",MODULE=1,UNIT=1521,TY
PE=CHUB,BKMODE=ONEPLUSONE,CLK1=16383,CLK2=16
383;
END OF STEPS
Result

After the unit is added successfully, corresponding slots of the rack


chart display these CHUB boards.

Creating a CLKG Unit


Prerequisites

Before the operation, it is required to confirm:

You know the ID of the exchange to be configured.

The UIM unit is configured.

The MML Terminal window is opened.

Context

Perform this procedure to create the CLKG logic board corresponding to that in the foreground BCTC shelf of MSCS exchange.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create a CLKG unit. The command is ADD UNIT.
describes the parameters in the ADD UNIT command.
Parameter
Name

Parameter
Description

Instructions
It is a mandatory
parameter and the format is
RACK-SHELF-SLOT.

LOC

The rack No. is within


1~15 and the default
value is 1. This
parameter is defined
by the ADD RACK
command.

The shelf No. is within


1~4. This parameter
is defined by the ADD
SHELF command.

The slot No. is within


1~17.

Unit location

MODULE

Module No.

It is a mandatory parameter.
Select the OMP module
belonging to CLKG.

UNIT

Unit No.

It is an optional parameter,
ranging from 1 to 2000.

Confidential and Proprietary Information of ZTE CORPORATION

45

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instructions

TYPE

Unit type

It is a mandatory parameter.
For CLKG, select CLKG

BKMODE

Backup mode

It is a mandatory parameter
and the backup mode is
ONEPLUSONE.

NAME

Alias

It is an optional parameter
and consists of 0~50
characters.

Example:
ments.

Create CLKG boards with the following require-

Location: Slots 13 and 14 of shelf 2 in rack 1

Unit type: CLKG

Backup mode: 1+1 active/standby backup

Other parameters: default.

The specific command is as follows.


ADD UNIT:LOC="1"-"2"-"13",MODULE=1,UNIT=1321,TY
PE=CLKG,BKMODE=ONEPLUSONE,CLK1=16383,CLK2=163
83;
3. After configuring the CLKG unit, configure the CLKG board parameters with the SET CLKETHR command as required. Configure its parameters based on the clock source actually provided.
Example: Configure the clock reference of the CLKG board is
8KBase. The command is as follows.
SET CLKETHR:CLKBASE=ALLOWED,BASETYPE=8KBase,B
ASEINFO="8KBase";
END OF STEPS
Result

After the unit is created successfully, corresponding slots of the


rack chart display these CLKG boards.

Creating an SIPI Unit


Prerequisites

Context

Before the operation, it is required to confirm:

You know the ID of the exchange to be configured.

The UIM unit is added.

The MML Terminal window is opened.

Perform this procedure to create the SIPI logic board corresponding to that in the foreground BCTC shelf of MSCS exchange.

SIPI boards work in load-sharing mode


In load-sharing mode, two SIG-IPI boards both serve as active board, and maintain each own associations. The relationship between associations is load-sharing, which means that

46

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

the service transmission is shared evenly by the associations


of these two SIG_IPI boards. When the association on one of
these two interface boards is interrupted, all the service data
will be moved to the association of another interface board that
works normally. In this way, the inter-office communication
will not be interrupted for this cause. This project is recommended for office commissioning .

SIPI boards work in active/standby mode .


Two SIG_IPI boards serve as mutual backup. In normal conditions, associations are only processed on active board, and
backed up only on standby board. The associations on the active board are disconnected when the active board is abnormal
or extracted. At this moment, the standby board quickly replaces the active board to connect the associations, thus to
restore the normal communication between offices.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create an SIPI unit. The command is ADD UNIT.
Table 18 describes the main parameters in the ADD UNIT command.
TABLE 18 PARAMETERS IN THE ADD UNIT COMMAND
Parameter
Name

Parameter
Description

Instructions
It is a mandatory
parameter, with a format
of RACK-SHELF-SLOT

RACK represents the rack


number, ranging from 1
to 15. In general, it is
configured as 1

SHELF represents the


shelf number, ranging
from 1 to 4

SLOT represents the slot


number.

Location of the unit


in the system

LOC

MODULE

Module number of
the unit

It is a mandatory parameter.
Select 1

UNT

Unit number of the


board

It is an optional parameter.
Ranging from 1 to 2000.

TYPE

Logic unit type of


the board

Select SIPI_NC

Backup mode of
the unit

It supports the NO (Without


backup) and ONEPLUSONE
(One plus one backup)
modes. Select it according to
the actual networking mode

BKMODE

Confidential and Proprietary Information of ZTE CORPORATION

47

ZXWN MSCS Data Configuration Guide(MSCS)

Example: Create SIPI boards with the following requirements.

Location: Slots 3 and 4 of shelf 2 in rack 1

Unit type: SIPI_NC

Backup mode: 1+1 active/standby backup

Other parameters: default.

The specific command is as follows.


ADD UNIT:LOC="1"-"2"-"3",MODULE=1,UNIT=321,TYPE
=SIPI_NC,BKMODE=ONEPLUSONE,CLK1=16383,CLK2=16
383;
END OF STEPS
Result

After the unit is created successfully, corresponding slots of the


rack chart display these SIPI boards.

Creating a USI Unit


Prerequisites

Before the operation, it is required to confirm:

You know the ID of the exchange to be configured.

The UIM unit is configured.

The MML Terminal window is opened.

Context

Perform this procedure to create the USI logic board corresponding


to that in the foreground BCTC shelf of MSCS exchange.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create a USI unit. The command is ADD UNIT.
Table 19 describes the main parameters in the ADD UNIT command.
TABLE 19 PARAMETERS IN THE ADD UNIT COMMAND
Parameter
Name

Parameter
Description

Instructions
It is a mandatory
parameter, with a format
of RACK-SHELF-SLOT

LOC

48

RACK represents the rack


number, ranging from 1
to 15. In general, it is
configured as 1

SHELF represents the shelf


number, ranging from 1 to
4

Location of the
unit in the system

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

Parameter
Name

Parameter
Description

Instructions

SLOT represents the slot


number.

MODULE

Module number of
the unit

It is a mandatory parameter.
Select 1

UNT

Unit number of
the board

It is an optional parameter.
Ranging from 1 to 2000.

TYPE

Logic unit type of


the board

Select USI_NC

BKMODE

Backup mode of
the unit

Select ONEPLUSONE

Example: Create SIPI boards with the following requirements.

Location: Slots 1 and 2 of shelf 2 in rack 1

Unit type: USI_NC

Backup mode: 1+1 active/standby backup

Other parameters: default.

The specific command is as follows.


ADD UNIT:LOC="1"-"2"-"1",MODULE=1,UNIT=121,TYPE
=USI_NC,BKMODE=ONEPLUSONE,CLK1=16383,CLK2=163
83;
END OF STEPS
Result

After the unit is created successfully, corresponding slots of the


rack chart display these USI boards.

Creating an SPB Unit


Prerequisites

Before the operation, it is required to confirm:

You know the ID of the exchange to be configured.

The UIM unit is configured.

The MML Terminal window is opened.

Context

Perform this procedure to create the SPB logic board corresponding to that in the foreground BCTC shelf of MSCS exchange. SPB
board is created only when the narrowband No.7 signaling is used
between MSCS and other offices, such as HLR.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create an SPB unit. The command is ADD UNIT.

Confidential and Proprietary Information of ZTE CORPORATION

49

ZXWN MSCS Data Configuration Guide(MSCS)

Table 20 describes the main parameters in the ADD UNIT command.


TABLE 20 PARAMETERS IN THE ADD UNIT COMMAND
Parameter
Name

Parameter
Description

Instructions
It is a mandatory
parameter and the format
is RACK-SHELF-SLOT.

LOC

The rack No. is within 1~15


and the default value is 1.
This parameter is defined by
the ADD RACK command.

The shelf No. is within 1~4.


This parameter is defined by
the ADD SHELF command.

The slot No. is within 1~17.

Location of the
unit in the system

MODULE

Module number
of the unit

It is a mandatory parameter.
Select 1

UNT

Unit number of
the boar

It is an optional parameter.
Ranging from 1 to 2000.

TYPE

Logic unit type of


the board

Select it according to the CPU


type of this SPB board, for
example, SPB_8260_8260C4

BKMODE

Backup mode of
the unit

Select NO

Example: Create an SPB board with the following requirements.

Location: Slot 7 of shelf 2 in rack 1

Unit type: SPB_8260_8260C4

Backup mode: No backup

Other parameters: default.

The command is as follows.


ADD UNIT:LOC="1"-"2"-"7",MODULE=1,UNIT=721,TYPE
=SPB_8260_8260C4,BKMODE=NO,CLK1=16383,CLK2=16
383;
Example: Create an SPB board with the following requirements.

Location: Slot 8 of shelf 2 in rack 1

Unit type: SPB_8260_8260C4

Backup mode: No backup

Other parameters: default.

The command is as follows.

50

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

ADD UNIT:LOC="1"-"2"-"8",MODULE=1,UNIT=821,TYPE
=SPB_8260_8260C4,BKMODE=NO,CLK1=16383,CLK2=16
383;
END OF STEPS
Result

After the unit is created successfully, corresponding slot of the rack


chart display the SPB board.

Creating MSCS Background Server


Prerequisites

Before the operation, it is required to confirm:

You know the ID of the exchange to be configured.

The corresponding MP module is configured.

The MML Terminal window is opened.

Context

Perform this procedure to connect the SMP with the billing server.
All SMP units should be mapped to the billing server.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create MSCS background server. The command is ADD SVRI
NF.
Table 21 describes the main parameters in the ADD SVRINF
command.
TABLE 21 PARAMETERS IN THE ADD SVRINF COMMAND
Parameter
Name

Parameter Description

Instructions

MODULE

Module number of
foreground MP

It is a mandatory
parameter, ranging from
1 to 127, including all
the modules except for
module 2

CGMODULE

Module number of
billing server

It is an optional
parameter, ranging
from 130 to 135

Example: Create the billing server node 130 corresponding to


the foreground SMP module 3. The specific command is as
follows.
ADD SVRINF: MODULE= 3, CGMODULE= 130;
END OF STEPS

Confidential and Proprietary Information of ZTE CORPORATION

51

ZXWN MSCS Data Configuration Guide(MSCS)

Capacity and Load-Sharing


Configuration
Overivew
Table 22 shows the capacity configuration flow.
TABLE 22 CAPACITY AND LOAD-SHARING CONFIGURATION
Steps

Operation

Instruction

Command

Setting the MSCS


office capacity

Set the capacity


for each table in
the MP module

SET MSCSCAPAC
ITY

Setting service
data area

Normally select the


default value for all
parameters

SET DATASIZE

Creating IMSI load


sharing

Select different
SMPs to process
different number
sections

ADD IMSILOAD

Creating TMSI
module load
sharing

Ccreate the TMSI


load sharing
when the IMSI
load-sharing
configuration is
completed.

ADD TMSILOAD

Setting the MSCS Office Capacity


Prerequisites

Context

To perform this operation, the following conditions must be met:

The ID of the exchange to be configured is known.

The physical configuration is completed.

The MML Terminal window is opened.

This topic describes how to set the capacity for each table in the MP
module. MSCS capacity is configured according to the actual capacity of the equipment, including these parameters such as GCI,
LAI, PCM, DNAL, and BSC. In general, these parameters adopt
their default value, except in special cases.

Caution:
After modifying the capacity for the LAI configuration table or the
BSC/RNC configuration table, it is required to restart the network
management.

52

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

Steps

1. If the exchange is not specified, it is required to use the command SET in the MML Terminal or select the network element
from the system tree in order to specify the exchange to be
configured.
For example, select MSCS 11 from the system tree.
SET:NEID=11;
2. Set the MSCS office capacity with the command SET MSCSC
APA.
The parameter description of the command SET MSCSCAPAC
ITY is shown in Table 23.
TABLE 23 PARAMETERS IN THE SET MSCSCAPACITY COMMAND
Parameter
Name

Parameter Description

Range

GCI

Capacity Of GCI Config


Table

1~12000

1280

LAI

Capacity Of LAI Config Table

1~1000

64

AOCFEE

Capacity Of Tariff Config


Table

1~1000

128

IROAM

Capacity Of IMSI Analysis


Config Table

1~3000

1000

PCM

Capacity Of PCM Table

2000~20
000

2048

BSC

Capacity Of
Config Table

1~128

32

MASK

Capacity Of Black/ White


List Number

1~80000

2048

NUMLEN

Capacity Of Number Preanalysis

1~20000

1000

CALLDATA

Capacity Of CFG Relationship Table

1~1024

512

CTRLUNT

Capacity Of Access Network Unit

1~128

64

SIPRES

Capacity Of SIP Call Resources

1000~15
000

2500

HRBTMS

Capacity Of Home Ring


Back Tone

1~80000

SSP

Capacity Of Special Service Phone Group

1~60000

1024

USER

Capacity Of Users Undercontrol

1~80000

4000

TIDTRUNK

Capacity Of TID And Trunk


Link

1~1024

512

BSC/RNC

Default

Confidential and Proprietary Information of ZTE CORPORATION

53

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter Description

Range

MDNAL

Capacity Of Mobile NumAnalysis Config

1~65535

8192

DNAL

Capacity Of Num-Analysis
Config

1~10000
0

8192

MPDFT

Capacity Of Default PerDef Timer(MP)

2000~10
000

2000

MPDEF

Capacity Of Defined PreDef Timer(MP)

2000~15
000

2000

PPDFT

Capacity Of Default PreDef Timer(PP)

2000~10
000

2000

PPDEF

Capacity Of Defined PreDef Timer(PP)

2000~10
000

2000

LIMITMS

Capacity Of Limit Cheating Subscriber

0~60000

DNHOME

Capacity
Home

1~40000
0

150000

LINK

Capacity Of Link

1920~50
00

1920

GT

Capacity Of GT

20001~5
0000

20000

SPC

Capacity Of SPC

1~2000

2000

VMSC

Capacity Of VMSC Table

16~256

16

SAI

Capacity Of SAI Config Table

1~12000

1280

MGW

Capacity Of MGW

1~128

32

ANANACAPACITY

Capacity Of Announcement User Analyzer

1~65535

1024

Of

Number

Default

For example, set the MSCS office capacity. Select the default
value for all parameters. The command is as follows:
SET MSCSCAPACITY;
END OF STEPS
Postrequisite

1. Configure the OMP startup parameters through a serial port.


2. Synchronize the capacity planning table to the foreground.
3. Restart OMP and the realted MP boards.
4. Synchronize all the tables to the foreground again.

54

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

Note:
It is required to synchronize the office capacity table to the foreground twice. After the first synchronization, wait 5~10 minutes
for the OMP to complete the disk saving, and then restart the OMP.
When the OMP starts successfully, it is required to synchronize the
capacity tables to the OMP again. After the first synchronization,
only the space of the capacity table on the OMP is established, but
the table contents are not added. After the second synchronization, the table contents are synchronization.

Setting Service Data Area


Prerequisites

Before the operation, it is required to confirm:

You know the ID of the exchange to be configured.

The physical configuration is completed.

The MML Terminal window is opened.

Context

Perform this procedure to configure the service data area. Generally, it adopts the default value, except in special cases.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Set the service data area. The command is SET DATASIZE.
Table 24 shows the description of main parameters in the SET
DATASIZE command.
TABLE 24 PARAMETERS IN THE SET DATASIZE COMMAND
Parameter
Name

Parameter
Description

Instruction

CMODEL

One-MSC
multi-MGW call
model, including
AMONLY(Associated Mode Only)
and QAMALLOW(Quasi-associated Mode
Allowed)

Select QMALLOW when a


call needs three MGWs under
the MSCS to provide bearers.
Otherwise, select AMONLY

Number of BCBM
data areas

Configure it as 10 when
the MSCS is associated
with one MGW to conform
a network, or in a full IP
networking mode. Configure
it as 3600 when the end

BCBMNUM

Confidential and Proprietary Information of ZTE CORPORATION

55

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction
office adopts the multi-call
model. Configure it as 12400
when the tandem office and
gateway office adopt the
multi-call model.

DSTCDNUM

Number of
destination codes

Type an integer ranging


from 1 to 10000, which
is associated with
the destination-code
traffic-statistics in the
performance statistics.

CTSTNUM

Maximum number
of mixed flow of
traffic

Integer numbers ranging


from 100 to 11000

CTSTINDEXS
IZE

CTST index size


(KB)

Integer numbers ranging


from 16 to 4096

VMSCNO7
NUM

Number of
VMSC/OMP module
NO7 call data area

Integer numbers ranging


from 2000 to 10000

CMPNO7NUM

Number of CMP
module NO7 call
data area

Integer numbers ranging


from 10000 to 30000

Example: Configure a service data area. The MSCS is associated with an MGW. The number of destination codes is 4096.
Other parameters adopt the default value. The specific command is as follows.
SET DATASIZE:CMODEL=AMONLY,BCBMNUM=10,DSTCD
NUM=4096;
END OF STEPS

Creating IMSI Load Sharing


Prerequisites

56

Before the operation, it is required to confirm:

You know the ID of the exchange to be configured.

CMP modules are created.

The MML Terminal window is opened.

Context

Creating IMSI load-sharing is used to select different SMPs to


process different number sections. It is required to configuring
the MSCS end office to make the CMP modules have the VMSCS
attributes.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

Example: Select the MSCS exchange with ID as 11 from the


system tree.
SET:NEID=11;
2. Create the load-sharing scale of CMP modules. The command
is ADD IMSILOAD.
Table 25 describes the main parameter description of the ADD
IMSILOAD command.
TABLE 25 PARAMETERS IN THE ADD IMSILOAD COMMAND
Parameter
Name

MODULE

Parameter
Description

Instruction

Service module
number of the
SMP processing
subscriber
services

The CMP module number is


already created in the system.
The default allocation mode of
IMSI is Continue. For example,
for the number section 0~999,
modules 5 will share the number
section 0~499, and module 6
will share the number section
500~999

Example: Create the load-sharing for CMP modules 5 and 6.


The specific command is as follows.
ADD IMSILOAD:MODULE="5"&"6";
END OF STEPS
Postrequisite

1. Synchronize the data to the foreground.


2. Restart the related SMP board.

Creating TMSI Load Sharing


Prerequisites

Before the operation, it is required to confirm:

You know the ID of the exchange to be configured.

IMSI load sharing configuration is completed.

The MML Terminal window is opened.

Context

Perform this procedure to create the TMSI load sharing when the
IMSI load-sharing configuration is completed.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the TMSI load sharing. The command is ADD TMSILO
AD.

Confidential and Proprietary Information of ZTE CORPORATION

57

ZXWN MSCS Data Configuration Guide(MSCS)

Example: Create the TMSI load sharing. The specific command


is as follows.
ADD TMSILOAD;
END OF STEPS
Postrequisite

1. Transmit the data to the foreground.


2. Restart the related SMP board.

Version Loading
Overview
Descriptions

All physical boards need the software to support the running. If


the same physical board is loaded with different running software,
it will be with different functions. At first, the physical board is not
loaded with the software supporting the running, so it is required
to load it by manual.
The version files of the OMP module are obtained from the OMC
server via FTP. For the version files of other boards (including RPU),
they are obtained from OMP during the restart. The steps to load
the version files are as follows:

58

Load the version files that are needed by the board from the
configured version file directory to the version database of the
OMC server.

Add the version files in the version database into the foreground OMP.

Add the corresponding records into the database table related


to the version files, so the other boards could obtain the version
files from OMP according to these records.

During restarting the board, compare the existing version files


with the old version files on OMP and check whether they are
consistent. If they are the same, adopt the old version fiels;
otherwise, download the new version files from OMP.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

Configuration
Flow

Figure 14 shows the loading flow of a board version files.


FIGURE 14 FLOW OF LOADING VERSION FILES

Flow Description
Steps

Operations

Instructions

Creating the
version file
directory

Make sure the version number and


path of the version files to be loaded.

Creating the OMP


boot files

Generate the ompcfgX.ini (X is the


ID of corresponded exchange) boot
file on the OMM server. OMP board
loads its version files according to
this file.

Configuring the
OMP startup
parameters via
serial port

Configures some parameter


information for OMP board to
communicate with OMM server
during startup.

Confidential and Proprietary Information of ZTE CORPORATION

59

ZXWN MSCS Data Configuration Guide(MSCS)

Steps

Operations

Instructions

Setting global data


OMP information

After OMP board is started,


the OMP global data should be
configured to make sure that the
foreground/background IP addresses
are in the same network section.

Synchronizing all
tables

After the data configuration is


completed, the configuration data
stored on the OMM server are
synchronized to the foreground
for foreground NEs to get the
configuration data from the OMM
server.

Loading version
files

Manually loads the version files


required for board running.

Creating Version File Directory


Prerequisites

Before the operation, it is required to confirm:

The version file has been prepared.

The physical configuration and the capacity configuration are


completed.

The MML Terminal window is opened.

Context

Perform this procedure to create the version name and version


path of the version file to be loaded.

Steps

1. On the NetNumen M30 window, select menus Views > Professional Maintenance to enter the Professional Maintenance window.
2. In the left pane, double-click the exchange node in the Professional Maintenance tree. Select Version Management
> Version Maintenance to show the Version Maintenance
tab in the right pane, as shown inFigure 15.

60

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

FIGURE 15 VERSION LOADING

3. On the Load Version tab, Click the button on the sub-toolbar to pop up the Config Version Path tab, as shown in Figure
16.
FIGURE 16 CONFIGURING VERSION PATH

4. Right-click the list on the Config Version Path tab, and select
Create from the short-cut menu. A new blank entry is added
on the Config Version Path tab.
5. Double-click the Version filed on the tab, and type the version
number (the version number format is V0.00.00.B0, in which,
0 indicates digital and B indicates character), which should be
consistent with the version number of the version file.

Confidential and Proprietary Information of ZTE CORPORATION

61

ZXWN MSCS Data Configuration Guide(MSCS)

6. On the Config Version Path tab, double-click the blank entry


in the File Path column. The
button appears.
7. Click the
button and then the OPEN dialog will pop up.
Select the save path for the version file, as shown in Figure
17.
FIGURE 17 VERSION FILE PATH

8. After setting the path, it is required to save the setting. On the


Config Version Path tab, right click any item and then select
the Save button. After the successful saving, the Successfully dialog appears. Click the OK button.
END OF STEPS

Creating OMP Boot Files


Prerequisites

Context

Before the operation, it is required to confirm:

Version file directory is created.

The MML Terminal window is opened.

To create an OMP boot file is to generate an ompcfgX.ini boot file


on the OMC server, of which the X is the number of the corresponding exchange. This file contains the file names of CPU and
FPGA required for normal running of OMP module.
The CPU files and the FPGA files required by OMP are listed inTable
26.

62

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

TABLE 26 VERSION DESCRIPTION OF OMP BOOT FILE


OMP CPU
Type

Version
Type

Version File Name

CPU

MSCS_MPX86_MP_X86_CS_Z_T.BIN

FPGA

MPX86_05_040202_FPGA_105.RBF

CPU

MSCS_MPX86_2_MP_P4_CS_Z_T.BIN

FPGA

MPX862_04_040704_FPGA_109.RBF

MPX86

CENTRINO

Steps

1. On the NetNumen M30 window, select menus Views > Professional Maintenance to enter the Professional Maintenance window.
2. Double-click the exchange node under the Professional
Maintenance tree and then select Version Management >
Version Maintenance, Load Version tab appears, as shown
in Figure 18.
FIGURE 18 LOAD VERSION

3. On the Load Version tab, select the version No. from the
pull-down list of the Version.
4. On the Load Version tab, press the CTRL key while selecting
the CPU file and FPGA file required by the OMP, which are listed
in Table 26. Right-click the selected version files, and then
select Create OMP Ini File from the shortcut menu, as shown
in Figure 19.

Confidential and Proprietary Information of ZTE CORPORATION

63

ZXWN MSCS Data Configuration Guide(MSCS)

FIGURE 19 CREATING OMP BOOT FILES

5. After the OMP boot file is created successfully, the message


area prompts that OMP boot files are created successfully.
END OF STEPS

Configuring OMP Running


Parameters via Serial Port
Prerequisites

Before the operation, it is required to confirm:

The serial cable has been prepared.

The OMP boot file has been created.

The hyper-terminal has been installed on the computer.

Context

Perform this procedure to configure some parameters, including


OMM address, OMC server address, office ID, FTP user name/password and startup mode. These parameters are required by OMP
board to communicate with the OMM server during startup.

Steps

1. Connect one end of RS232 serial cable to serial port of debugging computer, another end to debug port of OMP backboard.
2. On the debugging computer, click Start > Programs >
Accessories > Communications > Hyper Terminal in the
Windows OS, as shown in Figure 20.

64

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

FIGURE 20 CONNECTION DESCRIPTION

3. After click OK, the following figure pops up. Select the serial
port connected to the foreground and then click OK, as shown
in Figure 21.
FIGURE 21 CONNECT TO DIALOG BOX

4. On the COM1 dialog box, click the Restore Defaults button,


and then click OK, as shown in Figure 22

Confidential and Proprietary Information of ZTE CORPORATION

65

ZXWN MSCS Data Configuration Guide(MSCS)

FIGURE 22 COM1 PROPERTIES

5. After entering the hyper-terminal, if there is no words, restart


the OMP board. When the Press any key to stop auto-boot...
prompt appears after entering hyper-terminal, press any key
instantly to stop automatic booting and then to configure the
OMP parameters, as shown in Figure 23.
FIGURE 23 PRESS ANY KEY TO STOP AUTO-BOOT

6. If the Boot Password (3GPLAT or 3gplat) appears, as shown in


Figure 24, type the password 3gplat and press Enter.

66

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

FIGURE 24 BOOT PASSWORD

7. When the 3GPlat Boot appears, type 1 to select Config MPnet parameters (only for Omp and Cmp), and then press
Enter, as shown in Figure 25.
FIGURE 25 3GPLAT BOOT

8. Open the Config selection window, type 1 to select Set Omp


(or Cmp)s Omc IP.MAC.Gateway IP, and then press Enter,
as shown in Figure 26.

Confidential and Proprietary Information of ZTE CORPORATION

67

ZXWN MSCS Data Configuration Guide(MSCS)

FIGURE 26 CONFIG SELECTION

9. Enter the OMPs OMC Ip Address window, and type the IP


address 192.168.X.1 in which, the X indicates the office direction ID of the office, and then Press Enter, as shown in Figure
27.
FIGURE 27 ENTER OMPS OMC IP ADDRESS

10. Enter the Enter OMPs OMC Mac address window, type the
hardware address 00.208.208.161.00.X planned by OMP, in
which, the X indicates the office ID of the office, as shown in
Figure 28. Press Enter.

68

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

FIGURE 28 ENTER OMPS OMM MAC ADDRESS

11. Enter the Enter OMPs Gateway Ip address window, type


the network gateway IP address of the OMM server, or press
Enter to skip this configuration, as shown in Figure 29.
FIGURE 29 ENTER OMPS GATEWAY IP ADDRESS

12. Enter the Enter OMC Server IP Address address window,


type the IP address of the OMM server, and press Enter, or
press Enter directly to skip this configuration, as shown in
Figure 30.

Confidential and Proprietary Information of ZTE CORPORATION

69

ZXWN MSCS Data Configuration Guide(MSCS)

FIGURE 30 OMC SERVER IP ADDRESS

13. Enter the Config selection window, type 2, and then press
Enter, as shown in Figure 31.
FIGURE 31 CONFIG SELECTION

14. Enter the Enter OMC IP Address window, type the IP address
of the OMM server, and then press Enter, as shown in Figure
32.

70

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

FIGURE 32 OMM IP ADDRESS

15. Enter the Enter OMC FTPSVR User Name window, type the
default FTP name uep, and then press Enter. Then the Enter
OMC FTPSVR User Password window will pop up, type the
default FTP password uep and press Enter, as shown in Figure
33.
FIGURE 33 FTP CONFIG

16. Enter the Enter OMC FTPSVR File Path window, press Enter
to skip this configuration, and then enter the boot file configuration window.
17. Type the boot file name ompcfgX.ini, in which, the X indicates
the office direction ID of this office, then press Enter, as shown
in Figure 34.

Confidential and Proprietary Information of ZTE CORPORATION

71

ZXWN MSCS Data Configuration Guide(MSCS)

FIGURE 34 OMPCFG FILE

18. Enter the Config selection window and type 3, as shown in


Figure 35.
FIGURE 35 CONFIG SELECTION

19. Enter the Set OMP Boot Type window, type 0 and then press
Enter, as shown in Figure 36.

72

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

FIGURE 36 OMP BOOT TYPE

20. Enter the Config selection window and then type 4, as shown
in Figure 37.
FIGURE 37 CONFIG SELECTION

21. Enter the Enter Bureau No. window, type the office direction
ID, and then press Enter, as shown in Figure 38.

Confidential and Proprietary Information of ZTE CORPORATION

73

ZXWN MSCS Data Configuration Guide(MSCS)

FIGURE 38 BUREAU NO.

22. Enter the Config selection window and then type 5, as shown
in Figure 39.
FIGURE 39 CONFIG SELECTION

23. Enter the 3GPlat Boot configuration window, type 0 and


then press Enter, as shown in Figure 40.

74

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

FIGURE 40 3GPLAT BOOT

END OF STEPS
Result

When the OMP starts up automatically, it will download the version


file and the FPGA file from the OMM server. The OMP board runs
normally, and the RUN indicator on the OMP board flashes slowly.

Setting Global Data OMP Information


Prerequisites

Before the operation, it is required to confirm:

The OMM server and the local maintenance terminal are installed correctly.

OMP startup parameters are configured.

The MML Terminal window is opened.

Context

After OMP board is started, the OMP global data should be configured to make sure that the foreground/background IP addresses
are in the same network section. For example, the IP of the OMM
server is 192.4.1.1, and the IP of the foreground is 192.168.79.1.
In order to ensure that the IP address of the foreground and that
of the background are in the same network section, it is required
to set the MASK as 255.0.0.0.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Set the global data OMP information, the command is SET
OMP.
Table 27 describes the parameters in SET OMP command.

Confidential and Proprietary Information of ZTE CORPORATION

75

ZXWN MSCS Data Configuration Guide(MSCS)

TABLE 27 PARAMETERS IN THE SET OMP COMMAND


Parameter
Name

Parameter
Description

Instructions

OMPIP

OMP background IP
address

It indicates the valid


IP address. Enter
it according to the
actual conditions. The
background can access
the OMP through this IP
address

MASK

OMP background IP
mask

Configure the address


range of OMP. Types it
according to the real
condition

GATEWAY

OMP to OMM gateway

If there is no gateway, it
can be the sub-network
address of OMM SERVER

OMCIP

OMC server sub


network

It indicates the valid


IP address. Enter it
according to the actual
conditions

Example: Set the global data OMP information with the following requirements.

OMP IP address: 192.168.4.1

OMP subnet address to the background IP: 255.255.0.0

Gateway IP address: 192.168.1.1

OMC server IP address: 192.168.79.1

The command is as follows:


SET OMP:OMPIP="192.168.4.1",MASK="255.255.0.0",GA
TEWAY="192.168.1.1",OMCIP="192.168.79.1",RELINK=Y
ES;
END OF STEPS

Synchronizing All Tables


Prerequisites

Context

76

Before the operation, it is required to confirm:

The OMM server and the local maintenance terminal are installed correctly.

The MML Terminal window is opened.

To synchronize the data is to send the data saved in the OMM


server to the foreground so that the foreground network element
can obtain the data from the OMM server. Only the admin subscriber can synchronize all the tables.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Synchronize all the tables. The command is SYNA.
Table 28 describes the parameters in this command SYNA.
TABLE 28 PARAMETERS IN SYNA COMMAND
Parameter
Name

USERNAME

Parameter
Description

Instructions

User Name

It is an optional parameter for


designating the name of the
user whose data are transferred,
with a length ranging from 0 to
50 characters. If it is left blank,
the table data of admin's own
are transferred.
It includes

Transmission
type

STYPE

CHG (Single User Changed


Tables)

ALL (All Tables)

ALLCHG (All Changed


Tables)

It is an optional parameter for


designating the module(s) to be
transferred.
MODULES

Module list

Up to 127 modules can be


selected, which is represented
by a decimal numeral, and
separated with & (for example,
MODULES=1&3&4).
Empty string indicates all
modules.
It is an optional parameter, with
a default of 600.

TIMEOUT

Response
timeout
(100ms)

SAVE

Save when
completed

It is an optional parameter.
Usually the default value YES is
selected.

TOSLAVE

Sync to slave
when completed

It is an optional parameter. In
general, the default value YES
is selected.

Adjust this duration according


to the actual requirements. Set
a longer timeout duration when
the data are large, otherwise,
timeout failure may occur

Example: To synchronize all the tables with admin user, the


command is as follows:

Confidential and Proprietary Information of ZTE CORPORATION

77

ZXWN MSCS Data Configuration Guide(MSCS)

SYNA:STYPE=ALL,TIMEOUT=600,SAVE=YES,TOSLAVE=Y
ES;
END OF STEPS
Postrequisite

It is required to restart the OMP board.

Note:
It is required to resynchronize the data for three times and restart
the OMP board for two times. Before the restart, it is required to
confirm whether the synchronized table is saved. The save operation may take three to five minutes. Two methods are available.

Check the disk saving status of the foreground on the OMM


client.

Check whether the usage ratio of the foreground CPU is about


3% with the GetCpu command.

Checking Operations
1. Select Start > Run, then the Run dialog box will pop up.
2. Type CMD and then press Enter to enter the CMD dialog box.
3. Type telnet 192.168.X.1, in which, the X indicates the office
direction ID, and then press Enter.
4. Type the user name zte and the password zte, and then press
Enter for two times, as shown in Figure 41.
FIGURE 41 USER NAME AND PASSWORD

5. Type SCSSHowMcmInfo to check the status of the board and


then press Enter, as shown in Figure 42.

78

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

FIGURE 42 STATUS

The printed status of the board is MASTER and Work, which means
that the OMP board runs normally.

Loading Version Files


Prerequisites

Context

Before the operation, it is required to confirm:

All the tables are synchronized.

The version files of each board are ready.

The foreground and background are correctly connected.

A physical board initially does not load its version files, so you need
to add them manually.
Table 29 lists the board version files.

TABLE 29 BOARD VERSION FILES


Physical
Board Type

Logical
Board Type

Version Type

Version File Name

Instructions

MPX86

RPU

CPU

MSCS_MPX86_RPU_X86_C
S_Z_T.BIN

Version
of RPU

file

MPX86

MP

CPU

MSCS_MPX86_MP_X86_CS
_Z_T.BIN

Version
of SMP

file

MPX86_2

RPU

CPU

MSCS_MPX86_2_RPU_P4_
CS_Z_T.BIN

Version
of RPU

file

MPX86_2

MP

CPU

MSCS_MPX86__2MP_P4_C
S_Z_T.BIN

Version
of SMP

file

UIM_2

UIM

CPU

MSCS_UIM_2_UIM_755_C
S_Z_T.BIN

Version file
of UIMC

CPU

MSCS_MNIC_SIG_IPI_BEA
RM_CS_Z_T.BIN

MNIC

SIPI
MICROCODE

UC_MSCSERVER_MNIC_SI
G_IPI_CS__T.UOF

Version
of SIPI

Confidential and Proprietary Information of ZTE CORPORATION

file

79

ZXWN MSCS Data Configuration Guide(MSCS)

Physical
Board Type
SPB

MNIC

CHUB

CLKG

Logical
Board Type
SPB

Version Type

Version File Name

CPU

MSCS_SPB_SPB_8260_CS
_Z_T.BIN

CPU

MSCS_MNIC_USI_BEARM_
CS_Z_T.BIN

USI

CHUB

Steps

Instructions
Version
of SPB

file

Version
of USI

file

MICROCODE

UC_MSCSERVER_MNIC_US
I_CS__T.UOF

CPU

MSCS_CHUB_CHUB_8245_
CS_Z_T.BIN

Version file
of CHUB

It is not required
to
load the version files

1. On the NetNumen(TM) M30 MSCS/MGW window, select


Views > Professional Maintenance to enter the Professional Maintenance window.
2. Double-click the exchange under the Profession Maintenance tree in the left pane. Select the Version Management
> Version Maintenance node to pop up the Load Version
tab in the right pane, as shown in Figure 43.
FIGURE 43 VERSION LOADING

3. On the Load Version tab, select the version number from the
Version pull-down list.
4. On the Load Version tab, press down the CTRL key, and select
all the version files (the version files required by each board are
shown in Table 29) required by the foreground board, as shown
in Figure 44.

80

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

FIGURE 44 BATCH VERSION LOADING BY DEFAULT

5. Right click the selected version files and select the shortcut
menu Batch Load Default Version. The Switch Process
window will pop up, which displays the process of the version
file (that is the multicast process).
END OF STEPS
Result

Postrequisite

After the version loading is completed, the board will restart. The
board compares its version files, and obtains its required version
files. After the version files are loaded, the board is in normal
running status. The RUN indicator on the front panel of the board
will flash at 1 Hz.
It is required to synchronize the data.
Verifications
1. Judge whether the board runs normally through the indicators on the panel. Table 30 lists the indicator statuses of each
board.
TABLE 30 BOARD INDICATOR STATUSES
Name

Color

Meanings

Green

RUN
indicator

ACT

Green

Active/
standby
indicator

ALM

Red

Alarm

RUN

Instruction
Flashing at 5 Hz:
the board is being
powered on.
Flashing at 1 Hz:
the board is running
normally.
On: The board is
active
Off: The board is
standby
On: The board gives

Remarks
When all the
indicators
on the board
are ON,
probably
the board
hardware
is faulty,
the board
data is not
configured,
or the boot
file of the
does not

Confidential and Proprietary Information of ZTE CORPORATION

81

ZXWN MSCS Data Configuration Guide(MSCS)

Name

Color

Meanings

Instruction
an alarm.

indicator

Off: The board


gives no alarm.

Remarks
match the
version files.

2. On the Version Query tab, check whether the version file


number of the board is correct, thus to verify whether the version files are loaded correctly.

Creating MSCS Tones in


Batches
Prerequisites

Context

Before the operation, it is required to confirm:

The tone scripts are loaded.

The MML Terminal window is opened.

Perform this procedure to create the tone-related data on the


MSCS side in batches, including service tone ID, the conversion
of service key to service tone ID, and other tone packet configuration.
All the tone packet configurations are created in batches, except
interconnection conversion of external service keys that is configured manually with the ADD SVRTRANSKEY command.

Note:
Since there are many data to be processed, this process will last
for a while. And an alert dialog box pops up. It prompts that
the operation is in process. Do not terminate it to avoid the data
confusion. This dialog box will automatically disappear when the
creation is completed.
Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create MSCS tones in batches.
STONE.

The command is BADD

Table 31 describes main parameters in the BADD STONE command.

82

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

TABLE 31 PARAMETERS IN THE BADD STONE COMMAND


Parameter
Name

Parameter Description

Instructions

Voice type, includes

ALL: all configuration of


tone

ICP: tone service

KD: the relationship


between the call type
and the KD

LANGDES: language
description string

MSGID: external MSGID,


relation to inter service
key

TONEID: tone ID

TONEIN: service key and


its relation to tone ID

TONEPLAYMT: tone
playing method

TYPE

In general, the ALL


option is selected,
indicating that all
the tone types are
created in batches.

Example: Create the batch processing of all the MSCS tones.


The specific command is as follows.
BADD STONE:TYPE=ALL;
END OF STEPS

Office Information
Configuration
Overview
Table 32 shows the office information configuration flow.

Confidential and Proprietary Information of ZTE CORPORATION

83

ZXWN MSCS Data Configuration Guide(MSCS)

TABLE 32 OFFICE INFORMATION CONFIGURATION


Steps

Operations

Instructions

Command

Creating local
signaling point

The local SPC


configuration
includes 14-bit
SPC configuration,
24-bit SPC
configuration and
the upper-layer
user configuration
of MTP3.

ADD OPC

Creating the local


office configuration

Configure some
parameters of the
local exchange,
including the
exchange type,
signaling point
type, MTP3 test
code, and other
parameters.

ADD LOFC

Creating mobile
data of local office

Configure the
Country Code
(CC), Mobile
Country Code
(MCC), Mobile
Network Code
(MNC), National
Destination Code
(NDC), and
supported types

ADD MSCCFG

Creating the
Country Code

Create the country


code of the
country where
the equipment is
located.

ADD CC

Creating Other
MNC of Local Office

When a carrier
has several MNCs,
other MNCs are
created for judging
the inter-network
roaming.

ADD MNC

Creating a Local Signaling Point


Prerequisites

Context

84

Before the operation, it is required to confirm:

You know the ID of the exchange to be configured.

You know the 14-bit SPC, 24-bit SPC, and the local toll area
code.

The MML Terminal window is opened.

Signaling Point Code (SPC) is a unique code for identifying each


node in the signaling network. The local SPC configuration includes
14-bit SPC configuration, 24-bit SPC configuration and the upper-

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

layer user configuration of MTP3. If the multi-SPC networking is


adopted, it is required creating multiple local signaling points with
different network types.
Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the local signaling point. The command is ADD OPC.
Table 33 describes the main parameters in the ADD OPC command.
TABLE 33 PARAMETERS IN THE ADD OPC COMMAND
Parameter
Name

Parameter Description

Instruction

NET

The signaling network


where the local office
runs, which has the
same signaling network
type of the adjacent
office configured later.

It is a mandatory
parameter. It ranges
from 1 to 255. In
general, 1 is selected.

NAME

User-defined alias

It is a mandatory
parameter, with a length
ranging from 1 to 50
characters.

SPCFMT

Signaling point code


format

It is an optional
parameter. By default,
select TRIPLE_DEC,
which is a three-section
decimal number in
888/383 format.

OPC14

14-bit SPC of local office,


which is provided by the
operator

OPC24

APPTYPE

24-bit SPC of local office,


which is provided by the
operator

Protocols supported by
local office

It is configured
according to the
signaling point planning.

Select the application


types of this signaling
point, not unrelated
subscribers. According
to different network
types, Select H248 user,
BICC user, TUP user,
ISUP user, and SCCP
user for Mc interface,
SCCP user for the
signaling point to the
BSC, and SCCP user
and ALCAP user for the
signaling point to the
RNC.

Confidential and Proprietary Information of ZTE CORPORATION

85

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter Description

Instruction

RC

The toll zone code of the


place where the local
office is located

It is an optional
parameter. Do not
add 0 ahead of an area
code

PREFIX

Dialing prefix

Toll dialing prefix. It is 0


for China.

Network appearance
used in M3UA layer

This field is not used


when the local office
is interconnected with
a TDM office. It is
configured as 0. When
this signaling point is
interconnected with
an IP signaling point
with the same network
type, you need to
negotiate this field with
the opposite end for
consistency.

NETAPP

INFO

TAG

Identification field used


to configure whether the
network appearance is
effective. Three modes
can be chosen, including

NOUSE

NETAPP

NONETAPP

Other attributes

When NOUSE is chosen,


if the NETAPP field is 0,
the network appearance
is ineffective; if the
NETAPP field is not 0,
the network appearance
is effective.
When NETAPP is
chosen, the network
appearance is effective.
When NONETAPP
is chosen, the
network appearance
is ineffective.
Configure whether the
network corresponding
to the office has the ISNI
function and translation
node.

Example: Create a 24-bit signaling point with the following


requirements.

Direct-associated office: MSCS

Signaling point type: 24-bit signaling point

SPC: 3.11.1

Application type: ISUP, SCCP, BICC, and TUP

Alias: NET1

Other parameters: default

The specific command is as follows.


ADD OPC:NET=1,NAME="NET1",RC="25",SPCFMT=TRIPL
E_DEC,OPC24="3.11.1",APPTYPE="BICC"&"ISUP"&"SCCP

86

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

"&"TUP",PREFIX="0",NETAPP=0,INFO=NONETAPP,DMIDX
=0;
Example: Create a 14-bit signaling point that is interconnected
with a radio office through MGW with the following requirements.

SPC: 1.11.1

Application type: SCCP

Alias: NET2

Other parameters: default

The specific command is as follows.


ADD OPC:NET=2,NAME="NET2",RC="25",SPCFMT=TRIPLE
_DEC,OPC14="1.11.1",APPTYPE="SCCP",PREFIX="0",NET
APP=0,INFO=NONETAPP,DMIDX=0;
Example: Create a 14-bit signaling point that is interconnected
with MGW through Mc interface with the following requirements.

SPC: 1.11.2

Application type: H.248

Alias: NET3

Other parameters: default.

The specific command is as follows.


ADD OPC:NET=3,NAME="NET3",RC="25",SPCFMT=TRIPLE
_DEC,OPC14="1.11.2",APPTYPE="H.248",PREFIX="0",NE
TAPP=0,INFO=NONETAPP,DMIDX=0;
END OF STEPS

Creating the Local Exchange


Prerequisites

Before the operation, it is required to confirm:

The local signaling point is created.

You know the ID of the exchange to be configured.

The MML Terminal window is opened.

Context

Perform this procedure to create some parameters of the local exchange, including the exchange type, signaling point type, MTP3
test code, and other parameters.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the basic attributes of the local office. The command is
ADD LOFC.

Confidential and Proprietary Information of ZTE CORPORATION

87

ZXWN MSCS Data Configuration Guide(MSCS)

Table 34 describes the parameters in the ADD LOFC command.


TABLE 34 PARAMETERS IN THE ADD LOFC COMMAND
Parameter
Name

Parameter Description

Instruction

Local office type,


including

OFFTYPE

LOCAL (Local
Exchange)

DOMTOLL (National
Toll Exchange)

INTTOLL
(International Toll
Exchange)

OA (In One Area)

UM (User
Telephone)

R2NAT (R2 National


Exchange)

R2INT (R2
International
Exchange)

MGCF (MGCF
Exchange)

It is a mandatory
parameter. Several
options can be selected.
Configure this parameter
according to actual type.
In general, select Local
Exchange and National
Toll Exchange for an
MSCS end office.

NET

Network type

It is a mandatory
parameter for
designating the network
type ID of the local office.
In this case, one network
type is configured.

SEQ

Sequence in area

It is a mandatory
parameter with a default
of 0, ranging from 0 to
255.

Test code

It is an optional
character-type
parameter with a
length not more than
15 characters. This
parameter can contain
0~9, *, and #, with a
default of 1234

TCODE

88

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

Parameter
Name

Parameter Description

Instruction
It is an optional
parameter.

SPTYPE

RESTART

Signaling point type,


including SEP, STP, and
STEP

Signaling point restart

If this office serves


as a signaling
transfer point, select
STP

If this office only


serves as an end
office, select SEP

If this office serves


as an end office and
signaling transfer
point, select STEP

It is an optional
parameter, with a default
of YES. The default
value indicates that this
function is enabled

Languages of the office,


including:

LANG

RSTTIME

NAME

DEFAULT

FRENCH

ENGLISH

GERMAN

RUSSIAN

SPAISH

The default value is


DEFAULT.

Reset Time(ms)

The restart time when


the signaling point used
as STP (the unit is
ms). It is an integral
parameter, ranging from
100 to 59900, the default
value is 10000.

Alias

Not more than 50


characters. It is the
name customized by a
user for easy memory.

Example: Create the local exchange with the following requirements.

Office type: LOCAL&DOMTOLL

Network type No.: 1

Signaling point type: SEP

Other parameters: Default.

The command is as follows:

Confidential and Proprietary Information of ZTE CORPORATION

89

ZXWN MSCS Data Configuration Guide(MSCS)

ADD
LOFC:OFCTYPE="LOCAL"&"DOMTOLL",NET=1,SEQ
=0,TCODE="1234",SPTYPE=SEP,LANG=DEFAULT,RESTAR
T=YES,RSTTIME=10000,T19=68,T20=60,T21=64;
END OF STEPS

Creating Mobile Data of Local Office


Prerequisites

Before the operation, it is required to confirm:

The number of exchange to be configured is known.

The MML Terminal window is opened.

Context

By default, some data are created in the OMM system, including


Country Code (CC), Mobile Country Code (MCC), Mobile Network
Code (MNC), National Destination Code (NDC), and supported
types. Modify the mobile data of local exchange as required.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create local office mobile data as required. The command is
ADD MSCCFG.
Table 35 describes the main parameters in the ADD MSCCFG
command.
TABLE 35 PARAMETERS IN THE ADD MSCCFG COMMAND
Parameter
Name

Parameter
Description

Instruction

MSC number

It is a mandatory parameter,
with a length ranging from 1 to
16 digits. MSC GT number is
uniformly planned by the carrier
for distinguishing different MSCs

VLR

VLR number

It is a mandatory parameter,
with a length ranging from 0 to
16 digits. VLR GT number is
uniformly planned by the carrier
for distinguishing different VLRs

CC

Country Code
(CC)

It is an optional parameter, with


a length ranging from 0 to 4
digits. Type it according to the
actual conditions. The country
code of China is 86

NDC

National
destination code

It is an optional parameter, with


a length ranging from 0 to 4
digits. Type it according to the
actual conditions.

MSC

90

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

Parameter
Name

Parameter
Description

Instruction

MCC

Mobile country
code

It is an optional parameter, with


a length ranging from 0 to 3
digits. Type it according to the
actual conditions. The country
code of China is 460.

MNC

Mobile network
code

It is an optional parameter, with


a length ranging from 0 to 3
digits. Type it according to the
actual conditions.

OFCTYPE

Local exchange
type

It is an optional parameter,
including NONE (select none),
LV1 (first connection center),
LV2 (second connection center),
and EO (mobile peer office).
Select it according to the actual
conditions

SNLEN

Mobile subscriber
number length

It is an optional parameter. Type


an integer ranging from 3 to 4,
with a default of 3

PREINT

International toll
prefix

It is an optional parameter, with


a length ranging from 0 to 4
digits, with a default of 00

PRENAT

National toll
prefix

It is an optional parameter, with


a length ranging from 0 to 4
digits, with a default of 0

RC

Area code

It is an optional parameter. Do
not add 0 ahead of an area code

TAG

Miscellaneous
tag

It is an optional parameter.

NSYIND

NAS
synchronization
indicator

It is an optional parameter. It
ranges from 0 to 255, with a
default of 255 (0xff indicates
invalidity)

SOURCE

Data source
statistics
descriptor,
including
options:
SPEECH and
UNKNOWN

It is an optional parameter, with


a default of SPEECH

RNCRESET

Times of RNC
reset

It is an optional parameter. The


parameter are integers ranging
from 1 to 10, with a default of 3

SUPCAPA

Capabilities Of
local office

It is an optional parameter,
indicating the supplemental
functions supported by the
exchange. Options include
NONE and IP

Confidential and Proprietary Information of ZTE CORPORATION

91

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction

IPCONNMODE

IP connection
mode, including
options: IP and
SSP

It is an optional parameter,
indicating the connection mode
between the local MSCS and
SCP when the IP playback is
conducted

IPDLGVER

CAMEL version
between IP and
SCP, including
options:
CAMEL2 ,
CAMEL3 and
CAMEL4

It is an optional parameter.
Generally, it is configured as 3

SELFCIC

Local CIC (carrier


identification
code)

It is an optional parameter. It
ranges from 0 to 6, with a default
of 0

DEFCIC

Default CIC
(carrier
identification
code)

It is an optional parameter. It
ranges from 0 to 6, with a default
of 0

Binding carrier
PLMN

It is an optional parameter.
When the subscriber location
update succeeds, MSCS notifies
the PLMN number (a peer of MS)
through Equivalent PLMNs of the
LOCATION UPDATING ACCEPT
message. PLMNLIST can have
up to five groups of Equivalent
PLMNs.

OPERATOR

Carrier of local
office

It is an optional parameter. The


carrier of local office does not
need to be configured in the
background system, and it is
generated according to MCC and
MNC during the transmission.

CODETYPE

Default codec
type of local
office

It is an optional parameter,
including options: G711A64
(ITUT_G711A_64) and
G711U64 (ITUT_G711U_64)

SUPPCALLEDPBRT

PRBT support
mode of called
use

It is an optional parameter. The


parameter indicates whether the
exchange supports personalized
ring back tone (PRBT) and the
mode of the support. Options
include NO, CALLER1 and
CALLER2.

SUPPCALLINGPBRT

PRBT support
mode of calling
use, including
options: NO and
YES

It is an optional parameter, with


a default of NO

PLMNLIST

92

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

Parameter
Name

Parameter
Description

Instruction

PBRTPFX

Voice service
PRBT prefix

It is an optional parameter,
indicating the calling prefix of the
PRBT defined by operator and
mainly used for connection with
the PRBT center.

PLAYCWTONE

Whether to play
the warning tone
during the call
waiting, including
options: NO and
YES

It is an optional parameter, with


a default of NO

IPPFX

IP pre-embeded
prefix

It is an optional parameter

OMCPRIOR

Traffic control
static data
priority, including
options: NO and
YES

It is an optional parameter, with


a default of NO

LOADTYPE

Overload
route-selection
mode, including
options: INLV
and NEXTLV

It is an optional parameter, with


a default of NEXTLV

MISSCALL

MissCall short
message center

It is an optional parameter,
indicating the number of MissCall
short message center. It is made
up of numeric characters with
0~16 digits

IGWPSPSID

Special PSID
for packet
service(IGW)

It is an optional parameter. It is
made up of numeric characters
with 0~16 digits

RCSKEY

Remote Control
Key(IGW)

It is an optional parameter. It
ranges from 0 to 255, with a
default of 255

RCMINLEN

Minimum length
of code(IGW)

It is an optional parameter. It
ranges from 1 to 32, with a
default of 1

RCMAXLEN

Maximum length
of code(IGW)

It ranges from 1 to 32, with a


default of 20

RCTAG

Whether need to
press '#' to end,
including option
NO and YES

It is an optional parameter, with


a default of NO

CNID

CNID

It is an optional parameter. It
ranges from 0 to 4095, with a
default of 0

LICOFCID

Monitor Center
Office

It is an optional parameter. It
ranges from 0 to 3000, with a
default of 0

Confidential and Proprietary Information of ZTE CORPORATION

93

ZXWN MSCS Data Configuration Guide(MSCS)

94

Parameter
Name

Parameter
Description

Instruction

NAME

Alias

It is an optional parameter, which


is used to describe the local
mobile date of MSCS for easy
recognition

OSBDAS

OSB analysis
selector

It is an optional parameter,
indicating the calling prefix of
the multimedia PRBT defined by
operator and mainly used for
connection with the multimedia
PRBT center. It is made up of
numeric characters with 0~2000
digits

ROAMPLC

Roaming
Restriction
policy based
on subscriber
ID, including
options: NO,
MSISDN and
IMSI

It is an optional parameter, with


a default of NO

USSDPLC

USSD center
routing mode,
including options: MSISDN_USSDC and
IMSI_USSDC

It is an optional parameter, with


a default of MSISDN_USSDC

IFDFTZC

Enabled default
ZoneCode,
including
options:
DISABLE and
ENABLE

It is an optional parameter, with


a default of DISABLE

DFTZC

Default
ZoneCode

It is an optional parameter. It is
made up of characters with 0~4
digits, with a default of FFFF

RDIPREFIX

RDI prefix

It is an optional parameter. It is
made up of characters with 0~16
digits

USRTYPEJUDGE

Judgement
of user type,
including
options:
NUMBER and
ROAMTYPE

It is an optional parameter, with


a default of NUMBER

RELCALLNUM

Rate of
TUP/ISUP/BICC
releasing
successful call
relevant to
unaccessible
DPC(call number
per sec.)

The parameter is used


to configure the rate of
TUP/ISUP/BICC releasing
successful call relevant to
unaccessible DPC, and it is only
effective for the inter-office
signaling of TUP/ ISUP/BICC. It
is 0 or within a range of 40~500.
The default is 0 (not enable
the function). For values that

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

Parameter
Name

Parameter
Description

Instruction
are not 0, if the office direction
recovery is not considered
(the call of the office direction
is immediately released after
the office direction signaling is
recovered), the smaller the value
is, the slower the release speed
is. Thus the subscriber gets a
better experience, but the time
difference in the calling record
and called record becomes larger.
For the end office, one is advised
to set the value as 100, and the
value of the end office should
not exceed 200; For the tandem
office, the default is 310

Example: Configure the mobile data of local exchange with the


following requirements.

MSC number: 8613903023

VLR number: 8613903023

Country code: 86

Mobile country code: 460

Mobile network code: 00

Local office type: Mobile peer office

Miscellaneous tag: "SMS MT"&"SMS MO"&"LOCCIC_NOO


UT"
Other parameters: default.

The specific command is as follows.


ADD
MSCCFG:MSC="8613903023",VLR="8613903023",C
C="86",NDC="139",MCC="460",MNC="00",OFCTYPE="EO
",SNLEN=3,PREINT="00",RC="25",TAG="SMS MT"&"SMS
MO"&"LOCCIC_NOOUT",NSYIND=255,SOURCE=SPEECH,R
NCRESET=3,SUPCAPA="NONE",SELFCIC="0",DEFCIC="0
",DEFNAEA=65535,CODETYPE=G711A64,SUPPCALLEDPB
RT=NO,SUPPCALLINGPBRT=NO,PLAYCWTONE=NO,OMC
PRIOR=NO,LOADTYPE=NEXTLV,RCSKEY=255,RCMINLEN
=1,RCMAXLEN=20,RCTAG=NO,CNID=0,LICOFCID=0,OS
BDAS=0,ROAMPLC=NO,USSDPLC=MSISDN_USSDC,IFDFT
ZC=DISABLE,DFTZC="FFFF",USRTYPEJUDGE=NUMBER,RE
LCALLNUM=0,BICCCS=OFF,FAXDELAY=5,IGNLANOTALL
OW=NO,CRD=NO,CMPBSCCODEC=FALSE;
END OF STEPS

Creating the Country Code


Prerequisites

Before the operation, it is required to confirm:

Confidential and Proprietary Information of ZTE CORPORATION

95

ZXWN MSCS Data Configuration Guide(MSCS)

You know the ID of the exchange to be configured.

You know the country code.

The MML Terminal window is opened.

Context

Perform this procedure to create the country code of the country


where the equipment is located.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the country code. The command is ADD CC.
Table 36 describes the main parameters in the ADD CC command.
TABLE 36 PARAMETERS IN THE ADD CC COMMAND
Parameter
Name

Parameter
Description

Instruction

CC

Country code

It is a mandatory parameter. Type


it according to actual conditions.
The country code of China is 86

NAME

Alias

It is an optional parameter, with


a length ranging from 1 to 50
characters.

Example: Create the country code of China is 86 with an alias


as China. The specific command is as follows.
ADD CC:CC="86",NAME="China";
END OF STEPS

Creating other MNC of Local Office


Prerequisites

Before the operation, it is required to confirm:

You know the ID of the exchange to be configured.

You know other MNCs.

The MML Terminal window is opened.

Context

When a carrier has several MNCs, other MNCs are created for judging the inter-network roaming.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.

96

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

SET:NEID=11;
2. Create other MNCs. The command is ADD MNC.
Table 37 describes the main parameters in the ADD MNC command.
TABLE 37 PARAMETERS IN THE ADD MNC COMMAND
Parameter
Name

Parameter
Description

Instruction

MNC

Mobile network
code

It is a mandatory parameter,
with a length ranging from 2 to 3
digits. Type it according to actual
conditions

NAME

Alias

It is an optional parameter, with


a length ranging from 1 to 50
characters

Example: Create the MNC 02 for a carrier. The specific command is as follows.
ADD MNC:MNC="02",NAME="46002";
END OF STEPS

VLR Configuration
Overview
Table 38 shows the VLR configuration flow.
TABLE 38 VLR CONFIGURATION FLOW
Steps

Operations

Instructions

Command

Creating VLR
system parameters

Create the VLR


system parameters
of local office

ADD VLRSYS

Creating VLR
system capacity

Create the capacity


of each VLR table

ADD VLRCAP

Creating VLRsupported services

Create the service


type supported by
the VLR on local
office

ADD VLRSRV

Creating roaming
number prefix

Creating roaming
number prefix

ADD MRNPFX

Confidential and Proprietary Information of ZTE CORPORATION

97

ZXWN MSCS Data Configuration Guide(MSCS)

Steps

Operations

Instructions

Command

Creating MSRN
load sharing

A VLR module can


be configured with
an MSRN number
section during
the MSRN load
configuration.

ADD MRNSH

Creating VLR System Parameters


Prerequisites

Before the operation, it is required to confirm:

You know the ID of the exchange to be configured.

The MML Terminal window is opened.

Context

Perform this procedure to create the VLR system parameters of


local office, including extended type of Mobile Station Roaming
Number (MSRN), allocation policies, and dynamic bit length.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the VLR system parameters. The command is ADD
VLRSYS.
Table 39 describes the main parameters in the ADD VLRSYS
command.
TABLE 39 PARAMETERS IN THE ADD VLRSYS COMMAND
Parameter
Name

98

Parameter
Description

Instruction

MRNEXTYPE

MSRN
extended type

It is an optional parameter, with


a default of EXDYNA, when
EXMSRN is selected, several
roaming number prefixes can
be configured, which is usually
adopted in the case of large area
system or dual-homing system.
When EXDYNA is selected, only
one roaming number prefix can
be configured.

MRNALCTYPE

MSRN
allocation
policy

It is an optional parameter,
with a default of IGN2G3G
(Not distinguish 3G or 2G).
Select it according to the actual
conditions

MRNDYNDIGIT

Dynamic
allocation bit
(2~6)

It is an optional parameter,
ranging from 2 to 6, with a
default of 3. It is determined by
the roaming number section.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

Parameter
Name

Parameter
Description

Instruction

MSTMLMT

Time limit
for deleting
inactive user
(hour)

It is an optional parameter,
ranging from 0 to 255, with a
default of 24

MRNTMLMT

Time limit
for deleting
roaming data
(second)

It is an optional parameter,
ranging from 1 to 255, with a
default of 90

MHNTMLMT

Time limit
for deleting
handover
(second)

It is an optional parameter,
ranging from 1 to 255, with a
default of 90

LUTM

Periodic
location
update time
(minute)

It is an optional parameter,
ranging from 6 to 15300, with a
default of 30

LUPROTECTTM

Location
update
protection
time (minute)

It is an optional parameter,
ranging from 1 to 255, with a
default of 15

MAXFWD

Maximum
times of
forwarding

It is an optional parameter,
ranging from 1 to 255, with a
default of 1

PAGENRCNT

Times of
DETACH when
PAGE no
response

It is an optional parameter,
ranging from 1 to 255, with a
default of 3

PAGENRTM

Interval after
PAGE no
response

It is an optional parameter,
ranging from 1 to 255, with a
default of 2

BUSYLMT

User busy limit


(minute)

It is an optional parameter,
ranging from 1 to 255, with a
default of 5

IDREQ

Send ID
Request When
Inter MSC LU

It is an optional parameter.
Select the option as the case
may be

LOCTMSI

TMSI
Indicates Local
MSCSERVER

It is an optional parameter.
Select the option as the case
may be

OPCNTPA

Calling times
within one PA

It is an optional parameter,
ranging from 0 to 2147483647,
with a default of 0

TMLMTPA

Time limit
within one PA
(h)

It is an optional parameter,
ranging from 0 to 65534, with a
default of 0

MRNINTERRG

Support
MSRN over
multi-region

It is an optional parameter,
ranging from 0 to 1, with a
default of 0

Confidential and Proprietary Information of ZTE CORPORATION

99

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction

CMRNMODULE

Module
managing
common
MSRN

It is an optional parameter,
ranging from 0 to 127, with a
default of 0

RETMSITIME

Restore TMSIallocation
time after MP
restart (m)

It is an optional parameter,
ranging from 5 to 120, with a
default of 30

Example: Create the VLR system parameters with the following


requirements.

MSRN extended type: EXMSRN


MSRN allocation policy: IGN2G3G (Not distinguish 3G or
2G)
Dynamic allocation bit: 3
Other parameters: adopt the default value first, and then
modify them according to the service requirements later.

The specific command is as follows.


ADD
VLRSYS:MRNEXTYPE=EXMSRN,MRNALCTYPE=IG
N2G3G,MRNDYNDIGIT=3,MSTMLMT=24,MRNTMLMT=9
0,MHNTMLMT=90,LUTM=30,LUPROTECTTM=15,MAXFW
D=1,PAGENRCNT=3,PAGENRTM=2,BUSYLMT=5,IDREQ
=YES,LOCTMSI=ALWAYS0,OPCNTPA=0,TMLMTPA=0,MRN
INTERRG=NO,CMRNMODULE=0,RETMSITIME=30;
END OF STEPS

Creating VLR System Capacity


Prerequisites

Before the operation, it is required to confirm:

You know the ID of the exchange to be configured.

The MML Terminal window is opened.

Context

Perform this procedure to create the capacity of each VLR table,


which is planned according to the subscriber capacity supported
by hardware configuration.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the VLR system parameters. The command is ADD
VLRCAP.

100

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

Table 40 describes the main parameters in the ADD VLRCAP


command.
TABLE 40 PARAMETERS IN THE ADD VLRCAP COMMAND
Parameter Name

Parameter
Description

Instruction

TRATAB

Subscriber
tracing table

The parameter is used to set


the maximum capacity of the
subscriber tracing table. It ranges
from 50 to 100, with a default of
50

IMEITAB

IMEI tracing
table

The parameter is used to set the


maximum capacity of the IMEI
tracing table. It ranges from 50 to
100, with a default of 50

MRNTAB

Roaming
number table

The parameter is used to set the


maximum capacity of the roaming
number table. It ranges from 900
to 20000, with a default of 900.
The field value is limited by the
dynamic allocation bit length of
MRNDYNDIGIT roaming number in
the VLR system. If the dynamic
allocation bit length is 3, the
parameter ranges from 0 to 999.

MHNTAB

Handover
number table

The parameter is used to set the


maximum capacity of the handover
number table. It ranges from 100
to 1000, with a default of 100.

Percent of
interlock CUG
table (%)

The parameter is used to set the


maximum interlock CUG table
supported by the single module.
It is a percentage based on the
MSTAB user data table. It ranges
from 0 to 1000, with a default of
50

Percent of BSG
CUG table (%)

The parameter is used to set


the maximum BSG CUG table
supported by the single module.
It is a percentage based on the
MSTAB user data table. It is a
percentage based on the MSTAB
user data table. It ranges from 0
to 800, with a default of 50

Percent of zone
code table (%)

The parameter is used to set


the maximum zone code table
supported by the single module.
It is a percentage based on the
MSTAB user data table. It is a
percentage based on the MSTAB
user data table. It ranges from 0
to 100, with a default of 50

ICUGPER

BCUGPER

ZCPER

Confidential and Proprietary Information of ZTE CORPORATION

101

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter Name

Parameter
Description

Instruction

Percent of
CAMEL MO info
table (%)

The parameter is used to set the


maximum CAMEL MO info table
supported by the single module.
It is a percentage based on the
MSTAB user data table. It ranges
from 0 to 200, with a default of
120

Percent of
CAMEL SS info
table (%)

The parameter is used to set the


maximum CAMEL SS info table
supported by the single module.
It is a percentage based on the
MSTAB user data table. It ranges
from 1 to 100, with a default of
100

TCSIPER

Percent of
CAMEL MT info
table (%)

The parameter is used to set the


maximum CAMEL MT info table
supported by the single module.
It is a percentage based on the
MSTAB user data table. It ranges
from 0 to 300, with a default of
100

DCSIPER

Percent of
CAMEL dial
service info
table (%)

The parameter is used to set the


maximum CAMEL dial service
info table supported by the single
module. It is a percentage based
on the MSTAB user data table.
It ranges from 0 to 1000, with a
default of 100

MCSIPER

Percent of
CAMEL MM info
table (%)

It is a percentage based on the


MSTAB user data table. It ranges
from 0 to 100, with a default of
100

SMSCSIPER

Percent of
CAMEL SMS
info table (%)

It is a percentage based on the


MSTAB user data table. It ranges
from 0 to 100, with a default of
100

LCSPER

Percent of LCS
user info table
(%)

It is a percentage based on the


MSTAB user data table. It is an
optional parameter, ranging from 0
to 100, with a default of 20

BSGPER

Percent of basic
service group
table (%)

It is a percentage based on the


MSTAB user data table. It ranges
from 0 to 800, with a default of
400

FSAPER

Percent of
forwarding
address (%)

It is a percentage based on the


MSTAB user data table. It ranges
from 0 to 800, with a default of 50

ACCESSCD

Percent of
ACCESSCODE
Table(%)

It is an optional integral parameter.


It ranges from 0 to 200, with a
default of 0

OCSIPER

SSCSIPER

102

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

Parameter Name

Parameter
Description

Instruction

ALS

ALS table

It is an optional integral parameter.


It ranges from 0 to 512, with a
default of 0

IGWMSTAB

R_IGWMS table
capacity

It ranges from 0 to 99999, with a


default of 1000. If IGW attribute is
not supported, set this parameter
to 0

IGWTRATAB

R_IGWTRA
table capacity

It ranges from 0 to 99999, with a


default of 1000. If IGW attribute is
not supported, set this parameter
to 0

IGWZCTAB

R_IGWZNCD
table capacity

It ranges from 0 to 99999, with a


default of 1000. If IGW attribute is
not supported, set this parameter
to 0

IGWOCSI
TAB

R_IGWOCS
table capacity

It ranges from 0 to 99999, with a


default of 1000. If IGW attribute is
not supported, set this parameter
to 0

IGWTCSI
TAB

R_IGWTCSI
table capacity

It ranges from 0 to 99999, with a


default of 1000. If IGW attribute is
not supported, set this parameter
to 0

IGWCUG
TAB

R_IGWCUG
table capacity

It ranges from 0 to 99999, with a


default of 1000. If IGW attribute is
not supported, set this parameter
to 0

IGWSPCD
TAB

R_IGWSPCD
table capacity

It ranges from 0 to 99999, with a


default of 1000. If IGW attribute is
not supported, set this parameter
to 0

IGWABBR
TAB

R_IGWABBR
table capacity

It ranges from 0 to 99999, with a


default of 1000. If IGW attribute is
not supported, set this parameter
to 0

IGWMRN
TAB

R_IGWMSRN
table capacity

It ranges from 0 to 99999, with a


default of 1000. If IGW attribute is
not supported, set this parameter
to 0

USERBAK

MSC Pool
standby user
data capacity
(ten thousand)

It is optional integral parameter.


It ranges from 0 to 160, with a
default of 0

Example: VLR system capacity adopts its default configuration.


The specific command is as follows.
ADD VLRCAP:TRATAB=50,IMEITAB=50,MRNTAB=900,M
HNTAB=100,ICUGPER=50,BCUGPER=50,ZCPER=50,OCSI
PER=120,SSCSIPER=100,TCSIPER=100,DCSIPER=100,M
CSIPER=100,SMSCSIPER=100,LCSPER=20,BSGPER=40

Confidential and Proprietary Information of ZTE CORPORATION

103

ZXWN MSCS Data Configuration Guide(MSCS)

0,FSAPER=50,ACCESSCD=0,ALS=0,IGWMSTAB=1000,IG
WTRATAB=1000,IGWZCTAB=1000,IGWOCSITAB=1000,I
GWTCSITAB=1000,IGWCUGTAB=1000,IGWSPCDTAB=1
000,IGWABBRTAB=1000,IGWMRNTAB=1000,USERBAK
=0;
END OF STEPS
Postrequisite

After the table capacity proportion is adjusted, OMP/SMP/CMP


must be reset. In this way, the table capacity can be set up again
according to the configuration requirements.

Creating VLR-supported Services


Prerequisites

Before the operation, it is required to confirm:

You know the ID of the exchange to be configured.

The MML Terminal window is opened.

Context

Perform this procedure to create the service type supported by the


VLR on local office

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the VLR-supported services.
VLRSRV.

The command is ADD

Table 41 describes the main parameters in the ADD VLRSRV


command.
TABLE 41 PARAMETERS IN THE ADD VLRSRV COMMAND
Parameter
Name

Parameter Description

Instruction

ODB service, including

ALL_CALLOUT
(barring of all
outgoing calls)

INT_CALLOUT
(barring of
all outgoing
international calls)

ODB

104

EXP_PLMN_CALLOUT (barring of
all outgoing international calls except
those directed to the
home PLMN country)

HRATE_INFO
(barring of outgoing

Confidential and Proprietary Information of ZTE CORPORATION

It is an optional
parameter, with a default
of ALL

Chapter 3 Local Office Data Configuration

Parameter
Name

Parameter Description
call of premium
rate information
services)

HRATE_ENT(
High-Rate
Entertainment
Restrictions)

SPP_SRV (barring
of supplementary
services)

ALL (selecting all)

NONE (None)

Instruction

Including

OTHER

ACAUTH (Area
Code Unauthorized)

AOCI (Charging Tip


(Message))

AOCC (Charging
Tip(Fee))

CUG (Close User


Group)

ZONESUBS (Zone
Subscription)

EMLPP (Enhanced
Multi-Level Priority
Service)

OR (Support
Optimal Routing)

NAEA (Support
Equal Access)

ALL (All)

NONE (None)

It is an optional
parameter, with a default
of ALL

Telecom services,
including

TELE (telephone
service)

EMER_CALL
(emergency call)

TSMS_MTPP
(terminating short
message)

OSMS_MOPP
(originating short
message)

FAC3 (category-3
fax service)

AFAC3 (automatic
category-3 fax)

TELESRV

It is an optional
parameter, with a default
of ALL

Confidential and Proprietary Information of ZTE CORPORATION

105

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter Description

FAC4 (category-4
fax service)

VOCG (voice group


call)

VOCB (voice
broadcast)

ALL (selecting all)

NONE (None)

Instruction

Specify telecom
services, including
SPECTS

TS1~TSF (specified
telecom services)

ALL (selecting all)

NONE (None)

It is an optional
parameter, with a default
of ALL

Bearer service CDA,


including

CDA

CDA300

CDA1200

CDA1200_75

CDA2400

CDA4800

CDA9600

ALL

NONE (None)

It is an optional
parameter, with a default
of ALL

Bearer service CDS,


including

CDS

CDS1200

CDS2400

CDS4800

CDS9600

ALL

NONE (None)

It is an optional
parameter, with a default
of ALL

Bearer service PAD,


including

PAD

106

PAD300

PAD1200

PAD1200_75

PAD2400

PAD4800

PAD9600

ALL

Confidential and Proprietary Information of ZTE CORPORATION

It is an optional
parameter, with a default
of ALL

Chapter 3 Local Office Data Configuration

Parameter
Name

Parameter Description

Instruction

NONE (None)

Bearer service PDS,


including

PDS

PDS2400

PDS4800

PDS9600

ALL

NONE (None)

It is an optional
parameter, with a default
of ALL

Bearer service voice,


including
SPEECH

SPECBS

BS1 ~ BSF

ALL

NONE (None)

Specify bearer service

It is an optional
parameter, with a default
of ALL

It is an optional
parameter, with a default
of ALL

Customized Extended
Service, including

ALS: ALS service

ASCAMEL:
switching
intelligentized
service

CUST

It is an optional
parameter

VIRMSRNPBRT:
virtual roaming
number for PBRT
service

Example: Create the VLR support services. The specific command is as follows.
ADD
VLRSRV:ODB="ALL",OTHER="ALL",TELESRV="ALL
",SPECTS="ALL",CDA="ALL",CDS="ALL",PAD="ALL",PDS
="ALL",SPEECH="ALL",SPECBS="ALL",CCBS=NONE;
END OF STEPS

Creating Roaming Number Prefix


Prerequisites

Before the operation, it is required to confirm:

You know the ID of the exchange to be configured.

The mobile data of local office are configured.

The MML Terminal window is opened.

Confidential and Proprietary Information of ZTE CORPORATION

107

ZXWN MSCS Data Configuration Guide(MSCS)

Context

When a mobile subscriber is connected as a called party, VLR will


allocate a temporary roaming number to this subscriber. Therefore, creating a roaming number prefix is required. If the MRNEXTYPE parameter of VLR is configured as EXDYNA, only one roaming
number prefix can be created. A subscriber can be configured with
several roaming number prefix only when this parameter is configured as EXMSRN.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create a roaming number prefix. The command is ADD MRNP
FX.
MRNPFX represents the roaming number prefix. The length of
a prefix plus dynamic bits is not more than 15 bits. The roaming number prefix is planned in the whole network. It must
contain country code, and has no inclusion relation. For example, 861390302 contains 8613903023. Different exchange
can be distinguished through roaming number prefix
Example:
Configure the roaming number prefix
8613903023. The specific command is as follows.

as

ADD MRNPFX: MRNPFX ="8613903023";


END OF STEPS

Creating MSRN Load Sharing


Prerequisites

Before the operation, it is required to confirm:

You know the ID of the exchange to be configured.

The roaming prefix is created.

The MML Terminal window is opened.

Context

A VLR module can be configured with an MSRN number section


during the MSRN load configuration. It is also available to designate a service module allocated with an MSRN number section
as a common MSRN resource module by setting VLR system parameters. The MSRN number section of this module can provide
MSRN number to all the service modules when they have no MSRN
number.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the MSRN load sharing. The command is ADD MRNSH.

108

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

Table 42 describes the main parameters in the ADD MRNSH


command.
TABLE 42 PARAMETERS IN THE ADD MRNSH COMMAND
Parameter Name

Parameter
Description

Instruction

MSRN_Head

It is a mandatory parameter, ranging


from 1 to 13 numeric characters.
Type the roaming number prefix that
is configured.

MODULE

VLR module
number

It is a mandatory parameter. When


the roaming number type is 2G and
3G, select all CMP modules that are
configured with IMSI load sharing.
When the roaming number type is
HON (handover number), select
OMP modules.

NUMBEGIN

Start
granularity
value of an
MSRN section

NUMEND

End
granularity
value of an
MSRN section

MRNPFX

IDFLAG

Roaming
number type

It is a mandatory parameter. This


parameter is used to configure the
minimum and maximum value of
a roaming number and handover
number dynamic bit. A roaming
number ranges from 0 to 899, and
a hand number ranges from 900 to
999.
It is a mandatory parameter.
Select 2G (2G subscribers), 3G
(3G subscribers) ,HON (handover
number), IGW (IGW access) or
PBRTRNT (PBRT roaming number)
according to the actual conditions.

Example: Create the MSRN load sharing with the following requirements.

Roaming number prefix 8613903023

Roaming number type: 3G

MSRN start number: 0

MSRN end number: 899

Service module number: 5 and 6.

The specific command is as follows.


ADD MRNSH:MRNPFX="8613903023",MODULE="5"&"6",N
UMBEGIN=0,NUMEND=899,IDFLAG=3G;
Example: Create the MSRN load sharing with the following requirements.

Roaming number prefix 8613903023

Roaming number type: HON

MSRN start number: 900

MSRN end number: 999

Confidential and Proprietary Information of ZTE CORPORATION

109

ZXWN MSCS Data Configuration Guide(MSCS)

Service module number: 1.

The specific command is as follows.


ADD MRNSH:MRNPFX="8613903023",MODULE="1",NUM
BEGIN=900,NUMEND=999,IDFLAG=HON;
END OF STEPS

Virtual MSC Configuration


Overview
Table 43 shows the VMSC configuration flow.
TABLE 43 VIRTUAL MSC CONFIGURATION
Steps

Operations

Instructions

Command

Creating virtual
MSC

Virtual MSC
configuration is
required when
service areas are
divided.

ADD VMSC

Creating mapping
relationship
between MRSN
prefix and virtual
MSC

Create the mapping


relationship between
MSRN prefix and
virtual MSC when
service areas are
divided.

ADD REGION
MAP

Creating Virtual MSC


Prerequisites

Before the operation, it is required to confirm:

You know the ID of the exchange to be configured.

The MML Terminal window is opened.

Context

Virtual MSC configuration is required when service areas are divided.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create a virtual MSC. The command is ADD VMSC.

110

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

Table 44 describes the main parameters in the ADD VMSC


command.
TABLE 44 PARAMETERS IN THE ADD VMSC COMMAND
Parameter
Name

Parameter
Description

Instruction

VMSCIDX

Virtual MSC
index

It is a mandatory parameter,
corresponding to the area ID in
the resource management. It
ranges from 1 to 65535.

MSC

Virtual MSC
number

It is a mandatory parameter. The


MSC GT corresponded by this
virtual MSC, with a length ranging
from 1 to 16 digits.

VLR

Virtual VLR
number

It is a mandatory parameter,
indicating the MSC GT
corresponded by this virtual
MSC, with a length ranging from 1
to 16 digits.

AC

Area code

It is an optional parameter,
indicating the area code
corresponded by this virtual
MSC

NAME

Alias

It is a mandatory parameter.
It describes this MSC for easy
identification.

DMID

Working
domain index

It is an optional parameter. It
is the working domain ID of this
virtual MSC. Configure it as 0
when no working domain is added.

DASTPL

Template
of number
analysis
selector

It is an optional parameter.
It is the template of number
analysis selector of this virtual
MSC. Configure it as 0 when no
template is configured.

OSBDAS

Template of
OSB analysis
selector

It is an optional parameter. It
is the template of OSB analysis
selector of this virtual MSC.
Configure it as 0 when no
template is configured.

Example: Create a virtual MSC with the following requirements.

Virtual MSC index: 2511

MSC GT: 8613940100

VLR GT: 8613940100

Area code: 25

User alias: Nanjing

Other parameters: default.

The specific command is as follows.

Confidential and Proprietary Information of ZTE CORPORATION

111

ZXWN MSCS Data Configuration Guide(MSCS)

ADD VMSC:VMSCIDX=2511,MSC="8613940100",VLR="8
613940100",AC="25",NAME="nanjing",DMID=0,DASTPL
=0,OSBDAS=0;
END OF STEPS

Creating Mapping Relationship


between MRSN Prefix and Virtual
MSC
Prerequisites

Before the operation, it is required to confirm:

You know the ID of the exchange to be configured.

The virtual MSC is created.

Roaming number prefix is created.

The MML Terminal window is opened.

Context

Perform this procedure to create the mapping relationship between


MSRN prefix and virtual MSC when service areas are divided. This
is to designate the roaming number section (including handover
number) used by specified service area.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the mapping relationship between MSRN and virtual
MSC. The command is ADD REGIONMAP.
Table 45 describes the main parameters in the ADD REGION
MAP command.
TABLE 45 PARAMETERS IN THE ADD REGIONMAP COMMAND
Parameter
Name

Parameter
Description

Instructions

MRNPFX

Roaming
number prefix

It is a mandatory parameter. Type


the roaming number prefix that is
configured.

VMSCIDX

Virtual MSC
index

It is a mandatory parameter. Select


the virtual MSC index corresponding
to this roaming number prefix.

Alias

The parameter is used to detailedly


describe the relations between
roaming number prefix and virtual
MSC for identification.

NAME

112

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 3 Local Office Data Configuration

Example: Create the mapping relationship between the roaming number prefix 8613940100 and virtual MSC 2511. The
command is as follows.
ADD REGIONMAP:MRNPFX="8613940100",VMSCIDX=25
11;
END OF STEPS

Confidential and Proprietary Information of ZTE CORPORATION

113

ZXWN MSCS Data Configuration Guide(MSCS)

This page is intentionally blank.

114

Confidential and Proprietary Information of ZTE CORPORATION

Chapter

Resource Configuration
Table of Contents
Resource Planning ........................................................... 115
Configuring Resource Attributes......................................... 115

Resource Planning
It is very important to make the overall resource planning in advance no matter whether common networking, region-system networking, or dual-homing networking is adopted.
The basic principle of resource allocation is as follows:
1. Do not add unused resources in the resource management system.
For example, if it is not required to configure the SIP called
number analysis selector, do not configure the corresponding
resources.
2. Allocate the required resources on a basis of sections to avoid
too separate resource allocation.
For example, when the Office ID resource is allocated to 5
areas, each area is allocated with 100*N adjacent office IDs.
Each section has 100 adjacent office IDs, and N can be different
in different areas.
3. Add moderate surpluses for required resources, and do not use
up them.
For example, if the Office ID resource is allocated to 5 areas,
do not allocate all 2048 adjacent office IDs, except that each
area really has 400 adjacent offices to be configured. If the
Office ID resource in one area is insufficient after a period of
time, separately allocate one section of (100) adjacent office
IDs to this area.

Configuring Resource
Attributes
Prerequisites

Before the operation, it is required to confirm:

Confidential and Proprietary Information of ZTE CORPORATION

115

ZXWN MSCS Data Configuration Guide(MSCS)

Context

The overall resource planning is made.

The MML Terminal window is opened.

The MSCS has authority-division and area-division function, so it


is required to allocate different resource attributes for different
areas before configuring the data. If the area is not divided, all
the resource attributes can be configured in the common area.
Table 46 lists the resource types, key fields and value ranges in
the MSCS resource management system.
TABLE 46 RESOURCE TYPES, KEY FIELDS AND VALUE RANGES OF
THE MGCF
Configuration Items

Resource
Types

Key Fields

Minimum

Maximum

Office data
configuration

Adjacent
office

Office ID

3000

Signaling
linkset

Link set No.

1024

Signaling
route

Signaling
route No.

2000

SCTP

SCTP ID

2048

ASP

ASP ID

2048

AS

AS ID

640

M3UA static
route

M3UA
static route
ID

640

Node
Topology
Config

Topology
node ID.

2048

Voice Codec
Template

Template
ID

255

Trunk group

Trunk
group
number

4000

Outgoing
route

Route No.

20000

Outgoing
route set

Route set
No.

3000

Outgoing
route chain

Route
chain ID

3000

Chain analysis

Chain
analysis
index

3000

Protocol configuration

Topology
configuration

Trunk routing configuration

116

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 4 Resource Configuration

Configuration Items

Number
analysis

Access configuration

Service configuration

Steps

Resource
Types

Key Fields

Minimum

Maximum

Automatic
Re-routing
Route Set

Re-routing
route set

1000

Number
Pre-analysis
Selector

Number
Preanalysis
Selector

1000

Number
Analysis
Entrance

Number
Analysis
Entrance

1000

Number
Analysis
Selector

Number
Analysis
Selector

4096

Template
of Number
Analysis
Selector

Template
of Number
Analysis
Selector

65535

Number
Transform
Index

Number
Transform
Index

2048

Black White
List Selector

Black
White List
Selector

1000

SIP Called
Number
Analysis
Selector

Selector

1000

Location Area

Location
Area ID

65534

Emergency
Call Center
Index

Emergency
call center
index

255

Welcome
Messages

Welcome
Message
Code

128

Camel Access
Subscription
Information

Camel Information Index


Number

255

1. On the NetNumen (TM) M30 window, select menus Views


> Resource Management, and the Resource Management
window appears, as shown in Figure 45 .

Confidential and Proprietary Information of ZTE CORPORATION

117

ZXWN MSCS Data Configuration Guide(MSCS)

FIGURE 45 AREA TREE

2. In Area Tree, right click the area where resources need to


be added under the MSCS. Click the shortcut menu Add resource, as shown in Figure 46.
FIGURE 46 ADDING RESOURCES

3. The Add Resource dialog box appears, as shown in Figure 47.


The parameter description is shown in Table 46.

118

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 4 Resource Configuration

FIGURE 47 RESOURCE ADDING DIALOG BOX

4. Select the resource type to be added from the field Resource


Type drop-down list box, and input the corresponding parameters. Click the Add button, and the added resource is displayed
in the resource list.
5. After all kinds of required resource types are configured, click
the Confirm button to exit the resource configuration.
END OF STEPS

Confidential and Proprietary Information of ZTE CORPORATION

119

ZXWN MSCS Data Configuration Guide(MSCS)

This page is intentionally blank.

120

Confidential and Proprietary Information of ZTE CORPORATION

Chapter

MSCS-MGW
Interconnection Data
Configuration
Table of Contents
Overview........................................................................ 121
Interface Address Configuration......................................... 123
BFD Configuration (optional) ............................................. 126
Creating a Static Route .................................................... 129
Adjacent Office and Topology Configuration ......................... 131
SIGTRAN Configuration .................................................... 145
H.248 Configuration......................................................... 158

Overview
Description

Mc interface is the interface between MSCS and MGW. It usually adopts the IP bearer, and its protocol stack adopts the
BICC/M3UA/SCTP/IP mode.

Configuration
Flow

Figure 48 shows the flow of configuring the interconnection data


between MSCS and MGW.

Confidential and Proprietary Information of ZTE CORPORATION

121

ZXWN MSCS Data Configuration Guide(MSCS)

FIGURE 48 FLOW OF MSCS-MGW INTERCONNECTION


CONFIGURATION

Description

The flow of MSCS-MGW Interconnection data is shown in Table 47.


TABLE 47 FLOW DESCRIPTION

122

Steps

Operations

Procedures

Interface IP address
configuration

According to the IP address planning


, configure the loopback interface
address, SIPI interface address, and
USI interface address.

BFD configuration
(optional)

BFD parameters are configured


when load-sharing networking mode
is adopted. BFD is not required for
active/standby networking mode.

Creating static route

It is configured when the service IP


address of local signaling plane and

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 5 MSCS-MGW Interconnection Data Configuration

Steps

Operations

Procedures
PE interface address are not in the
same network section .

Adjacent office and


topology configuration

It is to create adjacent office and


topological node .

SIGTRAN configuration

It is configured when IP bearer is


adopted.

H.248 configuration

It is only configured for Mc interface.

Interface Address
Configuration
Overview
Introduction

Interface IP addresses are planned according to the actual networking applications. The IP address of Nc, Iu-CS and other interfaces can be configuration independently, or share with the Mc
interface address.

Creating a Loopback Interface


Prerequisites

Before the operation, it is required to confirm:

The RPU module configuration is completed, and the RPU works


normally.

The MML Terminal window is opened.

Context

Creating the loopback interface means creating the service address on the RPU loopback port. Since the service address of Mc
interface can use ports 1 and 2, it is recommended that each port
is configured with one IP address.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the RPU loop back interface. The command is INTERF
ACE LOOPBACK.
Port represents the port number, ranging from 1 to 128.
Example: Create the loop-back interface whose port number
is 1.
The command is as follows.

Confidential and Proprietary Information of ZTE CORPORATION

123

ZXWN MSCS Data Configuration Guide(MSCS)

INTERFACE LOOPBACK:PORT=1;
3. Create the interface address. The command is ADD IP ADDR
ESS.
Table 48 describes the main parameters in the ADD IP ADDRESS command.
TABLE 48 PARAMETERS IN THE ADD IP ADDRESS COMMAND
Parameter
Name

Parameter
Description

Instruction

ADDRESS

IP address

It is a mandatory parameter.
The IP address of the
loop-back address.

MASK

Mask

It is a mandatory parameter
of 32-bit. In general, it is
255.255.255.255.

BROADCASTIP

Broadcast IP
address

It is an optional parameter. In
general, it is 255.255.255.255.

Example: Create a loop back address with the following requirements.

IP address: 192.168.11.11

Subnet mask: 255.255.255.255.

The command is as follows.


ADD IP ADDRESS:ADDRESS="192.168.11.11",MASK="255
.255.255.255",BROADCASTIP="255.255.255.255";
4. Save the online configured data. Otherwise, these will loss
when the RPU is restarted.The command is SAVE ONLINEDA
TA;.
5. Exit the interface configuration mode. The command is EXIT;
END OF STEPS

Creating an SIPI Interface Address


Prerequisites

Before the operation, it is required to confirm:

The SIPI unit is created.

The MML Terminal window is opened.

Context

MSCS is interconnected to MGW on the CE through its SIPI board.


The online configuration of SIPI board interface is to assign an IP
address to some physical port of this SIPI board.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.

124

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 5 MSCS-MGW Interconnection Data Configuration

SET:NEID=11;
2. Enter the SIPI board interface configuration mode. The command is INTERFACE.
Table 49 describes the main parameters in the INTERFACE
command.
TABLE 49 INTERFACE REAL INTERFACE
Parameter
Name

Parameter
Description

Instruction

SUBSYSTEM

Subsystem ID

It is a mandatory parameter.
Select the default value 0.

MODULE

Module No.

It is a mandatory parameter.
Select the default value 1.

UNIT

Unit No.

It is a mandatory parameter. It
is the unit number of the real
interface. Select the unit number
of the board corresponded by the
interface.

SUNIT

Subunit No

It is a mandatory parameter. Real


interfaces sub-unit number fixedly
adopts 1.

Port number

It is a mandatory parameter. The


port number refers to the network
interface serial number of the
SIPI rear board for connecting to
the external. The four network
interfaces are numbered 1 to 4
from top to bottom. Only the first
port is used.

PORT

Example: Create the interface address of SIPI board. The configuration requirements are as follows.

Unit number: 321

Sub-unit number: 1

Port number: 1

Home module number: No.1 OMP module.

The command is as follows.


INTERFACE:SUBSYSTEM=0,MODULE=1,UNIT=321,SUNI
T=1,PORT=1;
3. Create the interface address of the SIPI. The command is ADD
IP ADDRESS.
Table 50 describes the main parameters in the ADD IP ADDR
ESS command.

Confidential and Proprietary Information of ZTE CORPORATION

125

ZXWN MSCS Data Configuration Guide(MSCS)

TABLE 50 ADD IP ADDRESS REAL INTERFACE


Parameter
Name

Parameter
Description

Instruction

ADDRESS

IP address

It is a mandatory parameter.
The Mc interface address of SIPI
board

MASK

Subnet mask

It is a mandatory parameter. The


real interface subnet address of
corresponding interface board

BROADCASTIP

Broadcast IP
address

It is an optional parameter,
corresponding to the broadcast
address of the real address of the
corresponding interface board.

Example: The configured parameters are as follows.

IP address: 192.168.1.11

Subnet mask: 255.255.255.248

Broadcast address: 255.255.255.255.

The command is as follows.


ADD IP ADDRESS:ADDRESS="192.168.1.11",MASK="255.
255.255.248",BROADCASTIP="255.255.255.255";
4. Save the online configured data. Otherwise, these will loss
when the RPU is restarted.The command is SAVE ONLINEDA
TA;.
5. Exit the interface configuration mode. The command is EXIT;
END OF STEPS

BFD Configuration (optional)


Overview

126

Definition

Bidirectional Forwarding Detection (BFD) can greatly accelerate


the fault detection speed and enhance the recovery function. Currently, BFD function is mainly used to quickly detect the link status of soft-switching equipment. It can not only find the link fault
quickly, but also inform the equipment that initiates this detection
to handle this fault.

BFD Function
Configuration

In general, BFD function is configured in the load-sharing networking mode. One interface is configured with a BFD session.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 5 MSCS-MGW Interconnection Data Configuration

Steps

Operation

Instruction

Command

Creating a BFD
authentication

The BFD authentication


entry is configured only
when the authentication
to the BFD session is
required.

ADD BFD
AUTH

Creatinga BFD
session

Create the mapping


relationship between the
real address of the local
SIPI interface board and
the router interface.

ADD BFD
SESSION

Creating a BFD Authentication Entry


Prerequisites

Before the operation, it is required to confirm:


The MML Terminal window is opened.

Context

The BFD authentication entry is configured only when the authentication to the BFD session is required.

Note:
Authentication type and Key of both ends must be consistent.
Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create BFD authentication. The command is ADD BFD AUTH.
Table 51 describes the parameters in the ADD BFD AUTH command.
TABLE 51 PARAMETERS IN THE ADD BFD AUTH COMMAND
Parameter
Name

Parameter
Description

Instruction

AUTHTYPE

Authentication
type

It is a mandatory parameter
including SIMPLE, MD5,
METIC_MD5, SHA1, and
METIC_SHA

AUTHKEYID

Authentication
ID

It is a mandatory parameter.
Type an integer within 1~255.

KEY

KEY

It is a mandatory parameter.
Enter it according to different
authentication types.

Confidential and Proprietary Information of ZTE CORPORATION

127

ZXWN MSCS Data Configuration Guide(MSCS)

Example: Create BFD authentication with the following requirements.

Authentication type: SIMPLE

Authentication ID: 1

KEY: 1.

The command is as follows:


ADD BFD AUTH:AUTHTYPE=SIMPLE,AUTHKEYID=1,KEY
="1";
END OF STEPS

Creating a BFD Session


Prerequisites

Before the operation, it is required to confirm:


The MML Terminal window is opened.

Context

Perform this procedure to create the mapping relationship between


the real address of the local SIPI interface board and the router
interface.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create BFD session. The command is ADD BFD SESSION.
Table 52 describes the parameters in the ADD BFD SESSION
command.
TABLE 52 PARAMETERS IN THE ADD BFD SESSION COMMAND

128

Parameter
Name

Parameter
Description

Instruction

SRCIP

Local address of
BFD session

It is a mandatory
parameter. Types the
interface address of SIPI.

DSTIP

Remote address of
BFD session

It is a mandatory
parameter. Types
the address of the
corresponding router

MULTIHOP

Multi hop flag

It is a mandatory
parameter. Includes
SINGLE_HOP and
MULTIHOP. In general,
select SINGLE_HOP

DESMINT-

Min-transmit

It is an optional parameter,

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 5 MSCS-MGW Interconnection Data Configuration

Parameter
Name

Parameter
Description

Instruction
ranging from 100000 to
10000000.

XINTVAL

interval (ms)

REQMINRXINTVAL

Min-receive
interval (ms)

DETECTMULT

Detect
accumulator

The router produced by


different manufacturers is
configured with different
values.
Both ends of the BFD
session should be
consistent.
It is an optional parameter.
Type an integer ranging
from 2 to 255.
The recommended value is
2

OPTMODE

Work mode

It is an optional parameter.
Select ASYNCHRONOUS

AUTHID

Authentication ID

The parameter ranges from


1 to 255

CHGOVER

Change Over

YES can be selected

Example: Create the BFD session when SIPI interface board is


connected with the router. The requirements are as follows.

Local address of BFD session: 10.0.74.4

Remote address of BFD session: 10.0.74.1

Single hop flag: SINGLE_HOP

Working mode: Asynchronous.

The command is as follows:


ADD BFD SESSION:SRCIP="10.0.74.4",DSTIP="10.0.74.1
",MULTIHOP=SINGLE_HOP,DESMINTXINTVAL=100000,R
EQMINRXINTVAL=100000,DETECTMULT=3,OPTMODE=A
SYNCHRONOUS;
END OF STEPS

Creating a Static Route


Prerequisites

Context

Before the operation, it is required to confirm:

The interface address is created.

The BFD parameters are created when load-sharing networking


mode is adopted.

The MML Terminal window is opened.

Static route is created when the service IP address of local signaling plane and PE interface address are not in the same net-

Confidential and Proprietary Information of ZTE CORPORATION

129

ZXWN MSCS Data Configuration Guide(MSCS)

work section. Under the active/standby working mode, a destination address needs to be configured with a route only. Under the
load-sharing working mode, a destination address usually needs
to be configured with two routes.
Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the static route. The command is ADD IP ROUTE.
Table 53 describes the parameters in the ADD IP ROUTE command.
TABLE 53 PARAMETERS IN THE ADD IP ROUTE COMMAND
Parameter
Name

Parameter
Description

NETPRE

Net prefix

MASK

Mask

Instruction

It is a mandatory parameter.
Type the network section of the
opposite-end equipment service
address according to the network
planning. Its prefix should match
its mask

NEXTHOP

Next hop IP

It is an optional parameter,
indicating the router interface
address (VRRP address). Type the
gateway address to the opposite
end office

DISTANCE

Distance

It is an optional parameter with a


default of 1, ranging from 1 to 254

Enable BFD
Detect

It is an optional parameter. In
general, select NO. The setting
Enable BFD Detect is effective
only when IP address acts as the
next hop.

BFDDETECT

Example: Create the static route to the opposite end with the
following requirements.

Working mode: active/standby mode

Service address of the opposite equipment: 11.11.11.11

Mask: 255.255.255.0

Next hop IP: 10.0.74.1.

The command is as follows:


ADD IP ROUTE:NETPRE="11.11.11.11",MASK="255.255.
255.0",NEXTHOP="10.0.74.1",DISTANCE=1,BFDDETECT
=NO;
Example: Create two static routes to the opposite end with the
following requirements.

130

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 5 MSCS-MGW Interconnection Data Configuration

Working mode: load-sharing mode

Service address of the opposite equipment: 11.11.11.11

Mask: 255.255.255.0

Next hop IP: 10.0.74.1 and 10.0.74.2.

The command is as follows:


ADD IP ROUTE:NETPRE="11.11.11.11",MASK="255.255.
255.0",NEXTHOP="10.0.74.1",DISTANCE=1,BFDDETECT
=NO;
ADD IP ROUTE:NETPRE="11.11.11.11",MASK="255.255.
255.0",NEXTHOP="10.0.74.2",DISTANCE=1,BFDDETECT
=NO;
END OF STEPS

Adjacent Office and


Topology Configuration
Overview
Introduction

Adjacent office configuration means configuring the neighboring


office of the local office. There are two association modes, direct
association and quasi-association.
If the adjacent office is regarded as a node in the whole network
topology when the local office is in the center, topological node
configuration means adding the topological node of its adjacent
office in the local office. The topological nodes configured on MSCS
include MGW, RNC/BSC, and MSCS (Nc).

Configuration
Flow

Steps

Operations

Instructions

Command

Creating an MGW
adjacent office

Create the basic information of


MGW adjacent office.

ADD ADJOFC

Creating an MGW
voice CODEC template

Create the encoding and decoding


speech type modules supported by
IM-MGW.

ADD CODECTPL

Creating a topology node

Create the topology


relationship
between
MGCF
node and IM-MGW
node.

ADD TOPO

Confidential and Proprietary Information of ZTE CORPORATION

131

ZXWN MSCS Data Configuration Guide(MSCS)

Steps

Operations

Instructions

Command

Creating
interMGW bear mode
(optional)

The
inter-MGW
bearer mode is
configured when
the Nb interfaces
between several
IM-MGWs
under
the same MGCF
are connected.

ADD MGWBEAR
MOD

Creating an MGW Adjacent Office


Prerequisites

Before the operation, it is required to confirm:

The physical IP connection between the MSCS and the MGW


is clear, which is implemented by the connection between the
FE1 interfaces on the rear board of the SIPI boards of these
two NEs.

The signaling interworking data is planned and negotiated.

The basic configuration of the local office is completed.

The range of adjacent office number is configured in the resource management.

The MML Terminal window is opened.

Context

Perform this procedure to configure the basic information of MGW


adjacent office. On the MSCS, each MGW is configured with three
adjacent offices according to the SCTP Planning.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the MGW adjacent office. The command is ADD ADJO
FC.
Table 54 describes the main parameters in the ADD ADJOFC
command.
TABLE 54 PARAMETERS IN THE ADD ADJOFC COMMAND
Parameter
Name

ID

132

Parameter
Description

Instruction

Office ID

A mandatory parameter,
indicating the identification
number of the adjacent
office, and ranging from
1 to 3000. In general,
it is configured as the
exchange ID of the
adjacent office during the
all-network planning

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 5 MSCS-MGW Interconnection Data Configuration

Parameter
Name

Parameter
Description

Instruction

NAME

User-defined alias

It is a mandatory
parameter. Type a
customized name.

NET

Network type

A mandatory parameter,
indicating the network
type of the SPC used for
connecting the local office
to the adjacent office
when the local office is
configured with several
SPs. The default is the
network type of this SP
when there is only one SP
in the local office

OFCTYPE

The type of adjacent


office

It is a mandatory
parameter. Select MGW
for the MGW bearing H248
signaling. Select SGW for
another two MGW offices.

SPCFMT

SPC format

Select TRIPLE_DEC.

SPCTYPE

SPC type

DPC

Destination SPC

RC

Area code

It is a mandatory
parameter. Select it
based on the SPC type
of the adjacent office
according to the signaling
point planning. In China,
all the NEs adopt the 24-bit
SPC except the BSC that
adopts the 14-bit SPC.
It is an optional parameter,
indicating the local toll
zone code of the adjacent
office. This parameter
has impact on the area
code added by the calling
number

Association type,
including:

ASSOTYPE

SPTYPE

AM_SURE (direct
connection mode)

AM_QUASI (half
direct connection
mode)

AM_NONE (none
connection mode).

Signaling point type,


including SEP, STP,
and STEP

It is an optional parameter.
Select AM_SURE

It is an optional parameter.
Select SEP (signaling
end point) for the MGW
bearing H248 signaling.
Select STEP (signaling
transition / end point) for
another two MGW offices

Confidential and Proprietary Information of ZTE CORPORATION

133

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction

Subservice function,
including

INTERNATIONAL
(International
signaling point
code)

INTERNATIONAL
STANDBY
(International
standby signaling
point code)

SSF

NATIONAL
(National signaling
point code)

NATIONAL
STANDBY
(National standby
signaling point
code).

It is an optional parameter.
In general, NATIONAL
is selected at home. For
the BSC adjacent office,
NATIONAL STANDBY is
selected.

Office Attribute,
including:
TAG

ISNI (Has ISNI


Function)
TRANS (Translate
Node)

It is an optional parameter

TEST (Need Test


Info:0X02/0X01)

TEST

Test flag

It is an optional parameter.
It is used to set whether
the MTP3 link actively
initiates the link test
after entering the service
status. In most cases, this
parameter is selected.
It is an optional parameter
with a default of NO. It
is used for SCCP to judge
whether to use the LUDT
message.

BANDFLAG

Broadband attribute

The maximum length of a


broadband link message
is 4,000, and that of a
narrowband link message
is 255. Because the MTP
layer does not have the
segmentation function, the
incorrect configuration of
this parameter probably
causes the long packet to
be discarded.
Select this parameter
when all the links between
two SPs are SIGTRAN or
ATM signaling links.

134

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 5 MSCS-MGW Interconnection Data Configuration

Parameter
Name

Parameter
Description
Protocol Type,
including:

PRTCTYPE

CLST

CHINA (China)

ITU (International
Telecommunications Union)

ANSI (American
National Standards
Institute)

Cluster ID

Instruction
It is an optional parameter.
The CHINA and the ITU
are used for the NO.7
signaling networking of
the ITU standard and the
ANSI is used for the NO.7
signaling networking of
the American standard.
In general, select CHINA
for the domestic office
and select ITU for the
international office
It is an optional parameter
within 0~65535. In
general, select the default
value 65535. It is valid
when the protocol type
of the adjacent office is
ANSI. The signaling point
connected to the signaling
transfer point belongs to
the corresponding cluster

Office Info, including:

CIC_PCM (CIC
starts the load
sharing according
to the PCM code
mode)

BLOCK (Manual
block status)

EVEN_CIC (The
office controls
the even CIC
when CIC resource
contention occurs)

INFO

CALLING(Calling
transform is
allowed)

CALLED (Called
transform is
allowed)

MOD24_CIC (CIC
mode with 24
mode)

TEST (Dynamic
test)

It is an optional parameter
and the default value is
CIC_PCM

Confidential and Proprietary Information of ZTE CORPORATION

135

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction

RELATEDOFC1

Related Office ID

It is an optional parameter
ranging from 0 to 3000

Office Extend Info,


including:

SIGBRDCST
(Support Signaling
Broadcast
Message)

MTP (Hongkong
MTP Standard)

DUPU ( Screen
DUPU message)

SUA_REC_DT1
(Receive SUA
message and
handle it as DT1
message)

INFOEX

SUA_SND_DT1
(Send SUA
message and
handle it as DT1
message without
SN.)

OPEN_TG_RES
(Open outter trunk
group resource)

It is an optional parameter

For example, create MGW adjacent office. The office ID is 101,


the alias is MGW1, and the destination SPC is 1.31.2. For other
parameters, adopt the default value. The command is as follows:
ADD
ADJOFC:ID=101,NAME="MGW1",NET=3,OFCTYPE
=MGW,SPCFMT=TRIPLE_DEC,SPCTYPE=14,DPC="1.31.2
",RC="25",ASSOTYPE=AM_SURE,SPTYPE=SEP,SSF=NATIO
NAL STANDBY,SUBPROTTYPE=DEFAULT,TEST=YES,BAND
FLAG=YES,PRTCTYPE=CHINA,CLST=65535,INFO="CIC_P
CM",RELATEDOFC1=0;
END OF STEPS

Creating an MGW Voice CODEC


Template
Prerequisites

136

Before the operation, it is required to confirm:

The basic configuration of the local office is completed.

The range of the MGW voice CODEC template numbers is configured in the resource management configuration.

The MML Terminal window is opened.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 5 MSCS-MGW Interconnection Data Configuration

Context

Perform this procedure to create the encoding and decoding


speech type modules supported by MGW. In general, MSCS is
configured with a default common voice CODEC template.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the MGW voice CODEC template. The command is ADD
CODECTPL.
Table 55 describes the main parameters in the ADD CODEC
TPL command.
TABLE 55 PARAMETERS IN THE ADD CODECTPL COMMAND
Parameter
Name

Parameter
Description

Instruction

ID

Template
number

It is a mandatory parameter
for defining an encoding and
decoding speech template,
ranging from 1 to 255.

GRPID

The group
number of the
speech coding.

It is a mandatory parameter for


specifying the OID format and
encoding and decoding type list.
Up to eight types can be defined
in an encoding and decoding
template.

VALFG

Valid option,
including YES
(valid) and NO
(invalid)

It is a mandatory parameter for


setting whether this encoding
and decoding speech template is
valid. Select YES
It is a mandatory parameter for
specify an Organization Identifier
(OID).
It has the following parameters.

OID

OID

OID_NONE: No OID

OID_ITU_T: ITU_T

OID_ETSI: ETSI

OID_IETF: IETF

ITYPE

ITU_T CODEC
type.

It is an optional parameter. In
general, ITUT_G711A_64 is
selected.

ETYPE

ETSI CODEC
type

It is an optional parameter. In
general, ETSI_UMTS_AMR
and ETSI_UMTS_AMR_2 are
selected.

ACTRATE

Activated
CODEC rate

It is an optional parameter. In
general, the default value is
selected

Confidential and Proprietary Information of ZTE CORPORATION

137

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction

SUPRATE

Supported
CODEC rate

It is an optional parameter. In
general, the default value is
selected

OM

ACS optimized
mode

It is an optional parameter. In
general, the default value is
selected

Example: Configure an MGW encoding and decoding speech


template with the following requirements.

Template ID: 1

CODEC group number: 1

Valid option: YES

OID: ETSI

ETSI CODEC type: ETSI_UMTS_AMR2

Activated CODEC rate: 5.90 K and 6.70 K

Supported CODEC rate: 5.90 K and 6.70 K

ACS optimize mode: Yes.

ADD
CODECTPL:ID=1,GRPID=GRPID1,VALFG=YES,OID
=OID_ETSI,ETYPE=ETSI_UMTS_AMR_2,ACTRATE="Rate59
0"&"Rate670",SUPRATE="Rate590"&"Rate670",OM=YES;
END OF STEPS

Creating a Topology Node


Prerequisites

Context

Before the operation, it is required to confirm:

The encoding and decoding speech template is configured.

The range of the topological node number is configured in the


resource management.

The MML Terminal window is opened.

Perform this procedure to configure the topology relationship


between MSCS node and MGW node. This command is used to
configure the adjacent NE information, including equipment type,
bearer type and attributes, user plane version, encoding and
decoding template, and other information.
For Mc interface, only the adjacent office bearing H.248 protocol
is configured as a topological node.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;

138

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 5 MSCS-MGW Interconnection Data Configuration

2. Create an MGW topology node. The command is ADD TOPO.


Table 56 describes the main parameters in the ADD TOPO
command.
TABLE 56 PARAMETERS IN THE ADD TOPO COMMAND
Parameter
Name

Parameter
Description

Topological node
ID

ID

OFCID

Office ID

Instruction
It is a mandatory parameter to
define ID of this node, ranging
from 1 to 2,048.
It is recommended that the ID
and office No. of a topological
node are consistent
It is a mandatory parameter
for specifying the office ID of
this topological node. This
parameter must be defined by
the ADD ADJOFC command
first.
In this case, type the actual
MGW office number

NAME

CODECID

ETYPE

Alias

It is a mandatory parameter
for naming this topological
node, with a length ranging
from 1 to 50 characters.

CODEC identity

It is a mandatory parameter
for specify the CODEC
template used by this
topological node. This
parameter must be defined
by the ADD CODECTPL
command first.

Equipment type

This parameter is used to


specify the NE type of this
topological node.
Select R4GW for an MGW
node

PROTTYPE

IPVER

Protocol type

Select H.248 for Mc interface.

IP version of the
node

It is the IP protocol version


supported between nodes.
Select IPV4 or IPV6
according to the actual
conditions. Currently, IPV4 is
supported.

Confidential and Proprietary Information of ZTE CORPORATION

139

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

ATTR

Parameter
Description

Bearer attributes

Instruction
This parameter is only valid
for the node with the type
of R4GW (MGW). The bearer
types supported by MGW
are BNCAAL1, BNCAAL2,
BNCAAL1S, BNCIPRTP, and
BNCTDM. MGW can support
one or more of these types of
bearers.
In general, select BNCAAL2,
BNCIPRTP, and BNCTDM

UPVER

User plane
protocol version
of RNC or MGW
Extended
attributes (tunnel
mode), including:

NOTUNL
(None tunnel
mode)

RTUNL
(Rapid tunnel
mode)

ATTR2

DTUNL
(Delay tunnel
mode)

Signaling transfer
mode, including:
TRFMOD

MCINTF (Mc
interface signal
transfer mode)

This parameter is used to set


the user plane version of this
node.
In general, select V2

This parameter is used to set


which tunnel mode is adopted
for bearer establishment when
this node supports the IP/RTP
bearer. The default value is
NOTUNL (None tunnel mode).
In general, select DTUNL
(Delay tunnel mode) for an
MGW topological node.

This parameter is used to set


which mode is used by the
topology for reporting when
it detects CNG or CED fax
signals.
The default value is MCINTF

Error SDU
control, including
options:

UPERRCTRL

140

YES: The user


plane entity implements error
inspection, and
sets the FQC bit
position according to the result.
It will transmit
all frames includes the error
frames to the
user plane layer.
During a call, the
error packet control parameter
delerrsdu=Yes,
which is delivered
by the terminal
established by

Confidential and Proprietary Information of ZTE CORPORATION

This parameter regulates the


handling method of the user
plane for error frames. It is
only valid for MGW-type and
RNC-type topological node.
The default value is YES

Chapter 5 MSCS-MGW Interconnection Data Configuration

Parameter
Name

Parameter
Description
MGW on the Mc
interface. The
error packet control parameter
deliveryOfErroneousSDU is YES,
NA, NA during
RAB assignment.

Instruction

NO: The user


plane entity implements the
error inspection.
It will directly
discard the error
frame. During
a call, the error packet control parameter
delerrsdu=No,
which is delivered
by the terminal
established by
MGW on the Mc
interface. The
error packet control parameter
deliveryOfErroneousSDU is NO,
NA, NA during
RAB assignment.
INVALIDTION:
The user plane
entity does not
implement the
error inspection.
During a call, the
error packet control parameter
delerrsdu=NA,
which is delivered
by the terminal
established by
MGW on the Mc
interface. The
error packet control parameter
deliveryOfErroneousSDU is NA,
NA, NA during
RAB assignment.

DTMFTC

Tandem office
send DTMF
use TC mode,
including two
options:

NO

YES

This parameter is used to set


whether the tandem office
uses the TC resources during
DTMF number delivery.
The default value is NO

Confidential and Proprietary Information of ZTE CORPORATION

141

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction
It contains the following
options.

MGWCON

MGW congestion
reporting
capability

SMGWCON (Standard
MGW congestion event)

CMGWCON (Custom MGW


congestion event).

The default value is


SMGWCON.

Example: Create a topology node with the following requirements.

MGW office ID: 101

Equipment type: R4 gateway

Protocol type: H248

Supported user plane protocol version: V2

CODEC ID: 1.

The specific command is as follows.


ADD TOPO:ID=101,OFCID=101,NAME="MGW101",CODE
CID=1,ETYPE=R4GW,PROTTYPE=H248,IPVER=IPV4,ATT
R="BNCAAL2"&"BNCIPRTP"&"BNCTDM",UPVER="V2",ATTR
2=DTUNL,TRFMOD=MCINTF,UPERRCTRL=YES,DTMFTC=N
O,MGWCON=SMGWCON,AUTOFAX=YES,OOBTC=NO,BCUI
D=0,SENDCAP=NO,G711TRAN=NO,BICCDTMF=TRANSPA
RENT,IPBCP2833=BYMGW,BICCDTMPPER=0,AOIPPRO=P
RIVATE;
END OF STEPS

Creating an Inter-MGW Bearer Mode


Prerequisites

Before the operation, it is required to confirm:

The MGW topological node is created.

The MML Terminal window is opened.

Context

The inter-MGW bearer mode is configured when the Nb interfaces


between several MGWs under the same MSCS are connected.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the inter-MGW bearer mode. The command is ADD
MGWBEARMOD.

142

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 5 MSCS-MGW Interconnection Data Configuration

Table 57 describes the main parameters in the ADD MGWBE


ARMOD command.
TABLE 57 PARAMETERS IN THE ADD MGWBEARMOD COMMAND
Parameter
Name

Parameter
Description

Instruction

MGWPAIR

MGW node pair

Type the gateway node ID


configured in the topological
node configuration.

Bearer attribute
between MGWs,
the options
include:
AAL1(support
bncAAL1)
AAL2(support
bncAAL2)

ATTR

AAL1S (support
nbcAAL1Struct)

The parameter specifies the


bearer attribute between
MGWs. Select RTP or TDM
according to the type of Nb
interface bearer.

RTP (support
bncIPRTP)
TDM(support
bncTDM)

CTYPE

Type of tone code


between MGWs,
the options
including:
GENERAL
AMRONLY

AMRONLY represents the AMR


encoding and decoding mode
is used only. When G.711 and
other encoding and decoding
modes are allowed, select
GENERAL

NAME

Alias

Adjacent office alias of


gateway 1-Adjacent office alias
of gateway 21

AAL1

AAL1 bearer type


rate(%)

The parameter specifies the


rate (%) of the AAL1 bearer
between two gateways

AAL2

AAL2 bearer type


rate(%)

The parameter specifies the


rate (%) of the AAL2 bearer
between two gateways

AAL1S

AAL1STRUCT
bearer type
rate(%)

The parameter specifies the


rate (%) of the AAL1 STRUCT
bearer between two gateways

RTP

IPRTP bearer type


rate(%)

The parameter specifies the


rate (%) of the IPRTP bearer
between two gateways

TDM

TDM bearer type


rate(%)

The parameter specifies the


rate (%) of the TDM bearer
between two gateways

Confidential and Proprietary Information of ZTE CORPORATION

143

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

DIRECT

Top-priority direct
link topology, the
options include:

Instruction

The default is NO

NO
YES
User plane mode
for multi-gateway
IP bearer, the
options include:
UPMODE

TRANSPARENT(transparent
mode)

The default is TRANSPARENT

SUPPORT(support
mode)
IPNET

G711TRAN

Public IP network
domain index
G711 that is
forced to use
the transparent
mode. Options
include:

The parameter is used to set


the public IP network domain
index (ADD IPDOMAIN)

The default is NO

NO
YES

Example: Configure the bearer mode between two MGWs with


the following requirements.

MGW 1 node ID: 101

MGW 2 node ID: 201

Bearer mode: RTP

Type of tone code between MGWS: AMRONLY

Supported version: V2

Alias: MGW101-MGW201

Other parameters: default value.

The specific command is as follows.


ADD MGWBEARMOD:MGWPAIR="101"-"201",ATTR="RTP
",NAME="MGW101-MGW201",CTYPE=AMRONLY,AAL1=0,A
AL2=0,AAL1S=0,RTP=100,TDM=0,DIRECT=NO,UPMODE
=TRANSPARENT,G711TRAN=NO;
END OF STEPS

144

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 5 MSCS-MGW Interconnection Data Configuration

SIGTRAN Configuration
Overview
Description

SINGTRAN-related configuration is required not only by the Mc


interface between MSCS and MGW, but also by the Nc interface
between MSCS and other direct-associated office over IP.
When the SCTP bears the M3UA protocol, configuring SCTP, ASP,
AS, M3UA static route and SIO-locating-AS is required.
When the SCTP bears H248 protocol, configuring SCTP is required
only. In general, this mode is not used.
Compared with the MTP data configuration of the traditional No.7
signaling, the SCTP association configuration and the ASP configuration of the M3UA are similar to the link logic and bearer information configurations in the MTP configuration, and the AS configuration of the M3UA is similar to the link set configuration in the
MTP configuration. The configuration of SIO location AS is similar
to the signaling office direction and route configuration in the MTP
configuration. The only difference between them is that one piece
of SIO location AS configuration record is configured the IP route
to a subscriber of an office.

Confidential and Proprietary Information of ZTE CORPORATION

145

ZXWN MSCS Data Configuration Guide(MSCS)

Configuration
Flow

Figure 49 shows the flow of SIGTRAN configuration.


FIGURE 49 SIGTRAN CONFIGURATION FLOW

According to the rules regulated in SCTP Planning, perform the


configuration by following the procedure specified below.

146

Steps

Operations

Instructions

Command

Creating SCTP

Create an association
between two offices

ADD SCTPCONN

Creating ASP

Create the oneto-one relationship


between the ASP and
the association. ASP
is one of instances of
AS.

ADD ASP

Creating AS

Create the tag, user


type, subsystem type
of AS

ADD AS

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 5 MSCS-MGW Interconnection Data Configuration

Steps

Operations

Instructions

Command

Creating M3UA
static route

Create the mapping


relationship between
the M3UA static route
and the AS.

ADD M3UART

Creating
the SIOLocating-AS

Locate one service to


a routing table that
is maintained by the
ASP under the AS.

ADD SIOLOCAS

SCTP Planning
The signaling carried by associations between MSCS and MGW is
as follows.
1. If the association bears the H248 signaling between MSCS and
MGW, the H248/M3UA/SCTP bearer is adopted usually, and the
H248/SCTP bearer is supported.
2. The association bears the ISUP, TUP, and SCCP signaling
between MSCS and MSC/HLR (MGW acts as an agent or
transfers the signaling). M3UA/SCTP adopts the (ISUP, TUP,
SCCP)/M3UA/SCTP bearer.
If the MTP3 direct-associated office does not exist on MGW, the
SCTP configuration is not required.
3. The association bears the BSSAP and RANAP signaling between
MSCS and RNC/BSC (MGW acts as an agent or transfers the
signaling), the SCCP/M3UA/SCTP bearer is adopted.
If MSCS is directly connected with BSC/RNC, the SCTP configuration is not required.
According to the rules regulated in SPC Configuration Rules in
Chaper 2, both MSCS and MGW adopts different combinations of
signaling points and network types for the three bearer modes
mentioned above. That is, an MSCS is configured with three adjacent offices on MGW, and one group of associations is configured
between every two adjacent offices for bearing different services.
The number of associations is related with the signaling networking, equipment capacity, and configured SMP number. It is also
limited by the configuration. For example, an AS can be configured with up to 16 SCTP associations.

Creating an SCTP
Prerequisites

Before the operation, it is required to confirm:

The physical configuration of the SMP module is completed.

The SCTP flag is configured in the resource management.

The MML Terminal window is opened.

Confidential and Proprietary Information of ZTE CORPORATION

147

ZXWN MSCS Data Configuration Guide(MSCS)

Context

The SCTP connection is called as association, which is of one-toone correspondence with ASP. It can be equivalent to the communication link used by the AS. An SMP can support up to 128
associations. When multiple BCTC shelves are configured, associations must share the load in each shelf.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the SCTP connection. The command is ADD SCTPCO
NN.
Table 58 describes the chief parameters of the ADD SCTPC
ONN command.
TABLE 58 PARAMETERS IN THE ADD SCTPCONN COMMAND
Parameter
Name

MODULE

OFCID

Parameter
Description

Instruction

Module No.

It is a mandatory
parameter, indicating
the number of the
signaling module
homed by this SCTP
association. Select the
SMP module number.
Each SMP can support
up to 128 associations.
The associations under
the same AS are
required sharing load
on SMP modules as
more as possible.

SCTP opposite office


ID

It is a mandatory
parameter, designating
the office No. of
the direct-associated
association. Type
the MGW adjacent
office No. specified
in the adjacent office
configuration.

Bearer protocol
types, including

M2UA

M2PA

M3UA

SUA

H248

BICC

IUA

DHCTRL

PROT

148

Confidential and Proprietary Information of ZTE CORPORATION

It is a mandatory
parameter. It is used to
identify the upper-layer
protocol type borne by
the SCTP association.
In general, M3UA is
selected. M2UA is
selected when MGW
transfers the signaling
with the M2UA mode.

Chapter 5 MSCS-MGW Interconnection Data Configuration

Parameter
Name

Parameter
Description

SIP

DIM

V5UA

H245

SCTP application
attributes. Options
include:
ROLE

SVR: SCTP is used


as server
CLT: SCTP is used as
client

LOCADDR

Local IP address

Instruction

It is a mandatory
parameter. For Mc
interface, MSCS is
configured as CLT, and
MGW is configured
as SVR. For Nc
interface, this should
be negotiated by both
sides. For example, the
small signaling point
serves as CLT, and
the big signaling point
serves as SVR
It is a mandatory
parameter. It
designates the service
address of local end
of this association,
with a format of
Local IP address
type-VPN of local
IP address-Local IP
address
Local IP address type:
IPv4 and IPv6
VPN of local IP address:
Rang from 0 to 65535
Local IP address:
the format is
xxx.yyy.zzz.mmm

LOCPORT

REMADDR

Local port number

Opposite IP address

It is a mandatory
parameter. It is the
local SCTP port number
of the association,
ranging from 1 to
65535.
It is a mandatory
parameter. It
designates the service
address of remote end
of this association,
with a format of
Remote IP address
type-VPN of remote
IP address-Remote
IP address
Remote IP address
type: IPv4 and IPv6;
VPN of remote IP
address: Rang from 0
to 65535

Confidential and Proprietary Information of ZTE CORPORATION

149

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction
Remote IP address:
the format is
xxx.yyy.zzz.mmm

REMPORT

Opposite port
number

It is a mandatory
parameter. It is
the opposite SCTP
port number of the
association, ranging
from 1 to 65535.

NAME

Alias

It is a mandatory
parameter with a
length ranging from 1
to 50 characters.

SCTP ID

It is an optional
parameter. It is the
global serial number of
the SCTP association,
ranging from 1 to 2048.
Configure it according
to the association
planning.

ID

Example: Create the SCTP connection for the Mc interface with


the following requirements.

MGW office ID: 101

Bearer protocol: M3UA

Application attribute: CLT

SCTP signaling processing module number: 3

Local port number: 2001

Opposite port number: 2001

Local IP address: 192.168.1.11

Opposite IP address: 192.168.1.31

SCTP association ID: 1

Other parameters: default value.

The command is as follows.


ADD SCTPCONN:MODULE=3,OFCID=101,PROT=M3UA,R
OLE=CLT,LOCADDR="IPv4"-"0"-"192.168.1.11",LOCPORT
=2001,REMADDR="IPv4"-"0"-"192.168.1.31",REMPORT=2
001,NAME="MGW101-1",ID=1,INSTRM=16,OUTSTRM=1
6,MAXRTRY=5,MAXRTO=500,MINRTO=50,INITRTO=10
0,HB=500,FIXNH=NO,SCTPMAXRTRYNUM=10,DELAYAC
K=20,MAXBURST=4,PRIMARYPATH=REMIP1,PMTU=0,BR
EAKTIME=0,PDTHRESH=0,MINCWND=0,PLTIMER=10,M
PPLTHRD=2,DPLEN=MTU,CB=200;
END OF STEPS

150

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 5 MSCS-MGW Interconnection Data Configuration

Creating an ASP
Prerequisites

Before the operation, it is required to confirm:

The SCTP association information configuration is completed.

The range of the ASP configuration identification is created in


the resource management configuration.

The MML Terminal window is opened.

Context

Perform this procedure to define the one-to-one relationship between the ASP and the association. ASP is one of instances of AS.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the ASP. The command is ADD ASP.
Table 59 describes the main parameters in the ADD ASP command.
TABLE 59 PARAMETERS IN THE ADD ASP COMMAND
Parameter
Name

Parameter
Description

Instruction
It is a mandatory parameter,
ranging from 1 to 2048

ASSOCID

NAME

ID

SCTP ID

Alias

ASP ID

ISLOOP

ASP self-loop ID

Type the association ID


configured in the SCTP
connection configuration.
It is a mandatory parameter,
with a lengthen ranging from
1 to 50 characters. It may
be named with a format of
Adjacent office alias-SCTP
number.
It is an optional parameter,
ranging from 1 to 2048.
It is recommended to be
consistent with ASSOCID.
It is an optional parameter. It is
used to set whether the ASP is
self-looped.
Select the default value NO

ISLOCK

ASP blocking flag

It is an optional parameter. It is
used set whether the ASP is in
blocking state.
Blocking is used for
management. Select the
default value NO

Confidential and Proprietary Information of ZTE CORPORATION

151

ZXWN MSCS Data Configuration Guide(MSCS)

Example: Create the ASP between MSCS and MGW for Mc interface with the following requirements.

MGW office ID: 101

SCTP association ID: 1

ASP configuration ID: 1

User alias: MGW101-1.

The command is as follows.


ADD ASP:ASSOCID=1,NAME="MGW101-1",ID=1,ISLOOP
=NO,ISLOCK=NO;
END OF STEPS

Creating an AS
Prerequisites

Before the operation, it is required to confirm:

The ASP configuration is finished.

The MML Terminal window is opened.

Context

The AS provides the transmission channels for upper-layer services. For example, H248 and TUP/UP are different services. They
use different AS for transmission. The AS can use one or more
associations for communication.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the AS. The command is ADD AS.
Table 60 describes the main parameters in the ADD AS command.
TABLE 60 PARAMETERS IN THE ADD AS COMMAND
Parameter
Name

152

Parameter
Description

Instruction

PROT

Supported
adaptation layer
protocols

It indicates the protocol


type of a bearer. In general,
M3UA is selected according
to the networking planning.
It is configured as M2UA
when MGW transfers the
signaling with M2UA mode.

ASP

ASP ID

It is associated with the


ASP ID configured in the
ASP configuration.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 5 MSCS-MGW Interconnection Data Configuration

Parameter
Name

Parameter
Description

Instruction

NAME

Alias

It is a mandatory
parameter. The alias
customized by the user.

AS ID

It is an optional
parameter. It is the unique
identification of the AS. In
general, it is the same as
that of the ASP for easy
memory. The parameter
ranges from 1 to 640

ID

EXISTCTX

Whether the routing


context ID exists

CTXID

Routing context ID

It is an optional parameter.
The routing context is
unique in the network.
This parameter must
be consistent with the
AS configuration of the
opposite-end. Its default
value is NO
It is an optional parameter.

Usage tag. Options


include:
SGP
ASTAG

ASP
SRV (IPSP server)
CLT (IPSP client)

ASUP

User types
supported by AS.
Options include TUP,
ISUP, BICC, H.248,
ALCAP SCCP, PCA,
NNSF and ALL

For Mc interface, MSCS


generally serves as
IPSP_Client, and MGW
serves as IPSP_Server.
When MGW acts as a SGW,
the AS at the MSCS side
serves as ASP, and the AS
at the SGW side serves as
SGP.
For Nc interface, this should
be negotiated by both
sides. For example, the
small signaling point serves
as IPSP_Client, and the big
signaling point serves as
IPSP_Server.
It is an optional parameter.
It defines the upper-layer
user types supported by
the AS. Currently, there are
eight types of users.
User type is not configured
when MGW transfers the
signaling with the M2UA
mode

Confidential and Proprietary Information of ZTE CORPORATION

153

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction
It is an optional parameter.
The supported service
modes include:

ASMD

Service modes
supported

OVERRIDE(Over-ride
mode)

LOAD (Load share


mode).

In the over-ride mode,


only one ASP is in the
activated statue. In this
case, only one ASP needs
be configured. In the
load sharing mode, N
ASPs should be configured
in the activated working
statue, and K ASPs should
be configured in the
deactivated standby statue.
The value of N+K is not
more than the number of
ASPs actually configured

SSN

Types of subsystem.
Options include
NO_SSN (subsystem
SSN excluded
(null)), SCCP, REV2
(standby), ISUP,
OMAP, MAP, HLR,
VLR, MSC, EIR, AUC,
REV11(standby),
INAP, USSD, VLRA,
SGSN_BSCAP,
RANAP, RNSAP,
GMLC_MAP, CAP,
GSMSCF_MAP,
SIWF_MAP, SGSN_
MAP, GGSN_MAP,
IP (intelligent
peripherals),
SMC, SSP_SCP,
BSC_BSSAP_LE,
MSC_BSSAP_LE,
SMLC_BSSAP_LE,
BSS_O_M_A ,
BSSAP_A and
RVE255.

Types of subsystem
supported by application
server (AS).

The parameter ranges from


0 to 16.
NVAL

The N value in load


sharing mode

The N+K should be equal to


the number of ASP under
AS.
The N value indicates that
AS puts into use if N ASPs
put into use.

Example: Configure the AS between MSCS and MGW for Mc


interface with the following requirements.

154

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 5 MSCS-MGW Interconnection Data Configuration

MGW office ID: 101

Supported adaptation layer protocol: M3UA

AS configuration ID: 1

Supported user type: H248

ASP ID: 1

Client: MSCS

Alias: H248

The command is as follows.


ADD AS:PROT=M3UA,ASPID="1",NAME="H248",ID=1,EX
ISTCTX=NO,ASTAG=SGP,ASUP="H248",ASMD=LOAD,NV
AL=1,KVAL=0;
END OF STEPS

Creating an M3UA Static Route


Prerequisites

Before the operation, it is required to confirm:

The AS configuration is finished.

The range of the M3UA static route identification is configured


in the resource management configuration.

The MML Terminal window is opened.

Context

Perform this procedure to configure the mapping relationship between the M3UA static route and the AS. An M3UA static route
can be used by up to 64 SIO-locating-ASs. Otherwise, configuring
more M3UA static routes is required.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the M3UA static route. The command is ADD M3UART.
Table 61 describes the main parameters in the ADD M3UART
command.
TABLE 61 PARAMETERS IN THE ADD M3UART COMMAND
Parameter
Name

Parameter
Description

Instruction

ID

ID of M3UA
static route

It is an optional parameter,
indicating the serial number of the
M3UA static route ID, ranging from
1 to 640. In general, it is the same
as the AS ID.

Confidential and Proprietary Information of ZTE CORPORATION

155

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction

ASID

AS ID

It is a mandatory parameter,
corresponding to the AS ID
specified in the ADD AS command.
Nature: routes are directly sorted
according by the ASP marshalling
sequence in the routing table.

MODE

Alignment
mode of
routes.
Options
include

BYTURNS

LOCAL

NATURE

Local: It is unnecessary to realize


the algorithm in the background.
The background just needs to make
the alignment according to the
Nature option.
BYTURNS: in the routing table,
the routes at the odd-bit position
are sorted by the serial number of
the activated ASP, and the routes
at the even-bit position are sorted
inversely by the serial number of
the activated ASP
The default is BYTURNS.

NAME

Alias

It is a mandatory parameter defined


by a user, with a length ranging
from 1 to 50 characters.

Example: Create an M3UA static route for Mc interface with


the following requirements.

MGW office ID: 101

M3UA static route ID: 1

AS ID: 1

User alias: MGW101.

The specific command is as follows.


ADD M3UART:ID=1,ASID=1,MODE=BYTURNS,NAME="MG
W101";
END OF STEPS

Creating the SIO-Locating-AS


Prerequisites

Context

156

Before the operation, it is required to confirm:

The M3UA static route configuration is completed.

The range of the SIO-locating-AS configuration ID is configured


in the resource management configuration.

The MML Terminal window is opened.

The configuration of SIO-locating-AS is used to locate one service


to a routing table that is maintained by the ASP under the AS. On
MSCS, H248 protocol is generally configured between MSCS and

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 5 MSCS-MGW Interconnection Data Configuration

MGW, and ISUP, TUP, and SCCP protocols are configured between
MSCS and other adjacent offices that are switched by MGW.
A routing key describes a set of No.7 signaling parameters and
parameter values. The corresponded AS is selected according to
the message attributes, thus to select a route for the message.
The message attributes include DPC+NET+OPC+SIO. The DPC
represents the destination SPC, the NET represents the network
type, OPC represents the original SPC, and the SIO represents
the service information octet.
Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the SIO-locating-AS. The command is ADD SIOLOCAS.
Table 62 describes the main parameters in the ADD SIOLO
CAS command.
TABLE 62 PARAMETERS IN THE ADD SIOLOCAS COMMAND
Parameter
Name

Parameter
Description

Instruction

ID

SIOlocation-AS ID

It is an optional parameter,
indicating the serial number of
SIO-locating-AS, ranging from 1 to
4096. In general, it is the same as
the AS ID.

NAME

Alias

It is a mandatory parameter, which


is the alias customized by the user.

Service
indication.
Options include

SIO

OFCID

NULL

TUP

ISUP

BICC

H.248

ALCAP

SCCP

PCA

NNSF

Destination
adjacent office
ID

It is a mandatory parameter,
indicating the subscriber type
belonged by the transmitted
message. Different user types can
be located to the same AS under
the precondition that the MS must
support these user types
Select H.248 for Mc interface,
BICC for Nc interface, SCCP for
the RNC or BSC office transferred
through MGW, and TUP or ISUP
for the 2G MSC/PSTN office
transferred through MGW.

It is a mandatory parameter,
indicating the adjacent office ID
corresponded by the destination
signaling point of the M3UA.
It needs to associate with the
adjacent office ID in the adjacent
office configuration.

Confidential and Proprietary Information of ZTE CORPORATION

157

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction

OPOFCID

Original
adjacent office
ID

It is the adjacent office ID


corresponding to the M3UA
originating signaling point. If
0 (indicating the local office)
is selected, it indicates that
the message is sent from the
local office, and the routing
context is routed according to
DPC+NET+OPC+SIO. If 65535
(invalid) is selected, it indicates
that the OPC field is invalid, and
the routing context is routed
according to DPC+NET+SIO

PCM

PCM system
number

It is an optional parameter. It
ranges from 0 to 65535, with a
default of 65535 (invalid).

RT1

RT2

ID 1 of M3UA
static route

ID 2 of M3UA
static route

It corresponds to the ID
specified in the M3UA static
route configuration. RT1 is a
mandatory parameter. In general,
RT1 is required. When the
optimum route mode is adopted,
RT1 is set as an active route, and
RT2 is set as a standby route.

Example: Create SIO-locating-AS between MSCS and MGW


with the following requirements.

MGW office ID: 101

Destination adjacent office ID: 101

Service indication: H.248

M3UA static route ID: 1.

The specific command is as follows.


ADD SIOLOCAS:ID=1,NAME="MGW-H248",SIO=H248,OF
CID=101,OPOFCID=65535,PCM=65535,RT1=1,RT2=0;
END OF STEPS

H.248 Configuration
Overview
Description

158

H.248 protocol is only used on Mc interface. It provides the following functions.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 5 MSCS-MGW Interconnection Data Configuration

Configuration
Flow

Under the control of MGC, it can establish, modify and release


the media channel in the MG, and can control the attributes of
bearer and user plane.

It reports the events in the MG to the MGC.

It maintains the office and terminal status between MGC and


MG.

Figure 50 shows the configuration flow of H.248 protocol.


FIGURE 50 CONFIGURATION FLOW

Flow Description

The H.248 configuration procedures are as follows:


Steps

Operations

Instructions

Command

Creating MGC
static data

Cofigure the data


related to the
MGCF and H.248.

ADD MGCSCFG

Creating an
MGW static data
template

Create the
template used
by the MGW
static data
configuration.

ADD MGSTPL

Confidential and Proprietary Information of ZTE CORPORATION

159

ZXWN MSCS Data Configuration Guide(MSCS)

Steps

Operations

Instructions

Command

Creating MGW
static data

Create the static


data for each
IM-MGW under
the MGCF.

ADD MGSCFG

Creating a TID
analyzer

The TID analysis


configuration is
necessary for
the H.248 server
to perform the
character string
conversion of
the CIC. Nomally
adopt the default
configuration.

ADD TIDANL

Creating a TID
analysis entry

Create a
TID analyzer
entrance.
Nomally adopt
the default
configuration.

ADD TIDENTR

Creating MGC Static Data


Prerequisites

Before the operation, it is required to confirm:

The data configuration of the local office is completed.

The MML Terminal window is opened.

Context

Perform this procedure to set the data related to the MSCS and
H.248.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the MGC static data. The command is ADD MGCSCFG.
Table 63 describes the main parameters in the ADD MGCSCFG
command.
TABLE 63 PARAMETERS IN THE ADD MGCSCFG COMMAND
Parameter
Name

MEGACO

160

Parameter
Description

Instruction

MEGACO version
number

It is an optional parameter.
Select the supported MEGACO
version number, which must be
consistent with that negotiated
with the MGW. The default value
is 1

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 5 MSCS-MGW Interconnection Data Configuration

Parameter
Name

Parameter
Description

Instruction

ACTTM

Service activation
detection
timer(s)

It is an optional parameter,
ranging from 0 to 3600, with a
default of 600

ACTCHK

Service activation
detection switch

It is an optional parameter,
being activated by default.

WAITTM

MGW answer
waiting timer
(ms)

It is an optional parameter,
ranging from 0 to 65535, with a
default of 7800

PTRYNUM

PEND retry
times(t)

It is an optional parameter,
ranging from 1 to 255, with a
default of 5

PTRYTM

PEND retry time


(ms)

It is an optional parameter,
ranging from 0 to 65535, with a
default of 4000

CTXLIVETM

Context live
time(s)

It is an optional parameter,
ranging from 0 to 65535, with a
default of 1200

Alias

It is an optional parameter,
ranging from 0 to 50 characters.
It may be the same as the office
name

NAME

Example: To create the MGC static data of an MSCS office with


all the parameters adopting default value, the specific command is as follows.
ADD MGCSCFG:MEGACO=1,ACTTM=600,ACTCHK=ON,W
AITTM=7800,PTRYNUM=5,PTRYTM=4000,CTXLIVETM=1
200,MGACTTM=600;
END OF STEPS

Creating an MGW Static Data


Template
Prerequisites

Before the operation, it is required to confirm:

The data configuration of the local office is completed.

The MML Terminal window is opened.

Context

Perform this procedure to set the template used by the MGW static
data configuration.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.

Confidential and Proprietary Information of ZTE CORPORATION

161

ZXWN MSCS Data Configuration Guide(MSCS)

SET:NEID=11;
2. Create an MGW static data template. The command is ADD
MGSTPL.
Table 64 describes the main parameters in the ADD MGSTPL
command.
TABLE 64 PARAMETERS IN THE ADD MGSTPL COMMAND
Parameter Name

Parameter
Description

Instruction

NAME

Alias

This is a mandatory parameter


with a length ranging from
1 to 50 characters. It can
be consistent with the office
name.

ID

Static data template


number

The number of a template,


ranging from 1 to 255

MEGACO

MEGACO version
number

This parameter must be


consistent with that negotiated
with the MGW.

ACTCHK

Gateway activation
detection switch

It is configured as ON by
default

PRTTM

Transient protection
timer (s)

It ranges from 1 to 180. Type


the default value 10

PRT

Transient protection
switch

It is configured as ON by
default.

PENDTM

Interval of PEND
messages (ms)

It ranges from 0 to 3600, with


a default of 200

LNGTM

Maximum existence
time (ms)

It ranges from 0 to 65535,


with a default of 15000

RTRNTM

Retransmission
timer (ms)

It ranges from 0 to 65535,


with a default of 3800

MTRNNUM

Maximum
transmission times

It ranges from 0 to 15, with a


default of 1

TRNMD

Retransmission
mode

CTYPE

H.248 protocol
coding mode

FIXED:
Duration
changeable

UNFIXED:
changeable

un-

Duration

It must be consistent with that


negotiated with the MGW data
configuration

Example: Create an MGW static data template with the following requirements.

162

Template ID: 1

User name: MGW101

Other parameters: default value.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 5 MSCS-MGW Interconnection Data Configuration

The specific command is as follows.


ADD MGSTPL:NAME="MGW101",ID=1,MEGACO=1,ACTC
HK=ON,PRTTM=10,PRT=ON,PENDTM=200,LNGTM=1500
0,RTRNTM=3800,MTRNNUM=1,TRNMD=UNFIXED,CTYPE
=TEXT;
END OF STEPS

Creating MGW Static Data


Prerequisites

Before the operation, it is required to confirm:

The MGW topological node is configured.

The MGW static data template is configured.

The MSCS voice batch processing is finished.

The MML Terminal window is opened.

Context

Perform this procedure to configure the static data for each MGW
under the MSCS.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create MGW static data. The command is ADD MGSCFG.
Table 65 describes the main parameters in the ADD MGSCFG
command.
TABLE 65 PARAMETERS IN THE ADD MGSCFG COMMAND
Parameter Name

Parameter
Description

Instruction

ID

Gateway
number

It is a mandatory parameter for


configuring the node number of
this gateway, ranging from 1 to
2048. It is associated with the node
ID specified by the ADD TOPO
command.

TPLID

Static data
template
number

It is a mandatory parameter
associated with the template
number configured on the MGW
static data template configuration.

TONEID

Service tone
template ID

It is an optional parameter ranging


from 0 to 65535. It uses the
template ID specified in the BADD
STONE command.

Confidential and Proprietary Information of ZTE CORPORATION

163

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter Name

Parameter
Description

Instruction

LANGID

Language
description
template ID

It is an optional parameter, ranging


from 0 to 65535. It uses the
template ID specified in the BADD
STONE command.

NAME

Alias

It is a mandatory parameter,
ranging from 0 to 50 characters. It
may be the same as the office name

BKMGC

Backup MGC
information

It is an optional parameter, with a


default of NULL

PKGLOST

Threshold of
package loss
rate (0.01%)

It is an optional parameter, ranging


from 0 to 10000, with a default of
10

JIT

Threshold
of network
jittering (ms)

It is an optional parameter, ranging


from 0 to 10000, with a default of
50

DELAY

Threshold of
network delay
(ms)

It is an optional parameter, ranging


from 0 to 5000, with a default of
200

MGW tandem

It is an optional parameter for


setting whether this MGW is used
for the tandem function. Type the
default value NO

MGW

Example: Create static data for an MGW with the following


requirements.

MGW office ID: 101

Static configuration template ID: 1

Alias: MGW101.

The specific command is as follows.


ADD MGSCFG:ID=101,NAME="MGW101",TPLID=1,TONE
ID=1,LANGID=1,PKGLOST=10,JIT=50,DELAY=200,MGW
=NO;
END OF STEPS

Creating a TID Analyzer


Prerequisites

Context

164

Before the operation, it is required to confirm:

The data configuration of the local office is completed.

The MML Terminal window is opened.

The TID analysis configuration is necessary for the H.248 server


to perform the character string conversion of the CIC. The H.248
server converts the CIC on the server to the corresponding character string according to the mode configured by the TID analysis.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 5 MSCS-MGW Interconnection Data Configuration

Then it sends this character string to the gateway's H.248 for analyzing and operating the corresponded CIC. Since the form of the
terminals used by the Mc interface is relatively fixed currently, you
may adopt the default configuration.
Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the TID analyzer. The command is ADD TIDANL.
Table 66 describes the main parameters in the ADD TIDANL
command.
TABLE 66 PARAMETERS IN THE ADD TIDANL COMMAND
Parameter Name

Parameter
Description

Instruction

User alias

It is a mandatory parameter,
ranging from 1 to 50
characters. It may be the
same as the office name.

PREV

TID analyzer index

It is an optional parameter.
It is the global number of
the current analyzer for TID
analyzer entry to use, ranging
from 1 to 255.

TIDPFX

TID prefix

It is an optional parameter with


a default of TDM

NAME

It is an optional parameter,
with a default of TRUNK (trunk
type).

TAG

Analysis result flag.


Options include
USER, TRUNK, RTP,
ATM, ROOT and
PCM+IDX.

PCMSPR

PCM flag

It is an optional parameter,
with a default of .

IDXSPR

IDX flag

It is an optional parameter,
with a default of /.

PCMPOS1

PCM start location

It is an optional parameter,
ranging from 0 to 255, with a
default of 1, indicating that the
PCM number starts from the
first digit of the PCM flag.

PCMPOS2

PCM end location

It is an optional parameter,
ranging from 0 to 255, with a
default of 0. Since there is a

Example: TDM_5/1 is a
trunk terminal form. TDM is
the TID prefix, _ is the PCM
separation mark, 5 is the PCM
number, "/ is the IDX (time
slot index) is the separation
mark, and 1 is the time slot
number

Confidential and Proprietary Information of ZTE CORPORATION

165

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter Name

Parameter
Description

Instruction
PCM flag, the End Location is
meaningless.

IDXPOS1

IDXPOS2

IDX start location

It is an optional parameter,
ranging from 0 to 255, with a
default of 1, indicating that the
time slot number starts from
the first digit of the IDX flag.

IDX end location

It is an optional parameter,
ranging from 0 to 255, with a
default of 0. Since there is an
IDX flag, the End Location is
meaningless.

Example: Create a TID analyzer with the following requirements.

MGW office ID: 101

TID index: 1

Alias: MGW101

Other parameters: default value.

The command is:


ADD
TIDANL:NAME="MGW101",PREV=1,TIDPFX="TDM
",TAG=TRUNK,PCMSPR="_",IDXSPR="/",PCMPOS1=1,PC
MPOS2=0,IDXPOS1=1,IDXPOS2=0;
END OF STEPS

Creating a TID Analyzer Entry


Prerequisites

Context
Steps

Before the operation, it is required to confirm:

The MGW topological node is configured.

The TID analyzer configuration is completed.

The MML Terminal window is opened.

Perform this procedure to configure a TID analyzer entry.


1. If no exchange is specified, execute command SET on the MML
Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create a TID analyzer entry. The command is ADD TIDENTR.
Table 67 describes the main parameters in the ADD TIDENTR
command.

166

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 5 MSCS-MGW Interconnection Data Configuration

TABLE 67 PARAMETERS IN THE ADD TIDENTR COMMAND


Parameter
Name

Parameter
Description

Instruction

ND

Gateway

It is a mandatory parameter. It is the


node ID allocated by the topological
node configuration.

TIDENTID

TID analyzer
index

It is a mandatory parameter
associating the TID analyzer ID
specified in the TID analyzer
configuration.

TIDTPLID

TID template
number

By default, the system already


creates a TID template whose ID is
1. You may query it with the SHOW
TIDTPL command.

User Alias

It is a mandatory parameter with


a length ranging from 0 to 50
characters. It may be the same as
the office name.

NAME

Example: Create a TID analyzer entry with the following requirements.

MGW office ID: 101

TID analyzer index: 1

TID template ID: 1

Alias: MGW101.

The specific command is as follows.


ADD TIDENTR:ND=101,TIDENTID=1,TIDTPLID=1,NAME
="MGW101";
END OF STEPS

Confidential and Proprietary Information of ZTE CORPORATION

167

ZXWN MSCS Data Configuration Guide(MSCS)

This page is intentionally blank.

168

Confidential and Proprietary Information of ZTE CORPORATION

Chapter

MSCS-Other-Exchange
Interconnection Data
Configuration
Table of Contents
Networking Mode............................................................. 169
Office Interconnection in IP Domain ................................... 170
TDM Office Interconnection ............................................... 186

Networking Mode
Overview

When MSCS is interconnected with the equipment (such as HLR,


SGSN, MSCS, 2G MSC/PSTN) at the network side, the interfaces
between them fall into TDM-type or IP-type according to different bearer modes, as described in Table 68. These interfaces may
also fall into direct-associated mode and quasi-associated mode
according to their connection method. You should select the corresponding configuration method according to the actual networking
condition.
TABLE 68 BEARER MODES OF MAIN INTERFACES
Interconnected
Equipment

Interface

Bearer Mode

MSCS

Nc

IP

SGSN

Gs

TDM/IP

HLR

TDM/IP

2G MSC/PSTN

Ai

TDM/IP

Take the interconnection between MSC and MSCS/MGW for example. When the traffic bearer is TDM bearer or IP bearer, MSC is
directly connected with MGW. However, the signaling modes between MSC and MSCS divide into the following three types.
1. MSC is connected with MSCS in TDM bearer mode.
When MSC is interconnected with the MSCS in TDM bearer
mode, they only transmit the narrowband signaling.

Confidential and Proprietary Information of ZTE CORPORATION

169

ZXWN MSCS Data Configuration Guide(MSCS)

i. MSC<->MSCS
MSC is directly associated with MSCS in a TDM bearer
mode.
ii. MSC<->STP<->MSCS
MSC is quasi-associated with MSCS through STP in TDM
bearer mode.
This method is applicable to the interconnection between two
devices in the circuit domain, which requires configuring the
narrow-band signaling processing board SPB on MSCS.
2. MSC is connected with MSCS in an IP bearer mode.
MSC is directly connected with MSCS in an IP bearer mode.
The signaling between them is transmitted through SIGTRAN.
The upper-layer signaling, such as BICC, is borne through
M3UA/SCTP or SCTP. This method is applicable to the interconnection between two devices in the IP domain.
3. MSC is connected with MSCS in IP bearer and TDM bearer
modes.
The signaling adaptation between MSC and MSCS is implemented through an intermediate node, which is MGW usually.
The signaling is transmitted by the path of MSC<->MGW<>MSCS, where the narrow-band signaling is transmitted between MSC and MGW, and SIGTRAN is transmitted between
MGW and MSCS.
The signaling may also be switched on MGW in M3UA or M2UA
mode.

When MSCS and MGW adopt different signaling points,


M3UA transfer mode is usually adopted.
When MSCS and MGW adopt the same signaling point,
M3UA proxy mode is usually adopted.
When MSCS and MGW adopt the same signaling point, and
MSCS manages several MGWs that are all connected with
MSCS, M2UA transfer mode may be adopted.

Office Interconnection in IP
Domain
Overview
Introduction

This section describes the procedure for configuring the office interconnection in the IP domain.
There are the following three interconnection modes in the IP domain.
1. Direct-associated office in the IP domain
The office is directly connected with MSCS in IP bearer mode.

170

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 6 MSCS-Other-Exchange Interconnection Data Configuration

2. M3UA-transferred office
MSCS and its opposite-end office provide IP and TDM bearers respectively. The signaling between them is transferred by
MGW in M3UA mode.
3. M2UA-transferred office
MSCS and its opposite-end office provide IP and TDM bearers respectively. The signaling between them is transferred by
MGW in M2UA mode.

Direct-Associated Office
Configuration in IP Domain
Overview
Configuration
Description

The direct-associated office in the IP domain is the office directly


connected with MSCS in the IP bearer mode. For example, two
MSCSs are connected through an Nc interface.

Configuration
Flow

Figure 51 shows the flow of configuring a direct-associated office


in the IP domain.
FIGURE 51 FLOW OF CONFIGURING A DIRECT-ASSOCIATED
OFFICE IN IP DOMAIN

Flow Description

Perform the following steps.

Confidential and Proprietary Information of ZTE CORPORATION

171

ZXWN MSCS Data Configuration Guide(MSCS)

Steps

Operations

Configuration Description

Creating an Adjacent
Office

Create other interconnected


office at the network side,
except for MGW. Select a
different adjacent office type.

Creating an MSCS
Topology Node

The topological node of the


opposite-end MSCS office
is configured during the Nc
interface configuration.

SIGTRAN Configuration

It is similar to the SIGTRAN


configuration on the Mc
interface, refer to Overview

Configuring an Adjacent Office


Prerequisites

Before the operation, it is required to confirm:

The signaling interworking data planning and negotiation between MSCS and other office are completed.

The data configuration of local office is completed.

The MML Terminal window is opened.

Context

Perform this procedure to configure the basic information of an


interconnected adjacent office.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Configure an adjacent office. The command is ADD ADJOFC.
describes the main parameters in the ADD ADJOFC command.
Parameter
Name

172

Parameter
Description

Instruction

ID

Office ID

It is a mandatory parameter.
It is the identification number
of the adjacent office, ranging
from 1 to 3000. It is usually
configured as the exchange ID
of the adjacent office during
the all-network planning

NAME

Alias

It is a mandatory parameter,
which is user-defined alias

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 6 MSCS-Other-Exchange Interconnection Data Configuration

Parameter
Name

Parameter
Description

Instruction

Network type

It is a mandatory parameter,
indicating the network type of
the SPC used for connecting
the local office to the adjacent
office when the local office
is configured with several
signaling points. The default
is the network type of this SP
when there is only one SP in
the local office.

OFCTYPE

Office type

It is a mandatory parameter.
Refer to Table 69 for the
configuration of adjacent office
at the network side.

SPCFMT

Signaling point
code format

TRIPLE_DEC is selected by
default.

SPCTYPE

Signaling point
code type

DPC

Signaling point
code

It is a mandatory parameter.
It is selected according to the
SPC type of the adjacent office.
In China, all the NEs adopt
24-bit SPC, except for BSC that
adopts 14-bit SPC. Configure it
according to the signaling point
planning.

NET

Area code

It is an optional parameter,
designating the area code
of this adjacent office. This
configuration has impact on the
area code added by the calling
number.

ASSOTYPE

Association Type

It is an optional parameter.
Select AM_SURE (directassociated mode) or
AM_QUASI (quasi-associated
mode) according to the
networking conditions.

SPTYPE

Signaling point
type, including
SEP, STP, and
STEP

Select SEP (signaling end


point), STEP (signaling
transfer/end point) or STP
(signaling transfer point)
according to the role of the
adjacent office in the signaling
network.

RC

Confidential and Proprietary Information of ZTE CORPORATION

173

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction

Subservice
function,
including

INTERNAT
IONAL(In
ternational
signaling
point code)

INTERN
ATIONAL
STANDBY(I
nternational
standby
signaling
point code)

SSF

NATIONAL
(National
signaling
point code)

NATIONAL
STANDBY
(National
standby
signaling
point code).

It is an optional parameter. In
general, select NATIONAL for
domestic use.

Office Attribute,
including:
TAG

ISNI (Has ISNI


Function)
TRANS (Translate
Node)

It is an optional parameter

TEST (Need Test


Info:0X02/0X01)

TEST

Test flag

It is an optional parameter, for


setting whether the MTP3 link
actively initiates the link test
after entering in the service
status. It is selected by default.
It is an optional parameter with
a default of NO. It is used for
SCCP to judge whether to use
the LUDT message.

BANDFLAG

Broadband
attribute

The maximum length of a


broadband link message
is 4,000, and that of a
narrowband link message
is 255. Because the MTP
layer does not have the
segmentation function, the
incorrect configuration of this
parameter probably causes the
long packet to be discarded.
Select this parameter when
all the links between two SPs

174

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 6 MSCS-Other-Exchange Interconnection Data Configuration

Parameter
Name

Parameter
Description

Instruction
are SIGTRAN or ATM signaling
links.

Protocol types,
including:

CHINA
(China)

ITU (International Telecommunications Union)

ANSI
(American
National
Standards
Institute).

PRTCTYPE

CLST

Cluster ID

It is an optional parameter.
CHINA and ITU are used for
the NO.7 signaling networking
of the ITU standards. ANSI
is used for the No.7 signaling
networking of the American
standards.

It is an optional parameter.
The cluster number should
be configured in ADD CLST.
The parameter ranges from
0 to 65535, with a default of
65535.

Office Info,
including:

CIC_PCM
(CIC starts
the load
sharing
according to
the PCM code
mode)

BLOCK
(Manual block
status)

EVEN_CIC
(The office
controls the
even CIC
when CIC
resource
contention
occurs)

INFO

CALLING(Calling
transform is
allowed)

CALLED
(Called
transform is
allowed)

MOD24_CIC
(CIC mode
with 24
mode)

It is an optional parameter,
with a default of CIC_PCM(CIC
using PCM Code Mode Starts
Load Control)

Confidential and Proprietary Information of ZTE CORPORATION

175

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

RELATEDOFC1

Instruction

TEST
(Dynamic
test)

Related office ID

It is an optional parameter,
ranging from 0 from 3000

Office extend info,


including

SIGBRDCST
(Support
Signaling
Broadcast
Message)

MTP
(Hongkong
MTP
Standard)

DUPU (
Screen DUPU
message)

SUA_REC_
DT1 (Receive
SUA message
and handle
it as DT1
message)

INFOEX

SUA_SND_DT1 (Send
SUA message
and handle
it as DT1
message
without SN.)

OPEN_TG_RES (Open
outter trunk
group resource)

It is an optional parameter

TABLE 69 ADJACENT OFFICE ATTRIBUTES

176

Adjacent Office

Adjacent office type

Level-1 tandem office

DOMTOLL and TMSC1

Level-2 tandem office

DOMTOLL and TMSC2

Soft-switched toll tandem office

DOMTOLL and TMSCS1

Soft-switched toll tandem office


(CMN)

DOMTOLL, TMSCS1, and CMN

MSC end office (local)

LOCAL, DOMTOLL, OA, and


MSCSERVER

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 6 MSCS-Other-Exchange Interconnection Data Configuration

Adjacent Office

Adjacent office type

Gateway office (local)

LOCAL, DOMTOLL, OA, and


GMSCSERVER

PSTN office

LOCAL, DOMTOLL, and PSTN

HLR

HLR/HLRe

STP

MSCSERVER

SCP

SCP/SCPe

Independent IP

LOCAL and DOMTOLL

Color ring back tone center

LOCAL and DOMTOLL

Dual-homing adjacent office

DHCTRL

SGSN

SGSN

For example, configure the HLR adjacent office during TDM


connection. The office ID is 104, the network type is 1, the
signaling point code is 20.250.31, the office type is HLR/HLRe,
and the domain type is SCN. For the other parameters, select
the default value. the command is as follows:
ADD ADJOFC:ID=104,NAME="HLR",NET=1,OFCTYPE="H
LR/HLRe",SPCFMT=TRIPLE_DEC,SPCTYPE=24,DPC="20.25
0.31",RC="25",ASSOTYPE=AM_SURE,SPTYPE=SEP,SSF=N
ATIONAL,SUBPROTTYPE=DEFAULT,TEST=YES,BANDFLAG
=NO,PRTCTYPE=CHINA,CLST=65535,INFO="CIC_PCM",RE
LATEDOFC1=0;
For example, configure the MSCS adjacent office. The network type is 1, the alias is MSCS105, the signaling point code
is 20.250.1 the signaling point code format is 24, the association type is AM_SURE, and the office type is DOMTOLL&LOCAL&MSCSERVER&OA. For other parameters, select the default value. The command is as follows:
ADD ADJOFC:ID=105,NAME="MSCS105",NET=1,OFCTYP
E="LOCAL"&"DOMTOLL"&"OA"&"MSCSERVER",SPCFMT=TRI
PLE_DEC,SPCTYPE=24,DPC="20.250.1",RC="25",ASSOTY
PE=AM_SURE,SPTYPE=SEP,SSF=NATIONAL ,SUBPROTTYP
E=DEFAULT,TEST=YES,BANDFLAG=YES,PRTCTYPE=CHIN
A,CLST=65535,INFO="CIC_PCM",RELATEDOFC1=0;
END OF STEPS

Creating an MSCS Topology Node


Prerequisites

Before the operation, it is required to confirm:

The voice CODEC template configuration is completed.

The range of topology nodes is created in the resource management.

The MML Terminal window is opened.

Confidential and Proprietary Information of ZTE CORPORATION

177

ZXWN MSCS Data Configuration Guide(MSCS)

Context

For Nc interface, the topology node of the opposite-end MSCS office needs to be configured.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create an MSCS topology node. The command is ADD TOPO.
Table 70 describes the main parameters in the ADD TOPO
command.
TABLE 70 PARAMETERS IN THE ADD TOPO COMMAND
Parameter
Name

Parameter
Description

Instruction

Topological node ID

It is a mandatory
parameter. For identifying
this node with a serial
number, ranging from 1 to
2048. It is recommended
to be consistent with the
office ID of this node

Office ID

It is a mandatory
parameter for specify the
office ID of this topological
node. This parameter
must be defined by the
ADD ADJOFC command
first. Type the MSCS office
ID according to the actual
conditions.

Alias

It is a mandatory
parameter for describing
a topological node, with a
length ranging from 1 to
50 characters.

CODEC identity

It is a mandatory
parameter for specify
the CODEC template used
by this topological node.
This parameter must
be defined by the ADD
CODECTPL command
first.

ETYPE

Equipment type

This parameter is used to


specify the NE equipment
type of this topological
node. Select MSCS for an
MSCS device.

PROTTYPE

Protocol type

Select BICC for an Nc


interface.

ID

OFCID

NAME

CODECID

178

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 6 MSCS-Other-Exchange Interconnection Data Configuration

Parameter
Name

IPVER

ATTR

Parameter
Description

Instruction

IP version of the
node

This parameter indicates


the IP protocol version
supported between nodes.
Select IPV4 or IPV6
according to the actual
conditions. Currently, it
is usually configured as
IPV4

Bearer attributes

This parameter is only


valid for the node with the
type of R4GW (MGW).
You need not to configure
it for an MSCS topological
node.

Extended attributes
(tunnel mode),
including:

NOTUNL (None
tunnel mode)

RTUNL (Rapid
tunnel mode)

DTUNL (Delay
tunnel mode)

ATTR2

Signaling transfer
mode, including:
TRFMOD

DTMFTC

MCINTF (Mc
interface signal
transfer mode)
Tandem office send
DTMF use TC mode,
including

NO (No)

YES (Yes)

This parameter sets which


tunnel mode is used for
setting up a bearer when
this node supports the
IP/RTP bearer, with a
default of NOTUNL (None
tunnel mode).

This parameter is used


to set that mode used by
the topology for reporting
the detected CNG or CED
fax signals, with a default
of MCINTF (Mc interface
signal transfer mode).
This parameter designates
whether TC resources are
used during DTMF number
delivery, with a default of
NO

MGW congestion
reporting capability,
including

SMGWCON
(Standard MGW
congestion
event)

CMGWCON
(Custom MGW
congestion
event).

MGWCON

This parameter designates


the MGW congestion
reporting capability, with
a default of SMGWCON
(standard MGW congestion
event).

Example: Create an MSCS topological node with the following


requirements.

MSCS office ID: 12

Equipment type: MSCS

Confidential and Proprietary Information of ZTE CORPORATION

179

ZXWN MSCS Data Configuration Guide(MSCS)

Protocol type: BICC

CODEC ID: 1

Other parameters: Default.

The specific command is as follows.


ADD TOPO:ID=12,OFCID=12,NAME="MSCS12",CODECI
D=1,ETYPE=MSCS,PROTTYPE=BICC,IPVER=IPV4,ATTR2
=NOTUNL,TRFMOD=MCINTF,UPERRCTRL=YES,DTMFTC=N
O,MGWCON=SMGWCON,AUTOFAX=YES,OOBTC=NO,BCUI
D=0,SENDCAP=NO,G711TRAN=NO,BICCDTMF=TRANSPA
RENT,IPBCP2833=BYMGW,BICCDTMPPER=0,AOIPPRO=P
RIVATE;
END OF STEPS

M3UA-Transferred Office
Configuration
Description

MSCS and its opposite-end office provide IP and TDM bearers respectively. The signaling between them is transferred by MGW in
M3UA mode.

Networking mode

Take the quasi-associated networking (M3UA-based) between


MSCS and 2G MSC/PSTN for example. Figure 52 shows its
interface protocol stack.
FIGURE 52 QUASI-ASSOCIATED NETWORKING BETWEEN MSCS
AND 2G MSC/PSTN (BASED ON M3UA)

The connection between MSCS and MGW is in the IP bearer mode,


and the connection between MGW and 2G MSC/PSTN is in the TDM
bearer mode. Therefore, to configure the interworking data between MSCS and 2G MSC/PSTN, you only need to create a 2G
MSC/PSTN adjacent office on the MSCS, and to configure the SIGTRAN data between MSCS and MGW to make the MGW complete
the signaling transit. In this case, the MGW serves as a signaling
gateway, working in a switching mode.

180

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 6 MSCS-Other-Exchange Interconnection Data Configuration

Configuration
Description

Figure 53 shows the flow of configuring an M3UA transit exchange.


FIGURE 53 FLOW OF M3UA TRANSIT EXCHANGE

Perform the
following steps.

Steps

Operations

Configuration
Description

Reference

Creating an
Adjacent
Office

Create other interconnected


office at the network side,
except for MGW. Select a
different adjacent office
type. It is required that
the network type of this
adjacent office is consistent
with the MGW network type
configured for this group of
associations.

Configuring an
Adjacent Office

SIGTRAN
Configuration

Based on the principles


of SCTP Planning, specify
the office ID parameter
in the SIO-locating-AS
configuration to be
consistent with the office
ID of the adjacent office
that is switched through
MGW, when the association
between MGW and MSCS is
configured.

Overview

Confidential and Proprietary Information of ZTE CORPORATION

181

ZXWN MSCS Data Configuration Guide(MSCS)

M2UA-Transferred Office
Configuration
Overview
Description

MSCS and its opposite-end office provide IP and TDM bearers respectively. The signaling between them is transferred by MGW in
M2UA mode.

Networking mode

Take the quasi-associated networking (M2UA-based) between


MSCS and 2G MSC/PSTN as an example. Figure 54 shows its
interface protocol stack.
FIGURE 54 QUASI-ASSOCIATED NETWORKING BETWEEN MSCS
AND 2G MSC/PSTN (BASED ON M2UA)

The connection between MSCS and MGW is in the IP bearer mode,


and the connection between MGW and 2G MSC/PSTN is in the
TDM bearer mode. When the signaling is transferred in the M2UA
mode, MGW serves as SG to only complete the adaptation of the
MTP2-layer protocol, and transparently transmits the MTP3 layer
protocols to the MSCS for processing. Therefore, you only need to
configure the No. 7 signaling data on the MSCS, which are transmitted to the adjacent office.
Configuration flow

182

Figure 55 shows the flow of configuring an M2UA transit exchange.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 6 MSCS-Other-Exchange Interconnection Data Configuration

FIGURE 55 FLOW OF M2UA TRANSIT EXCHANGE

Flow Description

Perform the following steps.

Confidential and Proprietary Information of ZTE CORPORATION

183

ZXWN MSCS Data Configuration Guide(MSCS)

Steps

Operations

Instruction

Reference

Creating an
adjacent
office

Create other
interconnected office
at the network side,
except for MGW.
Select a different
adjacent office type.

Configuring an
Adjacent Office

Creating an
SCTP

OFCID: select the


adjacent office ID
configured in Step 1.

Creating an SCTP

PROT: Select M2UA


4

Creating an
ASP

Creating an ASP

PROT: Select M2UA

Creating an
AS

EXSTCNTXT: No
routing context is
configured

Creating an AS

ASTAG: Select ASP


on MSCS.
ASUP: Select NULL

Creating a
signaling link
set

Select the type


of this signaling
link set according
toits signaling link
type. In general,
select N64 (64K
narrowband link
set).

Creating an
M2UA IP link

Creating an M2UA IP
Link

Creating a
signaling
route

Creating a Signaling
Route

Creating a
sSignaling
office

Creating a Signaling
Office

Creating a Signaling
Link Set

Creating an M2UA IP Link


Prerequisites

184

Before the operation, it is required to confirm:

The signaling link group configuration is completed.

The MML Terminal window is opened.

Context

When MGW forwards signaling in the M2UA mode, the M2UA IP


link connection to the adjacent office should be configured. The
signaling link is accessed through SIPI board, and SIGTRAN protocol is used for transmission.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 6 MSCS-Other-Exchange Interconnection Data Configuration

Example: Select the MSCS exchange with ID as 11 from the


system tree.
SET:NEID=11;
2. Create an M2UA IP link. The command is ADD M2UAIPLNK.
Table 71 describes the main parameters in the ADD M2UAIP
LNK command.
TABLE 71 PARAMETERS IN THE ADD M2UAIPLNK COMMAND
Parameter
Name

Parameter
Description

Instruction

LKSID

Signaling link
set ID

It is a mandatory parameter.
Type the link set No. of this link,
ranging from 1 to 1024. Which
is associated with the ID of the
signaling link set that is created

SLC

Signaling link
set code

It is an optional parameter to
configure the SLC of this signaling
link. It needs to be consistent with
the SLC of the same signaling link
of the opposite-end office

MODULE

SMP module
No.

It is a mandatory parameter. Type


the No. the SMP module that
processes this link, ranging from
1 to 127

Destination AS
ID

It is a mandatory parameter. Type


the AS No. used by this signaling
link, ranging from 1 to 640.In
this case, type the AS ID whose
adaptation layer is M2UA

ID

Link number

It is an optional parameter,
designating the global No. of the
signaling link on the MSCS. It
ranges from 1 to 5000

NAME

Alias

It is a mandatory parameter,
for describing the name of this
signaling link for easy identification

IIDTYPE

Interface ID
type, including INT(Integer Type),
TEXT(Text
Type and
BOTH(Integer And Text
Type)

The parameter indicates the


interface ID type. Currently, only
the integer type is supported.

IID

Interface ID

The parameter ranges from 0 to


4294967295

LOOP

Self loop,
including
options:
NO(Not Self
Loop) and
YES(Self
Loop)

The parameter indicates whether


the link is at a self loop status.

ASID

Confidential and Proprietary Information of ZTE CORPORATION

185

ZXWN MSCS Data Configuration Guide(MSCS)

Example: Create an M2UA IP signaling link connecting to a 2G


MSC office with the following requirements.

Link set ID: 28

SMP module No.: 3

Destination AS ID: 28

Link No.: 28

Alias: 2GMSC

ID of it in the signaling link set: 0

Other parameters: default.

The specific command is as follows.


ADD M2UAIPLNK:LKSID=28,SLC=0,MODULE=3,ASID=2
8,ID=28,NAME="2GMSC",IIDTYPE=INT,LOOP=NO;
END OF STEPS

TDM Office Interconnection


Overview

186

Description

TDM office refers to the office connecting with MSCS through TDM
bearer, including SCP, HLR, SGSN and other offices that connect
to the MSCS. To configure a direct-associated office, you need to
configure signaling link set, signaling link, signaling route, and signaling office. To configure a quasi-associated office, you only need
to configure the signaling office.

Configuration
Flow

Figure 56 shows the flow of configuring the interconnection data


between MSCS and TDM.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 6 MSCS-Other-Exchange Interconnection Data Configuration

FIGURE 56 TDM OFFICE INTERCONNECTION CONFIGURATION


FLOW

Flow Description

Perform the following steps.


Steps

Operations

Instructions

Command

Creating a
signaling link set

Configure a
narrowband
signaling link set
to the adjacent
office.

ADD N7LKS

Creating an
SPB-accessed
signaling Link

Configure a
narrowband
signaling link
to the adjacent
office.

ADD N7LNKE1

Confidential and Proprietary Information of ZTE CORPORATION

187

ZXWN MSCS Data Configuration Guide(MSCS)

Steps

Operations

Instructions

Command

Creating a
signaling route

The signaling
routing
configuration is
used for specifying
the signaling link
set to be selected
and the method
when the signaling
selects a route.

ADD N7ROUTE

Creating a
signaling office

Configure the
correspondence
between the
destination
signaling office
and the signaling
route.

ADD N7OFC

Creating a Signaling Link Set


Prerequisites

Context

Before the operation, it is required to confirm:

The adjacent office configuration is completed.

The data configuration of local office is completed.

The range of signaling link set is configured in the resource


management.

The MML Terminal window is opened.

Perform this procedure to configure a narrowband signaling link set


to the adjacent office, including 64k signaling link set, 2M signaling
link set, N64k signaling link set.
When configuring the signaling link set connected by TDM, you
may select N64, NN64, and N2M.

Steps

64k indicates that the narrow-band signaling link in this signaling link set only seizures one time slot on one E1 line, with
64 Kbps bandwidth.

N64K indicates that the narrow-band signaling link in this


signaling link set seizures N consecutive time slots on one E1
line (8n25).

2M indicates that the narrow-band signaling link in this signaling link set seizures all 31 time slots on one E1 line (time slot
0 is unavailable), with 1.984Mbps bandwidth.

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create a signaling link set. The command is ADD N7LKS.

188

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 6 MSCS-Other-Exchange Interconnection Data Configuration

Table 72 describes the main parameters in the ADD N7LKS


command.
TABLE 72 PARAMETERS IN THE ADD N7LKS COMMAND
Parameter
Name

OFCID

ID

NAME

TYPE

Parameter Description

Instruction

Direct-associated office
of the signaling link set

It is a mandatory
parameter. Type the
adjacent office ID of
this signaling link set,
which is specified in
the adjacent office
configuration.

Signaling link set ID

It is a mandatory
parameter. It
designates the signaling
link set No. for
distinguishing signaling
link sets, ranging from
1 to 1024.

Alias

It is a mandatory
parameter describing
the name of this
signaling link set for
easy identification.

Signaling link set type

This parameter indicates


the types of the
signaling links in this
signaling link set. Select
N64 for a 64K signaling
link, NN64 for an
n64K signaling link,
and N2M for a 2M
signaling link.

Link error revision,


including:

LECM

BASIC (basic error


revision, transit delay
15 ms): all the signaling
links use this method
for relatively short
transit delay, except for
satellite links.
PCR (Preventive Cyclic
Retransmission: transit
delay15 ms): Satellite
links use this method
for it has a relatively
long transit delay.

This parameter
designates the error
correction method of
the signaling links in
this set. In general,
select BASIC. In
general,BASICis
selected when the
line transit delay is less
than 15ms, and PCR is
selected when the line
transit delay is greater
than 15ms.For a 2M
signaling link, BASIC
must be selected. This
parameter shall be
consistent with that
of the opposite end
through negotiation.

Example: Create a signaling link set connected by HLR office


104 with the following requirements.

HLR office ID: 1

Confidential and Proprietary Information of ZTE CORPORATION

189

ZXWN MSCS Data Configuration Guide(MSCS)

Signaling link set No.: 1

Group type: 64K narrowband link set

Link error revision: Basic error revision

Alias: HLR-1.

The specific command is as follows.


ADD N7LKS:OFCID=1,TYPE=N64,ID=1,LECM=BASIC,NA
ME="HLR-1";
END OF STEPS

Creating an SPB-Accessed Signaling


Link
Prerequisites

Context

Before the operation, it is required to confirm:

The signaling link group configuration is completed.

The MML Terminal window is opened.

Signaling link is the physical channel carrying signaling messages.


The narrow-band signaling link used on the MSCS is an SPB-accessed signaling link.

Note:
In order to evenly distribute the traffic load to an office on each
link that is selected in the dynamic routing table corresponded
by the SLC, usually the number of links in a link set to a directassociated office is configured as 2n, namely, 2, 4, 8, or 16 links
are configured. Make sure that load onto each link is not too heavy
to cause it breakdown.
Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create an SPB-accessed signaling link. The command is ADD
N7LNKE1
Table 73 describes the main parameters in the ADD N7LNKE1
command.

190

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 6 MSCS-Other-Exchange Interconnection Data Configuration

TABLE 73 PARAMETERS IN THE ADD N7LNKE1 COMMAND


Parameter
Name

Parameter
Description

Instructions

Signaling link
set ID

It is a mandatory parameter,
designating the signaling link
set No. of this signaling link.
It is associated with the ID of
the signaling link set that is
configured.

Signaling Link
Code (SLC)

This parameter designates the


SLC of this signaling link, ranging
from 0 to 15. It needs to
be consistent with the SLC of
the same signaling link of the
opposite-end office.

MODULE

Signaling
management
module No.

It is a mandatory parameter.
Select a signaling module.
Several signaling links of the
same office should be configured
to different physical boards.
In addition, the signaling links
managed by each SMP module
should share load.

SPBUNT

SPB unit
number

CPU

CPU ID of SPB

LKSID

SLC

E1 number of
the SPB board

E1

It is a mandatory parameter.
The CPU ID ranges from 1 to 4.
Several signaling links of the same
office should be configured to
different SPB boards. In addition,
the signaling links processed by
the CPUs on SPB board should
share load.
This parameter designates the
number of the E1 where the
signaling link is located, ranging
from 9. By default, it is numbered
from 9
64k signaling link: the time slot
number of the signaling link is 16

Start timeslot
number of E1

TS

N64k signaling link: its start


time slot ranges from 1 to 31
2M signaling link: Its start time
slot is 1
Configure the number of the time
slots occupied by the signaling
link.

TSNUM

Quantity of
timeslots

64K signaling link: Its time slot


amount is 1.
N64K signaling link: Its time
slot amount is N.
2M signaling link: Its time slot
amount is 31.

Confidential and Proprietary Information of ZTE CORPORATION

191

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

NAME

Parameter
Description

Instructions

Alias

It is a mandatory parameter
designating the name of
the signaling link for easy
identification, with a length
ranging from 1 to 50 characters.

Miscellaneous
information,
including:
E1: This
link uses
the E1-type
interface.

INFO

N64KT1:
This link uses
the T1-type
interface, with
64K normal
coding mode.
I64KT1: This
link uses
the T1-type
interface, with
64K reversal
phase coding
mode.

Configure the interface type and


coding mode of this link. In
general, it is an E1 link.

56KT1: This
link uses
the T1-type
interface, with
54K coding
mode.

Example: Create an SPB-accessed signaling link with the following requirements.

Signaling link set No.: 1

Signaling link No.: 0

SMP module No.: 3

Signaling link alias: HLR-1-1

SPB board unit No.: 721

Start time slot number of E1: 9

Time slot amount: 1

Other parameters: default.

The specific command is as follows.


ADD N7LNKE1:LKSID=1,SLC=0,MODULE=3,NAME="HLR1-1",ID=1,SPBUNT=721,CPU=1,E1=9,TS=16,TSNUM=1,L
OOP=NO,INFO=E1,FCPLTHR=255;
END OF STEPS

192

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 6 MSCS-Other-Exchange Interconnection Data Configuration

Creating a Signaling Route


Prerequisites

Before the operation, it is required to confirm:

The signaling link group configuration is completed.

The range of signaling route ID is configured in the resource


management.

The MML Terminal window is opened.

Context

The signaling routing configuration is used for specifying the signaling link set to be selected and the method when the signaling
selects a route. The signaling route to a direct-associated office
only contains the signaling link sets to this office. The signaling
route to a quasi-associated office contains one or two signaling
link sets to the intermediate office.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create a signaling route. The command is ADD N7ROUTE.
Table 74 describes the main parameters in the ADD N7ROUTE
command.
TABLE 74 PARAMETERS IN THE ADD N7ROUTE COMMAND
Parameter
Name

Parameter
Description

Instruction

NAME

Alias

It is a mandatory parameter
designating a signaling route
for easy identification.

Signaling link set 1

The signaling route contains


the first signaling link set.
Type the serial number of the
signaling link set 1.

Signaling link set 2

It is the second signaling


link set contained by the
signaling route. At least
either LKSID1 or LKSID2
is not equal to zero and
contains signaling links. If
only one signaling link set
exists, type 0

Signaling route
number

This parameter designates


the serial number of the
signaling route, ranging from
1 to 2000. When there
is only one signaling link
set, this parameter may be
configured to be consistent
with the signaling link set
number.

LKSID1

LKSID2

ID

Confidential and Proprietary Information of ZTE CORPORATION

193

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction

LPM

Arrangement mode
of signaling link
sets. Refer to Table
75 for its options.

This parameter designates


the rules that should be
obeyed when the signaling
links of two signaling link
sets are sorted. When two
link sets have the same
signaling links, and the total
number is not more than
16, RAND (random order) is
recommended

LPMIN

Arrangement mode
in a signaling link
set. Refer to Table
75 for its options.

This parameter designates


the rules that should be
obeyed when the signaling
links in a signaling link set
are sorted. RAND (random
order) is recommended

MANUAL

Sort manually,
including NO(Need
Not Manual)
and YES(Need
Manual)

The parameter indicates


whether to manually sort the
signaling routes of the two
link groups

Link list

The maximum number


of instance is 16. The
format is <INDEX>-<LINK>,
representing the alignment
order and link number
respectively.

LINKS

TABLE 75 ARRANGEMENT MODE OF SIGNALING SETS

194

Mode

Meanings

Instruction

RAND

Random
arrangement
mode

Random arrangement mode

SLS0

Select On
SLS_BIT0

Selecting links between two


link sets according to Bit 0 of
SLS

SLS1

Select On
SLS_BIT1

Selecting links between two


link sets according to Bit 1 of
SLS

SLS2

Select On
SLS_BIT2

Selecting links between two


link sets according to Bit 2 of
SLS

SLS3

Select On
SLS_BIT3

Selecting links between two


link sets according to Bit 3 of
SLS

SLS01

Select On
SLS_BIT0-1

Selecting links between two


link sets according to Bits 0
and 1 of SLS

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 6 MSCS-Other-Exchange Interconnection Data Configuration

Mode

Meanings

Instruction

SLS12

Select On
SLS_BIT1-2

Selecting links between two


link sets according to Bits 1
and 2 of SLS

SLS23

Select On
SLS_BIT2-3

Selecting links between two


link sets according to Bits 2
and 3 of SLS

Example: Create a signaling route with the following requirements.

Alias: HLR

Signaling link set No.: 1

Signaling route No.: 1

Other parameters: default.

The specific command is as follows.


ADD
N7ROUTE:NAME="HLR",LKSID1=1,LKSID2=0,ID
=1,LPM=RAND,LPMIN=RAND,MANUAL=NO;
END OF STEPS

Creating a Signaling Office


Prerequisites

Before the operation, it is required to confirm:

The signaling route configuration is completed.

The MML Terminal window is opened.

Context

Perform this procedure for configuring the correspondence between the destination signaling office and the signaling route.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create a signaling office. The command is ADD N7OFC.
Table 76 describes the main parameters in the ADD N7OFC
command.

Confidential and Proprietary Information of ZTE CORPORATION

195

ZXWN MSCS Data Configuration Guide(MSCS)

TABLE 76 PARAMETERS IN THE ADD N7OFC COMMAND


Parameter
Name

Parameter Description

Instruction

ID

Signaling route office

It is a mandatory
parameter. Type the
adjacent office No. of
the destination office

RT1

This parameter
designates the serial
number of the direct
route to the destination
adjacent office.

It is a mandatory
parameter. Configure
the serial number of the
direct route to this office,
ranging from 1 to 2000

RT2

Alternate route 1,
indicating the serial
number of the first
alternate route to the
destination adjacent
office.

RT3

Alternate route 2,
indicating the serial
number of the second
alternate route to the
destination adjacent
office. This parameter
is configured when only
the first alternate route
is already configured.

RT4

Alternate route 3,
indicating the serial
number of the third
alternate route to the
destination adjacent
office. This parameter is
configured when only the
second alternate route is
already configured.

NAME

Alias

This parameter ranges


from 0 to 2000.
Select up to three
available alternate
routes according to the
actual conditions. When
there is no alternate
route, configure it as 0.

It is a mandatory
parameter. This
parameter designates
the name of the
signaling office for
easy identification

Example: Create a signaling office to a HLR adjacent office


whose office ID is 1 and the direct-associated route number is
1. The specific command is as follows.
ADD
N7OFC:ID=1,RT1=1,RT2=0,RT3=0,RT4=0,NAME
="HLR";
END OF STEPS

196

Confidential and Proprietary Information of ZTE CORPORATION

Chapter

MSCS-Radio-Office
Interconnection Data
Configuration
Table of Contents
Interconnection with RNC Office ........................................ 197
Interconnection with BSC Office......................................... 213

Interconnection with RNC


Office
Overview
Networking Modes

When MSCS is interconnected with RNC through Iu-CS interface,


there are two networking modes.
1. MSCS<->MGW<->RNC
RNC and MGW are directly associated through ATM, and MSCS
and MGW are connected through an IP bearer. Figure 57 shows
the networking structure and the interface protocols.

Confidential and Proprietary Information of ZTE CORPORATION

197

ZXWN MSCS Data Configuration Guide(MSCS)

FIGURE 57 QUASI-ASSOCIATION BETWEEN MGW AND RNC

The RANAP/SCCP signaling between MSCS and RNC is switched


by MGW. User data between MGW and RNC are transmitted
through AAL2 that is controlled by the ALCAP signaling. MSCS
and MGW can be interconnected with RNC through different
signaling points.
2. MSCS<->RNC MGW<->RNC
RNC can be interconnected with MSCS/MGW through an IP
bearer. Figure 58 shows the networking structure and the interface protocols.
FIGURE 58 DIRECT-ASSOCIATION BETWEEN MGW AND RNC

MSCS is directly connected with RNC through SIGTRAN protocol. User data between MGW and RNC are transmitted through
RTP/UDP/IP. And the RTP session is established, modified and
released through the RANAP signaling on MSCS.MGW is not
configured with a RNC adjacent office when the IP bearer is
adopted.
Configuration
Flow

198

Figure 59 shows the flow of configuring the interconnection between MSCS and RNC through the Iu-CS interface.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 7 MSCS-Radio-Office Interconnection Data Configuration

FIGURE 59 FLOW OF CONFIGURING MSCS-RNC INTERCONNECTION

Flow Description

Perform the following steps to configure the interconnection between MSCS and RNC.
Steps

Operations

Instructions

Commands

Creating the RNC


adjacent office

Configure the
basic information
of the RNC
adjacent office

ADD ADJOFC

Creating RNC office


attributes

Configure
some additive
attributes of the
RNC adjacent
office, thus to
associate the RNC
ID with the RNC
office.

ADD RNCOFC

Creating RNC
topological node

Configure the
adjacent NE
information

ADD TOPO

Confidential and Proprietary Information of ZTE CORPORATION

199

ZXWN MSCS Data Configuration Guide(MSCS)

Steps

Operations

Instructions

Commands

Creating the
topological
relationship between
RNC and MGW

Configure the
topological
relationship
between RNC
and MGW, thus
to associate the
MGW node with
the RNC node.

ADD RNCMGWT
OPO

SIGTRAN
Configuration

When MSCS is
connected to RNC
through MGW and
the association
between MGW
and MSCS is
configured,
you only need
to configure
SIO-locating-AS
according to
the principles
regulated in SCTP
planning. When
MSCS is directly
connected to RNC
through the IP
bearer, you need
to perform the
configuration
related to
SIGTRAN
protocol. Refer
to Overview

Creating an RNC Adjacent Office


Prerequisites

Before the operation, it is required to confirm:

The data configuration of the local office is completed.

The range of adjacent office number is configured in the resource management.

The MML Terminal window is opened.

Context

Perform this procedure for configuring the basic information of the


RNC adjacent office.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the RNC adjacent office. The command is ADD ADJO
FC.
Table 77 describes the main parameters in the ADD ADJOFC
command.

200

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 7 MSCS-Radio-Office Interconnection Data Configuration

TABLE 77 PARAMETERS IN THE ADD ADJOFC COMMAND


Parameter
Name

Parameter
Description

Instruction

ID

Office ID

It is a mandatory parameter,
indicating the identification
number of the adjacent office,
and ranging from 1 to 2048.
It is usually configured as the
exchange ID of the adjacent
office during the all-network
planning.

NAME

Alias

It is a mandatory parameter,
which is the alias customized
by the user.

NET

Network type

It is a mandatory parameter,
indicating the network type of
the SPC used for connecting
the local office to the adjacent
office when the local office is
configured with several SPs.
The default is the network type
of this SP when there is only
one SP in the local office.
It is a mandatory parameter.

OFCTYPE

Adjacent office type

SPCFMT

SPC format

Select TRIPLE_DEC

SPCTYPE

SPC type

It is a mandatory parameter.
Specify it based on the SPC
type of the adjacent office

DPC

SPC

RC

Area code

Type RNC in this case

When the adjacent office type


is RNC, RC must be empty.

Association type,
including

ASSOTYPE

AM_SURE
(direct
connection
mode)

AM_QUASI
(half direct
connection
mode)

It is an optional parameter.
Select AM_QUASI

AM_NONE
(none
connection
mode)

Confidential and Proprietary Information of ZTE CORPORATION

201

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction

Signaling point
type, including
SPTYPE

SEP

STP

STEP

It is an optional parameter.
Select SEP

Subservice
function, including

INTERNATIONAL (International signaling point


code)

INTERNATIONAL
STANDBY
(International
standby signaling point code)

SSF

TEST

NATIONAL
(National
signaling point
code)

NATIONAL
STANDBY
(National
standby
signaling point
code)

Test flag

It is an optional parameter. In
general, select NATIONAL for
domestic use.

It is an optional parameter, for


setting whether the MTP3 link
actively initiates the link test
after entering in the service
status.
It is selected by default.

BANDFLAG

Broadband
attribute

It is an optional parameter.
Select YES when all the links
between two SPs are SIGTRAN
or ATM signaling links.

Protocol types,
including:

CHINA (China)

ITU (International Telecommunications


Union)

ANSI
(American
National
Standards
Institute).

PRTCTYPE

202

Confidential and Proprietary Information of ZTE CORPORATION

It is an optional parameter.
CHINA and ITU are used for
the NO.7 signaling networking
of the ITU standards. ANSI
is used for the No.7 signaling
networking of the American
standards.

Chapter 7 MSCS-Radio-Office Interconnection Data Configuration

Parameter
Name

CLST

Parameter
Description

Instruction

Cluster ID

It is an optional parameter.
The cluster number should
be configured in ADD CLST.
The parameter ranges from
0 to 65535, with a default of
65535.

Office Info,
including:

CIC_PCM (CIC
starts the
load sharing
according to
the PCM code
mode)

BLOCK
(Manual block
status)

EVEN_CIC
(The office
controls the
even CIC when
CIC resource
contention
occurs)

INFO

RELATEDOFC1

CALLING(Calling
transform is allowed)

CALLED
(Called
transform is
allowed)

MOD24_CIC
(CIC mode with
24 mode)

TEST
(Dynamic test)

Related office ID

It is an optional parameter,
with a default of CIC_PCM
(CIC using PCM Code Mode
Starts Load Control)

It is an optional parameter,
ranging from 0 from 3000

Office extend info,


including

INFOEX

SIGBRDCST
(Support
Signaling
Broadcast
Message)

MTP
(Hongkong
MTP Standard)

DUPU (
Screen DUPU
message)

It is an optional parameter

Confidential and Proprietary Information of ZTE CORPORATION

203

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

SUA_REC_
DT1 (Receive
SUA message
and handle it as
DT1 message)

SUA_SND_DT1 (Send
SUA message
and handle it as
DT1 message
without SN.)

OPEN_TG_RES (Open
outter trunk
group resource)

Instruction

Example: Create an RNC adjacent office with the following requirements.

RNC office ID: 100

Network type: 2

User alias: RNC100

Destination SPC: 1.100.1

SPC type: 14-bit

Adjacent office type: RNC

Association type: Quasi-associated mode.

The specific command is as follows.


ADD
ADJOFC:ID=100,NAME="RNC100",NET=2,OFCTYP
E="RNC",SPCFMT=TRIPLE_DEC,SPCTYPE=14,DPC="1.10
0.1",ASSOTYPE=AM_QUASI,SPTYPE=SEP,SSF=NATIONAL
STANDBY,SUBPROTTYPE=DEFAULT,TEST=YES,BANDFLAG
=NO,PRTCTYPE=CHINA,CLST=65535,INFO="CIC_PCM",RE
LATEDOFC1=0;
END OF STEPS

Creating RNC Office Direction


Prerequisites

Context

204

Before the operation, it is required to confirm:

You know the number of the exchange to be configured.

The RNC adjacent office is created.

The MML Terminal window is opened.

Perform this procedure to configure some additive attributes of the


RNC adjacent office, thus to associate the RNCID with the RNC
office.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 7 MSCS-Radio-Office Interconnection Data Configuration

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the RNC office direction. The command is ADD RNCO
FC.
Table 78 describes the main parameters in the ADD RNCOFC
command.
TABLE 78 PARAMETERS IN THE ADD RNCOFC COMMAND
Parameter
Name

Parameter
Description

Instruction
It is a mandatory parameter
ranging from 1 to 256.

OFCID

RNC office ID

It is the RNC office ID


specified in the RNC office
configuration.

MCC

Mobile country code

It is a mandatory parameter,
ranging from 1 to 4
characters. For China,
it is 460.

MNC

Mobile network code

It is a mandatory parameter
with a length ranging from 2
to 3 characters.

RNCID

RNC ID

It is a mandatory parameter,
ranging from 0 to 4095. It is
provided by the RNC side.

RABDLY

RAB Delay(ms)

The parameter ranges from


0 to 65535, with a default of
100

Class A SDU Error


Ratio. The options
include:

ERRRATIO1
(1*10^(-2)

ERRRATIO2
(7*10^(-3)

SDUERA

ERRRATIO3
(1*10^(-3)

ERRRATIO4
(1*10^(-4)

ERRRATIO5
(1*10^(-5)

The default value is


ERRRATIO2 (7*10^(-3)

Confidential and Proprietary Information of ZTE CORPORATION

205

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction

Class A Residual BER.


The options include:

ERRRATIO1
(5*10^(-2))

ERRRATIO2
(1*10^(-2))

ERRRATIO3
(5*10^(-3))

ERRRATIO4
(1*10^(-3))

ERRRATIO5
(1*10^(-4))

ERRRATIO6
(1*10^(-5))

ERRRATIO7
(1*10^(-6))

RBERA

The default value is


ERRRATIO7 (1*10^(-6))

Class B Residual BER.


The options include:

ERRRATIO1
(5*10^(-2))

ERRRATIO2
(1*10^(-2))

ERRRATIO3
(5*10^(-3))

ERRRATIO4
(1*10^(-3))

ERRRATIO5
(1*10^(-4))

ERRRATIO6
(1*10^(-5))

ERRRATIO7
(1*10^(-6))

RBERB

The default value is


ERRRATIO4 (1*10^(-3))

Class C Residual BER.


The options include:

ERRRATIO1
(5*10^(-2))

ERRRATIO2
(1*10^(-2))

ERRRATIO3
(5*10^(-3))

ERRRATIO4
(1*10^(-3))

ERRRATIO5
(1*10^(-4))

ERRRATIO6
(1*10^(-5))

ERRRATIO7
(1*10^(-6))

RBERC

206

Confidential and Proprietary Information of ZTE CORPORATION

The default value is


ERRRATIO3 (5*10^(-3))

Chapter 7 MSCS-Radio-Office Interconnection Data Configuration

Parameter
Name

Parameter
Description

Instruction

Iu Interface Load
Share Mode. The
options include:
SELMGTYPE

ATMADDR

ADDRPLAN

EXCELLENT(Excellent choice
priority)

LOAD(Load share
priority)

RNC ATM Address

ATM Address
Plan, including
E.164(E.164) and
NSAP(NSAP)

The default value is


EXCELLENT (Excellent
choice priority)

It is an optional parameter.
Configure the ATM address
and coding plan of the
corresponding RNC.
ATM address code can adopt
the NSAP that has a fixed
length of 20 bytes) or E.164
(that is an extendable BCD
code).
The configuration here
should be consistent with
the RNC office ID parameters
at the MGW side.

First Rebear Mode.


The options include:

BTRY1

NO(NO RETRY);

BEARER(TRY
OTHER REBEAR
MODES;

MGW(TRY OTHER
MGW)

The default is NO(NO


RETRY)

Second Rebear Mode.


The options include:

BTRY2

RAS

NO(NO RETRY);

BEARER(TRY
OTHER REBEAR
MODES;

MGW(TRY OTHER
MGW)

RNC Office
ReAssignment.
Options include:

NO(NO);

YES(YES)

The default is NO(NO


RETRY)

The default value is NO(NO)

Example: Create the RNC office direction with the following


requirements.

RNC office ID: 100

Confidential and Proprietary Information of ZTE CORPORATION

207

ZXWN MSCS Data Configuration Guide(MSCS)

Mobile country code: 460

Mobile network code: 00

RNC ID: 1

ATM address of RNC: 12.3456.7890.abcd.efff.ffff.ffff.ffff.ffff.ffff.ff


ATM address plan: E164.

The specific command is as follows.


ADD RNCOFC:OFCID=100,MCC="460",MNC="00",RNCID
=1,RABDLY=100,SDUERA=ERRRATIO2,RBERA=ERRRATI
O7,RBERB=ERRRATIO4,RBERC=ERRRATIO3,SELMGTYPE
=EXCELLENT,ATMADDR="12.3456.7890.abcd.efff.ffff.ffff.fff
f.ffff.ffff.ff",ADDRPLAN=E164,BTRY1=NO,BTRY2=NO,RAS
=NO;
END OF STEPS

Creating an RNC Topology Node


Prerequisites

Before the operation, it is required to confirm:

You know the number of the exchange to be configured.

The voice CODEC template is created.

The MML Terminal window is opened.

Context

Perform this procedure to create the adjacent NE information, including equipment type, bearer type and attributes, user plane
version, encoding and decoding template, and other information.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create an RNC topology node. The command is ADD TOPO.
Table 79 describes the main parameters in the ADD TOPO
command.
TABLE 79 PARAMETERS IN THE ADD TOPO COMMAND
Parameter
Name

ID

208

Parameter
Description

Instruction

Topological
node ID

It is a mandatory parameter,
ranging from 1 to 2,048. It is used
for defining a topological node. It
is recommended that this ID is
consistent with the office ID of this
node.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 7 MSCS-Radio-Office Interconnection Data Configuration

Parameter
Name

Parameter
Description

Instruction

OFCID

Office ID

It is a mandatory parameter
for specify the office ID of this
topological node, ranging from 1
to 3,000. This parameter must
be defined by the ADD ADJOFC
command first. Type the RNC office
ID according to actual conditions.

NAME

Alias

It is a mandatory parameter for


naming this topological node, with
a length ranging from 1 to 50
characters.

CODECID

CODEC
identity

It is a mandatory parameter
for specifying the Encoding and
decoding speech Template used
by this topological node. This
parameter must be defined by the
ADD CODECTPL command first.
Type it according to the actual
conditions.

ETYPE

Equipment
type

It is an optional parameter for


specifying the NE type of this
topological node.
Select RNC for an RNC node.

IPVER

IP version of
the node

It is an optional parameter,
indicating the IP protocol version
supported between nodes. Select
IPV4 or IPV6 according to the
actual conditions. In general, it is
set as IPV4

ATTR

Bearer
attributes

This parameter is only valid for


the node with the type of R4GW
(MGW). You need not to configure
it for an RNC topology node.

UPVER

User plane
protocol
version

It is an optional parameter to
regulate the user plane version
of this node, ranging from V1
to V16. It can support one or
more of these user plane versions.
This parameter is only valid for
RNC-type or MGW-type NE.
In general, V2 is selected (meaning
supporting Version 2) according to
the user-plane version supported
by RNC.

Confidential and Proprietary Information of ZTE CORPORATION

209

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction

Extended
attributes
(tunnel
mode),
including

ATTR2

TRFMOD

NOTUNL
(None
tunnel
mode)

RTUNL
(Rapid
tunnel
mode)

DTUNL
(Delay
tunnel
mode)

Transmission
mode,
including
MCINTF (Mc
interface
signal transfer
mode)

This parameter sets which tunnel


mode is used for setting up a
bearer when this node supports
the IP/RTP bearer, with a default of
NOTUNL (None tunnel mode).

This parameter is used to set that


mode used by the topology for
reporting the detected CNG or
CED fax signals, with a default
of MCINTF (Mc interface signal
transfer mode).
YES: The user plane entity
implements error inspection, and
sets the FQC bit position according
to the result. It will transmit all
frames includes the error frames to
the user plane layer. During a call,
the error packet control parameter
delerrsdu=Yes, which is delivered
by the terminal established by
MGW on the Mc interface. The
error packet control parameter
deliveryOfErroneousSDU is YES,
NA, NA during RAB assignment.

UPERRCTRL

Error SDU
control

NO: The user plane entity


implements the error inspection.
It will directly discard the error
frame. During a call, the
error packet control parameter
delerrsdu=No, which is delivered
by the terminal established by
MGW on the Mc interface. The
error packet control parameter
deliveryOfErroneousSDU is NO,
NA, NA during RAB assignment.
INVALIDTION: The user plane
entity does not implement the
error inspection. During a call,
the error packet control parameter
delerrsdu=NA, which is delivered
by the terminal established by
MGW on the Mc interface. The
error packet control parameter
deliveryOfErroneousSDU is NA, NA,
NA during RAB assignment.

210

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 7 MSCS-Radio-Office Interconnection Data Configuration

Parameter
Name

Parameter
Description

Instruction
This parameter regulates the
handling method of the user
plane for error frames. It is only
valid for MGW-type and RNC-type
topological node. The default value
is YES

DTMFTC

Tandem office
send DTMF
use TC mode,
containing two
options: No
and YES

This parameter is used to set


whether the tandem office uses the
TC resources during DTMF number
delivery.
The default value is NO
It contains the following options.

MGWCON

MGW
congestion
reporting
capability

SMGWCON (Standard MGW


congestion event)

CMGWCON (Custom MGW


congestion event).

The default value is SMGWCON.

Example: Create a topology node with the following requirements.

RNC office ID: 100

Topology node ID: 100

Alias: RNC100

CODEC ID: 1

RNC-supported user-plane version: V2.

The specific command is as follows.


ADD TOPO:ID=100,OFCID=100,NAME="RNC100",CODEC
ID=1,ETYPE=RNC,PROTTYPE=H248,DMNAME="RNC",IP
VER=IPV4,UPVER="V2",ATTR2=NOTUNL,TRFMOD=MCINT
F,UPERRCTRL=YES,DTMFTC=NO,MGWCON=SMGWCON,A
UTOFAX=YES,OOBTC=NO,BCUID=0,SENDCAP=NO,G711
TRAN=NO,BICCDTMF=TRANSPARENT,IPBCP2833=BYMG
W,BICCDTMPPER=0,AOIPPRO=PRIVATE;
END OF STEPS

Creating the Topology Relationship


between RNC and MGW
Prerequisites

Before the operation, it is required to confirm:

You know the number of the exchange to be configured.

The RNC topology node is created.

The MML Terminal window is opened.

Confidential and Proprietary Information of ZTE CORPORATION

211

ZXWN MSCS Data Configuration Guide(MSCS)

Context

Perform this procedure to configure the topological relationship


between RNC and MGW, thus to associate the MGW node with the
RNC node.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the topology relationship between RNC and MGW. The
command is ADD RNCMGWTOPO.
Table 80 describes the main parameters in the ADD RNCMG
WTOPO command.
TABLE 80 PARAMETERS IN THE ADD RNCMGWTOPO COMMAND
Parameter
Name

Parameter
Description

Instruction
It is a mandatory parameter,
ranging from 1 to 2048.

MGWID

MGW node ID

RANTYPE

Office type

RANID

RNC/BSC node
number

It is the node ID specified


during the MGW topological
node configuration
It is a mandatory parameter.
Select RNC for RNC access.
It is a mandatory parameter,
ranging from 1 to 2048.
It is the node ID specified
during the RNC topological
node configuration.

Load Sharing
Mode, including:

SHMODE

NONE (NOT
Load Sharing)

BEARLOAD
(Bear Load
Sharing)

MBLOAD
(MasterBackup Load
Sharing)

Bearer Type 1,
including:
BTYPE1

BRATIO1

212

ATM (ATM)

IP (IP)

Bearer Type 1
Ratio

Confidential and Proprietary Information of ZTE CORPORATION

The parameter is used to


set the multiple load sharing
modes, with a default of
NONE

The parameter indicates


the first bearer type, with a
default of ATM
The parameter is used to the
set the proportion of the first
bearer type, with a default of
1

Chapter 7 MSCS-Radio-Office Interconnection Data Configuration

Parameter
Name

Parameter
Description
Bearer Type 2,
including:

BTYPE2

BRATIO2

NONE (NONE)

ATM (ATM)

IP (IP)

Bearer Type 2
Ratio

Instruction

The parameter indicates the


second bearer type, with a
default of NONE

The parameter is used to


the set the proportion of the
second bearer type, with a
default of 1
It is an optional parameter,
ranging from 1 to 10.

BPER

Ratio of bearer
from MGW to RNC

NAME

Alias

It is used for setting the


traffic load-sharing ratio
when the RNC accesses
several MGWs. If the RNC
only connects to one MGW,
this parameter is set as 1 by
default
It is an optional parameter
with a length ranging from 0
to 50 characters.

Example: Create the topology relationship between RNC and


MGW with the following requirements.

MGW node ID: 101

RNC node ID: 100.

The specific command is as follows.


ADD RNCMGWTOPO:MGWID=101,RANTYPE=RNC,RANI
D=100,SHMODE=NONE,BTYPE1=ATM,BRATIO1=1,BTYPE
2=NONE,BRATIO2=1,BPER=1;
END OF STEPS

Interconnection with BSC


Office
Overview
Networking Modes

When MSCS is interconnected with BSC through A-interface, there


are two networking modes.
1. MSCS<->MGW<->BSC

Confidential and Proprietary Information of ZTE CORPORATION

213

ZXWN MSCS Data Configuration Guide(MSCS)

MSCS and MGW are connected through IP bearer, BSC and


MGW are directly connected through TDM bearer. Figure 60
shows the networking structure and the interface protocols.
FIGURE 60 QUASI-ASSOCIATED NETWORKING BETWEEN MSCS
AND BSC

The BSSAP/SCCP signaling between MSCS and BSC is switched


by MGW. User data are transmitted between MGW and BSC
through TDM circuits. The A-interface circuits are managed by
the BSSAP signaling on MSCS. MSCS and MGW are interconnected with BSC through the same signaling point.
2. MSCS<->BSC, MGW<->BSC
When A-interface supports the IP bearer, BSC can be interconnected with MSCS/MGW through an IP bearer. Figure 61 shows
the networking structure and the interface protocols.
FIGURE 61 DIRECT-ASSOCIATED NETWORKING BETWEEN
MSCS AND BSC

MSCS and BSC are directly connected through SIGTRAN protocol. User data between MGW and BSC are transmitted through
RTP/UDP/IP.
Configuration
Flow

214

Figure 62 shows the flow of configuring the interconnection between MSCS and BSC through the A-interface.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 7 MSCS-Radio-Office Interconnection Data Configuration

FIGURE 62 FLOW OF CONFIGURING MSCS-BSC INTERCONNECTION

Flow Description

Perform the following steps to configure the interconnection between MSCS and BSC.
Steps

Operations

Instructions

Commands

Creating the BSC


adjacent office

Configure the basic


information of the BSC
adjacent office

ADD ADJOFC

Creating BSC
office direction

Configure some additive


attributes of the BSC
adjacent office

ADD BSCOFC

Creating BSC
topological node

Configure the adjacent


NE information

ADD TOPO

Confidential and Proprietary Information of ZTE CORPORATION

215

ZXWN MSCS Data Configuration Guide(MSCS)

Steps

Operations

Instructions

Commands

Creating the
topology
relationship
between BSC
and MGW

Configure the
topological relationship
between BSC and MGW,
thus to associate the
MGW node with the
BSC node.

ADD RNCMGW
TOPO

SIGTRAN
Configuration

When MSCS is
connected to BSC
through MGW and the
association between
MGW and MSCS is
configured, you only
need to configure
SIO-locating-AS
according to the
principles regulated
in SCTP planning.
When MSCS is directly
connected to BSC
through the IP bearer,
you need to perform the
configuration related
to SIGTRAN protocol.
Refer to Overview

Creating a BSC Adjacent Office


Prerequisites

Before the operation, it is required to confirm:

The data configuration of the local office is completed.

The range of adjacent office number is configured in the resource management.

The MML Terminal window is opened.

Context

Perform this procedure for configuring the basic information of the


BSC adjacent office.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the BSC adjacent office. The command is ADD ADJO
FC.
Table 81 describes the main parameters in the ADD ADJOFC
command.

216

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 7 MSCS-Radio-Office Interconnection Data Configuration

TABLE 81 PARAMETERS IN THE ADD ADJOFC COMMAND


Parameter
Name

Parameter
Description

Instruction

ID

Office ID

It is a mandatory parameter,
indicating the identification
number of the adjacent office,
and ranging from 1 to 2048.
It is usually configured as the
exchange ID of the adjacent
office during the all-network
planning.

NAME

Alias

It is a mandatory parameter,
which is the alias customized
by the user.

NET

Network type

It is a mandatory parameter,
indicating the network type of
the SPC used for connecting
the local office to the adjacent
office when the local office is
configured with several SPs.
The default is the network type
of this SP when there is only
one SP in the local office.

OFCTYPE

Adjacent office
type

It is a mandatory parameter.

SPCFMT

SPC format

Select TRIPLE_DEC

SPCTYPE

SPC type

DPC

SPC

RC

Area code

Type BSC in this case

It is a mandatory parameter.
Specify it based on the SPC
type of the adjacent office. In
China, BSC adopts the 14-bit
SPC.
When the adjacent office type
is BSC, RC must be empty.

Association type,
including

ASSOTYPE

AM_SURE
(direct
connection
mode)

AM_QUASI
(half direct
connection
mode)

AM_NONE(none connection
mode)

It is an optional parameter.
Select AM_QUASI

Confidential and Proprietary Information of ZTE CORPORATION

217

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction

Signaling point
type, including
SPTYPE

SEP

STP

STEP

It is an optional parameter.
Select SEP

Subservice
function, including

INTERNATIONAL (International signaling point


code)

INTERNATIONAL
STANDBY
(International
standby signaling point
code)

SSF

TEST

NATIONAL
(National
signaling point
code)

NATIONAL
STANDBY
(National
standby
signaling point
code).

Test flag

It is an optional parameter.
In general, select NATIONAL
STANDBY for BSC adjacent
office.

It is an optional parameter, for


setting whether the MTP3 link
actively initiates the link test
after entering in the service
status.
It is selected by default.

BANDFLAG

Broadband
attribute

It is an optional parameter.
Select NO

Protocol types,
including:

CHINA (China)

ITU (International Telecommunications


Union)

ANSI
(American
National
Standards
Institute).

PRTCTYPE

218

Confidential and Proprietary Information of ZTE CORPORATION

It is an optional parameter.
CHINA and ITU are used for
the NO.7 signaling networking
of the ITU standards. ANSI
is used for the No.7 signaling
networking of the American
standards.

Chapter 7 MSCS-Radio-Office Interconnection Data Configuration

Parameter
Name

CLST

Parameter
Description

Instruction

Cluster ID

It is an optional parameter.
The cluster number should
be configured in ADD CLST.
The parameter ranges from
0 to 65535, with a default of
65535.

Office Info,
including:

CIC_PCM (CIC
using PCM
Code Mode
Starts Load
Control)

BLOCK
(Manual Block
State)

EVEN_CIC
(Office
Controls Even
CIC if CIC
Resource
Collision)

INFO

RELATEDOFC1

CALLING
(Allow Calling
Transform)

CALLED
(Allow Called
Transform)

MOD24_CIC
(Mod 24 CIC
Mode)

TEST
(Dynamic Test)

Related office ID

It is an optional parameter,
with a default of CIC_PCM

It is an optional parameter,
ranging from 0 from 3000

Office extend info,


including

SIGBRDCST
(Support
Signaling
Broadcast
Message)

MTP
(Hongkong
MTP Standard)

INFOEX

DUPU (
Screen DUPU
message)

SUA_REC_
DT1 (Receive
SUA message
and handle

It is an optional parameter

Confidential and Proprietary Information of ZTE CORPORATION

219

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction

it as DT1
message)

SUA_SND_DT1 (Send
SUA message
and handle
it as DT1
message
without SN.)

OPEN_TG_RES (Open
outter trunk
group resource)

Example: Create a BSC adjacent office with the following requirements.

BSC office ID: 99

Network type: 2

User alias: BSC99

Destination SPC: 1.99.1

SPC type: 14-bit

Sub-service function: National standby SPC

Adjacent office type: BSC

Association type: Quasi-associated mode.

The specific command is as follows.


ADD
ADJOFC:ID=99,NAME="BSC99",NET=2,OFCTYPE
="BSC",SPCFMT=TRIPLE_DEC,SPCTYPE=14,DPC="1.99.
1",ASSOTYPE=AM_QUASI,SPTYPE=SEP,SSF=NATIONAL
STANDBY,SUBPROTTYPE=DEFAULT,TEST=YES,BANDFLAG
=NO,PRTCTYPE=CHINA,CLST=65535,INFO="CIC_PCM",RE
LATEDOFC1=0;
END OF STEPS

Creating BSC Office Direction


Prerequisites

Context

220

Before the operation, it is required to confirm:

You know the ID of the exchange to be configured.

The BSC adjacent office is created.

The MML Terminal window is opened.

Perform this procedure to configure some additive attributes of the


BSC adjacent office.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 7 MSCS-Radio-Office Interconnection Data Configuration

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the BSC office direction. The command is ADD BSCO
FC.
Table 82 describes the main parameters in the ADD BSCOFC
command.
TABLE 82 PARAMETERS IN THE ADD BSCOFC COMMAND
Parameter
Name

Parameter
Description

Instruction

BSCOFCID

BSC office ID

It is a mandatory parameter
ranging from 1 to 256.

MCC

Mobile country
code

It is a mandatory parameter
with the length ranging from 1
to 3 characters.

MNC

Mobile network
code

It is a mandatory parameter
with a length ranging from 1
to 3 characters.

Service identifier

It is an optional parameter.
Type it according to the actual
conditions. In general, all
the options can be selected,
except SUPCELLLOAD
(Support load-based switch)
and ALL (Support all).

INFO

A interface load
share mode,
including
SELTYPE

EXCELLENT
(excellent
choice priority)

LOAD (load
share priority)

It is an optional parameter.
Select EXCELLENT in this
case.

NAME

Alias

It is an optional parameter
with a length ranging from 0
to 50 characters.

RAS

BSC office
re-assignment

It is an optional parameter.
Select YES or NO according to
the actual conditions

CICINMGW

MGW manage BSC


CIC, including
options: NO(NO)
and YES(YES)

The default is NO(NO)

BEARTYPE

BSC bearer type,


including options:
TDM(TDM),
IPV4(IPV4) and
IPV6(IPV6)

It is an optional parameter,
with a default of TDM(TDM)

Confidential and Proprietary Information of ZTE CORPORATION

221

ZXWN MSCS Data Configuration Guide(MSCS)

Example: Create the BSC office direction with the following


requirements.

BSC office ID: 99

Mobile country code: 460

Mobile network code: 00

Service identifier: "BSCRST"&"MSCRST"&"BSCRCIC"&"MSCRCIC"&"BLOCKCIC"&"BLOCKCICG"&"UNBLOCKCIC"&"


UNBLOCKCICG"&"RESINDN"&"CHARGEINDN"&"FLUXCONTROL"&"BSCTRACK"&"MSCTRACK"&"QUEUEINDN"&"CALLREBUILD"&"SUPCELLLOAD"&"UNBLOCKCICINS"&"SupComID"&"SupEmlpp"&"SupChnNed"&"SupCIResMode"&"SupLCS"
Alias: BSC99.

The specific command is as follows.


ADD BSCOFC:BSCOFCID=99,MCC="460",MNC="00",INFO
="BSCRST"&"MSCRST"&"BSCRCIC"&"MSCRCIC"&"BLOCKCIC
"&"BLOCKCICG"&"UNBLOCKCIC"&"UNBLOCKCICG"&"RESIND
N"&"CHARGEINDN"&"FLUXCONTROL"&"BSCTRACK"&"MSCTR
ACK"&"QUEUEINDN"&"CALLREBUILD"&"SUPCELLLOAD"&"UN
BLOCKCICINS"&"SupComID"&"SupEmlpp"&"SupChnNed"&"S
upCIResMode"&"SupLCS",SELTYPE=EXCELLENT,NAME="BS
C99",RAS=NO,CICINMGW=NO,CICATTR="TFRV1"&"THRV
1"&"TFRV2"&"THRV2"&"TFRV3"&"THRV3"&"DFR14"&"DFR12
"&"DFR6"&"DFR3"&"DHR6"&"DHR3"&"HSCSD14x2"&"HSCSD1
2x2"&"HSCSD6x2"&"HSCSD14x4"&"HSCSD12x4"&"HSCSD6x
4"&"HSCSD12x6"&"HSCSD6x6",BEARTYPE=TDM,PROTYPE
=PRIVATE,IPCODECMODE=CC,SETPRE=SET1;
END OF STEPS

Creating a BSC Topology Node


Prerequisites

Before the operation, it is required to confirm:

You know the number of the exchange to be configured.

The encoding and decoding speech template is added.

The MML Terminal window is opened.

Context

Perform this procedure to configure the adjacent NE information,


including equipment type, bearer type and attributes, user plane
version, encoding and decoding template, and other information.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create a BSC topological node. The command is ADD TOPO.
Table 83 describes the main parameters in the ADD TOPO
command.

222

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 7 MSCS-Radio-Office Interconnection Data Configuration

TABLE 83 PARAMETERS IN THE ADD TOPO COMMAND


Parameter
Name

ID

OFCID

NAME

CODECID

Parameter
Description

Instruction

Topology node
ID

It is a mandatory parameter
ranging from 1 to 2048. It is
used for defining a topological
node. It is recommended that
this ID is consistent with the
office ID of this node.

Office ID

It is a mandatory parameter
for specify the office ID of this
topological node, ranging from 1
to 2048. This parameter must
be defined by the ADD ADJOFC
command first. Type the BSC
office ID according to actual
conditions.

Alias

It is a mandatory parameter for


naming this topological node,
with a length ranging from 1 to
50 characters.

CODEC identity

It is a mandatory parameter
for specifying the Encoding and
decoding speech Template used
by this topological node. This
parameter must be defined by
the ADD CODECTPL command
first.
Type it according to the actual
conditions.

ETYPE

Equipment type

It is an optional parameter for


specifying the NE type of this
topological node.
Select BSC for an BSC node.

IPVER

IP version of
the node

It is an optional parameter,
indicating the IP protocol version
supported between nodes.
Select IPV4 or IPV6 according
to the actual conditions. In
general, it is set as IPV4

ATTR

Bearer
attributes

This parameter is only valid


for the node with the type
of R4GW (MGW). You need
not to configure it for an BSC
topological node.

UPVER

User plane
protocol version

It is an optional parameter. This


parameter is not configured for
a BSC node

Confidential and Proprietary Information of ZTE CORPORATION

223

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction

Extended
attributes
(tunnel mode),
including

ATTR2

TRFMOD

NOTUNL
(None
tunnel
mode)

RTUNL
(Rapid
tunnel
mode)

DTUNL
(Delay
tunnel
mode)

Transmission
mode, including
MCINTF (Mc
interface signal
transfer mode)

This parameter sets which


tunnel mode is used for setting
up a bearer when this node
supports the IP/RTP bearer, with
a default of NOTUNL (None
tunnel mode).

This parameter is used to set


that mode used by the topology
for reporting the detected CNG
or CED fax signals, with a default
of MCINTF (Mc interface signal
transfer mode).
YES: The user plane entity
implements error inspection,
and sets the FQC bit position
according to the result. It will
transmit all frames includes
the error frames to the user
plane layer. During a call,
the error packet control
parameter delerrsdu=Yes,
which is delivered by the
terminal established by MGW
on the Mc interface. The
error packet control parameter
deliveryOfErroneousSDU is YES,
NA, NA during RAB assignment.

UPERRCTRL

Error SDU
control

NO: The user plane entity


implements the error inspection.
It will directly discard the
error frame. During a call, the
error packet control parameter
delerrsdu=No, which is delivered
by the terminal established by
MGW on the Mc interface. The
error packet control parameter
deliveryOfErroneousSDU is NO,
NA, NA during RAB assignment.
INVALIDTION: The user plane
entity does not implement the
error inspection. During a
call, the error packet control
parameter delerrsdu=NA,
which is delivered by the
terminal established by MGW
on the Mc interface. The
error packet control parameter

224

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 7 MSCS-Radio-Office Interconnection Data Configuration

Parameter
Name

Parameter
Description

Instruction
deliveryOfErroneousSDU is NA,
NA, NA during RAB assignment.
This parameter regulates the
handling method of the user
plane for error frames. It is
only valid for MGW-type and
RNC-type topological node. The
default value is YES

DTMFTC

Tandem office
send DTMF
use TC mode,
containing two
options:

NO

YES

This parameter is used to set


whether the tandem office uses
the TC resources during DTMF
number delivery.
The default value is NO

It contains the following options.

MGWCON

MGW
congestion
reporting
capability

SMGWCON (Standard MGW


congestion event)

CMGWCON (Custom MGW


congestion event).

The default value is SMGWCON.

Example: Create a BSC topological node with the following


requirements.

BSC office ID: 99

Topological node ID: 99

Alias: BSC99

CODEC ID: 1

The specific command is as follows.


ADD TOPO:ID=99,OFCID=99,NAME="BSC99",CODECID
=1,ETYPE=BSC,PROTTYPE=H248,DMNAME="RNC",IPVER
=IPV4,UPVER="V2",ATTR2=NOTUNL,TRFMOD=MCINTF,UP
ERRCTRL=YES,DTMFTC=NO,MGWCON=SMGWCON,AUTOF
AX=YES,OOBTC=NO,BCUID=0,SENDCAP=NO,G711TRAN
=NO,BICCDTMF=TRANSPARENT,IPBCP2833=BYMGW,BIC
CDTMPPER=0,AOIPPRO=PRIVATE;
END OF STEPS

Creating the Topology Relationship


between BSC and MGW
Prerequisites

Before the operation, it is required to confirm:

You know the number of the exchange to be configured.

The BSC topological node is configured.

Confidential and Proprietary Information of ZTE CORPORATION

225

ZXWN MSCS Data Configuration Guide(MSCS)

The MML Terminal window is opened.

Context

Perform this procedure to configure the topological relationship


between BSC and MGW, thus to associate the MGW node with the
BSC node.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the topological relationship between BSC and MGW. The
command is ADD RNCMGWTOPO.
Table 84 describes the main parameters in the ADD RNCMG
WTOPO command.
TABLE 84 MAIN PARAMETERS IN THE ADD RNCMGWTOPO
COMMAND
Parameter
Name

Parameter
Description

Instruction
It is a mandatory parameter
ranging from 1 to 2048.

MGWID

MGW node ID

RANTYPE

Office type

RANID

RNC/BSC node
number

It is the node ID specified


during the MGW topological
node configuration
It is a mandatory parameter.
Select BSC for BSC access.
It is a mandatory parameter
ranging from 1 to 2048.
It is the node ID specified
during the BSC topological
node configuration.

Load Sharing
Mode, including:

SHMODE

NONE (NOT
Load Sharing)

BEARLOAD
(Bear Load
Sharing)

MBLOAD
(MasterBackup Load
Sharing)

Bearer Type 1,
including:
BTYPE1

BRATIO1

226

ATM (ATM)

IP (IP)

Bearer Type 1
Ratio

Confidential and Proprietary Information of ZTE CORPORATION

The parameter is used to


set the multiple load sharing
modes, with a default of NONE

The parameter indicates the


first bearer type, with a default
of ATM
The parameter is used to the
set the proportion of the first
bearer type, with a default of 1

Chapter 7 MSCS-Radio-Office Interconnection Data Configuration

Parameter
Name

Parameter
Description
Bearer Type 2,
including:

BTYPE2

BRATIO2

NONE (NONE)

ATM (ATM)

IP (IP)

Bearer Type 2
Ratio

Instruction

The parameter indicates the


second bearer type, with a
default of NONE

The parameter is used to


the set the proportion of the
second bearer type, with a
default of 1
It is an optional parameter,
ranging from 1 to 10.

BPER

Ratio of bearer
from MGW to BSC

NAME

Alias

It is used for setting the traffic


load-sharing ratio when the
BSC accesses several MGWs.
If the BSC only connects to
one MGW, this parameter is set
as 1 by default
It is an optional parameter
with a length ranging from 0
to 50 characters.

Example: Create the topology relationship between BSC and


MGW with the following requirements.

MGW node ID: 101

Office type: BSC

BSC node ID: 99.

The specific command is as follows.


ADD RNCMGWTOPO:MGWID=101,RANTYPE=BSC,RANI
D=99,SHMODE=NONE,BTYPE1=ATM,BRATIO1=1,BTYPE2
=NONE,BRATIO2=1,BPER=1;
END OF STEPS

Confidential and Proprietary Information of ZTE CORPORATION

227

ZXWN MSCS Data Configuration Guide(MSCS)

This page is intentionally blank.

228

Confidential and Proprietary Information of ZTE CORPORATION

Chapter

Basic Service Data


Configuration
Table of Contents
Location Update Data Configuration ................................... 229
Call Data Configuration .................................................... 266

Location Update Data


Configuration
Access Configuration
Overview
When MSCS is interconnected with the RNC or BSC, the data related to the access should be configured on the MSCS side. The
access configuration contains the following operations, as shown
in Table 3.
TABLE 3 ACCESS CONFIGURATION
Steps

Operations

Instructions

Commands

Creating emergency call


center

Create emergency
call center

ADD ECC

Creating a special
service phone group

Create different
special-service
attendant consoles

ADD SSPN

Creating special service


phone called number
analysis

Create the special


service called
number analysis

ADD
TPDNAL

Confidential and Proprietary Information of ZTE CORPORATION

229

ZXWN MSCS Data Configuration Guide(MSCS)

Steps

Operations

Instructions

Commands

Creating a LAI controlled


by the local office

Create the basic


information for a
Location Area ID
(LAI) controlled by
the BSC/RNC

ADD LAI

Creating an adjacent
LAI

Create an adjacent
LAI where handover
services may occur

Creating a cell (only for


the interconnection with
the BSC)

When the BSC


accesses the MSCS,
it is required to
create the global
cell data.

ADD GCI

Creating a service
area (only for the RNC
interconnection)

During the RNC


access, it is required
to create the data
for the service area.

ADD SAI

Creating Emergency Call Center


Prerequisites

Context

Before the operation, it is required to confirm:

The exchange ID to be configured is given.

The MML Terminal window is opened.

The emergency call function does not analyze the emergency call
number. After the subscriber dials a specified emergency call number in one location area, the core network will obtain the emergency call center index according to the location area where the
emergency call is received. After that, it will find the corresponding number of the emergency call center number according to the
the emergency call center index, and then analyze this number.
This topic describes how to create emergency call center.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create emergency call center with the command ADD ECC.
The explanation of the main parameters in command ADD ECC
is shown in Table 85.

230

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

TABLE 85 PARAMETERS IN THE ADD ECC COMMAND

Parameter
Name

Parameter Description

Instruction

ECC

Emergency Call Center


Number

It is a mandatory
parameter, consisting
of 1~32 digits

ECCIDX

Emergency Call Center


Index

It is an optional
parameter, which is
an integer, ranging from
0 to 255

Emergency Call Service


Type, including

DFT: Default
Emergency Call
Center Number

POLICE: Police
Emergency Call
Center Number

AMBULANCE:
Ambulance
Emergency Call
Center Number

SERVTYPE

FIRE: Fire-fighting
Emergency Call
Center Number

MARINE: Marine
Emergency Call
Center Number

MOUTAIN: Mountain
Area Emergency Call
Center Number

It is an optional
parameter with the
default value DFT

Configuration Number
Type, including

UNKNOWN:
Unknown

INTERNATIONAL:
International

NATIONAL: National

SPECIAL: Special
Number Of The
Network

SHORT: Abbreviated
Number

NAT

NAME

Alias

It is an optional
parameter withe
the default value
UNKNOWN

It is an optional
parameter, consisting
of 0~50 characters

For example, create the emergency call center. The emergency


call number is 112, the emergency call center index is 1, the
emergency call service type is DFT, the configuration number

Confidential and Proprietary Information of ZTE CORPORATION

231

ZXWN MSCS Data Configuration Guide(MSCS)

type is international, and the alias is Emergency1. The command is as follows:


ADD ECC:ECC="112",ECCIDX=1,SERVTYPE="DFT",NAT=I
NTERNATIONAL,NAME="Emgergency1";
END OF STEPS

Creating a Special Service Phone Group


Prerequisites

Context

Before the operation, it is required to confirm:

The exchange ID to be configured is given.

The MML Terminal window is opened.

In the case of the MSCS being connected with the BSC, when you
dial a special-service number in different cells, it is required to
convert this number to different numbers for connection.
In the case of the MSCS being connected with the RNC, when you
dial a special-service number in different service areas, it is also
required to convert this number to different numbers for connection.
Therefore, different special-service attendant consoles need to be
configured.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create a special service phone group with the command ADD
SSPN.
The explanation of the main parameters in command ADD
SSPN is shown in Table 86.
TABLE 86 PARAMETERS IN THE ADD SSPN COMMAND
Parameter
Name

232

Parameter
Description

Instruction

SSPGID

Special
Service
Phone Group
ID

It is a mandatory parameter,
which is an integer, ranging form
1 to 65535. It is associated with
the special-service phone group
ID in the special-service group
configuration, exclusively defines an
attendant console together with the
special-service number

SSPGNAME

Special
Service
Phone Group
Name

It is an optional parameter, consisting


of 0~50 characters. It is used to
identify a special-service group

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Parameter
Name

SSNUM 1

PNUM1

SSNUM 2

PNUM2

SSNUM 3

PNUM3

SSNUM 4

PNUM4

Parameter
Description

Instruction

Special
Service
Number 1

It is a mandatory parameter, which


is an integer, ranging form 1 to
2147483647. It is the special-service
number, such as 114. It exclusively
defines an attendant console together
with the special-service traffic group
ID

Phone
Number 1

It is a mandatory parameter
indicating the phone console number
corresponding to the special service
phone group ID and the special
service number. It ranges from 0 to
40

Special
Service
Number 2

It is a mandatory parameter, which


is an integer, ranging form 1 to
2147483647. It is the special-service
number, such as 114. It exclusively
defines an attendant console together
with the special-service traffic group
ID

Phone
Number 2

It is a mandatory parameter
indicating the phone console number
corresponding to the special service
phone group ID and the special
service number. It ranges from 0 to
40

Special
Service
Number 3

It is a mandatory parameter, which


is an integer, ranging form 1 to
2147483647. It is the special-service
number, such as 114. It exclusively
defines an attendant console together
with the special-service traffic group
ID

Phone
Number 3

It is a mandatory parameter
indicating the phone console number
corresponding to the special service
phone group ID and the special
service number. It ranges from 0 to
40

Special
Service
Number 4

It is a mandatory parameter, which


is an integer, ranging form 1 to
2147483647. It is the special-service
number, such as 114. It exclusively
defines an attendant console together
with the special-service traffic group
ID

Phone
Number 4

It is a mandatory parameter
indicating the phone console number
corresponding to the special service
phone group ID and the special
service number. It ranges from 0 to
40

Confidential and Proprietary Information of ZTE CORPORATION

233

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

SSNUM 5

PNUM5

SSNUM 6

PNUM6

SSNUM 7

PNUM7

SSNUM 8

PNUM8

234

Parameter
Description

Instruction

Special
Service
Number 5

It is a mandatory parameter, which


is an integer, ranging form 1 to
2147483647. It is the special-service
number, such as 114. It exclusively
defines an attendant console together
with the special-service traffic group
ID

Phone
Number 5

It is a mandatory parameter
indicating the phone console number
corresponding to the special service
phone group ID and the special
service number. It ranges from 0 to
40

Special
Service
Number 6

It is a mandatory parameter, which


is an integer, ranging form 1 to
2147483647. It is the special-service
number, such as 114. It exclusively
defines an attendant console together
with the special-service traffic group
ID

Phone
Number 6

It is a mandatory parameter
indicating the phone console number
corresponding to the special service
phone group ID and the special
service number. It ranges from 0 to
40

Special
Service
Number 7

It is a mandatory parameter, which


is an integer, ranging form 1 to
2147483647. It is the special-service
number, such as 114. It exclusively
defines an attendant console together
with the special-service traffic group
ID

Phone
Number 7

It is a mandatory parameter
indicating the phone console number
corresponding to the special service
phone group ID and the special
service number. It ranges from 0 to
40

Special
Service
Number 8

It is a mandatory parameter, which


is an integer, ranging form 1 to
2147483647. It is the special-service
number, such as 114. It exclusively
defines an attendant console together
with the special-service traffic group
ID

Phone
Number 8

It is a mandatory parameter
indicating the phone console number
corresponding to the special service
phone group ID and the special
service number. It ranges from 0 to
40

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Parameter
Name

SSNUM 9

PNUM9

SSNUM 10

PNUM10

Parameter
Description

Instruction

Special
Service
Number 9

It is a mandatory parameter, which


is an integer, ranging form 1 to
2147483647. It is the special-service
number, such as 114. It exclusively
defines an attendant console together
with the special-service traffic group
ID

Phone
Number 9

It is a mandatory parameter
indicating the phone console number
corresponding to the special service
phone group ID and the special
service number. It ranges from 0 to
40

Special
Service
Number 10

It is a mandatory parameter, which


is an integer, ranging form 1 to
2147483647. It is the special-service
number, such as 114. It exclusively
defines an attendant console together
with the special-service traffic group
ID

Phone
Number 10

It is a mandatory parameter
indicating the phone console number
corresponding to the special service
phone group ID and the special
service number. It ranges from 0 to
40

For example, create the special service phone group. The Special service phone group ID is 1, the special service number is
110, the phone number is 0086251100 and the special service
phone group name is SSPN1. The command is as follows:
ADD SSPN:SSPGID=1,SSPGNAME="SSPN1",SSNUM1=11
0,PNUM1="0086251100";
END OF STEPS

Creating the Special Service Phone Called


Number Analysis
Prerequisites

Before the operation, it is required to confirm:

The exchange ID to be configured is given.

The number analyzer entry is created.

The special service phone group is created.

The MML Terminal window is opened.

Context

This topic details how to create the special service called number
analysis.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.

Confidential and Proprietary Information of ZTE CORPORATION

235

ZXWN MSCS Data Configuration Guide(MSCS)

Example: Select the MSCS exchange with ID as 11 from the


system tree.
SET:NEID=11;
2. Analyze the prefix of a called number by executing command
ADD TPDNAL.
The explanation of the main parameters in command ADD
TPDNAL is shown inTable 87
TABLE 87 PARAMETERS IN THE ADD TPDNAL COMMAND
Parameter Name

ENTR

DIGIT

Parameter
Description

Instructions

Number analyzer entry

It is a mandatory parameter,
which is an integer, ranging
from 1 to 1000. Select the
corresponding analyzer entry
of the analyzed number prefix.
For local calls, select the corresponding analyzer entry of the
local number analyzer

Analyzed number

It is a mandatory parameter,
consisting of 0~20 digits. Input
the prefix of the called number, whose length must make it
be distinguished in the local office. For intra-office calls, it is
required to configure both the
prefix of the called number and
that of the local-office roaming
number
It is an optional parameter,
consisting of 0~50 characters.
It is used to specifically
describe the called number
analysis to make it easily
recognized

NAME

User alias

CAT

Call service types

It is an optional parameter, select LSFR (Free Special Service


Of The Current Office)

RST1

Number analysis
result 1

Type the special service


number configured in ADD
SSPN

For example, create the special service called number analysis


with the following requirements:

236

Number analyzer entry: 1

User alias: SS1

Analyzed number: 110

Call service types: LSFR

Number analysis result 1 :110

Other parameters: Use default

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

The specific command is as follows.


ADD TPDNAL:ENTR=1,DIGIT="110",NAME="SS1",SPEC
RST=0,SPECIDX=0,CAT=LSFR,RST1=110,RST2=0,RST3
=0,CHAINAL=0,RNLEN=0,MINLEN=3,MAXLEN=20,OVLY
PRI=NO,REL=NO,NET=1,NAT=DEF,OPDDICONT=NO,TP
DDICONT=NO,OPDDI=0,TPDDI=0,OPDLYDDI=0,TPDLY
DDI=0,DDIOVERB=0,IWVIDEO=LSUP,TIMELMT=0,AUX
DAS=0,A6=0,PFXLEN=0,INSRV=INM,FAXIDX=0,AVIDX
=0,DVIDX=0,ADATAIDX=0,DDATAIDX=0,DDCPLAY=NO
NE,VAD=INVALID,CALLSERVPRILVL=INVALID,RERTS=0,I
NCHAIN=NO,BICT=NO,ICT=0,ICTT=10,GNM=NORMAL,S
TBILL=INVALID,HOPDAS=0,MCA=NO,IVVR=NO,WANTL
=0,IMSCENTR=NO;
END OF STEPS

Creating a LAI Controlled by the Local Office


Prerequisites

Before the operation, it is required to confirm:

The exchange ID to be configured is given.

The RNC/BSC office direction attributes are configured.

The LAI range is set in the Resource Management system.

The MML Terminal window is opened.

Context

This section introduces how to configure the basic information for


a Location Area ID (LAI) controlled by the BSC/RNC.

Steps

1. If no exchange is specified, execute the command SET on the


MML Terminal window or select a NE from the system tree to
specify the exchange to be configured.
Example: Select the MSCS 11 from the system tree.
SET:NEID=11;
2. Create a LAI controlled by the local office by executing command ADD LAI.
The explanation of the main parameters in command ADD LAI
is shown inTable 88.
TABLE 88 PARAMETERS IN THE ADD LAI COMMAND
Parameter
Name

Parameter
Description

Instruction

LAC

Location area
code (HEX)

It is a mandatory parameter,
consisting of 4 HEX digits. It
should be consistent with that
of the RNC/BSC side

Alias

It is an optional parameter,
consisting of 1~50 characters.
It is used to describe the LAI,
such as Adjacent BSC/RNC
office name-LAI

NAME

Confidential and Proprietary Information of ZTE CORPORATION

237

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction

Location area ID

It is an optional parameter.
It is used to define a LAI in
the system, ranging from
1~65534. If there is no special
requirements, enter the LAI
in the cell of the BSC/RNC
connected with the MSCS

Virtual MSC index

It is an optional parameter.
It indicates whether the
BSC/RNC connected with
the MSCS accesses the
MSCS through the public
domain. If the BSC/RNC
accesses the MSCS through
the public domain, enter 0.
Otherwise, enter the index of
the connected virtual MSC

MCC

Mobile Country
Code

It is an optional parameter,
consisting of 0~3 digits. Enter
it according to the actual
condition, such as 460 for
China

MNC

Mobile Network
Code

It is an optional parameter.
Enter the corresponding MNC
of this LAI

MSC number.

It indicates which MSC the


accessed RNC/BSC belongs to.
It is an optional parameter,
consisting of 0~16 digits.
At present, in the network
management system in the
default case, if the accessed
RNC/BSC is controlled by the
local office (i.e., the BELONG
field is MSC), no MSC number
needs to be entered. If
VMSCIDX is 0, the system
directly adopts the MSC
number from the local-office
mobile data. If VMSCIDX is not
0, the system directly adopts
the corresponding virtual MSC
number from the virtual MSC
configuration. If the accessed
RNC/BSC is not controlled by
the local office, this parameter
needs to be entered

ID

VMSCIDX

MSC

238

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Parameter
Name

VLR

LOCNUM

ECCIDX

BSC

RNC

TPDAS

Parameter
Description

Instruction

VLR number

It indicates which VLR the


accessed RNC/BSC belongs to.
It is an optional parameter,
consisting of 0~16 digits.
At present, in the network
management system in the
default case, if the accessed
RNC/BSC is controlled by
the local office (i.e., the
BELONG field is MSC), no
VLR number needs to be
entered. If VMSCIDX is 0, the
system directly adopts the VLR
number from the local-office
mobile data. If VMSCIDX is not
0, the system directly adopts
the corresponding virtual VLR
number from the virtual MSC
configuration. If the accessed
RNC/BSC is not controlled by
the local office, this parameter
needs to be entered

Location number

It is an optional parameter.
The VLR brings the location
number to the HLR during
PROVIDE-SUBSCRIBERLOCATION procedures. Enter
country code + area code,
such as 8625 for Nanjing in
China

Emergency call
index

It is an optional parameter.
Select a configured emergency
call index. If no emergency
call index is configured, select
0

BSC ID in the LAI

It is an optional parameter.
Enter one or more adjacent
BSC office IDs managing
this LAI. In case of the RAN
accessing the MSCS, there
is no need to configure this
parameter

RNC ID in the LAI

It is an optional parameter.
Enter one or more adjacent
RNC office IDs managing
this LAI. In case of the BSC
accessing the MSCS, there
is no need to configure this
parameter

DAS for the called


number

It is an optional parameter.
Enter the originating DAS 101
from the number analysis
configuration. If no DAS is
configured, enter 0 at first and
then modify it

Confidential and Proprietary Information of ZTE CORPORATION

239

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction

Belonging to,
including

BELONG

NO_MSC(not
belong to
local MSC
Server
domain)

MSC (belong
to local
MSC Server
domain)

DATTR
(belong to
double home
domain)

It is an optional parameter,
with MSC as the default value.
If this LAI is managed by
the local office, select MSC.
Otherwise, select NO_MSC. In
this case, it is required to enter
the MSC number and VLR
number where this LAI belongs
to. IF this LAI is managed by
a dual-homing domain, select
DATTR

Location area
attribute,
including:
LAIATTR

ATTBILL
(Produce
attempt call
bill)

NONE (none)

It is an optional parameter

WDMID

Work domain
index

It is an optional parameter,
with 0 as the default value.
In case of dual-homing
networking, enter the
dual-homing work domain
index ranging from 0 to 255

UPVER

UP mode version
of MSC-B

It is an optional parameter
indicating the version No. of
the MSC user plane where the
location area exists

R5HOCASE

GSMSSPGID

240

Support HO Case
of Version R5,
including:

NO

YES

GSM Special
Service Phone
Group ID

Confidential and Proprietary Information of ZTE CORPORATION

It is an optional parameter
and the default value is NO. It
configures whether the local
LAI supports the R5 handover.
During 3G-to-2G handover,
determine the transform
mode for the handover and
ensure the compatibility of
the version according to the
configuration. That is to say,
when the option is YES, the
handover is done according to
the handover reason defined
in R5 version. If the option
is NO, the handover is done
according to the handover
reason defined in R4 version
It is an optional parameter
ranging from 0 to 65535 and
it is defined by the command
ADD SSPN

Chapter 8 Basic Service Data Configuration

Parameter
Name

Parameter
Description

Instruction

UMTSSSPGID

UMTS Special
Service Phone
Group ID

It is an optional parameter
ranging from 0 to 65535. It is
defined by the command ADD
SSPN

Extend Info,
including:
EXTINFO

NONBCLAI
(Non-Broadcast
LAI in POOL)

It is an optional parameter.
For the non-broadcast LAI in
POOL, the value is Null

For example, create BSC location area with the following requirements.

Location area code: 12FB

Location area identity: 201

User alias: BSC-12FB

Mobile country code: 460

Mobile network code: 00

Location number: 8625

BSC ID in LAI: 99

DAS for the called number: 1

Other parameters: use default

The command is as follows:


ADD LAI:LAC="12FB",NAME="BSC-12FB",ID=201,MCC="4
60",MNC="00",LOCNUM="8625",ECCIDX=1,BSC="99",R
NC="0",TPDAS=1,BELONG=NO_MSC,WDMID=0,UPVER
=1,R5HOCASE=NO,GSMSSPGID=1,UMTSSSPGID=0,PAG
EIDX=0,ASSTIMER=0;
END OF STEPS

Creating an Adjacent LAI


Prerequisites

Context

Before the operation, it is required to confirm:

The exchange ID to be configured is given.

The LAI range is set in the Resource Management system.

The MML Terminal window is opened.

This section introduces how to create an adjacent LAI where handover services may occur.
When a handover occurs, the handover request message carries
the target cell. The MSCSERVER needs to get the MSCNUM according to the LAI in the message, and judge whether the handover
occurs within the local office. When the corresponding MSC number of the LAI is different with the local MSC number, it is required
to initiates an inter-office handover to other MSC. Therefore, it is

Confidential and Proprietary Information of ZTE CORPORATION

241

ZXWN MSCS Data Configuration Guide(MSCS)

required to configure the number of the home MSC/VLR of the adjacent LAI belongs.
Steps

1. If no exchange is specified, execute the command SET on the


MML Terminal window or select a NE from the system tree to
specify the exchange to be configured.
Example: Select the MSCS 11 from the system tree.
SET:NEID=11;
2. Create an adjacent LAI by executing command ADD LAI.
The explanation of the main parameters in command ADD LAI
is shown in Table 89.
TABLE 89 PARAMETERS IN THE ADD LAI COMMAND
Parameter
Name

Parameter
Description

Instructions

LAC

Location area code


(HEX)

It is a mandatory parameter.
It consists of 4 HEX digits. It
should be consistent with that
of the RNC/BSC side

Alias

It is an optional parameter,
consisting of 1~50 characters.
It is used to describe the LAI,
such as Adjacent BSC/RNC
office name-LAI

Location area ID

It is an optional parameter.
It is used to define a LAI in
the system, ranging from
1~65534. If there is no
special requirements, enter
the LAI in the cell of the
BSC/RNC connected with the
MSCS

Virtual MSC Index

It is an optional parameter.
It indicates whether the
BSC/RNC connected with
the MSCS accesses the
MSCS through the public
domain. If the BSC/RNC
accesses the MSCS through
the public domain, enter 0.
Otherwise, enter the index of
the connected virtual MSC

Mobile Country
Code

It is an optional parameter,
consisting of 0~3 digits. Enter
it according to the actual
condition, such as 460 for
China

Mobile Network
Code

It is an optional parameter.
Enter the corresponding MNC
of this LAI, such as 00 for
China Mobile, and 01 for
China Unicom

NAME

ID

VMSCIDX

MCC

MNC

242

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Parameter
Name

MSC

VLR

LOCNUM

Parameter
Description

Instructions

MSC number

It indicates which MSC the


accessed RNC/BSC belongs to.
It is an optional parameter,
consisting of 0~16 digits.
At present, in the network
management system in the
default case, if the connected
RNC/BSC is controlled by the
local office (i.e., the BELONG
field is MSC), no MSC number
needs to be entered. If
VMSCIDX is 0, the system
directly adopts the MSC
number from the local-office
mobile data. If VMSCIDX is
not 0, the system directly
adopts the corresponding
virtual MSC number from the
virtual MSC configuration. If
the accessed RNC/BSC is not
controlled by the local office,
this parameter needs to be
entered. When configuring
the adjacent LAI, enter the
corresponding MSC GT of the
adjacent LAI

VLR number

It indicates which VLR the


accessed RNC/BSC belongs to.
It is an optional parameter,
consisting of 0~16 digits.
At present, in the network
management system in the
default case, if the accessed
RNC/BSC is controlled by the
local office (i.e., the BELONG
field is MSC), no VLR number
needs to be entered. If
VMSCIDX is 0, the system
directly adopts the VLR
number from the local-office
mobile data. If VMSCIDX is
not 0, the system directly
adopts the corresponding
virtual VLR number from the
virtual MSC configuration. If
the accessed RNC/BSC is not
controlled by the local office,
this parameter needs to be
entered. When configuring
the adjacent LAI, enter the
corresponding VLR GT of the
adjacent LAI

Location number

It is an optional parameter.
The VLR brings the location
number to the HLR during
PROVIDE-SUBSCRIBERLOCATION procedures. Enter
country code + area code,
such as 8625 for Nanjing in
China

Confidential and Proprietary Information of ZTE CORPORATION

243

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instructions

Belonging,
including

BELONG

NO_MSC(not
belong to local
MSC Server
domain)

MSC (belong
to local
MSC Server
domain)

DATTR
(belong to
double home
domain)

It is an optional parameter,
with MSC as the default value.
If this LAI is managed by
the local office, select MSC.
Otherwise, select NO_MSC.
In this case, it is required to
enter the MSC number and
VLR number where this LAI
belongs to. IF this LAI is
managed by a dual-homing
domain, select DATTR

Location area
attribute,
including:
LAIATTR

ATTBILL
(Produce
attempt call
bill)

NONE (none)

It is an optional parameter

WDMID

Work domain
index

It is an optional parameter,
with 0 as the default value.
In case of dual-homing
networking, enter the
dual-homing work domain
index ranging from 0 to 255

UPVER

UP mode version
of MSC-B

It is an optional parameter
indicating the version No. of
the MSC user plane where the
location area exists

R5HOCASE

GSMSSPGID

244

Support HO Case
of Version R5,
including:

NO

YES

GSM Special
Service Phone
Group ID

Confidential and Proprietary Information of ZTE CORPORATION

It is an optional parameter
and the default value is NO. It
configures whether the local
LAI supports the R5 handover.
During 3G-to-2G handover,
determine the transform
mode for the handover and
ensure the compatibility of
the version according to the
configuration. That is to say,
when the option is YES, the
handover is done according to
the handover reason defined
in R5 version. If the option
is NO, the handover is done
according to the handover
reason defined in R4 version
It is an optional parameter
ranging from 0 to 65535 and
it is defined by the command
ADD SSPN

Chapter 8 Basic Service Data Configuration

Parameter
Name

Parameter
Description

Instructions

UMTSSSPGID

UMTS Special
Service Phone
Group ID

It is an optional parameter
ranging from 0 to 65535. It is
defined by the command ADD
SSPN

Extend Info,
including:
EXTINFO

NONBCLAI
(Non-Broadcast
LAI in POOL)

It is an optional parameter.
For the non-broadcast LAI in
POOL, the value is Null

For example, create the BSC location area with the following
requirements.

Location area code: 1111

Location area identity: 301

User alias: BSC-1111

Mobile country code: 460

Mobile network code: 01

Location number: 8625

VLR number: 8613954353

Belong type: NO_MSC

Other parameters: use default

The command is as follows:


ADD LAI:LAC="1111",NAME="BSC-1111",ID=301,MCC="4
60",MNC="01",MSC="8613954353",VLR="8613954353",LO
CNUM="8625",ECCIDX=0,BSC="0",RNC="0",TPDAS=0,BE
LONG=NO_MSC,WDMID=0,UPVER=1,R5HOCASE=NO,GS
MSSPGID=0,UMTSSSPGID=0,PAGEIDX=0,ASSTIMER=0;
END OF STEPS

Creating a Global Cell


Prerequisites

Context

Before the operation, it is required to confirm:

The exchange ID to be configured is given.

The DAS for the called number is configured.

The BSC LAI is configured.

The MML Terminal window is opened.

When the BSC accesses the MSCS, it is required to configure the


global cell data. When a GSM handover occurs, the handoveroriginated office (intra/inter-office handover) needs to know the
home BSC of the handover-terminated cell, so that it can initiates
a handover request to the BSC.

Confidential and Proprietary Information of ZTE CORPORATION

245

ZXWN MSCS Data Configuration Guide(MSCS)

Steps

1. If no exchange is specified, execute the command SET on the


MML Terminal window or select a NE from the system tree to
specify the exchange to be configured.
Example: Select the MSCS 11 from the system tree.
SET:NEID=11;
2. Create a global cell by executing command ADD GCI.
The explanation of the main parameters in command ADD GCI
is shown in Table 90.
TABLE 90 PARAMETERS IN THE ADD GCI COMMAND
Parameter Name

Parameter
Description

Instructions

Location area ID

It is a mandatory parameter,
ranging 1 to 65534. Select the
home LAI of the cell from the list
of configured LAIs

Cell Identity
(hex)

It is an optional parameter
composed of GCIBEGIN (Cell
Identity Begin) and GCIEND (Cell
Identity End). The format of it is
CIB-CIE. Configure it according to
the real conditions. It should be
consistent with that of the BSC
side

TPDAS

Called Number
Selector

It is an optional parameter. It
ranges from 0 to 4096, with
a default of 0. It may not be
configured here. During the call
data configuration, it could be
modified and the referred value
is the number analysis selector in
the number analysis configuration

BSC

BSC Office

It is an optional parameter, ranging


from 0 to 3000. Select the BSC
office that manages this cell

LAIID

GCI

Cell Attribute,
including
GCIATTR

NONE (none)

It is a mandatory parameter

ATTBILL
(produce
attempt call bill)

246

NAME

Alias

It is an optional parameter,
consisting of 0~50 characters

SSPGID

Special service
phone group ID

It is an optional parameter ranging


from 0 to 65535. It is defined by
the command ADD SSPN

VMSCIDX

Virtual MSC
Index

It is an optional parameter. It
ranges from 0 to 65535. If 0
is selected, it represents public
domain, if 0 is not selected,

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Parameter Name

Parameter
Description

Instructions
the virtual MSC index should be
entered.

ECCIDX

Emergency
index

call

It is an optional parameter ranging


from 0 to 65535.

For example, create the global cell with the following requirements.

Location area ID: 201

Called number selector: 101

Cell identity (Hex): 1111-1111

BSC office ID: 99

Alias: GCI1

Special service phone group ID: 1

Emergency call index: 1

Other parameters: adopt the default value.

The command is as follows.


ADD GCI:LAIID=201,GCI="1111"-"1111",TPDAS=1,BSC
=99,NAME="GCI1",SSPGID=1,ECCIDX=1;
END OF STEPS

Creating a Service Area


Prerequisites

Before the operation, it is required to confirm:

The exchange ID to be configured is given.

The RNC LAI is created.

The MML Terminal window is opened.

Context

During the RNC access, it is required to configure the data for the
service area.

Steps

1. If the exchange is not specified, execute the command SET


on the MML Terminal window or select a NE from the system
tree to specify the exchange to be configured.
Example: Select the MSCS 11 from the system tree.
SET:NEID=11;
2. Create a service area with the command ADD SAI.
The parameter description of the command ADD SAI is shown
in Table 91.

Confidential and Proprietary Information of ZTE CORPORATION

247

ZXWN MSCS Data Configuration Guide(MSCS)

TABLE 91 PARAMETERS IN THE ADD SAI COMMAND


Parameter
Name

Parameter
Description

LAIID

Location
Area ID

It is a mandatory parameter ranging


from 1 to 65534. Select the home LAI
of the cell from the list of the configured LAIs

SAC

Service Area
Code (hex)

It is a mandatory parameter composed of SACB (Service Area Code


Begin) and SACE (Service Area Code
End).
The format is SACB-SACE.
Configure it according to the real conditions. It should be consistent with
that of the RNC side

RNC

RNC Office

It is an optional parameter ranging


from 0 to 2048. Select the RNC office
that manages this service area

NAME

Alias

It is an optional parameter ranging


from 0 to 50 characters

SSPGID

Special Service
Phone
Group

It is an optional parameter ranging


from 0 to 65535 and it is defined by
the command ADD SSPN

VMSCIDX

Virtual
Index

It is an optional parameter ranging


from 0 to 65535. If 0 is selected, it
means the common domain. If it is
not 0, enter the accessed virtual MSC
index No.

ECCIDX

Emergency
call index

MSC

Instructions

It is an optional parameter ranging


from 0 to 65535.

For example, create a service area identity with the following


requirements. The is 201, the , and the is 100. For the other
parameters, select the default value. The command is as follows:

Location area ID: 201

Service area code: 0000

RNC office ID: 100

Alias: SAI1

Special service phone group: 1

Emergency call index: 1

Other parameters: use default

The command is as follows:


ADD SAI:LAIID=201,SAC="0000"-"0000",RNC=100,NAME
="SAI1",SSPGID=1,ECCIDX=1;
END OF STEPS

248

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

SCCP Data Configuration


Overview
Description

The SCCP data configuration is used to provide the routing service for the SCCP. In the R4 system, the MAP signaling between
the MSCS/VLR and entities (such as HLR) in the network is transferred through the SCCP. Each entity can be directly connected with
each other, and also can be connected with each other through
STPs. When receiving messages from the MAP application layer,
the SCCP will send, receive and forward these messages according to the route labels carried in the messages. The SCCP has two
routing modes: GT and DPC +SSN.
The difference between the GT and the DPC+SSN routing modes is
manifested in the case where there are STPs in the source signaling
point and the destination signaling point.
In the DPC+SSN routing mode, it is required that all the signaling
points (including the source signaling point, destination signaling
point, and STP) in the network can identify the Destination signaling Point Code (DPC). The signaling is directly sent from the MTP
layer after reaching the intermediate point instead of passing the
SCCP layer. In this case, more DPC data need to be configured for
the source signaling point and the STP.
The GT routing mode can be used when the final DPC of the signaling is unknown to the source signaling point and part of STPs.
When this addressing mode is adopted, and when the signaling is
transferred to the STP, the SCCP translates the GT to the destination signaling point or the DPC of the next-hop STP, and then
sends the message to the MTP for transfer. When the GT routing
mode is adopted, the source signaling point only needs to send
the signaling to the STP of the next-hop GT translation according
to the GT number prefix, and then the STP determines whether
to send the signaling to the next STP or the destination signaling
point . In this case, less DPC data need to be configured for the
source signaling point and the STP.

Data Configuration

The related operations of the SCCP data configuration are as follows.


No.

Operations

Instructions

Commands

Createing a
GT translation
selector

In general,
one or two GT
translation selectors
are configured,
corresponding to
E164 and E214
numbering plans
respectively

ADD GTT

Creating GT
translation data

Create the GT
translation data
for the source
address and the
destination address

ADD GT

Confidential and Proprietary Information of ZTE CORPORATION

249

ZXWN MSCS Data Configuration Guide(MSCS)

No.

Operations

Instructions

Commands

of the signaling on
each end point or
transfer point.

Creating a GT Translation Selector


Prerequisites

Context

Before the operation, it is required to confirm:

The exchange ID to be configured is given.

Interconnection with the adjacent HLR office is completed, and


the signaling office direction is successfully debugged.

The MML Terminal window is opened.

In general, one or two GT translation selectors are configured,


corresponding to E164 and E214 numbering plans respectively.
The numbers to be configured are described as follows:
1. E214 number
The format of the E.212 number is MCC+MNC+MSIN, while
that of the E.214 number is CC+NDC+MSIN, which are used
for location registration of mobile subscribers.
It is usually required to convert the MCC+MNC part to
CC+NDC according to mobile number analysis, to construct
the format of the E214 number.
2. E164 number
The format of the E.164 number is MSISDN, which is used for
communication when the mobile subscriber acts as the called
party, and the communication between mobile NEs.
During the location update debugging procedure, it is only required to configure the MSC/VLR GT and HLR GT of the local
office.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create a GT translation selector by executing command ADD
GTT.
The explanation of the main parameters in command ADD GTT
is shown in Table 92.

250

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

TABLE 92 PARAMETERS IN THE ADD GTT COMMAND


Parameter Name

GTT

TT

Parameter
Description

Instruction

GT type

It is a mandatory parameter,
raging from 1 to 4. When it
is 1, the GT contains address
attributes. When it is 2,
the GT contains translation
type. When it is 3, the GT
contains translation type,
numbering plan, and coding
design. When it is 4, the
GT contains translation type,
numbering plan, coding design,
and address attributes. GT4 is
selected by default

Translation type

It is a mandatory parameter,
ranging from 0 to 255. It is
the translation type of the GT
number, with the default value
as 0

Numbering plan,
including

PLAN

NULL (idle)

E.164
(ISDN/phone
numbering
plan)

E.214
(ISDN/mobile
numbering
plan)

X.121 (Data
numbering
plan)

F.69 (Telex
numbering
plan)

E.210(Maritime mobile
numbering
plan)

E.212 (Land
mobile
numbering
plan)

Reserved(2),
Reserved(8)Reserved (255):
Reserved

It is a mandatory parameter.
Select E.164 for the E164
format, and select E.214
for the E214 format. For
example, if the mobile number
is analyzed as HLR, select
E.164 for GT analysis of this
number. If the mobile number
is analyzed as ISDN, select
E.214 for GT analysis of this
number

Confidential and Proprietary Information of ZTE CORPORATION

251

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter Name

Parameter
Description

Instruction

Address attribute,
including

NATURE

SUB (address
attributes is
subscriber
number)

INT (address
attributes is
international
number)

NATRSV
(address
attributes
is national
reserved
number)

NATSIGN
(address
attributes is
national valid
number)

INAPSCP (SCP
standby)

CAMEL
(address
attributes is
intelligent
network service
number)

VACANT0, VACANT7 VACANT255: vacancy

It is a mandatory parameter.
Select INT

ID

GT translation
selector

It is an optional parameter,
ranging from 0 to 1023. It is
the global number of the GT
translation selector

CC

Country code

It is an optional parameter,
consisting of 0~4 digits. It is
86 in China

National minimum
digit length

They are optional parameters,


which are integers, ranging
from 1 to 20. They respectively
correspond to the national
minimum GT number length,
and national maximum GT
number length configured
in the GT translation data
configuration. In general, the
national minimum digit length
is set to 5, while the national
maximum digit length is set to
15

NMIN

252

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Parameter Name

Parameter
Description

NMAX

National maximum
bit length

IMIN

International
minimum digit
length

IMAX

International
maximum digit
length

CTRL

GT translation
attributes, including
R_L (intercepting
digits from the
number to be
analyzed from
right to left
for alignment,
corresponding
to the maximum
matching policy),
and L_R
((intercepting digits
from the number
to be analyzed
from left to right
for alignment,
corresponding
to the minimum
matching policy)

Instruction

They are optional parameters,


which are integers, ranging
from 1 to 20. They respectively
correspond to the international
minimum GT number length,
and international maximum
GT number length configured
in the GT translation data
configuration. In general, the
international minimum digit
length is set to 1, while the
international maximum digit
length is set to 5

It is an optional parameter,
with the default choice as
R_L. Maximum Matching
means match the number
from right to left. When
analyzing a GT number, search
the matched options with
the maximum length. GT
numbers are analyzed in the
descending order of their
lengths, facilitating reducing
the workload of GT data
configuration

It is a mandatory parameter,
consisting of 1~50 characters.
NAME

User alias

It is used to identify a GT
translation selector to make it
easily recognized

Example: Create a GT translation selector with the following


requirements:

GT type: 4

Translation type: 0

Numbering plan: E.164

Address attribute: international number

GT translation selector: 1

Confidential and Proprietary Information of ZTE CORPORATION

253

ZXWN MSCS Data Configuration Guide(MSCS)

National minimum digit length: 5

National maximum digit length: 15

International minimum digit length: 1

International maximum digit length: 5

User alias: E.164.

The command is:


ADD GTT:GTT=4,TT=0,PLAN=E.164,NATURE=INT,GTTO
PT=0,ID=1,CC="86",NMIN=5,NMAX=15,IMIN=1,IMAX
=5,CTRL=R_L,NAME="E.164";
Example: Create a GT translation selector with the following
requirements:

GT type: 4

Translation type: 0

Numbering plan: E.214

Address attribute: international number

GT translation selector: 2

National minimum digit length: 5

National maximum digit length: 15

International minimum digit length: 1

International maximum digit length: 5

User alias: E.214.

The command is:


ADD GTT:GTT=4,TT=0,PLAN=E.214,NATURE=INT,GTTO
PT=0,ID=2,CC="86",NMIN=5,NMAX=15,IMIN=1,IMAX
=5,CTRL=R_L,NAME="E.214";
END OF STEPS

Creating GT Translation Data


Prerequisites

Context

Before the operation, it is required to confirm:

The exchange ID to be configured is given.

GT translation selectors are configured.

The MML Terminal window is opened.

The GT translation data are used for location update, calls and
inter-office handover. When configuring GT translation data, it is
required to add the GT translation data for the source address
and the destination address of the signaling on each end point or
transfer point.
When configuring location update data, it is required to translate
the local GT number to the office ID 0, that is, local office, and
translate the GT number of the HLR to the HLR or STP. Therefore,
it is required to configure at lease two sets of GT translation data
on the MSCS.

254

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

E164 number: It is required to configure the local MSC/VLR GT,


MSISDN number, and the MSC/VLR GT having the LAI adjacency
relationship.
E214 number: It is required to configure the corresponding number in E214 format (CC+NDC+MSISDN) of the IMSI number (E212
format: MCC+NDC+MSISDN).
Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create GT translation data by executing command ADD GT.
The explanation of the main parameters in command ADD GT
is shown in Table 93.
TABLE 93 PARAMETERS IN THE ADD GT COMMAND
Parameter
Name

GT

OPGT

GTSL

Parameter
Description

Instruction

Called GT number

It is a mandatory parameter,
consisting of 1~20 digits.
It is used to query the
destination GT number of
message routing

Calling GT number

It is an optional parameter,
consisting of 0~20 digits.
It is the number of the
virtual MSC where the
subscriber is located during
GT translation. During GT
routing, query where there
are matched data according
to the VMSC where the
subscriber is located and the
target GT number. If there
are matched data, perform
GT translation based on the
matched data. If there is
no matched data, perform
translation again based on
that the calling GT number
is 0

GT translation
selector

It is a mandatory parameter,
ranging from 0 to 1023.
Select the GT translation
selector respectively
according to configured
E164 and E214 numbers

Confidential and Proprietary Information of ZTE CORPORATION

255

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction

Number change ID

It ranges from 0 to 256,


with the default value as
0. It is the ID of flexible
policy template change. The
target GT number can be
flexibly changed based on
it. When the GT translation
result contains a new GT,
this parameter does not
take effect

OFCIDS

Office ID and poll list

It is a mandatory parameter.
The number of instance is
1~4 when office ID grouping
is supported. The number
of instance is 1~16 when
office ID grouping is not
supported. The format
is <OFCID>-<SELNUM>,
representing the office ID to
be polled and the number of
poll respectively.

GRP

Whether to support
grouping of office ID

It is an optional parameter,
with a default of NO

The office ID and


poll number of the
multiple signaling
points for the second
group

It is an optional parameter.
The number of instance is
1~4 when office ID grouping
is supported. The user
does not need to type when
the office ID grouping is
supported. The format
is <OFCID>-<SELNUM>,
representing the office ID to
be polled and the number of
poll respectively.

The office ID and


poll number of the
multiple signaling
points for the third
group

It is an optional parameter.
The number of instance is
1~4 when office ID grouping
is supported. The user
does not need to type when
the office ID grouping is
supported. The format
is <OFCID>-<SELNUM>,
representing the office ID to
be polled and the number of
poll respectively.

The office ID and


poll number of the
multiple signaling
points for the fourth
group

It is an optional parameter.
The number of instance is
1~4 when office ID grouping
is supported. The user
does not need to type when
the office ID grouping is
supported. The format
is <OFCID>-<SELNUM>,
representing the office ID to
be polled and the number of
poll respectively.

GTDI

OFCGRP2

OFCGRP3

OFCGRP34

256

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Parameter
Name

Parameter
Description

Instruction

SSN

Subsystem No. Refer


to Table 94 for the
options involved

It is an optional parameter.
In the GT routing mode,
select the default value
for SSN. In the DPC+SSN
routing mode, select the
corresponding SSN

NGT

New GT number

It is an optional parameter,
ranging from 0 to 20 of
characters. It represents
the new GT translation type.

NTRNTYPE

New GT translation
type

It is an optional parameter,
ranging from 0 to 255.
It represents the new GT
translation type.

TRNRLT

Whether the
translation result
contains DPC and
SSN. The options
includes NULL
(neither DPC nor
SSN is in the result),
DPC (containing DPC
in the result), and
SSN (containing SSN
in the result)

It is an optional parameter.
In the GT routing mode,
select the default value for
TRNRLT. In the DPC+SSN
routing mode, select the
DPC and SSN for TRNRLT

RTTYPE

Routing mode,
including GT (routing
based on GT) and
DPC (routing based
on DPC+SSN)

It is an optional parameter.
In general, select GT for
direct connection, and
DPC+SSN for non-direct
connection

Attribute of the new


GT , including the
following options:
NGT (No new GT in
the GT translation
result): The GT
number in the GT
translation result is
still the called GT
number.
NGTTAG

NAI: The GT number


in the GT translation
result is the new
GT number in the
NGT parameter, only
containing Nature
Of Address Indicator
(NAI).

It is an optional parameter.
It is the attribute of the
new GT contained in the GT
translation result. NGT(No
new GT in the GT translation
result) is selected by default

NTT: The GT number


in the GT translation
result is the new
GT number in the
NGT parameter, only
containing translation
type.

Confidential and Proprietary Information of ZTE CORPORATION

257

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction

NTTES: The GT
number in the GT
translation result is
the new GT number
in the NGT parameter,
only containing
translation type,
numbering plan, and
coding design.
NTTNAI: The GT
number in the GT
translation result is
the new GT number
in the NGT parameter,
containing translation
type, numbering plan,
coding design, and
NAI
SCCP coding type,
including:
SCCP

INT (international
coding) and USA(USA
coding)

It is an optional parameter.
It indicates the standard
type referred to by the SCCP
coding in the GT translation
result. The default value is
INT

VGT

GT varying with
different office IDs,
including NO (not
supported), and YES
(supported)

It is an optional parameter,
with NO as the default value

TT

TT conversion,
including NO (not
supported), and YES
(supported)

It is an optional parameter,
with NO as the default value

NAME

Alias

The alias of the GT


translation data for easy
memory.

TABLE 94 SSN

258

SSN

Meaning

NO_SSN

Not containing SSN

SCCP

SCCP

ISUP

ISDN user part

OMAP

Operation and maintenance application part

MAP

Mobile user part

HLR

Home location register

VLR

Visitor location register

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

SSN

Meaning

MSC

Mobile switching center

EIR

Equipment identity register

AUC

Authentication center

ISDN/ASE

ISDN_ASE(11)

INAP/OTA

INAP/OTA subsystem

USSD

USSD

VLRA

VLRA

SGSN_BSCAP

SGSN BSCAP

RANAP

RANAP

RNSAP

RNSAP

GMLC_MAP

GMLC MAP

CAP

CAP

GSMSCF_MAP

GSMSCF MAP

SIWF_MAP

SIWF MAP

SGSN_MAP

SGSN MAP

GGSN_MAP

GGSN MAP

IP

IP

SMC

SMC subsystem

SSP_SCP

SSPSCP subsystem

BSC_BSSAP_LE/MPC

BSC_BSSAP_LE/MPC

MSC_BSSAP_LE

MSC_BSSAP_LE

SMLC_BSSAP_LE

SMLC_BSSAP_LE

BSS_O_M_A

BSS_O_M_A

BSSAP_A

BSSAP_A

NPDB

NPDB

ATER

ATER

UDS_DMCC

UDS_DMCC

Other Reserved

Reserved

Example: Create the HLR GT translation data with the following


requirements:

Confidential and Proprietary Information of ZTE CORPORATION

259

ZXWN MSCS Data Configuration Guide(MSCS)

GT number: 8613907551

GT translation selector ID: 1

Office ID poll: 1-1

Routing mode: GT routing

Other parameters: Adopt default values.

The command is:


ADD GT:GT="8613907551",OPGT="1",GTSL=0,GTDI=0,O
FCIDS="1"-"1",GRP=NO,SSN=NO_SSN,NTRNTYPE=0,TR
NRLT="NULL",RTTYPE=GT,NGTTAG=NGT,SCCP=INT,VGT
=NO,TT=NO,NPFLAG=NO,NPLAN=NULL,SRVTYPE=NULL;
END OF STEPS

Roaming Data Configuration


Overview
Description

Data Configuration

The following conditions can judge whether a subscriber is roaming:

Whether the subscriber roams from one country to another


one: Based on the MCC, compare the MCC configured in the
local-office mobile data configuration.

Whether the subscriber roams from one network to another


one: Based on the MNC, compare the MNC configured in the
local-office mobile data configuration, and the MNCs configured
in the local-office other-MNC configuration.

Whether the subscriber roams within a LAI: Based on the number in the IMSI excluding the MCC and MNC, compare the location number configured in the LAI configuration, and the area
code configured in the mobile-network area-code configuration.

The related operations of the roaming data configuration are as


follows.
Steps

260

Operations

Instructions

Commands

Creating IMSI number


analysis

IMSI number
analysis is used
to convert the
IMSI number to
another number
or a number that
can address the
HLR

ADD IMSI
ANA

Creating a mobile service


access number and MNC

Configure the
relationship
between a
mobile service

ADD
NDCMNC

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Steps

Operations

Instructions

Commands

access number
and a MNC for
inter-network
roaming

Creating a mobile network


ID and area code mapping

Configure the
relationship
between a mobile
network ID and
a area code to
judge whether
a subscribers is
roaming

ADD
NCCFG

Creating IMSI Number Analysis


Prerequisites

Context

Before the operation, it is required to confirm:

The exchange ID to be configured is given.

The MML Terminal window is opened.

IMSI number analysis is used to convert the IMSI number to a


number that can address the HLR. The VLRMAP performs GT translation through this number to address the HLR where the IMSI is
registered. Create IMSI number analysis according to the roaming
data provided by operators, usually configuring the local-network
and international roaming data.
Background
In IMSI number analysis, it is required to set the home destination
code type, which can be ISDN or HLR.
1. ISDN
The corresponding number prefix in the IMSI is converted into
the specified analysis result, and the rest digits are added
behind the analysis result. For example, if the analyzed
number is 46000, it is converted to 86139, the network-admitted IMSI number is 460001234567890, the corresponding
Country Code (CC) is 86, and the Network Destination Code
(NDC) is 139. In this mode, this IMSI number is analyzed
into 86139123456789046000. Based on this, the typical
application of this mode is to convert the MCC+MNC in the
IMSI into the CC+NDC, and keep the rest part, forming the
E214 number format.
2. HLR
The corresponding number prefix in the IMSI is converted into
the specified analysis result, and the rest digits are deleted. For
example, if the analyzed number is 46000, it is converted to the
GT number 8613903066 of the HLR, and the network-admitted
IMSI number is 460001234567890. In this mode, this IMSI
number is analyzed to 8613903066, that is the GT number of
the HLR. Based on this, the typical application of this mode is
to convert the IMSI headed by specific MCC+MNC into the GT
number of a HLR.

Confidential and Proprietary Information of ZTE CORPORATION

261

ZXWN MSCS Data Configuration Guide(MSCS)

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Creating IMSI number analysis by executing command ADD
IMSIANA.
The explanation of the main parameters in command ADD
IMSIANA is shown in Table 95.
TABLE 95 PARAMETERS IN THE ADD IMSIANA COMMAND
Parameter
Name

IMSI

HDSTCODE

Parameter
Description

Instruction

IMSI prefix

It is a mandatory parameter,
consisting of 20-digit integers
at most. It is the MCC+MNC
in the IMSI

Home destination
code

It is a mandatory parameter,
consisting of 16-digit integers
at most. It is the number that
the IMSI number is converted
to. It is of the format of
CC+NDC or the HLR GT
number in general
It is an optional parameter.
HLR: When there is a specific
HLR number, select HLR

262

HDSTCODET

Home destination
code type,
including ISDN
and HLR

NAME

Alias

Confidential and Proprietary Information of ZTE CORPORATION

ISDN: The MAP makes the


analyzed home destination
code replace the CC in
an IMSI to form the
corresponding destination
number of this IMSI. For
example, if the IMSI is
46003091212, and the
home destination code is
87, the translated result is
8703091212. The ISDN
mode is usually used
for international roaming
subscribers
It is used to describe a piece
of IMSI analysis record for
easy memory. It consists of
50-digit integers at most.

Chapter 8 Basic Service Data Configuration

Parameter
Name

Parameter
Description

Instruction

Whether to enable
options, including:

ENOTHOPT

CRTN:
Criterion

PRDG:
Predigestion
and SMS
Format

CHKIMEI:
CheckIMEI
ADD

Format code of
short message

SM

OPID

Operator ID

Whether to enable options


related to HLR.

The parameter ranges from 0


to 255, with a default of
0
The parameter ranges from 0
to 255, with a default of
0

INDADC

Independent
ADC GT
Number,inclduding

NO

YES

It is an optional parameter.

Example: Configure the IMSI number analysis with the following requirements:

Prefix: 46000

Home destination code: 86139

Home destination code type: ISDN

Other parameters: Adopt default values.

The command is:


ADD IMSIANA:IMSI="46000",HDSTCODE="86139",HDST
CODET=ISDN,SM=0,OPID=0,INDADC=NO;
END OF STEPS

Creating a Mobile Service Access Number and


MNC
Prerequisites

Context

Before the operation, it is required to confirm:

The exchange ID to be configured is given.

The MML Terminal window is opened.

This section introduces how to configure the relationship between a


mobile service access number and a MNC for inter-network roaming.

Confidential and Proprietary Information of ZTE CORPORATION

263

ZXWN MSCS Data Configuration Guide(MSCS)

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the relationship between a mobile service access number and a MNC by executing command ADD NDCMNC.
The explanation of the main parameters in command ADD
NDCMNC is shown in Table 96.
TABLE 96 PARAMETERS IN THE ADD NDCMNC COMMAND
Parameter
Name

Parameter
Description

Instruction

NAME

User alias

It is a mandatory parameter,
consisting of 0~50
characters. It is used to
describe the relationship
between a mobile service
access number and a MNC

ID

Access number
configuration ID

It identifies the order of


configuring access numbers,
ranging from 1 to 1000

Country code

It indicates the CC of the


mobile service access code.
Enter it according to the
actual condition, with the
default value as 86

NDC

National destination
code

It indicates the mobile digital


service access number. Enter
it according to the actual
condition, with the default
value as 139

MCC

Mobile country code

Enter it according to the


actual condition, with the
default value as 460

MNC

Mobile network code

Enter it according to the


actual condition, with the
default value as 01

CC

Example: Create the relationship between a mobile service


access number and a MNC with the following requirements.

Mobile service access number: 139

Access number configuration ID: 1

CC: 86

MCC: 460

MNC: 00.

The command is:

264

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

ADD NDCMNC:NAME="139",ID=1,CC="86",NDC="139",M
CC="460",MNC="00";
END OF STEPS

Creating a Mobile Network ID and Area Code


Mapping
Prerequisites

Before the operation, it is required to confirm:

The exchange ID to be configured is given.

The MML Terminal window is opened.

Context

This section introduces how to configure the relationship between


a mobile network ID and a area code to judge whether a subscribers is roaming.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create the relationship between a mobile network ID and an
area code by executing command ADD NCCFG.
The explanation of the main parameters in command ADD
NCCFG is shown in Table 97.
TABLE 97 PARAMETERS IN THE ADD NCCFG COMMAND
Parameter
Name

Parameter
Description

Instruction

MSIN

Mobile subscriber
identification
number

It is a mandatory parameter.
Enter the No. 3-8 digits in
the IMSI except MCC+MNC

Area code

It is a mandatory parameter.
Enter the area code of the
area where the subscriber
belongs

ACODE

Example: Create the relationship between a mobile network


ID and an area code with the following requirements.

Mobile Subscriber Identification Number: 1234

Area code: 25.

The command is:


ADD NCCFG:MSIN="1234",ACODE="25";
END OF STEPS

Confidential and Proprietary Information of ZTE CORPORATION

265

ZXWN MSCS Data Configuration Guide(MSCS)

Call Data Configuration


Number Analysis Configuration
Number Analysis
The switch performs network addressing based on each type of
numbers. In the mobile switch, there are two types of numbers.
One type is subscriber number, including fixed subscriber number
and mobile subscriber number. The other type is network number, including Mobile Station Roaming Number (MSRN), MSC/VLR
number, HLR number, and handover number. ZXWN MSCS number analysis configuration is used to determine the corresponding
network addressing and service processing methods of each type
of number to ensure that the switch can correctly perform signaling interaction and voice channel connection.
ZXWN MSCS system provides seven number analyzers: new service number analyzer, CENTREX number analyzer, private-network
number analyzer, special-service number analyzer, local-network
number analyzer, national toll-service number analyzer, and international toll-service number analyzer. For a specified DAS, numbers pass each type of analyzers specified by this DAS in a fixed
order. The analyzers strictly follow the following order to perform
number analysis, as shown in Figure 63.
FIGURE 63 ANALYSIS ORDER OF NUMBER ANALYZERS

Configuration instances of common DASs and the number analysis


results are as follows:
1. DAS for pre-analyzing the called number
It is used to process special dial prefixes, including performing
call restriction, format conversion of the called number.

266

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

After an exchange receives 10193+called number dialed by


a subscriber, 10193 is deleted in this exchange, and the subsequent routing is based on the existing traffic routing, as shown
in Table 98.
TABLE 98 DAS FOR PRE-ANALYZING THE CALLED NUMBER
Analyzer
Entry

Analyzed Number

Analysis Result
If call restriction is
required, analyze it to
pre-analysis ending, and
call rejected

10193 + 0 + local area


code

New
service
number
analyzer

10193 + 0 + non-local
area code
10193 + G network
number section

10193 + C network
number section

If no call restriction is
required, analyze it to
pre-analysis normally
ending, and delete
10193 + 0 + local area
code from the change
index of the called
number
Analyze it to
pre-analysis normally
ending, and delete
10193 from the change
index of the called
number.
Whether to add 10193 to
the called-number index
in the CDR depends
on the CDR filling
requirements on the
billing center

2. Originating DAS: used to analyze the called number in the local-office-originated call, as shown in Table 99.
TABLE 99 ORIGINATING DAS
Analyzer
Entry

Analyzed Number

Analysis Result

New
service
number
analyzer

Charging query number

Analyze it to the SSP


charging query service

Free special-service
number

Analyze it to the
local-office free special
service, pointing to
the special-service
number configured on
the attendant console

Corresponding attendant
console number of the
special-service number

Analyze it to the
outgoing free special
service, pointing to the
special-service circuit
group

Specialservice
number
analyzer

Confidential and Proprietary Information of ZTE CORPORATION

267

ZXWN MSCS Data Configuration Guide(MSCS)

Analyzer
Entry

Analyzed Number

Analysis Result

Short number

Special-service number
of the operator

Analyze it to the
outgoing free special
service, pointing to the
special-service circuit
group
Vacant number

Localnetwork
number
analyzer

All numbers are analyzed


by the subsequent
analyzers

Local PSTN number

Analyze it to
the local-network
outgoing/local-call
service, pointing to
the gateway office

Local number section of


other mobile network

Analyze it to
the local-network
outgoing/local-call
service, pointing to
the gateway office

Non-local number section


of other mobile network

Analyze it to the
automatic service in
the national toll region,
pointing to the tandem
office of the local province

Number section of the


local mobile network

Analyze it to the MSC


common service
Vacant number

National
toll-service
number
analyzer

International
toll-service number
analyzer

All numbers are analyzed


by the subsequent
analyzers

0 + Local area code +


Local PSTN number

Analyze it to
the local-network
outgoing/local-call
service, pointing to
the gateway office

0 + Non-local area code

Analyze it to the
automatic service in
the national toll region,
pointing to the tandem
office of the local province

00 + International
number

Analyze it to the
international toll
automatic service

3. Forwarding DAS: used to analyze the number to which the call


is forwarded, as shown in Table 100.

268

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

TABLE 100 FORWARDING DAS


Analyzer Entry

Analyzed Number

Analysis Result
Vacant number

Local-network
number analyzer

All numbers are


analyzed by
the subsequent
analyzers

Local PSTN number

Analyze it to the
local-network
outgoing/local-call
service, pointing to
the gateway office

Local number
section of other
mobile network

Analyze it to the
local-network
outgoing/local-call
service, pointing to
the gateway office

Non-local number
section of other
mobile network

Analyze it to the
automatic service
in the national toll
region, pointing to
the tandem office of
the local province

Number section of
the local mobile
network

Analyze it to the MSC


common service
Vacant number

National toll-service
number analyzer

All numbers are


analyzed by
the subsequent
analyzers

0 + Local area
code + Local PSTN
number

Analyze it to the
local-network
outgoing/local-call
service, pointing to
the gateway office

0 + Non-local area
code

Analyze it to the
automatic service
in the national toll
region, pointing to
the tandem office of
the local province

4. Roaming DAS: used to analyze the roaming number in the response message to the routing information query message, as
shown in Table 101. It is unnecessary to analysis the CC in
national roaming numbers.

Confidential and Proprietary Information of ZTE CORPORATION

269

ZXWN MSCS Data Configuration Guide(MSCS)

TABLE 101 ROAMING DAS


Analyzer Entry

Analyzed Number

Analysis Result

Roaming number
section of the local
service area in the
local office

Analyze it to the
local MSC service
Analyze it to the
outgoing service of
the local MSC.

Local-network
number analyzer

Roaming number
section of non-local
service area in the
local office

Note: The roaming


DAS is used when
there is no direct
voice channel
between MGWs
(switched through
the T office) in the
region networking

National other
roaming sections

Analyze it to the
national toll call

00 + International
number

Analyze it to the
international toll
automatic service

Overview
Description

This section only introduces the basic steps of number analysis.


For detailed configuration related with number analysis (including number pre-analysis, calling number analysis, and number
change), refer to ZXWN MSCS MSC Server Number Analysis.

Data Configuration

The related operations of the number analysis configuration are as


follows.
Steps

Operations

Instructions

Commands

Creating a number
analyzer entry

Specify an ID
for each type of
number analyzers

ADD ENTR

Creating a DAS

The DAS is the


collection of
various number
analyzer entries,
specifying the
order and rule
of performing
number analysis.

ADD DAS

Setting the default


DAS template of
the local office

Set the default


DAS template
of the local
office means
creating the DAS
used for localoffice service
processing.

SET LDASTM
PLT

270

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Steps

Operations

Instructions

Commands

Creating a
DAS template
(optional)

Create multiple
DAS templates in
the dual-homing
or regional
networking.

ADD ACRTMPLT

Creating the called


numbers analysis

Create number
analysis for
prefixes of called
numbers and
roaming numbers

ADD TPDNAL

Creating a Number Analyzer Entry


Prerequisites

Before the operation, it is required to confirm:

The exchange ID to be configured is given.

The number analyzer entry range is set in the resource management system.

The MML Terminal window is opened.

Context

Creating number analyzer entries means specifying an ID for each


type of number analyzers.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create a number analyzer entry by executing command ADD
ENTR.
The explanation of the main parameters in command ADD
ENTR is shown in Table 102.
TABLE 102 PARAMETERS IN THE ADD ENTR COMMAND
Parameter
Name

Parameter Description

Instruction

ID

Analyzer entry

It is an optional
parameter, which is
an integer, ranging from
1 to 1000

NAME

User alias

It is a mandatory
parameter, consisting of
0~50 characters

TYPE

Analyzer entry type

It is an optional
parameter. Refer
to Table 103 for the
configuration description

NTYPE

Number analysis result


under this analyzer,

It is an optional
parameter, with CALLED

Confidential and Proprietary Information of ZTE CORPORATION

271

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

VMSCIDX

Parameter Description
including CALLED
(analysis on called
numbers), CALLING
(analysis on calling
numbers), FORWARD
(analysis on calling
numbers during call
forwarding), OPIMSI
(analysis on calling IMSI
numbers), TPIMSI
(analysis on called
IMSI numbers), and
FWDIMSI (analysis on
IMSI numbers during
call forwarding)

Virtual MSC index

Instruction

as the default value. In


general, select CALLED

It is an optional
parameter, which is
an integer, ranging
from 0 to 65535. Enter
it according to the
actual condition. The
default value is 0 (public
domain)

TABLE 103 ANALYZER ENTRY TYPES


Parameter
Name

Parameter Description

Configuration
Description

NEWSRV

New service number


analyzer

After this analyzer


is configured, if the
number is not matched
in this analyzer, it is sent
to the next entry for
analysis

CENTREX

CENTREX number
analyzer

This analyzer is not


configured

PRINET

Private-network number
analyzer

This analyzer is not


configured

Special-service number
analyzer

After this analyzer


is configured, if the
number is not matched
in this analyzer, it is is
sent to the next entry
for analysis

LOCAL

Local-network number
analyzer

After this analyzer


is configured, if the
number is not matched
in this analyzer, the
analysis ends

NATIONAL

National toll-service
number analyzer

After this analyzer


is configured, if the
number is not matched

SPECSRV

272

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Parameter
Name

Parameter Description

Configuration
Description
in this analyzer, the
analysis ends

INTER

International toll-service
number analyzer

After the number is


analyzed in this analyzer,
the analysis ends

Example: Create a number analyzer entry with the following


requirements.

Number analyzer entry ID: 1

User alias: Entr1

Number analyzer entry type: Local number analyzer

Analyzed number type: Called number.

The command is:


ADD ENTR:ID=1,NAME="Entr1",TYPE=LOCAL,NTYPE=CAL
LED;
END OF STEPS

Creating a DAS
Prerequisites

Context

Before the operation, it is required to confirm:

The exchange ID to be configured is given.

The DAS range is set in the resource management system.

The number analyzer entry is configured.

The MML Terminal window is opened.

The DAS is the collection of various number analyzer entries, specifying the order and rule of performing number analysis.
Table 104 lists common DASs.
TABLE 104 COMMON DASS
Parameter
Name

Parameter Description

Configuration
Description

MS

MS originating

Used to analyze the called


number when an MS
originates a call

MSRN

Mobile station roaming


number

Used to analyze roaming


numbers or handover
numbers

CNG

Calling number analysis

Used for traffic division of


calling numbers

LI

Intercepted number

Used for the interception


function

Confidential and Proprietary Information of ZTE CORPORATION

273

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter Description

Configuration
Description

PBRT

Personal Back Ring Tone

Used for the PBRT function

FWD

Forwarding number
analysis

Used to analyze the


third-party number to
which the call is forwarded

Number pre-analysis

Used for the number


pre-analysis function,
standardizing called
numbers, and performing
call restriction based on
numbers

PREDAS

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create a DAS by executing command ADD DAS.
The explanation of the main parameters in command ADD DAS
is shown in Table 105.
TABLE 105 PARAMETERS IN THE ADD DAS COMMAND
Parameter
Name

274

Parameter Description

Instruction

ID

DAS

It is a mandatory
parameter, which is an
integer, ranging from
1 to 4096. It is the
index number of the
newly-added DAS

NAME

User alias

It is an optional
parameter, consisting of
0~50 characters.

NEWSRV

New service number


analyzer entry

CENTR

CENTREX number
analyzer entry

PRINET

Private-network number
analyzer entry

SPECSRV

Special-service number
analyzer entry

LOCAL

Local-network number
analyzer entry

NATIONAL

National toll-service
number analyzer entry

Confidential and Proprietary Information of ZTE CORPORATION

Enter the umber


analyzer entry IDs
contained by a DAS

Chapter 8 Basic Service Data Configuration

Parameter
Name

Parameter Description

INTER

International
toll-service number
analyzer entry

VMSCIDX

Virtual MSC index

Instruction

Example: Create a MS originating DAS with the following requirements.

DAS ID: 101

User alias: MSQH

Local number analyzer entry: 1

Other parameters: Adopt the default values.

The command is:


ADD
DAS:ID=101,NAME="MSQH",NEWSRV=0,CENTR
=0,PRINET=0,SPECSRV=0,LOCAL=1,NATIONAL=0,INTE
R=0;
END OF STEPS

Setting the Default DAS Template of the Local


Office
Prerequisites

Before the operation, it is required to confirm:

The exchange ID to be configured is given.

The DAS is configured.

The MML Terminal window is opened.

Context

Creating the default DAS template of the local office means creating the DAS used for local-office service processing.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Set the default DAS template of the local office by executing
command SET LDASTMPLT.
The explanation of the main parameters in command SET
LDASTMPLT is shown in Table 106.

Confidential and Proprietary Information of ZTE CORPORATION

275

ZXWN MSCS Data Configuration Guide(MSCS)

TABLE 106 PARAMETERS IN THE SET LDASTMPLT COMMAND


Parameter Name

MS

MSRN

Parameter
Description

Instruction

MS originating
DAS

It is an optional parameter, which


is an integer, ranging from 0
to 4096. It is used to analyze
the called number when an MS
originates a call. If the called
party is a mobile subscriber,
the MSC needs to query the
routing information from the
corresponding HLR. If the called
party is a fixed subscriber, the
MSC connect the call to the
corresponding local exchange or
toll exchange according to location
of the called party

MSRN DAS

It is an optional parameter, which


is an integer, ranging from 0
to 4096. It is used to analyze
the MSRN returned from the
HLR, and judge whether the call
belongs to the local-office mobile
service or outgoing mobile service
based on this number. If the call
belongs to the local-office mobile
service, this number is sent to
the corresponding module for
processing. If the call belongs to
the outgoing mobile service, select
the corresponding route chain
for call connection. In addition,
this DAS also analyzes forwarding
numbers returned from the HLR,
and subscriber numbers from
other mobile office or fixed office
It is an optional parameter, which
is an integer, ranging from 0 to
4096.

OR

Preferred
routing DAS

When it is set that the local office


supports preferred routing in the
global variable control system,
configure this DAS for international
roaming call and the forwarding
service
It is an optional parameter, which
is an integer, ranging from 0 to
4096.

CNG

LI

276

Calling number
DAS

Interception
DAS

It is used to analyze the calling


number in outgoing calls to
implement traffic division of the
calling number and calling number
change function
It is an optional parameter, which
is an integer, ranging from 0 to
4096.
It is used for the interception
service

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Parameter Name

IP

Parameter
Description

IP DAS

Instruction
It is an optional parameter, which
is an integer, ranging from 0 to
4096.
It is used for the IP telephone
service

ICBCNG

PBRT

Incoming call
restriction DAS
for calling
numbers

PBRT DAS

It is an optional parameter, which


is an integer, ranging from 0 to
4096.
It is used for the incoming call
restriction service
It is an optional parameter, which
is an integer, ranging from 0 to
4096.
It is used for the PBRT service

FWD

Forwarding DAS

It is an optional parameter, which


is an integer, ranging from 0 to
4096

FWDCNG

Forwarding
DAS for calling
numbers

It is an optional parameter, which


is an integer, ranging from 0 to
4096

CNGVIGW

Calling number
DAS of virtual
IGW

It is an optional parameter, which


is an integer, ranging from 0 to
4096

FWDVIGW

Forwarding DAS
of virtual IGW

It is an optional parameter, which


is an integer, ranging from 0 to
4096

INTRA

Wire and
wireless
integrated DAS

It is an optional parameter, which


is an integer, ranging from 0 to
4096. It is used for the function
of one number for two MSs and
mixed group

ROUTCAT1

MS originating
DAS for
category-1
subscribers

It is an optional parameter, which


is an integer, ranging from 0 to
4096

ROUTCAT2

MS originating
DAS for
category-2
subscribers

It is an optional parameter, which


is an integer, ranging from 0 to
4096

ROUTCAT3

MS originating
DAS for
category-3
subscribers

It is an optional parameter, which


is an integer, ranging from 0 to
4096

ROUTCAT4

MS originating
DAS for
category-4
subscribers

It is an optional parameter, which


is an integer, ranging from 0 to
4096

Confidential and Proprietary Information of ZTE CORPORATION

277

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter Name

Parameter
Description

Instruction

ROUTCAT5

MS originating
DAS for
category-5
subscribers

It is an optional parameter, which


is an integer, ranging from 0 to
4096

IMSIOPDAS

Outgoing IMSI
traffic division
DAS

It is an optional parameter, which


is an integer, ranging from 0 to
4096

OVERLAY

Calling
OVERLAY DAS

It is an optional parameter, which


is an integer, ranging from 0 to
4096

IGWMONITOR

IGW
interception
DAS

It is an optional parameter, which


is an integer, ranging from 0 to
4096

SHLRSKEY

SHLR service
key conversion
DAS

It is an optional parameter, which


is an integer, ranging from 0 to
4096

IMSITPDAS

DAS for called


IMSI

It is an optional parameter, which


is an integer, ranging from 0 to
4096

IMSIFWDAS

DAS for the


IMSI of the
subscriber to
whom the call is
forwarded

It is an optional parameter, which


is an integer, ranging from 0 to
4096

TESTCALLDAS

Test call DAS

It is an optional parameter, which


is an integer, ranging from 0 to
4096

MRBT

Multi-media
ring back tone
DAS

It is an optional parameter, which


is an integer, ranging from 0 to
4096

INTPREDAS

International
number
pre-analysis
DAS

It is an optional parameter, which


is an integer, ranging from 0 to
4096

PREDAS

Number
pre-analysis
DAS

It is an optional parameter, which


is an integer, ranging from 0 to
1000

RECNCTDAS

Reconnection
DAS

It is an optional parameter, which


is an integer, ranging from 0 to
4096

Example: Configure the default DAS template of the local office


with the following requirements.

MS originating DAS: 101

MSRN DAS: 201

Forwarding DAS: 301.

The command is:

278

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

SET LDASTMPLT:MS=101,MSRN=201,FWD=301;
END OF STEPS

Creating a DAS Template


Prerequisites

Before the operation, it is required to confirm:

The exchange ID to be configured is given.

The MML Terminal window is opened.

Context

It is required to create multiple DAS templates in the dual-homing


or regional networking.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create a DAS template by executing command ADD ACRTMP
LT.
The explanation of the main parameters in command ADD
ACRTMPLT is shown in Table 107.
TABLE 107 PARAMETERS IN THE ADD ACRTMPLT COMMAND
Parameter
Name

Parameter Description

Instruction

TMPLIDX

Routing template ID

It is a mandatory
parameter, ranging
from 1~65535

NAME

User alias

It is a mandatory
parameter, consisting
of 1~50 characters

MS

MS originating DAS

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

MSRN

MSRN DAS

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

OR

Preferred routing DAS

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

CNG

Calling number DAS

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

Confidential and Proprietary Information of ZTE CORPORATION

279

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter Description

Instruction

LI

Interception DAS

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

IP

IP DAS

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

CBCNG

Incoming call restriction


DAS for calling numbers

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

PRBT DAS

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

FWD

Forwarding DAS

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

FWDCNG

Forwarding DAS for


calling numbers

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

CNGVIGW

Calling number DAS of


virtual IGW

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

FWDVIGW

Forwarding DAS of
virtual IGW

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

INTRA

Wire and wireless


integrated DAS

It is an optional
parameter, which is
an integer, ranging from
0 to 4096. It is used
for the function of one
number for two MSs and
mixed group

ROUTCAT1

MS originating DAS for


category-1 subscribers

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

ROUTCAT2

MS originating DAS for


category-2 subscribers

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

PBRT

280

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Parameter
Name

Parameter Description

Instruction

ROUTCAT3

MS originating DAS for


category-3 subscribers

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

ROUTCAT4

MS originating DAS for


category-4 subscribers

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

ROUTCAT5

MS originating DAS for


category-5 subscribers

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

IMSIOPDAS

Calling IMSI number


selector

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

OVERLAY

Calling OVERLAY DAS

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

LIIGW

IGW interception DAS

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

SHLRSKEY

SHLR service key DAS

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

IMSITPDAS

DAS for called IMSI

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

IMSIFWDAS

DAS for the IMSI of the


subscriber to whom the
call is forwarded

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

MBRT

Multi-media ring back


tone DAS

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

INTPREDAS

International number
pre-analysis DAS

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

Confidential and Proprietary Information of ZTE CORPORATION

281

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter Description

Instruction

PREDAS

Number pre-analysis
DAS

It is an optional
parameter, which is
an integer, ranging from
0 to 1000

Reconnection DAS

It is an optional
parameter, which is
an integer, ranging from
0 to 4096

RECNCTDAS

Example: Add a DAS template with the following requirements.

DAS template ID: 1

User alias: VMSC1

MS originating DAS: 101

MSRN DAS: 201

Preferred routing DAS: 301

Calling number DAS: 401

Other parameters: Adopt the default values.

The command is:


ADD
ACRTMPLT:TPLIDX=1,NAME="VMSC1",MS=101,M
SRN=201,OR=301,CNG=401,LI=0,IP=0,CBCNG=0,PBRT
=0,CFU=0,CFUCNG=0,CFNDUB=0,CFNDUBCNG=0,CFUD
UB=0,CFUDUBCNG=0,CFNRC_E=0,CFNRCCNG_E=0,CF
NRC_L=0,CFNRCCNG_L=0,CFNRY=0,CFNRYCNG=0,CD
=0,CDCNG=0,FWD=0,FWDCNG=0,CNGVIGW=0,FWDVI
GW=0,INTRA=0,ROUTCAT1=0,ROUTCAT2=0,ROUTCAT3
=0,ROUTCAT4=0,ROUTCAT5=0,IMSIOPDAS=0,OVERLA
Y=0,LIIGW=0,SHLRSKEY=0,IMSITPDAS=0,IMSIFWDAS
=0,MBRT=0,INTPREDAS=0,PREDAS=0,CFPRE=0,CFUPR
E=0,NDUBPRE=0,UDUBPRE=0,CFNRCE_PRE=0,CFNRCL_
PRE=0,CFNRYPRE=0,CDPRE=0,MORCPRE=0,GMSCRCPR
E=0,CFRCPRE=0,MTRCPRE=0,RECNCTDAS=0,CAMELDN
ALIDX=0,SSDAS=0,ASCODEDAS=0;
END OF STEPS

Creating the Called Number Analysis


Prerequisites

Context

282

Before the operation, it is required to confirm:

The exchange ID to be configured is given.

The number analyzer entry is configured.

The MML Terminal window is opened.

This section introduces how to configure number analysis for prefixes of called numbers and roaming numbers. The called number
analysis determines the subsequent service procedures of the call.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Analyze the prefix of a called number or roaming number by
executing command ADD TPDNAL.
The explanation of the main parameters in command ADD
TPDNAL is shown in Table 108.
TABLE 108 PARAMETERS IN THE ADD TPDNAL COMMAND
Parameter
Name

ENTR

DIGIT

Parameter
Description

Instruction

Number
analyzer entry

It is a mandatory parameter, which


is an integer, ranging from 1 to
1000. Select the corresponding
analyzer entry of the analyzed
number prefix. For local calls,
select the corresponding analyzer
entry of the local number analyzer

Analyzer
number

It is a mandatory parameter,
consisting of 1~20 digits. Input
the prefix of the called number,
whose length must make it be
distinguished in the local office.
For intra-office calls, it is required
to configure both the prefix of
the called number and that of the
local-office roaming number
It is an optional parameter,
consisting of 0~50 characters.

NAME

SPECRST

User alias

Special analysis
result rule

It is used to specifically describe


the called number analysis to
make it easily recognized
It is used to specify the index
number of the special analysis
result rule for the associated called
number. This parameter must
be defined by command ADD
CEDSPECRL at first. Then it can
be indexed here. This parameter
is configured to implement the
routing service based on number
length. When the system performs
analysis on the called number,
it automatically matches the
actual length of the called number
to see whether the length is
within the range of Special
analysis result rule for called
numbers. If the length is within
the range, the system adopts the
routing information in Special
analysis result of called numbers.
Otherwise, the system adopts the

Confidential and Proprietary Information of ZTE CORPORATION

283

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction
routing information in the called
number analysis

SPECIDX

CAT

RST1

Special analysis
result index

Call service
types, including
the options in
Table 109

Number
analysis result
1

It is used to specify the index


number of the special analysis
result of the associated called
number. This parameter must
be defined by command ADD
SPECRST at first. Then it can
be indexed here. This parameter
is configured to implement the
routing service based on number
length. When the system performs
analysis on the called number,
it automatically matches the
actual length of the called number
to see whether the length is
within the range of Special
analysis result rule for called
numbers. If the length is within
the range, the system adopts the
routing information in Special
analysis result of called numbers.
Otherwise, the system adopts the
routing information in the called
number analysis
It is an optional parameter. It is
used to specify the service type
triggered by this number, and
determine the direction of this
call. The system adopts vacant
number by default.
The called number of the local
office is analyzed to MSCO (MSC
common service). The roaming
number of the local office is
analyzed to MSLL (MSC local
service). The roaming number of
other office is analyzed to MSLO
(MSC local outgoing service)
When the call service type is
vacant number, local-network
local-office/common service, MSC
local-network local-office service,
Mobile Number Portability (MNP),
or H323 call, number analysis
result 1 must be fixed to 0. When
the call service type is outgoing
call or toll call, number analysis
result 1 is used to specify the
index number of the outgoing
route chain.
When the call service type is
equal access: CIC of the
operator where the subscriber
is located or equal access:
non-local-network CIC, number
analysis result 1 is used to specify
the index number of the outgoing
route chain.

284

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Parameter
Name

Parameter
Description

Instruction
When the call service type is
OVERLAY prefix incoming
service, number analysis result
1 is used to specify the index
number of the outgoing route
chain. When the call service type
is OVERLAY: CAMEL service
triggered by MO, or OVERLAY:
CAMEL service triggered by MT,
number analysis result 1 is used
to specify the index number of the
outgoing route chain.
When the call service type is IP
service, IP mobile service, or
independent IP service number
analysis result 1 is used to specify
the index number of the outgoing
route chain.
When the call service type is
MNP outgoing routing number
analysis result 1 is used to specify
the index number of the outgoing
route chain.
When the call service type is
Outgoing paid special service
or Outgoing free special
service, number analysis result
1 is used to specify the index
number of the outgoing route
chain.
The above-specified index number
of the outgoing route chain must
be defined by command ADD
CHAIN at first. Then it can be
indexed here.
When the call service type is
Mobile emergency special
service, Local-office paid
special service or Local-office
free special service, number
analysis result 1 is used to specify
the special-service number. This
parameter must be defined by
command ADD SSPN at first.
Then it can be indexed here.
When the call service type is Tone
play service, CAT_SEND_TONE,
number analysis result 1 is used
to specify the ID of the tone to be
played

Confidential and Proprietary Information of ZTE CORPORATION

285

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

RST2

Parameter
Description

Number
analysis result
2

Instruction
It is used to specify the index
number of CAMEL access
subscription information of the
calling subscriber. This parameter
must be defined by command
ADD CAINFO at first. Then it
can be indexed here. When the
call service type is equal access:
CIC of the operator where the
subscriber is located or equal
access: non-local-network CIC,
this parameter must be configured.
When the call service type is
OVERLAY: CAMEL service
triggered by MO, or OVERLAY:
CAMEL service triggered by
MT, this parameter must be
configured. When the call service
type is other types except the
above-listed, number analysis
result 2 must be fixed to 0

RST3

CHAINAL

RNLEN

286

Number
analysis result
3

It is used to specify the index


number of CAMEL access
subscription information of the
called subscriber. This parameter
must be defined by command ADD
CAINFO at first. Then it can be
indexed here.
When the call service type is
OVERLAY: CAMEL service
triggered by MO, or OVERLAY:
CAMEL service triggered by
MT, this parameter must be
configured. When the call service
type is other types except the
above-listed, number analysis
result 3 must be fixed to 0

Route chanin
analysis index

It is used to specify the analysis


index number of the route chain.
This parameter must be defined
by command ADD CHAINAL at
first. Then it can be indexed. This
parameter takes effect only when
the call service type is outgoing
service (including various outgoing
services). It priority is higher than
that of the outgoing route chain
referred to in number analysis
result 1. Route chain analysis is
an intelligent routing policy better
than the policy of specifying a
single route chain

Length of the
carried routing
number

When the call service type is MNP


outgoing routing, it is configured
to the length of the carried routing
number. When the call service
type is other types except the
above-listed, it must be fixed to 0

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Parameter
Name

Parameter
Description

Instruction
It is an optional parameter, which
is an integer ranging from 0 to
255, with a default of 3. It is
used to specify the minimum digit
length of the analyzed number
required for call connection.

MINLEN

Minimum digit
length of
numbers

During an incoming call, if the


received digits are shorter than
this length, the system waits
for the subsequent digits. If the
system judges that there is no
subsequent digit, and the received
digits are shorter than this length,
the system considers that the
number format is wrong, and
releases the call.
During a local-office-originated
call, if the received digits are
shorter than this length, the
system considers that the number
format is wrong, and releases the
call.
For the OVERLAY prefix incoming
service, the system gets the length
of the OVERLAY prefix according
to the minimum digit length of
numbers. Therefore, it is required
to configure the minimum digit
length of numbers to the length of
the OVERLAY prefix. Otherwise,
procedures cannot be correctly
processed
It is an optional parameter, which
is an integer ranging from 0 to
255, with a default of 20. It is
used to specify the maximum digit
length of the analyzed number
required for call connection.

MAXLEN

Maximum
digit length of
numbers

During an incoming call, it is


the basis of whether to wait
for subsequent digits. If the
received digits reach this length,
the system does not wait for
subsequent digits.
During a local-office-originated
call, if the received digits are
longer than this length, the system
determines whether to continue or
release the call according to flag
No call when the called number
exceeds the length in the option
enabling configuration. If the
system determines to continue the
call, it cuts the exceeding digits

Confidential and Proprietary Information of ZTE CORPORATION

287

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction

OVERLAY
priority,
including:

OVLYPRI

NO (No
priority):
Trigger the
intelligent
service based
on CSI at
first, and
then trigger
the intelligent
service again
based on
OVERLAY
HCSI (Higher
than the CSI
in priority):
Trigger the
intelligent
service based
on OVERLAY
at first, and
then trigger
the intelligent
service again
based on CSI

It is used to the priority relationship


between triggering the intelligent
service based on CSI and triggering
the intelligent service based on
OVERLAY. The system adopts No
Priority by default. When the call
service type is OVERLAY(CAMEL
service triggered by MO), this
parameter is effective. Otherwise,
this parameter is ineffective

Voice channel
release mode,
including:
CING (calling
control
release):
The calling
party controls
whether to
release the
call. In this
mode, when
only the called
party hooks on,
the call still can
continue.
REL

CED(called
control
release):
The called
party controls
whether to
release the call.
In this mode,
when only the
calling party
hooks on, the
call still can
continue.

It is an optional parameter. It
indicates a resource release mode
when subscribers hook on. In
general, select NO. Select CED for
such special numbers as 110 and
119

NO (noncontrol
release): Both
the calling

288

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Parameter
Name

NET

Parameter
Description
party and the
called party
can control
whether to
release the call.
In this mode,
no matter
whether the
calling party or
the called party
hooks on, the
call is released

Type of the
destination
network

Instruction

It is an optional parameter, with


a default of 1. For calls to other
office in the local network, select
the signaling network where the
destination office is located. For
intra-office calls, this option is
meaningless.

Number
address
attribute,
including:
DEF (default
attribute): Do
not replace
the address
attribute of
the analyzed
number.

NAT

INT
(international
number):
Replace the
address
attribute of
the analyzed
number with
international
number.
NAT (national
number):
Replace the
address
attribute of
the analyzed
number with
national (valid)
number.

It is an optional parameter. It
is used to replace the address
attribute of the analyzed number.
In general, it is set to DEF, or is
set according to the requirements
of the peer end

LOC(local
number):
Replace the
address
attribute of
the analyzed
number with
local number.
UNK (attribute
unknown):
Replace the

Confidential and Proprietary Information of ZTE CORPORATION

289

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description
address
attribute of
the analyzed
number with
unknown

Instruction

Transforming
the calling
number again,
including:

OPDDICONT

NO (Not
allowed): It is
not allowed to
transform the
calling number
again in the
subsequent call
procedures.
YES (allowed):
It is allowed to
transform the
calling number
again in the
subsequent call
procedures.

It is an optional parameter. It
is used to specify whether it is
allowed to transform the calling
number again in the subsequent
call procedures when the calling
number was already transformed
once. The system adopts NO by
default

Transforming
the called
number again,
including:

TPDDICONT

NO (Not
allowed): It is
not allowed to
transform the
called number
again in the
subsequent call
procedures.
YES (allowed):
It is allowed to
transform the
called number
again in the
subsequent call
procedures

OPDDI

290

Calling-number
immediate
transform
index

It is an optional parameter. It
is used to specify whether it is
allowed to transform the called
number again in the subsequent
call procedures when the called
number was already transformed
once. The system adopts NO by
default

It is an optional parameter. It
is the number stream transform
index of the calling-number
immediate transform. Immediate
transform immediately makes the
calling number transformed. This
parameter must be defined by
command ADD DDI at first. Then
it can be indexed here

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Parameter
Name

TPDDI

OPDLYDDI

Parameter
Description

Instruction

Called-number
immediate
transform
index

It is an optional parameter. It
is the number stream transform
index of the called-number
immediate transform. Immediate
transform immediately makes the
called number transformed. This
parameter must be defined by
command ADD DDI at first. Then
it can be indexed here

Calling-number
delay transform
index

It is an optional parameter. It
is the number stream transform
index of the calling-number delay
transform. Delay transform takes
effects in the IAM message at the
outgoing side instead of making
the calling number transformed
immediately. This parameter must
be defined by command ADD DDI
at first. Then it can be indexed
here.
According to the IAM message at
the outgoing side, perform the
calling-number delay transform
here, and then perform the
calling-number delay transform in
the number pre-analysis

TPDLYDDI

DDIOVERB

Called-number
delay transform
index

It is an optional parameter. It
is the number stream transform
index of the called-number
immediate transform. Immediate
transform immediately makes the
called number transformed. This
parameter must be defined by
command ADD DDI at first. Then
it can be indexed here

B-interface
number
transform
index

It is the number stream transform


index of the called number in the
outgoing call request message
between the MSC and the VLR. The
transform purpose is to facilitate
the VLR judging the toll call
authority. This parameter must be
defined by command ADD DDI at
first. Then it can be indexed here

Whether to
support the
interworking
between video
calls, including:
IWVEDIO

LSUP:
Local-network
subscribers
support the
interworking
between
video calls by
default). The
call continues.

It is an optional parameter. It is
used to specify whether to support
the interworking between video
calls. The default value is LSUP

Confidential and Proprietary Information of ZTE CORPORATION

291

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction

OSUP:
Subscribers in
other networks
support the
interworking
between video
calls). The call
continues.
ONSUP:
Subscribers
in other
networks do
not support the
interworking

Maximum
call duration
(minute)

It is used to specify the maximum


call duration allowed for a call.
When the duration of a call reaches
the maximum call duration, the
system automatically release the
call. If it is unnecessary to restrict
the maximum call duration, adopt
the default value of 0

AUXDAS

Assistant DAS

It is an optional parameter. It
is used to specify the DAS for
analyzing the called number again
when the call service type is
outgoing service, and when the
connection between the local office
and the mutually-backed-up office
is broken in the mutual backup
dual-homing networking. This
parameter must be defined by
command ADD DAS at first. Then
it can be indexed here

A6

Sending A6
signal after
receiving
how many
digits during
incoming calls

It is used to specify the number


of digits that the system receives
enough to send A6 signal to the
front office. This parameter only
takes effect during incoming
calls using Channel Associated
Signaling (CAS)

PFXLEN

Toll prefix +
Area code
length

It is an optional parameter, which


is an integer, ranging from 0
to 15. When the call service
type is national/international toll
service, this parameter needs to
be configured

ENOPT

Enabled
options Refer
to Table 110 for
details

It is an optional parameter.
In general, select CCS7
(Automatically sending the
calling number when using CCS7
for outgoing services) and (No call
when the called number exceeds
the maximum digit length)

TIMELMT

292

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Parameter
Name

FAXIDX

AVIDX

DVIDX

Parameter
Description

Instruction

Fax analysis
resutl index

It is used to specify the bearer


analysis result index number of
the called number associated with
the fax service. This parameter
must be defined by command ADD
BEARRST at first. Then it can be
indexed here. This parameter
is configured to implement the
routing service based on the bearer
capability. For the fax service,
if the associated bearer analysis
result index of the called number
is configured, the call adopts the
associated bearer analysis result
of the called number, thus flexible
routing is implemented

Analog video
analysis result
index

It is used to specify the bearer


analysis result index number of
the called number associated
with the analog video service.
This parameter must be defined
by command ADD BEARRST at
first. Then it can be indexed here.
This parameter is configured to
implement the routing service
based on the bearer capability.
For the analog video service, if
the associated bearer analysis
result index of the called number
is configured, the call adopts the
associated bearer analysis result
of the called number, thus flexible
routing is implemented

Digital video
analysis result
index

It is used to specify the bearer


analysis result index number of
the called number associated
with the digital video service.
This parameter must be defined
by command ADD BEARRST at
first. Then it can be indexed here.
This parameter is configured to
implement the routing service
based on the bearer capability.
For the digital video service, if
the associated bearer analysis
result index of the called number
is configured, the call adopts the
associated bearer analysis result
of the called number, thus flexible
routing is implemented

Confidential and Proprietary Information of ZTE CORPORATION

293

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

ADATAIDX

DDATAIDX

Parameter
Description

Instruction

Analog data
analysis result
index

It is used to specify the bearer


analysis result index number of
the called number associated with
the analog data service. This
parameter must be defined by
command ADD BEARRST at first.
Then it can be indexed here.
This parameter is configured to
implement the routing service
based on the bearer capability.
For the analog data service, if
the associated bearer analysis
result index of the called number
is configured, the call adopts the
associated bearer analysis result
of the called number, thus flexible
routing is implemented

Digital data
analysis result
index

It is used to specify the bearer


analysis result index number of
the called number associated
with the digital data service. This
parameter must be defined by
command ADD BEARRST at first.
Then it can be indexed here.
This parameter is configured to
implement the routing service
based on the bearer capability.
For the digital data service, if the
associated bearer analysis result
index of the called number is
configured, the call adopts the
associated bearer analysis result
of the called number, thus flexible
routing is implemented

Whether to play
the DDC tone,
including:

DDCPLAY

NONE (Not
playing the
DDC tone): It
is not required
to play the DDC
tone in the local
office.
PLAY (Playing
the DDC tone):
It is required
to play the DDC
tone in the local
office.

294

It is used to specify whether


to play the DDC tone in the
local office. The system adopts
NONE by default. The purpose
of configuring whether to play
the DDC tone in the number
analysis configuration is to avoid
no tone play or repeated tone play
caused by inconsistent tone play
configuration during inter-office
DDC calls

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Parameter
Name

Parameter
Description

Instruction

Voice Activity
Detection
(VAD) flag,
including:
CLOSE: Not
starting the
VAD function.
OPEN: Starting
the VAD
function.
INVALID: The
VAD function is
invalid

VAD

OPPMGWID

Opposite-end
MGW ID

It is used to specify whether to


start the VAD function. The system
adopts INVALID by default

It is used to specify between which


opposite-end MGW and the local
MGW the TDM backup route is
adopted. The QOSs between the
local MGW and all opposite-end
MGWs can be found through
automatic test calls. When the
QOS difference between the
opposite-end MGW and the local
MGW is specified, the call adopts
the TDM backup route

Call type
priority,
including:
INVALID: The
call priority is
invalid.
HIGHEST: The
call has the
highest priority.

CALLSERVPRILVL

HIGHER: The
call has a
priority one
level lower than
the highest
priority.
NORMAL:
The call has
a priority one
level lower
than the higher
priority.

It is used to specify the call


priority. The system adopts
INVALID by default. The call
priority has two functions. In
one case, in the softswitch office
in the toll softswitch network,
the voice coding format can be
dynamically selected according to
the call priority and the load on
the IP bearer network. In another
case, based on the combined
information of office ID and
priority configured in the number
analysis configuration, the final
priority of a call is got to perform
load control

LOW: The call


has the lowest
priority

Confidential and Proprietary Information of ZTE CORPORATION

295

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

RERTS

Parameter
Description

Re-routing
route chain

Instruction
It is used to specify the re-routing
route chain ID. This parameter
must be defined by command
ADD RERTS at first. Then it
can be indexed here. When flag
RRTO in enabled options takes
effect, the re-routing route chain
takes effect too. For an outgoing
call procedure, if the call fails,
and the corresponding failure
cause is configured with Enabling
rerouting for failure in the R_ICP
configuration, re-select the route
from this route chain according
to the re-routing route chain.
For an incoming call using ISUP,
TUP, or BICC signaling, when
the call procedure is an outgoing
procedure, and the call fails before
the IAM message is sent, the
re-routing route chain serves as
the standby route, and is not
controlled by RRTO.
If route chain analysis is
configured, the re-routing
route chain here is invalid. In this
case, use the re-routing route
chain configured in the route chain
analysis

Inter-MGW
route chain or
not, including:

INCHAIN

NO: The
outgoing route
chain got
from number
analysis is not
an inter-MGW
route chain.
YES: The
outgoing route
chain got
from number
analysis is
an inter-MGW
route chain

It is used to specify whether the


outgoing route chain got from
number analysis is an inter-MGW
route chain. The system select
NO by default. If YES is selected,
the routes in the outgoing route
chains will not be selected for
the outgoing route. The outgoing
route will be got after perform
number analysis again according
to the associated called number
DAS configured in the outgoing
route chain.
This parameter is used in the
following cases:
One virtual outgoing route chain
is got based on number analysis
at first, and then the real outgoing
route is got based on the called
number DAS associated with the
virtual outgoing route chain.
When one MSCS controls multiple
areas, the outgoing route chain
facilitates subscriber management

RECMDMGWNODEID

296

Recommended
MGW nodes

It is used to specify the set of


recommended MGWs for outgoing
service. In the case of multiple IP
domains, if one MSCS manages
multiple MGWs, and these MGWs
belong to different IP domains,

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Parameter
Name

Parameter
Description

Instruction
the set of recommended MGWs
for outgoing service needs to be
configured. The MGW set here
should be a sub-set of the MGW
set supported by outgoing service.
This parameter must be defined
by command ADD TOPO at first.
Then it can be indexed here

TABLE 109 CALL SERVICE TYPES


Call
Service
Types

Meanings

Description

NONE

Vacant number

Indicates that the subsequent call


procedures are processed based
on the procedure of processing
vacant numbers

LLC

Localnetwork localoffice/common
service

Indicates that the subsequent call


procedures are processed based
on the local service procedure

Local-network
outgoing/localcall service

Indicates that the subsequent


call procedures are processed
based on the local-call service
procedure. The mobile-to-fixed
local outgoing call service is
usually analyzed to this type

Local-network
outgoing/rural
(network) call
service

Indicates that the subsequent


call procedures are processed
based on the local rural (network)
outgoing call service procedure.
The mobile-to-fixed rural outgoing
call service is usually analyzed to
this type

DWTM

Domestic toll
(intra-region)
manual service

Indicates that the subsequent call


procedures are processed based
on the domestic toll (intra-region)
manual service procedure. In
general, it is not recommended to
configure this service type

DWTA

Domestic toll
(intra-region)
automatic
service

Indicates that the subsequent call


procedures are processed based
on the domestic toll (intra-region)
automatic service procedure. In
general, it is not recommended to
configure this service type

Domestic toll
(inter-region)
manual service

Indicates that the subsequent call


procedures are processed based
on the domestic toll (inter-region)
manual service procedure. In
general, it is not recommended to
configure this service type

LOL

LORU

DBTM

Confidential and Proprietary Information of ZTE CORPORATION

297

ZXWN MSCS Data Configuration Guide(MSCS)

Call
Service
Types

Meanings

Description

DBTA

Domestic toll
(inter-region)
automatic
service

Indicates that the subsequent call


procedures are processed based
on the domestic toll (inter-region)
automatic service procedure. The
domestic toll call service is usually
analyzed to this type

INTM

International
toll manual
service

Indicates that the subsequent call


procedures are processed based
on the international toll manual
service procedure. In general, it
is not recommended to configure
this service type

International
toll automatic
service

Indicates that the subsequent


call procedures are processed
based on the international toll
automatic service procedure. The
international toll call service is
usually analyzed to this type

Local-office paid
special service

Indicates that the subsequent


call procedures are processed
based on the local-office paid
special service procedure. The
local-office paid special service is
usually analyzed to this type

Local-office free
special service

Indicates that the subsequent


call procedures are processed
based on the local-office free
special service procedure. The
local-office free special service is
usually analyzed to this type

Outgoing paid
special service

Indicates that the subsequent call


procedures are processed based
on the outgoing paid special
service procedure. The outgoing
paid special service is usually
analyzed to this type

Outgoing free
special service

Indicates that the subsequent


call procedures are processed
based on the outgoing free special
service procedure. The outgoing
free special service is usually
analyzed to this type

DEPS

Additional
service

Indicates that the subsequent


call procedures are processed
based on the additional service
procedure. In general, it is not
recommended to configure this
service type

CENTL

Intra-office
call within
the CENTREX
business group

Indicates that the subsequent call


procedures are processed based
on the intra-office call procedure
within the CENTREX business
group.

INTA

LSPA

LSFR

OUPA

OUFR

298

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Call
Service
Types

Meanings

Description

CENTO

Outgoing call
within the
CENTREX
business group

Indicates that the subsequent call


procedures are processed based
on the outgoing call procedure
within the CENTREX business
group

TELCA

Intelligent
Ntwork service
call

Indicates that the subsequent call


procedures are processed based
on the intelligent network service
call procedure

EQACL

Equal access:
CIC of the
operator where
the subscriber is
located

Indicates that the subsequent


call procedures are processed
based on the procedure of Equal
access: CIC of the operator where
the subscriber is located

EQACO

Equal access:
non-localnetwork CIC

Indicates that the subsequent


call procedures are processed
based on the procedure of Equal
access: non-local-network CIC

Tone play service, CAT_SEND_TONE

Indicates that the subsequent


call procedures are processed
based on the tone play service
procedure. After calling the
number that is analyzed to this
type, the system will directly play
the tone according to the tone
ID configured in number analysis
result 1

Toll DDC
incoming call

Indicates that the subsequent


call procedures are processed
based on the toll DDC incoming
call service procedure. The toll
incoming DDC call that needs to
be routed in the local office is
analyzed to this type

Local DDC call

Indicates that the subsequent call


procedures are processed based
on the local DDC call service
procedure. The local DDC call
(dialing the MSISDN number) that
needs to be routed in the local
office is analyzed to this type

Toll DDC
outgoing call

Indicates that the subsequent


call procedures are processed
based on the toll DDC outgoing
call service procedure. The toll
outgoing DDC call is analyzed to
this type

Local DDC
outgoing call

Indicates that the subsequent


call procedures are processed
based on the local DDC outgoing
call service procedure. The local
outgoing DDC call is analyzed to
this type

STONE

DDCI

DDCC

DDCO

DDCCO

Confidential and Proprietary Information of ZTE CORPORATION

299

ZXWN MSCS Data Configuration Guide(MSCS)

Call
Service
Types

Meanings

Description

MSCO

MSC common
service

Indicates that the subsequent call


procedures are processed based
on the MSC common service
procedure. The call (dialing the
MSISDN number) that needs to
be routed in the local office is
analyzed to this type

MSLL

MSC localnetwork
local-office
service (only
for roaming
numbers)

Indicates that the subsequent


call procedures are processed
based on the MSC local-network
local-office service procedure. It
is used to analyze the roaming
numbers and handover numbers
of the local office

MSLO

MSC local
outgoing
service (only
for roaming
numbers)

Indicates that the subsequent call


procedures are processed based
on the local outgoing service
procedure. The local outgoing call
of roaming numbers is analyzed
to this type

CINRE

Calling-number
incoming call
restriction

Indicates that the subsequent call


procedures are processed based
on the calling-number incoming
call restriction procedure

MSLTE

MSC national
toll call (only
for roaming
numbers)

Indicates that the subsequent


call procedures are processed
based on the MSC national toll
call service procedure. The toll
outgoing call of roaming numbers
is analyzed to this type

AAC

Automatic
response
number

Indicates that the subsequent


call procedures are processed
based on the automatic response
number service procedure

OVERLAY
prefix incoming
service

Indicates that the subsequent call


procedures are processed based
on the OVERLAY prefix incoming
service procedure. The OVERLAY
prefix incoming call is analyzed to
this type

OVCS

OVERLAY call
service

Indicates that the subsequent call


procedures are processed based
on the OVERLAY call service
procedure. It is used for the IGW
system

MSITE

MSC
international
toll call (only
for roaming
numbers)

Indicates that the subsequent


call procedures are processed
based on the MSC international
toll call service procedure. The
international toll outgoing call is
analyzed to this type

OVPRE

300

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Call
Service
Types

Meanings

Description

IP

IP fixed service

Indicates that the subsequent call


procedures are processed based
on the IP fixed service procedure.
It is used for the IGW system

SSP

SSP charging
and querying
service

Indicates that the subsequent call


procedures are processed based
on the SSP charging and querying
service procedure.

NSSP

Non-SSP
charging and
querying service

Reserved

IPMO

IP mobile
service

Indicates that the subsequent


call procedures are processed
based on the IP mobile service
procedure. The IP service in the
mobile system is analyzed to this
type

INSIP

IP service dialed
by intelligentnetwork
subscribers

Reserved

ALIP

Independent IP
service

Indicates that the subsequent call


procedures are processed based
on the independent IP service
procedure. The independent IP
incoming call is analyzed to this
type

OVMO

OVERLAY:
MO-triggered
CAMEL service

Indicates that the subsequent call


procedures are processed based
on the OVERLAY: MO-triggered
CAMEL service procedure

OVMT

OVERLAY:
MT-triggered
CAMEL service

Indicates that the subsequent call


procedures are processed based
on the OVERLAY: MT-triggered
CAMEL service procedure

MNP

Mobile number
portability

Indicates that the subsequent call


procedures are processed based
on the MNP service procedure

MNPR

MNP MNP
outgoing routing

Indicates that the subsequent call


procedures are processed based
on the MNP outgoing routing
service procedure

SIPO

SIP outgoing
call

Indicates that the subsequent call


procedures are processed based
on the SIP outgoing call service
procedure

Confidential and Proprietary Information of ZTE CORPORATION

301

ZXWN MSCS Data Configuration Guide(MSCS)

Call
Service
Types

Meanings

Description

H323

H323 call

Indicates that the subsequent


call procedures are processed
based on the H323 call service
procedure.

MOIMC

Mobile
emergency
special service

Indicates that the subsequent call


procedures are processed based
on the mobile emergency special
service procedure

SSSP

Independent
SSP outgoing
service

Indicates that the subsequent


call procedures are processed
based on the independent SSP
outgoing service procedure. The
SSSP (Independent SSP outgoing
service) in the analysis result of
the called number is used for the
IGW system

IGWA

IGW
supplementary
service (only for
IGW)

Indicates that the subsequent


call procedures are processed
based on the IGW supplementary
service procedure

DASA

DAS service
(virtual IGW)
(only for IGW)

A new DAS is got through number


analysis, which is used for the
subsequent analysis of the called
number

OCIC

Local valid CIC


service

Indicates that the subsequent call


procedures are processed based
on the local valid CIC service
procedure. This parameter is
reserved

OUPAOD

Outgoing
paid special
service (can
be dialed by
the defaulting
subscribers)

Indicates that the subsequent call


procedures are processed based
on the outgoing paid special
service (can be dialed by the
defaulting subscribers) procedure

LINTS

Local-office
intelligent
service

Indicates that the subsequent call


procedures are processed based
on the local-office intelligent
service procedure. It is used for
the IGW system

SHLRQ

SHLR querying
service (only for
IGW)

Indicates that the subsequent call


procedures are processed based
on the SHLR querying service
procedure

IGW common
service (only for
IGW)

Indicates that the subsequent


call procedures are processed
based on the IGW common
service procedure. The call to
PHS subscribers, which needs to
be routed in the local office, is
analyzed to this type

IGWC

302

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Call
Service
Types

Meanings

Description

ISSPQ

IGWSSP
charging and
querying service
(only for IGW)

Indicates that the subsequent call


procedures are processed based
on the IGW SSP charging and
querying service procedure

IGWLF

IGW local-office
free special
service

Indicates that the subsequent


call procedures are processed
based on the IGW local-office free
special service procedure

IGWLP

IGW local-office
paid special
service

Indicates that the subsequent


call procedures are processed
based on the IGW local-office paid
special service procedure

IGWOV

IGWOVERLAY
prefix incoming
service

Indicates that the subsequent


call procedures are processed
based on the IGWOVERLAY prefix
incoming service procedure

IGWDDCIN

IGW toll DDC


incoming call

Indicates that the subsequent call


procedures are processed based
on the IGW toll DDC incoming call
service procedure

IGWDDCLOCAL

IGW local DDC


call

Indicates that the subsequent call


procedures are processed based
on the IGW local DDC call service
procedure

TEST

Test call

Indicates that the subsequent call


procedures are processed based
on the test call service procedure.
It is used to analyze test calls

TABLE 110 ENABLED OPTIONS


Enabled
Options

CCS7

Meanings

Description

Automatically sending
the calling number when
using CCS7 for outgoing
services

It indicates whether the


outgoing TUP signaling
carries the calling
number. When the local
office actively sends the
calling number, it sends
an IAI message of TUP
signaling to the peer-end
office, carrying the calling
number. Otherwise, the
local office sends an
IAM message of TUP
signaling to the peer-end
office, not carrying
the calling number.
For ISUP signaling, it
indicates whether the
local MSC number is filled

Confidential and Proprietary Information of ZTE CORPORATION

303

ZXWN MSCS Data Configuration Guide(MSCS)

Enabled
Options

Meanings

Description
in the location number
information

Changing the type of


calling subscribers

Indicates whether to
set the type of the
calling subscriber in the
outgoing IAM message of
ISUP or BICC signaling
to the calling subscriber
types flexibly configured
in security variables

CHGN

Changing the number

Indicates that the


analyzed number is
changed, and the system
notifies the calling
subscriber by playing
the tone

DELA

Delayed dialing of the


special service

Reserved

MAIL

166-voice-mailbox
service

Indicates that the call


is a 166-voice-mailbox
service

NSCP

Not waiting for SCP


responses

Reserved

RRTO

Rerouting after outgoing


failure

For incoming calls


using ISUP, TUP, or
BICC signaling, the
call procedure is an
outgoing call procedure.
When the local office
does not receives a REL
message after sending an
outgoing IAM message to
the peer-end office, this
option control whether
rerouting is allowed

NETF

IN forward message

Reserved

VNUM

Virtual number

Reserved

HRA

High rate

Reserved

NUMLEN

Estimate Number Length

Estimate Number Length

CEC

Charge as emergency
call

Charge as emergency
call

NOLMTLEN

No Limited Time Length


For Tone

No Limited Time Length


For Tone

IGFWD

Ignore Redirection Info


In Outgoing Call

Ignore Redirection Info


In Outgoing Call

ECL

Use Emergency Call Level

Use Emergency Call Level

CHGK

304

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Enabled
Options

Meanings

Description

NTC

Not triggering IN service


of the calling number

Indicates whether the


call triggers the IN
service of the calling
number. This option is
used for the case where
the IN service of the
calling number cannot
be triggered when the
call to the IN subscriber
is forwarded or when
some special numbers
are dialed

NCEL

No call when the called


number exceeds the
length

Indicates whether the


system releases the call
if the analyzed number
exceeds the configured
maximum digit length

Interception number
incoming

Indicates whether the


call is an incoming
call returned from the
interception center. This
option is only used in the
IGW system

Sending the connect


message in advance
(only for IGW)

Indicates whether the


local office sends a
ringing message of the
called subscriber and a
connect message to
the calling subscriber
at the same time (that
is, sends a connect
message to the calling
subscriber before the
called subscriber answers
the call). This option is
only used in the IGW
system

Not triggering SHLR


query

Indicates whether the


number section needs
to be transformed in
the SHLR during call
origination. In the
SHLR mixed networking,
common call origination
procedures need to
interact with the SHLR
to get the calling
logic number, and the
called physical number.
However, in the specific
calls, the called number
needs no transform. In
this case, select this
option in the number
analysis result. This
option is only used in the
IGW system

LSIN

CON

SHLRF

Confidential and Proprietary Information of ZTE CORPORATION

305

ZXWN MSCS Data Configuration Guide(MSCS)

Enabled
Options

SHLRG

JUDG

REBO

Meanings

Description

Over net number in SHLR

Indicates whether the


incoming call restrain
the SHLR from returning
the IN access code. This
option is used to prevent
repeatedly triggering IN
services. This option is
only used in the IGW
system

Needing to judge the IP


resource

Indicates whether the


routing query in the SHLR
is forcibly performed
during IP calls. This
option is only used in the
IGW system

Restraining HOMEBOX
service

Indicates whether
incoming calls trigger
the HOMEBOX service
in the local office. This
option is only used in the
IGW system

Example: Configure the called number analysis with the following requirements.

Analyzer entry: 1

User alias: TPDNAL1

Analyzed number: 13902099

Call service type: MSC common service

Other parameters: Adopt the default values.

The command is:


ADD TPDNAL:ENTR=1,DIGIT="13902099",NAME="TPDN
AL1",SPECRST=0,SPECIDX=0,CAT=MSCO,RST1=0,RST2
=0,RST3=0,CHAINAL=0,RNLEN=0,MINLEN=3,MAXLEN
=20,OVLYPRI=HCSI,REL=NO,NET=1,NAT=DEF,OPDDIC
ONT=NO,TPDDICONT=NO,OPDDI=0,TPDDI=0,OPDLYD
DI=0,TPDLYDDI=0,DDIOVERB=0,IWVIDEO=LSUP,TIME
LMT=0,AUXDAS=0,A6=0,PFXLEN=0,INSRV=INM,FAXID
X=0,AVIDX=0,DVIDX=0,ADATAIDX=0,DDATAIDX=0,D
DCPLAY=NONE,VAD=INVALID,CALLSERVPRILVL=INVALI
D,RERTS=0,INCHAIN=NO,BICT=NO,ICT=0,ICTT=10,GN
M=NORMAL,STBILL=INVALID,HOPDAS=0,MCA=NO,IVVR
=NO,WANTL=0,IMSCENTR=NO;
Example: Configure the roaming number analysis of the local
office with the following requirements.

306

Analyzer entry: 1

User alias: TPDNAL1

Analyzed number: 15902099

Call service type: MSC local service

Other parameters: Adopt the default values.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

The command is:


ADD TPDNAL:ENTR=1,DIGIT="15902099",NAME="TPDN
AL2",SPECRST=0,SPECIDX=0,CAT=MSLL,RST1=0,RST2
=0,RST3=0,CHAINAL=0,RNLEN=0,MINLEN=3,MAXLEN
=20,OVLYPRI=HCSI,REL=NO,NET=1,NAT=DEF,OPDDIC
ONT=NO,TPDDICONT=NO,OPDDI=0,TPDDI=0,OPDLYD
DI=0,TPDLYDDI=0,DDIOVERB=0,IWVIDEO=LSUP,TIME
LMT=0,AUXDAS=0,A6=0,PFXLEN=0,INSRV=INM,FAXID
X=0,AVIDX=0,DVIDX=0,ADATAIDX=0,DDATAIDX=0,D
DCPLAY=NONE,VAD=INVALID,CALLSERVPRILVL=INVALI
D,RERTS=0,INCHAIN=NO,BICT=NO,ICT=0,ICTT=10,GN
M=NORMAL,STBILL=INVALID,HOPDAS=0,MCA=NO,IVVR
=NO,WANTL=0,IMSCENTR=NO;
END OF STEPS

Trunk Data Configuration


Overview
The related operations of the trunk data configuration are as follows.
Steps

Operations

Instructions

Command

Creating a DT
trunk group

When the A
interface and Ai
interface adopts
the TDM bearer,
or when MGWs
are interconnected
through the TDM
bearer, configure
DT trunk groups

ADD TG DT

Creating an ATM
trunk group

When the ATM


bearer is adopted
between MGWs,
configure ATM trunk
groups

ADD TG ATM

Creating a RTP
trunk group

When the IP bearer


is adopted between
MGWs, configure
BICC trunk groups.
When the MSCS
servers as a MGCF,
configure SIP trunk
groups for MGWs

ADD TG RTP

Confidential and Proprietary Information of ZTE CORPORATION

307

ZXWN MSCS Data Configuration Guide(MSCS)

Steps

Operations

Instructions

Command

Creating a PCM
system

DT, ATM, and


RTP trunk groups
all need to be
configured with
PCM systems

ADD SPCM

Creating a PCM
system between
MGWs

When the MGWs


managed by
one MSCS are
interconnected
through TDM
circuits, no trunk
group or trunk
route needs to
be configured,
and only PCM
systems between
the MGWs need to
be configured

ADD INPCM

Creating a DT Trunk Group


Prerequisites

Before the operation, it is required to confirm:

The exchange ID to be configured is given.

The adjacent office to which the trunk group points is created.

The trunk group No. range is set in the resource management


system.

The MML Terminal window is opened.

Context

When the A interface or Ai interface adopts the TDM bearer, or


when MGWs are interconnected through the TDM bearer, DT trunk
groups need to be configured. The circuit status in each trunk
group is managed by the corresponding trunk management module, so it is required to configure multiple trunk groups to each
BSC office (4~8 trunk groups are recommended). To implement
load sharing, it is required to allocate roughly the same number of
BSC circuits to each CMP module.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create a DT trunk group by executing command ADD TG DT.
The explanation of the main parameters in command ADD TG
DT is shown in Table 111.

308

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

TABLE 111 PARAMETERS IN THE ADD TG DT COMMAND


Parameter
Name

Parameter Description

Instruction

Trunk group ID

It is a mandatory
parameter. It is used
to define a trunk
group, and needs to be
planned in the resource
management system in
advance

ID of the office where


the trunk group belongs

It is a mandatory
parameter. It is
used to specify the
corresponding office of
the trunk group. This
parameter must be
defined by command
ADD ADJOFC at first.
Then it can be indexed
here

MODULE

Module where the trunk


group belongs

It is a mandatory
parameter. It indicates
a service module.
Different trunk groups
to the same office
need to be allocated to
different CMP modules

ND

Node No. of the MGW


where the trunk group
belongs

It is a mandatory
parameter. Select the
MGW topology node
connected with the 2G
MSC/PSTN node

User alias

It is an optional
parameter, consisting
of 0~50 characters. It
is used to specifically
describe a trunk group
to make it easily
recognized

TG

OFC

NAME

Inter-office line signal


identification. Options
include:

SIGLINE

BSC: BSC Ground


Circuit

TUP: Interoffice
Common Channel
Signaling TUP

ISUP: Interoffice
Common Channel
Signaling ISUP

DLC1: Interoffice
Channel Associated
Signaling DL/DC(1)

R2: R2 Signaling

BICC: BICC Type

It is an optional
parameter. It is used
to identify the line type
of this trunk. Select it
according to inter-office
signaling. For the Ai
interface, select ISUP]
or TUP

Confidential and Proprietary Information of ZTE CORPORATION

309

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter Description

ANU: ANU Signaling

SORMUP: SORMUP
Signaling

Instruction

Trunk group types,


including the following
three types:
IN (incoming trunk
group): Indicates
that the local office
processes the incoming
calls from the peer-end
office.

KIND

OUT (outgoing trunk


group): Indicates that
the local office only
processes the outgoing
calls to the peer-end
office.

It is an optional
parameter. If BSC
is selected for the
inter-office line signal
identification, it must be
configured to BIDIR

BIDIR (Two-way trunk


group): Indicates
that the local office
processes both the
incoming calls from the
peer-end office and the
outgoing calls to the
peer-end office
Bearer establishment
direction, including the
following three types:
NODIR: The inter-office
bearer is established
without direction.
BWAY

BACK: The inter-office


bearer is established
based on the backward
mode.

It is an optional
parameter. Select
NODIR for DT trunk
groups

FORWD: The
inter-office bearer is
established based on
the forward mode

THD

310

Overload control
threshold

Confidential and Proprietary Information of ZTE CORPORATION

It is an optional
parameter, ranging from
0 to 100, with a default
of 100. This parameter
takes effect when levels
of congestion occur and
load control is required

Chapter 8 Basic Service Data Configuration

Parameter
Name

Parameter Description

Instruction

Circuit selecting modes,


including:
MIN: Every time when
the system selects a
trunk circuit, it always
begins with the circuit
with the minimum
number. This mode can
implement the preferred
plan of trunk circuits.
MAX: Every time when
the system selects a
trunk circuit, it always
begins with the circuit
with the maximum
number. This mode can
implement the preferred
plan of trunk circuits.

CICSEL

CYC: Every time when


the system selects
a trunk circuit, it
always begins with
the circuit next to the
one previously selected.
Suppose the numbers
of the trunk circuits in a
trunk group in ascending
order are TKC0, TKC1,
. , TKCn. If TKC0
is selected at the first
time, the system will
select the trunk circuit
in the order of TKC0T
KC1TKCnTKC0
TKC1TKCn.

It is an optional
parameter. It is used to
specify the trunk circuit
selecting policy of the
system within this trunk
group, with a default of
CYC. If this No.7 trunk
group is a two-way
trunk group, it is
recommended to set the
circuit selecting mode
to ODD/EVEN mode
to prevent contention
when two exchanges
select circuits

ODD: Every time when


the system selects a
trunk circuit, it always
selects the circuit with
an odd number.
EVEN: Every time when
the system selects a
trunk circuit, it always
selects the circuit with
an even number.
IDLE: Every time when
the system selects a
trunk circuit, it always
selects the idlest circuit.
BUSY: Every time when
the system selects a
trunk circuit, it always
selects the busiest
circuit

Confidential and Proprietary Information of ZTE CORPORATION

311

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

DAS

SIPDAS

OPDAS

PREDAS

DDI

OPDDI

MINNAT

312

Parameter Description

Instruction

DAS for the called


number

It is an optional
parameter. It is used
to analyze the called
number in an incoming
call. This parameter
must be defined by
command ADD DAS at
first. Then it can be
indexed here

DAS for the domain


name of the called
number during a SIP
outgoing call

It is used get the name


of the IMS domain
where the called party
is located through
analyzing the called
number during a SIP
outgoing call. It is
only used for RTP trunk
groups

DAS for the calling


number

It is used to analyze
the calling number in
an incoming call. This
parameter must be
defined by command
ADD DAS at first. Then
it can be indexed here

DAS for pre-analyzing


the called number

It is used to pre-analyze
the called number in
an incoming call. This
parameter must be
defined by command
ADD PREDAS at first.
Then it can be indexed
here

Incoming called number


transform ID

It is the index of
the incoming called
number transform. This
parameter must be
defined by command
ADD DDI at first. Then
it can be indexed here

Incoming calling
number transform ID

It is the index of
the incoming calling
number transform. This
parameter must be
defined by command
ADD DDI at first. Then
it can be indexed here

Minimum national
number length

It is an optional
parameter, which is
an integer ranging from
0 to 26, with a default
of 0. It is used to
specify the minimum
digit length of the
called number during a
national incoming call

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Parameter
Name

Parameter Description

Instruction

Maximum national
number length

It is an optional
parameter, which is
an integer ranging from
0 to 26, with a default
of 26. It is used to
specify the maximum
digit length of the
called number during a
national incoming call

Minimum international
number length

It is an optional
parameter, which is
an integer ranging from
0 to 26, with a default
of 0. It is used to
specify the minimum
digit length of the
called number during an
international incoming
call

MAXINT

Maximum international
number length

It is an optional
parameter, which is
an integer ranging from
0 to 26, with a default
of 26. It is used to
specify the maximum
digit length of the
called number during an
international incoming
call

INREG

Incoming register
signaling flag, including
options: INVALID,
MFC, MFP, DTMF, DP
and MF

It is an optional
parameter, with a
default of INVALID

OUTREG

Outgoing register
signaling flag, including
options: INVALID,
MFC, MFP, DTMF, DP
and MF

It is an optional
parameter, with a
default of INVALID

COLEN

The maximum length of


CAS calling number end

It is an optional
parameter. It ranges
from 1 to 32, with a
default of 10.

MAXNAT

MININT

Confidential and Proprietary Information of ZTE CORPORATION

313

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter Description

Instruction

Trunk circuit usage

It is an optional
parameter, which is
an integer ranging
from 1 to 100, with a
default of 100. After
the trunk circuit usage
is configured, when the
ratio of busy circuits to
all circuits in this trunk
group exceeds this
value, congestion occurs
in this trunk group.
After the congestion
is relieved, report the
trunk congestion times
and congestion duration
in the performance
statistics. This
parameter does not
take effect when it is
configured to 100

ROAMDAS

DAS for roaming


numbers

It is an optional
parameter. After this
DAS is configured, if
the local office serves
as a GMSC, this DAS
is preferred for the
returned roaming
numbers. Otherwise,
the roaming number
DAS configured in
the number analysis
template is used

Q850CCIDX

Q850 customization
index

It is an optional
parameter. It ranges
from 0 to 65535, with a
default of 0.

ID of signaling
modification entrance

It is an optional
parameter, associated
with the inter-office
signaling modification
entrance. It ranges
from 0 to 65535, with a
default of 0

BUSYRATE

SMENTERID

Example: Create a DT trunk group to the BSC office with the


following requirements:

Trunk group ID: 99

ID of the office where the trunk group belongs: 99

User alias: BSC99

No. of the CMP module where the trunk group belongs: 3

MGW topology node No.: 101

Other parameters: Adopt the default values.

The command is:

314

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

ADD TG DT:TG=99,OFC=99,MODULE=4,ND=101,NAME
="BSC99",SIGLINE=BSC,KIND=BIDIR,BWAY=NODIR,THD
=100,CICSEL=ODD,DAS=0,SIPDAS=0,OPDAS=0,PREDA
S=0,DDI=0,OPDDI=0,MINNAT=0,MAXNAT=26,MININT
=0,MAXINT=26,INREG=INVALID,OUTREG=INVALID,COLE
N=10,BUSYRATE=100,ROAMDAS=0,Q850CCIDX=0,SME
NTERID=0,MLPPDM=4294967295,DISINDEX=0;
END OF STEPS

Creating an ATM Trunk Group


Prerequisites

Before the operation, it is required to confirm:

The exchange ID to be configured is given.

The trunk group No. range is set in the resource management


system.

The adjacent MGW office to which the trunk group points is


created.

The MML Terminal window is opened.

Context

When the ATM bearer is adopted between MGWs, configure ATM


trunk groups.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create an ATM trunk group by executing command ADD TG
ATM.
The explanation of the main parameters in command ADD TG
ATM is shown in Table 112.
TABLE 112 PARAMETERS IN THE ADD TG ATM COMMAND
Parameter
Name

TG

OFC

Parameter Description

Instruction

Trunk group ID

It is a mandatory
parameter. It is used
to define an ATM trunk
group, and needs to be
planned in the resource
management system in
advance. It is a global
unified number

ID of the office where


the trunk group belongs

It is a mandatory
parameter, ranging
from 1 to 256. It is
used to specify the
corresponding office of
the trunk group. This
parameter must be

Confidential and Proprietary Information of ZTE CORPORATION

315

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter Description

Instruction
defined by command
ADD ADJOFC at first.
Then it can be indexed
here

NAME

User alias

It is an optional
parameter, consisting
of 0~50 characters.
It is used to specifically
describe a trunk group to
make it easily recognized

Module where the trunk


group belongs

It is a mandatory
parameter, which is
an integer, ranging from
1 to 127. It is used to
specify the SMP module
of processing traffic on
this trunk group

ND

Node No. of the MGW


where the trunk group
belongs

It is a mandatory
parameter, which is
an integer, ranging from
1~2048. It is used to
specify the topology
node No. of the MGW
providing bearer, which
is controlled by the local
MGCF

SIGLINE

Inter-office line signal


identification, including
BICC (BICC signaling)

It is an optional
parameter. It is used to
identify the line type of
this trunk, with a default
of BICC

MODULE

Trunk group types,


including the following
three types:
IN (incoming trunk
group): Indicates that
the local office processes
the incoming calls from
the peer-end office.

KIND

OUT (outgoing trunk


group): Indicates that
the local office only
processes the outgoing
calls to the peer-end
office.
BIDIR (Two-way trunk
group): Indicates that
the local office processes
both the incoming calls
from the peer-end office
and the outgoing calls to
the peer-end office

316

Confidential and Proprietary Information of ZTE CORPORATION

It is an optional
parameter. It is used
to specify the call
connection direction
in this trunk group in
the local office, with
a default of BIDIR. It
should be negotiated
with the peer-end office

Chapter 8 Basic Service Data Configuration

Parameter
Name

Parameter Description

Instruction

Bearer establishment
direction, including the
following three types:
NODIR (No direction):
The inter-office bearer
is established without
direction.
BWAY

BACK: The inter-office


bearer is established
based on the backward
mode.

It is an optional
parameter. It is used to
specify the inter-office
bearer establishment
direction, with a default
of NODIR

FORWD: The
inter-office bearer is
established based on the
forward mode

Overload control
threshold

THD

It is an optional
parameter, ranging from
0 to 100, with a default
of 100. This parameter
takes effect when levels
of congestion occur and
load control is required

Circuit selecting modes,


including:
MIN: Every time when
the system selects a
trunk circuit, it always
begins with the circuit
with the minimum
number. This mode can
implement the preferred
plan of trunk circuits.

CICSEL

MAX: Every time when


the system selects a
trunk circuit, it always
begins with the circuit
with the maximum
number. This mode can
implement the preferred
plan of trunk circuits.
CYC: Every time when
the system selects
a trunk circuit, it
always begins with
the circuit next to the
one previously selected.
Suppose the numbers
of the trunk circuits in a
trunk group in ascending
order are TKC0, TKC1,
. , TKCn. If TKC0
is selected at the first
time, the system will
select the trunk circuit in
the order of TKC0TKC
1TKCnTKC0TK
C1TKCn.

It is an optional
parameter. It is used to
specify the trunk circuit
selecting policy of the
system within this trunk
group, with a default
of CYC. If this trunk
group is a two-way
trunk group, it is
recommended to set the
circuit selecting mode
to ODD/EVEN mode to
prevent contention when
two exchanges select
circuits

Confidential and Proprietary Information of ZTE CORPORATION

317

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter Description

Instruction

ODD: Every time when


the system selects a
trunk circuit, it always
selects the circuit with
an odd number.
EVEN: Every time when
the system selects a
trunk circuit, it always
selects the circuit with
an even number.
IDLE: Every time when
the system selects a
trunk circuit, it always
selects the idlest circuit.
BUSY: Every time when
the system selects a
trunk circuit, it always
selects the busiest circuit

DAS

SIPDAS

OPDAS

PREDAS

318

DAS for the called


number

It is an optional
parameter. It is used
to analyze the called
number in an incoming
call. This parameter
must be defined by
command ADD DAS at
first. Then it can be
indexed here

DAS for the domain


name of the called
number during SIP
outgoing calls

It is used get the name


of the IMS domain
where the called party
is located through
analyzing the called
number during a SIP
outgoing call. It is
only used for RTP trunk
groups

DAS for the calling


number

It is used to analyze
the calling number in
an incoming call. This
parameter must be
defined by command
ADD DAS at first. Then
it can be indexed here

DAS for pre-analyzing


the called number

It is used to pre-analyze
the called number in
an incoming call. This
parameter must be
defined by command
ADD PREDAS at first.
Then it can be indexed
here

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Parameter
Name

DDI

OPDDI

MINNAT

MAXNAT

MININT

MAXINT

INREG

Parameter Description

Instruction

Incoming called number


transform ID

It is the index of
the incoming called
number transform. This
parameter must be
defined by command
ADD DDI at first. Then
it can be indexed here

Incoming calling number


transform ID

It is the index of
the incoming calling
number transform. This
parameter must be
defined by command
ADD DDI at first. Then
it can be indexed here

Minimum national
number length

It is an optional
parameter, which is an
integer ranging from 0 to
26, with a default of 0.
It is used to specify the
minimum digit length of
the called number during
a national incoming call

Maximum national
number length

It is an optional
parameter, which is an
integer ranging from 0 to
26, with a default of 26.
It is used to specify the
maximum digit length of
the called number during
a national incoming call

Minimum international
number length

It is an optional
parameter, which is an
integer ranging from 0 to
26, with a default of 0.
It is used to specify the
minimum digit length
of the called number
during an international
incoming call

Maximum international
number length

It is an optional
parameter, which is an
integer ranging from 0 to
26, with a default of 26.
It is used to specify the
maximum digit length
of the called number
during an international
incoming call

Incoming register
signaling flag. Options
include:
INVALID

It is an optional
parameter, with a default
value of INVALID

Confidential and Proprietary Information of ZTE CORPORATION

319

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter Description

OUTREG

Outgoing register
signaling flag. Options
include:
INVALID

Instruction

It is an optional
parameter, with a default
value of INVALID

The maximum length of


CAS calling number end

It is an optional
parameter. It ranges
from 1 to 32, with a
default of 10.

Trunk circuit usage

It is an optional
parameter, which is
an integer ranging
from 1 to 100, with a
default of 100. After
the trunk circuit usage
is configured, when the
ratio of busy circuits
to all circuits in this
trunk group exceeds this
value, congestion occurs
in this trunk group.
After the congestion
is relieved, report the
trunk congestion times
and congestion duration
in the performance
statistics. This
parameter does not
take effect when it is
configured to 100

ROAMDAS

DAS for roaming


numbers

It is an optional
parameter. After this
DAS is configured, if
the local office serves
as a GMSC, this DAS
is preferred for the
returned roaming
numbers. Otherwise,
the roaming number
DAS configured in
the number analysis
template is used

Q850CCIDX

Q850 customization
index

It is an optional
parameter. It ranges
from 0 to 65535, with a
default of 0.

ID of signaling
modification entrance

IIt is an optional
parameter, associated
with the inter-office
signaling modification
entrance. It ranges
from 0 to 65535, with a
default of 0

COLEN

BUSYRATE

SMENTERID

Example: Create an ATM trunk group with the following requirements.

320

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Trunk group ID: 100

ID of the office where the trunk group belongs: 100

User alias: RNC

No. of the module processing the trunk group: 3

MGW topology node No.: 101

Inter-office line signal identification: BICC

Other parameters: Adopt the default values.

The command is:


ADD TG ATM:TG=100,OFC=100,MODULE=4,ND=101,NA
ME="RNC",SIGLINE=BICC,KIND=BIDIR,BWAY=NODIR,TH
D=100,CICSEL=ODD,DAS=0,SIPDAS=0,OPDAS=0,PRED
AS=0,DDI=0,OPDDI=0,MINNAT=0,MAXNAT=26,MININT
=0,MAXINT=26,INREG=INVALID,OUTREG=INVALID,COLE
N=10,BUSYRATE=100,ROAMDAS=0,Q850CCIDX=0,SME
NTERID=0,MLPPDM=4294967295,DISINDEX=0;
END OF STEPS

Configuring a RTP Trunk Group


Prerequisites

Before the operation, it is required to confirm:

The exchange ID to be configured is given.

The adjacent MGW or IM-MGW office to which the trunk group


points is created.

The trunk group No. range is set in the resource management


system.

The MML Terminal window is opened.

Context

When the IP bearer is adopted between MGWs, configure RTP trunk


groups, which are BICC trunk groups. When the MSCS servers
as a MGCF, the MGCF needs to control the IP resources from the
IM-MGW to the IMS domain through the RTP trunk group configuration data. In this case, SIP trunk groups need to be configured.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Add a RTP trunk group by executing command ADD TG RTP.
The explanation of the main parameters in command ADD TG
RTP is shown in Table 113.

Confidential and Proprietary Information of ZTE CORPORATION

321

ZXWN MSCS Data Configuration Guide(MSCS)

TABLE 113 PARAMETERS IN THE ADD TG RTP COMMAND


Parameter
Name

TG

OFC

NAME

MODULE

Parameter
Description

Instruction

Trunk group ID

It is a mandatory
parameter. It is used
to define a trunk group.
This trunk group can be
BICC trunk group or SIP
trunk group. It is a global
unified number

ID of the office where


the trunk group
belongs

It is a mandatory
parameter. It is used to
specify the corresponding
office of the trunk group.
This parameter must be
defined by command ADD
ADJOFC at first. Then it
can be indexed here

User alias

It is an optional parameter,
consisting of 0~50
characters. It is used
to specifically describe a
trunk group to make it
easily recognized

Module where the


trunk group belongs

It is a mandatory
parameter, which is an
integer, ranging from 1
to 127. It is used to
specify the SMP module of
processing traffic on this
trunk group

Inter-office line
signal identification,
including
SIGLINE

BICC (BICC
signaling)

SIP (SIP signaling)

It is an optional parameter.
Select SIP for the MGCF.

Trunk group types,


including the following
three types:
IN (incoming trunk
group): Indicates
that the local
office processes the
incoming calls from
the peer-end office.
KIND

OUT (outgoing trunk


group): Indicates
that the local office
only processes the
outgoing calls to the
peer-end office.
BIDIR (Two-way
trunk group):
Indicates that the local
office processes both

322

Confidential and Proprietary Information of ZTE CORPORATION

It is an optional parameter.
BIDIR is selected by
default. It should be
negotiated with the
peer-end office.

Chapter 8 Basic Service Data Configuration

Parameter
Name

Parameter
Description
the incoming calls
from the peer-end
office and the outgoing
calls to the peer-end
office

Instruction

Bearer establishment
direction, including
the following three
types:

BWAY

NODIR (No
direction): The
inter-office bearer
is established without
direction.
BACK: The inter-office
bearer is established
based on the backward
mode.

It is an optional parameter.
For RTP trunk groups, it
is set according to the
network plan of operators

FORWD: The
inter-office bearer
is established based
on the forward mode
Threshold for overload
control

THD

It is an optional parameter,
ranging from 0 to 100, with
a default of 100

Circuit selecting
modes, including:
MIN: Every time when
the system selects a
trunk circuit, it always
begins with the circuit
with the minimum
number. This mode
can implement the
preferred plan of trunk
circuits.

CICSEL

MAX: Every time


when the system
selects a trunk
circuit, it always
begins with the circuit
with the maximum
number. This mode
can implement the
preferred plan of trunk
circuits.

It is an optional parameter,
with a default of CYC. In
general, the signaling point
with big code prefers the
circuit with an even number,
while the one with small
code prefers the circuit
with an odd number. It
should be negotiated with
the peer-end office

CYC: Every time when


the system selects
a trunk circuit, it
always begins with the
circuit next to the one
previously selected.
Suppose the numbers
of the trunk circuits
in a trunk group in
ascending order are
TKC0, TKC1, . ,
TKCn. If TKC0 is

Confidential and Proprietary Information of ZTE CORPORATION

323

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction

selected at the first


time, the system will
select the trunk circuit
in the order of TKC0
TKC1TKCnTK
C0TKC1TKCn.
ODD: Every time
when the system
selects a trunk circuit,
it always selects the
circuit with an odd
number.
EVEN: Every time
when the system
selects a trunk circuit,
it always selects the
circuit with an even
number.
IDLE: Every time
when the system
selects a trunk circuit,
it always selects the
idlest circuit.
BUSY: Every time
when the system
selects a trunk circuit,
it always selects the
busiest circuit

DAS

SIPDAS

324

DAS for the called


number

It is an optional parameter,
which is an integer ranging
from 0 to 4096, with a
default of 0. When the
local office has the GMSC
function, this DAS is used to
analyze the called number
from other offices. When
the called number is from
the BSC office, this DAS is
meaningless, and does not
need to be configured

DAS for the domain


name of the called
number during SIP
outgoing calls

It is used get the name


of the IMS domain where
the called party is located
through analyzing the
called number during a
SIP outgoing call. If the
outgoing SIP trunk group
is configured with this
DAS, the invite message
during a SIP outgoing call
can only contain SIP URL
mode. If the outgoing
SIP trunk group is not
configured with this DAS,
configure the URLOPT in
the SIP adjacent office
configuration to decide
whether the outgoing call
uses TEL or SIP URL mode.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Parameter
Name

Parameter
Description

Instruction
After this DAS is used
on this trunk group, all
outgoing calls on this
trunk group will get the
corresponding domain
name according to the
called number, and then
form a SIP URL

OPDAS

DAS for the calling


number

It is an optional parameter,
which is an integer ranging
from 0 to 4096, with a
default of 0. When the
local office has the GMSC
function, this DAS is used to
analyze the calling number
from other offices. When
the calling number is from
the BSC office, this DAS is
meaningless, and does not
need to be configured

Example: Create a RTP trunk group with the following requirements.

Trunk group ID: 102

ID of the office where the trunk group belongs: 102

User alias: MGW102

No. of the module processing the trunk group: 3

Inter-office line signal identification: BICC

Other parameters: Adopt the default values.

The command is:


ADD TG RTP:TG=102,OFC=102,MODULE=4,NAME="MG
W102",SIGLINE=BICC,KIND=BIDIR,BWAY=NODIR,THD
=11,CICSEL=CYC,DAS=0,SIPDAS=0,OPDAS=0,PREDAS
=0,DDI=0,OPDDI=0,MINNAT=0,MAXNAT=26,MININT
=0,MAXINT=26,INREG=INVALID,OUTREG=INVALID,COLE
N=10,BUSYRATE=100,ROAMDAS=0,Q850CCIDX=0,SME
NTERID=0,MLPPDM=4294967295,SIPRUTS=0,DISINDEX
=0;
END OF STEPS

Creating a PCM System


Prerequisites

Before the operation, it is required to confirm:

The exchange ID to be configured is given.

The DT, ATM, or RTP trunk group is configured.

The MML Terminal window is opened.

Confidential and Proprietary Information of ZTE CORPORATION

325

ZXWN MSCS Data Configuration Guide(MSCS)

Context

The PCM system management data associate the resources on the


MGW with the signaling on the MSCS.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create a PCM system by executing command ADD SPCM.
The explanation of the main parameters in command ADD
SPCM is shown in Table 114.
TABLE 114 PARAMETERS IN THE ADD SPCM COMMAND
Parameter
Name

TG

Parameter
Description

Instruction

No. of the trunk


group where
the PCM system
belongs

It is a mandatory parameter,
which is an integer, ranging
from 1~1000. Select the
trunk group where this PCM
system belongs from the list
of configured trunk groups. It
is used to specify the trunk
group invoking this PCM
system. This parameter is
associated with the trunk
group No. in command ADD
TG ATM, ADD TG DT, ADD
TG PRA, and ADD TG RTP
It is a mandatory parameter.
It is a parameter for
interconnection with the
peer-end office. If the
configured PCM system
belongs to the inter-office
trunk, the PCM system No. of
the same circuit between two
offices must be the same.

PCM

PCM system No.

When the inter-office line


identification of a trunk group
is TUP or ISUP, the PCM
system No. ranges from 0 to
127.
When the inter-office line
identification of a trunk group
is BICC, the PCM system No.
ranges from 0 to 5999.
When the inter-office line
identification of a trunk group
is BSC or ANU, the PCM
system No. ranges from 0 to
2047

326

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Parameter
Name

NUM

Parameter
Description

Instruction

Number of created
PCM systems

It is an optional parameter. If
PCM systems belong to a DT
trunk group, this parameter
needs not be configured. If
PCM systems belong to a RTP
or ATM trunk group, select
the number the created PCM
systems

PCM No. in the


MGW

MGWPCM

NAME

E1

DDF

The corresponding
trunk group can
invoke the PCM
resources between
the start PCM No.
in the MGW and the
end PCM No.

It is an optional parameter.
If the PCM system belongs
to a RTP or ATM trunk group,
this parameter needs not be
configured. If the PCM system
belongs to a DT trunk group,
select the corresponding PCM
No. in the MGW

User alias

It is an optional parameter,
consisting of 1~50 characters.
It is used to specifically
describe the PCM system
configuration to make it
easily recognized

E1 identification

It is an optional parameter,
consisting of 1~50 characters.
For DT trunk groups,
describes the E1 with any
characters, which can be set
to DTB/SDTB unit No.-E1
No.

Digital Distribution
Frame (DDF)
location description

It is an optional parameter,
consisting of 1~50 characters.
For DT trunk groups, the DDF
location description can be set
to Frame No.-Row No.-Port
No.

Example: Create a PCM system to the BSC office with the following requirements:

No. of the trunk group where the PCM system belongs: 99

PCM system No.: 1

PCM No. in the MGW: 46

User alias: BSC1-1.

The command is:


ADD SPCM:TG=99,PCM=1,NUM=3,MGWPCM="4"-"6",INF
O=65535,NAME="BSC1-1";
END OF STEPS

Confidential and Proprietary Information of ZTE CORPORATION

327

ZXWN MSCS Data Configuration Guide(MSCS)

Creating a PCM System between MGWs


Prerequisites

Before the operation, it is required to confirm:

The exchange ID to be configured is given.

The bearer mode between the MGWs is configured in the topology configuration. .

The MML Terminal window is opened.

Context

When the MGWs managed by one MSCS are interconnected


through TDM circuits, it is required to configure the PCM systems
between the MGWs. Since the MGWs are interconnected within
the MSCS, it is required to add the bearer mode between the
MGWs in the topology configuration, but no trunk group, trunk
route or other parameters need to be configured.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create a PCM system between MGWs by executing command
ADD INPCM.
The explanation of the main parameters in command ADD
INPCM is shown in Table 115.
TABLE 115 PARAMETERS IN THE ADD INPCM COMMAND

328

Parameter
Name

Parameter
Description

Instruction

ND1

MGW1 node No.

It is a mandatory parameter.
Enter the topology node No. of
MGW1

ND2

MGW2 node No.

It is a mandatory parameter.
Enter the topology node No. of
MGW2

PCM

PCM system No.

It is a mandatory parameter.
Enter the PCM system No. in the
MSCS

ND1PCM

PCM No. in
MGW1

It is a mandatory parameter.
Enter the PCM system No. in
MGW1

ND2PCM

PCM No. in
MGW2

It is a mandatory parameter.
Enter the PCM system No. in
MGW2

MODULE

Management
module No.

It is a mandatory parameter.
Select the No. of the CMP module
of managing this PCM system

PCMTYPE

PCM type

It is an optional parameter, with a


default of E1

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Parameter
Name

Parameter
Description

Instruction

NAME

User alias

It is an optional parameter, which


is in the format of Adjacent office
MGW1 user alias-Adjacent office
MGW2 user alias-PCM system No.

ND1E1

E1 identification

It is an optional parameter, which


can be set to DTB/SDTB unit
No.-E1 No.

ND1DDF

DDF location
description

It is an optional parameter, which


can be set to Frame No.-Row
No.-Port No.

ND2E1

MGW2 E1 ID

It is an optional parameter, which


can be set to DTB/SDTB unit
No.-E1 No.

ND2DDF

Description of
MGW2 DDF
location

It is an optional parameter, which


can be set to Frame No.-Row
No.-Port No.

Example: Add a PCM system between MGWs with the following


requirements.

PCM system No.: 0

PCM No. in MGW1 and MGW2: 1

Management module No.: 4

User alias: MGW1-MGW2.

The command is:


ADD INPCM:ND1=101,ND2=102,PCM=0,ND1PCM=1,ND2
PCM=1,MODULE=4,PCMTYPE=E1,NAME="MGW1-MGW2";
END OF STEPS

Routing Data Configuration


Overview
Description

Outgoing route chains are directly referred to in number analysis


results. Each outgoing route chain contains at most 4 outgoing
route groups (in active/standby relationship), and each outgoing
route group contains at most 12 outgoing routes (in load sharing
relationship). The outgoing route has a one-to-one correspondence with the trunk group.

Data Configuration

The related operations of the routing data configuration are as follows.

Confidential and Proprietary Information of ZTE CORPORATION

329

ZXWN MSCS Data Configuration Guide(MSCS)

Steps

Operations

Instructions

Commands

Creating an
outgoing route

Each trunk group


corresponds to an
outgoing route.

ADD RT

Creating an
outgoing route
group

Each route
belongs to a
route group, and
each route group
contains at most
12 routes.

ADD RTS

Creating an
outgoing route
chain

Each outgoing
route group
belongs to an
outgoing route
chain, and each
route chain
contains at most 4
route groups.

ADD CHAIN

Creating an Outgoing Route


Prerequisites

Context
Steps

Before the operation, it is required to confirm:

The exchange ID to be configured is given.

The outgoing route No. range is set in the resource management system.

The MML Terminal window is opened.

Each trunk group corresponds to an outgoing route.


1. If no exchange is specified, execute command SET on the MML
Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Create an outgoing route by executing command ADD RT.
The explanation of the main parameters in command ADD RT
is shown in Table 116.
TABLE 116 PARAMETERS IN THE ADD RT COMMAND
Parameter
Name

RT

330

Parameter
Description

Instruction

Route No.

It is a mandatory parameter,
which is an integer, ranging
from 1~20000. It exclusively
identifies a route. To facilitate
management, the route No.
is configured to be consistent
with the trunk group No.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

Parameter
Name

Parameter
Description

Instruction

TG

Trunk group No.

It is a mandatory parameter,
corresponding to the trunk
group No. in the trunk group
configuration

Called number
transform index
during outgoing
calls

It is an optional parameter,
which is an integer ranging
from 0 to 2048, with a default
of 0. The called number is
transformed according to this
index during outgoing calls.
This index has no influence on
the incoming calls through this
trunk

OPDDI

Calling number
transform index
during outgoing
calls

It is an optional parameter,
which is an integer ranging
from 0 to 2048, with a default
of 0. The calling number is
transformed according to this
index during outgoing calls.
This index has no influence on
the incoming calls through this
trunk

DLPFX

Whether to delete
the prefix of the
calling number
during outgoing
calls, including
NO and YES

It is an optional parameter,
with a default of NO. If YES
is selected, the prefix of the
calling number (such as 0/00)
will be deleted during outgoing
calls

NAME

User alias

It is an optional parameter,
consisting of 0~50 characters.

DDI

Example: Create an outgoing route with the following requirements.

Route No.: 28

Trunk group No.: 28

User alias: Rout128

The command is:


ADD RT:RT=28,TG=28,DDI=0,OPDDI=0,DLPFX=NO,NAM
E="ROUT28",HOPCNT=0,RERTS=0,CLISETIDX=65535;
END OF STEPS

Creating an Outgoing Route Group


Prerequisites

Before the operation, it is required to confirm:

The exchange ID to be configured is given.

The outgoing route No. is added.

The MML Terminal window is opened.

Confidential and Proprietary Information of ZTE CORPORATION

331

ZXWN MSCS Data Configuration Guide(MSCS)

Context

Each route belongs to a route group, and each route group contains at most 12 routes.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Creat an outgoing route group by executing command ADD
RTS.
The explanation of the main parameters in command ADD RTS
is shown in Table 117.
TABLE 117 PARAMETERS IN THE ADD RTS COMMAND
Parameter
Name

RTS

NAME

Parameter
Description

Instruction

Route group No.

It is a mandatory parameter,
which is an integer, ranging
from 1~3000. It is used to
identify a route group

User alias

It is an optional parameter,
consisting of 0~50 characters.
It is used to specifically
describe a route group to make
it easily recognized
t is an optional parameter. It
is in the format of No.-Route
No.-Load sharing proportion.
When the percentage is set to
0, the poll mode is adopted.
SEQ: No., which is the location
of the route in the route group.

RTPER

Route No. and


load sharing
proportion list

RTVAL: Route No., associated


with the route group. This
parameter must be defined
by command ADD RT at first.
Then it can be indexed here.
PERVAL: Load sharing
proportion of each route in the
route group. If it is set to 0
for all routes by default, the
load is evenly allocated to each
route

Example: Add an outgoing route group with the following requirements.

332

Route group No.: 28

User alias: Rout28

Locaiton:1

Route No.: 28

Percentage: 0

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 8 Basic Service Data Configuration

The command is:


ADD RTS:RTS=28,NAME="ROUT28",RTPER="1"-"28"-"0";

Note:
Each outgoing route group can be configured with at most 12
outgoing routes, performing load sharing based on the poll or
percentage mode. One outgoing route can be allocated to different adjacent offices (such as TMSC1 and TMSC2), thus to
implement traffic load sharing to different offices.
END OF STEPS

Creating an Outgoing Route Chain


Prerequisites

Before the operation, it is required to confirm:

The exchange ID to be configured is given.

The outgoing route chain No. range is set in the resource management system.

The MML Terminal window is opened.

Context

Each outgoing route group belongs to an outgoing route chain, and


each route chain contains at most 4 route groups.

Steps

1. If no exchange is specified, execute command SET on the MML


Terminal window or select a NE from the system tree to specify the exchange to be configured.
Example: Select the MSCS exchange with ID as 11 from the
system tree.
SET:NEID=11;
2. Creat an outgoing route chain by executing command ADD
CHAIN.
The explanation of the main parameters in command ADD
CHAIN is shown in Table 118.
TABLE 118 PARAMETERS IN THE ADD CHAIN COMMAND
Parameter
Name

Parameter
Description

Instruction

CHAIN

Route chain No.

It is a mandatory parameter,
which is an integer, ranging
from 1 to 3000. It is
used to define an outgoing
route chain. When it is
configured in the number
analysis configuration, it
is associated to the route
chain configured here

NAME

User alias

It is an optional parameter,
consisting of 0~50
characters. It is used

Confidential and Proprietary Information of ZTE CORPORATION

333

ZXWN MSCS Data Configuration Guide(MSCS)

Parameter
Name

Parameter
Description

Instruction
to specifically describe a
route chain to make it easily
recognized

Whether the
preference policy
is supported in the
MGW, including:

PRND

NO: When 2B occurs,


the calls in the
same MGW are
not preferred, and
routing is performed
according to other
routing policies of the
system instead.

It is an optional parameter,
with a default of YES. It is
a policy for selecting the
rouging route

YES: When 2B
occurs, the calls in
the same MGW are
preferred

334

RTS1

No. of route group


1, used to set the
route group with
the highest priority
in a route chain
during routing. One
route chain can be
configured with at
most 4 route groups

RTS2

No. of route group 2,


used to set the route
group with the level-2
priority in a route
chain during routing.
One route chain can
be configured with at
most 4 route groups

RTS3

No. of route group 3,


used to set the route
group with the level-3
priority in a route
chain during routing.
One route chain can
be configured with at
most 4 route groups

RTS4

No. of route group 4,


used to set the route
group with the level-4
priority in a route
chain during routing.
One route chain can
be configured with at
most 4 route groups

Confidential and Proprietary Information of ZTE CORPORATION

It is an optional parameter.
Select route groups
according to the priority
order. Select route group 1
fist. Only when the circuits
in route group 1 are used
up or all the circuits are
unavailable, the circuits
in route group 2 can be
selected. Only when the
circuits in route group 2 are
used up or all the circuits
are unavailable, the circuits
in route group 3 can be
selected

Chapter 8 Basic Service Data Configuration

Parameter
Name

Parameter
Description

Instruction

RTPLC

Route Selection Policy


Number

It is an optional parameter.
Select the route selection
policy number configured in
ADD RTPLC command

DAS for the called


number

It is an optional parameter.
It is used to analyze
the called number in
an incoming call. This
parameter must be defined
by command ADD DAS
at first. Then it can be
indexed here. It needs to be
set only when Inter-MGW
route chain is set in the
called number analysis. The
default value is 0

TPDAS

Example: Create an outgoing route chain with the following


requirements.

Route chain No.: 28

User alias: RLink28

No. of Route group 1: 28

Other parameters: Adopt the default values.

The command is:


ADD
CHAIN:CHAIN=28,NAME="RLink28",PRINODE=YE
S,RTS1=28,RTS2=0,RTS3=0,RTS4=0,RTPLC=0,TPDAS
=0;
END OF STEPS

Confidential and Proprietary Information of ZTE CORPORATION

335

ZXWN MSCS Data Configuration Guide(MSCS)

This page is intentionally blank.

336

Confidential and Proprietary Information of ZTE CORPORATION

Chapter

Configuration Instance
Table of Contents
Overview........................................................................ 337
Local Office Data Configuration.......................................... 340
Resource Attribute Configuration ....................................... 345
Adjacent MGW Office Interconnection Data Configuration ............................................................................... 346
Adjacent HLR Office Interconnection Data Configuration ......... 349
Adjacent RNC Office Interconnection Data Configuration ............................................................................... 350
Location Update Data Configuration ................................... 352
Call Data Configuration .................................................... 354
Data Synchronization ....................................................... 355
MSCS-MGW Interconnection Debugging Procedure ............... 355
MSCS-HLR Interconnection Debugging Procedure................. 359
MSCS-RNC Interconnection Debugging Procedure ................ 365
Basic Service Debugging Procedure.................................... 366

Overview
Introduction

This chapter introduces the local office configuration procedure and


office interconnection data configuration procedure by taking the
example of creating a MSCS pilot office. Figure 64 shows the networking diagram.

Confidential and Proprietary Information of ZTE CORPORATION

337

ZXWN MSCS Data Configuration Guide(MSCS)

FIGURE 64 NETWORKING DIAGRAM

Note: Real lines indicate bearer connections, while dashed lines


indicate signaling connections
The RNC is directly connected with the MGW through the ATM
bearer, while the MSCS is directly connected with the MGW through
the IP bearer. The RANAP/SCCP signaling between the MSCS and
the RNC is forwarded by the MGW. The user data between the
MGW and the RNC are transferred through AAL2, and ALCAP signaling controls the AAL2 connection. The MSCS and MGW can be
interconnected with the RNC through different signaling points.
According to the networking condition shown in Figure 65, the operator is required to provide the negotiation data listed in Table
119 and Table 120.
TABLE 119 NEGOTIATION DATA INSTANCE
NE

Parameter

Attributes

Office ID

27

GT number of local office

8613903023

Signaling point type of the


local office

24-bit

SPC of the local office

3.20.1

Prefix of the roaming


numbers in the local office

8613903023

Roaming number range of


the local office

0~899

Prefix of the handover


numbers in the local office

8613903023

MSCS

338

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 9 Configuration Instance

NE

Parameter

Attributes

Handover number range of


the local office

900~999

17 channels of (9-interface)
E1 16 TS To HLR

SLC 0

Call prefix of the test


number

8613902099

PLMN ID

46000

Office ID

24

GT number of local office

8613903021

Signaling point type of the


local office

24-bit

SPC of the local office

3.21.1

ATM address

20.2020.0000.0000.0000.
0000.0000.0000.0000.000
0.00

AAL5 (signaling)
interconnecting with
VPI/VCI (4#)

1/32 (MGW) to 1/51 (RNC)

AAL2 (tone) interconnecting


with VPI/VCI (4#)

1/33 (MGW) to 2/32 (RNC)

Office ID

66

GT number of local office

8613903030

Signaling point type of the


local office

24-bit

SPC of the local office

100.100.30

Signaling point type of the


local office

24-bit

SPC of the local office

3.20.30

RNCID

123

Location Area Code (LAC)

0014

AMR coding/decoding rate

122

ATM address/coding type


(the coding type is NSAP)

30.3030.0000.0000.0000.
0000.0000.0000.0000.000
0.00

MGW

HLR

RNC

Confidential and Proprietary Information of ZTE CORPORATION

339

ZXWN MSCS Data Configuration Guide(MSCS)

TABLE 120 SIGTRAN IP ADDRESS INSTANCE OF THE MC


INTERFACE
Parameter

Attributes

IP of the loop-back interface at


the MSCS side

192.168.2.11/32

IP of the SIPI interface at the


MSCS side

192.168.1.11/16

IP of the loop-back interface at


the MGW side

192.168.2.22/32

IP of the SIPI interface at the


MGW side

192.168.1.22/16

Local Office Data


Configuration
The procedure of the local office data configuration is as follows:
Steps

Operations

Local exchange configuration

Physical configuration

Capacity and load sharing configuration

Version loading

Office data configuration

VLR configuration

Local Exchange Configuration


Data Planning

Table 121 lists the parameters in the local exchange configuration.


TABLE 121 DATA PLANNING OF THE LOCAL EXCHANGE
CONFIGURATION

340

Configuration Parameters

Configuration Description

Office ID

27

Exchange type

MSCS

User alias

MSCS27

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 9 Configuration Instance

Command

Configuration Parameters

Configuration Description

Code of the province where this


exchange is located

320000

Code of the city where this


exchange is located

320101

ADD NE:ID=27,TYPE=MSCS,MESUBTYPE=NONE,NAME="MSC
S27",VENDOR="ZTE",STATE=0;
SET PCINFO:PROVINCE="320000",CITY="320101";

Physical Configuration
Data Planning

When the MSCS office uses only one shelf, the board layout of the
BCTC shelf is shown in Figure 65. Table 122 lists the data planning
of the physical configuration.
FIGURE 65 BOARD LAYOUT OF THE BCTC SHELF

TABLE 122 DATA PLANNING OF THE PHYSICAL CONFIGURATION

Board

Type

CPU

Slot
No.

Unit
No.

Module
No.

Backup
Mode

OMP

X86

Slots 11
and 12

No. 1
OMP

1+1 activ
e/standby
mode

No.2 RPU

UIMC

UIM2_GC
S_755

Slots 9
and 10

921

1+1 activ
e/standby
mode

SMP

X86

Slots 7
and 8

34

1+1 activ
e/standby
mode

Confidential and Proprietary Information of ZTE CORPORATION

341

ZXWN MSCS Data Configuration Guide(MSCS)

Command

Board

Type

CPU

Slot
No.

Unit
No.

Module
No.

Backup
Mode

SIPI

SIPI_NC

Slot 3

321

No backup

SPB

SPB2_82
60_8262
0C4

Slot 5

521

No backup

1. Select an exchange.
SET:NEID=27;
2. Create a shelf.
ADD SHELF:RACK=1,SHELF=2,TYPE=BCTC;
3. Create UIM units
ADD UNIT:LOC="1"-"2"-"9",MODULE=1,UNIT=921,TYPE
=UIM2_GCS_755,BKMODE=ONEPLUSONE,CLK1=16383,CL
K2=16383;
4. Create modules.
ADD MODULE:LOC="1"-"2"-"7",MODULE="3",FUNC1="SM
P"&"MSCBASECMP"&"VMSC/CMP_GO/CMP_MSCe/CMP_VLR/C
MP_G_GMSC",CPUTYPE=CENTRINO,BKMODE=NO;
5. Create SPB units.
ADD UNIT:LOC="1"-"2"-"5",MODULE=1,UNIT=521,TYPE
=SPB2_8260_8260C4,BKMODE=NO,CLK1=16383,CLK2=16
383;
6. Create SIPI units.
ADD UNIT:LOC="1"-"2"-"3",MODULE=1,UNIT=321,TYPE
=SIPI_NC,BKMODE=NO,CLK1=16383,CLK2=16383;

Capacity and Load Sharing


Configuration
Data Planning

Table 123 lists the parameters in the capacity and load sharing
configuration.
TABLE 123 DATA PLANNING OF THE CAPACITY AND LOAD
SHARING CONFIGURATION

Command

342

Configuration Parameters

Configuration Description

Office capacity

Adopts the default value

Service data area

The number of destination codes


is 4096

1. Configure the MSCS office capacity.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 9 Configuration Instance

SET MSCSCAPACITY;
For the subsequent steps, refer to Setting the MSCS Office Capacity.
2. Configure the service data area.
SET DATASIZE:CMODEL=AMONLY,BCBMNUM=10,DSTCD
NUM=4096;
3. Create the IMSI load sharing.
ADD IMSILOAD:MODULE="3";
4. Create the TMSI load sharing.
ADD TMSILOAD;

Version Loading
After the physical configuration and capacity configuration are
completed, it is required to load the board version in order to let
the foreground board run normally. For the steps of loading the
version files, refer to Overview.

Office Data Configuration


Data Planning

Table 124 lists the parameters in the office data configuration.


TABLE 124 DATA PLANNING OF THE OFFICE DATA
CONFIGURATION
Configuration Parameters

Configuration Description

Network type

Area code

25

Signaling point type of the local


office

24-bit

SPC of the local office

3.20.1

Exchange type

Local exchange/toll exchange/in


the same region

Signaling point type

SEP

MSC number of the local office

8613903023

VLR number of the local office

8613903023

MCC

460

MNC

00

Length of the mobile subscriber


number

Confidential and Proprietary Information of ZTE CORPORATION

343

ZXWN MSCS Data Configuration Guide(MSCS)

Command

1. Configure the signaling point of the local office.


ADD OPC:NET=1,NAME="MSCS27",RC="25",SPCFMT=TRI
PLE_DEC,OPC24="3.20.1",APPTYPE="ALCAP"&"BICC"&"H.2
48"&"SCCP",PREFIX="0",NETAPP=0,INFO=NONETAPP,DM
IDX=0;
2. Create the local exchange configuration.
ADD
LOFC:OFCTYPE="LOCAL"&"DOMTOLL",NET=1,SEQ
=0,TCODE="1234",SPTYPE=SEP,LANG=DEFAULT,RESTAR
T=YES,RSTTIME=10000,T19=68,T20=60,T21=64;
3. Create the local office mobile data.
ADD
MSCCFG:MSC="8613903023",VLR="8613903023",C
C="86",NDC="139",MCC="460",MNC="00",OFCTYPE="EO
",SNLEN=3,PREINT="00",RC="25",TAG="SMS MT"&"SMS
MO"&"LOCCIC_NOOUT",NSYIND=255,SOURCE=SPEECH,R
NCRESET=3,SUPCAPA="NONE",SELFCIC="0",DEFCIC="0
",DEFNAEA=65535,CODETYPE=G711A64,SUPPCALLEDPB
RT=NO,SUPPCALLINGPBRT=NO,PLAYCWTONE=NO,OMC
PRIOR=NO,LOADTYPE=NEXTLV,RCSKEY=255,RCMINLEN
=1,RCMAXLEN=20,RCTAG=NO,CNID=0,LICOFCID=0,OS
BDAS=0,ROAMPLC=NO,USSDPLC=MSISDN_USSDC,IFDFT
ZC=DISABLE,DFTZC="FFFF",USRTYPEJUDGE=NUMBER,RE
LCALLNUM=0,BICCCS=OFF,FAXDELAY=5,IGNLANOTALL
OW=NO,CRD=NO,CMPBSCCODEC=FALSE;
4. Create the CC.
ADD CC:CC="86",NAME="CHINA";

VLR Configuration
Data Planning

Table 125 lists the parameters in the VLR configuration.


TABLE 125 DATA PLANNING OF THE VLR CONFIGURATION
Configuration Parameters

Configuration Description

VLR system parameter


VLR system capacity

Adopts the default value

Services supported by the VLR

Command

344

Prefix of the roaming numbers in


the local office

8613903023 (Prefix + Dynamic


digits (not more than 15 digits)

Prefix of the handover numbers in


the local office

8613903023

Roaming number range of the


local office

0~899

Handover number range of the


local office

900~999

1. Create the VLR system parameter.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 9 Configuration Instance

ADD
VLRSYS:MRNEXTYPE=EXMSRN,MRNALCTYPE=IG
N2G3G,MRNDYNDIGIT=3,MSTMLMT=24,MRNTMLMT=9
0,MHNTMLMT=90,LUTM=30,LUPROTECTTM=15,MAXFW
D=1,PAGENRCNT=3,PAGENRTM=2,BUSYLMT=5,IDREQ
=YES,LOCTMSI=ALWAYS0,OPCNTPA=0,TMLMTPA=0,MRN
INTERRG=NO,CMRNMODULE=0,RETMSITIME=30;
2. Create the VLR system capacity.
ADD VLRCAP:TRATAB=50,IMEITAB=50,MRNTAB=900,M
HNTAB=100,ICUGPER=50,BCUGPER=50,ZCPER=50,OCSI
PER=120,SSCSIPER=100,TCSIPER=100,DCSIPER=100,M
CSIPER=100,SMSCSIPER=100,LCSPER=20,BSGPER=40
0,FSAPER=50,ACCESSCD=0,ALS=0,IGWMSTAB=1000,IG
WTRATAB=1000,IGWZCTAB=1000,IGWOCSITAB=1000,I
GWTCSITAB=1000,IGWCUGTAB=1000,IGWSPCDTAB=1
000,IGWABBRTAB=1000,IGWMRNTAB=1000,USERBAK
=0;

Note:
Restart the MP after the configuration.
3. Create the services supported by the VLR.
ADD
VLRSRV:ODB="ALL",OTHER="ALL",TELESRV="ALL
",SPECTS="ALL",CDA="ALL",CDS="ALL",PAD="ALL",PDS
="ALL",SPEECH="ALL",SPECBS="ALL",CCBS=NONE;
4. Create the prefix of the roaming numbers in the local office.
ADD MRNPFX:MRNPFX="8613903023";
5. Create load sharing for roaming numbers.
ADD MRNSH:MRNPFX="8613903023",MODULE="3",NUM
BEGIN=0,NUMEND=899,IDFLAG=3G;
ADD MRNSH:MRNPFX="8613903023",MODULE="1",NUM
BEGIN=900,NUMEND=999,IDFLAG=HON;

Resource Attribute
Configuration
Resource Planning

The instance of resource attribute configuration is shown in Table


126.

Confidential and Proprietary Information of ZTE CORPORATION

345

ZXWN MSCS Data Configuration Guide(MSCS)

TABLE 126 RESOURCE PLANNING INSTANCE


Configuration Items

Resource
Types

Key Fields

Minimum

Maximum

Office data
configuration

Adjacent
office

Office ID

20

Node
Topology
Config

Topology
node ID.

20

Voice codec
template

Template ID

10

SCTP

SCTP ID

20

ASP

ASP ID

20

AS

AS ID

20

M3UA static
route

M3UA static
route ID

Signaling
link set

Link set No.

20

Signaling
route

Signaling
route No.

20

Number
Analysis
Selector

Number
Analysis
Selector

300

Number
Analysis
Entrance

Number
Analysis
Entrance

50

Location
Area

Location
Area ID

5000

Topology
configuration

Protocol
configuration

Access configuration

Adjacent MGW Office


Interconnection Data
Configuration
Data Planning

346

Table 127 lists the parameters in the adjacent-MGW-office interconnection data configuration.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 9 Configuration Instance

TABLE 127 PARAMETERS IN THE ADJACENT MGW OFFICE


INTERCONNECTION DATA CONFIGURATION
Configuration Parameters

Configuration Description

IP of the loop-back interface at


the MSCS side

192.168.2.11/32

IP of the SIPI interface at the


MSCS side

192.168.1.11/16

IP of the loop-back interface at


the MGW side

192.168.2.22/32

IP of the SIPI interface at the


MGW side

192.168.1.22/16

Adjacent MGW office ID

Adjacent MGW office type

MGW

Association mode

AM_SURE (Associated)

MGW topology node No.

Signaling point type of the MGW

24-bit

SPC of the MGW

3.21.1
he coding/decoding template No.
is 1.

Tone coding/decoding template


No.

The ETSI coding/decoding type is


ETSI_UMTS_AMR_2.
The supported coding/decoding
rates are 5.90K and 6.70K.
The activated coding/decoding
rates are 5.90K and 6.70K

Command

SCTP ID

ASP ID

AS ID

M3UA static route ID

SIO-locating-AS ID

TID analyzer index

TID command template No.

It is 1 by default

1. Create the loop-back interface.


INTERFACE LOOPBACK:PORT=1;
ADD IP ADDRESS:ADDRESS="192.168.2.11",MASK="255.
255.255.255",BROADCASTIP="255.255.255.255";
SAVE ONLINEDATA;
EXIT;

Confidential and Proprietary Information of ZTE CORPORATION

347

ZXWN MSCS Data Configuration Guide(MSCS)

2. Create the SIPI interface address.


INTERFACE:SUBSYSTEM=0,MODULE=1,UNIT=321,SUNI
T=1,PORT=1;
ADD IP ADDRESS:ADDRESS="192.168.1.11",MASK="255.
255.0.0",BROADCASTIP="255.255.255.255";
SAVE ONLINEDATA;
EXIT;
3. Create an adjacent MGW office.
ADD ADJOFC:ID=3,NAME="MGW3",NET=1,OFCTYPE=M
GW,SPCFMT=TRIPLE_DEC,SPCTYPE=24,DPC="3.21.1",RC
="25",ASSOTYPE=AM_SURE,SPTYPE=SEP,SSF=NATIONA
L,SUBPROTTYPE=DEFAULT,TEST=YES,BANDFLAG=YES,P
RTCTYPE=CHINA,CLST=65535,INFO="CIC_PCM",RELATE
DOFC1=0;
4. Create a tone coding/decoding template.
ADD
CODECTPL:ID=1,GRPID=GRPID1,VALFG=YES,OID
=OID_ETSI,ETYPE=ETSI_UMTS_AMR_2,ACTRATE="Rate59
0"&"Rate670",SUPRATE="Rate590"&"Rate670",OM=YES;
5. Create a MGW topology node.
ADD TOPO:ID=3,OFCID=3,NAME="MGW3",CODECID=1,E
TYPE=R4GW,PROTTYPE=H248,DMNAME="MGW",IPVER
=IPV4,ATTR="BNCAAL2"&"BNCIPRTP"&"BNCTDM",UPVER
="V2",ATTR2=DTUNL,TRFMOD=MCINTF,UPERRCTRL=YE
S,DTMFTC=NO,MGWCON=SMGWCON,AUTOFAX=YES,OO
BTC=NO,BCUID=0,SENDCAP=NO,G711TRAN=NO,BICCD
TMF=TRANSPARENT,IPBCP2833=BYMGW,BICCDTMPPER
=0,AOIPPRO=PRIVATE;
6. Create the SCTP.
ADD SCTPCONN:MODULE=3,OFCID=3,PROT=M3UA,ROL
E=CLT,LOCADDR="IPv4"-"0"-"192.168.2.11",LOCPORT=2
100,REMADDR="IPv4"-"0"-"192.168.2.22",REMPORT=210
0,NAME="MGW3-1",ID=1,INSTRM=16,OUTSTRM=16,MA
XRTRY=5,MAXRTO=500,MINRTO=50,INITRTO=100,HB
=500,FIXNH=NO,SCTPMAXRTRYNUM=10,DELAYACK=2
0,MAXBURST=4,PRIMARYPATH=REMIP1,PMTU=0,BREAK
TIME=3,PDTHRESH=0,MINCWND=0,PLTIMER=10,MPPL
THRD=2,DPLEN=MTU,CB=200;
7. Create the ASP.
ADD ASP:ASSOCID=1,NAME="MGW3-1",ID=1,ISLOOP=N
O,ISLOCK=NO;
8. Create the AS.
ADD
AS:PROT=M3UA,ASPID="1",NAME="MGW3-1",ID
=1,EXISTCTX=NO,ASTAG=CLT,ASUP="H248",ASMD=LOA
D,NVAL=1,KVAL=0;
9. Create a M3UA static route.
ADD M3UART:ID=1,ASID=1,MODE=BYTURNS,NAME="MG
W3";
10. Create the SIO-locating-AS.

348

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 9 Configuration Instance

ADD SIOLOCAS:ID=1,NAME="MGW3",SIO=H248,OFCID
=3,OPOFCID=65535,PCM=65535,RT1=1,RT2=0;
11. Create MSCS tones in batches.
BADD STONE:TYPE=ALL;
12. Create the MGC static data.
ADD MGCSCFG:MEGACO=1,ACTTM=600,ACTCHK=ON,W
AITTM=7800,PTRYNUM=5,PTRYTM=4000,CTXLIVETM=1
200,MGACTTM=600;
13. Create the MGW static data template.
ADD MGSTPL:NAME="MGW3",ID=1,MEGACO=1,ACTCHK
=ON,PRTTM=10,PRT=ON,PENDTM=200,LNGTM=15000,R
TRNTM=3800,MTRNNUM=1,TRNMD=UNFIXED,CTYPE=TE
XT;
14. Create the MGW static data.
ADD
MGSCFG:ID=3,TPLID=1,TONEID=1,LANGID=1,N
AME="MGW3",PKGLOST=10,JIT=50,DELAY=200,MGW
=NO;
15. Create the TID analyzer.
ADD TIDANL:NAME="MGW3",PREV=1,TIDPFX="TDM",TA
G=TRUNK,PCMSPR="_",IDXSPR="/",PCMPOS1=1,PCMPO
S2=0,IDXPOS1=1,IDXPOS2=0;
16. Create the TID analyzer entry.
ADD
TIDENTR:ND=3,TIDENTID=1,TIDTPLID=1,NAME
="MGW3";

Adjacent HLR Office


Interconnection Data
Configuration
Data Planning

Table 128 lists the parameters in the adjacent-HLR-office interconnection data configuration.
TABLE 128 PARAMETERS IN THE ADJACENT HLR OFFICE
INTERCONNECTION DATA CONFIGURATION
Configuration Parameters

Configuration Description

Adjacent HLR office ID

Adjacent HLR office type

HLR/HLRe

Association mode

AM_SURE (Associated)

Area code

25

Signaling point type of the HLR

24-bit

Confidential and Proprietary Information of ZTE CORPORATION

349

ZXWN MSCS Data Configuration Guide(MSCS)

Command

Configuration Parameters

Configuration Description

SPC of the HLR

100.100.30

Signaling link set ID (64K


narrow-band)

Signaling link ID

Start time slot No. of the E1

16

Signaling link code in a signaling


link set

0 (consistent with that of the peer


end)

Signaling route ID

1. Create an adjacent HLR office.


ADD ADJOFC:ID=1,NAME="HLR",NET=1,OFCTYPE="HLR/
HLRe",SPCFMT=TRIPLE_DEC,SPCTYPE=24,DPC="100.100
.30",RC="25",ASSOTYPE=AM_SURE,SPTYPE=SEP,SSF=N
ATIONAL,SUBPROTTYPE=DEFAULT,TEST=YES,BANDFLAG
=NO,PRTCTYPE=CHINA,CLST=65535,INFO="CIC_PCM",RE
LATEDOFC1=0;
2. Create a signaling link set.
ADD N7LKS:OFCID=1,TYPE=N64,ID=1,LECM=BASIC,NA
ME="HLR-1";
3. Create a SPB access signaling link.
ADD N7LNKE1:LKSID=1,SLC=0,MODULE=3,NAME="HLR1-1",ID=1,SPBUNT=521,CPU=1,E1=9,TS=16,LOOP=NO,I
NFO=E1,FCPLTHR=255;
4. Create a signaling route.
ADD
N7ROUTE:NAME="HLR1",LKSID1=1,LKSID2=0,ID
=1,LPM=RAND,LPMIN=RAND,MANUAL=NO;
5. Create the signaling office direction.
ADD
N7OFC:ID=1,RT1=1,RT2=0,RT3=0,RT4=0,NAME
="HLR1";

Adjacent RNC Office


Interconnection Data
Configuration
Data Planning

350

Table 129 lists the parameters in the adjacent-RNC-office interconnection data configuration.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 9 Configuration Instance

TABLE 129 PARAMETERS IN THE ADJACENT RNC OFFICE


INTERCONNECTION DATA CONFIGURATION

Command

Configuration Parameters

Configuration Description

Signaling point type of the RNC

24-bit

SPC of the RNC

3.20.30

Adjacent RNC office ID

Adjacent RNC office type

RNC

Association mode

AM_QUASI (Quasi-associated)

RNC topology node No.

RNCID

123 (provided by the radio side)

ATM address/coding type (the


coding type is NSAP)

20.2020.0000.0000.0000.0000.0
000.0000.0000.0000.00

SCTP ID

ASP ID

AS ID

M3UA static route ID

SIO-locating-AS ID

1. Create an adjacent RNC office.


ADD ADJOFC:ID=2,NAME="RNC2",NET=1,OFCTYPE="RN
C",SPCFMT=TRIPLE_DEC,SPCTYPE=24,DPC="3.20.30",AS
SOTYPE=AM_QUASI,SPTYPE=SEP,SSF=NATIONAL,SUBPR
OTTYPE=DEFAULT,TEST=YES,BANDFLAG=NO,PRTCTYPE
=CHINA,CLST=65535,INFO="CIC_PCM",RELATEDOFC1=0;
2. Create the RNC office direction attributes.
ADD
RNCOFC:OFCID=2,MCC="460",MNC="00",RNCID
=1,RABDLY=100,SDUERA=ERRRATIO2,RBERA=ERRRATIO
7,RBERB=ERRRATIO4,RBERC=ERRRATIO3,SELMGTYPE=E
XCELLENT,ATMADDR="123456789012345",ADDRPLAN=E1
64,BTRY1=NO,BTRY2=NO,RAS=NO;
3. Create a RNC topology node.
ADD TOPO:ID=2,OFCID=2,NAME="RNC2",CODECID=1,E
TYPE=RNC,PROTTYPE=H248,DMNAME="RNC",IPVER=IPV
4,UPVER="V2",ATTR2=NOTUNL,TRFMOD=MCINTF,UPERR
CTRL=YES,DTMFTC=NO,MGWCON=SMGWCON,AUTOFAX
=YES,OOBTC=NO,BCUID=0,SENDCAP=NO,G711TRAN=N
O,BICCDTMF=TRANSPARENT,IPBCP2833=BYMGW,BICCD
TMPPER=0,AOIPPRO=PRIVATE;
4. Create the topology relationship between the RNC and the
MGW.
ADD
RNCMGWTOPO:MGWID=3,RANTYPE=RNC,RANID
=2,SHMODE=NONE,BTYPE1=ATM,BRATIO1=1,BTYPE2=N
ONE,BRATIO2=1,BPER=1;

Confidential and Proprietary Information of ZTE CORPORATION

351

ZXWN MSCS Data Configuration Guide(MSCS)

5. Create the SCTP.


ADD SCTPCONN:MODULE=3,OFCID=3,PROT=M3UA,ROL
E=CLT,LOCADDR="IPv4"-"0"-"192.168.2.11",LOCPORT=2
101,REMADDR="IPv4"-"0"-"192.168.2.22",REMPORT=210
1,NAME="MGW3-2",ID=2,INSTRM=16,OUTSTRM=16,MA
XRTRY=5,MAXRTO=500,MINRTO=50,INITRTO=100,HB
=500,FIXNH=NO,SCTPMAXRTRYNUM=10,DELAYACK=2
0,MAXBURST=4,PRIMARYPATH=REMIP1,PMTU=0,BREAK
TIME=3,PDTHRESH=0,MINCWND=0,PLTIMER=10,MPPL
THRD=2,DPLEN=MTU,CB=200;
6. Create the ASP.
ADD ASP:ASSOCID=2,NAME="MGW3-2",ID=2,ISLOOP=N
O,ISLOCK=NO;
7. Create the AS.
ADD
AS:PROT=M3UA,ASPID="2",NAME="MGW3-2",ID
=2,EXISTCTX=NO,ASTAG=ASP,ASUP="SCCP"&"ALCAP",AS
MD=LOAD,NVAL=1,KVAL=0;
8. Create a M3UA static route.
ADD M3UART:ID=2,ASID=2,MODE=BYTURNS,NAME="RN
C2";
9. Create the SIO-locating-AS.
ADD
SIOLOCAS:ID=2,NAME="RNC2",SIO=SCCP,OFCID
=2,OPOFCID=65535,PCM=65535,RT1=2,RT2=0;

Location Update Data


Configuration
Data Planning

Table 130 lists the parameters in the location update data configuration.
TABLE 130 PARAMETERS IN THE LOCATION UPDATE DATA
CONFIGURATION

352

Configuration
Parameters

Configuration Description

LAC (HEX)

14

LAI

11

MCC

460

MNC

GT number of the HLR

8613903030

GT number of the
MSCS

8613903023

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 9 Configuration Instance

Configuration
Parameters

Configuration Description

Call prefix of the test


number

8613902099
T translation selector 1: E.164 numbering
plan
The national minimum digit length is 5, and
the national maximum digit length is 15.

GT translation selector

The international minimum digit length is 1,


and the international maximum digit length
is 5.
GT translation selector 2: E.214 numbering
plan
The national minimum digit length is 5, and
the national maximum digit length is 15.
The international minimum digit length is 1,
and the international maximum digit length
is 5.

Command

Routing mode

GT routing

IMSI prefix

46000

1. Create a LAI controlled by the local office.


ADD LAI:LAC="0014",NAME="LAI1",ID=11,MCC="460",M
NC="00",LOCNUM="01",ECCIDX=0,BSC="0",RNC="3",TP
DAS=0,BELONG=MSC,WDMID=0,UPVER=1,R5HOCASE
=NO,GSMSSPGID=0,UMTSSSPGID=0,PAGEIDX=0,ASST
IMER=0;
2. Create a GT translation Selector.
ADD GTT:GTT=4,TT=0,PLAN=E.164,NATURE=INT,GTTO
PT=0,ID=1,CC="86",NMIN=5,NMAX=15,IMIN=1,IMAX
=5,CTRL=R_L,NAME="E.164";
ADD GTT:GTT=4,TT=0,PLAN=E.214,NATURE=INT,GTTO
PT=0,ID=2,CC="86",NMIN=5,NMAX=15,IMIN=1,IMAX
=5,CTRL=R_L,NAME="E.214";
3. Create GT translation data.
ADD GT:GT="8613903030",GTSL=1,GTDI=0,OFCIDS="1
"-"1",GRP=NO,SSN=NO_SSN,NTRNTYPE=0,TRNRLT="NU
LL",RTTYPE=GT,NGTTAG=NGT,SCCP=INT,VGT=NO,TT=N
O,NPFLAG=NO,NPLAN=NULL,SRVTYPE=NULL;
ADD GT:GT="8613903023",GTSL=1,GTDI=0,OFCIDS="0
"-"1",GRP=NO,SSN=NO_SSN,NTRNTYPE=0,TRNRLT="NU
LL",RTTYPE=GT,NGTTAG=NGT,SCCP=INT,VGT=NO,TT=N
O,NPFLAG=NO,NPLAN=NULL,SRVTYPE=NULL;
ADD GT:GT="8613902099",GTSL=1,GTDI=0,OFCIDS="1
"-"1",GRP=NO,SSN=NO_SSN,NTRNTYPE=0,TRNRLT="NU
LL",RTTYPE=GT,NGTTAG=NGT,SCCP=INT,VGT=NO,TT=N
O,NPFLAG=NO,NPLAN=NULL,SRVTYPE=NULL;
4. Create IMSI number analysis.
ADD IMSIANA:IMSI="46000",HDSTCODE="8613903030
",HDSTCODET=HLR,SM=0,OPID=0,INDADC=NO;

Confidential and Proprietary Information of ZTE CORPORATION

353

ZXWN MSCS Data Configuration Guide(MSCS)

5. Create a mobile service access number and MNC


ADD NDCMNC:NAME="139",ID=1,CC="86",NDC="139",M
CC="460",MNC="00";

Call Data Configuration


Data Planning

Table 131 lists the parameters in the call data configuration.


TABLE 131 PARAMETERS IN THE CALL DATA CONFIGURATION
Configuration
Parameters

Configuration Description

Number analyzer entry

1 (Local number analyzer)

DAS

Originating DAS 101


Roaming number DAS 201

Call prefix of the test


number

8613902099

Prefix of the roaming


numbers in the local
office

8613903023

Prefix of the handover


numbers in the local
office

8613903023
13902099: MSCO (MSC common service)

Command

Call service type

1390302: MSLL (MSC local-network


local-office service)

PLMN ID

46007

1. Create a number analyzer entry.


ADD ENTR:ID=1,NAME="LOCAL",TYPE=LOCAL,NTYPE=CA
LLED;
ADD ENTR:ID=2,NAME="LOCAL",TYPE=LOCAL,NTYPE=CA
LLED;
2. Create a DAS.
ADD
DAS:ID=101,NAME="MSQH",NEWSRV=0,CENTR
=0,PRINET=0,SPECSRV=0,LOCAL=1,NATIONAL=0,INTE
R=0;
ADD
DAS:ID=201,NAME="ROAM",NEWSRV=0,CENTR
=0,PRINET=0,SPECSRV=0,LOCAL=2,NATIONAL=0,INTE
R=0;
3. Modify the DAS for the called number in the LAI.
SET LAI:ID=11,TPDAS=101;
4. Create the default DAS template of the local office.

354

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 9 Configuration Instance

SET LDASTMPLT:MS=101,MSRN=201;
5. Create called number anlysis.
ADD TPDNAL:ENTR=1,DIGIT="13902099",SPECRST=0,S
PECIDX=0,CAT=MSCO,RST1=0,RST2=0,RST3=0,CHAIN
AL=0,RNLEN=0,MINLEN=3,MAXLEN=20,OVLYPRI=NO,R
EL=NO,NET=1,NAT=DEF,OPDDICONT=NO,TPDDICONT
=NO,OPDDI=0,TPDDI=0,OPDLYDDI=0,TPDLYDDI=0,DD
IOVERB=0,IWVIDEO=LSUP,TIMELMT=0,AUXDAS=0,A6
=0,PFXLEN=0,INSRV=INM,FAXIDX=0,AVIDX=0,DVIDX
=0,ADATAIDX=0,DDATAIDX=0,DDCPLAY=NONE,VAD=IN
VALID,CALLSERVPRILVL=INVALID,RERTS=0,INCHAIN=N
O,BICT=NO,ICT=0,ICTT=10,GNM=NORMAL,STBILL=INVA
LID,HOPDAS=0,MCA=NO,IVVR=NO,WANTL=0,IMSCENTR
=NO;
ADD TPDNAL:ENTR=2,DIGIT="1390302",SPECRST=0,S
PECIDX=0,CAT=MSLL,RST1=0,RST2=0,RST3=0,CHAINA
L=0,RNLEN=0,MINLEN=3,MAXLEN=20,OVLYPRI=NO,R
EL=NO,NET=1,NAT=DEF,OPDDICONT=NO,TPDDICONT
=NO,OPDDI=0,TPDDI=0,OPDLYDDI=0,TPDLYDDI=0,DD
IOVERB=0,IWVIDEO=LSUP,TIMELMT=0,AUXDAS=0,A6
=0,PFXLEN=0,INSRV=INM,FAXIDX=0,AVIDX=0,DVIDX
=0,ADATAIDX=0,DDATAIDX=0,DDCPLAY=NONE,VAD=IN
VALID,CALLSERVPRILVL=INVALID,RERTS=0,INCHAIN=N
O,BICT=NO,ICT=0,ICTT=10,GNM=NORMAL,STBILL=INVA
LID,HOPDAS=0,MCA=NO,IVVR=NO,WANTL=0,IMSCENTR
=NO;

Data Synchronization
Command

SYNA:STYPE=ALL,TIMEOUT=600,SAVE=YES,TOSLAVE=YES;

MSCS-MGW Interconnect
ion Debugging Procedure
After data of the MGW are configured on the MSC Server, the common procedures for data debugging are as follows:
Steps

Operations

Description

Check the MGW office status

Check whether the MGW


office is accessible

Check the physical


connection

When the office is


inaccessible, first confirm
whether there is any
hardware problem

Confidential and Proprietary Information of ZTE CORPORATION

355

ZXWN MSCS Data Configuration Guide(MSCS)

Steps

Operations

Description

Debug the SCTP

After the hardware problem


is removed, confirm whether
there is any problem in the
SCTP association

Debug the M3UA

After the problem in the


SCTP association is removed,
confirm whether there is
any problem in upper-layer
M3UA signaling link

Confirm the working status


of the MGW

After the problem on the


M3UA layer is removed,
check the H.248 gateway
configuration

Checking the MGW Office Status


Context

Check whether the office is accessible is the first step for debugging. This section introduces the detailed procedures for checking
whether the MGW office is accessible.

Steps

1. On the NetNumen M30 window, select menus Views > MML


Terminal to enter the MML Terminal window.
2. If no exchange is specified, execute command SET on the MML
Terminal window or select a NE from the system tree to specify the MSCS exchange to be configured.
3. Enter the following command on the MML Terminal window,
and click Execute to query the status of the adjacent MGW
office. OFC is the adjacent MGW office ID.
SHOW OFCSTAT:OFC=3;
4. If the office is inaccessible, skip to Checking the Physical Connection.

Note:
You can check whether the office is accessible, and the status
of the SIGTRAN signaling on the Dinamic management page
of the View window.
END OF STEPS

Checking the Physical Connection


Context

356

If it is found that the adjacent MGW office is inaccessible on the


NetNumen M30 window, confirm whether the physical connection between the MSCS and the MGW is normal.

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 9 Configuration Instance

Steps

1. When the ZXWN MSCS is connected with the MGW through


HUB, the straight network cable should be adopted. When the
ZXWN MSCS is directly connected with the MGW, the crossover
network cable should be adopted.
2. The physical connection is normal when the indicators Link1
and Link3 on the SIPI board are always on.
END OF STEPS

Debugging the SCTP


Context
Steps

If the physical connection is normal, debug the SCTP.


1. On the NetNumen M30 window, select menus Views > MML
Terminal to enter the MML Terminal window.
2. If no exchange is specified, execute command SET on the MML
Terminal window or select a NE from the system tree to specify the MSCS exchange to be configured.
3. Enter the following command on the command terminal, and
click Execute to query the STCP status. ASSOCID is the association ID.
SHOW SCTPSTAT:ASSOCID=1;
4. If the association is disconnected, check whether the IP address configuration of the port is correct.
END OF STEPS

Debugging the M3UA


Context

If the SCTP is normal, debug the M3UA.


The physical status of the ASP is decided by the association status. After the association can be used, the ASPs at the both ends
perform handshaking of the service status maintenance message
ASPTM. If the handshaking is successful, the service can be used.

Steps

1. On the NetNumen M30 window, select menus Views > MML


Terminal to enter the MML Terminal window.
2. If no exchange is specified, execute command SET on the MML
Terminal window or select a NE from the system tree to specify the MSCS exchange to be configured.
3. Enter the following command on the MML Terminal window,
and click Execute to query the ASP status. ASID is the AS ID,
and ASPID is the ASP ID.
SHOW ASPSTAT:ASID=1,ASPID=1;
4. When the ASP status in normal, ASP Status=ASP_ACTIVE should be
displayed.

Confidential and Proprietary Information of ZTE CORPORATION

357

ZXWN MSCS Data Configuration Guide(MSCS)

5. Enter the following command on the MML Terminal window,


and click Execute to query the AS status. ASID is the AS ID.
SHOW ASSTAT:ASID=1;
6. When the AS status in normal, AS Status=AS_ACTIVE should be
displayed.
END OF STEPS

Confirming the Working Status of the


MGW
Context

After the office direction to the MGW is debugged successfully, the


status of the MGW is not guaranteed to be normal. This section introduces the method of confirming the working status of the MGW.
After the data for connection between the ZXWN MSCS and the
MGW are configured and the equipment is started, the MGW will
actively register the gateway information to the MSC Server. This
topic describes the method of confirming the working status of the
MGW.

Steps

1. On the NetNumen M30 window, select menus Views > MML


Terminal to enter the MML Terminal window.
2. If no exchange is specified, execute command SET on the MML
Terminal window or select a NE from the system tree to specify the MSCS exchange to be configured.
3. Enter the following command on the MML Terminal window,
and click Execute to query the registration status of the gateway.
SHOW MGWSTAT;
4. When the working status of the gateway is exceptional, check
whether the corresponding parameters in the H248 configuration and the SIGTRAN configuration on the MSC Server and the
MGW are consistent and meet the requirements.
END OF STEPS

H.248/SCTP Problem Location


Method
For two NEs adopting SIGTRAN networking, to judge whether the
bottom-layer link is reliable, it is necessary to confirm whether
two connections are normal. One is the connection between two
SIG_IPIs, and the other is the control channel between the SIG_IPI
and the SMP.

358

Debugging the IP protocol stack

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 9 Configuration Instance

Debugging the connection between two SIG_IPIs means debugging the IP protocol stack. When the physical connection is
normal, connect one computer to HUB or to SIGIPI through the
crossover network cable. Ping the IP addresses of the SIPI interface and the loop-back interface of the local end, and those
of the opposite end. When the IP protocol stack is correctly
configured, these IP addresses should be pinged successfully.
If they cannot be pinged successfully, confirm whether the IP
protocol stack is correctly configured.

Debugging the basic SCTP connection information


After the protocol stack is normal, it is necessary to check data
in the SCTP configuration , including whether the protocol type,
the server and the client are normal; whether the office ID, IP
address, and port number are correct; and whether the port
number is repeated.

M3UA Problem Location Method


When the status of the lower-layer association is normal, and
the status of the AS/ASP is abnormal, it is necessary to confirm
whether AS data, ASP data, and SIO-locating-AS data are correctly configured, and whether the interconnecting parameters
between the local office and the opposite-end office are consistent.

MSCS-HLR Interconnection
Debugging Procedure
The MSCS is connected with the HLR through the TDM mode. After
data of the HLR are configured on the MSC Server, the common
procedures for data debugging are as follows:
Steps

Operations

Description

Reference

Check the HLR office


status

Check whether
the HLR office is
accessible

Checking the HLR


Office Status

Check the physical


connection

When the office is


inaccessible, first
confirm whether
there is any
hardware problem

Checking
the
Physical Connection

Debugging the
narrow-band
signaling link

After the hardware


problem is
removed, confirm
whether there is
any problem in
the narrowband
signaling link

Debugging
the
Narrow-Band Signaling Link

Confidential and Proprietary Information of ZTE CORPORATION

359

ZXWN MSCS Data Configuration Guide(MSCS)

Checking the HLR Office Status


Context

Checking whether the office is accessible is the first step for debugging. This section introduces the detailed procedures for checking
whether the HLR office is accessible.

Steps

1. On the NetNumen M30 window, select menus Views > MML


Terminal to enter the MML Terminal window.
2. If no exchange is specified, execute command SET on the MML
Terminal window or select a NE from the system tree to specify the MSCS exchange to be configured.
3. Enter the following command on the MML Terminalwindow,
and click Execute to query the status of the adjacent HLR office. OFC is the adjacent HLR office ID.
SHOW OFCSTAT:OFC=1;
4. If the office is inaccessible, skip to Checking the Physical Connection.
END OF STEPS

Checking the Physical Connection


Context

If it is found that the adjacent HLR office is inaccessible on the


NetNumen M30 window, confirm whether the physical connection between the MSCS and the HLR is normal.

Note:
During the debugging, to ensure that there is no problem in the E1
hardware connection, exchange the receiving cable and the sending cable of the E1.
Steps

1. Observe the status of the corresponding E1 indicator on the


SPB board.
2. If the E1 indicator flashes quickly (at 5Hz), it indicates that
the physical E1 line is clear, and that at least one of the E1
signaling links configured on the E1 line is in the In Service
status.
3. If the E1 indicator flashes slowly (at 1Hz), it indicates that the
physical E1 line is clear, and that none of the E1 signaling links
configured on the E1 line is in the In Service status.
4. If the E1 indicator is always on, it indicates that the corresponding subunit of the E1 line has existed in the physical configuration, but the physical E1 line is obstructed.

360

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 9 Configuration Instance

5. If the E1 indicator is off, it indicates that the corresponding


subunit of the E1 line does not exist in the physical configuration (that is, the data are not configured).
END OF STEPS

Debugging the Narrow-Band


Signaling Link
Context

If the physical connection is normal, debug the narrow-band signaling link .


TABLE 132 LINK STATUS DESCRIPTION
Link Statuses

Descriptions

Out of service

The local-end MTP3 does not initiate the link


establishment request, and the link is unavailable.
Maybe the MTP3 doest not receive the configuration
information of this link, or the fault in the
communication between the SMP and the SPB causes
the SPB unable to receive the link establishment
request

Initial
alignment

The link establishment request has been received


from the local-end MTP3 , the link is being
established, and the link is unavailable. If the link
status alternates between Initial alignment and
Out of service, maybe there is a fault in the physical
layer or the opposite-end MTP3 does not initiate link
establishment

Alignment
ready

The link establishment request has been received


from the local-end MTP3 , the verification phase
of the link establishment has been successfully
completed, the physical layer is OK, the opposite end
is performing verification, and the link is unavailable.
Please wait

In service

Both parties have successfully established the link,


and the link is available

Processor
outage

There is a fault in the SMP of the local end or the


opposite end, and the link is unavailable. Check
whether the SMP is suspended

Confidential and Proprietary Information of ZTE CORPORATION

361

ZXWN MSCS Data Configuration Guide(MSCS)

TABLE 133 COMMON REASONS FOR LINK BROKEN AND THE


SOLUTIONS
Number

Reasons for
Link Broken

Common Reasons for Link Broken and


the Solutions
Check whether the network types, signaling
point code types, signaling point codes and
sub-service fields are correctly configured
in the office attributes at the both ends.

L3 stop

Observe whether the MTP3 management


message interaction SLTM/SLTA of the both
ends is normal through the signaling tracing
.
Check whether the Self loop button in the
dynamic management is clicked under the
normal connection.
Check whether the local exchange data are
configured in the local exchange

Abnormal
BSNR

Check whether there are bit errors in the


physical layer;
The opposite-end MTP2 protocol is
implemented by error
Check whether there are bit errors in the
physical layer;

Abnormal FIBR

T2 timeout

The narrow link at the opposite end is not


activated

Receive SIOS
when aligned

The narrow link of the opposite end is


deactivated

The opposite-end MTP2 protocol is


implemented by error
The physical layer is obstructed;

T3 timeout

The physical layer is clear in one direction


(the opposite-end-to-local-end direction is
clear, while the local-end-to-opposite-end
direction is obstructed, and check the
connection line;
Check whether there are bit errors in the
physical layer

Receive SIOS
when proving

Abort proving

The narrow link of the opposite end is


deactivated;
Check whether there are bit errors in the
physical layer at the opposite end
Check whether there are bit errors in the
physical layer
Check whether the physical link is suddenly
disconnected;

T9 timeout

The opposite end is suspended;


Check whether there are bit errors in the
physical layer

362

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 9 Configuration Instance

Number

Reasons for
Link Broken

Common Reasons for Link Broken and


the Solutions

10

Too many error


SUs

Check whether there are bit errors in the


physical layer

11

Receive SIO

The opposite-end MTP2 protocol is


implemented by error

12

Receive SIOS

The narrow link of the opposite end is


deactivated

13

T1 timeout

The opposite-end MTP2 protocol is


implemented by error

14

T7 timeout

Check whether there are bit errors in the


physical layer

15

T6 timeout

The duration of congestion in the opposite


end is too long

16

Steps

Receive SIN

Check whether there are bit errors in the


physical layer;
The opposite-end MTP2 protocol is
implemented by error
Check whether there are bit errors in the
physical layer;

17

Receive SIE

18

TX buffer not
enough

19

Too many error


SUs in an
interval

The opposite end is suspended

20

Link deleted or
changed

The network management deletes or


modifies the narrow-band link attributes

21

Link timer not


available

OSS error in the local end

The opposite-end MTP2 protocol is


implemented by error
Check whether the CPU occupancy of the
SPB is too high, whether ERL is too big, and
whether the traffic on the upper layer of the
local end is too heavy
Check whether there are bit errors in the
physical layer;

1. Telnet to the SPB board, and type lsta to check the status of
the signaling link . The system will display the statuses of all
the signaling links on the SPB board, as shown in Figure 66.
The descriptions of the signaling link status are shown in Table
132.

Confidential and Proprietary Information of ZTE CORPORATION

363

ZXWN MSCS Data Configuration Guide(MSCS)

FIGURE 66 QUERYING THE STATUS OF THE NARROW-BAND


SIGNALING LINK

2. When the displayed link status is not In Service, check the reason for link broken. Type lwhy on the window, and the reason
for history link broken will be displayed, as shown in Figure
67. The common reasons for link broken and the solutions are
shown in Table 133.
FIGURE 67 CHECKING THE REASON FOR LINK BROKEN

3. The tracing management or dynamic management tool of the


network management system can be used when the signaling
link is being debugged.
END OF STEPS

364

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 9 Configuration Instance

Signaling Link Problem Location


Method
When it is confirmed that there is no problem in the hardware connection, first judge whether the signaling link blocking is caused
by errors in the local-office data configuration or the opposite-end
office data configuration. The method is as follows:
1. Self loop the corresponding E1 cable of the signaling link (There
are software self-loop and hardware self-loop. After the software self-loop debugging is completed, be sure to open the
software self-loop)
2. If the E1 indicator flashes quickly, it can be confirmed that there
is no problem in the local-end data configuration. At this time,
it is necessary to cooperate with the opposite end to check
whether the interconnection data configuration is consistent.
3. If the E1 indicator cannot flash quickly after the E1 is self
looped, it is necessary to check the local-end data configuration . For the checking method, please refer to Debugging
the Narrow-Band Signaling Link.

MSCS-RNC Interconnection
Debugging Procedure
When the MSCS is connected with the RNC in a quasi-associated
mode, after data of the RNC are configured on the MSC Server, the
common procedures for data debugging are as follow. The debugging procedure is similar with that of Mc interface (i.e. MSCS-MGW
interconnection debugging).
Steps

Operations

Description

Reference

Check the
RNC office
status

Check whether
the RNC office is
accessible

Checking the RNC


Office Status

Check the
physical
connection

When the office is


inaccessible, first
confirm whether
there is any hardware
problem

Checking the Physical


Connection

Debug the
SCTP

After the hardware


problem is removed,
confirm whether
there is any
problem in the SCTP
association

Debugging the SCTP

Confidential and Proprietary Information of ZTE CORPORATION

365

ZXWN MSCS Data Configuration Guide(MSCS)

Steps

Operations

Description

Reference

Debug the
M3UA

After the problem in


the SCTP association
is removed, confirm
whether there is
any problem in
upper-layer M3UA
signaling link

Debugging the M3UA

Check the
MGW working
status

After the problem


on the M3UA layer
is removed, check
the H.248 gateway
configuration

Confirming the
Working Status of
the MGW

Checking the RNC Office Status


Context

Checking whether the office is accessible is the first step for debugging. This section introduces the detailed procedures for checking
whether the RNC office is accessible.

Steps

1. On the NetNumen M30 window, select menus Views > MML


Terminal to enter the MML Terminal window.
2. If no exchange is specified, execute command SET on the MML
Terminal window or select a NE from the system tree to specify the MSCS exchange to be configured.
3. Enter the following command on the MML Terminal window,
and click Execute to query the status of the adjacent RNC
office. OFC is the adjacent MGW office ID.
SHOW OFCSTAT:OFC=2;
4. If the office is inaccessible, skip to Checking the Physical Connection.
END OF STEPS

Basic Service Debugging


Procedure
Basic service debugging includes location update service debugging and local-office call service debugging.

366

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 9 Configuration Instance

Debugging the Location Update


Service
Prerequisites

1. The interconnection between the MSCS and the local HLR is


completed.
The MSCS is associated with the local HLR. The HLR office
should be accessible, and the status of the subsystem is normal. The GT-related configuration on the MSCS side is completed, and the GT configuration of the MSC/VLR on the local
HLR is completed too.
2. The interconnection between the MSCS and the RNC is completed.
The signaling between the MSCS and the BSC/RNC is accessible. The LAI and cell data configuration are completed.
3. The test card and test mobile phone are prepared.
The test number is allocated in the HLR, and basic services are
enabled.

Context
Steps

This section introduces the basic debugging steps by taking the


example of the location update of a local subscriber.
1. Open the signaling tracing and failure observation tools.

Open the BSSAP/RANAP signaling tracing of the SCCP.

Open the MM and VLRMAP signaling tracing.

Open the SCCP signaling tracing of the MTP3 signaling tracing to the HLR office.
Open the SCCP signaling tracing of the MTP3 signaling tracing to the BSC/RNC office.
Trace the failure observation of the MM, VLRMAP, and SCCP
modules.

2. Power on the mobile phone, log onto the network, and perform
location update debugging.
END OF STEPS

Debugging the Local-Office Call


Prerequisites

1. The location update of the mobile phone is successful.


The location update of the mobile phone is successfully debugged, and the subscriber information can be successfully
queried in the VLR.
2. The MGW is successfully registered.
Enter the following command on the MML Terminal window
of NetNumen (TM) 30 of the MSCS to query the MGW status.
SHOW MGWSTA;

Confidential and Proprietary Information of ZTE CORPORATION

367

ZXWN MSCS Data Configuration Guide(MSCS)

3. The status of the physical resources on the MGW is normal.


On the NetNumen (TM) 30 window of the MGW, select menus
Views > Daily Maintenanceto enter the Daily Maintenance
window. From the navigation tree, click Dynamic Management > Physical Resourceto check the statuses of the subunits of the DTB, MRB, VTCD, and other boards. In another
way, telnet to the VTCD, and MRB boards to check through
command SCSShowDSPStatus.
The method of checking the status of the level-2 forwarding
table is as follows: On the IPI, GIPI, VTCD, and APBE boards,
execute the debugging command brdl2. On the UIM board,
execute the debugging command uiml2. When the PortIdx
in the result is 255, the port is invalid. Command SCSShowL2
can be used to query the status of the corresponding port.
When EffectPort is 0, the port is invalid.
4. On the MGW, it is found that the Iu bearer is successfully established by checking the foreground R_ATMPVC and R_AAL2PATH
tables.
Context
Steps

This section introduces the basic debugging procedure by taking


an intra-office call as example.
1. Open the signaling tracing and failure observation tools.
i. Open the MM, VLRMAP, and MSCMAP signaling tracing.
ii. Open the SCCP signaling tracing of the MTP3 signaling tracing to the HLR office.
iii. Open the SCCP signaling tracing of the MTP3 signaling tracing to the BSC/RNC office.
iv. Trace the failure observation of the MM, VLRMAP, MSCMAP,
MCC, and SCCP modules.
2. Perform the local-office call dialing test, and perform debugging according to signaling and call loss.
END OF STEPS

368

Confidential and Proprietary Information of ZTE CORPORATION

Figure

Figure 1 OVERALL FLOW OF THE MSCS DATA CONFIGURATION .. 2


Figure 2 START PROCESS OF THE OMM SERVER ..................... 4
Figure 3 START INFORMATION OF THE OMM SERVER............... 4
Figure 4 LOGIN Window ...................................................... 5
Figure 5 NetNumn M30 MSCS/MGW OMM SYSTEM Window ...... 6
Figure 6 CONFIGURATION & MANAGEMENT MAIN Window........ 7
Figure 7 MML TERMINAL Window .......................................... 7
Figure 8 COMMAND EXECUTION OPERATIONS ........................ 8
Figure 9 SINGLE BCTC SHELF WITH FULL CONFIGURATION.....20
Figure 10 SIGNALING SERVICE IP CONFIGURATION ...............25
Figure 11 ADJACENT OFFICE ID ALLOCATION ........................26
Figure 12 THE HOME OFFICE DATA CONFIGURATION FLOW .....30
Figure 13 PHYSICAL CONFIGURATION FLOW .........................35
Figure 14 FLOW OF LOADING VERSION FILES .......................59
Figure 15 VERSION LOADING..............................................61
Figure 16 CONFIGURING VERSION PATH ..............................61
Figure 17 VERSION FILE PATH.............................................62
Figure 18 Load Version .......................................................63
Figure 19 CREATING OMP BOOT FILES .................................64
Figure 20 CONNECTION DESCRIPTION .................................65
Figure 21 CONNECT TO DIALOG BOX ...................................65
Figure 22 COM1 PROPERTIES ..............................................66
Figure 23 PRESS ANY KEY TO STOP AUTO-BOOT ....................66
Figure 24 BOOT PASSWORD................................................67
Figure 25 3GPLAT BOOT .....................................................67
Figure 26 CONFIG SELECTION.............................................68
Figure 27 ENTER OMPS OMC IP ADDRESS ............................68
Figure 28 ENTER OMPS OMM MAC ADDRESS ........................69
Figure 29 ENTER OMPS GATEWAY IP ADDRESS .....................69
Figure 30 OMC SERVER IP ADDRESS ....................................70
Figure 31 CONFIG SELECTION.............................................70
Figure 32 OMM IP ADDRESS ...............................................71
Figure 33 FTP CONFIG........................................................71
Figure 34 OMPCFG FILE......................................................72

Confidential and Proprietary Information of ZTE CORPORATION

369

ZXWN MSCS Data Configuration Guide(MSCS)

Figure 35 CONFIG SELECTION.............................................72


Figure 36 OMP BOOT TYPE ..................................................73
Figure 37 CONFIG SELECTION.............................................73
Figure 38 BUREAU NO. .......................................................74
Figure 39 CONFIG SELECTION.............................................74
Figure 40 3GPLAT BOOT .....................................................75
Figure 41 USER NAME AND PASSWORD ................................78
Figure 42 STATUS..............................................................79
Figure 43 VERSION LOADING..............................................80
Figure 44 BATCH VERSION LOADING BY DEFAULT ..................81
Figure 45 AREA TREE ....................................................... 118
Figure 46 ADDING RESOURCES ......................................... 118
Figure 47 RESOURCE ADDING DIALOG BOX ........................ 119
Figure 48 FLOW OF MSCS-MGW INTERCONNECTION
CONFIGURATION ............................................. 122
Figure 49 SIGTRAN CONFIGURATION FLOW ........................ 146
Figure 50 CONFIGURATION FLOW ...................................... 159
Figure 51 FLOW OF CONFIGURING A DIRECT-ASSOCIATED
OFFICE IN IP DOMAIN ...................................... 171
Figure 52 QUASI-ASSOCIATED NETWORKING BETWEEN
MSCS AND 2G MSC/PSTN (BASED ON M3UA) ...... 180
Figure 53 FLOW OF M3UA TRANSIT EXCHANGE ................... 181
Figure 54 QUASI-ASSOCIATED NETWORKING BETWEEN
MSCS AND 2G MSC/PSTN (BASED ON M2UA) ...... 182
Figure 55 FLOW OF M2UA TRANSIT EXCHANGE ................... 183
Figure 56 TDM OFFICE INTERCONNECTION CONFIGURATION
FLOW............................................................. 187
Figure 57 QUASI-ASSOCIATION BETWEEN MGW AND RNC .... 198
Figure 58 DIRECT-ASSOCIATION BETWEEN MGW AND RNC... 198
Figure 59 FLOW OF CONFIGURING MSCS-RNC
INTERCONNECTION ......................................... 199
Figure 60 QUASI-ASSOCIATED NETWORKING BETWEEN
MSCS AND BSC ............................................... 214
Figure 61 DIRECT-ASSOCIATED NETWORKING BETWEEN
MSCS AND BSC ............................................... 214
Figure 62 FLOW OF CONFIGURING MSCS-BSC
INTERCONNECTION ......................................... 215
Figure 63 ANALYSIS ORDER OF NUMBER ANALYZERS ........... 266
Figure 64 NETWORKING DIAGRAM..................................... 338
Figure 65 BOARD LAYOUT OF THE BCTC SHELF ................... 341

370

Confidential and Proprietary Information of ZTE CORPORATION

Figures

Figure 66 QUERYING THE STATUS OF THE NARROW-BAND


SIGNALING LINK ............................................. 364
Figure 67 CHECKING THE REASON FOR LINK BROKEN.......... 364

Confidential and Proprietary Information of ZTE CORPORATION

371

ZXWN MSCS Data Configuration Guide(MSCS)

This page is intentionally blank.

372

Confidential and Proprietary Information of ZTE CORPORATION

Table

Table 1 LOGIN PARAMETER DESCRIPTION.............................. 5


Table 2 PARAMETERS IN THE SYNA COMMANDS..................... 9
Table 3 PARAMETERS IN THE SYN COMMANDS......................10
Table 4 OFFICE NUMBER ALLOCATION PRINCIPLE ..................13
Table 5 IP ADDRESS ALLOCATION PRINCIPLE OF THE
INTERNAL NETWORK OF THE NMS .......................13
Table 6 IP ADDRESS ALLOCATION PRINCIPLE OF THE
EXTERNAL NETWORK OF THE NMS.......................15
Table 7 IP ADDRESS ALLOCATION PRINCIPLE OF THE
EXTERNAL NETWORK OF THE NMS.......................16
Table 8 IP ADDRESS ALLOCATION PRINCIPLE OF THE
INTERNAL NETWORK OF THE IP MANAGEMENT
SYSTEM ...........................................................17
Table 9 AN INSTANCE OF MC INTERFACE IP ADDRESSES ........25
Table 10 PARAMETERS IN THE ADD NE COMMAND ................32
Table 11 PARAMETERS IN THE SET PCINFO COMMAND .........34
Table 12 PARAMETERS IN THE ADD RACK COMMAND ............36
Table 13 PARAMETERS IN ADD SHELF COMMAND .................38
Table 14 PARAMETERS IN THE ADD UNIT COMMAND.............39
Table 15 PARAMETERS IN ADD MODULE COMMAND ..............41
Table 16 MSCS BOARD TYPES .............................................43
Table 17 PARAMETERS IN THE ADD UNIT COMMAND.............44
Table 18 PARAMETERS IN THE ADD UNIT COMMAND.............47
Table 19 PARAMETERS IN THE ADD UNIT COMMAND.............48
Table 20 PARAMETERS IN THE ADD UNIT COMMAND.............50
Table 21 PARAMETERS IN THE ADD SVRINF COMMAND.........51
Table 22 CAPACITY AND LOAD-SHARING CONFIGURATION......52
Table 23 PARAMETERS IN THE SET MSCSCAPACITY
COMMAND ........................................................53
Table 24 PARAMETERS IN THE SET DATASIZE COMMAND ......55
Table 25 PARAMETERS IN THE ADD IMSILOAD COMMAND ....57
Table 26 VERSION DESCRIPTION OF OMP BOOT FILE .............63
Table 27 PARAMETERS IN THE SET OMP COMMAND ..............76
Table 28 PARAMETERS IN SYNA COMMAND ..........................77

Confidential and Proprietary Information of ZTE CORPORATION

373

ZXWN MSCS Data Configuration Guide(MSCS)

Table 29 Board Version Files................................................79


Table 30 BOARD INDICATOR STATUSES ................................81
Table 31 PARAMETERS IN THE BADD STONE COMMAND ........83
Table 32 Office Information Configuration .............................84
Table 33 PARAMETERS IN THE ADD OPC COMMAND ..............85
Table 34 PARAMETERS IN THE ADD LOFC COMMAND ............88
Table 35 PARAMETERS IN THE ADD MSCCFG COMMAND ........90
Table 36 PARAMETERS IN THE ADD CC COMMAND ................96
Table 37 PARAMETERS IN THE ADD MNC COMMAND..............97
Table 38 VLR CONFIGURATION FLOW ...................................97
Table 39 PARAMETERS IN THE ADD VLRSYS COMMAND.........98
Table 40 PARAMETERS IN THE ADD VLRCAP COMMAND ...... 101
Table 41 PARAMETERS IN THE ADD VLRSRV COMMAND ...... 104
Table 42 PARAMETERS IN THE ADD MRNSH COMMAND ....... 109
Table 43 VIRTUAL MSC CONFIGURATION ............................ 110
Table 44 PARAMETERS IN THE ADD VMSC COMMAND .......... 111
Table 45 PARAMETERS IN THE ADD REGIONMAP
COMMAND ...................................................... 112
Table 46 RESOURCE TYPES, KEY FIELDS AND VALUE RANGES
OF THE MGCF.................................................. 116
Table 47 FLOW DESCRIPTION............................................ 122
Table 48 PARAMETERS IN THE ADD IP ADDRESS
COMMAND ...................................................... 124
Table 49 INTERFACE REAL INTERFACE .............................. 125
Table 50 ADD IP ADDRESS REAL INTERFACE..................... 126
Table 51 PARAMETERS IN THE ADD BFD AUTH COMMAND ... 127
Table 52 PARAMETERS IN THE ADD BFD SESSION
COMMAND ...................................................... 128
Table 53 PARAMETERS IN THE ADD IP ROUTE COMMAND.... 130
Table 54 PARAMETERS IN THE ADD ADJOFC COMMAND ...... 132
Table 55 PARAMETERS IN THE ADD CODECTPL COMMAND .. 137
Table 56 PARAMETERS IN THE ADD TOPO COMMAND .......... 139
Table 57 PARAMETERS IN THE ADD MGWBEARMOD
COMMAND ...................................................... 143
Table 58 PARAMETERS IN THE ADD SCTPCONN COMMAND .. 148
Table 59 PARAMETERS IN THE ADD ASP COMMAND ............ 151
Table 60 PARAMETERS IN THE ADD AS COMMAND .............. 152
Table 61 PARAMETERS IN THE ADD M3UART COMMAND...... 155
Table 62 PARAMETERS IN THE ADD SIOLOCAS COMMAND... 157
Table 63 PARAMETERS IN THE ADD MGCSCFG COMMAND.... 160

374

Confidential and Proprietary Information of ZTE CORPORATION

Tables

Table 64 PARAMETERS IN THE ADD MGSTPL COMMAND ...... 162


Table 65 PARAMETERS IN THE ADD MGSCFG COMMAND...... 163
Table 66 PARAMETERS IN THE ADD TIDANL COMMAND....... 165
Table 67 PARAMETERS IN THE ADD TIDENTR COMMAND..... 167
Table 68 BEARER MODES OF MAIN INTERFACES .................. 169
Table 69 ADJACENT OFFICE ATTRIBUTES ............................ 176
Table 70 PARAMETERS IN THE ADD TOPO COMMAND .......... 178
Table 71 PARAMETERS IN THE ADD M2UAIPLNK
COMMAND ...................................................... 185
Table 72 PARAMETERS IN THE ADD N7LKS COMMAND ........ 189
Table 73 PARAMETERS IN THE ADD N7LNKE1 COMMAND .... 191
Table 74 PARAMETERS IN THE ADD N7ROUTE COMMAND.... 193
Table 75 ARRANGEMENT MODE OF SIGNALING SETS............ 194
Table 76 PARAMETERS IN THE ADD N7OFC COMMAND ........ 196
Table 77 PARAMETERS IN THE ADD ADJOFC COMMAND ...... 201
Table 78 PARAMETERS IN THE ADD RNCOFC COMMAND ...... 205
Table 79 PARAMETERS IN THE ADD TOPO COMMAND .......... 208
Table 80 PARAMETERS IN THE ADD RNCMGWTOPO
COMMAND ...................................................... 212
Table 81 PARAMETERS IN THE ADD ADJOFC COMMAND ...... 217
Table 82 PARAMETERS IN THE ADD BSCOFC COMMAND ...... 221
Table 83 PARAMETERS IN THE ADD TOPO COMMAND .......... 223
Table 84 MAIN PARAMETERS IN THE ADD RNCMGWTOPO
COMMAND ...................................................... 226
Table 85 PARAMETERS IN THE ADD ECC COMMAND............. 231
Table 86 PARAMETERS IN THE ADD SSPN COMMAND .......... 232
Table 87 PARAMETERS IN THE ADD TPDNAL COMMAND ...... 236
Table 88 PARAMETERS IN THE ADD LAI COMMAND ............. 237
Table 89 PARAMETERS IN THE ADD LAI COMMAND ............. 242
Table 90 PARAMETERS IN THE ADD GCI COMMAND............. 246
Table 91 PARAMETERS IN THE ADD SAI COMMAND ............. 248
Table 92 PARAMETERS IN THE ADD GTT COMMAND ............ 251
Table 93 PARAMETERS IN THE ADD GT COMMAND .............. 255
Table 94 SSN .................................................................. 258
Table 95 PARAMETERS IN THE ADD IMSIANA COMMAND .... 262
Table 96 PARAMETERS IN THE ADD NDCMNC COMMAND ..... 264
Table 97 PARAMETERS IN THE ADD NCCFG COMMAND ........ 265
Table 98 DAS FOR PRE-ANALYZING THE CALLED NUMBER ..... 267
Table 99 ORIGINATING DAS .............................................. 267
Table 100 FORWARDING DAS ............................................ 269

Confidential and Proprietary Information of ZTE CORPORATION

375

ZXWN MSCS Data Configuration Guide(MSCS)

Table 101 ROAMING DAS.................................................. 270


Table 102 PARAMETERS IN THE ADD ENTR COMMAND ........ 271
Table 103 ANALYZER ENTRY TYPES .................................... 272
Table 104 COMMON DASS................................................. 273
Table 105 PARAMETERS IN THE ADD DAS COMMAND .......... 274
Table 106 PARAMETERS IN THE SET LDASTMPLT
COMMAND ...................................................... 276
Table 107 PARAMETERS IN THE ADD ACRTMPLT
COMMAND ...................................................... 279
Table 108 PARAMETERS IN THE ADD TPDNAL COMMAND .... 283
Table 109 CALL SERVICE TYPES......................................... 297
Table 110 ENABLED OPTIONS............................................ 303
Table 111 PARAMETERS IN THE ADD TG DT COMMAND........ 309
Table 112 PARAMETERS IN THE ADD TG ATM COMMAND ..... 315
Table 113 PARAMETERS IN THE ADD TG RTP COMMAND...... 322
Table 114 PARAMETERS IN THE ADD SPCM COMMAND ........ 326
Table 115 PARAMETERS IN THE ADD INPCM COMMAND ...... 328
Table 116 PARAMETERS IN THE ADD RT COMMAND............. 330
Table 117 PARAMETERS IN THE ADD RTS COMMAND........... 332
Table 118 PARAMETERS IN THE ADD CHAIN COMMAND ...... 333
Table 119 NEGOTIATION DATA INSTANCE ........................... 338
Table 120 SIGTRAN IP ADDRESS INSTANCE OF THE MC
INTERFACE ..................................................... 340
Table 121 DATA PLANNING OF THE LOCAL EXCHANGE
CONFIGURATION ............................................. 340
Table 122 DATA PLANNING OF THE PHYSICAL
CONFIGURATION ............................................. 341
Table 123 DATA PLANNING OF THE CAPACITY AND LOAD
SHARING CONFIGURATION ............................... 342
Table 124 DATA PLANNING OF THE OFFICE DATA
CONFIGURATION ............................................. 343
Table 125 DATA PLANNING OF THE VLR CONFIGURATION ..... 344
Table 126 RESOURCE PLANNING INSTANCE ........................ 346
Table 127 PARAMETERS IN THE ADJACENT MGW OFFICE
INTERCONNECTION DATA CONFIGURATION ........ 347
Table 128 PARAMETERS IN THE ADJACENT HLR OFFICE
INTERCONNECTION DATA CONFIGURATION ........ 349
Table 129 PARAMETERS IN THE ADJACENT RNC OFFICE
INTERCONNECTION DATA CONFIGURATION ........ 351

376

Confidential and Proprietary Information of ZTE CORPORATION

Tables

Table 130 PARAMETERS IN THE LOCATION UPDATE DATA


CONFIGURATION ............................................. 352
Table 131 PARAMETERS IN THE CALL DATA CONFIGURATION .. 354
Table 132 LINK STATUS DESCRIPTION ............................... 361
Table 133 COMMON REASONS FOR LINK BROKEN AND THE
SOLUTIONS .................................................... 362

Confidential and Proprietary Information of ZTE CORPORATION

377

ZXWN MSCS Data Configuration Guide(MSCS)

This page is intentionally blank.

378

Confidential and Proprietary Information of ZTE CORPORATION

Index
A

Active/standby mode ......... 47


Active/standby
networking.................... 122
Address planning............. 122
Adjacent office ......... 123, 172
Association ..................... 173

Inter-office ....................... 47
Interconnection ................. 23
Interconnection
data ......................... 3, 121
Internal network ............... 12
Interworking ................... 172
IP address ...................... 359
IP protocol stack ............. 359

B
Background ........................1
BFD configuration ............ 122
Billing system ................... 12
BOSS............................... 12
Broadband...................... 175

C
Cable connection .................1
Commissioning.................. 47
crossover network
cable ............................ 357
Crossover network
cable ............................ 359

L
LAN ...................................1
link......................... 361364
Link ............................... 358
Load-sharing .................. 122
Load-sharing mode ............ 46
local office ...................... 359
Loop-back interface ......... 359

M
M3UA............................. 357
MML Terminal......................3
MTP2 ............................. 362
MTP3 ...................... 361362

Data configuration ....... 3, 365


Data Synchronization ...........3
Destination signaling
point ............................ 249
Dual-server ...................... 14

OMM Client .........................3


OMM server ........................1

Network section .............. 123

External network ............... 12

F
Floating IP ........................ 14

physical configuration ....................... 360361


Physical configuration ........ 34
Protocol stack ................. 121

GT routing ...................... 249


GT translation data .......... 250
GT translation selector ..... 249

H248 configuration .......... 123


Hardware installation ...........1

Rack ..................................1
Radio office ...................... 23

Quasi-associated ............. 182

Confidential and Proprietary Information of ZTE CORPORATION

379

ZXWN MSCS Data Configuration Guide(MSCS)

Roaming number ............. 108


Roaming number prefix .... 108

S
SCCP ............................. 249
SCTP configuration .......... 359
Shelf..................................1
signaling link .... 361, 363365
signaling point ................ 362
Signaling point .................. 22
Signaling point code ........ 177
Signaling Point Code .......... 22
Signaling Route ............... 184
signaling tracing .............. 362
SIGTRAN ........................ 358
SIGTRAN configuration ..... 123
Source signaling point ...... 249

T
Tandem office ................. 176
Topological node.............. 123

V
VLR ............................... 108

380

Confidential and Proprietary Information of ZTE CORPORATION