0% found this document useful (0 votes)

223 views385 pages

SG7000 Data Configuration (V200R005C02 - 02)

Uploaded by

Catherine Higino

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

223 views385 pages

SG7000 Data Configuration (V200R005C02 - 02)

Uploaded by

Catherine Higino

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 385

U-SYS SG7000 Signaling Gateway

V200R005C02

Data Configuration

Issue 02
Date 2009-12-14

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2009. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China

Website: http://www.huawei.com
Email: [email protected]

Issue 02 (2009-12-14) Huawei Proprietary and Confidential i

About This Document

Purpose
This document describes the data configuration, management, and maintenance operation on
the U-SYS SG7000 Signaling Gateway.

Related Versions
The following table lists the product versions related to this document.

Product Name Version

U-SYS SG7000 V200R005C02

Intended Audience
The intended audiences of this document are:

l Installation engineers
l Commissioning engineers
l System engineers

Organization
Chapter Description

1 Description of Data Configuration Describes the general steps of configuring

SG7000 data, principles and precautions.

2 Configuring Hardware Data Describes the concept and steps of configuring

the hardware data.

3 Configuring Local Office Data Describes how to configure the local office
information.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential iii

Chapter Description

4 Configuring MTP Data Describes how to configure the MTP data.

5 Configuring MTP Shielding Data Describes how to configure the MTP shielding
data.

6 Configuring SCCP Data Describes how to configure the SCCP data.

7 Configuring SCCP Shielding Data Describes how to configure the SCCP shielding
data.

8 Configuring SCTP Data Describes how to configure the SCTP data.

11 Configuring M3UA Data Describes how to configure the M3UA data.

13 Configuring M2PA Data Describes how to configure the M2PA data.

14 Configuring M2UA Data Describes how to configure the M2UA data.

15 Configuring IUA Data Describes how to configure the IUA data.

16 List of Data Configuration Lists the commands used in the data

Commands configuration.

Conventions
Symbol Conventions
The following symbols may be found in this document. They are defined as follows.

Symbol Description

Indicates a hazard with a high level of risk which, if not

avoided, will result in death or serious injury.
DANGER

Indicates a hazard with a medium or low level of risk which,

if not avoided, could result in minor or moderate injury.
WARNING

Indicates a potentially hazardous situation that, if not

avoided, could cause equipment damage, data loss, and
CAUTION
performance degradation, or unexpected results.
TIP Indicates a tip that may help you solve a problem or save
your time.

NOTE Provides additional information to emphasize or

supplement important points of the main text.

iv Huawei Proprietary and Confidential Issue 02 (2009-12-14)

General Conventions
Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in boldface. For
example, log in as user root.

Italic Book titles are in italics.

Courier New Terminal display is in Courier New.

Command Conventions
Convention Description

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italic.

[] Items (keywords or arguments) in square brackets [ ] are

optional.

{ x | y | ... } Alternative items are grouped in braces and separated by

vertical bars. One is selected.

[ x | y | ... ] Optional alternative items are grouped in square brackets

and separated by vertical bars. One or none is selected.

{ x | y | ... } * Alternative items are grouped in braces and separated by

vertical bars. A minimum of one or a maximum of all can
be selected.

GUI Conventions
Convention Description

Boldface Buttons, menus, parameters, tabs, window, and dialog titles are in
boldface. For example, click OK.

> Multi-level menus are in boldface and separated by the ">" signs. For
example, choose File > Create > Folder.

Keyboard Operation
Format Description

Key Press the key. For example, press Enter and press Tab.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential v

Format Description

Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt+A means the
three keys should be pressed concurrently.

Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means the two keys
should be pressed in turn.

Mouse Operation
Action Description

Click Select and release the primary mouse button without moving the pointer.

Double-click Press the primary mouse button twice continuously and quickly without
moving the pointer.

Drag Press and hold the primary mouse button and move the pointer to a certain
position.

Update History
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous versions.

Updates in Issue 02 (2009-12-14)

The PDB (DPD100-2-20) is added.

Updates in Issue 01 (2009-09-27)

Initial commercial release.

vi Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Contents

About This Document...................................................................................................................iii

1 Description of Data Configuration.........................................................................................1-1
1.1 Data Configuration Procedures.......................................................................................................................1-3
1.1.1 Overview................................................................................................................................................1-3
1.1.2 Configuration Tasks...............................................................................................................................1-4
1.2 General Principles...........................................................................................................................................1-6
1.3 Guide to Using MML......................................................................................................................................1-8
1.3.1 Description of MML Operation.............................................................................................................1-8
1.3.2 Usage of Data Script..............................................................................................................................1-9
1.3.3 Common Commands..............................................................................................................................1-9
1.4 Operation of Database...................................................................................................................................1-10
1.4.1 Overview of Database..........................................................................................................................1-10
1.4.2 Setting Online Mode............................................................................................................................1-11
1.4.3 Converting Format...............................................................................................................................1-12
1.4.4 Checking Consistency..........................................................................................................................1-13
1.4.5 Backing Up Database...........................................................................................................................1-14

2 Configuring Hardware Data....................................................................................................2-1

2.1 Configuration Preparations.............................................................................................................................2-3
2.1.1 OSTA 16IP Background Information....................................................................................................2-3
2.1.2 Relation Between Data Tables...............................................................................................................2-6
2.1.3 Data Collection.......................................................................................................................................2-7
2.1.4 Configuration Principles........................................................................................................................2-8
2.1.5 General Steps..........................................................................................................................................2-9
2.2 Configuring Board Data..................................................................................................................................2-9
2.2.1 Configuring Trunk Interface Board Work Status.................................................................................2-10
2.2.2 Configuring Clock Board Work Status................................................................................................2-12
2.2.3 Adding Local IP Address.....................................................................................................................2-14
2.2.4 Adding Board.......................................................................................................................................2-15
2.3 Loading Hardware Data................................................................................................................................2-18
2.4 Configuration Examples................................................................................................................................2-19

3 Configuring Local Office Data................................................................................................3-1

3.1 Configuration Preparations.............................................................................................................................3-3

Issue 02 (2009-12-14) Huawei Proprietary and Confidential vii

3.1.1 Terms......................................................................................................................................................3-3
3.1.2 Relation Between Data Tables...............................................................................................................3-4
3.1.3 Data Collection.......................................................................................................................................3-4
3.1.4 General Steps..........................................................................................................................................3-5
3.2 Configuring Basic Local Office Information..................................................................................................3-5
3.2.1 Adding Logical Network (Optional)......................................................................................................3-6
3.2.2 Adding Local Office Information..........................................................................................................3-8
3.2.3 Adding the Local Office OPC Information (Optional)..........................................................................3-9
3.3 Configuration Examples................................................................................................................................3-10

4 Configuring MTP Data.............................................................................................................4-1

4.1 Configuration Preparations.............................................................................................................................4-3
4.1.1 Terms......................................................................................................................................................4-3
4.1.2 Networking Structure...........................................................................................................................4-13
4.1.3 Relation Between Data Tables.............................................................................................................4-13
4.1.4 Data Collection.....................................................................................................................................4-15
4.1.5 Configuration Principles......................................................................................................................4-16
4.1.6 General Steps........................................................................................................................................4-20
4.2 Configuring MTP Data..................................................................................................................................4-21
4.2.1 Adding MTP DSP................................................................................................................................4-22
4.2.2 Adding MTP Link Set..........................................................................................................................4-24
4.2.3 Adding MTP Route..............................................................................................................................4-31
4.2.4 Adding TDM Semi-Permanent Connection.........................................................................................4-33
4.2.5 Adding MTP Link................................................................................................................................4-35
4.3 Configuration Examples................................................................................................................................4-39

5 Configuring MTP Shielding Data..........................................................................................5-1

5.1 Configuration Preparations.............................................................................................................................5-3
5.1.1 Terms......................................................................................................................................................5-3
5.1.2 Networking Structure.............................................................................................................................5-3
5.1.3 Relation Between Data Tables...............................................................................................................5-4
5.1.4 Data Collection.......................................................................................................................................5-6
5.1.5 General Steps..........................................................................................................................................5-6
5.2 Configuring MTP Shielding Data...................................................................................................................5-7
5.2.1 Adding Prohibited TFM Table...............................................................................................................5-7
5.2.2 Adding Allowed SIO Table....................................................................................................................5-8
5.2.3 Adding Prohibited SIO Table...............................................................................................................5-10
5.2.4 Adding Allowed DPC Table................................................................................................................5-13
5.2.5 Adding Allowed OPC Table................................................................................................................5-16
5.2.6 Adding Prohibited DPC Table.............................................................................................................5-17
5.2.7 Adding Prohibited OPC Table.............................................................................................................5-19
5.2.8 Adding Link Set Shielding Table.........................................................................................................5-20
5.2.9 Adding Initial Shielding Table.............................................................................................................5-22
5.3 Configuration Examples................................................................................................................................5-24

viii Huawei Proprietary and Confidential Issue 02 (2009-12-14)

6 Configuring SCCP Data............................................................................................................6-1

6.1 Configuration Preparations............................................................................................................................. 6-3
6.1.1 Terms......................................................................................................................................................6-3
6.1.2 Networking Structure.............................................................................................................................6-6
6.1.3 Relation Between Data Tables...............................................................................................................6-7
6.1.4 Data Collection.......................................................................................................................................6-8
6.1.5 Configuration Principles........................................................................................................................ 6-8
6.1.6 General Steps........................................................................................................................................6-12
6.2 Configuring SCCP Data................................................................................................................................6-14
6.2.1 Adding SCCP Subsystem (Optional)...................................................................................................6-15
6.2.2 Adding New Global Title (GT) (Optional)..........................................................................................6-16
6.2.3 Adding SCCP Calling GT Segment (Optional)...................................................................................6-20
6.2.4 Adding Calling GT Load-Share Select Set (Optional).........................................................................6-22
6.2.5 Adding OPC Section Range (Optional)...............................................................................................6-23
6.2.6 Adding OPC Load-Share Select Set (Optional)...................................................................................6-24
6.2.7 Adding SCCP Addressing Policy (Optional).......................................................................................6-25
6.2.8 Adding GT............................................................................................................................................6-31
6.3 Configuration Examples................................................................................................................................6-34
6.3.1 Configuration Example of Single Point Work Mode...........................................................................6-34
6.3.2 Configuration Example of Multipoint Work Mode.............................................................................6-36

7 Configuring SCCP Shielding Data.........................................................................................7-1

7.1 Configuration Preparations............................................................................................................................. 7-3
7.1.1 Terms......................................................................................................................................................7-3
7.1.2 Networking Structure.............................................................................................................................7-3
7.1.3 Relation Between Data Tables...............................................................................................................7-4
7.1.4 Data Collection.......................................................................................................................................7-5
7.1.5 General Steps..........................................................................................................................................7-5
7.2 Configuring SCCP Shielding Data..................................................................................................................7-6
7.2.1 Adding the Called GT Translation Type Shielding............................................................................... 7-7
7.2.2 Adding the Called GT Shielding Table..................................................................................................7-8
7.2.3 Adding the Called DPCSSN Shielding Table......................................................................................7-12
7.2.4 Adding the SCCP Message Type Shielding Table...............................................................................7-13
7.2.5 Adding the Caller GT Type Shielding.................................................................................................7-14
7.2.6 Adding the Caller GT Shielding Table................................................................................................7-16
7.2.7 Adding the Caller DPCSSN Shielding Table.......................................................................................7-20
7.3 Configuration Examples................................................................................................................................7-22

8 Configuring SCTP Data............................................................................................................8-1

8.1 Configuration Preparations............................................................................................................................. 8-3
8.1.1 Terms......................................................................................................................................................8-3
8.1.2 Networking Structure.............................................................................................................................8-5
8.1.3 Relation Between Data Tables...............................................................................................................8-5
8.1.4 Data Collection.......................................................................................................................................8-5

Issue 02 (2009-12-14) Huawei Proprietary and Confidential ix

8.1.5 General Steps..........................................................................................................................................8-5

8.2 Configuring SCTP Data..................................................................................................................................8-6
8.2.1 Setting SCTP Initialization Parameter Data (Optional).........................................................................8-6
8.2.2 Adding SCTP Protocol Parameter Data (Optional)...............................................................................8-8

9 Configuring SUA Data..............................................................................................................9-1

9.1 Configuration Preparations.............................................................................................................................9-3
9.1.1 Terms......................................................................................................................................................9-3
9.1.2 Networking Structure for Configuring the SUA Data...........................................................................9-7
9.1.3 Relations Between Data Tables..............................................................................................................9-7
9.1.4 Data Collection.......................................................................................................................................9-8
9.1.5 Configuration Principles........................................................................................................................9-9
9.1.6 General Steps........................................................................................................................................9-10
9.2 Configuring the SUA Data............................................................................................................................9-11
9.2.1 Adding the Local IP Address...............................................................................................................9-12
9.2.2 Adding the Local IP Address Combination.........................................................................................9-12
9.2.3 Adding the Remote IP Address............................................................................................................9-13
9.2.4 Adding the Remote IP Address Combination......................................................................................9-14
9.2.5 Adding the Access Control Information..............................................................................................9-15
9.2.6 Adding the MTP DSP..........................................................................................................................9-16
9.2.7 Adding the SUA Application Server....................................................................................................9-16
9.2.8 Adding the SUA Link Set....................................................................................................................9-17
9.2.9 Adding the SUA Link..........................................................................................................................9-19
9.3 Configuration Examples................................................................................................................................9-22

10 Configuring the SUA Shielding Data................................................................................10-1

10.1 Configuration Preparations.........................................................................................................................10-3
10.1.1 Terms..................................................................................................................................................10-3
10.1.2 Networking Structure of the SUA Shielding......................................................................................10-3
10.1.3 Relations Between Data Tables..........................................................................................................10-4
10.1.4 Data Collection...................................................................................................................................10-6
10.1.5 General Steps......................................................................................................................................10-6
10.2 Configuring the SUA Shielding Data..........................................................................................................10-7
10.2.1 Adding the SUA Message Type Screen Table...................................................................................10-8
10.3 Configuration Examples............................................................................................................................10-11

11 Configuring M3UA Data......................................................................................................11-1

11.1 Configuration Preparations.........................................................................................................................11-3
11.1.1 Terms..................................................................................................................................................11-3
11.1.2 Networking Structure.........................................................................................................................11-6
11.1.3 Relation Between Data Tables...........................................................................................................11-6
11.1.4 Data Collection...................................................................................................................................11-9
11.1.5 Configuration Principles....................................................................................................................11-9
11.1.6 General Steps....................................................................................................................................11-10

x Huawei Proprietary and Confidential Issue 02 (2009-12-14)

11.2 Configuring M3UA Data..........................................................................................................................11-11

11.2.1 Adding Local IP Address.................................................................................................................11-12
11.2.2 Adding Local IP Address Combination...........................................................................................11-12
11.2.3 Adding Remote IP Address..............................................................................................................11-13
11.2.4 Adding Remote IP Address Combination........................................................................................11-14
11.2.5 Adding Access Control Information................................................................................................11-14
11.2.6 Adding Destination Signaling Point ................................................................................................11-15
11.2.7 Adding M3UA Application Server Data..........................................................................................11-15
11.2.8 Adding M3UA Complementary Routing Data (Optional)...............................................................11-17
11.2.9 Adding M3UA Link Set Data..........................................................................................................11-20
11.2.10 Adding M3UA Route Data............................................................................................................11-27
11.2.11 Adding M3UA Association Data...................................................................................................11-28
11.3 Configuration Examples............................................................................................................................11-31
11.3.1 Transfer Mode (Example 1).............................................................................................................11-32
11.3.2 Agent Mode (Example 2).................................................................................................................11-34

12 Configuring M3UA Shielding Data...................................................................................12-1

12.1 Configuration Preparations.........................................................................................................................12-3
12.1.1 Terms..................................................................................................................................................12-3
12.1.2 Networking Structure of the M3UA Shielding..................................................................................12-4
12.1.3 Mapping Between Data Tables..........................................................................................................12-5
12.1.4 Data Collection...................................................................................................................................12-8
12.1.5 General Steps......................................................................................................................................12-8
12.2 Configuring the M3UA Shielding Data......................................................................................................12-9
12.2.1 Adding the Prohibited RC Table........................................................................................................12-9
12.2.2 Adding the M3UA Message Type Shielding Table.........................................................................12-10
12.2.3 Adding Allowed SIO Table..............................................................................................................12-12
12.2.4 Adding Prohibited SIO Table...........................................................................................................12-14
12.2.5 Adding Allowed DPC Table............................................................................................................12-17
12.2.6 Adding Allowed OPC Table............................................................................................................12-19
12.2.7 Adding Prohibited DPC Table.........................................................................................................12-21
12.2.8 Adding Prohibited OPC Table.........................................................................................................12-22
12.2.9 Adding Link Set Shielding Table.....................................................................................................12-24
12.2.10 Adding the Initial Shielding Table.................................................................................................12-26
12.3 Configuration Examples............................................................................................................................12-27

13 Configuring M2PA Data.......................................................................................................13-1

13.1 Configuration Preparations.........................................................................................................................13-3
13.1.1 Terms..................................................................................................................................................13-3
13.1.2 Networking Structure.........................................................................................................................13-3
13.1.3 Relation Between Data Tables...........................................................................................................13-4
13.1.4 Data Collection...................................................................................................................................13-4
13.1.5 Configuration Principles....................................................................................................................13-5
13.1.6 General Steps......................................................................................................................................13-5

Issue 02 (2009-12-14) Huawei Proprietary and Confidential xi

13.2 Configuring M2PA Data.............................................................................................................................13-6

13.2.1 Adding M2PA Link............................................................................................................................13-7
13.3 Configuration Examples............................................................................................................................13-10

14 Configuring M2UA Data......................................................................................................14-1

14.1 Configuration Preparations.........................................................................................................................14-3
14.1.1 Terms..................................................................................................................................................14-3
14.1.2 Networking Structure.........................................................................................................................14-5
14.1.3 Relation Between Data Tables...........................................................................................................14-6
14.1.4 Data Collection...................................................................................................................................14-7
14.1.5 Configuration Principles....................................................................................................................14-7
14.1.6 General Steps......................................................................................................................................14-8
14.2 Configuring M2UA Data............................................................................................................................14-9
14.2.1 Adding M2UA Link Set...................................................................................................................14-10
14.2.2 Adding M2UA Link.........................................................................................................................14-11
14.2.3 Adding MTP Link............................................................................................................................14-14
14.3 Configuration Examples............................................................................................................................14-17

15 Configuring IUA Data...........................................................................................................15-1

15.1 Configuration Preparations.........................................................................................................................15-3
15.1.1 Terms..................................................................................................................................................15-3
15.1.2 Networking Structure.........................................................................................................................15-4
15.1.3 Relation Between Data Tables...........................................................................................................15-5
15.1.4 Data Collection...................................................................................................................................15-6
15.1.5 Configuration Principles....................................................................................................................15-6
15.1.6 General Steps......................................................................................................................................15-7
15.2 Configuring IUA Data.................................................................................................................................15-8
15.2.1 Adding the Board...............................................................................................................................15-9
15.2.2 Adding Local IP Address.................................................................................................................15-11
15.2.3 Adding Local IP Address Combination...........................................................................................15-11
15.2.4 Adding Extended Remote IP Address..............................................................................................15-11
15.2.5 Adding Extended Remote IP Address Combination........................................................................15-12
15.2.6 Adding the Extended Access Control Information..........................................................................15-13
15.2.7 Setting Software Configuration Parameter......................................................................................15-13
15.2.8 Converting Formats..........................................................................................................................15-14
15.2.9 Setting Board Software DIP Switch.................................................................................................15-15
15.2.10 Adding IUA Link Set.....................................................................................................................15-15
15.2.11 Adding IUA link.............................................................................................................................15-16
15.3 Configuration Examples............................................................................................................................15-19

16 List of Data Configuration Commands..............................................................................16-1

xii Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Figures

Figure 1-1 Procedures of the SG7000 data configuration....................................................................................1-2

Figure 2-1 Data configuration procedure.............................................................................................................2-2
Figure 2-2 Full configuration of the SG7000 16IP cabinets................................................................................2-4
Figure 2-3 Board configuration in main control frame........................................................................................2-6
Figure 2-4 Board configuration in service frame.................................................................................................2-6
Figure 2-5 Parameters relationship of hardware data configuration commands..................................................2-7
Figure 2-6 Clock connection..............................................................................................................................2-20
Figure 3-1 Data configuration procedure.............................................................................................................3-2
Figure 3-2 Parameter index between local office data commands.......................................................................3-4
Figure 4-1 Data configuration procedure.............................................................................................................4-2
Figure 4-2 SS7 structure.......................................................................................................................................4-4
Figure 4-3 Adjacent signaling point.....................................................................................................................4-5
Figure 4-4 Non-adjacent signaling point..............................................................................................................4-5
Figure 4-5 TDM semi-permanent connection in the same slot............................................................................4-8
Figure 4-6 TDM semi-permanent connection in different slots...........................................................................4-9
Figure 4-7 Relations between the VP, VC, and physical channel........................................................................4-9
Figure 4-8 Typical networking for implementing the binding-based linkset load sharing function..................4-12
Figure 4-9 Networking through the MTP3 protocol..........................................................................................4-13
Figure 4-10 Relations between the MTP data tables..........................................................................................4-14
Figure 4-11 Relations between the timer, threshold, and MTP data tables........................................................4-15
Figure 4-12 Relation between the MTP initial shielding table and the MTP link set table...............................4-15
Figure 4-13 Load sharing of signaling traffic among multiple SPCs.................................................................4-20
Figure 4-14 Configuration example...................................................................................................................4-39
Figure 5-1 Data configuration procedure.............................................................................................................5-2
Figure 5-2 Networking through the MTP3 protocol............................................................................................5-4
Figure 5-3 Data indices between MTP shielding data table.................................................................................5-5
Figure 6-1 Data configuration procedure.............................................................................................................6-2
Figure 6-2 Networking of configuring SCCP data...............................................................................................6-7
Figure 6-3 Relations between the SCCP data tables............................................................................................6-7
Figure 6-4 Structure 1...........................................................................................................................................6-8
Figure 6-5 Structure 2...........................................................................................................................................6-9
Figure 6-6 Step 1 of load sharing algorithm ......................................................................................................6-11
Figure 6-7 Example of SCCP sending messages...............................................................................................6-34

Issue 02 (2009-12-14) Huawei Proprietary and Confidential xiii

Figure 6-8 Multipoint sharing SCCP..................................................................................................................6-36

Figure 7-1 Data configuration procedure.............................................................................................................7-2
Figure 7-2 Networking of configuring SCCP data...............................................................................................7-3
Figure 7-3 Relation between the shielding data tables starting from the caller SCCPSSN.................................7-4
Figure 7-4 Relation between the shielding data tables starting from the caller GT.............................................7-5
Figure 8-1 Data configuration procedure.............................................................................................................8-2
Figure 8-2 SCTP data networking........................................................................................................................8-5
Figure 9-1 Data configuration procedure.............................................................................................................9-2
Figure 9-2 SIGTRAN protocol module................................................................................................................9-4
Figure 9-3 SUA protocol stack.............................................................................................................................9-4
Figure 9-4 SG-ASP application mode..................................................................................................................9-5
Figure 9-5 IPSP-IPSP application mode..............................................................................................................9-5
Figure 9-6 Networking structure for configuring the SUA data..........................................................................9-7
Figure 9-7 Relations between SUA data tables....................................................................................................9-8
Figure 9-8 Networking structure for configuring the SUA data........................................................................ 9-22
Figure 10-1 Data configuration procedure.........................................................................................................10-2
Figure 10-2 Networking structure for configuring the SUA data...................................................................... 10-4
Figure 10-3 Reference relations starting from the calling SCCPSSN................................................................10-5
Figure 10-4 Reference relations starting from the calling GT........................................................................... 10-6
Figure 11-1 Data configuration procedure.........................................................................................................11-2
Figure 11-2 SIGTRAN protocol module............................................................................................................11-4
Figure 11-3 Networking structure of the M3UA data........................................................................................11-6
Figure 11-4 Relation between the M3UA data tables........................................................................................11-8
Figure 11-5 Networking of the M3UA data configuration..............................................................................11-32
Figure 12-1 Data configuration procedure.........................................................................................................12-2
Figure 12-2 Networking structure of the M3UA shielding................................................................................12-4
Figure 12-3 Reference relation between M3UA shielding conditions and link set........................................... 12-5
Figure 12-4 Reference relations internal the M3UA shielding data table..........................................................12-7
Figure 13-1 Data configuration procedure.........................................................................................................13-2
Figure 13-2 Networking structure when configuring the M2PA data................................................................13-3
Figure 13-3 Relation Between the M2PA Data Tables......................................................................................13-4
Figure 13-4 Configuration example.................................................................................................................13-10
Figure 14-1 Data configuration procedure.........................................................................................................14-2
Figure 14-2 M2UA protocol stack in the SG7000.............................................................................................14-3
Figure 14-3 Relationship between the SS7 link, interface ID, and AS and ASP...............................................14-4
Figure 14-4 M2UA network structure................................................................................................................14-5
Figure 14-5 Simplified M2UA network structure..............................................................................................14-5
Figure 14-6 M2UA application..........................................................................................................................14-6
Figure 14-7 Relation between the M2UA configuration parameters.................................................................14-6
Figure 14-8 Network requiring the M2UA data configuration........................................................................14-17
Figure 15-1 Data configuration procedure.........................................................................................................15-2
Figure 15-2 IUA protocol stack..........................................................................................................................15-3

xiv Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Figure 15-3 Application of IUA in the SG7000.................................................................................................15-4

Figure 15-4 SG7000 networking with the IUA protocol...................................................................................15-5
Figure 15-5 Relation between IUA data tables..................................................................................................15-5
Figure 15-6 Networking of the IUA data configuration...................................................................................15-20

Issue 02 (2009-12-14) Huawei Proprietary and Confidential xv

Tables

Table 1-1 Procedures of the SG7000 data configuration.....................................................................................1-3

Table 1-2 Contents of the SG7000 data configuration.........................................................................................1-4
Table 1-3 Configuring data for the first deployment............................................................................................1-7
Table 1-4 Implication of the MML command....................................................................................................1-10
Table 2-1 Relationship between switch bit and logical frame number................................................................2-5
Table 2-2 Hardware data collection table.............................................................................................................2-7
Table 2-3 Steps of configuring hardware data......................................................................................................2-9
Table 2-4 Related commands for configuring the trunk interface board working status...................................2-12
Table 2-5 Related commands for configuring the clock board working status..................................................2-13
Table 2-6 Related commands for adding the local IP address............................................................................2-15
Table 2-7 Related commands for adding the board............................................................................................2-18
Table 2-8 Load hardware data............................................................................................................................2-19
Table 2-9 Hardware data collection table...........................................................................................................2-20
Table 3-1 Data collection table.............................................................................................................................3-5
Table 3-2 Procedures for configuring local office information............................................................................3-5
Table 3-3 Related commands for configuring the logical network......................................................................3-7
Table 3-4 Related commands for configuring the local office information.........................................................3-9
Table 3-5 Related commands for configuring the local office OPC information..............................................3-10
Table 3-6 Data collection table...........................................................................................................................3-11
Table 4-1 Load sharing for all SLSs (SLS0-SLS15) when all links are available.............................................4-11
Table 4-2 Load sharing for valid SLSs (bold) when link2 is faulty (before reallocation of SLSs)....................4-11
Table 4-3 Load sharing for valid SLSs (bold) when link2 is faulty (after reallocation of SLSs)......................4-11
Table 4-4 Data collection...................................................................................................................................4-15
Table 4-5 Configuring the MTP data.................................................................................................................4-21
Table 4-6 Related commands for configuring the MTP DSP............................................................................4-24
Table 4-7 Related commands for configuring the MTP DSP............................................................................4-31
Table 4-8 Related commands for configuring the MTP route............................................................................4-33
Table 4-9 Related commands for configuring the TDM semi-permanent connection.......................................4-35
Table 4-10 Parameters of SAT64 kbit/s, NOR64 kbit/s and HSL......................................................................4-38
Table 4-11 Parameters of ATM .........................................................................................................................4-38
Table 4-12 Related commands for configuring the MTP link............................................................................4-39
Table 4-13 Data collection table.........................................................................................................................4-40
Table 5-1 Data collection table.............................................................................................................................5-6

Issue 02 (2009-12-14) Huawei Proprietary and Confidential xvii

Table 5-2 Steps to configure the MTP shielding data..........................................................................................5-6

Table 5-3 Related commands for configuring the prohibited TFM table.............................................................5-8
Table 5-4 Related commands for configuring the allowed SIO table................................................................5-10
Table 5-5 Related commands for configuring the prohibited SIO table............................................................5-13
Table 5-6 Related commands for configuring the allowed DPC table...............................................................5-15
Table 5-7 Related commands for configuring the allowed OPC table...............................................................5-17
Table 5-8 Related commands for configuring the prohibited DPC table...........................................................5-19
Table 5-9 Related commands for configuring the prohibited OPC table...........................................................5-20
Table 5-10 Related commands for configuring the link set shielding table.......................................................5-22
Table 5-11 Related commands for configuring the initial shielding table.........................................................5-23
Table 5-12 Data collection table.........................................................................................................................5-24
Table 6-1 Structure of GT4..................................................................................................................................6-4
Table 6-2 Data collection table.............................................................................................................................6-8
Table 6-3 Configuring the SCCP to single point work mode.............................................................................6-12
Table 6-4 Configuring the SCCP to SLS or LIDX or TID load sharing mode..................................................6-13
Table 6-5 Configuring the SCCP to OPC load sharing mode............................................................................6-13
Table 6-6 Configuring SCCP to CLNG load sharing mode...............................................................................6-14
Table 6-7 Related commands for configuring the SCCP subsystem..................................................................6-16
Table 6-8 Options of Address prefix convert mode........................................................................................6-18
Table 6-9 Convert example................................................................................................................................6-19
Table 6-10 Related commands for configuring the new GT..............................................................................6-20
Table 6-11 Related commands for configuring the SCCP calling segment.......................................................6-22
Table 6-12 Related commands for configuring the SCCP calling the GT load-share select set........................6-23
Table 6-13 Related commands for configuring the OPC section range.............................................................6-24
Table 6-14 Related commands for configuring the SCCP OPC load-share select set.......................................6-25
Table 6-15 Related commands for configuring the SCCP addressing policy....................................................6-30
Table 6-16 Related commands for configuring the GT......................................................................................6-34
Table 6-17 SP A data collection table................................................................................................................6-35
Table 6-18 SP B data collection table................................................................................................................6-35
Table 6-19 Data collection table.........................................................................................................................6-37
Table 7-1 Data collection table.............................................................................................................................7-5
Table 7-2 Configuring the SCCPSSN shielding data...........................................................................................7-6
Table 7-3 Configuring the caller GT shielding data.............................................................................................7-6
Table 7-4 Related commands for configuring the called GT type shielding table...............................................7-8
Table 7-5 Related commands for configuring the called GT shielding table.....................................................7-11
Table 7-6 Related commands for configuring the called DPCSSN shielding table...........................................7-13
Table 7-7 Related commands for configuring the SCCP message type shielding table....................................7-14
Table 7-8 Related commands for configuring the caller GT type shielding table..............................................7-16
Table 7-9 Related commands for configuring the caller GT shielding table.....................................................7-20
Table 7-10 Related commands for configuring the caller DPCSSN shielding table..........................................7-22
Table 7-11 Data collection table.........................................................................................................................7-22
Table 8-1 Configuring the SCTP data..................................................................................................................8-5

xviii Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Table 8-2 Related commands for setting the SCTP initialization parameter.......................................................8-8
Table 8-3 Related commands for configuring the SCTP protocol parameter......................................................8-9
Table 9-1 SUA data collection table.....................................................................................................................9-9
Table 9-2 General steps for configuring the SUA data......................................................................................9-10
Table 9-3 Related commands for configuring the local IP address combination...............................................9-13
Table 9-4 Related commands for configuring the remote IP address................................................................ 9-13
Table 9-5 Related commands for configuring the remote IP address combination........................................... 9-14
Table 9-6 Related commands for configuring the access control information...................................................9-15
Table 9-7 Related commands for configuring the SUA application server........................................................9-17
Table 9-8 Related commands for configuring the SUA link set........................................................................ 9-19
Table 9-9 Related commands for configuring the SUA link..............................................................................9-22
Table 9-10 SUA data collection table.................................................................................................................9-23
Table 10-1 Data collection table.........................................................................................................................10-6
Table 10-2 Configuring the SUA shielding data................................................................................................10-7
Table 10-3 Configuring the SCCPSSN shielding data.......................................................................................10-7
Table 10-4 Configuring the caller GT shielding data.........................................................................................10-7
Table 10-5 Related commands for configuring the SUA message type screen table.......................................10-11
Table 10-6 Data collection table.......................................................................................................................10-11
Table 11-1 M3UA data collection table.............................................................................................................11-9
Table 11-2 Steps for configuring the M3UA data............................................................................................11-10
Table 11-3 Related commands for configuring the local IP address combination table..................................11-13
Table 11-4 Related commands for configuring the remote IP address............................................................11-13
Table 11-5 Related commands for configuring the remote IP address combination table...............................11-14
Table 11-6 Related commands for configuring the access control information...............................................11-15
Table 11-7 Related commands for configuring the M3UA application server................................................11-17
Table 11-8 Related commands for configuring the M3UA complementary routing.......................................11-19
Table 11-9 Related commands for configuring the M3UA link set.................................................................11-27
Table 11-10 Related commands for configuring the M3UA route...................................................................11-28
Table 11-11 Related commands for configuring the M3UA link set...............................................................11-31
Table 11-12 Data collection table of example 1...............................................................................................11-33
Table 11-13 Data collection table of example 2...............................................................................................11-34
Table 12-1 Data collection table.........................................................................................................................12-8
Table 12-2 General steps for configuring the M3UA shielding data................................................................. 12-8
Table 12-3 Related commands for configuring the prohibited RC table..........................................................12-10
Table 12-4 Related commands for configuring the M3UA message type table...............................................12-11
Table 12-5 Related commands for configuring the allowed SIO table............................................................12-14
Table 12-6 Related commands for configuring the prohibited SIO table........................................................12-16
Table 12-7 Related commands for configuring the allowed DPC table...........................................................12-19
Table 12-8 Related commands for configuring the allowed OPC table...........................................................12-21
Table 12-9 Related commands for configuring the prohibited DPC table.......................................................12-22
Table 12-10 Related commands for configuring the prohibited OPC table.....................................................12-24
Table 12-11 Related commands for configuring the link set shielding table...................................................12-25

Issue 02 (2009-12-14) Huawei Proprietary and Confidential xix

Table 12-12 Related commands for configuring the initial shielding table.....................................................12-27
Table 12-13 Data collection table.....................................................................................................................12-27
Table 13-1 Data collection table.........................................................................................................................13-4
Table 13-2 Steps for adding the M2PA connection...........................................................................................13-6
Table 13-3 Reference list....................................................................................................................................13-6
Table 13-4 Parameter descriptions when the Circuit type is set to M2PALINK.............................................13-9
Table 13-5 Related commands for configuring the MTP link............................................................................13-9
Table 13-6 Data Collection Table....................................................................................................................13-10
Table 14-1 M2UA data collection table.............................................................................................................14-7
Table 14-2 Steps for configuring M2UA data....................................................................................................14-8
Table 14-3 Reference list....................................................................................................................................14-9
Table 14-4 Related commands for configuring the M2UA link set.................................................................14-11
Table 14-5 Related commands for configuring the M2UA link......................................................................14-14
Table 14-6 Related commands for configuring the MTP link..........................................................................14-17
Table 14-7 M2UA data collection table...........................................................................................................14-17
Table 15-1 IUA data collection table.................................................................................................................15-6
Table 15-2 Steps for configuring the IUA data..................................................................................................15-7
Table 15-3 Related commands for adding the board........................................................................................15-11
Table 15-4 Related commands for configuring the local IP address combination...........................................15-12
Table 15-5 Related commands for configuring the extended remote IP address combination........................15-13
Table 15-6 Related commands for configuring the extended access control information...............................15-13
Table 15-7 Related commands for adding the IUA link set.............................................................................15-14
Table 15-8 Related commands for adding the IUA link set.............................................................................15-16
Table 15-9 Related commands for adding the IUA link..................................................................................15-19
Table 15-10 IUA data collection table.............................................................................................................15-20

xx Huawei Proprietary and Confidential Issue 02 (2009-12-14)

1 Description of Data Configuration

About This Chapter

This chapter describes the general steps for configuring SG7000 data, principles and precautions.
The hardware data and local data must be configured first as they help in configuring other data.
Configure protocol data (including narrowband protocol data and broadband protocol data)
according to actual networking applications. Do not perform the protocol configuration steps
which are not involved. Figure 1-1 lists the procedures of the SG7000 data configuration.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 1-1

Figure 1-1 Procedures of the SG7000 data configuration

1.1 Data Configuration Procedures

This section describes the configuration procedure and the contents to be configured.
1.2 General Principles
The SG7000 uses SQL Server as the database software for the Back Administration Module
(BAM). When data is configured in the SG7000, the data validity check is performed for the
database security. Therefore, you must add or delete data in a certain sequence.
1.3 Guide to Using MML
Configure and set the data with the local maintenance terminal (LMT). For the usage of MML
terminal, see the U-SYS SG7000 Operation Manual - Terminal Guide.
1.4 Operation of Database
This section describes the database operations, including online mode setting, format conversion,
consistency check, and database backup.

1-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

1.1 Data Configuration Procedures

This section describes the configuration procedure and the contents to be configured.

There are two types of data to be configured in the SG7000:

l During the deployment, you must configure the global data of the SG7000 because the
database is empty.
l During operation, modify certain network environment data when, for instance, you add a
network element or modify link data.
1.1.1 Overview
The SG7000 data configuration consists of the hardware data, local office data, and protocol
data configuration. The hardware data and local data must be configured first as they help in
configuring other data. Configure protocol data according to actual networking applications. Do
not perform the protocol configuration steps which are not involved.
1.1.2 Configuration Tasks
In actual application, the contents configured in each step may be different.

1.1.1 Overview
The SG7000 data configuration consists of the hardware data, local office data, and protocol
data configuration. The hardware data and local data must be configured first as they help in
configuring other data. Configure protocol data according to actual networking applications. Do
not perform the protocol configuration steps which are not involved.

Table 1-1 lists the procedures of the SG7000 data configuration.

Table 1-1 Procedures of the SG7000 data configuration

Step Operation

1 2 Configuring Hardware Data

2 3 Configuring Local Office Data

3 4 Configuring MTP Data

4 5 Configuring MTP Shielding Data

5 6 Configuring SCCP Data

6 7 Configuring SCCP Shielding Data

7 8 Configuring SCTP Data

8 9 Configuring SUA Data

8 10 Configuring the SUA Shielding Data

10 11 Configuring M3UA Data

11 12 Configuring M3UA Shielding Data

12 13 Configuring M2PA Data

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 1-3

Step Operation

13 14 Configuring M2UA Data

14 15 Configuring IUA Data

1.1.2 Configuration Tasks

In actual application, the contents configured in each step may be different.

Table 1-2 lists the configuration tasks of each step in Table 1-1.

Table 1-2 Contents of the SG7000 data configuration

Configuration Type Configuration Content

Hardware data configuration Adding work status of the trunk interface board

Adding work status of the clock board

Adding the local IP address

Adding the SG7000 board

Local office data Adding the logical network (optional)

configuration
Adding the local office information

Adding the local office OPC information (optional)

MTP data configuration Setting the alarm threshold (optional)

Setting the congestion threshold (optional)

Setting the timer (optional)

Adding the MTP destination signaling point (DSP)

Adding the MTP link set

Adding the MTP route

Adding the semi-permanent connection

Adding the MTP link

MTP shielding data Adding the initial shielding table

configuration
Adding the link set shielding table

Adding the prohibited OPC table

Adding the prohibited DPC table

Adding the allowed OPC table

Adding the allowed DPC table

1-4 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Configuration Type Configuration Content

Adding the prohibited SIO table

Adding the prohibited TFM table

SCCP data configuration Adding the SCCP subsystem (optional)

Adding the new global title (GT) (optional)

Adding the GT

SCCP shielding data Adding the caller DPCSSN shielding table

configuration
Adding the caller GT shielding table

Adding the caller GT translation type shielding table

Adding the callee DPCSSN shielding table

Adding the caller GT shielding table

Adding the callee GT translation type shielding table

SCTP data configuration Setting the SCTP initialization parameter data (optional)

Setting the SCTP protocol parameter data (optional)

M3UA data configuration Adding the local IP address

Adding the local IP address combination

Adding the remote IP address

Adding the remote IP address combination

Adding the access control information

Adding the M3UA application server data

Adding the M3UA complementary routing data (optional)

Adding the M3UA association set data

Adding the M3UA route data

Adding the M3UA association data

M2PA data configuration Adding the local IP address

Adding the local IP address combination

Adding the remote IP address

Adding the remote IP address combination

Adding the access control information

Setting the alarm threshold (optional)

Setting the congestion threshold (optional)

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 1-5

Configuration Type Configuration Content

Setting the timer (optional)

Adding the DSP

Adding the link set

Adding the route data

Adding the M2PA link

M2UA data configuration Adding the local IP address

Adding the local IP address combination table

Adding the remote IP address

Adding the remote IP address combination table

Adding the access control information

Adding the MTP DSP

Adding the MTP link set

Adding the MTP route

Adding the M2UA link

IUA data configuration Adding the board

Adding the local IP address

Adding the local IP address combination table

Adding the extended remote IP address

Adding the extended remote IP address combination table

Adding the extended access control information

Setting the software configuration parameter

Converting the formats of all data

Setting the board software DIP switch

Adding the IUA link set

Adding the IUA link

1.2 General Principles

The SG7000 uses SQL Server as the database software for the Back Administration Module
(BAM). When data is configured in the SG7000, the data validity check is performed for the
database security. Therefore, you must add or delete data in a certain sequence.

1-6 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Data configuration must follow the principles below:

l The cabinet, frame, and slot numbers of a board should not conflict with each other. The
data describing the same object cannot be configured repeatedly.
l All data should be configured within the corresponding ranges.
l The red parameters of the commands in the assistant command input window are
mandatory.
l Boards or frames configured with links or connections cannot be deleted; and links or
connections without boards or frames cannot be added, either.
l Data of originating point code (OPC), destination point code (DPC), link set or association
set that are being referenced cannot be deleted.

The configuration of the signaling management part includes the following:

l Message transfer part (MTP) management

l Signaling connection control part (SCCP) management
l Stream control transmission protocol (SCTP) management
l No.7 MTP3-user adaptation layer (M3UA) management
l No.7 MTP2-user peer-to-peer adaptation layer (M2PA) management
l No.7 MTP2-user adaptation layer (M2UA) management
l ISDN Q.921-user adaptation layer (IUA) management

They can be configured optionally based on the actual situation. For example, if the SG7000
performs the signaling transfer between two narrowband signaling points (SPs), only the
configuration of the MTP management data is required.

You must note the following during the data configuration:

l Some parameters of signaling management part can be configured only after the negotiation
with the peer end.
l Usually, the default values are adopted for setting the software configuration parameter
(SET SOFTCFG) and the SCTP initialization parameter (SET SCTPINIT). Modify them
carefully to avoid the adverse effect on the system operation.
l When configuring data for the first time, configure the data offline, load the data online
and reload the data through the steps in Table 1-3.

Table 1-3 Configuring data for the first deployment

Command or Step Implication

SET OPMODE: LN=LOFF Setting the mode to offline.

SET CWSON: SWT=OFF Turning off the alarm switch.

Configure data -

SET OPMODE: LN=LON Setting online mode.

SET CWSON: SWT=ON Turning on the alarm switch.

FMT Formatting the data.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 1-7

Command or Step Implication

SET SFTSWT: MODE=ALL, VAL=64; Setting a board soft dial-in-line package

(DIP) switch.

Power off the board and then power it on Power off to load data and then power on.
to load the data

ACT CNSCHK Checking the data consistency.

l Usually, the data is configured online during daily maintenance. Most commands can be
set online but a few commands require loading.
l To learn more about parameters, press F1 to obtain the online help information of
commands.

1.3 Guide to Using MML

Configure and set the data with the local maintenance terminal (LMT). For the usage of MML
terminal, see the U-SYS SG7000 Operation Manual - Terminal Guide.
1.3.1 Description of MML Operation
This section describes the precautions when you perform the MML operations.
1.3.2 Usage of Data Script
Configure the data by loading the script, when you configure the data in the office deployment
for the first time, or when you configure many data.
1.3.3 Common Commands
This section describes the classifications and implications of common commands.

1.3.1 Description of MML Operation

This section describes the precautions when you perform the MML operations.

When performing the MML operations, note the following:

l When the MML terminal is used to set the data, set the data in the offline mode, when you
configure the data in the office deployment for the first time, or when you configure large
volume of data. Run SET OPMODE, and set LN to LOFF. After the data is configured,
run SET OPMODE and set LN to LON to load the data. Data is usually configured online,
and the command prompt will instruct you how to proceed with the configuration.
l When you type a command in the assistant command input window, the parameters in red
are mandatory. The other parameters can remain as default values if they do not conflict
with other configurations.
l To set the data, select the appropriate command in the navigation tree on the operation and
maintenance interface of LMT, and then double click it to display the input window of the
command.
l Press F1 or click Help in the window to learn how to use the command in detail.
l If you are not familiar with the navigation tree, you can type the keyword of the command
in the Search interface to find the command.

1-8 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

1.3.2 Usage of Data Script

Configure the data by loading the script, when you configure the data in the office deployment
for the first time, or when you configure many data.

Preparing the Script

NOTE

You can perform the following steps to prepare the data configuration script on another BAM in advance.

Step 1 Select System > Save input command on the operation and maintenance interface of the LMT
to make the scripts. You can specify the name of file and path to store the scripts.

The script file is a CMD* TXT text file. The "*" stands for the time (year-month-date) when the
command is saved.

For example, CMD-0501251750 stands for the script saved at 2005-01-25 17:50.

Step 2 Then input a command in the assistant command input window to configure the data.

Step 3 Select System > Save on the menu bar after the configuration to save the script.

----End

Using the Script

Step 1 Right-click the .txt script file. Modify the data according to the actual conditions and then save
the file.

Step 2 On the LMT, run SET OPMODE: LN=LOFF to set the data management module to offline
mode.

Step 3 Select System > Execute batch commands and choose the prepared data script in the pop-up
dialog box.

Step 4 Run FMT.

Step 5 On the LMT, run SET OPMODE: LN=LON to set the data management module to online
mode.

Step 6 Power on the board again to load data.

NOTE

If the commands to be processed in batch are few, you can run the batch command without setting the data
management module to offline mode.
When the equipment is working normally, you can add or modify the data in an online mode.

----End

1.3.3 Common Commands

This section describes the classifications and implications of common commands.

Table 1-4 illustrates the implication of common commands.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 1-9

Table 1-4 Implication of the MML command

Command Implication

ADD It is used to add the data.

MOD It is used to modify the data.

RMV It is used to remove the data.

LST It is used to list the data in the BAM database.

DSP It is used to display the data in the host, or the state of relevant equipment
and resources.

SET It is used to set the data or the state.

SET OPMODE It is used to set the online mode.

FMT It is used to convert the data format.

ACT CNSCHK It is used to check the data consistency.

1.4 Operation of Database

This section describes the database operations, including online mode setting, format conversion,
consistency check, and database backup.
1.4.1 Overview of Database
This section describes the classifications of the database and relations among different databases.
1.4.2 Setting Online Mode
This section describes the function of setting online mode, related parameters, and operations.
1.4.3 Converting Format
This command (FMT) is used to convert the format of the data in the BAM database to binary
file, which can be identified by the host. Thus, the data can be loaded to the host. By default,
the converted host data load file is stored under the directory D:\SGDATA on the BAM hard
disk. The file name of the equipment table is of the db_?.STP format, and that of the service
table is of the db_?.SV format.
1.4.4 Checking Consistency
This section describes how to check data consistency by using ACT CNSCHK and compare
host and BAM data files by using CMP TBL.
1.4.5 Backing Up Database
The system backs up the BAM database at 4:30 every morning by default to ensure the BAM
database security. The system performs roll backup mechanism and can back up at most 11
database files.

1.4.1 Overview of Database

This section describes the classifications of the database and relations among different databases.

1-10 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Database Category
The SG7000 database can be categorized as host database and BAM database by the storage
location as follows:
l Host database
The host database is stored on each board of the host. It stores the data which is closely
related to the operation of the host. These boards include HSYS, SBPU/SBPE, and SBPI.
l Background database
The background database is the SQL database stored in the BAM hard disk. It stores the
data which supports the operation of the host. It consists of the BAM database, alarm
database, and traffic measurement database. The BAM database is most related to the host
database because it contains all information about generating the host database.

Relations Between BAM Database and Host Database

The formats of the BAM database and host database are different. Therefore, you can directly
operate the BAM database by using the data configuration command, that is, the MML
command. The "Dataman process" of the BAM server converts the formats of the two databases.
Under normal conditions, when you set the data online on the operation maintenance client, the
BAM does the following operations if you add, modify, or delete the data.
1. The "Dataman process" of the BAM server updates the BAM database in real time.
2. The "Dataman process" of the BAM server converts the format of the set data and refreshes
the corresponding host load data file.
3. The "Exchange process" of the BAM server sends the new data to the host.

1.4.2 Setting Online Mode

This section describes the function of setting online mode, related parameters, and operations.

Function
The command to set the online mode is SET OPMODE. It determines whether to set the data in
online or offline mode on the clients (including the general workstation, the emergency
workstation, and the BAM) of the SG7000 terminal system. When the BAM is reset, the system
sets the data online by default.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 1-11

Parameter
Paramete Paramete Parameter Description
r ID r Name

LN LN There are three options for the online mode:

l LOFF: It means setting the data offline. If you set the online
mode to offline when modifying the BAM database on any
client, only the "Dataman process" of the BAM server converts
the format of the data, but the "Exchange process" does not send
the data to the host. In that case, the information of the BAM
database is inconsistent with that of the host database. That is,
the modification of the BAM database is not synchronized with
that of the host database.
l LON: It means setting the data online. If you set the mode to
online, when modifying the BAM database on any client, the
"Dataman process" of the BAM server first converts the format
of the data in real time, and then the "Exchange process" sends
the data to the host. Under this condition, the information of the
BAM database is consistent with that of the host database. That
is, the modification of the BAM database is synchronized with
that of the host database.
Generally, data setting in offline mode is used for data
configuration in deployment or system expansion for the
purpose of saving configuration time. After the data setting is
completed, the information in the BAM database is inconsistent
with that in the host database. In this case, you must reload the
data to complete the synchronization.
l PERM: It means permanent online. When the data is configured,
the database is processed in the same way as that under the LON
mode.

Operation Example
Enter the online mode.
SET OPMODE: LN=LON;

1.4.3 Converting Format

This command (FMT) is used to convert the format of the data in the BAM database to binary
file, which can be identified by the host. Thus, the data can be loaded to the host. By default,
the converted host data load file is stored under the directory D:\SGDATA on the BAM hard
disk. The file name of the equipment table is of the db_?.STP format, and that of the service
table is of the db_?.SV format.

Function
After setting the data offline, you must format all the data with the command FMT and load the
data to the corresponding board in the host.

1-12 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Parameter
None.

Operation Example
Convert data format.
FMT:;

1.4.4 Checking Consistency

This section describes how to check data consistency by using ACT CNSCHK and compare
host and BAM data files by using CMP TBL.

Checking Data Consistency by Using ACT CNSCHK

This command is used to check whether the equipment data in the BAM database is in accordance
with that in the host database. The result only shows whether they are the same. Compare data
tables by using the command CMP TBL.
Data consistency includes the following:
l The Flash data on the active HSYS is consistent with the BAM data.
l The Flash data on the active HSYS is consistent with that on other boards.
l The Flash data on every board is consistent with the static data on the board.
l The static data on every board is consistent with the dynamic data on the board.

The equipment data in the host is classified into the backup data, static data, and dynamic data:
l The backup data is stored in the FLASH memory of a board and it is loaded by loading
module when the board is started, so backup data is also called FLASH data.
l The static data is generated based on the backup data during the data management
initialization and it is stored in the memory.
l The dynamic data is generated based on the static data after the data management
initialization and it adopts the structure defined by its own protocol and service module.
For data inconsistency, proceed as follows:
1. Inconsistency between the HSYS and BAM: You can run RST DBTBL to restore the data;
otherwise, you must re-load all boards.
2. Inconsistency between the HSYS and other boards: You can run RST TBL to restore the
data; otherwise, you must re-load this board.
3. Inconsistency between the active HSYS and standby HSYS: You can re-load the HSYS.
4. You can restore data only by re-loading.

Parameter Description of ACT CNSCHK

None.

Operation Examples of ACT CNSCHK

Check the consistency of all equipment data tables.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 1-13

ACT CNSCHK:;

Comparing Files in Foreground with that in Background by Using CMP TBL

The command is used to check whether the information of the BAM database is consistent with
that of the host database. It can locate the error of the data table level. This command can provide
more information than ACT CNSCHK.

Parameter Description of CMP TBL

Paramete Paramete Parameter Description
r ID r Name

TBLID Table ID It specifies the ID of the data table to be compared between the
host and the BAM. It is mandatory.

Operation Examples of CMP TBL

Compare the MTP link table of the foreground with that of the background. The table ID of the
MTP link table is 3.
CMP TBL: TBLID=3;

1.4.5 Backing Up Database

The system backs up the BAM database at 4:30 every morning by default to ensure the BAM
database security. The system performs roll backup mechanism and can back up at most 11
database files.

Function
The BAM database backup file includes the following:

l The default storage directory: E:\MSSQL\SGDATA

l Save the database backup files of continuous seven days before the current day (including
the current day but excluding Sunday). The format of the name of the six files is
BamYYYYMMDD.dat.
l Save the database backup files of four Sundays within the past 28 days. The format of the
name of the four files is BamYYYYMMDD.dat.
l Save a BAM database backup file at the first day of each month. The format of the name
of the file is BamMonthBak.dat.
NOTE

l The host load data file is under the directory of D:\SGDATA on the BAM hard disk. The format of
the name of the file is db_? .STP, db_?.SV, or db_?$. STP. db_?$. SV. And the db_?$. SV. db_?$. SV
are the compressed file of the corresponding db_?$. STP. db_?$. SV.
l To decrease the communication flow between the BAM and the host, and to increase the loading speed,
save all the load data files sent from the BAM to the host by internal Ethernet in the format db_?$.STP
or db_?.SV.

After you run the command, a BAM database file with the name format
BamYYYYMMDD.dat and a BAM registry file with the name format BamReg.bak are auto

1-14 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

generated under the directory E:\MSSQL\SGDATA on the BAM hard disk. The two files
restore the BAM database when it fails.

Parameter
None.

Operation Example
Back up the BAM database and registry.
BKP DB:;

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 1-15

2 Configuring Hardware Data

About This Chapter

Hardware data is part of the basic data of the SG7000. It defines the physical hardware, physical
port and relevant information of the SG7000. This chapter tells the concept and steps of
configuring the hardware data of the SG7000.
To configure the SG7000 data, follow the procedure as shown in Figure 2-1. In this way, the
key fields are defined before they are referenced by other data tables and no junk data is
generated.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 2-1

Figure 2-1 Data configuration procedure

2.1 Configuration Preparations

This section describes the background information, configuration principles, and configuration
steps to be studied before hardware data configuration.
2.2 Configuring Board Data
Configuring board data includes configuring the trunk interface board working status,
configuring the clock board working status, adding the local IP address, and adding boards.
2.3 Loading Hardware Data
After the hardware data is configured in offline mode, you must load the data to the host.
2.4 Configuration Examples
This section provides examples to describe how to configure the hardware data.

2-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

2.1 Configuration Preparations

This section describes the background information, configuration principles, and configuration
steps to be studied before hardware data configuration.
2.1.1 OSTA 16IP Background Information
This section describes the background information of the OSTA 16IP platform, including the
cabinet number, frame number, and slot number.
2.1.2 Relation Between Data Tables
This section describes the relations between data tables related to hardware data configuration.
2.1.3 Data Collection
Before data configuration, you must prepare the basic hardware information of the SG7000.
2.1.4 Configuration Principles
Before configuring hardware data, you must learn configuration principles to avoid error.
2.1.5 General Steps
You must follow certain procedures to configure the hardware data.

2.1.1 OSTA 16IP Background Information

This section describes the background information of the OSTA 16IP platform, including the
cabinet number, frame number, and slot number.

Cabinet Number
On the 16IP platform, the SG7000 can be installed with up to five cabinets numbered from 0 to
4.
Main control cabinet must be configured and its number is always 0. Expansion cabinets can be
configured according to different conditions of networking and capacity, and numbered serially
(from left to right or from right to left). See Figure 2-2.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 2-3

Figure 2-2 Full configuration of the SG7000 16IP cabinets

Frame Number
Each frame is allocated with the following two numbers:
l Physical frame number: a number allocated within the cabinet
l Logical frame number: a number allocated in the whole system
NOTE

The parameter Frame number in the command ADD BRD is a physical number rather than a logical
number.

The system supports up to 16 frames. The numbering principle of the physical number is as
follows.

2-4 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

The frames in a cabinet are numbered from 0 from bottom to top. The main control cabinet can
hold two frames, of which the main control frame is always numbered 0. Expansion cabinets
1-3 can hold four frames respectively and the frames are numbered 0, 1, 2 and 3 from bottom
to top. Expansion cabinet 4 can hold up to two frames and the frames are numbered 0 and 1 from
bottom to top. See Figure 2-2.

The logical number of frame is set by the 8-bit DIP switch S3 on the high-level system board
back interface unit (HBIU) boards, which are the back boards inserted in slot 6 and slot 8. You
must set the same frame number for slots 6 and 8 in the same frame.

Table 2-1 shows the logical frame numbers set by the HBIU DIP switch S3.

Table 2-1 Relationship between switch bit and logical frame number

Frame DIP Switch Bit

Numb
er 1 2 3 4 5 6 7 8

0 ON ON ON ON ON ON ON ON

1 OFF ON ON ON ON ON ON ON

2 ON OFF ON ON ON ON ON ON

3 OFF OFF ON ON ON ON ON ON

4 ON ON OFF ON ON ON ON ON

5 OFF ON OFF ON ON ON ON ON

6 ON OFF OFF ON ON ON ON ON

7 OFF OFF OFF ON ON ON ON ON

8 ON ON ON OFF ON ON ON ON

9 OFF ON ON OFF ON ON ON ON

10 ON OFF ON OFF ON ON ON ON

11 OFF OFF ON OFF ON ON ON ON

12 ON ON OFF OFF ON ON ON ON

13 OFF ON OFF OFF ON ON ON ON

14 ON OFF OFF OFF ON ON ON ON

15 OFF OFF OFF OFF ON ON ON ON

Note: "ON" stands for 0; "OFF" stands for 1.

Slot Number
The frame of the SG7000 can be inserted with front boards and back boards. The front boards
are numbered 0-20 from left to right, and the corresponding back boards are numbered 0-20
from right to left, so there are 21 pairs of slots in all.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 2-5

An SG7000 board has its own place in a frame. Figure 2-3 shows the arrangement of boards in
the main control frame.

Figure 2-3 Board configuration in main control frame

Figure 2-4 shows the boards in the service frame.

Figure 2-4 Board configuration in service frame

Clock Scheme
For the clock scheme of the SG7000, see the U-SYS SG7000 Operation Manual - System
Principle.

2.1.2 Relation Between Data Tables

This section describes the relations between data tables related to hardware data configuration.
Figure 2-5 shows the relationship between parameters in hardware data. The parameter Board
property indicator of ADD BRD is indexed from Index number of ADD TRUNKSTAT,

2-6 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

ADD CKISTAT and ADD LIP. The index numbers of the three commands are allocated by
system after the ADD commands are executed.
Before configuring the signaling E1 peripheral interface unit (SEPU), clock interface unit (CKII)
and signaling broadband processing interface (SBPI), pay attention to the following:
l Before adding the SEPU, configure the state of trunk interface board with ADD
TRUNKSTAT to obtain Board property indicator.
l Before adding the CKII, configure the state of clock board with ADD CKISTAT to obtain
Board property indicator.
l Before adding the SBPI, configure the local IP address with ADD LIP to obtain Board
property indicator.
l Add other types of boards with ADD BRD directly.

Figure 2-5 Parameters relationship of hardware data configuration commands

2.1.3 Data Collection

Before data configuration, you must prepare the basic hardware information of the SG7000.
Before configuring the hardware data of the SG7000, you need to collect the data as listed in
Table 2-2.

Table 2-2 Hardware data collection table

Cabinet number Frame number Frame type

Clock reference Providing trunk board slot of Providing E1/T1 port of the
source of the CKII the CKII clock source CKII clock source

Local IP address Subnet mask Default gateway

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 2-7

Confirming Board Type

l The high-level system unit (HSYS), HBIU, hot swappable control unit (HSCU), alarm unit
interface (ALUI), universal power (UPWR), and signaling broadband processing unit
(SBPU)/broadband signaling processing enhanced unit (SBPE) are the boards that must be
configured in each frame.
l The CKII is only configured in the main service frame, but not the slave service frame.
l The signaling link processing unit (SLPU) and the signaling high level link processing unit
(SHPU) are the subboards on the SBPU for processing MTP links. The signaling high level
link processing enhanced unit (SHPE), signaling link processing unit (SLPU), and signaling
high level link processing unit (SHPU) are the subboards on the SBPE for processing MTP
links. They can be divided into the SHPE, SLPU-64K, SLPU-2M, SHPU-64K and
SHPU-2M by processing ability. Select one or more according to actual conditions.
l Configure the SBPI when necessary. To support broadband links, the SBPI must be
configured.
l The versatile interface extension unit B (VIEB) is the back board of the SBPI, and they are
configured in pairs.

Confirming Board Number

l Configure two HSYSs, two HBIUs and two HSCUs for each frame, and they work in active/
standby mode.
l Configure one ALUI for each frame.
l Configure four UPWRs for each frame, two in the front and two in the back, and they work
in active/standby mode.
l Configure two CKIIs for the main service frame, and they work in active/standby mode.
l The number of SBPUs/SBPEs depends on actual networking and capacity. The main
control frame can hold at most nine SBPUs/SBPEs and the slave frames can hold at most
12 SBPUs/SBPEs.
l Configure the SBPIs in pairs for each frame and they work in load sharing mode. The
number of boards depends on actual network and capacity.
l The number of SEPUs must be consistent with that of SBPUs/SBPEs. The number of VIEBs
must be consistent with that of SBPIs.

Confirming Local IP Address

If the SG7000 is configured with the SBPI, the IP address, subnet mask and default gateway of
the FE interface must be configured. If no SBPI is configured, such parameters are not needed.

2.1.4 Configuration Principles

Before configuring hardware data, you must learn configuration principles to avoid error.

l Configure all types of boards according to the corresponding relationship between boards
and slots in Figure 2-3 (main service frame) and Figure 2-4 (slave service frame).
l Configure subboards (SLPU or SHPU) of the same type on the same SBPU. If two SLPUs
or SHPUs are configured, one can be the SLPU/SHPU-2M and the other one can be the
SLPU/SHPU-64K.

2-8 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

l You can configure subboards (SLPU, SHPU, or SHPE) of the same type on the same SBPU,
or one SHPU and one SHPE on the same SBPU. If two SLPUs or SHPUs are configured,
one can be the SLPU/SHPU-2M and the other one can be the SLPU/SHPU-64K.
l The SBPIs are configured in slots 5 and 10 in pairs, and they work in active/stand or load
sharing mode. The load sharing mode is recommended. The SBPIs can also be configured
in other symmetrical slots by taking slots 6 - 9 as the core, such as slots 5 and 10, slots 4
and 11 and slots 3 and 12. If only one SBPI is configured, neither of the front slot and back
slot of its symmetrical slot can be configured with other boards, such as SBPU and SEPU.
l If the clock source of the CKII is the line clock on the SEPU, it is recommended that the
two line clocks on the same CKII are from the SEPUs connecting different office directions
to achieve the backup of line 1 and line 2. If the clock source of the CKII is on the BITS,
it is recommended that the two BITS clocks on the same CKII are from different BITSs to
achieve the backup of BITS1 and BITS2.
l No configuration is needed for HBIU, HSCU, VIEB and UPWR. They can be put into use
after being powered on.

2.1.5 General Steps

You must follow certain procedures to configure the hardware data.
The steps and commands for configuring hardware data are as shown in Table 2-3.

Table 2-3 Steps of configuring hardware data

Step Operation

1 To add TRUNK work status (ADD TRUNKSTAT)

2 To add CKII work status (ADD CKISTAT)

3 To add local IP address (ADD LIP)

4 To add the board (ADD BRD)

2.2 Configuring Board Data

Configuring board data includes configuring the trunk interface board working status,
configuring the clock board working status, adding the local IP address, and adding boards.
2.2.1 Configuring Trunk Interface Board Work Status
If a record of the SEPU work status is added, the system allocates an index value for it. The
index maps the value of Board property indicator in ADD BRD used to add the SEPU, that
is, parameters of ADD BRD describe the physical position of the SEPU, parameters of ADD
TRUNKSTAT describe its work status, and Board property indicator of ADD BRD correlates
the two commands.
2.2.2 Configuring Clock Board Work Status
If a record of CKII work status is added, the system will allocate an idle index value for it. The
index value corresponds to the value of Board property indicator in ADD BRD used to add
the CKII. That is parameters of ADD BRD describe the physical position of CKII, parameters
of ADD CKISTAT describe its work status, and Board property indicator correlates the two
commands.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 2-9

2.2.3 Adding Local IP Address

When a record of local IP address is added, the system will allocate an idle index value for it.
This value will be referenced by Board property indicator in ADD BRD used to add the SBPI
to allocate an IP address for the FE interface on the SBPI.
2.2.4 Adding Board
When adding boards, the sequences vary depending on board types. You must exactly follow
the board adding procedure.

2.2.1 Configuring Trunk Interface Board Work Status

If a record of the SEPU work status is added, the system allocates an index value for it. The
index maps the value of Board property indicator in ADD BRD used to add the SEPU, that
is, parameters of ADD BRD describe the physical position of the SEPU, parameters of ADD
TRUNKSTAT describe its work status, and Board property indicator of ADD BRD correlates
the two commands.

Command
ADD TRUNKSTAT

Parameter
Paramete Paramete Parameter Description
r ID r Name

BT Board It is mandatory. Its value is of the enumeration type. It can be set

type to:
l EI (EPII board)
l EU (SEPU board)
It must be configured based on actual conditions.

LT Link type It is optional. Its value is of the enumeration type. It is valid only
when BT is set to EU.
It can be set to:
l E1 (E1 link)
l T1 (T1 link)
It must be configured based on actual conditions.

2-10 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Paramete Paramete Parameter Description

r ID r Name

CH110 TDM chip It specifies which clock source is chosen for the TDM chip, that
clock is, for the trunk board (the TDM chip is on the trunk board).
source It is mandatory and its value is of enumeration type. It can be set
selection to:
l LB (Crystal oscillation of the board): The clock is provided by
the board itself through free-run oscillation.
l CK1 (Clock 1 of CKII board): The clock is extracted from the
active CKII.
l CK0 (Clock 0 of CKII board): The clock is extracted from the
standby CKII.
Follow the principles below when choosing the clock source for
the TDM chip:
l Choose LB for all trunk boards in the main control frame.
l Choose CK1/CK0 for the boards connecting with 8 KHz clock
cables in the expansion service frames.
l Choose LB for all other trunk boards in the expansion service
frames.

CL2M 2M clock It specifies the number of the trunk link on which the clock signals
output are exported from the trunk board to the CKII. This parameter is
reference valid only when BT is set to EI.
source This parameter is optional and its value is of the enumeration type.
It is used to select an E1 port, through which the EPII sends the
clock signal to the CKII. The range P0-P7 stands for the E1 port
numbered 0-7 in the EPII. NONE means the port is not configured.
NOTE
The SEPU configures the clock signal output reference source through the
hardware DIP switch. Therefore, when the SEPU is selected, the parameter
is not needed. For the description of the DIP switch of the SEPU, see the
U-SYS SG7000 Hardware Description Manual.

EP0-EP15 Configura It is used to configure the frame format of the E1 port. Parameters
tion of EP0-EP7 are mandatory and EP8-EP15 are optional.
port 0-15 Parameters EP8-EP15 are valid only when BT is set to EU.
The value of the parameter is of enumeration type. It can be set to:
l DF (DOUBLE FRAME format)
l C4 (CRC4 format)
l SF (superframe format)
l ESF (extended superframe format)
l NONE (no configuration)
Make sure that the port frame format in the local office is the same
as that in the peer office.
To the EPII, EP0-EP7 are mandatory. To the SEPU, EP0-EP15 are
mandatory.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 2-11

Paramete Paramete Parameter Description

r ID r Name

CM Balanced Configure the E1 balanced mode with this parameter when the EPII
mode is selected. The E1 balanced mode is determined by the DIP switch
S1 on the EPII. When all the eight switches of S1 are set to ON, it
means connecting with 75-ohm coaxial cable; when they are all set
to OFF, it means connecting with 120-ohm twisted pair. There are
two options.
l BM (balanced mode, connecting with 120-ohm E1 cable)
l UBM (unbalanced mode, connecting with 75-ohm E1 cable)
The parameter configuration is consistent with the DIP switch on
the EPII.
The E1 balanced mode of the SEPU is determined by the DIP
switch on the board. For the description of the DIP switch on the
SEPU, see the U-SYS SG7000 Hardware Description Manual.

Related Commands

Table 2-4 Related commands for configuring the trunk interface board working status
Command Function

ADD TRUNKSTAT To add TRUNK work status

RMV TRUNKSTAT To remove TRUNK work status

MOD TRUNKSTAT To modify TRUNK work status

LST TRUNKSTAT To list TRUNK work status

2.2.2 Configuring Clock Board Work Status

If a record of CKII work status is added, the system will allocate an idle index value for it. The
index value corresponds to the value of Board property indicator in ADD BRD used to add
the CKII. That is parameters of ADD BRD describe the physical position of CKII, parameters
of ADD CKISTAT describe its work status, and Board property indicator correlates the two
commands.

Command
ADD CKISTAT

2-12 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Parameter
Paramete Paramete Parameter Description
r ID r Name

SRCG Configure It maps the level of the clock reference source.

the level It is mandatory and its value is of enumeration type. It can be set
of to:
reference
source l L2 (LEVEL 2): Indicating that the reference source is of
stratum-2 clock
l L3 (LEVEL 3): Indicating that the reference source is of
stratum-3 clock

PRI1-4 Configure The reference sources 1, 2, 3 and 4 refer to the clock input ports
the BITS1, BITS2, LINE1 and LINE2 of the CKII.
priority of The priorities can be set to 0-3. When it is set to 0, the priority is
reference the highest, while set to 3, the priority is the lowest. If the reference
sources source is configured with priority, the CKII selects reference
1-4 source from the highest priority to the lowest priority. If the
priorities of two reference sources are the same, the CKII selects
from reference source 1 to reference source 4.

SRCT1-2 Type of The reference sources 1 and 2 refer to clock input ports BITS1 and
reference BITS2 of the CKII. Select the type of reference sources according
sources to actual conditions. It has three options.
1-2 l T2MB (E1, 2 Mbit/s): It is connected to the input BITS
reference source in the 2 Mbit/s mode.
l T2MH (2MHz): It is connected to the input BITS reference
source in the 2 MHz mode.
l NO (NOUSED): It is the default option, which indicates it is
not connected to the BITS reference source.

Related Commands

Table 2-5 Related commands for configuring the clock board working status
Command Function

ADD CKISTAT To add CKII work status

RMV CKISTAT To remove CKII work status

MOD CKISTAT To modify CKII work status

LST CKISTAT To list CKII work status

DSP CKIILOCK To query the phase locking status

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 2-13

2.2.3 Adding Local IP Address

Command
ADD LIP

Parameter
Paramete Paramete Parameter Description
r ID r Name

LN Local IP It refers to the IP address of the FE interface on the SBPI, such as

address of 10.10.10.2. The SBPIs must be configured in pairs in each frame
FE and they work in active/stand or load sharing mode. The load
interface sharing mode is recommended.

MSK IP mask of It is the subnet mask of an FE interface, the input mode is like
FE 255.255.255.0.
interface

DGW Default It is the default gateway of an FE interface, the input mode is like
gateway 10.10.10.1.
of FE
interface

EA Ethernet It is optional. Its value is of the enumeration type. The options are
attribute as follows:
of FE l 0: AUTO (self-adaptation)
interface
l 1: HT (HALF10 M)
l 2: HH (HALF100 M)
l 3: FT (FULL10 M)
l 4: FH (FULL100 M)
It is set to AUTO by default.
It is recommended to configure this parameter to FH or AUTO.
When it is configured to FH or AUTO, the working mode of the
network port of the peer switch must be the same as that of the
local network port.

IFT ICMP It is optional. Its value is of numeral type and ranges 0-65535. It
flow is set to 65535 by default.
threshold

2-14 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Paramete Paramete Parameter Description

r ID r Name

FUNCFL ARP It is optional and its value is of enumeration type. It can be set to:
AG gateway l CLOSE (Close): Indicating that the ARP gateway function is
function disabled
l OPEN (Open): Indicating that the ARP gateway function is
enabled
When it is set to OPEN, the SBPI periodically sends the ARP
request to the ARP gateway. When the ARP gateway does not
respond, the system switches over the SBPIs.
It is set to OPEN by default.

Related Commands

Table 2-6 Related commands for adding the local IP address

Command Function

ADD LIP To add local IP address

RMV LIP To remove local IP address

MOD LIP To modify local IP address

LST LIP To list local IP address

2.2.4 Adding Board

When adding boards, the sequences vary depending on board types. You must exactly follow
the board adding procedure.
It is recommended to proceed as follows:
l Add front boards.
l Add subboards on the front boards (skip this step if there is no subboard).
l Add back boards with the same slot numbers as those of the front boards.

Command
ADD BRD

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 2-15

Parameter
Para Para Parameter Description
met met
er er
ID Na
me

SHN Shel It specifies the shelf number of a board. It is mandatory and its value is of
f numeral type. It can be set to different values based different hardware
num platforms:
ber l As to 16IP platform, it is set to 0-4.
l As to 16T platform, it is set to 0-3.
The main control cabinet is always numbered 0, and other cabinets are
numbered based on their physical positions.

FN Fra It specifies the frame number of a board. It is mandatory and its value is of
me numeral type. It can be set to different values based different hardware
num platforms:
ber l As to 16IP platform, it is set to 0-3.
l As to 16T platform, it is set to 0-1.
The frame number here indicates the number of a frame in a single cabinet.
The frame at the bottom of the cabinet is numbered 0. Frames are numbered
from the bottom to top.

FT Fra It is mandatory and its value is of enumeration type. It can be set to:
me l NULL (Dummy frame)
type
l MAIN (Main service frame)
The following parameters are enabled only when FT is set to MAIN.

SN Slot The range of the slot number is 0-20. Refer to Figure 2-3 and Figure 2-4 for
num the slot configuration of each board in the service frame. It must be configured
ber according to the actual conditions.

2-16 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Para Para Parameter Description

met met
er er
ID Na
me

LOC Loca It is optional and its value is of enumeration type. It can be set to:
tion l FPB (Front board)
l UDB (Upper pinch board)
l DDB (Lower pinch board)
l BPB (Back board)
Select board location according to the type of board when adding a board. The
relationship between board type and location is as shown in Figure 2-3 and
Figure 2-4.
You do not need to configured the data of the HBIU (back boards of the
HSYS), and the data of the VIEB (back boards of the SDUI and SBPI). The
data of the back boards is generated when their corresponding front boards are
added.
In addition, there are 3 types of subboards: SHPE, SHPU and SLPU. The
SBPU can be installed with two SLPUs or two SHPUs. The SBPE can be
installed with two SHPE, two SLPU, or two SHPU. One subboard is pinched
at the upper location of the SBPU/SBPE and the other is pinched at the lower
location of the SBPU/SBPE. You can uniquely determine the location of a
subboard with UDB (Upper pinch board) and DDB (Lower subboard).

BT Boar It specifies the type of the board to be added. It is optional and its value is of
d enumeration type.
type There are following board types: NULL, HSYS, SBPU, SBPE, SBPI,
SLPU64K, SLPU2M, SHPU64K, SHPU2M, SHPE, EPII, CKII, ALUI,
SCBU, SEPU, and SDUI.
Among which, the SLPU64K, SLPU2M, SHPU64K, and SHPU2M can be
used as the subboard of the SBPU. The SLPU64K, SLPU2M, SHPU64K,
SHPU2M, and SHPE can be used as the subboard of the SBPE.
The boards which are not listed here need no configuration. They can be put
into use after being powered on.
Choose the board type based on the actual conditions.
The back board VIEA maps the option SCBU in Board Type.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 2-17

Para Para Parameter Description

met met
er er
ID Na
me

PI Boar It is optional. Its value is of numeral type and ranges 0-65535. It is set to 0 by
d default.
prop It is designed for the SBPI (providing IP ports), SEPU/EPII (providing E1/T1
erty ports), CKII, and SBPU/SBPE.
indic
ator The configuration principles are as follows:
l To add the SBPI, reference the index of the record generated in the
command ADD LIP.
l To add the EPII/SEPU, reference the index of the record generated in the
command ADD TRUNKSTAT.
l To add the CKII, reference the index of the record generated in the
command ADD CKISTAT.
l When you add the SBPU/SBPE, PI=0 indicates that the IUA connects to
the MGC and PI=1 indicates that the IUA connects to the IAD.
l The front slots corresponding to the CKIIs cannot be configured with the
SBPI.

Related Commands

Table 2-7 Related commands for adding the board

Command Function

ADD BRD To add the board

RMV BRD To remove the board

MOD BRD To modify the board

LST BRD To list the board

DSP BRD To query the information of board status

2.3 Loading Hardware Data

After the hardware data is configured in offline mode, you must load the data to the host.
To add hardware data, follow the steps listed in Table 2-8.

2-18 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Table 2-8 Load hardware data

Command or step Function

SET OPMODE: LN=LON It is used to set online mode.

SET CWSON: SWT=ON It is used to turn on the alarm switch.

FMT Format all data.

SET SFTSWT: MODE=ALL Set the board software DIP switch.

Power off the board first and then power it on to -

get it loaded.

ACT CNSCHK It is used to check data consistency.

Check the running status of each board after loading. If the indicators are normal and the
equipment panel on the maintenance console is displayed normally, the hardware data
configuration is finished.

2.4 Configuration Examples

This section provides examples to describe how to configure the hardware data.

OSTA 16IP Board Configuration

NOTE

This section takes the SBPU that is configured as the front board of the SEPU for an example:
l When the front board of the SEPU is SBPU, only the SHPU or SLPU can be installed on the SBPU.
l When the front board of the SEPU is SBPE, the SHPU, SLPU, or SHPE can be configured on the
SBPE.

Configure a main service frame. The board location is as shown in Figure 2-3. Configure two
SHPU subboards on each SBPU, and configure the SEPU as back board.

Clock Configuration
According to the principle of connecting clocks on the CKII, Figure 2-6 shows how to connect
clocks in the main service frame. The SEPU in slots 0 and 1 provide line clock for active and
standby CKII. The CKIIs in slot 13 and 14 are active, and the CKIIs in slot 15 and 16 are standby.
The 2M-A interfaces of the SEPU in slots 0 and 1 output clock to active CKII, and the 2M-B
interfaces of the SEPU in slots 0 and 1 output clock to standby CKII.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 2-19

Figure 2-6 Clock connection

Data Collection Table

Table 2-9 lists the hardware data to be collected.

Table 2-9 Hardware data collection table

Cabinet number Frame number Frame type

0 0 Main service frame

Clock reference source Providing trunk board slot of Providing E1/T1 port of the
of the CKII the CKII clock source CKII clock source

Line clock of the SEPU 0, 1 E1 port 0 in slot 0

E1 port 0 in slot 1

Local IP address Subnet mask Default gateway

10.10.10.2 255.255.0.0 10.10.10.1

Procedure
Step 1 Set the mode to offline.
SET OPMODE: LN=LOFF;

Step 2 Turn off the alarm switch.

SET CWSON: SWT=OFF;

NOTE

By default, the data of the HSYSs in slots 6 and 8, of the ALUI in slot 16 has been configured. If the data
is consistent with the boards configured in the cabinet, use the default data. If not, remove the default data
and configure it again. The following data configuration is conducted in the case that there is no default
data.

Step 3 Add the active and standby HSYSs in slot 6 and slot 8.

2-20 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

ADD BRD: FN=0, SHN=0, FT=MAIN, SN=6, LOC=FPB, BT=HSYS;

ADD BRD: FN=0, SHN=0, FT=MAIN, SN=8, LOC=FPB, BT=HSYS;

Step 4 Add the ALUI in slot 16.

ADD BRD: FN=0, SHN=0, FT=MAIN, SN=16, LOC=FPB, BT=ALUI;

Step 5 Add the SBPU in slots 0-3.

ADD BRD: FN=0, SHN=0, FT=MAIN, SN=0, LOC=FPB, BT=SBPU;
ADD BRD: FN=0, SHN=0, FT=MAIN, SN=1, LOC=FPB, BT=SBPU;
ADD BRD: FN=0, SHN=0, FT=MAIN, SN=2, LOC=FPB, BT=SBPU;
ADD BRD: FN=0, SHN=0, FT=MAIN, SN=3, LOC=FPB, BT=SBPU;

Step 6 Add the upper subboard SLPU-64K and lower subboard SLPU-64K of the SBPU in slots 0-3.
ADD BRD: FN=0, SHN=0, FT=MAIN, SN=0, LOC=UDB, BT=SLPU64K;
ADD BRD: FN=0, SHN=0, FT=MAIN, SN=0, LOC=DDB, BT=SLPU64K;
ADD BRD: FN=0, SHN=0, FT=MAIN, SN=1, LOC=UDB, BT=SLPU64K;
ADD BRD: FN=0, SHN=0, FT=MAIN, SN=1, LOC=DDB, BT=SLPU64K;
ADD BRD: FN=0, SHN=0, FT=MAIN, SN=2, LOC=UDB, BT=SLPU64K;
ADD BRD: FN=0, SHN=0, FT=MAIN, SN=2, LOC=DDB, BT=SLPU64K;
ADD BRD: FN=0, SHN=0, FT=MAIN, SN=3, LOC=UDB, BT=SLPU64K;
ADD BRD: FN=0, SHN=0, FT=MAIN, SN=3, LOC=DDB, BT=SLPU64K;

Step 7 To add the SEPU work status in slots 0-3, set Board type to EI (EPII board), TDM chip clock
source collection to LB (Crystal oscillation of the board), and Configuration of ports 0-15
to DF (Doubleframe format), run the following command:
ADD TRUNKSTAT: BT=EU, LT=E1, CH110=LB, EP0=DF, EP1=DF, EP2=DF, EP3=DF,
EP4=DF, EP5=DF, EP6=DF, EP7=DF, EP8=DF, EP9=DF, EP10=DF, EP11=DF,
EP12=DF, EP13=DF, EP14=DF, EP15=DF;

After the command is carried out, index 0 is obtained.

Step 8 To add SEPUs in slots 0-3, set the SEPU in slots 0 and 1 as the clock source board of the CKII
with hardware DIP switch, and the board property indicator to 0, run the following command:
ADD BRD: FN=0, SHN=0, FT=MAIN, SN=0, LOC=BPB, BT=SEPU, PI=0;
ADD BRD: FN=0, SHN=0, FT=MAIN, SN=1, LOC=BPB, BT=SEPU, PI=0;
ADD BRD: FN=0, SHN=0, FT=MAIN, SN=2, LOC=BPB, BT=SEPU, PI=0;
ADD BRD: FN=0, SHN=0, FT=MAIN, SN=3, LOC=BPB, BT=SEPU, PI=0;

Step 9 To add the CKII work status, set priority of clock sources 1 and 2 to 1, and priority of clock
sources 3 and 4 to 0.
ADD CKISTAT: SRCG=L2, PRI1=1, PRI2=1, PRI3=0, PRI4=0;

After the command is carried out, index 0 is obtained.

Step 10 To add the CKIIs in slots 13 and 14, slots 15 and 16, set the board property indicator to 0, run
the following command:
ADD BRD: FN=0, SHN=0, FT=MAIN, SN=13, LOC=BPB, BT=CKII, PI=0; ADD BRD:
FN=0, SHN=0, FT=MAIN, SN=15, LOC=BPB, BT=CKII, PI=0;

Step 11 To add local IP address, set local IP address to 10.10.10.2, mask to 255.255.0.0, and default
gateway to 10.10.10.1, run the following command:

The local IP address is 10.10.10.2, the subnet mask is 255.255.0.0, and the IP address of the
default gateway is 10.10.10.1.
ADD LIP: LIP="10.10.10.2", MSK="255.255.0.0", DGW="10.10.10.1";

Step 12 Add the SBPIs in slots 5 and 10.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 2-21

ADD BRD: FN=0, SHN=0, FT=MAIN, SN=5, LOC=FPB, BT=SBPI, PI=0;

ADD BRD: FN=0, SHN=0, FT=MAIN, SN=10, LOC=FPB, BT=SBPI, PI=0;

Step 13 Prepare for loading.

Set the mode to online.
SET OPMODE: LN=LON;

Step 14 Turn on the alarm switch.

SET CWSON: SWT=ON;

Step 15 Format all data

FMT:;

Step 16 Set the board software DIP switch

SET SFTSWT: MODE=ALL;

Step 17 Power off the board and then power it on to load the data.

----End

2-22 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

3 Configuring Local Office Data

About This Chapter

The local office data is mainly used to define certain basic information of the SG7000, which
acts as a signaling point (SP) in the SS7 network.
To configure the SG7000 data, follow the procedure as shown in Figure 3-1. In this way, the
key fields are defined before they are referenced by other data tables and no junk data is
generated.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 3-1

Figure 3-1 Data configuration procedure

3.1 Configuration Preparations

This section describes the background information, technical terms, and configuration steps to
be studied before data configuration.
3.2 Configuring Basic Local Office Information
Configuring the basic local office information includes adding the logical network, adding the
local office data, and adding the local OPC information.
3.3 Configuration Examples
This section provides examples to describe how to configure the local office data.

3-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

3.1 Configuration Preparations

This section describes the background information, technical terms, and configuration steps to
be studied before data configuration.
3.1.1 Terms
This section describes the terms used during configuring the local office data.
3.1.2 Relation Between Data Tables
This section describes the relations between data tables related to local office data configuration.
3.1.3 Data Collection
Before configuring the local office information, collect the information as the code of a local
office signaling point, to which signaling network the local office belongs, and whether the local
office supports multiple SPCs.
3.1.4 General Steps
You must follow certain procedures to configure the local office data.

3.1.1 Terms
This section describes the terms used during configuring the local office data.

Signaling Point
In the SS7, the SP includes the origination point code (OPC) and destination point code (DPC)
of the signaling messages. It can be a PSTN switching office, a data switching office, or an ISDN
switching office. It can also be service centers like the network management center, maintenance
center, and service control point (SCP). The OPC generates the signaling messages, while the
DPC receives the signaling messages.

Signaling Point Coding

In the SS7, a signaling point code (SPC) denotes a signaling point, including the signaling
transfer point (STP). The SPC also helps signaling messages select the route in the signaling
network. According to SS7, there are four types of signaling network:

l International network
l International reserved network
l National network
l National reserved network

A signaling point can locate in the four signaling networks and be coded separately.

The SPC can be in 24-bit or 14-bit form, according to the specifications of International
Telecommunications Union (ITU). The coding principles are as follows:

l International network must adopt 14-bit coding.

l The coding mode of the national network is determined by a country's executive telecom
administration. For example, China Ministry of Information Industry prescribes that the
national network of China adopts 24-bit coding.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 3-3

l Coding modes of the international and national reserved networks are decided by the
operators.

Multi-Signaling Points
In the SS7, a physical node can be logically divided into multiple signaling points. Each point
can communicate with other signaling points. The maximum number of signaling links between
two signaling points is 16. Through the mode of multiple signaling points, however, the links
between two signaling points can exceed 16. At the same time, the signaling load can be
balanced.

Function of SCCP
Signaling connection and control part (SCCP) of the SS7 provides additional function for the
MTP. The SCCP and third level of the MTP implements packet switch function of the virtual
circuits and datagram. Through the SS7 network, the circuit-related and non-circuit-related
signaling information and other information can be transferred among switching offices, or
between office and specialized centers (like SCP, network management center). In this case, the
SCCP can establish non-connection and connection-oriented services in the telecom network.

Logical Network
Logical network divides a physical STP into multiple logical STPs, which can serve several
operators at the same time.

3.1.2 Relation Between Data Tables

This section describes the relations between data tables related to local office data configuration.

The index number in ADD LN must be defined before the logical network index in ADD
OPC and the logical network index in SET OFI are referenced. See Figure 3-2 for the parameter
index between local office data commands.

Figure 3-2 Parameter index between local office data commands

ADD OPC

ADD LN [ Logical network index ]

[ Index number] SET OFI

[ Logical network index ]

3.1.3 Data Collection

Before configuring the local office information, collect the information as the code of a local
office signaling point, to which signaling network the local office belongs, and whether the local
office supports multiple SPCs.

3-4 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Table 3-1 Data collection table

Local SP code The signaling network Whether it supports the
the local office belongs to multi SP codes

Whether to provide SCCP Backup SP index Logical network index

function

3.1.4 General Steps

You must follow certain procedures to configure the local office data.
The steps and commands for configuring the local office data are listed in Table 3-2.
If the record of the default logical network is consistent with the actual conditions, you can set
local office data directly. Otherwise, you must add a logical network or modify the logical
network default data. You can then obtain the logical network index number.
If the SG7000 supports multiple SPCs, besides configuring the local office data, you must set
the local office OPC.

Table 3-2 Procedures for configuring local office information

Procedure Operation

1 To add the logic network table (ADD LN) or modify logic network table
(MOD LN) (optional)

2 To set the local office information (SET OFI)

3 To add the local office OPC information (ADD OPC) (optional)

3.2 Configuring Basic Local Office Information

Configuring the basic local office information includes adding the logical network, adding the
local office data, and adding the local OPC information.
3.2.1 Adding Logical Network (Optional)
The logical network defines attributes such as the architecture of the signaling network where
the signaling point is located. An existing default record in the system shows that the index is
0. If the record of the default logical network complies with the actual conditions, the local office
information can be set directly. Otherwise, the logical network default data is modified or a new
logical network is added.
3.2.2 Adding Local Office Information
This section describes the command, parameter, and related commands for configuring the local
office information.
3.2.3 Adding the Local Office OPC Information (Optional)

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 3-5

3.2.1 Adding Logical Network (Optional)

The logical network defines attributes such as the architecture of the signaling network where
the signaling point is located. An existing default record in the system shows that the index is
0. If the record of the default logical network complies with the actual conditions, the local office
information can be set directly. Otherwise, the logical network default data is modified or a new
logical network is added.
After a logical network is added with ADD LN, the system generates an index value. The index
value will be referenced by SET OFI or ADD OPC. It refers to network attributes of the
signaling point or the local office OPC signaling point.

Command
ADD LN

Parameter
Paramete Paramete Parameter Description
r ID r Name

INS Internatio These parameters indicate the length of the local office SPC in
nal signaling networks. Signaling point codes are different in different
network countries and regions. Take China for an example:
architectur l According to ITU-T, the signaling point coding is 14 bits.
e
l It is decided by the operators. To distinguish it from the
IN2S Internatio International Network, it is recommended to set the signaling
nal point coding to 24 bits.
reserved l According to the China Ministry of Information Industry, the
network signaling point coding is 24 bits.
architectur l It is decided by the operators. To distinguish it from the National
e Network, it is recommended to set the signaling point coding to
NNS National 14 bits.
network Note that, an SG7000 can be available in four signaling networks,
architectur but the SPC must follow rules of the different networks.
e

NN2S National
reserved
network
architectur
e

3-6 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Paramete Paramete Parameter Description

r ID r Name

RSF Restart It indicates whether the logical network uses the restart function.
function The parameter is set based on actual conditions of the logical
flag network. For example, the national network of China is
recommended to set the Restart function flag to False.
Signaling point restarting is a sub-function of MTP signaling
service management. Signaling point can be isolated from the
entire signaling network beyond a certain time. In this case, it
cannot decide whether the previous route data remains effective
after recovering. Services transmission recovery may generate
wrong route data. It may cause the missing of some user services.
Signaling point restarting aims to protect the restarted signaling
points and the entire network, so enough restarting time is needed
to activate signaling links and exchange route data. Then services
will be recovered.
The core of the signaling point restarting is exchanges of network
status information between the restarted signaling point and its
adjacency. To ensure validity of the data, the network status must
have no major change during information exchange. In this case,
an entire restarting time must be defined. The entire time can serve
the restarted signaling point and its adjacency. All activities
required for the restart must be implemented within the time limit.

RCT Route The flag indicates whether the logical network needs to use this
congestio function. To prevent problems led by protocols disagreement, it is
n test flag recommended not to adopt route set congestion test.

TFR Transmiss The flag indicates whether the logical network needs to use this
ion function. To prevent problems led by protocols disagreement,
restricted recommend to avoid setting this function.
flag

Related Commands

Table 3-3 Related commands for configuring the logical network

Name Function

ADD LN To add the logic network table

RMV LN To delete the logic network table

MOD LN To modify the logic network table

LST LN To query the logical network information

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 3-7

3.2.2 Adding Local Office Information

This section describes the command, parameter, and related commands for configuring the local
office information.

Command
SET OFI

Parameter
Paramete Paramete Parameter Description
r ID r Name

SN1-4 First Between two local signaling points, there are two or more signaling
searched network connections. The parameters set the sequence to search
network, for signaling networks. The SG7000 can be located in the
Second following four networks at the same time:
searched l International network (IM)
network,
Third l International reserved network (IS)
searched l National network (NM)
network,
l National reserved network (NS)
Fourth
searched Set the network in the sequence as National network, National
network reserved network, International network and International
reserved network for searching. If the sequence is repeated, the
command cannot be executed.

IPC Internatio The parameters indicate the codes of the signaling point in the
nal above four networks. The value range is expressed in the
network hexadecimal number, such as, AAAAAA.
code Unify the codes of the signaling point to a letter in upper or lower
case. Letter in upper case is recommended in this manual.
IP2C Internatio
nal
reserved
network
code

NPC National
network
code

NP2C National
reserved
network
code

3-8 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Paramete Paramete Parameter Description

r ID r Name

RC1-4 Route The four parameters are used when the SG7000 serves as a
context 1, softswitch. No configuration is required in normal networks.
Route The four parameters correspond to the network ID 0-3 respectively.
context 2, For example, if the local signaling point is in the national network,
Route the network ID is 2. In this case, Route context 3 is valid, while
context 3, the other three remain invalid (set to 65535).
Route
context 4

SCCP SCCP The function indicates whether the SG7000 uses the SCCP
function function. Set this parameter based on the actual conditions.

RPX Backup If the SCCP function is used, the parameter is the substitute
signaling signaling point index in the DSP table. If no substitute signaling
point point is needed, it is set to 65535.
index

LNI Logical The index is generated after running ADD LN.

network The value range is 0-127, and by default it is set to 0.
index
Specify the logical network index based on the network attributes
of the signaling point.

Related Commands

Table 3-4 Related commands for configuring the local office information
Name Function

SET OFI To set the local office information

LST OFI To query the local office information

3.2.3 Adding the Local Office OPC Information (Optional)

If the SG7000 has multiple signaling point codes, the main signaling point code is configured
by SET OFI when configuring the local office information. Other signaling point codes are
configured by ADD OPC.
If the SG7000 has only one signaling point code, the local office OPC information is not required.

Command
ADD OPC

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 3-9

Parameter
Paramete Paramete Parameter Description
r ID r Name

IPC Internatio These parameters indicate the codes of the signaling point in the
nal above four networks. The value range is expressed in the
network hexadecimal number, such as, AAAAAA.
code Unify the codes of the signaling point to a letter in upper or lower
case. Letter in upper case is recommended in this manual.
IP2C Internatio
nal
reserved
network
code

NPC National
network
code

NP2C National
reserved
network
code

LNI Logical The index is generated after running ADD LN.

network The value range is 0-127, and by default it is set to 0.
index
Specify the logical network index based on the network attributes
of the signaling point.

Related Commands

Table 3-5 Related commands for configuring the local office OPC information
Name Function

ADD OPC To add the local office OPC information

RMV OPC To remove the local office OPC information

MOD OPC To modify the local office OPC information

LST OPC To query the local office OPC information

3.3 Configuration Examples

This section provides examples to describe how to configure the local office data.

Assumption
The collection of local office information is listed in Table 3-6.

3-10 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Table 3-6 Data collection table

Local SP code The signaling network Whether it supports the
the local office belongs to multi SP codes

A1111A National (NM) No

Whether to provide SCCP Backup SP index Logical network index

function

No None 0

Procedure
Step 1 Run LST LN to query the default logical network record. The result corresponds to the actual
conditions of the signaling point.
LST LN: IDX=0;

The query result is as follows:

Logical network table information

INDEX = 0
DESCRIPTION = NULL
INTERNATIONAL NETWORK STRUCTURE = NOT USED
INTERNATIONAL RESERVED NETWORK STRUCTURE = NOT USED
NATIONAL NETWORK STRUCTURE = 24 BIT
NATIONAL RESERVED NETWORK STRUCTURE = NOT USED
RESTART FUNCTION FLAG = TRUE
ROUTE CONGESTION TEST FLAG = FALSE
TRANSMISSION RESTRICTED FLAG = FALSE

--- END

Step 2 To add the local office information, set National network signaling point code to A1111A,
SCCP to FALSE, and keep the default value of the Logical network index as 0. Now, run the
following command:
SET OFI: SN1=NM, SN2=NS, SN3=IM, SN4=IS, NPC="A1111A", SCCP=FALSE;

After the command is carried out, the local office signaling point index 0 is obtained.

----End

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 3-11

4 Configuring MTP Data

About This Chapter

This chapter describes how to configure the data when the SG interworks with the STP or local
switch (LS) over the MTP3. Before configuring the MTP3 data on the SG, make sure that the
hardware data and local office data are configured.
To configure the SG7000 data, follow the procedure as shown in Figure 4-1. In this way, the
key fields are defined before they are referenced by other data tables and no junk data is
generated.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-1

Figure 4-1 Data configuration procedure

4.1 Configuration Preparations

This section describes the background information, technical terms, and configuration steps to
be studied before data configuration.
4.2 Configuring MTP Data
Configuring the MTP data includes adding the MTP DSP, adding the MTP link set, and adding
the MTP route.
4.3 Configuration Examples
This section provides examples to describe how to configure the MTP data.

4-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

4.1 Configuration Preparations

This section describes the background information, technical terms, and configuration steps to
be studied before data configuration.
4.1.1 Terms
This section describes the terms used during configuring the MTP data.
4.1.2 Networking Structure
This section describes the networking structure for configuring the MTP data.
4.1.3 Relation Between Data Tables
This section describes the relations between data tables related to MTP data configuration.
4.1.4 Data Collection
Before configuring the MTP data, you must collect the data including the local SPC, DPC, and
DSP type.
4.1.5 Configuration Principles
This section describes the principles to be followed when you configure the MTP data.
4.1.6 General Steps
You must follow certain procedures to configure the MTP data.

4.1.1 Terms
This section describes the terms used during configuring the MTP data.

Signaling System Number 7 (SS7)

The International Telegraph and Telephone Consultative Committee (CCITT) 1988 Blue Book
Recommendation Q.700 provides the basic structure of the Signaling System No.7 (SS7). The
entire signaling system is composed of the following functional levels:
l Message Transfer Part (MTP)
l Signaling Connection Control Part (SCCP)
l Telephone User Part (TUP)
l ISDN User Part (ISUP)
l Transaction Capabilities Application Part (TCAP)

Figure 4-2 shows the architecture of the SS7 and the functional relationship between the various
functional blocks of the SS7 and the Open Systems Interconnection (OSI) reference model
layers.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-3

Figure 4-2 SS7 structure

Users of SS7

OSI layers

7 TCAP
ISDN
User Part Telephone
6 Transcation (ISUP) User Part
5 (TUP) 4
Capabilities(TC)
4
Siginaling Connection
Control Part
(SCCP)Level4 Level4 Level4
3
Other MTP
users
M Level 3 Signaling network functions
3
T
Level 2 Signaling link functions 2
1 P 1
Level 1 Signaling data link functions

Other SS7 signaling

nodes

As illustrated in Figure 4-2, the relationship is as follows:

l MTP level 1 functions as the OSI layer 1 (physical layer).
l MTP level 2 functions as the OSI layer 2 (data link layer).
l MTP level 3 along with the SCCP function as the OSI layer 3 (network layer).
l TC functions as the OSI layers 4 to 6 (transport layer, session layer, and presentation layer).
l TCAP implements partial function of OSI layer 7.
l TC user implements the other functions of OSI layer 7.
NOTE

When the SS7 is used in the SG, only the configuration of the MTP3 protocol data (referred to as the MTP
data in this document) and SCCP data is required. See 6 Configuring SCCP Data for details.

Adjacent/Non-Adjacent Destination Signaling Point (DSP)

Based on the location attribute of the local office signaling point and destination signaling point
(DSP) in the SS7 network, the DSP can be divided into adjacent DSP and non-adjacent DSP. If
there is a straight signaling link between two signaling points, these two signaling points are
adjacent DSPs, as SP1 and SP2 shown in Figure 4-3. If there is no straight signaling link, but
two or more than two series signaling links between two signaling points, these signaling points
form the non-adjacent DSPs (SP1 and SP2) as shown in Figure 4-4.

4-4 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Figure 4-3 Adjacent signaling point

SP: signaling point

Figure 4-4 Non-adjacent signaling point

STP: signaling transfer point

Signaling Transfer Point (STP)

The STP performs the signaling transfer. It is a signaling point that transfers a signaling message
from one signaling link to another, as shown in Figure 4-4.

Signaling Link
Signaling links include the signaling data link to connect two SPs (or STPs) and the transmission
tool with the transmission and control function. Each running signaling link is assigned with a
signaling data link and two signaling terminals at both ends of the signaling data link, as shown
in Figure 4-3 and Figure 4-4.

Signaling Link Code (SLC)

The SLC specifies the logical number of a signaling link in a signaling link set. This logical
number is a No.7 signaling protocol number. To facilitate two parties connected by the signaling
link to manage the signaling link, all the signaling links in a signaling link set must be numbered.
The SLCs of the same signaling link are the same at both ends of the signaling link, with values
ranging from 0 to 15. This number can uniquely identify a signaling link in a signaling link set.

Signaling Link Set

The MTP signaling link set refers to all links between two adjacent signaling points.

Signaling Route
In the SS7, signaling route refers to the local direction for signaling transmission. That is, a
signaling message can be transmitted from the local signaling point (SP) to the designated DSP

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-5

through a specified link set. It is irrelevant to the subsequent channel of message transmission,
which is determined by the subsequent SP.

Signaling Link Selection Code (SLS)

The routing function of the user message (that is, a link set) is implemented with the help of the
message flag in the message signaling unit. This is the message routing function of the MTP
layer-3. A 4-bit signaling link selection code (SLS) exists in the message flag. In the TUP
message, the SLS is the last four bits of circuit identification code (CIC). In the ISUP message,
the SLS is a sole field. The 4-bit code of the SLS can indicate 16 types of codes, that is,
0000-1111. The first bit from the right side is the least significant bit, and the first bit from the
left side is the most significant bit of the SLS.
Route selection and link selection are based on the SLS. The SLS varies with the calls, so the
route and the link used by the signaling unit also vary, thus implementing the load sharing on
the signaling links.

Route Selection Field

Route selection field selects the route among multiple signaling routes. The value of the route
selection field should be an 8-bit binary code. Through the algorithm with the SLS, the route
selection field determines the group of links that should be used by a signaling unit. The value
1 of the route selection field indicates the corresponding bit of the SLS to be reserved, and the
value 0 indicates the corresponding bit of the SLS to be masked.
The steps of algorithm are as follows:
l AND the SLS and last four bits of the route selection field to get A;
l Add A to the first four bits of the route selection field to get B;
l Divide B by the total route number to obtain the remainder. If B is less than the total route
number, the reminder is B.
For example:
If the value of the route selection field is 17 (0001, 0001), SLS is 0001, and there are two routes
between adjacent SPs, calculate the route selection in the following way:

4-6 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Here, A = 1, and the first four bits of the route selection field are also 1. So B = 2. The route
number is 2, and the reminder is obtained by 2%2. Thus, the route number obtained is 0.

Link Selection Field

Link selection field is used to select different links in a link set. The value of link selection field
should be a 4-bit binary code. The value 1 of the link selection field indicates the corresponding
bit of the SLS to be reserved, and the value 0 indicates the corresponding bit of the SLS to be
masked. Perform an "AND" operation to the SLS and the mask, keeping only a bit in the SLS
value that maps the position of a bit whose value is 1 in the mask. The resulting value determines
the link to be selected.
For example:
If the value of the link selection field is 2 (0010), SLS is 1011, then the link selected is 1.

The result value of the calculation of SLS and the mask is of a 4-bit binary number, and the value
range is determined by the mask. In principle, if the decimal value of the mask equals that getting
by taking 1 from the total link number of a certain link set, the signaling unit can directly use
this result value to select the link.
For example:
There are four links in a link set and the link selection code is 0011. Even if the SLS varies, the
calculation result of the SLS and the mask remains in the range of 0-3. And this result can be
directly or indirectly used to select the link.

Overlapping
When the route selection field and the link selection field are both used for selecting the link,
overlapping may occur. The signaling unit always selects the same link set number and signaling
link number.
For example:
Suppose there are two MTP link sets (numbered 0 and 1) in one office direction, each MTP link
set has two links (numbered 0 and 1), and the value of both the link set selection mask and the
link selection mask are 0010. The link set selection mask and the link selection mask share the
same algorithm; therefore, when the system originates calls, link 0 of link set 0 and link 1 of
link set 1 are always occupied; while link 1 of link set 0 and link 0 of link set 1 are idle all the
time.
To prevent overlapping of bits when the system selects the link and the link set, do not set the
"route selection field" and the "link selection field" with the same value. It is recommended to
set "1" in the two masks to different positions. For example, if the link set selection mask is
0110, you can set the link selection mask to 1001.

TDM Semi-Permanent Connection

It is a signaling link connected to the trunk interface board SEPU. It can be connected to the
signaling link on the pinch card (SLPU/SHPU) of the SBPUs or the pinch card (SLPU/SHPU/

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-7

SHPE) of the SBPE through the H.110 bus (that is, TDM bus), to construct a physical path for
message transmission. This path is constructed through the commands, so it is called TDM semi-
permanent connection.
Figure 4-5 shows that the SEPU can construct semi-permanent connection with the SLPU/SHPU
through the internal HW in the same slot. The broken line in the figure indicates the signaling
message transmission path in the same slot.

NOTE

This section takes the configuration of the SBPU for an example. The configuration of the SBPE is the same as
that of the SBPU.

Figure 4-5 TDM semi-permanent connection in the same slot

As shown in Figure 4-6, the SEPU can also establish the TDM semi-permanent connection with
the SLPU/SHPU/SBPE in other slots of the same frame through the H.110 bus.
The SEPU in slot 0 is connected to the SEPU in slot 3 through the H.110 bus, and the SEPU in
slot 3 is connected to the SLPU/SHPU/SBPE in slot 3 through the internal HW to construct a
signaling transmission path. The broken line in the figure indicates the signaling message
transmission path in different slots.

4-8 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Figure 4-6 TDM semi-permanent connection in different slots

E1/T1 E1/T1

SEPU0 SEPU3

H.110 bus

HW HW

SLPU SLPU
/ /
SHPU SHPU

SBPU0 SBPU3

ATM
ATM is the short for asynchronous transfer mode. It takes cell as the unit for message
transmitting, multiplexing, and switching. The ATM cell has the fixed length of 53 bytes, in
which 5 bytes are the header, and the other 48 bytes are the payload. In this case, asynchronous
transfer means each cell is transmitted solely without interworking with other cells. The cell is
short, and thus the transmission has short delay.

VP/VC
The ATM is connection-oriented and the ATM header requires an identifier to indicate the
connection to which each cell belongs. Therefore, the concept of virtual connection is introduced.
Virtual connection means that a physical channel is divided into multiple logic channels. When
a connection is established, the corresponding logic channel is designated to connect two users,
and after the connection is removed, this logic channel can be assigned to other users. Virtual
connection can be established at two levels: virtual path (VP) level and virtual channel (VC)
level, which are identified by the virtual path identifier (VPI) and virtual channel identifier (VCI)
respectively in the header.
The VP is the collection of many VCs with the same VPI value. The VPs take different VPI
values, and the VCs in the same VP take different VCIs, but the VCs of different VPs can have
the same VCI. The relationship between the VP, VC, and physical path is as shown in Figure
4-7.

Figure 4-7 Relations between the VP, VC, and physical channel

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-9

AAL
The ATM adaptation layer (AAL) is the interface between the upper protocol and the ATM
layer, and it transfers the messages between them. Currently, there are four kinds of AAL: AAL1,
AAL2, AAL3/4, and AAL5. Each type of AAL supports a specific service in the ATM network.
Commonly, the ATM equipment providers adopt AAL5 to support the data communication
services.

Message TID Load Sharing

The function of message transaction ID (TID) load sharing implements the following:
l SCCP dynamic load sharing between sixteen signaling points, with each signaling point
bearing up to 16 links
l Multi-route dynamic load sharing between multiple signaling points
l Multi-route dynamic load sharing between non-binding groups

Load Sharing on Partial SLS Missing

Assume that the messages are performed load sharing on an STP before being sent to the SG,
or all SLSs are received by the SG but there are multiple routes between the SG to the destination
signaling point, and thus the SLSs in each route are incomplete. When a certain link in a route
is faulty, the load on the links in this route is unbalanced.

The load sharing on partial SLS missing is a solution developed to solve such kind of problem,
that is, load sharing problem in the case of incomplete SLSs and link failure. The system finds
out an available link which contains the least valid SLSs and allocates an SLS contained in the
faulty link to this available link. Then, the system performs this operation again and allocates
another SLS till all SLSs contained in the faulty link are allocated to the available links. Thus,
the load is evenly shared among the links of a route.

For example: There are three links with the highest priority. The mask code of these links is
1111 (binary). When all SLSs (SLS0-SLS15) are received by the SG, the SLSs are shared among
all these three links, as shown in Table 4-1.

If only SLS0, SLS1, SLS2, SLS6, SLS7, and SLS8 are received by the SG and at the same time
link2 is faulty, as shown in Table 4-2, the system implements the load sharing by following the
steps below:

1. The system finds out an available link which contains the least valid SLSs. The number of
the valid SLSs in link0 is the same as that in link1, that is, 2. In this case, the system allocates
SLS2 contained in link2 to link0 based on the minimum matching rule of the signaling link
code (SLC).
2. The system performs step 1 and finds that the number of valid SLSs in link1 is 2, which is
smaller than that in link0, that is, 3. In this case, the system allocates SLS5 to link1.
3. The system performs step 1 and allocates SLS8 to link1.
4. The system performs step 1 and finds that the number of the valid SLSs in link0 is the same
as that in link1, that is, 3. In this case, the system allocates SLS11 contained in link2 to
link0 based on the minimum matching rule of the signaling link code (SLC).
5. The system performs step 1 and allocates SLS14 to link0.

4-10 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

NOTE
SLS11 is a invalid SLS, so the number of the valid SLSs in link0 is also the same as that in link1, that is,
3. In this case, the system still allocates SLS14 to link0 based on the SLC rule.
6. All SLSs contained in link2 are allocated to link0 and link1. Link0 and link1 separately
contain three valid SLSs, as shown in Table 4-3. Thus, the load sharing on partial SLS
missing is implemented.

Table 4-1 Load sharing for all SLSs (SLS0-SLS15) when all links are available
Link0 0 3 6 9 12 15

Link1 1 4 7 10 13 -

Link2 2 5 8 11 14 -

Table 4-2 Load sharing for valid SLSs (bold) when link2 is faulty (before reallocation of SLSs)
Link0 0 3 6 9 12 15

Link1 1 4 7 10 13 -

Link2 2 5 8 11 14 -
(faulty)

Table 4-3 Load sharing for valid SLSs (bold) when link2 is faulty (after reallocation of SLSs)
Link0 0 3 6 9 12 15 2 11 14

Link1 1 4 7 10 13 5 8 - -

Link2 - - - - - - - - -
(fault
y)

Binding-Based Linkset Load Sharing

Implementation Principle
To better focus on network performance and improve operation efficiency, the SG, serving as
the signaling gateway between the current network and other carrier's networks, binds incoming
and outgoing linksets into different groups based on the linkset load sharing binding rules. During
service processing, the SG selects linksets based on priorities of the linksets and then forwards
messages to the destination (for example, GSM and CDMA messages can be forwarded to the
peer network over different linksets based on the binding-based linkset load sharing function).
This facilitates network monitoring and maintenance. Figure 4-8 shows the typical networking
for implementing the binding-based linkset load sharing function.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-11

Figure 4-8 Typical networking for implementing the binding-based linkset load sharing function

NE1
1
SG_A 2 STP1
4
Network1
NE2

5
3 6

NE3

Network2
STP2
SG_B

NE4
Vendor Other

In the above figure, SG_A, serving as the ISTP, uses different linksets to interwork with
Network1 (GSM network), Network2 (CDMA network), and the STP in the peer network.
(Assume linksets 1 and 2 are used for transmitting GSM messages and linksets 4 and 5 are used
for transmitting CDMA messages. Linksets 3 and 6 are C links between SG_A and SG_B.
Linkset 3 is used for transmitting GSM messages while linkset 6 is used for transmitting CDMA
messages.)

Take SG_A and GSM network as an example to describe the implementation of the binding-
based linkset load sharing function, which is similar for SG_B and CDMA network.

Between SG_A and another signaling point (for example, NE1), there are several available
linksets:

l GSM messages can be transmitted over linksets 1, 2, and 3. The priorities of linksets 1 and
2 are the same and the highest, and then the linkset 3.
l CDMA messages can be transmitted over linksets 4, 5, and 6. The priorities of linksets 4
and 5 are the same and the highest, and then the linkset 6.

After receiving a GSM message, SG_A forwards the message over linksets 1 and 2 in load
sharing mode. If linksets 1 and 2 are unavailable, SG_A forwards the message over linkset 3.

If linksets 1, 2, and 3 are unavailable simultaneously, SG_A forwards the message over linksets
4 and 5 in load sharing mode. If linksets 1, 2, 3, 4, and 5 are unavailable simultaneously,
SG_A forwards the message over linkset 6.

Data Configuration Requirement

The data configuration of the binding-based linkset load sharing function must meet the
following requirements:

4-12 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

l Linksets 1 and 2 must bind with linkset 3 and all linksets in the GSM network, and linkset
3 must bind with all linksets in the GSM networks.
l Linksets 4 and 5 must bind with linkset 6 and all linksets in the CDMA network, and linkset
6 must bind with all linksets in the CDMA networks.

4.1.2 Networking Structure

This section describes the networking structure for configuring the MTP data.
Figure 4-9 shows the connections between the SG7000 and the STP or LS through the MTP3
protocol.

Figure 4-9 Networking through the MTP3 protocol

4.1.3 Relation Between Data Tables

This section describes the relations between data tables related to MTP data configuration.

Relation Between MTP Data Tables

The sequence of the items in Figure 4-10 from the top to bottom indicates the order of data
configuration. When adding the table items, add the top items first, and then the lower items.
When deleting the items, delete the lower items and then the upper items.
Example 1:
When deleting a DSP, and all information (signaling route, signaling link set and signaling link)
of the DSP, proceed as follows:
Delete signaling link → delete signaling route → delete signaling link set → delete DSP...
Example 2:
When adding a DSP, and all information (signaling route, signaling link set and signaling link)
of the DSP, proceed as follows:
Add DSP → add a signaling link set → add a signaling route → add signaling link

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-13

Figure 4-10 Relations between the MTP data tables

ADD N7DSP ADD LN

ADD N7RT
[ DSP index ]
[ DSP title ]
[ Link set index ]
[ Link set title ]

ADD TDMCONN

[ Index ]

ADD N7LNK
[ Link set index ]
[Link set title ]
Semipermanent
[ ]
connection code

Relation Between MTP and Other Data Tables

Figure 4-10 shows the parameter relations between the MTP data and the local office data. The
MTP DSP table references the index of the command ADD LN, and the MTP link set table
references the index of the command SET OFI or the index of the command ADD OPC
(multiple SPs). The commands ADD LN, SET OFI, and ADD OPC have been introduced in
3 Configuring Local Office Data.
Figure 4-11 shows the parameter relations between the timer table, alarm threshold table,
congestion threshold table, and MTP data table. The MTP data table imports items from the
timer table, alarm threshold table, and congestion threshold table. Either of the timer table, alarm
threshold table, or the congestion threshold table has a default value. Use the default index when
configuring the MTP data.

4-14 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Figure 4-11 Relations between the timer, threshold, and MTP data tables

Figure 4-12 shows the parameter relation between the MTP initial shielding table and the MTP
link set table. The link set table references index from the MTP initial shielding table, thus the
system can control the MTP message shielding. See 5 Configuring MTP Shielding Data for
details.

Figure 4-12 Relation between the MTP initial shielding table and the MTP link set table

4.1.4 Data Collection

Before configuring the MTP data, you must collect the data including the local SPC, DPC, and
DSP type.

Collect the information as shown in Table 4-4 before configuring the MTP data.

Table 4-4 Data collection

Local SP code DSP code DSP style Whether DSPs are

adjacent or not

Route selection field Link selection field Signaling link code Signaling link type

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-15

Local SP code DSP code DSP style Whether DSPs are

adjacent or not

4.1.5 Configuration Principles

This section describes the principles to be followed when you configure the MTP data.

Route Selection Field and Link Selection Field

l To implement load sharing among the links, the configuration of Route selection field in
the DSP table and that of Link selection field in the link set table should be considered
together.
Suppose there are two routes with the same priority to a DSP, that is, there are two link
sets, and each link set has eight links.
If Route Selection Field is set to 8 ("1000" in binary) and Link Selection Field is set to
7 ("0111" in binary), and none of the bits of the two parameters is set to 1.
SLS Route Selection Link Selection

0000 0 0

0001 0 1

0010 0 2

0011 0 3

0100 0 4

0101 0 5

0110 0 6

0111 0 7

1000 1 0

1001 1 1

1010 1 2

1011 1 3

1100 1 4

1101 1 5

1110 1 6

1111 1 7

4-16 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

As listed above, half of 16 messages will be sent in route 0, and the other half will be sent
in route 1, and the load can be shard evenly by each link of each route. This is a kind of
ideal setting.
l To prevent overlapping, you can set the least four bits of Route Selection Field and all bits
of Link Selection Field to 0, but do not set them to 1 at the same time.
Suppose there are two routes with the same priority to a DSP, that is, there are two link
sets, and each link set has 8 links. Suppose Route Selection Field is set to 12 ("00001100"
in binary) and Link Selection Field is set to 7 ("0111" in binary), then,
SLS Route Selection Link Selection

0000 0 0

0001 0 1

0010 0 2

0011 0 3

0100 1 4

0101 1 5

0110 1 6

0111 1 7

1000 0 0

1001 0 1

1010 0 2

1011 0 3

1100 1 4

1101 1 5

1110 1 6

1111 1 7

Eight messages will be sent to route 0, and the other half will be sent to route 1, but in route
0, only links 0-3 are occupied and in route 1, only links 4-7 are occupied. The load sharing
is not implemented because the load is not shared evenly by the 8 links of each link set.
This is not an ideal setting. Therefore, do not set the Route Selection Field to 12 because
the second bits of the Route Selection Field and the Link Selection Field are set to the
same value.
l Try to use the first four bits of the Route selection field, and thus all the link sets sent to
different non-adjacent signaling points can be selected to share all the SLSs.
Suppose there are two routes with the same priority to a DSP, that is, there are two link
sets, and each link set has 16 links, if Route Selection Field is set to 8 and Link Selection
Field is set to 15, then,

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-17

SLS Route Selection Link Selection

0000 0 0

0001 0 1

0010 0 2

0011 0 3

0100 0 4

0101 0 5

0110 0 6

0111 0 7

1000 1 8

1001 1 9

1010 1 10

1011 1 11

1100 1 12

1101 1 13

1110 1 14

1111 1 15

Load sharing can be implemented. In route 0, however, only links 0-7 are occupied and in
route 1, only links 8-15 are occupied. The load is not evenly shared by each link of each
link set. Assign the first four bits of the route mask to share the load evenly.
Suppose there are two routes with the same priority to a DSP, that is, there are two link
sets, and each link set has 16 links. The two link sets are also used for the second DSP.
Then, configure as follows: The route mask of the first DSP is the shown in the above table.
The route mask of the second DSP is 24 (00011000). The routing of the second DSP is
shown in the following table:
SLS Route Selection Link Selection

0000 1 0

0001 1 1

0010 1 2

0011 1 3

0100 1 4

0101 1 5

4-18 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

SLS Route Selection Link Selection

0110 1 6

0111 1 7

1000 0 8

1001 0 9

1010 0 10

1011 0 11

1100 0 12

1101 0 13

1110 0 14

1111 0 15

With the above two tables, all the 32 links can be used for routing.

Partial SLS Missing Load-Share of Message

l The availability of the SLS must be configured through the Available SLS parameter in
the SET SOFTCFG2 command. For example, when only SLS0, SLS1, SLS2, SLS6, SLS7,
and SLS8 are valid among SLS0-SLS15, you must select these SLSs in the Available
SLS parameter.
l When you configure the availability of the SLS or run ADD N7LKS to modify Partial
SLS missing load-share of message of Enhance route policy, packet loss or disorder may
occur immediately due to the dynamic data change on multiple link sets after the operation.
Therefore, perform the operation with caution.
l This function is applicable to the MTP route selection only.

Start/End Index
The link set binding policy table must be configured (ADD N7LKSPL) to implement the load
sharing of signaling traffic when the SG is configured with multiple SPCs. When Type is set to
MTP, the index is used by incoming SS7 link sets; When Type is set to M3UA, the index is
used by incoming M3UA link sets.
For example:
As shown in Figure 4-13, the SG has three OPCs. Link set six is to be configured between the
SG and SP4. The problem is, how to implement the load sharing from SP1-SP3 and AS1-AS2
to SP4.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-19

Figure 4-13 Load sharing of signaling traffic among multiple SPCs

Note: [1, 4] indicates that the first link of the link set is 1, and the last link is 4.

If we can know the quantities of the signaling messages sent from SP1-SP3 and AS1-AS2 to
SP4 through the SG, the traffic to SP4 can be grouped based on the number of outgoing link
sets. That is, all incoming link sets to SP4 through the SG are grouped so that the messages
transmitted by all the link sets of each group to SP4 through the SG will be transferred by an
outgoing link set. In this way, the traffic to a certain office direction is evenly shared by each
link set. According to the traffic changes of various office directions in the network, this
calculation method can be modified by resetting the packet data to implement even load sharing.

As shown in Figure 4-13, the following data must be configured before adding link set six:

l Incoming link set binding data, in which Type is MTP, Start index is 1, End index is 3,
and Binding reference is 1.
l Outgoing link set binding data, in which Type is M3UA, Start index is 4, End index is
4, and Binding reference is 1.

When adding link set six, set Binding reference to 1. That means, all signaling messages sent
from SP1-SP3 and AS1 to SP4 through the SG are transmitted over link set 6. The signaling
traffic of the AS2 to SP4 can be configured when link set seven is added.

Configuration Principles of the Link Set and Link

For the sake of load sharing, it is recommended to configure links of the same type in the same
link set. You must avoid configuring both 64-kbit/s and 2-Mbit/s links in the same link set.

4.1.6 General Steps

You must follow certain procedures to configure the MTP data.

When configuring the alarm threshold (ADD N7ALMT), congestion threshold (ADD
N7CGT), and timer (ADD TIMER), use the default value. If necessary, the data configuration
should be implemented before configuring the MTP data. Generally, the enhanced route policy
is configured only when the load sharing function of multiple SPCs is to be implemented. Before
configuring the enhanced route policy, you must well plan and configure the start index and end
index.

The procedures of configuring the MTP data are as listed in Table 4-5. This chapter specifies
data configuration from step 4.

4-20 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Table 4-5 Configuring the MTP data

Step Operation

1 To add the alarm threshold definition (ADD N7ALMT) (optional)

2 To add the congestion threshold definition (ADD N7CGT) (optional)

3 To add timer (ADD TIMER) (optional)

4 To add the MTP DSP (ADD N7DSP)

5 To add the MTP link set (ADD N7LKS)

6 To add the MTP link set policy (ADD N7LKSPL) (Optional)

7 To add the MTP route (ADD N7RT)

8 To add TDM SPC (ADD TDMCONN)

9 To add the MTP link (ADD N7LNK)

4.2 Configuring MTP Data

Configuring the MTP data includes adding the MTP DSP, adding the MTP link set, and adding
the MTP route.
4.2.1 Adding MTP DSP
To enable the signaling messages of the local office to reach the designated MTP DSP, in the
No.7 signaling network, add the data describing this DSP in the local office. If an MTP DSP is
to be added, you must know the attributes of this DSP and set the local office information before
adding it.
4.2.2 Adding MTP Link Set
If a new adjacent DSP is added, the MTP link set should also be added accordingly. Then you
need know the index of the newly added adjacent DSP and the link set selection. If the data of
the adjacent DSP connected with the local link set is not configured, the MTP DSP should be
added first.
4.2.3 Adding MTP Route
MTP route is a channel for signaling message transmission between two SPs. For adding a new
MTP route, you should configure the data such as the number of the link set to the DSP, priority,
DSP index should be obtained first. If the MTP link set is not configured for the route to be
added, it should be added first.
4.2.4 Adding TDM Semi-Permanent Connection
TDM semi-permanent connection is the signaling link configured from the E1/T1 of the SEPU
to the pinch card SLPU/SHPU/SHPE of the SBPU/SBPE. This command defines the trunk
interface board (SEPU) that accesses signaling links as well as the time slots on the trunk
interface board that are used by the semi-permanent connections.
4.2.5 Adding MTP Link
Signaling links are physical connections used for connecting signaling points and transmitting
signaling message.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-21

4.2.1 Adding MTP DSP

To enable the signaling messages of the local office to reach the designated MTP DSP, in the
No.7 signaling network, add the data describing this DSP in the local office. If an MTP DSP is
to be added, you must know the attributes of this DSP and set the local office information before
adding it.
When a record is added to the MTP DSP table, the system allocates an idle index value for this
record, which is quoted when configuring the MTP link set and MTP route.

Command
ADD N7DSP

Parameter
Par Paramet Parameter Description
ame er Name
ter
ID

IPC Internatio It indicates the code of a signaling point in the network. It is optional. Its
nal value contains 6-digit hexadecimal numbers, such as, AAAAAA.
network According to the No.7 signaling protocol, an SP can exist in four different
code signaling networks at the same time, namely international network,
international reserved network, national network and national reserved
IP2 Internatio
network. The value 0 indicates invalid SPC value. The SPCs cannot be
C nal
identical, that is, one SP cannot correspond to two different DSP indices.
reserved
network Unify the codes of the signaling point to a letter in upper or lower case.
code Letter in upper case is recommended in this manual.

NP National
C network
code

NP2 National
C reserved
network
code

STP Signaling When the DSP is an STP or has the signaling transfer function, it is set
transfer to True, otherwise, it is set to False. If the DSP has the signaling transfer
point function, it must be set to STP, or the transferred signaling route cannot
be added.

APF Adjacent It indicates if the DSP is adjacent to the local office SP, that is, if there
flag is a direct signaling link between the DSP and the local office SP. If there
is a direct signaling link to the local office SP, it is set to True, otherwise,
it is set to False.

4-22 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Par Paramet Parameter Description

ame er Name
ter
ID

SLS Route It specifies ways to implement load sharing of the signaling traffic
selection between multiple signaling routes to the DSP. See section 4.1.1 Terms
field for details. The value of the route selection field is an 8-bit binary number
ranging 0-255. By default, it is set to null.
The configuration principles of the parameters are as follows:
l When there is only one link set between the SG and the DSP, set the
Route Selection Field to 0, which is the default value.
l When there are two or more MTP link sets, the decimal value of the
Route Selection Field should not be smaller than the number of total
link sets minus 1.
l Use the first four bits of the route selection field, and thus all the MTP
links in the same link set sent to different non-adjacent signaling points
can be selected to share the signaling load. See 4.1.5 Configuration
Principles for examples.
l To prevent overlapping, you cannot set the last four bits of the Route
selection field and the Route selection field in each link with the same
value. It is recommended to set 1 in the two fields at different positions.
For example, if the link set selection field is 0110 (first four bits are
0), you can set the link selection mask to 1001.

STD DSP type Currently, the signaling network supports two standards, namely the ITU
STY standard, which adopts 24-bit or 14-bit signaling point code, and the
LE American National Standards Institute (ANSI) standard, which adopts
24-bit or 14-bit signaling point code.
This parameter specifies the standard that needs to be adopted by the
DSP. China adopts ITU standard that supports 24-bit signaling point
code, which is the default value.

SCC SCCP It indicates whether an SP has the SCCP function. Set the value to Yes
PUS function or No according to the actual situation of the SP.
ED

TX Timer It indicates the index number of the timer value used by this DSP. This
index value is the index returned by the system after executing the command
ADD TIMER successfully. The timer table has the default value in the
system. The index is 0.

SU SUA It specifies the SUA singling switch. It can be set to:

AP point code l False (False)
OIN
T l True (True)
It is set to False by default.

LNI logic It specifies the local network in which this DSP is located.
network It is optional. Its value is of numeral type and ranges 0-127. It is set to
index 0 by default.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-23

Par Paramet Parameter Description

ame er Name
ter
ID

SER Service This switch controls the services that are applied for on the DSP.
FU function It is optional and its value is of enumeration type. It can be set to one or
NC switch both of the following values:
SW
CH l BIT0 (Collecting digits for ISUP message): Judging according to the
office direction whether to collect digits. If yes, the system sends the
IAM and SAM to the MNP service module for processing; if not, the
system sends the IAM only.

Related Commands

Table 4-6 Related commands for configuring the MTP DSP

Command Function

ADD N7DSP To add the MTP DSP

MOD N7DSP To modify the MTP DSP

RMV N7DSP To remove the MTP DSP

LST N7DSP To query the MTP DSP

NOTE

If an important parameter is to be modified, first disconnect (deactivate) all the signaling links to this DSP
or make all the signaling routes to this DSP become offline to make this DSP unreachable (inaccessible),
and then modify the parameter of this DSP, finally reconnect (activate) all the disconnected signaling links.
An insignificant parameter can be modified directly through the command MOD.

4.2.2 Adding MTP Link Set

If a new adjacent DSP is added, the MTP link set should also be added accordingly. Then you
need know the index of the newly added adjacent DSP and the link set selection. If the data of
the adjacent DSP connected with the local link set is not configured, the MTP DSP should be
added first.
All link set data of the DSPs that are adjacent and have direct links to the local office should be
described here. The data of non-straight (non-directional) links is unnecessary to be described
here.
When a new record is added in the MTP link set table, the system will allocate an idle index for
this record, which will be used during the configuration of the MTP route and MTP link.

Command
ADD N7LKS

4-24 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Parameter
Par Paramete Parameter Description
ame r Name
ter
ID

AP Adjacent It indicates the adjacent DSP connected with the direct signaling link set.
X SP index It corresponds to the DSP index in the MTP DSP table, and the adjacent
flag of the DSP should be set to True.

APT Adjacent It specifies the name of the adjacent destination signaling point
SP title associated with the direct signaling link set.
It is optional. Its value is of the character type and can contain up to 40
English characters.

OF Local SP If the equipment supports multiple SPCs and two or more than two local
X index SPs have been set, this parameter is used to configure the OPC of the
link set.

NI Network It indicates to which network (international, international reserved,

indication national or national reserved) this link set belongs.

SLS Link It indicates how to implement load sharing of the signaling traffic
selection between multiple signaling links in a signaling link set. See section 4.1.1
field Terms for descriptions. Actually the value of this filed is the load sharing
mask for signaling links. This parameter is the decimal value of a 4-bit
binary number and it ranges from 1 to 15. By default, it is set to 0.
The configuration principles of this parameter are as follows:
l If there is only one signaling link in a signaling link set, set Link
selection field to 0 by default.
l If there are two MTP links, set one of the bits to 1.
l If there are three or four MTP links, set two of the bits to 1.
l If there are five to eight MTP links, set three of the bits to 1.
l If there are more than eight MTP links, set all the bits to 1.
l To prevent overlapping, you cannot set the last four bits of Route
selection field and the Link selection field of all link sets to the same
value. It is recommended to set 1 in the two fields in different
positions. For example, if the Route selection field is 0110, you can
set the Link selection field to 1001 (first four bits are 0).
See section 4.1.5 Configuration Principles for details about the
configuration of Link selection field.

WR Alarm It indicates the index of the alarm threshold value used by the local link
NX threshold set. The value used here is the returned value after the successful
index execution of the command ADD N7ALMT. And the alarm parameter
value corresponding to this index is listed in the alarm threshold table.
It is optional. Its value is of the numeral type. Its value range is 0-65534.
It is set to 0 by default.
When this parameter value is set to 65535, it indicates that alarm
threshold is not needed. In practice, the index is set to 0 by default.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-25

Par Paramete Parameter Description

ame r Name
ter
ID

RO Enhance It specifies whether the MTP uses the enhanced routing policy to select
UTE route links.
POL policy It is optional. Its value is of the enumeration type. It can be set to:
ICY
l OTID (OTID load-share of message): The system selects MTP links
based on the TID.
l FULL (Full load-share of message): The system selects MTP links
for unsegmented XUDT and UDT messages based on the TID load
sharing, and for the segmented XUDT and UDT messages based on
the SLS.
l DTID (DTID load-share of message): The system selects MTP links
for continue messages based on the TID load sharing.
l PSML (Partial SLS missing load-share of message): The system
performs load sharing in the case of SLS missing.
l UNUSED (Unused of enhanced policy): The system selects MTP
links based on the SLS rather than using the enhanced policy.
It is set to UNUSED (Unused of enhanced policy) by default.

ISX Incoming It indicates the index of the initial shielding table used for shielding the
shielding messages received by the local link set. This index is used to search the
table initial shielding table for a certain shielding control table item. The value
index used here is the returned value after the successful execution of the
command ADD N7IM.
It is optional. Its value is of the numeral type. Its value range is 0-65535.
It is set to 65535 by default.
When it is set to 65535, it indicates that shielding control is disabled for
the messages received by the link set. When a message is received by the
local link set, and if the value of this parameter is valid, the corresponding
shielding control table item will be searched in the initial shielding table
according to the index, and the standard shielding control process will
be enabled.
NOTE
The initial shielding table indexed 0 serves as the public shielding conditions for
all incoming links, and it cannot be bound with the link set. So, INCOMING
SHIELDING TABLE INDEX and OUTGOING SHIELDING TABLE
INDEX can only reference the non-zero index in the shielding control table.

4-26 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Par Paramete Parameter Description

ame r Name
ter
ID

OS Outgoing It indicates the index of initial shielding table used for shielding the
X shielding messages sent by the local link set. This index is used to search the initial
table shielding table for a certain shielding control table item. The value used
index here is the returned value after the successful execution of the command
ADD N7IM.
It is optional. Its value is of the numeral type. Its value range is 0-65535.
It is set to 65535 by default.
When the parameter value is set to 65535, it indicates that shielding
control is disabled for the messages sent by the link set. When a message
is sent by the local link set, and if the value of this parameter is valid, the
corresponding shielding control table item will be searched in the initial
shielding table according to the index, and the standard shielding control
process will be enabled.

TX Timer It indicates the index number of the timer used by the local link set. The
index value used here is the returned index after the successful execution of the
command ADD TIMER. The timer parameter value corresponding to
this index is listed in the timer table. In practice, the index is set to 0 by
default.

CT Congestio It indicates the index number of the congestion threshold value used by
X n the local link set. The value used here is the returned index after the
threshold successful execution of the command ADD N7CGT. The alarm
index parameter value corresponding to this index is listed in the congestion
threshold table. In practice, the index is set to 0 by default.

SCR Masking It is the switch of the FireWall. The value OFF indicates to disable the
N function FireWall, ON to enable. This parameter is only used when the function
of FireWall is enabled.

REF Masking It is the masking reference from the FW initial shielding table. This
reference parameter is used when the function of FireWall is enabled.
It is optional. Its value is of the numeral type. Its value range is 0-65535.
It is set to 65535 by default, indicating not use.

DFT Default It is masking reference 0 from the FW initial shielding table. This
REF masking parameter is used when the function of FireWall is enabled.
reference It is optional. Its value is of the numeral type. Its value range is 0-65535.
It is set to 65535 by default, indicating not use.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-27

Par Paramete Parameter Description

ame r Name
ter
ID

SR Service It enables or disables the functions of number change and black & white
VP process list. To enable this function, tick the box. It is set to Disable by default.
RO switch It is optional. Its value is of the enumeration type. It can be set to one or
SW more of the following values:
T
l BW (BW switch)
l NS (Number switch)
l ISUP (ISUP fraud prevention)
l ROSWT (Reroute switch)
l CFSSWT (CFS service switch)
l CNLSWT (CNL service switch)
l LNPSWT (LNP service switch)
l MCSWT (Message copy switch)
If the reroute and message copy functions are simultaneously enabled,
the system performs the message copy function first and then the reroute
function.

LN Linkset It determines which bit of the SLS is discarded and which bit in the last
KSE expansion four bits of the OPC or in the first four bits of the 24-bit ANSI message
TSE route is added to construct the new SLS.
LE selection It is optional. Its value is of the numeral type and is an 8-bit binary code.
It is set to 0 by default. During the configuration, you must enter a
hexadecimal number.
The configuration principles are as follows:
l If any bit of the last four bits is 1, the corresponding bit of the SLS is
not taken into account of computing the SLS.
l If any bit of the first four bits is 1, the corresponding bit of the last
four bits of the OPC or the first four bits of the SLS in the ANSI
message is taken into account of computing the SLS.
l The number of bit 1 in the first four bits must be the same as that in
the last four bits.
l If it is set to 0, this function is disabled and the message is sent based
on the previous processing flow.

REF Binding It maps with Binding reference in the ADD N7LKSPL command. The
VA reference link sets with the same binding reference are bound to the same link set.
L It is optional. Its value is of the numeral type and ranges 0-65535. It is
set to 65535 by default. For details, see Start/End Index.

4-28 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Par Paramete Parameter Description

ame r Name
ter
ID

RR Reroute It specifies the mode that the system adopts to process different messages
T policy in the redirect service.
It is valid only when ROSWT is set to Open.
It is optional and its value is of the enumeration type. It can be set to:
l ANP (All DPC not processed): All MSU messages are processed
based on the original processing flow instead of the reroute processing
flow despite of the message type.
l SPP (DPC in self PC processed): When the MSU message is the
locally terminated message, the system obtains Type of next reroute
table and Next reroute reference, and then sends the message to the
reroute part for processing. When the MSU message is not the locally
terminated message, the system processes the message based on the
original processing flow instead of the reroute processing flow.
l NSPP (DPC not in self PC processed): When the MSU message is not
the locally terminated message, the system obtains Type of next
reroute table and Next reroute reference, and then sends the message
to the reroute part for processing. When the MSU message is the
locally terminated message, the system processes the message based
on the original processing flow instead of the reroute processing flow.
l AP (All DPC processed): The system obtains Type of next reroute
table and Next reroute reference, and then sends the MSU message to
the reroute part for processing despite of the message type.
It is set to ANP by default. It must be configured based on the actual
conditions.

TTY Type of It specifies the type of the table corresponding to the next operation of
PE next the reroute.
reroute It is valid when ROSWT is set to Open and the MSU message meets the
table condition set in RRT.
It is optional and its value is of the enumeration type. It can be set to:
l VOID (Void)
l ROT (Reroute OPC table)
l RDT (Reroute DPC table)
l RCDT (Reroute called GT table)
l RCGT (Reroute calling GT table)
l ROCT (Reroute operation code table)
l RRLT (Reroute rule table)
It is set to VOID by default. It must be set based on the actual conditions.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-29

Par Paramete Parameter Description

ame r Name
ter
ID

NR Next It specifies the reroute reference of the table type corresponding to the
R reroute next operation of the reroute.
reference It is valid when ROSWT is set to Open and the MSU message meets the
condition set in RRT. It is used to match the corresponding data in the
reroute table configured in Type of next reroute table.
It is optional. Its value is of numeral type and ranges 0-65535. It is set to
65535 by default. It must be set based on the actual conditions.

CO Signaling It indicates the signaling collection policy corresponding to this link set.
LLI collection The signaling collection policy is configured by ADD COLLECTRPL.
DX policy Its value range is 0-255. It is set to 0 by default, indicating that the system
index uses the default signaling collection policy.

NU Number It specifies the number discrimination type of the link set. After
MDI discrimina comparing with the number discrimination type that maps the called
SM tion number, the system performs the corresponding processing. The
OPT option processing principles are as follows:
l If the type of number to be discriminated is calling number, and calling
number belongs to the number discrimination type of the link set, the
system performs subsequent processing.
l If the type of number to be discriminated is called number, and called
number belongs to the number discrimination type of the link set, the
system performs subsequent processing.
l In other cases, the system transfers messages through the original
route.
This parameter is optional. Its value is of the enumeration type. It can be
set to:
l BIT0 (Calling number)
l BIT1 (Called number)
Note that both values can be selected.

CPP Message It specifies the processing policy for copying messages. It is valid only
OLI copy when Service process switch is set to Message copy switch. If Message
CY policy copy switch is enabled, the system judges the message copy conditions.
The system copies the required messages based on configured rules and
transmits them to the specified signaling point over the original route.
It is optional. Its value is of the enumeration type. It can be set to:
l ANP (All DPC not processed)
l ISP (DPC in self PC processed)
l NISP (DPC not in self PC processed)
l AP (All DPC processed)
It is set to ANP (All DPC not processed) by default.

4-30 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Par Paramete Parameter Description

ame r Name
ter
ID

NC Type of It specifies the copy table whose configuration is used to process the
PTY next message in a link set. If the messages are not to be queried and copied,
PE message set this parameter to Void. This parameter, together with Next message
copy table copy reference, determines the table item set used in the next message
query and copy. This parameter can be set to:
l Void
l Message copy OPC table
l Message copy DPC table
l Message copy called GT table
l Message copy calling GT table
l Message copy operation code table
l Message copy rule table
It is set to Void by default.

NC Next It specifies the reference of the message copy in the next message copy
PRE message table. This parameter, together with Type of next message copy table,
F copy determines the table item set used in the next message query and copy.
reference If the messages are not to be queried and copied, this parameter need not
be configured.

Related Commands

Table 4-7 Related commands for configuring the MTP DSP

Command Function

ADD N7LKS To add the MTP link set

MOD N7LKS To modify the MTP link set

RMV N7LKS To remove the MTP link set

LST N7LKS To query the MTP link set

NOTE

To modify a referencing or/and referenced parameter, you must first make the link set to be modified
unavailable (deactivate all links in this link set or directly deactivate this link set when the link set works
normally) and then modify this parameter. After the modification, activate the deactivated links. You can
directly modify parameters that have no referencing or/and referenced relations.

4.2.3 Adding MTP Route

MTP route is a channel for signaling message transmission between two SPs. For adding a new
MTP route, you should configure the data such as the number of the link set to the DSP, priority,

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-31

DSP index should be obtained first. If the MTP link set is not configured for the route to be
added, it should be added first.
When a new record is added in the MTP route table, the system allocates an idle index value for
this record.

Command
ADD N7RT

Parameter
Paramete Paramete Parameter Description
r ID r Name

LSX Link set It is mandatory. Its value is of numeral type and ranges 0-65534.
index It indicates the first signaling link set that the signaling route passes
on the way to the destination signaling point. It references the index
of a record generated in ADD N7LKS.

LST Link set It is optional. Its value is of the character type and can contain up
title to 40 English characters.
It specifies the name of the first signaling link set that the signaling
route passes on the way to the destination signaling point. It
references the name of a record generated in ADD N7LKS.

DPX DSP index It is mandatory. Its value is of numeral type and ranges 0-65534.
It identifies the destination signaling point to which the signaling
route is destined. It references the index of a record generated in
ADD N7DSP.

DPT DSP title It is optional. Its value is of the character type and can contain up
to 40 English characters.
It specifies the name of the destination signaling point to which the
signaling route is destined. It references the name of a record
generated in ADD N7DSP.

PR Priority It is optional. Its value is of numeral type and ranges 0-254. It is

set to 0 by default.
It specifies the priority of this route.
Value 0 indicates the highest priority. Among the multiple
signaling routes to the destination signaling point, those with
higher priority will preferentially chosen to bear the signaling
services; while those with lower priority will be in service only
after all the signaling routes with higher priority become
unavailable. If priority recognition is not required, it is set to 0;
otherwise, it is set in the sequence from 0 according to the priority
level from higher to lower.

4-32 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Paramete Paramete Parameter Description

r ID r Name

TX Timer It is optional. Its value is of numeral type and ranges 0-65534. It

index is set to 0 by default.
It indicates the index of the timer used by the local route.
It references the index returned after ADD TIMER is successfully
executed. The timer parameter value corresponding to this index
is listed in the timer table. Generally, the default value is used, that
is, 0.

Related Commands

Table 4-8 Related commands for configuring the MTP route

Command Function

ADD N7RT To add the MTP route

MOD N7RT To modify the MTP route

RMV N7RT To remove the MTP route

LST N7RT To query the MTP route

NOTE

To modify an important parameter, you must first set the route to be modified to offline and then modify
this parameter. After the modification, set the route online. You can directly modify parameters that are
less important.

4.2.4 Adding TDM Semi-Permanent Connection

TDM semi-permanent connection is the signaling link configured from the E1/T1 of the SEPU
to the pinch card SLPU/SHPU/SHPE of the SBPU/SBPE. This command defines the trunk
interface board (SEPU) that accesses signaling links as well as the time slots on the trunk
interface board that are used by the semi-permanent connections.
NOTE

The SHPE can be configured only on the SBPE.

When you add a TDM semi-permanent connection successfully, the system returns a connection
index. This index will be referenced by the command ADD N7LNK to construct a complete
semi-permanent connection with the SLPU/SHPU link set configured in the MTP link table.
Before you configure the 64-kbit/s normal link, 64-kbit/s satellite link, HSL link and ATM 2-
Mbit/s link, the TDM semi-permanent connection must be configured. M2PALNK requires no
TDM semi-permanent connection.

Command
ADD TDMCONN

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-33

Parameter
Paramete Paramete Parameter Description
r ID r Name

HLA SPC It specifies the attribute of the semi-permanent connection to be

attribute added. It is mandatory and its value is of enumeration type. It can
be set to:
l STSL: signaling time slot connection
l TTSL: voice channel time slot connection
l WFS: monitor forward signaling
l WBS: monitor backward signaling

SHN Shelf These three parameters define the shelf number, frame number,
number and slot number of the SEPU to which the semi-permanent
connection belongs.
FN Frame
The positions of the pinch cards of the SEPU and the designated
number
SBPU/SBPE can be freely set. That is, the shelf number, frame
SN Slot number and the slot number of the SEPU configured here can be
number different from those configured through the command ADD
N7LNK.
The number of the time slot connections configured between slots
is determined by Net time slot number, which can be up to 64. If
there is no net time slot resource between the related two boards,
the time slot connections cannot be configured even though the
two boards are set with combination restriction conditions.
The combination restriction conditions between the SEPU and the
SBPU/SBPE are as follows:
l The time slot connections can be configured between any two
slots among slots 0 - 3 in the main service frame.
l The time slot connections can be configured between any two
slots among slots 0 - 3 in the slave service frame.
l The time slot connections can be configured between any two
slots among slots 12 - 15 in the slave service frame.

E1P Port It indicates the E1/T1 port. It determines which E1/T1 ports on the
number SEPU are selected to provide time slots for implementation of
semi-permanent connection. The value range is 0-15.
It is mandatory. Its value is of numeral type and ranges 0-16. It can
be set to different values based different hardware platforms:
l When the back board is the SEPU, its value range is 0-15.
l When the back board is the EPII, its value range is 0-7.

TS Start time This parameter selects the start time slot on E1/T1 port. It is used
slot together with Count of occupied time slot to select the time slot
for semi-permanent connection. One E1 has 32 time slots with the
value range 0-31, in which time slot 0 is used to transmit
synchronization information. One T1 has 24 time slots with the
value range 0-23.

4-34 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Paramete Paramete Parameter Description

r ID r Name

TSN Count of On E1/T1 port, the numbers of the time slots used by the semi-
occupied permanent connection are as follows: for E1, the value range is
time slot 1-31; for T1, the value range is 1-24.
The 64-kbit/s normal link and the 64-kbit/s satellite link take only
one time slot.
When connecting 2-Mbit/s link, the time slots occupied must be
between 1 and 31 (E1 uses time slots 1-31).
When connecting 1.5-Mbit/s link, the time slot occupied must be
between 1 and 24 (T1 uses the time slots 0-23).

NTN Net time This parameter is required when the time slot resource is used, for
slot example, by semi-permanent connection of the SEPU in different
number slots of the same frame in the same shelf. If the semi-permanent
connection in the same slots of the same frame in the same shelf
does not use the net time slot resource, the net time slot resource
is not configured.
Before entering the net time slot number, use LST
FREENETTS to query the utilization of the net time slot resource.
Enter free time slot number only. The value range of the net time
slot resource is 0-255. The value 65535 indicates that the net time
slot resource is not required. By default, it is set to 65535.

PLN Related This parameter is optional when the semi-permanent connection

index attribute is voice channel time slot connection, monitor forward
signaling and monitor backward signaling. The value range is
0-65535 and by default it is set to 65535.

Related Commands

Table 4-9 Related commands for configuring the TDM semi-permanent connection

Command Function

ADD TDMCONN To add TDM SPC

MOD TDMCONN To modify TDM SPC

RMV TDMCONN To delete TDM SPC

LST TDMCONN To query TDM SPC

4.2.5 Adding MTP Link

Signaling links are physical connections used for connecting signaling points and transmitting
signaling message.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-35

When a new record is added in the MTP link table, the system will allocate an idle index value
for this record.

Command
ADD N7LNK

Parameter
Paramete Paramete Parameter Description
r ID r Name

SHN Shelf If a normal 64-kbit/s link, a 64-kbit/s satellite link, a 2-Mbit/s or

number 1.5-Mbit/s, or an ATM 2-Mbit/s link is to be added, the shelf
number, frame number and slot number indicating the location of
FN Frame the SLPU/SHPU used by the link should be inputted.
number

SN Slot
number

LOC Board If a normal 64-kbit/s link, a 64-kbit/s satellite link, a 2-Mbit/s or

position 1.5-Mbit/s, or ATM 2-Mbit/s link is to be added, it determines
whether the SLPU/SHPU is the upper pinch board or lower pinch
board.
This parameter together with the parameters Shelf number,
Frame number, and Slot number determines the position of the
board to which a link belongs.

4-36 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Paramete Paramete Parameter Description

r ID r Name

LPN Link port It indicates which port of the SLPU/SHPU is occupied by the
number normal 64-kbit/s link, 64-kbit/s satellite link, and 2-Mbit/s or 1.5-
Mbit/s link. The value range is 0-31.
It also indicates which link of the SBPU/SBPE is occupied by the
M2PA link. The value range is 0-7.
The configuration complies with the following principles:
l When only 64-kbit/s links are configured on the SLPU_64K
board, the port numbers can be set to 0-15.
l When only 64-kbit/s links are configured on the SHPU_64K
board, the port numbers can be set to 0-31.
l When only the HSL link is configured on the SLPU_2M board,
only one link is allowed and the port number is always set to 0.
l When only the ATM 2-Mbit/s link is configured on the
SHPU_2M board, only one link is allowed and the port number
is always set to 0. Other links are not allowed on this board.
l When two HSL links are configured on the SHPU_2M board,
the port numbers are always set to 0 and 1.
l When one HSL link and 64-kbit/s links are configured on the
SHPU_2M board, port 0 is configured with the HSL link, ports
1-15 are idle, and ports 16-31 are configured with 64-kbit/s
links.
l The SHPE can only be configured with HSLs. A maximum of
four HSLs can be configured on ports 0, 1, 2, 3 of the SHPE.

LSX Link set The index number of the signaling link in the link set. It
index corresponds to the index of the link set.

LST Link set It specifies the name of the MTP link set to which this MTP link
title belongs.
It is optional. Its value is of the character type and can contain up
to 40 English characters.

SLC Signaling Set the code of a signaling link at an SP to be same as that at the
link code peer SP.

PR Intra-set It indicates the priority of the signaling link in the link set. The
priority available signaling links with higher priorities in the link set are
used first for carrying signaling traffic. The links with lower
priorities are used only after all signaling links with higher
priorities are unavailable. Therefore, it is the same as the priority
field in the MTP route table. The higher the priority is, the lower
the value will be. The value 255 is invalid.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-37

Paramete Paramete Parameter Description

r ID r Name

CT Link type It indicates the type of a link. It must be set based on actual
conditions.
If any option is selected, the system will pop up the description
parameters related to this link type.
If the link type is M2PALNK, see 13 Configuring M2PA Data
for details.
If the link type is M264K or M22M, see 14 Configuring M2UA
Data for details.
The parameter items and setting methods of SAT64 kbit/s, NOR64
kbit/s, and HSL are the same. See Table 4-10 for details.
For the satellite links, the delay is rather long. In this case, the
preventive cyclic retransmission/error control method is adopted
in the MTP layer 2. It must be used to transmit signaling correctly
and fast. Therefore, set the data for the MTP.
When the link type is ATM, see Table 4-11 for parameter
description. For other parameter settings, see Table 4-10.

Table 4-10 Parameters of SAT64 kbit/s, NOR64 kbit/s and HSL

Parameter NOR64 kbit/s SAT64 kbit/s HSL

Timer index It indicates the index number of the timer value used by the local link. The
timer parameter value corresponding to this index is listed in the timer table.
The value of this parameter must be valid; otherwise, the related MTP
management processes cannot be carried out successfully.

Semi- It is the number of the semi-permanent connection mapping the link. The
permanent value is the returned index after the execution of the command ADD
connection TDMCONN. Before configuring the MTP link, you should configure the
number semi-permanent connection corresponding to the MTP link.

Bit reverse By default, it is set to No. When set to Yes, the high level and the low level
on the signaling link will be reversed.

Table 4-11 Parameters of ATM

Parameter ATM 2M

Virtual path This parameter defines the virtual path for data transmission. Value
identifier range is 0¨C3 and by default it is set to 0.

Virtual channel One virtual path contains multiple virtual channels which are used for
identifier data transmission. VCI defines the virtual channel in which the data is
transmitted. The identifier for each channel must be unique. The value
range of the channels is 0¨C255. By default, it is set to 1.

4-38 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Parameter ATM 2M

Flow type The flow type and the volume must be described at the source and
destination ends of each virtual connection. This parameter defines the
level of the data flow. By default, it is set to CBR.

AAL type AAL, used to transmit and receive data in the ATM, may be of different
kinds. This parameter defines the AAL type of the ATM 2-Mbit/s link.
By default, it is set to AAL5.

Related Commands

Table 4-12 Related commands for configuring the MTP link

Command Function

ADD N7LNK To add the MTP link

RMV N7LNK To remove the MTP link

MOD N7LNK To modify the MTP link

LST N7LNK To query the MTP link

NOTE

To modify an important parameter, you must first disconnect the link to be modified and then modify this
parameter. After the modification, connect the disconnected link. You can directly modify parameters that
are less important.

4.3 Configuration Examples

This section provides examples to describe how to configure the MTP data.

Networking Structure
As shown in Figure 4-14, the DSP is adjacent to the local SP and has no SCCP function, so the
signaling is uncharged.
Only one link set is required between the two offices, set Route selection field to 0. The link
set includes one 64-kbit/s normal link and one 2-Mbit/s HSL link, set Link selection field to
2.

Figure 4-14 Configuration example

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-39

Data Collection
The hardware description here specifies only the service boards and interface boards related to
the data in this example.

l Configure back slot 0 and back slot 1 with one SEPU each. Through the TDM semi-
permanent connection between different slots, all the links on the SEPUs are processed by
the SHPU.
l Configure the front slot 0 and front slot 1 with one SEPU each. The SBPU in slot 0 is
configured with a lower pinch card SHPU_2M. In this example, one 64-kbit/s normal link
and one 2-Mbit/s HSL link are configured on the same SHPU_2M card.

Retain the default values of the timer, alarm threshold and congestion threshold.

The records with the logic network index 0 are consistent with the DSP conditions, so the logic
network index uses the default value 0.

Table 4-13 shows the MTP data collection.

Table 4-13 Data collection table

Local SP code DSP code DSP type Whether DSPs are

adjacent or not

A1111A B1111B ITU Yes

Route selection field Link selection field SP code Signaling link type

0 2 0, 1 Two NOR64-kbit/s
links

Procedure
Step 1 Add the local office information.

To add local office information (OFI), set National network code to A1111A, SCCP
function to False, and Logic network index to 0, run the following command:
SET OFI: SN1=NM, SN2=NS, SN3=IM, SN4=IS, NPC="A1111A", SCCP=FALSE;

After the command is carried out, the local office signaling point index 0 is returned.

Step 2 Add the MTP DSP.

To add the MTP DSP, set DSP title to HW-A, National network code to B1111B, DSP
style to ITU, Route selection field to 0 (only one link set), SCCP function to NONE, and keep
the default values of other parameters, run the following command:
ADD N7DSP: DESC="HW-A", NPC="B1111B", SCCPUSED=NONE;

After the command is carried out, the DSP index 1 is returned.

Step 3 Add MTP link set

4-40 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

To add the MTP link set, set APX to 2, OFX to 0, NI to NM, and keep the default values of
other parameters, run the following command:
ADD N7LKS: APX=2, OFX=0, NI=NM;

Step 4 Add the MTP route.

To add MTP link set, set Adjacent SP index to 1, Local SP index to 0, Network indicator to
National network, Link selection field to 2 (two links in a group), and keep the default values
of other parameters, run the following command:
ADD N7RT: DESC="HW-A", LSX=0, DPX=1;

After the command is carried out, the link set index 0 is returned.
Step 5 Add the TDM semi-permanent connection
1. To add TDM SPC, set SPC name to toLINK1, SPC attribute to Signaling time slot
connection (STSL), Shelf number, Frame number, Slot number, Port number all to
0, Start time slot to 1, and Count of occupied time slot for adding 64-kbit/s normal link
to 1, run the following command:
ADD TDMCONN: HLN="toLINK1", HLA=STSL, FN=0, SHN=0, SN=0, E1P=0, TS=1,
TSN=1;

After the command is carried out, the semi-permanent connection index 0 is returned.
2. To query the idle time slot resource in the network, set Shelf number on source end,
Frame number on source end, Slot number on source end, Shelf number on
destination end, and Frame number on destination end all to 0, and Slot number on
destination end to 1, run the following command:
LST FREENETTS: SFN=0, SSHN=0, SSN=0, EFN=0, ESHN=0, ESN=1;

The start number of the query result is 64. The subsequent 64 time slot resources in the
network are all idle.
3. To add TDM SPC, set SPC name to toLINK2, SPC attribute to Signaling time slot
connection (STSL), Shelf number, Frame number, and Port number all to 0, Slot
number and Start time slot to 1, Count of occupied time slot for adding 2-Mbit/s HSL
link to 31, and Net time slot number to 64, run the following command:
ADD TDMCONN: HLN="toLINK2", HLA=STSL, FN=0, SHN=0, SN=1, E1P=0, TS=1,
TSN=1, NTN=64;

After the command is carried out, the semi-permanent connection index 1 is obtained.
Step 6 Add the MTP link
1. To add MTP link, set Link title to LINK1, Shelf number, Frame number, Slot
number of the SHPU_2M to 0, Location to DDB, Link type to NOR64 kbit/s, Link port
number to 16, Link set index to 0, Signaling link code to 0 (default value), Intra-set
priority, Timer index, and TDM SPC index all to 0, run the following command:
ADD N7LNK: LN="LINK2", FN=0, SHN=0, SN=0, LOC=DDB, CT=NOR64K, LPN=16,
LSX=0, HLN=0;
2. To add MTP link, set Link title to LINK2, Shelf number, Frame number, Slot
number of the SHPU_2M to 0, Location to DDB, Link type to HSL, Link port
number to 0, Link set index to 0, Signaling link code to 1, Intra-set priority and Timer
index to 0, and TDM SPC index to 1, run the following command:
ADD N7LNK: LN="LINK2", FN=0, SHN=0, SN=0, LOC=DDB, CT= NOR64K, LPN=0,
LSX=0, SLC=1, HLN=1;

----End

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-41

5 Configuring MTP Shielding Data

About This Chapter

This chapter describes how to configure the MTP shielding data. Before configuring the MTP
shielding data, make sure that the hardware data, local office data, and MTP data are configured.
Configure the data when it is required. If you do not require the MTP shielding function, you
can proceed to the next chapter.
To configure the SG7000 data, follow the procedure as shown in Figure 5-1. In this way, the
key fields are defined before they are referenced by other data tables and no junk data is
generated.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 5-1

Figure 5-1 Data configuration procedure

5.1 Configuration Preparations

This section describes the background information, technical terms, and configuration steps to
be studied before data configuration.
5.2 Configuring MTP Shielding Data
Configuring MTP shielding data includes adding the initial shielding table, adding the link set
shielding table, and configuring the prohibited OPC table.
5.3 Configuration Examples
This section provides examples to describe how to configure the MTP shielding data.

5-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

5.1 Configuration Preparations

This section describes the background information, technical terms, and configuration steps to
be studied before data configuration.
5.1.1 Terms
This section describes the terms used during configuring the MTP shielding data.
5.1.2 Networking Structure
The networking structure of configuring the MTP shielding data is the same as that of configuring
the MTP data.
5.1.3 Relation Between Data Tables
This section describes the relations between data tables related to MTP shielding data
configuration.
5.1.4 Data Collection
Set shielding conditions before configuring MTP shielding data. Select the shielding table
relating to the shielding condition first, and then confirm the shielding reference of this shielding
link.
5.1.5 General Steps
You must follow certain procedures to configure the MTP shielding data.

5.1.1 Terms
This section describes the terms used during configuring the MTP shielding data.
MTP shielding is a function of the MTP, which is used to discard the specific messages that
must not be transmitted. The specific message indicates that the message contents and related
information have some prescriptive features. Such information includes the following:
l Link set of the received message
l Link set of the message to be sent
l OPC in the message
l DPC in the message
l SIO in the message
l H0H1 in the message
l Information of related signaling point in the message

One or more items of these features can be combined together to control the object which has
multiple features.
In the SG7000, the MTP shielding is implemented by searching and matching the specified
message. The searching process compares the designated message with a serial of shielding
conditions (shielding links). If the conditions match, the operation specified in this table item is
executed; otherwise, the default operation is executed.

5.1.2 Networking Structure

The networking structure of configuring the MTP shielding data is the same as that of configuring
the MTP data.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 5-3

Figure 5-2 Networking through the MTP3 protocol

5.1.3 Relation Between Data Tables

This section describes the relations between data tables related to MTP shielding data
configuration.

Relation Between MTP Shielding Data and Other Data

The index of the MTP initial shielding table is indexed by Outgoing shielding index and
Incoming shielding index in the MTP link set table. For the relationship between parameters
and indices, see 4 Configuring MTP Data.

Internal Relation Between MTP Shielding Data Tables

Figure 5-3 shows the referencing relationship between parameters of the MTP shielding data
tables in this chapter. The figure is divided into three sub-figures to avoid line crossing. Thus,
you can see the figure more clearly.

l Part a in Figure 5-3 shows that the parameter Shielding reference of the N7DTFM table
and N7DSIO table can be indexed only by the shielding table above them, but cannot be
indexed by the shielding table under them.
l Part b in Figure 5-3 shows that the parameter Shielding reference of the N7ED table and
N7EO table can be indexed only by the shielding table above them, but cannot be indexed
by the shielding table under them.
l Part c in Figure 5-3 shows that the parameter Shielding reference of the N7DD table,
N7DO table and N7LSM table can be indexed only by the shielding table above them, but
cannot be indexed by the shielding table under them.

The eight shielding tables from top to bottom in the figure comprise different shielding chains.
For example:

l Initial shielding table (N7IM) → link set shielding table (N7LSM) → prohibited OPC table
(N7DO) → prohibited SIO table (N7DSIO) comprise a shielding chain.
l Initial shielding table (N7IM) → link set shielding table (N7LSM) → prohibited OPC table
(N7DO) → prohibited DPC table (N7DD) → prohibited TFM table (N7DTFM) comprise
a shielding chain.

It is recommended to add a shielding chain from bottom to top, that is, add the shielding table
(as shown in Figure 5-3) at the bottom first, and then add the shielding table above it. When
deleting a shielding chain, delete the shielding table at the top of the shielding chain, and then
delete the shielding table below it, because the referenced shielding table cannot be deleted.

5-4 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Figure 5-3 Data indices between MTP shielding data table

ADD N7IM ADD N7IM ADD N7IM

[ Next shielding ] Next shielding Next shielding

[ ] [ ]
reference reference reference

ADD N7LSM
ADD N7LSM ADD N7LSM
Shielding
[ ]
reference Shielding Shielding
[ ] [ ]
[ Next shielding ] reference reference
reference Next shielding Next shielding
[ ] [ ]
reference reference
ADD N7DO
Shielding
[ ] ADD N7DO ADD N7DO
reference
Next shielding Shielding Shielding
[ ] [ ] [ ]
reference reference reference
Next shielding Next shielding
[ ] [ ]
reference reference
ADD N7DD
Shielding
[ ]
reference
ADD N7DD ADD N7DD
Next shielding
[ ]
reference Shielding Shielding
[ ] [ ]
reference reference
ADD N7EO Next shielding Next shielding
[ ] [ ]
reference reference
Shielding
[ ]
reference
Next shielding ADD N7EO c
[ ]
reference
Shielding
[ ]
reference
ADD N7ED Next shielding
[ ]
Shielding reference
[ ]
reference
Next shielding
[ ] ADD N7ED
reference
Shielding
[ ]
ADD N7DSIO reference
Shielding Next shielding
[ ] [ ]
reference reference
Next shielding
[ ]
reference b

ADD N7ESIO
Shielding
[ ]
reference
Next shielding
[ ]
reference

ADD N7DTFM
Shielding
[ ]
reference

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 5-5

5.1.4 Data Collection

Set shielding conditions before configuring MTP shielding data. Select the shielding table
relating to the shielding condition first, and then confirm the shielding reference of this shielding
link.

Table 5-1 illustrates the data to be collected.

Table 5-1 Data collection table

Shielding tables to be added Shielding reference

5.1.5 General Steps

You must follow certain procedures to configure the MTP shielding data.

Configure the MTP shielding data from step 1 to step 8 in order, as shown in Table 5-2. The
last step is mandatory. The last step in each table is mandatory. Each table except for the last
refers to a shielding condition and thus they are optional. During configuration, configure one
or more required shielding tables according to the sequences as listed in Table 5-2.

Table 5-2 Steps to configure the MTP shielding data

Step Operation

1 To add the prohibited TFM (ADD N7DTFM)

2 To Add the allowed SIO (ADD N7ESIO)

3 To add the prohibited SIO (ADD N7DSIO)

4 To add the allowed DPC (ADD N7ED)

5 To add the allowed OPC (ADD N7EO)

6 To add the prohibited DPC (ADD N7DD)

7 To add the prohibited OPC (ADD N7DO)

8 To add the link set shielding (ADD N7LSM)

9 To add the initial shielding (ADD N7IM) (mandatory)

NOTE

After configuring the MTP shielding data, you complete the setting of shielding conditions only. You must
reference the index in the initial shielding table of the command ADD N7IM to Outgoing shielding table
index or Incoming shielding table index of the command ADD N7LKS to implement the MTP shielding
function. Refer to 5.3 Configuration Examples for the configuration method.

5-6 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

5.2 Configuring MTP Shielding Data

Configuring MTP shielding data includes adding the initial shielding table, adding the link set
shielding table, and configuring the prohibited OPC table.
5.2.1 Adding Prohibited TFM Table
It is used to specify the shielding conditions for the related signaling points in the signaling route
management messages (TFP, TFA, TFR and TFC). This table can only be used as the last table
of the shelding link tables.
5.2.2 Adding Allowed SIO Table
This section describes the command, parameter, and related commands for adding the allowed
SIO table.
5.2.3 Adding Prohibited SIO Table
This section describes how to configure screening conditions for a field which indicates the
message type, such as the SIO of a message.
5.2.4 Adding Allowed DPC Table
This section describes the allowed DPC sets.
5.2.5 Adding Allowed OPC Table
It is used to configure the set of OPCs allowed to pass. When the number of OPCs to be prohibited
is more, you can use this table to designate the set of OPCs allowed to simplify the data setting
process.
5.2.6 Adding Prohibited DPC Table
This section describes the command, parameter, and related commands for adding the prohibited
DPC table.
5.2.7 Adding Prohibited OPC Table
This section describes the command, parameter, and related commands for adding the prohibited
OPC table.
5.2.8 Adding Link Set Shielding Table
This section describes the command, parameter, and related commands for adding the link set
shielding table.
5.2.9 Adding Initial Shielding Table
This section describes the command, parameter, and related commands for adding the initial
shielding table.

5.2.1 Adding Prohibited TFM Table

It is used to specify the shielding conditions for the related signaling points in the signaling route
management messages (TFP, TFA, TFR and TFC). This table can only be used as the last table
of the shelding link tables.

Command
ADD N7DTFM

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 5-7

Parameter
Paramete Paramete Parameter Description
r ID r Name

MR Shielding Shielding reference is the flag for distinguishing the records under
reference different shielding conditions of the same table. For example,
setting link set shielding table serves for setting the shielding
conditions of different link sets. You can set Shielding
reference of the record whose link set index is 0 to 0, and that of
the record whose link set index is 1 to 1. The value range of the
shielding reference is from 0 to 65535.

NI Network It indicates the signaling network in which the object specified by

indication the shielding table item is located.

FO MIN. PC It indicates the minimum number of signaling point specified by

number this table item. The PC numbers, which are greater than or equal
to this value, but lesser than or equal to the MAX. PC number,
are the PC numbers controlled in this table.

TO MAX. PC It indicates the maximum number of the signaling point specified

number by this table item.

Related Commands

Table 5-3 Related commands for configuring the prohibited TFM table
Command Function

ADD N7DTFM To add the prohibited TFM

MOD N7DTFM To modify the prohibited TFM

RMV N7DTFM To remove the prohibited TFM

LST N7DTFM To query the prohibited TFM

5.2.2 Adding Allowed SIO Table

This section describes the command, parameter, and related commands for adding the allowed
SIO table.

Command
ADD N7ESIO

5-8 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Parameter
Parame Paramete Parameter Description
ter ID r Name

MR Shielding It is the flag for distinguishing the records under different shielding
reference conditions of the same table.
It is mandatory. Its value is of the numeral type and ranges 0-65535.

FSI MIN.SI They specify the values of the minimum and maximum service types
specified by this table item. The value ranges from 0 to 15.
TSI MAX.SI
l Value 0 stands for the signaling network management message.

l Value 1 stands for the signaling network test and maintenance

message.
l Value 2 is reserved.
l Value 3 stands for the message of signaling connection control
part.
l Value 4 stands for the TUP message.
l Value 5 stands for the ISUP message.
l Value 6 and 7 stand for the digital subscriber part message.
l Values 8-15 are reserved.
They are mandatory. The value is of the numeral type and ranges
0-15. The value of MIN.SI cannot be greater than that of MAX.SI.

FNI MIN.NI They specify the minimum and maximum values of the signaling
network in which the object specified by this shielding table item is
TNI MAX.NI located.
They are mandatory. The value ranges from 0 to 3.
l Value 0 stands for the international network.

l Value 1 stands for the international reserved network.

l Value 2 stands for the national network.
l Value 3 stands for the national reserved network.
The value of MIN.NI cannot be greater than that of MAX.NI.

FH0 MIN.H0 They specify the minimum and maximum values of H0 of the
message specified by this table item. The H0 is a field in the TUP
TH0 MAX.H0 message, used for indicating the category of message.
They are mandatory. The value is of the numeral type and ranges
0-15.
The value of MIN.H0 cannot be greater than that of MAX.H0.

FH1 MIN.H1 They specify the minimum and maximum values of H1 of the
message specified by this table item. The H1 is a field in the TUP
TH1 MAX.H1 message, used for indicating the type of message.
They are mandatory. The value is of the numeral type and ranges
0-15.
The value of MIN.H1 cannot be greater than that of MAX.H1.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 5-9

Parame Paramete Parameter Description

ter ID r Name

TTYPE Type of It, together with Next shielding reference, determines the
next subsequent shielding principle.
shielding It indicates the data of the table to be used for shielding in the next
table step. If it is not required to search the shielding data, it must be set
to END. Together with Next shielding reference, it decides the table
item set to be used in the next shielding. If a record in any of the
following tables is referenced by the allowed SIO table, the record
cannot be removed, and in addition, the value of Shielding
reference cannot be modified. The type of next shielding table of
allowed SIO table includes the following:
l END (End)
l DTT (Prohibited TFM table)
l M3MT (M3UA message type shielding table)
l M3RC (Route context shielding table)

NMR Next It indicates the index of the shielding reference in the next shielding
shielding table of the next step. Together with Type of next shielding table,
reference it decides the table item set used in the next shielding. If it is not
required to search the shielding date, you need not set this parameter.
This parameter must be configured in the shielding table in which
the Type of next shielding table parameter is configured. It is the
Shielding reference parameter of a record in the next shielding table.

Related Commands

Table 5-4 Related commands for configuring the allowed SIO table
Comman Function
d

ADD To add the allowed SIO

N7ESIO

MOD To modify the allowed SIO

N7ESIO

RMV To remove the allowed SIO

N7ESIO

LST To query the allowed SIO

N7DESIO

5.2.3 Adding Prohibited SIO Table

This section describes how to configure screening conditions for a field which indicates the
message type, such as the SIO of a message.

5-10 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Command
ADD N7DSIO

Parameter
Pa Pa Parameter Description
ra ra
m m
et et
er er
ID N
a
m
e

M Sh Shielding reference is the flag for distinguishing the records under different
R iel shielding conditions of the same table. For example, setting link set shielding table
di serves for setting the shielding conditions of different link sets. You can set
ng Shielding reference of the record whose link set index is 0 to 0, and that of the
ref record whose link set index is 1 to 1. The value range of the shielding reference
ere is from 0 to 65535.
nc
e

FS MI It indicates the value of the minimum service type specified by this table item. The
I N. value ranges from 0 to 15.
SI l Value 0 stands for the signaling network management message.
l Value 1 stands for the signaling network test and maintenance message.
l Value 2 is reserved.
l Value 3 stands for the message of signaling connection control part.
l Value 4 stands for the TUP message.
l Value 5 stands for the ISUP message.
l Value 6 and 7 stand for the digital subscriber part message.
l Values 8-15 are reserved.

TS M It indicates the value of the maximum service type specified by this table item.
I A The value range is the same as MIN.SI.
X.
SI

F MI It indicates the minimum value of the signaling network in which the object
NI N. specified by this shielding table item is located. The value ranges from 0 to 3.
NI l Value 0 stands for the international network.
l Value 1 stands for the international reserved network.
l Value 2 stands for the national network.
l Value 3 stands for the national reserved network.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 5-11

Pa Pa Parameter Description
ra ra
m m
et et
er er
ID N
a
m
e

T M It indicates the maximum value of the signaling network in which the object
NI A specified by this shielding table item is located. The value range is the same as
X. MIN.NI.
NI

F MI It indicates the minimum value of H0 of the message specified by this table item.
H0 N. The H0 is a field in the TUP message, used for indicating the category of message.
H0

T M It indicates the maximum value of H0 of the message specified by this table item.
H0 A
X.
H0

F MI It indicates the minimum value of H1 of the message specified by this table item.
H1 N. The H1 is a field in the TUP message, used for indicating the type of message.
H1

T M It indicates the maximum value of H1 of the message specified by this table item.
H1 A
X.
H1

TT Ty It, together with Next shielding reference, determines the subsequent shielding
Y pe principle.
PE of It indicates the data of the table to be used for shielding in the next step. If it is not
ne required to search the shielding data, it must be set to END. Together with Next
xt shielding reference, it decides the table item set to be used in the next shielding.
shi The type of next shielding table of prohibited SIO table includes the following:
eld
in l END (End)
g l EST (Allowed SIO table)
tab
l DTT (Prohibited TFM table)
le
l M3MT (M3UA message type shielding table)
l M3RC (Route context shielding table)

5-12 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Pa Pa Parameter Description
ra ra
m m
et et
er er
ID N
a
m
e

N Ne It indicates the index of the shielding reference in the next shielding table of the
M xt next step. Together with Type of next shielding table, it decides the table item
R shi set used in the next shielding. If it is not required to search the shielding date, you
eld need not set this parameter.
in
g
ref
ere
nc
e

Related Commands

Table 5-5 Related commands for configuring the prohibited SIO table
Command Function

ADD N7DSIO To add the prohibited SIO

MOD N7DSIO To modify the prohibited SIO

RMV N7DSIO To remove the prohibited SIO

LST N7DSIO To query the prohibited SIO

5.2.4 Adding Allowed DPC Table

This section describes the allowed DPC sets.

Command
ADD N7ED

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 5-13

Parameter
Pa Pa Parameter Description
ra ra
m m
et et
er er
I N
D a
m
e

NI N It indicates the signaling network in which the object specified by the shielding
et table item is located.
w
or
k
in
di
ca
tio
n

F M It indicates the minimum number of signaling point specified by this table item.
O IN The DPC numbers, which are greater than or equal to this value, but lesser than or
. equal to the MAX. DPC number, are the DPC numbers allowed in this table.
D
P
C
nu
m
be
r

T M It indicates the maximum number of the signaling point specified by this table
O A item. Together with the MIN. DPC number, it specifies the DPC numbers allowed
X. in this table.
D
P
C
nu
m
be
r

5-14 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Pa Pa Parameter Description
ra ra
m m
et et
er er
I N
D a
m
e

T Ty It, together with Next shielding reference, determines the subsequent shielding
T pe principle.
Y of It indicates the data of the table to be used for shielding in the next step. If it is not
P ne required to search the shielding data, it must be set to END. Together with Next
E xt shielding reference, it decides the table item set to be used in the next shielding.
sh The type of next shielding table of allowed DPC table includes the following:
iel
di l END (End)
ng l DST (Prohibited SIO table)
ta
l EST (Allowed SIO table)
bl
e l DTT (Prohibited TFM table)
l M3MT (M3UA message type shielding table)
l M3RC (Route context shielding table)

N N It indicates the index of the shielding reference in the next shielding table of the
M ex next step. Together with Type of next shielding table, it decides the table item
R t set used in the next shielding. If it is not required to search the shielding date, you
sh need not set this parameter.
iel
di
ng
ref
er
en
ce

Related Commands

Table 5-6 Related commands for configuring the allowed DPC table
Command Function

ADD N7ED To add the allowed DPC

MOD N7ED To modify the allowed DPC

RMV N7ED To remove the allowed DPC

LST N7ED To query the allowed DPC

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 5-15

5.2.5 Adding Allowed OPC Table

It is used to configure the set of OPCs allowed to pass. When the number of OPCs to be prohibited
is more, you can use this table to designate the set of OPCs allowed to simplify the data setting
process.
The following shielding table is not recommended for this table. If the following shielding table
is configured, the data in this table is only used to designate the set of OPCs as one of the
combined conditions. Such data can not prohibit or allow the OPCs, but the table items at the
end of a shielding link prohibit or allow the OPCs.

Command
ADD N7EO

Parameter
Paramete Paramete Parameter Description
r ID r Name

NI Network It indicates the signaling network in which the object specified by

indication the shielding table item is located.

FO MIN. It indicates the minimum number of signaling point specified by

OPC this table item. The OPC numbers which are greater than or equal
number to this value, but lesser than or equal to the MAX. OPC
number, are the OPC numbers allowed in this table.

TO MAX. It indicates the maximum number of the signaling point specified

OPC by this table item. Together with MIN. OPC number, it specifies
number the OPC numbers allowed in this table.

5-16 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Paramete Paramete Parameter Description

r ID r Name

TTYPE Type of It, together with Next shielding reference, determines the
next subsequent shielding principle.
shielding It indicates the data of the table to be used for shielding in the next
table step. If it is not required to search the shielding data, it must be set
to END. Together with the Next shielding reference, it decides
the table item set to be used in the next shielding. The type of next
shielding table of the allowed OPC table includes the following:
l END (End)
l EDT (Allowed DPC table)
l DST (Prohibited SIO table)
l EST (Allowed SIO table)
l DTT (Prohibited TFM table)
l M3MT (M3UA message type shielding table)
l M3RC (Route context shielding table)

NMR Next It indicates the index of the shielding reference in the next shielding
shielding table of the next step. Together with Type of next shielding
reference table, it decides the table item set used in the next shielding. If it
is not required to search the shielding date, you need not set this
parameter.

Related Commands

Table 5-7 Related commands for configuring the allowed OPC table

Command Function

ADD N7EO To add the allowed OPC

MOD N7EO To modify the allowed OPC

RMV N7EO To remove the allowed OPC

LST N7EO To query the allowed OPC

5.2.6 Adding Prohibited DPC Table

This section describes the command, parameter, and related commands for adding the prohibited
DPC table.

Command
ADD N7DD

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 5-17

Parameter
Paramete Paramete Parameter Description
r ID r Name

NI Network It indicates the signaling network in which the object specified by

indication the shielding table item is located.

FO MIN. It indicates the minimum number of the signaling point specified

OPC by this table item. The DPC numbers which are greater than or
number equal to this value, but lesser than or equal to the MAX. DPC
number, are the DPC numbers prohibited in this table.

TO MAX. It indicates the maximum number of the signaling point specified

OPC by this table item. Together with MIN. DPC number, it specifies
number the DPC numbers prohibited in this table.

TTYPE Type of It, together with Next shielding reference, determines the
next subsequent shielding principle.
shielding It indicates the data of the table to be used for shielding in the next
table step. If it is not required to search the shielding data, it must be set
to END. Together with Next shielding reference, it decides the
table item set to be used in the next shielding. The type of next
shielding table of the prohibited DPC table includes the following:
l END (End)
l EOT (Allowed OPC table)
l EDT (Allowed DPC table)
l DST (Prohibited SIO table)
l EST (Allowed SIO table)
l DTT (Prohibited TFM table)
l M3MT (M3UA message type shielding table)
l M3RC (Route context shielding table)

5-18 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Related Commands

Table 5-8 Related commands for configuring the prohibited DPC table
Command Function

ADD N7DD To add the prohibited DPC

MOD N7DD To modify the prohibited DPC

RMV N7DD To remove the prohibited DPC

LST N7DD To query the prohibited DPC

5.2.7 Adding Prohibited OPC Table

This section describes the command, parameter, and related commands for adding the prohibited
OPC table.

Command
ADD N7DO

Parameter
Paramete Paramete Parameter Description
r ID r Name

NI Network It indicates the signaling network in which the object specified by

indication the shielding table item is located.

FO MIN. It indicates the minimum number of the signaling point specified

OPC by this table item. The numbers are greater than or equal to MIN.
number OPC number, but lesser than or equal to the MAX. OPC
number.

TO MAX. It indicates the maximum number of the signaling point specified

OPC by this table item. Together with MIN. OPC number, it specifies
number the OPC numbers prohibited in this table.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 5-19

Paramete Paramete Parameter Description

r ID r Name

TTYPE Type of It, together with Next shielding reference, determines the
next subsequent shielding principle.
shielding It indicates the data of the table to be used for shielding in the next
table step. If it is not required to search the shielding data, it must be set
to END. Together with the Next shielding reference, it decides
the table item set to be used in the next shielding. The type of next
shielding table of the prohibited OPC table includes the following:
l END (End)
l DDT (Prohibited DPC table)
l EOT (Allowed OPC table)
l EDT (Allowed DPC table)
l DST (Prohibited SIO table)
l EST (Allowed SIO table)
l DTT (Prohibited TFM table)
l M3MT (M3UA message type shielding table)
l M3RC (Route context shielding table)

Related Commands

Table 5-9 Related commands for configuring the prohibited OPC table
Command Function

ADD N7DO To add the prohibited OPC

MOD N7DO To modify the prohibited OPC

RMV N7DO To remove the prohibited OPC

LST N7DO To query the prohibited OPC

5.2.8 Adding Link Set Shielding Table

This section describes the command, parameter, and related commands for adding the link set
shielding table.

5-20 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Command
ADD N7LSM

Parameter
Par Par Parameter Description
ame ame
ter ter
ID Na
me

MR Shie Shielding reference is the flag for distinguishing the records under different
ldin shielding conditions of the same table. For example, setting link set shielding
g table serves for setting the shielding conditions of different link sets. You can
refer set Shielding reference of the record whose link set index is 0 to 0, and that
ence of the record whose link set index is 1 to 1. The value range of the shielding
reference is from 0 to 65535.

LSX Link It indicates the index of the outgoing link set related to this shielding table
set item. When this table item is used for the first time, and if the tested message
inde uses an outgoing link set index that is different from this index value, it is
x unrelated to this shielding table item.

TTY Typ It, together with Next shielding reference, determines the subsequent
PE e of shielding principle.
next It indicates the data of the table to be used for shielding in the next step. If it
shiel is it is not required to search the shielding data, it must be set to END. The
ding type of next shielding table of the link set shielding table includes the
table following:
l END (End)
l DOT (Prohibited OPC table)
l DDT (Prohibited DPC table)
l EOT (Allowed OPC table)
l EDT (Allowed DPC table)
l DST (Prohibited SIO table)
l EST (Allowed SIO table)
l DTT (Prohibited TFM table)
l M3MT (M3UA message type shielding table)
l M3RC (Route context shielding table)

NM Next It indicates the index of the shielding reference in the next shielding table of
R shiel the next step. Together with Type of next shielding table, it decides the table
ding item set used in the next shielding. If it is not required to search the shielding
refer date, you need not set this parameter.
ence

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 5-21

Related Commands

Table 5-10 Related commands for configuring the link set shielding table
Command Function

ADD N7LSM To add the link set shielding

MOD N7LSM To modify the link set shielding

RMV N7LSM To remove the link set shielding

LST N7LSM To query the link set shielding

5.2.9 Adding Initial Shielding Table

This section describes the command, parameter, and related commands for adding the initial
shielding table.

NOTE

The initial shielding table is the public shielding condition of all the incoming links. Its index value is 0.
Therefore, it cannot be indexed by the Incoming shielding table index and Outgoing shielding table
index of the command ADD N7LKS to act as the shielding condition of a certain link set. The Incoming
shielding table index and Outgoing shielding table index can only index the initial shielding table the
index value of which is not 0.

Command
ADD N7IM

5-22 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Parameter
Parame Paramete Parameter Description
ter ID r Name

TTYPE Type of It, together with Next shielding reference, determines the
next subsequent shielding principle.
shielding It indicates the data of the table to be used in shielding. If it is not
table required to search the shielding data, it must be set to END. The type
of next shielding table of the initial shielding table includes the
following:
l END (End)
l LSMT (Link set shielding table)
l DOT (Prohibited OPC table)
l DDT (Prohibited DPC table)
l EOT (Allowed OPC table)
l EDT (Allowed DPC table)
l DST (Prohibited SIO table)
l EST (Allowed SIO table)
l DTT (Prohibited TFM table)
l M3MT (M3UA message type shielding table)
l M3RC (Route context shielding table)

MODE Screen It specifies whether the system screens the message and reports the
mode result.
Its value is of the enumeration type. It can be set to:
l No screening
l Screen and don't report
l Screen and report
It is set to No screening by default. To record messages, you must
set this parameter to Screen and report and set the Record file
creation switch in the SET CREATRFILE command to Open.

Related Commands

Table 5-11 Related commands for configuring the initial shielding table

Command Function

ADD N7IM To add the initial shielding

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 5-23

Command Function

MOD N7IM To modify the initial shielding

RMV N7IM To remove the initial shielding

LST N7IM To query the initial shielding

5.3 Configuration Examples

This section provides examples to describe how to configure the MTP shielding data.

Assumption
The shielding condition is shielding the messages sent from the link of the link set, the index
value of which is 0.

Table 5-12 Data collection table

Shielding tables to be added Shielding reference

Initial shielding table and link set shielding 0

table

Procedure
Step 1 Add the initial shielding table. The initial shielding table indexed 0, is the public shielding
condition, so you can use the default value to generate an initial shielding table record indexed
0. Then, add the initial shielding table.
ADD N7IM:;

Step 2 Add the link set shielding table, with the shielding reference value of 0, link set type of MTP3,
and link set index value of 0.
ADD N7LSM: MR=0, LSTYPE=MTP3, LSX=0;

Step 3 Add the link set shielding table, the shielding reference value of which is 0. Obtain index 1 after
running the command.
ADD N7IM: TTYPE=LSMT, NMR=0, MASK=TRUE;

Step 4 Set the index 1 of the initial shielding table to the Outgoing shielding table index of link set 0.
MOD N7LKS: IDX=0, OSX=1;

----End

5-24 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

6 Configuring SCCP Data

About This Chapter

This chapter describes how to configure the SCCP data. The SCCP data is used to set the
information relevant to the SCCP message route addressing when the SG7000 interconnects
with the STP or LS. The information includes the SCCP destination signaling point, SCCP
subsystem, global title, and GT work mode. Before configuring the SCCP data, ensure that the
hardware data, local office data, and MTP data are configured.
To configure the SG7000 data, follow the procedure as shown in Figure 6-1. In this way, the
key fields are defined before they are referenced by other data tables and no junk data is
generated.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 6-1

Figure 6-1 Data configuration procedure

6.1 Configuration Preparations

This section describes the background information, technical terms, and configuration steps to
be studied before data configuration.
6.2 Configuring SCCP Data
Configuring the SCCP data includes adding the SCCP subsystem, adding the new GT, adding
the SCCP calling number range, and adding the global GT.
6.3 Configuration Examples
This section provides examples to describe how to configure the SCCP data.

6-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

6.1 Configuration Preparations

This section describes the background information, technical terms, and configuration steps to
be studied before data configuration.
6.1.1 Terms
This section describes the terms used during configuring the SCCP data.
6.1.2 Networking Structure
This section describes the networking structure for configuring the SCCP data.
6.1.3 Relation Between Data Tables
This section describes the relations between data tables related to SCCP data configuration.
6.1.4 Data Collection
Before configuring the SCCP data, you must collect the data including the network indication,
GT type, translation result, and numbering plan.
6.1.5 Configuration Principles
You must follow certain procedures to configure the SCCP data.
6.1.6 General Steps
You must follow certain procedures to configure the SCCP data.

6.1.1 Terms
This section describes the terms used during configuring the SCCP data.

SCCP

SCCP is the signaling connection control part in SS7.

The SS7 meets the requirements for communicating and transmitting the information relevant
to the connection, according to the proposal issued in 1980. Therefore, only the requirements of
four function levels are put forward. With the development of the ISDN and intelligent network,
however, it is necessary to transmit the information relevant to the circuit connection and some
other information. For example, the end-to-end information is used in maintenance management
for ISDN users. Thus, the original MTP function cannot meet the demands. Under this condition,
the SCCP is added in the revision made in 1984, to enhance the MTP function without modifying
the MTP, so that the requirements for transmitting end-to-end information oriented to the
connection or non-connection can be met. In this case, the SS7 must meet the requirements of
the four function levels and thus MTP, and SCCP are together called the network service part
(NSP).

Subsystem Number (SSN)

The subsystem number (SSN) is used to identify different SCCP users of the same node, such
as the ISDN user part (ISUP), mobile application part (MAP), and transaction capability
application part (TCAP). The requirements for new services can be met by adding more users
and the expanding the addressing scope.

On receiving an SCCP message, a destination SCCP point cannot send the message to a user
until it gets the SSN of the message. Therefore, if the SCCP message includes no SSN, the SCCP

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 6-3

must refer the GT translation table to get the SSN according to the GT (see below for its
definition) in the message.

GT
The global title (GT) codes, for example international telephone number, national telephone
number, and ISDN number, do not indicate the route information in its signaling network, so
the route information can be obtained only through GT translation.
DPC is significant only in the national or international SS7 network where it is defined, but not
globally significant. The GT has global significance and its address scope is much larger than
that of DPC. It facilitates the transmission of messages irrelevant to circuit between any two
signaling points in the world. The powerful addressing ability of GT is an important characteristic
of SCCP.
There are four formats for using GTs. At present, GT4 is commonly used. Table 6-1 illustrates
the structure of GT4.

Table 6-1 Structure of GT4

Byte Bit

8-5 4-1

The first byte GT indicator

The second byte Translation type

The third byte Numbering plan Encoding scheme

The fourth byte Free Nature of the address indicator

After the fourth byte Address information

The first byte indicates the format of the GT. This type is called the GT indicator. The valid
values of the GT indicator are 1, 2, 3, and 4. Other values are invalid.
l If the GT indicator is 1, the global title consists of the Nature of address indicator and
Global title address information. It is type-1 GT.
l If the GT indicator is 2, the global title consists of the Translation type and Global title
address information. It is type-2 GT.
l If the GT indicator is 3, the global title consists of the Translation type, Numbering
plan, Encoding scheme, and Global title address information. It is type-3 GT.
l If the GT indicator is 4, the global title consists of the Translation type, Numbering
plan, Encoding scheme, Nature of address indicator, and Global title address
information. It is type-4 GT.
The second byte indicates the translation type.
Bit8-Bit5 of the third byte indicate the numbering plan. That is, the way in which the address
information is numbered.
Bit4-Bit1 of the third byte indicate the encoding scheme. They indicate whether the address
information length is odd or even. 1 stands for an odd number and 2 stands for an even number.

6-4 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

The fourth byte indicates the address information indicator, that is, the attribute of address
information.

The fifth byte and the subsequent ones indicate the address information, that is, the telephone
number. Write 1111 for the higher four bits of the last byte at the end of the address information,
if the address information length is odd.

Example:

GT: 04006101214365F7

It means that the GT indicator is 4 and translation type is 0 (only 0 is allowed at present). The
code plan is the land move code plan (code 6). The encoding scheme is 0001 (that is, 1) because
the address information length is odd. The nature of address indicator is the subscriber number
(code 1). The global title address information is 1234567.

SCCP Addressing Mode

The address type indicator in the SCCP global title address information indicates the SCCP
addressing mode. The two SCCP addressing modes are as follows:

l Addressing by DPC: The message is sent to the SCCP user message destination and requires
no transfer through the SCCP.
l Addressing by GT: The message is sent to the SCCP transfer point, but not to the user
message destination directly.

SCCP Routing Principles

The SCCP connectionless service is used in the intelligent network application protocol (INAP),
CAP, and MAP. The SCCP routing principle under non-connection condition; therefore is
described in this manual.

The routing principles for connectionless SCCP messages sent by the local SCCP users are as
follows:

l If the SCCP address includes the DPC, and the DPC is not a local node, the MTP sends the
signaling message to the destination signaling point according to the type of DPC. If the
DPC is the local node, the message is returned to the local SSN.
l If the SCCP address does not include the DPC, the system refers the GT translation table
to get the DPC, and then takes measures as mentioned above.
l The routing principles for connectionless SCCP messages received by the MTP are as
follows:
– If the routing indicator is 1 (addressing by DPC), it means that the local node is the
destination of the message. The signaling message is sent to the local node SSN in this
case.
– If the routing indicator is 0 (addressing by GT), the system refers the GT translation
table to get the DPC. If the DPC is a local node, the message is sent to the local SSN;
if the DPC is not a local node, the system flags an SIF route notation to the signaling
message and the MTP sends it to the destination signaling point according to the type
of DPC.

GT Translation Result Indicator

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 6-5

When the SCCP requests the MTP to send messages, the SCCP users must provide the DPC of
the next network node. If not, the SCCP must translate the callee's GT into the information with
the DPC, and then transfers it to the MTP.

The GT translation result indicator indicates the format of the translation result after a GT is
translated by the local SCCP. There are four types of GT formats:

l DPC + SSN: Indicating that the translation result is of "DPC + SSN" form.
l DPC + GT: Indicating that the translation result is of "DPC + GT" form.
l DPC + new GT index: Indicating that the translation result is of "DPC + new GT index"
form.
l DPC: Indicating that the translation result is of "DPC" form.

For more details, see 6.1.5 Configuration Principles.

SCCP Multipoint Load Sharing

SCCP multipoint load sharing means that a maximum of sixteen points (including active and
standby points) share the load in GT addressing mode, according to different policies. Load
sharing can be achieved according to the message SLS, incoming link index, message OPC,
message caller number, and TID message.

Address Information

It indicates the subscriber number to be performed GT translation. It consists of the country

code, toll area code, and user number. The length of the number cannot be longer than 24 digits.
For example, in the address information 8675528960132, 86 is the country code, 755 is the toll
area code, and 28960132 is the user number.

The address information can also be expressed by characters A - E, where, A, B, C, and D indicate
the actual values. The value of E is defined by the Wildcard function in GTT parameter in the
SET SOFTCFG2 command. When Wildcard function in GTT is set to close, E is an ordinary
character; when Wildcard function in GTT is set to open, E is a wildcard and can be used only
in the last second, third, or fourth bit. For example, when address Information is set to
86755289EAEEC, it indicates all numbers with the prefix "86755289E" and trailer "C".

Message TID Load Sharing

6.1.2 Networking Structure

This section describes the networking structure for configuring the SCCP data.

As shown in Figure 6-2, the SG7000 connects the STP or LS through the SCCP. When PSTN
users are the ISDN users, the equipment can be connected through the SCCP.

6-6 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Figure 6-2 Networking of configuring SCCP data

6.1.3 Relation Between Data Tables

This section describes the relations between data tables related to SCCP data configuration.

For the referencing relationship between parameters of the SCCP data tables, see Figure 6-3.
The figure shows the GT added with ADD SCCPGT. Under this condition, if the SCCP's work
mode is configured to the single point, reference the DPC index, SSN code, and New GT
index. If the SCCP's work mode is configured to the multipoint work mode, reference the Index
of SCCP addressing policy and New GT index.

Figure 6-3 Relations between the SCCP data tables

ADD SCCPGT
ADD N7DSP
[ DPC index ] [ Index ]
[ DPC title ] [ DSP title ]

ADD SCCPSSN
[ SSN code ] [ SSN code ]
[ DPC title ] ADD SCCPGGTSEG
ADD SCCPNGT [ Segment index ]
[ New GT index ] [ New GT index ]
[ New GT title ] [ New GT title ]
ADD SCCPOPCRANGE
[ GT work mode ] ADD SCCPADDRPL
=MTWM [ Segment index ]
[ Index of SCCP ] [Index of SCCP addressing Policy]
addressing Policy
SCCP addressing ADD SCCPOPCLSS
[ policy title ] [ SCCP addressing policy title ]
Index of load-share
[Type of load-share=SLS] [ ]
Select Set
[Type of load-share=LIDX] [ Segment index ]
[Type of load-share=OPC]
[Index of load-share select set] ADD SCCPOPCLSS
[Type of load-share=LING]
Index of load-share
[Index of load-share select set] [ select set ]
[Type of load-share=TID ] [ Segment index ]

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 6-7

For more details, see 6.2 Configuring SCCP Data.

6.1.4 Data Collection

Before configuring the SCCP data, you must collect the data including the network indication,
GT type, translation result, and numbering plan.
Table 6-2 lists the data required to configure the SCCP data. Some optional data is not listed in
the table.

Table 6-2 Data collection table

Network Translation result GT type Numbering plan
indication type

GT work mode SSN code (optional) Address attribute Address

indication information
(optional)

6.1.5 Configuration Principles

You must follow certain procedures to configure the SCCP data.

Selecting GT Translation Result Type

If the SG7000 is located in different networks, the GT translation result types are different. The
corresponding relationship between the SG7000 networking and GT translation result type is as
follows:

l "DPC + GT"
This translation type is used when an SCCP message transfer point is required between the
local point and the SCCP message destination point. Figure 6-4 shows the networking
structure.

Figure 6-4 Structure 1

In structure 1, when the SCCP message to be sent to SP B reaches SG A, the SG A translates

the GT in the SCCP message to obtain the route from SG B to SP B, because the SG A has
no MTP route reaching the SP B. At the same time, the SG B needs to forward the message
according to the GT in the SCCP message. Therefore, set the GT translation type to "DPC

6-8 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

+GT" when setting the GT translation table on the SG A. The DPC is the signaling point
code of the SG B.
Thus, the SCCP message contains the original GT when it is sent to the SG B. After it is
configured with the SCCP translation data, the SG B transfers the SCCP message from
SG A to SP B.
l "DPC + new GT"

This translation type is used when an SCCP message transfer point is required between a
local signaling point and a destination signaling point, and the GT requires translation.
In structure 1, as shown in Figure 6-4, if the GT of a user of the SP B is changed (for
example, GT type is changed) for SG B, set the changed GT in the message at SG A. In
this way, the message can be translated correctly at the SG B and transferred to the user of
the SP B. In such a condition, the translation type of "DPC + new GT" must be used in the
GT translation table of the SG A and the new GT must be replaced with that required by
the SG B.
l "DPC + SSN"

This translation type is used when no SCCP message transfer is required between the local
point and SCCP message destination, but the SCCP message does not include the SSN.
Figure 6-5 shows the structure.

Figure 6-5 Structure 2

In structure 2, assume that the SG A knows the DPC of the SP A and the MTP route reaching
the SP A exists, but the SCCP message sent by the SP A does not include the SSN
information. Under this condition, the GT translation type of the SP A can be set as "DPC
+ SSN" on the SG A. After receiving the DPC of the SP A, the SG A sends the message to
the MTP, which transfers it to the SP A. Then the SP A sends the message to the appropriate
SCCP user according to the SSN.
l "DPC"

This translation type is used when no SCCP message transfer is required between the local
point and the SCCP message destination, and the SCCP message includes the SSN. The
structure is shown in Figure 6-5.
In structure 2, assume that the SG A identifies the DPC of the SP A and the MTP route
reaching the SP A exists, but the SCCP message includes the SSN information. The GT
translation type of the SP A can be set to "DPC" on the SG A. Thus the message can be
sent to the SP A through the MTP. The SCCP of the SP A sends the message to the
appropriate SCCP user according to the SSN.

GT Compression

The SG7000 utilizes the "front" matching method for the translation of GT, which greatly
increases the quantity of global titles actually processed and simplifies the process of adding the
GT translation table.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 6-9

To configure a group of GTs in the SG7000 at a time, you can compress a group of relevant GTs
according to some rules. By this way, you need only to configure a GT record to the GT
translation table, but not to add each GT to the GT translation table.

Some examples regarding different translation types are as follows:

l The translation type is "DPC + GT" or "DPC".

For this type of GTs, if the DPCs in the translation results are the same, the appropriate
"combination" processing can be performed. For example, assume that there are two such
GTs:
a = 04004201123456
b = 0400420112345789
If the DPCs of the translation results are the same, the GT c can replace the GTs a and b if
no other GT equals c (0400420112345).
l The translation type is "DPC + new GT" or "DPC + SSN".
This type of GTs cannot be "combined", while appropriate "truncate" operation can be
performed on them according to the actual requirements. For example, there is one such
GT:
d = 040042013333312345
The last four digits of the GT d are the same as that of the GT c. If no other GT equals e
(04004201333331234), the GT e can replace the GT d, that is, the tail of the GT d is "cut".
In this way, the case of more than four digits repeated can be avoided to improve the retrieval
efficiency of the GTs by the system.
l If a GT is "combined" or "compressed", the appropriate information regarding the modified
GT should be reserved for further check by the GT addition.

Load-Share Select Mask

The SCCP can support a maximum of 16 load sharing signaling points. Load-share select
mask is an important parameter used in addressing to share the load evenly among multiple
signaling points that support the SCCP.

Different parameters can be used together with Load-share select mask in addressing
calculation based on the different load sharing types.

l If the type of load sharing is "message SLS load sharing", you can obtain the destination
load sharing signaling point by calculating Load-share select mask and the SLS in the
signaling message.
l If the type of load sharing is "incoming link index load sharing", you can obtain the
destination load sharing signaling point by calculating Load-share select mask and the
incoming link index in the signaling message.
l If the type of load sharing is "caller load sharing", you can obtain the destination load
sharing signaling point by calculating Load-share select mask and the caller GT in the
signaling message. The use of the caller GT is determined by the configuration made
through the command ADD SCCPCGGTSEG.
l If the type of load sharing is "OPC load sharing", you can obtain the destination load sharing
signaling point by calculating Load-share select mask and the OPC in the signaling
message. The use of the OPC is determined by the command ADD SCCPOPCRANGE.

6-10 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

l When TID (TID load-share of message) is selected for the load sharing mode, the TID
contained in the signaling message is used together with the number of reachable load-
sharing signaling points to calculate the destination load-sharing signaling points.

The addressing calculation of load sharing is as follows:

A is the load sharing select mask, B is the parameter used based on different load sharing types,
and D is the reachable load sharing signaling point.

1. AND is the binary value of A and B. Delete 0 (related to the mask) from the result, thus
getting the result C.
2. If D is the number of reachable load sharing signaling points, divide the decimal value of
the result C by D and get the remainder. If the value of C is lesser than D, the last result is
C.
3. The value last obtained is the index of the DSP in the SCCP addressing policy table.

Example:

If the load sharing select mask is 5 (0101), and B is 12 (1100), the load sharing signaling point
is 4.

1. As shown in Figure 6-6, calculate AND for 0101 and 1100 to obtain 0100. Delete 0 from
the result and arrange 1 from the last bit to first bit, thus getting a binary value 10.

Figure 6-6 Step 1 of load sharing algorithm

1100
AND algorithm 0101
Obtain the bits 0100
corresponding to "1"
in the mask code 0101
Arrange from 1 0
the last bit
0010

2. The decimal value of the result 0010 obtained is 2, that is, 2%4 = 2.
Therefore, the reachable signaling point, which has an index of 3, is the DSP obtained by
calculating the signaling message in the load sharing algorithm.

The load sharing addressing algorithm for "TID load-share of message" is as follows:
l For 4-byte TID:
1. Obtain the most significant bit of every byte of the TID and sum up the bits to get A.
Perform modulo operation on A and the number of reachable load-sharing signaling
points B to get C.
2. C is the index of the destination signaling point in the SCCP addressing policy table.
l For 8-byte TID:
1. Obtain the most significant bit of every byte of the TID and sum up the bits to get A.
Perform modulo operation on A and the number of reachable load-sharing signaling

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 6-11

points, and then calculate the switchover between 4 bits and 8 bits through dummy
messages to get C.
2. C is the index of the destination signaling point in the SCCP addressing policy table.

Example: Assume that the TID is 12345678 and the number of reachable load-sharing signaling
points is 16.
1. Obtain the most significant bit of every byte of the TID and sum up the bits: 1 + 2 + 3 + 4
+ 5 + 6 + 7 + 8 = 36. Then, perform modulo operation on A and the number of reachable
load-sharing signaling points: 36%16=4.
2. Through the load-sharing algorithm, the calculated destination signaling point is the
reachable signaling point with index 4.

6.1.6 General Steps

You must follow certain procedures to configure the SCCP data.

The SCCP supports the single point mode and multipoint load sharing mode. The multipoint
load sharing mode is divided into four types of work modes according to the differences of load
sharing select modes. Table 6-3, Table 6-4, Table 6-5, and Table 6-6 describe the steps for
configuring the SCCP data in different work modes. Refer to 3 Configuring Local Office
Data for the configuration of local information table, and refer to 4 Configuring MTP Data
for the configuration of destination signaling point table. This chapter describes the configuration
from step 3.

NOTE

During the configuration of SCCP data, if you configure the local office information with the command
SET OFI or ADD OPC, you must set SCCP FUNCTION to TRUE.

Based on the situations of the SCCP data configuration, the following configuration steps are
optional:

l The step "adding the SCCP subsystem" (ADD SCCPSSN) is optional. If GT translation
result type in the step "adding the global GT" is set to DPC or DPC+SSN, the step "adding
the SCCP subsystem" must be performed; otherwise, it is unnecessary.
l The step "adding the new GT" (ADD SCCPNGT) is optional. If GT translation result
type in the step "adding the global GT" is set to DPC+NEWGT, the step "adding the new
GT" must be performed; otherwise, it is unnecessary.

Configuration Steps in Single Point Work Mode

Table 6-3 Configuring the SCCP to single point work mode

Step Operation

1 To add the local office information table (SET OFI or ADD OPC)

2 To add the DSP table (ADD N7DSP)

3 To add the SCCP subsystem (ADD SCCPSSN) (optional)

4 To add the new GT (ADD SCCPNGT) (optional)

5 To add the SCCP OPC segment (ADD SCCPOPCRANGE)

6-12 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Step Operation

6 To add the SCCP OPC load-share select set (ADD SCCPOPCLSS)

7 To add the SCCP addressing policy (ADD SCCPADDRPL)

8 To add the GT (ADD SCCPGT)

Configuration Steps in Multipoint Work Mode

There are four types of load sharing when the SCCP is configured to multipoint load sharing
work mode.
l When the load sharing type is SLS or LIDX or TID, see Table 6-4 for the configuration
steps.
l When the load sharing type is OPC, see Table 6-5 for the configuration steps.
l When the load sharing type is CLNG, see Table 6-6 for the configuration steps.

Table 6-4 Configuring the SCCP to SLS or LIDX or TID load sharing mode
Step Operation

1 To add the local office information table (SET OFI or ADD OPC)

2 To add the DSP table (ADD N7DSP)

3 To add the SCCP subsystem (ADD SCCPSSN) (optional)

4 To add the new GT (ADD SCCPNGT) (optional)

5 To add the SCCP addressing policy (ADD SCCPADDRPL)

6 To add the GT (ADD SCCPGT)

Table 6-5 Configuring the SCCP to OPC load sharing mode

Step Operation

1 To add the local office information table (SET OFI or ADD OPC)

2 To add the DSP table (ADD N7DSP)

3 To add the SCCP subsystem (ADD SCCPSSN) (optional)

4 To add the new GT (ADD SCCPNGT) (optional)

5 To add the OPC section range (ADD SCCPOPCRANGE)

6 To add the SCCP OPC load-share select set (ADD SCCPOPCLSS)

7 To add the SCCP addressing policy (ADD SCCPADDRPL)

8 To add the GT (ADD SCCPGT)

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 6-13

Table 6-6 Configuring SCCP to CLNG load sharing mode

Step Operation

1 To add the local office information table (SET OFI or ADD OPC)

2 To add the DSP table (ADD N7DSP)

3 To add the SCCP subsystem (ADD SCCPSSN) (optional)

4 To add the new GT (ADD SCCPNGT) (optional)

5 To add the SCCP calling GT segment (ADD SCCPCGGTSEG)

6 To add the SCCP calling GT load-share select set (ADD SCCPCGGTLSS)

7 To add the SCCP addressing policy (ADD SCCPADDRPL)

8 To add the GT (ADD SCCPGT)

6.2 Configuring SCCP Data

Configuring the SCCP data includes adding the SCCP subsystem, adding the new GT, adding
the SCCP calling number range, and adding the global GT.
6.2.1 Adding SCCP Subsystem (Optional)
This operation must be performed only when Translation result type in the ADD SCCPGT is
set to DPC or DPC+SSN.
6.2.2 Adding New Global Title (GT) (Optional)
This command is used only when the Translation result type in the GT table SCCPGT is DPC
+NEWGT.
6.2.3 Adding SCCP Calling GT Segment (Optional)
This command is used only when Type of load-share in the SCCP addressing policy table
SCCPADDRPL is CLNG (Load-share according to calling GT).
6.2.4 Adding Calling GT Load-Share Select Set (Optional)
This command is used only when Type of load-share in the SCCP addressing policy table
SCCPADDRPL is CLNG (Load-share according to calling GT).
6.2.5 Adding OPC Section Range (Optional)
This command is used only when Type of load-share in the SCCP addressing policy table
SCCPADDRPL is OPC (Load-share according to OPC).
6.2.6 Adding OPC Load-Share Select Set (Optional)
This command is used only when Type of load-share in the SCCP addressing policy table
SCCPADDRPL is OPC (Load-share according to OPC).
6.2.7 Adding SCCP Addressing Policy (Optional)
This command is used only when GT work mode in the GT table SCCPGT is MTWM (Multi-
point work mode).
6.2.8 Adding GT
This section describes the command, parameter, and related commands for adding the GT. The
GT table supports a maximum of 200,000 records

6-14 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

6.2.1 Adding SCCP Subsystem (Optional)

This operation must be performed only when Translation result type in the ADD SCCPGT is
set to DPC or DPC+SSN.

Command
ADD SCCPSSN

Parameter
Paramete Paramete Parameter Description
r ID r Name

NI Network It specifies the signaling network where the signaling point of the
number of SSN user is located. It may be:
the l IM (International)
subsystem
l IS (International reserved)
l NM (National)
l NS (National reserved)

SSN SSN code It is the addressing information for SCCP users used by the SCCP.
It distinguishes different SCCP users in the same node. It is an 8-
bit code. The SG7000 supports the following SCCP user parts:
l 1-SCMG:SCCP management
l 2-RESERVED:Reserved
l 3-ISUP:ISDN user part
l 4-OMAP:Operation, maintenance and administration part
OMAP
l 5-MAP:MAP application part
l 6-HLR:Home location register
l 7-VLR:Visitor location register
l 8-MSC:Mobile switching center
l 9-EIC:Equipment identity register
l 10-AUC:Authentication center
l 11-RESERVED:Reserved
l 12-INAP:Intelligent network application part
l Others are for extended reserved users.

DX DPC It is the referenced DPC after translation. The corresponding DPC

index is referenced in the destination signaling point table.
It is mandatory. Its value is of the numeral type. Its value range is
0-65535. The value 65534 indicates the local office.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 6-15

Paramete Paramete Parameter Description

r ID r Name

DT DPC title It specifies the name of the destination signaling point code to be
referenced after the translation from the destination signaling point
table.
Note: A local SP cannot be added according to the DPC name.
It is optional. Its value is of the character type and can contain up
to 40 characters.

RLS1-5 Related They indicate the local subsystem numbers relative with the
local subsystem.
subsystem
1-5

BX Backup It indicates the index value of the backup subsystem. If the

subsystem subsystem has no backup subsystem, its value is 65535.
index During the configuration of the backup subsystem index, the
subsystem must work in the active and standby mode with its
backup subsystem. For example, if the backup subsystem of the
subsystem 1 is the subsystem 3, the subsystem 3 must be valid and
its backup subsystem must be the subsystem 1.

Related Commands

Table 6-7 Related commands for configuring the SCCP subsystem

Command Function

ADD SCCPSSN To add the SCCP subsystem

RMV SCCPSSN To remove the SCCP subsystem

MOD SCCPSSN To modify the SCCP subsystem

LST SCCPSSN To query the SCCP subsystem

6.2.2 Adding New Global Title (GT) (Optional)

This command is used only when the Translation result type in the GT table SCCPGT is DPC
+NEWGT.

Command
ADD SCCPNGT

6-16 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Parameter
Paramete Paramete Parameter Description
r ID r Name

GT GT It has six values: GT1 (ITU GT1), GT2 (ITU GT2), GT3 (ITU
indicator GT3), GT4 (ITU GT4), GT5 (ANSI GT1), and GT6 (ANSI GT2).
It is typically set to GT4.

TT Translatio It specifies the translation type.

n type It is valid only when GT is not set to GT1.
It is optional. Its value is of numeral type and ranges 0-255. It is
set to 0 by default. It must be set based on the actual conditions.

CP Numberin It is the numbering plan of GT and indicates the way in which the
g plan address information is numbered. It is valid only when GT is set
to GT3, GT4, or GT5.
It is optional and its value is of enumeration type. It can be set to:
l UNDEF (Undefined)
l ISDN (ISDN/telephone code plan)
l STANDBY (Standby)
l DATA (Data code plan)
l TELEX (Telex code plan)
l MARINE (Marine move code plan)
l LAND (Land move code plan)
l ISDNMOV (ISDN/move code plan)
It is set to UNDEF by default. LAND is the coding mode used by
a base station when it communicates with the MSC.

AI Nature of It indicates the nature of the address message. It is valid only when
address GT is set to GT1 or GT4.
indicator It is optional and its value is of enumeration type. It can be set to:
l FREE (Idle)
l USRCODE (Subscriber number)
l NS (National reserved)
l NM (National valid number)
l INTER (International user)
The SG7000 is often set to INTER.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 6-17

Paramete Paramete Parameter Description

r ID r Name

CHANGE Address It defines the conversion mode of GT translation information. It is

MODE prefix optional and its value is of enumeration type. It can be set to:
convert l NOCHG (Nochange): Performing no change to address
mode information. Parameters Address prefix convert position and
Address prefix convert prefix can be modified.
l ADD (Add): Adding new prefix information to the previous
address information
l DELETE (Delete): Removing prefix information used to
specify the length in Address prefix convert position from the
previous address information
l MODIFY (Modify): Removing prefix information used to
specify the length in Address prefix convert position from the
previous address information and then adding the corresponding
prefix information of Address prefix convert prefix
l REPLACE (Replace): Replacing the entire previous address
information with the corresponding contents of Address prefix
convert prefix
NOTE
The length of the address information after the GT translation cannot
exceed 20 digits.

CHANGE Address It specifies the digits to be removed from the original address
LEN prefix information. It is valid only in DELETE and MODIFY. Its value
convert is of numeral type and ranges 0-15.
position

AF Address It specifies the prefix content to be added in MODIFY and ADD

prefix or the content to be entirely replaced in REPLACE.
convert
prefix

Example
Table 6-8 lists the options of Address prefix convert mode under different conditions.

Table 6-8 Options of Address prefix convert mode

Option Address Corresponding Condition
prefix convert mode

NOCHG (Nochange) When other attributes rather than the address information require
modification.

ADD (Add) When the address information requires modification and the prefix
is added before the specified content

6-18 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Option Address Corresponding Condition

prefix convert mode

DELETE (Delete) When the address information requires modification and the prefix
is removed from the specified content

MODIFY (Modify) When the address information requires modification and the prefix
is replaced

REPLACE (Replace) When the entire previous address information with the
corresponding contents are replaced

Table 6-9 lists the original code stream and the converted code stream which vary depending
on Address prefix convert mode.

Table 6-9 Convert example

Original GT Tr Numbe Nat Add Add Addres Converted
code type an ring ure ress ress s prefix code stream
stream sla plan of pref pref convert (0x)
(0x) tio add ix ix prefix
n ress con con
typ indi vert vert
e cato mo posi
r de tioi
n

04006101 GT4 5 LAND Nati Noc 0405610121436

214365F7 onal hang 5F7
user e

04006101 GT4 5 LAND Nati Add 021 0405620120113

214365F7 onal 25476
user

04006101 GT4 5 LAND Nati Dele 2 040561014365F

214365F7 onal te 7
user

04006101 GT4 5 LAND Nati Mod 2 789 0405620187395

214365F7 onal ify 476
user

04006101 GT4 5 LAND Nati Repl 9876543 0405620189674

214365F7 onal ace 21 52301
user

NOTE

The blank in Table 6-9 indicates invalid parameters corresponding to Address prefix convert mode.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 6-19

Related Commands

Table 6-10 Related commands for configuring the new GT

Command Function

ADD SCCPNGT To add the new GT

RMV SCCPNGT To remove the new GT

MOD SCCPNGT To modify the new GT

LST SCCPNGT To query the new GT table

6.2.3 Adding SCCP Calling GT Segment (Optional)

This command is used only when Type of load-share in the SCCP addressing policy table
SCCPADDRPL is CLNG (Load-share according to calling GT).

Command
ADD SCCPCGGTSEG

Parameter
Paramete Paramete Parameter Description
r ID r Name

GT GT It has six values: GT1 (ITU GT1), GT2 (ITU GT2), GT3 (ITU
indicator GT3), GT4 (ITU GT4), GT5 (ANSI GT1), and GT6 (ANSI GT2).
It is typically set to GT4.

FTT MIN. It indicates the minimum translation type.

translation It is optional. Its value is of the numeral type. Its value range is
type 0-255. It is set to 0 by default. It must be configured based on the
actual conditions.

6-20 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Paramete Paramete Parameter Description

r ID r Name

FCP MIN. It is the minimum numbering plan of selecting the GT. It specifies
numberin the way in which the address information is numbered. The options
g plan are as follows:
l UNDEF (Undefined)
l ISDN (ISDN/Telephone code plan)
l STANDBY (Standby)
l DADA (Data code plan)
l TELEX (Telex code plan)
l MARINE (Marine move code plan)
l LAND (Land move code plan)
l ISDNMOV (ISDN/move code plan)
ISDN is used to find callees in a call connection. ISDNMOV is
used to update a roaming subscriber's location. LAND is the code
used by a base station when it communicates with the MSC.

FAI MIN. It specifies the nature of minimum address information. The

nature of options are as follows:
address l FERR (Idle)
indicator
l USRCODE (Subscriber number)
l NS (National reserved)
l NM (National valid number)
l INTER (International number)

FAF MIN. It is the GT address message and specifies the value of the GT, that
address is, the concrete address signal. The address message consists of a
message national code, toll area code, and subscriber number. For example,
if the address message of a GT is "8675512345678", "86" is the
national code, "755" is the toll area code, and "12345678" is the
subscriber number.
The minimum address message and maximum address message
define the range of the address message.

TTT MAX. It indicates the maximum translation type.

translation It is optional. Its value is of the numeral type. Its value range is
type 0-255. It is set to 0 by default. It must be configured based on the
actual conditions.

TCP MAX. It is the maximum numbering plan of selecting GT. For the
numberin description of its options, refer to MIN. numbering plan. The
g plan value of MAX. numbering plan must be greater than that of MIN.
numbering plan.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 6-21

Paramete Paramete Parameter Description

r ID r Name

TAI MAX. It specifies the nature of the maximum address information. The
nature of options are as follows:
address l FERR (Idle)
indicator
l USRCODE (Subscriber Number)
l NS (National reserved)
l NM (National valid number)
l INTER (International number)

TAF MAX. It is the GT address message and specifies the value of the GT, that
address is, the concrete address signal. The address message consists of a
message national code, toll area code, and subscriber number. For example,
if the address message of a GT is "8675512345678", "86" is the
national code, "755" is the toll area code, and "12345678" is the
subscriber number.
The minimum address message and maximum address message
define the range of the address message. The value of MAX.
address message must be greater than that of MIN. address
message.

Related Commands

Table 6-11 Related commands for configuring the SCCP calling segment
Command Function

ADD SCCPCGGTSEG To add the SCCP calling GT segment

RMV SCCPCGGTSEG To remove the SCCP calling GT segment

MOD SCCPCGGTSEG To modify the SCCP calling GT segment

LST SCCPCGGTSEG To list the SCCP calling GT segment

6.2.4 Adding Calling GT Load-Share Select Set (Optional)

This command is used only when Type of load-share in the SCCP addressing policy table
SCCPADDRPL is CLNG (Load-share according to calling GT).

Command
ADD SCCPCGGTLSS

6-22 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Parameter
Paramete Paramete Parameter Description
r ID r Name

USED0-1 Used flag They specify whether the corresponding segment index is used.
27 0-127 Value: NONE (not used); USED (used)
Default value: NONE (not used)

IDX0-127 Segment They are in the SCCP segment table, which is defined by ADD
index SCCPCGGTSEG.
0-127 NOTE
The calling load-share select set composes of 128 groups (two parameters
form one group). At lest one group of data is configured for a user. If
multiple groups are configured, they must be configured in order, which
starts from 0.

Related Commands

Table 6-12 Related commands for configuring the SCCP calling the GT load-share select set

Command Function

ADD SCCPCGGTLSS To add the SCCP calling the GT load-share select set

RMV SCCPCGGTLSS To delete the SCCP calling the GT load-share select set

MOD SCCPCGGTLSS To modify the SCCP calling the GT load-share select set

LST SCCPCGGTLSS To query the SCCP calling the GT load-share select set

6.2.5 Adding OPC Section Range (Optional)

This command is used only when Type of load-share in the SCCP addressing policy table
SCCPADDRPL is OPC (Load-share according to OPC).

Command
ADD SCCPOPCRANGE

Parameter
Paramete Paramete Parameter Description
r ID r Name

NI Network It indicates to which network this signaling point is homed. IM

indication means international network, IS means international standby
network, NM means national network, and NS means national
reserved network.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 6-23

Paramete Paramete Parameter Description

r ID r Name

LN LN index Its value range is 0-255. By default, it is set to 0.

MINOPC Minimum It refers to the minimum code of the signaling point that generates
OPC the SCCP message. Together with the Maximum OPC, it
determines the range of the source signaling point code. When the
SG7000 receives the SCCP messages from the signaling points
within this range, the SG7000 follows the load-share policy
configured in the SCCP addressing policy table and sends the
messages to the specified load-share signaling point.
Note that the value of Maximum OPC must be greater than that
of Minimum OPC.

MAXOPC Maximum It refers to the minimum code of the signaling point that generates
OPC the SCCP message. Together with the Maximum OPC, it
determines the range of the source signaling point code. When the
SG7000 receives the SCCP messages from the signaling points
within this range, the SG7000 follows the load-share policy
configured in the SCCP addressing policy table and sends the
messages to the specified load-share signaling point.
Note that the value of Maximum OPC must be greater than that
of Minimum OPC.

All these parameters compose a group of description of the OPC section range. Up to 1024
descriptions can be configured.

Related Commands

Table 6-13 Related commands for configuring the OPC section range
Command Function

ADD SCCPOPCRANGE To add the OPC section range

RMV SCCPOPCRANGE To delete the OPC section range

MOD SCCPOPCRANGE To modify the OPC section range

LST SCCPOPCRANGE To query the OPC section range

6.2.6 Adding OPC Load-Share Select Set (Optional)

This command is used only when Type of load-share in the SCCP addressing policy table
SCCPADDRPL is OPC (Load-share according to OPC).

Command
ADD SCCPOPCLSS

6-24 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Parameter
Paramete Paramete Parameter Description
r ID r Name

USED0-1 Used flag It indicates whether the segment is used. The number segment is
27 0-127 not used by default.
Value: NONE (Not used); USED (Used)
Default: NONE (Not used)

IDX0-127 Segment It is the index of the OPC segment table, which is defined by ADD
index SCCPOPCRANGE.
0-127 NOTE
The calling load-share select set composes of 128 groups (two parameters
form one group). At lest one group of data is configured for a user. If
multiple groups are configured, they must be configured in order, which
starts from 0.

Related Commands

Table 6-14 Related commands for configuring the SCCP OPC load-share select set
Command Function

ADD SCCPOPCLSS To add the SCCP OPC load-share select set

RMV SCCPOPCLSS To delete the SCCP OPC load-share select set

MOD SCCPOPCLSS To modify the SCCP OPC load-share select set

LST SCCPOPCLSS To query the SCCP OPC load-share select set

6.2.7 Adding SCCP Addressing Policy (Optional)

This command is used only when GT work mode in the GT table SCCPGT is MTWM (Multi-
point work mode).

Command
ADD SCCPADDRPL

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 6-25

Parameter
Pa Pa Parameter Description
ra ra
m m
et et
er er
I N
D a
m
e

Cl Lo This parameter specifies the load-sharing modes used by the SCCP to transmit
as ad messages.
s0 - It is optional. Its value is of enumeration type.
Ty sh
pe ar Value range:
e l BIT0 (Fully load-share of 0 class message)
m l BIT1 (Fully load-share of 1 class message)
od
e When Load-share mode of message is set to BIT0 (Fully load-share of 0 class
of message), all five types of SCCP load sharing modes are valid to class-1 messages.
m When Load-share mode of message is set to BIT1 (Fully load-share of 1 class
es message), all five types of SCCP load sharing modes are valid to class-0 messages.
sa
ge

R Ty It specifies the load-share type of the SCCP. The following are the four types of
O pe load-share:
U of l SLS (Load-share according to the SLS of MSU): It means sharing the load
T lo according to the SLS in a signaling message. The type is the default value.
T ad
Y - l LIDX (Load-share according to the SLC of MSU): It means sharing the load
P sh according to an incoming link number.
E ar l OPC (Load-share according to the OPC): It means sharing the load according
e to the OPC in a signaling message. Before selecting "OPC", configure the OPC
load-share select set table with the command ADD SCCPOPCLSS and
generate a table index, which is used for Type of load-share select set.
l CLNG (Load-share according to the calling GT): It means sharing the load
according to the calling number. Before selecting "CLNG", configure the calling
load-share select set table with the command ADD SCCPCGGTLSS and
generate a table index, which is used for Type of load-share select set.
l TID (TID load-share of message): Enabling the dynamic load sharing among
16 signaling points and 256 links.

6-26 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Pa Pa Parameter Description
ra ra
m m
et et
er er
I N
D a
m
e

L In It specifies the index of the corresponding load-share select set.

SS de l This parameter is null when Type of load-share is set to SLS or LIDX.
ID x
X of l This parameter is mandatory when Type of load-share is set to OPC. It means
lo referencing to the OPC load-share select set table.
ad l This parameter is mandatory when Type of load-share is set to CLNG. It means
- referencing the calling load-share select set table.
sh
ar
e
sel
ec
t
set

L Lo The parameter is used to load the SCCP message equally to multiple load sharing
S ad signaling points through an algorithm.
M - For details of the algorithm, see section 6.1.5 Configuration Principles. The value
sh field of the parameter is the decimal value of a 4-digit binary number. For example,
ar if the load-share select mask is 1001, the corresponding decimal value is 5. The
e value range of the parameter is 0-15, and it is set to 15 by default.
sel
ec The configuration principle of the parameter is as follows:
t l Set it to 0 when there is only one load sharing signaling point.
m l Set any one digit of the number to 1 when there are two load sharing signaling
as points.
k
l Set any two digits of the number to 1 when there are three or four load sharing
signaling points.
l Set any three digits of the number to 1 when there are five to eight load sharing
signaling points.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 6-27

Pa Pa Parameter Description
ra ra
m m
et et
er er
I N
D a
m
e

L Lo It is valid only when the OPC or CLNG load sharing mode is used.
S ad Its value range is 0-127.
M -
2 sh
ar
e
sel
ec
t
m
as
k
2

D D It specifies the name of a DSP.

SP SP It is optional. Its value is of the character type and can contain up to 40 English
T0 0- characters.
-1 15
5 titl
e

6-28 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Pa Pa Parameter Description
ra ra
m m
et et
er er
I N
D a
m
e

D D The three parameters form a group. There are sixteen groups of data in all in the
SP SP addressing policy table. It means that sixteen types of load sharing for signaling
0- 0- point are supported.
15 15
in
de
x

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 6-29

Pa Pa Parameter Description
ra ra
m m
et et
er er
I N
D a
m
e

SS Re
N lat
0- ed
15 lo
ca
l
su
bs
ys
te
m
0-
15

P Pr
RI ior
O ity
RI 0-
T 15
Y
0-
15

Related Commands

Table 6-15 Related commands for configuring the SCCP addressing policy
Command Function

ADD SCCPADDRPL To add the SCCP addressing policy

RMV SCCPADDRPL To delete the SCCP addressing policy

MOD SCCPADDRPL To modify the SCCP addressing policy

LST SCCPADDRPL To query the SCCP addressing policy

6-30 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

6.2.8 Adding GT
This section describes the command, parameter, and related commands for adding the GT. The
GT table supports a maximum of 200,000 records

Command
ADD SCCPGT

Parameter
Paramete Paramete Parameter Description
r ID r Name

NI Network It specifies the network of the DPC in the GT translation result.

indication The configured "network indication + DPC" must be defined in the
destination signaling point table.

RT Translatio It indicates the type of the GT translation result. The following are
n result the four types of results:
type l STP1: Indicating the translation result is of "DPC + GT" form.
l LSPC1: Indicating the translation result is of "DPC + SSN"
form.
l STP2: Indicating the translation result is of "DPC + NEWGT"
form.
l LSPC2: Indicating the translation result is of "DPC" form.

WM GT work It specifies the work mode of the GT translation. The following are
mode the two options:
l Single point work mode: In this mode, do not configure Index
of SCCP addressing policy.
l Multi-point work mode: In this mode, Index of SCCP
addressing policy must be configured.
NOTE
When the GT is in the multi-point work mode, do not configure the DPC
INDEX and SSN code.

RPX Index of This parameter must be configured when GT is in the multi-point

SCCP work mode. The index specifies the SCCP addressing policy table
addressing in which the DSPSSN or DSP can be obtained.
policy

RPT SCCP It specifies the name of the SCCP addressing policy table. The
addressing SCCP module performs load sharing based on the addressing
policy title policy table.
It is optional. Its value is of the character type and can contain up
to 40 characters.
It is required when WM is set to MTWM.

DX DPC It is the referenced DPC after translation. The corresponding DPC

index is referenced in the destination signaling point table.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 6-31

Paramete Paramete Parameter Description

r ID r Name

SSN SSN code This parameter is optional. The parameter is used when the
translation result type is "DPC + SSN". The corresponding SSN is
referenced in the subsystem table. The configured "network
indication + DPC + SSN" must be defined in the subsystem table.
It is an 8-bit code. The SG7000 supports the following SCCP user
parts:
l 1-SCMG :SCCP management
l 2-RESERVED:Reserved
l 3-ISUP:ISDN user part
l 4-OMAP:Operation, maintenance and administration part
l 5-MAP:MAP application
l 6-HLR:Home location register
l 7-VLR:Visitor location register
l 8-MSC:Mobile switching center
l 9-EIC:Equipment identity register
l 10-AUC:Authentication center
l 11-reserved:Reserved
l 12-INAP :Intelligent network application part
l Others are for the extended reserved users.

NGX New GT When the translation result type is "DPC + NEWGT", this new
index translated GT index must be defined in the new GT table. The new
GT index is not used for other translation result types.

GT GT It has six values: GT1 (ITU GT1), GT2 (ITU GT2), GT3 (ITU
indicator GT3), GT4 (ITU GT4), GT5 (ANSI GT1), and GT6 (ANSI GT2).
It is typically set to GT4.

TT Translatio It specifies the type the GT translation. It is set to 0 by default. It

n type must be set based on the actual conditions.

6-32 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Paramete Paramete Parameter Description

r ID r Name

CP Numberin It is the numbering plan of GT and indicates the way in which the
g plan address information is numbered. The value may be one of the
following:
l UNDEF (Undefined)
l ISDN (ISDN/telephone code plan)
l STANDBY (Standby)
l DATA (Data code plan)
l TELEX(Telex code plan)
l MARINE (Marine move code plan)
l LAND (Land move code plan)
l ISDNMOV (ISDN/move code plan)
LAND is the coding mode used by a base station when it
communicates with the MSC. ISDN is used to find callees in a
connection. ISDNMOV is used to update a roaming subscriber's
location.

AI Nature of It indicates the nature of the address message. It is often set to

address INTER. It has the following items:
indicator l FREE (Idle)
l USRCODE (Subscriber number)
l NS (National reserved)
l NM (National valid number)
l INTER (International number)

AF Address It indicates the user number whose GT is to be translated. The

message number comprises a national code, toll area code and user number.
The number has up to 24 digits. For example, in the address
message of 8675528960132, 86 is the national code, 755 is the toll
area code, and 28960132 is the user number.
When the GT wildcard switch is enabled (configured by running
SET SOFTCFG2), the address message can be represented by the
wildcard "E" or "e". A wildcard can exist in the last second, third,
and fourth digits, which indicates all numbers. For example,
867552896EEE2 indicates all user numbers from 8675528960002
to 8675528969992, in which the last digit is 2.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 6-33

Related Commands

Table 6-16 Related commands for configuring the GT

Command Function

ADD SCCPGT To add the GT

RMV SCCPGT To remove the GT

MOD SCCPGT To modify the GT

LST SCCPGT To query the GT table

6.3 Configuration Examples

This section provides examples to describe how to configure the SCCP data.
6.3.1 Configuration Example of Single Point Work Mode
This section provides examples to describe how to configure the SCCP data in single point
working mode.
6.3.2 Configuration Example of Multipoint Work Mode
This section provides examples to describe how to configure the SCCP data in multipoint
working mode.

6.3.1 Configuration Example of Single Point Work Mode

This section provides examples to describe how to configure the SCCP data in single point
working mode.

Assumption
In Figure 6-7, if SP A requires to send messages to SP C, the SP A must know the DPC of the
SP C. Here, the SP A knows the DPC of the SP B, and the SP B knows the DPC of the SP C.

Since SP A does not know the DPC of SP C, it has to address the SCCP users of SP C through
GT. It translates GT and then the signaling initiated from the SP A is forwarded by SP B.
Therefore, the GT translation type of the SP C must be set to "DPC + GT" at SP A. The DPC is
the signaling point code of the SP B.

When the SP B knows the DPC of the SP C and has an MTP route reaching it, the SP B can send
messages to the SP C directly without the SCCP transfer and set the GT translation type to "DPC
+ SSN". The DPC is the signaling point code of the SP C.

Figure 6-7 Example of SCCP sending messages

6-34 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Table 6-17 shows the collected data of the SP A.

Table 6-17 SP A data collection table

Network Translation result GT type Numbering plan

indication type

NM DPC+GT GT4 ISDN

GT work mode SSN code (optional) Address attribute Address

indication information
(optional)

SGWM - INTER 86755123456

Table 6-18 shows the collected data of the SP B.

Table 6-18 SP B data collection table

Network Translation result GT type Numbering plan

indication type

NM DPC+SSN GT4 ISDN

GT work mode SSN code (optional) Address attribute Address

indication information
(optional)

SGWM INAP INTER 86755123456

The following examples are about the single point work mode of the SCCP. The description
starts from the configuration of local data related to the SCCP. The configuration of the hardware
data and MTP data is not described here.

Procedure
Step 1 Configure SP A.
1. To add a local signaling point, set SCCP function to True, and run the following command:
SET OFI: SN1=NM, SN2=NS, SN3=IM, SN4=IS, NPC="A1111A", SCCP=TRUE;
2. To add destination signaling point SP B, set SCCP function to NOBAK, SHARE,
MST, EVENSH or ODDSH, STP to True, keep the default values for other parameters,
and run the following command:
ADD N7DSP: NPC="B1111B";

After running the command, the DPC index 1 is returned.

3. To add the GT translation table of the SP C, set GT work mode to SGWM, DPC index
to the signaling point code of the SP B, Translation result type to STP1 (DPC+GT), and
run the following command:

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 6-35

ADD SCCPGT: NI=NM, RT=STP1, WM=SGWM, DX=1, GT=GT4, CP=ISDN, AI=INTER,

AF="86755123456";

Step 2 Configure SP B.
1. To add local signaling point, set SCCP function to True, and run the following command:
SET OFI: SN1=NM, SN2=NS, SN3=IM, SN4=IS, NPC="B1111B", SCCP=TRUE;
2. To add destination signaling point SP C, set SCCP function to NOBAK, SHARE,
MST, EVENSH or ODDSH, STP to False, keep the default values for other parameters,
and run the following command:
ADD N7DSP: NPC="C1111C", STP=FALSE;

After running the command, the DPC index 0 is returned.

3. To add subsystem table, set SSN code to INAP, DPC index to 0, and run the following
command:
ADD SCCPSSN: NI=NM, SSN=INAP, DX=0;
4. To add the GT translation table of the SP C, set DPC index to 0, Translation result
type to LSPC1 (DPC+SSN), and SSN code to INAP. Set GT type and other parameters
to the values set on the SP A and run the following command:
ADD SCCPGT: NI=NM, RT=LSPC1, WM=SGWM, DX=0, SSN=INAP, GT=GT4, CP=ISDN,
AI=INTER, AF="86755123456";

----End

6.3.2 Configuration Example of Multipoint Work Mode

This section provides examples to describe how to configure the SCCP data in multipoint
working mode.

Assumption

Figure 6-8 Multipoint sharing SCCP

In Figure 6-8, SP A-SP B indicate the original signaling points generating the SCCP message,
that is, the signaling points where the callers are located. SP 0-SP 2 indicates the load sharing
signaling points. In the following examples, the MTP connection is created between the local
office signaling point and SP 0-SP 2.

6-36 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

The example introduces only the load sharing mode of the SCCP message configured on SG to
signaling points SP 0-SP 2. The configurations on SP A-SP D and SP 0-SP 2 are not included.

This section describes the ways to configure the SCCP data, therefore the configurations of the
hardware data and MTP data are excluded. For more details about configuring the MTP links,
see chapter 4 Configuring MTP Data.

Configuration Description
The following examples describe the four SCCP load sharing modes configured on the SP A.
The configuration examples start from the local office data relevant to the SCCP. The
configurations of the hardware data and MTP data are excluded.

Table 6-19 shows the data to be collected. The load share modes are different.

Table 6-19 Data collection table

Network Translation result GT type Numbering plan

indication type

NM - GT4 ISDN

GT work mode SSN code (optional) Address attribute Address

indication information
(optional)

MTWM - INTER 86755123456

Configuring SCCP to SLS Load Sharing Mode

Step 1 To add local office signaling point, set SCCP function to True, and run the following command:
SET OFI: SN1=NM, SN2=NS, SN3=IM, SN4=IS, NPC="666666", SCCP=TRUE;

Step 2 To add three DSPs, SP 0-SP 2 (one each time), set SCCP function to True, STP to True, other
parameters to default values, and run the following command:
ADD N7DSP: NPC="111111";
ADD N7DSP: NPC="111112";
ADD N7DSP: NPC="111113";

After running the command, the DPC index numbers 0-2 are returned.

To add the first SCCP calling GT number segment, set GT type to GT4, MIN. nature of address
indicator and MAX. nature of address indicator to INTER, MIN. numbering plan and
MAX. numbering plan to LAND, MIN. address message to 8675518800010000, MAX.
address message to 8675518800011000, and keep the default values for other parameters, run
the command. After the execution of the command, the index 0 is obtained.

Step 3 To add SCCP addressing policy, set Type of load-share to SLS and Load-share select mask
to 1, DSP0 to 0, DSP1 to 1, DSP2 to 2, all Network indication of DSP to National, all
priorities to 0, and run the following command:
ADD SCCPADDRPL: ROUTTYPE=SLS, LSM=1, DSP0=0, NIDSP0=NM, PRIORITY0=0,
DSP1=1, NIDSP1=NM, PRIORITY1=0, DSP2=2, NIDSP2=NM, PRIORITY2=0;

After running the command, the index 1 of GT addressing policy is returned.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 6-37

Step 4 To add the GT, set Translation result type to STP1 (DPC+GT), GT work mode to
MTWM, Index of SCCP addressing policy to 1, and run the following command:
ADD SCCPGT: NI=NM, WM=MTWM, RPX=1, GT=GT4, CP=ISDN, AI=INTER,
AF="867551234";

----End

Configuring SCCP to LIDX Incoming Link Index Load Sharing Mode

Step 1 To add local office signaling point, set SCCP function to True, and run the following command:
SET OFI: SN1=NM, SN2=NS, SN3=IM, SN4=IS, NPC="666666", SCCP=TRUE;

Step 2 To add three DSPs, SP 0-SP 2 (one each time), set the SCCP function to True, STP to True,
other parameters to default values, and run the following command:
ADD N7DSP: NPC="111111";
ADD N7DSP: NPC="111112";
ADD N7DSP: NPC="111113";

After running the command, the DPC index 0, DPC index 1, and DPC index 2 are returned.
Step 3 To add SCCP addressing policy, set Type of load-share to LIDX and Load-share select
mask to 1, DSP0 to 0, DSP1 to 1, DSP2 to 2, all Network indication of DSP to National, all
priorities to 0, and run the following command:
ADD SCCPADDRPL: ROUTTYPE=LIDX, LSM=1, DSP0=0, NIDSP0=NM, PRIORITY0=0,
DSP1=1, NIDSP1=NM, PRIORITY1=0, DSP2=2, NIDSP2=NM, PRIORITY2=0;

After running the command, the index 1 of GT addressing policy is returned.

Step 4 To add the GT, set translation result type to STP1 (DPC+GT), GT work mode to MTWM,
Index of SCCP addressing policy to 1, and run the following command:
ADD SCCPGT: NI=NM, WM=MTWM, RPX=1, GT=GT4, CP=ISDN, AI=INTER,
AF="867551234";

----End

Configuring SCCP to OPC Load Sharing Mode

Step 1 To add local office signaling point, set SCCP function to True, and run the following command:
SET OFI: SN1=NM, SN2=NS, SN3=IM, SN4=IS, NPC="666666", SCCP=TRUE;

After running the command, the DPC index 0, DPC index 1, and DPC index 2 are returned.
Step 3 Add OPC section range table: Select the two OPC sections 222220-222221 and 222222-222223.
Set Network indication to NM and LN number to 0 and 1.
ADD SCCPOPCRANGE: NI=NM, LN=0, MIN0PC="222220", MAX0PC="222221";
ADD SCCPOPCRANGE: NI=NM, LN=1, MINPOC="222222", MAXOPC="222223";

After running the command, the load-share select set indexes 0 and 1 are returned.
Step 4 To add SCCP OPC load-share select set, set the parameter as follows:
ADD SCCPOPCLSS: USED0=USED, IDX0=0, USED1=USED, IDX1=1;

6-38 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Step 5 To add SCCP addressing policy, set Type of load-share to OPC and Load-share select
mask to 1, DSP0 to 0, DSP1 to 1, DSP2 to 2, all Network indication of DSP to National, all
priorities to 0, and run the following command:
ADD SCCPADDRPL: ROUTTYPE=OPC, LSSIDX=1, LSM=1, DSP0=0, NIDSP0=NM,
PRIORITY0=0, DSP1=1, NIDSP1=NM, PRIORITY1=0, DSP1=2, NIDSP2=NM,
PRIORITY2=0;

After running the command, the index 1 of GT addressing policy is returned.

Step 6 To add the GT, set Translation result type to STP1 (DPC+GT), GT work mode to
MTWM, Index of SCCP addressing policy to 1, and run the following command:
ADD SCCPGT: NI=NM, WM=MTWM, RPX=1, GT=GT4, CP=ISDN, AI=INTER,
AF="867551234";

----End

Configuring SCCP to CLNG Load Sharing Mode

Step 1 To add local office signaling point, set SCCP function to True, and run the following command:
SET OFI: SN1=NM, SN2=NS, SN3=IM, SN4=IS, NPC="666666", SCCP=TRUE;

After running the command, the DPC index 0, DPC index 1, and DPC index 2 are returned.
Step 3 To add the first SCCP calling GT segment, set GT indicator to GT4, MIN nature of address
indicator and MAX nature of address indicator to INTER, MIN numbering plan and MAX
numbering plan to LAND, MIN address message to 8675518800011000, MAX address
message to 8675518800011000, other parameters to default values, and run the following
command:
ADD SCCPCGGTSEG: FGT=GT4, FCP=LAND, FAI=INTER, FAF="8675513800010001",
TCP=LAND, TAI=INTER, TAF="8675513800010020";

After running the command, the segment index 0 is returned.

Step 4 To add the second SCCP calling GT segment, set GT indicator to GT4, MIN nature of address
indicator and MAX nature of address indicator to INTER, MIN numbering plan and MAX
numbering plan to LAND, MIN address message to 8675518800011001, MAX address
message to 8675518800012000, other parameters to default values, and run the following
command:
ADD SCCPCGGTSEG: FGT=GT4, FCP=LAND, FAI=INTER, FAF="8675518800011001",
TCP=LAND, TAI=INTER, TAF="8675518800012000";

After running the command, the segment index 1 is returned.

Step 5 To add the SCCP calling GT load-share select set, set Used Flag0 to Used, Segment index0 to
0, Used flag1 to Used, Segment index1 to 1, and run the following command:
ADD SCCPCGGTLSS: USED0=USED, CLGNRNIDX0=0, USED1=USED, CLGNRNIDX1=1;

After running the command, the index 1 of calling number load-share select set is returned.
Step 6 To add the SCCP addressing policy, set Type of load-share to CLNG, Index of load-share
select set to 1 and Load-share select mask to 1, DSP0 to 0, DSP1 to 1, DSP2 to 2, all Network
indication of DSP to National, all priorities to 0, and run the following command:

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 6-39

ADD SCCPADDRPL: ROUTTYPE=CLNG, LSSIDX=1, LSM=1, DSP0=0, NIDSP0=NM,

PRIORITY0=0, DSP1=1, NIDSP1=NM, PRIORITY1=0, DSP1=2, NIDSP2=NM,
PRIORITY2=0;

After running the command, the index 1 of GT addressing policy is returned.

Step 7 To add the GT, set Translation result type to STP1 (DPC+GT), GT work mode to
MTWM, Index of SCCP addressing policy to 1, and run the following command:
ADD SCCPGT: NI=NM, WM=MTWM, RPX=1, GT=GT4, CP=ISDN, AI=INTER,
AF="867551234";

----End

Configuring SCCP to TID Load Sharing Mode

Step 1 To add local office signaling point, set SCCP function to True, and run the following command:
SET OFI: SN1=NM, SN2=NS, SN3=IM, SN4=IS, NPC="666666", SCCP=TRUE;

Step 3 To add SCCP addressing policy, set Type of load-share to TID and Load-share select mask
to 1, DSP0 to 0, DSP1 to 1, DSP2 to 2, all Network indication of DSP to National, all
priorities to 0, and run the following command:
ADD SCCPADDRPL: ROUTTYPE=SLS, LSM=1, DSP0=0, NIDSP1=NM, PRIORITY0=0,
DSP1=1, NIDSP1=NM, PRIORITY1=0, DSP2=2, NIDSP2=NM, PRIORITY2=0;

After running the command, the index 1 of GT addressing policy is returned.

----End

6-40 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

7 Configuring SCCP Shielding Data

About This Chapter

This chapter describes how to configure the SCCP shielding data. Before configuring the SCCP
shielding data, you must have completed configuring the hardware data, local office data, MTP
data, and SCCP data.
To configure the SG7000 data, follow the procedure as shown in Figure 7-1. In this way, the
key fields are defined before they are referenced by other data tables and no junk data is
generated.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 7-1

Figure 7-1 Data configuration procedure

7.1 Configuration Preparations

This section describes the background information, technical terms, and configuration steps to
be studied before data configuration.
7.2 Configuring SCCP Shielding Data
Configuring SCCP shielding data including adding the calling DPCSSN shielding table, adding
the calling GT shielding table, adding the called GT translation result type shielding table, and
adding the called DPCSSN shielding table.
7.3 Configuration Examples
This section provides examples to describe how to configure the SCCP shielding data.

7-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

7.1 Configuration Preparations

This section describes the background information, technical terms, and configuration steps to
be studied before data configuration.
7.1.1 Terms
This section describes the terms used during configuring the SCCP shielding data.
7.1.2 Networking Structure
The networking is the same as that of the SCCP data configuration.
7.1.3 Relation Between Data Tables
This section describes the relations between data tables related to SCCP shielding data
configuration.
7.1.4 Data Collection
Set shielding conditions before configuring the SCCP shielding data. Select the shielding tables
corresponding to the shielding conditions. Then select the Shielding Reference of the shielding
link.
7.1.5 General Steps
You must follow certain procedures to configure the SCCP shielding data.

7.1.1 Terms
This section describes the terms used during configuring the SCCP shielding data.
The SCCP shielding function is used to discard a message that has the following features:
l DPC + SSN.
l GT code.
l GT translation type.

These features can be combined to form a feature set to control objects that have multiple
features.

7.1.2 Networking Structure

The networking is the same as that of the SCCP data configuration.

Figure 7-2 Networking of configuring SCCP data

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 7-3

7.1.3 Relation Between Data Tables

This section describes the relations between data tables related to SCCP shielding data
configuration.
The following are the two lines of the SCCP shielding data configuration:
l The shielding chain starting from the caller SCCPSSN shielding table.
l The shielding chain starting from the caller GT shielding table.

Figure 7-3 and Figure 7-4 indicate the parameter referencing relationship between the SCCP
shielding data tables in this chapter. Parameter reference of every table in the figures can be
referenced only by any shielding table above it.
Add a shielding chain in Figure 7-3 or Figure 7-4 from bottom to top. In other words, add the
shielding table at the bottom first, and then add the shielding table above it. When deleting a
shielding chain, delete the shielding table at the top of the shielding chain, and then delete the
shielding table below it, because the referenced shielding table cannot be deleted.

Figure 7-3 Relation between the shielding data tables starting from the caller SCCPSSN
ADD SCCPCDS

[ Next Shielding reference ]

ADD SCCPDGT
[ Shielding reference ]
[ Next Shielding reference ]

ADD SCCPMT
[ Shielding reference ]
[ Next Shielding reference ]

ADD SCCPDDS

[ Shielding reference ]

ADD SCCPDGTT

[ Shielding reference ]

7-4 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Figure 7-4 Relation between the shielding data tables starting from the caller GT
ADD SCCPCGT

[ Next Shielding reference ]

ADD SCCPCGTT
[ Shielding reference ]
[ Next Shielding reference ]

ADD SCCPMT
[ Shielding reference ]
[ Next Shielding reference ]

ADD SCCPDGT
[ Shielding reference ]
[ Next Shielding reference ]

ADD SCCPDSS

[ Shielding reference ]

ADD SCCPDGTT

[ Shielding reference ]

7.1.4 Data Collection

Set shielding conditions before configuring the SCCP shielding data. Select the shielding tables
corresponding to the shielding conditions. Then select the Shielding Reference of the shielding
link.

Table 7-1 Data collection table

Shielding tables to be added Shielding reference

7.1.5 General Steps

You must follow certain procedures to configure the SCCP shielding data.
You must follow certain procedures to configure the SCCP shielding data.
There are two ways for setting the SCCP shielding data. The setting sequences are as listed in
Table 7-2 and Table 7-3. The last step in each table is mandatory. Each table except for the last

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 7-5

refers to a shielding condition and thus they are optional. During configuration, configure one
or more required shielding tables according to the sequences as listed in Table 7-2 and Table
7-3.
Caller DPCSSN shielding table or caller GT shielding table can only be the initial shielding
condition of a shielding link. Called DPCSSN shielding table or called GT translation type table
can only be the ending shielding condition of a shielding link.

Table 7-2 Configuring the SCCPSSN shielding data

Step Operation

1 To add the called GT type shielding (ADD SCCPDGTT)

2 To add the called GT shielding (ADD SCCPDGT)

3 To add the SCCP message type shielding table (ADD SCCPMT)

4 To add the called DPCSSN shielding (ADD SCCPDDS)

5 To add the caller DPCSSN shielding (ADD SCCPCDS) (Mandatory)

Table 7-3 Configuring the caller GT shielding data

Step Operation

1 To add the called GT type shielding (ADD SCCPDGTT)

2 To add the called GT shielding (ADD SCCPDGT)

3 To add the SCCP message type shielding table (ADD SCCPMT)

4 To add the called DPCSSN shielding (ADD SCCPDDS)

5 To add the caller GT type shielding (ADD SCCPCGTT)

6 To add the caller GT shielding (ADD SCCPCGT) (Mandatory)

7.2 Configuring SCCP Shielding Data

Configuring SCCP shielding data including adding the calling DPCSSN shielding table, adding
the calling GT shielding table, adding the called GT translation result type shielding table, and
adding the called DPCSSN shielding table.
7.2.1 Adding the Called GT Translation Type Shielding
The table shields the SCCP messages according to the translation types of the called GT. The
table can only be the ending shielding condition.
7.2.2 Adding the Called GT Shielding Table
The table shields the SCCP messages according to the called GT codes.
7.2.3 Adding the Called DPCSSN Shielding Table
The table shields the SCCP messages according to the conditions of the called DPC + SSN. The
table can only be the ending shielding condition.

7-6 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

7.2.4 Adding the SCCP Message Type Shielding Table

The table shields the message type field in the SCCP protocol.
7.2.5 Adding the Caller GT Type Shielding
The table shields the SCCP messages according to the caller GT translation types.
7.2.6 Adding the Caller GT Shielding Table
The table shields the SCCP information according to attributes of the caller GT. The table can
only be the initial shielding condition.
7.2.7 Adding the Caller DPCSSN Shielding Table
The table shields the SCCP messages according to the conditions of the caller DPC + SSN. The
table can only be the initial shielding condition.

7.2.1 Adding the Called GT Translation Type Shielding

The table shields the SCCP messages according to the translation types of the called GT. The
table can only be the ending shielding condition.

Command
ADD SCCPDGTT

Parameter
Paramete Paramete Parameter Description
r ID r Name

MR Shielding Multiple records may exist in the same type of shielding table, so
reference it is required to distinguish table items that belong to different
shielding condition groups in the same type of shielding table. The
Shielding reference is used to distinguish table items of different
shielding condition groups in the same type of shielding table.
Configure the Shielding reference of the shielding tables in the
shielding condition groups in the same type to distinguish the
shielding conditions.

NI Network It indicates the signaling network in which the SP of the subsystem

indication is located. The parameter includes the following options:
l IM-International
l IS-International reserved
l NM-National
l NS-National reserved

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 7-7

Paramete Paramete Parameter Description

r ID r Name

FGTT MIN. The parameter indicates the types of minimal caller GT translation
translation result. Together with MAX. GT translation result type, it shows
result type the translation result type range of the messages to be shielded. The
four types of MIN. translation result type are as follows:
l STP1 (DPC+SSN)
l LSPC1 (DPC+GT)
l STP2 (DPC+NEWGT)
l LSPC2 (DPC)

TGTT MAX. The parameter indicates the types of maximal caller GT translation
translation result. Together with MIN. GT translation result type, it shows
result type the translation result type range of the messages to be shielded. The
types of MAX. translation result type are the same as that of the
MIN. translation result types.

Related Commands

Table 7-4 Related commands for configuring the called GT type shielding table
Command Function

ADD SCCPDGTT To add the called GT type shielding

RMV SCCPDGTT To remove the called GT type shielding

MOD SCCPDGTT To modify the called GT type shielding

LST SCCPDGTT To query the called GT type shielding

7.2.2 Adding the Called GT Shielding Table

The table shields the SCCP messages according to the called GT codes.

Command
ADD SCCPDGT

7-8 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Parameter
Paramete Paramete Parameter Description
r ID r Name

NI Network It indicates the signaling network in which the SP of the subsystem

indication is located. The parameter includes the following options:
l IM-International
l IS-International reserved
l NM-National
l NS-National reserved

FGT MIN. GT Together with MAX. GT indicator, the MIN. GT indicator

indicator shows the GT range of the messages to be shielded. Options are:
l GT1 (ITU GT1)
l GT2 (ITU GT2)
l GT3 (ITU GT3)
l GT4 (ITU GT4)
l GT5 (ANSI GT1)
l GT6 (ANSI GT2)
Refer to the terms in 6.1.1 Terms in chapter 6 Configuring SCCP
Data for GT code types.

FTT MIN. Together with MAX. translation type, the MIN. translation
translation type shows the translation type range of the GT codes to be
type shielded. The value range is 0-255. The default value is 0. Always
set the field value to 0.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 7-9

Paramete Paramete Parameter Description

r ID r Name

FCP MIN. Together with MAX. translation type, the MIN. translation
numberin type shows the numbering plan range of the GT codes to be
g plan shielded. The options are as follows:
l UNDEF (Undefined)
l ISDN (ISDN/telephone code plan E.163, E.164)
l STANDBY (Standby)
l DATA (Data code plan X.121)
l TELEX (Telex code plan F.69)
l MARINE (Marine move code plan E.210, E.211)
l LAND (Land move code plan E.212)
l ISDNMOV (ISDN/move code plan E.214)

FAI MIN. Together with MAX. nature of address indicator, the MIN.
nature of nature of address indicator shows the address indicator range of
address the GT code to be shielded. The options are as follows and INTER
indicator is often selected:
l FERR (Idle)
l USRCODE (Subscriber number)
l NS (National reserved)
l NM (National valid number)
l INTER (International number)

FAF MIN. Together with MAX. address message, the MIN. address
address message shows the address message range of the GT code to be
message shielded.

TGT MAX. GT Together with MIN. GT indicator, the MAX. GT indicator

indicator shows the GT indicator range of messages to be shielded. The value
range is the same as that of the MIN. GT indicator.

TTT MAX. Together with MIN. translation type, the MAX. translation
translation type shows the translation type range of the GT codes to be
type shielded. The value range is 0-255. The default value is 0. Always
set the field value to 0.

TCP MAX. Together with MIN. numbering plan, the MAX. numbering
numberin plan shows the numbering plan range of the GT codes to be
g plan shielded. The value range is the same as that of the MIN.
numbering plan.

TAI MAX. Together with MIN. nature of address indicator, the MAX.
nature of nature of address indicator shows the address indicator range of
address the GT code to be shielded. The value range is the same as that of
indicator the MIN. nature of address indicator.

7-10 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Paramete Paramete Parameter Description

r ID r Name

TAF MAX. Together with MIN. address message, the MAX. address
address message shows the address message range of the GT code to be
message shielded.

TTYPE Next It indicates the data of a table, which will be used for shielding in
shielding the next step. If it is not required to go on searching the shielding
table data, it must be set to END. Together with Next shielding
reference, it determines the table item set to be used in the next
shielding.
Next shielding table can be:
l END (End)
l DGTT (Called GT translation type)

NMR Next It indicates the index of the shielding reference in the next shielding
shielding table to be used in the next step. It determines the table item set to
reference be used in the next shielding search, together with the next
shielding table. If it is not required to search shielding date, do not
specify the parameter.

FSSN Min. It specifies the minimum called SSN carried in an originating

subsystem message. It, together with the maximum called SSN, defines the
number scope of the subsystems for which messages should be screened.
The minimum SSN cannot be greater than the maximum SSN.
It is optional. Its value is of the numeral type and ranges 0-255. It
is set to 255 by default, indicating an invalid record.

TSSN Max. It specifies the maximum called SSN carried in an originating

subsystem message. It, together with the minimum called SSN, defines the
number scope of the subsystems for which messages should be screened.
The minimum SSN cannot be greater than the maximum SSN.
It is optional. Its value is of the numeral type and ranges 0-255. It
is set to 255 by default, indicating an invalid record.

Related Commands

Table 7-5 Related commands for configuring the called GT shielding table

Commands Function

ADD SCCPDGT To add the called GT shielding

RMV SCCPDGT To remove the called GT shielding

MOD SCCPDGT To modify the called GT shielding

LST SCCPDGT To query the called GT shielding

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 7-11

7.2.3 Adding the Called DPCSSN Shielding Table

The table shields the SCCP messages according to the conditions of the called DPC + SSN. The
table can only be the ending shielding condition.

Command
ADD SCCPDDS

Parameter
Paramet Paramete Parameter Description
er ID r Name

NI Network It indicates the signaling network in which the SP of the subsystem

indication is located. The parameter includes the following options:
l IM-International
l IS-International reserved
l NM-National
l NS-National reserved

FO MIN. PC The parameter indicates the code of the minimal caller DPC. It is
number a hexadecimal number with less than six digits. Together with
MAX. PC number, the parameter shows the SP code range of
messages to be shielded.

TO MAX. PC The parameter indicates the code of the maximal caller DPC. It is
number a hexadecimal number with less than six digits. Together with
MIN. PC number, the parameter shows the SP code range of
messages to be shielded.

FSSN MIN. Refer to the terms in 6.1.1 Terms in chapter 6 Configuring SCCP
subsystem Data for the caller MIN. subsystem number. Together with
number MAX. subsystem number, the parameter shows the subsystem
range of messages to be shielded.

TSSN MAX. Refer to the terms in 6.1.1 Terms in chapter 6 Configuring SCCP
subsystem Data for the caller MAX. subsystem number. Together with
number MIN. subsystem number, the parameter shows the subsystem
range of messages to be shielded.

7-12 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Related Commands

Table 7-6 Related commands for configuring the called DPCSSN shielding table
Command Function

ADD SCCPCDS To add the called DPCSSN shielding

RMV SCCPDDS To remove the called DPCSSN shielding

MOD SCCPDDS To modify the called DPCSSN shielding

LST SCCPDDS To query the called DPCSSN shielding

7.2.4 Adding the SCCP Message Type Shielding Table

The table shields the message type field in the SCCP protocol.

Command
ADD SCCPMT

Parameter
Parame Paramete Parameter Description
ter ID r Name

DESC Descriptio It specifies the field to be shielded in an SCCP message.

MR Shielding Multiple records may exist in the same type of shielding table, so it
reference is required to distinguish table items that belong to different shielding
condition groups in the same type of shielding table. The Shielding
reference is used to distinguish table items of different shielding
condition groups in the same type of shielding table. Configure the
Shielding reference of the shielding tables in the shielding condition
groups in the same type to distinguish the shielding conditions.
It is mandatory. Its value ranges from 0 to 65535.

FROM Min.Msg It specifies the minimum type of the message to be shielded. It is

MSGT Type mandatory. Its value is of the numeral type and ranges 0-255. It,
YPE together with Max.Msg Type, determines the type range of the
SCCP message to be shielded.

TOMS Max.Msg It specifies the maximum type of the message to be shielded. It is

GTYPE Type mandatory. Its value is of the numeral type and ranges 0-255. It,
together with Min.Msg Type, determines the type range of the SCCP
message to be shielded.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 7-13

Parame Paramete Parameter Description

ter ID r Name

TTYPE Type of It indicates the data of the table to be used for shielding in the next
next step. If it is not required to search the shielding data, it must be set
shielding to END. Together with Next shielding reference, it decides the table
table item set to be used in the next shielding. It is optional. The allowed
next shielding table include:
l END (End)
l DDS (Called DPCSSN)
l DGT (Called GT)
l DGTT (Called GT translation type)

Related Commands

Table 7-7 Related commands for configuring the SCCP message type shielding table
Command Function

ADD To add the SCCP message type shielding table

SCCPMT

RMV To remove the SCCP message type shielding table

SCCPMT

MOD To modify the SCCP message type shielding table

SCCPMT

LST To query the SCCP message type shielding table

SCCPMT

7.2.5 Adding the Caller GT Type Shielding

The table shields the SCCP messages according to the caller GT translation types.

Command
ADD SCCPCGTT

7-14 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Parameter
Param Parameter Parameter Description
eter ID Name

NI Network It indicates the signaling network in which the SP of the subsystem

indication is located. The parameter includes the following options:
l IM-International
l IS-International reserved
l NM-National
l NS-National reserved

DRI Called route It is the 7th bit value of the address indicator byte in the called
indicator address of the messages. There are two options as follows:
l BYGT (Addressing by GT)
l BYGT (Addressing by DPC)

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 7-15

Param Parameter Parameter Description

eter ID Name

TTYPE Type of next It indicates the data of the table, which must be used for shielding
shielding in the next step. If it is not required to search the shielding data, it
table must be set to END. Together with Next shielding reference, it
determines the table item set to be used in the next shielding. The
next shielding table can be the following:
l END (End)
l SCCP (SCCP message type)
l DDS (Called DPCSSN)
l DGT (Called GT)
l DGTT (Called GT translation type)

NMR Next It indicates the index of the shielding reference in the next shielding
shielding table to be used in the next step. It determines the table item set to
reference be used in the next shielding search, together with the next shielding
table. If it is not required to search shielding date, do not specify
the parameter.

Related Commands

Table 7-8 Related commands for configuring the caller GT type shielding table
Command Function

ADD SCCPCGTT To add the caller GT type shielding

RMV SCCPCGTT To remove the caller GT type shielding

MOD SCCPCGTT To modify the caller GT type shielding

LST SCCPCGT To query the caller GT type shielding

7.2.6 Adding the Caller GT Shielding Table

The table shields the SCCP information according to attributes of the caller GT. The table can
only be the initial shielding condition.

Command
ADD SCCPCGT

7-16 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Parameter
Paramete Paramete Parameter Description
r ID r Name

NI Network It indicates the signaling network in which the SP of the subsystem

indication is located. The parameter includes the following options:
l IM-International
l IS-International reserved
l NM-National
l NS-National reserved

FGT MIN. GT Together with MAX. GT indicator, the MIN. GT indicator

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 7-17

Paramete Paramete Parameter Description

r ID r Name

FAF MIN. Together with MAX. address message, the MIN. address
address message shows the address message range of the GT code to be
message shielded.

TGT MAX. GT Together with MIN. GT indicator, the MAX. GT indicator

indicator shows the GT indicator range of messages to be shielded. The value
range is the same as that of the MIN. GT indicator.

7-18 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Paramete Paramete Parameter Description

r ID r Name

TAF MAX. Together with MIN. address message, the MAX. address
address message shows the address message range of the GT code to be
message shielded.

DRI Called It is the 7th bit value of the address indicator byte in the called
route address of the messages. There are two options as follows:
indicator l BYGT (Addressing by GT)
l BYGT (Addressing by DPC)

TTYPE Type of It indicates the data of the table, which must be used for shielding
next in the next step. If it is not required to search the shielding data, it
shielding must be set to END. Together with the Next shielding
table reference, it determines the table item set to be used in the next
shielding. The next shielding table can be as follows:
l END (End)
l DGTT (Caller GT translation type)
l SCCP (SCCP message type)
l DDS (Called DPCSSN)
l DGT (Called GT)
l DGTT (Called GT translation type)

FSSN Min. It specifies the minimum calling SSN carried in an originating

subsystem message. It, together with the maximum calling SSN, defines the
number scope of the subsystems for which messages should be screened.
The minimum SSN cannot be greater than the maximum SSN.
It is optional. Its value is of the numeral type and ranges 0-255. It
is set to 255 by default, indicating an invalid record.

TSSN Max. It specifies the maximum calling SSN carried in an originating

subsystem message. It, together with the minimum calling SSN, defines the
number scope of the subsystems for which messages should be screened.
The minimum SSN cannot be greater than the maximum SSN.
It is optional. Its value is of the numeral type and ranges 0-255. It
is set to 255 by default, indicating an invalid record.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 7-19

Related Commands

Table 7-9 Related commands for configuring the caller GT shielding table
Command Function

ADD SCCPCGT To add the caller GT shielding

RMV SCCPCGT To remove the caller GT shielding

MOD SCCPCGT To modify the caller GT shielding

LST SCCPCGT To query the caller GT shielding

7.2.7 Adding the Caller DPCSSN Shielding Table

The table shields the SCCP messages according to the conditions of the caller DPC + SSN. The
table can only be the initial shielding condition.

Command
ADD SCCPCDS

Parameter
Par Par Parameter Description
ame ame
ter ter
ID Na
me

MO Scre It specifies whether the system screens the message and reports the result.
DE en Its value is of the enumeration type. It can be set to:
mod
e l No screening
l Screen and don't report
l Screen and report
It is set to No screening by default. To record messages, you must set this
parameter to Screen and report and set the Record file creation switch in
the SET CREATRFILE command to Open.

NI Net It indicates the signaling network in which the SP of the subsystem is located.
wor The parameter includes the following options:
k l IM-International
indi
cati l IS-International reserved
on l NM-National
l NS-National reserved

7-20 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Par Par Parameter Description

ame ame
ter ter
ID Na
me

FO MI It is the minimal caller DPC code. It is a hexadecimal number with less than
N. six digits. Together with MAX. PC number, the MIN. PC number shows
PC the SP code range of the messages to be shielded.
num
ber

TO MA It is the maximal caller DPC code. It is a hexadecimal number with less than
X. six digits. Together with MIN. PC number, the MAX. PC number shows
PC the SP code range of the messages to be shielded.
num
ber

FSS MI It refers to the terms explained in chapter 6 Configuring SCCP Data for the
N N. caller MIN. subsystem number. Together with MAX. subsystem number,
subs the parameter shows the subsystem range of the messages to be shielded.
yste
m
num
ber

TSS MA It refers to the terms explained in chapter 6 Configuring SCCP Data for the
N X. MAX. subsystem number. Together with MIN. subsystem number, the
subs parameter shows the subsystem range of the messages to be shielded.
yste
m
num
ber

DRI Call It is the 7th bit value of the address indicator byte in the called address of
ed messages. The parameter includes the following options:
rout l BYGT (Addressing by GT, by default)
e
indi l BYDPC (Addressing by DPC)
cato
r

TT Nex It indicates the table in which the data must be used for shielding in the next
YPE t step. If it is not required to search the shielding data, it must be set to END.
shiel Together with Next shielding reference, it determines the table item set to be
ding used in the next shielding. The Next shielding table can be the following:
tabl l END (End)
e
l SCCP (SCCP message type)
l DDS (Called DPC SSN)
l DGT (Called GT)
l DGTT (Called GT translation type)

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 7-21

Par Par Parameter Description

ame ame
ter ter
ID Na
me

NM Nex It indicates the index of the shielding reference in the next shielding table to
R t be used in the next step. It determines the table item set to be used in the next
shiel shielding search, together with the next shielding table. If it is not required to
ding search shielding date, do not specify the parameter.
refer
ence

Related commands

Table 7-10 Related commands for configuring the caller DPCSSN shielding table

Command Function

ADD To add the caller DPCSSN shielding

SCCPCDS

RMV To remove the caller DPCSSN shielding

SCCPCDS

MOD To modify the caller DPCSSN shielding

SCCPCDS

LST To query the caller DPCSSN shielding

SCCPCDS

7.3 Configuration Examples

This section provides examples to describe how to configure the SCCP shielding data.

Assumption
Shielding condition: Shield the SCCP messages, where the SSN range (1-11) is sent by the
shielding callers and the messages where the called translation result type ranges from DPC +
GT to DPC + NEWGT.

Table 7-11 Data collection table

Shielding tables to be added Shielding reference

Caller SCCPSSN shielding table and called translation 0

result type shielding table

7-22 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Procedure
Step 1 To add the called translation result type shielding to shield the messages, where the shielding
reference is 0, the translation result type ranges from DPC + GT to DPC + NEWGT, and reserve
the messages of which the translation result is DPC, run the following command:
ADD SCCPDGTT: MR=0, NI=NM, FGTT=STP2, TGTT=STP2;

Step 2 To add the caller SCCPSSN shielding data, where the MAX PC number and MIN PC number
is 112211, shield the SCCP messages of which the SSN range (1-11) is sent by the SP acting as
the shielding caller, the next shielding type is the called translation result shielding, and the
shielding reference is 0, run the following command:
ADD SCCPCDS: MASK=TRUE, NI=NM, FO="112211", TO="112211", FSSN=1, TSSN=11,
TTYPE=DGTT, NMR=0;

----End

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 7-23

8 Configuring SCTP Data

About This Chapter

The chapter describes how to configure the SCTP data. The SCTP data is required when the
SG7000 connects with the softswitch device through the SCTP, which is used as the transport
layer. Configure the SCTP data after configuring the hardware data and local office data, but
before configuring the M2PA data, M3UA data, M2UA data, and IUA data.
It is recommended to use the default SCTP data in the system.
To configure the SG7000 data, follow the procedure as shown in Figure 8-1. In this way, the
key fields are defined before they are referenced by other data tables and no junk data is
generated.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 8-1

Figure 8-1 Data configuration procedure

8.1 Configuration Preparations

This section describes the background information, technical terms, and configuration steps to
be studied before data configuration.
8.2 Configuring SCTP Data
Configuring the SCTP data including setting SCTP initialization parameter data and adding the
SCTP protocol parameter.

8-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

8.1 Configuration Preparations

This section describes the background information, technical terms, and configuration steps to
be studied before data configuration.
8.1.1 Terms
This section describes the terms used during configuring the SCTP data.
8.1.2 Networking Structure
The SCTP protocol is the protocol on the transport layer of the SIGTRAN protocol stack.
Configure the SCTP data before configuring the M2UA, M3UA, IUA, and M2PA data. The
network for configuring the SCTP data is the same as that for configuring the M2UA, M3UA,
IUA, and M2PA data.
8.1.3 Relation Between Data Tables
Data tables in this chapter have no mutual reference.
8.1.4 Data Collection
You need to collect the IP addresses of all the remote devices that are permitted to access the
SG7000.
8.1.5 General Steps
You must follow certain procedures to configure the SCTP data.

8.1.1 Terms
This section describes the terms used during configuring the SCTP data.

SCTP
Before SCTP was used, the User Datagram Protocol (UDP) and Transmission Control Protocol
(TCP) were used to transport the PSTN signaling over the IP network. The UDP and TCP
however, could not meet the needs on transmission quality, and therefore, they were replaced
by the SCTP. The SCTP is connection-oriented and is based on packet. It enables higher
reliability for signaling transmission. The SCTP can control congestion, prevent flood and spoof
attack, and support the real-time use and multi-homing.

The SCTP is the transport layer protocol. The upper layer is the SCTP user application layer and
the lower layer is the packet network layer. For SIGTRAN, the upper layer user of the SCTP is
the adaptation module of the SCN signaling (like M2UA, M3UA, IUA, and M2PA), while the
lower layer is the IP network.

Host and Endpoint

l Host
A host has one or more IP addresses. It is a typical physical entity.
l SCTP Endpoint
The SCTP endpoint is a basic logical entity. It acts as a logical sender and receiver of
datagram.
A transmission address (IP address + SCTP port number) denotes an endpoint only. An
endpoint can have multiple addresses. For one target endpoint, you can configure multiple
IP addresses using the same SCTP port.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 8-3

NOTE

A host can have multiple endpoints.

SCTP Transmission Address

The SCTP transmission address consists of an IP address and a SCTP port number. The SCTP
port number, the same as a TCP port number, is a flag used by the SCTP to denote different
users in the same address. For example, the IP address 10.105.28.92 and port number 1024, IP
address 10.105.28.93 and port number 1024, and IP address 10.105.28.92 and port number 1023
denote three different users.

SCTP Association
An association is a logical connection or path for data transmission between two SCTP endpoints.
It is created by the four-step handshaking mechanism by the SCTP. It is defined in the SCTP
that only one association can be created between two endpoints anytime. An association is
defined by the transmission addresses of the two endpoints. Therefore, you can uniquely denote
an SCTP association by configuring the four parameters: local IP address, local SCTP port
number, peer IP address, and peer SCTP port number. In the SG7000, an association can be
regarded as an M2UA link, M3UA link, or IUA link.

Stream
A stream indicates a sequence of messages to be sent in an order to the upper layer protocols.
Messages in the same stream must be sent according to their sequence. A stream is a logical path
from one endpoint to another in an SCTP association. An association consists of multiple one-
way streams. Streams are independent and identified by stream IDs. Each stream can send data
without being affected by other streams.

Messages that belong to the same sequence must be sent in the same stream.

NOTE

An association can contain multiple streams. The number of available streams is negotiated by the two
endpoints when an association is created. One stream can belong to one association only. At the same time,
amount of outgoing and incoming streams can be different.

Path and Primary Path

l Path
A path is a route used by an endpoint to send SCTP packets to a specific destination
transmission address of the peer endpoint. If an endpoint sends SCTP packets to different
destination transmission addresses of the peer endpoint, you need not configure extra paths.
l Primary Path
Primary path is used to send the destination and original address in SCTP packets to the
peer endpoint by default. If there are multiple destination addresses for an endpoint, the
SCTP endpoint is multi-homed. If the endpoint that sends SCTP packets is multi-homed,
and the destination and original address are defined, the return path of the response data
block and the interface through which data packets are sent can be controlled.
An association can have multiple paths but only one primary path.

SCTP Multi-Homing

8-4 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Both the endpoints of an SCTP association can be configured with multiple IP addresses, and
thus there are multiple paths between them. That is SCTP multi-homed, which is distinguishes
the SCTP from the TCP.

Heartbeat
When a path is idle, the local SCTP user requires SCTP to generate heartbeat messages and send
them to the peer endpoint through the path. Then the peer endpoint must respond with messages
for confirming the receipt of the heartbeat messages. The mechanism is used to measure the
Round Trip Time (RTT), monitor the associations and keep them active.

8.1.2 Networking Structure

The SCTP protocol is the protocol on the transport layer of the SIGTRAN protocol stack.
Configure the SCTP data before configuring the M2UA, M3UA, IUA, and M2PA data. The
network for configuring the SCTP data is the same as that for configuring the M2UA, M3UA,
IUA, and M2PA data.
See Figure 8-2 for the SCTP data networking.

Figure 8-2 SCTP data networking

8.1.3 Relation Between Data Tables

Data tables in this chapter have no mutual reference.

8.1.4 Data Collection

You need to collect the IP addresses of all the remote devices that are permitted to access the
SG7000.

8.1.5 General Steps

You must follow certain procedures to configure the SCTP data.
The steps for configuring the SCTP data are listed in Table 8-1. You can use the system default
values and need not configure the SCTP data.

Table 8-1 Configuring the SCTP data

Step Operation

1 To set the SCTP initialization parameter (SET SCTPINIT)

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 8-5

Step Operation

2 To add the SCTP protocol parameter (ADD SCTPP)

8.2 Configuring SCTP Data

Configuring the SCTP data including setting SCTP initialization parameter data and adding the
SCTP protocol parameter.
8.2.1 Setting SCTP Initialization Parameter Data (Optional)
This section describes the command, parameter, and related commands for setting the SCTP
initialization parameter data.
8.2.2 Adding SCTP Protocol Parameter Data (Optional)
This section describes the command, parameter, and related commands for adding the SCTP
protocol parameter.

8.2.1 Setting SCTP Initialization Parameter Data (Optional)

This section describes the command, parameter, and related commands for setting the SCTP
initialization parameter data.

NOTE

l If there is no special requirement, adopt the system default value instead of setting the SCTP initialized
parameters. Be careful when setting the parameters because it may affect normal running of the system.
l After running the command, you must reset all boards to re-load data to validate the settings.

Command
SET SCTPINIT

8-6 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Parameter
Par Par Parameter Description
ame ame
ter ter
ID Na
me

MA MA It is the maximum number of associations allowed by SBPUs/SBPEs of the

XA X. SG7000.
SSN SCT It is optional. Its value is of the enumeration type. It can be set to:
UM P
asso l MAXNUM8(8): The maximum number of associations is 8.
ciati l MAXNUM32(32): The maximum number of associations is 32.
ons
It must be configured based on the board and memory capacity.
num
ber
supp
orte
d by
the
SCT
P
prot
ocol
stac
k

MA MA It is the maximum number of streams allowed by each STCP association. The

XST X. value range is 1-32. It is set to 32 by default. Generally, the system default
MN strea value is used.
UM m of
each
SCT
P
asso
ciati
on
allo
wed
by
the
SCT
P
prot
ocol
stac
k

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 8-7

Related Commands

Table 8-2 Related commands for setting the SCTP initialization parameter
Command Function

SET To set the SCTP initialization parameter

SCTPINIT

LST To query the SCTP initialization parameter

SCTPINIT

8.2.2 Adding SCTP Protocol Parameter Data (Optional)

This section describes the command, parameter, and related commands for adding the SCTP
protocol parameter.

NOTE

The default record with index 0 already exists in the system.

If there is no special requirement, adopt the system default value instead of adding the SCTP parameters.
You can add the data according the actual conditions. Be careful when modifying any default parameter
because it may affect normal running of the system.

Command
ADD SCTPPP

Parameter
Paramete Paramete Parameter Description
r ID r Name

AMR MAX. Acknowledgement and re-sending mechanism guarantees reliable

times of transmission of the SCTP. The SCTP endpoint status management
couple re- is a counter for peer endpoint maintenance. The counter measures
sending the continuous re-sending times to the endpoint. When the MAX
times of couple re-sending is reached, the peer endpoint is
considered not reachable and the SCTP association enters the
CLOSED state.
The maximum times of couple re-sending is defined here. Its value
range is 1-254 in the unit of times. It is set to 9 by default.

HB Heartbeat It specifies the interval between two adjacent heartbeat data sent
interval by the SCTP. Its value range is 1-180000 in the unit of millisecond.
It is set to 15000s by default.

8-8 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Paramete Paramete Parameter Description

r ID r Name

PMR MAX. SCTP maintains one T3 timer for every destination address. The
times of SCTP path management aims at every peer address. In other words,
path re- the SCTP maintains a counter for every peer address to record the
sending timeout times of sending the T3 timer on the address and the times
of not receiving responses within the specified time after sending
the heartbeat messages. If the times exceed the MAX. times of
path re-sending, it is regarded that the path is not reachable.
The maximum times of path re-sending is defined here. Its value
range is 1-254 in the unit of times. It is set to 9 by default.

IMR MAX. An SCTP association is set by the four-step handshaking

times of mechanism, that is, the exchange of four messages: INIT, INIT
init re- ACK, COOKIE ECHO, and COOKIE ACK.
sending During the first handshaking, the original endpoint of the
association sends an INIT message to the peer endpoint and starts
an INIT timer while waiting for an INIT ACK message from the
peer endpoint. Upon timeout of the timer, the original endpoint
resends the INIT messages until the MAX. times of init re-
sending is reached.
The maximum times of re-sending the INIT messages is defined
here. The value range is 1-254. It is set to 8 by default.

SCS Send the They denote whether to check the data of SCTP packets in the
checksum transmission layer. Note whether an endpoint sending the
checksum is consistent with its peer endpoint receiving the
RCS Receive checksum. It is set to YES by default.
the
checksum

CKTYP Checksum It specifies the data checksum type of the SCTP packets in the
type transmission layer. Note that the Checksum of an endpoint and
that of its peer endpoint must be consistent. It can be set to
CRC32 or ADLER32. It is set to CRC32 by default.

Related Commands

Table 8-3 Related commands for configuring the SCTP protocol parameter

Command Function

ADD SCTPPP To add the SCTP protocol parameter

MOD SCTPPP To modify the SCTP protocol parameter

RMV SCTPPP To remove the SCTP protocol parameter

LST SCTPPP To query the SCTP protocol parameter

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 8-9

9 Configuring SUA Data

About This Chapter

This chapter describes how to configure the SUA data. The SUA data is used for the interworking
between this system and other equipment through the SUA protocol. Before configuring the
SUA data, ensure that the hardware data, local office data, and SCTP data is already configured.
To configure the SG7000 data, follow the procedure as shown in Figure 9-1. In this way, the
key fields are defined before they are referenced by other data tables and no junk data is
generated.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 9-1

Figure 9-1 Data configuration procedure

9.1 Configuration Preparations

This section describes the related background information, terms, and general steps for
configuring the SUA data.
9.2 Configuring the SUA Data
Configuring the SUA data includes the following: configuring the local IP address, configuring
the local IP address combination, and configuring the SUA link.
9.3 Configuration Examples
This section provides examples to describe how to configure the SUA data.

9-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

9.1 Configuration Preparations

This section describes the related background information, terms, and general steps for
configuring the SUA data.
9.1.1 Terms
This section describes the terms used when you configure the SUA data.
9.1.2 Networking Structure for Configuring the SUA Data
This section describes the networking structure for configuring the SUA data.
9.1.3 Relations Between Data Tables
This section describes the mapping relations between data tables related to the SUA data
configuration.
9.1.4 Data Collection
Before configuring the SUA data, you must collect the information including the SUA AS type,
DPC, remote IP address, and remote port number.
9.1.5 Configuration Principles
This section describes the principles to be followed when you configure the SUA data.
9.1.6 General Steps
You must follow certain procedures to configure the SUA data.

9.1.1 Terms
This section describes the terms used when you configure the SUA data.

Basic Concept of SIGTRAN Protocol

The signaling transport (SIGTRAN) protocol supports to transmit the traditional switched circuit
network (SCN) signaling over the IP network. The SIGTRAN protocol supports the standard
primitive interface between layers defined in the SCN signaling protocol layered model to make
sure that the present SCN signaling can be used without being modified. The SIGTRAN protocol
also uses the standard IP transmission protocol as the lower layer of transmission and meets the
special transmission requirements for the SCN signaling by enhancing its own functions.
The SIGTRAN is a protocol stack, which contains two layers of protocols: transmission protocol
and adaptation protocol. The former one is the SCTP/IP and the latter one includes SUA (SCCP
User Adaptation), M2UA (applicable to MTP2 users), M3UA (applicable to MTP3 users),
V5UA (applicable to V5 users), and IUA (applicable to Q.921 users). The SIGTRAN protocol
module is as shown in Figure 9-2.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 9-3

Figure 9-2 SIGTRAN protocol module

M3UA M2UA M2PA V5UA IUA SUA

layer layer layer layer layer layer

SCTP

MAC

M3UA: MTP3 User Adaptation M2UA: MTP2 User Adaptation

IUA: ISDN Q.921 User Adaptation V5UA: V5 User Adaptation

SCTP: Stream Control Transmission Protocol IP: Internet Protocol

M2PA: MTP2 Peer Adaptation SUA: SCCP User Adaptation

MAC: Media Access Control -

NOTE

The SG7000, at present, only supports 5 adaptation protocols, such as SUA, M2UA, M3UA, IUA, and
M2PA.

SUA Protocol
The SUA protocol is defined by the RFC3868 specifications and is the SCCP User Adaptation
protocol. Throuth the SUA protocol, the signaling messages of the upper-layer protocol (such
as TCAP/MAP) of the original SCCP can be transmitted over the IP network in seamless mode,
regardless of the lower protocol.
Through the SUA protocol, the SCCP protocol and its upper-layer protocol can run
independently on different network elements. For example, the SCCP protocol runs on the SG
and its upper-layer protocol (such as TCAP/MAP) runs on the MGC, which enables the MGC
to better implement its control function in the core network.
Figure 9-3 shows the SUA protocol stack.

Figure 9-3 SUA protocol stack

9-4 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

NOTE

Q.931 and Q.921 are standard protocols of the ITU-T organization and they are applied in the data link
layer and network layer. For details, refer to the relevant protocols.

The SUA protocol is applied in the following modes:

l SG-ASP application mode: The SUA protocol is applied on both the SG and the MGC,
which enables the SCCP protocol and its upper-layer protocol to run independently on
different network elements. Figure 9-4 shows SG-ASP application mode.

Figure 9-4 SG-ASP application mode

l IPSP-IPSP application mode: In the entire IP network, the SUA protocol implements the
seamless transmission of the upper-layer protocol messages of the original SCCP. This
enables the upper-layer protocol of the original SCCP to be smoothly applied in the IP
network without being changed. Figure 9-5 shows IPSP-IPSP application mode.

Figure 9-5 IPSP-IPSP application mode

Application Server (AS)

AS is a logical entity, which represents some resources and corresponds to a special "route key".
An example of an application server is a virtual database unit, handling all querying transactions

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 9-5

identified by "DPC/OPC/SCCP_SSN". Each AS contains a group of application server processes

(ASPs), among which one or more ASPs can process transactions.

Application Server Process (ASP)

It is an actual processing entity of an AS, such as the softswitch equipment which carries an AS
service. An ASP corresponds to an SCTP endpoint. Messages of the ASs convey signaling
through the link between the ASP and the SG.

IP Server Process (IPSP)

It is a process instance of an IP-based application. An IPSP is essentially the same as an ASP,
except that it uses M3UA in a point-to-point fashion instead of using the services of a signaling
gateway.

Signaling Gateway (SG)

An SG receives and sends SS7 higher-layer user messages at the edge of the IP network and
SS7 network. An SG appears to the SS7 network as an SS7 signaling point. An SG contains one
or more signaling gateway processes, of which one or more is normally processing traffic. When
an SG contains more than one SGP, the SG is a logical entity and the contained SGPs must be
coordinated into a single management view to the SS7 network and to the supported application
servers.

Signaling Gateway Process (SGP)

It is a process instance of a signaling gateway. It may be in the active, standby, or load-sharing
state.

C/S Mode of SCTP Association

The C/S mode is the client/server mode. When the SIGTRAN protocol adopts the SCTP as a
transmission layer and the SCTP association adopts the client/server mode, you must know the
work mode of each device in the SCTP association to make sure that the SIGTRAN protocol is
working normally. If a device serves as an SG, it acts as the server in the SCTP association, and
the peer device acts as the client in the link.
For example, when the SG7000, as a signaling gateway, interworks with a softswitch, it is the
server and the softswitch is the client in the SCTP association bearing M3UA. It is true in other
conditions.

SCN
It is the switch signaling network.

Routing Key
A routing key describes a set of SS7 parameters and parameter values, such as DPC, SIO + DPC,
SIO + DPC + OPC, SIO + DPC + OPC + CIC, and SIO + DPC + OPC + SSN. It defines the
range of signaling traffic to be handled by a particular application server.

Routing Context

9-6 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

It is an identification index value that identifies a routing key. It corresponds to the routing key.

SUA link
An SUA link is a link that connects two SCTP endpoints through the SUA protocol.

SUA link set

An SUA link set is a set of all SUA links between an SG and an AS, or between two ASs.

Independent Point Code Mode

If all ASs have a unique point code, it is called an AS independent point code mode, otherwise,
it is called an AS dependent point code mode.

9.1.2 Networking Structure for Configuring the SUA Data

This section describes the networking structure for configuring the SUA data.
As shown in Figure 9-6, when you configure the SUA data, the SG7000 interconnects with
another equipment (SMSC in the figure) through the SUA protocol. When the SUA protocol is
used to construct the network, other equipment is not required to support the MTP3 and its lower-
layer narrowband protocols.

NOTE

The SUA protocol is applied in two networking modes: SG-ASP application mode and IPSP application
mode. The two modes are similar except for the belonging-to application network. This document takes
SG-ASP application mode for an example.

Figure 9-6 Networking structure for configuring the SUA data

9.1.3 Relations Between Data Tables

This section describes the mapping relations between data tables related to the SUA data
configuration.
Figure 9-7 shows the relations between SUA data tables. Figure 9-7 shows the configuration
sequences from the top to the bottom. When adding records to the tables, conduct the operations
from the upper tables to the lower ones. When removing records from the tables, conduct the
operations from the lower tables to the upper ones.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 9-7

l For example, add a DSP and all its related information (the SUA AS, SUA link set, and
SUA link).
Correct steps: Add the DSP -> Add the SUA AS -> Add the SUA link set -> Add the SUA
link.
l For another example, remove a DSP and all its related information (the SUA AS, SUA link
set, and SUA link).
Correct steps: Remove the SUA link -> Remove SUA link set -> Remove the the SUA AS
-> Remove the DSP.

Figure 9-7 Relations between SUA data tables

NOTE

l Note: Data of any table can be removed only when the data is in unavailable state.
l Before removing a configuration table, make sure that this table is not referenced by other tables.

9.1.4 Data Collection

Before configuring the SUA data, you must collect the information including the SUA AS type,
DPC, remote IP address, and remote port number.

Table 9-1 lists the SUA data to be collected.

9-8 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Table 9-1 SUA data collection table

SUA AS type DSP DPC Local SPC Remote IP

address

Remote port Local IP Port number of C/S mode

address local end

Routing context Link work

mode

9.1.5 Configuration Principles

This section describes the principles to be followed when you configure the SUA data.

Principles for Configuring the Local IP Address Combination

l During local IP address binding of the SCTP, the first IP address is regarded as the preferred
IP address.
If the preferred IP address is unavailable, the second IP address in the combination will be
chosen. In this case, different index sequences indicate different priorities of the IP
addresses and different IP address sequences indicate different address combinations.
l When configuring the links in the same frame, you must configure the first IP address in
the local IP address combination index as the IP address of the SBPI in this frame. This
enables the data in the same frame to be sent from the SBPI in this frame in priority, thus
reducing inter-frame data transfer. For example, there are three local IP addresses
(10.11.200.1, 10.11.200.2, and 10.11.200.3) which correspond to the local IP address
indexes 1, 2, and 3, and correspond to the SBPIs in slots 1, 2, and 3. When you configure
the local IP address combination table, and the following local IP address combinations are
configured:
– Combination 1: 1, 2, and 3
– Combination 2: 2, 1, and 3
– Combination 3: 3, 2, and 1
they are three different IP address combinations. If the link is configured on a board in
frame 1, the combination 1 is preferred; If the link is configured on a board in frame 2, the
combination 2 is preferred; and If the link is configured on a board in frame 3, the
combination 3 is preferred. This ensures that the messages are sent from the SBPIs in this
frame.

Principles for Configuring the SUA Link

l The broadband links configured on the same SBPU/SBPE reference the same local IP
address combination index. The first IP address in the combination index references the IP
address of the SBPI in the same frame as the SBPU/SBPE.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 9-9

l If the broadband links configured on the same SBPU/SBPE cannot reference the same local
IP address combination index, you must ensure that no identical IP address index exists in
different IP address combinations.
l The broadband links on the same board are configured based on the following conditions:
– If the local network ports are different, the local IP address combination index can be
chosen freely; however, you must avoid the situation of inter-frame message transfer.
– If the local network ports are the same, you are recommended to choose the same local
IP address combination index. If the local IP address combinations are different, you
must judge whether the identical local IP address exists in different local IP address
combination. If yes, the broadband link cannot be added.

9.1.6 General Steps

You must follow certain procedures to configure the SUA data.
Configuring the SUA data contains the following lines:
l Configure the IP address and configure the IP address combination.
l Configure the route selection data based on the following sequences: configure the local
office information -> configure the AS -> configure the link set -> configure the link. The
method is the same as that for configuring the MTP route selection data.
Before configuring the SUA data, make sure that the hardware data, local office data, and SCTP
data is already configured. See Table 9-2 for general steps.

Table 9-2 General steps for configuring the SUA data

Step Operation

1 Add the local IP address (ADD LIP)

2 Add the local IP address combination (ADD LIPC)

3 Add the remote IP address (ADD RIP)

4 Add the remote IP address combination (ADD RIPC)

5 Add the access control information (ADD IPDACL)

6 Add the MTP DSP (ADD N7DSP)

7 Add the SUA application server (ADD SUAAS)

8 Add the SUA association set (ADD SUALKS)

9 Add the SUA association (ADD SUALNK)

NOTE

The destination signaling point table and local office information table are used by all protocol data.

9-10 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

9.2 Configuring the SUA Data

Configuring the SUA data includes the following: configuring the local IP address, configuring
the local IP address combination, and configuring the SUA link.
When you configure the SUA data, the purpose of configuring the IP address table and IP address
combination table is to flexibly configure the local IP address and remote IP address
combinations to implement the SCTP multi-homing feature, thus ensuring reliable message
transmission.
After the local IP address and remote IP address combinations are configured, you can reference
the indexes of these combinations when you run the ADD SUALNK command.
9.2.1 Adding the Local IP Address
The local IP address table is the FE interface configuration table of the SCTP associations. The
local IP address table is used to allocate IP addresses for the FE interfaces of the SBPIs when
adding the SBPIs.
9.2.2 Adding the Local IP Address Combination
The IP address table and IP address combination table are configured to flexibly combine the
local IP addresses and remote IP addresses to ensure the reliability of the broadband links based
on the multi-homed feature of the SCTP.
9.2.3 Adding the Remote IP Address
It is typically the IP address of the corresponding interface board of the softswitch in case of this
equipment interworks with a softswitch.
9.2.4 Adding the Remote IP Address Combination
This command is used to add the remote IP address combination after the remote IP address is
added. It uses the SCTP multi-homing feature to ensure the reliability of the broadband links
between this equipment and the peer-end equipment and enhance the anti-fault capability of the
equipment.
9.2.5 Adding the Access Control Information
This command is used to add the remote IP addresses in the remote IP address list on this
equipment in order that the remote IP address can normally access the local office. The IP
addresses that are not configured in the list cannot access this equipment.
9.2.6 Adding the MTP DSP
The SUA data and the MTP data use the same N7DSP table. The difference is that, the parameter
SUA point code is set to True when the table is used for configuring the SUA DSP.
9.2.7 Adding the SUA Application Server
The function of the SUA application server table is similar to that of the MTP DSP table. When
a record is added to the SUA AS table, the system allocates an idle index for the record.
9.2.8 Adding the SUA Link Set
It can be used to configure all information of an SUA link set directed from the local office to
an SUA application server. When a record is added to the SUA link set table, the system allocates
an idle index for the record.
9.2.9 Adding the SUA Link
When a record is added to the SUA link table, the system allocates an idle index for the record.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 9-11

9.2.1 Adding the Local IP Address

The local IP address table is the FE interface configuration table of the SCTP associations. The
local IP address table is used to allocate IP addresses for the FE interfaces of the SBPIs when
adding the SBPIs.

The local IP address must be configured when you configure the hardware data, that is, before
you add the SBPIs. See 2.2.3 Adding Local IP Address for the method of adding the local IP
address.

9.2.2 Adding the Local IP Address Combination

The IP address table and IP address combination table are configured to flexibly combine the
local IP addresses and remote IP addresses to ensure the reliability of the broadband links based
on the multi-homed feature of the SCTP.

The local IP address combination table contains up to 16 local IP address indexes. Different IP
address sequences represent different IP address combinations. The sequence of the IP address
indexes from 1 to 16 indicates different priorities (from higher to lower). If the FE interface
corresponding to an IP address with higher priority becomes faulty, the FE interface
corresponding to the IP address priority with lower priority will replace the faulty one and ensures
the reliability of the broadband link.

FE indexes 1-16 are the indexes of the local IP addresses that are already defined in the local IP
address table. The index of a local IP address can be queried through LST RIP.

Command
ADD LIPC

Parameter
Parame Paramete Parameter Description
ter ID r Name

DESC Descriptio It specifies the local IP address combination to be added.

n It is the descriptive information. It is optional. It is null by default.

FEX1 FE index 1 It specifies the index of the local IP address whose priority is the
highest.
It is mandatory. Its value is of the numeral type and ranges 0-127.
You can query the index of the IP address whose priority is the
highest through LST LIP.

FEX2-1 FE It is optional. Its value is of the numeral type and ranges 0-65535. It
6 indexes is set to 65535 by default, indicating that this index is invalid.
2-16 If the SCTP has the multi-homing feature, you must enter the index
of the valid IP address. You must set FE indexes 2-16 orderly, that
is, FE index 2, FE index 3, FE index 4, ..., and FE index 16. Any
index in the range of FE indexes 1-16 is unique.

9-12 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Related Commands

Table 9-3 Related commands for configuring the local IP address combination

Command Function

ADD LIPC To add the local IP address combination

RMV LIPC To remove the local IP address combination

MOD LIPC To modify the local IP address combination

LST LIPC To query the local IP address combination

9.2.3 Adding the Remote IP Address

It is typically the IP address of the corresponding interface board of the softswitch in case of this
equipment interworks with a softswitch.

Command
ADD RIP

Parameter
Parame Paramete Parameter Description
ter ID r Name

DESC Remote IP It specifies the remote IP address to be added.

address It is the descriptive information. It is optional. It is null by default.
title

RIP Remote IP It maps a remote IP address.

address It is mandatory and its value is of character type. It must be configured
by negotiating with the peer end.

Related Commands

Table 9-4 Related commands for configuring the remote IP address

Command Function

ADD RIP To add the remote IP address

RMV RIP To remove the remote IP address

MOD RIP To modify the remote IP address

LST RIP To query the remote IP address

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 9-13

9.2.4 Adding the Remote IP Address Combination

This command is used to add the remote IP address combination after the remote IP address is
added. It uses the SCTP multi-homing feature to ensure the reliability of the broadband links
between this equipment and the peer-end equipment and enhance the anti-fault capability of the
equipment.

The remote IP address is used to communicate with the remote equipment over broadband links.
Many remote IP addresses are combined based on combination rules to form an address group,
that is called remote IP address combination.

Among these remote IP addresses combined, only one IP address is in active state and others
are in standby state. In case that this active IP address is unavailable, a new IP address becomes
active based on the priority of the standby IP addresses.

Command
ADD RIPC

Parameter
Parame Paramete Parameter Description
ter ID r Name

DESC Descriptio It specifies the remote IP address combination to be added.

n It is the descriptive information. It is optional. It is null by default.

RIPX1 Remote IP It specifies the index of the local IP address whose priority is the
Address highest.
Index 1 It is mandatory. Its value is of the numeral type and ranges 0-2047.
The index of a remote IP address can be queried through LST RIP.

RIPX2- Remote IP It is optional. Its value is of the numeral type and ranges 0-65535. It
16 Address is set to 65535 by default, indicating that this index is invalid.
Index 2- You must first set Remote IP address index 1, and then Remote IP
Remote IP address index 2, then Remote IP address index 3, .... Set Remote
Address IP address index 16 at last. In addition, any index from Remote IP
Index 16 address index 1 to Remote IP address index 16 must be unique.
The index of a remote IP address can be queried through LST RIP.

Related Commands

Table 9-5 Related commands for configuring the remote IP address combination

Command Function

ADD RIPC To add the remote IP address combination

RMV RIPC To remove the remote IP address combination

MOD RIPC To modify the remote IP address combination

9-14 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Command Function

LST RIPC To query the remote IP address combination

9.2.5 Adding the Access Control Information

This command is used to add the remote IP addresses in the remote IP address list on this
equipment in order that the remote IP address can normally access the local office. The IP
addresses that are not configured in the list cannot access this equipment.
This function is equal to a filter or firewall. The system intercepts the packets related to the IP
addresses that are not added to the access control table. If a remote IP address is added in the
local office but its access control authority is not added, the remote IP address cannot access the
local office.

Command
ADD IPDACL

Parameter
Parame Paramete Parameter Description
ter ID r Name

DESC Descriptio It specifies the record to be added.

n It is the descriptive information. It is optional. It is null by default.

IP IP address It specifies the added IP address by which the remote device accesses
the local device.
It is mandatory and its value is of character type. It must be set based
on the actual conditions.

Related Commands

Table 9-6 Related commands for configuring the access control information
Command Function

ADD IPDACL To add the access control information

RMV IPDACL To remove the access control information

MOD IPDACL To modify the access control information

LST IPDACL To query the access control information

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 9-15

9.2.6 Adding the MTP DSP

The SUA data and the MTP data use the same N7DSP table. The difference is that, the parameter
SUA point code is set to True when the table is used for configuring the SUA DSP.
See 4.2.1 Adding MTP DSP for the method of adding the MTP DSP.

9.2.7 Adding the SUA Application Server

The function of the SUA application server table is similar to that of the MTP DSP table. When
a record is added to the SUA AS table, the system allocates an idle index for the record.

Command
ADD SUAAS

Parameter
Parame Paramet Parameter Description
ter ID er Name

DESC SUA It specifies the SUA AS to be added.

applicatio It is the descriptive information. It is optional. It is null by default.
n server
title It is recommended to use the name format "abbreviated city
name_equipment type_equipment serial number".

RC Routing It specifies the context of the route corresponding to an application

context server. In SUA, the application server and route context correspond
to each other uniquely.
The route context configured on the SUA AS must be consistent with
that configured on the AS of the peer side.
It is mandatory. Its value is of the numeral type and ranges 0-65535.

DPCX DSP It maps a record in the MTP DSP table. The parameter SUA point
index code of the referenced record must be set to True.
It is mandatory. Its value is of the numeral type and ranges 0-2047.
It is used when GT translation is required for protocol translation.

ASTYP SUA AS It specifies the network indication type of a destination entity. It

E type specifies the network type of the interworking equipment.
It is optional and its value is of the enumeration type. It can be set to:
l TM (SUA point code)
l AM (SUA IP address)
It is set to SUA point code by default.

9-16 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Parame Paramet Parameter Description

ter ID er Name

NI Network It can be set to:

indication l IM (International)
l IS (International reserved)
l NM (National)
l NS (National reserved)

DSP SUA It maps SUA AS type. This parameter is valid only when Destination
point code entity type is set to SUA point code.
It is optional. Its value contains 6-digit hexadecimal numbers, such
as, AAAAAA.

IP IP address It maps SUA AS type. This parameter is valid only when Destination
entity type is set to SUA IP address.
It is optional and its value is of the character string type, such as
192.168.1.1.

Related Commands

Table 9-7 Related commands for configuring the SUA application server
Command Function

ADD SUAAS To add the SUA application server

RMV SUAAS To remove the SUA application server

MOD SUAAS To modify the SUA application server

LST SUAAS To query the SUA application server

9.2.8 Adding the SUA Link Set

It can be used to configure all information of an SUA link set directed from the local office to
an SUA application server. When a record is added to the SUA link set table, the system allocates
an idle index for the record.

Command
ADD SUALKS

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 9-17

Parameter
Parame Paramete Parameter Description
ter ID r Name

DESC SUA It specifies an SUA link set to be added. Both Chinese and English
associatio characters are supported.
n set title It is the descriptive information. It is optional. It is null by default.

ASX Adjacent It specifies the index of the adjacent application server to which this
applicatio SUA link set is connected. It references the index of a record
n server generated by using ADD SUAAS.
index It is mandatory. Its value is of the numeral type and ranges 0-255.

ASC Associatio It determines how to distribute the traffic load over several SUA links
n select directed to the same SUA application server. This value is in effect
mask code the mask code of load-sharing mode. The value is a decimal value of
a 4-bit binary number. For example, for the link select mask code
1001, the corresponding decimal value is 5. It is set to 0 by default.
The configuration principles of the parameter are as follows:
l Set all bits to 0 if there is only one SUA link.
l Set any one bit to 1 when there are two SUA links.
l Set any two bits to 1 when there are 3-4 SUA links.
l Set any three bits to 1 when there are 5-8 SUA links.
l Set all four bits to 1 when there are more than eight SUA links.

TM Traffic It specifies the traffic mode of the SUA links in this SUA link set.
mode It is optional and its value is of the enumeration type. It can be set to:
l OVERRIDE (Override): It is the N+1 backup mode. In this mode,
only one SUA link in the link set is active and bears services, and
the other SUA links are in the standby state. When the active SUA
link is faulty, one of the standby SUA links is activated and bears
services.
l LOADSHARE (LoadShare): All SUA links in the SUA link set
are active and the traffic is shared by all SUA links in the SUA
link set.
It is set to LOADSHARE by default.
The two ends interconnected by the same SUA link set must be in
the same transmission mode; otherwise, the SUA links cannot work
normally. It is recommended to use the load sharing mode.

9-18 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Parame Paramete Parameter Description

ter ID r Name

WM Work It specifies the working mode of this SUA link set.

mode It is mandatory and its value is of enumeration type. It can be set to:
l ASP (Act AS ASP): The local SUA link set works in application
server mode.
l SGP (Act AS SGP): The local SUA link set works in signaling
gateway mode.
l IPSPS (Act AS IPSP): The local SUA link set works in IP server
mode.
l IPSPC (IP client): The local SUA link set works in IPSP client
mode.
On the SG7000, it is generally set to SGP or IPSPS.

Related Commands

Table 9-8 Related commands for configuring the SUA link set
Command Function

ADD SUALKS To add the SUA link set

RMV SUALKS To remove the SUA link set

MOD SUALKS To modify the SUA link set

LST SUALKS To query the SUA link set

9.2.9 Adding the SUA Link

When a record is added to the SUA link table, the system allocates an idle index for the record.

Command
ADD SUALNK

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 9-19

Parameter
Parame Paramete Parameter Description
ter ID r Name

DESC SUA It specifies the SUA link to be added.

associatio It is the descriptive information. It is optional. It is null by default.
n title
The format of the name is "abbreviated city name_equipment
type_equipment serial number" + "Link port number", such as,
BJG1-L0.

SN Shelf It specifies the number of the shelf where the SBPU/SBPE bearing
number the SUA link is located.
It is mandatory and its value is of the numeral type. Its value range
is 0-4. It must be configured based on actual conditions.

FN Frame It specifies the number of the frame where the SBPU/SBPE bearing
number the SUA link is located.
It is mandatory and its value is of the numeral type. Its value range
is 0-3. It must be configured based on actual conditions.

BN Slot It specifies the number of the slot where the SBPU/SBPE bearing the
number SUA link is located.
It is mandatory. Its value is of the numeral type and ranges 0-16.

PLNO Board It specifies the number specified for the SUA link on an SBPU/
Assoc. SBPE. An SBPU/SBPE can be configured with up to 32 SUA links.
number It is mandatory. Its value is of the numeral type and ranges 0-31.
You must select an unused link number here.

LIPCX Local IP It specifies the index of the local IP address combination to which
combinati the SCTP association bearing this SUA link is bound. It references
on index the index of the record generated in the command ADD LIPC.
It is mandatory. Its value is of the numeral type and ranges 0-2047.

LP Local port It specifies the local port number of the SCTP association bearing
this SUA link.
It is optional. Its value is of the numeral type and ranges 1024-65534.
It is set to 14001 by default.
It must be configured by referencing the configuration of the peer-
end equipment.

RIPCX Remote IP It specifies the index of the remote IP address combination to which
combinati the SCTP association bearing this SUA link is bound. It references
on index the index of the record generated in the command ADD RIPC.
It is mandatory. Its value is of the numeral type and ranges 0-2047.
This configuration is used to support the multi-homing function of
the peer SCTP links, thus enhancing the reliability of the system.

9-20 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Parame Paramete Parameter Description

ter ID r Name

RP Remote It specifies the remote port number of the SCTP association bearing
port this SUA link.
It is optional. Its value is of numeral type and ranges 1024-65534. It
is set to 14001 by default.
It must be configured by referencing the configuration of the peer-
end softswitch equipment.

CS C/S mode It specifies the local working mode of the SCTP association bearing
this SUA link.
It is mandatory and its value is of enumeration type. It can be set to:
l C (Client side): The local SCTP association is a client.
l S (Server side): The local SCTP association is a server.
It determines whether this equipment is interconnected with the peer
equipment as the client or as the server. When this equipment acts as
the server, the peer equipment must act as the client. Negotiation is
required for configuring this parameter. Typically this equipment is
configured to act as the server, and the peer equipment is configured
to act as the client.

ASSI SUA It specifies the index of the SUA link set to which this SUA link
associatio belongs. It references the index of a record generated by using ADD
n set index SUALKS.
It is mandatory. Its value is of the numeral type and ranges 0-255.

ASF Active_sta It specifies the initial working status of this SUA link. It is enabled
ndby flag only when Traffic mode of the SUA link set is set to Override.
It is mandatory and its value is of enumeration type. It can be set to:
l NO (Standby initially): It indicates that the initial working status
of this SUA link is standby mode.
l YES (Active initially): It indicates that the initial working status
of this SUA link is active mode.

PRI Priority It specifies the priority of the SUA links to be chosen within the same
SUA link set. It is enabled only when Traffic mode of the SUA link
set is set to LoadShare.
It is optional. Its value is of numeral type and ranges 0-254 is set to
0 by default.
The links with higher priorities are chosen first. The links with lower
priorities cannot carry the signaling traffic until all the links with
higher priorities become unavailable. The value 0 stands for the
highest priority and the value 1 stands for the second highest priority.

MAXIS Max. in It specifies the maximum number of the incoming streams that the
streams SCTP association bearing this SUA link can accommodate.
It is optional. Its value is of numeral type and ranges 1-17. It is set to
17 by default.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 9-21

Parame Paramete Parameter Description

ter ID r Name

MAXO Max. out It specifies the maximum number of the outgoing streams that the
S streams SCTP association bearing this SUA link can accommodate.
It is optional. Its value is of numeral type and ranges 1-17. It is set to
17 by default.

SCTPI SCTP It specifies the SCTP parameter that is referenced by this SUA link.
DX index It references the index of the record generated in the command ADD
SCTPPP.
It is mandatory. Its value is of the numeral type and ranges 0-127.

Related Commands

Table 9-9 Related commands for configuring the SUA link

Command Function

ADD SUALNK To add the SUA link

RMV SUALNK To remove the SUA link

MOD SUALK To modify the SUA link

LST SUALK To query the SUA link

9.3 Configuration Examples

This section provides examples to describe how to configure the SUA data.

Example Description
As shown in Figure 9-8, the destination entity type of the SG7000 is signaling point code.

Figure 9-8 Networking structure for configuring the SUA data

9-22 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Two SUA links are established between the SMSC and the SG7000. The services on the links
use the load-sharing mode. Slots 5 and 10 of the SG7000 are configured with SBPIs, used for
providing the local IP address. The data collected for configuring the SUA data is as listed in
Table 9-10.

Table 9-10 SUA data collection table

SUA AS type DSP DPC Local SPC Remote IP

address

SUA point code B1111B A1111A 11.11.11.1/255.2

(National) (National) 55.0.0

Remote port Local IP Port number of C/S mode

address local end

SUA link 0: 10.10.10.1/255.2 14001 SERVER

14001; SUA link 55.0.0
1: 14002

Routing context Link work

mode

1166 LoadShare

The following example describes the SUA data configuration in SCCP single-point working
mode. It starts from the SCCP-related local office data configuration. The hardware data, SCCP
data, and MTP data configurations are omitted.

Procedure
Step 1 To configure the local office data, where First searched network to National, National
network code is A1111A, SCCP function to TRUE, and Logic network index is the default
value 0, run the following command:
SET OFI: SN1=NM, NPC="A1111A", SCCP=TRUE;

Step 2 To add the local IP address, run the following command. Suppose that after the command is
successfully executed, the index 2 is generated.
ADD LIP: LIP="10.10.10.1", MSK="255.255.0.0", DGW="10.10.1.1";

Step 3 To add SBPIs for slots 5 and 10, where Board property indicator is 2 and the IP address
allocated to the SBPI is 10.10.10.1/255.255.0.0, run the following command:
ADD BRD: FN=0, SHN=0, FT=MAIN, SN=5, LOC=FPB, BT=SBPI, PI=2;
ADD BRD: FN=0, SHN=0, FT=MAIN, SN=10, LOC=FPB, BT=SBPI, PI=2;

Step 4 To add the local IP address combination, where Index 1 is the IP address of the SBPI in this
frame and the index of the IP address is 2, run the following command. Suppose that after the
command is successfully executed, the index 0 is generated.
ADD LIPC: FEX1=2;

Step 5 To add the remote IP address, run the following command. Suppose that after the command is
successfully executed, the index 0 is generated.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 9-23

ADD RIP: RIP="11.11.11.1";

Step 6 To add the remote IP address combination, where Index 1 is 0, run the following command.
Suppose that after the command is successfully executed, the index 0 is generated.
ADD RIPC: RIPX1=0;

Step 7 Add the IP address of the SMSC to the access control table.
ADD IPDACL: IP="11.11.11.1";

Step 8 To add the MTP DSP, where DSP title is HW-A, National network code is B1111B, Route
selection field is 0 (for only one link set), SUA point code is True, run the following command.
Suppose that after the command is successfully executed, the index 1 is generated.
ADD N7DSP: DESC="HW-A", NPC="B1111B", SLS=0,SUAPOINT=TRUE;

Step 9 To add the SUA AS, where Route context is 1166, DPC index is 1, SUA AS Type is SUA
point code, Network indication is National network, SUA point code is B1111B, run the
following command. Suppose that after the command is successfully executed, the index 0 is
generated.
ADD SUAAS: RC=1166, DSPIDX=1, ASTYPE=TM, NI=NM, DSP="B1111B";

Step 10 To add the SUA link set, where Adjacent application server index is 0, Association select
mask code is 1 (for two SUA links), and Work mode is Act as SGP, run the following command.
Suppose that after the command is successfully executed, the index 0 is generated.
ADD SUALKS: ASX=0, WM=SGP, ASC=1;

Step 11 To add the first SUA link, where SUA association title is 0, Remote port is 14001, Priority is
0, Work mode is LoadShare, and keep other parameters as the default values, run the following
command.
ADD SUALNK: SN=0, FN=0, BN=0, PLNO=0, LIPCX=0, RIPCX=0, CS=S, ASSI=0, ASF=YES,
SCTPIDX=0;

Step 12 To add the second SUA link, where SUA association title is 1, Remote port is 14002,
Priority is 1, Work mode is LoadShare, and keep other parameters as the default values, run
the following command.
ADD SUALNK: SN=0, FN=0, BN=0, PLNO=1, LIPCX=0, LP=14002, RIPCX=0, RP=14002, CS=S,
ASSI=0, ASF=YES, SCTPIDX=0;

----End

9-24 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

10 Configuring the SUA Shielding Data

About This Chapter

This chapter describes how to configure the SUA shielding data. Before configuring the SUA
shielding data, you must ensure that the hardware data, local office data, and SCTP data is already
configured.
To configure the SG7000 data, follow the procedure as shown in Figure 10-1. In this way, the
key fields are defined before they are referenced by other data tables and no junk data is
generated.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 10-1

Figure 10-1 Data configuration procedure

10.1 Configuration Preparations

This section describes the related background information, terms, and general steps for
configuring the SUA shielding data.
10.2 Configuring the SUA Shielding Data
Configuring the SUA shielding data includes adding the SUA message type screen table, adding
the calling DPCSSN shielding table, and adding the calling GT shielding table.
10.3 Configuration Examples
This section provides examples to describe how to configure the SUA shielding data.

10-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

10.1 Configuration Preparations

This section describes the related background information, terms, and general steps for
configuring the SUA shielding data.
10.1.1 Terms
This section describes the terms used when you configure the SUA shielding data.
10.1.2 Networking Structure of the SUA Shielding
The networking structure for configuring the SUA shielding data is the same as that for
configuring the SUA data.
10.1.3 Relations Between Data Tables
This section describes the mapping between data tables related to the SUA shielding data
configuration.
10.1.4 Data Collection
Before configuring the SUA shielding data, you must plan the shielding conditions in advance.
10.1.5 General Steps
You must follow certain procedures to configure the SUA shielding data.

10.1.1 Terms
This section describes the terms used when you configure the SUA shielding data.
The SUA shielding function is used to shield the received messages that have some special
features. The features can be classified into the following types:
l Message class and message type of the SUA messages
l DPC+SSN
l GT code
l GT translation type

One or more of the preceding items can be combined to form a shielding condition to filter the
specific messages.

10.1.2 Networking Structure of the SUA Shielding

The networking structure for configuring the SUA shielding data is the same as that for
configuring the SUA data.
As shown in Figure 10-2, when you configure the SUA shielding data, the SG7000 interconnects
with another equipment (SMSC in the figure) through the SUA protocol. When the SUA protocol
is used to construct the network, other equipment is not required to support the MTP3 and its
lower-layer narrowband protocols.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 10-3

Figure 10-2 Networking structure for configuring the SUA data

10.1.3 Relations Between Data Tables

This section describes the mapping between data tables related to the SUA shielding data
configuration.
Configuring the SUA shielding data can be classified into three lines:
l Line one: It is a shielding chain starting from the SUA message type screen table.
l Line two: It is a shielding chain starting from the calling SCCPSSN shielding table.
l Line three: It is a shielding chain starting from the calling GT shielding table.

The reference relations between the SUA message type screen table and other tables are not
specified here. As shown in Figure 10-4, the parameter Shielding reference in a table can be
referenced only by the shielding tables above.
It is recommended to add a shielding chain from bottom to top, that is, add the shielding table
(as shown in Figure 10-3 or Figure 10-4) at the bottom first, and then add the shielding table
above it. When deleting a shielding chain, delete the shielding table at the top of the shielding
chain, and then delete the shielding table below it, because the referenced shielding table cannot
be deleted.

10-4 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Figure 10-3 Reference relations starting from the calling SCCPSSN

ADD SCCPCDS

[ Next Shielding reference ]

ADD SCCPDGT
[ Shielding reference ]
[ Next Shielding reference ]

ADD SCCPMT
[ Shielding reference ]
[ Next Shielding reference ]

ADD SCCPDDS

[ Shielding reference ]

ADD SCCPDGTT

[ Shielding reference ]

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 10-5

Figure 10-4 Reference relations starting from the calling GT

ADD SCCPCGT

[ Next Shielding reference ]

ADD SCCPCGTT
[ Shielding reference ]
[ Next Shielding reference ]

ADD SCCPMT
[ Shielding reference ]
[ Next Shielding reference ]

ADD SCCPDGT
[ Shielding reference ]
[ Next Shielding reference ]

ADD SCCPDSS

[ Shielding reference ]

ADD SCCPDGTT

[ Shielding reference ]

10.1.4 Data Collection

Before configuring the SUA shielding data, you must plan the shielding conditions in advance.
Table 10-1 illustrates the data to be collected for configuring the SUA shielding data.

Table 10-1 Data collection table

Class of the messages to be shielded Type of the messages to be
shielded

10.1.5 General Steps

You must follow certain procedures to configure the SUA shielding data.
The sequences for configuring the SUA shielding data are as listed in Table 10-2, Table 10-3,
and Table 10-4. The last step in each table is mandatory. Each table except for the last refers to
a shielding condition and thus they are optional. During configuration, configure one or more

10-6 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

required shielding tables according to the sequences as listed in Table 10-2, Table 10-3, and
Table 10-4.
The calling DPCSSN shield table or the calling GT shield table can be used only as the start
shielding condition in a shielding chain; the called DPCSSN shield table or the called GT shield
table can be used only as the end shielding condition in a shielding chain.

Table 10-2 Configuring the SUA shielding data

Step Operation

1 To add SUA message type screen table (ADD SUAMS)

Table 10-3 Configuring the SCCPSSN shielding data

Step Operation

1 To add the called GT type shielding (ADD SCCPDGTT)

2 To add the called GT shielding (ADD SCCPDGT)

3 To add the SCCP message type shielding table (ADD SCCPMT)

4 To add the called DPCSSN shielding (ADD SCCPDDS)

5 To add the caller DPCSSN shielding (ADD SCCPCDS) (Mandatory)

Table 10-4 Configuring the caller GT shielding data

Step Operation

1 To add the called GT type shielding (ADD SCCPDGTT)

2 To add the called GT shielding (ADD SCCPDGT)

3 To add the SCCP message type shielding table (ADD SCCPMT)

4 To add the called DPCSSN shielding (ADD SCCPDDS)

5 To add the caller GT type shielding (ADD SCCPCGTT)

6 To add the caller GT shielding (ADD SCCPCGT) (Mandatory)

10.2 Configuring the SUA Shielding Data

Configuring the SUA shielding data includes adding the SUA message type screen table, adding
the calling DPCSSN shielding table, and adding the calling GT shielding table.
SUA is the SCCP User Adaptation part and it retains all SCCP shielding functions. For the
method of configuring the SCCP shielding data, see 7 Configuring SCCP Shielding Data.
10.2.1 Adding the SUA Message Type Screen Table

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 10-7

This table is used to shield the SUA messages based on SUA message class and message type.

10.2.1 Adding the SUA Message Type Screen Table

This table is used to shield the SUA messages based on SUA message class and message type.

Command
ADD SUAMS

Parameter
Parame Paramet Parameter Description
ter ID er Name

DESC Descripti It specifies a record to be added.

on It is optional. Its value is of the character string type. It is null by
default.

SCREE Screen It controls whether to enable the message screening function. It can
NSWT function be set to:
switch l FALSE (Off)
l TRUE (On)
It is set to Off by default.

MSGC Message It specifies the class of the SUA message to be screened. Its value
LASS class range is 0-255.
This parameter is related to Message type. You must set Message
class before setting Message type.
It can be set to:
l 0 SUA Management (MGMT) Message
l 1 Reserved
l 2 Signalling Network Management (SNM) Messages
l 3 ASP State Maintenance (ASPSM) Messages
l 4 ASP Traffic Maintenance (ASPTM) Messages
l 5 Reserved
l 6 Reserved
l 7 Connectionless(CL) Messages
l 8 Connection-Oriented(CO) Messages
l 9 Routing Key Management (RKM) Messages
l 10 - 127 Reserved by the IETF
l 128 - 255 Reserved for IETF-Defined Message Class Extensions

10-8 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Parame Paramet Parameter Description

ter ID er Name

MSGT Message It specifies the type of the SUA message to be screened. Its value
YPE type range is 0-255.
This parameter is related to Message class. You must set Message
class before setting Message type.
It can be set to:
l SUA Management Messages
– 0 Error (ERR)
– 1 Notify (NTFY)
– 2 - 127 Reserved by the IETF
– 128- 255 Reserved for IETF-Defined Message Class Extensions
l Signalling Network Management (SNM) Messages
– 0 Reserved
– 1 Destination Unavailable (DUNA)
– 2 Destination Available (DAVA)
– 3 Destination State Audit (DAUD)
– 4 Signalling Congestion (SCON)
– 5 Destination User Part Unavailable (DUPU)
– 6 Destination Restricted (DRST)
– 7 - 127 Reserved by the IETF
– 128 - 255 Reserved for IETF-Defined Message Class
Extensions
l Application Server Process State Maintenance (ASPSM)
Messages
– 0 Reserved
– 1 ASP Up (UP)
– 2 ASP Down (DOWN)
– 3 Heartbeat (BEAT)
– 4 ASP Up Ack (UP ACK)
– 5 ASP Down Ack (DOWN ACK)
– 6 Heartbeat Ack (BEAT ACK)
– 7 - 127 Reserved by the IETF
– 128 - 255 Reserved for IETF-Defined Message Class
Extensions
l ASP Traffic Maintenance (ASPTM) Messages
– 0 Reserved
– 1 ASP Active (ACTIVE)
– 2 ASP Inactive (INACTIVE)

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 10-9

Parame Paramet Parameter Description

ter ID er Name

– 3 ASP Active Ack (ACTIVE ACK)

– 4 ASP Inactive Ack (INACTIVE ACK)
– 5 - 127 Reserved by the IETF
– 128 - 255 Reserved for IETF-Defined Message Class
Extensions
l Connectionless (CL) Messages
– 0 Reserved
– 1 Connectionless Data Transfer (CLDT)
– 2 Connectionless Data Response (CLDR)
– 3 - 127 Reserved by the IETF
– 128 - 255 Reserved for IETF-Defined Message Class
Extensions
l Connection-Oriented (CO) Messages
– 0 Reserved
– 1 Connection Request (CORE)
– 2 Connection Acknowledge (COAK)
– 3 Connection Refused (COREF)
– 4 Release Request (RELRE)
– 5 Release Complete (RELCO)
– 6 Reset Confirm (RESCO)
– 7 Reset Request (RESRE)
– 8 Connection Oriented Data Transfer (CODT)
– 9 Connection Oriented Data Acknowledge (CODA)
– 10 Connection Oriented Error (COERR)
– 11 Inactivity Test (COIT)
– 12 - 127 Reserved by the IETF
– 128 - 255 Reserved for IETF-Defined Message Class
Extensions
l Routing Key Management (RKM) Messages
– 0 Reserved
– 1 Registration Request (REG REQ)
– 2 Registration Response (REG RSP)
– 3 Deregistration Request (DEREG REQ)
– 4 Deregistration Response (DEREG RSP)
– 5 - 127 Reserved by the IETF
– 128 - 255 Reserved for IETF-Defined Message Class
Extensions

10-10 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Related Commands

Table 10-5 Related commands for configuring the SUA message type screen table
Command Function

ADD SUAMS To add the SUA message type screen table

RMV SUAMS To remove the SUA message type screen table

MOD SUAMS To modify the SUA message type screen table

LST SUAMS To query the SUA message type screen table

10.3 Configuration Examples

This section provides examples to describe how to configure the SUA shielding data.

Example Description
This section takes the shielding on the SUA ACTIVE messages for an example.
Table 10-6 illustrates the data collected for configuring the SUA shielding data.

Table 10-6 Data collection table

Class of the messages to be shielded Type of the messages to be
shielded

4 1

Procedure
Step 1 To add a record to the SUA message type screen table, where Screen function switch is On,
Message class is 4, and Message type is 1, run the following command:
ADD SUAMS: SCREENSWT=TRUE, MSGCLASS=4, MSGTYPE=1;

----End

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 10-11

11 Configuring M3UA Data

About This Chapter

The M3UA data is required when the SG7000 connects to a softswitch device over the M3UA
protocol. Before configuring the M3UA data, make sure that the hardware data, local data, and
SCTP data are configured.
To configure the SG7000 data, follow the procedure as shown in Figure 11-1. In this way, the
key fields are defined before they are referenced by other data tables and no junk data is
generated.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 11-1

Figure 11-1 Data configuration procedure

11.1 Configuration Preparations

This section describes the command, parameter, and related commands for configuring the
M3UA data.
11.2 Configuring M3UA Data
When configuring the M3UA data, the IP address tables and IP address combination tables are
also configured to flexibly combine the local IP addresses and remote IP addresses to implement
the multi-homed feature of the SCTP, so that the messages can be transferred reliably.
11.3 Configuration Examples
This section provides examples to describe how to configure the M3UA data.

11-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

11.1 Configuration Preparations

This section describes the command, parameter, and related commands for configuring the
M3UA data.
11.1.1 Terms
This section describes the terms used during configuring the M3UA data.
11.1.2 Networking Structure
This section describes the networking structure for configuring the M3UA data.
11.1.3 Relation Between Data Tables
This section describes the relations between data tables related to M3UA data configuration.
11.1.4 Data Collection
Before configuring the M3UA data, you must collect the data including the working mode, DPC,
remote IP address, and remote port number of the SG.
11.1.5 Configuration Principles
You must follow certain principles to configure the M3UA data.
11.1.6 General Steps
You must follow certain procedures to configure the M3UA data.

11.1.1 Terms
This section describes the terms used during configuring the M3UA data.

Basic Concept of SIGTRAN Protocol

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 11-3

Figure 11-2 SIGTRAN protocol module

M3UA M2UA M2PA V5UA IUA SUA

layer layer layer layer layer layer

SCTP

MAC

M3UA: MTP3 User Adaptation M2UA: MTP2 User Adaptation

IUA: ISDN Q.921 User Adaptation V5UA: V5 User Adaptation

SCTP: Stream Control Transmission Protocol IP: Internet Protocol

M2PA: MTP2 Peer Adaptation SUA: SCCP User Adaptation

MAC: Media Access Control -

NOTE

The SG7000, at present, only supports 5 adaptation protocols, such as SUA, M2UA, M3UA, IUA, and
M2PA.

M3UA Protocol
The M3UA, which is defined by RFC3332, is the No.7 MTP3-user adaptation protocol. It uses
the stream control transmission protocol (SCTP) to transmit user signaling messages such as
ISUP, TUP, and SCCP of the No.7 MTP3 layer through the IP to achieve the seamless operation
of the MTP3 peer users in the SS7 and IP field. In the SG, the M3UA is used to transmit signaling
between the SG and media gateway controller (MGC).

Application Server (AS)

AS is a logical entity, which represents some resources and corresponds to a special "route key".
An example of an application server is a virtual database unit, handling all querying transactions
identified by "DPC/OPC/SCCP_SSN". Each AS contains a group of application server processes
(ASPs), among which one or more ASPs can process transactions.

Application Server Process (ASP)

11-4 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

IP Server Process (IPSP)

Signaling Gateway (SG)

Signaling Gateway Process (SGP)

It is a process instance of a signaling gateway. It may be in the active, standby, or load-sharing
state.

C/S Mode of SCTP Association

SCN
It is the switch signaling network.

Routing Context
It is an identification index value that identifies a routing key. It corresponds to the routing key.

M3UA Route
It refers to the path to a specific M3UA entity.

M3UA Association

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 11-5

It is a logical connection between two SCTP endpoints and it bears the M3UA.

M3UA Link Set

It refers to a set of all the M3UA links between an SG and an AS or between two ASs.

Independent Point Code Mode

If all ASs have a unique point code, it is called an AS independent point code mode, otherwise,
it is called an AS dependent point code mode.

11.1.2 Networking Structure

This section describes the networking structure for configuring the M3UA data.

In Figure 11-3, the SG7000 connects with a softswitch, for example, the Softx3000 of Huawei
Technologies Co. Ltd. (hereinafter referred to as Huawei), over the M3UA protocol during the
configuration of the M3UA data. With the M3UA protocol, the SG7000 can occupy an
independent signaling point code and share the same signaling point code with the softswitch.
The softswitch does not require to support the MTP3 and its lower-layer narrowband
protocols.

Figure 11-3 Networking structure of the M3UA data

11.1.3 Relation Between Data Tables

This section describes the relations between data tables related to M3UA data configuration.

Figure 11-4 shows the relationship between parameters and indices of the M3UA data tables.
Configure the M3UA data from the upper table to the lower table in the figure. Add the upper
tables first then the lower tables. Delete lower tables first, then the upper tables.

Example 1:

Add a destination signaling point and all its information, such as the M3UA application server,
M3UA route, M3UA link set, and M3UA link.

The correct order is: add destination signaling point -> add M3UA application server -> add
M3UA link set -> add M3UA route -> add M3UA link.

Example 2:

Delete a destination signaling point and all its information, such as the M3UA application server,
M3UA route, M3UA link set, and M3UA link.

11-6 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

The right order is: delete M3UA link -> delete M3UA route -> delete M3UA link set -> delete
M3UA application server -> delete destination signaling point.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 11-7

Figure 11-4 Relation between the M3UA data tables

ADD N7DSP
[ Index number ]
[ DSP title ]

ADD M3AS
[ DPC title ]
[ DPC Index ]
[ Application server title ]
[ Index number ]
ADD M3ASSOS

[ Adjacent application ]
server index
[ Adjacent application ]
ADD LIP
server title
[ Association set index ]
[ Index number ]
[ Association set title ]
ADD M3RT
[Application server index] ADD LIPC
[ Application server title ] [ FE index 1-16 ]
[ Association set title ]
[ Index number ]
[ Association set index ]

ADD M3ASSO ADD RIP

[ Association set title ] [ Index number ]
[ Association set index ]
ADD RIPC
[ Local IP ]
combination index Remote IP address
index 1-16
Remote IP [ Index number ]
[ ]
Combination Index

11-8 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

NOTE

l All data in tables can be deleted only when the data is not being used.
l A configuration table can be deleted only when it is not indexed by other tables.

11.1.4 Data Collection

Before configuring the M3UA data, you must collect the data including the working mode, DPC,
remote IP address, and remote port number of the SG.

Table 11-1 lists the data required when configuring the M3UA data.

Table 11-1 M3UA data collection table

SG work mode DSP code Remote IP address Remote port

number

Local IP address Local port number C/S mode Routing context

11.1.5 Configuration Principles

You must follow certain principles to configure the M3UA data.

Local IP Address Combination

l The SCTP uses the first IP address among the local IP addresses by default when the local
IP addresses are bound.
If the first IP address is not available, the second IP address in the combination is chosen,
then the third, the fourth, and so on. Therefore, the index sequence indicates the priority to
use the addresses. In addition, different IP address sequences indicate different address
combinations.
l For the connection in the same frame, the first IP address in the local IP address combination
index must be configured as the IP address of the SBPI. Thus, the data in the same frame
can be sent from the SBPI in this frame first. Thus, the number of times a data is forwarded
is decreased.
For example, there are three local IP addresses 10.11.200.1, 10.11.200.2, and 10.11.200.3
with respective indices 1, 2, and 3, which correspond to the SBPI board in three frames.
The following combinations are configured for the local IP address combination table:
– Combination 1: 1, 2, 3
– Combination 2: 2, 1, 3
– Combination 3: 3, 2, 1
The three combinations are different. It is recommended to use the combination 1 if the
link is configured on the board in the first frame. Use the combination 2 if the link is
configured on the board in the second frame. Use the combination 3 if the link is configured

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 11-9

on the board in the third frame. This ensures that the messages can be sent through the SBPI
board in the same frame as possible as the message should be.
l To add a new record of local IP address combination, the IP address index should be
configured from 1 to 16 consecutively, and there must not be an empty index not configured
between two IP address indices.

M3UA Link

When configuring broadband links, you must ensure that the combination of "local IP address
+ local port number + remote port number + remote IP address" is unique on one SG7000.
Otherwise, the first broadband link added with this combination can work normally, and other
links cannot be successfully configured.

11.1.6 General Steps

You must follow certain procedures to configure the M3UA data.

The M3UA data configuration includes the following aspects:

l Configure the IP address and IP address combination.

l Configure the routing data following the sequence of the local office information,
application server, link set, router, and link. The configuration of these routing data is the
same as that of the MTP routing data.

Configure the hardware data, local office data, and SCTP data before configuring the M3UA
data. Refer to Table 11-2 for details.

You need not perform step 8 ADD M3CR if the SG7000 works in the signaling transfer point
mode.

Table 11-2 Steps for configuring the M3UA data

Step Operation

1 To add the local IP address (ADD LIP)

2 To add the local IP address combination table (ADD LIPC)

3 To add the remote IP address (ADD RIP)

4 To add the remote IP address combination table (ADD RIPC)

5 To add the access control information (ADD IPDAL)

6 To add the MTP DSP (ADD N7DSP)

7 To add the M3UA application server (ADD M3AS)

8 To add the M3UA complementary routing (ADD M3CR) (optional)

9 To add the M3UA link set (ADD M3ASSOS)

10 To add the M3UA route (ADD M3RT)

11 To add the M3UA link (ADD M3ASSO)

11-10 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

NOTE

The destination signaling point table and local office information table are used by all protocol data.

11.2 Configuring M3UA Data

When configuring the M3UA data, the IP address tables and IP address combination tables are
also configured to flexibly combine the local IP addresses and remote IP addresses to implement
the multi-homed feature of the SCTP, so that the messages can be transferred reliably.
After the local IP address combination and remote IP address combination are configured, the
indexes of these address combinations can be referenced when configuring the data by running
ADD M3ASSO.
11.2.1 Adding Local IP Address
The local IP address table is the FE interface configuration table of SCTP associations. The
added data is used to allocate IP address for the FE port of the SBPI when you add an SPBI.
11.2.2 Adding Local IP Address Combination
The IP address tables and IP address combination tables are configured to flexibly combine the
local IP addresses and remote IP addresses to implement the multi-homed feature of the SCTP.
This is to ensure the reliability of the M3UA link.
11.2.3 Adding Remote IP Address
The parameter of the command for adding a remote IP address has only one IP address. It is
typically the IP address of the corresponding interface board of the softswitch in case of the
SG7000 interworking with a softswitch. When a new record is added, an idle index value is
allocated for it.
11.2.4 Adding Remote IP Address Combination
If a softswitch supports the multi-homed feature of the SCTP association, you can configure the
multiple remote addresses to the combination of the remote IP addresses. This configuration
supports the multi-homed feature of the SCTP association at the softswitch. The sequence of the
IP address indices 1-16 indicates different priorities (from higher to lower). If the interface
corresponding to an IP address with higher priority becomes faulty, the interface corresponding
to the IP address with lower priority will replace the faulty one and ensures the reliability of the
M3UA link.
11.2.5 Adding Access Control Information
All IP addresses of the remote equipment connected with the SG7000 through the SIGTRAN
protocol must be added here. The SG7000 checks whether the IP address of the remote equipment
is valid. The IP addresses in the IPDACL table are valid IP addresses, with which the equipment
can access the SG7000, while the equipment with the invalid IP addresses cannot access the
SG7000.
11.2.6 Adding Destination Signaling Point
The N7DSP table used, when configuring the M3UA data, is the same that is used when
configuring the MTP data.
11.2.7 Adding M3UA Application Server Data
The M3UA application server table is similar to the MTP3 destination signaling point table.
11.2.8 Adding M3UA Complementary Routing Data (Optional)
If an M3UA application server processes the signaling services in a prescribed scope, a
complementary routing must be configured to the M3UA application server. If the SG7000
works in the agent mode, a complementary routing table must be configured to indicate which
routing keys the SG7000 is serving for.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 11-11

11.2.9 Adding M3UA Link Set Data

When a new record is added in the M3UA link set table, an idle index value is allocated for the
record.
11.2.10 Adding M3UA Route Data
When a new record is added for the M3UA route, an idle index value is allocated for the record.
11.2.11 Adding M3UA Association Data
When a new record is added in the M3UA association table, an idle index value is allocated for
the record.

11.2.1 Adding Local IP Address

The local IP address table is the FE interface configuration table of SCTP associations. The
added data is used to allocate IP address for the FE port of the SBPI when you add an SPBI.
Add local IP address before adding the SBPI in hardware data configuration. See chapter 2.2.3
Adding Local IP Address for the addition of local IP address.

11.2.2 Adding Local IP Address Combination

The IP address tables and IP address combination tables are configured to flexibly combine the
local IP addresses and remote IP addresses to implement the multi-homed feature of the SCTP.
This is to ensure the reliability of the M3UA link.
The local IP address combination table contains the parameters of the 16 local IP address indices.
Different IP address sequences represent different address combinations. The sequence of the
IP address indices from 1 to 16 indicates different priorities (from higher to lower). If the FE
interface corresponding to an IP address with higher priority becomes faulty, the FE interface
corresponding to the IP address priority with lower priority will replace the faulty one and ensures
the reliability of the M3UA link.

Command
ADD LIPC

Parameter
Paramete Paramete Parameter Description
r ID r Name

FEX1-6 FE index These are the indices of the local IP addresses that are already
1-16 defined. When adding the local IP address combination, query the
index of the local IP address with the command LST LIP.
FE index 1 is mandatory and FE index 2-16 is optional.
If the SCTP has the multi-homing feature, you must enter the index
of the valid IP address. You must set FE indexes 2-16 orderly, that
is, FE index 2, FE index 3, FE index 4, ..., and FE index 16. Any
index in the range of FE indexes 1-16 is unique.

11-12 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Related Commands

Table 11-3 Related commands for configuring the local IP address combination table

Command Function

ADD LIPC To add the local IP address combination table

RMV LIPC To remove the local IP address combination table

MOD LIPC To modify the local IP address combination table

LST LIPC To list the local IP address combination table

11.2.3 Adding Remote IP Address

The parameter of the command for adding a remote IP address has only one IP address. It is
typically the IP address of the corresponding interface board of the softswitch in case of the
SG7000 interworking with a softswitch. When a new record is added, an idle index value is
allocated for it.

Command
ADD RIP

Parameter
Paramete Paramete Parameter Description
r ID r Name

RIP Remote IP It maps the remote IP address. It is mandatory. Its value is of the
address character type. The value of this parameter must be configured
under negotiation with the peer side.
Input format: 10.11.2.200.

Related Commands

Table 11-4 Related commands for configuring the remote IP address

Command Function

ADD RIP To add the remote IP address

RMV RIP To remove the remote IP address

MOD RIP To modify the remote IP address

LST RIP To list the remote IP address

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 11-13

11.2.4 Adding Remote IP Address Combination

If a softswitch supports the multi-homed feature of the SCTP association, you can configure the
multiple remote addresses to the combination of the remote IP addresses. This configuration
supports the multi-homed feature of the SCTP association at the softswitch. The sequence of the
IP address indices 1-16 indicates different priorities (from higher to lower). If the interface
corresponding to an IP address with higher priority becomes faulty, the interface corresponding
to the IP address with lower priority will replace the faulty one and ensures the reliability of the
M3UA link.
The remote IP address combination table contains up to 16 remote IP address indices. When a
new record is added, an idle index value is allocated for it.

Command
ADD RIPC

Parameter
Paramete Paramete Parameter Description
r ID r Name

RIPX1-6 Remote IP These are the indices of the remote IP addresses that are already
address defined. When adding the remote IP address combination, query
index 1-16 the index of the remote IP address with the command LST RIP.
FE index 1 is mandatory and FE index 2-16 is optional.
You must first set Remote IP address index 1, and then Remote
IP address index 2, then Remote IP address index 3, .... Set
Remote IP address index 16 at last. In addition, any index from
remote IP Address Index 1 to remote IP Address Index 16 must be
unique.

Related Commands

Table 11-5 Related commands for configuring the remote IP address combination table
Command Function

ADD RIPC To add the remote IP address combination table

RMV RIPC To remove the remote IP address combination table

MOD RIPC To modify the remote IP address combination table

LST RIPC To list the remote IP address combination table

11.2.5 Adding Access Control Information

All IP addresses of the remote equipment connected with the SG7000 through the SIGTRAN
protocol must be added here. The SG7000 checks whether the IP address of the remote equipment

11-14 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

is valid. The IP addresses in the IPDACL table are valid IP addresses, with which the equipment
can access the SG7000, while the equipment with the invalid IP addresses cannot access the
SG7000.

Command
ADD IPDACL

Parameter
Paramete Paramete Parameter Description
r ID r Name

IP IP address The remote IP address, which is allowed to access the SG7000, is

set here. If there are multiple remote IP addresses, they must be
added in the IPDACL table.

Related Commands

Table 11-6 Related commands for configuring the access control information

Command Function

ADD IPDACL To add the access control information

RMV IPDACL To remove the access control information

MOD IPDACL To modify the access control information

LST IPDACL To query the access control information

11.2.6 Adding Destination Signaling Point

The N7DSP table used, when configuring the M3UA data, is the same that is used when
configuring the MTP data.

To add the destination signaling point table, see chapter 4.2.1 Adding MTP DSP.

11.2.7 Adding M3UA Application Server Data

The M3UA application server table is similar to the MTP3 destination signaling point table.

When a new record is added in the M3UA application server table, an idle index value is allocated
for this record.

Command
ADD M3AS

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 11-15

Parameter
Paramete Paramete Parameter Description
r ID r Name

DESC Applicatio It identifies an M3UA application server interconnected with the

n server SG7000. The suggested format is
title "cityname&Equipmenttype&Equipmentnumber".

SWN Work The work mode of the SG7000 may be TM (Transfer mode) or
mode AM (Agent mode) when it interconnects with the M3UA
application server. In the transfer mode, the SG7000 has a
signaling point code, which is different from that of the AS; while
in the agent mode, their signaling point codes are the same.

DPCX Destinatio In the SG7000, the local office information table (OFI) and
n point destination signaling point table (N7DSP) are shared by both
code index M3UA and MTP3. The M3UA has no individual OFI and N7DSP.
If the SG7000 works in the transfer mode, the Destination point
code index is obtained from the destination signaling point table.
If it works in the agent mode, the Destination point code index is
obtained from the local office information table or local office OPC
information table.

DPCT Destinatio It specifies the name of a record in the local information (OFI) table
n point or DSP (N7DSP) table.
code title It is optional. Its value is of the character type and can contain up
to 40 English characters.
The principles for configuring this parameter are as follows:
l When Work mode is set to Transfer mode, the DSP title is
obtained from the DSP table.
l When Work mode is set to Agent mode, the DSP title is
obtained from the local office information (or local OPC
information) table.

RC Routing It is the index of the corresponding routing key of the application

context server. In the M3UA, application server, routing key, and routing
context correspond to each other. The Routing context configured
on the SG7000 must be consistent with that on the application
server.

11-16 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Paramete Paramete Parameter Description

r ID r Name

ASC Associatio To achieve the balance of traffic to a specific application server,

n set select an algorithm must be defined to distribute the traffic over different
mask code routes. In the SG7000, the link set select mask code participates in
the algorithm for load-sharing of the traffic. The value field is the
decimal value of the 4-bit binary number. For example, the link set
select mask code is 1001 and the corresponding decimal value is
9. It is set to 0 by default.
The configuration principle of the parameter is as follows:
l Set all bits to 0 if there is only one M3UA link set.
l Set one bit to 1 if there are two M3UA link sets.
l Set two bits to 1 if there are three or four M3UA link sets.
l Set three bits to 1 if there are five to eight M3UA link sets.
l Set all four bits to 1 if there are more than eight link sets.
l To avoid the repeated selection, do not set the selection mask
code of the link set the same as the selection mask code of the
link. It is recommended to put "1" of the two mask codes in the
different place. For example, if the link set selection mask code
is 0110, the link selection mask code can be set to 1001.

Related Commands

Table 11-7 Related commands for configuring the M3UA application server

Command Function

ADD M3AS To add the M3UA application server

RMV M3AS To remove the M3UA application server

MOD M3AS To modify the M3UA application server

LST M3AS To list the M3UA application server

11.2.8 Adding M3UA Complementary Routing Data (Optional)

If an M3UA application server processes the signaling services in a prescribed scope, a
complementary routing must be configured to the M3UA application server. If the SG7000
works in the agent mode, a complementary routing table must be configured to indicate which
routing keys the SG7000 is serving for.

The complementary routing table must be flexibly configured according to the service
requirements and actual networking mode. The parameters in the table comprise the routing key.
Through the Application server index, it has a corresponding relationship with the Routing
context of the application server.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 11-17

When a new record is added in the complementary routing table, an idle index value is allocated
for the record.

Command
ADD M3CR

Parameter
Paramete Paramete Parameter Description
r ID r Name

ASX Applicatio It specifies the application server to which the SG7000 forwards
n server the M3UA message received from the original signaling point. The
index index value here is the one allocated by the system after the running
the command ADD M3AS.

OFX Original It is the original point code index generating the service messages
point code and specifies the scope of the M3UA messages forwarded by the
index SG7000. That is, under the condition that the SG7000 receives all
signaling messages, it forwards the message whose OPC field
matches with that in the Original point code index configured
here; otherwise, the message is discarded.
The value is ALL by default, indicating that the application server
can process the messages from all the signaling points instead of
only one signaling point.

NI Network It specifies the type of network indication of the application server.

indication The options include IM (International network), IS
(International reserved network), NM (National network), NS
(National reserved network), and ALL (All). The value is
ALL by default, indicating that the application server can process
the messages from all the signaling networks instead of only one
signaling network.

SI Service It specifies the scope of the M3UA messages forwarded by the

identify SG7000. That is, under the condition that the SG7000 receives all
the signaling messages, it forwards the message whose SI field
matches with that defined here; otherwise, the message is
discarded.
The options for the M3UA are SCCP (SCCP message), TUP
(TUP message), ISUP (ISUP message), and BICC (BICC
message). It is set to ALL (ALL message) by default, indicating
that all the traffic of the SCCP, TUP, ISUP, and BICC can be
processed. If ALL (ALL message) is selected, it is not required to
specify any value for the Start CIC, End CIC or Sub-system
code, and all the messages may be processed within the valid CIC
range and valid SSN range.

SCIC Start CIC It is a decimal number corresponding to a 12-bit binary field.

If TUP (TUP message)/ISUP (ISUP message)/BICC (BICC
message) is selected for Service identify, it is required to judge

11-18 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Paramete Paramete Parameter Description

r ID r Name

ECIC End CIC Start CIC and End CIC according to the value of Service
identify.
For example, if the parameter Service identify is set to TUP (TUP
message), the mark part of the MSU contains such fields as DPC,
OPC, CIC, and so on. Of them, the CIC filed uniquely determines
to which voice channel this TUP message belongs.
If several application servers share one signaling point code,
routing cannot be implemented by the OPC and DPC. In this case,
you can define a range by specifying Start CIC and End CIC.
Under the condition that the SG7000 receives all the signaling
messages, it forwards the message whose CIC value is within the
range defined here; otherwise, the message is discarded.

SSN Sub- If SCCP (SCCP message) is selected for Service identify, it is

system required to configure Sub-system code.
code The Sub-system code identifies an SCCP user. It is a decimal
number corresponding to an 8-bit binary code. The system supports
the following SCCP user parts:
l SCMG: SCCP management
l SPARE: Reserved
l ISUP: ISDN user part
l OMAP: Operation, maintenance and administration part
l MAP: MAP application part
l HLR: Home location register
l VLR: Visitor location register
l MSC: Mobile switching center
l EIR: Equipment identity register
l AUC: Authentication center
l SPARE1: Reserved 1
l INAP: Intelligent network application part

Related Commands

Table 11-8 Related commands for configuring the M3UA complementary routing
Command Function

ADD M3CR To add the M3UA complementary routing

RMV M3CR To remove the M3UA complementary routing

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 11-19

Command Function

MOD M3CR To modify the M3UA complementary routing

LST M3CR To list the M3UA complementary routing

11.2.9 Adding M3UA Link Set Data

When a new record is added in the M3UA link set table, an idle index value is allocated for the
record.

Command
ADD M3ASSOS

Parameter
Par Par Parameter Description
ame ame
ter ter
ID Na
me

AS Adja It identifies the application server which has a direct signaling route to the
X cent SG7000. The index value here is allocated by the system after the command
appl ADD M3AS is executed.
icati
on
serv
er
inde
x

AST Adja It specifies the name of the adjacent application server to which this M3UA
cent link set is connected. It references the name of the record generated in the
appl command ADD M3AS.
icati It is optional. Its value is of the character type and can contain up to 40 English
on characters.
serv
er
title

11-20 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Par Par Parameter Description

ame ame
ter ter
ID Na
me

AS Ass It indicates how to distribute the traffic load over several M3UA links to the
C ociat same M3UA application server. The value of this filed is the load sharing mask.
ion The value field is the decimal value of a 4-bit binary number. For example, for
sele the link select mask code 1001, the corresponding decimal value is 9. It is set
ct to 0 by default.
mas The configuration principle of the parameter is as follows:
k
code l Set all the four bits to 0 if there is only one M3UA link.
l Set one bit to 1 if there are two M3UA links.
l Set two bits to 1 if there are three or four M3UA links.
l Set three bits to 1 if there are five or eight M3UA links.
l Set all the four bits to 1 if there are more than eight links.
l To avoid the system always choosing the same link, do not set the link set
select mask code and this parameter to the same value. It is recommended
to stagger the places of "1" of the two mask codes. For example, if the link
set select mask code is 0110, the link select mask code can be set to 1001.

TM Traf It identifies the traffic mode of the M3UA links in the M3UA link set. The two
fic ends of the interconnected link sets must be in the same transmission mode,
mod otherwise the M3UA link cannot work. It is recommended to use the load
e sharing mode. The two options of traffic mode are as follows:
l OVERRIDE (Over-ride mode): It is the N+1 backup mode. In this mode,
only one M3UA link in the link set is active, and the others are in the standby
state. When the active link fails, a standby link is activated and it begins to
transmit the traffic.
l LOADSHARE (Load-share mode): All links in the M3UA link set are
active. The traffic carried over this M3UA link set is shared by all the links
in the set.
By default, it is set to LOADSHARE.

WM Wor It identifies the working mode of the M3UA link set. The three options of the
k work mode are as follows:
mod l ASP (Act AS ASP): The local M3UA link set works in the application server
e mode.
l SGP (Act AS SGP): The local M3UA link set works in the signaling gateway
mode.
l IPSP (Act AS IPSP): The local M3UA link set works in the IP server mode.
The SGP mode is always selected for the SG7000.

SCR Mas It is the switch of the FireWall. The value OFF indicates to disable the FireWall,
N king ON to enable. This parameter is only used when the function of FireWall is
func enabled.
tion

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 11-21

Par Par Parameter Description

ame ame
ter ter
ID Na
me

REF Mas It is the masking reference from the FW initial shielding table. This parameter
king is used when the function of FireWall is enabled.
refer It is optional. Its value is of the numeral type. Its value range is 0-65535. It is
ence set to 65535 by default, indicating not use.

DFT Defa It is masking reference 0 from the FW initial shielding table. This parameter
REF ult is used when the function of FireWall is enabled.
mas It is optional. Its value is of the numeral type. Its value range is 0-65535. It is
king set to 65535 by default, indicating not use.
refer
ence

SR Serv It enables or disables the functions of number change and black & white list.
VP ice To enable this function, tick the box. It is set to Disable by default.
RO proc It is optional. Its value is of the enumeration type. It can be set to one or more
SW ess of the following values:
T swit
ch l BW (BW switch)
l NS (Number switch)
l ISUP (ISUP fraud prevention)
l ROSWT (Reroute switch)
l CFSSWT (CFS service switch)
l CNLSWT (CNL service switch)
l LNPSWT (LNP service switch)
l MCSWT (Message copy switch)
If the reroute and message copy functions are simultaneously enabled, the
system performs the message copy function first and then the reroute function.

11-22 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Par Par Parameter Description

ame ame
ter ter
ID Na
me

RR Rero It specifies the mode that the system adopts to process different messages in
T ute the redirect service.
poli It is valid only when ROSWT is set to Open.
cy
It is optional and its value is of the enumeration type. It can be set to:
l ANP (All DPC not processed): All MSU messages are processed based on
the original processing flow instead of the reroute processing flow despite
of the message type.
l SPP (DPC in self PC processed): When the MSU message is the locally
terminated message, the system obtains Type of next reroute table and Next
reroute reference, and then sends the message to the reroute part for
processing. When the MSU message is not the locally terminated message,
the system processes the message based on the original processing flow
instead of the reroute processing flow.
l NSPP (DPC not in self PC processed): When the MSU message is not the
locally terminated message, the system obtains Type of next reroute table
and Next reroute reference, and then sends the message to the reroute part
for processing. When the MSU message is the locally terminated message,
the system processes the message based on the original processing flow
instead of the reroute processing flow.
l AP (All DPC processed): The system obtains Type of next reroute table and
Next reroute reference, and then sends the MSU message to the reroute part
for processing despite of the message type.
It is set to ANP by default. It must be configured based on the actual conditions.

TT Typ It specifies the type of the table corresponding to the next operation of the
YPE e of reroute.
next It is valid when ROSWT is set to Open and the MSU message meets the
rero condition set in RRT.
ute
table It is optional and its value is of the enumeration type. It can be set to:
l VOID (Void)
l ROT (Reroute OPC table)
l RDT (Reroute DPC table)
l RCDT (Reroute called GT table)
l RCGT (Reroute calling GT table)
l ROCT (Reroute operation code table)
l RRLT (Reroute rule table)
It is set to VOID by default. It must be set based on the actual conditions.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 11-23

Par Par Parameter Description

ame ame
ter ter
ID Na
me

NR Next It specifies the reroute reference of the table type corresponding to the next
R rero operation of the reroute.
ute It is valid when ROSWT is set to Open and the MSU message meets the
refer condition set in RRT. It is used to match the corresponding data in the reroute
ence table configured in Type of next reroute table.
It is optional. Its value is of numeral type and ranges 0-65535. It is set to 65535
by default. It must be set based on the actual conditions.

CO Sign It indicates the signaling collection policy corresponding to this link set. The
LLI alin signaling collection policy is configured by ADD COLLECTRPL. Its value
DX g range is 0-255. It is set to 0 by default, indicating that the system uses the
colle default signaling collection policy.
ctio
n
poli
cy
inde
x

INS Inco It indicates the index of the initial shielding table used for shielding the
CR min messages received by the local link set. This index is used to search the initial
EE g shielding table for a certain shielding control table item. The value used here
N shiel is the returned value after the successful execution of the command ADD
ding N7IM.
table It is optional. Its value is of the numeral type. Its value range is 0-65535. It is
inde set to 65535 by default.
x
When it is set to 65535, it indicates that shielding control is disabled for the
messages received by the link set. When a message is received by the local
link set, and if the value of this parameter is valid, the corresponding shielding
control table item will be searched in the initial shielding table according to
the index, and the standard shielding control process will be enabled.
NOTE
The initial shielding table indexed 0 serves as the public shielding conditions for all
incoming links, and it cannot be bound with the link set. So, INCOMING SHIELDING
TABLE INDEX and OUTGOING SHIELDING TABLE INDEX can only reference
the non-zero index in the shielding control table.

11-24 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Par Par Parameter Description

ame ame
ter ter
ID Na
me

OU Out It indicates the index of initial shielding table used for shielding the messages
TSC goin sent by the local link set. This index is used to search the initial shielding table
REE g for a certain shielding control table item. The value used here is the returned
N shiel value after the successful execution of the command ADD N7IM.
ding It is optional. Its value is of the numeral type. Its value range is 0-65535. It is
table set to 65535 by default.
inde
x When the parameter value is set to 65535, it indicates that shielding control is
disabled for the messages sent by the link set. When a message is sent by the
local link set, and if the value of this parameter is valid, the corresponding
shielding control table item will be searched in the initial shielding table
according to the index, and the standard shielding control process will be
enabled.

TX Tim It indicates the index number of the timer used by the local link set. The value
er used here is the returned index after the successful execution of the command
inde ADD TIMER. The timer parameter value corresponding to this index is listed
x in the timer table. In practice, the index is set to 0 by default.

NU Nu It specifies the number discrimination type of the link set. After comparing
MD mbe with the number discrimination type that maps the called number, the system
ISM r performs the corresponding processing. The processing principles are as
OPT discr follows:
imin l If the type of number to be discriminated is calling number, and calling
atio number belongs to the number discrimination type of the link set, the system
n performs subsequent processing.
opti
on l If the type of number to be discriminated is called number, and called
number belongs to the number discrimination type of the link set, the system
performs subsequent processing.
l In other cases, the system transfers messages through the original route.
This parameter is optional. Its value is of the enumeration type. It can be set
to:
l BIT0 (Calling number)
l BIT1 (Called number)
Note that both values can be selected.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 11-25

Par Par Parameter Description

ame ame
ter ter
ID Na
me

CPP Mes It specifies the processing policy for copying messages. It is valid only when
OLI sage Service process switch is set to Message copy switch. If Message copy
CY copy switch is enabled, the system judges the message copy conditions. The system
poli copies the required messages based on configured rules and transmits them to
cy the specified signaling point over the original route.
It is optional. Its value is of the enumeration type. It can be set to:
l ANP (All DPC not processed)
l ISP (DPC in self PC processed)
l NISP (DPC not in self PC processed)
l AP (All DPC processed)
It is set to ANP (All DPC not processed) by default.

NC Typ It specifies the copy table whose configuration is used to process the message
PTY e of in a link set. If the messages are not to be queried and copied, set this parameter
PE next to Void. This parameter, together with Next message copy reference,
mes determines the table item set used in the next message query and copy. This
sage parameter can be set to:
copy l Void
table
l Message copy OPC table
l Message copy DPC table
l Message copy called GT table
l Message copy calling GT table
l Message copy operation code table
l Message copy rule table
It is set to Void by default.

NC Next It specifies the reference of the message copy in the next message copy table.
PRE mes This parameter, together with Type of next message copy table, determines
F sage the table item set used in the next message query and copy. If the messages are
copy not to be queried and copied, this parameter need not be configured.
refer
ence

11-26 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Related Commands

Table 11-9 Related commands for configuring the M3UA link set
Command Function

ADD To add the M3UA link set

M3ASSOS

RMV To remove the M3UA link set

M3ASSOS

MOD To modify the M3UA link set

M3ASSOS

LST To list the M3UA link set

M3ASSOS

11.2.10 Adding M3UA Route Data

When a new record is added for the M3UA route, an idle index value is allocated for the record.

Command
ADD M3RT

Parameter
Paramete Paramete Parameter Description
r ID r Name

ASX Applicatio It identifies the destination application server to which the M3UA
n server route is directed. The application server must be defined in the
index command ADD M3AS. The index value here is allocated by the
system after running the command ADD M3AS.

AST Applicatio It specifies the name of the application server to which this M3UA
n server route is directed.
title It is optional. Its value is of the character type and can contain up
to 40 English characters.

ASSX Associatio It indicates the first M3UA link set through which the M3UA route
n set index passes to the application server. The link set must be defined in the
command ADD M3ASSOS. The index value here is allocated by
the system after running the command ADD M3ASSOS.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 11-27

Paramete Paramete Parameter Description

r ID r Name

PR Priority It specifies the priority of the route. Its value ranges from 0 to 254.
The value 0 indicates the highest priority. If multiple M3UA routes
to the application server have different priorities, the routes with
higher priorities are preferred to carry the signaling traffic. The
M3UA routes with lower priorities cannot carry the signaling
traffic until all the routes with higher priorities become
unavailable. If all the routes have the same priority, it should be
set to 0; otherwise, it should be set from 0 by the descending order
of priorities.

Related Commands

Table 11-10 Related commands for configuring the M3UA route

Command Function

ADD M3RT To add the M3UA route

RMV M3RT To remove the M3UA route

MOD M3RT To modify the M3UA route

LST M3RT To list the M3UA route

11.2.11 Adding M3UA Association Data

When a new record is added in the M3UA association table, an idle index value is allocated for
the record.

Command
ADD M3ASSO

Parameter
Par Par Parameter Description
ame ame
ter ter
ID Na
me

SN Shel It is the number of the shelf, frame or board, which has the SBPU/SBPE board
f bearing the M3UA link.
num
ber

11-28 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Par Par Parameter Description

ame ame
ter ter
ID Na
me

FN Fra
me
num
ber

BN Boar
d
num
ber

PLN Boar It is the index number of the link on the board. One SBPU/SBPE board can
O d provide a maximum of 32 M3UA links. Its value range is 0-31. You can select
asso an unused link number here.
c.
num
ber

LIP Loc It identifies the local IP address combination index to which the SCTP
CX al IP association bearing this M3UA link is bound. The local IP combination must
com have been configured in the command ADD LIPC before. The index value
bina here is allocated by the system after the command ADD LIPC is executed.
tion
inde
x

LP Loc As one of the parameters interconnecting with softswitches, it is the local port
al number of the SCTP association over the M3UA association. Its value ranges
port 1024-65534. By default, it is set to 2905. The SG7000 works in Server mode
in the M3UA link, so the default value 2905 is usually selected.
NOTE
The M2UA, M3UA, IUA, and M2PA are based on the SCTP transmission. To ease the
management, the combination of the local IP address, local port number, remote IP
address, and remote port number must be unique. In addition, the combinations of the
local IP address, local port number, and remote port number on different links of the same
board must be unique.

RIP Rem It identifies the remote IP combination index to which the SCTP association
CX ote bearing this M3UA link is bound. If the softswitch supports the multi-home
IP feature of the SCTP association, the remote IP address combination can be
com configured to improve the reliability of the networking.
bina The remote IP combination must be configured before the command ADD
tion RIPC. The index value here is allocated by the system after running the
inde command ADD RIPC.
x

RP Rem It is the remote port number of the SCTP association over the M3UA
ote association. The parameter needs to be configured after negotiating with the
port softswtich equipment. Its value range is 1024-65534. It is set to 2905 by
default.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 11-29

Par Par Parameter Description

ame ame
ter ter
ID Na
me

CS C/S It identifies the mode in which the SCTP association bearing this M3UA link
mod works locally. There are two options as follows:
e l C (Client side): The local SCTP association is a client.
l S (Server side): The local SCTP association is a server.
This parameter is used when setting the SG7000 to act as a client or a server
according to the condition of interworking with the softswitch.
Note that the softswitch must be configured to a client if you choose S (Server
side) for the SG7000 when interworking between them. Negotiation is required
to configure this parameter. Typically the SG7000 is configured to a server,
and the softswitch is configured to a client.

ASS Ass It is the index of the M3UA link set to which this M3UA link belongs. The
I ociat index value here is allocated by the system after running the command ADD
ion M3ASSOS.
set
inde
x

ASS Ass It specifies the name of the M3UA link set to which this M3UA link belongs.
T ociat It is optional. Its value is of the character type and can contain up to 40 English
ion characters.
set
title

ASF Acti It is used to configure whether this added link works in an active or standby
ve_s state. Note that this field is enabled if OVERRIDE (Over-ride mode) is
tand selected for Traffic mode parameter of the ADD M3ASSOS command;
by otherwise, this field is disabled.
flag

PRI Prio It specifies the priority of the M3UA links to be used within the same M3UA
rity link set. The links with higher priorities are selected first. The links with lower
priorities cannot carry the signaling traffic until all the links with higher
priorities become unavailable. The value 0 stands for the highest priority and
the value 1 stands for the second highest priority.
Note that this field will be enabled if LOADSHARE (Load-share mode) is
selected for Traffic mode parameter of the ADD M3ASSOS command;
otherwise, this field is disabled.

MA MA It is the maximum number of incoming streams the SCTP association bearing

XIS X. in this M3UA link can accommodate. Its value ranges 1-17. It specifies the
strea maximum number of SCTP streams contained in each M3UA protocol
ms message received by the SG7000. The default value 17 is selected. After the
SCTP association is created, the actual number of incoming streams is
negotiated by the both offices.

11-30 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Par Par Parameter Description

ame ame
ter ter
ID Na
me

MA MA It is the maximum number of outgoing streams which the SCTP association

XO X. bearing this M3UA link can accommodate. Its value range is 1-17. It specifies
S out the maximum number of SCTP streams contained in each M3UA protocol
strea message sent by the SG7000. The default value 17 is selected. After the SCTP
ms association is created, the actual number of outgoing streams is negotiated by
the both offices.

SCT SCT It specifies the SCTP parameter referenced by this M3UA link. It references
PID P the index generated when a record is added through ADD SCTPPP. It is
X inde mandatory. Its value is of numeral type and ranges 0-127.
x

Related Commands

Table 11-11 Related commands for configuring the M3UA link set
Command Function

ADD To add the M3UA link set

M3ASSO

RMV To remove the M3UA link set

M3ASSO

MOD To modify the M3UA link set

M3ASSO

LST To list the M3UA link set

M3ASSO

11.3 Configuration Examples

This section provides examples to describe how to configure the M3UA data.

Assumption
The M3UA data configuration networking is shown in Figure 11-5. This section describes the
data configuration when the SG7000 works in the transfer mode and agent mode respectively.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 11-31

Figure 11-5 Networking of the M3UA data configuration

11.3.1 Transfer Mode (Example 1)

This section provides examples to describe how to configure the M3UA data in transfer mode.
11.3.2 Agent Mode (Example 2)
This section provides examples to describe how to configure the M3UA data in agent mode.

11.3.1 Transfer Mode (Example 1)

This section provides examples to describe how to configure the M3UA data in transfer mode.

Data Collection
In example 1 in Figure 11-5, the SG7000 works in the transfer mode and has independent
signaling code.
There are two M3UA links between the SoftX3000A and the SG7000. Each M3UA link bears
SS7 services in load sharing mode. The slots 5 and 10 of the SG7000 are configured with two
SBPIs to provide the local IP address. Refer to Table 11-12 for the data collection.

11-32 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Table 11-12 Data collection table of example 1

SG work Local office Remote IP Remote SCTP

mode DPC SPC address port number

Transfer B1111B A1111A 11.11.11.1/255 M3UA link 0: 2905

mode (National (National .255.0.0 M3UA link 1: 2911
network) network)

Local IP Local SCTP C_S mode Routing Work mode of link

address port number context

10.10.10.1/2 2905 SERVER 1166 Load sharing

55.255.0.0

Procedure
Step 1 To set the local office information, set National network code to A1111A, SCCP function to
False, Logic network index to 0, and run the following command:
SET OFI: SN1=NM, SN2=NS, SN3=IM, SN4=IS, NPC="A1111A", SCCP=FALSE;

Step 2 Add the local IP address. The index 2 is obtained.

ADD LIP: LIP="10.10.10.1", MSK="255.255.0.0", DGW="10.10.1.1";

Step 3 To add the SBPI in slots 5 and 10, set Board property indicator to 2. That is, the IP address
allocated to the SBPI is 211.169.150.70, and the subnet mask is 255.255.0.0. Run the following
command:
ADD BRD: FN=0, SHN=0, FT=MAIN, SN=5, LOC=FPB, BT=SBPI, PI=2;
ADD BRD: FN=0, SHN=0, FT=MAIN, SN=10, LOC=FPB, BT=SBPI, PI=2;

Step 4 To add the local IP combination, set FE index 1 to the IP address of the SBPI of the local frame.
The index number of the address is 2. The local IP combination index 0 is obtained after running
the command.
ADD LIPC: FEX1=2;

Step 5 Add the remote IP address and obtain the index 0 of the remote IP address.
ADD RIP: RIP="11.11.11.1";

Step 6 To add the remote IP combination, set Remote IP address index 1 to 0. The index 0 of the
remote IP combination is obtained after running the command.
ADD RIPC: RIPX1=0;

Step 7 Add the IP address of the SoftX3000A into the IPDACL table.
ADD IPDACL: IP="11.11.11.1";

Step 8 Set DSP title to HW-A, National network code to B1111B, STP to False, Route selection
field to 0, and SCCP function to False. For the other parameters, keep the default values. The
DSP index 1 is obtained after running the command.
ADD N7DSP: DESC="HW-A", NPC="B1111B", STP=FALSE, SLS=0, SCCPUSED=NONE;

Step 9 To add the M3UA application server, set Destination point code index to 1, Network
indication to National network, Association set select mask code to 0 because there is only
one link set. The index 0 of the application server is obtained after running the command.
ADD M3AS: NI=NM, SWM=TM, DPCX=1, RC=1166;

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 11-33

Step 10 To add the M3UA link set, set Association select mask code to 1 because there are two M3UA
links. The link set index 0 is obtained after running the command.
ADD M3ASSOS: ASX=1, ASC=1, WM=SGP;

Step 11 Add the M3UA route.

ADD M3RT: ASX=0, ASSX=0;

Step 12 To add the first M3UA link, set Board assoc. number to 0, Remote port to 2905, Priority to
0, SCTP index to 0, and Active_standby flag to any value because Traffic mode is set to
LOADSHARE in the command ADD M3ASSOS. Keep the default values for other parameters.
ADD M3ASSO: FN=0, SN=0, BN=0, PLNO=0, LIPCX=0, RIPCX=0, CS=S, ASSI=0,
ASF=YES, SCTPIDX=0;

Step 13 To add the second M3UA link, set Board assoc. number to 1, Remote port to 2911,
Priority to 1, SCTP index to 1, and Active_standby flag to any value because Traffic mode
is set to LOADSHARE in the command ADD M3ASSOS, and keep the default values for other
parameters, run the following command:
ADD M3ASSO: FN=0, SN=0, BN=0, PLNO=1, LIPCX=0, RIPCX=0, RP=2911, CS=S,
ASSI=0, ASF=YES, PRI=1, SCTPIDX=1;

----End

11.3.2 Agent Mode (Example 2)

This section provides examples to describe how to configure the M3UA data in agent mode.

Data Collection
In example 2 in Figure 11-5, the SG7000 connects to the SoftX3000C through the M3UA
protocol. The SG7000 works in the agent mode and shares a signaling point code with the
SoftX3000. The LS is the DSP of the SG7000 and SoftX3000C.

There are two M3UA links between the SoftX3000C and the SG7000. Each M3UA link bears
SS7 signaling services in load sharing mode. Slots 5 and 10 of the SG7000 are configured with
two SBPIs to provide the local IP address. Refer to Table 11-13 for the data collection.

Table 11-13 Data collection table of example 2

Local office
SG work signaling Remote IP Remote SCTP port
mode DSP code point code address number

Agent mode D1111D C1111C 22.22.22.1/255 M3UA link 0: 2905

(National (National .255.0.0 M3UA link 1: 2911
network) network)

Local IP Local SCTP C_S mode Routing Work mode of link

address port number context

10.10.10.1/2 2905 SERVER 2266 Load share

55.255.0.0

11-34 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

NOTE

In agent mode, the processing of GT translation varies depending on the setting of Parameter 1 in the
SET SOFTCFG command:
l When Parameter 1 is set to 0, the STP agent function is disabled and the GT translation is performed
on the SoftX3000.
l When Parameter 1 is set to 8, the STP agent function is enabled and the GT translation is performed
on the SG7000.

Procedure
Step 1 To add the local office OPC information, set National network code to C1111C and Logic
network index to 0. The signaling point index 1 is obtained after running the command.
ADD OPC: NPC="C1111C";
NOTE

l In example 1, use the command SET OFI to add the local office information of the SG7000 and the
SoftX3000 whose signaling point code is B1111B. Therefore, use the command ADD OPC to add the
other local office signaling point code of the SG7000.
l The local IP and local IP combination is configured in example 1. Thus, it is not required to configure
them again.

Step 2 Add the IP address of the SoftX3000C into the IPDACL table.
ADD IPDACL: IP="22.22.22.1";

Step 3 Add the remote IP address to obtain the index 1 of the remote IP address.
ADD RIP: RIP="22.22.22.1";

Step 4 To add the remote IP combination, set Remote IP address index 1 to 1. The index 1 of the
remote IP combination is obtained after running the command.
ADD RIPC: RIPX1=1;

Step 5 To add the M3UA application server, set Network indication to National network,
Destination point code index to the local office signaling point index 1 of the SG7000, and
Association set select mask code to 0 because there is only one link set. The index 1 of the
application server is obtained after running the command.
ADD M3AS: NI=NM, SWM=AM, DPCX=1, RC=2266;

Step 6 To add the complementary routing, set Application server index and Original point code
index to 1 because the original signaling point generating the M3UA messages is the application
server. Set the default values for other parameters.
ADD M3CR: ASX=1, OFX=1;

Step 7 To add the M3UA link set, set Association select mask code to 2 because there are two M3UA
links. The link set index 1 is obtained after running the command.
ADD M3ASSOS: ASX=0, ASC=2, WM=SGP;

Step 8 Add the M3UA route.

ADD M3RT: ASX=1, ASSX=1;

Step 9 To add the first M3UA link, set Board assoc. number to 2, Remote port to 2905, Priority to
0, SCTP index to 0, and Active_standby flag to any value because the Traffic mode is set to
LOADSHARE in the command ADD M3ASSOS, and keep the default values for other
parameters, run the following command:
ADD M3ASSO: FN=0, SN=0, BN=0, PLNO=2, LIPCX=0, RIPCX=1, CS=S, ASSI=1,
ASF=YES, SCTPIDX=0;

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 11-35

Step 10 To add the second M3UA link, set Board assoc. number to 3, Remote port to 2911,
Priority to 1, SCTP index to 1, and Active_standby flag to any value because the Traffic
mode is set to LOADSHARE in the command ADD M3ASSOS, and keep the default values
for other parameters, run the following command:
ADD M3ASSO: FN=0, SN=0, BN=0, PLNO=3, LIPCX=0, RIPCX=1, RP=2911, CS=S,
ASSI=1, ASF=YES, PRI=1, SCTPIDX=1;

----End

11-36 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

12 Configuring M3UA Shielding Data

About This Chapter

This chapter describes how to configure the M3UA shielding data. Before configuring the
M3UA shielding data, you must ensure that the hardware data, local office data, MTP data, and
M3UA data are already configured. This chapter is optional. When the M3UA shielding data is
not required, you can skip this chapter.
The M3UA and MTP shielding data references the same data table. The difference is that the
M3UA shielding data cannot reference the forbidden TFM shielding condition; however, the
message type and route context are added as the shielding conditions to the M3UA shielding
data. The reference relations are describes as follows:
l If two M3UA-specific shielding conditions are not used by the shielding chain when you
configure the shielding data, the configured shielding chain data can be referenced by both
the MTP and M3UA shielding. You only need to reference the corresponding index of the
initial shielding table when you configure Incoming shielding table index and Outgoing
shielding table index of a link set.
l If two M3UA-specific shielding conditions are used by the shielding chain when you
configure the shielding data, the configured shielding chain data can be referenced only by
the M3UA link set.
l If the forbidden TFM shielding conditions are used by the shielding chain when you
configure the shielding data, the configured shielding chain data can be referenced only by
the MTP link.
To configure the SG7000 data, follow the procedure as shown in Figure 12-1. In this way, the
key fields are defined before they are referenced by other data tables and no junk data is
generated.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 12-1

Figure 12-1 Data configuration procedure

12.1 Configuration Preparations

This section describes the related background information, terms, and general steps for
configuring the M3UA shielding data.
12.2 Configuring the M3UA Shielding Data
Configuring the M3UA shielding data includes adding the initial shielding table, adding the link
set shielding table, and configuring the prohibited OPC table.
12.3 Configuration Examples
This section provides examples to describe how to configure the M3UA shielding data.

12-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

12.1 Configuration Preparations

This section describes the related background information, terms, and general steps for
configuring the M3UA shielding data.
12.1.1 Terms
This section describes the terms used when you configure the M3UA shielding data.
12.1.2 Networking Structure of the M3UA Shielding
This section describes the networking structure for configuring the M3UA shielding data.
12.1.3 Mapping Between Data Tables
This section describes the mapping between data tables related to the M3UA shielding data
configuration.
12.1.4 Data Collection
Set shielding conditions before configuring the M3UA shielding data. Select the shielding table
relating to the shielding condition first, and then confirm the shielding reference of this shielding
chain.
12.1.5 General Steps
You must follow certain procedures to configure the M3UA shielding data.

12.1.1 Terms
This section describes the terms used when you configure the M3UA shielding data.
With the M3UA shielding function, the system can filter the specific messages based on message
types. The filtered messages are transferrable; however, they should be discarded. When the
message content or the related information of a message contains a certain specified feature, the
message is called a specific message. The message content or the related information is classified
into the following types:
l The link set that receives the message
l The link set that sends the message
l The OPC in the message
l The DPC in the message
l The SIO in the message
l The route context in the message
l The related signaling point information in the message
l The message type in the message

One or more of the preceding items can be combined to form a shielding condition to filter the
specific messages. For example, you can filter an M3UA message by combining the following
filter conditions:
l The message is sent from signaling point AAAAAA.
l The message class is 0.
l The message type is 0.

The difference between the M3UA message shielding and the MTP message shielding is that,
M3UA messages can be shielded based on the message type and the route context.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 12-3

The system shields the specific M3UA messages in searching and matching mode. That is, the
system compares the contents of the specific M3UA message with a series of sequential shielding
conditions (shielding chain) to check whether the shielding conditions are met. If yes, the system
performs the operation specified by the table item. If not, the system performs the default
operation.

Incoming Shielding Table Index

It indicates the index of the initial shielding table used for shielding the messages received by
the local link set. This index is used to search the initial shielding table for a certain shielding
control table item. When a message comes into the link set and this index is valid, this index
will be used to search the initial shielding table for a certain shielding control table item and the
standard shielding control process will be enabled.

Outgoing Shielding Table Index

It indicates the index of initial shielding table used for shielding the messages sent by the local
link set. This index is used to search the initial shielding table for a certain shielding control
table item. When a message is sent from the link set and this index is valid, this index will be
used to search the initial shielding table for a certain shielding control table item and the standard
shielding control process will be enabled.

12.1.2 Networking Structure of the M3UA Shielding

This section describes the networking structure for configuring the M3UA shielding data.
As shown in Figure 12-2, the SG7000 is connected with the softswitch device (for example,
Huawei SoftX3000) through the M3UA protocol. In the networking structure using the M3UA
protocol, the SG7000 can occupy an independent SPC or share an SPC with the softswitch
device. The softswitch device is not required to support the MTP3 and its lower-layer
narrowband protocols. Instead, it interconnects with the signaling network through the
SG7000. The M3UA shielding function is used to shield the M3UA messages that meet the
configured shielding conditions in this networking structure.

Figure 12-2 Networking structure of the M3UA shielding

This network structure demonstrates only the interconnection between the SG7000 and the
softswitch device. Any device that interconnects with the SG7000 through the M3UA protocol
can implement the M3UA shielding function. The SG7000 can shield the M3UA messages
between other networks and the softswitch device based on the configured shielding conditions.

12-4 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

After the M3UA shielding data that is configured on the SG7000 is referenced by a configured
M3UA link, the M3UA link can shield the M3UA messages based on the referenced shielding
chain. For example, after the shielding chain "shielding OPC is AAAAAA" configured on the
SG7000 is referenced by Outgoing shielding table index of the M3UA link set between the
SG7000 and the softswitch device, all messages sent from the signaling point AAAAAA to the
softswitch device through the SG7000 are discarded. In this example, the type of signaling point
AAAAAA is irrelevant to this service.

12.1.3 Mapping Between Data Tables

This section describes the mapping between data tables related to the M3UA shielding data
configuration.

Reference Relations Between M3UA Shielding Data and Other Data

The reference relation exists between the M3UA shielding data table and the M3UA link set
table. That is, The index in the M3UA initial shielding table is referenced by Incoming shielding
table index and Outgoing shielding table index in the M3UA link set table. The reference
relation is as shown in Figure 12-3.

Figure 12-3 Reference relation between M3UA shielding conditions and link set

Reference relations internal the M3UA shielding data table

Figure 12-4 shows the reference relations internal the M3UA shielding data table. To avoid line
intersections, the figure is divided into part a and part b, and only reference relations between
the prohibited M3UA message type table, prohibited RC table, prohibited TFM table, and other
data tables are described. Figure 5-3 shows the reference relations between other data tables.

l As shown by part a in Figure 12-4, the parameter Shielding reference in the prohibited
M3UA message type table and the prohibited RC table can be referenced only by the
shielding tables above them except the prohibited TFM table.
l As shown by part b in Figure 12-4, the parameter Shielding reference in the prohibited
TFM table can be referenced only by the shielding tables above the table. The prohibited
TFM table can only be an end shielding condition in the MTP shielding.
l The reference relations in other tables are similar as those in the prohibited RC table,
prohibited M3UA message type table, and prohibited TFM table. That is, the parameter
Shielding reference in a table can be referenced only by the shielding tables above.

Ten shielding tables in the figure can form different shielding chains from top to bottom. For
example:

l Initial shielding table (N7IM) -> Link set shielding table (N7LSM) -> Prohibited OPC table
(N7DO) -> prohibited SIO table (N7DSIO)

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 12-5

l Initial shielding table (N7IM) -> link set shielding table (N7LSM) -> prohibited OPC table
(N7DO) -> prohibited DPC table (N7DD) -> prohibited TFM table (N7DTFM)
l Initial shielding table (N7IM) -> link set shielding table (N7LSM) -> prohibited OPC table
(N7DO) -> prohibited DPC table (N7DD) -> allowed OPC table (N7EO) -> allowed DPC
table (N7ED) -> prohibited SIO table (N7DSIO) -> prohibited M3UA message type table
-> prohibited RC table (M3RC)
NOTE

The prohibited TFM table and prohibited RC table can only be the end of the shielding chain, that is, they
cannot reference other shielding tables. The prohibited TFM table can only be referenced in the MTP
shielding, and the prohibited RC table and prohibited M3UA message type table can only be referenced in
the M3UA shielding.

It is recommended to add a shielding chain from bottom to top, that is, add the shielding table
(as shown in Figure 12-4) at the bottom first, and then add the shielding table above it. When
deleting a shielding chain, delete the shielding table at the top of the shielding chain, and then
delete the shielding table below it, because the referenced shielding table cannot be deleted.

12-6 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Figure 12-4 Reference relations internal the M3UA shielding data table
ADD N7IM ADD N7IM

[Next shielding reference] [Next shielding reference]

ADD N7LSM ADD N7LSM

[ Shielding reference ] [ Shielding reference ]

[Next shielding reference] [Next shielding reference]

ADD N7DO ADD N7DO

[ Shielding reference ] [ Shielding reference ]

[Next shielding reference] [Next shielding reference]
ADD N7DD ADD N7DD
[ Shielding reference ] [ Shielding reference ]
[Next shielding reference] [Next shielding reference]
ADD N7EO ADD N7EO

[ Shielding reference ] [ Shielding reference ]

[Next shielding reference] [Next shielding reference]
ADD N7ED ADD N7ED
[ Shielding reference ] [ Shielding reference ]
[Next shielding reference] [Next shielding reference]

ADD N7DSIO ADD N7DSIO

[ Shielding reference ] [ Shielding reference ]
[Next shielding reference] [Next shielding reference]

ADD N7ESIO ADD N7ESIO

[ Shielding reference ] [ Shielding reference ]
[Next shielding reference] [Next shielding reference]

ADD N7DTFM ADD N7DTFM

[ Shielding reference ] [ Shielding reference ]
[Next shielding reference] [Next shielding reference]
ADD M3MT b

[ Shielding reference ]
[Next shielding reference]
ADD M3RC

[ Shielding reference ]

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 12-7

12.1.4 Data Collection

Set shielding conditions before configuring the M3UA shielding data. Select the shielding table
relating to the shielding condition first, and then confirm the shielding reference of this shielding
chain.

Table 12-1 illustrates the data to be collected.

Table 12-1 Data collection table

Shielding Condition Shielding reference

12.1.5 General Steps

You must follow certain procedures to configure the M3UA shielding data.

You must configure the M3UA shielding data from step 1 to step 9 in order, as shown in Table
12-2. The last step is mandatory. The last step in each table is mandatory. Each table except for
the last refers to a shielding condition and thus they are optional. During configuration, configure
one or more required shielding tables according to the sequences as listed in Table 12-2.

Table 12-2 General steps for configuring the M3UA shielding data

Step Operation

1 Add the route context shielding table (ADD M3RC)

2 Add the M3UA message type shielding table (ADD M3MT)

3 Add the allowed SIO (ADD N7ESIO)

4 Add the prohibited SIO (ADD N7DSIO)

5 Add the allowed DPC (ADD N7ED)

6 Add the allowed OPC (ADD N7EO)

7 Add the prohibited DPC (ADD N7DD)

8 Add the prohibited OPC (ADD N7DO)

9 Add the link set shielding (ADD N7LSM)

10 Add the initial shielding (ADD N7IM) (Mandatory)

NOTE

After configuring the M3UA shielding data, you complete the setting of shielding conditions only. You
must reference the index in the initial shielding table of the command ADD N7IM to Outgoing shielding
table index or Incoming shielding table index of the command ADD M3ASSOS to implement the M3UA
shielding function. For details of the configuration method, see 12.3 Configuration Examples.

12-8 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

12.2 Configuring the M3UA Shielding Data

Configuring the M3UA shielding data includes adding the initial shielding table, adding the link
set shielding table, and configuring the prohibited OPC table.
12.2.1 Adding the Prohibited RC Table
This section describes the command, parameters, and related commands for adding the
prohibited route context (RC) table. This table can only be the last table in a shielding chain.
12.2.2 Adding the M3UA Message Type Shielding Table
This section describes the command, parameters, and related commands for adding the M3UA
message type shielding table.
12.2.3 Adding Allowed SIO Table
This section describes the command, parameter, and related commands for adding the allowed
SIO table.
12.2.4 Adding Prohibited SIO Table
This section describes how to configure screening conditions for a field which indicates the
message type, such as the SIO of a message.
12.2.5 Adding Allowed DPC Table
This section describes the allowed DPC sets.
12.2.6 Adding Allowed OPC Table
It is used to configure the set of OPCs allowed to pass. When the number of OPCs to be prohibited
is more, you can use this table to designate the set of OPCs allowed to simplify the data setting
process.
12.2.7 Adding Prohibited DPC Table
This section describes the command, parameter, and related commands for adding the prohibited
DPC table.
12.2.8 Adding Prohibited OPC Table
This section describes the command, parameter, and related commands for adding the prohibited
OPC table.
12.2.9 Adding Link Set Shielding Table
This section describes the command, parameter, and related commands for adding the link set
shielding table.
12.2.10 Adding the Initial Shielding Table
This section describes the command, parameters, and related commands for adding the initial
shielding table.

12.2.1 Adding the Prohibited RC Table

This section describes the command, parameters, and related commands for adding the
prohibited route context (RC) table. This table can only be the last table in a shielding chain.

Command
ADD M3RC

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 12-9

Parameter
Parame Paramete Parameter Description
ter ID r Name

MR Shielding It is used to distinguish the records that have different screening

reference conditions in the same screening table. For example, you can set the
Shielding reference of the record with index 0 in the route context
shielding table to 0 and that of the record with index 1 to 1.
It is mandatory. Its value is of the numeral type and ranges 0-65535.

FROM Min. RC They specify the number segment of the RC to be shielded.

RC They are mandatory. They must be set based on the actual conditions.
TORC Max. RC The rules for configuring the parameters are as follows:
l The value of Min. RC cannot be greater than that of Max. RC.

l Different records can be repeated, intersected, or overlapped.

Related Commands

Table 12-3 Related commands for configuring the prohibited RC table

Command Function

ADD M3RC To add the prohibited RC table

MOD M3RC To modify the prohibited RC table

RMV M3RC To remove the prohibited RC table

LST M3RC To query the prohibited RC table

12.2.2 Adding the M3UA Message Type Shielding Table

This section describes the command, parameters, and related commands for adding the M3UA
message type shielding table.

Command
ADD M3MT

12-10 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Parameter
Parame Paramete Parameter Description
ter ID r Name

MR Shielding It is used to distinguish the records that have different screening

FROM Min.Msg They specify the class scope of the messages to be shielded. The
MSGC class message class is defined in the header of a public message in the
LS M3UA protocol with the length of one byte. The common messages
are classified into the management message 0x00, transmission
TOMS Max.Msg message 0x01, and SS7 signaling network management message
GCLS class 0x02. For detailed message classes, refer to the M3UA protocol. The
value of Min.Msg class cannot be greater than that of Max.Msg
class. Different records can be repeated, intersected, or overlapped.
It is mandatory. Its value range is 0-255.

FROM Min.Msg They specify the type scope of the messages to be shielded. The
MSGT type message type is defined in the header of a public message in the
YPE M3UA protocol with the length of one byte. For detailed message
types, refer to the M3UA protocol. The value of Min.Msg type
TOMS Max.Msg cannot be greater than that of Max.Msg type. Different records can
GTYPE type be repeated, intersected, or overlapped.
It is mandatory. Its value range is 0-255.

TTYPE Type of This parameter, together with Next shielding reference, determines
next the subsequent shielding rules.
shielding They specify the table from which the data is referenced for the next
table shielding condition. It is set to End if the screening data is not
required. It can be set to:
l M3RC (Route context shielding table)

NMR Next It specifies the screening reference index in the next shielding
shielding reference table, which is to be used in the next step. This parameter,
reference together with Type of next shielding table, determines the table item
set used for the next screening search. You do not need to configure
this parameter if the screening data is not required.

Related Commands

Table 12-4 Related commands for configuring the M3UA message type table

Command Function

ADD M3MT To add the M3UA message type shielding table

MOD M3MT To modify the M3UA message type shielding table

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 12-11

Command Function

RMV M3MT To remove the M3UA message type shielding table

LST M3MT To query the M3UA message type shielding table

12.2.3 Adding Allowed SIO Table

This section describes the command, parameter, and related commands for adding the allowed
SIO table.

Command
ADD N7ESIO

Parameter
Parame Paramete Parameter Description
ter ID r Name

MR Shielding It is the flag for distinguishing the records under different shielding
reference conditions of the same table.
It is mandatory. Its value is of the numeral type and ranges 0-65535.

l Value 1 stands for the signaling network test and maintenance

FNI MIN.NI They specify the minimum and maximum values of the signaling
network in which the object specified by this shielding table item is
located.
They are mandatory. The value ranges from 0 to 3.
l Value 0 stands for the international network.

l Value 1 stands for the international reserved network.

l Value 2 stands for the national network.
l Value 3 stands for the national reserved network.

12-12 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Parame Paramete Parameter Description

ter ID r Name

TNI MAX.NI The value of MIN.NI cannot be greater than that of MAX.NI.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 12-13

Related Commands

Table 12-5 Related commands for configuring the allowed SIO table
Comman Function
d

ADD To add the allowed SIO

N7ESIO

MOD To modify the allowed SIO

N7ESIO

RMV To remove the allowed SIO

N7ESIO

LST To query the allowed SIO

N7DESIO

12.2.4 Adding Prohibited SIO Table

This section describes how to configure screening conditions for a field which indicates the
message type, such as the SIO of a message.

Command
ADD N7DSIO

Parameter
Pa Pa Parameter Description
ra ra
m m
et et
er er
ID N
a
m
e

12-14 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Pa Pa Parameter Description
ra ra
m m
et et
er er
ID N
a
m
e

TS M It indicates the value of the maximum service type specified by this table item.
I A The value range is the same as MIN.SI.
X.
SI

T M It indicates the maximum value of the signaling network in which the object
NI A specified by this shielding table item is located. The value range is the same as
X. MIN.NI.
NI

F MI It indicates the minimum value of H0 of the message specified by this table item.
H0 N. The H0 is a field in the TUP message, used for indicating the category of message.
H0

T M It indicates the maximum value of H0 of the message specified by this table item.
H0 A
X.
H0

F MI It indicates the minimum value of H1 of the message specified by this table item.
H1 N. The H1 is a field in the TUP message, used for indicating the type of message.
H1

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 12-15

Pa Pa Parameter Description
ra ra
m m
et et
er er
ID N
a
m
e

T M It indicates the maximum value of H1 of the message specified by this table item.
H1 A
X.
H1

Related Commands

Table 12-6 Related commands for configuring the prohibited SIO table

Command Function

ADD N7DSIO To add the prohibited SIO

MOD N7DSIO To modify the prohibited SIO

RMV N7DSIO To remove the prohibited SIO

12-16 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Command Function

LST N7DSIO To query the prohibited SIO

12.2.5 Adding Allowed DPC Table

This section describes the allowed DPC sets.

Command
ADD N7ED

Parameter
Pa Pa Parameter Description
ra ra
m m
et et
er er
I N
D a
m
e

NI N It indicates the signaling network in which the object specified by the shielding
et table item is located.
w
or
k
in
di
ca
tio
n

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 12-17

Pa Pa Parameter Description
ra ra
m m
et et
er er
I N
D a
m
e

T M It indicates the maximum number of the signaling point specified by this table
O A item. Together with the MIN. DPC number, it specifies the DPC numbers allowed
X. in this table.
D
P
C
nu
m
be
r

12-18 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Pa Pa Parameter Description
ra ra
m m
et et
er er
I N
D a
m
e

Related Commands

Table 12-7 Related commands for configuring the allowed DPC table
Command Function

ADD N7ED To add the allowed DPC

MOD N7ED To modify the allowed DPC

RMV N7ED To remove the allowed DPC

LST N7ED To query the allowed DPC

12.2.6 Adding Allowed OPC Table

Command
ADD N7EO

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 12-19

Parameter
Paramete Paramete Parameter Description
r ID r Name

NI Network It indicates the signaling network in which the object specified by

indication the shielding table item is located.

FO MIN. It indicates the minimum number of signaling point specified by

OPC this table item. The OPC numbers which are greater than or equal
number to this value, but lesser than or equal to the MAX. OPC
number, are the OPC numbers allowed in this table.

TO MAX. It indicates the maximum number of the signaling point specified

OPC by this table item. Together with MIN. OPC number, it specifies
number the OPC numbers allowed in this table.

TTYPE Type of It, together with Next shielding reference, determines the
next subsequent shielding principle.
shielding It indicates the data of the table to be used for shielding in the next
table step. If it is not required to search the shielding data, it must be set
to END. Together with the Next shielding reference, it decides
the table item set to be used in the next shielding. The type of next
shielding table of the allowed OPC table includes the following:
l END (End)
l EDT (Allowed DPC table)
l DST (Prohibited SIO table)
l EST (Allowed SIO table)
l DTT (Prohibited TFM table)
l M3MT (M3UA message type shielding table)
l M3RC (Route context shielding table)

12-20 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Related Commands

Table 12-8 Related commands for configuring the allowed OPC table
Command Function

ADD N7EO To add the allowed OPC

MOD N7EO To modify the allowed OPC

RMV N7EO To remove the allowed OPC

LST N7EO To query the allowed OPC

12.2.7 Adding Prohibited DPC Table

This section describes the command, parameter, and related commands for adding the prohibited
DPC table.

Command
ADD N7DD

Parameter
Paramete Paramete Parameter Description
r ID r Name

NI Network It indicates the signaling network in which the object specified by

indication the shielding table item is located.

FO MIN. It indicates the minimum number of the signaling point specified

OPC by this table item. The DPC numbers which are greater than or
number equal to this value, but lesser than or equal to the MAX. DPC
number, are the DPC numbers prohibited in this table.

TO MAX. It indicates the maximum number of the signaling point specified

OPC by this table item. Together with MIN. DPC number, it specifies
number the DPC numbers prohibited in this table.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 12-21

Paramete Paramete Parameter Description

r ID r Name

TTYPE Type of It, together with Next shielding reference, determines the
next subsequent shielding principle.
shielding It indicates the data of the table to be used for shielding in the next
table step. If it is not required to search the shielding data, it must be set
to END. Together with Next shielding reference, it decides the
table item set to be used in the next shielding. The type of next
shielding table of the prohibited DPC table includes the following:
l END (End)
l EOT (Allowed OPC table)
l EDT (Allowed DPC table)
l DST (Prohibited SIO table)
l EST (Allowed SIO table)
l DTT (Prohibited TFM table)
l M3MT (M3UA message type shielding table)
l M3RC (Route context shielding table)

Related Commands

Table 12-9 Related commands for configuring the prohibited DPC table
Command Function

ADD N7DD To add the prohibited DPC

MOD N7DD To modify the prohibited DPC

RMV N7DD To remove the prohibited DPC

LST N7DD To query the prohibited DPC

12.2.8 Adding Prohibited OPC Table

This section describes the command, parameter, and related commands for adding the prohibited
OPC table.

Command
ADD N7DO

12-22 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Parameter
Paramete Paramete Parameter Description
r ID r Name

NI Network It indicates the signaling network in which the object specified by

indication the shielding table item is located.

FO MIN. It indicates the minimum number of the signaling point specified

OPC by this table item. The numbers are greater than or equal to MIN.
number OPC number, but lesser than or equal to the MAX. OPC
number.

TO MAX. It indicates the maximum number of the signaling point specified

OPC by this table item. Together with MIN. OPC number, it specifies
number the OPC numbers prohibited in this table.

TTYPE Type of It, together with Next shielding reference, determines the
next subsequent shielding principle.
shielding It indicates the data of the table to be used for shielding in the next
table step. If it is not required to search the shielding data, it must be set
to END. Together with the Next shielding reference, it decides
the table item set to be used in the next shielding. The type of next
shielding table of the prohibited OPC table includes the following:
l END (End)
l DDT (Prohibited DPC table)
l EOT (Allowed OPC table)
l EDT (Allowed DPC table)
l DST (Prohibited SIO table)
l EST (Allowed SIO table)
l DTT (Prohibited TFM table)
l M3MT (M3UA message type shielding table)
l M3RC (Route context shielding table)

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 12-23

Related Commands

Table 12-10 Related commands for configuring the prohibited OPC table
Command Function

ADD N7DO To add the prohibited OPC

MOD N7DO To modify the prohibited OPC

RMV N7DO To remove the prohibited OPC

LST N7DO To query the prohibited OPC

12.2.9 Adding Link Set Shielding Table

This section describes the command, parameter, and related commands for adding the link set
shielding table.

Command
ADD N7LSM

Parameter
Par Par Parameter Description
ame ame
ter ter
ID Na
me

12-24 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Par Par Parameter Description

ame ame
ter ter
ID Na
me

Related Commands

Table 12-11 Related commands for configuring the link set shielding table
Command Function

ADD N7LSM To add the link set shielding

MOD N7LSM To modify the link set shielding

RMV N7LSM To remove the link set shielding

LST N7LSM To query the link set shielding

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 12-25

12.2.10 Adding the Initial Shielding Table

This section describes the command, parameters, and related commands for adding the initial
shielding table.

Command
ADD N7IM

Parameter
Parame Paramete Parameter Description
ter ID r Name

12-26 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Related Commands

Table 12-12 Related commands for configuring the initial shielding table
Command Function

ADD N7IM To add the initial shielding

MOD N7IM To modify the initial shielding

RMV N7IM To remove the initial shielding

LST N7IM To query the initial shielding

12.3 Configuration Examples

This section provides examples to describe how to configure the M3UA shielding data.

Example Description
Shielding condition: To shield the messages sent from the links with link set index "0".

Table 12-13 Data collection table

Shielding Condition Shielding Reference

Prohibited RC: 10-100 100

Prohibited message class: 3
Prohibited message type: 0-255
Prohibited DPC: National network with SPC
range 410000-610000

NOTE

The shielding conditions are collected based on requirements. The shielding reference should be planned
based on requirements and not be identical with any existing record. Configure related information in the
corresponding shielding table based on the collected shielding conditions.

Procedure
Step 1 To add the prohibited RC table, where Description is RC_10_to_100, Shielding reference is
100, Min. RC is 10, and Max. RC is 100, run the following command. After the command is
successfully executed, the index 0 is generated.
ADD M3RC: DESC="RC_10_to_100", MR=100, FROMRC=10, TORC=100,CONFIRM=Y;

Step 2 To add the prohibited M3UA message type table, where Description is ASPM, Shielding
reference is 100, Min.Msg class is 03, Max.Msg class is 03, Min.Msg type is 00, Max.Msg
type is 255, Type of next shielding table is Prohibited RC table, and Next shielding
reference is 100, run the following command. After the command is successfully executed, the
index 0 is generated.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 12-27

ADD M3MT: DESC="ASPM", MR=100, FROMMSGCLS=03, TOMSGCLS=03,

FROMMSGTYPE=00, TOMSGTYPE=255, TTYPE=M3RC, NMR=100,CONFIRM=Y;

Step 3 To add the prohibited DPC table, where Description is DPC_410000_to_610000, Shielding
reference is 100, Network indication is National, Min. DPC is 410000, Max. DPC is
610000, Type of next shielding table is Prohibited M3UA message type table, and Next
shielding reference is 100, run the following command. After the command is successfully
executed, the index 0 is generated.
ADD N7DD: DESC="DPC_410000_to_610000", MR=100, NI=NM, FO="410000",
TO="610000", TTYPE=M3MT, NMR=100,CONFIRM=Y;

Step 4 To add the initial shielding table, where Type of next shielding table is Prohibited DPC
table, Next shielding reference is 100, and Shielding function needed or not is True, run the
following command. After the command is successfully executed, the index 1 is generated.
ADD N7IM: TTYPE=DDT, NMR=100, MASK=TRUE,CONFIRM=Y;

Step 5 To reference index 1 of the initial shielding table to Outgoing shielding table index of which
the link set index is 0, run the following command.
MOD M3ASSOS: IDX=0, OUTSCREEN=1, CONFIRM=Y;

----End

12-28 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

13 Configuring M2PA Data

About This Chapter

The M2PA data is required when the SG7000 connects with the softswitch device that supports
the MTP3 over M2PA. Before configuring the M2PA data, make sure that the hardware data,
local office data, and SCTP data are configured.
To configure the SG7000 data, follow the procedure as shown in Figure 13-1. In this way, the
key fields are defined before they are referenced by other data tables and no junk data is
generated.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 13-1

Figure 13-1 Data configuration procedure

13.1 Configuration Preparations

This section describes the background information, technical terms, and configuration steps to
be studied before data configuration.
13.2 Configuring M2PA Data
Configuring the M2PA data including adding the local IP address, adding the local IP address
combination, adding the remote IP address, and adding the remote IP address combination.
13.3 Configuration Examples
This section provides examples to describe how to configure the M2PA data.

13-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

13.1 Configuration Preparations

This section describes the background information, technical terms, and configuration steps to
be studied before data configuration.
13.1.1 Terms
This section describes the terms used during configuring the M2PA data.
13.1.2 Networking Structure
This section describes the networking structure for configuring the M2PA data.
13.1.3 Relation Between Data Tables
The M2PA data shares the serial tables of adding the link set, adding the route, and adding the
link with the MTP. The steps for configuring the M2PA data are similar as those for configuring
the MTP data. The difference is that you must configure the local and remote IP addresses, but
not the semi-permanent connection for adding an M2PA link.
13.1.4 Data Collection
Before configuring the M2PA data, you must collect the data including the local office SPC,
DPC, and local IP address.
13.1.5 Configuration Principles
You must follow certain principles to configure the M2PA data.
13.1.6 General Steps
The steps for configuring the M2PA data are almost the same as those for configuring the MTP
data. The difference is that you require to configure the local and remote IP address, but not the
semi-permanent connection for adding an M2PA link.

13.1.1 Terms
This section describes the terms used during configuring the M2PA data.
M2PA is the peer-to-peer adaptation layer of No.7 MTP2 in the SIGTRAN protocol. The M2PA,
together with the SCTP, simulates functions of the MTP2 to provide an IP No.7 signaling link
and the primitive access of the MTP2 for its upper layer. In this way, MTP3 can operate the IP-
based links.

13.1.2 Networking Structure

This section describes the networking structure for configuring the M2PA data.
During the configuration of the M2PA data, the SG7000 is connected with softswitch such as
the SoftX3000 of Huawei through the M2PA. See Figure 13-2 for more details. In the
networking, the SG7000 occupies an independent signaling point code and the softswitch
requires to support the MTP3.

Figure 13-2 Networking structure when configuring the M2PA data

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 13-3

13.1.3 Relation Between Data Tables

The M2PA data shares the serial tables of adding the link set, adding the route, and adding the
link with the MTP. The steps for configuring the M2PA data are similar as those for configuring
the MTP data. The difference is that you must configure the local and remote IP addresses, but
not the semi-permanent connection for adding an M2PA link.

For parameter referencing relationship between the tables shared by the MTP and M2PA, see
chapter 4 Configuring MTP Data.

The parameter referencing relation between the M2PA link and the local IP address combination,
and the M2PA data and the remote IP address combination are shown in Figure 13-3.

Figure 13-3 Relation Between the M2PA Data Tables

13.1.4 Data Collection

Before configuring the M2PA data, you must collect the data including the local office SPC,
DPC, and local IP address.

Before configuring the M2PA data, collect the data listed in Table 13-1.

Table 13-1 Data collection table

Local office Destination Whether Signaling link

signaling point code signaling point code adjacent code

13-4 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Local office Destination Whether Signaling link

signaling point code signaling point code adjacent code

Local IP address Peer IP address Local SCTP port Peer SCTP port
number number

13.1.5 Configuration Principles

You must follow certain principles to configure the M2PA data.
You must follow the principles below to configure the M2PA data:
l In the process of local address binding, the first IP address has the highest priority by default.
If it is unavailable, the second IP address in this combination is selected. The sequence of
indices is the sequence of priorities of the IP addresses. In different address combinations,
the IP address sequences are different.
l For the connection of the same frame, the first IP address in the local IP address combination
index should be set to the IP address of the SBPI in the frame. Thus, the data of the same
frame is first sent from the SBPI in this frame to avoid data transfer among the frames.
For example, there are three local IP addresses (10.11.200.1, 10.11.200.2, and 10.11.200.2).
The local IP address index numbers 1, 2, and 3 relate to the SBPI in frames 1, 2, and 3
respectively. When configuring the local IP address combination table, configure the
following local IP address combinations:
– Combination 1: 1, 2, and 3
– Combination 2: 2, 1, and 3
– Combination 3: 3, 2, and 1
These are the three different IP address combinations. If the connection is configured on
the board in frame 1, use combination 1. If the connection is configured on the board in
frame 2, use combination 2. If the connection is configured on the board in frame 3, use
combination 3. Thus, the data is first sent from the SBPI of the frame where the data belongs.
l In the record of adding local IP address combinations, configure IP address index from 1
to 16 sequentially. Ensure that all IP address indices are configured.

13.1.6 General Steps

The steps for configuring the M2PA data are almost the same as those for configuring the MTP
data. The difference is that you require to configure the local and remote IP address, but not the
semi-permanent connection for adding an M2PA link.
The data configuration of the M2PA includes the following two aspects:
l Configure IP address and IP address combination.
l Configure the routing data according to the "destination signaling point -> link set -> route
-> link" mode. The configuration mode of the routing data is the same as that of the MTP
routing data.
Configure the hardware data, local office data, and SCTP data before configuring the M2PA
data. The detailed configuration of the M2PA data is listed in Table 13-2.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 13-5

Table 13-2 Steps for adding the M2PA connection

Step Operation

1 To add the local IP address (ADD LIP)

2 To add the local IP address combination table (ADD LIPC)

3 To add the remote IP address (ADD RIP)

4 To add the remote IP address combination table (ADD RIPC)

5 To add the access control information (ADD IPDAL)

6 To add the MTP DSP (ADD N7DSP)

7 To add the MTP link set (ADD N7LKS)

8 To add the MTP route (ADD N7RT)

9 To add the M2PA link (ADD N7LNK)

13.2 Configuring M2PA Data

Configuring the M2PA data including adding the local IP address, adding the local IP address
combination, adding the remote IP address, and adding the remote IP address combination.

The configuration of some M2PA data is described in preceding chapters and you can refer to
the specified chapter based on Table 13-3.

Table 13-3 Reference list

Configuration Chapter to Be Referenced

Operation

Adding local IP The local IP address table is the FE interface configuration table of the
address (ADD SCTP association.
LIP) Configure the local IP address before adding the SBPI when configuring
the hardware data. For how to add local IP addresses, see chapter 2
Configuring Hardware Data.

Adding local IP For principles and methods of configuration, see chapter 11 Configuring
address M3UA Data.
combination
(ADD LIPC)

Adding remote
IP address (ADD
RIP)

Adding remote
IP address
combination
(ADD RIPC)

13-6 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Configuration Chapter to Be Referenced

Operation

Adding access
control
information
(ADD IPDAL)

Adding The operation of adding the M2PA link and adding the MTP link share
destination the same N7DSP table. For configuration methods, see chapter 4
signaling point Configuring MTP Data.
(ADD N7DSP)

Adding MTP link The same N7DSP table is used for adding the M2PA link and adding the
set (ADD MTP link. For configuration methods, see chapter 4 Configuring MTP
N7LKS) Data.

Adding MTP The same N7DSP table is used for adding the M2PA link and adding the
route (ADD MTP link. For configuration methods, see chapter 4 Configuring MTP
N7RT) Data.

13.2.1 Adding M2PA Link

The same N7DSP table is used for adding the M2PA link and adding the MTP link.

13.2.1 Adding M2PA Link

The same N7DSP table is used for adding the M2PA link and adding the MTP link.

When a record is added to the M2PA link table, the system allocates an idle index value for the
record.

Command
ADD N7LNK

Parameter
Par Par Parameter Description
ame ame
ter ter
ID Na
me

SN Shel It specifies the numbers of the shelf, frame, and slot where the SBPU/SBPE
f board used by the M2PA link is located.
num
ber

FN Fra
me
num
ber

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 13-7

Par Par Parameter Description

ame ame
ter ter
ID Na
me

BN Slot
num
ber

LO Loc It specifies the location of the SBPU/SBPE (Front Board).

C atio This parameter and the former three parameters, specifies the location of a
n board where a link is located.

LPN Link It specifies which link on the SBPU/SBPE is occupied by the link. On each
port SBPU/SBPE, there are at most 32 M2PA links corresponding to port numbers
num 0-31 respectively. Therefore, the value of the parameter must be from 0-31
ber when you configure the M2PA links.

LSX Link It specifies the index number of the MTP link set to which the link belongs.
set
inde
x

SLC Sign The signaling link code must be the same as that at the other end of the same
alin link. You must coordinate with the peer end on how to set the signaling link
g code.
link
code

PR Intra It specifies the priority of the intra-set link to which the signaling link belongs.
-set The signaling links with the higher priorities are first selected to bear the
prio services. The signaling links with lower priorities bear the services only when
rity the signaling links with higher priorities in the same link set become
unavailable. It is the same as the priority field in "routing table". If the value
is lower, the corresponding priority is higher. The value 255 indicates an
invalid priority.

CT Circ The options are as follows:

uit l NOR64K (64K ordinary link)
type
l SAT64K (64K satellite link)
l HSL (2M/1.5M link)
l M2PALNK (M2PA link)
l ATM (ATM 2M link)
l M264K (M2UA 64K link)
l M22M (M2UA 2M link)
Select M2PALINK here. Table 13-4 lists the parameter descriptions when the
Circuit type is set to M2PALINK.

13-8 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Table 13-4 Parameter descriptions when the Circuit type is set to M2PALINK
Parameter M2PALNK

Timer index Timer index It specifies the index number of the timer value used by the link.
The timer parameter value to which the index corresponds is in the timer table.

Port number The four parameters are used to create the same SCTP association.
of local end, The Port number of local end and Port number of peer end are the
Port number parameters used when the SG7000 interconnects with the softswitch. You
of peer end, must coordinate with the peer end to set the Port number of local end and
IP address Port number of peer end to the value the same as that at the peer end. The
combination value ranges from 1024 to 65535.
index of
local end, The value of IP address combination index of local end is the index value
and IP obtained after running the command ADD LIPC. The value of IP address
address combination index of peer end is the index value obtained after running the
combination command ADD RIPC.
index of peer
end

Is it the Both the SG7000 and softswitch can act as a client or a server. The peer end
server using the M2PA must be configured to the server at one end and the client
starting SCTP association at the other end. The SG7000 serves as the server
and the softswitch serves as the client by default, which can start the SCTP
association to the SG7000.

Link status It tests whether the link status is normal. It is set to A by default. That is, when
fill-in data you send A to the peer end, the returned value is also A if the link status is
normal.

Number of It specifies the number of data filled in the signaling. The value ranges from
fill-in data 0 to 255. It is set to 40 by default.

NOTE

The M2UA, M3UA, IUA, and M2PA protocols are based on the SCTP transmission, and it is recommended
to unify the ranges of local SCTP port number of all protocol links before configuring the data for easy
management. Do not use the same port number repeatedly.

Related Commands

Table 13-5 Related commands for configuring the MTP link

Command Function

ADD N7LNK To add the MTP link

RMV N7LNK To remove the MTP link

MOD N7LNK To modify the MTP link

LST N7LNK To query the MTP link

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 13-9

13.3 Configuration Examples

This section provides examples to describe how to configure the M2PA data.

Assumption
Add two M2PA links between the SG7000 and the SoftX3000. The two links belong to the same
link set.
The networking structure for configuring the M2PA is as shown in Figure 13-4.

Figure 13-4 Configuration example

The data collection is listed in Table 13-6.

Table 13-6 Data Collection Table

Local SP code Destination SP code Is it adjacent Signaling link
code

A1111A B1111B Yes 0, 1

IP address of local end IP address of peer end SCTP port SCTP port
number of local number of peer
end end

10.10.10.1/255.255.0.0 11.11.11.1/255.255.0.0 2905 2905

Procedure
Step 1 To add the IP address of local end, run the following command:
ADD LIP: LIP="10.10.10.1", MSK="255.255.0.0", DGW="10.10.1.1";

After running the command, the index 2 is returned.

Step 2 To add the SBPI boards in slot 5 and 10, set Board property indicator to 2. That is, the IP
address of the SBPI is 10.10.10.1/255.255.0.0. Run the following command:
ADD BRD: FN=0, SHN=0, FT=MAIN, SN=5, LOC=FPB, BT=SBPI, PI=2;
ADD BRD: FN=0, SHN=0, FT=MAIN, SN=10, LOC=FPB, BT=SBPI, PI=2;

Step 3 To add the local IP address combination, set the index 1 to the IP address of the SBPI board and
the index number of the address to 2, and run the following command:
ADD LIPC: FEX1=2;

13-10 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

After running the command, the local IP address combination index 0 is returned.

Step 4 To add the remote IP address, run the following command:

ADD RIP: RIP="11.11.11.1";

After running the command, the remote IP address index 0 is returned.

Step 5 To add the remote IP address combination, set index 1 to 0, and run the following command:
ADD RIPC: RIPX1=0;

After running the command, the remote IP address combination index 0 is returned.

Step 6 To add the IP address of the SoftX3000 to the Table IPDACL, run the following command:
ADD IPDACL: IP="11.11.11.1";

Step 7 To add the local office information, set National network code to A1111A, SCCP function to
FALSE, Logic network index to default value 0.x, and run the following command:
SET OFI: SN1=NM, SN2=NS, SN3=IM, SN4=IS, NPC="A1111A", SCCP=FALSE;

After running the command, the local SP index number 0 is returned.

Step 8 To add the destination signaling point, set DSP title to HW-A, National network code to
B1111B, Route selection field to 0 (only one link set), SCCP function to FALSE, use the
default values for other parameters, and run the following command:
ADD N7DSP: DESC="HW-A", NPC="B1111B", SCCPUSED=NONE;

After running the command, the DSP index 1 is obtained.

Step 9 To add the signaling link set, set Adjacent SP index to 1, Local SP index to 0, Link selection
field to 2 (two links in the link set), use the default values for other parameters, and run the
following command:
ADD N7LKS: APX=1, OFX=0, NI=NM, SLS=2;

After running the command, the link set index 1 is returned.

Step 10 Add the MTP route.

To add the MTP route, set Route title to HW-A, Link set index to 0, DSP index to 1, use the
default values for other parameters, and run the following command:
ADD N7RT: DESC="HW-A", LSX=0, DPX=1;

Step 11 Add the MTP signaling link.

l To add the MTP link, set Link title to M2PALINK1, Shelf number to 0, Frame number
to 0, Slot number to 0, Location to FPB, Circuit type to M2PALNK, Link port
number to 5, Link set index to 1, Signaling link code to 0 (By default), Intra-set
priority to 0, Timer index to 0, Port number of local end to 2000, Port number of peer
end to 2005, Server to SG7000, SCTP index to 0, and run the following command:
ADD N7LNK: LN="toM2PALINK1", FN=0, SHN=0, SN=0, LOC=FPB, CT=M2PALNK,
LPN=5, LSX=1, LP=2000, PP=2005, LIPCX=0, PIPCX=0, SCTPIDX=0;
l To add the MTP link, set Link title to M2PALINK2, Shelf number to 0, Frame number
to 0, Slot number to 1, Location to FPB, Circuit type to M2PALNK, Link port
number to 0, Link set index to 1, Signaling link code to 0, Intra-set priority to 0, Timer
index to 0, Port number of local end to 2000, Port number of peer end to 2010, Server
to SG7000, SCTP index to 1, and run the following command:

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 13-11

ADD N7LNK: LN="toM2PALINK2", FN=0, SHN=0, SN=1, LOC=FPB, CT=M2PALNK,

LPN=0, LSX=1, SLC=1, LP=2000, PP=2010, LIPCX=0, PIPCX=0, SCTPIDX=1;

----End

13-12 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

14 Configuring M2UA Data

About This Chapter

The No.7 MTP2-User Adaptation layer protocol (M2UA) data is required when the SG7000
connects with NGN equipment such as the trunk media gateway (TMG) over M2UA. Before
configuring the M2UA data, make sure that the hardware data, local office data, and SCTP data
are configured.
To configure the SG7000 data, follow the procedure as shown in Figure 14-1. In this way, the
key fields are defined before they are referenced by other data tables and no junk data is
generated.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 14-1

Figure 14-1 Data configuration procedure

14.1 Configuration Preparations

This section describes the background information, technical terms, and configuration steps to
be studied before data configuration.
14.2 Configuring M2UA Data
Configuring the M2UA data including adding the local IP address, adding the local IP address
combination, adding the remote IP address, and adding the remote IP address combination.
14.3 Configuration Examples
This section provides examples to describe how to configure the M2UA data.

14-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

14.1 Configuration Preparations

This section describes the background information, technical terms, and configuration steps to
be studied before data configuration.
14.1.1 Terms
This section describes the terms used during configuring the M2UA data.
14.1.2 Networking Structure
This section describes the networking structure for configuring the M2UA data.
14.1.3 Relation Between Data Tables
M2UA data and MTP data share tables to add destination signaling points (DSPs), routes and
links, and link sets. The steps for configuring the M2UA data are similar to those for adding the
MTP data. When adding the M2UA links, you need to however configure the local IP address
combination, M2UA link set and M2UA link, and remote IP address combination, without
configuring semi-permanent connections.
14.1.4 Data Collection
Before configuring the M2UA data, you must collect the data including the local SPC, DPC,
and local IP address.
14.1.5 Configuration Principles
You must follow certain principles to configure the M2UA data.
14.1.6 General Steps
You must follow certain procedures to configure the M2UA data.

14.1.1 Terms
This section describes the terms used during configuring the M2UA data.

M2UA
M2UA is defined by RFC 3331. It transmits Message Transfer Part Level 3 (MTP3) messages
through IP, using Stream Control Transmission Protocol (SCTP) or other proper transmission
protocols. In the SG7000, functions of M2UA are realized at the application server (AS) side.
Figure 14-2 shows the protocol stack.

Figure 14-2 M2UA protocol stack in the SG7000

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 14-3

MTP3 is the upper layer of M2UA.

Application Server (AS)

An AS is a logical entity. It represents certain resources and corresponds to a specific routing
key. For example, it can be a virtual database unit, processing all query transactions with the
"DPC/OPC/SCCP_SSN" identifier. An AS contains a group of application server processes
(ASPs), one or some of which can process certain services.

For instance, the media gateway controller (MGC) processes calls on MTP3 and those on SS7
links terminated at the SG7000. An MTP2 link over an M2UA link set is regarded as an AS in
the NGN.

ASP
An ASP is an instance of the AS process. It corresponds to an SCTP endpoint and can serve
multiple ASs. It works in the active/standby mode in the M2UA application. Only the active
ASP processes services.

Interface ID

It is used to communicate between the two ends of M2UA. It can be in the text coding scheme
or the integer coding scheme. An interface ID corresponds to an actual physical link and is locally
effective. It is negotiated by equipment (such as the SG and the TMG) connecting the two ends.
See Figure 14-3.

Figure 14-3 Relationship between the SS7 link, interface ID, and AS and ASP

Signaling Gateway Process

Signaling gateway process (SGP) is an instance communicating with the signaling link terminal
through the M2UA. It has three states: active, standby, and load sharing.

Layer Management
It is the node function of the SG or the ASP, which processes input and output between the
M2UA layer and the local management entities.

14-4 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

M2UA Link
It is the logical connection between the SG and the MGC/TMG ASP. An M2UA link contains
SCTP associations of the SG and the ASP and those between the SG and the ASP. Its state
corresponds to the states of the ASP and the SCTP association.

Figure 14-4 shows the M2UA network structure. The structure can be simplified after the M2UA
links are introduced, as shown in Figure 14-5.

Figure 14-4 M2UA network structure

Figure 14-5 Simplified M2UA network structure

The M2UA link provides channels for one or multiple MTP2 links, to communicate with the
MTP3 users. Each MTP2 link is mapped to a specific M2UA link through an M2UA interface
ID. You must run commands to configure the relationship. Therefore, data from the MTP2 links
can be transparently transmitted through the M2UA links.

Client/Server Model
Both, the SGP and the ASP can support operations on the server and the client. If there are two
endpoints using the M2UA, configure one endpoint as the client and the other as the server.

14.1.2 Networking Structure

This section describes the networking structure for configuring the M2UA data.

Figure 14-6 shows the networking structure of the M2UA application. The SG7000 terminates
the M2UA link coming from the TMG, and then sends signaling messages to the SoftX3000
through the M3UA link.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 14-5

Figure 14-6 M2UA application

14.1.3 Relation Between Data Tables

M2UA data and MTP data share tables to add destination signaling points (DSPs), routes and
links, and link sets. The steps for configuring the M2UA data are similar to those for adding the
MTP data. When adding the M2UA links, you need to however configure the local IP address
combination, M2UA link set and M2UA link, and remote IP address combination, without
configuring semi-permanent connections.
For relationship between configuration parameters in the table shared by the M2UA data and
MTP data, see chapter 4 Configuring MTP Data.
Figure 14-7 describes the relation between parameters and indexes of the M2UA link, M2UA
link set, local IP address combination, and remote IP address combination.

Figure 14-7 Relation between the M2UA configuration parameters

14-6 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

NOTE

l You can delete data in the tables only when the data is unavailable.
l You can delete a configuration table only when it is not referenced by other tables.

14.1.4 Data Collection

Before configuring the M2UA data, you must collect the data including the local SPC, DPC,
and local IP address.
Table 14-1 lists the data required for configuring the M2UA data.

Table 14-1 M2UA data collection table

Local IP address Local port number Remote IP address Remote port
number

Equipment type Service processing Type of the interface Value of the

mode ID interface ID

Local office signaling point code Destination signaling point code

14.1.5 Configuration Principles

You must follow certain principles to configure the M2UA data.

Local IP Address Combination

l When binding the local IP addresses, the SCTP uses the first IP address by default.
If the first IP address is unavailable, The SCTP chooses the second one in the combination;
if the second one is also unavailable, it chooses the third one; until it chooses the available
one. Therefore, index sequences indicate the priorities of IP addresses; and the IP address
combination varies with the IP address sequence.
l When configuring links in a frame, configure the first IP address in the local IP address
combination index as the IP address of the SBPI in the frame. In this case, the data in the
frame can be sent from the SBPI in the frame first, which decreases data forwarding between
frames.
For example, indices of the local IP addresses 10.11.200.1, 10.11.200.2, and 10.11.200.3
are 1, 2, and 3, which corresponds to the SBPIs in frames 1, 2, and 3 respectively. When
configuring the local IP address combination table, configure the following combinations:
– Combination 1: 1, 2, 3
– Combination 2: 2, 1, 3
– Combination 3: 3, 2, 1
These combinations are different. If you configure the link on the board in frame 1, use
combination 1; if you configure the link on the board in frame 2, use combination 2; if you

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 14-7

configure the link on the board in frame 3, use combination 3. Thus, messages can be sent
from the SBPI board in the located frame.
l When adding a new record of the local IP address combination, consecutively configure
the IP address index from 1 to 16. Make sure that all indices between two IP address indices
are configured.

M2UA Link
l Select the same local IP address combination index for links on one SBPU/SBPE. Set the
first IP address of the combination index to the IP address index of the SBPI board in the
same frame with the SBPU/SBPE.
l If the same IP address combination index is unavailable for links on one SBPU/SBPE,
ensure that there are no repeated IP address indices in different IP address combinations.
l Configure M2UA links belonging to one M2UA link set on the same board.
l Configure the M2UA link and the M2UA link that carries its services on the same board.

14.1.6 General Steps

You must follow certain procedures to configure the M2UA data.

The M2UA data configuration includes two main aspects:

l Configure the M2UA data in the sequence of IP address and IP address combination →
M2UA link set → M2UA link.
l Configure routing data in the sequence of destination signaling point (DSP) → link set
→ route → link. The configuration method is the same as that of configuring the MTP
routing data.
l Configure the M2UA data after configuring the hardware data, local office data, and SCTP
data. For details of configuration steps, see Table 14-2.

Table 14-2 Steps for configuring M2UA data

Step Operation

1 To add the local IP address (ADD LIP)

2 To add the local IP address combination table (ADD LIPC)

3 To add the remote IP address (ADD RIP)

4 To add the remote IP address combination table (ADD RIPC)

5 To add the access control information (ADD IPDAL)

6 To add the M2UA link set (ADD M2UALKS)

7 To add the M2UA link (ADD M2UALNK)

8 To add the MTP DSP (ADD N7DSP)

9 To add the MTP link set (ADD N7LKS)

10 To add the MTP route (ADD N7RT)

14-8 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Step Operation

11 To add the MTP link (ADD N7LNK)

14.2 Configuring M2UA Data

Configuring the M2UA data including adding the local IP address, adding the local IP address
combination, adding the remote IP address, and adding the remote IP address combination.
The configuration of some M2UA data is described in preceding chapters and you can refer to
the specified chapter based on Table 14-3.

Table 14-3 Reference list

Configuration Chapter to Be Referenced
Operation

Adding local IP For principles and methods of configuration, see chapter 11 Configuring
address M3UA Data.
combination
(ADD LIPC)

Adding remote
IP address (ADD
RIP)

Adding remote
IP address
combination
(ADD RIPC)

Adding access
control
information
(ADD IPDAL)

Adding The operation of adding the M2PA link and adding the MTP link share
destination the same N7DSP table. For configuration methods, see chapter 4
signaling point Configuring MTP Data.
(ADD N7DSP)

Adding MTP link The same N7DSP table is used for adding the M2PA link and adding the
set (ADD MTP link. For configuration methods, see chapter 4 Configuring MTP
N7LKS) Data.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 14-9

Configuration Chapter to Be Referenced

Operation

Adding MTP The same N7DSP table is used for adding the M2PA link and adding the
route (ADD MTP link. For configuration methods, see chapter 4 Configuring MTP
N7RT) Data.

14.2.1 Adding M2UA Link Set

When a new record is added in the M2UA link set table, the system allocates an idle index value
for the record.
14.2.2 Adding M2UA Link
When a new record is added in the M2UA link table, the system allocates an idle index value
for the record.
14.2.3 Adding MTP Link
You can use the same N7LNK table to add the M2UA links and MTP links.

14.2.1 Adding M2UA Link Set

When a new record is added in the M2UA link set table, the system allocates an idle index value
for the record.

Command
ADD M2UALKS

Parameter
Paramete Paramete Parameter Description
r ID r Name

TMODE Traffic It identifies the traffic mode of the M2UA links in an M2UA link
manage set. The two ends of the interconnected link sets must be in the
mode same transmission mode; otherwise, the M2UA link cannot work
normally. The load sharing mode is recommended. There are two
options:
l MB (Primary-standby): It is the N+1 backup mode. In this mode,
only one M2UA link in the link set is active, and the others are
in the standby state. When the active link fails, a standby link is
activated and begins to transmit the traffic.
l SHARE (Charge-shared): All links in the M2UA link set are
active. The traffic is shared by all the links in the set.
By default, it is set to SHARE.

14-10 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Paramete Paramete Parameter Description

r ID r Name

USETXT Whether It identifies the working mode of an M2UA link set. There are two
use text options:
interface l UNUSED (Unused): integer interface ID of the local M2UA
index link set
l USE (Use): text interface ID of the local M2UA link set
By default, it is set to UNUSED, indicating the integer interface
ID.
NOTE
To use the text interface ID depends on the negotiation with the peer office.

Related Commands

Table 14-4 Related commands for configuring the M2UA link set
Command Function

ADD M2UALKS To add the M2UA link set

RMV M2UALKS To delete the M2UA link set

MOD M2UALKS To modify the M2UA link set

LST M2UALKS To query the M2UA link set

14.2.2 Adding M2UA Link

When a new record is added in the M2UA link table, the system allocates an idle index value
for the record.

Command
ADD M2UALNK

Parameter
Par Par Parameter Description
ame ame
ter ter
ID Na
me

SH Shel They are the numbers of the shelf, frame, or board where the SBPU/SBPE
N f bearing the M2UA link is located.
num
ber

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 14-11

Par Par Parameter Description

ame ame
ter ter
ID Na
me

FN Fra
me
num
ber

SN Boar
d
num
ber

PH Boar It is the index number of the link on the board. An SBPU/SBPE can provide a
YN d maximum of 32 M2UA links. You can select an unused link number here.
O asso
c.
num
ber

LIPI Loc It identifies the local IP address combination index to which the SCTP
DX al IP association bearing this M2UA link is bound. The local IP address combination
com must be configured through the command ADD LIPC. The index value here
bina is allocated by the system after running the command ADD LIPC.
tion
inde
x

LO Loc It is one of the interconnection parameters to the peer equipment. It identifies

CP al the local port number of the SCTP association that carries the M2UA link. It
OR port is set to 2904 by default.
T NOTE
M2UA, M3UA, IUA and M2PA protocol are all based on SCTP association. To ease
management, regulate the range of the local SCTP port number of each protocol link
before configuring the data. The port number should be different.

RIPI Rem It identifies the remote IP address combination index to which the SCTP
DX ote association bearing this M2UA link is bound. If the softswtich supports the
IP multi-home feature of the SCTP association, you can configure the remote IP
com address combination to improve the networking reliability of the system.
bina The remote IP address combination must be configured through the command
tion ADD RIPC. The index value here is allocated by the system after running the
inde command ADD RIPC.
x

RM Rem It is the remote port number of the SCTP association that carries the M2UA
TPO ote link. Whether to configure the parameter depends on the negotiation with the
RT port remote softswtich. It is set to 2904 by default.

14-12 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Par Par Parameter Description

ame ame
ter ter
ID Na
me

AST C/S It identifies the local working mode of the SCTP association that bears this
YPE mod M2UA link. There are two options:
e l CLNT (Client): The local SCTP association is a client.
l SVR (Server): The local SCTP association is a server.
This parameter is used to set whether the SG7000 acts as a client or a server
when interconnecting with the peer softswitch. Set one end of the network
connection to the server, and the other end to the client. Configure this
parameter after negotiating with the peer office.
NOTE
At present, the SG7000 only supports the client mode. The peer office should be
configured as the server.

LN Ass It identifies the M2UA link set to which this M2UA link belongs. The index
KSI ociat value here is allocated by the system after running the command ADD
DX ion M2UALKS.
set
inde
x

ASF Acti It specifies whether the newly added link works in active or standby mode.
LA ve_s When Traffic manage mode in the command ADD M2UALKS is set to MB
G tand (Primary-Standby), this parameter is valid. Otherwise, this parameter is
by invalid.
flag l ACTIV (Active initially): The added link is active.
l STDBY (Standby initially): The added link is standby.

PRI Prio It specifies priority of the M2UA links in an M2UA link set. The link with the
OR rity higher priority will be selected first. The link with the lower priority can carry
signaling traffic only when the links with higher priorities are unavailable. The
value 0 stands for the highest priority and value 1 stands for the second highest
priority.
This field is valid if Traffic manage mode is set to SHARE (Charge
shared) in ADD M2UALKS; otherwise, it is invalid.

MA MA It is the maximum number of incoming streams of the SCTP association that

XIS X. in bears this M2UA link. It specifies the maximum number of SCTP streams
TM strea contained in each M2UA message received by the SG7000. Generally, the
ms default value 17 is selected. After the SCTP association is set up, the actual
number of incoming streams is coordinated by the two parties.

MA MA It is the maximum number of outgoing streams of the SCTP association that

XO X. bears this M2UA link. It specifies the maximum number of SCTP streams
ST out contained in each M2UA message sent by the SG7000. The default value 17
M strea is selected. After the SCTP association is set up, the actual number of outgoing
ms streams is coordinated by the two parties.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 14-13

Par Par Parameter Description

ame ame
ter ter
ID Na
me

SSC Con It is the start threshold when congestion occurs to this M2UA link. When the
TH gesti signaling load on the M2UA link reaches this threshold, the SG7000 starts the
on congestion control. It is set to 70% by default.
onse
t
thres
hold

ESC Con It is the threshold when congestion on this M2UA link vanishes. After the
TH gesti SG7000 starts the congestion control and restricts the signaling load
on transmitted on an M2UA link and when the signaling load on the M2UA link
disc decreases to this threshold, the SG7000 cancels the congestion control. It is set
ard to 50% by default. The M2UA link can transmit the traffic again after the
thres congestion control is cancelled.
hold

Related Commands

Table 14-5 Related commands for configuring the M2UA link

Command Function

ADD To add the M2UA link

M2UALNK

RMV To delete the M2UA link

M2UALNK

MOD To modify the M2UA link

M2UALNK

LST To query the M2UA link

M2UALNK

EST To establish the M2UA link

M2UALNK

ACT To activate the M2UA link

M2UALNK

14.2.3 Adding MTP Link

You can use the same N7LNK table to add the M2UA links and MTP links.

14-14 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

When a new record is added in the M2UA link table, the system allocates an idle index value
for the record.

Command
ADD N7LNK

Parameter
Paramete Paramete Parameter Description
r ID r Name

SN Shelf When adding an M2UA link, enter the numbers of the shelf, frame
number and board where the SBPU/SBPE used is located.

FN Frame
number

BN Board
number

LOC Location To add an M2UA link, select the SBPU/SBPE, that is, the front
board.
It determines the position of the board where a link is located, by
coordinating with the previous three parameters.

LPN Link port It specifies which link on the SBPU/SBPE is occupied by the link.
number Each SBPU/SBPE has 32 links, corresponding to port numbers 0
to 31 respectively. When adding a link, set this parameter to a value
within the range of 0 to 31. The configuration principles for M2UA
link port numbers are as follows:
l When only 64-kbit/s links are configured on the SLPU_64K
board, the port numbers can be set to 0-15.
l When only 64-kbit/s links are configured on the SLPU_64K
board, the port numbers can be set to 0-31.
l When only one HSL link is configured on the SLPU_2M board,
the port number is always set to 0.
l When only one ATM 2-Mbit/s link is configured on the
SHPU_2M board, the port number is always set to 0. Other links
are not allowed on this board.
l When two HSL links are configured on the SHPU_2M board,
the port numbers are always set to 0 and 1.
l When one HSL link and 64-kbit/s links are configured on the
SHPU_2M board, port 0 is configured with the HSL link, ports
1-15 are idle, and ports 16-31 are configured with 64-kbit/s
links.
l The SHPE can be configured with only HSLs. A maximum of
four HSLs can be configured on ports 0, 1, 2, and 3 of the SHPE.

LSX Link set It specifies the index of the MTP link set to which this MTP link
index belongs.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 14-15

Paramete Paramete Parameter Description

r ID r Name

SLC Signaling As the signaling link code of a link must be the same as that of the
link code peer link, negotiate with the peer office and set the signaling link
code carefully.

PR Intra-set It indicates the priority of the signaling link in the resident signaling
priority link set. Available signaling links with higher priority are preferred
to carry the traffic. Signaling links with lower priority can carry
the signaling traffic only when links with higher priority in the
same link set are unavailable. In this aspect, it is the same as the
priority field in the routing table. The higher the priority is, the
lower its value is. The value 255 is an invalid priority.

CT Circuit There are the following options:

type l NOR64K (64K ordinary link)
l SAT64K (64K satellite link)
l HSL (2M/1.5M link)
l M2PALNK (M2PA link)
l ATM (ATM 2M link)
l M264K (M2UA 64K link)
l M22M (M2UA 2M link)
When configuring an M2UA link, set it to M264K or M22M.

M2LKSI M2UA It is the index number of the M2UA link set to which the link
link set belongs. Its value is the index value returned by the system after
number running the command ADD M2UALKS.

INTIID Integer When adding an M2UA link set with the command ADD
interface M2UALKS, if Whether use text interface index is set to
ID UNUSED, enter an integer parameter here. It is one of the
interworking parameters between the SG7000 and the peer
equipment. Negotiate with the peer office and keep it consistent.

TXTIID Text When adding an M2UA link set with the command ADD
interface M2UALKS, if Whether use text interface index is set to
ID USED, enter a text parameter here. It is one of the interworking
parameters between the SG7000 and the peer equipment.
Negotiate with the peer office and keep it consistent.

TX Timer It indicates the index number of the timer used by the link. The
index corresponding timer parameter value is in the timer table.

14-16 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Related Commands

Table 14-6 Related commands for configuring the MTP link

Command Function

ADD N7LNK To add the MTP link

RMV N7LNK To remove the MTP link

MOD N7LNK To modify the MTP link

LST N7LNK To query the MTP link

ACT N7LNK To activate the MTP link

DEA N7LNK To deactivate the MTP link

14.3 Configuration Examples

This section provides examples to describe how to configure the M2UA data.

Assumption
Figure 14-8 shows a network that requires M2UA data configuration.

Figure 14-8 Network requiring the M2UA data configuration

Table 14-7 lists the data collection table.

Table 14-7 M2UA data collection table

Local IP address Local port number Remote IP Remote port number

address

10.10.10.1/255.255. 2904 11.11.11.1/255.25 2904

0.0 5.0.0

Equipment type Service processing Type of the Value of the interface

mode interface ID ID

Client Load sharing Integer 0

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 14-17

Local IP address Local port number Remote IP Remote port number

address

Local office signaling point code Destination signaling point code

A1111A B1111B

Procedure
Step 1 To add the local office information, set National network code to A1111A, SCCP function to
False, Logic network index to 0, and run the following command:
SET OFI: SN1=NM, SN2=NS, SN3=IM, SN4=IS, NPC="A1111A", SCCP=FALSE;

Step 2 To add the local IP address 10.10.10.1 or 255.255.0.0, run the following command: The index
0 is obtained.
ADD LIP: LIP="10.10.10.1", MSK="255.255.0.0", DGW="10.10.1.1";

Step 3 To add the SBPU to slot 3 of frame 1 in shelf 4, run the following command:
ADD BRD: FN=4, SHN=1, FT=MAIN, SN=3, LOC=FPB, BT=SBPU;

Step 4 To add the local IP address combination, set FE index 1 to 0 (the local IP address index generated
after running the command ADD LIP), and run the following command:
ADD LIPC: FEX1=0;

After running the command, the local IP address combination index 0 is returned.

Step 5 To add the remote IP address, run the following command:

ADD RIP: RIP="11.11.11.1";

After running the command, the remote IP address index 0 is returned.

Step 6 To add the remote IP address combination, set Remote IP address index 1 to 0, and run the
following command:
ADD RIPC: RIPX1=0;

After running the command, the remote IP address combination index 0 is returned.

Step 7 To add the IP address of the TMG to the IPDACL table, run the following command:
ADD IPDACL: IP="11.11.11.1";

Step 8 To add the M2UA link set, set Description to TMG, Traffic manage mode to SHARD,
Whether use text interface index to UNUSED, and run the following command:
ADD M2UALKS: DESC="TMG", TMODE=SHARE, USETXT=UNUSED;

After running the command, the link set index 0 is returned.

Step 9 To add the M2UA link, suppose the M2UA link is set up on the SBPU in slot 3 of frame 1 in
shelf 4, set Description to TMG, Shelf number to 4, Frame number to 1, Board number to
3, Board asso. number to 0, Local IP combination index to 0, Remote IP combination
index to 0, Local port to 2904, Remote port to 2904, Association set index to 0,
Active_standby flag to ACTIV, and run the following command:
ADD M2UALNK: DESC="TMG", SHN=4, FN=1, SN=3, PHYNO=0, LIPIDX=0, RIPIDX=0,
LNKSIDX=0;

14-18 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Step 10 To add the DSP, set DSP title to HW-A, National network code to B1111B, STP to False,
Route selection field to 0 (only one link set), SCCP function to NONE, and keep the default
values for other parameters. Now, run the following command:
ADD N7DSP: DESC="HW-A", NPC="B1111B", STP=FALSE, SCCPUSED=NONE;

After running the command, the DSP index 0 is returned.

Step 11 To add the MTP link set, set Local SP index to 0, Adjacent SP index to 0, Network
indication to NM, and keep the default values for the other parameters. Now, run the following
command:
ADD N7LKS: APX=0, OFX=0, NI=NM;

After running the command, the index 0 is returned.

Step 12 To add the route, run the following command:
ADD N7RT: LSX=0, DPX=0;

Step 13 To add the MTP link, set Link set index to 0, Signaling link code to 0, Circuit type to
M264K, M2UA link set number to 0 (the index obtained by adding the M2UA link set), Integer
interface ID to 0 (the same as that of the link at the TDM), Text interface ID to 1, Timer
index to 1, and run the following command:
ADD N7LNK: LN="toSP", FN=4, SHN=1, SN=3, LOC=FPB, LPN=0, LSX=0, CT=M264K,
M2LKSI=0, INTIID=0, TXTIID="1", TX=1;

Text interface ID is set to UNUSED; therefore it does not contain a value here.

----End

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 14-19

15 Configuring IUA Data

About This Chapter

The IUA data is required when the SG7000 connects with the softswitch device and the IAD
over the ISDN Q.921-User Adaptation (IUA) protocol. Before configuring the IUA data, make
sure that the hardware data, local office data, and SCTP data are configured.
To configure the SG7000 data, follow the procedure as shown in Figure 15-1. In this way, the
key fields are defined before they are referenced by other data tables and no junk data is
generated.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 15-1

Figure 15-1 Data configuration procedure

15.1 Configuration Preparations

This section describes the background information, technical terms, and configuration steps to
be studied before data configuration.
15.2 Configuring IUA Data
Configuring the IUA data including adding the local IP address, adding the local IP address
combination, adding the remote IP address, and adding the remote IP address combination.
15.3 Configuration Examples
This section provides examples to describe how to configure the IUA data.

15-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

15.1 Configuration Preparations

This section describes the background information, technical terms, and configuration steps to
be studied before data configuration.
15.1.1 Terms
This section describes the terms used during configuring the IUA data.
15.1.2 Networking Structure
In the SG7000, the IUA protocol acts as a bridge to connect an MGC (for example, the
SoftX3000) with an IAD. The SG7000 converges and forwards the IUA message sent by the
IAD and transparently sends the Q.931 message to the MGC (for example, the SoftX3000).
Then, the MGC processes the Q.931 call control message.
15.1.3 Relation Between Data Tables
This section describes the relations between data tables related to IUA data configuration.
15.1.4 Data Collection
Before configuring the M2UA data, you must collect the data including the local IP address,
local port number, and remote IP address.
15.1.5 Configuration Principles
You must follow certain principles to configure the IUA data.
15.1.6 General Steps
Configure the IUA data according to this sequence: IP address and IP address combination →
IUA link set → IUA link operation.

15.1.1 Terms
This section describes the terms used during configuring the IUA data.

IUA Protocol
The IUA protocol is defined by RFC 3057. IUA transmits the user signaling message (Q.931)
of the Q.921 layer of DSS1 through the stream control transmission protocol (SCTP) or other
proper protocols and IP. The ISDN interface supporting the IUA protocol is ISDN basic rate
access (BRA) interface and primary rate access (PRA) interface. Figure 15-2 shows the protocol
stack.

Figure 15-2 IUA protocol stack

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 15-3

The SG7000 supports the convergence and forwarding functions provided in the standard IUA
protocol. The communication process can be as follows:
l Point-to-point
l Point-to-multipoint

Figure 15-3 shows the use of IUA.

Figure 15-3 Application of IUA in the SG7000

Interface
The IUA protocol supports the interface related to the ISDN signaling channel. The ISDN
signaling channel can be the channel D with the speed of 16 kbit/s, which is used for ISDN BRI,
and the basic or backup signaling channel with the speed of 64 kbit/s, which is used for ISDN
PRI.

Application Server (AS)

The AS is a logical entity for a specified application. For example, the AS can process the Q.
931 message and the call process for channel D terminated at a gateway.

Application Server Process (ASP)

ASP specifies the process case of an AS, for example, the active or standby MGC.

Layer Management
Layer management is the function of a local node. It processes the transmission of messages
between the IUA layer and the local management entity.

15.1.2 Networking Structure

In the SG7000, the IUA protocol acts as a bridge to connect an MGC (for example, the
SoftX3000) with an IAD. The SG7000 converges and forwards the IUA message sent by the
IAD and transparently sends the Q.931 message to the MGC (for example, the SoftX3000).
Then, the MGC processes the Q.931 call control message.

15-4 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

The networking structure for configuring the IUA data is as shown in Figure 15-4.
In the IUA connection between one or more IADs and the SG7000 , the IAD serves as an SGP,
and the SG7000 serves as an ASP. In the IUA connection between the SG7000 and the
Softswtich, the SG7000 is located at the SGP side, and the softswtich at the ASP side.

Figure 15-4 SG7000 networking with the IUA protocol

15.1.3 Relation Between Data Tables

This section describes the relations between data tables related to IUA data configuration.
For the referencing relationship between the parameters of IUA data tables, see Figure 15-5.
Configure IUA data from the top table to the bottom table in the figure. To add the data tables,
add the upper tables first, and then the lower tables. To delete the data tables, delete the lower
tables first, and then the upper tables.

Figure 15-5 Relation between IUA data tables

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 15-5

NOTE

l All data in the tables can be deleted only when they are unavailable.

l A configuration table can be deleted only when it is not referenced by other tables.

15.1.4 Data Collection

Before configuring the M2UA data, you must collect the data including the local IP address,
local port number, and remote IP address.

Table 15-1 lists the data required when configuring the IUA data.

Table 15-1 IUA data collection table

Local IP address Local port number Remote IP address

Remote port number Maximum number of IUA Maximum number of IUA links
link sets

Maximum users of C/S mode Traffic mode

IAD

15.1.5 Configuration Principles

You must follow certain principles to configure the IUA data.

CAUTION
When configuring the IUA data, do not configure any other data.

Local IP Address Combination

For details, see chapter 11 Configuring M3UA Data.

Remote IP Address Combination

The quantity of remote devices may be very large; therefore, special commands are used to
configure the remote IP address combination, remote IP address, and access control information.

IUA link

15-6 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

l In initial state, you cannot configure the IUA link directly. Set MAX NUMBERS OF IUA
LINKSET, MAX NUMBERS OF IUA LINK, and MAX USERS OF IAD to a value
(except 0) in the command SET SOFTCFG before configuring the IUA link.
l When the connection between the SG7000 and the IAD is configured, the IUA links need
configuring. It is recommended to configure the data offline, and then load all the
configured data to the host.
l When you create the link from the IAD to the MGC through the SG7000 converging, add
the IUA link set from the SG7000 to the IAD because the IUA link set from the SG7000
to the MGC already exists by default.
NOTE

The system provides 256 IUA link sets between the SG7000 and the MGC by default. In this case, when
you use the command ADD IUALKS to add the IUA link set, it is the link set between the IAD and the
SG7000. The index of the link set starts from 256.

Interface
The IUA feature of the SG7000 only implements the convergence and forwarding functions of
the IUA link. When the interface of an IUA link is globally unique, the interface configured on
the SG to connect the IAD cannot be the same as the one configured to connect the softswitch.

An IAD interface must correspond to a softswitch interface so that the SG7000 can transparently
transfer the IUA message. In the SG7000, the interface between the SG7000 and the IAD (or
the softswitch) is configured by the system. You do not require to configure them manually at
the background. The calculation principle inside the system is as follows:

The value of the interface between the SG7000 and each IAD is the value between 0 and the
value generated by subtracting 1 from the maximum number of users of the IAD. The value of
the interface between the SG7000 and the softswitch is generated like this: Multiply the IAD
index with 256 (eighth power of 2) to obtain a value, and then add the obtained value to the value
of the IAD interface.

According to the above calculation principle, the IAD interfaces and softswitch interfaces are
configured. At the same time, the corresponding relationship between every IAD interface and
every softswitch interface is formed.

15.1.6 General Steps

Configure the IUA data according to this sequence: IP address and IP address combination →
IUA link set → IUA link operation.

Configure the IUA data after configuring the hardware data, local office data, and SCTP data.
For details of configuration steps, see Table 15-2.

Table 15-2 Steps for configuring the IUA data

Step Operation

1 To add the board (ADD BRD)

2 To add the local IP address (ADD LIP)

3 To add the local IP address combination table (ADD LIPC)

4 To add the extended remote IP address (ADD EXRIP)

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 15-7

Step Operation

5 To add the extended remote IP address combination table (ADD

EXRIPC)

6 To add the extended access control information (ADD EXIPDACL)

7 To set the software configuration parameter (SET SOFTCFG)

8 To convert the formats of all data (FMT)

9 To set the board software DIP switch (SET SFTSWT)

10 To add the IUA link set (ADD IUALKS)

11 To add the IUA link (ADD IUALNK)

15.2 Configuring IUA Data

Configuring the IUA data including adding the local IP address, adding the local IP address
combination, adding the remote IP address, and adding the remote IP address combination.
15.2.1 Adding the Board
This section describes the command, parameter, and related commands for adding a board.
15.2.2 Adding Local IP Address
The local IP address table is the FE interface configuration table of the SCTP association.
15.2.3 Adding Local IP Address Combination
This section describes the command, parameter, and related commands for adding the local IP
address combination.
15.2.4 Adding Extended Remote IP Address
The parameter of the command for adding an extended remote IP address has only one IP address.
When the SG7000 is interconnected with the softswitch, this parameter defines the IP address
of an interface board on the softswitch. When a record is added, the system allocates an idle
index for this record.
15.2.5 Adding Extended Remote IP Address Combination
The extended remote IP address combination table can hold up to 100,000 extended remote IP
address indexes. When a record is added, the system allocates an idle index for this record.
15.2.6 Adding the Extended Access Control Information
With this function, the SG7000 checks whether the access of the IP address of remote equipment
is illegal.
15.2.7 Setting Software Configuration Parameter
This command is used to set the software configuration parameter. In the initial state, the values
of MAX numbers of IUA linkset, MAX numbers of IUA link, and MAX users of IAD are
0, which indicates that the IUA is not enabled. You can continue to configure the IUA data only
after you set the values for the three parameters based on actual conditions.
15.2.8 Converting Formats
This command is used to convert the format of the data in the BAM database to binary file which
can be identified by the host. Thus the data can be loaded to the host. The host data load file

15-8 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

converted is stored under the directory D:\SGDATA on the BAM hard disk, with the file name
format of db_?.dat by default.
15.2.9 Setting Board Software DIP Switch
This section describes the command, parameter, and related commands for setting the board
software DIP switches.
15.2.10 Adding IUA Link Set
When a record is added in the IUA link set table, an idle index value will be allocated for the
record.
15.2.11 Adding IUA link
When a record is added in the IUA link table, an idle index value will be allocated for the record.

15.2.1 Adding the Board

This section describes the command, parameter, and related commands for adding a board.

Command
ADD BRD

Parameter
Para Para Parameter Description
met met
er er
ID Na
me

SHN Shel It supports up to five combined cabinets. The range is from 0 to 4. The main
f control cabinet is always numbered 0. The other cabinets are numbered
num sequentially according to their physical locations.
ber

FN Fra Either the main control cabinet or the expansion cabinet 4 can be configured
me with up to two service frames. Each expansion cabinets from 1 to 3 can be
num configured with up to four service frames. The service frames are numbered
ber from 0 to 3 from the bottom upwards.
The service frame number is determined by 8 switches of the DIP switch S3
on the HBIU. The frame numbers configured here must be unanimous with
those set by the HBIU DIP switch.

FT Fra There are two types of frames: NULL (Dummy frame) and MAIN (Main
me service frame).
type The following parameters are activated only when MAIN (MAIN SERVICE
FRAME) is selected.

SN Slot The range of the slot number is 0-20.

num
ber

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 15-9

Para Para Parameter Description

met met
er er
ID Na
me

LOC Loca There are four types of locations: FPB (Front board), UDB (Upper subboard),
tion DDB (Lower subboard), and BPB (Back board).
Select the board location according to the type of board, when adding a board.
In addition, there are two SLPUs or SHPUs on the SBPU. The SBPE can be
configured with two SHPEs, two SHPUs, or two SLPUs. One is pinched on
the upper location of the SBPU/SBPE and the other is pinched on the lower
location of the SBPU/SBPE. You can uniquely determine the location of a
subboard with the UDB (Upper pinch board) and DDB (Lower
subboard).

BT Boar The types of board are as follows:

d l NULL (Dummy board)
type
l HSYS (HSYS board)
l SBPU (SBPU board)
l SBPE (SBPE board)
l SBPI (SBPI board)
l SLPU64K (SLPU64K board)
l SLPU2M (SLPU2M board)
l SHPU64K (SHPU64K board)
l SHPU2M (SHPU2M board)
l SHPE (SHPE board)
l EPII (EPII board)
l SEPU (SEPU board)
l CKII (CKII board)
l ALUI (ALUI board)
The SLPU64K, SLPU2M, SHPU64K, and SHPU2M are subboards of the
SBPU.
The SLPU64K, SLPU2M, SHPU64K, SHPU2M, and SHPE are subboards of
the SBPE.
The boards which are not listed here need no configuration. These can be used
after being powered on.

15-10 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Para Para Parameter Description

met met
er er
ID Na
me

PI Boar This parameter is designed for the SBPI (providing the IP interface), EPII
d (providing the E1 interface), SEPU (providing the E1/T1 interface), SBPU/
prop SBPE, and CKII.
erty When configuring the IUA links on the SBPU/SBPE, this parameter defines
indic the type of the peer device. When the peer device is the MGC, this parameter
ator is set to 0; when the device is the IAD, this parameter is set to 1.
NOTE
The SBPU/SBPE supports up to eight IUA links to interconnect with the MGC and up
to 1250 IUA links to interconnect with the IAD.

Related Commands

Table 15-3 Related commands for adding the board

Command Function

ADD BRD To add the board

RMV BRD To remove the board

MOD BRD To modify the board

LST BRD To query the board

DSP BRD To query the information of board status

15.2.2 Adding Local IP Address

The local IP address table is the FE interface configuration table of the SCTP association.

Add local IP address before adding the SBPU/SBPE in the hardware data configuration. See
chapter 2 Configuring Hardware Data.

15.2.3 Adding Local IP Address Combination

This section describes the command, parameter, and related commands for adding the local IP
address combination.

For details, see chapter 11 Configuring M3UA Data.

15.2.4 Adding Extended Remote IP Address

The parameter of the command for adding an extended remote IP address has only one IP address.
When the SG7000 is interconnected with the softswitch, this parameter defines the IP address

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 15-11

of an interface board on the softswitch. When a record is added, the system allocates an idle
index for this record.

Command
ADD EXRIP

Parameter
Paramete Paramete Parameter Description
r ID r Name

RIP Extended Input format: 10.11.2.200.

remote IP It must be configured under the negotiation with the peer side.
address

Related Commands

Table 15-4 Related commands for configuring the local IP address combination

Command Function

ADD EXRIP To add the extended remote IP address

RMV EXRIP To remove the extended remote IP address

MOD EXRIP To modify the extended remote IP address

LST EXRIP To query the extended remote IP address

15.2.5 Adding Extended Remote IP Address Combination

The extended remote IP address combination table can hold up to 100,000 extended remote IP
address indexes. When a record is added, the system allocates an idle index for this record.

Command
ADD EXRIPC

Parameter
Paramete Paramete Parameter Description
r ID r Name

RIPX1-16 Extended These are indices of the extended remote IP addresses that are
remote IP already defined. When adding the extended remote IP address
address combination, query these indices with the command LST
index 1-16 EXRIP.

15-12 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Related Commands

Table 15-5 Related commands for configuring the extended remote IP address combination
Command Function

ADD EXRIPC To add the extended remote IP address combination table

RMV EXRIPC To remove the extended remote IP address combination table

MOD EXRIPC To modify the extended remote IP address combination table

LST EXRIPC To query the extended remote IP address combination table

15.2.6 Adding the Extended Access Control Information

With this function, the SG7000 checks whether the access of the IP address of remote equipment
is illegal.

Command
ADD EXIPDACL

Parameter
Paramete Paramete Parameter Description
r ID r Name

IP Extended The remote IP address, which is allowed to access the SG7000 is

IP address set here. If there are multiple remote IP addresses, they must be
added in the IPDACL table here.

Related Commands

Table 15-6 Related commands for configuring the extended access control information
Command Function

ADD EXIPDACL To add the extended access control information

RMV EXIPDACL To remove the extended access control information

MOD EXIPDACL To modify the extended access control information

LST EXIPDACL To query the extended access control information

15.2.7 Setting Software Configuration Parameter

This command is used to set the software configuration parameter. In the initial state, the values
of MAX numbers of IUA linkset, MAX numbers of IUA link, and MAX users of IAD are

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 15-13

0, which indicates that the IUA is not enabled. You can continue to configure the IUA data only
after you set the values for the three parameters based on actual conditions.

Command
SET SOFTCFG

Parameter
Paramete Paramete Parameter Description
r ID r Name

MAXLN Max It specifies the maximum number of IUA link sets. Its value ranges
KS numbers 256-80000.
of IUA
linkset

MAXLN Max It specifies the maximum number of IUA links. Its value ranges
K numbers 0-100000.
of IUA
link

MXUSER Max users It specifies the maximum number of users of the IAD. Its value
of IAD ranges 0-8.

Related Commands

Table 15-7 Related commands for adding the IUA link set

Command Function

SET SOFTCFG To set the software configuration parameter

LST SOFTCFG To query the software configuration parameter

15.2.8 Converting Formats

This command is used to convert the format of the data in the BAM database to binary file which
can be identified by the host. Thus the data can be loaded to the host. The host data load file
converted is stored under the directory D:\SGDATA on the BAM hard disk, with the file name
format of db_?.dat by default.

After setting the data offline, you must format all the data with the command FMT and load the
data to the corresponding board in the host.

Command
FMT

15-14 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Parameter
None.

Related Commands
None.

15.2.9 Setting Board Software DIP Switch

This section describes the command, parameter, and related commands for setting the board
software DIP switches.

Command
SET SFTSWT

Parameter
Paramete Paramete Parameter Description
r ID r Name

MODE Set mode It specifies whether a board or all boards is set. Set ALL (All
boards) for this parameter.

SHN Shelf When ONE (Specified board) is set for the Set mode, the three
number parameters specify the location of the board.

FN Frame
number

SN Slot
number

LOC Location When ONE (Specified board) is set for the Set mode, you can set
FPB, UDB, DDB, and BPB for this parameter.

VAL DIP This parameter is used when you start a board. There are six
switch options: 0 (Not to load data and program), 64 (Load data and save),
value 128 (Load program), 160 (Load program and save), 192 (Load both
program and data, but save data only) and 224 (Load & save both
program and data). For IUA configuration, select 224 (Load & save
both program and data).

Related Commands
None.

15.2.10 Adding IUA Link Set

When a record is added in the IUA link set table, an idle index value will be allocated for the
record.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 15-15

Command
ADD IUALKS

Parameter
Paramete Paramete Parameter Description
r ID r Name

TRAFMO Traffic It identifies the traffic mode of the IUA links in the IUA link set.
DE mode The two ends of the interconnected link sets must be in the same
transmission mode; otherwise, the IUA link cannot work normally.
It is recommended to use the load sharing mode. The two options
of the traffic mode are as follows:
l OVERRIDE (Over-ride mode): It is the N+1 backup mode. In
this mode, only one IUA link in the link set is active, and the
others are in the standby state. When the active link is faulty, a
standby link will be activated and begin to transmit the traffic.
l LOADSHARE (Load-share mode): All links in the IUA link set
are active. The traffic transmitted over this IUA link set is shared
by all the links in the set.

IADIDX IAD index It identifies the IAD connected with the IUA link set. This index
can uniquely identify an IAD.

MGCIDX MGC It uniquely identifies an IUA link set connected with the MGC.
linkset The traffic borne by the newly added IUA link set is transferred to
index this IUA link set.
NOTE
The IUA link sets added with this command are all connected to the IAD.

Related Commands

Table 15-8 Related commands for adding the IUA link set

Command Function

ADD IUALKS Adding IUA link set

RMV IUALKS To delete IUA link set

MOD IUALKS To modify IUA link set

LST IUALKS To query IUA link set

15.2.11 Adding IUA link

When a record is added in the IUA link table, an idle index value will be allocated for the record.

15-16 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Command
ADD IUALNK

Parameter
Paramete Paramete Parameter Description
r ID r Name

SHN Shelf These are the numbers of the shelf, frame, or slot, where the
number SBPU/SBPE board bearing the IUA link is located.

FN Frame
number

SN Slot
number

PLNO Board It is the index number of the link on the board. One SBPU/SBPE
assoc. can support up to 1250 IUA links. You can select an unused link
number number here.

LIPCX Local IP It identifies the local IP address combination index to which the
combinati SCTP association bearing this IUA link is bound. The local IP
on index address combination must be configured in the command ADD
LIPC. The index value here is allocated by the system after
running the command ADD LIPC.

LP Local port It is the local port number of the SCTP association that carries the
IUA link.
NOTE
When M2UA, M3UA, IUA, and M2PA are all based on the SCTP
transmission, it is recommended to define the range of the local SCTP port
number of each protocol link before configuring the data. Do not use the
same port number again.

RIPCX Remote IP It identifies the remote IP combination index to which the SCTP
combinati association bearing this IUA link is bound. If the softswtich
on index supports the multi-home feature of the SCTP association, the
remote IP address combination can be configured to improve the
reliability of the networking.
The remote IP combination must be configured in the command
ADD EXRIPC. The index value here is allocated by the system
after running the command ADD EXRIPC.

RP Remote It is the remote port number of the SCTP association over which
port the IUA link is borne. The parameter requires to be configured after
negotiating with the softswitch equipment.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 15-17

Paramete Paramete Parameter Description

r ID r Name

CS C/S mode It identifies in which mode the local end of the SCTP association
bearing this IUA link works. There are two options as follows:
l C (Client side): The local SCTP association is a client.
l S (Server side): The local SCTP association is a server.
This parameter is used when setting the SG7000 to act as a client
or a server under the condition of interworking with the softswitch.
Set a server at one end of the network and set a client at the other
end. Configure this parameter after negotiating with the peer end.

ASSI Associatio It identifies the IUA link set to which the IUA link belongs. The
n set index index value here is allocated by the system after running the
command ADD IUALKS.
If these IUA links are the links between the SG7000 and the MGC,
the indices of the link sets are from 0 to 255.
If these IUA links are the links between the SG7000 and the IAD,
the index values here are allocated by the system after running the
command ADD IUALKS.

ASF Active_sta It is used to configure whether this added link works in an active
ndby flag state or a standby state. Note that this field will be enabled if
OVERRIDE (Over-ride mode) is selected for the Traffic
mode in the command ADD IUALKS; otherwise, this field is
disabled.
l NO (Active initially): The new link is in the active state.
l YES (Standby initially): The new link is in the standby state.

PRI Priority It specifies the priority of the IUA links to be used within the same
IUA link set. The links with higher priorities will be selected first.
The links with lower priorities cannot carry the signaling traffic
until all the links with higher priorities become unavailable. The
value 0 stands for the highest priority and the value 1 stands for
the second highest priority.
Note that this field will be enabled if LOADSHARE (Load-share
mode) is selected for the Traffic mode in the ADD IUALKS
command; otherwise, this field is disabled.

MAXIS MAX. in It specifies the maximum number of incoming streams that the
streams SCTP association bearing this IUA link can support. It specifies
the maximum number of SCTP streams contained in each IUA
protocol message received by the SG7000. The default value 17 is
selected. After the SCTP association is created, the actual number
of incoming streams is coordinated by the two parties.

15-18 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Paramete Paramete Parameter Description

r ID r Name

MAXOS MAX. out It specifies the maximum number of outgoing streams that the
streams SCTP association bearing this IUA link can support. It specifies
the maximum number of SCTP streams contained in each IUA
protocol message sent by the SG7000. The default value 17 is
selected. After the SCTP association is created, the actual number
of outgoing streams is the result of negotiation between the two
parties.

COT Congestio This is the start threshold when congestion occurs to this IUA link.
n onset It specifies the threshold of the signaling load of the SG7000 on
threshold the IUA link, above which the congestion control is started. The
unit is "%".

CDT Congestio This is the threshold value to discard the congestion occurring to
n discard this IUA link. It specifies the threshold of the signaling load of the
threshold SG7000 on the IUA link, below which the congestion control is
discarded after the SG7000 starts the congestion control and
restricts the transmission signaling load of an IUA link. The unit
is "%". The IUA link can transmit the traffic again after the
congestion control is discarded.

Related Commands

Table 15-9 Related commands for adding the IUA link

Command Function

ADD IUALNK To add the IUA link

RMV IUALNK To delete the IUA link

MOD IUALNK To modify the IUA link

LST IUALNK To query the IUA link

15.3 Configuration Examples

This section provides examples to describe how to configure the IUA data.

Assumption
Figure 15-6 shows a network that requires the IUA data configuration.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 15-19

Figure 15-6 Networking of the IUA data configuration

The collected data is shown in Table 15-10.

Table 15-10 IUA data collection table

Local IP address Local port number Remote IP address

10.10.10.1/255.255.0.0 1025 IAD: 11.11.11.1/255.255.0.0

MGC: 12.12.12.1/255.255.0.0

Remote port number Maximum number of IUA Maximum number of IUA links
link sets

1025 10000 20000

Maximum users of C/S mode Traffic mode

IAD

8 SG to IAD: client Load sharing

SG to MGC: server

Procedure
Step 1 To add the local IP address 10.10.10.1/255.255.0.0, run the following command:
ADD LIP: LIP="10.10.10.1", MSK="255.255.0.0", DGW="10.10.1.1";

After running the command, the index 0 is returned.

Step 2 To add the front board SBPU in slot 3, service frame 1, and shelf 4, proceed as follows:
NOTE

This section takes the configuration on the SBPU for an example. The configuration on the SBPE is the same
as that on the SBPU.
1. Set Board property indicator to 1, indicating that the IUA on the local board is connected
with the IAD.
ADD BRD: FN=4, SHN=1, FT=MAIN, SN=3, LOC=FPB, BT=SBPU, PI=1;
2. To add the front board SBPU in slot 4, service frame 1, and shelf 4, set Board property
indicator to 0, indicating that the IUA on the local board is connected with the MGC.
ADD BRD: FN=4, SHN=1, FT=MAIN, SN=4, LOC=FPB, BT=SBPU, PI=0;

Step 3 To add the local IP address combination table, set FE index 1 to the IP address of the SBPU of
the local frame, the index number of the address to 0, and run the following command:

15-20 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

ADD LIPC: FEX1=0;

After running the command, the local IP address combination index 0 is returned.

Step 4 To add the IP address of the IAD, run the following command:
ADD EXRIP: RIP="11.11.11.1";

After running the command, the extended remote IP address index 0 is returned.

Step 5 To add the extended remote IP address combination table, set Remote IP address index 1 to
0, and run the following command:
ADD EXRIPC: RIPX1=0;

After running the command, the extended remote IP address combination index 0 is returned.

Step 6 To add the extended access control information, set Extended IP address to 11.11.11.1, and
run the following command:
ADD EXIPDACL: IP="11.11.11.1";

Step 7 To add the IP address of the MGC, run the following command:
ADD EXRIP: RIP="12.12.12.1";

After running the command, the extended remote IP address index 1 is returned.

Step 8 To add the extended remote IP address combination table, set Remote IP address index 2 to
1, and run the following command:
ADD EXRIPC: RIPX2=1;

After running the command, the extended remote IP address combination index 1 is returned.

Step 9 To add the extended access control information, set Extended IP address to 12.12.12.1, and
run the following command:
ADD EXIPDACL: IP="12.12.12.1";

Step 10 Initialize the IUA function.

To set the software configuration parameter, set MAX numbers of IUA linkset to 10000, MAX
numbers of IUA link to 20000, MAX users of IAD to 4, and run the following command:
SET SOFTCFG: MXLNKS=10000, MXLNK=20000, MXUSER=4;

Step 11 Convert the formats of all the data.

FMT:;

Step 12 Stop all the service processes on the BAM and then restart them.

To set the board software DIP switch, set Set mode to ALL, DIP switch value to 224, and run
the following command:
SET SFTSWT: MODE=ALL, VAL=224;

Step 13 Reset all boards to load the program and data.

To set the offline mode, set LN to LOFF.

SET OPMODE: LN=LOFF;

Step 14 To add the IUA link set, set Link Set title to To IAD, Traffic mode to LOADSHARE, IAD
index to 2, MGC linkset index to 1, and run the following command:
ADD IUALKS: SDESC="TO IAD", TRAFMODE=LOADSHARE, IADIDX=2, MGCIDX=1;

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 15-21

After running the command, the link set index 256 is returned.
Step 15 To add the IUA links, set Association title to To IAD, Shelf number to 4, Frame number to
1, Slot number to 3, Board assoc. number to 0, Local IP combination index to 0, Remote
IP combination index to 0, Local port to 1025, Remote port to 1025, C/S mode to Client
side, Association set index to 256, and use the default values for the other parameters. Now,
run the following command:
ADD IUALNK: SDESC="TO IAD", SHN=4, FN=1, SN=3, PLNO=0, LIPCX=0, LP=1025,
RIPCX=0, RP=1025, CS=C, ASSI=256;

Step 16 To add the IUA links, set Association title to To MGC, Shelf number to 4, Frame number
to 1, Slot number to 4, Board assoc. number to 1, Local IP combination index to 1, Remote
IP combination index to 1, Local port to 1025, Remote port to 1025, C/S mode to Server
side, Association set index to 1, and use the default values for the other parameters. Now, run
the following command:
ADD IUALNK: SDESC="TO MGC", SHN=4, FN=1, SN=4, PLNO=1, LIPCX=1, LP=1025,
RIPCX=1, RP=1025, CS=C, ASSI=1;

Step 17 Prepare for loading.

To set the online mode, set LN to LON.
SET OPMODE: LN=LON;

Step 18 To turn on the alarm switch, set ON/OFF to ON.

SET CWSON: SWT=ON;

Step 19 Convert the formats of all the data.

FMT:;

Step 20 Power off the board and then power it on.

----End

15-22 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

16 List of Data Configuration Commands

List of Equipment Management Commands

Category Function Command

Equipment Add the board ADD BRD

Management
Remove the board RMV BRD

Modify the board MOD BRD

Query the board LST BRD

TRUNK work Add TRUNK work status ADD TRUNKSTAT

status
Remove TRUNK work status RMV TRUNKSTAT

Modify TRUNK work status MOD TRUNKSTAT

List TRUNK work status LST TRUNKSTAT

CKII work Add CKII work status ADD CKISTAT

status
Remove CKII work status RMV CKISTAT

Modify CKII work status MOD CKISTAT

List CKII work status LST CKISTAT

List of MTP Management Commands

Category Function Command

MTP DSPS Add the MTP DSP ADD N7DSP

Remove the MTP DSP RMV N7DSP

Modify the MTP DSP MOD N7DSP

Query the MTP DSP LST N7DSP

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 16-1

Category Function Command

MTP link set Add the MTP link set ADD N7LKS

Remove the MTP link set RMV N7LKS

Modify the MTP link set MOD N7LKS

Query the MTP link set LST N7LKS

MTP route Add the MTP route ADD N7RT

Remove the MTP route RMV N7RT

Modify the MTP route MOD N7RT

Query the MTP route LST N7RT

MTP link Add the MTP link ADD N7LNK

Remove the MTP link RMV N7LNK

Modify the MTP link MOD N7LNK

Query the MTP link LST N7LNK

Routing area Add the routing area ADD N7RTB

Remove the routing area RMV N7RTB

Modify the routing area MOD N7RTB

Query the routing area LST N7RTB

Initial shielding Add the initial shielding ADD N7IM

Remove the initial shielding RMV N7IM

Modify the initial shielding MOD N7IM

Query the initial shielding LST N7IM

Link set Add the link set shielding ADD N7LSM

shielding
Remove the link set shielding RMV N7LSM

Modify the link set shielding MOD N7LSM

Query the link set shielding LST N7LSM

Prohibited OPC Add the prohibited OPC ADD N7DO

Remove the prohibited OPC RMV N7DO

Modify the prohibited OPC MOD N7DO

Query the prohibited OPC LST N7DO

Prohibited DPC Add the prohibited DPC ADD N7DD

Remove the prohibited DPC RMV N7DD

16-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Category Function Command

Modify the prohibited DPC MOD N7DD

Query the prohibited DPC LST N7DD

Allowed OPC Add the allowed OPC ADD N7EO

Remove the allowed OPC RMV N7EO

Modify the allowed OPC MOD N7EO

Query the allowed OPC LST N7EO

Allowed DPC Add the allowed DPC ADD N7ED

Remove the allowed DPC RMV N7ED

Modify the allowed DPC MOD N7ED

Query the allowed DPC LST N7ED

Prohibited SIO Add the prohibited SIO ADD N7SIO

Remove the prohibited SIO RMV N7SIO

Modify the prohibited SIO MOD N7SIO

Query the prohibited SIO LST N7SIO

Prohibited TFM Add the prohibited TFM ADD N7DTFM

Remove the prohibited TFM RMV N7DTFM

Modify the prohibited TFM MOD N7DTFM

Query the prohibited TFM LST N7DTFM

List of SCCP Management Commands

Category Function Command

SCCP Add the SCCP subsystem ADD SCCPSSN

subsystem
Remove the SCCP subsystem RMV SCCPSSN

Modify the SCCP subsystem MOD SCCPSSN

Query the SCCP subsystem LST SCCPSSN

GT Add the GT ADD SCCPGT

Remove the GT RMV SCCPGT

Modify the GT MOD SCCPGT

Query the GT table LST SCCPGT

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 16-3

Category Function Command

New GT Add the new GT ADD SCCPNGT

Remove the new GT RMV SCCPNGT

Modify the new GT MOD SCCPNGT

Query the new GT table LST SCCPNGT

SCCP calling Add the SCCP calling GT segment ADD SCCPCGGTSEG

GT segment
management Delete the SCCP calling GT segment RMV SCCPCGGTSEG

Modify the SCCP calling GT segment MOD SCCPCGGTSEG

Query the SCCP calling GT segment LST SCCPCGGTSEG

SCCP Add the SCCP addressing policy ADD SCCPADDRPL

addressing
policy Delete the SCCP addressing policy RMV SCCPADDRPL
management Modify the SCCP addressing policy MOD SCCPADDRPL

Query the SCCP addressing policy LST SCCPADDRPL

SCCP OPC Add the SCCP OPC load-share select ADD SCCPOPCLSS
load-share select set
set management
Delete the SCCP OPC load-share RMV SCCPOPCLSS
select set

Modify the SCCP OPC load-share MOD SCCPOPCLSS

select set

Query the SCCP OPC load-share LST SCCPOPCLSS

select set

SCCP calling Add the SCCP calling GT load-share ADD SCCPCGGTLSS

GT load-share select set
select set
management Delete the SCCP calling GT load- RMV SCCPCGGTLSS
share select set

Modify the SCCP calling GT load- MOD SCCPCGGTLSS

share select set

Query the SCCP calling GT load- LTS SCCPCGGTLSS

share select set

Caller DPCSSN Add the caller DPCSSN shielding ADD SCCPCDS

shielding
Remove the caller DPCSSN shielding RMV SCCPCDS

Modify the caller DPCSSN shielding MOD SCCPCDS

Query the caller DPCSSN shielding LST SCCPCDS

Caller GT Add the caller GT shielding ADD SCCPCGT

shielding

16-4 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Category Function Command

Remove the caller GT shielding RMV SCCPCGT

Modify the caller GT shielding MOD SCCPCGT

Query the caller GT shielding LST SCCPCGT

Caller GT type Add the caller GT type shielding ADD SCCPCGTT

shielding
Remove the caller GT type shielding RMV SCCPCGTT

Modify the caller GT type shielding MOD SCCPCGTT

Query the caller GT type shielding LST SCCPCGTT

Called DPCSSN Add the called DPCSSN shielding ADD SCCPDDS

shielding
Remove the called DPCSSN RMV SCCPDDS
shielding

Modify the called DPCSSN shielding MOD SCCPDDS

Query the called DPCSSN shielding LST SCCPDDS

Called GT Add the called GT shielding ADD SCCPDGT

shielding
Remove the called GT shielding RMV SCCPDGT

Modify the called GT shielding MOD SCCPDGT

Query the called GT shielding LST SCCPDGT

Called GT type Add the called GT type shielding ADD SCCPDGTT

shielding
Remove the called GT type shielding RMV SCCPDGTT

Modify the called GT type shielding MOD SCCPDGTT

Query the called GT type shielding LST SCCPDGTT

List of SCTP Management Commands

Category Function Command

SCTP Set the SCTP initialization parameter SET SCTPINIT

initialization
parameter Query the SCTP initialization LST SCTPINIT
parameter

SCTP protocol Set the SCTP protocol parameter SET SCTPPP

parameter
Query the SCTP protocol parameter LST SCTPPP

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 16-5

List of IPD Management Commands

Category Function Command

Access control Add the access control information ADD IPDACL

information
Remove the access control RMV IPDACL
information

Modify the access control MOD IPDACL

information

Query the access control information LST IPDACL

List of M3UA Management Commands

Category Function Command

Local IP address Add local IP address ADD LIP

Remove local IP address RMV LIP

Modify local IP address MOD LIP

List local IP address LST LIP

Remote IP Add remote IP address ADD RIP

address
Remove remote IP address RMV RIP

Modify remote IP address MOD RIP

List remote IP address LST RIP

Local IP address Add local IP address combination ADD LIPC

combination table
table
Remove local IP address combination RMV LIPC
table

Modify local IP address combination MOD LIPC

table

List local IP address combination LST LIPC

table

Remote IP Add remote IP address combination ADD RIPC

address table
combination
table Remove remote IP address RMV RIPC
combination table

Modify remote IP address MOD RIPC

combination table

List remote IP address combination LST RIPC

table

16-6 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Category Function Command

M3UA Add M3UA application server ADD M3AS

application
server Remove M3UA application server RMV M3AS

Modify M3UA application server MOD M3AS

List M3UA application server LST M3AS

M3UA Add M3UA application server ADD M3CR

application
server Remove M3UA application server RMV M3CR

Modify M3UA application server MOD M3CR

List M3UA application server LST M3CR

M3UA Add M3UA association set ADD M3ASSOS

association set
Remove M3UA association set RMV M3ASSOS

Modify M3UA association set MOD M3ASSOS

List M3UA association set LST M3ASSOS

M3UA route Add M3UA route ADD M3RT

Remove M3UA route RMV M3RT

Modify M3UA route MOD M3RT

List M3UA route LST M3RT

M3UA Add M3UA association set ADD M3ASSO

association set
Remove M3UA association set RMV M3ASSO

Modify M3UA association set MOD M3ASSO

List M3UA association set LST M3ASSO

List of M2UA Management Commands

Category Function Command

M2UA link set Add M2UA link set ADD M2UALKS

Delete M2UA link set RMV M2UALKS

Modify M2UA link set MOD M2UALKS

Query M2UA link set LST M2UALKS

M2UA link Add M2UA link ADD M2UALNK

Delete M2UA link RMV M2UALNK

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 16-7

Category Function Command

Modify M2UA link MOD M2UALNK

Query M2UA link LST M2UALNK

List of IUA Management Commands

Category Function Command

IUA association Add IUA association set ADD IUALKS

set
Delete IUA association set RMV IUALKS

Modify IUA association set MOD IUALKS

Query IUA association set LST IUALKS

IUA association Add IUA association ADD IUALNK

Delete IUA association RMV IUALNK

Modify IUA association MOD IUALNK

Query IUA association LST IUALNK

List of Commands for Configuring Called SMR Service Data

Category Function Command

Setting short Set the software configuration SET SOFTCFG

message routing parameter
number type
Query the software configuration LST SOFTCFG
parameter

MC local SMSC Add the MC local SMSC address ADD SMRVSMSC

address
management Modify the MC local SMSC address MOD SMRVSMSC

Remove the MC local SMSC address RMV SMRVSMSC

List the MC local SMSC address LST SMRVSMSC

SMSC address Add the new SMSC address mapping ADD SMRSMCMAP
mapping table table
management
Modify the new SMSC address MOD SMRSMCMAP
mapping table

Delete the new SMSC address RMV SMRSMCMAP

mapping table

16-8 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Category Function Command

Query the new SMSC address LST SMRSMCMAP

mapping table

SMSC GT Add the GT ADD SCCPGT

translation
Modify the GT MOD SCCPGT

Remove the GT RMV SCCPGT

Query the GT LST SCCPGT

List of Commands for Configuring Calling SMR Service Data

Category Function Command

SMS routing Set the software configuration SET SOFTCFG

number type parameter

Query the software configuration LST SOFTCFG

parameter

SMSC address Set the SMS configuration SET SMSICSOFTCG

Query the SMS intercept LST SMSICSOFTCG

configuration

SMSC mapping Add the new SMSC address mapping ADD SMRSMCMAP
table table

Modify the new SMSC address MOD SMRSMCMAP

mapping table

Delete the new SMSC address RMV SMRSMCMAP

mapping table

Query the new SMSC address LST SMRSMCMAP

mapping table

SMSC GT Add the GT ADD SCCPGT

translation
Modify the GT MOD SCCPGT

Remove the GT RMV SCCPGT

Query the GT LST SCCPGT

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 16-9

List of Commands for Configuring IMEI Catch Service Data

Category Function Command

Network Add the net information config table ADD NETINFO

information
configuration Modify the net information config MOD NETINFO
table table

Remove the net information config RMV NETINFO

table

Query the net information config LST NETINFO

table

SDUI board Add the board ADD BRD

configuration
Modify the board MOD BRD

Remove the board RMV BRD

Query the board LST BRD

IMEI Catch Set the IMEI catch configuration table SET IMEICFG
service software
parameter table Query the IMEI catch configuration LST IMEICFG
management table

Service user Add the service user data ADD SERUATTR

data
management Modify the service user data MOD SERUATTR

Remove the service user data RMV SERUATTR

List the service user data LST SERUATTR

List of Commands for Configuring MNP Service

Category Function Command

MNP software Set the MNP software configuration SET MNPSOFTCFG

parameter table parameter
management
Query the software configuration LST MNPSOFTCFG
parameter

HLR address Add the HLR address ADD MNPHLRADDR

management
Modify the HLR address MOD MNPHLRADDR

Remove the HLR address RMV MNPHLRADDR

Query the HLR address LST MNPHLRADDR

MNP routing Add the MNP route number ADD MNPROUTENUM

number
management Modify the MNP route number MOD MNPROUTENUM

16-10 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Category Function Command

Delete the MNP route number RMV MNPROUTENUM

Query the MNP route number LST MNPROUTENUM

MNP foreign Add the foreign number range ADD MNPFRGNRNG

number range
management Modify the foreign number range MOD MNPFRGNRNG

Delete the foreign number range RMV MNPFRGNRNG

Query the foreign number range LST MNPFRGNRNG

Service user Add the service user data ADD SERUATTR

data
management Modify the service user data MOD SERUATTR

Remove the service user data RMV SERUATTR

List the service user data LST SERUATTR

List of Commands for Configuring CRBT Service

Category Function Command

Virtual roaming Add the dummy ramble number ADD CRVMSRN

number
management Modify the dummy ramble number MOD CRVMSRN

Delete the dummy ramble number RMV CRVMSRN

Query the dummy ramble number LST CRVMSRN

CRBT software Set CRBT software parameter SET CRSOFTCFG

parameter
management Query CRBT software parameter LST CRSOFTCFG

Word crest Add the word crest analyse table ADD NUMPFX
analysis
management Modify the word crest analyse table MOD NUMPFX

Remove the word crest analyse table RMV NUMPFX

Query the word crest analyse table LST NUMPFX

Provincial Add the province VMSC range ADD CRVMSCRNG

VMSC number
range Modify the province VMSC range MOD CRVMSCRNG
management Remove the province VMSC range RMV CRVMSCRNG

Query the province VMSC range LST CRVMSCRNG

User number Add the user range ADD SERUSERNG

range
management Modify the user range MOD SERUSERNG

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 16-11

Category Function Command

Remove the user range RMV SERUSERNG

Query the user range LST SERUSERNG

CRBT user data Add the service user data ADD SERUATTR
management
Modify the service user data MOD SERUATTR

Remove the service user data RMV SERUATTR

List the service user data LST SERUATTR

CRBT GT Add the RBT GT number range ADD SERGTNUMRNG

number range
shielding Modify the RBT GT number range MOD SERGTNUMRNG
management Delete the RBT GT number range RMV SERGTNUMRNG

Query the RBT GT number range LST SERGTNUMRNG

CRBT user Add the RBT user number range ADD SERUSRNUMRNG
number range
shielding Modify the RBT user number range MOD SSERUSRNUMRNG
management Delete the RBT user number range RMV SERUSRNUMRNG

Query the RBT user number range LST SERUSRNUMRNG

List of Commands for Configuring B&W Lists and Number Change Service Data
Category Function Command

MTP link set Add the MTP link set ADD N7LKS
management
Modify the MTP link set MOD N7LKS

Remove the MTP link set RMV N7LKS

Query the MTP link set LST N7LKS

Local number Add the operator number range table ADD LNUMRNG
range table
management Modify the operator number range MOD LNUMRNG
table

Delete the operator number range RMV LNUMRNG

table

Query the operator number range LST LNUMRNG

table

Virtual number Add the dummy number table ADD ISUPDUMMYNUM

table
management Modify the dummy number table MOD ISUPDUMMYNUM

Delete the dummy number table RMV ISUPDUMMYNUM

16-12 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Category Function Command

Query the dummy number table LST ISUPDUMMYNUM

DSP index Add the DSP index reference ADD DSPIDXREF

reference
management Modify the DSP index reference MOD DSPIDXREF

Delete the DSP index reference RMV DSPIDXREF

Query the DSP index reference LST DSPIDXREF

Calling B&W Add the calling B&W list ADD CALLINGBW

lists
management Modify the calling B&W list MOD CALLINGBW

Remove the calling B&W list RMV CALLINGBW

List the calling B&W list LST CALLINGBW

Called B&W Add the called B&W list ADD CALLEDBW

lists
management Modify the called B&W list MOD CALLEDBW

Remove the called B&W list RMV CALLEDBW

List the called B&W list LST CALLEDBW

Number Add the number operation ADD NUMOPER

operation policy
management Modify the number operation MOD NUMOPER

Remove the number operation RMV NUMOPER

List the number operation LST NUMOPER

Calling number Add the calling number trans ADD CALLINGTN

change
management Modify the calling number trans MOD CALLINGTN

Remove the calling number trans RMV CALLINGTN

List the calling number trans LST CALLINGTN

Called number Add the called number trans ADD CALLEDTN

change
management Modify the called number trans MOD CALLEDTN

Remove the called number trans RMV CALLEDTN

List the called number trans LST CALLEDTN

CPC Add the CPC ADD CPC

management
Modify the CPC MOD CPC

Delete the CPC RMV CPC

Query the CPC LST CPC

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 16-13

List of Commands for Configuring Protocol Translation Service Data

Category Function Command

MTP SPC Add the mtp pc convert ADD N7PCCVT

conversion
management Modify the mtp pc convert MOD N7PCCVT

Remove the mtp pc convert RMV N7PCCVT

Query the mtp pc convert LST N7PCCVT

MTP protocol Add the mtp protocol change dsp set ADD N7PRTTRSDSP
conversion DSP
set management Modify the mtp protocol change dsp MOD N7PRTTRSDSP
set

Remove the mtp protocol change dsp RMV N7PRTTRSDSP

set

Query the mtp protocol change dsp set LST N7PRTTRSDSP

List of Commands for Configuring Firewall Service Data

Category Function Command

FIREWALL Set the FIREWALL software SET FWSOFTCFG

software configuration parameter
parameter
management Query the FIREWALL software LST FWSOFTCFG
configuration parameter

MAP contents Add the FW MAP content masking ADD FWMAPCNBLK

screening
management Modify the FW MAP content MOD FWMAPCNBLK
masking

Delete the FW MAP content masking RMV FWMAPCNBLK

Query the FW MAP content masking LST FWMAPCNBLK

Operation code Add the FW operation code set ADD FWOPCODE

set management
Modify the FW operation code set MOD FWOPCODE

Delete the FW operation code set RMV FWOPCODE

Query the FW operation code set LST FWOPCODE

Subsystem set Add the FW subsystem set ADD FWSSN

management
Modify the FW subsystem set MOD FWSSN

Delete the FW subsystem set RMV FWSSN

Query the FW subsystem set LST FWSSN

16-14 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Category Function Command

MAP operation Add the FW MAP operation code ADD FWMAPCODEBLK

code masking masking
management
Modify the FW MAP operation code MOD FWMAPCODEBLK
masking

Delete the FW MAP operation code RMV FWMAPCODEBLK

masking

Query the FW MAP operation code LST FWMAPCODEBLK

masking

Called GT Add the FW called GT masking ADD FWCDGTBLK

masking
management Modify the FW called GT masking MOD FWCDGTBLK

Delete the FW called GT masking RMV FWCDGTBLK

Query the FW called GT masking LST FWCDGTBLK

Calling GT Add the FW calling GT masking ADD FWCGGTBLK

masking
management Modify the FW calling GT masking MOD FWCGGTBLK

Delete the FW calling GT masking RMV FWCGGTBLK

Query the FW calling GT masking LST FWCGGTBLK

DPC masking Add the FW DPC masking ADD FWDPCBLK

management
Modify the FW DPC masking MOD FWDPCBLK

Delete the FW DPC masking RMV FWDPCBLK

Query the FW DPC masking LST FWDPCBLK

OPC masking Add the FW OPC masking ADD FWOPCBLK

management
Modify the FW OPC masking MOD FWOPCBLK

Delete the FW OPC masking RMV FWOPCBLK

Query the FW OPC masking LST FWOPCBLK

Link set public Add the FW link set public default ADD FWDEFSHR
default masking masking
management
Modify the FW link set public default MOD FWDEFSHR
masking

Delete the FW link set public default RMV FWDEFSHR

masking

Query the FW link set public default LST FWDEFSHR

masking

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 16-15

Category Function Command

Link set public Add the FW link set public masking ADD FWSHR
masking
management Modify the FW link set public MOD FWSHR
masking

Delete the FW link set public masking RMV FWSHR

Query the FW link set public masking LST FWSHR

Initial masking Add the FW initial masking ADD FWIM

management
Modify the FW initial masking MOD FWIM

Delete the FW initial masking RMV FWIM

Query the FW initial masking LST FWIM

MTP link set Add the MTP link set ADD N7LKS
management
Modify the MTP link set MOD N7LKS

Remove the MTP link set RMV N7LKS

Query the MTP link set LST N7LKS

Firewall Test the process result of users input TST FWMSG

maintenance
and test data
management

FW alarm Add the FW alarm configuration ADD FWALMCFG

configuration
table Modify the FW alarm configuration MOD FWALMCFG
management Delete the FW alarm configuration RMV FWALMCFG

Query the FW alarm configuration LST FWALMCFG

FW statistics Add the FW statistics configuration ADD FWSTATCFG

configuration
management Modify the FW statistics MOD FWSTATCFG
configuration

Delete the FW statistics configuration RMV FWSTATCFG

Query the FW statistics configuration LST FWSTATCFG

FW SMSC Add the SMSC address stat ADD FWSMSCAC

address statistics configuration
management
Modify the SMSC address stat MOD FWSMSCAC
configuration

Delete the SMSC address stat RMV FWSMSCAC

configuration

Query the SMSC address stat LST FWSMSCAC

configuration

16-16 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Category Function Command

SMSC statistics Query the SMSC address statistics LST TRFSMSCDATA

management data

Permanent Query the permanent statistics data DSP TRFPERMDATA

statistics data
management

List of Commands for Configuring MC Service Data

Category Function Command

MC software Set the SMS configuration SET SMSICSOFTCFG

parameter
management Query the SMS configuration LST SMSICSOFTCFG

MC routing Add the MC routing number ADD MCROUTE

number
management Modify the MC routing number MOD MCROUTE

Delete the MC routing number RMV MCROUTE

Query the MC routing number LST MCROUTE

Local network Add the MC local SMSC address ADD MCSMSCADDR

SMSC address
management Modify the MC local SMSC address MOD MCSMSCADDR

Delete the MC local SMSC address RMV MCSMSCADDR

Query the MC local SMSC address LST MCSMSCADDR

User attribute Add the service user data ADD SERUATTR

table
management Modify the service user data MOD SERUATTR

Remove the service user data RMV SERUATTR

List the service user data LST SERUATTR

User sub Add the sub msisdn ADD SUBUSR

MSISDN
management Modify the sub msisdn MOD SUBUSR

Remove the sub msisdn RMV SUBUSR

Query the sub msisdn LST SUBUSR

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 16-17

List of Commands for Configuring FNR Service Data - General

Category Function Command

HLR address Add the HLR address ADD MNPHLRADDR

management
Modify the HLR address MOD MNPHLRADDR

Remove the HLR address RMV MNPHLRADDR

Query the HLR address LST MNPHLRADDR

MNP software Set the MNP software configuration SET MNPSOFTCFG

parameter parameter
management
Query the MNP software LST MNPSOFTCFG
configuration parameter

MNP routing Add the MNP route number ADD MNPROUTENUM

number
management Modify the MNP route number MOD MNPROUTENUM

Remove the MNP route number RMV MNPROUTENUM

Query the MNP route number LST MNPROUTENUM

User attribute Add the service user data ADD SERUATTR

table
management Modify the service user data MOD SERUATTR

Remove the service user data RMV SERUATTR

List the service user data LST SERUATTR

List of Commands for Configuring FNR Service Data - Specific

Category Function Command

HLR address Add the HLR address ADD MNPHLRADDR

management
Modify the HLR address MOD MNPHLRADDR

Remove the HLR address RMV MNPHLRADDR

Query the HLR address LST MNPHLRADDR

MNP software Set the MNP software configuration SET MNPSOFTCFG

parameter parameter
management
Query the MNP software LST MNPSOFTCFG
configuration parameter

MNP routing Add the MNP route number ADD MNPROUTENUM

number
management Modify the MNP route number MOD MNPROUTENUM

Remove the MNP route number RMV MNPROUTENUM

16-18 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Category Function Command

Query the MNP route number LST MNPROUTENUM

User attribute Add the service user data ADD SERUATTR

table
management Modify the service user data MOD SERUATTR

Remove the service user data RMV SERUATTR

List the service user data LST SERUATTR

User sub Add the sub msisdn ADD SUBUSR

MSISDN
management Modify the sub msisdn MOD SUBUSR

Remove the sub msisdn RMV SUBUSR

Query the sub msisdn LST SUBUSR

List of Commands for Configuring SMI Service Data

Category Function Command

SMI software Set the SMS configuration SET SMSICSOFTCFG

parameter
management Query the SMS configuration LST SMSICSOFTCFG

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 16-19

SG7000 Configuration Examples (V200R005C02 - 02)
No ratings yet
SG7000 Configuration Examples (V200R005C02 - 02)
73 pages
HUAWEI CG9812 V300R001 Product Description
0% (2)
HUAWEI CG9812 V300R001 Product Description
26 pages
Nokia Core Kpi
No ratings yet
Nokia Core Kpi
1 page
Azure Virtual Machines
100% (1)
Azure Virtual Machines
1 page
SG7000 V200R005 Function Descriptions
100% (1)
SG7000 V200R005 Function Descriptions
37 pages
CloudCore Feature List 20180628
No ratings yet
CloudCore Feature List 20180628
13 pages
OEB9B1131 USN9810 (MME&SGSN) System Overview ISSUE1
No ratings yet
OEB9B1131 USN9810 (MME&SGSN) System Overview ISSUE1
63 pages
HLR9820 COMMON Feature Description
No ratings yet
HLR9820 COMMON Feature Description
56 pages
Huawei GPRS Core Network Solution
67% (3)
Huawei GPRS Core Network Solution
70 pages
A&S Public-Basic Training On SS7 Signaling Fundamentals V1.5
No ratings yet
A&S Public-Basic Training On SS7 Signaling Fundamentals V1.5
72 pages
OEB9B0512 MME POOL Principle ISSUE 1.20 (Duxiaoqin 20140724)
No ratings yet
OEB9B0512 MME POOL Principle ISSUE 1.20 (Duxiaoqin 20140724)
33 pages
Huawei - Configuring Signaling Transport Data
No ratings yet
Huawei - Configuring Signaling Transport Data
100 pages
Test UGW
No ratings yet
Test UGW
533 pages
Full-Guide February 2019 FV Final
No ratings yet
Full-Guide February 2019 FV Final
58 pages
Oeb9b0511 Mme Pool Solution Issue 1.20 (Duxiaoqin 20140724)
No ratings yet
Oeb9b0511 Mme Pool Solution Issue 1.20 (Duxiaoqin 20140724)
24 pages
5-UMG8900 Exercise Guide For V3R3-Centralized Mode
No ratings yet
5-UMG8900 Exercise Guide For V3R3-Centralized Mode
12 pages
CS10.0 Introduction To MSOFTX3000 V200R010C00
No ratings yet
CS10.0 Introduction To MSOFTX3000 V200R010C00
28 pages
(Basic Training) HSS9820 Data Configuration ISSUE3.30
No ratings yet
(Basic Training) HSS9820 Data Configuration ISSUE3.30
76 pages
Number Analysis
No ratings yet
Number Analysis
11 pages
Technical Manual TELLIN-USAU Universal Signaling Access Unit
No ratings yet
Technical Manual TELLIN-USAU Universal Signaling Access Unit
86 pages
1 OAS025101 SG7000 System Overview ISSUE1.00
No ratings yet
1 OAS025101 SG7000 System Overview ISSUE1.00
54 pages
OWB9A2501 SGSN Pool Solution Issue 1.20
No ratings yet
OWB9A2501 SGSN Pool Solution Issue 1.20
32 pages
Alarm Core CS Nokia w46
No ratings yet
Alarm Core CS Nokia w46
19 pages
BSC6900V900R012 UO Global and Equipment Data Configuration-20101218-B-V1.0
No ratings yet
BSC6900V900R012 UO Global and Equipment Data Configuration-20101218-B-V1.0
50 pages
1 MSOFTX3000 ATCA Hardware System PDF
100% (2)
1 MSOFTX3000 ATCA Hardware System PDF
53 pages
OWH007101 UMG8900 System Overview ISSUE 2.0
No ratings yet
OWH007101 UMG8900 System Overview ISSUE 2.0
67 pages
PDP Context Activation Guide
No ratings yet
PDP Context Activation Guide
124 pages
E8000E Series Firewall Hardware PDF
100% (1)
E8000E Series Firewall Hardware PDF
39 pages
ZXIN10 SACP IMP Platform Installation Guide
No ratings yet
ZXIN10 SACP IMP Platform Installation Guide
55 pages
MSC Pool
No ratings yet
MSC Pool
5 pages
Link Configuration of MSoftX3000
No ratings yet
Link Configuration of MSoftX3000
7 pages
PCRF Information: UPCC Service Analysis
No ratings yet
PCRF Information: UPCC Service Analysis
7 pages
SCP Service Control Point 032010 en
No ratings yet
SCP Service Control Point 032010 en
4 pages
2015CustomerTrainingCatalog CourseDescriptions (CN USC)
No ratings yet
2015CustomerTrainingCatalog CourseDescriptions (CN USC)
56 pages
To Create M3UA Signalling in An Existing Office: 1. Login MGW Netnumen, and Open MML Terminal From The Views Tab
No ratings yet
To Create M3UA Signalling in An Existing Office: 1. Login MGW Netnumen, and Open MML Terminal From The Views Tab
11 pages
MSOFTX3000 BICC Data Configuration 20090227 B 1 0
No ratings yet
MSOFTX3000 BICC Data Configuration 20090227 B 1 0
52 pages
Sps 7.2 Oas053201 Sps v3 (Dra) Data Configuration Issue 3.00
No ratings yet
Sps 7.2 Oas053201 Sps v3 (Dra) Data Configuration Issue 3.00
155 pages
OAX000200 SoftX3000 Data Configuration For h.323 Sip Terminal ISSUE2.0-20041018-A
No ratings yet
OAX000200 SoftX3000 Data Configuration For h.323 Sip Terminal ISSUE2.0-20041018-A
21 pages
PS Core
No ratings yet
PS Core
23 pages
¡ New Features of SoftX3000 V300R601C05¡¿AGCF Feature
No ratings yet
¡ New Features of SoftX3000 V300R601C05¡¿AGCF Feature
58 pages
M3UA Message Classes and Types:: Management (MGMT) Messages Transfer Messages
No ratings yet
M3UA Message Classes and Types:: Management (MGMT) Messages Transfer Messages
8 pages
VAS
No ratings yet
VAS
50 pages
U-SYS UMG8900 Universal Media Gateway
No ratings yet
U-SYS UMG8900 Universal Media Gateway
15 pages
Huawei CS9 2 HD Voice 2G Validation Report V1 2
No ratings yet
Huawei CS9 2 HD Voice 2G Validation Report V1 2
35 pages
GSM Inter MSC Handover Subscriber MSC Interactions
No ratings yet
GSM Inter MSC Handover Subscriber MSC Interactions
1 page
NGN Fault Analysis SoftX3000
100% (2)
NGN Fault Analysis SoftX3000
73 pages
¡ IMS 8.2¡¿SPG2800 Version Differences (Between R3C02 and R3C01)
No ratings yet
¡ IMS 8.2¡¿SPG2800 Version Differences (Between R3C02 and R3C01)
23 pages
Assignment Procedure in GSM Call Flow
No ratings yet
Assignment Procedure in GSM Call Flow
5 pages
High Risk Command List
No ratings yet
High Risk Command List
93 pages
BSS Feature Configuration Guide (Based On MML) (V900R008C12 - 01)
No ratings yet
BSS Feature Configuration Guide (Based On MML) (V900R008C12 - 01)
438 pages
Gi and SGi Interfaces
No ratings yet
Gi and SGi Interfaces
4 pages
1 Huawei Core MSC HLR MGW Training - Sample Training
No ratings yet
1 Huawei Core MSC HLR MGW Training - Sample Training
55 pages
Configuration Guide (V100R007 02, NGN)
No ratings yet
Configuration Guide (V100R007 02, NGN)
382 pages
EPC Dimensioning Tool
No ratings yet
EPC Dimensioning Tool
13 pages
ZTE ZXG10 MSC - VLR Technical-Overview
No ratings yet
ZTE ZXG10 MSC - VLR Technical-Overview
62 pages
BICC Vs SIP
100% (1)
BICC Vs SIP
8 pages
Network Capacity
No ratings yet
Network Capacity
104 pages
Diameter Protocol A Complete Guide
From Everand
Diameter Protocol A Complete Guide
Gerardus Blokdyk
No ratings yet
Voice over LTE Standard Requirements
From Everand
Voice over LTE Standard Requirements
Gerardus Blokdyk
3/5 (1)
IP Multimedia Subsystem IMS A Complete Guide
From Everand
IP Multimedia Subsystem IMS A Complete Guide
Gerardus Blokdyk
No ratings yet
Drive testing The Ultimate Step-By-Step Guide
From Everand
Drive testing The Ultimate Step-By-Step Guide
Gerardus Blokdyk
No ratings yet
Commissioning Guide - (V200R008C02 01, NGN)
No ratings yet
Commissioning Guide - (V200R008C02 01, NGN)
148 pages
Feature Description - (V200R008C02 01, NGN)
No ratings yet
Feature Description - (V200R008C02 01, NGN)
432 pages
00-2 About This Document
No ratings yet
00-2 About This Document
10 pages
01-2 Installation Guide
No ratings yet
01-2 Installation Guide
335 pages
Huawei Igwb User Manual
No ratings yet
Huawei Igwb User Manual
68 pages
User Manual: Huawei Igwb
No ratings yet
User Manual: Huawei Igwb
3 pages
SG7000 Hardware Description (V200R005C02 - 02)
No ratings yet
SG7000 Hardware Description (V200R005C02 - 02)
185 pages
02 Part
No ratings yet
02 Part
4 pages
User Manual: Part 1 Product Description Part 2 Installation Guide Part 3 Configuration Guide Part 4 Routine Maintenance
No ratings yet
User Manual: Part 1 Product Description Part 2 Installation Guide Part 3 Configuration Guide Part 4 Routine Maintenance
2 pages
0D50
No ratings yet
0D50
1 page
Feature History For SIP Tel URI Support
No ratings yet
Feature History For SIP Tel URI Support
4 pages
RCC Create Circuit Group: Function
No ratings yet
RCC Create Circuit Group: Function
11 pages
Data Privacy Contact Form: Republic of The Philippines City of Mandaluyong
100% (1)
Data Privacy Contact Form: Republic of The Philippines City of Mandaluyong
1 page
290L ECONAVI INVERTER Bottom Freezer Black 2-Door Refrigerator NR-BV320GKPH
No ratings yet
290L ECONAVI INVERTER Bottom Freezer Black 2-Door Refrigerator NR-BV320GKPH
1 page
MandaVax Opt-Out
100% (3)
MandaVax Opt-Out
1 page
Acer Swift User Manual
No ratings yet
Acer Swift User Manual
75 pages
18Y10-B-300 T1 18Y10-A-300 T1: Software Consultants (Pty) LTD
No ratings yet
18Y10-B-300 T1 18Y10-A-300 T1: Software Consultants (Pty) LTD
1 page
Cookbook - IBM AI + Sust
No ratings yet
Cookbook - IBM AI + Sust
28 pages
5991 3719en
No ratings yet
5991 3719en
8 pages
Mis-0114 Ds Agile Studio 2.8 Release Notes v280 r0
No ratings yet
Mis-0114 Ds Agile Studio 2.8 Release Notes v280 r0
6 pages
Ei-SMART Sewing System
No ratings yet
Ei-SMART Sewing System
22 pages
Windows Shotcut Keys
No ratings yet
Windows Shotcut Keys
15 pages
Microsoft SC-200 - QuestionsPrt2
No ratings yet
Microsoft SC-200 - QuestionsPrt2
252 pages
The Processor: CPU Performance Factors
No ratings yet
The Processor: CPU Performance Factors
66 pages
Basic Fundamentals of Computer
No ratings yet
Basic Fundamentals of Computer
5 pages
JAXB
100% (1)
JAXB
48 pages
Ultimate
No ratings yet
Ultimate
19 pages
C# Tutorial
50% (2)
C# Tutorial
5 pages
Ibs 1000
No ratings yet
Ibs 1000
2 pages
RomCmdOutput TimeOut
No ratings yet
RomCmdOutput TimeOut
25 pages
Java Intro
100% (1)
Java Intro
11 pages
CMG Numerical Methods
No ratings yet
CMG Numerical Methods
4 pages
Full Stack Engineer - Pareto - Ai
No ratings yet
Full Stack Engineer - Pareto - Ai
3 pages
Option - 1 Option - 2 Option - 3 Option - 4 Correct Answer Marks
No ratings yet
Option - 1 Option - 2 Option - 3 Option - 4 Correct Answer Marks
4 pages
Mounika Resume
No ratings yet
Mounika Resume
3 pages
MockTest 4 W
No ratings yet
MockTest 4 W
3 pages
Large Scale Font Independent Urdu Text Recognition System
No ratings yet
Large Scale Font Independent Urdu Text Recognition System
9 pages
Official Remix Flexi Extra Size Cat Print in Place Bfcf289a C48e 4543 966c 0eb7c0004ab1
No ratings yet
Official Remix Flexi Extra Size Cat Print in Place Bfcf289a C48e 4543 966c 0eb7c0004ab1
4 pages
Recipes With S7-1200
No ratings yet
Recipes With S7-1200
47 pages
Viva Questions & Answers - GXEST204 (Programming in C Lab)
No ratings yet
Viva Questions & Answers - GXEST204 (Programming in C Lab)
4 pages
ECSWI269ver020 Online Proctored Exams Candidate GuidelinesmacOs
No ratings yet
ECSWI269ver020 Online Proctored Exams Candidate GuidelinesmacOs
14 pages
Microsoft Innovation Centers: Local Software Economy Case Study
No ratings yet
Microsoft Innovation Centers: Local Software Economy Case Study
3 pages
Unit 5 - Software Defined Network
No ratings yet
Unit 5 - Software Defined Network
6 pages
Unit 1 - Creating GUI
No ratings yet
Unit 1 - Creating GUI
25 pages