sj-20100211152857-010-zxwn mscs (v3.09.21) msc server common configuration operation guide

ZXWN MSCSMSC Server

Common Configura-tion Operation Guide

Version 3.09.21

ZTE CORPORATIONNO. 55, Hi-tech Road South, ShenZhen, P.R.ChinaPostcode: 518057Tel: (86) 755 26771900Fax: (86) 755 26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATION

Copyright © 2010 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution ofthis document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPO-RATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATIONor of their respective owners.

This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions are dis-claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-fringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on theinformation contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subjectmatter 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-010

Contents

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

Declaration of RoHS Compliance ....................... I

Data Making for New Commissioning ................1Overview....................................................................... 1

MGW Data Configuration ................................................. 1

Overview................................................................... 1

Interface Address Configuration.................................... 3

Overview .......................................................... 3

Creating a Loopback Interface ............................. 4

Creating an SIPI Interface Address....................... 5

Creating a Static Route ............................................... 7

Adjacent Office and Topology Configuration.................... 8

Overview .......................................................... 8

Creating an MGW Adjacent Office ......................... 9

Creating an MGW Voice CODEC Template .............14

Creating a Topology Node...................................15

Creating an Inter-MGW Bearer Mode ...................19

SIGTRAN Configuration ..............................................22

Overview .........................................................22

Creating an SCTP..............................................24

Creating an ASP................................................27

Creating an AS .................................................28

Creating an M3UA Static Route ...........................32

Creating the SIO-Locating-AS .............................33

H.248 Configuration...................................................35

Overview .........................................................35

Creating MGC Static Data...................................37

Creating an MGW Static Data Template ................38

Creating MGW Static Data ..................................40

Creating a TID Analyzer .....................................41

Creating a TID Analyzer Entry.............................43

Confidential and Proprietary Information of ZTE CORPORATION I

ZXWN MSCS Common Configuration Operation Guide

HLR Data Configuration ..................................................44

Overview..................................................................44

Creating a HLR Adjacent Office....................................47

Signaling Data Configuration .......................................48

Creating a Signaling Link Set ..............................48

Creating an SPB-Accessed Signaling Link .............50

Creating a Signaling Route .................................53

Creating a Signaling Office .................................55

Creating IMSI Analysis ...............................................57

SCCP Data Configuration ............................................59

Creating GT Translation Selector .........................59

Creating GT Translation Data ..............................63

STP Data Configuration ..................................................69

Overview..................................................................69

Creating an STP Adjacent Office ..................................71

Signaling Data Configuration .......................................73

Creating a Signaling Link Set to the STP...............73

Creating a Signaling Link to the STP ....................75

Creating a Signaling Route to the STP..................78

Creating a Signaling Office to the STP..................79

Creating a GT Translation Data ....................................81

SCP Data Configuration (Destination Network)...................85

Overview..................................................................85

Creating a Signaling Subsystem ..................................87

Creating GT Translation Data.......................................89

Creating the CAMEL Configuration................................93

Recharge and Query Configuration...............................94

Creating CAMEL Access Subscription

Information...........................................94

Creating Called Number Analysis.........................97

Configuration Related to Intelligent Tone Play ................99

Creating Interconnection Conversion for Service

Keys................................................... 100

Creating Tone Keys on the MGW Tone Board ......... 102

SMC Data Configuration ............................................... 104

Overview................................................................ 104

Creating GT Translation Data..................................... 106

Modifying VLR-Supported Services ............................. 110

Modifying Mobile Data of Local Office.......................... 111

PSTN/2G MSC (M3UA) Data Configuration....................... 111

II Confidential and Proprietary Information of ZTE CORPORATION

Overview................................................................ 111

Creating 2G MSC/PSTN Adjacent Office....................... 113

Configuration Related to Trunk and Route ................... 115

Creating a DT Trunk Group ............................... 115

Creating a PCM System.................................... 119

Creating an Outgoing Route.............................. 121

Creating an Outgoing Route Set ........................ 122

Creating an Outgoing Route Link ....................... 123

SIGTRAN Configuration ............................................ 126

Creating an SCTP............................................ 126

Creating an ASP.............................................. 129

Creating an AS ............................................... 130

Creating an M3UA Static Route ......................... 133

Creating the SIO-Locating-AS ........................... 134

BSC Data Configuration ................................................ 137

Overview................................................................ 137

Office Direction and Topology Configuration................. 139

Creating a BSC Adjacent Office ......................... 139

Creating BSC Office Direction............................ 143

Creating a BSC Topology Node.......................... 145

Creating the Topology Relationship between BSC

and MGW............................................ 148

Trunk and PCM Configuration .................................... 150

Creating a DT Trunk Group ............................... 150


SIGTRAN Configuration ............................................ 159

Creating an SCTP............................................ 159

Creating an ASP.............................................. 161

Creating an AS ............................................... 163

Creating an M3UA Static Route ......................... 165

Creating the SIO-Locating-AS ........................... 166

RNC Data Configuration................................................ 168

Overview................................................................ 168

Creating an RNC Adjacent Office................................ 170

Office Direction and Topology Configuration................. 174

Creating RNC Office Direction ........................... 174

Creating an RNC Topology Node ........................ 178

Creating the Topology Relationship between RNC

and MGW............................................ 181

Trunk and PCM Configuration .................................... 183

Confidential and Proprietary Information of ZTE CORPORATION III


Creating an ATM Trunk Group ........................... 183


Access Data Configuration.............................193Overview.................................................................... 193

Creating Emergency Call Center .................................... 194

Special Serivce Configuration ........................................ 196

Creating a Special Service Phone Group...................... 196

Creating the Special Service Phone Called Number

Analysis ......................................................... 199

LAI and GCI/Service Area Configuration.......................... 201

Creating a LAI Controlled by the Local Office ............... 201

Creating an Adjacent LAI .......................................... 205

Creating a Global Cell............................................... 209

Creating a Service Area............................................ 211

Number Analysis Data Making.......................213Number Analysis ......................................................... 213

Number Analysis Configuration...................................... 218

Overview................................................................ 218

Creating a Number Analyzer Entry ............................. 218

Creating a DAS ....................................................... 221

Setting the Default DAS Template of the Local

Office............................................................. 223

Creating a DAS Template .......................................... 226

Creating the Called Number Analysis .......................... 230

Tone Configuration........................................257Creating MSCS Tones in Batches.................................... 257

Creating the Fixed Tone Play Data.................................. 258

Creating the Basic Service Tone Play Data....................... 265

Creating the Intelligent Service Tone Play Data................ 274

Figure............................................................283

Table .............................................................285

Index ............................................................289

IV Confidential and Proprietary Information of ZTE CORPORATION

About This Manual

Purpose At first, thank you for choosing ZXWN wireless core network sys-tem of ZTE Corporation!

ZXWN system is the 3G mobile communication system developedbased on the UMTS technology. ZXWN system boasts powerfulservice processing capability in both CS domain and PS domain,providing more abundant service contents. Comparing with theGSM, ZXWN provides telecommunication services in wider range,capable of transmitting sound, data, graphics and other multi-me-dia services. In addition, ZXWN has higher speed and resource uti-lization rate. ZXWN wireless core network system supports both2G and 3G subscriber access, and provides various services re-lated with the 3G core network.

The ZXWN MSCS system is designed for the UMTS system at thecore network control level. It supports the GSM core network,UMTS protocols in the R99/R4/R5 stage and relevant functions atthe same time, and provides the carriers with an overall solutionto the evolution from the GSM core network to the 3GPP R99 andthen to the 3GPP R5.

The ZXWN MSCS system completes the functions of the MobileSwitching Center Server and the Visitor Location Register (VLR)together, and provides the Service Switching Point (SSP) functionsof intelligent calls. The ZXWN MSCS system supports the MGCFfunction, and the coexistence of the MGCF and GMSCS. It also cansmoothly upgrade to the MGCF.

This manual aims to help operators master the methods of com-mon data configuration of ZXWN MSCS.

IntendedAudience

This document is intended for engineers, technical and mainte-nance personnel who have mastered the principles of mobile net-work communications.

Prerequisite Skilland Knowledge

To use this document effectively, users should have a general un-derstanding of wireless telecommunications technology. Familiar-ity with the following is helpful:

� CS network and its network elements

� The basic knowledge, interfaces and protocols, and servicefunctions of ZXWN MSCS

What Is in ThisManual

This manual contains the following chapters:

Chapter Summary

Chapter 1, Data Makingfor New Commissioning

Introduces the procedure and method forcollecting and configuring interconnectiondata so as to add various offices on thesoft-switch equipment that is normallyrunning in the current network

Chapter 2, Access DataConfiguration

Introduces the procedure and method forconfiguring the location area and the celldata on the MSCS



Chapter Summary

Chapter 3, NumberAnalysis Data Making

Introduces the procedure and methodfor configuring the number analysis datawhen the soft-switch equipment runs inthe current network normally

Chapter 4, ToneConfiguration

Introduces the procedure and method forconfiguring the tone resources and toneplay data

FCC ComplianceStatement

This device complies with part 15 of the FCC Rules. Operation issubject to the following two conditions.

1. This device may not cause harmful interference.

2. This device must accept any interference received, includinginterference that may cause undesired operation.

Changes or modifications not expressly approved by the party re-sponsible for compliance could void the user's authority to operatethe 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 andcompany name.

Note: Provides additional information about a certaintopic.

Checkpoint: Indicates that a particular step needs tobe checked before proceeding further.

Tip: Indicates a suggestion or hint to make thingseasier or more productive for the reader.

Mouse operation conventions are listed as follows:

Typeface Meaning

Click Refers to clicking the primary mouse button (usually theleft mouse button) once.

Double-click

Refers to quickly clicking the primary mouse button(usually the left mouse button) twice.

Right-click Refers to clicking the secondary mouse button (usuallythe right mouse button) once.


Declaration of RoHSCompliance

Tominimize the environmental impact and take more responsibilityto the earth we live, this document shall serve as formal declara-tion that ZXWN MSCS manufactured by ZTE CORPORATION are incompliance with the Directive 2002/95/EC of the European Parlia-ment - RoHS (Restriction of Hazardous Substances) with respectto the following substances:

� Lead (Pb)

� Mercury (Hg)

� Cadmium (Cd)

� Hexavalent Chromium (Cr (VI))

� PolyBrominated Biphenyls (PBB’s)

� PolyBrominated Diphenyl Ethers (PBDE’s)

…

The ZXWN MSCS manufactured by ZTE CORPORATION meetthe requirements of EU 2002/95/EC; however, some assembliesare customized to client specifications. Addition of specialized,customer-specified materials or processes which do not meet therequirements of EU 2002/95/EC may negate RoHS compliance of theassembly. To guarantee compliance of the assembly, the need forcompliant product must be communicated to ZTE CORPORATION inwritten form. This declaration is issued based on our current levelof knowledge. Since conditions of use are outside our control, ZTECORPORATION makes no warranties, express or implied, and assumesno liability in connection with the use of this information.



This page is intentionally blank.


C h a p t e r 1

Data Making for NewCommissioning

Table of ContentsOverview........................................................................... 1MGW Data Configuration ..................................................... 1HLR Data Configuration ......................................................44STP Data Configuration ......................................................69SCP Data Configuration (Destination Network).......................85SMC Data Configuration ................................................... 104PSTN/2G MSC (M3UA) Data Configuration........................... 111BSC Data Configuration.................................................... 137RNC Data Configuration.................................................... 168

OverviewDescription This chapter introduces the procedure and method of collecting

and making interconnection data so as to add various office direc-tions on the ZXWN MSCS equipment.

MGW Data ConfigurationOverview

TypicalNetworking

Mc interface is the interface between MSCS and MGW. The net-working structure is shown in Figure 1.

Confidential and Proprietary Information of ZTE CORPORATION 1


FIGURE 1 NETWORKING BETWEEN MSCS AND MGW

The Mc interface usually uses the IP bearer. Its protocol stack usesthe H.248/M3UA/SCTP/IP mode.

Data Collection Collect the data related to the Mc interface before data configura-tion, as described in Table 1.

TABLE 1 DATA COLLECTION TABLE

Parameter Items Parameter Values

Real address of the MSCS 192.168.1.11

Loopback address of the MSCS 192.168.11.11

Port number of the MSCS 2001

Real address of the MGW 192.168.1.31

Loopback address of the MGW 192.168.31.31

Port number of the MGW 2001

Coding scheme of H.248 protocol TEXT

MSCS signaling point code 1.11.2

MGW signaling point code 1.31.2

ConfigurationFlow

This configuration aims to complete the interconnection betweenthe MSCS and the MGW over the Mc interface so as to achieve themanagement and control over the media resources of the MGW.Table 2 describes the configuration flow.

2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Data Making for New Commissioning

TABLE 2 CONFIGURATION FLOW

Steps Operations Related Command

1 Creating a loop-back interfaceINTERFACELOOPBACK

ADD IP ADDRESS

2 Creating an SIPI interfaceaddress

INTERFACE

ADD IP ADDRESS

3 Creating a static route ADD IP ROUTE

4 Creating an MGW adjacentoffice ADD ADJOFC

5 Creating an MGW voiceCODEC template ADD CODECTPL

6 Creating a topology node ADD TOPO

7 Creating an inter-MGW bearermode ADD MGWBEARMOD

8 Creating an SCTP ADD SCTPCONN

9 Creating an ASP ADD ASP

10 Creating an AS ADD AS

11 Creating an M3UA static route ADD M3UART

12 Creating the SIO-locating-AS ADD SIOLOCAS

13 Creating MGC static data ADD MGCSCFG

14 Creating an MGW static datatemplate ADD MGSTPL

15 Creating MGW static data ADD MGSCFG

16 Creating a TID analyzer ADD TIDANL

17 Creating a TID analyzer entry ADD TIDENTR

Interface Address Configuration

Overview

Introduction Interface IP addresses are planned according to the actual net-working applications. The IP address of Nc, Iu-CS and other in-terfaces can be configuration independently, or share with the Mcinterface address.



Creating a Loopback Interface

Prerequisites Before the operation, it is required to confirm:

� The RPUmodule configuration is completed, and the RPU worksnormally.

� The MML Terminal window is opened.

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

Steps 1. If no exchange is specified, execute command SET on theMMLTerminal window or select a NE from the system tree to spec-ify the exchange to be configured.

Example: Select the MSCS exchange with ID as 11 from thesystem tree.

SET:NEID=11;

2. Create the RPU loop back interface. The command is INTERFACE LOOPBACK.

Port represents the port number, ranging from 1 to 128.

Example: Create the loop-back interface whose port numberis 1.

The command is as follows.

INTERFACE LOOPBACK:PORT=1;

3. Create the interface address. The command is ADD IP ADDRESS.

Table 3 describes the main parameters in the ADD IP AD-DRESS command.

TABLE 3 PARAMETERS IN THE ADD IP ADDRESS COMMAND

ParameterName

ParameterDescription Instruction

ADDRESS IP addressIt is a mandatory parameter.The IP address of theloop-back address.

MASK MaskIt is a mandatory parameterof 32-bit. In general, it is255.255.255.255.

BROADCASTIP Broadcast IPaddress

It is an optional parameter. Ingeneral, it is 255.255.255.255.

Example: Create a loop back address with the following re-quirements.

� IP address: 192.168.11.11

� Subnet mask: 255.255.255.255.




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 losswhen the RPU is restarted.The command is SAVE ONLINEDATA;.

5. Exit the interface configuration mode. The command is EXIT;

END OF STEPS

Creating an SIPI Interface Address


� The SIPI unit is created.


Context MSCS is interconnected to MGW on the CE through its SIPI board.The online configuration of SIPI board interface is to assign an IPaddress to some physical port of this SIPI board.



SET:NEID=11;

2. Enter the SIPI board interface configuration mode. The com-mand is INTERFACE.

Table 4 describes the main parameters in the INTERFACEcommand.

TABLE 4 INTERFACE REAL INTERFACE

ParameterName


SUBSYS-TEM 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. Itis the unit number of the realinterface. Select the unit numberof the board corresponded by theinterface.

SUNIT Subunit NoIt is a mandatory parameter. Realinterface’s sub-unit number fixedlyadopts 1.

PORT Port number

It is a mandatory parameter. Theport number refers to the networkinterface serial number of theSIPI rear board for connecting tothe external. The four network



ParameterName


interfaces are numbered 1 to 4from top to bottom. Only the firstport is used.

Example: Create the interface address of SIPI board. The con-figuration requirements are as follows.

� Unit number: 321

� Sub-unit number: 1

� Port number: 1

� Home module number: No.1 OMP module.


INTERFACE:SUBSYSTEM=0,MODULE=1,UNIT=321,SUNIT=1,PORT=1;

3. Create the interface address of the SIPI. The command is ADDIP ADDRESS.

Table 5 describes the main parameters in the ADD IP ADDRESS command.

TABLE 5 ADD IP ADDRESS REAL INTERFACE

ParameterName


ADDRESS IP addressIt is a mandatory parameter.The Mc interface address of SIPIboard

MASK Subnet maskIt is a mandatory parameter. Thereal interface subnet address ofcorresponding interface board

BROADCAS-TIP

Broadcast IPaddress

It is an optional parameter,corresponding to the broadcastaddress of the real address of thecorresponding 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.


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 losswhen the RPU is restarted.The command is SAVE ONLINEDATA;.



5. Exit the interface configuration mode. The command is EXIT;

END OF STEPS

Creating a Static Route


� The interface address is created.

� The BFD parameters are created when load-sharing networkingmode is adopted.


Context Static route is created when the service IP address of local sig-naling plane and PE interface address are not in the same net-work section. Under the active/standby working mode, a destina-tion address needs to be configured with a route only. Under theload-sharing working mode, a destination address usually needsto be configured with two routes.



SET:NEID=11;

2. Create the static route. The command is ADD IP ROUTE.

Table 6 describes the parameters in the ADD IP ROUTE com-mand.

TABLE 6 PARAMETERS IN THE ADD IP ROUTE COMMAND

ParameterName


NETPRE Net prefix

MASK Mask

It is a mandatory parameter.Type the network section of theopposite-end equipment serviceaddress according to the networkplanning. Its prefix should matchits mask

NEXTHOP Next hop IP

It is an optional parameter,indicating the router interfaceaddress (VRRP address). Type thegateway address to the oppositeend office

DISTANCE Distance It is an optional parameter with adefault of 1, ranging from 1 to 254

BFDDETECT Enable BFDDetect

It is an optional parameter. Ingeneral, select NO. The settingEnable BFD Detect is effectiveonly when IP address acts as thenext hop.



Example: Create the static route to the opposite end with thefollowing 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 thefollowing requirements.

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




END OF STEPS

Adjacent Office and TopologyConfiguration

Overview

Introduction Adjacent office configuration means configuring the neighboringoffice of the local office. There are two association modes, directassociation and quasi-association.

If the adjacent office is regarded as a node in the whole networktopology when the local office is in the center, topological nodeconfiguration means adding the topological node of its adjacentoffice in the local office. The topological nodes configured on MSCSinclude MGW, RNC/BSC, and MSCS (Nc).



ConfigurationFlow Steps Operations Instructions Command

1 Creating an MGWadjacent office

Create the ba-sic information ofMGW adjacent of-fice.

ADD ADJOFC

2Creating an MGWvoice CODEC tem-plate

Create the encod-ing and decodingspeech type mod-ules supported byIM-MGW.

ADD CODECTPL

3 Creating a topol-ogy node

Create the topol-ogy relationshipbetween MGCFnode and IM-MGWnode.

ADD TOPO

4Creating inter-MGW bear mode(optional)

The inter-MGWbearer mode isconfigured whenthe Nb interfacesbetween severalIM-MGWs underthe same MGCFare connected.

ADD MGWBEARMOD

Creating an MGW Adjacent Office


� The physical IP connection between the MSCS and the MGWis clear, which is implemented by the connection between theFE1 interfaces on the rear board of the SIPI boards of thesetwo 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 re-source management.


Context Perform this procedure to configure the basic information of MGWadjacent office. On the MSCS, each MGW is configured with threeadjacent offices according to the SCTP Planning.



SET:NEID=11;

2. Create the MGW adjacent office. The command is ADD ADJOFC.

Table 7 describes the main parameters in the ADD ADJOFCcommand.



TABLE 7 PARAMETERS IN THE ADD ADJOFC COMMAND

ParameterName


ID Office ID

A mandatory parameter,indicating the identificationnumber of the adjacentoffice, and ranging from1 to 3000. In general,it is configured as theexchange ID of theadjacent office during theall-network planning

NAME User-defined aliasIt is a mandatoryparameter. Type acustomized name.

NET Network type

A mandatory parameter,indicating the networktype of the SPC used forconnecting the local officeto the adjacent officewhen the local office isconfigured with severalSPs. The default is thenetwork type of this SPwhen there is only one SPin the local office

OFCTYPE The type of adjacentoffice

It is a mandatoryparameter. Select MGWfor the MGW bearing H248signaling. Select SGW foranother two MGW offices.

SPCFMT SPC format Select TRIPLE_DEC.

SPCTYPE SPC type

DPC Destination SPC

It is a mandatoryparameter. Select itbased on the SPC typeof the adjacent officeaccording to the signalingpoint planning. In China,all the NEs adopt the 24-bitSPC except the BSC thatadopts the 14-bit SPC.

RC Area code

It is an optional parameter,indicating the local tollzone code of the adjacentoffice. This parameterhas impact on the areacode added by the callingnumber



ParameterName


ASSOTYPE

Association type,including:

� AM_SURE (directconnection mode)

� AM_QUASI (halfdirect connectionmode)

� AM_NONE (noneconnection mode).

It is an optional parameter.Select AM_SURE

SPTYPESignaling point type,including SEP, STP,and STEP

It is an optional parameter.Select SEP (signalingend point) for the MGWbearing H248 signaling.Select STEP (signalingtransition / end point) foranother two MGW offices

SSF

Subservice function,including

� INTERNATIONAL(Internationalsignaling pointcode)

� INTERNATIONALSTANDBY(Internationalstandby signalingpoint code)

� NATIONAL(National signalingpoint code)

� NATIONALSTANDBY(National standbysignaling pointcode).

It is an optional parameter.

In general, NATIONALis selected at home. Forthe BSC adjacent office,NATIONAL STANDBY isselected.

TAG

Office Attribute,including:

ISNI (Has ISNIFunction)

TRANS (TranslateNode)

TEST (Need TestInfo:0X02/0X01)

It is an optional parameter

TEST Test flag

It is an optional parameter.It is used to set whetherthe MTP3 link activelyinitiates the link testafter entering the servicestatus. In most cases, thisparameter is selected.



ParameterName


BANDFLAG Broadband attribute

It is an optional parameterwith a default of NO. Itis used for SCCP to judgewhether to use the LUDTmessage.

The maximum length of abroadband link messageis 4,000, and that of anarrowband link messageis 255. Because the MTPlayer does not have thesegmentation function, theincorrect configuration ofthis parameter probablycauses the long packet tobe discarded.

Select this parameterwhen all the links betweentwo SPs are SIGTRAN orATM signaling links.

PRTCTYPE

Protocol Type,including:

� CHINA (China)

� ITU (InternationalTelecommunica-tions Union)

� ANSI (AmericanNational StandardsInstitute)

It is an optional parameter.The CHINA and the ITUare used for the NO.7signaling networking ofthe ITU standard and theANSI is used for the NO.7signaling networking ofthe American standard.In general, select CHINAfor the domestic officeand select ITU for theinternational office

CLST Cluster ID

It is an optional parameterwithin 0~65535. Ingeneral, select the defaultvalue 65535. It is validwhen the protocol typeof the adjacent office is“ANSI”. The signaling pointconnected to the signalingtransfer point belongs tothe corresponding cluster

INFO

Office Info, including:

� CIC_PCM (CICstarts the loadsharing accordingto the PCM codemode)

� BLOCK (Manualblock status)

� EVEN_CIC (Theoffice controlsthe even CICwhen CIC resourcecontention occurs)

It is an optional parameterand the default value isCIC_PCM



ParameterName


� CALLING(Callingtransform isallowed)

� CALLED (Calledtransform isallowed)

� MOD24_CIC (CICmode with 24mode)

� TEST (Dynamictest)

RELATE-DOFC1 Related Office ID It is an optional parameter

ranging from 0 to 3000

INFOEX

Office Extend Info,including:

� SIGBRDCST(Support SignalingBroadcastMessage)

� MTP (HongkongMTP Standard)

� DUPU ( ScreenDUPU message)

� SUA_REC_DT1(Receive SUAmessage andhandle it as DT1message)

� SUA_SND_DT1(Send SUAmessage andhandle it as DT1message withoutSN.)

� OPEN_TG_RES(Open outter trunkgroup resource)


For example, create MGW adjacent office. The office ID is 101,the alias is MGW1, and the destination SPC is 1.31.2. For otherparameters, adopt the default value. The command is as fol-lows:

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=NATIONAL STANDBY,SUBPROTTYPE=DEFAULT,TEST=YES,BANDFLAG=YES,PRTCTYPE=CHINA,CLST=65535,INFO="CIC_PCM",RELATEDOFC1=0;

END OF STEPS



Creating an MGW Voice CODEC Template


� The basic configuration of the local office is completed.

� The range of the MGW voice CODEC template numbers is con-figured in the resource management configuration.


Context Perform this procedure to create the encoding and decodingspeech type modules supported by MGW. In general, MSCS isconfigured with a default common voice CODEC template.



SET:NEID=11;

2. Create the MGW voice CODEC template. The command is ADDCODECTPL.

Table 8 describes the main parameters in the ADD CODECTPLcommand.

TABLE 8 PARAMETERS IN THE ADD CODECTPL COMMAND

ParameterName


ID Templatenumber

It is a mandatory parameterfor defining an encoding anddecoding speech template,ranging from 1 to 255.

GRPIDThe groupnumber of thespeech coding.

It is a mandatory parameter forspecifying the OID format andencoding and decoding type list.Up to eight types can be definedin an encoding and decodingtemplate.

VALFG

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

It is a mandatory parameter forsetting whether this encodingand decoding speech template isvalid. Select YES

OID OID

It is a mandatory parameter forspecify an Organization Identifier(OID).

It has the following parameters.

� OID_NONE: No OID

� OID_ITU_T: ITU_T

� OID_ETSI: ETSI

� OID_IETF: IETF



ParameterName


ITYPE ITU_T CODECtype.

It is an optional parameter. Ingeneral, ITUT_G711A_64 isselected.

ETYPE ETSI CODECtype

It is an optional parameter. Ingeneral, ETSI_UMTS_AMRand ETSI_UMTS_AMR_2 areselected.

ACTRATE ActivatedCODEC rate

It is an optional parameter. Ingeneral, the default value isselected

SUPRATE SupportedCODEC rate


OM ACS optimizedmode


Example: Configure an MGW encoding and decoding speechtemplate 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="Rate590"&"Rate670",SUPRATE="Rate590"&"Rate670",OM=YES;

END OF STEPS

Creating a Topology Node


� The encoding and decoding speech template is configured.

� The range of the topological node number is configured in theresource management.


Context Perform this procedure to configure the topology relationshipbetween MSCS node and MGW node. This command is used toconfigure the adjacent NE information, including equipment type,



bearer type and attributes, user plane version, encoding anddecoding template, and other information.

For Mc interface, only the adjacent office bearing H.248 protocolis configured as a topological node.



SET:NEID=11;

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

Table 9 describes the main parameters in the ADD TOPO com-mand.

TABLE 9 PARAMETERS IN THE ADD TOPO COMMAND

ParameterName


ID Topological nodeID

It is a mandatory parameter todefine ID of this node, rangingfrom 1 to 2,048.

It is recommended that the IDand office No. of a topologicalnode are consistent

OFCID Office ID

It is a mandatory parameterfor specifying the office ID ofthis topological node. Thisparameter must be defined bythe ADD ADJOFC commandfirst.

In this case, type the actualMGW office number

NAME Alias

It is a mandatory parameterfor naming this topologicalnode, with a length rangingfrom 1 to 50 characters.

CODECID CODEC identity

It is a mandatory parameterfor specify the CODECtemplate used by thistopological node. Thisparameter must be definedby the ADD CODECTPLcommand first.

ETYPE Equipment type

This parameter is used tospecify the NE type of thistopological node.

Select R4GW for an MGWnode

PROTTYPE Protocol type Select H.248 for Mc interface.



ParameterName


IPVER IP version of thenode

It is the IP protocol versionsupported between nodes.Select IPV4 or IPV6according to the actualconditions. Currently, IPV4 issupported.

ATTR Bearer attributes

This parameter is only validfor the node with the typeof R4GW (MGW). The bearertypes supported by MGWare BNCAAL1, BNCAAL2,BNCAAL1S, BNCIPRTP, andBNCTDM. MGW can supportone or more of these types ofbearers.

In general, select BNCAAL2,BNCIPRTP, and BNCTDM

UPVERUser planeprotocol versionof RNC or MGW

This parameter is used to setthe user plane version of thisnode.

In general, select V2

ATTR2

Extendedattributes (tunnelmode), including:

� NOTUNL(None tunnelmode)

� RTUNL(Rapid tunnelmode)

� DTUNL(Delay tunnelmode)

This parameter is used to setwhich tunnel mode is adoptedfor bearer establishment whenthis node supports the IP/RTPbearer. The default value isNOTUNL (None tunnel mode).

In general, select DTUNL(Delay tunnel mode) for anMGW topological node.

TRFMOD

Signaling transfermode, including:

MCINTF (Mcinterface signaltransfer mode)

This parameter is used to setwhich mode is used by thetopology for reporting whenit detects CNG or CED faxsignals.

The default value is MCINTF

UPERRCTRL

Error SDUcontrol, includingoptions:

YES: The userplane entity im-plements errorinspection, andsets the FQC bitposition accord-ing to the result.It will transmitall frames in-cludes the errorframes to theuser plane layer.

This parameter regulates thehandling method of the userplane for error frames. It isonly valid for MGW-type andRNC-type topological node.The default value is YES



ParameterName


During a call, theerror packet con-trol parameterdelerrsdu=Yes,which is deliveredby the terminalestablished byMGW on the Mcinterface. Theerror packet con-trol parameterdeliveryOfErro-neousSDU is YES,NA, NA duringRAB assignment.

NO: The userplane entity im-plements theerror inspection.It will directlydiscard the errorframe. Duringa call, the er-ror packet con-trol parameterdelerrsdu=No,which is deliveredby the terminalestablished byMGW on the Mcinterface. Theerror packet con-trol parameterdeliveryOfErro-neousSDU is NO,NA, NA duringRAB assignment.

INVALIDTION:The user planeentity does notimplement theerror inspection.During a call, theerror packet con-trol parameterdelerrsdu=NA,which is deliveredby the terminalestablished byMGW on the Mcinterface. Theerror packet con-trol parameterdeliveryOfErro-neousSDU is NA,NA, NA duringRAB assignment.



ParameterName


DTMFTC

Tandem officesend DTMFuse TC mode,including twooptions:

� NO

� YES

This parameter is used to setwhether the tandem officeuses the TC resources duringDTMF number delivery.

The default value is NO

MGWCONMGW congestionreportingcapability

It contains the followingoptions.

� SMGWCON (StandardMGW congestion event)

� CMGWCON (Custom MGWcongestion event).

The default value isSMGWCON.

Example: Create a topology node with the following require-ments.

� 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",CODECID=1,ETYPE=R4GW,PROTTYPE=H248,IPVER=IPV4,ATTR="BNCAAL2"&"BNCIPRTP"&"BNCTDM",UPVER="V2",ATTR2=DTUNL,TRFMOD=MCINTF,UPERRCTRL=YES,DTMFTC=NO,MGWCON=SMGWCON,AUTOFAX=YES,OOBTC=NO,BCUID=0,SENDCAP=NO,G711TRAN=NO,BICCDTMF=TRANSPARENT,IPBCP2833=BYMGW,BICCDTMPPER=0,AOIPPRO=PRIVATE;

END OF STEPS

Creating an Inter-MGW Bearer Mode


� The MGW topological node is created.


Context The inter-MGW bearer mode is configured when the Nb interfacesbetween several MGWs under the same MSCS are connected.





SET:NEID=11;

2. Create the inter-MGW bearer mode. The command is ADDMGWBEARMOD.

Table 10 describes the main parameters in the ADD MGWBEARMOD command.

TABLE 10 PARAMETERS IN THE ADD MGWBEARMOD COMMAND

ParameterName


MGWPAIR MGW node pairType the gateway node IDconfigured in the topologicalnode configuration.

ATTR

Bearer attributebetween MGWs,the optionsinclude:

AAL1(supportbncAAL1)

AAL2(supportbncAAL2)

AAL1S (supportnbcAAL1Struct)

RTP (supportbncIPRTP)

TDM(supportbncTDM)

The parameter specifies thebearer attribute betweenMGWs. Select RTP or TDMaccording to the type of Nbinterface bearer.

CTYPE

Type of tone codebetween MGWs,the optionsincluding:

GENERAL

AMRONLY

AMRONLY represents the AMRencoding and decoding modeis used only. When G.711 andother encoding and decodingmodes are allowed, selectGENERAL

NAME Alias“Adjacent office alias ofgateway 1-Adjacent office aliasof gateway 21”

AAL1 AAL1 bearer typerate(%)

The parameter specifies therate (%) of the AAL1 bearerbetween two gateways

AAL2 AAL2 bearer typerate(%)

The parameter specifies therate (%) of the AAL2 bearerbetween two gateways

AAL1SAAL1STRUCTbearer typerate(%)

The parameter specifies therate (%) of the AAL1 STRUCTbearer between two gateways

RTP IPRTP bearer typerate(%)

The parameter specifies therate (%) of the IPRTP bearerbetween two gateways



ParameterName


TDM TDM bearer typerate(%)

The parameter specifies therate (%) of the TDM bearerbetween two gateways

DIRECT

Top-priority directlink topology, theoptions include:

NO

YES

The default is NO

UPMODE

User plane modefor multi-gatewayIP bearer, theoptions include:

TRANSPAR-ENT(transparentmode)

SUPPORT(supportmode)

The default is TRANSPARENT

IPNET Public IP networkdomain index

The parameter is used to setthe public IP network domainindex (ADD IPDOMAIN)

G711TRAN

G711 that isforced to usethe transparentmode. Optionsinclude:

NO

YES

The default is NO

Example: Configure the bearer mode between two MGWs withthe 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.


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

END OF STEPS



SIGTRAN Configuration

Overview

Description SINGTRAN-related configuration is required not only by the Mcinterface between MSCS and MGW, but also by the Nc interfacebetween 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 requiredonly. In general, this mode is not used.

Compared with the MTP data configuration of the traditional No.7signaling, the SCTP association configuration and the ASP config-uration of the M3UA are similar to the link logic and bearer infor-mation configurations in the MTP configuration, and the AS config-uration of the M3UA is similar to the link set configuration in theMTP configuration. The configuration of SIO location AS is similarto the signaling office direction and route configuration in the MTPconfiguration. The only difference between them is that one pieceof SIO location AS configuration record is configured the IP routeto a subscriber of an office.



ConfigurationFlow

Figure 2 shows the flow of SIGTRAN configuration.

FIGURE 2 SIGTRAN CONFIGURATION FLOW

According to the rules regulated in SCTP Planning, perform theconfiguration by following the procedure specified below.

Steps Operations Instructions Command

1 Creating SCTP Create an associationbetween two offices ADD SCTPCONN

2 Creating ASP

Create the one-to-one relationshipbetween the ASP andthe association. ASPis one of instances ofAS.

ADD ASP

3 Creating ASCreate the tag, usertype, subsystem typeof AS

ADD AS




4 Creating M3UAstatic route

Create the mappingrelationship betweenthe M3UA static routeand the AS.

ADD M3UART

5Creatingthe SIO-Locating-AS

Locate one service toa routing table thatis maintained by theASP under the AS.

ADD SIOLOCAS

Creating an SCTP


� The physical configuration of the SMP module is completed.

� The SCTP flag is configured in the resource management.


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



SET:NEID=11;

2. Create the SCTP connection. The command is ADD SCTPCONN.

Table 11 describes the chief parameters of the ADD SCTPCONN command.

TABLE 11 PARAMETERS IN THE ADD SCTPCONN COMMAND

ParameterName


MODULE Module No.

It is a mandatoryparameter, indicatingthe number of thesignaling modulehomed by this SCTPassociation. Select theSMP module number.Each SMP can supportup to 128 associations.The associations underthe same AS arerequired sharing loadon SMP modules asmore as possible.



ParameterName


OFCID SCTP opposite officeID

It is a mandatoryparameter, designatingthe office No. ofthe direct-associatedassociation. Typethe MGW adjacentoffice No. specifiedin the adjacent officeconfiguration.

PROT

Bearer protocoltypes, including

� M2UA

� M2PA

� M3UA

� SUA

� H248

� BICC

� IUA

� DHCTRL

� SIP

� DIM

� V5UA

� H245

It is a mandatoryparameter. It is used toidentify the upper-layerprotocol type borne bythe SCTP association.In general, M3UA isselected. M2UA isselected when MGWtransfers the signalingwith the M2UA mode.

ROLE

SCTP applicationattributes. Optionsinclude:

SVR: SCTP is usedas server

CLT: SCTP is used asclient

It is a mandatoryparameter. For Mcinterface, MSCS isconfigured as CLT, andMGW is configuredas SVR. For Ncinterface, this shouldbe negotiated by bothsides. For example, thesmall signaling pointserves as CLT, andthe big signaling pointserves as SVR

LOCADDR Local IP address

It is a mandatoryparameter. Itdesignates the serviceaddress of local endof this association,with a format ofLocal IP addresstype-VPN of localIP address-Local IPaddress

Local IP address type:IPv4 and IPv6

VPN of local IP address:Rang from 0 to 65535



ParameterName


Local IP address:the format isxxx.yyy.zzz.mmm

LOCPORT Local port number

It is a mandatoryparameter. It is thelocal SCTP port numberof the association,ranging from 1 to65535.

REMADDR Opposite IP address

It is a mandatoryparameter. Itdesignates the serviceaddress of remote endof this association,with a format ofRemote IP addresstype-VPN of remoteIP address-RemoteIP address

Remote IP addresstype: IPv4 and IPv6;

VPN of remote IPaddress: Rang from 0to 65535

Remote IP address:the format isxxx.yyy.zzz.mmm

REMPORT Opposite portnumber

It is a mandatoryparameter. It isthe opposite SCTPport number of theassociation, rangingfrom 1 to 65535.

NAME Alias

It is a mandatoryparameter with alength ranging from 1to 50 characters.

ID SCTP ID

It is an optionalparameter. It is theglobal serial number ofthe SCTP association,ranging from 1 to 2048.Configure it accordingto the associationplanning.

Example: Create the SCTP connection for the Mc interface withthe following requirements.


� 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



ADD SCTPCONN:MODULE=3,OFCID=101,PROT=M3UA,ROLE=CLT,LOCADDR="IPv4"-"0"-"192.168.1.11",LOCPORT=2001,REMADDR="IPv4"-"0"-"192.168.1.31",REMPORT=2001,NAME="MGW101-1",ID=1,INSTRM=16,OUTSTRM=16,MAXRTRY=5,MAXRTO=500,MINRTO=50,INITRTO=100,HB=500,FIXNH=NO,SCTPMAXRTRYNUM=10,DELAYACK=20,MAXBURST=4,PRIMARYPATH=REMIP1,PMTU=0,BREAKTIME=0,PDTHRESH=0,MINCWND=0,PLTIMER=10,MPPLTHRD=2,DPLEN=MTU,CB=200;

END OF STEPS

Creating an ASP


� The SCTP association information configuration is completed.

� The range of the ASP configuration identification is created inthe resource management configuration.


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



SET:NEID=11;

2. Create the ASP. The command is ADD ASP.

Table 12 describes the main parameters in the ADD ASP com-mand.



TABLE 12 PARAMETERS IN THE ADD ASP COMMAND

ParameterName


ASSOCID SCTP ID

It is a mandatory parameter,ranging from 1 to 2048

Type the association IDconfigured in the SCTPconnection configuration.

NAME Alias

It is a mandatory parameter,with a lengthen ranging from1 to 50 characters. It maybe named with a format of“Adjacent office alias-SCTPnumber”.

ID ASP ID

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

It is recommended to beconsistent with ASSOCID.

ISLOOP ASP self-loop ID

It is an optional parameter. It isused to set whether the ASP isself-looped.

Select the default value NO

ISLOCK ASP blocking flag

It is an optional parameter. It isused set whether the ASP is inblocking state.

Blocking is used formanagement. Select thedefault value NO

Example: Create the ASP between MSCS and MGW for Mc in-terface with the following requirements.



� ASP configuration ID: 1

� User alias: MGW101-1.


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

END OF STEPS

Creating an AS


� The ASP configuration is finished.




Context The AS provides the transmission channels for upper-layer ser-vices. For example, H248 and TUP/UP are different services. Theyuse different AS for transmission. The AS can use one or moreassociations for communication.



SET:NEID=11;

2. Create the AS. The command is ADD AS.

Table 13 describes the main parameters in the ADD AS com-mand.

TABLE 13 PARAMETERS IN THE ADD AS COMMAND

ParameterName


PROTSupportedadaptation layerprotocols

It indicates the protocoltype of a bearer. In general,M3UA is selected accordingto the networking planning.It is configured as M2UAwhen MGW transfers thesignaling with M2UA mode.

ASP ASP IDIt is associated with theASP ID configured in theASP configuration.

NAME AliasIt is a mandatoryparameter. The aliascustomized by the user.

ID AS ID

It is an optionalparameter. It is the uniqueidentification of the AS. Ingeneral, it is the same asthat of the ASP for easymemory. The parameterranges from 1 to 640

EXISTCTX Whether the routingcontext ID exists

CTXID Routing context ID

It is an optional parameter.The routing context isunique in the network.This parameter mustbe consistent with theAS configuration of theopposite-end. Its defaultvalue is NO



ParameterName


ASTAG

Usage tag. Optionsinclude:

SGP

ASP

SRV (IPSP server)

CLT (IPSP client)


For Mc interface, MSCSgenerally serves asIPSP_Client, and MGWserves as IPSP_Server.When MGW acts as a SGW,the AS at the MSCS sideserves as ASP, and the ASat the SGW side serves asSGP.

For Nc interface, this shouldbe negotiated by bothsides. For example, thesmall signaling point servesas IPSP_Client, and the bigsignaling point serves asIPSP_Server.

ASUP

User typessupported by AS.Options include TUP,ISUP, BICC, H.248,ALCAPSCCP, PCA,NNSF and ALL

It is an optional parameter.It defines the upper-layeruser types supported bythe AS. Currently, there areeight types of users.

User type is not configuredwhen MGW transfers thesignaling with the M2UAmode

ASMD Service modessupported

It is an optional parameter.The supported servicemodes include:

� OVERRIDE(Over-ridemode)

� LOAD (Load sharemode).

In the over-ride mode,only one ASP is in theactivated statue. In thiscase, only one ASP needsbe configured. In theload sharing mode, NASPs should be configuredin the activated workingstatue, and K ASPs shouldbe configured in thedeactivated standby statue.

The value of N+K is notmore than the number ofASPs actually configured



ParameterName


SSN

Types of subsystem.Options includeNO_SSN (subsystemSSN 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 (intelligentperipherals),SMC, SSP_SCP,BSC_BSSAP_LE,MSC_BSSAP_LE,SMLC_BSSAP_LE,BSS_O_M_A ,BSSAP_A andRVE255.

Types of subsystemsupported by applicationserver (AS).

NVAL The N value in loadsharing mode

The parameter ranges from0 to 16.

The N+K should be equal tothe number of ASP underAS.

The N value indicates thatAS puts into use if N ASPsput into use.

Example: Configure the AS between MSCS and MGW for Mcinterface with the following requirements.


� Supported adaptation layer protocol: M3UA

� AS configuration ID: 1

� Supported user type: H248

� ASP ID: 1

� Client: MSCS

� Alias: H248


ADD AS:PROT=M3UA,ASPID="1",NAME="H248",ID=1,EXISTCTX=NO,ASTAG=SGP,ASUP="H248",ASMD=LOAD,NVAL=1,KVAL=0;

END OF STEPS



Creating an M3UA Static Route


� The AS configuration is finished.

� The range of the M3UA static route identification is configuredin the resource management configuration.


Context Perform this procedure to configure the mapping relationship be-tween the M3UA static route and the AS. An M3UA static routecan be used by up to 64 SIO-locating-ASs. Otherwise, configuringmore M3UA static routes is required.



SET:NEID=11;

2. Create the M3UA static route. The command is ADDM3UART.

Table 14 describes the main parameters in the ADD M3UARTcommand.

TABLE 14 PARAMETERS IN THE ADD M3UART COMMAND

ParameterName


ID ID of M3UAstatic route

It is an optional parameter,indicating the serial number of theM3UA static route ID, ranging from1 to 640. In general, it is the sameas the AS ID.

ASID AS IDIt is a mandatory parameter,corresponding to the AS IDspecified in the ADD AS command.

MODE

Alignmentmode ofroutes.Optionsinclude

� BYTURNS

� LOCAL

� NATURE

Nature: routes are directly sortedaccording by the ASP marshallingsequence in the routing table.

Local: It is unnecessary to realizethe algorithm in the background.The background just needs to makethe alignment according to theNature option.

BYTURNS: in the routing table,the routes at the odd-bit positionare sorted by the serial number ofthe activated ASP, and the routesat the even-bit position are sortedinversely by the serial number ofthe activated ASP

The default is BYTURNS.

NAME AliasIt is a mandatory parameter definedby a user, with a length rangingfrom 1 to 50 characters.



Example: Create an M3UA static route for Mc interface withthe following requirements.


� M3UA static route ID: 1

� AS ID: 1

� User alias: MGW101.


ADD M3UART:ID=1,ASID=1,MODE=BYTURNS,NAME="MGW101";

END OF STEPS

Creating the SIO-Locating-AS


� The M3UA static route configuration is completed.

� The range of the SIO-locating-AS configuration ID is configuredin the resource management configuration.


Context The configuration of SIO-locating-AS is used to locate one serviceto a routing table that is maintained by the ASP under the AS. OnMSCS, H248 protocol is generally configured between MSCS andMGW, and ISUP, TUP, and SCCP protocols are configured betweenMSCS and other adjacent offices that are switched by MGW.

A routing key describes a set of No.7 signaling parameters andparameter values. The corresponded AS is selected according tothe message attributes, thus to select a route for the message.

The message attributes include DPC+NET+OPC+SIO. The DPCrepresents the destination SPC, the NET represents the networktype, OPC represents the original SPC, and the SIO representsthe service information octet.



SET:NEID=11;

2. Create the SIO-locating-AS. The command is ADD SIOLOCAS.

Table 15 describes the main parameters in the ADD SIOLOCAS command.



TABLE 15 PARAMETERS IN THE ADD SIOLOCAS COMMAND

ParameterName


ID SIO-location-AS ID

It is an optional parameter,indicating the serial number ofSIO-locating-AS, ranging from 1 to4096. In general, it is the same asthe AS ID.

NAME Alias It is a mandatory parameter, whichis the alias customized by the user.

SIO

Serviceindication.Options include

� NULL

� TUP

� ISUP

� BICC

� H.248

� ALCAP

� SCCP

� PCA

� NNSF

It is a mandatory parameter,indicating the subscriber typebelonged by the transmittedmessage. Different user types canbe located to the same AS underthe precondition that the MS mustsupport these user types

Select H.248 for Mc interface,BICC for Nc interface, SCCP forthe RNC or BSC office transferredthrough MGW, and TUP or ISUPfor the 2G MSC/PSTN officetransferred through MGW.

OFCIDDestinationadjacent officeID

It is a mandatory parameter,indicating the adjacent office IDcorresponded by the destinationsignaling point of the M3UA.It needs to associate with theadjacent office ID in the adjacentoffice configuration.

OPOFCIDOriginaladjacent officeID

It is the adjacent office IDcorresponding to the M3UAoriginating signaling point. If0 (indicating the local office)is selected, it indicates thatthe message is sent from thelocal office, and the routingcontext is routed according toDPC+NET+OPC+SIO. If 65535(invalid) is selected, it indicatesthat the OPC field is invalid, andthe routing context is routedaccording to DPC+NET+SIO

PCM PCM systemnumber

It is an optional parameter. Itranges from 0 to 65535, with adefault of 65535 (invalid).



ParameterName


RT1 ID 1 of M3UAstatic route


It corresponds to the IDspecified in the M3UA staticroute configuration. RT1 is amandatory parameter. In general,RT1 is required. When theoptimum route mode is adopted,RT1 is set as an active route, andRT2 is set as a standby route.

Example: Create SIO-locating-AS between MSCS and MGWwith the following requirements.


� Destination adjacent office ID: 101

� Service indication: H.248

� M3UA static route ID: 1.


ADD SIOLOCAS:ID=1,NAME="MGW-H248",SIO=H248,OFCID=101,OPOFCID=65535,PCM=65535,RT1=1,RT2=0;

END OF STEPS

H.248 Configuration

Overview

Description H.248 protocol is only used on Mc interface. It provides the fol-lowing functions.

� Under the control of MGC, it can establish, modify and releasethe media channel in the MG, and can control the attributes ofbearer and user plane.

� It reports the events in the MG to the MGC.

� It maintains the office and terminal status between MGC andMG.



ConfigurationFlow

Figure 3 shows the configuration flow of H.248 protocol.

FIGURE 3 CONFIGURATION FLOW

Flow Description The H.248 configuration procedures are as follows:


1 Creating MGCstatic data

Cofigure the datarelated to theMGCF and H.248.

ADD MGCSCFG

2Creating anMGW static datatemplate

Create thetemplate usedby the MGWstatic dataconfiguration.

ADD MGSTPL

3 Creating MGWstatic data

Create the staticdata for eachIM-MGW underthe MGCF.

ADD MGSCFG




4 Creating a TIDanalyzer

The TID analysisconfiguration isnecessary forthe H.248 serverto perform thecharacter stringconversion ofthe CIC. Nomallyadopt the defaultconfiguration.

ADD TIDANL

5 Creating a TIDanalysis entry

Create aTID analyzerentrance.Nomally adoptthe defaultconfiguration.

ADD TIDENTR

Creating MGC Static Data


� The data configuration of the local office is completed.


Context Perform this procedure to set the data related to the MSCS andH.248.



SET:NEID=11;

2. Create the MGC static data. The command is ADD MGCSCFG.

Table 16 describes the main parameters in the ADD MGCSCFGcommand.

TABLE 16 PARAMETERS IN THE ADD MGCSCFG COMMAND

ParameterName


MEGACO MEGACO versionnumber

It is an optional parameter.Select the supported MEGACOversion number, which must beconsistent with that negotiatedwith the MGW. The default valueis 1

ACTTMService activationdetectiontimer(s)

It is an optional parameter,ranging from 0 to 3600, with adefault of 600

ACTCHK Service activationdetection switch

It is an optional parameter,being activated by default.



ParameterName


WAITTMMGW answerwaiting timer(ms)


PTRYNUM PEND retrytimes(t)


PTRYTM PEND retry time(ms)


CTXLIVETM Context livetime(s)


NAME Alias

It is an optional parameter,ranging from 0 to 50 characters.It may be the same as the officename

Example: To create the MGC static data of an MSCS office withall the parameters adopting default value, the specific com-mand is as follows.

ADD MGCSCFG:MEGACO=1,ACTTM=600,ACTCHK=ON,WAITTM=7800,PTRYNUM=5,PTRYTM=4000,CTXLIVETM=1200,MGACTTM=600;

END OF STEPS

Creating an MGW Static Data Template




Context Perform this procedure to set the template used by the MGW staticdata configuration.



SET:NEID=11;

2. Create an MGW static data template. The command is ADDMGSTPL.

Table 17 describes the main parameters in the ADD MGSTPLcommand.



TABLE 17 PARAMETERS IN THE ADD MGSTPL COMMAND

Parame-ter Name


NAME Alias

This is a mandatory parameterwith a length ranging from1 to 50 characters. It canbe consistent with the officename.

ID Static data templatenumber

The number of a template,ranging from 1 to 255

MEGACO MEGACO versionnumber

This parameter must beconsistent with that negotiatedwith the MGW.

ACTCHK Gateway activationdetection switch

It is configured as ON bydefault

PRTTM Transient protectiontimer (s)

It ranges from 1 to 180. Typethe default value 10

PRT Transient protectionswitch

It is configured as ON bydefault.

PENDTM Interval of PENDmessages (ms)

It ranges from 0 to 3600, witha default of 200

LNGTM Maximum existencetime (ms)

It ranges from 0 to 65535,with a default of 15000

RTRNTM Retransmissiontimer (ms)

It ranges from 0 to 65535,with a default of 3800

MTRNNUM Maximumtransmission times

It ranges from 0 to 15, with adefault of 1

TRNMD Retransmissionmode

� FIXED: Duration un-changeable

� UNFIXED: Durationchangeable

CTYPE H.248 protocolcoding mode

It must be consistent with thatnegotiated with the MGW dataconfiguration

Example: Create an MGW static data template with the follow-ing requirements.

� Template ID: 1

� User name: MGW101



ADD MGSTPL:NAME="MGW101",ID=1,MEGACO=1,ACTCHK=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


� The MGW topological node is configured.

� The MGW static data template is configured.

� The MSCS voice batch processing is finished.


Context Perform this procedure to configure the static data for each MGWunder the MSCS.



SET:NEID=11;

2. Create MGW static data. The command is ADD MGSCFG.

Table 18 describes the main parameters in the ADD MGSCFGcommand.

TABLE 18 PARAMETERS IN THE ADD MGSCFG COMMAND

Parame-ter Name


ID Gatewaynumber

It is a mandatory parameter forconfiguring the node number ofthis gateway, ranging from 1 to2048. It is associated with the nodeID specified by the ADD TOPOcommand.

TPLIDStatic datatemplatenumber

It is a mandatory parameterassociated with the templatenumber configured on the MGWstatic data template configuration.

TONEID Service tonetemplate ID

It is an optional parameter rangingfrom 0 to 65535. It uses thetemplate ID specified in the BADDSTONE command.

LANGIDLanguagedescriptiontemplate ID

It is an optional parameter, rangingfrom 0 to 65535. It uses thetemplate ID specified in the BADDSTONE command.



Parame-ter Name


NAME AliasIt is a mandatory parameter,ranging from 0 to 50 characters. Itmay be the same as the office name

BKMGC Backup MGCinformation

It is an optional parameter, with adefault of NULL

PKGLOSTThreshold ofpackage lossrate (0.01%)

It is an optional parameter, rangingfrom 0 to 10000, with a default of10

JITThresholdof networkjittering (ms)


DELAYThreshold ofnetwork delay(ms)


MGW MGW tandem

It is an optional parameter forsetting whether this MGW is usedfor the tandem function. Type thedefault value NO

Example: Create static data for an MGW with the followingrequirements.


� Static configuration template ID: 1

� Alias: MGW101.


ADD MGSCFG:ID=101,NAME="MGW101",TPLID=1,TONEID=1,LANGID=1,PKGLOST=10,JIT=50,DELAY=200,MGW=NO;

END OF STEPS

Creating a TID Analyzer




Context The TID analysis configuration is necessary for the H.248 serverto perform the character string conversion of the CIC. The H.248server converts the CIC on the server to the corresponding char-acter string according to the mode configured by the TID analysis.Then it sends this character string to the gateway's H.248 for an-alyzing and operating the corresponded CIC. Since the form of theterminals used by the Mc interface is relatively fixed currently, youmay adopt the default configuration.





SET:NEID=11;

2. Create the TID analyzer. The command is ADD TIDANL.

Table 19 describes the main parameters in the ADD TIDANLcommand.

TABLE 19 PARAMETERS IN THE ADD TIDANL COMMAND

Parame-ter Name


NAME User alias

It is a mandatory parameter,ranging from 1 to 50characters. It may be thesame as the office name.

PREV TID analyzer index

It is an optional parameter.It is the global number ofthe current analyzer for TIDanalyzer entry to use, rangingfrom 1 to 255.

TIDPFX TID prefix It is an optional parameter witha default of TDM

TAG

Analysis result flag.Options includeUSER, TRUNK, RTP,ATM, ROOT andPCM+IDX.

It is an optional parameter,with a default of TRUNK (trunktype).

Example: “TDM_5/1” is atrunk terminal form. “TDM” isthe TID prefix, “_” is the PCMseparation mark, “5” is the PCMnumber, "/” is the IDX (timeslot index) is the separationmark, and “1” is the time slotnumber

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 adefault of 1, indicating that thePCM number starts from thefirst digit of the PCM flag.

PCMPOS2 PCM end location

It is an optional parameter,ranging from 0 to 255, with adefault of 0. Since there is aPCM flag, the End Location ismeaningless.

IDXPOS1 IDX start location It is an optional parameter,ranging from 0 to 255, with a



Parame-ter Name


default of 1, indicating that thetime slot number starts fromthe first digit of the IDX flag.

IDXPOS2 IDX end location

It is an optional parameter,ranging from 0 to 255, with adefault of 0. Since there is anIDX flag, the End Location ismeaningless.

Example: Create a TID analyzer with the following require-ments.


� TID index: 1

� Alias: MGW101


The command is:

ADD TIDANL:NAME="MGW101",PREV=1,TIDPFX="TDM",TAG=TRUNK,PCMSPR="_",IDXSPR="/",PCMPOS1=1,PCMPOS2=0,IDXPOS1=1,IDXPOS2=0;

END OF STEPS

Creating a TID Analyzer Entry


� The MGW topological node is configured.

� The TID analyzer configuration is completed.


Context Perform this procedure to configure a TID analyzer entry.



SET:NEID=11;

2. Create a TID analyzer entry. The command is ADD TIDENTR.

Table 20 describes the main parameters in the ADD TIDENTRcommand.



TABLE 20 PARAMETERS IN THE ADD TIDENTR COMMAND

ParameterName


ND GatewayIt is a mandatory parameter. It is thenode ID allocated by the topologicalnode configuration.

TIDENTID TID analyzerindex

It is a mandatory parameterassociating the TID analyzer IDspecified in the TID analyzerconfiguration.

TIDTPLID TID templatenumber

By default, the system alreadycreates a TID template whose ID is1. You may query it with the SHOWTIDTPL command.

NAME User Alias

It is a mandatory parameter witha length ranging from 0 to 50characters. It may be the same asthe office name.

Example: Create a TID analyzer entry with the following re-quirements.


� TID analyzer index: 1

� TID template ID: 1

� Alias: MGW101.


ADD TIDENTR:ND=101,TIDENTID=1,TIDTPLID=1,NAME="MGW101";

END OF STEPS

HLR Data ConfigurationOverview

TypicalNetworking

When ZXWN CS is interconnected with the HLR, the HLR is usuallyconnected to the MSCS in the TDM mode in the existing network.Figure 4 shows the typical networking between ZXWN CS and theHLR.



FIGURE 4 TYPICAL NETWORKING BETWEEN THE ZXWN CS AND THE HLR

Data Collection Before data configuration, it is supposed to complete collectingand negotiating the related data from the MSCS to the HLR office.Table 21 lists the data to be collected. The parameter values arejust examples. Input these parameters according to the actualcondition during the practical data construction procedure.

TABLE 21 MSCS-HLR INTERCONNECTION DATA COLLECTION


ZXWN MSCS signaling point code (24-bit) 3.11.1

HLR signaling point code (24-bit) 3.1.1

HLR number 8613907551

Signaling point code type 24-bit signaling point code

SP type SEP

Association type Direct connect

Signaling link code 0

Signaling E1 number E1 9

Start timeslot number of E1 16TS

Quantity of timeslots 1

Data Configura-tion Flow

Table 22 describes the data configuration flow of the HLR adjacentoffice.



TABLE 22 DATA FOR INTERCONNECTION WITH THE HLR


1 Creating a HLR AdjacentOffice ADD ADJOFC

2 Creating a Signaling Link Set ADD N7LKS

3 Creating an SPB-accessedSignaling Link ADD N7LNKE1

4 Creating a Signaling Route ADD N7ROUTE

5 Creating a Signaling Office ADD N7OFC

6 Creating IMSI Analysis ADD IMSIANA

7 Creating GT TranslationSelector ADD GTT

8 Creating GT Translator Data ADD GT

Generally, the following five types of GT numbers are configuredin ZXWN.

� Local office’s MSC/VLR number GT

� HLR number GT

� Mobile subscriber number (MSISDN) GT

� MSC/VLR number GT with interoffice handover

� IMSI-constructed GT

Here, whether to configure the last number in the E214 formatdepends on the specific result of "IMSI Number Analysis". Forexample, if MCC+MNC (such as 46000) in "IMSI Number Analysis"is configured as CC+NDC (such as 86139) in E214 format, the GTnumber in this E214 format should be configured here. If the IMSInumber analysis is configured as the E164 number in the HLT GTform in "IMSI Number Analysis", the corresponding GT number inthe E164 format should be configured here.

For the above four number forms, the rule to select GT is to startfrom the beginning so as to select this number's minimum prefixthat can identify different office directions for analysis, and to se-lect as few identifiable prefixes as possible so as to simplify the GTconfiguration.

Different carriers have different requirements on whether the GTor the DPC addressing mode is used for transferring the MAP andCAP messages between two signaling points. Some carriers re-quire transferring the MAP and CAP messages between the in-tra-province signaling points in the DPC addressing mode, andthe MAP and CAP messages between the extra-province signal-ing points in the GT addressing mode, and some carriers requiretransfer all the MAP and CAP messages in the GT addressing mode.In case of the DPC addressing mode, the STP has light load, butis configured with more data. In case of the GT addressing mode,the STP has heavy load, but are configure with less data.



Creating a HLR Adjacent Office


� The E1 line between the MSCS and HLR is well corrected.Meanwhile, the signaling interworking data is planned andnegotiated.

� The configuration of local office data is complete.



Context Creating the HLR adjacent office means configuring the basic in-formation for the HLR adjacent office.



SET:NEID=11;

2. Create a HLR adjacent office. The command is ADD ADJOFC.

Table 23 describes the parameters in the ADD ADJOFC com-mand.


ParameterName

ParameterDescription Instructions

SPCFMT Signaling point codeformat

Select TRIPLE_DEC(888/333 formatDec NumericCharacters).

SPCTYPE Signaling point codetype

Specify it according tothe SPC type of theadjacent office. In thiscase, select 24 (24bit signaling pointcode).

DPC Destination signalingpoint code

It is a mandatoryparameter. Setthe 24-bit signalingpoint code to thisHLR adjacent officeaccording to itssignaling point codetype.

OFCTYPE Adjacent Office Types SelectHLR/HLRe&AUC.



ParameterName


BANDFLAG

Broadband attribute,including:

� YES (Supportbroadbandattribute)

� No (Not supportbroadbandattribute)

Select No (Not supportbroadband attribute).

For example, create a HLR adjacent office with the followingrequirements.

� Office ID: 1

� Signaling point code: 3.1.1

� Signaling point code type: 24–bit

� Adjacent office type: HLR/HLRe and AUC

� Association type: Direct connection mode


ADD ADJOFC:ID=1,NAME="HLR",NET=1,OFCTYPE="HLR/HLRe"&"AUC",SPCFMT=TRIPLE_DEC,SPCTYPE=24,DPC="3.1.1",RC="25",ASSOTYPE=AM_SURE,SPTYPE=SEP,SSF=NATIONAL,SUBPROTTYPE=DEFAULT,TEST=YES,BANDFLAG=NO,PRTCTYPE=CHINA,CLST=65535,INFO="CIC_PCM",RELATEDOFC1=0;

END OF STEPS

Signaling Data Configuration

Creating a Signaling Link Set


� The adjacent office configuration is completed.

� The data configuration of local office is completed.

� The range of signaling link set is configured in the resourcemanagement.


Context Perform this procedure to configure a narrowband signaling link setto the adjacent office, including 64k signaling link set, 2M signalinglink set, N×64k signaling link set.

When configuring the signaling link set connected by TDM, youmay select N64, NN64, and N2M.



� 64k indicates that the narrow-band signaling link in this sig-naling link set only seizures one time slot on one E1 line, with64 Kbps bandwidth.

� N×64K indicates that the narrow-band signaling link in thissignaling link set seizures N consecutive time slots on one E1line (8≤n≤25).

� 2M indicates that the narrow-band signaling link in this signal-ing link set seizures all 31 time slots on one E1 line (time slot0 is unavailable), with 1.984Mbps bandwidth.



SET:NEID=11;

2. Create a signaling link set. The command is ADD N7LKS.

Table 24 describes the main parameters in the ADD N7LKScommand.

TABLE 24 PARAMETERS IN THE ADD N7LKS COMMAND

ParameterName

Parameter Descrip-tion Instruction

OFCID Direct-associated officeof the signaling link set

It is a mandatoryparameter. Type theadjacent office ID ofthis signaling link set,which is specified inthe adjacent officeconfiguration.

ID Signaling link set ID

It is a mandatoryparameter. Itdesignates the signalinglink set No. fordistinguishing signalinglink sets, ranging from1 to 1024.

NAME Alias

It is a mandatoryparameter describingthe name of thissignaling link set foreasy identification.

TYPE Signaling link set type

This parameter indicatesthe types of thesignaling links in thissignaling link set. SelectN64 for a 64K signalinglink, NN64 for ann×64K signaling link,and N2M for a 2Msignaling link.

LECM Link error revision, This parameter



ParameterName


including:

BASIC (basic errorrevision, transit delay ≤15 ms): all the signalinglinks use this methodfor relatively shorttransit delay, except forsatellite links.

PCR (Preventive CyclicRetransmission: transitdelay≥15 ms): Satellitelinks use this methodfor it has a relativelylong transit delay.

designates the errorcorrection method ofthe signaling links inthis set. In general,select BASIC. Ingeneral,BASICisselected when theline transit delay is lessthan 15ms, and PCR isselected when the linetransit delay is greaterthan 15ms.For a 2Msignaling link, BASICmust be selected. Thisparameter shall beconsistent with thatof the opposite endthrough negotiation.

Example: Create a signaling link set connected by HLR office104 with the following requirements.

� HLR office ID: 1

� Signaling link set No.: 1

� Group type: 64K narrowband link set

� Link error revision: Basic error revision

� Alias: HLR-1.


ADD N7LKS:OFCID=1,TYPE=N64,ID=1,LECM=BASIC,NAME="HLR-1";

END OF STEPS

Creating an SPB-Accessed Signaling Link


� The signaling link group configuration is completed.


Context Signaling link is the physical channel carrying signaling messages.The narrow-band signaling link used on the MSCS is an SPB-ac-cessed signaling link.



Note:

In order to evenly distribute the traffic load to an office on eachlink that is selected in the dynamic routing table correspondedby the SLC, usually the number of links in a link set to a direct-associated office is configured as 2n, namely, 2, 4, 8, or 16 linksare configured. Make sure that load onto each link is not too heavyto cause it breakdown.



SET:NEID=11;

2. Create an SPB-accessed signaling link. The command is ADDN7LNKE1

Table 25 describes the main parameters in the ADD N7LNKE1command.

TABLE 25 PARAMETERS IN THE ADD N7LNKE1 COMMAND

ParameterName


LKSID Signaling linkset ID

It is a mandatory parameter,designating the signaling linkset No. of this signaling link.It is associated with the ID ofthe signaling link set that isconfigured.

SLC Signaling LinkCode (SLC)

This parameter designates theSLC of this signaling link, rangingfrom 0 to 15. It needs tobe consistent with the SLC ofthe same signaling link of theopposite-end office.

MODULESignalingmanagementmodule No.

It is a mandatory parameter.Select a signaling module.Several signaling links of thesame office should be configuredto different physical boards.In addition, the signaling linksmanaged by each SMP moduleshould share load.

NAME Alias

It is a mandatory parameterdesignating the name ofthe signaling link for easyidentification, with a lengthranging from 1 to 50 characters.



ParameterName


SPBUNT SPB unitnumber

CPU CPU ID of SPB

It is a mandatory parameter.The CPU ID ranges from 1 to 4.Several signaling links of the sameoffice should be configured todifferent SPB boards. In addition,the signaling links processed bythe CPUs on SPB board shouldshare load.

E1 E1 number ofthe SPB board

This parameter designates thenumber of the E1 where thesignaling link is located, rangingfrom 9 to 25. By default, it isnumbered from 9

TS Start timeslotnumber of E1

64k signaling link: the time slotnumber of the signaling link is 16

N×64k signaling link: its starttime slot ranges from 1 to 31

2M signaling link: Its start timeslot is 1

TSNUM Quantity oftimeslots

Configure the number of the timeslots occupied by the signalinglink.

64K signaling link: Its time slotamount is 1.

N×64K signaling link: Its timeslot amount is N.

2M signaling link: Its time slotamount is 31.

INFO

Miscellaneousinformation,including:

E1: Thislink usesthe E1-typeinterface.

N64KT1:This link usesthe T1-typeinterface, with64K normalcoding mode.

I64KT1: Thislink usesthe T1-typeinterface, with64K reversalphase codingmode.

56KT1: Thislink usesthe T1-typeinterface, with54K codingmode.

Configure the interface type andcoding mode of this link. Ingeneral, it is an E1 link.



Example: Create an SPB-accessed signaling link with the fol-lowing requirements.


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


ADD N7LNKE1:LKSID=1,SLC=0,MODULE=3,NAME="HLR-1-1",ID=1,SPBUNT=721,CPU=1,E1=9,TS=16,TSNUM=1,LOOP=NO,INFO=E1,FCPLTHR=255;

END OF STEPS

Creating a Signaling Route


� The signaling link group configuration is completed.

� The range of signaling route ID is configured in the resourcemanagement.


Context The signaling routing configuration is used for specifying the sig-naling link set to be selected and the method when the signalingselects a route. The signaling route to a direct-associated officeonly contains the signaling link sets to this office. The signalingroute to a quasi-associated office contains one or two signalinglink sets to the intermediate office.



SET:NEID=11;

2. Create a signaling route. The command is ADD N7ROUTE.

Table 26 describes the main parameters in the ADD N7ROUTEcommand.



TABLE 26 PARAMETERS IN THE ADD N7ROUTE COMMAND

ParameterName


NAME AliasIt is a mandatory parameterdesignating a signaling routefor easy identification.

LKSID1 Signaling link set 1

The signaling route containsthe first signaling link set.Type the serial number of thesignaling link set 1.

LKSID2 Signaling link set 2

It is the second signalinglink set contained by thesignaling route. At leasteither LKSID1 or LKSID2is not equal to zero andcontains signaling links. Ifonly one signaling link setexists, type 0

ID Signaling routenumber

This parameter designatesthe serial number of thesignaling route, ranging from1 to 2000. When thereis only one signaling linkset, this parameter may beconfigured to be consistentwith the signaling link setnumber.

LPM

Arrangement modeof signaling linksets. Refer to Table27 for its options.

This parameter designatesthe rules that should beobeyed when the signalinglinks of two signaling linksets are sorted. When twolink sets have the samesignaling links, and the totalnumber is not more than16, RAND (random order) isrecommended

LPMIN

Arrangement modein a signaling linkset. Refer to Table27 for its options.

This parameter designatesthe rules that should beobeyed when the signalinglinks in a signaling link setare sorted. RAND (randomorder) is recommended

MANUAL

Sort manually,including NO(NeedNot Manual)and YES(NeedManual)

The parameter indicateswhether to manually sort thesignaling routes of the twolink groups

LINKS Link list

The maximum numberof instance is 16. Theformat is <INDEX>-<LINK>,representing the alignmentorder and link numberrespectively.



TABLE 27 ARRANGEMENT MODE OF SIGNALING SETS

Mode Meanings Instruction

RANDRandomarrangementmode

Random arrangement mode

SLS0 Select OnSLS_BIT0

Selecting links between twolink sets according to Bit 0 ofSLS







SLS01 Select OnSLS_BIT0-1

Selecting links between twolink sets according to Bits 0and 1 of SLS





Example: Create a signaling route with the following require-ments.

� Alias: HLR


� Signaling route No.: 1

� Other parameters: default.


ADD N7ROUTE:NAME="HLR",LKSID1=1,LKSID2=0,ID=1,LPM=RAND,LPMIN=RAND,MANUAL=NO;

END OF STEPS

Creating a Signaling Office


� The signaling route configuration is completed.




Context Perform this procedure for configuring the correspondence be-tween the destination signaling office and the signaling route.



SET:NEID=11;

2. Create a signaling office. The command is ADD N7OFC.

Table 28 describes the main parameters in the ADD N7OFCcommand.

TABLE 28 PARAMETERS IN THE ADD N7OFC COMMAND

ParameterName


ID Signaling route office

It is a mandatoryparameter. Type theadjacent office No. ofthe destination office

RT1

This parameterdesignates the serialnumber of the directroute to the destinationadjacent office.

It is a mandatoryparameter. Configurethe serial number of thedirect route to this office,ranging from 1 to 2000

RT2

Alternate route 1,indicating the serialnumber of the firstalternate route to thedestination adjacentoffice.

RT3

Alternate route 2,indicating the serialnumber of the secondalternate route to thedestination adjacentoffice. This parameteris configured when onlythe first alternate routeis already configured.

RT4

Alternate route 3,indicating the serialnumber of the thirdalternate route to thedestination adjacentoffice. This parameter isconfigured when only thesecond alternate route isalready configured.

This parameter rangesfrom 0 to 2000.Select up to threeavailable alternateroutes according to theactual conditions. Whenthere is no alternateroute, configure it as 0.

NAME Alias

It is a mandatoryparameter. Thisparameter designatesthe name of thesignaling office foreasy identification



Example: Create a signaling office to a HLR adjacent officewhose office ID is 1 and the direct-associated route number is1. The specific command is as follows.

ADD N7OFC:ID=1,RT1=1,RT2=0,RT3=0,RT4=0,NAME="HLR";

END OF STEPS

Creating IMSI Analysis


� The No. of the exchange to be configured is given.


Context The UE brings with an IMSI number in the E212 format when orig-inating a location update request. The MSC/VLR builds the GTaccording to this IMSI for addressing the HLR. The IMSI numberanalysis is used to convert the IMSI number to a number that canaddress to the HLR.

There are two types of analysis result indications: ISDN formatand HLR format.

1. ISDN

The corresponding number prefix in the IMSI is convertedinto specified analysis result, and the rest digits are addedbehind the analysis result. For example, if the analyzednumber is 46000, the network-accepted IMSI number is460001234567890, the corresponding Country Code (CC) is86 and the Network Destination Code (NDC) is 139. In theanalysis of ISDN mode, 46000 can be analyzed into 86139.This number is analyzed into 861391234567890. Based onthis, the typical application of this mode is to convert theMCC+MNC in the IMSI into the CC+NDC, and keep the restpart, thus forming the E214 number format.

2. HLR

The corresponding number prefix in the IMSI is converted intospecified analysis result, and the rest digits are deleted. Forexample, if the analyzed number is 46000, the conversion re-sult is HLR’s GT number 8613907551, and the network-ac-cepted IMSI number is 460001234567890. In the HLR mode,this IMSI number is analyzed into 8613907551234, namely theHLR’s GT number. Based on this, the typical application of thismode is to convert the IMSI headed by specific MCC+MNC intothe GT number of a HLR.



SET:NEID=11;

2. Create an IMSI analysis. The command is ADD IMSIANA.



Table 29 describes the parameters in the ADD IMSIANA com-mand.

TABLE 29 PARAMETERS IN THE ADD IMSIANA COMMAND

Parame-ters Explanation Instruction

IMSI IMSI prefix

It is a mandatory parameter,specifying the IMSI prefix tobe analyzed. It is an integer,consisting of 1~20 digits.

HDSTCODE Home destinationcode

It is a mandatory parameter,which is an integer consistingof 1~16 digits. It is thenumber converted from anIMSI number. It may be“CC+NDC” or “HLR’s GTnumber”. In this case, enterthe GT number of the HLR.

HDSTCO-DET

Destination codetype, includingHLR and ISDN.

In this case, enter HLR.

NAME Alias

It is an optional parameter,consisting of 1~50 characters.It is used to specificallydescribe an IMSI analysisrecord to make it easilyrecognized.

SM Short message ID Enter the default 0.

OPID Operator ID Enter the default 0.

INDADC Independent ADC Enter the default 0.

For example, create the IMSI number analysis with the follow-ing requirements.

� Analyzed number: 460001234

� Home destination code: 8613907551

� Analysis result: HLR

� Alias: HLR


ADD IMSIANA:IMSI="460001234",HDSTCODE="8613907551",HDSTCODET=HLR,NAME="HLR",SM=0,OPID=0,INDADC=NO;

END OF STEPS



SCCP Data Configuration

Creating GT Translation Selector




Context The GT translation selector and the GT translation data config-uration both belong to the SCCP data configuration. The SCCPdata configuration serves the SCCP routing. In the R4 system,the MAP signaling between such entities as MSCS/VLR and HLR inthe network is transferred through the SCCP. All the entities maybe directly connected, or forwarded by a signaling transfer point.When the SCCP receives messages from the MAP application layer,it will send, receive and forward these messages according to theroute labels in the messages. The SCCP is of two message routingmodes, GT routing and DPC+SSN routing.

These two routing modes are different when the STP exists be-tween the originating signaling point and the destination signalingpoint. The DPC+SSN routing mode requires that all the signal-ing points in the network (including originating signaling points,destination signaling points, and STP) can identify this destinationsignaling point code (DPC). The signaling is directly transferredthrough the MTP layer after reaching the intermediate node, with-out passing the SCCP layer. In this case, more DPC data are con-figured for the originating signaling point and STPs. The GT rout-ing method may be used in case that the originating SP and someSTPs do not know the final DPC of this signaling. In this address-ing method, when the signaling reaches the STP, the GT shouldbe translated into the destination signaling point, or the DPC ofSTP of the next hop GT translation at first through the SCCP, andthen messages are transferred to the MTP for transmission. In theGT routing mode, the originating signaling point only sends thesignaling to the STP of the next hop GT translation according tothe GT number prefix. The STP translates it and decides whetherto send it the next STP or the destination signaling point. In thiscase, less DPC data are configured for the originating signalingpoint and STPs.

Before configuring the GT translation data, configure the GT trans-lation selector to determine the basic attribute of the GT transla-tion. In general, two GT translation selectors are required, respec-tively corresponding to E164 and E214 coding plans. Pay attentionto the configurations of numbering plan, address attributes, coun-try code and bit length during configuration.



SET:NEID=11;

2. Create a GT translation selector. The command is ADD GTT.



Table 30 describes the parameters in the ADD GTT command.

TABLE 30 PARAMETERS IN THE ADD GTT COMMAND

ParameterName


GTT GT type

It is a mandatory parameter,raging from 1 to 4. When itis 1, the GT contains addressattributes. When it is 2, theGT contains translation type.When it is 3, the GT containstranslation type, numberingplan, and coding design.When it is 4, the GT containstranslation type, numberingplan, coding design, andaddress attributes. GT4 isselected by default

TT Translation type

It is a mandatory parameter,ranging from 0 to 255. It isthe translation type of theGT number, with the defaultvalue as 0

PLAN

Numbering plan,including

� NULL (idle)

� E.164(ISDN/phonenumberingplan)

� E.214(ISDN/mobilenumberingplan)

� RES(reserved)

� X.121 (Datanumberingplan)

� F.69 (Telexnumberingplan)

� E.210(Mari-time mobilenumberingplan)

� E.212 (Landmobilenumberingplan)

� Reserved(2),Re-served(8)Re-served (255):Reserved

It is a mandatory parameter.Select E.164 for the E164format, and select E.214for the E214 format. Forexample, if the mobilenumber is analyzed as HLR,select E.164 for GT analysisof this number. If the mobilenumber is analyzed as ISDN,select E.214 for GT analysisof this number



ParameterName


NATURE

Address attribute,including

� NULL(idle)

� SUB (addressattributes issubscribernumber)

� INT (addressattributes isinternationalnumber)

� NATRSV(addressattributesis nationalreservednumber)

� NATSIGN(addressattributes isnational validnumber)

� CAMEL(addressattributes isintelligentnetworkservicenumber)

� VACANT0,VA-CANT7 VA-CANT255: va-cancy

It is a mandatory parameter.Select INT

ID GT translationselector

It is an optional parameter,ranging from 0 to 1023. It isthe global number of the GTtranslation selector

CC Country codeIt is an optional parameter,consisting of 0~4 digits. It is86 in China

NMIN National minimumdigit length

They are optional parameters,which are integers, rangingfrom 1 to 20. Theyrespectively correspond to thenational minimum GT numberlength, and national maximumGT number length configuredin the GT translation dataconfiguration. In general, thenational minimum digit lengthis set to 5, while the nationalmaximum digit length is setto 15



ParameterName


NMAX National maximumbit length

IMINInternationalminimum digitlength

IMAXInternationalmaximum digitlength

They are optional parameters,which are integers, rangingfrom 1 to 20. Theyrespectively correspondto the international minimumGT number length, andinternational maximum GTnumber length configuredin the GT translation dataconfiguration. In general, theinternational minimum digitlength is set to 1, while theinternational maximum digitlength is set to 5

CTRL

GT translationattributes,including R_L(intercepting digitsfrom the numberto be analyzedfrom right to leftfor alignment,correspondingto the maximummatching policy),and L_R((interceptingdigits from thenumber to beanalyzed fromleft to rightfor alignment,correspondingto the minimummatching policy)

It is an optional parameter,with the default choice asR_L. Maximum Matchingmeans match the numberfrom right to left. Whenanalyzing a GT number,search the matched optionswith the maximum length.GT numbers are analyzed inthe descending order of theirlengths, facilitating reducingthe workload of GT dataconfiguration

NAME User alias

It is a mandatory parameter,consisting of 1~50 characters.

It is used to identify a GTtranslation selector to make iteasily recognized

For example, create a GT translation selector with the followingrequirements.

� GT type: 4

� Translation type: 0

� Numbering plan: ISDN/phone numbering plan

� Address attribute: international number

� GT translation selector ID: 1



� Alias: E164


ADD GTT:GTT=4,TT=0,PLAN=E.164,NATURE=INT,GTTOPT=0,ID=1,CC="86",NMIN=5,NMAX=9,IMIN=2,IMAX=5,CTRL=R_L,NAME="E164";

For example, create a GT translation selector with the followingrequirements.

� GT type: 4

� Translation type: 0

� Numbering plan: ISDN/mobile numbering plan

� Address attribute: international number


� Alias: E214


ADD GTT:GTT=4,TT=0,PLAN=E.214,NATURE=INT,GTTOPT=0,ID=2,CC="86",NMIN=5,NMAX=9,IMIN=2,IMAX=5,CTRL=R_L,NAME="E214";

END OF STEPS

Creating GT Translation Data



� The GT translation selector is configured.


Context The GT data are used for location update, call, and inter-officehandover. Configuring GT translation data should follow this prin-ciple: Understanding the service signaling flow and making clearthe signaling route. To response every message sent to the oppo-site end, the GT translation data both of the source address anddestination address of signaling must be configured at every endpoint or transfer point.

When configuring the location update data, the local office’s GTnumber is translated to office 0, namely, the local office, and theHLR’s GT number is translated to the HLR or the STP. Therefore,at least two types of the GT translation data are configured on theMSCS. In general, the following two kinds of GT translation dataare required.

E164 number: it requires configuring the local office’s MSC/VLRGT, MSISDN number, and MSC/VLR GT with location-area adjacentrelation.

E214 number: it requires configuring E214 format number corre-sponded by IMSI number (E212 format).





SET:NEID=11;

2. Create the GT translation data. The command is ADD GT.

Table 31 describes the parameters in the ADD GT command.

TABLE 31 PARAMETERS IN THE ADD GT COMMAND

ParameterName

ParameterDescription

Instruction

GT Called GT number

It is a mandatory parameter,consisting of 1~20 digits. It isused to query the destinationGT number of messagerouting

OPGT Calling GT number

It is an optional parameter,consisting of 0~20 digits. Itis the number of the virtualMSC where the subscriber islocated during GT translation.During GT routing, querywhere there are matched dataaccording to the VMSC wherethe subscriber is located andthe target GT number. If thereare matched data, performGT translation based on thematched data. If there isno matched data, performtranslation again based onthat the calling GT number is0

GTSL GT translationselector

It is a mandatory parameter,ranging from 0 to 1023. Selectthe GT translation selectorrespectively according toconfigured E164 and E214numbers

GTDI Number changeID

It ranges from 0 to 256,with the default value as0. It is the ID of flexiblepolicy template change. Thetarget GT number can beflexibly changed based onit. When the GT translationresult contains a new GT,this parameter does not takeeffect



ParameterName


Instruction

OFCIDS Office ID and polllist

It is a mandatory parameter.The number of instance is1~4 when office ID groupingis supported. The numberof instance is 1~16 whenoffice ID grouping is notsupported. The formatis <OFCID>-<SELNUM>,representing the office ID tobe polled and the number ofpoll respectively.

GRPWhether tosupport groupingof office ID

It is an optional parameter,with a default of NO

OFCGRP2

The office ID andpoll number of themultiple signalingpoints for thesecond group

It is an optional parameter.The number of instance is1~4 when office ID groupingis supported. The userdoes not need to type whenthe office ID grouping issupported. The formatis <OFCID>-<SELNUM>,representing the office ID tobe polled and the number ofpoll respectively.

OFCGRP3

The office ID andpoll number of themultiple signalingpoints for the thirdgroup


OFCGRP34

The office ID andpoll number of themultiple signalingpoints for thefourth group


SSN

Subsystem No.Refer to Table 32for the optionsinvolved

It is an optional parameter. Inthe GT routing mode, selectthe default value for SSN. Inthe DPC+SSN routing mode,select the corresponding SSN

NGT New GT number

It is an optional parameter,ranging from 0 to 20 ofcharacters. It represents thenew GT translation type.



ParameterName


Instruction

NTRNTYPE New GTtranslation type

It is an optional parameter,ranging from 0 to 255.It represents the new GTtranslation type.

TRNRLT

Whether thetranslation resultcontains DPCand SSN. Theoptions includesNULL (neitherDPC nor SSN is inthe result), DPC(containing DPCin the result), andSSN (containingSSN in the result)

It is an optional parameter. Inthe GT routing mode, selectthe default value for TRNRLT.In the DPC+SSN routingmode, select the DPC andSSN for TRNRLT

RTTYPE

Routing mode,including GT(routing basedon GT) and DPC(routing based onDPC+SSN)

It is an optional parameter. Ingeneral, select GT for directconnection, and DPC+SSNfor non-direct connection

NGTTAG

Attribute of thenew GT , includingthe followingoptions:

NGT (No newGT in the GTtranslationresult): The GTnumber in the GTtranslation resultis still the calledGT number.

NAI: The GTnumber in theGT translationresult is the newGT number in theNGT parameter,only containingNature Of AddressIndicator (NAI).

NTT: The GTnumber in theGT translationresult is the newGT number in theNGT parameter,only containingtranslation type.

NTTES: The GTnumber in the GTtranslation resultis the new GTnumber in theNGT parameter,only containing

It is an optional parameter.It is the attribute of thenew GT contained in the GTtranslation result. NGT(Nonew GT in the GT translationresult) is selected by default



ParameterName


Instruction

translation type,numbering plan,and coding design.

NTTNAI: The GTnumber in the GTtranslation resultis the new GTnumber in theNGT parameter,containingtranslation type,numbering plan,coding design,and NAI

SCCP

SCCP coding type,including:

INT (internationalcoding) andUSA(USA coding)

It is an optional parameter.It indicates the standard typereferred to by the SCCP codingin the GT translation result.The default value is INT

VGT

GT varyingwith differentoffice IDs,including NO (notsupported), andYES (supported)

It is an optional parameter,with NO as the default value

TT

TT conversion,including NO (notsupported), andYES (supported)

It is an optional parameter,with NO as the default value

NAME Alias The alias of the GT translationdata for easy memory.

TABLE 32 SSN

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

MSC Mobile switching center

EIR Equipment identity register



SSN Meaning

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 GMLCMAP

CAP CAP

GSMSCF_MAP GSMSCFMAP

SIWF_MAP SIWFMAP

SGSN_MAP SGSNMAP

GGSN_MAP GGSNMAP

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

For example, create the GT translation data with the followingrequirements.

� GT number: 8613907551


� Office poll: 1-1



� Subsystem’s SSN number: SCCP


ADD GT:GT="8613907551",GTSL=1,GTDI=0,OFCIDS="1"-"1",GRP=NO,SSN=NO_SSN,NTRNTYPE=0,TRNRLT="DPC"&"SSN",RTTYPE=GT,NGTTAG=NGT,SCCP=INT,VGT=NO,TT=NO,NPFLAG=NO,NPLAN=NULL,SRVTYPE=NULL;

END OF STEPS

STP Data ConfigurationOverview

TypicalNetworking

ZXWN CS may interconnect with the STP in one of the followingtwo ways.

� ZXWM MSCS is directly connected to the STP.

� The built-in SG of ZXWN MGW forwards the signaling.

In the current networking environment, the STP is usually directlyconnected to the ZXWN MSCS in the TDM mode. This section in-troduces this configuration method.

NetworkingDiagram

Figure 5 shows the typical networking between ZXWN CS and theSTP.

FIGURE 5 TYPICAL NETWORKING BETWEEN THE ZXWN CS AND THE STP

Data Collection Before data configuration, it is supposed to complete collecting andnegotiating the related data from the MSCS to the STP adjacentoffice. Table 33 lists the data to be collected. Where, the param-eter values are just examples. Enter these parameters according



to the actual condition during the practical data construction pro-cedure.

TABLE 33 MSCS-STP DATA COLLECTION


ZXWN MSCS signaling point code(24-bit) 3.11.1

STP signaling point code (24-bit) 3.2.1

Signaling point code type 24-bit signaling point code

SP type STP







Table 34 describes the configuration flow.

TABLE 34 MSCS-STP DATA CONFIGURATION FLOW


1 Creating an STP adjacentoffice ADD ADJOFC

2 Creating a signaling link setto the STP ADD N7LKS

3 Creating a signaling link tothe STP ADD N7LNKE1

4 Creating a signaling route tothe STP ADD N7ROUTE

5 Creating a signaling office tothe STP ADD N7OFC

6 Creating a GT translationdata ADD GT

� In the above configuration flow table, the SSN subsystem ofthe SCCP is generated automatically according to the adjacentoffice type specified in the adjacent office configuration. Youmay query the generated subsystem with the SHOW N7SSNcommand.

� In general, all the GT numbers except the local office are trans-mitted to the corresponding STP for forwarding, when the GTnumber is configured in the current network. In operationmethod, analyze the subdivided GT number in the local officeto the local office direction, and then analyze the smallest GT



prefix (such as 86139) in the network to the STP, thus greatlysimplify the working load of data configuration.

Creating an STP Adjacent Office


� The E1 line between the MSCS and the STP is well connected.Meanwhile, the signaling interworking data is planned and ne-gotiated.




Context Creating an STP adjacent office means configuring the basic infor-mation for the opposite STP office.



SET:NEID=11;

2. Create an STP adjacent office. The command is ADD ADJOFC.



Parame-ter Name


ID Office ID

It is a mandatory parameter,indicating the ID of the adjacentoffice, and ranging from 1 to3000. It is usually configuredas the exchange ID of theadjacent office during theall-network planning.

NAME AliasIt is a mandatory parameter.Enter a character string todescribe an STP adjacent office.

NET Network type

It is a mandatory parameter,indicating the network type ofthe SPC used for connectingthe local office to the adjacentoffice when the local officeis configured with severalSignaling Points (SP). Thedefault is the network type ofthis SP when there is only oneSP in the local office.



Parame-ter Name


OFCTYPE Adjacent OfficeTypes

Configure the adjacent officetype. Select MSCSERVER forthe STP adjacent office.

SPCFMT Signaling pointcode format

Select TRIPLE_DEC(888/333 format Dec NumericCharacters).

SPCTYPE Signaling pointcode type

Specify it according to the SPCtype of the adjacent office. Inthis case, select 24 (24 bitsignaling point code).

DPCDestinationsignaling pointcode

It is a mandatory parameter.Set the 24-bit signaling pointcode to this STP adjacent officeaccording to its signaling pointcode type.

RC Area code Indicates the local toll zonecode of the adjacent office

ASSOTYPE Association type Select AM_SURE (directconnection mode) in this case.

SPTYPE Signaling pointtype

If this signaling point forwardsmessages through this adjacentoffice, it is configured as STPor STEP. Otherwise, it isconfigured as SEP. In this case,select STP.

SSF Subservice type In this case, select National(National signaling point code).

BANDFLAG

Broadbandattribute,including:


� No (Notsupportbroadbandattribute)

Since the MSCS is connectedto the STP through the TDM,select NO (Not supportbroadband attribute).

PRTCTYPE Protocol type Select CHINA.

For example, create an STP adjacent office with the followingrequirements.

� Office ID: 2

� Signaling point code: 3.2.1

� Signaling point code type: 24-bit

� Adjacent office type: MSCSERVER

� Association type: Direct connection mode




ADD ADJOFC:ID=2,NAME="STP",NET=1,OFCTYPE="MSCSERVER",SPCFMT=TRIPLE_DEC,SPCTYPE=24,DPC="3.2.1",RC="25",ASSOTYPE=AM_SURE,SPTYPE=STP,SSF=NATIONAL,SUBPROTTYPE=DEFAULT,TEST=YES,BANDFLAG=NO,PRTCTYPE=CHINA,CLST=65535,INFO="CIC_PCM",RELATEDOFC1=0;

END OF STEPS

Signaling Data Configuration

Creating a Signaling Link Set to the STP


� The adjacent office is configured.


� The range of signaling link set is configured in the resourcemanagement.


Context Perform this procedure to add an MTP link set to the STP adjacentoffice.



SET:NEID=11;

2. Create a signaling link set to the STP adjacent office. The com-mand is ADD N7LKS.

Table 36 describes the parameters in the ADD N7LKS com-mand.

TABLE 36 PARAMETERS IN THE ADD N7LKS COMMAND

ParameterName


OFCID Office ID

It is a mandatory parameter,designating the adjacent officedirectly connected to this signalinglink set. It is the STP adjacentoffice ID specified in the ADDADJOFC command. Note thatevery adjacent office can only hasone link set.

TYPE Linkset type,including:

It is a mandatory parameter.Select N64, NN64, or N2M for



ParameterName


� N64K (64Knarrowbandsignalinglink set)

� NN64K(n×64Knarrowbandsignalinglink set)

� N2M (2Mnarrowbandsignalinglink set)

� ATM(Broadbandsignalinglink set)

� M2PA (M2PAsignalinglink set)

the signaling link set connectedthrough the TDM.

64k indicates that thenarrow-band signaling linkin this signaling link set onlyseizures one time slot on one E1line, with 64 Kbps bandwidth.

N×64K indicates that thenarrow-band signaling link inthis signaling link set seizures Nconsecutive time slots on one E1line (8≤n≤25).

2M indicates that the narrowbandsignaling links in this link setseizures all 31 time slots of oneE1 line, with the bandwidth as1.984Mbps.

Select ATM for the signaling linkset connected through ATM.

Select M2PA for the signaling linkset connected through IP.

Generally, select N64 for thesignaling link set to the STP.

This parameter should benegotiated by the two ends of theconnection for consistency.

ID Linkset ID

It is an optional parameter,designating the unique No. of thissignaling link set. It is numberedfrom 1. It is suggested to be thesame as the adjacent office ID.

LECM

Link errorrevision,including:

� BASIC(basic errorrevision)

� PCR (pre-ventive cy-clic retrans-mission)

BASIC (basic error revision,transit delay ≤ 15 ms): all thesignaling links except satellitelinks uses this method.

PCR (Preventive CyclicRetransmission: transit delay≥15ms): Satellite links use thismethod for it has a relatively longtransit delay.

In this case, select BASIC (basicerror revision).

NAME AliasIt is a mandatory parameter fornaming this signaling link set foreasy identification.

For example, create a signaling link set to the STP office withthe following requirements.

� STP office ID: 2

� Signaling link set number: 2

� Signaling link set type: 64K narrowband link set

� Link error revision: Basic error revision



� Alias: TOSTP


ADD N7LKS:OFCID=2,TYPE=N64,ID=2,LECM=BASIC,NAME="TOSTP";

END OF STEPS

Creating a Signaling Link to the STP


� The signaling link set configuration is complete.

� The SPB board configuration is complete.


Context Signaling links are the physical channels bearing signaling mes-sages. Configuring an MTP link to the STP means creating an sig-naling link borne on the E1.



SET:NEID=11;

2. Create an E1 signaling link. The command is ADD N7LNKE1.

Table 37 describes the parameters in the ADD N7LNKE1 com-mand.

TABLE 37 PARAMETERS IN THE ADD N7LNKE1 COMMAND

ParameterName


LKSID Linkset ID

It is a mandatory parameter,indicating the signaling linkset belonged by this signalinglink, and using the signalinglink set ID configured in theADD N7LKS command.

SLC Signaling linkcode

It is the link selecting code,ranging from 0 to 15. Onesignaling link set has up to16 narrowband signalinglinks. This parameter mustbe consistent with that ofthe opposite end office. Thesignaling link codes in thesame signaling link set cannotbe repeated.

MODULE SMP module No.

It is a mandatory parameter,designating the modulenumber of the SMP managingthis signaling link.



ParameterName


NAME AliasIt is a mandatory parameter,which is the alias customizedby the user.

ID Signaling Link

It is the global number of asignaling link. In general, itranges from 1 to 1000 fora narrowband signaling link,and from 1001 to 1920 for abroadband signaling link. Itis suggested that this numbershould be consistent with theadjacent office ID.

SPBUNT SPB unit No.

It is a mandatory parameter,designating the unit numberof the SPB board specified inthe physical configuration.

CPU SPB CPU

It is the CPU number of theSPB board that has fourCPUs. There is no fixedcorrespondence between theE1 No. of this signaling linkand the SPB subunit No..Since an SPB board provides16 E1 lines, and supports upto 64 64Kbps narrowbandlinks, the narrowband linksshould be distributed evenlyin the subunit.

E1 SPB E1

An SPB board has 16 E1 linesnumbered from 9 to 24. E1numbers are corresponded tothe E1 lines on the rear boardof the SPB board. Select theE1 number correspondingto the E1 line actuallyconnected.

TS SPB E1 time slotstart number

It is the start time slotnumber of the SPB E1 subunitused by this E1 signalinglink for outgoing the office.This parameter should beconsistent with the oppositeend through negotiation.It ranges from 1 to 31 for64Kbps signaling links.

TSNUM SPB E1 timeslotamount

It is the quantity ofconsecutive timeslots onthe E1 subunit of the SPBboard. These timeslots areused by this E1 signalinglink for outgoing the office.This parameter should beconsistent with that ofthe opposite end throughnegotiation. It is fixed as 1for 64Kpbs signaling link



ParameterName


LOOP Self loop In general, select NO.

INFO

Link info,including:

� E1: Thislink usesthe E1-typeinterface.

� N64KT1(supportT1-64 normalcode): Thislink usesthe T1-typeinterface, with64K normalcoding mode.

� I64KT1(supportT1-64invertedcode): Thislink usesthe T1-typeinterface, with64K inversecoding mode.

� 56KT1(supportT1-64K): Thislink usesthe T1-typeinterface, with56K codingmode.

Select E1.

For example, create a signaling link with the following require-ments.

� Signaling link set: 2

� Signaling link code: 0

� SMP module manages this signaling link: 3

� Unit No. of the SPB board: 721

� SPB E1: 10

� Initial time slot of E1: 16

� Number of time slot: 1


ADD N7LNKE1:LKSID=2,SLC=0,MODULE=3,NAME="TOSTP",ID=2,SPBUNT=721,CPU=1,E1=10,TS=16,TSNUM=1,LOOP=NO,INFO=E1,FCPLTHR=255;

END OF STEPS



Creating a Signaling Route to the STP


� The signaling link set configuration is complete.

� The range of signaling route ID is configured in the resourcemanagement.


Context The signaling routing configuration is used for specifying the sig-naling link set to be selected and the method when the signalingselects a route.



SET:NEID=11;

2. Create the signaling route to the STP. The command is ADDN7ROUTE.

Table 38 describes the parameters in the ADD N7ROUTE com-mand.

TABLE 38 PARAMETERS IN THE ADD N7ROUTE COMMAND

ParameterName


NAME Alias

It is a mandatory parameterfor naming a signaling officefor easy recognition, consistingof 1~50 characters.

LKSID1 Linkset 1 ID

It is an optional parameter,designating the first signalinglink set used by this route. Ituses the signaling link set IDspecified in the ADD N7LKScommand, ranging from 0 to1024.

LKSID2 Linkset 2 ID

It is an optional parameter,designating the secondsignaling link set used by thisroute. In general, a routeto a directly connected officeonly has one signaling linkset. Then, enter 0 for thisparameter. If there are twoSTPs between the local officeand a quasi-associated office,respectively select the ID of thesignaling link sets to these twoSTPs, ranging from 0 to 1024.

ID Signaling routeID

It is a mandatory parameter,designating the global numberof the signaling route, rangingfrom 1 to 2000. This parameter



ParameterName


is used for selecting a signalingroute in the signaling officeconfiguration.

LPM Line modeamong linkset

In general, select RAND, whichmeans that link sets are sortedat random. The links in thestatic route table are sorted byturns. For example, there aretwo signaling links, link a andlink b. The sorting method is:a, b, b, a, a, b, b, a, a, b, b, a,a, b, b, a.

LPMIN Line mode in alink set

In general, the RAND option isselected, namely being sortedat random.

MANUAL Sort manually Select NO (Need not manual).

For example, create a signaling route with the following re-quirements.


� Alias: TOSTP


� Signaling route No.: 2


ADD N7ROUTE:NAME="TOSTP",LKSID1=2,LKSID2=0,ID=2,LPM=RAND,LPMIN=RAND,MANUAL=NO;

END OF STEPS

Creating a Signaling Office to the STP


� The signaling route is configured.


Context Creating a signaling office to the STP means configuring the map-ping relationship between the destination signaling office and thesignaling route.



SET:NEID=11;

2. Create the signaling office to the STP. The command is ADDN7OFC.



Table 39 describes the parameters in the ADD N7OFC com-mand.

TABLE 39 PARAMETERS IN THE ADD N7OFC COMMAND

ParameterName


ID Signaling office ID

It is a mandatoryparameter, designatingthe destination officewhere the signaling arrivesfinally. It is the HLRadjacent office ID specifiedin the ADD ADJOFCcommand, ranging from 1to 3000.

RT1

This parameterdesignates theserial number ofthe direct routeto the destinationadjacent office.

It is a mandatoryparameter, designatingthe route preferentiallyselected for sending thesignaling message tothe destination office.It is the signaling routeID specified in the ADDN7ROUTE command,ranging from 1 to 2000.

RT2

Alternate route1, indicating theserial number of thefirst alternate routeto the destinationadjacent office.

It is an optional parameter.The first alternative routeis selected when thesignaling message fails toreach the destination officethrough the direct route.It is the signaling routeID specified in the ADDN7ROUTE command,ranging from 0 to 2000.

RT3

Alternate route2, indicating theserial numberof the secondalternate routeto the destinationadjacent office.

It is an optional parameter,corresponding to the linkroute already configured.It is configured only whenthe first alternative routeis configured, ranging from0 to 2000.

RT4

Alternate route 3,indicating the serialnumber of the thirdalternate routeto the destinationadjacent office.

It is an optional parameter,corresponding to the linkroute already configured.It is configured only whenthe second alternativeroute is configured,ranging from 0 to 2000.

NAME AliasIt is a mandatoryparameter for naminga signaling office.

For example, create a signaling office with the following re-quirements.




� Direct-connected route number: 2

� Alias: TOSTP


ADDN7OFC:ID=2,RT1=2,RT2=0,RT3=0,RT4=0,NAME="TOSTP";

END OF STEPS

Creating a GT Translation Data





Context The GT data are used for location update, call, and inter-officehandover. Configuring GT translation data should follow this prin-ciple: Understanding the service signaling flow and making clearthe signaling route. To response every message sent to the oppo-site end, the GT translation data both of the source address anddestination address of signaling must be configured at every endpoint or transfer point.

When configuring the location update data, the local office’s GTnumber is translated to office 0, namely, the local office, and theHLR’s GT number is translated to the HLR or the STP. Therefore,at least two types of the GT translation data are configured on theMSCS. In general, the following two kinds of GT translation dataare required.

E164 number: it requires configuring the local office’s MSC/VLRGT, MSISDN number, and MSC/VLR GT with location-area adjacentrelation.

E214 number: it requires configuring E214 format number corre-sponded by IMSI number (E212 format).



SET:NEID=11;






Parame-ter Name


Instruction

GT Called GT number

It is a mandatory parameter,consisting of 1~20 digits. It isused to query the destinationGT number of message routing

OPGT Calling GT number

It is an optional parameter,consisting of 0~20 digits. It isthe number of the virtual MSCwhere the subscriber is locatedduring GT translation. DuringGT routing, query where thereare matched data according tothe VMSC where the subscriberis located and the target GTnumber. If there are matcheddata, perform GT translationbased on the matched data.If there is no matched data,perform translation again basedon that the calling GT numberis 0


It is a mandatory parameter,ranging from 0 to 1023. Selectthe GT translation selectorrespectively according toconfigured E164 and E214numbers

GTDI Number change ID

It ranges from 0 to 256, withthe default value as 0. It is theID of flexible policy templatechange. The target GT numbercan be flexibly changed basedon it. When the GT translationresult contains a new GT, thisparameter does not take effect

OFCIDS Office ID and polllist

It is a mandatory parameter.The number of instance is1~4 when office ID groupingis supported. The numberof instance is 1~16 whenoffice ID grouping is notsupported. The formatis <OFCID>-<SELNUM>,representing the office ID to bepolled and the number of pollrespectively.

GRPWhether to supportgrouping of officeID

It is an optional parameter, witha default of NO



Parame-ter Name


Instruction

OFCGRP2

The office ID andpoll number of themultiple signalingpoints for thesecond group

It is an optional parameter. Thenumber of instance is 1~4 whenoffice ID grouping is supported.The user does not need to typewhen the office ID groupingis supported. The formatis <OFCID>-<SELNUM>,representing the office ID to bepolled and the number of pollrespectively.

OFCGRP3



OFCGRP34

The office ID andpoll number of themultiple signalingpoints for the fourthgroup


SSN Subsystem No.

It is an optional parameter. Inthe GT routing mode, select thedefault value for SSN. In theDPC+SSN routing mode, selectthe corresponding SSN

NGT New GT number

It is an optional parameter,ranging from 0 to 20 ofcharacters. It represents thenew GT translation type.

NTRNTYPE New GT translationtype

It is an optional parameter,ranging from 0 to 255.It represents the new GTtranslation type.

TRNRLT

Whether thetranslation resultcontains DPCand SSN. Theoptions includesNULL (neitherDPC nor SSN is inthe result), DPC(containing DPCin the result), andSSN (containingSSN in the result)

It is an optional parameter. Inthe GT routing mode, select thedefault value for TRNRLT. In theDPC+SSN routing mode, selectthe DPC and SSN for TRNRLT



Parame-ter Name


Instruction

RTTYPE

Routing mode,including GT(routing basedon GT) and DPC(routing based onDPC+SSN)

It is an optional parameter. Ingeneral, select GT for directconnection, and DPC+SSN fornon-direct connection

NGTTAG

Attribute of the newGT , including thefollowing options:

NGT (No new GT inthe GT translationresult): The GTnumber in the GTtranslation result isstill the called GTnumber.

NAI: The GTnumber in the GTtranslation resultis the new GTnumber in theNGT parameter,only containingNature Of AddressIndicator (NAI).

NTT: The GTnumber in the GTtranslation resultis the new GTnumber in theNGT parameter,only containingtranslation type.

NTTES: The GTnumber in the GTtranslation resultis the new GTnumber in theNGT parameter,only containingtranslation type,numbering plan,and coding design.

NTTNAI: The GTnumber in the GTtranslation resultis the new GTnumber in theNGT parameter,containingtranslation type,numbering plan,coding design, andNAI

It is an optional parameter. Itis the attribute of the new GTcontained in the GT translationresult. NGT(No new GT inthe GT translation result) isselected by default



Parame-ter Name


Instruction

SCCP



It is an optional parameter.It indicates the standard typereferred to by the SCCP codingin the GT translation result. Thedefault value is INT

VGT

GT varying withdifferent office IDs,including NO (notsupported), andYES (supported)

It is an optional parameter, withNO as the default value

TT

TT conversion,including NO (notsupported), andYES (supported)

It is an optional parameter, withNO as the default value

NAME Alias The alias of the GT translationdata for easy memory.


� GT number: 861390010


� Office poll: 2-1



ADD GT:GT="861390010",GTSL=1,GTDI=0,OFCIDS="2"-"1",GRP=NO,SSN=SCCP,NTRNTYPE=0,TRNRLT="DPC"&"SSN",RTTYPE=GT,NGTTAG=NGT,SCCP=INT,VGT=NO,TT=NO,NPFLAG=NO,NPLAN=NULL,SRVTYPE=NULL;

END OF STEPS

SCP Data Configuration(Destination Network)Overview

TypicalNetworking

In the existing networks, the SCP is usually connected with theMSCS (SSP) through the STP in the signaling network. The pro-tocol stack structure at both the MSCS side and the SCP side areCAP/TCAP/SCCP/MTP. Figure 6 shows the networking diagram.



FIGURE 6 NETWORKING BETWEEN THE ZXWN CS AND THE SCP

Data Collection Before data configuration, it is supposed to complete collectingand negotiating the related data from the MSCS to the SCP office.Table 41 lists the data to be collected. The parameter values arejust examples. Input these parameters according to the actualcondition during the practical data construction procedure.





STP Signaling point code type 24-bit signaling point code

SP type STP






SCP GT 8613907552

CAMEL version CAMEL3

Definition of SCP service key Service key values of varioussubscribers


The SCP adjacent office data configuration contains the followingthree parts.

1. Creating a direct-connected link to the STP.



2. Creating the GT translation data to the SCP.

3. Creating intelligent service data.

Table 42 describes the SCP adjacent office data configuration flow.

TABLE 42 MSCS-SCP DATA CONFIGURATION FLOW



2 Creating a signaling link setto STP ADD N7LKS

3 Creating an MTP Link to theSTP ADD N7LNKE1



6 Creating a signalingsubsystem ADD N7SSN

7 Creating GT translationselector ADD GTT

8 Creating GT translation datato the SCP ADD GT

9 Creating the CAMELconfiguration ADD CAMEL

10 Creating CAMEL accesssubscription information ADD CAINFO

11 Creating called numberanalysis ADD TPDNAL

12 Creating interconnectionconversion for service keys ADD SVRTRANSKEY

13 Creating tone keys on theMGW tone board ADD TONESVC

Creating a Signaling Subsystem




Context Perform this procedure for configuring a No.7 signaling subsys-tem. According to the subsystem, the lower-layer signaling is dis-tributed to the upper-layer service module for processing.



In general, a subsystem is automatically generated during the ad-jacent office configuration. In this networking system, since SCPis forwarded through STP, configuring SCP adjacent office data isnot required. Therefore, it is required to create the subsystemmanually on the MML Terminal of NMS system.



SET:NEID=11;

2. Create a signaling subsystem. The command is ADD N7SSN.

Table 43 describes the parameters in the ADD N7SSN com-mand.

TABLE 43 PARAMETERS IN THE ADD N7SSN COMMAND

ParameterName


OFCID Office ID

Enter the office IDcorresponded by thesignaling point. 0represents the localoffice ID.

SSN Signaling pointsubsystem.

In this case, selectSSP_SCP.

ID N7SSN ID

This parameter identifiesthe serial number of thissubsystem, ranging from0 to 32784.

TAG With backup SSN Select No (Withoutbackup SSN) by default.

NAME AliasThe name of this signalingsubsystem to make iteasily recognized.

For example, create a subsystem with the following require-ments.

� Office ID: 0

� Signaling point subsystem: SSP_SCP

� Subsystem ID: 1

� Alias: SCPSSN


ADD N7SSN:OFCID=0,SSN=SSP_SCP,ID=1,TAG=NO,NAME="SCPSSN";

END OF STEPS








Context Create the SCP GT data. The GT of the SCP is sent to the SCCPlayer of the STP office for it to convert the GT into the DPC + SSNof the SCP for addressing.



SET:NEID=11;




ParameterName


GT Called GT number

It is a mandatoryparameter, consistingof 1~20 digits. It is usedto query the destinationGT number of messagerouting


It is a mandatoryparameter, ranging from0 to 1023. Select theGT translation selectorrespectively accordingto configured E164 andE214 numbers


It ranges from 0 to 256,with the default value as0. It is the ID of flexiblepolicy template change.The target GT numbercan be flexibly changedbased on it. When theGT translation resultcontains a new GT, thisparameter does not takeeffect



ParameterName


OFCIDS Office ID and poll list

It is a mandatoryparameter. The numberof instance is 0~3000when office ID grouping issupported. The numberof instance is 1~64 whenoffice ID grouping is notsupported. The formatis <OFCID>-<SELNUM>,representing the officeID to be polled andthe number of pollrespectively.

GRP Whether to supportgrouping of office ID

It is an optionalparameter, with a defaultof NO

OFCGRP2

The office ID andpoll number of themultiple signalingpoints for the secondgroup

It is an optionalparameter. The numberof instance is 1~4 whenoffice ID grouping issupported. The user doesnot need to type whenthe office ID grouping issupported. The formatis <OFCID>-<SELNUM>,representing the officeID to be polled andthe number of pollrespectively.

OFCGRP3



OFCGRP34

The office ID andpoll number of themultiple signalingpoints for the fourthgroup




ParameterName


SSN Subsystem No.

It is an optionalparameter. In the GTrouting mode, selectthe default value forSSN. In the DPC+SSNrouting mode, select thecorresponding SSN

NGT New GT number

It is an optionalparameter, ranging from0 to 20 of characters. Itrepresents the new GTtranslation type.

NTRNTYPE New GT translationtype

It is an optionalparameter, ranging from0 to 255. It representsthe new GT translationtype.

TRNRLT

Whether thetranslation resultcontains DPC andSSN. The optionsincludes NULL(neither DPC norSSN is in the result),DPC (containing DPCin the result), andSSN (containing SSNin the result)

It is an optionalparameter. In the GTrouting mode, select thedefault value for TRNRLT.In the DPC+SSN routingmode, select the DPCand SSN for TRNRLT

RTTYPE

Routing mode,including GT (routingbased on GT) andDPC (routing basedon DPC+SSN)

It is an optionalparameter. In general,select GT for directconnection, andDPC+SSN for non-directconnection

NGTTAG

Attribute of the newGT , including thefollowing options:

NGT (No new GT inthe GT translationresult): The GTnumber in the GTtranslation result isstill the called GTnumber.

NAI: The GT numberin the GT translationresult is the newGT number in theNGT parameter, onlycontaining NatureOf Address Indicator(NAI).

NTT: The GT numberin the GT translationresult is the newGT number in the

It is an optionalparameter. It is theattribute of the newGT contained in theGT translation result.NGT(No new GT in theGT translation result) isselected by default



ParameterName


NGT parameter,only containingtranslation type.

NTTES: The GTnumber in the GTtranslation resultis the new GTnumber in theNGT parameter,only containingtranslation type,numbering plan, andcoding design.

NTTNAI: The GTnumber in the GTtranslation resultis the new GTnumber in theNGT parameter,containingtranslation type,numbering plan,coding design, andNAI

SCCP



It is an optionalparameter. It indicatesthe standard typereferred to by theSCCP coding in theGT translation result. Thedefault value is INT

VGT

GT varying withdifferent office IDs,including NO (notsupported), and YES(supported)

It is an optionalparameter, with NOas the default value

TT

TT conversion,including NO (notsupported), and YES(supported)


NAME AliasThe alias of the GTtranslation data for easymemory.


� GT number: 8613907552


� Office poll: 2-1 (here, the office is STP)



ADD GT:GT="8613907552",GTSL=1,GTDI=0,OFCIDS="2"-"1",GRP=NO,SSN=SCCP,NTRNTYPE=0,TRNRLT="DPC"&"S



SN",RTTYPE=GT,NGTTAG=NGT,SCCP=INT,VGT=NO,TT=NO,NPFLAG=NO,NPLAN=NULL,SRVTYPE=NULL;

END OF STEPS

Creating the CAMEL Configuration




� The support capability of local office is configured as "NULL" inthe local office mobile data configuration.

� The No.7 signaling subsystem of the local office is generatedproperly. (Query it with the SHOW N7SSN command.)

Context Creating the CAMEL configuration is to make the intelligent sub-scriber subscribed OCSI in the HLR properly trigger the IN service,and make and receive a call.



SET:NEID=11;

2. Create the CAMEL configuration. The command is ADDCAMEL.

Table 45 describes the parameters in the ADD CAMEL com-mand.

TABLE 45 PARAMETERS IN THE ADD CAMEL COMMAND

ParameterName


VER

CAMEL phase,including:

� None: Notsupported

� CAMEL1: SupportCAMEL1




It is an optionalparameter. The CAMELversion supported bythe local office mustbe consistent with thatsupported by the SCP.



ParameterName


CNMACT

Approach of highversion CAMELsubscription info,including:

� REJ (Reject)

� Ignore (Ignore)

Type the default valueREJ (REJ).

C1ACT

Approach of CAMEL1subscription info,including:

� REJ (Reject)

� Ignore (Ignore)

� ACPT (Accept)

Select ACPT, by default.

INAPTYPE INAP protocol type Select CHINA, bydefault.

For example, create the CAMEL configuration with the followingrequirements.

� CAMEL phase: CAMEL3

� Approach of high version CAMEL subscription information:REJ (reject)

� Approach of CAMEL1 subscription information: ACPT (ac-cept)


ADD CAMEL:VER=CAMEL3,CNMACT=REJ,C1ACT=ACPT,INAPTYPE=CHINA;

END OF STEPS

Recharge and Query Configuration

Creating CAMEL Access Subscription Information


� The No. of the exchange to be configured is known.


� The support capability of local office is configured as "NULL" inthe local office mobile data configuration.

� The No.7 signaling subsystem of the local office is generatedproperly. (Query it with the SHOW N7SSN command.)

Context The access code of the call service can trigger the intelligent net-work service.





SET:NEID=11;

2. Create the CAMEL subscription information. The command isADD CAINFO.

Table 46 describes the main parameters in the command.

TABLE 46 PARAMETERS IN THE ADD CAINFO COMMAND

ParameterName


CAMELIDX CAMEL informationindex

It is a mandatory parameter,which is an integer,ranging from 1 to 255.It is used to set theintra-system number ofthis configuration for usingin the configuration of thenumber analysis result. Itis not to be repeated withany other.

CIC Carrier identitycode

It is a mandatory parameter,consisting of 1~6 numericcharacters.

SCPSCP address(Country code +National Number)

It is a mandatory stringparameter with a lengthranging from 1 to 16 digits.It is the GT number ofthe SCP. It must be in theinternational format.

SKEY External servicekey

It is a mandatory parameter,which is an integer, rangingfrom 1 to 4294967295. It isuniquely identify the serviceafter the negotiation withthe SCP.

NAME Alias

It is a mandatory parameter,consisting of 1~50characters. It is usedto describe the CAMELaccess subscription type tomake it easily recognized.

ID CAMELconfiguration ID

It is an optional parameter,which is an integer, rangingfrom 1 to 65535.



ParameterName


NUMPLAN

Numbering plan,including:

� E164(ISDN/phonenumberingplan E164)

� X121 (Datanumberingplan X121)

� F69 (Telegraphnumberingplan F69)

It is an optional parameter.Select E164.

VER

CAMEL phase,including:

� None: Notsupported

� CAMEL1:SupportCAMEL1




It is an optional parameter.This parameter is set afterthe negotiation with theSCP. Currently, the versionCAMEL3 is frequently used.

DCH

Default callhandling,including:

� HOLD (Holdcall)

� RELEASE(Release call)

It is an optional parameter.Configure it according to theactual service requirements.Select HOLD by default.

For example, create the CAMEL access subscription informationwith the following requirements.

� CAMEL index: 1

� SCP address: 8613907552

� External service key: 1

� Alias: PPS

� Number plan: ISDN/phone numbering plan E164




ADD CAINFO:CAMELIDX=1,CIC="111",SCP="8613907552",SKEY=1,NAME="PPS",NUMPLAN=E164,VER=CAMEL3,DCH=HOLD;

END OF STEPS

Creating Called Number Analysis




� The CAMEL access subscription information is configured.

� The number analyzer entry is configured.

Context The subscriber must dial special service access number to triggerthe IN services, and then the system performs the number analy-sis. If the number analysis result is the IN service, the IN serviceflow is triggered. Therefore, in the ZXWN MSCS system, the num-ber analysis result corresponded by the called number must beconfigured as the IN service type. In this way, the IN service canbe triggered.



SET:NEID=11;

2. Create the called number analysis. The command is ADDTPDNAL.

Table 47 describes the parameters in the ADD TPDNAL com-mand.

TABLE 47 PARAMETERS IN THE ADD TPDNAL COMMAND

ParameterName


ENTR Analyzer entry

It is a mandatory parameter,which is an integer, rangingfrom 1 to 1000. Select thecorresponding analyzer entryof the analyzed numberprefix. This analyzer entry isconfigured by the ADD ENTRcommand.

DIGIT AnalyzedNumber

It is a character string,consisting of 0~9, *, #, D, orE.



ParameterName


NAME Alias

It is a mandatory parameter,consisting of 0~50 characters.It is used to specificallydescribe the called numberanalysis to make it easilyrecognized.

CAT Call service types

It is an optional parameter,with a default of NULL. It isused to specify the service typetriggered by this number, anddetermine the direction of thiscall. Select an IN service type.Select SSP in this case.

RST1 Number analysisresult 1

It is an optional integer-typeparameter, ranging from 0 to2147483647. Keep the default,because this configuration doesnot take effect here.


It is an optional integer-typeparameter, ranging from 0 to255. Select the CANELIDX(CAMEL information index)already configured in theCAMEL access subscriptioninformation.


It is an optional integer-typeparameter, ranging from 0to 2147483647. Select theCANELIDX (CAMEL informationindex) already configured inthe CAMEL access subscriptioninformation.

CHAINAL Chain analysisindex

It is used to specify theanalysis index number of therouting chain. This parametermust be defined by the ADDCHAINAL command at first.Then it can be indexed here.This parameter takes effectonly when the call service typeis outgoing service (includingvarious outgoing services).

RNLEN MNP routingnumber length

It is an optional parameter.Enter an integer ranging from0 to 40.



ParameterName


MINLEN Minimumnumber length

It is an optional parameter,which is an integer rangingfrom 0 to 255, with a defaultof 3. It is used to specify theminimum digit length of thecalled number. If the callednumber is shorter than thislength, the call failure occurs.In general, it is configured as6.

MAXLEN Maximumnumber length

It is an optional parameter,which is an integer rangingfrom 0 to 255, with a defaultof 20. It is used to specify themaximum digit length of thedialed number. If the callednumber exceeds this length,the call failure occurs. Ingeneral, it is configured as 11.

For example, create the called number analysis for the SSPrecharge query service with the following requirements.


� SN of number analyzer entry: 1

� Service type: SSP

� Number analysis result 1: 1


ADD TPDNAL:ENTR=1,DIGIT="13800138000",NAME="Recharge Service",SPECRST=0,SPECIDX=0,CAT=SSP,RST1=1,RST2=0,RST3=0,CHAINAL=0,RNLEN=0,MINLEN=3,MAXLEN=20,OVLYPRI=NO,REL=NO,NET=1,NAT=DEF,OPDDICONT=NO,TPDDICONT=NO,OPDDI=0,TPDDI=0,OPDLYDDI=0,TPDLYDDI=0,DDIOVERB=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=INVALID,CALLSERVPRILVL=INVALID,RERTS=0,INCHAIN=NO,BICT=NO,ICT=0,ICTT=10,GNM=NORMAL,STBILL=INVALID,HOPDAS=0,MCA=NO,IVVR=NO,WANTL=0,IMSCENTR=NO;

END OF STEPS

Configuration Related to IntelligentTone Play

The data related to the basic tone and the intelligent tone are cre-ated during the tone-related configuration is created in batches.



The intelligent tone play requires attention to the configuration ofservice keys. Service key divides into the internal service keys andthe external service keys. External key code is delivered by theSCP, while internal service key code is the corresponded internalservice code.

Therefore, the intelligent tone play configuration includes the in-terconnection conversion configuration of external service keysand the service key configuration of the MGW tone board.

The internal service keys of the ZXWN MSCS are described in Table48.

TABLE 48 INTERNAL SERVICE KEYS

Service Service Key Value

Basic services 1

PPS services 2

VPMN services 3

17951 IP services 4

Mobile phone rechargeable card services 5

Calling/called party paid services 6

Mobile Eight Hundred services 8

Zone– and time-dependent services 41

Creating Interconnection Conversion for ServiceKeys


� The conversion of service key to service tone ID is created inbatches on the MSCS.


Context Creating the CAMEL tone play data is to configure the mappingrelationship between the internal and external service keys, thusto convert the external service key into the internal one. After theintelligent service is triggered, the MSCS can implement the ser-vice processing flow properly, and the MGW can play the intelligentservice tone correctly.



SET:NEID=11;

2. Create the interconnection conversion for service keys. Thecommand is ADD SVRTRANSKEY.



Table 49 describes the parameters in the ADD SVRTRANSKEYcommand.

TABLE 49 PARAMETERS IN THE ADD SVRTRANSKEY COMMAND

ParameterName


ID Configuration ID

It is an optionalinteger-type parameter,ranging from 0 to4294967295. This IDis used inside the system.It is not to be repeated withany other.

SVCKEYService key coding.Refer to Table 50 forthe options involved.

It is a mandatoryparameter. Select itaccording to the actuallyconfigured service type.

NAME Alias

It is a mandatoryparameter, consistingof 1~50 characters. Itis used to describe anservice-key interconnectionconversion to make it easilyrecognized.

SCPTYPE SCP type

It is an optionalinteger-type parameter,ranging from 0 to 255. Itidentifies the SCP type.Currently, it is configuredas 0.

TABLE 50 SERVICE KEY CODES

Options Meanings

TRDT Traditional services

PPS PPS services

VPMN VPMN services

17951IP 17951IP services

MBCARD Handset voucher card services

PAY Calling/called payment services

MB800 Mobile 800 services

SMSPPS SMSPPS

IVC New voucher service tone

IGWVPMN IGWVPMN services

IGWPPS IGWPPS services



Options Meanings

UPTANN1.2 Universal one number

ONS One Number

ES Universal in students service

IPVN2 IPVN2

CLTM Cell and time division service

IPZHTC IP direct-bus service

LTIC All-purpose IC service

MS Universal in multi-cities

121V1 Uniform showing incoming call

ACC_200 ACC_200

200V1 Changing number acknowledgment serv-ice

RC Different phone handling tone

ACC_300 ACC_300

VOT VOT

VPN VPN

UPT UPT

FPH FPH

For example, create a service-key interconnection conversionwith the following requirements.

� External service key code: 11

� Service key code: PPS service

� Alias: PPS service

� ID: 1

� SCP type: 0


ADD SVRTRANSKEY:EXSVCKEY=11,SVCKEY=PPS,NAME="PPS Service",ID=1,SCPTYPE=0;

END OF STEPS

Creating Tone Keys on the MGW Tone Board


� The corresponded MRB unit is created on the MGW.




Context Perform this procedure for configuring the service keys on theMGW tone board.



SET:NEID=11;

2. Create a service key on the tone board. The command is ADDTONESVC.

Table 51 describes the parameters in the ADD TONESVC com-mand.

TABLE 51 PARAMETERS IN THE ADD TONESVC COMMAND

Parame-ter Name


UNIT Tone unit number

It is a mandatory integer-typeparameter, ranging from 1 to2000. Select the MRB unitnumber of the intelligent tone.

SUNIT Tone subunitnumber

It is a mandatory integer-typeparameter, ranging from 1 to255. Enter the TONE subunitNo. of the MRB.

SKEY1 Service key 1

SKEY2 Service key 2

SKEY3 Service key 3

SKEY4 Service key 4

SKEY5 Service key 5

SKEY6 Service key 6

It is an optional integer-typeparameter, ranging from 0 to65535. Configure the internalservice key delivered by theSCP corresponded by this toneresource.

NAME Alias

It is a mandatory parameter,consisting of 1~50 characters.It is used to describe atone unit to make it easilyrecognized.

For example, create the service key on the tone board with thefollowing requirements.

� Tone unit number: 1209

� Subunit number: 9




ADD TONESVC:UNIT=1209,SUNIT=9,SKEY1=1,SKEY2=1,SKEY3=1,SKEY4=1,SKEY5=1,SKEY6=1,NAME="SVC1";

END OF STEPS

SMC Data ConfigurationOverview

TypicalNetworking

In the existing networks, the SMC is usually connected to the MSCSthrough the STP in the signaling network. The protocol stacks atthe MSCS and the SMC sides both use the MAP/TCAP/SCCP/MTPmethod. The MAP protocol is employed between the MSCS andthe SMC. This protocol may be borne either on the TDM or theIP. In general, the current networking mode uses the TDM bearer.Figure 7 shows the networking diagram.

FIGURE 7 NETWORKING BETWEEN ZXWN CS AND SMC

Data Collection Before data configuration, it is supposed to complete collectingand negotiating the related data from the MSCS to the SMC office.Table 52 lists the data to be collected. The parameter values arejust examples. Input these parameters according to the actualcondition during the practical data construction procedure.





ZXWN MSCS signaling point code (24-bit) 3.11.1


STP Signaling point code type 24-bit signaling pointcode

SP type STP




Start timeslot number of E1 16 TS


SMC GT 8613907553


Table 53 describes the data configuration flow of the SMC adjacentoffice.

TABLE 53 DATA CONFIGURATION FLOW OF SMC ADJACENT OFFICE



2 Creating a signaling link setto the STP ADD N7LKS

3 Creating a signaling link tothe STP ADD N7LNKE1



6 Creating GT translation datato the SMC ADD GT

7 Modifying VLR-supportedSservices SET VLRSRVEN

8 Modifying mobile data oflocal office SET MSCCFG








Context Perform this procedure to configure the SMC GT data. The GT ofthe SMC is sent to the SCCP layer of the STP office, and the SCCPlayer of the STP office converts the GT into the DPC + SSN, andthen deliver it to the MTP layer for addressing.



SET:NEID=11;


Table 54 describes the parameters in the ADD GTT command.


ParameterName


GT Called GT number

It is a mandatoryparameter, consistingof 1~20 digits. Itis used to query thedestination GT numberof message routing

GTSL GT translation selector

It is a mandatoryparameter, rangingfrom 0 to 1023. Selectthe GT translationselector respectivelyaccording to configuredE164 and E214numbers


It ranges from 0 to256, with the defaultvalue as 0. It is theID of flexible policytemplate change. Thetarget GT number canbe flexibly changedbased on it. When theGT translation resultcontains a new GT, thisparameter does nottake effect



ParameterName


OFCIDS Office ID and poll list

It is a mandatoryparameter. Thenumber of instanceis 0~3000 whenoffice ID grouping issupported. The numberof instance is 1~64when office ID groupingis not supported.The format is<OFCID>-<SELNUM>,representing the officeID to be polled andthe number of pollrespectively.

GRP Whether to supportgrouping of office ID

It is an optionalparameter, with adefault of NO

OFCGRP2

The office ID and pollnumber of the multiplesignaling points for thesecond group

It is an optionalparameter. The numberof instance is 1~4 whenoffice ID grouping issupported. The userdoes not need to typewhen the office IDgrouping is supported.The format is<OFCID>-<SELNUM>,representing the officeID to be polled andthe number of pollrespectively.

OFCGRP3

The office ID and pollnumber of the multiplesignaling points for thethird group




ParameterName


OFCGRP34

The office ID and pollnumber of the multiplesignaling points for thefourth group


SSN Subsystem No.

It is an optionalparameter. In theGT routing mode, selectthe default value forSSN. In the DPC+SSNrouting mode, selectthe corresponding SSN

NGT New GT number

It is an optionalparameter, rangingfrom 0 to 20 ofcharacters. Itrepresents the newGT translation type.

NTRNTYPE New GT translation type

It is an optionalparameter, rangingfrom 0 to 255. Itrepresents the new GTtranslation type.

TRNRLT

Whether the translationresult contains DPCand SSN. The optionsincludes NULL (neitherDPC nor SSN is inthe result), DPC(containing DPC inthe result), and SSN(containing SSN in theresult)

It is an optionalparameter. In theGT routing mode,select the defaultvalue for TRNRLT. Inthe DPC+SSN routingmode, select the DPCand SSN for TRNRLT

RTTYPE

Routing mode,including GT (routingbased on GT) andDPC (routing based onDPC+SSN)

It is an optionalparameter. Ingeneral, select GTfor direct connection,and DPC+SSN fornon-direct connection



ParameterName


NGTTAG

Attribute of the new GT, including the followingoptions:

NGT (No new GT in theGT translation result):The GT number in theGT translation resultis still the called GTnumber.

NAI: The GT number inthe GT translationresult is the newGT number in theNGT parameter, onlycontaining NatureOf Address Indicator(NAI).

NTT: The GT number inthe GT translationresult is the newGT number in theNGT parameter, onlycontaining translationtype.

NTTES: The GT numberin the GT translationresult is the newGT number in theNGT parameter, onlycontaining translationtype, numbering plan,and coding design.

NTTNAI: The GTnumber in the GTtranslation result isthe new GT numberin the NGT parameter,containing translationtype, numbering plan,coding design, and NAI

It is an optionalparameter. It is theattribute of the newGT contained in theGT translation result.NGT(No new GT in theGT translation result) isselected by default

SCCP


INT (internationalcoding) and USA(USAcoding)

It is an optionalparameter. It indicatesthe standard typereferred to by theSCCP coding in the GTtranslation result. Thedefault value is INT

VGT

GT varying withdifferent office IDs,including NO (notsupported), and YES(supported)




ParameterName


TT

TT conversion,including NO (notsupported), and YES(supported)


NAME AliasThe alias of the GTtranslation data foreasy memory.


� GT number: 8613907553


� Office poll: 2-1 (here, the office is STP)



ADD GT:GT="8613907553",GTSL=1,GTDI=0,OFCIDS="2"-"1",GRP=NO,SSN=SCCP,NTRNTYPE=0,TRNRLT="DPC"&"SSN",RTTYPE=GT,NGTTAG=NGT,SCCP=INT,VGT=NO,TT=NO,NPFLAG=NO,NPLAN=NULL,SRVTYPE=NULL;

END OF STEPS

Modifying VLR-Supported Services




Context For details about VLR-supported services, refer to ZXWN MSCSMSC Server Data Configuration Guide. Here we only modify therelated parameters for the VLR to support the MO/MT SMS ser-vices.



SET:NEID=11;

2. Modify the VLR-supported services to make the VLR supportingthe MO/MT SMS.

SET VLRSRVEN:TELESRV="TSMS_MTPP"&"OSMS_MOPP";



Where, TSMS_MTPP means MT SMS, while OSMS_MOPPmeans MO SMS.

END OF STEPS

Modifying Mobile Data of Local Office




Context For details, refer to “Local Office Data Configuration” in ZXWNMSCS MSC Server Data Configuration Guide. Here, we only modifythe related parameters to make the local office support the SMSservice.



SET:NEID=11;

2. Perform this procedure for modify the mobile data of the localoffice to make it support the SMS service. The command is asfollows.

SET MSCCFG:ENTAG="SMS";

Where, The parameter SMS means that the local office sup-ports the SMS service.

END OF STEPS

PSTN/2G MSC (M3UA)Data ConfigurationOverview

TypicalNetworking

TUP/ISUP signaling is used between ZXWN MSCS and PSTN/MSC.The signaling from MSCS to MGW uses the IP bearer, and MGWimplements the signaling transfer between the IP bearer and theTMD bearer. In the existing network, ZXWN MSCS is usually in-terconnected with the opposite switch in the M3UA mode. Figure8 shows the networking structure and interface protocols.



FIGURE 8 INTERCONNECTION BETWEEN ZXWN MSCS AND PSTN/MSC

Data Collection Before data configuration, it is supposed to complete collecting therelated data of MSCS-to-MGW, and MGW-to-PSTN/MSC. Table 55and Table 56 list the data to be collected. The parameter valuesare just examples. Input these parameters according to the actualcondition during the practical data construction procedure.

TABLE 55 DATA FOR INTERCONNECTION WITH THE MGW


Real interface address of ZXWN MSCS 192.168.1.11

Real interface address of ZXWN MGW 192.168.1.31


Signaling point code (24-bit) of ZXWNMGW (SG) 3.31.1

SCTP port No. of ZXWN MSCS (client) 3001

SCTP port No. of ZXWN MGW (server) 3001

TABLE 56 DATA FOR INTERCONNECTION WITH THE PSTN/MSC OFFICE


Signaling point code of the PSTN/MSCswitch 3.28.1

Inter-office signaling type ISUP

CIC code of the junction circuit 0~31


This section introduces the data configuration on the MSCS foradding a PSTN/2G MSC adjacent office under the precondition thatthe H248 data between the MGW and the MSCS are configured,and that the MGW is successfully registered to the MSCS. Table



57 describes the configuration flow of the PSTN/2G MSC adjacentoffice data.

TABLE 57 CONFIGURATION FLOW OF PSTN/2G MSC ADJACENT OFFICEDATA


1 Creating 2G MSC/PSTNadjacent office ADD ADJOFC

2 Creating a DT trunk group ADD TG DT

3 Creating a PCM system ADD SPCM

4 Creating an outgoing route ADD RT

5 Creating an outgoing route set ADD RTS

6 Creating an outgoing route link ADD CHAIN

ADD SCTPCONN

ADD ASP

ADD AS7

Creating the associations andthe M3UA data switched by thesignaling

ADD M3UART

8 Creating the SIO-locating-AS ADD SIOLOCAS

Creating 2G MSC/PSTN AdjacentOffice


� The E1 line between the MGW and the 2G MSC/PSTN is wellconnected. Meanwhile, the signaling interworking data isplanned and negotiated.




Context Perform this procedure to configure the basic information of the2G MSC/PSTN adjacent office.



SET:NEID=11;

2. Create a 2G MSC/PSTN adjacent office. The command is ADDADJOFC.





ParameterName


ASSOTYPE

Association type,including:

� AM_SURE(directconnectionmode)

� AM_QUASI(half directconnectionmode)

� AM_NONE(noneconnectionmode).

Select AM_QUASI.

BANDFLAG

Broadbandattribute,including:


� No (Notsupportbroadbandattribute)

Select NO.

OFCTYPE Adjacent OfficeTypes

If the adjacent office is 2GMSC, select MSCSERVERor GMSCSERVERaccording to its functions.If the adjacent office isPSTN, select PSTN.

For example, create a 2G MSC adjacent office with the followingrequirements., with the , , , and the . The 24-bit signaling pointcoding mode and the quasi-associated mode are adopted.

� Office ID: 28

� Network type: 1

� User alias: TO2GMSC

� Destination SPC: 3.28.1

� Adjacent office type: GMSCSERVER

� Association type: half direct connection mode


ADD ADJOFC:ID=28,NAME="2G MSC",NET=1,OFCTYPE="GMSCSERVER",SPCFMT=TRIPLE_DEC,SPCTYPE=24,DPC="3.28.1",RC="25",ASSOTYPE=AM_SURE,SPTYPE=STEP,SSF=NATIONAL,SUBPROTTYPE=DEFAULT,TEST=YES,BAND



FLAG=NO,PRTCTYPE=CHINA,CLST=65535,INFO="CIC_PCM",RELATEDOFC1=0;

END OF STEPS

Configuration Related to Trunk andRoute

Creating a DT Trunk Group



� The adjacent office pointed by the trunk group is created.

� The range of the trunk group number is configured in the re-source management configuration.


Context Perform this procedure to create a DT trunk group.



SET:NEID=11;

2. Create a DT trunk group by executing command ADD TG DT.

Table 59 describes the parameters in the ADD TG DT com-mand.

TABLE 59 PARAMETERS IN THE ADD TG DT COMMAND

ParameterName


TG Trunk group ID

It is a mandatoryparameter. It is usedto define a trunk group,and needs to be planned inthe resource managementsystem in advance

OFCID of the office wherethe trunk groupbelongs

It is a mandatoryparameter. It is used tospecify the correspondingoffice of the trunk group.This parameter must bedefined by command ADDADJOFC at first. Then itcan be indexed here



ParameterName


MODULE Module where thetrunk group belongs

It is a mandatoryparameter. It indicatesa service module. Differenttrunk groups to the sameoffice need to be allocatedto different CMP modules

NDNode No. of the MGWwhere the trunk groupbelongs

It is a mandatoryparameter. Select the MGWtopology node connectedwith the 2G MSC/PSTNnode

NAME User alias

It is an optional parameter,consisting of 0~50characters. It is usedto specifically describe atrunk group to make iteasily recognized

SIGLINE

Inter-office line signalidentification. Optionsinclude:

� BSC: BSC GroundCircuit

� TUP: InterofficeCommon ChannelSignaling TUP

� ISUP: InterofficeCommon ChannelSignaling ISUP

� DLC1: InterofficeChannelAssociatedSignalingDL/DC(1)

� R2: R2 Signaling

� BICC: BICC Type

� ANU: ANUSignaling

� SORMUP: SORMUPSignaling

It is an optional parameter.It is used to identify the linetype of this trunk. Selectit according to inter-officesignaling. For the Aiinterface, select ISUP] orTUP

KIND

Trunk group types,including the followingthree types:

IN (incoming trunkgroup): Indicatesthat the local officeprocesses theincoming calls fromthe peer-end office.

OUT (outgoing trunkgroup): Indicates thatthe local office onlyprocesses the outgoing

It is an optional parameter.If BSC is selected for theinter-office line signalidentification, it must beconfigured to BIDIR



ParameterName


calls to the peer-endoffice.

BIDIR (Two-waytrunk group):Indicates that the localoffice processes boththe incoming callsfrom the peer-endoffice and the outgoingcalls to the peer-endoffice

BWAY

Bearer establishmentdirection, including thefollowing three types:

NODIR: Theinter-office beareris established withoutdirection.

BACK: The inter-officebearer is establishedbased on the backwardmode.

FORWD: Theinter-office beareris established basedon the forward mode

It is an optional parameter.Select NODIR for DT trunkgroups

THD Overload controlthreshold

It is an optional parameter,ranging from 0 to 100,with a default of 100. Thisparameter takes effectwhen levels of congestionoccur and load control isrequired

CICSEL

Circuit selectingmodes, including:

MIN: Every time whenthe system selects atrunk circuit, it alwaysbegins with the circuitwith the minimumnumber. This modecan implement thepreferred plan of trunkcircuits.

MAX: Every time whenthe system selects atrunk circuit, it alwaysbegins with the circuitwith the maximumnumber. This modecan implement thepreferred plan of trunkcircuits.

CYC: Every time whenthe system selectsa trunk circuit, italways begins with thecircuit next to the one

It is an optional parameter.It is used to specify thetrunk circuit selecting policyof the system within thistrunk group, with a defaultof CYC. If this No.7 trunkgroup is a two-way trunkgroup, it is recommendedto set the circuit selectingmode to ODD/EVEN modeto prevent contentionwhen two exchanges selectcircuits



ParameterName


previously selected.Suppose the numbersof the trunk circuitsin a trunk group inascending order are“TKC0, TKC1, …. ,TKCn”. If TKC0 isselected at the firsttime, the system willselect the trunk circuitin the order of “TKC0®TKC1®…®TKCn®TKC0®TKC1®…®TKCn”.

ODD: Every time whenthe system selects atrunk circuit, it alwaysselects the circuit withan odd number.

EVEN: Every timewhen the systemselects a trunk circuit,it always selects thecircuit with an evennumber.

IDLE: Every timewhen the systemselects a trunk circuit,it always selects theidlest circuit.

BUSY: Every timewhen the systemselects a trunk circuit,it always selects thebusiest circuit

DAS DAS for the callednumber

It is an optional parameter.It is used to analyzethe called number inan incoming call. Thisparameter must be definedby command ADD DASat first. Then it can beindexed here

Example: Create a DT trunk group to the 2G MSC office withthe following requirements:

� Trunk group ID: 28

� ID of the office where the trunk group belongs: 28

� User alias: DT28

� No. of the CMP module where the trunk group belongs: 4

� MGW topology node No.: 101

� Other parameters: Adopt the default values.


ADD TG DT:TG=28,OFC=28,MODULE=4,ND=101,NAME="DT28",SIGLINE=ISUP,KIND=BIDIR,BWAY=NODIR,THD



=100,CICSEL=ODD,DAS=0,SIPDAS=0,OPDAS=1,PREDAS=0,DDI=0,OPDDI=0,MINNAT=0,MAXNAT=26,MININT=0,MAXINT=26,INREG=INVALID,OUTREG=INVALID,COLEN=10,BUSYRATE=100,ROAMDAS=0,Q850CCIDX=0,SMENTERID=0,MLPPDM=4294967295,DISINDEX=0;

END OF STEPS

Creating a PCM System



� The DT trunk group is configured.


Context The PCM system management data associate the resources on thegateway with the signaling on the MSCS.



SET:NEID=11;

2. Create a PCM system by executing command ADD SPCM.

Table 60 describes the parameters in the ADD SPCM com-mand.

TABLE 60 PARAMETERS IN THE ADD SPCM COMMAND

ParameterName


TG

No. of the trunkgroup wherethe PCM systembelongs

It is a mandatory parameter,which is an integer, rangingfrom 1~1000. Select thetrunk group where this PCMsystem belongs from the listof configured trunk groups. Itis used to specify the trunkgroup invoking this PCMsystem. This parameter isassociated with the trunkgroup No. in command ADDTG ATM, ADD TG DT, ADDTG PRA, and ADD TG RTP

PCM PCM system No.

It is a mandatory parameter.It is a parameter forinterconnection with thepeer-end office. If theconfigured PCM systembelongs to the inter-officetrunk, the PCM system No. ofthe same circuit between twooffices must be the same.



ParameterName


When the inter-office lineidentification of a trunk groupis TUP or ISUP, the PCMsystem No. ranges from 0 to127.

When the inter-office lineidentification of a trunk groupis BICC, the PCM system No.ranges from 0 to 5999.

When the inter-office lineidentification of a trunk groupis BSC or ANU, the PCMsystem No. ranges from 0 to2047

NUM Number of createdPCM systems

It is an optional parameter. IfPCM systems belong to a DTtrunk group, this parameterneeds not be configured. IfPCM systems belong to a RTPor ATM trunk group, selectthe number the created PCMsystems

MGWPCM

PCM No. in theMGW

The correspondingtrunk group caninvoke the PCMresources betweenthe start PCM No.in the MGW and theend PCM No.

It is an optional parameter.If the PCM system belongsto a RTP or ATM trunk group,this parameter needs not beconfigured. If the PCM systembelongs to a DT trunk group,select the corresponding PCMNo. in the MGW

NAME User alias

It is an optional parameter,consisting of 1~50 characters.It is used to specificallydescribe the PCM systemconfiguration to make iteasily recognized

E1 E1 identification

It is an optional parameter,consisting of 1~50 characters.For DT trunk groups,describes the E1 with anycharacters, which can be setto “DTB/SDTB unit No.-E1No.”

DDFDigital DistributionFrame (DDF)location description

It is an optional parameter,consisting of 1~50 characters.For DT trunk groups, the DDFlocation description can be setto “Frame No.-Row No.-PortNo.”

Example: Create a PCM system to the BSC office with the fol-lowing requirements:

� No. of the trunk group where the PCM system belongs: 28



� PCM system No.: 1

� PCM No. in the MGW: 1–3


ADD SPCM:TG=28,PCM=1,NUM=3,MGWPCM="1"-"3",INFO=65535;

END OF STEPS

Creating an Outgoing Route



� The range of outgoing route ID is configured in the resourcemanagement.


Context Configuring outgoing routes make every trunk group correspondto an outgoing route.



SET:NEID=11;

2. Create an outgoing route by executing command ADD RT.

Table 61 describes the parameters in the ADD RT command.

TABLE 61 PARAMETERS IN THE ADD RT COMMAND

Parame-ter Name


RT Route No.

It is a mandatory parameter,which is an integer, rangingfrom 1~2000. It exclusivelyidentifies a route. To facilitatemanagement, the route No. isconfigured to be consistent withthe trunk group No.

TG Trunk group No.

It is a mandatory parameter,corresponding to the trunkgroup No. in the trunk groupconfiguration

DDI

Called numbertransform indexduring outgoingcalls

It is an optional parameter, whichis an integer ranging from 0 to2048, with a default of 0. Thecalled number is transformedaccording to this index duringoutgoing calls. This index has noinfluence on the incoming callsthrough this trunk



Parame-ter Name


OPDDI

Calling numbertransform indexduring outgoingcalls

It is an optional parameter, whichis an integer ranging from 0 to2048, with a default of 0. Thecalling number is transformedaccording to this index duringoutgoing calls. This index has noinfluence on the incoming callsthrough this trunk

DLPFX

Whether to deletethe prefix of thecalling numberduring outgoingcalls, includingNO and YES

It is an optional parameter,with a default of NO. If YES isselected, the prefix of the callingnumber (such as 0/00) will bedeleted during outgoing calls

NAME User alias It is an optional parameter,consisting of 0~50 characters.

Example: Create an outgoing route with the following require-ments.

� Route No.: 28

� Trunk group No.: 28

� User alias: Rout28


ADD RT:RT=28,TG=28,DDI=0,OPDDI=0,DLPFX=NO,NAME="ROUT28",HOPCNT=0,RERTS=0,CLISETIDX=65535;

END OF STEPS

Creating an Outgoing Route Set



� The outgoing route set number is created.


Context Perform this procedure to create an outgoing route set. Everyroute belongs to a route set, which contains up to 12 routes.



SET:NEID=11;

2. Creat an outgoing route group by executing command ADDRTS.

Table 62 describes the parameters in the ADD RTS command.



TABLE 62 PARAMETERS IN THE ADD RTS COMMAND

ParameterName


RTS Route group No.

It is a mandatory parameter,which is an integer, rangingfrom 1~3000. It is used toidentify a route group

NAME User alias

It is an optional parameter,consisting of 0~50 characters.It is used to specificallydescribe a route group to makeit easily recognized

RTPERRoute No. andload sharingproportion list

It is an optional parameter. Itis in the format of “No.-RouteNo.-Load sharing proportion.When the percentage is set to0, the poll mode is adopted.

SEQ: No., which is the locationof the route in the route group.

RTVAL: Route No., associatedwith the route group. Thisparameter must be definedby command ADD RT at first.Then it can be indexed here.

PERVAL: Load sharingproportion of each route in theroute group. If it is set to 0for all routes by default, theload is evenly allocated to eachroute

Example: Create an outgoing route group with the followingrequirements.

� Route group No.: 28

� User alias: Rout28

� Locaiton: 1

� Route No.: 28

� Percentage: 0


ADD RTS:RTS=28,NAME="ROUT28",RTPER="1"-"28"-"0";

END OF STEPS

Creating an Outgoing Route Link



� The range of outgoing route link ID is configured in the resourcemanagement.




Context Perform this procedure to configure an outgoing route link. Everyoutgoing route set belongs to an outgoing route link, which con-tains up to four route sets.



SET:NEID=11;

2. Creat an outgoing route chain by executing command ADDCHAIN.

Table 63 describes the parameters in the ADD CHAIN com-mand.

TABLE 63 PARAMETERS IN THE ADD CHAIN COMMAND

ParameterName


CHAIN Route chain No.

It is a mandatory parameter,which is an integer, rangingfrom 1 to 3000. It isused to define an outgoingroute chain. When it isconfigured in the numberanalysis configuration, itis associated to the routechain configured here

NAME User alias

It is an optional parameter,consisting of 0~50characters. It is usedto specifically describe aroute chain to make it easilyrecognized

PRND

Whether thepreference policyis supported in theMGW, including:

NO: When 2B occurs,the calls in thesame MGW arenot preferred, androuting is performedaccording to otherrouting policies of thesystem instead.

YES: When 2Boccurs, the calls inthe same MGW arepreferred

It is an optional parameter,with a default of YES. It isa policy for selecting therouging route



ParameterName


RTS1

No. of route group1, used to set theroute group withthe highest priorityin a route chainduring routing. Oneroute chain can beconfigured with atmost 4 route groups

RTS2

No. of route group 2,used to set the routegroup with the level-2priority in a routechain during routing.One route chain canbe configured with atmost 4 route groups

RTS3


RTS4


It is an optional parameter.Select route groupsaccording to the priorityorder. Select route group 1fist. Only when the circuitsin route group 1 are usedup or all the circuits areunavailable, the circuitsin route group 2 can beselected. Only when thecircuits in route group 2 areused up or all the circuitsare unavailable, the circuitsin route group 3 can beselected

RTPLC Route Selection PolicyNumber

It is an optional parameter.Select the route selectionpolicy number configured inADD RTPLC command

TPDAS DAS for the callednumber

It is an optional parameter.It is used to analyzethe called number inan incoming call. Thisparameter must be definedby command ADD DASat first. Then it can beindexed here. It needs to beset only when “Inter-MGWroute chain” is set in thecalled number analysis. Thedefault value is 0

Example: Create an outgoing route chain with the followingrequirements.

� Route chain No.: 28

� User alias: RLink28



� No. of Route group 1: 28



ADD CHAIN:CHAIN=28,NAME="RLink28",PRINODE=YES,RTS1=28,RTS2=0,RTS3=0,RTS4=0,RTPLC=0,TPDAS=0;

END OF STEPS


Creating an SCTP


� The physical configuration of the SMP module is complete.

� The range of the SCTP ID is configured in the resource man-agement configuration.


Context The configuration of SCTP basic connection is used to configurethe basic information of the SCTP association.

Tip:

SCTP basic connection configuration requires using the real inter-face address or the loop-back IP address. If the IP protocol stackis configured before the configuration of the interconnection datawith MGW, configuring IP protocol stack again is not required. TheIP address of this real interface can be used directly when a newassociation is created. Different associations are distinguished bydifferent SCTP port numbers.



SET:NEID=11;

2. Create an SCTP. The command is ADD SCTPCONN.

Table 64 describes the parameters in the ADD SCTPCONNcommand.




Parame-ter Name


MODULE Module No.

It is a mandatory parameter,indicating the number of thesignaling module homed by thisSCTP association. Select the SMPmodule number. Each SMP cansupport up to 128 associations.The associations under the sameAS are required sharing loadon SMP modules as more aspossible.

OFCID SCTP oppositeoffice ID

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

PROT


� M2UA

� M2PA

� M3UA

� SUA

� H248

� BICC

� IUA

� DHCTRL

� SIP

� DIM

� V5UA

� H245

It is a mandatory parameter. It isused to identify the upper-layerprotocol type borne by the SCTPassociation. In general, M3UA isselected.M2UA is selected whenMGW transfers the signaling withthe M2UA mode.

ROLE

SCTP applicationattributes.Options include:

SVR: SCTP isused as server

CLT: SCTP is usedas client

It is a mandatory parameter. ForMc interface, MSCS is configuredas CLT, and MGW is configuredas SVR. For Nc interface, thisshould be negotiated by bothsides. For example, the smallsignaling point serves as CLT,and the big signaling point servesas SVR



Parame-ter Name



It is a mandatory parameter. Itdesignates the service addressof local end of this association,with a format of Local IPaddress type-VPN of local IPaddress-Local IP address

Local IP address type: IPv4 andIPv6;

VPN of local IP address: Rangfrom 0 to 65535;

Local IP address: the format isxxx.yyy.zzz.mmm

LOCPORT Local portnumber

It is a mandatory parameter. Itis the local SCTP port number ofthe association, ranging from 1to 65535.

REMADDR Opposite IPaddress

It is a mandatory parameter. Itdesignates the service address ofopposite end of this association,ranging from 1 to 65535.


It is a mandatory parameter. It isthe opposite SCTP port numberof the association, ranging from1 to 65535.

NAME AliasIt is a mandatory parameter witha length ranging from 1 to 50characters.

ID SCTP ID

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

For example, configure the SCTP connection between MSCS 30and MGW 31. Bearer protocol is M3UA, SCTP signaling process-ing module number is 3, local port number is 3001, oppositeport number is 3001, local IP address is 192.168.1.30, oppo-site IP address is 192.168.1.31, and SCTP association ID is 2.















ADD SCTPCONN:MODULE=3,OFCID=101,PROT=M3UA,ROLE=CLT,LOCADDR="IPv4"-"0"-"192.168.1.11",LOCPORT=3001,REMADDR="IPv4"-"0"-"192.168.1.31",REMPORT=3001,NAME="PSTN",ID=2,INSTRM=16,OUTSTRM=16,MAXRTRY=5,MAXRTO=500,MINRTO=50,INITRTO=100,HB=500,FIXNH=NO,SCTPMAXRTRYNUM=10,DELAYACK=20,MAXBURST=4,PRIMARYPATH=REMIP1,PMTU=0,BREAKTIME=0,PDTHRESH=0,MINCWND=0,PLTIMER=10,MPPLTHRD=2,DPLEN=MTU,CB=200;

END OF STEPS

Creating an ASP


� The SCTP association information is configured.

� The range of the ASP ID is configured in the resource manage-ment configuration.


Context ASP configuration defines the one-to-one relationship between theASP and the association.



SET:NEID=11;


Table 65 describes the parameters in the ADD ASP command.


Parame-ter Name


ASSOCID SCTP ID

It is a mandatory parameter, rangingfrom 1 to 2048

Type the association ID configured inthe SCTP connection configuration.

NAME Alias

It is a mandatory parameter, witha lengthen ranging from 1 to 50characters. It may be named with aformat of “Adjacent office alias-SCTPnumber”.

ID ASP ID It is an optional parameter, rangingfrom 1 to 2048.



Parame-ter Name


It is recommended to be consistentwith ASSOCID.

ISLOOP ASP self-loopID

It is an optional parameter. It is usedto set whether the ASP is self-looped.


ISLOCK ASP blockingflag

It is an optional parameter. It is usedset whether the ASP is in blockingstate.

Blocking is used for management.Select the default value NO

Example: Create the ASP between MSCS and MGW with thefollowing requirements.




� User alias: ISUP.

ADD ASP:ASSOCID=2,NAME="ISUP",ID=2,ISLOOP=NO,ISLOCK=NO;

END OF STEPS

Creating an AS


� The ASP configuration is complete.

� The range of the AS ID is configured in the resource manage-ment configuration.


Context AS configuration is used to configure the basic information for theapplication server.



SET:NEID=11;

2. Create the AS. The command is ADD AS.

Table 66 describes the parameters in the ADD AS command.



TABLE 66 PARAMETERS IN THE ADD AS COMMAND

ParameterName


PROTSupportedadaptation layerprotocols

It indicates the protocoltype of a bearer. In general,M3UA is selected accordingto the networking planning.It is configured as M2UAwhen MGW transfers thesignaling with M2UA mode.

ASPID ASP IDIt is associated with theASP ID configured in theASP configuration.

NAME AliasIt is a mandatoryparameter. The aliascustomized by the user.

ID AS ID

It is an optionalparameter. It is the uniqueidentification of the AS. Ingeneral, it is the same asthat of the ASP for easymemory. The parameterranges from 1 to 640

EXISTCTX Whether the routingcontext ID exists


It is an optional parameter.The routing context isunique in the network.This parameter mustbe consistent with theAS configuration of theopposite-end. Its defaultvalue is NO

ASTAG

Usage tag. Optionsinclude:

SGP

ASP

SRV (IPSP server)

CLT (IPSP client)


For Mc interface, MSCSgenerally serves asIPSP_Client, and MGWserves as IPSP_Server.When MGW acts as a SGW,the AS at the MSCS sideserves as ASP, and the ASat the SGW side serves asSGP.

For Nc interface, this shouldbe negotiated by bothsides. For example, thesmall signaling point servesas IPSP_Client, and the bigsignaling point serves asIPSP_Server.



ParameterName


ASUP

User typessupported by AS.Options include TUP,ISUP, BICC, H.248,ALCAPSCCP, PCA,NNSF and ALL

It is an optional parameter.It defines the upper-layeruser types supported bythe AS. Currently, there areeight types of users.

User type is not configuredwhen MGW transfers thesignaling with the M2UAmode

ASMD Service modessupported

It is an optional parameter.The supported servicemodes include:

� OVERRIDE(Over-ridemode)

� LOAD (Load sharemode).

In the over-ride mode,only one ASP is in theactivated statue. In thiscase, only one ASP needsbe configured. In theload sharing mode, NASPs should be configuredin the activated workingstatue, and K ASPs shouldbe configured in thedeactivated standby statue.

The value of N+K is notmore than the number ofASPs actually configured

SSN

Types of subsystem.Options includeNO_SSN (subsystemSSN 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 (intelligentperipherals),SMC, SSP_SCP,BSC_BSSAP_LE,MSC_BSSAP_LE,SMLC_BSSAP_LE,BSS_O_M_A ,BSSAP_A andRVE255.

Types of subsystemsupported by applicationserver (AS).



ParameterName


NVAL The N value in loadsharing mode

The parameter ranges from0 to 16.

The N+K should be equal tothe number of ASP underAS.

The N value indicates thatAS puts into use if N ASPsput into use.

Example: Create the AS between MSCS and MGW with thefollowing requirements.



� AS configuration ID: 2

� Supported user type: ISUP

� ASP ID: 2

� Client: MSCS

� Alias: ISUP


ADD AS:PROT=M3UA,ASPID="2",NAME="ISUP",ID=2,EXISTCTX=NO,ASTAG=CLT,ASUP="ISUP",ASMD=LOAD,NVAL=1,KVAL=0;

END OF STEPS



� The AS configuration is complete.

� The range of M3UA static route ID is configured in the resourcemanagement.


Context Creating an M3UA static route means configuring the mapping re-lationship between an M3UA static route and an AS.



SET:NEID=11;






ParameterName





MODE


� BYTURNS

� LOCAL

� NATURE









� AS ID: 2

� User alias: ISUP.


ADD M3UART:ID=2,ASID=2,MODE=BYTURNS,NAME="ISUP";

END OF STEPS



� The M3UA static route configuration is complete.





Context Where, a routing keyword describes the parameters and their val-ues of a group of No.7 signaling messages. The corresponding ASis selected according to the message attributes, serving the pur-pose of selecting route for messages.

The attribute of the message includes DPC+NET+OPC+SIO,where, DPC is the destination signaling point code, NET is thenetwork type, OPC is the originating signaling point code, andSIO is the service indicator octet.

The configuration of SIO-locating-AS is used to locate one serviceto a routing table that is maintained by the ASPs under the AS.Compared with the MTP data configuration of the traditional No.7signaling, the ASP configuration of the SCTP connection and M3UAis similar to the link logic and bearer information configuration inthe MTP configuration, the AS configuration of the M3UA is similarto the link set configuration in the MTP configuration, and the SIO-locating-AS configuration is similar to the signaling office ID androute configuration in the MTP configuration. The difference is thatthe IP route to one subscriber of one office is configured in oneSIO-locating-AS configuration record.



SET:NEID=11;


Table 68 describes the parameters in the ADD SIOLOCAScommand.


ParameterName


ID SIO-location-AS ID

It is an optional parameter,indicating the serial number ofSIO-locating-AS, ranging from 1 to4096. In general, it is the same asthe AS ID.

NAME Alias It is a mandatory parameter, whichis the alias customized by the user.



ParameterName


SIO

Serviceindication.Options include

� TUP

� ISUP

� BICC

� H.248

� ALCAP

� SCCP

� PCA

� NNSF

It is a mandatory parameter,indicating the subscriber typebelonged by the transmittedmessage. Different user types canbe located to the same AS underthe precondition that the MS mustsupport these user types

Select H.248 for Mc interface,BICC for Nc interface, SCCP forthe RNC or BSC office transferredthrough MGW, and TUP or ISUPfor the 2G MSC/PSTN officetransferred through MGW.

OFCIDDestinationadjacent officeID

It is a mandatory parameter,indicating the adjacent office IDcorresponded by the destinationsignaling point of the M3UA.It needs to associate with theadjacent office ID in the adjacentoffice configuration.

OPOFCIDOriginaladjacent officeID

It is the adjacent office IDcorresponding to the M3UAoriginating signaling point. If0 (indicating the local office)is selected, it indicates thatthe message is sent from thelocal office, and the routingcontext is routed according toDPC+NET+OPC+SIO. If 65535(invalid) is selected, it indicatesthat the OPC field is invalid, andthe routing context is routedaccording to DPC+NET+SIO

PCM PCM systemnumber

It is an optional parameter. Itranges from 0 to 65535, with adefault of 65535 (invalid).



It corresponds to the IDspecified in the M3UA staticroute configuration. RT1 is amandatory parameter. In general,RT1 is required. When theoptimum route mode is adopted,RT1 is set as an active route, andRT2 is set as a standby route.

Example: Create SIO-locating-AS between MSCS and 2G MSCwith the following requirements.

� 2G MSC office ID: 28

� Service indication: ISUP





ADD SIOLOCAS:ID=2,NAME="ISUP",SIO=ISUP,OFCID=28,OPOFCID=65535,PCM=65535,RT1=2,RT2=0;

END OF STEPS

BSC Data ConfigurationOverview

TypicalNetworking

BSSAP signaling is used between the ZXWN MSCS and BSC. Thesignaling from the ZXWN MSCS to the MGW uses the IP bearer, andthe MGW completes the signaling switching from the IP bearer tothe TMD bearer. The MGW provides the TDM bearer of the userplane, and the user data are transferred through PCM codes. Inthe existing networks, both the MSCS and the MGW usually usethe same 14-bit SPC for interworking with the BSC. The networkingdiagram is shown in Figure 9.

FIGURE 9 NETWORKING WITH BSC

Data Collection Before data configuration, it is supposed to complete collectingthe related data of MSCS-to-MGW, and MGW-to-BSC. Table 69 andTable 70 list the data to be collected. The parameter values arejust examples. Input these parameters according to the actualcondition during the practical data construction procedure.







Signaling point code (14-bit) of ZXWNMSCS 1.11.1




TABLE 70 DATA FOR INTERCONNECTION WITH THE BSC


BSC signaling point code 1.99.1

Inter-office signaling type BSSAP

CIC code of the junction circuit 0~31


This section introduces the data configuration on the MSCS foradding a BSC adjacent office under the precondition that the H248data between the MGW and the MSCS are configured, and that theMGW is successfully registered to the MSCS. Table 71 describes theBSC adjacent office data configuration flow.

TABLE 71 BSC ADJACENT OFFICE DATA CONFIGURATION FLOW


1 Creating a BSCadjacent office ADD ADJOFC

2 Creating BSC officedirection ADD BSCOFC

3 Creating a BSCtopology node ADD TOPO

4Creating the topologyrelationship betweenBSC and MGW

ADD RNCMGWTOPO

5 Creating a DT trunkgroup to the BSC ADD TG DT

6 Creating a PCMsystem ADD SPCM

7 Creating theassociations and the




ADD SCTPCONN

ADD ASP

ADD AS

M3UA data switchedby the signaling

ADD M3UART

8 Creating theSIO-locating-AS ADD SIOLOCAS

Office Direction and TopologyConfiguration

Creating a BSC Adjacent Office





Context Perform this procedure for configuring the basic information of theBSC adjacent office.



SET:NEID=11;

2. Create the BSC adjacent office. The command is ADD ADJOFC.





ParameterName


ID Office ID

It is a mandatory parameter,indicating the identificationnumber of the adjacent office,and ranging from 1 to 2048.It is usually configured as theexchange ID of the adjacentoffice during the all-networkplanning.


NET Network type

It is a mandatory parameter,indicating the network type ofthe SPC used for connectingthe local office to the adjacentoffice when the local office isconfigured with several SPs.

The default is the network typeof this SP when there is onlyone SP in the local office.

OFCTYPE Adjacent officetype

It is a mandatory parameter.

Type BSC in this case

SPCFMT SPC format Select TRIPLE_DEC

SPCTYPE SPC type

DPC SPC

It is a mandatory parameter.Specify it based on the SPCtype of the adjacent office. InChina, BSC adopts the 14-bitSPC.

RC Area code When the adjacent office typeis BSC, RC must be empty.

ASSOTYPE

Association type,including



� AM_NONE(n-one connectionmode)


Select AM_QUASI



ParameterName


SPTYPE

Signaling pointtype, including

� SEP

� STP

� STEP


Select SEP

SSF

Subservicefunction, including

� INTERNA-TIONAL (In-ternational sig-naling pointcode)

� INTERNA-TIONALSTANDBY(Internationalstandby sig-naling pointcode)

� NATIONAL(Nationalsignaling pointcode)

� NATIONALSTANDBY(Nationalstandbysignaling pointcode).

It is an optional parameter.In general, select NATIONALSTANDBY for BSC adjacentoffice.

TEST Test flag

It is an optional parameter, forsetting whether the MTP3 linkactively initiates the link testafter entering in the servicestatus.

It is selected by default.

BANDFLAG Broadbandattribute

It is an optional parameter.Select NO

PRTCTYPE

Protocol types,including:

� CHINA (China)

� ITU (Interna-tional Telecom-municationsUnion)

� ANSI(AmericanNationalStandardsInstitute).


CHINA and ITU are used forthe NO.7 signaling networkingof the ITU standards. ANSIis used for the No.7 signalingnetworking of the Americanstandards.



ParameterName


CLST Cluster ID

It is an optional parameter.The cluster number shouldbe configured in ADD CLST.The parameter ranges from0 to 65535, with a default of65535.

INFO

Office Info,including:

� CIC_PCM (CICusing PCMCode ModeStarts LoadControl)

� BLOCK(Manual BlockState)

� EVEN_CIC(OfficeControls EvenCIC if CICResourceCollision)

� CALLING(Allow CallingTransform)

� CALLED(Allow CalledTransform)

� MOD24_CIC(Mod 24 CICMode)

� TEST(Dynamic Test)

It is an optional parameter,with a default of CIC_PCM

RELATE-DOFC1 Related office ID It is an optional parameter,

ranging from 0 from 3000

INFOEX

Office extend info,including

� SIGBRDCST(SupportSignalingBroadcastMessage)

� MTP(HongkongMTP Standard)

� DUPU (Screen DUPUmessage)

� SUA_REC_DT1 (ReceiveSUA messageand handle




ParameterName


it as DT1message)

� SUA_SND-_DT1 (SendSUA messageand handleit as DT1messagewithout SN.)

� OPEN_TG-_RES (Openoutter trunkgroup re-source)

Example: Create a BSC adjacent office with the following re-quirements.

� BSC office ID: 99

� Network type: 2

� User alias: BSC99


� SPC type: 14-bit

� Sub-service function: National standby SPC

� Adjacent office type: BSC

� Association type: Quasi-associated mode.


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=NATIONALSTANDBY,SUBPROTTYPE=DEFAULT,TEST=YES,BANDFLAG=NO,PRTCTYPE=CHINA,CLST=65535,INFO="CIC_PCM",RELATEDOFC1=0;

END OF STEPS

Creating BSC Office Direction


� You know the ID of the exchange to be configured.

� The BSC adjacent office is created.


Context Perform this procedure to configure some additive attributes of theBSC adjacent office.





SET:NEID=11;

2. Create the BSC office direction. The command is ADD BSCOFC.

Table 73 describes the main parameters in the ADD BSCOFCcommand.

TABLE 73 PARAMETERS IN THE ADD BSCOFC COMMAND

ParameterName


BSCOFCID BSC office ID It is a mandatory parameterranging from 1 to 256.

MCC Mobile countrycode

It is a mandatory parameterwith the length ranging from 1to 3 characters.

MNC Mobile networkcode

It is a mandatory parameterwith a length ranging from 1to 3 characters.

INFO Service identifier

It is an optional parameter.Type it according to the actualconditions. In general, allthe options can be selected,except SUPCELLLOAD(Support load-based switch)and ALL (Support all).

SELTYPE

A interface loadshare mode,including

� EXCELLENT(excellentchoice priority)

� LOAD (loadshare priority)

It is an optional parameter.Select EXCELLENT in thiscase.

NAME AliasIt is an optional parameterwith a length ranging from 0to 50 characters.

RAS BSC officere-assignment

It is an optional parameter.Select YES or NO according tothe actual conditions

CICINMGW

MGW manage BSCCIC, includingoptions: NO(NO)and YES(YES)

The default is NO(NO)

BEARTYPE

BSC bearer type,including options:TDM(TDM),IPV4(IPV4) andIPV6(IPV6)

It is an optional parameter,with a default of TDM(TDM)



Example: Create the BSC office direction with the followingrequirements.


� Mobile country code: 460

� Mobile network code: 00

� Service identifier: "BSCRST"&"MSCRST"&"BSCRCIC"&"M-SCRCIC"&"BLOCKCIC"&"BLOCKCICG"&"UNBLOCKCIC"&"UNBLOCKCICG"&"RESINDN"&"CHARGEINDN"&"FLUXCON-TROL"&"BSCTRACK"&"MSCTRACK"&"QUEUEINDN"&"CALL-REBUILD"&"SUPCELLLOAD"&"UNBLOCKCICINS"&"SupCo-mID"&"SupEmlpp"&"SupChnNed"&"SupCIResMode"&"Su-pLCS"

� Alias: BSC99.


ADD BSCOFC:BSCOFCID=99,MCC="460",MNC="00",INFO="BSCRST"&"MSCRST"&"BSCRCIC"&"MSCRCIC"&"BLOCKCIC"&"BLOCKCICG"&"UNBLOCKCIC"&"UNBLOCKCICG"&"RESINDN"&"CHARGEINDN"&"FLUXCONTROL"&"BSCTRACK"&"MSCTRACK"&"QUEUEINDN"&"CALLREBUILD"&"SUPCELLLOAD"&"UNBLOCKCICINS"&"SupComID"&"SupEmlpp"&"SupChnNed"&"SupCIResMode"&"SupLCS",SELTYPE=EXCELLENT,NAME="BSC99",RAS=NO,CICINMGW=NO,CICATTR="TFRV1"&"THRV1"&"TFRV2"&"THRV2"&"TFRV3"&"THRV3"&"DFR14"&"DFR12"&"DFR6"&"DFR3"&"DHR6"&"DHR3"&"HSCSD14x2"&"HSCSD12x2"&"HSCSD6x2"&"HSCSD14x4"&"HSCSD12x4"&"HSCSD6x4"&"HSCSD12x6"&"HSCSD6x6",BEARTYPE=TDM,PROTYPE=PRIVATE,IPCODECMODE=CC,SETPRE=SET1;

END OF STEPS

Creating a BSC Topology Node


� You know the number of the exchange to be configured.

� The encoding and decoding speech template is added.


Context Perform this procedure to configure the adjacent NE information,including equipment type, bearer type and attributes, user planeversion, encoding and decoding template, and other information.



SET:NEID=11;

2. Create a BSC topological node. The command is ADD TOPO.

Table 74 describes the main parameters in the ADD TOPOcommand.




ParameterName


ID Topology nodeID

It is a mandatory parameterranging from 1 to 2048. It isused for defining a topologicalnode. It is recommended thatthis ID is consistent with theoffice ID of this node.

OFCID Office ID

It is a mandatory parameterfor specify the office ID of thistopological node, ranging from 1to 2048. This parameter mustbe defined by the ADD ADJOFCcommand first. Type the BSCoffice ID according to actualconditions.

NAME Alias

It is a mandatory parameter fornaming this topological node,with a length ranging from 1 to50 characters.

CODECID CODEC identity

It is a mandatory parameterfor specifying the Encoding anddecoding speech Template usedby this topological node. Thisparameter must be defined bythe ADD CODECTPL commandfirst.

Type it according to the actualconditions.

ETYPE Equipment type

It is an optional parameter forspecifying the NE type of thistopological node.

Select BSC for an BSC node.

IPVER IP version ofthe node

It is an optional parameter,indicating the IP protocol versionsupported between nodes.Select IPV4 or IPV6 accordingto the actual conditions. Ingeneral, it is set as IPV4

ATTR Bearerattributes

This parameter is only validfor the node with the typeof R4GW (MGW). You neednot to configure it for an BSCtopological node.

UPVER User planeprotocol version

It is an optional parameter. Thisparameter is not configured fora BSC node



ParameterName


ATTR2

Extendedattributes(tunnel mode),including

� NOTUNL(Nonetunnelmode)

� RTUNL(Rapidtunnelmode)

� DTUNL(Delaytunnelmode)

This parameter sets whichtunnel mode is used for settingup a bearer when this nodesupports the IP/RTP bearer, witha default of NOTUNL (Nonetunnel mode).

TRFMOD

Transmissionmode, includingMCINTF (Mcinterface signaltransfer mode)

This parameter is used to setthat mode used by the topologyfor reporting the detected CNGor CED fax signals, with a defaultof MCINTF (Mc interface signaltransfer mode).

UPERRCTRL Error SDUcontrol

YES: The user plane entityimplements error inspection,and sets the FQC bit positionaccording to the result. It willtransmit all frames includesthe error frames to the userplane layer. During a call,the error packet controlparameter delerrsdu=Yes,which is delivered by theterminal established by MGWon the Mc interface. Theerror packet control parameterdeliveryOfErroneousSDU is YES,NA, NA during RAB assignment.

NO: The user plane entityimplements the error inspection.It will directly discard theerror frame. During a call, theerror packet control parameterdelerrsdu=No, which is deliveredby the terminal established byMGW on the Mc interface. Theerror packet control parameterdeliveryOfErroneousSDU is NO,NA, NA during RAB assignment.

INVALIDTION: The user planeentity does not implement theerror inspection. During acall, the error packet controlparameter delerrsdu=NA,which is delivered by theterminal established by MGWon the Mc interface. Theerror packet control parameter



ParameterName


deliveryOfErroneousSDU is NA,NA, NA during RAB assignment.

This parameter regulates thehandling method of the userplane for error frames. It isonly valid for MGW-type andRNC-type topological node. Thedefault value is YES

DTMFTC

Tandem officesend DTMFuse TC mode,containing twooptions:

� NO

� YES

This parameter is used to setwhether the tandem office usesthe TC resources during DTMFnumber delivery.


MGWCON

MGWcongestionreportingcapability

It contains the following options.

� SMGWCON (Standard MGWcongestion event)


The default value is SMGWCON.

Example: Create a BSC topological node with the followingrequirements.


� Topological node ID: 99

� Alias: BSC99

� CODEC ID: 1


ADD TOPO:ID=99,OFCID=99,NAME="BSC99",CODECID=1,ETYPE=BSC,PROTTYPE=H248,DMNAME="RNC",IPVER=IPV4,UPVER="V2",ATTR2=NOTUNL,TRFMOD=MCINTF,UPERRCTRL=YES,DTMFTC=NO,MGWCON=SMGWCON,AUTOFAX=YES,OOBTC=NO,BCUID=0,SENDCAP=NO,G711TRAN=NO,BICCDTMF=TRANSPARENT,IPBCP2833=BYMGW,BICCDTMPPER=0,AOIPPRO=PRIVATE;

END OF STEPS

Creating the Topology Relationship between BSCand MGW



� The BSC topological node is configured.




Context Perform this procedure to configure the topological relationshipbetween BSC and MGW, thus to associate the MGW node with theBSC node.



SET:NEID=11;

2. Create the topological relationship between BSC and MGW. Thecommand is ADD RNCMGWTOPO.

Table 75 describes the main parameters in the ADD RNCMGWTOPO command.

TABLE 75 MAIN PARAMETERS IN THE ADD RNCMGWTOPOCOMMAND

ParameterName


MGWID MGW node ID

It is a mandatory parameterranging from 1 to 2048.

It is the node ID specifiedduring the MGW topologicalnode configuration

RANTYPE Office type It is a mandatory parameter.Select BSC for BSC access.

RANID RNC/BSC nodenumber


It is the node ID specifiedduring the BSC topologicalnode configuration.

SHMODE

Load SharingMode, including:

� NONE (NOTLoad Sharing)

� BEARLOAD(Bear LoadSharing)

� MBLOAD(Master-Backup LoadSharing)

The parameter is used toset the multiple load sharingmodes, with a default of NONE

BTYPE1

Bearer Type 1,including:

� ATM (ATM)

� IP (IP)

The parameter indicates thefirst bearer type, with a defaultof ATM

BRATIO1 Bearer Type 1Ratio

The parameter is used to theset the proportion of the firstbearer type, with a default of 1



ParameterName


BTYPE2


� NONE (NONE)

� ATM (ATM)

� IP (IP)

The parameter indicates thesecond bearer type, with adefault of NONE


The parameter is used tothe set the proportion of thesecond bearer type, with adefault of 1

BPER Ratio of bearerfrom MGW to BSC


It is used for setting the trafficload-sharing ratio when theBSC accesses several MGWs.If the BSC only connects toone MGW, this parameter is setas 1 by default


Example: Create the topology relationship between BSC andMGW with the following requirements.

� MGW node ID: 101

� Office type: BSC

� BSC node ID: 99.


ADD RNCMGWTOPO:MGWID=101,RANTYPE=BSC,RANID=99,SHMODE=NONE,BTYPE1=ATM,BRATIO1=1,BTYPE2=NONE,BRATIO2=1,BPER=1;

END OF STEPS

Trunk and PCM Configuration

Creating a DT Trunk Group


� 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 managementsystem.




Context When the A interface or Ai interface adopts the TDM bearer, orwhen MGWs are interconnected through the TDM bearer, DT trunkgroups need to be configured. The circuit status in each trunkgroup is managed by the corresponding trunk management mod-ule, so it is required to configure multiple trunk groups to eachBSC office (4~8 trunk groups are recommended). To implementload sharing, it is required to allocate roughly the same number ofBSC circuits to each CMP module.



SET:NEID=11;

2. Create a DT trunk group by executing command ADD TG DT.

The explanation of the main parameters in command ADD TGDT is shown in Table 76.

TABLE 76 PARAMETERS IN THE ADD TG DT COMMAND

ParameterName


TG Trunk group ID

It is a mandatoryparameter. It is usedto define a trunkgroup, and needs to beplanned in the resourcemanagement system inadvance

OFC ID of the office wherethe trunk group belongs

It is a mandatoryparameter. It isused to specify thecorresponding office ofthe trunk group. Thisparameter must bedefined by commandADD ADJOFC at first.Then it can be indexedhere

MODULE Module where the trunkgroup belongs

It is a mandatoryparameter. It indicatesa service module.Different trunk groupsto the same officeneed to be allocated todifferent CMP modules


It is a mandatoryparameter. Select theMGW topology nodeconnected with the 2GMSC/PSTN node



ParameterName


NAME User alias

It is an optionalparameter, consistingof 0~50 characters. Itis used to specificallydescribe a trunk groupto make it easilyrecognized

SIGLINE

Inter-office line signalidentification. Optionsinclude:

� BSC: BSC GroundCircuit

� TUP: InterofficeCommon ChannelSignaling TUP

� ISUP: InterofficeCommon ChannelSignaling ISUP

� DLC1: InterofficeChannel AssociatedSignaling DL/DC(1)

� R2: R2 Signaling

� BICC: BICC Type

� ANU: ANU Signaling

� SORMUP: SORMUPSignaling

It is an optionalparameter. It is usedto identify the line typeof this trunk. Select itaccording to inter-officesignaling. For the Aiinterface, select ISUP]or TUP

KIND


IN (incoming trunkgroup): Indicatesthat the local officeprocesses the incomingcalls from the peer-endoffice.

OUT (outgoing trunkgroup): Indicates thatthe local office onlyprocesses the outgoingcalls to the peer-endoffice.

BIDIR (Two-way trunkgroup): Indicatesthat the local officeprocesses both theincoming calls from thepeer-end office and theoutgoing calls to thepeer-end office

It is an optionalparameter. If BSCis selected for theinter-office line signalidentification, it must beconfigured to BIDIR



ParameterName


BWAY


NODIR: The inter-officebearer is establishedwithout direction.


FORWD: Theinter-office bearer isestablished based onthe forward mode

It is an optionalparameter. SelectNODIR for DT trunkgroups


It is an optionalparameter, ranging from0 to 100, with a defaultof 100. This parametertakes effect when levelsof congestion occur andload control is required

CICSEL

Circuit selecting modes,including:

MIN: Every time whenthe system selects atrunk circuit, it alwaysbegins with the circuitwith the minimumnumber. This mode canimplement the preferredplan of trunk circuits.

MAX: Every time whenthe system selects atrunk circuit, it alwaysbegins with the circuitwith the maximumnumber. This mode canimplement the preferredplan of trunk circuits.

CYC: Every time whenthe system selectsa trunk circuit, italways begins withthe circuit next to theone previously selected.Suppose the numbersof the trunk circuits in atrunk group in ascendingorder are “TKC0, TKC1,…. , TKCn”. If TKC0is selected at the firsttime, the system willselect the trunk circuitin the order of “TKC0®TKC1®…®TKCn®TKC0®TKC1®…®TKCn”.

ODD: Every time whenthe system selects a

It is an optionalparameter. It is used tospecify the trunk circuitselecting policy of thesystem within this trunkgroup, with a default ofCYC. If this No.7 trunkgroup is a two-waytrunk group, it isrecommended to set thecircuit selecting modeto ODD/EVEN modeto prevent contentionwhen two exchangesselect circuits



ParameterName


trunk circuit, it alwaysselects the circuit withan odd number.

EVEN: Every time whenthe system selects atrunk circuit, it alwaysselects the circuit withan even number.

IDLE: Every time whenthe system selects atrunk circuit, it alwaysselects the idlest circuit.

BUSY: Every time whenthe system selects atrunk circuit, it alwaysselects the busiestcircuit


It is an optionalparameter. It is usedto analyze the callednumber in an incomingcall. This parametermust be defined bycommand ADD DAS atfirst. Then it can beindexed here

SIPDAS

DAS for the domainname of the callednumber during a SIPoutgoing call

It is used get the nameof the IMS domainwhere the called partyis located throughanalyzing the callednumber during a SIPoutgoing call. It isonly used for RTP trunkgroups

OPDAS DAS for the callingnumber

It is used to analyzethe calling number inan incoming call. Thisparameter must bedefined by commandADD DAS at first. Thenit can be indexed here

PREDAS DAS for pre-analyzingthe called number

It is used to pre-analyzethe called number inan incoming call. Thisparameter must bedefined by commandADD PREDAS at first.Then it can be indexedhere



ParameterName


DDI Incoming called numbertransform ID

It is the index ofthe incoming callednumber transform. Thisparameter must bedefined by commandADD DDI at first. Thenit can be indexed here

OPDDI Incoming callingnumber transform ID

It is the index ofthe incoming callingnumber transform. Thisparameter must bedefined by commandADD DDI at first. Thenit can be indexed here

MINNAT Minimum nationalnumber length

It is an optionalparameter, which isan integer ranging from0 to 26, with a defaultof 0. It is used tospecify the minimumdigit length of thecalled number during anational incoming call

MAXNAT Maximum nationalnumber length

It is an optionalparameter, which isan integer ranging from0 to 26, with a defaultof 26. It is used tospecify the maximumdigit length of thecalled number during anational incoming call

MININT Minimum internationalnumber length

It is an optionalparameter, which isan integer ranging from0 to 26, with a defaultof 0. It is used tospecify the minimumdigit length of thecalled number during aninternational incomingcall

MAXINT Maximum internationalnumber length

It is an optionalparameter, which isan integer ranging from0 to 26, with a defaultof 26. It is used tospecify the maximumdigit length of thecalled number during aninternational incomingcall



ParameterName


INREG

Incoming registersignaling flag, includingoptions: INVALID,MFC, MFP, DTMF, DPand MF

It is an optionalparameter, with adefault of INVALID

OUTREG

Outgoing registersignaling flag, includingoptions: INVALID,MFC, MFP, DTMF, DPand MF

It is an optionalparameter, with adefault of INVALID

COLEN The maximum length ofCAS calling number end

It is an optionalparameter. It rangesfrom 1 to 32, with adefault of 10.

BUSYRATE Trunk circuit usage

It is an optionalparameter, which isan integer rangingfrom 1 to 100, with adefault of 100. Afterthe trunk circuit usageis configured, when theratio of busy circuits toall circuits in this trunkgroup exceeds thisvalue, congestion occursin this trunk group.After the congestionis relieved, report thetrunk congestion timesand congestion durationin the performancestatistics. Thisparameter does nottake effect when it isconfigured to 100

ROAMDAS DAS for roamingnumbers

It is an optionalparameter. After thisDAS is configured, ifthe local office servesas a GMSC, this DASis preferred for thereturned roamingnumbers. Otherwise,the roaming numberDAS configured inthe number analysistemplate is used



ParameterName


Q850CCIDX Q850 customizationindex


SMENTERID ID of signalingmodification entrance

It is an optionalparameter, associatedwith the inter-officesignaling modificationentrance. It rangesfrom 0 to 65535, with adefault of 0

Example: Create a DT trunk group to the BSC office with thefollowing requirements:



� User alias: BSC99

� No. of the CMP module where the trunk group belongs: 3



The command is:

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,PREDAS=0,DDI=0,OPDDI=0,MINNAT=0,MAXNAT=26,MININT=0,MAXINT=26,INREG=INVALID,OUTREG=INVALID,COLEN=10,BUSYRATE=100,ROAMDAS=0,Q850CCIDX=0,SMENTERID=0,MLPPDM=4294967295,DISINDEX=0;

END OF STEPS




� The DT trunk group is configured.





SET:NEID=11;






ParameterName


PCM TG PCM-belonged trunk group ID

NUM Number

It is an optional integer-typeparameter, ranging from 1 to100. In general, select thedefault value.

MGWPCM MGW PCMnumber

It is an optional parameter,consisting of MGWPCM_S andMGWPCM_F. The start andend numbers of the MGWPCM mean that the trunkscorresponded by PCM resourcesof this number section can beinvoked. This parameter is leftblank when the PCM-belongedtrunk number is an interofficeBICC.

INFO Self-loop PCMnumber

It is an optional parameter,with a default of 65535.Enter an integer rangingfrom 0 to 65535. In general,select the default value. Thecorresponding self-loop PCMnumber is required in case ofconfiguring a self-loop office.

NAME Alias It is an optional parameter,consisting of 1~50 characters.

Example: Create a PCM system to the BSC office with the fol-lowing requirements:

� No. of the trunk group where the PCM system belongs: 99



� User alias: BSC1-1.


ADD SPCM:TG=99,PCM=1,NUM=3,MGWPCM="4"-"6",INFO=65535,NAME="BSC1-1";

END OF STEPS




Creating an SCTP


� The physical configuration of the SMP module is complete.

� The range of the SCTP ID is configured in the resource man-agement configuration.


Context The configuration of SCTP basic connection is used to configurethe basic information of the SCTP association.



SET:NEID=11;

2. Create the SCTP connection. The command is ADD SCTPCONN.

Table 78 describes the parameters in the ADD SCTPCONNcommand.


Parame-ter Name


MODULE Module No.

It is a mandatory parameter,indicating the number of thesignaling module homed by thisSCTP association. Select the SMPmodule number. Each SMP cansupport up to 128 associations.The associations under the sameAS are required sharing loadon SMP modules as more aspossible.

OFCID SCTP oppositeoffice ID

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



Parame-ter Name


PROT


� M2UA

� M2PA

� M3UA

� SUA

� H248

� BICC

� IUA

� DHCTRL

� SIP

� DIM

� V5UA

� H245

It is a mandatory parameter. It isused to identify the upper-layerprotocol type borne by the SCTPassociation. In general, M3UA isselected.M2UA is selected whenMGW transfers the signaling withthe M2UA mode.

ROLE

SCTP applicationattributes.Options include:

SVR: SCTP isused as server

CLT: SCTP is usedas client

It is a mandatory parameter. ForMc interface, MSCS is configuredas CLT, and MGW is configuredas SVR. For Nc interface, thisshould be negotiated by bothsides. For example, the smallsignaling point serves as CLT,and the big signaling point servesas SVR


It is a mandatory parameter. Itdesignates the service addressof local end of this association,with a format of Local IPaddress type-VPN of local IPaddress-Local IP address

Local IP address type: IPv4 andIPv6;

VPN of local IP address: Rangfrom 0 to 65535;

Local IP address: the format isxxx.yyy.zzz.mmm

LOCPORT Local portnumber

It is a mandatory parameter. Itis the local SCTP port number ofthe association, ranging from 1to 65535.

REMADDR Opposite IPaddress

It is a mandatory parameter. Itdesignates the service address ofopposite end of this association,ranging from 1 to 65535.


It is a mandatory parameter. It isthe opposite SCTP port numberof the association, ranging from1 to 65535.



Parame-ter Name


NAME AliasIt is a mandatory parameter witha length ranging from 1 to 50characters.

ID SCTP ID

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













ADD SCTPCONN:MODULE=3,OFCID=101,PROT=M3UA,ROLE=CLT,LOCADDR="IPv4"-"0"-"192.168.1.11",LOCPORT=4001,REMADDR="IPv4"-"0"-"192.168.1.31",REMPORT=4001,NAME="BSC",ID=3,INSTRM=16,OUTSTRM=16,MAXRTRY=5,MAXRTO=500,MINRTO=50,INITRTO=100,HB=500,FIXNH=NO,SCTPMAXRTRYNUM=10,DELAYACK=20,MAXBURST=4,PRIMARYPATH=REMIP1,PMTU=0,BREAKTIME=0,PDTHRESH=0,MINCWND=0,PLTIMER=10,MPPLTHRD=2,DPLEN=MTU,CB=200;

END OF STEPS

Creating an ASP


� The SCTP association information is configured.

� The range of the ASP ID is configured in the resource manage-ment configuration.


Context ASP configuration defines the one-to-one relationship between theASP and the association.





SET:NEID=11;


Table 79 describes the parameters in the ADD ASP command.


ParameterName


ASSOCID SCTP ID

It is a mandatory parameter,ranging from 1 to 2048

Type the association IDconfigured in the SCTPconnection configuration.

NAME Alias

It is a mandatory parameter,with a lengthen ranging from1 to 50 characters. It maybe named with a format of“Adjacent office alias-SCTPnumber”.

ID ASP ID


It is recommended to beconsistent with ASSOCID.

ISLOOP ASP self-loop ID

It is an optional parameter. It isused to set whether the ASP isself-looped.


ISLOCK ASP blocking flag

It is an optional parameter. It isused set whether the ASP is inblocking state.

Blocking is used formanagement. Select thedefault value NO

Example: Create the ASP between MSCS and MGW with thefollowing requirements.




� User alias: SCCP.




ADD ASP:ASSOCID=3,NAME="SCCP",ID=3,ISLOOP=NO,ISLOCK=NO;

END OF STEPS

Creating an AS


� The ASP configuration is complete.



Context AS configuration is used to configure the basic information for theapplication server.



SET:NEID=11;

2. Create an AS. The command is ADD AS.

Table 80 describes the parameters in the ADD AS command.

TABLE 80 AS PARAMETERS

ParameterName


PROT Adaptation layerprotocol

It is a mandatoryparameter. It is requiredto be consistent with thatat the adjacent office side.Configure it according tothe actual conditions. Ingeneral, select M3UA.

ASPID ASP IDIt is associated with theASP ID configured in theASP configuration.

NAME Alias

It is a mandatoryparameter, which iscustomized by the userfor easy recognition.

ID AS ID

It is an optionalparameter. It is theunique ID of the AS. Ingeneral, it is the same asthat of the ASP for easymemory.



ParameterName


EXISTCTX

If routing contextexists, including:

� NO: Routingcontext does notexist

� YES: Routingcontext exists

This parameter mustbe consistent with theAS configuration of theopposite-end.


It is an integer parameter.If the YES (Routingcontext exists) optionis selected for theEXISTCTX parameter,this parameter mustbe consistent with theAS configuration of theopposite-end.

ASTAG Usage tag In this case, select CLT(IPSP Client).

ASUP User typesIt is an optionalparameter. In this case,select SCCP.

ASMD

Service mode,including:

� OVERRIDE(Over-ride mode)

� LOAD (Load sharemode)

In the over-ride mode,only one ASP is activated.In this case, only one ASPneeds to be configured. Inthe load sharing mode, NASPs should be configuredto be in activated workingstatus, and K ASPs shouldbe configured to be indeactivated standbystatus. Make sure thatthe value of N+K is notmore than the number ofASPs actually configured.This parameter should benegotiated between bothends for consistency.

NVAL N value of load sharemode

It is an integer parameter,ranging from 0 to 16.

N+K should be equalto the number of ASPsconfigured under this AS.

N indicates that this ASis in service as soon as NASPs are in service.

KVAL K value of load sharemode

It is an integer parameter,ranging from 0 to 16.

N+K should be equalto the number of ASPsconfigured under this AS.

K indicates that this AS isout of service as soon asK ASPs are out of service.



Example: Create the AS between MSCS and MGW with thefollowing requirements.


� AS ID: 3

� Supported user type: SCCP

� ASP ID: 3

� Client: MSCS

� Alias: BSSAP


ADD AS:PROT=M3UA,ASPID="3",NAME="BSSAP",ID=3,EXISTCTX=NO,ASTAG=CLT,ASUP="SCCP",ASMD=LOAD,NVAL=1,KVAL=0;

END OF STEPS



� The AS configuration is complete.

� The range of M3UA static route ID is configured in the resourcemanagement.


Context Configuring an M3UA static route means configuring the mappingrelationship between an M3UA static route and an AS.



SET:NEID=11;




ParameterName







ParameterName


MODE


� BYTURNS

� LOCAL

� NATURE








� AS ID: 3

� User alias: SCCP.


ADD M3UART:ID=3,ASID=3,MODE=BYTURNS,NAME="SCCP";

END OF STEPS



� The M3UA static route configuration is complete.



Context Where, a routing keyword describes the parameters and their val-ues of a group of No.7 signaling messages. The corresponding ASis selected according to the message attributes, serving the pur-pose of selecting route for messages. The attribute of the messageincludes DPC+NET+OPC+SIO, where, DPC is the destination sig-naling point code, NET is the network type, OPC is the originatingsignaling point code, and SIO is the service indicator octet.

The configuration of SIO-locating-AS is used to locate one serviceto a routing table that is maintained by the ASPs under the AS.Compared with the MTP data configuration of the traditional No.7



signaling, the ASP configuration of the SCTP connection and M3UAis similar to the link logic and bearer information configuration inthe MTP configuration, the AS configuration of the M3UA is similarto the link set configuration in the MTP configuration, and the SIO-locating-AS configuration is similar to the signaling office ID androute configuration in the MTP configuration. The difference is thatthe IP route to one subscriber of one office is configured in oneSIO-locating-AS configuration record.



SET:NEID=11;


Table 82 describes the parameters in the ADD SIOLOCAScommand.


Parame-ter Name


ID SIO-locating-AS ID

It is an optional parameter,indicating the serial numberof SIO-locating-AS, rangingfrom 1 to 4096. In general,it is the same as the AS ID.

NAME The name of theSIO-locating-AS

It is customized by users foridentification.

OFCID Destination office ID

The ID of the adjacentoffice corresponded by thedestination signaling pointof M3UA. It correspondsto the adjacent officeID specified in the ADDADJOFC command.

SIO Service indication Select SCCP.

RT1 M3UA static route ID 1It is the static route IDconfigured by the ADDM3UART command.

Example: Create SIO-locating-AS between MSCS and BSC withthe following requirements.


� Destination adjacent office ID: 99

� Service indication: SCCP





ADD SIOLOCAS:ID=3,NAME="SCCP",SIO=SCCP,OFCID=99,OPOFCID=65535,PCM=65535,RT1=3,RT2=0;

END OF STEPS

RNC Data ConfigurationOverview

TypicalNetworking

In the R4 phase, the interface between the RNC and the CS domainuses the ATM bearer, and the MSCS processes the control planeof the Iu_CS interface. The signaling is based on the AAL5 andis transmitted by the SCCP. MGW processes the user plane andthe bearer control plane of the Iu-CS interface. The user dataare based on the AAL2, and transferred on the AAL2 connection.The ALCAP controls the establishment and release of user planeconnections. In the existing networks, the signaling interworkingbetween the MSCS and the RNC is implemented by the built-in SG(SG) in the MGW. Figure 10 shows the networking mode and theinterface protocol stack.

FIGURE 10 NETWORKING BETWEEN MGW AND RNC

The ATM bearer is used between the MGW and the RNC, and theIP bearer is used between the MGW and MSCS. Working in theswitching mode, the built-in SG in the MGW performs the signalingswitching between the MSCS and the RNC.

Data Collection Before data configuration, it is supposed to complete collectingthe related data of MSCS-to-MGW, and MGW-to-RNC. Table 83 andTable 84 list the data to be collected. The parameter values arejust examples. Input these parameters according to the actualcondition during the practical data construction procedure.







Signaling point code (14-bit) of ZXWNMSCS 1.11.1




TABLE 84 DATA FOR INTERCONNECTION WITH THE RNC


The type of the local signaling point 14-bit

SPC of the local office 1.100.1

RNCID 1

Location area code 12FB

Service area code 1

AMR codec rate (newly added) 122

ATM address/coding type (the codingtype is NSAP)

00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.06

MCC+MNC 46007

Path ID 1

Signaling link code (SLC) in a signalinglink set 0


This section introduces the data configuration on the MSCS foradding a RNC adjacent office under the precondition that the MGWis successfully registered to the MSCS, including the configurationsof signaling-forwarded data to and through the RNC. Table 85 de-scribes the configuration flow.



TABLE 85 RNC ADJACENT OFFICE DATA CONFIGURATION FLOW


1 Creating a RNC adjacentoffice ADD ADJOFC

2 Creating RNC officedirection ADD RNCOFC

3 Creating a RNC topologynode ADD TOPO

4Creating the topologyrelationship between RNCand MGW

ADD RNCMGWTOPO

5 Creating an ATM trunkgroup ADD TG ATM

6 Creating a PCM system ADD SPCM

ADD SCTPCONN

ADD ASP

ADD AS7

Creating the associationsand the M3UA data switchedby the signaling

ADD M3UART

8 Creating the SIO-Locating-AS ADD SIOLOCAS

Creating an RNC Adjacent Office





Context Perform this procedure for configuring the basic information of theRNC adjacent office.



SET:NEID=11;

2. Create the RNC adjacent office. The command is ADD ADJOFC.





ParameterName


ID Office ID

It is a mandatory parameter,indicating the identificationnumber of the adjacent office,and ranging from 1 to 2048.It is usually configured as theexchange ID of the adjacentoffice during the all-networkplanning.


NET Network type

It is a mandatory parameter,indicating the network type ofthe SPC used for connectingthe local office to the adjacentoffice when the local office isconfigured with several SPs.

The default is the network typeof this SP when there is onlyone SP in the local office.

OFCTYPE Adjacent office typeIt is a mandatory parameter.

Type RNC in this case

SPCFMT SPC format Select TRIPLE_DEC

SPCTYPE SPC type

DPC SPC

It is a mandatory parameter.Specify it based on the SPCtype of the adjacent office

RC Area code When the adjacent office typeis RNC, RC must be empty.

ASSOTYPE

Association type,including



� AM_NONE(noneconnectionmode)


Select AM_QUASI



ParameterName


SPTYPE

Signaling pointtype, including

� SEP

� STP

� STEP


Select SEP

SSF

Subservicefunction, including

� INTERNA-TIONAL (In-ternational sig-naling pointcode)

� INTERNA-TIONALSTANDBY(Internationalstandby signal-ing point code)

� NATIONAL(Nationalsignaling pointcode)

� NATIONALSTANDBY(Nationalstandbysignaling pointcode)

It is an optional parameter. Ingeneral, select NATIONAL fordomestic use.

TEST Test flag

It is an optional parameter, forsetting whether the MTP3 linkactively initiates the link testafter entering in the servicestatus.

It is selected by default.

BANDFLAG Broadbandattribute

It is an optional parameter.Select YES when all the linksbetween two SPs are SIGTRANor ATM signaling links.

PRTCTYPE

Protocol types,including:

� CHINA (China)

� ITU (Interna-tional Telecom-municationsUnion)

� ANSI(AmericanNationalStandardsInstitute).


CHINA and ITU are used forthe NO.7 signaling networkingof the ITU standards. ANSIis used for the No.7 signalingnetworking of the Americanstandards.



ParameterName


CLST Cluster ID

It is an optional parameter.The cluster number shouldbe configured in ADD CLST.The parameter ranges from0 to 65535, with a default of65535.

INFO

Office Info,including:

� CIC_PCM (CICstarts theload sharingaccording tothe PCM codemode)

� BLOCK(Manual blockstatus)

� EVEN_CIC(The officecontrols theeven CIC whenCIC resourcecontentionoccurs)

� CALL-ING(Callingtransform is al-lowed)

� CALLED(Calledtransform isallowed)

� MOD24_CIC(CIC mode with24 mode)

� TEST(Dynamic test)

It is an optional parameter,with a default of CIC_PCM(CIC using PCM Code ModeStarts Load Control)

RELATE-DOFC1 Related office ID It is an optional parameter,

ranging from 0 from 3000

INFOEX

Office extend info,including

� SIGBRDCST(SupportSignalingBroadcastMessage)

� MTP(HongkongMTP Standard)

� DUPU (Screen DUPUmessage)




ParameterName


� SUA_REC_DT1 (ReceiveSUA messageand handle it asDT1 message)

� SUA_SND-_DT1 (SendSUA messageand handle it asDT1 messagewithout SN.)

� OPEN_TG-_RES (Openoutter trunkgroup re-source)

Example: Create an RNC adjacent office with the following re-quirements.

� RNC office ID: 100

� Network type: 2

� User alias: RNC100


� SPC type: 14-bit

� Adjacent office type: RNC

� Association type: Quasi-associated mode.


ADD ADJOFC:ID=100,NAME="RNC100",NET=2,OFCTYPE="RNC",SPCFMT=TRIPLE_DEC,SPCTYPE=14,DPC="1.100.1",ASSOTYPE=AM_QUASI,SPTYPE=SEP,SSF=NATIONALSTANDBY,SUBPROTTYPE=DEFAULT,TEST=YES,BANDFLAG=NO,PRTCTYPE=CHINA,CLST=65535,INFO="CIC_PCM",RELATEDOFC1=0;

END OF STEPS

Office Direction and TopologyConfiguration

Creating RNC Office Direction



� The RNC adjacent office is created.




Context Perform this procedure to configure some additive attributes of theRNC adjacent office, thus to associate the RNCID with the RNCoffice.



SET:NEID=11;

2. Create the RNC office direction. The command is ADD RNCOFC.

Table 87 describes the main parameters in the ADD RNCOFCcommand.

TABLE 87 PARAMETERS IN THE ADD RNCOFC COMMAND

ParameterName


OFCID RNC office ID


It is the RNC office IDspecified in the RNC officeconfiguration.

MCC Mobile country code

It is a mandatory parameter,ranging from 1 to 4characters. For China,it is 460.

MNC Mobile network codeIt is a mandatory parameterwith a length ranging from 2to 3 characters.

RNCID RNC IDIt is a mandatory parameter,ranging from 0 to 4095. It isprovided by the RNC side.

RABDLY RAB Delay(ms)The parameter ranges from0 to 65535, with a default of100

SDUERA

Class A SDU ErrorRatio. The optionsinclude:

� ERRRATIO1(1*10^(-2)

� ERRRATIO2(7*10^(-3)

� ERRRATIO3(1*10^(-3)

� ERRRATIO4(1*10^(-4)

� ERRRATIO5(1*10^(-5)

The default value isERRRATIO2 (7*10^(-3)



ParameterName


RBERA

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))

The default value isERRRATIO7 (1*10^(-6))

RBERB

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))


RBERC

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))




ParameterName


SELMGTYPE

Iu Interface LoadShare Mode. Theoptions include:

� EXCELLENT(Ex-cellent choicepriority)

� LOAD(Load sharepriority)

The default value isEXCELLENT (Excellentchoice priority)

ATMADDR RNC ATM Address

ADDRPLAN

ATM AddressPlan, includingE.164(E.164) andNSAP(NSAP)

It is an optional parameter.Configure the ATM addressand coding plan of thecorresponding RNC.

ATM address code can adoptthe NSAP that has a fixedlength of 20 bytes) or E.164(that is an extendable BCDcode).

The configuration hereshould be consistent withthe RNC office ID parametersat the MGW side.

BTRY1

First Rebear Mode.The options include:

� NO(NO RETRY);

� BEARER(TRYOTHER REBEARMODES;

� MGW(TRY OTHERMGW)

The default is NO(NORETRY)

BTRY2

Second Rebear Mode.The options include:

� NO(NO RETRY);

� BEARER(TRYOTHER REBEARMODES;

� MGW(TRY OTHERMGW)

The default is NO(NORETRY)

RAS RNC OfficeReAssignment.Options include:

� NO(NO);

� YES(YES)

The default value is NO(NO)

Example: Create the RNC office direction with the followingrequirements.






� RNC ID: 1

� ATM address of RNC: 12.3456.7890.abcd.efff.ffff.ffff.ffff.ff-ff.ffff.ff

� ATM address plan: E164.


ADD RNCOFC:OFCID=100,MCC="460",MNC="00",RNCID=1,RABDLY=100,SDUERA=ERRRATIO2,RBERA=ERRRATIO7,RBERB=ERRRATIO4,RBERC=ERRRATIO3,SELMGTYPE=EXCELLENT,ATMADDR="12.3456.7890.abcd.efff.ffff.ffff.ffff.ffff.ffff.ff",ADDRPLAN=E164,BTRY1=NO,BTRY2=NO,RAS=NO;

END OF STEPS

Creating an RNC Topology Node



� The voice CODEC template is created.


Context Perform this procedure to create the adjacent NE information, in-cluding equipment type, bearer type and attributes, user planeversion, encoding and decoding template, and other information.



SET:NEID=11;

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

Table 88 describes the main parameters in the ADD TOPOcommand.


ParameterName


ID Topologicalnode ID

It is a mandatory parameter,ranging from 1 to 2,048. It is usedfor defining a topological node. Itis recommended that this ID isconsistent with the office ID of thisnode.

OFCID Office IDIt is a mandatory parameterfor specify the office ID of thistopological node, ranging from 1



ParameterName


to 3,000. This parameter mustbe defined by the ADD ADJOFCcommand first. Type the RNC officeID according to actual conditions.

NAME Alias

It is a mandatory parameter fornaming this topological node, witha length ranging from 1 to 50characters.

CODECID CODECidentity

It is a mandatory parameterfor specifying the Encoding anddecoding speech Template usedby this topological node. Thisparameter must be defined by theADD CODECTPL command first.

Type it according to the actualconditions.

ETYPE Equipmenttype

It is an optional parameter forspecifying the NE type of thistopological node.

Select RNC for an RNC node.

IPVER IP version ofthe node

It is an optional parameter,indicating the IP protocol versionsupported between nodes. SelectIPV4 or IPV6 according to theactual conditions. In general, it isset as IPV4

ATTR Bearerattributes

This parameter is only valid forthe node with the type of R4GW(MGW). You need not to configureit for an RNC topology node.

UPVERUser planeprotocolversion

It is an optional parameter toregulate the user plane versionof this node, ranging from V1to V16. It can support one ormore of these user plane versions.This parameter is only valid forRNC-type or MGW-type NE.

In general, V2 is selected (meaningsupporting Version 2) according tothe user-plane version supportedby RNC.

ATTR2

Extendedattributes(tunnelmode),including

� NOTUNL(Nonetunnelmode)

� RTUNL(Rapidtunnelmode)

This parameter sets which tunnelmode is used for setting up abearer when this node supportsthe IP/RTP bearer, with a default ofNOTUNL (None tunnel mode).



ParameterName


� DTUNL(Delaytunnelmode)

TRFMOD

Transmissionmode,includingMCINTF (Mcinterfacesignal transfermode)

This parameter is used to set thatmode used by the topology forreporting the detected CNG orCED fax signals, with a defaultof MCINTF (Mc interface signaltransfer mode).

UPERRCTRL Error SDUcontrol

YES: The user plane entityimplements error inspection, andsets the FQC bit position accordingto the result. It will transmit allframes includes the error frames tothe user plane layer. During a call,the error packet control parameterdelerrsdu=Yes, which is deliveredby the terminal established byMGW on the Mc interface. Theerror packet control parameterdeliveryOfErroneousSDU is YES,NA, NA during RAB assignment.

NO: The user plane entityimplements the error inspection.It will directly discard the errorframe. During a call, theerror packet control parameterdelerrsdu=No, which is deliveredby the terminal established byMGW on the Mc interface. Theerror packet control parameterdeliveryOfErroneousSDU is NO,NA, NA during RAB assignment.

INVALIDTION: The user planeentity does not implement theerror inspection. During a call,the error packet control parameterdelerrsdu=NA, which is deliveredby the terminal established byMGW on the Mc interface. Theerror packet control parameterdeliveryOfErroneousSDU is NA, NA,NA during RAB assignment.

This parameter regulates thehandling method of the userplane for error frames. It is onlyvalid for MGW-type and RNC-typetopological node. The default valueis YES



ParameterName


DTMFTC

Tandem officesend DTMFuse TC mode,containing twooptions: Noand YES

This parameter is used to setwhether the tandem office uses theTC resources during DTMF numberdelivery.


MGWCON

MGWcongestionreportingcapability

It contains the following options.

� SMGWCON (Standard MGWcongestion event)


The default value is SMGWCON.

Example: Create a topology node with the following require-ments.


� Topology node ID: 100

� Alias: RNC100

� CODEC ID: 1

� RNC-supported user-plane version: V2.


ADD TOPO:ID=100,OFCID=100,NAME="RNC100",CODECID=1,ETYPE=RNC,PROTTYPE=H248,DMNAME="RNC",IPVER=IPV4,UPVER="V2",ATTR2=NOTUNL,TRFMOD=MCINTF,UPERRCTRL=YES,DTMFTC=NO,MGWCON=SMGWCON,AUTOFAX=YES,OOBTC=NO,BCUID=0,SENDCAP=NO,G711TRAN=NO,BICCDTMF=TRANSPARENT,IPBCP2833=BYMGW,BICCDTMPPER=0,AOIPPRO=PRIVATE;

END OF STEPS

Creating the Topology Relationship between RNCand MGW



� The RNC topology node is created.


Context Perform this procedure to configure the topological relationshipbetween RNC and MGW, thus to associate the MGW node with theRNC node.





SET:NEID=11;

2. Create the topology relationship between RNC and MGW. Thecommand is ADD RNCMGWTOPO.

Table 89 describes the main parameters in the ADD RNCMGWTOPO command.

TABLE 89 PARAMETERS IN THE ADD RNCMGWTOPO COMMAND

ParameterName


MGWID MGW node ID

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

It is the node ID specifiedduring the MGW topologicalnode configuration

RANTYPE Office type It is a mandatory parameter.Select RNC for RNC access.

RANID RNC/BSC nodenumber

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

It is the node ID specifiedduring the RNC topologicalnode configuration.

SHMODE

Load SharingMode, including:

� NONE (NOTLoad Sharing)

� BEARLOAD(Bear LoadSharing)

� MBLOAD(Master-Backup LoadSharing)

The parameter is used toset the multiple load sharingmodes, with a default ofNONE

BTYPE1


� ATM (ATM)

� IP (IP)

The parameter indicatesthe first bearer type, with adefault of ATM


The parameter is used to theset the proportion of the firstbearer type, with a default of1

BTYPE2


� NONE (NONE)

� ATM (ATM)

� IP (IP)

The parameter indicates thesecond bearer type, with adefault of NONE



ParameterName



The parameter is used tothe set the proportion of thesecond bearer type, with adefault of 1

BPER Ratio of bearerfrom MGW to RNC


It is used for setting thetraffic load-sharing ratiowhen the RNC accessesseveral MGWs. If the RNConly connects to one MGW,this parameter is set as 1 bydefault


Example: Create the topology relationship between RNC andMGW with the following requirements.

� MGW node ID: 101

� RNC node ID: 100.


ADD RNCMGWTOPO:MGWID=101,RANTYPE=RNC,RANID=100,SHMODE=NONE,BTYPE1=ATM,BRATIO1=1,BTYPE2=NONE,BRATIO2=1,BPER=1;

END OF STEPS

Trunk and PCM Configuration

Creating an ATM Trunk Group



� The trunk group No. range is set in the resource managementsystem.

� The adjacent MGW office to which the trunk group points iscreated.


Context When the ATM bearer is adopted between MGWs, configure ATMtrunk groups.





SET:NEID=11;

2. Create an ATM trunk group by executing command ADD TGATM.

The explanation of the main parameters in command ADD TGATM is shown in Table 90.

TABLE 90 PARAMETERS IN THE ADD TG ATM COMMAND

ParameterName


TG Trunk group ID

It is a mandatoryparameter. It is usedto define an ATM trunkgroup, and needs to beplanned in the resourcemanagement system inadvance. It is a globalunified number

OFC ID of the office wherethe trunk group belongs

It is a mandatoryparameter, rangingfrom 1 to 256. It isused to specify thecorresponding office ofthe trunk group. Thisparameter must bedefined by commandADD ADJOFC at first.Then it can be indexedhere

NAME User alias

It is an optionalparameter, consistingof 0~50 characters.

It is used to specificallydescribe a trunk group tomake it easily recognized

MODULE Module where the trunkgroup belongs

It is a mandatoryparameter, which isan integer, ranging from1 to 127. It is used tospecify the SMP moduleof processing traffic onthis trunk group


It is a mandatoryparameter, which isan integer, ranging from1~2048. It is used tospecify the topologynode No. of the MGWproviding bearer, whichis controlled by the localMGCF



ParameterName


SIGLINEInter-office line signalidentification, includingBICC (BICC signaling)

It is an optionalparameter. It is used toidentify the line type ofthis trunk, with a defaultof BICC

KIND


IN (incoming trunkgroup): Indicates thatthe local office processesthe incoming calls fromthe peer-end office.

OUT (outgoing trunkgroup): Indicates thatthe local office onlyprocesses the outgoingcalls to the peer-endoffice.

BIDIR (Two-way trunkgroup): Indicates thatthe local office processesboth the incoming callsfrom the peer-end officeand the outgoing calls tothe peer-end office

It is an optionalparameter. It is usedto specify the callconnection directionin this trunk group inthe local office, witha default of BIDIR. Itshould be negotiatedwith the peer-end office

BWAY


NODIR (No direction):The inter-office beareris established withoutdirection.


FORWD: Theinter-office bearer isestablished based on theforward mode

It is an optionalparameter. It is used tospecify the inter-officebearer establishmentdirection, with a defaultof NODIR


It is an optionalparameter, ranging from0 to 100, with a defaultof 100. This parametertakes effect when levelsof congestion occur andload control is required



ParameterName


CICSLTP

Circuit selecting modes,including:

MIN: Every time whenthe system selects atrunk circuit, it alwaysbegins with the circuitwith the minimumnumber. This mode canimplement the preferredplan of trunk circuits.

MAX: Every time whenthe system selects atrunk circuit, it alwaysbegins with the circuitwith the maximumnumber. This mode canimplement the preferredplan of trunk circuits.

CYC: Every time whenthe system selectsa trunk circuit, italways begins withthe circuit next to theone previously selected.Suppose the numbersof the trunk circuits in atrunk group in ascendingorder are “TKC0, TKC1,…. , TKCn”. If TKC0is selected at the firsttime, the system willselect the trunk circuit inthe order of “TKC0®TKC1®…®TKCn®TKC0®TKC1®…®TKCn”.

ODD: Every time whenthe system selects atrunk circuit, it alwaysselects the circuit withan odd number.

EVEN: Every time whenthe system selects atrunk circuit, it alwaysselects the circuit withan even number.

IDLE: Every time whenthe system selects atrunk circuit, it alwaysselects the idlest circuit.

BUSY: Every time whenthe system selects atrunk circuit, it alwaysselects the busiest circuit

It is an optionalparameter. It is used tospecify the trunk circuitselecting policy of thesystem within this trunkgroup, with a defaultof CYC. If this trunkgroup is a two-waytrunk group, it isrecommended to set thecircuit selecting modeto ODD/EVEN mode toprevent contention whentwo exchanges selectcircuits



ParameterName



It is an optionalparameter. It is usedto analyze the callednumber in an incomingcall. This parametermust be defined bycommand ADD DAS atfirst. Then it can beindexed here

SIPDAS

DAS for the domainname of the callednumber during SIPoutgoing calls

It is used get the nameof the IMS domainwhere the called partyis located throughanalyzing the callednumber during a SIPoutgoing call. It isonly used for RTP trunkgroups

OPDAS DAS for the callingnumber

It is used to analyzethe calling number inan incoming call. Thisparameter must bedefined by commandADD DAS at first. Thenit can be indexed here

PREDAS DAS for pre-analyzingthe called number

It is used to pre-analyzethe called number inan incoming call. Thisparameter must bedefined by commandADD PREDAS at first.Then it can be indexedhere

DDI Incoming called numbertransform ID

It is the index ofthe incoming callednumber transform. Thisparameter must bedefined by commandADD DDI at first. Thenit can be indexed here

OPDDI Incoming calling numbertransform ID

It is the index ofthe incoming callingnumber transform. Thisparameter must bedefined by commandADD DDI at first. Thenit can be indexed here

MINNAT Minimum nationalnumber length

It is an optionalparameter, which is aninteger ranging from 0 to26, with a default of 0.It is used to specify theminimum digit length ofthe called number duringa national incoming call



ParameterName


MAXNAT Maximum nationalnumber length

It is an optionalparameter, which is aninteger ranging from 0 to26, with a default of 26.It is used to specify themaximum digit length ofthe called number duringa national incoming call

MININT Minimum internationalnumber length

It is an optionalparameter, which is aninteger ranging from 0 to26, with a default of 0.It is used to specify theminimum digit lengthof the called numberduring an internationalincoming call

MAXINT Maximum internationalnumber length

It is an optionalparameter, which is aninteger ranging from 0 to26, with a default of 26.It is used to specify themaximum digit lengthof the called numberduring an internationalincoming call

INREG

Incoming registersignaling flag. Optionsinclude:

INVALID

It is an optionalparameter, with a defaultvalue of INVALID

OUTREG

Outgoing registersignaling flag. Optionsinclude:

INVALID

It is an optionalparameter, with a defaultvalue of INVALID

COLEN The maximum length ofCAS calling number end


BUSYRATE Trunk circuit usage

It is an optionalparameter, which isan integer rangingfrom 1 to 100, with adefault of 100. Afterthe trunk circuit usageis configured, when theratio of busy circuitsto all circuits in thistrunk group exceeds thisvalue, congestion occursin this trunk group.After the congestionis relieved, report thetrunk congestion timesand congestion durationin the performancestatistics. This



ParameterName


parameter does nottake effect when it isconfigured to 100

ROAMDAS DAS for roamingnumbers

It is an optionalparameter. After thisDAS is configured, ifthe local office servesas a GMSC, this DASis preferred for thereturned roamingnumbers. Otherwise,the roaming numberDAS configured inthe number analysistemplate is used

Q850CCIDX Q850 customizationindex


SMENTERID ID of signalingmodification entrance

IIt is an optionalparameter, associatedwith the inter-officesignaling modificationentrance. It rangesfrom 0 to 65535, with adefault of 0

Example: Create an ATM trunk group with the following re-quirements.



� User alias: RNC

� No. of the module processing the trunk group: 3


� Inter-office line signal identification: BICC


The command is:

ADD TG ATM:TG=100,OFC=100,MODULE=4,ND=101,NAME="RNC",SIGLINE=BICC,KIND=BIDIR,BWAY=NODIR,THD=100,CICSEL=ODD,DAS=0,SIPDAS=0,OPDAS=0,PREDAS=0,DDI=0,OPDDI=0,MINNAT=0,MAXNAT=26,MININT=0,MAXINT=26,INREG=INVALID,OUTREG=INVALID,COLEN=10,BUSYRATE=100,ROAMDAS=0,Q850CCIDX=0,SMENTERID=0,MLPPDM=4294967295,DISINDEX=0;

END OF STEPS






� The ATM trunk group is configured.





SET:NEID=11;




ParameterName


PCM TG PCM-belonged trunk group ID

NUM Number

It is an optional integer-typeparameter, ranging from 1 to100. In general, select the defaultvalue.

MGWPCM MGW PCMnumber

It is an optional parameter,consisting of MGWPCM_S andMGWPCM_F. The start and endnumbers of the MGW PCM meanthat the trunks corresponded byPCM resources of this numbersection can be invoked. Thisparameter is left blank when thePCM-belonged trunk number is aninteroffice BICC.

INFO Self-loop PCMnumber

It is an optional parameter, with adefault of 65535. Enter an integerranging from 0 to 65535. Ingeneral, select the default value.The corresponding self-loop PCMnumber is required in case ofconfiguring a self-loop office.

NAME Alias It is an optional parameter,consisting of 1~50 characters.

Example: Create a PCM system to the RNC office with the fol-lowing requirements:



� No. of the trunk group where the PCM system belongs:100



� User alias: RNC.


ADD SPCM:TG=100,PCM=1,NUM=3,MGWPCM="7"-"9",INFO=65535,NAME="RNC";

END OF STEPS


C h a p t e r 2

Access DataConfiguration

Table of ContentsOverview........................................................................ 193Creating Emergency Call Center ........................................ 194Special Serivce Configuration ............................................ 196LAI and GCI/Service Area Configuration.............................. 201

OverviewDescription This chapter describes how to configure the location area and the

cell data on the MSCS. When a base station is added on the radioside, the corresponding cell data need to be configured on theMSCS. When the adjacent MSC is added on the network side, theadjacent location area data need to be configured on MSCS for theproper handover between the offices.

When the MSCS is interconnected with the BSC, the special ser-vice number dialed in different cells requires to converting to dif-ferent numbers for connection. When the MSCS is interconnectedwith the RNC, the special service number dialed in different cellspossibly also requires conversion. Therefore, configuring differentspecial service attendant consoles and special service group datais required.

ConfigurationFlow

Table 92 describes the access configuration flow.

TABLE 92 ACCESS CONFIGURATION FLOW


1 Creating emergency call center ADD ECC

2 Creating a special-servicephone group ADD SSPN

3 Creating the special servicephone called number analysis ADD TPDNAL

4 Creating a LAI controlled bythe local office ADD LAI

5 Creating an adjacenet LAI ADD LAI




6 Creating a global cell ADD GCI

7 Creating a service area ADD SAI

Creating Emergency CallCenter




Context The emergency call function does not analyze the emergency callnumber. After the subscriber dials a specified emergency call num-ber in one location area, the core network will obtain the emer-gency call center index according to the location area where theemergency call is received. After that, it will find the correspond-ing number of the emergency call center number according to thethe emergency call center index, and then analyze this number.

This topic describes how to create emergency call center.



SET:NEID=11;

2. Create emergency call center with the command ADD ECC.

The explanation of the main parameters in command ADD ECCis shown in Table 93.

TABLE 93 PARAMETERS IN THE ADD ECC COMMAND

ParameterName Parameter Description Instruction

ECC Emergency Call CenterNumber

It is a mandatoryparameter, consistingof 1~32 digits

ECCIDX Emergency Call CenterIndex

It is an optionalparameter, which isan integer, ranging from0 to 255

SERVTYPE

Emergency Call ServiceType, including

� DFT: DefaultEmergency CallCenter Number

It is an optionalparameter with thedefault value DFT


Chapter 2 Access Data Configuration


� POLICE: PoliceEmergency CallCenter Number

� AMBULANCE:AmbulanceEmergency CallCenter Number

� FIRE: Fire-fightingEmergency CallCenter Number

� MARINE: MarineEmergency CallCenter Number

� MOUTAIN: MountainArea Emergency CallCenter Number

NAT

Configuration NumberType, including

� UNKNOWN:Unknown

� INTERNATIONAL:International

� NATIONAL: National

� SPECIAL: SpecialNumber Of TheNetwork

� SHORT: AbbreviatedNumber

It is an optionalparameter withethe default valueUNKNOWN

NAME AliasIt is an optionalparameter, consistingof 0~50 characters

For example, create the emergency call center. The emergencycall number is 112, the emergency call center index is 1, theemergency call service type is DFT, the configuration numbertype is international, and the alias is Emergency1. The com-mand is as follows:

ADD ECC:ECC="112",ECCIDX=1,SERVTYPE="DFT",NAT=INTERNATIONAL,NAME="Emgergency1";

END OF STEPS



Special SerivceConfigurationCreating a Special Service PhoneGroup




Context In the case of the MSCS being connected with the BSC, when youdial a special-service number in different cells, it is required toconvert this number to different numbers for connection.

In the case of the MSCS being connected with the RNC, when youdial a special-service number in different service areas, it is alsorequired to convert this number to different numbers for connec-tion.

Therefore, different special-service attendant consoles need to beconfigured.



SET:NEID=11;

2. Create a special service phone group with the command ADDSSPN.

The explanation of the main parameters in command ADDSSPN is shown in Table 94.

TABLE 94 PARAMETERS IN THE ADD SSPN COMMAND

ParameterName


SSPGID

SpecialServicePhone GroupID

It is a mandatory parameter,which is an integer, ranging form1 to 65535. It is associated withthe special-service phone groupID in the special-service groupconfiguration, exclusively defines anattendant console together with thespecial-service number

SSPGNAME

SpecialServicePhone GroupName

It is an optional parameter, consistingof 0~50 characters. It is used toidentify a special-service group



ParameterName


SSNUM 1SpecialServiceNumber 1

It is a mandatory parameter, whichis an integer, ranging form 1 to2147483647. It is the special-servicenumber, such as 114. It exclusivelydefines an attendant console togetherwith the special-service traffic groupID

PNUM1 PhoneNumber 1

It is a mandatory parameterindicating the phone console numbercorresponding to the special servicephone group ID and the specialservice number. It ranges from 0 to40



PNUM2 PhoneNumber 2




PNUM3 PhoneNumber 3




PNUM4 PhoneNumber 4




ParameterName




PNUM5 PhoneNumber 5




PNUM6 PhoneNumber 6




PNUM7 PhoneNumber 7




PNUM8 PhoneNumber 8




ParameterName




PNUM9 PhoneNumber 9




PNUM10 PhoneNumber 10


For example, create the special service phone group. The Spe-cial service phone group ID is 1, the special service number is110, the phone number is 0086251100 and the special servicephone group name is SSPN1. The command is as follows:

ADD SSPN:SSPGID=1,SSPGNAME="SSPN1",SSNUM1=110,PNUM1="0086251100";

END OF STEPS

Creating the Special Service PhoneCalled Number Analysis



� The number analyzer entry is created.

� The special service phone group is created.


Context This topic details how to create the special service called numberanalysis.





SET:NEID=11;

2. Analyze the prefix of a called number by executing commandADD TPDNAL.

The explanation of the main parameters in command ADDTPDNAL is shown inTable 95


Parame-ter Name


ENTR Number analyzer en-try

It is a mandatory parameter,which is an integer, rangingfrom 1 to 1000. Select thecorresponding analyzer entryof the analyzed number prefix.For local calls, select the corre-sponding analyzer entry of thelocal number analyzer

DIGIT Analyzed number

It is a mandatory parameter,consisting of 0~20 digits. Inputthe prefix of the called num-ber, whose length must make itbe distinguished in the local of-fice. For intra-office calls, it isrequired to configure both theprefix of the called number andthat of the local-office roamingnumber

NAME User alias

It is an optional parameter,consisting of 0~50 characters.

It is used to specificallydescribe the called numberanalysis to make it easilyrecognized

CAT Call service typesIt is an optional parameter, se-lect LSFR (Free Special ServiceOf The Current Office)


Type the special servicenumber configured in ADDSSPN

For example, create the special service called number analysiswith the following requirements:

� Number analyzer entry: 1

� User alias: SS1


� Call service types: LSFR



� Number analysis result 1 :110

� Other parameters: Use default


ADD TPDNAL:ENTR=1,DIGIT="110",NAME="SS1",SPECRST=0,SPECIDX=0,CAT=LSFR,RST1=110,RST2=0,RST3=0,CHAINAL=0,RNLEN=0,MINLEN=3,MAXLEN=20,OVLYPRI=NO,REL=NO,NET=1,NAT=DEF,OPDDICONT=NO,TPDDICONT=NO,OPDDI=0,TPDDI=0,OPDLYDDI=0,TPDLYDDI=0,DDIOVERB=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=INVALID,CALLSERVPRILVL=INVALID,RERTS=0,INCHAIN=NO,BICT=NO,ICT=0,ICTT=10,GNM=NORMAL,STBILL=INVALID,HOPDAS=0,MCA=NO,IVVR=NO,WANTL=0,IMSCENTR=NO;

END OF STEPS

LAI and GCI/Service AreaConfigurationCreating a LAI Controlled by theLocal Office



� The RNC/BSC office direction attributes are configured.

� The LAI range is set in the Resource Management system.


Context This section introduces how to configure the basic information fora Location Area ID (LAI) controlled by the BSC/RNC.

Steps 1. If no exchange is specified, execute the command SET on theMML Terminal window or select a NE from the system tree tospecify 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 com-mand ADD LAI.

The explanation of the main parameters in command ADD LAIis shown inTable 96.



TABLE 96 PARAMETERS IN THE ADD LAI COMMAND

ParameterName


LAC Location areacode (HEX)

It is a mandatory parameter,consisting of 4 HEX digits. Itshould be consistent with thatof the RNC/BSC side

NAME Alias

It is an optional parameter,consisting of 1~50 characters.It is used to describe the LAI,such as “Adjacent BSC/RNCoffice name-LAI”

ID Location area ID

It is an optional parameter.It is used to define a LAI inthe system, ranging from1~65534. If there is no specialrequirements, enter the LAIin the cell of the BSC/RNCconnected with the MSCS

VMSCIDX Virtual MSC index

It is an optional parameter.It indicates whether theBSC/RNC connected withthe MSCS accesses theMSCS through the publicdomain. If the BSC/RNCaccesses the MSCS throughthe public domain, enter 0.Otherwise, enter the index ofthe connected virtual MSC

MCC Mobile CountryCode

It is an optional parameter,consisting of 0~3 digits. Enterit according to the actualcondition, such as 460 forChina

MNC Mobile NetworkCode

It is an optional parameter.Enter the corresponding MNCof this LAI

MSC MSC number.

It indicates which MSC theaccessed RNC/BSC belongs to.It is an optional parameter,consisting of 0~16 digits.At present, in the networkmanagement system in thedefault case, if the accessedRNC/BSC is controlled by thelocal office (i.e., the BELONGfield is MSC), no MSC numberneeds to be entered. IfVMSCIDX is 0, the systemdirectly adopts the MSCnumber from the local-officemobile data. If VMSCIDX is not0, the system directly adoptsthe corresponding virtual MSCnumber from the virtual MSCconfiguration. If the accessedRNC/BSC is not controlled by



ParameterName


the local office, this parameterneeds to be entered

VLR VLR number

It indicates which VLR theaccessed RNC/BSC belongs to.It is an optional parameter,consisting of 0~16 digits.At present, in the networkmanagement system in thedefault case, if the accessedRNC/BSC is controlled bythe local office (i.e., theBELONG field is MSC), noVLR number needs to beentered. If VMSCIDX is 0, thesystem directly adopts the VLRnumber from the local-officemobile data. If VMSCIDX is not0, the system directly adoptsthe corresponding virtual VLRnumber from the virtual MSCconfiguration. If the accessedRNC/BSC is not controlled bythe local office, this parameterneeds to be entered

LOCNUM Location number

It is an optional parameter.The VLR brings the locationnumber to the HLR duringPROVIDE-SUBSCRIBER-LOCATION procedures. Entercountry code + area code,such as 8625 for Nanjing inChina

ECCIDX Emergency callindex

It is an optional parameter.Select a configured emergencycall index. If no emergencycall index is configured, select0

BSC BSC ID in the LAI

It is an optional parameter.Enter one or more adjacentBSC office IDs managingthis LAI. In case of the RANaccessing the MSCS, thereis no need to configure thisparameter

RNC RNC ID in the LAI

It is an optional parameter.Enter one or more adjacentRNC office IDs managingthis LAI. In case of the BSCaccessing the MSCS, thereis no need to configure thisparameter

TPDAS DAS for the callednumber

It is an optional parameter.Enter the originating DAS 101from the number analysisconfiguration. If no DAS isconfigured, enter 0 at first andthen modify it



ParameterName


BELONG

Belonging to,including

� NO_MSC(notbelong tolocal MSCServerdomain)

� MSC (belongto localMSC Serverdomain)

� DATTR(belong todouble homedomain)

It is an optional parameter,with MSC as the default value.If this LAI is managed bythe local office, select MSC.Otherwise, select NO_MSC. Inthis case, it is required to enterthe MSC number and VLRnumber where this LAI belongsto. IF this LAI is managed bya dual-homing domain, selectDATTR

LAIATTR

Location areaattribute,including:

� ATTBILL(Produceattempt callbill)

� NONE (none)


WDMID Work domainindex

It is an optional parameter,with 0 as the default value.In case of dual-homingnetworking, enter thedual-homing work domainindex ranging from 0 to 255

UPVER UP mode versionof MSC-B

It is an optional parameterindicating the version No. ofthe MSC user plane where thelocation area exists

R5HOCASE

Support HO Caseof Version R5,including:

� NO

� YES

It is an optional parameterand the default value is NO. Itconfigures whether the localLAI supports the R5 handover.During 3G-to-2G handover,determine the transformmode for the handover andensure the compatibility ofthe version according to theconfiguration. That is to say,when the option is YES, thehandover is done according tothe handover reason definedin R5 version. If the optionis NO, the handover is doneaccording to the handoverreason defined in R4 version

GSMSSPGIDGSM SpecialService PhoneGroup ID

It is an optional parameterranging from 0 to 65535 andit is defined by the commandADD SSPN



ParameterName


UMTSSSPGIDUMTS SpecialService PhoneGroup ID

It is an optional parameterranging from 0 to 65535. It isdefined by the command ADDSSPN

EXTINFO

Extend Info,including:

NONBCLAI(Non-BroadcastLAI in POOL)

It is an optional parameter.For the non-broadcast LAI inPOOL, the value is Null

For example, create BSC location area with the following re-quirements.

� Location area code: 12FB

� Location area identity: 201

� User alias: BSC-12FB



� Location number: 8625

� BSC ID in LAI: 99

� DAS for the called number: 1

� Other parameters: use default


ADD LAI:LAC="12FB",NAME="BSC-12FB",ID=201,MCC="460",MNC="00",LOCNUM="8625",ECCIDX=1,BSC="99",RNC="0",TPDAS=1,BELONG=NO_MSC,WDMID=0,UPVER=1,R5HOCASE=NO,GSMSSPGID=1,UMTSSSPGID=0,PAGEIDX=0,ASSTIMER=0;

END OF STEPS

Creating an Adjacent LAI



� The LAI range is set in the Resource Management system.


Context This section introduces how to create an adjacent LAI where han-dover services may occur.

When a handover occurs, the handover request message carriesthe target cell. The MSCSERVER needs to get the MSCNUM accord-ing to the LAI in the message, and judge whether the handoveroccurs within the local office. When the corresponding MSC num-ber of the LAI is different with the local MSC number, it is required



to initiates an inter-office handover to other MSC. Therefore, it isrequired to configure the number of the home MSC/VLR of the ad-jacent LAI belongs.



SET:NEID=11;

2. Create an adjacent LAI by executing command ADD LAI.

The explanation of the main parameters in command ADD LAIis shown in Table 97.

TABLE 97 PARAMETERS IN THE ADD LAI COMMAND

ParameterName


LAC Location area code(HEX)

It is a mandatory parameter.It consists of 4 HEX digits. Itshould be consistent with thatof the RNC/BSC side

NAME Alias

It is an optional parameter,consisting of 1~50 characters.It is used to describe the LAI,such as “Adjacent BSC/RNCoffice name-LAI”

ID Location area ID

It is an optional parameter.It is used to define a LAI inthe system, ranging from1~65534. If there is nospecial requirements, enterthe LAI in the cell of theBSC/RNC connected with theMSCS

VMSCIDX Virtual MSC Index

It is an optional parameter.It indicates whether theBSC/RNC connected withthe MSCS accesses theMSCS through the publicdomain. If the BSC/RNCaccesses the MSCS throughthe public domain, enter 0.Otherwise, enter the index ofthe connected virtual MSC

MCC Mobile CountryCode

It is an optional parameter,consisting of 0~3 digits. Enterit according to the actualcondition, such as 460 forChina

MNC Mobile NetworkCode

It is an optional parameter.Enter the corresponding MNCof this LAI, such as 00 forChina Mobile, and 01 forChina Unicom



ParameterName


MSC MSC number

It indicates which MSC theaccessed RNC/BSC belongs to.It is an optional parameter,consisting of 0~16 digits.At present, in the networkmanagement system in thedefault case, if the connectedRNC/BSC is controlled by thelocal office (i.e., the BELONGfield is MSC), no MSC numberneeds to be entered. IfVMSCIDX is 0, the systemdirectly adopts the MSCnumber from the local-officemobile data. If VMSCIDX isnot 0, the system directlyadopts the correspondingvirtual MSC number from thevirtual MSC configuration. Ifthe accessed RNC/BSC is notcontrolled by the local office,this parameter needs to beentered. When configuringthe adjacent LAI, enter thecorresponding MSC GT of theadjacent LAI

VLR VLR number

It indicates which VLR theaccessed RNC/BSC belongs to.It is an optional parameter,consisting of 0~16 digits.At present, in the networkmanagement system in thedefault case, if the accessedRNC/BSC is controlled by thelocal office (i.e., the BELONGfield is MSC), no VLR numberneeds to be entered. IfVMSCIDX is 0, the systemdirectly adopts the VLRnumber from the local-officemobile data. If VMSCIDX isnot 0, the system directlyadopts the correspondingvirtual VLR number from thevirtual MSC configuration. Ifthe accessed RNC/BSC is notcontrolled by the local office,this parameter needs to beentered. When configuringthe adjacent LAI, enter thecorresponding VLR GT of theadjacent LAI

LOCNUM Location number

It is an optional parameter.The VLR brings the locationnumber to the HLR duringPROVIDE-SUBSCRIBER-LOCATION procedures. Entercountry code + area code,such as 8625 for Nanjing inChina



ParameterName


BELONG

Belonging,including

� NO_MSC(notbelong to localMSC Serverdomain)

� MSC (belongto localMSC Serverdomain)

� DATTR(belong todouble homedomain)

It is an optional parameter,with MSC as the default value.If this LAI is managed bythe local office, select MSC.Otherwise, select NO_MSC.In this case, it is required toenter the MSC number andVLR number where this LAIbelongs to. IF this LAI ismanaged by a dual-homingdomain, select DATTR

LAIATTR

Location areaattribute,including:

� ATTBILL(Produceattempt callbill)

� NONE (none)


WDMID Work domainindex

It is an optional parameter,with 0 as the default value.In case of dual-homingnetworking, enter thedual-homing work domainindex ranging from 0 to 255

UPVER UP mode versionof MSC-B

It is an optional parameterindicating the version No. ofthe MSC user plane where thelocation area exists

R5HOCASE

Support HO Caseof Version R5,including:

� NO

� YES

It is an optional parameterand the default value is NO. Itconfigures whether the localLAI supports the R5 handover.During 3G-to-2G handover,determine the transformmode for the handover andensure the compatibility ofthe version according to theconfiguration. That is to say,when the option is YES, thehandover is done according tothe handover reason definedin R5 version. If the optionis NO, the handover is doneaccording to the handoverreason defined in R4 version

GSMSSPGIDGSM SpecialService PhoneGroup ID

It is an optional parameterranging from 0 to 65535 andit is defined by the commandADD SSPN



ParameterName


UMTSSSPGIDUMTS SpecialService PhoneGroup ID

It is an optional parameterranging from 0 to 65535. It isdefined by the command ADDSSPN

EXTINFO

Extend Info,including:

NONBCLAI(Non-BroadcastLAI in POOL)

It is an optional parameter.For the non-broadcast LAI inPOOL, the value is Null

For example, create the BSC location area with the followingrequirements.

� Location area code: 1111

� Location area identity: 301

� User alias: BSC-1111



� Location number: 8625

� VLR number: 8613954353

� Belong type: NO_MSC



ADD LAI:LAC="1111",NAME="BSC-1111",ID=301,MCC="460",MNC="01",MSC="8613954353",VLR="8613954353",LOCNUM="8625",ECCIDX=0,BSC="0",RNC="0",TPDAS=0,BELONG=NO_MSC,WDMID=0,UPVER=1,R5HOCASE=NO,GSMSSPGID=0,UMTSSSPGID=0,PAGEIDX=0,ASSTIMER=0;

END OF STEPS

Creating a Global Cell



� The DAS for the called number is configured.

� The BSC LAI is configured.


Context When the BSC accesses the MSCS, it is required to configure theglobal cell data. When a GSM handover occurs, the handover-originated office (intra/inter-office handover) needs to know thehome BSC of the handover-terminated cell, so that it can initiatesa handover request to the BSC.





SET:NEID=11;

2. Create a global cell by executing command ADD GCI.

The explanation of the main parameters in command ADD GCIis shown in Table 98.

TABLE 98 PARAMETERS IN THE ADD GCI COMMAND

Parame-ter Name


LAIID Location area ID

It is a mandatory parameter,ranging 1 to 65534. Select thehome LAI of the cell from the listof configured LAIs

GCI Cell Identity(hex)

It is an optional parametercomposed of GCIBEGIN (CellIdentity Begin) and GCIEND (CellIdentity End). The format of it isCIB-CIE. Configure it according tothe real conditions. It should beconsistent with that of the BSCside

TPDAS Called NumberSelector

It is an optional parameter. Itranges from 0 to 4096, witha default of 0. It may not beconfigured here. During the calldata configuration, it could bemodified and the referred valueis the number analysis selector inthe number analysis configuration

BSC BSC OfficeIt is an optional parameter, rangingfrom 0 to 3000. Select the BSCoffice that manages this cell

GCIATTR

Cell Attribute,including

NONE (none)

ATTBILL(produceattempt call bill)

It is a mandatory parameter

NAME Alias It is an optional parameter,consisting of 0~50 characters

SSPGID Special servicephone group ID

It is an optional parameter rangingfrom 0 to 65535. It is defined bythe command ADD SSPN

VMSCIDX Virtual MSCIndex

It is an optional parameter. Itranges from 0 to 65535. If 0is selected, it represents publicdomain, if 0 is not selected,



Parame-ter Name


the virtual MSC index should beentered.

ECCIDX Emergency callindex

It is an optional parameter rangingfrom 0 to 65535.

For example, create the global cell with the following require-ments.

� Location area ID: 201

� Called number selector: 101

� Cell identity (Hex): 1111-1111


� Alias: GCI1

� Special service phone group ID: 1

� Emergency call index: 1

� Other parameters: adopt the default value.


ADD GCI:LAIID=201,GCI="1111"-"1111",TPDAS=1,BSC=99,NAME="GCI1",SSPGID=1,ECCIDX=1;

END OF STEPS

Creating a Service Area



� The RNC LAI is created.


Context During the RNC access, it is required to configure the data for theservice area.

Steps 1. If the exchange is not specified, execute the command SETon the MML Terminal window or select a NE from the systemtree to specify the exchange to be configured.


SET:NEID=11;

2. Create a service area with the command ADD SAI.

The parameter description of the command ADD SAI is shownin Table 99.



TABLE 99 PARAMETERS IN THE ADD SAI COMMAND

ParameterName


LAIID LocationArea ID

It is a mandatory parameter rangingfrom 1 to 65534. Select the home LAIof the cell from the list of the config-ured LAIs

SAC Service AreaCode (hex)

It is a mandatory parameter com-posed of SACB (Service Area CodeBegin) and SACE (Service Area CodeEnd). The format is SACB-SACE.Configure it according to the real con-ditions. It should be consistent withthat of the RNC side

RNC RNC OfficeIt is an optional parameter rangingfrom 0 to 2048. Select the RNC officethat manages this service area

NAME Alias It is an optional parameter rangingfrom 0 to 50 characters

SSPGIDSpecial Serv-ice PhoneGroup

It is an optional parameter rangingfrom 0 to 65535 and it is defined bythe command ADD SSPN

VMSCIDX Virtual MSCIndex

It is an optional parameter rangingfrom 0 to 65535. If 0 is selected, itmeans the common domain. If it isnot 0, enter the accessed virtual MSCindex No.

ECCIDX Emergencycall index

It is an optional parameter rangingfrom 0 to 65535.

For example, create a service area identity with the followingrequirements. The is 201, the , and the is 100. For the otherparameters, select the default value. The command is as fol-lows:

� Location area ID: 201

� Service area code: 0000


� Alias: SAI1

� Special service phone group: 1

� Emergency call index: 1



ADD SAI:LAIID=201,SAC="0000"-"0000",RNC=100,NAME="SAI1",SSPGID=1,ECCIDX=1;

END OF STEPS


C h a p t e r 3

Number Analysis DataMaking

Table of ContentsNumber Analysis ............................................................. 213Number Analysis Configuration.......................................... 218

Number AnalysisThe switch performs network addressing based on each type ofnumbers. In the mobile switch, there are two types of numbers.One type is subscriber number, including fixed subscriber numberand mobile subscriber number. The other type is network num-ber, including Mobile Station Roaming Number (MSRN), MSC/VLRnumber, HLR number, and handover number. ZXWN MSCS num-ber analysis configuration is used to determine the correspondingnetwork addressing and service processing methods of each typeof number to ensure that the switch can correctly perform signal-ing interaction and voice channel connection.

ZXWN MSCS system provides seven number analyzers: new ser-vice number analyzer, CENTREX number analyzer, private-networknumber analyzer, special-service number analyzer, local-networknumber analyzer, national toll-service number analyzer, and inter-national toll-service number analyzer. For a specified DAS, num-bers pass each type of analyzers specified by this DAS in a fixedorder. The analyzers strictly follow the following order to performnumber analysis, as shown in Figure 11.



FIGURE 11 ANALYSIS ORDER OF NUMBER ANALYZERS

Configuration instances of common DASs and the number analysisresults are as follows:

1. DAS for pre-analyzing the called number

It is used to process special dial prefixes, including performingcall restriction, format conversion of the called number.

After an exchange receives “10193+called number” dialed bya subscriber, 10193 is deleted in this exchange, and the subse-quent routing is based on the existing traffic routing, as shownin Table 100.

TABLE 100 DAS FOR PRE-ANALYZING THE CALLED NUMBER

AnalyzerEntry Analyzed Number Analysis Result

10193 + 0 + local areacode

If call restriction isrequired, analyze it to“pre-analysis ending, andcall rejected”

If no call restriction isrequired, analyze it to“pre-analysis normallyending”, and delete“10193 + 0 + local areacode” from the changeindex of the callednumber

10193 + 0 + non-localarea code

10193 + G networknumber section

Newservicenumberanalyzer

10193 + C networknumber section

Analyze it to“pre-analysis normallyending”, and delete10193 from the changeindex of the callednumber.

Whether to add 10193 tothe called-number indexin the CDR dependson the CDR fillingrequirements on thebilling center


Chapter 3 Number Analysis Data Making

2. Originating DAS: used to analyze the called number in the lo-cal-office-originated call, as shown in Table 101.

TABLE 101 ORIGINATING DAS


Newservicenumberanalyzer

Charging query number Analyze it to the SSPcharging query service

Free special-servicenumber

Analyze it to thelocal-office free specialservice, pointing tothe special-servicenumber configured onthe attendant console

Corresponding attendantconsole number of thespecial-service number

Analyze it to theoutgoing free specialservice, pointing to thespecial-service circuitgroup

Short number -

Special-servicenumberanalyzer

Special-service numberof the operator

Analyze it to theoutgoing free specialservice, pointing to thespecial-service circuitgroup

Vacant number

0 All numbers are analyzedby the subsequentanalyzers

Local PSTN number

Analyze it tothe local-networkoutgoing/local-callservice, pointing tothe gateway office

Local number section ofother mobile network


Non-local number sectionof other mobile network

Analyze it to theautomatic service inthe national toll region,pointing to the tandemoffice of the local province

Local-networknumberanalyzer

Number section of thelocal mobile network

Analyze it to the MSCcommon service




Vacant number

0 All numbers are analyzedby the subsequentanalyzers

0 + Local area code +Local PSTN number


Nationaltoll-servicenumberanalyzer

0 + Non-local area code

Analyze it to theautomatic service inthe national toll region,pointing to the tandemoffice of the local province

Inter-nationaltoll-serv-ice numberanalyzer

00 + Internationalnumber

Analyze it to theinternational tollautomatic service

3. Forwarding DAS: used to analyze the number to which the callis forwarded, as shown in Table 102.

TABLE 102 FORWARDING DAS

Analyzer Entry Analyzed Number Analysis Result

Vacant number

0 All numbers areanalyzed bythe subsequentanalyzers

Local PSTN number

Analyze it to thelocal-networkoutgoing/local-callservice, pointing tothe gateway office

Local numbersection of othermobile network


Non-local numbersection of othermobile network

Analyze it to theautomatic servicein the national tollregion, pointing tothe tandem office ofthe local province

Local-networknumber analyzer




Number section ofthe local mobilenetwork

Analyze it to the MSCcommon service

Vacant number

0 All numbers areanalyzed bythe subsequentanalyzers

0 + Local areacode + Local PSTNnumber


National toll-servicenumber analyzer

0 + Non-local areacode

Analyze it to theautomatic servicein the national tollregion, pointing tothe tandem office ofthe local province

4. Roaming DAS: used to analyze the roaming number in the re-sponse message to the routing information query message, asshown in Table 103. It is unnecessary to analysis the CC innational roaming numbers.

TABLE 103 ROAMING DAS


Roaming numbersection of the localservice area in thelocal office

Analyze it to thelocal MSC service

Roaming numbersection of non-localservice area in thelocal office

Analyze it to theoutgoing service ofthe local MSC.

Note: The roamingDAS is used whenthere is no directvoice channelbetween MGWs(switched throughthe T office) in theregion networking

National otherroaming sections

Analyze it to thenational toll call

Local-networknumber analyzer

00 + Internationalnumber

Analyze it to theinternational tollautomatic service



Number AnalysisConfigurationOverview

Description This section only introduces the basic steps of number analysis.For detailed configuration related with number analysis (includ-ing number pre-analysis, calling number analysis, and numberchange), refer to ZXWN MSCS MSC Server Number Analysis.

Data Configura-tion

The related operations of the number analysis configuration are asfollows.

Steps Operations Instructions Commands

1 Creating a numberanalyzer entry

Specify an IDfor each type ofnumber analyzers

ADD ENTR

2 Creating a DAS

The DAS is thecollection ofvarious numberanalyzer entries,specifying theorder and ruleof performingnumber analysis.

ADD DAS

3Setting the defaultDAS template ofthe local office

Set the defaultDAS templateof the localoffice meanscreating the DASused for local-office serviceprocessing.

SET LDASTMPLT

4Creating aDAS template(optional)

Create multipleDAS templates inthe dual-homingor regionalnetworking.

ADD ACRTMPLT

5 Creating the callednumbers analysis

Create numberanalysis forprefixes of callednumbers androaming numbers

ADD TPDNAL

Creating a Number Analyzer Entry





� The number analyzer entry range is set in the resource man-agement system.


Context Creating number analyzer entries means specifying an ID for eachtype of number analyzers.



SET:NEID=11;

2. Create a number analyzer entry by executing command ADDENTR.

The explanation of the main parameters in command ADDENTR is shown in Table 104.

TABLE 104 PARAMETERS IN THE ADD ENTR COMMAND

ParameterName


ID Analyzer entry


NAME User aliasIt is a mandatoryparameter, consisting of0~50 characters

TYPE Analyzer entry type

It is an optionalparameter. Referto Table 105 for theconfiguration description

NTYPE

Number analysis resultunder this analyzer,including CALLED(analysis on callednumbers), CALLING(analysis on callingnumbers), FORWARD(analysis on callingnumbers during callforwarding), OPIMSI(analysis on calling IMSInumbers), TPIMSI(analysis on calledIMSI numbers), andFWDIMSI (analysis onIMSI numbers duringcall forwarding)

It is an optionalparameter, with CALLEDas the default value. Ingeneral, select CALLED


It is an optionalparameter, which isan integer, rangingfrom 0 to 65535. Enterit according to theactual condition. Thedefault value is 0 (publicdomain)



TABLE 105 ANALYZER ENTRY TYPES

ParameterName

Parameter Descrip-tion

ConfigurationDescription

NEWSRV New service numberanalyzer

After this analyzeris configured, if thenumber is not matchedin this analyzer, it is sentto the next entry foranalysis

CENTREX CENTREX numberanalyzer

This analyzer is notconfigured

PRINET Private-network numberanalyzer

This analyzer is notconfigured

SPECSRV Special-service numberanalyzer

After this analyzeris configured, if thenumber is not matchedin this analyzer, it is issent to the next entryfor analysis

LOCAL Local-network numberanalyzer

After this analyzeris configured, if thenumber is not matchedin this analyzer, theanalysis ends

NATIONAL National toll-servicenumber analyzer

After this analyzeris configured, if thenumber is not matchedin this analyzer, theanalysis ends

INTER International toll-servicenumber analyzer

After the number isanalyzed in this analyzer,the analysis ends

Example: Create a number analyzer entry with the followingrequirements.

� 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=CALLED;

END OF STEPS



Creating a DAS



� The DAS range is set in the resource management system.



Context The DAS is the collection of various number analyzer entries, spec-ifying the order and rule of performing number analysis.

Table 106 lists common DASs.

TABLE 106 COMMON DASS

ParameterName Parameter Description Configuration

Description

MS MS originatingUsed to analyze the callednumber when an MSoriginates a call

MSRN Mobile station roamingnumber

Used to analyze roamingnumbers or handovernumbers

CNG Calling number analysis Used for traffic division ofcalling numbers

LI Intercepted number Used for the interceptionfunction

PBRT Personal Back Ring Tone Used for the PBRT function

FWD Forwarding numberanalysis

Used to analyze thethird-party number towhich the call is forwarded

PREDAS Number pre-analysis

Used for the numberpre-analysis function,standardizing callednumbers, and performingcall restriction based onnumbers



SET:NEID=11;

2. Create a DAS by executing command ADD DAS.

The explanation of the main parameters in command ADDDASis shown in Table 107.



TABLE 107 PARAMETERS IN THE ADD DAS COMMAND

ParameterName


ID DAS

It is a mandatoryparameter, which is aninteger, ranging from1 to 4096. It is theindex number of thenewly-added DAS

NAME User aliasIt is an optionalparameter, consisting of0~50 characters.

NEWSRV New service numberanalyzer entry

CENTR CENTREX numberanalyzer entry

PRINET Private-network numberanalyzer entry

SPECSRV Special-service numberanalyzer entry

LOCAL Local-network numberanalyzer entry

NATIONAL National toll-servicenumber analyzer entry

INTERInternationaltoll-service numberanalyzer entry


Enter the umberanalyzer entry IDscontained by a DAS

Example: Create a MS originating DAS with the following re-quirements.

� DAS ID: 101

� User alias: MSQH

� Local number analyzer entry: 1


The command is:

ADD DAS:ID=101,NAME="MSQH",NEWSRV=0,CENTR=0,PRINET=0,SPECSRV=0,LOCAL=1,NATIONAL=0,INTER=0;

END OF STEPS



Setting the Default DAS Template ofthe Local Office



� The DAS is configured.


Context Creating the default DAS template of the local office means creat-ing the DAS used for local-office service processing.



SET:NEID=11;

2. Set the default DAS template of the local office by executingcommand SET LDASTMPLT.

The explanation of the main parameters in command SETLDASTMPLT is shown in Table 108.

TABLE 108 PARAMETERS IN THE SET LDASTMPLT COMMAND

Parame-ter Name


MS MS originatingDAS

It is an optional parameter, whichis an integer, ranging from 0to 4096. It is used to analyzethe called number when an MSoriginates a call. If the calledparty is a mobile subscriber,the MSC needs to query therouting information from thecorresponding HLR. If the calledparty is a fixed subscriber, theMSC connect the call to thecorresponding local exchange ortoll exchange according to locationof the called party

MSRN MSRN DAS

It is an optional parameter, whichis an integer, ranging from 0to 4096. It is used to analyzethe MSRN returned from theHLR, and judge whether the callbelongs to the local-office mobileservice or outgoing mobile servicebased on this number. If the callbelongs to the local-office mobileservice, this number is sent tothe corresponding module forprocessing. If the call belongs tothe outgoing mobile service, selectthe corresponding route chainfor call connection. In addition,



Parame-ter Name


this DAS also analyzes forwardingnumbers returned from the HLR,and subscriber numbers fromother mobile office or fixed office

OR Preferredrouting DAS

It is an optional parameter, whichis an integer, ranging from 0 to4096.

When it is set that the local officesupports preferred routing in theglobal variable control system,configure this DAS for internationalroaming call and the forwardingservice

CNG Calling numberDAS


It is used to analyze the callingnumber in outgoing calls toimplement traffic division of thecalling number and calling numberchange function

LI InterceptionDAS


It is used for the interceptionservice

IP IP DAS


It is used for the IP telephoneservice

ICBCNG

Incoming callrestriction DASfor callingnumbers


It is used for the incoming callrestriction service

PBRT PBRT DAS


It is used for the PBRT service

FWD Forwarding DASIt is an optional parameter, whichis an integer, ranging from 0 to4096

FWDCNGForwardingDAS for callingnumbers

It is an optional parameter, whichis an integer, ranging from 0 to4096

CNGVIGWCalling numberDAS of virtualIGW




Parame-ter Name


FWDVIGW Forwarding DASof virtual IGW


INTRAWire andwirelessintegrated DAS

It is an optional parameter, whichis an integer, ranging from 0 to4096. It is used for the functionof one number for two MSs andmixed group

ROUTCAT1

MS originatingDAS forcategory-1subscribers


ROUTCAT2



ROUTCAT3



ROUTCAT4



ROUTCAT5



IMSIOP-DAS

Outgoing IMSItraffic divisionDAS


OVERLAY CallingOVERLAY DAS


IGWMONI-TOR

IGWinterceptionDAS


SHLRSKEYSHLR servicekey conversionDAS


IMSITPDAS DAS for calledIMSI


IMSIFW-DAS

DAS for theIMSI of thesubscriber towhom the call isforwarded




Parame-ter Name


TESTCALL-DAS Test call DAS


MRBTMulti-mediaring back toneDAS


INTPRE-DAS

Internationalnumberpre-analysisDAS


PREDASNumberpre-analysisDAS


RE-CNCTDAS

ReconnectionDAS


Example: Configure the default DAS template of the local officewith the following requirements.

� MS originating DAS: 101

� MSRN DAS: 201

� Forwarding DAS: 301.

The command is:

SET LDASTMPLT:MS=101,MSRN=201,FWD=301;

END OF STEPS

Creating a DAS Template




Context It is required to create multiple DAS templates in the dual-homingor regional networking.



SET:NEID=11;

2. Create a DAS template by executing command ADD ACRTMPLT.



The explanation of the main parameters in command ADDACRTMPLT is shown in Table 109.

TABLE 109 PARAMETERS IN THE ADD ACRTMPLT COMMAND

ParameterName


TMPLIDX Routing template IDIt is a mandatoryparameter, rangingfrom 1~65535

NAME User aliasIt is a mandatoryparameter, consistingof 1~50 characters

MS MS originating DAS


MSRN MSRN DAS


OR Preferred routing DAS


CNG Calling number DAS


LI Interception DAS


IP IP DAS


CBCNG Incoming call restrictionDAS for calling numbers


PBRT PRBT DAS


FWD Forwarding DAS




ParameterName


FWDCNG Forwarding DAS forcalling numbers


CNGVIGW Calling number DAS ofvirtual IGW


FWDVIGW Forwarding DAS ofvirtual IGW


INTRA Wire and wirelessintegrated DAS

It is an optionalparameter, which isan integer, ranging from0 to 4096. It is usedfor the function of onenumber for two MSs andmixed group

ROUTCAT1 MS originating DAS forcategory-1 subscribers










IMSIOPDAS Calling IMSI numberselector


OVERLAY Calling OVERLAY DAS




ParameterName


LIIGW IGW interception DAS


SHLRSKEY SHLR service key DAS


IMSITPDAS DAS for called IMSI


IMSIFWDASDAS for the IMSI of thesubscriber to whom thecall is forwarded


MBRT Multi-media ring backtone DAS


INTPREDAS International numberpre-analysis DAS


PREDAS Number pre-analysisDAS


RECNCTDAS Reconnection DAS


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


The command is:

ADD ACRTMPLT:TPLIDX=1,NAME="VMSC1",MS=101,MSRN=201,OR=301,CNG=401,LI=0,IP=0,CBCNG=0,PBRT=0,CFU=0,CFUCNG=0,CFNDUB=0,CFNDUBCNG=0,CFUDUB=0,CFUDUBCNG=0,CFNRC_E=0,CFNRCCNG_E=0,CFNRC_L=0,CFNRCCNG_L=0,CFNRY=0,CFNRYCNG=0,CD



=0,CDCNG=0,FWD=0,FWDCNG=0,CNGVIGW=0,FWDVIGW=0,INTRA=0,ROUTCAT1=0,ROUTCAT2=0,ROUTCAT3=0,ROUTCAT4=0,ROUTCAT5=0,IMSIOPDAS=0,OVERLAY=0,LIIGW=0,SHLRSKEY=0,IMSITPDAS=0,IMSIFWDAS=0,MBRT=0,INTPREDAS=0,PREDAS=0,CFPRE=0,CFUPRE=0,NDUBPRE=0,UDUBPRE=0,CFNRCE_PRE=0,CFNRCL_PRE=0,CFNRYPRE=0,CDPRE=0,MORCPRE=0,GMSCRCPRE=0,CFRCPRE=0,MTRCPRE=0,RECNCTDAS=0,CAMELDNALIDX=0,SSDAS=0,ASCODEDAS=0;

END OF STEPS

Creating the Called Number Analysis





Context This section introduces how to configure number analysis for pre-fixes of called numbers and roaming numbers. The called numberanalysis determines the subsequent service procedures of the call.



SET:NEID=11;

2. Analyze the prefix of a called number or roaming number byexecuting command ADD TPDNAL.

The explanation of the main parameters in command ADDTPDNAL is shown in Table 110.


ParameterName


ENTR Numberanalyzer entry

It is a mandatory parameter, whichis an integer, ranging from 1 to1000. Select the correspondinganalyzer entry of the analyzednumber prefix. For local calls,select the corresponding analyzerentry of the local number analyzer

DIGIT Analyzernumber

It is a mandatory parameter,consisting of 1~20 digits. Inputthe prefix of the called number,whose length must make it bedistinguished in the local office.For intra-office calls, it is requiredto configure both the prefix of



ParameterName


the called number and that of thelocal-office roaming number

NAME User alias

It is an optional parameter,consisting of 0~50 characters.

It is used to specifically describethe called number analysis tomake it easily recognized

SPECRST Special analysisresult rule

It is used to specify the indexnumber of the special analysisresult rule for the associated callednumber. This parameter mustbe defined by command ADDCEDSPECRL at first. Then it canbe indexed here. This parameteris configured to implement therouting service based on numberlength. When the system performsanalysis on the called number,it automatically matches theactual length of the called numberto see whether the length iswithin the range of “Specialanalysis result rule for callednumbers”. If the length is withinthe range, the system adopts therouting information in “Specialanalysis result of called numbers”.Otherwise, the system adopts therouting information in the callednumber analysis

SPECIDX Special analysisresult index

It is used to specify the indexnumber of the special analysisresult of the associated callednumber. This parameter mustbe defined by command ADDSPECRST at first. Then it canbe indexed here. This parameteris configured to implement therouting service based on numberlength. When the system performsanalysis on the called number,it automatically matches theactual length of the called numberto see whether the length iswithin the range of “Specialanalysis result rule for callednumbers”. If the length is withinthe range, the system adopts therouting information in “Specialanalysis result of called numbers”.Otherwise, the system adopts therouting information in the callednumber analysis



ParameterName


CAT

Call servicetypes, includingthe options inTable 111

It is an optional parameter. It isused to specify the service typetriggered by this number, anddetermine the direction of thiscall. The system adopts “vacantnumber” by default.

The called number of the localoffice is analyzed to MSCO (MSCcommon service). The roamingnumber of the local office isanalyzed to MSLL (MSC localservice). The roaming number ofother office is analyzed to MSLO(MSC local outgoing service)

RST1Numberanalysis result1

When the call service type isvacant number, local-networklocal-office/common service, MSClocal-network local-office service,Mobile Number Portability (MNP),or H323 call, number analysisresult 1 must be fixed to 0. Whenthe call service type is outgoingcall or toll call, number analysisresult 1 is used to specify theindex number of the outgoingroute chain.

When the call service type isequal access: CIC of theoperator where the subscriberis located or equal access:non-local-network CIC, numberanalysis result 1 is used to specifythe index number of the outgoingroute chain.

When the call service type isOVERLAY prefix incomingservice, number analysis result1 is used to specify the indexnumber of the outgoing routechain. When the call service typeis OVERLAY: CAMEL servicetriggered by MO, or OVERLAY:CAMEL service triggered by MT,number analysis result 1 is usedto specify the index number of theoutgoing route chain.

When the call service type is IPservice, IP mobile service, orindependent IP service numberanalysis result 1 is used to specifythe index number of the outgoingroute chain.

When the call service type isMNP outgoing routing numberanalysis result 1 is used to specifythe index number of the outgoingroute chain.

When the call service type isOutgoing paid special service



ParameterName


or Outgoing free specialservice, number analysis result1 is used to specify the indexnumber of the outgoing routechain.

The above-specified index numberof the outgoing route chain mustbe defined by command ADDCHAIN at first. Then it can beindexed here.

When the call service type isMobile emergency specialservice, Local-office paidspecial service or Local-officefree special service, numberanalysis result 1 is used to specifythe special-service number. Thisparameter must be defined bycommand ADD SSPN at first.Then it can be indexed here.

When the call service type is Toneplay service, CAT_SEND_TONE,number analysis result 1 is usedto specify the ID of the tone to beplayed


It is used to specify the indexnumber of CAMEL accesssubscription information of thecalling subscriber. This parametermust be defined by commandADD CAINFO at first. Then itcan be indexed here. When thecall service type is equal access:CIC of the operator where thesubscriber is located or “equalaccess: non-local-network CIC,this parameter must be configured.

When the call service type isOVERLAY: CAMEL servicetriggered by MO, or OVERLAY:CAMEL service triggered byMT, this parameter must beconfigured. When the call servicetype is other types except theabove-listed, number analysisresult 2 must be fixed to 0


It is used to specify the indexnumber of CAMEL accesssubscription information of thecalled subscriber. This parametermust be defined by command ADDCAINFO at first. Then it can beindexed here.

When the call service type isOVERLAY: CAMEL servicetriggered by MO, or OVERLAY:CAMEL service triggered byMT, this parameter must beconfigured. When the call service



ParameterName


type is other types except theabove-listed, number analysisresult 3 must be fixed to 0

CHAINAL Route chaninanalysis index

It is used to specify the analysisindex number of the route chain.This parameter must be definedby command ADD CHAINAL atfirst. Then it can be indexed. Thisparameter takes effect only whenthe call service type is outgoingservice (including various outgoingservices). It priority is higher thanthat of the outgoing route chainreferred to in number analysisresult 1. Route chain analysis isan intelligent routing policy betterthan the policy of specifying asingle route chain

RNLENLength of thecarried routingnumber

When the call service type is MNPoutgoing routing, it is configuredto the length of the carried routingnumber. When the call servicetype is other types except theabove-listed, it must be fixed to 0

MINLENMinimum digitlength ofnumbers

It is an optional parameter, whichis an integer ranging from 0 to255, with a default of 3. It isused to specify the minimum digitlength of the analyzed numberrequired for call connection.

During an incoming call, if thereceived digits are shorter thanthis length, the system waitsfor the subsequent digits. If thesystem judges that there is nosubsequent digit, and the receiveddigits are shorter than this length,the system considers that thenumber format is wrong, andreleases the call.

During a local-office-originatedcall, if the received digits areshorter than this length, thesystem considers that the numberformat is wrong, and releases thecall.

For the OVERLAY prefix incomingservice, the system gets the lengthof the OVERLAY prefix accordingto the minimum digit length ofnumbers. Therefore, it is requiredto configure the minimum digitlength of numbers to the length ofthe OVERLAY prefix. Otherwise,procedures cannot be correctlyprocessed



ParameterName


MAXLENMaximumdigit length ofnumbers

It is an optional parameter, whichis an integer ranging from 0 to255, with a default of 20. It isused to specify the maximum digitlength of the analyzed numberrequired for call connection.

During an incoming call, it isthe basis of whether to waitfor subsequent digits. If thereceived digits reach this length,the system does not wait forsubsequent digits.

During a local-office-originatedcall, if the received digits arelonger than this length, the systemdetermines whether to continue orrelease the call according to flag“No call when the called numberexceeds the length” in the optionenabling configuration. If thesystem determines to continue thecall, it cuts the exceeding digits

OVLYPRI

OVERLAYpriority,including:

NO (Nopriority):Trigger theintelligentservice basedon CSI atfirst, andthen triggerthe intelligentservice againbased onOVERLAY

HCSI (Higherthan the CSIin priority):Trigger theintelligentservice basedon OVERLAYat first, andthen triggerthe intelligentservice againbased on CSI

It is used to the priority relationshipbetween triggering the intelligentservice based on CSI and triggeringthe intelligent service based onOVERLAY. The system adopts NoPriority by default. When the callservice type is OVERLAY(CAMELservice triggered by MO), thisparameter is effective. Otherwise,this parameter is ineffective



ParameterName


REL

Voice channelrelease mode,including:

CING (callingcontrolrelease):The callingparty controlswhether torelease thecall. In thismode, whenonly the calledparty hooks on,the call still cancontinue.

CED(calledcontrolrelease):The calledparty controlswhether torelease the call.In this mode,when only thecalling partyhooks on, thecall still cancontinue.

NO (non-controlrelease): Boththe callingparty and thecalled partycan controlwhether torelease the call.In this mode,no matterwhether thecalling party orthe called partyhooks on, thecall is released

It is an optional parameter. Itindicates a resource release modewhen subscribers hook on. Ingeneral, select NO. Select CED forsuch special numbers as 110 and119

NETType of thedestinationnetwork

It is an optional parameter, witha default of 1. For calls to otheroffice in the local network, selectthe signaling network where thedestination office is located. Forintra-office calls, this option ismeaningless.



ParameterName


NAT

Numberaddressattribute,including:DEF (defaultattribute): Donot replacethe addressattribute ofthe analyzednumber.

INT(internationalnumber):Replace theaddressattribute ofthe analyzednumber withinternationalnumber.

NAT (nationalnumber):Replace theaddressattribute ofthe analyzednumber withnational (valid)number.

LOC(localnumber):Replace theaddressattribute ofthe analyzednumber withlocal number.

UNK (attributeunknown):Replace theaddressattribute ofthe analyzednumber withunknown

It is an optional parameter. Itis used to replace the addressattribute of the analyzed number.In general, it is set to DEF, or isset according to the requirementsof the peer end

OPDDI-CONT

Transformingthe callingnumber again,including:

NO (Notallowed): It isnot allowed totransform thecalling numberagain in thesubsequent callprocedures.

It is an optional parameter. Itis used to specify whether it isallowed to transform the callingnumber again in the subsequentcall procedures when the callingnumber was already transformedonce. The system adopts NO bydefault



ParameterName


YES (allowed):It is allowed totransform thecalling numberagain in thesubsequent callprocedures.

TPDDI-CONT

Transformingthe callednumber again,including:

NO (Notallowed): It isnot allowed totransform thecalled numberagain in thesubsequent callprocedures.

YES (allowed):It is allowed totransform thecalled numberagain in thesubsequent callprocedures

It is an optional parameter. Itis used to specify whether it isallowed to transform the callednumber again in the subsequentcall procedures when the callednumber was already transformedonce. The system adopts NO bydefault

OPDDI

Calling-numberimmediatetransformindex

It is an optional parameter. Itis the number stream transformindex of the calling-numberimmediate transform. Immediatetransform immediately makes thecalling number transformed. Thisparameter must be defined bycommand ADD DDI at first. Thenit can be indexed here

TPDDI

Called-numberimmediatetransformindex

It is an optional parameter. Itis the number stream transformindex of the called-numberimmediate transform. Immediatetransform immediately makes thecalled number transformed. Thisparameter must be defined bycommand ADD DDI at first. Thenit can be indexed here

OPDLYDDICalling-numberdelay transformindex

It is an optional parameter. Itis the number stream transformindex of the calling-number delaytransform. Delay transform takeseffects in the IAM message at theoutgoing side instead of makingthe calling number transformedimmediately. This parameter mustbe defined by command ADD DDIat first. Then it can be indexedhere.

According to the IAM message atthe outgoing side, perform thecalling-number delay transform



ParameterName


here, and then perform thecalling-number delay transform inthe number pre-analysis

TPDLYDDICalled-numberdelay transformindex

It is an optional parameter. Itis the number stream transformindex of the called-numberimmediate transform. Immediatetransform immediately makes thecalled number transformed. Thisparameter must be defined bycommand ADD DDI at first. Thenit can be indexed here

DDIOVERB

B-interfacenumbertransformindex

It is the number stream transformindex of the called number in theoutgoing call request messagebetween the MSC and the VLR. Thetransform purpose is to facilitatethe VLR judging the toll callauthority. This parameter must bedefined by command ADD DDI atfirst. Then it can be indexed here

IWVEDIO

Whether tosupport theinterworkingbetween videocalls, including:

LSUP:Local-networksubscriberssupport theinterworkingbetweenvideo calls bydefault). Thecall continues.

OSUP:Subscribers inother networkssupport theinterworkingbetween videocalls). The callcontinues.

ONSUP:Subscribersin othernetworks donot support theinterworking

It is an optional parameter. It isused to specify whether to supportthe interworking between videocalls. The default value is LSUP

TIMELMTMaximumcall duration(minute)

It is used to specify the maximumcall duration allowed for a call.When the duration of a call reachesthe maximum call duration, thesystem automatically release thecall. If it is unnecessary to restrictthe maximum call duration, adoptthe default value of 0



ParameterName


AUXDAS Assistant DAS

It is an optional parameter. Itis used to specify the DAS foranalyzing the called number againwhen the call service type isoutgoing service, and when theconnection between the local officeand the mutually-backed-up officeis broken in the mutual backupdual-homing networking. Thisparameter must be defined bycommand ADD DAS at first. Thenit can be indexed here

A6

Sending A6signal afterreceivinghow manydigits duringincoming calls

It is used to specify the numberof digits that the system receivesenough to send A6 signal to thefront office. This parameter onlytakes effect during incomingcalls using Channel AssociatedSignaling (CAS)

PFXLENToll prefix +Area codelength

It is an optional parameter, whichis an integer, ranging from 0to 15. When the call servicetype is national/international tollservice, this parameter needs tobe configured

ENOPT

Enabledoptions Referto Table 112 fordetails

It is an optional parameter.In general, select CCS7(Automatically sending thecalling number when using CCS7for outgoing services) and (No callwhen the called number exceedsthe maximum digit length)

FAXIDX Fax analysisresutl index

It is used to specify the beareranalysis result index number ofthe called number associated withthe fax service. This parametermust be defined by command ADDBEARRST at first. Then it can beindexed here. This parameteris configured to implement therouting service based on the bearercapability. For the fax service,if the associated bearer analysisresult index of the called numberis configured, the call adopts theassociated bearer analysis resultof the called number, thus flexiblerouting is implemented



ParameterName


AVIDXAnalog videoanalysis resultindex

It is used to specify the beareranalysis result index number ofthe called number associatedwith the analog video service.This parameter must be definedby command ADD BEARRST atfirst. Then it can be indexed here.This parameter is configured toimplement the routing servicebased on the bearer capability.For the analog video service, ifthe associated bearer analysisresult index of the called numberis configured, the call adopts theassociated bearer analysis resultof the called number, thus flexiblerouting is implemented

DVIDXDigital videoanalysis resultindex

It is used to specify the beareranalysis result index number ofthe called number associatedwith the digital video service.This parameter must be definedby command ADD BEARRST atfirst. Then it can be indexed here.This parameter is configured toimplement the routing servicebased on the bearer capability.For the digital video service, ifthe associated bearer analysisresult index of the called numberis configured, the call adopts theassociated bearer analysis resultof the called number, thus flexiblerouting is implemented

ADATAIDXAnalog dataanalysis resultindex

It is used to specify the beareranalysis result index number ofthe called number associated withthe analog data service. Thisparameter must be defined bycommand ADD BEARRST at first.Then it can be indexed here.This parameter is configured toimplement the routing servicebased on the bearer capability.For the analog data service, ifthe associated bearer analysisresult index of the called numberis configured, the call adopts theassociated bearer analysis resultof the called number, thus flexiblerouting is implemented



ParameterName


DDATAIDXDigital dataanalysis resultindex

It is used to specify the beareranalysis result index number ofthe called number associatedwith the digital data service. Thisparameter must be defined bycommand ADD BEARRST at first.Then it can be indexed here.This parameter is configured toimplement the routing servicebased on the bearer capability.For the digital data service, if theassociated bearer analysis resultindex of the called number isconfigured, the call adopts theassociated bearer analysis resultof the called number, thus flexiblerouting is implemented

DDCPLAY

Whether to playthe DDC tone,including:

NONE (Notplaying theDDC tone): Itis not requiredto play the DDCtone in the localoffice.

PLAY (Playingthe DDC tone):It is requiredto play the DDCtone in the localoffice.

It is used to specify whetherto play the DDC tone in thelocal office. The system adoptsNONE by default. The purposeof configuring whether to playthe DDC tone in the numberanalysis configuration is to avoidno tone play or repeated tone playcaused by inconsistent tone playconfiguration during inter-officeDDC calls

VAD

Voice ActivityDetection(VAD) flag,including:

CLOSE: Notstarting theVAD function.OPEN: Startingthe VADfunction.INVALID: TheVAD function isinvalid

It is used to specify whether tostart the VAD function. The systemadopts INVALID by default

OPPMGWID Opposite-endMGW ID

It is used to specify between whichopposite-end MGW and the localMGW the TDM backup route isadopted. The QOSs between thelocal MGW and all opposite-endMGWs can be found throughautomatic test calls. When theQOS difference between theopposite-end MGW and the localMGW is specified, the call adoptsthe TDM backup route



ParameterName


CALLSERV-PRILVL

Call typepriority,including:

INVALID: Thecall priority isinvalid.

HIGHEST: Thecall has thehighest priority.

HIGHER: Thecall has apriority onelevel lower thanthe highestpriority.

NORMAL:The call hasa priority onelevel lowerthan the higherpriority.

LOW: The callhas the lowestpriority

It is used to specify the callpriority. The system adoptsINVALID by default. The callpriority has two functions. Inone case, in the softswitch officein the toll softswitch network,the voice coding format can bedynamically selected according tothe call priority and the load onthe IP bearer network. In anothercase, based on the combinedinformation of office ID andpriority configured in the numberanalysis configuration, the finalpriority of a call is got to performload control

RERTS Re-routingroute chain

It is used to specify the re-routingroute chain ID. This parametermust be defined by commandADD RERTS at first. Then itcan be indexed here. When flagRRTO in enabled options takeseffect, the re-routing route chaintakes effect too. For an outgoingcall procedure, if the call fails,and the corresponding failurecause is configured with “Enablingrerouting for failure” in the R_ICPconfiguration, re-select the routefrom this route chain accordingto the re-routing route chain.For an incoming call using ISUP,TUP, or BICC signaling, whenthe call procedure is an outgoingprocedure, and the call fails beforethe IAM message is sent, there-routing route chain serves asthe standby route, and is notcontrolled by RRTO.

If route chain analysis isconfigured, the re-routingroute chain here is invalid. In thiscase, use the re-routing routechain configured in the route chainanalysis



ParameterName


INCHAIN

Inter-MGWroute chain ornot, including:

NO: Theoutgoing routechain gotfrom numberanalysis is notan inter-MGWroute chain.

YES: Theoutgoing routechain gotfrom numberanalysis isan inter-MGWroute chain

It is used to specify whether theoutgoing route chain got fromnumber analysis is an inter-MGWroute chain. The system selectNO by default. If YES is selected,the routes in the outgoing routechains will not be selected forthe outgoing route. The outgoingroute will be got after performnumber analysis again accordingto the associated called numberDAS configured in the outgoingroute chain.

This parameter is used in thefollowing cases:

One virtual outgoing route chainis got based on number analysisat first, and then the real outgoingroute is got based on the callednumber DAS associated with thevirtual outgoing route chain.

When one MSCS controls multipleareas, the outgoing route chainfacilitates subscriber management

RECMDMG-WNODEID

RecommendedMGW nodes

It is used to specify the set ofrecommended MGWs for outgoingservice. In the case of multiple IPdomains, if one MSCS managesmultiple MGWs, and these MGWsbelong to different IP domains,the set of recommended MGWsfor outgoing service needs to beconfigured. The MGW set hereshould be a sub-set of the MGWset supported by outgoing service.This parameter must be definedby command ADD TOPO at first.Then it can be indexed here

TABLE 111 CALL SERVICE TYPES

CallServiceTypes

Meanings Description

NONE Vacant number

Indicates that the subsequent callprocedures are processed basedon the procedure of processingvacant numbers

LLC

Local-network local-office/commonservice

Indicates that the subsequent callprocedures are processed basedon the local service procedure



CallServiceTypes


LOLLocal-networkoutgoing/local-call service

Indicates that the subsequentcall procedures are processedbased on the local-call serviceprocedure. The mobile-to-fixedlocal outgoing call service isusually analyzed to this type

LORU

Local-networkoutgoing/rural(network) callservice

Indicates that the subsequentcall procedures are processedbased on the local rural (network)outgoing call service procedure.The mobile-to-fixed rural outgoingcall service is usually analyzed tothis type

DWTMDomestic toll(intra-region)manual service

Indicates that the subsequent callprocedures are processed basedon the domestic toll (intra-region)manual service procedure. Ingeneral, it is not recommended toconfigure this service type

DWTA

Domestic toll(intra-region)automaticservice

Indicates that the subsequent callprocedures are processed basedon the domestic toll (intra-region)automatic service procedure. Ingeneral, it is not recommended toconfigure this service type

DBTMDomestic toll(inter-region)manual service

Indicates that the subsequent callprocedures are processed basedon the domestic toll (inter-region)manual service procedure. Ingeneral, it is not recommended toconfigure this service type

DBTA

Domestic toll(inter-region)automaticservice

Indicates that the subsequent callprocedures are processed basedon the domestic toll (inter-region)automatic service procedure. Thedomestic toll call service is usuallyanalyzed to this type

INTMInternationaltoll manualservice

Indicates that the subsequent callprocedures are processed basedon the international toll manualservice procedure. In general, itis not recommended to configurethis service type

INTAInternationaltoll automaticservice

Indicates that the subsequentcall procedures are processedbased on the international tollautomatic service procedure. Theinternational toll call service isusually analyzed to this type



CallServiceTypes


LSPA Local-office paidspecial service

Indicates that the subsequentcall procedures are processedbased on the local-office paidspecial service procedure. Thelocal-office paid special service isusually analyzed to this type

LSFR Local-office freespecial service

Indicates that the subsequentcall procedures are processedbased on the local-office freespecial service procedure. Thelocal-office free special service isusually analyzed to this type

OUPA Outgoing paidspecial service

Indicates that the subsequent callprocedures are processed basedon the outgoing paid specialservice procedure. The outgoingpaid special service is usuallyanalyzed to this type

OUFR Outgoing freespecial service

Indicates that the subsequentcall procedures are processedbased on the outgoing free specialservice procedure. The outgoingfree special service is usuallyanalyzed to this type

DEPS Additionalservice

Indicates that the subsequentcall procedures are processedbased on the additional serviceprocedure. In general, it is notrecommended to configure thisservice type

CENTL

Intra-officecall withinthe CENTREXbusiness group

Indicates that the subsequent callprocedures are processed basedon the intra-office call procedurewithin the CENTREX businessgroup.

CENTO

Outgoing callwithin theCENTREXbusiness group

Indicates that the subsequent callprocedures are processed basedon the outgoing call procedurewithin the CENTREX businessgroup

TELCAIntelligentNtwork servicecall

Indicates that the subsequent callprocedures are processed basedon the intelligent network servicecall procedure

EQACL

Equal access:CIC of theoperator wherethe subscriber islocated

Indicates that the subsequentcall procedures are processedbased on the procedure of “Equalaccess: CIC of the operator wherethe subscriber is located”



CallServiceTypes


EQACOEqual access:non-local-network CIC

Indicates that the subsequentcall procedures are processedbased on the procedure of “Equalaccess: non-local-network CIC”

STONETone play serv-ice, CAT_SEND-_TONE

Indicates that the subsequentcall procedures are processedbased on the tone play serviceprocedure. After calling thenumber that is analyzed to thistype, the system will directly playthe tone according to the toneID configured in number analysisresult 1

DDCI Toll DDCincoming call

Indicates that the subsequentcall procedures are processedbased on the toll DDC incomingcall service procedure. The tollincoming DDC call that needs tobe routed in the local office isanalyzed to this type

DDCC Local DDC call

Indicates that the subsequent callprocedures are processed basedon the local DDC call serviceprocedure. The local DDC call(dialing the MSISDN number) thatneeds to be routed in the localoffice is analyzed to this type

DDCO Toll DDCoutgoing call

Indicates that the subsequentcall procedures are processedbased on the toll DDC outgoingcall service procedure. The tolloutgoing DDC call is analyzed tothis type

DDCCO Local DDCoutgoing call

Indicates that the subsequentcall procedures are processedbased on the local DDC outgoingcall service procedure. The localoutgoing DDC call is analyzed tothis type

MSCO MSC commonservice

Indicates that the subsequent callprocedures are processed basedon the MSC common serviceprocedure. The call (dialing theMSISDN number) that needs tobe routed in the local office isanalyzed to this type

MSLL

MSC local-networklocal-officeservice (onlyfor roamingnumbers)

Indicates that the subsequentcall procedures are processedbased on the MSC local-networklocal-office service procedure. Itis used to analyze the roamingnumbers and handover numbersof the local office



CallServiceTypes


MSLO

MSC localoutgoingservice (onlyfor roamingnumbers)

Indicates that the subsequent callprocedures are processed basedon the local outgoing serviceprocedure. The local outgoing callof roaming numbers is analyzedto this type

CINRECalling-numberincoming callrestriction

Indicates that the subsequent callprocedures are processed basedon the calling-number incomingcall restriction procedure

MSLTE

MSC nationaltoll call (onlyfor roamingnumbers)

Indicates that the subsequentcall procedures are processedbased on the MSC national tollcall service procedure. The tolloutgoing call of roaming numbersis analyzed to this type

AACAutomaticresponsenumber

Indicates that the subsequentcall procedures are processedbased on the automatic responsenumber service procedure

OVPREOVERLAYprefix incomingservice

Indicates that the subsequent callprocedures are processed basedon the OVERLAY prefix incomingservice procedure. The OVERLAYprefix incoming call is analyzed tothis type

OVCS OVERLAY callservice

Indicates that the subsequent callprocedures are processed basedon the OVERLAY call serviceprocedure. It is used for the IGWsystem

MSITE

MSCinternationaltoll call (onlyfor roamingnumbers)

Indicates that the subsequentcall procedures are processedbased on the MSC internationaltoll call service procedure. Theinternational toll outgoing call isanalyzed to this type

IP IP fixed service

Indicates that the subsequent callprocedures are processed basedon the IP fixed service procedure.It is used for the IGW system

SSPSSP chargingand queryingservice

Indicates that the subsequent callprocedures are processed basedon the SSP charging and queryingservice procedure.

NSSPNon-SSPcharging andquerying service

Reserved



CallServiceTypes


IPMO IP mobileservice

Indicates that the subsequentcall procedures are processedbased on the IP mobile serviceprocedure. The IP service in themobile system is analyzed to thistype

INSIP

IP service dialedby intelligent-networksubscribers

Reserved

ALIP Independent IPservice

Indicates that the subsequent callprocedures are processed basedon the independent IP serviceprocedure. The independent IPincoming call is analyzed to thistype

OVMOOVERLAY:MO-triggeredCAMEL service

Indicates that the subsequent callprocedures are processed basedon the “OVERLAY: MO-triggeredCAMEL service” procedure

OVMTOVERLAY:MT-triggeredCAMEL service

Indicates that the subsequent callprocedures are processed basedon the “OVERLAY: MT-triggeredCAMEL service” procedure

MNP Mobile numberportability

Indicates that the subsequent callprocedures are processed basedon the MNP service procedure

MNPR MNP MNPoutgoing routing

Indicates that the subsequent callprocedures are processed basedon the MNP outgoing routingservice procedure

SIPO SIP outgoingcall

Indicates that the subsequent callprocedures are processed basedon the SIP outgoing call serviceprocedure

H323 H323 call

Indicates that the subsequentcall procedures are processedbased on the H323 call serviceprocedure.

MOIMCMobileemergencyspecial service

Indicates that the subsequent callprocedures are processed basedon the mobile emergency specialservice procedure



CallServiceTypes


SSSPIndependentSSP outgoingservice

Indicates that the subsequentcall procedures are processedbased on the independent SSPoutgoing service procedure. TheSSSP (Independent SSP outgoingservice) in the analysis result ofthe called number is used for theIGW system

IGWA

IGWsupplementaryservice (only forIGW)

Indicates that the subsequentcall procedures are processedbased on the IGW supplementaryservice procedure

DASADAS service(virtual IGW)(only for IGW)

A new DAS is got through numberanalysis, which is used for thesubsequent analysis of the callednumber

OCIC Local valid CICservice

Indicates that the subsequent callprocedures are processed basedon the local valid CIC serviceprocedure. This parameter isreserved

OUPAOD

Outgoingpaid specialservice (canbe dialed bythe defaultingsubscribers)

Indicates that the subsequent callprocedures are processed basedon the outgoing paid specialservice (can be dialed by thedefaulting subscribers) procedure

LINTSLocal-officeintelligentservice

Indicates that the subsequent callprocedures are processed basedon the local-office intelligentservice procedure. It is used forthe IGW system

SHLRQSHLR queryingservice (only forIGW)

Indicates that the subsequent callprocedures are processed basedon the SHLR querying serviceprocedure

IGWCIGW commonservice (only forIGW)

Indicates that the subsequentcall procedures are processedbased on the IGW commonservice procedure. The call toPHS subscribers, which needs tobe routed in the local office, isanalyzed to this type

ISSPQ

IGWSSPcharging andquerying service(only for IGW)

Indicates that the subsequent callprocedures are processed basedon the IGW SSP charging andquerying service procedure

IGWLFIGW local-officefree specialservice

Indicates that the subsequentcall procedures are processedbased on the IGW local-office freespecial service procedure



CallServiceTypes


IGWLPIGW local-officepaid specialservice

Indicates that the subsequentcall procedures are processedbased on the IGW local-office paidspecial service procedure

IGWOVIGWOVERLAYprefix incomingservice

Indicates that the subsequentcall procedures are processedbased on the IGWOVERLAY prefixincoming service procedure

IGWDDCIN IGW toll DDCincoming call

Indicates that the subsequent callprocedures are processed basedon the IGW toll DDC incoming callservice procedure

IGWDDCL-OCAL

IGW local DDCcall

Indicates that the subsequent callprocedures are processed basedon the IGW local DDC call serviceprocedure

TEST Test call

Indicates that the subsequent callprocedures are processed basedon the test call service procedure.It is used to analyze test calls

TABLE 112 ENABLED OPTIONS

EnabledOptions Meanings Description

CCS7

Automatically sendingthe calling number whenusing CCS7 for outgoingservices

It indicates whether theoutgoing TUP signalingcarries the callingnumber. When the localoffice actively sends thecalling number, it sendsan IAI message of TUPsignaling to the peer-endoffice, carrying the callingnumber. Otherwise, thelocal office sends anIAM message of TUPsignaling to the peer-endoffice, not carryingthe calling number.For ISUP signaling, itindicates whether thelocal MSC number is filledin the location numberinformation

CHGK Changing the type ofcalling subscribers

Indicates whether toset the type of thecalling subscriber in theoutgoing IAM message ofISUP or BICC signalingto the calling subscribertypes flexibly configuredin security variables




CHGN Changing the number

Indicates that theanalyzed number ischanged, and the systemnotifies the callingsubscriber by playingthe tone

DELA Delayed dialing of thespecial service Reserved

MAIL 166-voice-mailboxservice

Indicates that the callis a 166-voice-mailboxservice

NSCP Not waiting for SCPresponses Reserved

RRTO Rerouting after outgoingfailure

For incoming callsusing ISUP, TUP, orBICC signaling, thecall procedure is anoutgoing call procedure.When the local officedoes not receives a RELmessage after sending anoutgoing IAM message tothe peer-end office, thisoption control whetherrerouting 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 emergencycall

Charge as emergencycall

NOLMTLEN No Limited Time LengthFor Tone

No Limited Time LengthFor Tone

IGFWD Ignore Redirection InfoIn Outgoing Call

Ignore Redirection InfoIn Outgoing Call

ECL Use Emergency Call Level Use Emergency Call Level

NTC Not triggering IN serviceof the calling number

Indicates whether thecall triggers the INservice of the callingnumber. This option isused for the case wherethe IN service of thecalling number cannotbe triggered when thecall to the IN subscriberis forwarded or whensome special numbersare dialed




NCELNo call when the callednumber exceeds thelength

Indicates whether thesystem releases the callif the analyzed numberexceeds the configuredmaximum digit length

LSIN Interception numberincoming

Indicates whether thecall is an incomingcall returned from theinterception center. Thisoption is only used in theIGW system

CONSending the “connect”message in advance(only for IGW)

Indicates whether thelocal office sends aringing message of thecalled subscriber and a“connect” message tothe calling subscriberat the same time (thatis, sends a “connect”message to the callingsubscriber before thecalled subscriber answersthe call). This option isonly used in the IGWsystem

SHLRF Not triggering SHLRquery

Indicates whether thenumber section needsto be transformed inthe SHLR during callorigination. In theSHLR mixed networking,common call originationprocedures need tointeract with the SHLRto get the callinglogic number, and thecalled physical number.However, in the specificcalls, the called numberneeds no transform. Inthis case, select thisoption in the numberanalysis result. Thisoption is only used in theIGW system

SHLRG Over net number in SHLR

Indicates whether theincoming call restrainthe SHLR from returningthe IN access code. Thisoption is used to preventrepeatedly triggering INservices. This option isonly used in the IGWsystem




JUDG Needing to judge the IPresource

Indicates whether therouting query in the SHLRis forcibly performedduring IP calls. Thisoption is only used in theIGW system

REBO Restraining HOMEBOXservice

Indicates whetherincoming calls triggerthe HOMEBOX servicein the local office. Thisoption is only used in theIGW system

Example: Configure the called number analysis with the fol-lowing requirements.

� Analyzer entry: 1

� User alias: TPDNAL1


� Call service type: MSC common service


The command is:

ADD TPDNAL:ENTR=1,DIGIT="13902099",NAME="TPDNAL1",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,OPDDICONT=NO,TPDDICONT=NO,OPDDI=0,TPDDI=0,OPDLYDDI=0,TPDLYDDI=0,DDIOVERB=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=INVALID,CALLSERVPRILVL=INVALID,RERTS=0,INCHAIN=NO,BICT=NO,ICT=0,ICTT=10,GNM=NORMAL,STBILL=INVALID,HOPDAS=0,MCA=NO,IVVR=NO,WANTL=0,IMSCENTR=NO;

Example: Configure the roaming number analysis of the localoffice with the following requirements.

� Analyzer entry: 1

� User alias: TPDNAL1


� Call service type: MSC local service


The command is:

ADD TPDNAL:ENTR=1,DIGIT="15902099",NAME="TPDNAL2",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,OPDDICONT=NO,TPDDICONT=NO,OPDDI=0,TPDDI=0,OPDLYDDI=0,TPDLYDDI=0,DDIOVERB=0,IWVIDEO=LSUP,TIMELMT=0,AUXDAS=0,A6=0,PFXLEN=0,INSRV=INM,FAXID



X=0,AVIDX=0,DVIDX=0,ADATAIDX=0,DDATAIDX=0,DDCPLAY=NONE,VAD=INVALID,CALLSERVPRILVL=INVALID,RERTS=0,INCHAIN=NO,BICT=NO,ICT=0,ICTT=10,GNM=NORMAL,STBILL=INVALID,HOPDAS=0,MCA=NO,IVVR=NO,WANTL=0,IMSCENTR=NO;

END OF STEPS


C h a p t e r 4

Tone Configuration

Table of ContentsCreating MSCS Tones in Batches........................................ 257Creating the Fixed Tone Play Data...................................... 258Creating the Basic Service Tone Play Data........................... 265Creating the Intelligent Service Tone Play Data.................... 274

Creating MSCS Tones inBatches


The MML Terminal window is opened.

Context The NetNumen M30 network management system provides thefunction of quickly creating tone play data in batches, avoidinglow efficiency, and the error-prone problem of the manual setting.Since most of the tones in the system have been clearly defined inthe related protocols and national standard, it is suggested to con-figure tone play data through this function in practical use. In caseof special requirements, adjust different system tones accordingto different services.

Note:

During batch deletion, delete the MGW static data first; otherwise,the system will prompt that “The tone play template No. is beingused by the MGW static data, so it cannot be deleted”.



SET:NEID=11;

2. Create MSCS tones in batches. The command is BADDSTONE.

Table 113 describes the main parameters in the BADD STONEcommand.



TABLE 113 PARAMETERS IN THE BADD STONE COMMAND


TYPE

Voice type, includes

� ALL: all configuration oftone

� ICP: tone service

� KD: the relationshipbetween the call typeand the KD

� LANGDES: languagedescription string

� MSGID: external MSGID,relation to inter servicekey

� TONEID: the servicetone ID to the protocolpackage

� TONEIN: service key andits relation to tone ID

� TONEPLAYMT: themethod of playing tones

Select itaccording to theactual condition.

Example: Create the batch processing of all the MSCS tones.The specific command is as follows.

BADD STONE:TYPE=ALL;

3. After completing the tone play data configuration on both theMSCS and the MGW, perform the dial test to check whether thesystem can correctly play tones.

END OF STEPS

Creating the Fixed TonePlay Data

Prerequisites � The NMS system works properly, and the client logs in to theserver.

� The physical data configuration is complete, and the TONE-typeMRB board is created on the MGW.

Context 1. Description of the tone play data of fixed tones on the MSCS

� ToneID: ID of a service tone in the MSCS system. TheToneID of fixed tones ranges from 1 to 99.

� Tone package type (TonePro): a parameter defined in theH.248 protocol. It is specified in the Q.1950 protocol thatthe tone packages of fixed tones are divided into two types,


Chapter 4 Tone Configuration

BCG (Basic Call Progress Tones Generator with Direction-ality) and XCG (Expanded Call Progress tones GeneratorPackage). Each fixed tone must belong to one of them.

� Service tone No. in the tone package (PKGID): a parameterdefined in the H.248 protocol, used to distinguish differentservice tones in the same type of tone packages.

� In the actual configuration, perform the configuration ac-cording to the tones supported by the system.

2. Description of the tone play data of fixed tones on the MGW

� ToneID: same with that of the MSCS.

� Tone package type (TonePro): same with that of the MSCS.

� Service tone No. in the tone package (PKGID): same withthat of the MSCS.

� Frequency point: an internal ID in the MGW, associatedwith the frequency point No. in the code dot informationconfiguration. Through it, the play frequency, volume, andthe circuit type of the fixed tone can be indexed.

� Play duration: the duration of playing a part of tone at afrequency of a fixed tone. A fixed tone is played in seriesbased on the duration of each frequency. The play periodof a fixed tone equals to the sum of durations of all fre-quencies.

� Frequency: tone frequency of a fixed tone.

� Volume: volume

� Circuit type: PCM compression mode of a fixed tone, in-cluding A law and u law

� The MRB board circularly plays tones according to the con-figured duty ratio. If there is phase and amplitude saltusbetween the first dot and the last one of the code dots of thetone generated according to a special frequency f, noise willoccur when the MRB board circularly plays the tone. Thebackground generates single-frequency tones according toCOS (π×f×L)/4000, where π is the constant of circumfer-ence ratio, f is the frequency for generating fixed tones,and L is the code dot length. f×L/4000 must be an integer,so that the generated fixed tone can be circularly playedwithout interruption. Therefore, during the configuration,it is required to confirm whether to select 640 bytes or 800bytes for the fixed code dot length according to the fre-quency.

3. Brief introduction to data association

The MSCS translates the ToneID generated by the service intothe exclusive combination of TonPro and PKGID, and transfersit the MGW.

The MGW translates the exclusive combination of TonePro andPKGID into the ToneID. It gets the frequency point and playduration according to the ToneID, and then gets the actual fre-quency, volume, circuit type of the tone play according to thefrequency point.

This topic introduces how to create tone play data for a fixed tone,taking the ring back tone as an example. The fixed tone play data



configuration is used to implement the function of playing fixedtones.In normal cases, the fixed tone configuration data can becreated in batches. In case of special requirements, it is requiredto separately configure the fixed tone play data.



SET:NEID=11;

2. Create a tone ID. The command is ADD TONEID.

Table 114 describes the main parameters in the ADD TONEIDcommand.

TABLE 114 PARAMETERS IN THE ADD TONEID COMMAND FORFIXED TONES

ParameterName

ParameterDescriptions Instruction

TPLID Playback templateindex number

Numbered from 1,used in “MGW staticdata configuration(ADD MGSCFG), anddetermining the playedtones supported by theMGW

TONE Tone ID

Tone ID self-defined inZXWN, for internal use.It is usually consistentwith the internal Tone IDof the MGW. Refer to thecorresponding tone list ofthe Tone ID to configureit. The TONEID of the ringback tone is 2.

PKG

Tone package type,including:

� CG (CG package)

� CT (CT package)

� AU (AU package)

� AN (AN package)

� BCG (BCGpackage)

� XCG (XCGpackage)

� THREEGXCG(THREEGXCGpackage)

� AASB (AASBpackage)

� AASDC (AASDCpackage)

A parameter definedin the H.248 protocol,for classifying tones inthe H.248 protocol. Fordetails, see the contentsin the H.248 protocol.The tone package typeof the ring back tone isBCG (Basic Call ProgressTones Generator withDirectionality)



ParameterName

ParameterDescriptions Instruction

� 132 (132 package)

INPKGID Tone ID in the tonepackage

A parameter defined in theH.248 protocol, specifyingthe number of a tone inthe specific type of tonepackage. For details, seethe contents in the H.248protocol. The number ofthe ring back tone in theBCG package is 65.

ID ID Used to specify the ID ofthis service tone

URL

URL address/characterstring codecorresponded by theservice tone

Used to specify thecorresponding URLaddress of this servicetone. In general, only ANand AASB packages needto be configured.

For example, create a service tone ID with the following re-quirements.

� Tone play template index: 1

� Service tone ID: 2

� Tone package type: BCG

� Service tone No. in this tone package: 65

� ID: 2


ADD TONEID:TPLID=1,TONE=2,ANARSLT=EOTA,PKG=BCG,INPKGID=65,ID=2;

3. If no exchange is specified, execute command SET on theMMLTerminal window or select a NE from the system tree to spec-ify the exchange to be configured.

Example: Select the MGW exchange with ID as 31 from thesystem tree.

SET:NEID=31;

4. Create a service-tone-to-protocol-tone-package configuration.The command is ADD TONEPRO.

Table 115 describes the parameters in the ADD TONEPROcommand.



TABLE 115 PARAMETERS IN THE ADD TONEPRO COMMAND

ParameterName


TPROID SN

Used to define a service-tone-ID-to-protocol-tone-packageconfiguration in the system. Itis of a unified number globally,ranging from 1 to 10000.

PKGTP Package type

A parameter defined in the H.248protocol, for classifying tones inthe H.248 protocol. For details,see the contents in the H.248protocol. The tone packagetype of the ring back tone isBCG (Basic Call Progress TonesGenerator with Directionality)

TPRO

Servicetone type,correspondingto the INPKGIDparameterin the ADDTONEIDcommand onthe MSCS

A parameter defined in the H.248protocol, specifying the numberof a tone in the specific type oftone package. For details, see thecontents in the H.248 protocol.The number of the ring back tonein the BCG package is 65.

TONE Tone ID

Tone ID self-defined in ZXWN,for internal use. It is usuallyconsistent with the internal ToneID of the MSCS. Refer to thecorresponding tone list of theTone ID to configure it. TheTONEID of the ring back tone is 2.

ANSPEC Service keycode

A parameter defined in theH.248 protocol, corresponding tothe URL parameter in the ADDTONEID command on the MSCS,which does not take effect duringconfiguring fixed tones. Configureit to 1.

SKEY Service key

The internal service key in ZXWN.The fixed tones belong to basicservice tones, and the service keyis 1.

NAME AliasUsed to specifically describe theconfiguration of a service tone IDto make it easily recognized.

For example, create ring-back-tone-to-protocol-tone-packageconfiguration with the following requirements.

� ID: 1

� Package type: BCG


� Service key: 1



� Alias: RingbackTone


ADD TONEPRO:TPROID=1,PKGTP=BCG,TPRO=65,TONE=2,ANSPEC="1",SKEY=1,NAME="RingbackTone";

5. Create a tone frequency. The command is ADD CODEDOTS.

Table 116 describes the parameters in the ADD CODEDOTScommand. The ring back tone includes mute and 450 Hz tone.First set the frequency and volume for the mute, and then setthe frequency point information for the 450 Hz tone.

TABLE 116 PARAMETERS IN THE ADD CODEDOTS COMMAND

ParameterName


FREQ

Frequency point No..Specify the frequencyof tone play andnumber it globally

Set it according to theplan.

CDFREQ Code point frequency(Hz)

Select it according to theactual conditions.

DECIBEL Code point volume(Db)


CTYPE Circuit type, includingA law and u law

The circuit type ofall records must beconfigured to be thesame, being A law or ulaw instead of both

CDLEN

Code point bytestream length, whichcan be 640 bytes or800 bytes

When no code pointbyte stream length isentered, the systemwill set a default valueaccording to the circuittype, 640 for A law, and800 for u law. A/u lawand code point lengthcan be specified at thesame time.

NAME Alias

Specifically describesthe language descriptionstring to make it easilyrecognized

Note:

The MRB board circularly plays tones according to the config-ured duty ratio. If there is phase and amplitude saltus betweenthe first dot and the last one of the code dots of the tone gen-erated according to a special frequency f, noise will occur whenthe MRB board circularly plays the tone.

The background generates single-frequency tones according toCOS (π×f×L)/4000, where π is the constant of circumferenceratio, f is the frequency for generating fixed tones, and L is the



code dot length. f×L/4000 must be an integer, so that the gen-erated fixed tone can be circularly played without interruption.

For double-frequency or multiple-frequency tones,they are generated according to COS(π×f1×L)/4000+COS(π×f2×L)/4000+…+ COS(π×fn×L)/4000. In this case, allf×L/4000s must be integers.

For example, create a frequency for the ring back tone withthe following requirements.

� Frequency No.: 9

� Code point frequency: 440 Hz and 480 Hz

� Code point volume: –16Db

� Circuit type: A law

� Code point byte stream length: 800 bytes

� Alias: RingbackTone


ADD CODEDOTS:FREQ=9,CDFREQ="440"&"480",DECIBEL=-16,CTYPE=A,CDLEN=800,NAME="RingbackTone";

6. Create a fixed tone. The command is ADD FIXTONE.

The ADD FIXTONE command is used to set the frequencypoint information included by the fixed tone, and the play du-ration of each frequency point. The explanation of the mainparameters is described in Table 117.

TABLE 117 PARAMETERS IN THE ADD FIXTONE COMMAND

ParameterName


TONE Service Tone ID

Used to define a servicetone ID configurationin the system. Thisparameter ranges from 1to 50. and is of a unifiednumber in the entireoffice.

FRDU Frequency point andduration (in 10 ms)

Frequency point usesthe frequency point No.defined in the ADDCODEDOTS command.Configure the durationaccording to the actualconditions.

NAME Alias

Specifically describesthe language descriptionstring to make it easilyrecognized

For example, create a ring back tone with the following re-quirements.




� Frequency point: 9-40

� Duration: 0-20

� Alias: RingbackTone.


ADD FIXTONE:TONE=2,FRDU="9"-"40"&"0"-"20",NAME="RingbackTone";

7. Transfer data to the foregrounds of the MSCS and the MGW.Dial a local mobile phone to test whether the ring back tone isproperly played.

END OF STEPS

Creating the Basic ServiceTone Play Data



� Each kind of tone play requirement and the corresponding re-lationship between basic tones in the version are planned wellin the local office.

Context 1. Description of the tone-play data of basic service tones on theMSCS

� ErrCode: When a service fails, the system will exclusivelyidentify the service failure according to the ErrCode, whichis the initial condition of the basic service tone play. TheMSCS confirm the ToneID based on the above information.

� ToneID: ID of a service tone in the MSCS system. TheToneID of fixed tones ranges from 100 to 200.

� Tone package type (TonePro): a parameter defined in theH.248 protocol. It is specified in the H.248.7 protocol thatthe tone package type of basic service is “an”.

� Service tone No. in the tone package (PKGID): a parameterdefined in the H.248 protocol, used to distinguish differentservice tones in the same type of tone packages. For theallocation of PKGID, refer to the H.248 protocol.

� Language type: language type of service tones, such asEnglish, Chinese, first Chinese and then English.

� Play duration: tone play period.

� Play times: times of playing tones.

� Play interval: interval between two times of playing tones.

� Notify that the tone play is complete: Whether to notify theMSCS after tone play.



2. Description of the tone-play data of basic service tones on theMGW

� ToneID: ID of a service tone in the MGW system. TheToneID of fixed tones ranges from 100 to 200.

� Tone package type (TonePro): same with that of the MSCS.

� Service tone No. in the tone package (PKGID): same withthat of the MSCS.

� Language type: same with that of the MSCS.

� Play duration: same with that of the MSCS.

� Play times: same with that of the MSCS.

� Play interval: same with that of the MSCS.

� Notify that the play is complete: same with that of theMSCS.

� Service key: The ZXWN system defines an ID for each ser-vice. The tone play types for different services are differ-ent. The service key of the basic services is fixed as 1. Theservice key of each tone subunit is configured in the net-work management system, determining the service tonetype of the tone subunit.

� Fixed tone elements and variable tone elements: In thesame service, tone elements are used to distinguish differ-ent tones. After finding the subunit of the tone resource,the system can play the tone on the subunit according tofixed tone elements and variable tone elements.

� Unit No.: associated with the unit No. of the MRB board inthe physical configuration in the ZXWN network manage-ment system, and used to address the MRB board playingthe tone during the tone play.

� Subunit No.: associated with the subunit No. of the MRBboard in the physical configuration in the ZXWN networkmanagement system. The subunits of the MRB board canbe configured to TONE, DTMF, and MFC. Only the subunitof TONE type can be used to play tones. The service keyof each subunit of TONE type should be configured on thenetwork management system.


The MSCS translates the ErrCode generated by the service pro-cessing module into the ToneID. Then it translates the ToneIDinto the exclusive combination of TonePro and URL, and trans-lates the language type, play method, and other parametersof the basic services at the same time. It transfers TonePro,URL, language type, and the play method to the MGW.

The MGW translates the exclusive combination of TonePro andURL into the ToneID and the service key, translates the lan-guage type to that on the MGW, and saves the play method.It gets the tone element component (fixed tone elements andvariable tone elements) according to the ToneID and the lan-guage type, and gets the tone unit No. and the subunit No.according to service key 1 of the basic services.

The basic service tone play data configuration is used to implementthe function that the system automatically plays the related tone



when a basic call service fails. For example, the system plays theinvalid number tone when a subscriber dials an incorrect number,and ringing-time-out tone when the called subscriber makes noreply for a long time. In normal cases, the basic service toneplay data can be created in batches. This topic introduces how toconfigure the tone play data for a basic tone, taking the vacantnumber tone as an example.



SET:NEID=11;

2. Create a voice service. The command is ADD TONESRV.

Table 118 describes the parameters in the ADD TONESRVcommand.

TABLE 118 PARAMETERS IN THE ADD TONESRV COMMAND

ParameterName


FAILCODE Tone play cause

Enter it according to theerror code returned bythe service processingmodule.

ANARSLT

Analysis result,including:

� EOTA: Endanalysis

� CONT: Numberanalyzedsubsequently


TONE Tone ID

Tone ID self-defined inZXWN, for internal use.It is usually consistentwith the internal Tone IDof the MGW.

SRVTAG

Service tag providedin the call failurecode, including:

� TONESIG(Sending tonesignal betweenoffices): Sendingtone signal to thecalling side.

� ACKSIG(Sending thecalled-party-answering signalto the callingside): Sendingfalse answering

It is an optionalparameter, which is ofenumeration type, with adefault of TONESIG.



ParameterName


signal to thecalling side.

� PLAYFLG:Meaning whetherto set the toneplay duration andtimes accordingto the servicetones.

NAME AliasSpecifically describes thevoice service to make iteasily recognized

ITERR Iteration times

It is used to specify thetimes of this failure toneto be played repeatedly,with a default of 0. It isinvalid to the fixed failuretone.

DURATION Playback duration (s)

It is used to specifythe play duration ofthis failure tone, with adefault of 0.

For example, create a vacant-number-tone service with thefollowing requirements.

� Call failure code: 4005

� Analysis result: end of tone analysis


� Service tag provided to subscribers in the call failure code:TONESIG

� Alias: "Invalid Number Tone"

� Play times of failure tones: 5

� Play duration of failure tones: 10 seconds


ADD TONESRV:FAILCODE=4005,ANARSLT=EOTA,TONE=101,SRVTAG="TONESIG",ITERR=5,DURATION=10;

3. Create a tone ID. The command is ADD TONEID.

Table 119 describes the parameters in the ADD TONEID com-mand.



TABLE 119 PARAMETERS IN THE ADD TONEID COMMAND

ParameterName



Numbered from 1, usedin “MGW static dataconfiguration (ADDMGSCFG), and determiningthe played tones supportedby the MGW

ANARSLT


� EOTA: Endanalysis



TONE Tone ID

Tone ID self-defined inZXWN, for internal use. It isusually consistent with theinternal Tone ID of the MGW.Refer to the correspondingtone list of the Tone ID toconfigure it.

PKG


� CG (CG package)

� CT (CT package)

� AU (AU package)

� AN (AN package)






� 132 (132package)

A parameter defined inthe H.248 protocol, forclassifying tones in theH.248 protocol. For details,see the contents in theH.248 protocol.


This parameter is invalid forbasic service tones.



ParameterName


ID ID Used to specify the ID of thisservice tone

URL

URL address/char-acter string codecorresponded by theservice tone

Used to specify thecorresponding URL addressof this service tone. Ingeneral, only AN andAASB packages need to beconfigured.

For example, create an ID for the vacant number with the fol-lowing requirements.

� ToneID: 101


� Tone package type: AN

� Corresponding URL: cmcc_bs_101


ADD TONEID:TPLID=1,TONE=101,ANARSLT=EOTA,PKG=AN,INPKGID=101,ID=101,URL="cmcc_bs_101",NAME="Invalid Number Tone";

4. Create the play method for service tones. The command isADD TONEPLAYMT.

Table 120 describes the parameters in the ADD TONEPLAYMTcommand.

TABLE 120 PARAMETERS IN THE ADD TONEPLAYMT COMMANDFOR BASIC SERVICE TONES

ParameterName


SRVKEY Service key The basic service key is TRDT.

LANG Language type

Selected according to theactual requirements. Forexample 4097 (First Chineseand then English)

ITERR Iteration timesSelect it according to theactual requirement, such as 5times.

DURATION Playbackduration(s)

Select it according to theactual requirement, such as15 seconds.

CMP

Notify that the toneplay is complete,indicating whetherto notify the MSCSafter tone play

Selected according to theactual requirements. For thevacant number tone, it isrequired to set “notifying theMSCS after tone play”.



For example, create a tone play method for the vacant numbertone with the following requirements.

� Service key: traditional service TDRT

� Language type: 4097 (First Chinese then English)

� Tone play times: 5

� Tone play duration: 15 seconds.


ADD TONEPLAYMT:SRVKEY=TRDT,LANG=4097,ITERR=5,DURATION=15,INTERVAL=1,CMP=YES;



SET:NEID=31;

6. Create a service-tone-to-protocol-tone-package configuration.The command is ADD TONEPRO.

Table 121 describes the parameters in the ADD TONEPROcommand.

TABLE 121 PARAMETERS IN THE ADD TONEPRO COMMAND

ParameterName


PKGTP

Service tone type,corresponding to thePKG parameter inthe ADD TONEIDcommand on the MSCS

A parameter definedin the H.248 protocol,for classifying tones inthe H.248 protocol. Fordetails, see the contentsin the H.248 protocol.

TPRO Service tone type in theprotocol

This parameter is invalidfor basic service tones.Configure it to 1.

TONE Tone ID

Tone ID self-defined inZXWN, for internal use.It is usually consistentwith the internal ToneID of the MSCS. Refer tothe corresponding tonelist of the Tone ID toconfigure it.

ANSPEC Service tone number inthe protocol

A parameter definedin the H.248 protocol,corresponding to theURL parameter in theADD TONEID commandon the MSCS.

SKEY Service keyAn internal service key.The service key of thebasic service tones is 1.



For example, create the vacant-number-ToneID-to-protocoltone package configuration.

� ToneID: 101

� Tone packet type: AN

� Corresponding URL: cmcc_bs_101.


ADD TONEPRO:TPROID=24,PKGTP=AN,TPRO=1,TONE=101,ANSPEC="cmcc_bs_101",SKEY=1,NAME="InvalidNumber Tone";

7. Create the tone-language comparison configuration. The com-mand is ADD LANGSTR.

Table 122 describes the parameters in the ADD LANGSTRcommand.

TABLE 122 PARAMETERS IN THE ADD LANGSTR COMMAND

Parame-ter Name


LGSTR Language Descriptor

Kept to be consistent with theLANG parameter in the ADDTONEPLAYMT command,and analyzing the languagecharacter string.

LG1 Language 1

Configured according to theactual situation, such as Eng,where language 1 is ENG(English)

LG2 Language 2 Configured according to theactual situation




For example, create the vacant-number-tone-language com-parison configuration with the following requirements.

� Language descriptor: Eng

� Language 1: English


ADD LANGSTR:LGSTR="EN",LG1=Eng,LG2=INVALID,LG3=INVALID,LG4=INVALID,LG5=INVALID,NAME="InvalidNumber Tone";

8. Create a tone ID and tone element composition configuration.The command is ADD TONELIST.

Table 123 describes the parameters in the ADD TONELISTcommand.



TABLE 123 PARAMETERS IN THE ADD TONELIST COMMAND

Parame-ter Name


TONE Tone ID Enter the ToneID, which is 101 forthe vacant number tone.

LANG Language type Enter the language type of theservice tone (EN)

KIND Tone type Select Exclu for the vacant numbertone

For example, create composition of the vacant number toneIDand tone element, and add the English tone element compo-nents of the vacant number tone. The specific command is asfollows.

ADD TONELIST:TONE=101,LANG=Eng,KIND=Exclu,ST1=0,ST2=0,ST3=0,ST4=0,ST5=0,VTP1=Invalid,VTP2=Invalid,VTP3=Invalid,VTP4=Invalid,VTP5=Invalid,CD1=65535,CD2=65535,CD3=65535,CD4=65535,CD5=65535,CD6=65535,NAME="Invalid Number Tone";

9. Create a service key configuration on the tone board. The com-mand is ADD TONESVC.

Table 124 describes the parameters in the ADD TONESVCcommand.

TABLE 124 PARAMETERS IN THE ADD TONESVC COMMAND

ParameterName


UNIT MRB unit No. Enter the MRB unit No.

SUNIT Tone subunit No. inthe MRB

Enter the tone subunitNo.

SKEY1 Service key Enter basic service key 1






For example, create the service key configuration on the toneboard in the MGW office with the following requirements. Con-figure service key 1 of the basic services on the TONE subunitof the MRB board. The specific command is as follows.

ADD TONESVC:UNIT=221,SUNIT=9,SKEY1=1,SKEY2=0,SKEY3=0,SKEY4=0,SKEY5=0,SKEY6=0;



10. Transfer data to the foregrounds of the MSCS and the MGW.Dial a local mobile phone to test whether the ring back tone isproperly played.

END OF STEPS

Creating the IntelligentService Tone Play Data



� The MTP interconnection data configuration and the SCCP dataconfiguration with the SCP are complete.

� The service keys and EMIDs are planned together with the SCP.

Context 1. Description of the tone-play data of basic service tones on theMSCS

� External EMID: A tone parameter in PA operations, whichcan exclusively identify the contents and the language typeof the tone to be played between the SCP and the MSCS.This parameter is determined by the SCP, and sent to theSSP.

� Internal EMID: the EMID defined by ZTE. Its coding stan-dard is shown in Figure 12.

FIGURE 12 CODING STANDARD OF THE INTERNAL EMID

� External service key: The service key delivered by theSCP. It is contained in the EMID, which consists of the 8most significant bits in the internal EMID.

� Internal service key: IDs of different intelligent servicein ZTE, which is the highest in the internal EMID code.

Other parameters are the same with those of the basic ser-vice tone play.

2. The intelligent service tone play data on the MGW are the samewith the basic service tone play data on the MGW.




The MSCS translates the external EMID sent from the SCP intothe internal EMID, and finds the external service key, languagetype, and the record notification No. according to the EMID.Then it translates the external service key into the internalservice key, and gets the play method of the corresponding in-telligent service tone. It gets ToneID according to the servicetone notification No. and the service key, translates the ToneIDinto the exclusive combination of TonePro and URL, and trans-lates the language type, play method, and other parametersof the intelligent services at the same time. Then it transfersthe TonePro, URL, language type, and the play method to theMGW.

The intelligent service tone play procedure of the MGW is thesame with the basic service tone play procedure of the MGW.The MGW translates the exclusive combination of TonePro andURL into the ToneID and the service key, translates the lan-guage type to that on the MGW, and saves the play method.It gets the tone element components (fixed tone elements andvariable tone elements) according to the ToneID and the lan-guage type, and gets the tone unit No. and the subunit No.according to service key of the intelligent services.

The intelligent service tone play data configuration is used to en-able the ZXWN CS equipment to play intelligent service tones,complete the SRF function, and implement the function that thesystem can play the related intelligent service tone based on theEMID sent from the SCP. This topic introduces how to configurethe tone play data for the intelligent service.



SET:NEID=11;

2. Create MSGID conversion. The command is ADD EMIDTRF.

Table 125 explains the parameters in the ADD EMIDTRF com-mand.



TABLE 125 PARAMETERS IN THE ADD EMIDTRIF COMMAND

ParameterName


EMID ID of external message Used to specify theEMID to be converted

SRVKEY Service key

Used to specify theexternal service key towhich the EMID is to beconverted

MID Code in the service key

Used to specify theradio access modeapplied to the handoverpolicy

LANG

Language type,including:

� MIXED: indicatesthat the languagetype is mixed tone.

� MANDARIN:indicates thelanguage type ismandarin.

� EN: indicates thelanguage type isEnglish.

� LOCAL: indicatesthe language typeis local language

Select it according tothe actual condition.

Tip:

MSGID (MSGID conversion) can be added in batches throughDev Configuration > Tone Configuration > Tone BatchOperation > Batch Create MSCS Tone (BADD STONE) onthe MML Terminal window.

For example, create MSGID conversion with the following re-quirements.

� External message ID: 201

� Service key: 1

� Code in the service key: 1

� Language type: English.


ADD EMIDTRF:EMID=201,SRVKEY=1,MID=1,LANG=EN;

3. Create the interconnection conversion for service keys. Thecommand is ADD SVRTRANSKEY.

Table 126 describes the parameters in the ADD SVRTRANSKEY command.



TABLE 126 PARAMETERS IN THE ADD SVRTRANSKEYCOMMAND

ParameterName


EXSVCKEY External service keycoding

Specifies the code of anexternal service key

SVCKEY Service Key Codes Specifies a service keycode in the system

NAME Alias

Specifically describesthe service keyinterconnectionconversion to makeit easily recognized

ID IDDefines the servicekey interconnectionconversion in the system

SCPTYPE SCP type Used to specify the SCPtype

SVCKEYDES Service keydescription

Used to specificallydescribe thecorresponding servicekey to make it easilyrecognized

For example, create the service key interconnection conversionwith the following requirements.

� External service key No.: 11

� Service key No.: PPS service

� Alias: "PPS service"

� Configuration ID: 1

� SCP type: 0


ADD SVRTRANSKEY:EXSVCKEY=10,SVCKEY=PPS,NAME="PPS Service",ID=1,SCPTYPE=0;

4. Create service-key-to-service-tone-ID configuration. Thecommand is ADD TONEIN.

Table 127 describes the parameters in the ADD TONEIN com-mand.



TABLE 127 PARAMETERS IN THE ADD TONEIN COMMAND

ParameterName


SVCKEY Service Key Codes Specifies a service keycode in the system

MID The code in the servicekey

Specifies the code ofthe service tone in thecorresponding servicekey

ANARSLT


� EOTA: End analysis


Select it according tothe actual conditions.

TONEID Tone ID Used to specify the IDof the service tone

ID ID

Used to definethe service keyinterconnectionconversion in thesystem

NAME Alias

Used to specificallydescribe the servicekey interconnectionconversion to make iteasily recognized

For example, create service-key-to-service-tone-ID conversionconfiguration with the following requirements.

� Service key codes: PPS service

� Code in the service key: 1



� The No. is tone 20001.


ADD TONEIN:SRVKEY=PPS,ANARSLT=EOTA,MID=1,TONEID=201,ID=20001;

5. Create a tone ID. The command is ADD TONEID. Configurethe ToneID, the corresponding protocol tone package type, andthe corresponding URL of the service tone.

Table 128 describes the parameters in the ADD TONEID com-mand. This step of configuration mainly aims to configure thetone play method for the intelligent service on the MSCS.



TABLE 128 PARAMETERS IN THE ADD TONEID COMMAND

ParameterName



Numbered from 1,used in “MGW staticdata configuration(ADD MGSCFG), anddetermining the playedtones supported by theMGW

TONE Tone ID

Tone ID self-defined inZXWN, for internal use.It is usually consistentwith the internal Tone IDof the MGW. Refer to thecorresponding tone list ofthe Tone ID to configure it.

PKG


� CG (CG package)

� CT (CT package)

� AU (AU package)

� AN (AN package)






� 132 (132package)

A parameter definedin the H.248 protocol,for classifying tones inthe H.248 protocol. Fordetails, see the contentsin the H.248 protocol.


A parameter defined in theH.248 protocol, specifyingthe number of a tone inthe specific type of tonepackage. For details, seethe contents in the H.248protocol.

URL

URL address/char-acter string codecorresponded by theservice tone

Used to indicate thecorresponding URLaddress of the servicetone. In general, only ANand AASB packages needto be configured.

6. Create the play method for service tones. The command isADD TONEPLAYMT.



Table 129 describes the parameters in the ADD TONEPLAYMTcommand. This step of configuration mainly aims to configurethe tone play method for the intelligent service on the MSCS.

TABLE 129 PARAMETERS IN THE ADD TONEPLAYMT COMMAND

ParameterName


SRVKEY Service key Select it according to theactual requirement.

LANG Language type

Selected according to theactual requirements. Forexample 4097 (FirstChinese and then English)

ITERR Iteration timesSelect it according to theactual requirement, such as5 times.

DURATION Playback durationSelect it according to theactual requirement, such as15 seconds.

CMP

Notify that the toneplay is complete,indicating whetherto notify the MSCSafter tone play

Select it according to theactual requirement.

7. Create the language description string. The command is ADDLANGDES.

Table 130 explains the parameters in the ADD LANGDES com-mand. This step of configuration mainly aims to configure thelanguage translation data on the MSCS.

TABLE 130 PARAMETERS IN THE ADD LANGDES COMMAND

ParameterName


TPLID Language templateNo.

Used to specify the templateNo. of the languagedescription string

LANG Language type Used to specify the languagetype

LANGDES Languagedescription string

Used to specify thecorresponding descriptionstring of the language type

NAME Alias

Used to specifically describethe language descriptionstring to make it easilyrecognized

For example, create a language description string with the fol-lowing requirements.



� Language template No.: 1

� Language type: 2

� Language description string: en


ADD LANGDES:TPLID=1,LANG=2,LANGDES="en";



SET:NEID=31;

9. The data configuration procedure of the MGW is the same withthat of the basic service tone on the MGW.

END OF STEPS


Figure

Figure 1 Networking Between MSCS and MGW........................ 2

Figure 2 SIGTRAN CONFIGURATION FLOW............................23

Figure 3 CONFIGURATION FLOW..........................................36

Figure 4 Typical Networking Between the ZXWN CS and the

HLR .................................................................45

Figure 5 Typical Networking Between the ZXWN CS and the

STP .................................................................69

Figure 6 Networking Between the ZXWN CS and the SCP ........86

Figure 7 Networking Between ZXWN CS and SMC ................ 104

Figure 8 Interconnection between ZXWN MSCS and

PSTN/MSC ...................................................... 112

Figure 9 Networking with BSC ........................................... 137

Figure 10 Networking Between MGW and RNC..................... 168

Figure 11 ANALYSIS ORDER OF NUMBER ANALYZERS ........... 214

Figure 12 Coding Standard of the Internal EMID .................. 274


Table

Table 1 Data Collection Table................................................ 2

Table 2 Configuration Flow ................................................... 3

Table 3 PARAMETERS IN THE ADD IP ADDRESS COMMAND .... 4

Table 4 INTERFACE REAL INTERFACE................................... 5

Table 5 ADD IP ADDRESS REAL INTERFACE ......................... 6

Table 6 PARAMETERS IN THE ADD IP ROUTE COMMAND ........ 7

Table 7 PARAMETERS IN THE ADD ADJOFC COMMAND ..........10

Table 8 PARAMETERS IN THE ADD CODECTPL COMMAND ......14

Table 9 PARAMETERS IN THE ADD TOPO COMMAND..............16

Table 10 PARAMETERS IN THE ADD MGWBEARMOD

COMMAND........................................................20

Table 11 PARAMETERS IN THE ADD SCTPCONN COMMAND....24

Table 12 PARAMETERS IN THE ADD ASP COMMAND ..............28

Table 13 PARAMETERS IN THE ADD AS COMMAND ................29

Table 14 PARAMETERS IN THE ADD M3UART COMMAND........32

Table 15 PARAMETERS IN THE ADD SIOLOCAS COMMAND.....34

Table 16 PARAMETERS IN THE ADD MGCSCFG COMMAND......37

Table 17 PARAMETERS IN THE ADD MGSTPL COMMAND ........39

Table 18 PARAMETERS IN THE ADD MGSCFG COMMAND........40

Table 19 PARAMETERS IN THE ADD TIDANL COMMAND.........42

Table 20 PARAMETERS IN THE ADD TIDENTR COMMAND.......44

Table 21 MSCS-HLR Interconnection Data Collection...............45

Table 22 Data for Interconnection with the HLR .....................46

Table 23 PARAMETERS IN THE ADD ADJOFC COMMAND ........47

Table 24 PARAMETERS IN THE ADD N7LKS COMMAND ..........49

Table 25 PARAMETERS IN THE ADD N7LNKE1 COMMAND ......51

Table 26 PARAMETERS IN THE ADD N7ROUTE COMMAND......54

Table 27 ARRANGEMENT MODE OF SIGNALING SETS..............55

Table 28 PARAMETERS IN THE ADD N7OFC COMMAND ..........56

Table 29 PARAMETERS IN THE ADD IMSIANA COMMAND ......58

Table 30 PARAMETERS IN THE ADD GTT COMMAND ..............60

Table 31 PARAMETERS IN THE ADD GT COMMAND ................64

Table 32 SSN ....................................................................67

Table 33 MSCS-STP Data Collection......................................70



Table 34 MSCS-STP Data Configuration Flow .........................70

Table 35 PARAMETERS IN THE ADD ADJOFC COMMAND ........71

Table 36 PARAMETERS IN THE ADD N7LKS COMMAND ..........73

Table 37 PARAMETERS IN THE ADD N7LNKE1 COMMAND ......75

Table 38 PARAMETERS IN THE ADD N7ROUTE COMMAND......78

Table 39 PARAMETERS IN THE ADD N7OFC COMMAND ..........80


Table 41 Data Collection Table .............................................86

Table 42 MSCS-SCP Data Configuration Flow .........................87

Table 43 PARAMETERS IN THE ADD N7SSN COMMAND..........88


Table 45 PARAMETERS IN THE ADD CAMEL COMMAND ..........93

Table 46 PARAMETERS IN THE ADD CAINFO COMMAND ........95

Table 47 PARAMETERS IN THE ADD TPDNAL COMMAND ........97

Table 48 Internal Service Keys .......................................... 100

Table 49 PARAMETERS IN THE ADD SVRTRANSKEY

COMMAND...................................................... 101

Table 50 Service Key Codes .............................................. 101

Table 51 PARAMETERS IN THE ADD TONESVC COMMAND .... 103

Table 52 Data Collection Table ........................................... 105

Table 53 Data Configuration Flow of SMC Adjacent Office ...... 105

Table 54 PARAMETERS IN THE ADD GT COMMAND .............. 106

Table 55 Data for Interconnection with the MGW.................. 112

Table 56 Data for Interconnection with the PSTN/MSC Office .. 112

Table 57 Configuration Flow of PSTN/2G MSC Adjacent Office

Data .............................................................. 113

Table 58 PARAMETERS IN THE ADD ADJOFC COMMAND ...... 114

Table 59 PARAMETERS IN THE ADD TG DT COMMAND ......... 115

Table 60 PARAMETERS IN THE ADD SPCM COMMAND.......... 119

Table 61 PARAMETERS IN THE ADD RT COMMAND .............. 121

Table 62 PARAMETERS IN THE ADD RTS COMMAND ............ 123

Table 63 PARAMETERS IN THE ADD CHAIN COMMAND ........ 124

Table 64 PARAMETERS IN THE ADD SCTPCONN COMMAND .. 127

Table 65 PARAMETERS IN THE ADD ASP COMMAND ............ 129

Table 66 PARAMETERS IN THE ADD AS COMMAND .............. 131

Table 67 PARAMETERS IN THE ADD M3UART COMMAND...... 134

Table 68 PARAMETERS IN THE ADD SIOLOCAS COMMAND... 135


Table 70 Data for Interconnection with the BSC ................... 138

Table 71 BSC Adjacent Office Data Configuration Flow .......... 138


Tables


Table 73 PARAMETERS IN THE ADD BSCOFC COMMAND ...... 144

Table 74 PARAMETERS IN THE ADD TOPO COMMAND.......... 146

Table 75 MAIN PARAMETERS IN THE ADD RNCMGWTOPO

COMMAND...................................................... 149

Table 76 PARAMETERS IN THE ADD TG DT COMMAND ......... 151


Table 78 PARAMETERS IN THE ADD SCTPCONN COMMAND .. 159

Table 79 PARAMETERS IN THE ADD ASP COMMAND ............ 162

Table 80 AS Parameters.................................................... 163

Table 81 PARAMETERS IN THE ADD M3UART COMMAND...... 165

Table 82 PARAMETERS IN THE ADD SIOLOCAS COMMAND... 167


Table 84 Data for Interconnection with the RNC ................... 169

Table 85 RNC Adjacent Office Data Configuration Flow .......... 170


Table 87 PARAMETERS IN THE ADD RNCOFC COMMAND...... 175

Table 88 PARAMETERS IN THE ADD TOPO COMMAND.......... 178

Table 89 PARAMETERS IN THE ADD RNCMGWTOPO

COMMAND...................................................... 182

Table 90 PARAMETERS IN THE ADD TG ATM COMMAND....... 184


Table 92 Access Configuration Flow .................................... 193

Table 93 PARAMETERS IN THE ADD ECC COMMAND............. 194

Table 94 PARAMETERS IN THE ADD SSPN COMMAND .......... 196

Table 95 PARAMETERS IN THE ADD TPDNAL COMMAND ...... 200

Table 96 PARAMETERS IN THE ADD LAI COMMAND ............. 202

Table 97 PARAMETERS IN THE ADD LAI COMMAND ............. 206

Table 98 PARAMETERS IN THE ADD GCI COMMAND............. 210

Table 99 PARAMETERS IN THE ADD SAI COMMAND............. 212

Table 100 DAS FOR PRE-ANALYZING THE CALLED NUMBER ... 214

Table 101 ORIGINATING DAS ............................................ 215

Table 102 FORWARDING DAS............................................ 216

Table 103 ROAMING DAS.................................................. 217

Table 104 PARAMETERS IN THE ADD ENTR COMMAND ........ 219

Table 105 ANALYZER ENTRY TYPES .................................... 220

Table 106 COMMON DASS................................................. 221

Table 107 PARAMETERS IN THE ADD DAS COMMAND .......... 222

Table 108 PARAMETERS IN THE SET LDASTMPLT

COMMAND...................................................... 223



Table 109 PARAMETERS IN THE ADD ACRTMPLT

COMMAND...................................................... 227

Table 110 PARAMETERS IN THE ADD TPDNAL COMMAND .... 230

Table 111 CALL SERVICE TYPES......................................... 244

Table 112 ENABLED OPTIONS............................................ 251

Table 113 PARAMETERS IN THE BADD STONE COMMAND .... 258

Table 114 PARAMETERS IN THE ADD TONEID COMMAND

FOR FIXED TONES ........................................... 260

Table 115 PARAMETERS IN THE ADD TONEPRO COMMAND .. 262

Table 116 PARAMETERS IN THE ADD CODEDOTS

COMMAND...................................................... 263

Table 117 PARAMETERS IN THE ADD FIXTONE COMMAND... 264

Table 118 PARAMETERS IN THE ADD TONESRV COMMAND .. 267

Table 119 PARAMETERS IN THE ADD TONEID COMMAND..... 269

Table 120 PARAMETERS IN THE ADD TONEPLAYMT

COMMAND FOR BASIC SERVICE TONES .............. 270

Table 121 PARAMETERS IN THE ADD TONEPRO COMMAND .. 271

Table 122 PARAMETERS IN THE ADD LANGSTR COMMAND .. 272

Table 123 PARAMETERS IN THE ADD TONELIST COMMAND .. 273

Table 124 PARAMETERS IN THE ADD TONESVC COMMAND .. 273

Table 125 PARAMETERS IN THE ADD EMIDTRIF COMMAND .. 276

Table 126 PARAMETERS IN THE ADD SVRTRANSKEY

COMMAND...................................................... 277

Table 127 PARAMETERS IN THE ADD TONEIN COMMAND .... 278

Table 128 PARAMETERS IN THE ADD TONEID COMMAND..... 279

Table 129 PARAMETERS IN THE ADD TONEPLAYMT

COMMAND...................................................... 280

Table 130 PARAMETERS IN THE ADD LANGDES COMMAND .. 280


Index

DData configuration ....... 2,45, 59, 69, 71, 86–87,93, 104–105, 112, 135,137–138, 168–169, 258,260, 265–266, 269,274–275, 279, 281

GGT translationselector .................. 59,62–63, 68, 81, 85, 87,89, 92, 106, 110

HHandover ................. 46,63, 81, 193, 276

NNetworking mode ..... 104, 168Number section........ 158, 190

OOutgoing route.........113,121–124

PPhysical configura-tion .......... 76, 126, 159, 266

SSignaling link ............ 70,73–79, 105, 169Signaling point ............ 2,45–48, 59, 70, 72, 86,88, 105, 112, 114, 138,166–167, 169Signaling route.......... 70,78–80, 87, 105


sj-20100211152857-010-zxwn mscs (v3.09.21) msc server common configuration operation guide

Documents