HLR9820-Configuration Guide(V900R003C02 04,Db2)

HUAWEI HLR9820 Home Location Register V900R003C02

Configuration Guide

Issue

04

Date

2009-01-15

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any assistance, please contact our local office or company headquarters.

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]

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 the property of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice 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 the statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.


HUAWEI HLR9820 Home Location Register Configuration Guide

Contents

Contents About This Document.....................................................................................................................1 1 Overview of Data Configuration............................................................................................1-1 1.1 Data Configuration Process.............................................................................................................................1-2 1.2 Introduction to MML Commands...................................................................................................................1-2 1.2.1 Meanings of Common MML Commands..............................................................................................1-2 1.2.2 Rules for Setting MML Command Parameters......................................................................................1-3 1.2.3 Data Setting Procedures.........................................................................................................................1-4 1.3 Precautions for Data Configuration.................................................................................................................1-6 1.3.1 Impact of the Maximum Number of Tuples on Data Configuration......................................................1-6 1.3.2 Impact of Value Ranges of Software Parameters on Data Configuration..............................................1-7 1.3.3 Impact of Software Parameters on Data Configuration.........................................................................1-8 1.3.4 Impact of Board Restarting on Data Configuration...............................................................................1-8

2 Hardware Data Configuration.................................................................................................2-1 2.1 Basic Concepts................................................................................................................................................2-2 2.1.1 Rack Number..........................................................................................................................................2-2 2.1.2 Subrack Number.....................................................................................................................................2-2 2.1.3 Slot Number...........................................................................................................................................2-4 2.1.4 Module Number.....................................................................................................................................2-6 2.1.5 Cluster....................................................................................................................................................2-6 2.1.6 Node.......................................................................................................................................................2-6 2.2 Data Configuration Flow Chart.......................................................................................................................2-7 2.3 Hardware Data Table Relation........................................................................................................................2-9 2.4 Data Configuration Procedure.......................................................................................................................2-11 2.4.1 Adding a Rack......................................................................................................................................2-12 2.4.2 Adding an OSTA 1.0 Subrack..............................................................................................................2-12 2.4.3 Setting the OSTA 1.0 Board Type.......................................................................................................2-12 2.4.4 Adding an OSTA 1.0 Board.................................................................................................................2-12 2.4.5 Configuring the Hardware Data in TDM Networking.........................................................................2-12 2.4.6 Configuring the Hardware Data in IP Networking..............................................................................2-13 2.4.7 Configuring the Hardware Data in ATM-2M Networking..................................................................2-13 2.4.8 Adding an OSTA 2.0 Subrack..............................................................................................................2-13 2.4.9 Adding an OSTA 2.0 Board.................................................................................................................2-13 Issue 04 (2009-01-15)


i

Contents

HUAWEI HLR9820 Home Location Register Configuration Guide 2.4.10 Setting the Local Office Information.................................................................................................2-13 2.4.11 Adding the Cluster Configuration......................................................................................................2-13 2.4.12 Adding the Node Configuration.........................................................................................................2-14 2.4.13 Setting the HDU Configuration..........................................................................................................2-14 2.4.14 Adding the Remote Node Configuration...........................................................................................2-14 2.4.15 Adding the MEM Configuration........................................................................................................2-14 2.4.16 Generating SAU Data Loading Files.................................................................................................2-14 2.4.17 Synchronizing the HDU Configuration..............................................................................................2-14

2.5 Data Configuration Examples.......................................................................................................................2-15 2.5.1 Data Configuration in TDM Networking.............................................................................................2-15 2.5.2 Data Configuration in ATM-2M Networking......................................................................................2-19 2.5.3 Data Configuration in IP Networking..................................................................................................2-23

3 Local Office Data Configuration.............................................................................................3-1 3.1 Basic Concepts................................................................................................................................................3-2 3.1.1 Local Office Information.......................................................................................................................3-2 3.1.2 Called Prefix...........................................................................................................................................3-2 3.1.3 SPC.........................................................................................................................................................3-2 3.2 Data Configuration Procedure.........................................................................................................................3-2 3.3 Data Configuration Example...........................................................................................................................3-4 3.3.1 Description.............................................................................................................................................3-5 3.3.2 Example..................................................................................................................................................3-5

4 Signaling Data Configuration................................................................................................. 4-1 4.1 Basic Concepts................................................................................................................................................4-2 4.1.1 MTP-Specific Concepts.........................................................................................................................4-2 4.1.2 MTP3B-Specific Concepts...................................................................................................................4-10 4.1.3 SIGTRAN-Specific Concepts..............................................................................................................4-13 4.1.4 SCCP-Specific Concepts......................................................................................................................4-16 4.1.5 Signaling Data Configuration Principles..............................................................................................4-21 4.2 Data Configuration Procedures.....................................................................................................................4-21 4.2.1 Data Configuration Procedure in TDM Networking............................................................................4-21 4.2.2 Data Configuration Procedure in ATM-2M Networking.....................................................................4-22 4.2.3 Data Configuration Procedure in IP Networking.................................................................................4-23 4.3 MTP Data Configuration Procedure.............................................................................................................4-24 4.4 MTP3B Data Configuration Procedure.........................................................................................................4-26 4.5 M3UA Data Configuration Procedure..........................................................................................................4-27 4.6 SCCP Data Configuration Procedure............................................................................................................4-28 4.6.1 SCCP Data Configuration Principles...................................................................................................4-28 4.6.2 SCCP Data Table Relation...................................................................................................................4-28 4.7 Data Configuration Examples.......................................................................................................................4-29 4.7.1 Data Configuration in TDM Networking.............................................................................................4-30 4.7.2 Data Configuration in ATM-2M Networking......................................................................................4-32 4.7.3 Data Configuration in IP Networking..................................................................................................4-33 ii


Issue 04 (2009-01-15)


Contents

A Abbreviations...........................................................................................................................A-1 Index.................................................................................................................................................i-1

Issue 04 (2009-01-15)


iii


Figures

Figures Figure 1-1 Data configuration process.................................................................................................................1-2 Figure 1-2 MML command input window...........................................................................................................1-4 Figure 2-1 Data configuration flow chart.............................................................................................................2-8 Figure 2-2 OSTA 1.0 hardware data table relation............................................................................................2-10 Figure 2-3 OSTA 2.0 hardware data table relation............................................................................................2-11 Figure 2-4 Board configuration of the OSTA 1.0 subrack ................................................................................2-16 Figure 2-5 Board configuration of the OSTA 2.0 subrack ................................................................................2-16 Figure 2-6 Board configuration of the OSTA 1.0 subrack.................................................................................2-19 Figure 2-7 Board configuration of the OSTA 2.0 subrack.................................................................................2-20 Figure 2-8 Board configuration of the OSTA 1.0 subrack.................................................................................2-23 Figure 2-9 Board configuration of the OSTA 2.0 subrack.................................................................................2-24 Figure 4-1 Structure of the MTP protocol stack...................................................................................................4-2 Figure 4-2 Configuration of the DSPs..................................................................................................................4-4 Figure 4-3 Associated mode.................................................................................................................................4-4 Figure 4-4 Quasi-Associated mode......................................................................................................................4-5 Figure 4-5 Inter-SP communication through the STP..........................................................................................4-5 Figure 4-6 Direct route and alternative route.......................................................................................................4-7 Figure 4-7 Load sharing in one link set................................................................................................................4-7 Figure 4-8 Load sharing among different link sets..............................................................................................4-7 Figure 4-9 Routing of signaling services.............................................................................................................4-9 Figure 4-10 Broadband MTP structure..............................................................................................................4-10 Figure 4-11 Configuration of the DSPs..............................................................................................................4-12 Figure 4-12 Model of the SIGTRAN protocol stack..........................................................................................4-14 Figure 4-13 Inter-SP communication through the STP......................................................................................4-20 Figure 4-14 DPC + GT addressing.....................................................................................................................4-20 Figure 4-15 Procedure for configuring the signaling data in TDM networking................................................4-22 Figure 4-16 Procedure for configuring the signaling data in ATM-2M networking.........................................4-23 Figure 4-17 Procedure for configuring the signaling data in IP networking......................................................4-24 Figure 4-18 MTP data table relation..................................................................................................................4-25 Figure 4-19 MTP3B data table relation..............................................................................................................4-26 Figure 4-20 M3UA data table relation...............................................................................................................4-27 Figure 4-21 SCCP data table relation.................................................................................................................4-29 Figure 4-22 Signaling networking......................................................................................................................4-30 Issue 04 (2009-01-15)


v


Figures

Figure 4-23 Signaling networking......................................................................................................................4-32 Figure 4-24 Signaling networking......................................................................................................................4-33

vi


Issue 04 (2009-01-15)


Tables

Tables Table 1-1 Frequently used MML commands.......................................................................................................1-3 Table 1-2 Procedure for setting the SAU data online...........................................................................................1-5 Table 1-3 Procedure for setting the HDU data online..........................................................................................1-5 Table 1-4 Procedure for setting the SAU data offline..........................................................................................1-5 Table 1-5 Procedure for setting the HDU data offline.........................................................................................1-6 Table 2-1 Relation between the subrack numbers and the settings of S3............................................................2-3 Table 2-2 Relation between the subrack numbers and the settings of the DIP switch.........................................2-3 Table 2-3 Procedure for generating a .dat file....................................................................................................2-14 Table 2-4 Procedure for synchronizing the HDU configuration........................................................................2-15 Table 3-1 Data configuration procedure...............................................................................................................3-3 Table 3-2 Data configuration of the local office..................................................................................................3-5 Table 4-1 Mapping between the number of the links/link sets and the number of 1s in the mask......................4-8 Table 4-2 Example of the selection of link set and link by SLS..........................................................................4-9 Table 4-3 Number assignment for the subsystems related to the HLR..............................................................4-17 Table 4-4 GT indicator.......................................................................................................................................4-17 Table 4-5 GT components..................................................................................................................................4-19 Table 4-6 Mapping between the translation result and the routing indicator.....................................................4-19 Table 4-7 Procedure for configuring the MTP data...........................................................................................4-24 Table 4-8 Procedure for configuring the MTP3B data.......................................................................................4-26 Table 4-9 Procedure for configuring the M3UA data........................................................................................4-27 Table 4-10 Procedure for configuring the SCCP data........................................................................................4-29

Issue 04 (2009-01-15)


vii


About This Document

About This Document

Purpose This section describes the related versions, intended audience, organization, conventions, and update history of the Configuration Guide of the HLR9820.

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

Version

HLR9820

V900R003C02

Intended Audience The intended audiences of this document are: l

Technical support engineers

l

Maintenance engineers

Organization The Configuration Guide describes the data configuration of the HLR9820.

Issue 04 (2009-01-15)

Chapter

Description

1 Overview of Data Configuration

This chapter describes the configuration process of the HLR9820, MML commands, and precautions of the data configuration.

2 Hardware Data Configuration

This chapter describes how to configure the hardware data of the HLR9820.


1


About This Document

Chapter

Description

3 Local Office Data Configuration

This chapter describes how to configure the local site data and system resource data of the HLR9820.

4 Signaling Data Configuration

This chapter describes how to configure the TDM signaling data, ATM-2M signaling data, and IP signaling data of the HLR9820.

A Abbreviations

This appendix lists all acronyms and abbreviations used in this manual.

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

Description

DANGER

WARNING

CAUTION

Indicates a hazard with a high level of risk, which if not avoided, will result in death or serious injury. Indicates a hazard with a medium or low level of risk, which if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation, which if not avoided, could result in equipment damage, data loss, performance degradation, or unexpected results.

TIP

Indicates a tip that may help you solve a problem or save time.

NOTE

Provides additional information to emphasize or supplement important points of the main text.

General Conventions The general conventions that may be found in this document are defined as follows.

2

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

Examples of information displayed on the screen are in Courier New.


Issue 04 (2009-01-15)


About This Document

Command Conventions The command conventions that may be found in this document are defined as follows. Convention

Description

Boldface

The keywords of a command line are in boldface.

Italic

Command arguments are in italics.

[]

Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... }

Optional items are grouped in braces and separated by vertical bars. One item is selected.

[ x | y | ... ]

Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected.

{ x | y | ... }*

Optional items are grouped in braces and separated by vertical bars. A minimum of one item or a maximum of all items can be selected.

[ x | y | ... ]*

Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected.

GUI Conventions The GUI conventions that may be found in this document are defined as follows. 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 Operations The keyboard operations that may be found in this document are defined as follows. Format

Description

Key

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

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 Operations The mouse operations that may be found in this document are defined as follows. Issue 04 (2009-01-15)


3


About This Document

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 04 (2009-01-15) Third commercial release. The updated contents are as follows: Version information updated only.

Updates in Issue 03 (2008-05-30) Second commercial release. The updated contents are as follows: The description of the 750C boards is added.

Updates in Issue 02 (2008-04-15) Initial commercial release. The updated contents are as follows: 2.5.1 Data Configuration in the TDM Networking The reference to the IP address planning for the modules such as the SMU and HDU is modified. The description of the ETU is added to the document.

Updates in Issue 01 (2008-01-31) Initial field trial release

4


Issue 04 (2009-01-15)


1


Overview of Data Configuration

About This Chapter 1.1 Data Configuration Process 1.2 Introduction to MML Commands 1.3 Precautions for Data Configuration

Issue 04 (2009-01-15)


1-1



1.1 Data Configuration Process Figure 1-1 shows the data configuration process of the HLR9820. Figure 1-1 Data configuration process Start

Configure hardware data

Configure office data

Configure signaling data

End

1.2 Introduction to MML Commands 1.2.1 Meanings of Common MML Commands 1.2.2 Rules for Setting MML Command Parameters 1.2.3 Data Setting Procedures

1.2.1 Meanings of Common MML Commands Generally, database operations are implemented using Human-Machine Language (MML) commands. The MML commands are in the action + object format. For example, the ADD BRD command consists of the action ADD and the object BRD. The action ADD indicates that a data record will be added to the BAM database, and the object BRD indicates that the data record will be added to the board data table. The MML commands can be classified into two types, namely, configuration commands and maintenance commands. The configuration commands apply to the BAM and SMU database. The maintenance commands apply to the equipment, signaling links, and system resources. Table 1-1 lists the frequently used MML commands. The part from ADD to LST describes the configuration commands. The part from ACT to SWP describes the maintenance commands.

1-2


Issue 04 (2009-01-15)



Table 1-1 Frequently used MML commands Command

Description

ADD

Adds a data record to the database.

RMV

Removes an existing record from the database. Note that the RMV command can remove only the data records added to the database using the ADD command.

MOD

Modifies certain fields of a data record in the database. Note that the MOD command can modify only the data records added to the database using the ADD or SET command.

LST

Lists the details of one or more records in the database.

ACT

Activates a signaling link or service.

BLK

Blocks a signaling link.

BKP

Backs up the database or the configured data.

DEA

Deactivates a signaling link or service.

DSP

Displays the status of the specified equipment or signaling link, or the usage of system resources.

RST

Resets the specified equipment or signaling link or clears the system resources.

SND

Sends a message to the peer equipment.

SWP

Switches over the active and the standby boards. After the switchover, the active board changes to standby and the standby board changes to active. This command is applicable to the active board only.

1.2.2 Rules for Setting MML Command Parameters The HLR9820 provides a user-friendly Graphic User Interface (GUI). Through the GUI, you can conveniently set the MML command parameters. Figure 1-2 shows the MML command input window of the HLR9820.

Issue 04 (2009-01-15)


1-3



Figure 1-2 MML command input window

When configuring data, pay attention to the following points: l

The parameters in red are the key parameters, for example, Shelf number, Position number, Row number, and Column number, as shown in Figure 1-2. The parameters of this type are mandatory. If these parameters are not specified, running the command fails.

l

The parameters in black are generally ordinary parameters, for example, Location title, as shown in Figure 1-2. The parameters of this type are optional. They do not affect the running of the command.

l

Certain stable parameters are set with default values, for example, PDB location, as shown in Figure 1-2. This helps simplify the configuration. You can modify the values of the parameters of this type as required.

l

If you do not know the default value or value range of a certain parameter, you can place the cursor over the input box of the parameter for about one second. The default value and the value range are displayed, for example, PDB location, as shown in Figure 1-2.

1.2.3 Data Setting Procedures Data setting refers to the process in which the operator configures the data in the database by using MML commands during deployment, expansion, or maintenance. The HLR9820 supports two types of data settings, namely, online setting and offline setting. NOTE

The types of data settings are not distinguished when the configuration is performed through the SMU client. The types of data settings are distinguished only when the configuration is performed through the Local Maintenance Terminal (LMT). l

Online setting Online setting refers to the procedure for refreshing the data in the BAM database, SAU, or HDU by running MML commands on the LMT. It is mainly used for setting the data in the BAM database during routine maintenance. The data volume involved is generally small. Table 1-2 lists the steps of setting the SAU data online.

1-4


Issue 04 (2009-01-15)



Table 1-2 Procedure for setting the SAU data online Step

Description

Command

1

Enable the format conversion switch.

SET FMT: STS=ON;

2

Switch to the online mode.

LON:;

3

Run the data configuration command (example).

ADD N7LNK: MN=22, LNKN=0, LNKNAME="TO MSC", LNKTYPE=1, TS=1, LSX=0, SLC=0, SLCS=0;

4

…

…

Table 1-3 lists the steps of setting the HDU data online. Table 1-3 Procedure for setting the HDU data online

l

Step

Description

Command

1

Enable the HDU configuration switch.

SET CFGSWITCH: SW=ON;

2


ADD MEMCFG: MN=22, LIP1="172.16.200.22", LIP2="172.17.200.22", MSK="255.255.0.0";

3

…

…

Offline setting Offline setting refers to the procedure for refreshing only the data in the BAM database by running MML commands on the LMT. During deployment or expansion, the data volume involved is great because a large number of MML commands are run. In such a circumstance, offline setting is recommended to improve the efficiency. Table 1-4 lists the steps of setting the SAU data offline. Table 1-4 Procedure for setting the SAU data offline

Issue 04 (2009-01-15)

Step

Description

Command

1

Switch to the offline mode.

LOF:;

2

Disable the format conversion switch.

SET FMT: STS=OFF;

3


ADD SHF: SHN=0, LT="HLR", PN=0, RN=0, CN=0;

4

…

…

5


SET FMT: STS=ON;

6

Format all the data.

FMT:;


1-5



Step

Description

Command

7


LON:;

8

Reset the board or the subrack to reload the data.

-

Table 1-5 lists the steps of setting the HDU data offline. Table 1-5 Procedure for setting the HDU data offline Step

Description

Command

1

Disable the HDU configuration switch.

SET CFGSWITCH: SW=OFF;

2


ADD MEMCFG: MN=22, LIP1="172.16.200.22", LIP2="172.17.200.22", MSK="255.255.0.0";

3

…

…

4

Synchronize the HDU configuration.

SYN HDUCFG: MN=250;

5



1.3 Precautions for Data Configuration 1.3.1 Impact of the Maximum Number of Tuples on Data Configuration 1.3.2 Impact of Value Ranges of Software Parameters on Data Configuration 1.3.3 Impact of Software Parameters on Data Configuration 1.3.4 Impact of Board Restarting on Data Configuration

1.3.1 Impact of the Maximum Number of Tuples on Data Configuration Since the memory capacity and the CPU processing capability are limited, the system must consider the memory space required for the software and the databases of various SAU boards when allocating space for the memory zones of the boards. Thus, the system will not allocate excessive storage space for the databases operating in the memory zones of the SAU boards, that is, the system must restrict the maximum number of tuples stored in various data tables in the database. The HLR9820 manages the maximum number of tuples based on modules, including the WSMU, WCCU, and WBSG. For the WCCU and the WBSG, the maximum number of tuples consists of two parts: 1-6


Issue 04 (2009-01-15)



l

Maximum number of tuples of the special table: The maximum number of tuples of a certain special table need not be the same for all the modules of the same type.

l

Maximum number of tuples of the public table: The maximum number of tuples of the public table must be the same for all the modules of the same type. If the system detects that the maximum number of tuples stored in a certain public table is inconsistent among modules, an error occurs when the system formats all the data.

You can use the LST MAXT command to query the maximum number of tuples. If you specify a module number, the system displays the maximum number of tuples of the special table in the module. If you do not specify a module number, the system displays the maximum number of tuples of the public table in the module. Generally, avoid modifying the maximum number of tuples for the databases of the SAU boards. If you modify the maximum number of tuples, the storage capability of other key data will be affected. In addition, the database query efficiency will be reduced because the size of the database is overlarge or even the reliability of the system will be degraded because the size of the database exceeds the system design capability. If it is necessary to modify the maximum number of tuples of the database, contact Huawei technical support engineers.

1.3.2 Impact of Value Ranges of Software Parameters on Data Configuration To facilitate management and control, a theoretical value range is defined for each numerical parameter during data configuration. Generally, if the field mapping a parameter is not the key field, the system allows you to configure data as long as the value you set for the parameter is within the theoretical value range. Take the ADD M3LNK command for example. When the ADD M3LNK command is run to add an M3UA link, since Local port and Peer port are not the key fields used by the database to sort and retrieve the data tables of the M3UA links, the actual values of Local port and Peer port are restricted by their theoretical value ranges, respectively. If the field mapping a parameter is the primary or secondary key field used by the database of the SAU board to sort and retrieve the related data tables, the value you set for the parameter is restricted by both the theoretical value range and the maximum number of tuples of the table where the parameter exists. There are two cases as follows: l

Primary key field If the field mapping a parameter (must be numbered globally) is the primary key field used by the database to sort and retrieve the data records in a certain table, to improve the efficiency, the system allocates the storage space for the data table in the database based on the maximum index number of the parameter. In other words, the actual value of the maximum index number of the parameter is equal to the maximum number of tuples of the table. This can be verified through simple conversion. For example, in the M3UA Link Set table configured by the ADD M3LKS command, Link set index (must be numbered globally) is the primary key field used by the database to sort and retrieve data records in the M3UA Link Set table. Assume that the theoretical value range of Link set index is 0 - M and the maximum number of tuples of the M3UA Link Set table is N for the ADD M3LKS command. If the theoretical value range is not considered, the actual value range of Link set index is 0 - (N-1). Otherwise, the actual value range is the intersection of 0 - M and 0 - (N-1).

Issue 04 (2009-01-15)


1-7



When you configure the M3UA link set using the ADD M3LKS command, the actual value range of Link set index is 0 - 127 but not 0 - 65534 if M is 65534 and N is 128. If you set the parameter to a value that is greater than 128, an error occurs. l

Secondary key field If the field mapping a parameter (need not be numbered globally) is the secondary key field used by the database to sort and retrieve the data records in a certain table, the maximum number of tuples limits only the maximum number of data records that can be configured. In this case, the actual value range of the parameter is also restricted by its theoretical value range. For example, in the M3UA Link table configured by the ADD M3LNK command, Module number (must be numbered globally) is the primary key field and Link number (need be numbered in the module only) is the secondary key field for the host database to sort and retrieve data of the M3UA Link table. Assume that the theoretical value range of Link number is 0 - M and the maximum number of tuples of the M3UA Link table is N for the ADD M3LNK command. The actual value range of Link number is still 0 - M. When you configure the M3UA link using the ADD M3LNK command, the actual value range of Link number is 0 - 63 if M is 63 and N is 32. For a certain WBSG module, the actual value range of Link number is 0 - 63 but the total number of M3UA links, however, cannot exceed 32. An error occurs when you add more than 32 M3UA links.

1.3.3 Impact of Software Parameters on Data Configuration Software parameters are designed to solve specific problems. Each bit of a software parameter has a unique meaning. Generally, you can directly use the default values. If you need to modify a software parameter, contact Huawei technical support engineers.

1.3.4 Impact of Board Restarting on Data Configuration If the SAU and the BAM of the HLR9820 are normal when you configure the databases of the SAU boards on the LMT in online mode, the system can ensure data consistency between the databases of the SAU boards and the database of the BAM. In certain cases, for example, troubleshooting, software upgrade, or system expansion, you may need to switch over or reset a board. At this point, the board loads programs and data from the BAM again. This process is called board restarting. The operation of the board is unstable during restarting. To be specific, the communication between the board and the BAM is unstable; the communication between the board and other boards is unstable; the board cannot respond to maintenance commands in time. At this point, do not carry out operations that may change the database data on the LMT. Otherwise, the database data between the SAU board and the BAM may be inconsistent. This affects the security and stability of the system. After switching over or resetting a board, you must run the DSP BRD command to check the operating status of the board and run the STR CRC command to check the data consistency. You should configure data on the LMT only when the board is normal.

1-8


Issue 04 (2009-01-15)


2


Hardware Data Configuration

About This Chapter Hardware data is the basic data of the HLR9820. The purpose of hardware data configuration is to define the hardware of the HLR9820 and the related information. Hardware data configuration is the basis for the configuration of other data. 2.1 Basic Concepts 2.2 Data Configuration Flow Chart 2.3 Hardware Data Table Relation 2.4 Data Configuration Procedure 2.5 Data Configuration Examples

Issue 04 (2009-01-15)


2-1



2.1 Basic Concepts 2.1.1 Rack Number 2.1.2 Subrack Number 2.1.3 Slot Number 2.1.4 Module Number 2.1.5 Cluster 2.1.6 Node

2.1.1 Rack Number Each rack is allocated a number, which is called the rack number. The HLR9820 can be configured with a maximum of six racks. The rack number ranges from 0 to 5. Based on the internal components, the cabinets are classified into the integrated cabinet and the extended cabinet. l

The integrated cabinet, also called the basic cabinet, houses the components such as the power distribution box (PDB), OSTA 1.0 subrack, OSTA 2.0 subrack, LAN switch (optional) and disk array. The integrated cabinet is mandatory and perpetually numbered 0.

l

The extended cabinets are optional. They are numbered from 1 to 5 sequentially.

You can add a rack by running the ADD SHF command.

2.1.2 Subrack Number Each subrack is allocated a number, which is called the subrack number.

Numbering of OSTA 1.0 Subracks The HLR9820 can be configured with a maximum of 10 OSTA 1.0 subracks. The subrack number ranges from 0 to 9. The basic subrack is perpetually numbered 0. The subracks are numbered according to the following rules: l

The subracks in a cabinet are numbered in ascending sequence from the top to the bottom of the cabinet.

l

The subracks in multiple subracks are numbered in ascending sequence based on the cabinet number.

You can set the subrack number through the DIP switch S3 (which comprises eight sub-switches) on the Wireless System Interface Unit (WSIU). Table 2-1 presents the relation between the subrack numbers and the settings of S3.

2-2


Issue 04 (2009-01-15)



Table 2-1 Relation between the subrack numbers and the settings of S3 Subrack Number

Sub-switch 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

The On position (at the lower side) denotes 0, and the Off position (at the upper side) denotes 1. NOTE

l

The OSTA 1.0 subrack housing the WCKI is the basic subrack.

l

You can add an OSTA 1.0 subrack by running the ADD FRM command.

Numbering of OSTA 2.0 Subracks The HLR9820 can be configured with a maximum of 16 OSTA 2.0 subracks. The subrack number ranges from 30 to 45. The basic subrack is perpetually numbered 30.The subracks are numbered according to the following rules: l

The subracks in a cabinet are numbered in ascending sequence from the bottom to the top of the cabinet.

l

The subracks in multiple subracks are numbered in ascending sequence based on the cabinet number.

You can set the subrack number through the DIP switch on the Subrack Data Module (SDM). Table 2-2 presents the relation between the subrack numbers and the settings of the DIP switch. Table 2-2 Relation between the subrack numbers and the settings of the DIP switch Subrack Number

Issue 04 (2009-01-15)

Sub-switch 1

2

3

4

5

6

7

8

30

Off

Off

Off

On

On

On

On

Off

31

Off

Off

Off

On

On

On

On

On


2-3



Subrack Number

Sub-switch 1

2

3

4

5

6

7

8

32

Off

Off

On

Off

Off

Off

Off

Off

33

Off

Off

On

Off

Off

Off

Off

On

34

Off

Off

On

Off

Off

Off

On

Off

35

Off

Off

On

Off

Off

Off

On

On

36

Off

Off

On

Off

Off

On

Off

Off

37

Off

Off

On

Off

Off

On

Off

On

38

Off

Off

On

Off

Off

On

On

Off

39

Off

Off

On

Off

Off

On

On

On

...

...

45

Off

Off

On

Off

On

On

Off

On

The DIP switch on the SDM and the DIP switch on the WSIU indicate different values. The On position (at the lower side) denotes 1, and the Off position (at the upper side, refer to Setting the OSTA 2.0 Subrack Numbers) denotes 0. NOTE

l

The OSTA 2.0 subrack housing the INU is the basic subrack.

l

For details on the SDM, refer to the Hardware Description.

l

You can add an OSTA 2.0 subrack by running the ADD SFRM command.

2.1.3 Slot Number Different types of boards are configured in the slots of a subrack based on the functions to be implemented. Each slot is allocated a slot number.

Rules for Configuring the OSTA 1.0 Boards An OSTA 1.0 subrack has a maximum of 21 slots numbered from 0 to 20. The OSTA 1.0 subrack is configured with the following boards: l

The WSMUs are permanently configured in front slots 6 and 8, and the Wireless System Interface Units (WSIUs) are configured in the rear slots.

l

The Wireless Hot-Swap and Control Units (WHSCs) are configured in rear slots 7 and 9, whereas the front slots 7 and 9 are left empty.

l

The Wireless Alarm Unit (WALU) is configured in front slot 16.

l

The UMSC PSM Power Modules (UPWRs) are configured in front slots 17 to 20, and rear slots 19 and 20. NOTE

The rear slots 17-18 are reserved for a UPWR in the case of system expansion. By default, the two slots are not configured with the UPWR.

2-4


Issue 04 (2009-01-15)



Different boards can be configured in the remaining slots based on the networking mode of the HLR9820. l

If the HLR9820 adopts TDM networking, see OSTA 1.0 Board Configuration in TDM Networking for the board configuration of the OSTA 1.0 subrack.

l

If the HLR9820 adopts IP networking, see OSTA 1.0 Board Configuration in IP Networking for the board configuration of the OSTA 1.0 subrack.

l

If the HLR9820 adopts ATM-2M networking, see OSTA 1.0 Board Configuration in ATM-2M Networking for the board configuration of the OSTA 1.0 subrack.

Rules for Configuring the OSTA 2.0 Boards An OSTA 2.0 subrack has a maximum of 16 slots. The slot number ranges from 0 to 15, board configuration refer toBoard Configuration for Different Product Applications. The OSTA 2.0 subrack has 14 vertical slots, which are numbered from 0 to 13. The front slots can be configured with the following types of boards: l

Data Management Unit (DMU)

l

Data Routing Unit (DRU)

l

Data Service Unit (DSU)

l

Service Process Unit (SCU)

l

Back Management Unit (BAM)

l

Subscriber Management Unit (SMU)

l

BAM and SMU Unit (BSU)

l

Installation Unit (INU)

l

Emergency Takeover Unit (ETU)

The rear slots can be configured with the following types of boards: l

Service FC Interface (FCI, that is, USI3)

l

Service GE Interface (GEI, that is, USI1)

l

Switch Interface Unit (SWI)

The OSTA 2.0 subrack has two horizontal slots, which are numbered from 14 to 15. They are perpetually configured with the Shelf Management Modules (SMMs). The rules for configuring the OSTA 2.0 boards are as follows: l

The INU is perpetually configured in front slot 10 in OSTA 2.0 subrack 30, and the GEI is configured in the rear slot.

l

The DMUs are perpetually configured in front slots 0 and 2 in OSTA 2.0 subrack 30, and the FCIs are configured in the rear slots.

l

The BSUs or BAMs are configured in front slots 11 and 13 in OSTA 2.0 subrack 30, and the GEIs are configured in the rear slots.

l

The ETU is perpetually configured in front slot 12 in OSTA 2.0 subrack 30, whereas the rear slot is left empty.

l

The SMUs are perpetually configured in front slots 11 and 13 in OSTA 2.0 subrack 31, and the GEIs are configured in the rear slots.

Issue 04 (2009-01-15)


2-5


2 Hardware Data Configuration l

The DRUs are configured in front slots 1 and 3 in OSTA 2.0 subracks, whereas the rear slots are left empty.

l

The SCUs and DSUs are configured in the remaining slots. The SCUs are preferentially configured in front slots 0, 2, 4, and 8. The DSUs are preferentially configured in front slots 1, 3, 5, 9, 11, and 13. The rear slots are left empty.

OSTA 2.0 Boards shows the board configuration of the OSTA 2.0 subrack.

2.1.4 Module Number A board in the HLR9820 is considered as a module. Each module is allocated a number, which is called the module number. The module number of each board is unique. The boards working in active/standby mode have the same module number. The modules are numbered as follows: l

BAM: 0

l

WSMU: 2 to 21 (automatically allocated)

l

WCSU/WESU/WCCU: 22 to 101

l

WIFM/WBSG/WEAM: 132 to 211

l

BSU/SMU: 212 to 213

l

DSU/DMU/SCU/DRU/ETU/INU: 216 to 249

2.1.5 Cluster A cluster refers to a group of processes or nodes that provide the same service. Generally, a cluster consists of one master node and several slave nodes. If the master node is faulty, the services of the master node are switched to another node in the cluster for processing. Thus, the service provisioning is not affected by the failure of a single node, and the system reliability is improved. The rules for numbering clusters are as follows: l

The HSU cluster ID is set to 1.

l

The DRU cluster ID is set to 11.

l

The DSU cluster ID ranges from 12 to 512.

The rules for configuring clusters are as follows: l

An HSU cluster is permanently configured. Therefore, you need not configure the HSU cluster manually.

l

A DRU cluster is permanently configured. Therefore, you need not configure the DRU cluster manually.

l

Three DSU clusters are configured for each pair of DSU boards.

2.1.6 Node A node refers to a unit that can independently provide services. A host or board may have one or more nodes. The nodes that manage the same subscriber data constitute a cluster. Based on the node status, the nodes can be classified into two types: 2-6


Issue 04 (2009-01-15)



l

Master node: Each cluster can have only one master node. The master node implements functions such as adding, deleting, modifying, and querying data.

l

Slave node: Each cluster may have one or more or no slave nodes. The slave nodes can only query data.

The nodes of the HLR can be classified into the HSU, DRU, and DSU nodes. The rules for configuring the nodes are as follows: l

Each DMU board is permanently configured with one HSU node.

l

Each SCU board is permanently configured with one HSU node.

l

Each DRU board is permanently configured with one DRU node.

l

Each DSU board is permanently configured with three DSU nodes.

2.2 Data Configuration Flow Chart Figure 2-1 shows the procedure for configuring the hardware data and the related commands.

Issue 04 (2009-01-15)


2-7



Figure 2-1 Data configuration flow chart Start Add a rack(ADD SHF) Add an OSTA 1.0 subrack(ADD FRM) Set the OSTA 1.0 board type(ADD BRDTYPE) Add an OSTA 1.0 board(ADD BRD) TDM networking

ATM-2M networking IP networking

Configure the E1 information (ADD EPICFG)

Configure the E1 information (ADD EPICFG)

Add the WIFM FE port information (ADD FECFG)

Configure the clock reference resource (SET CKICFG)

Configure the clock reference resource (SET CKICFG)

Add the IMA group information (ADD IMAGRP)

Add the UNI link information (ADD UNILNK)

Add the IMA link information (ADD IMALNK)

Add the PVC link information (ADD PVCLNK)

Add an OSTA 2.0 subrack(ADD SFRM) Add an OSTA 2.0 board(ADD SBRD) Set the local office information (SET LOCALSITE) Add the cluster configuration(ADD CLUSTER) Add the node configuration(ADD NODE) Set the HDU configuration(SET HDU) Add the remote node configuration (ADD REMOTENODE)(Optional)

On the SMU client HDU configuration

Add the MEM configuration(ADD MEMCFG) Loading SAU data files Synchronizing the HDU Configuration End

2-8


Issue 04 (2009-01-15)



CAUTION After configuring the Fabric network segments by using the SET LOCALSITE command, perform one of the following operations for the configuration to take effect: l

Run the IPMISTARTDEAMOND.sh script in the /etc/init.d/ directory on all the boards (except the INU).

l

On the LMT, run the RST BRD command to restart all the USPs (except the INU) running the Linux operating system.

l

On all the USPs (except the INU) running the Linux operating system, run the sync;reboot command to restart the USPs. NOTE

l

The procedures marked in blue in Figure 2-1 are performed during the software installation, skip these procedures during the data configuration.

l

If ATM-2M links are used to transfer inter-office signaling, select inverse multiplexing for ATM (IMA) or user network interface (UNI) mode to configure the data of the system. The configuration modes of both ends must be the same.

l

Configuration of remote node data (by using the ADD REMOTENODE command) is required only for the seamless geographic redundancy solution.

2.3 Hardware Data Table Relation As shown in Figure 2-1, the hardware data is configured in the following sequence: l

Configuring a rack

l

Configuring a subrack

l

Configuring a board

Therefore, certain parameters are required to associate them. For example, during the configuration of a subrack, a parameter is required to ensure that the subrack is configured in the specified rack. During the configuration of a board, a parameter is required to ensure that the board is configured in the specified subrack. Figure 2-2 and Figure 2-3 show the relations between the hardware data tables.

Issue 04 (2009-01-15)


2-9



Figure 2-2 OSTA 1.0 hardware data table relation

ADD SHF [Shelf number] [Location title] [Position number] [Row number] [Column number] … ADD FRM

ADD FECFG [IFM module number] [IP address] [Mask address] [Default gateway] … ADD MEMCFG

[Frame number] [Shelf number] [Position number]

[Module number] [Local IP address]

…

ADD BRD [Module number] [Frame number] [Slot number]

ADD EPICFG

[Frame number] [Slot number]

[Location title] …

2-10


Issue 04 (2009-01-15)



Figure 2-3 OSTA 2.0 hardware data table relation

ADD SHF [Shelf number] [Location title]

ADD CLUSTER

[Position number] [Row number] [Column number]

[Cluster ID]

ADD SFRM [Shelf number] [Frame number] [Position number]

ADD REMOTENODE [Cluster ID] [Node ID] [IP address]

ADD SBRD [Frame number]

ADD NODE

[Slot number]

[Node ID]

[Location title]

[Cluster ID]

[Module number]

[Module number]

2.4 Data Configuration Procedure 2.4.1 Adding a Rack 2.4.2 Adding an OSTA 1.0 Subrack 2.4.3 Setting the OSTA 1.0 Board Type 2.4.4 Adding an OSTA 1.0 Board 2.4.5 Configuring the Hardware Data in TDM Networking Issue 04 (2009-01-15)


2-11



2.4.6 Configuring the Hardware Data in IP Networking 2.4.7 Configuring the Hardware Data in ATM-2M Networking 2.4.8 Adding an OSTA 2.0 Subrack 2.4.9 Adding an OSTA 2.0 Board 2.4.10 Setting the Local Office Information 2.4.11 Adding the Cluster Configuration 2.4.12 Adding the Node Configuration 2.4.13 Setting the HDU Configuration 2.4.14 Adding the Remote Node Configuration 2.4.15 Adding the MEM Configuration 2.4.16 Generating SAU Data Loading Files 2.4.17 Synchronizing the HDU Configuration

2.4.1 Adding a Rack Add a rack by running the ADD SHF command. For details, refer to Adding a Shelf (ADD SHF). NOTE

The hardware data is configured in offline mode by default. Before adding a rack, switch the SAU and HDU to the offline state by running the LOF:; command.

2.4.2 Adding an OSTA 1.0 Subrack Add an OSTA 1.0 subrack by running the ADD FRM command. For details, refer to Adding a Frame (ADD FRM).

2.4.3 Setting the OSTA 1.0 Board Type You can run the SET BRDTYPE command to set the type of the OSTA 1.0 board. For details on the command description, refer to Set Local Office Board Type (SET BRDTYPE).

2.4.4 Adding an OSTA 1.0 Board Add an OSTA 1.0 board by running the ADD BRD command. For details, refer to Adding a Board (ADD BRD).

2.4.5 Configuring the Hardware Data in TDM Networking As shown in Figure 2-1, the E1 information and clock reference source are also required to be set in TDM networking. For details on how to set the E1 information, refer to Adding the WEPI Configuration (ADD EPICFG). 2-12


Issue 04 (2009-01-15)



For details on how to set the clock reference source, refer to Setting the WCKI (SET CKICFG).

2.4.6 Configuring the Hardware Data in IP Networking As shown in Figure 2-1, the FE port information of the WIFM is also required to be set in IP networking. For details on how to add the FE port information, refer to Adding the FE Configuration (ADD FECFG).

2.4.7 Configuring the Hardware Data in ATM-2M Networking As shown in Figure 2-1, the information such as IMA group information or UNI link information is also required to be set in ATM-2M networking. For details on how to set the E1 information, refer to Adding the WEPI Configuration (ADD EPICFG). For details on how to set the clock reference source, refer to Setting the WCKI (SET CKICFG). For details on how to add the IMA group information, refer to Adding the IMA Group Configuration (ADD IMAGRP). For details on how to add the IMA link information, refer to Adding the IMA Link Configuration (ADD IMALNK). For details on how to add the UNI link information, refer to Adding the UNI Link Configuration (ADD UNILNK). For details on how to add the PVC link information, refer to Adding the PVC Link Configuration (ADD PVCLNK).

2.4.8 Adding an OSTA 2.0 Subrack Add an OSTA 2.0 subrack by running the ADD SFRM command. For details, refer to Adding an OSTA 2.0 Frame (ADD SFRM).

2.4.9 Adding an OSTA 2.0 Board Add an OSTA 2.0 board by running the ADD SBRD command. For details, refer to Adding an OSTA 2.0 Board (ADD SBRD).

2.4.10 Setting the Local Office Information Set the local office information by running the SET LOCALSITE command. For details, refer to Setting the Local Site Information (SET LOCALSITE).

2.4.11 Adding the Cluster Configuration A cluster consists of multiple logical nodes. Each node can provide services. During deployment and expansion, you must add the cluster configuration. Issue 04 (2009-01-15)


2-13



Add the cluster configuration by running the ADD CLUSTER command. For details, refer to Adding the Cluster Configuration (ADD CLUSTER).

2.4.12 Adding the Node Configuration Add the node configuration by running the ADD NODE command. For details, refer to Adding the Node Configuration (ADD NODE).

2.4.13 Setting the HDU Configuration Set the HDU configuration by running the SET HDU command. For details, refer to Setting the SMU-HDU Connection (SET HDU). NOTE

This operation must be performed on the SMU client.

2.4.14 Adding the Remote Node Configuration Add the remote node configuration by running the ADD REMOTENODE command. For details, refer to Adding the Remote Node Configuration (ADD REMOTENODE).

2.4.15 Adding the MEM Configuration Add the MEM configuration by running the ADD MEMCFG command. For details, refer to Adding the MEM Configuration (ADD MEMCFG).

2.4.16 Generating SAU Data Loading Files If the SAU hardware data is added offline, you must format the data of all the modules to generate .dat files after the SAU hardware data configuration is complete. By default, the files are stored in the path D:\HLR9820\Load. Table 2-3 lists the procedure for generating a .dat file. Table 2-3 Procedure for generating a .dat file Ste p

Command

Function

1

SET FMT: STS=ON;


2

FMT:;

Format the data of all the modules.

3

LON:;


2.4.17 Synchronizing the HDU Configuration If the HDU hardware data is added offline, you must synchronize the data in the HDU database with that in the BAM database after the HDU hardware data configuration is complete. Table 2-4 lists the procedure for synchronizing the HDU configuration. 2-14


Issue 04 (2009-01-15)



Table 2-4 Procedure for synchronizing the HDU configuration Step

Command

Function

1



2

SYN HDUCFG: MN=250;

Synchronize the data in the HDU database with that in the BAM database.

2.5 Data Configuration Examples 2.5.1 Data Configuration in TDM Networking 2.5.2 Data Configuration in ATM-2M Networking 2.5.3 Data Configuration in IP Networking

2.5.1 Data Configuration in TDM Networking Description A rack named HLR9820 is configured. It is located in row 0 and column 0 in the equipment room and numbered 0. The rack is configured with an OSTA 1.0 basic subrack in TDM networking. In addition to the WSMU, WALU, and UPWR, the WCSU and WEPI are configured in the subrack to implement narrowband signaling processing. Figure 2-4 shows the board configuration of the OSTA 1.0 basic subrack. Clock signals are extracted from E1 0 on the WEPI in slot 0. The rack is also configured with an OSTA 2.0 subrack. Figure 2-5 shows the board configuration of the OSTA 2.0 subrack. The port of the maintenance plane is numbered 16504, and that of the service plane is numbered 16500. The location ID of the local site is 1. The IP addresses of the Fabric network segment are 172.18.100.0 and 172.19.100.0.

Issue 04 (2009-01-15)


2-15



Figure 2-4 Board configuration of the OSTA 1.0 subrack Back 0 1 2 3 4 5 6 7

8 9 10 11 12 13 14 15 16 17 18 19 20

W E P I

W S I U

W E P I

W S I U

W H S C

W C K I

W H S C

0 1 2 3 4 5 6 7

8 9 10 11 12 13 14 15 16 17 18 19 20

W C S U

W S M U

W C S U

W S M U

W A L U

U P W R

W C K I

U P W R

U P W R

Front

Figure 2-5 Board configuration of the OSTA 2.0 subrack Back 0

1

F C I

2

3

4

F C I

0

1

2

3

4

5

6

7

8

9

D M U

D R U

D M U

D R U

S C U

D S U

S W U

S W U

S C U

D S U

14

SMM

5

15

6

7

S W I

S W I

8

9

10 11 12 13 G E I

G E I

G E I

10 11 12 13 I N U

B S U

E T U

B S U

SMM

Front

Example /*Enable the offline mode.*/ LOF:; /*Disable the data formatting function.*/ SET FMT: STS=OFF; /*Disable the online data configuration for the HDU.*/ SET CFGSWITCH: SW=OFF; /*Add a rack.*/

2-16


Issue 04 (2009-01-15)



ADD SHF: SHN=0, LT="HLR9820", PN=0, RN=0, CN=0; /*You can run the LST SHF command to check whether the rack is added.*/ /*Add an OSTA 1.0 subrack.*/ ADD FRM: FN=0, SHN=0, PN=3; /*You can run the LST FRM command to check whether the OSTA 1.0 subrack is added.*/ /*You can run the LST BRD command to query the boards added to the OSTA 1.0 subrack.*/ /*Set the board type.*/ SET BRDTYPE: BT=B; /*The OSTA 1.0 subrack is already configured with the WSMU, WALU, and UPWR. You need to add the WCSU, WEPI, and WCKI.*/ /*Add the WCSUs. The WCSUs in slots 0 and 1 work in active/standby mode.*/ */ ADD BRD: FN=0, SLN=0, LOC=FRONT, BT=WCSU, MN=22, ASS=1; /*Add the interface boards (WEPIs) for the WCSUs.*/ ADD BRD: FN=0, SLN=0, LOC=BACK, BT=WEPI; ADD BRD: FN=0, SLN=1, LOC=BACK, BT=WEPI; /*Add the WCKIs.*/ ADD BRD: FN=0, SLN=13, LOC=BACK, BT=WCKI; ADD BRD: FN=0, SLN=15, LOC=BACK, BT=WCKI; /*You can run the LST BRD command to query the board configuration.*/ /*Add E1s.*/ ADD EPICFG: FN=0, SLN=0, E0=DF, E1=DF, E2=DF, E3=DF, E4=DF, E5=DF, E6=DF, E7=DF, BM=BALANCE; /*Configure the clock reference source and set its work mode to Automatic.*/ SET CKICFG: WM=AUTO; SET CLKSRC: FN=0, SN1=13, SN2=15; /*Enable the system to use the clock reference source extracted from E1 0 on the WEPI in slot 0.*/ ADD BOSRC: FN=0, SLN=0, EN=0; /*Add an OSTA 2.0 subrack.*/ ADD SFRM: FN=30, SHN=0, PN=2; /*You can run the LST SFRM command to check whether the OSTA 2.0 subrack is added.*/ /*You can run the LST SBRD command to query the boards added to the OSTA 2.0 subrack.*/ /*Add OSTA 2.0 boards.*/ /*Add the DMUs in slots 0 and 2.*/ ADD SBRD: FN=30, SLN=0, LOC=FRONT, BT=DMU, MN=216, BAPORT=16504; ADD SBRD: FN=30, SLN=2, LOC=FRONT, BT=DMU, MN=217, BAPORT=16504; /*Add the DRUs in slots 1 and 3.*/ ADD SBRD: FN=30, SLN=1, LOC=FRONT, BT=DRU, MN=218, BAPORT=16504; ADD SBRD: FN=30, SLN=3, LOC=FRONT, BT=DRU, MN=219, BAPORT=16504; /*Add the SCUs in slots 4 and 8.*/ ADD SBRD: FN=30, SLN=4, LOC=FRONT, BT=SCU, MN=220, BAPORT=16504, FBPORT=16500; ADD SBRD: FN=30, SLN=8, LOC=FRONT, BT=SCU, MN=221, BAPORT=16504,

Issue 04 (2009-01-15)


2-17


2 Hardware Data Configuration FBPORT=16500;

/*Add the DSUs in slots 5 and 9.*/ ADD SBRD: FN=30, SLN=5, LOC=FRONT, BT=DSU, MN=222, BAPORT=16504; ADD SBRD: FN=30, SLN=9, LOC=FRONT, BT=DSU, MN=223, BAPORT=16504; /*Add two BSUs in slots 11 and 13 of subrack 30, and enable the two BAMs to work in active/standby mode.*/ ADD SBRD: FN=30, SLN=11, LOC=FRONT, BT=BSU, MN=212, ASS=13; /*Add an INU in slot 10.*/ ADD SBRD: FN=30, SLN=10, LOC=FRONT, BT=INU, MN=224, BAPORT=16504; /*Add an ETU in slot 12.*/ ADD SBRD: FN=30, SLN=12, LOC=FRONT, BT=ETU, MN=249, BAPORT=16504; /*You can run the LST SBRD command to query the board configuration.*/ /*Set the location ID of the local site.*/ SET LOCALSITE: LOCID=1, IP1="172.18.100.0", MSK1="255.255.255.0", IP2="172.19.100.0", MSK2="255.255.255.0"; /*Add a cluster.*/ ADD CLUSTER: CID=12, CT=DSU; ADD CLUSTER: CID=13, CT=DSU; ADD CLUSTER: CID=14, CT=DSU; /*Add nodes.*/ ADD NODE: MN=216, ADD NODE: MN=217, ADD NODE: MN=220, ADD NODE: MN=221, ADD NODE: MN=218, ADD NODE: MN=219, ADD NODE: MN=222, ADD NODE: MN=223, ADD NODE: MN=222, ADD NODE: MN=223, ADD NODE: MN=222, ADD NODE: MN=223,

NID=1, NT=HSU, NOFCF=0, NOFSMF=2, CID=1, IPPORTCODE=1; NID=2, NT=HSU, NOFCF=0, NOFSMF=2, CID=1, IPPORTCODE=1; NID=3, NT=HSU, NOFCF=3, NOFSMF=0, CID=1, IPPORTCODE=1; NID=4, NT=HSU, NOFCF=3, NOFSMF=0, CID=1, IPPORTCODE=1; NID=5, NT=DRU, NOFRDBS=2, CID=11, IPPORTCODE=1; NID=6, NT=DRU, NOFRDBS=2, CID=11, IPPORTCODE=1; NID=7, NT=DSU, NOFRDBS=2, CID=12, IPPORTCODE=1; NID=10, NT=DSU, NOFRDBS=2, CID=12, IPPORTCODE=1; NID=8, NT=DSU, NOFRDBS=2, CID=13, IPPORTCODE=2; NID=11, NT=DSU, NOFRDBS=2, CID=13, IPPORTCODE=2; NID=9, NT=DSU, NOFRDBS=2, CID=14, IPPORTCODE=3; NID=12, NT=DSU, NOFRDBS=2, CID=14, IPPORTCODE=3;

/*Configure the MEM module. Set the module number to 22, local IP address 1 to 172.16.200.22, local IP address 2 to 172.17.200.22, and the subnet mask to 255.255.0.0.*/ ADD MEMCFG: MN=22, LIP1="172.16.200.22", LIP2="172.17.200.22", MSK="255.255.0.0"; /*Load the configured data to the HDU.*/ SYN HDUCFG: MN=250; /*Enable the online data configuration for the HDU.*/ SET CFGSWITCH: SW=ON; /*Enable the data formatting function.*/ SET FMT: STS=ON; /*Format the data.*/ FMT:; /*Start the online mode.*/ LON:;

2-18


Issue 04 (2009-01-15)



/*Configure the HDU data on the SMU client. */ SET HDU: OPTYPE=ADD, HDUNAME="DMU0", HDUIP1="172.18.100.2", HDUIP2="172.19.100.2"; SET HDU: OPTYPE=ADD, HDUNAME="DMU2", HDUIP1="172.18.100.4", HDUIP2="172.19.100.4"; /*You can run the LST HDU command to query the HDU configuration.*/ /*Switch on or restart (switch off and then switch on) the OSTA 1.0 subrack to load the data to all modules.*/

For details on the IP address planning for the modules such as the SMU and the HDU, refer to IP Addresses of the OSTA 2.0 Boards.

2.5.2 Data Configuration in ATM-2M Networking Description A rack named HLR9820 is configured. It is located in row 0 and column 0 in the equipment room and numbered 0. The rack is configured with an OSTA 1.0 basic subrack in ATM-2M networking. In addition to the WSMU, WALU, and UPWR, the WEAM and its back board WEPI are configured in the subrack to process IMA or UNI links. Figure 2-6 shows the board configuration of the OSTA 1.0 basic subrack. Clock signals are extracted from E1 0 on the WEPI in slot 0. IMA group 0 with IMA group ID 0 is added. IMA link 0 is added for IMA group 0. The rack is also configured with an OSTA 2.0 subrack. Figure 2-7 shows the board configuration of the OSTA 2.0 subrack. The port of the maintenance plane is numbered 16504, and that of the service plane is numbered 16500. The location ID of the local site is 1. The IP addresses of the Fabric network segment are 172.18.100.0 and 172.19.100.0. Figure 2-6 Board configuration of the OSTA 1.0 subrack Back 0 1 2 3 4 5 6 7 W E P I

W E P I

W S I U

W H S C

8 9 10 11 12 13 14 15 16 17 18 19 20 W S I U

W H S C

W C K I

0 1 2 3 4 5 6 7

8 9 10 11 12 13 14 15 16 17 18 19 20

W E A M

W S M U

W E A M

W C C U

W C C U

W S M U

W B S G

W B S G

W A L U

U P W R

W C K I

U P W R

U P W R

Front

Issue 04 (2009-01-15)


2-19




1

F C I

2

3

4

F C I

0

1

2

3

4

5

6

7

8

9

D M U

D R U

D M U

D R U

S C U

D S U

S W U

S W U

S C U

D S U

14

5

SMM

15

6

7

S W I

S W I

8

9

10 11 12 13 G E I

G E I

G E I

10 11 12 13 I N U

B S U

E T U

B S U

SMM

Front

Example /*Enable the offline mode.*/ LOF:; /*Disable the data formatting function.*/ SET FMT: STS=OFF; /*Disable the online data configuration for the HDU.*/ SET CFGSWITCH: SW=OFF; /*Add a rack.*/ ADD SHF: SHN=0, LT="HLR9820", PN=0, RN=0, CN=0; /*You can run the LST SHF command to check whether the rack is added.*/ /*Add an OSTA 1.0 subrack.*/ ADD FRM: FN=0, SHN=0, PN=3; /*You can run the LST FRM command to check whether the OSTA 1.0 subrack is added.*/ /*You can run the LST BRD command to query the boards added to the OSTA 1.0 subrack.*/ /*Set the board type.*/ SET BRDTYPE: BT=B; /*The OSTA 1.0 subrack is already configured with the WSMU, WALU, and UPWR. You need to add the WEAM, WEPI, WCCU, WBSG, and WCKI.*/ /*Add the WEAMs in slots 0 and 1. The WEAMs work in load-sharing mode.*/ ADD BRD: FN=0, SLN=0, LOC=FRONT, BT=WEAM, MN=132; ADD BRD: FN=0, SLN=1, LOC=FRONT, BT=WEAM, MN=133; /*Add the interface boards (WEPIs) for the WEAMs.*/ ADD BRD: FN=0, SLN=0, LOC=BACK, BT=WEPI; ADD BRD: FN=0, SLN=1, LOC=BACK, BT=WEPI;

2-20


Issue 04 (2009-01-15)



/*Add a WCCU.*/ ADD BRD: FN=0, SLN=2, LOC=FRONT, BT=WCCU, MN=22, ASS=3; /*Add the WBSGs.*/ ADD BRD: FN=0, SLN=10, LOC=FRONT, BT=WBSG, MN=134; ADD BRD: FN=0, SLN=11, LOC=FRONT, BT=WBSG, MN=135; /*Add the WCKIs.*/ ADD BRD: FN=0, SLN=13, LOC=BACK, BT=WCKI; ADD BRD: FN=0, SLN=15, LOC=BACK, BT=WCKI; /*You can run the LST BRD command to query the board configuration.*/ /*Add E1s.*/ ADD EPICFG: FN=0, SLN=0, LM=E1, E0=DF, E1=DF, E2=DF, E3=DF, E4=DF, E5=DF, E6=DF, E7=DF, BM=BALANCE, LC=HDB3; ADD EPICFG: FN=0, SLN=1, LM=E1, E0=DF, E1=DF, E2=DF, E3=DF, E4=DF, E5=DF, E6=DF, E7=DF, BM=BALANCE, LC=HDB3; /*Configure the clock reference source and set its work mode to Automatic.*/*/ SET CKICFG: WM=AUTO; /*Enable the system to use the clock signal extracted from E1 0 of the WEPI in slot 0.*/ ADD BOSRC: FN=0, SLN=0, EN=0; /*Add an IMA link group, and set the IMA group ID to 0.*/ ADD IMAGRP: MN=132, IGN=0, IID=0, IVR=VER1.1; /*Add a link for IMA link group 0.*/ ADD IMALNK: MN=132, IGN=0, IPN=0; /*Add a PVC link.*/ ADD PVCLNK: PLN=0, VPI=0, VCI=1, PCR=1920, SCR=1920, MCR=1920, SDMN=132, SHMN=134, BT=IMA, IGN=0; /*Add an OSTA 2.0 subrack.*/ ADD SFRM: FN=30, SHN=0, PN=2; /*You can run the LST SFRM command to check whether the OSTA 2.0 subrack is added.*/ /*You can run the LST SBRD command to query the boards added to the OSTA 2.0 subrack.*/ /*Add OSTA 2.0 boards.*/ /*Add the DMUs in slots 0 and 2.*/ ADD SBRD: FN=30, SLN=0, LOC=FRONT, BT=DMU, MN=216, BAPORT=16504; ADD SBRD: FN=30, SLN=2, LOC=FRONT, BT=DMU, MN=217, BAPORT=16504; /*Add the DRUs in slots 1 and 3.*/ ADD SBRD: FN=30, SLN=1, LOC=FRONT, BT=DRU, MN=218, BAPORT=16504; ADD SBRD: FN=30, SLN=3, LOC=FRONT, BT=DRU, MN=219, BAPORT=16504; /*Add the SCUs in slots 4 and 8.*/ ADD SBRD: FN=30, SLN=4, LOC=FRONT, BT=SCU, MN=220, BAPORT=16504, FBPORT=16500; ADD SBRD: FN=30, SLN=8, LOC=FRONT, BT=SCU, MN=221, BAPORT=16504, FBPORT=16500; /*Add the DSUs in slots 5 and 9.*/ ADD SBRD: FN=30, SLN=5, LOC=FRONT, BT=DSU, MN=222, BAPORT=16504;

Issue 04 (2009-01-15)


2-21



ADD SBRD: FN=30, SLN=9, LOC=FRONT, BT=DSU, MN=223, BAPORT=16504; /*Add two BSUs in slots 11 and 13 of subrack 30, and enable the two BAMs to work in active/standby mode.*/ ADD SBRD: FN=30, SLN=11, LOC=FRONT, BT=BSU, MN=212, ASS=13; /*Add an ETU in slot 12.*/ ADD SBRD: FN=30, SLN=12, LOC=FRONT, BT=ETU, MN=249, BAPORT=16504; /*You can run the LST SBRD command to query the board configuration.*/ /*Set the location ID of the local site.*/ SET LOCALSITE: LOCID=1, IP1="172.18.100.0", MSK1="255.255.255.0", IP2="172.19.100.0", MSK2="255.255.255.0"; /*Add a cluster.*/ ADD CLUSTER: CID=12, CT=DSU; ADD CLUSTER: CID=13, CT=DSU; ADD CLUSTER: CID=14, CT=DSU; /*Add nodes.*/ ADD NODE: MN=216, ADD NODE: MN=217, ADD NODE: MN=220, ADD NODE: MN=221, ADD NODE: MN=218, ADD NODE: MN=219, ADD NODE: MN=222, ADD NODE: MN=223, ADD NODE: MN=222, ADD NODE: MN=223, ADD NODE: MN=222, ADD NODE: MN=223,


/*Configure the MEM module. Set the module number to 22, local IP address 1 to 172.16.200.22, local IP address 2 to 172.17.200.22, and the subnet mask to 255.255.0.0.*/ ADD MEMCFG: MN=22, LIP1="172.16.200.22", LIP2="172.17.200.22", MSK="255.255.0.0"; /*Load the configured data to the HDU.*/ SYN HDUCFG: MN=250; /*Enable the online data configuration for the HDU.*/ SET CFGSWITCH: SW=ON; /*Enable the data formatting function.*/ SET FMT: STS=ON; /*Format the data.*/ FMT:; /*Start the online mode.*/ LON:; /*Configure the HDU data on the SMU client.*/ SET HDU: OPTYPE=ADD, HDUNAME="DMU0", HDUIP1="172.18.100.2", HDUIP2="172.19.100.2"; SET HDU: OPTYPE=ADD, HDUNAME="DMU2", HDUIP1="172.18.100.4", HDUIP2="172.19.100.4"; /*You can run the LST HDU command to query the HDU configuration.*/

2-22


Issue 04 (2009-01-15)



/*Switch on or restart (switch off and then switch on) the OSTA 1.0 subrack to load the data to all modules.*/

2.5.3 Data Configuration in IP Networking Description The HLR9820 adopts the IP networking. A rack named HLR9820 is configured. The rack is numbered 0 and placed in row 0 and column 0 in the equipment room. The rack is configured with an OSTA 1.0 basic subrack. The OSTA 1.0 basic subrack is configured with two WIFMs, two WBFIs (back boards of the WIFMs), two WCCUs, two WSMUs, two WBSGs, one WALU, and two UPWRs. Figure 2-8 shows the configuration of the OSTA 1.0 basic subrack. The IP address of the WIFM is 10.10.10.201, the subnet mask is 255.255.255.192, and the gateway IP address is 10.10.10.254. The rack is also configured with an OSTA 2.0 subrack. Figure 2-9 shows the board configuration of the OSTA 2.0 subrack. The port of the maintenance plane is numbered 16504, and the port of the service plane is numbered 16500. The location ID of the local site is 1, and the IP addresses of the Fabric network segment is 172.18.100.0 and 172.19.100.0. Figure 2-8 Board configuration of the OSTA 1.0 subrack Back 0

0

1

W C C U

W C C U

2 3

4

5

1

2 3

4

5

6 7

8 9 10 11 12 13 14 15 16 17 18 19 20

W H S C

W S I U

W S I U

W H S C

W B F I

W H S C

W B F I

6 7

8 9 10 11 12 13 14 15 16 17 18 19 20

W S M U

W S M U

W I F M

W I F M

W B S G

W B S G

W A L U

U P W R

U P W R

U P W R

Front

Issue 04 (2009-01-15)


2-23




1

F C I

2

3

4

F C I

0

1

2

3

4

5

6

7

8

9

D M U

D R U

D M U

D R U

S C U

D S U

S W U

S W U

S C U

D S U

14

5

SMM

15

6

7

S W I

S W I

8

9

10 11 12 13 G E I

G E I

G E I

10 11 12 13 I N U

B S U

E T U

B S U

SMM

Front

Example /*Enable the offline mode.*/ LOF:; /*Disable the data formatting function.*/ SET FMT: STS=OFF; /*Disable the online data configuration for the HDU.*/ SET CFGSWITCH: SW=OFF; /*Add a rack.*/ ADD SHF: SHN=0, LT="HLR9820", PN=0, RN=0, CN=0; /*Add an OSTA 1.0 subrack.*/ ADD FRM: FN=0, SHN=0, PN=3; /*You can run the LST FRM command to check whether the OSTA 1.0 subrack is added.*/ /*You can run the LST BRD command to query the boards added to the OSTA 1.0 subrack.*/ /*Set the board type.*/ SET BRDTYPE: BT=B; /*Add boards and module numbers.*/ /*Add the WCCUs.*/ ADD BRD: FN=0, SLN=0, LOC=FRONT, BT=WCCU, MN=22, ASS=1; /*Add the WIFMs and the WBSGs.*/ ADD BRD: FN=0, SLN=12, LOC=FRONT, BT=WIFM, MN=132, ASS=13; ADD BRD: FN=0, SLN=14, LOC=FRONT, BT=WBSG, MN=133; ADD BRD: FN=0, SLN=15, LOC=FRONT, BT=WBSG, MN=134; /*Configure the FE port data for the WIFMs.*/ ADD FECFG: MN=132, IP="10.10.10.201", MSK="255.255.255.192", DGW="10.10.10.254";

2-24


Issue 04 (2009-01-15)



/*Add an OSTA 2.0 subrack.*/ ADD SFRM: FN=30, SHN=0, PN=2; /*You can run the LST SFRM command to check whether the OSTA 2.0 subrack is added.*/ /*You can run the LST SBRD command to query the boards added to the OSTA 2.0 subrack.*/ /*Add OSTA 2.0 boards.*/ /*Add the DMUs in slots 0 and 2.*/ ADD SBRD: FN=30, SLN=0, LOC=FRONT, BT=DMU, MN=216, BAPORT=16504; ADD SBRD: FN=30, SLN=2, LOC=FRONT, BT=DMU, MN=217, BAPORT=16504; /*Add the DRUs in slots 1 and 3.*/ ADD SBRD: FN=30, SLN=1, LOC=FRONT, BT=DRU, MN=218, BAPORT=16504; ADD SBRD: FN=30, SLN=3, LOC=FRONT, BT=DRU, MN=219, BAPORT=16504; /*Add the SCUs in slots 4 and 8.*/ ADD SBRD: FN=30, SLN=4, LOC=FRONT, BT=SCU, MN=220, BAPORT=16504, FBPORT=16500; ADD SBRD: FN=30, SLN=8, LOC=FRONT, BT=SCU, MN=221, BAPORT=16504, FBPORT=16500; /*Add the DSUs in slots 5 and 9.*/ ADD SBRD: FN=30, SLN=5, LOC=FRONT, BT=DSU, MN=222, BAPORT=16504; ADD SBRD: FN=30, SLN=9, LOC=FRONT, BT=DSU, MN=223, BAPORT=16504;

/*Add two BSUs in slots 11 and 13 of subrack 30, and enable the two BAMs to work in active/standby mode.*/ ADD SBRD: FN=30, SLN=11, LOC=FRONT, BT=BSU, MN=212, ASS=13; /*Add an ETU in slot 12.*/ ADD SBRD: FN=30, SLN=12, LOC=FRONT, BT=ETU, MN=249, BAPORT=16504; /*You can run the LST SBRD command to query the board configuration.*/ /*Set the location ID of the local site.*/ SET LOCALSITE: LOCID=1, IP1="172.18.100.0", MSK1="255.255.255.0", IP2="172.19.100.0", MSK2="255.255.255.0"; /*Add a cluster.*/ ADD CLUSTER: CID=12, CT=DSU; ADD CLUSTER: CID=13, CT=DSU; ADD CLUSTER: CID=14, CT=DSU; /*Add nodes.*/ ADD NODE: MN=216, ADD NODE: MN=217, ADD NODE: MN=220, ADD NODE: MN=221, ADD NODE: MN=218, ADD NODE: MN=219, ADD NODE: MN=222, ADD NODE: MN=223, ADD NODE: MN=222, ADD NODE: MN=223, ADD NODE: MN=222, ADD NODE: MN=223,


/*Configure the MEM module. Set the module number to 22, local IP address 1 to 172.16.200.22, local IP address 2 to 172.17.200.22, and the subnet mask to 255.255.0.0.*/

Issue 04 (2009-01-15)


2-25



ADD MEMCFG: MN=22, LIP1="172.16.200.22", LIP2="172.17.200.22", MSK="255.255.0.0"; /*Load the configured data to the HDU.*/ SYN HDUCFG: MN=250; /*Enable the online data configuration for the HDU.*/ SET CFGSWITCH: SW=ON; /*Enable the data formatting function.*/ SET FMT: STS=ON; /*Format the data.*/ FMT:; /*Start the online mode.*/ LON:; /*Configure the HDU data on the SMU client. SET HDU: OPTYPE=ADD, HDUNAME="DMU0", HDUIP1="172.18.100.2", HDUIP2="172.19.100.2"; SET HDU: OPTYPE=ADD, HDUNAME="DMU2", HDUIP1="172.18.100.4", HDUIP2="172.19.100.4"; /*You can run the LST HDU command to query the HDU configuration.*/ /*Switch on or restart (switch off and then switch on) the OSTA 1.0 subrack to load the data to all modules.*/

2-26


Issue 04 (2009-01-15)


3


Local Office Data Configuration

About This Chapter The local office information refers to the basic information of the HLR. It includes the SAU and SMU local office type, network type, and service type. The HLR can process services only after the local office data is configured. 3.1 Basic Concepts 3.2 Data Configuration Procedure 3.3 Data Configuration Example

Issue 04 (2009-01-15)


3-1



3.1 Basic Concepts 3.1.1 Local Office Information 3.1.2 Called Prefix 3.1.3 SPC

3.1.1 Local Office Information The HLR9820 local office information includes the following two parts: l

l

SAU local office information –

Local office type

–

Network type

–

Local SPC

SMU local office information –

Network type

–

Country code

–

Mobile country code

–

Mobile network code

–

System ID

–

Switch ID

–

Default PL

–

System resource data

3.1.2 Called Prefix A called prefix is a number segment truncated from a called number from the first digit. Its length is less than or equal to that of the called number. For details on the use of the called prefix, see ADD CALLEDNA.

3.1.3 SPC The signaling point code (SPC) is the code used in the Signaling System No.7 (SS7) network. The signaling point (SP) is identified by the SPC. The originating signaling point (OSP) is the point from which a signaling message is originated. The destination signaling point (DSP) is the point to which a signaling message is destined. Generally, the international SPC is 14-bit long. The SPC must be configured based on the actual condition.

3.2 Data Configuration Procedure 3-2


Issue 04 (2009-01-15)



There is no clearly-defined procedure for configuring the local office data. The sequence presented in this section is recommended. The local office data must be configured on the following clients: l

HLR9820 LMT: Configure the local office information of the SAU and add local SPCs. The latter operation is optional.

l

HLR9820 SMU client: Configure the SMU global data and the system resource data. NOTE

l

In the HLR9820, the country code and global title (GT) (used for SCCP signaling processing) set in the Local Office Information table on the SAU must be consistent with the country code and HLR number (that is, Sender IN, used for MAP signaling processing) set in the Local Office Information table on the SMU client.

l

It takes time for the local fastDB to update its global data after the global data is loaded. The time is determined by the Interval of global table refresh parameter set by using the SET MAPSERV command.

Table 3-1 lists the procedure for configuring the local office data. Table 3-1 Data configuration procedure Operation Client

Data Configuration Procedure

Command

LMT

Configure the local office information.

SET OFI

Add a local SPC.

ADD OFI

Set the local office information.

SET INTROFF

Add a domestic longdistance area code.

ADD DAREA

Add a country code or an area code.

ADD CNTRCD

Add a VLR type.

ADD VLRTYP

Add an SGSN type.

ADD SGSNTYP

Configure MAP service parameters.

SET MAPSERV

Configure MAP configuration parameters.

SET MAPCONF

Add a forbidden forwarded-to number (FTN).

ADD FRFWDNO

Add a record to the MSISDN area code table.

ADD ISDNARC

Add a record to the IMSI area code table.

ADD IMSIARC

SMU client

Issue 04 (2009-01-15)


3-3



Operation Client

Data Configuration Procedure

Command

Add the unstructured supplementary service data (USSD).

ADD USSDDAT

Add the called number analysis data.

ADD CALLEDNA

Set the FTN conversion rule.

SET FTNTRANS

Add the information of an FTN.

ADD FTNNCS

Set the default notification to calling subscriber (NCS) attributes.

SET DEFNCS

Add the CAMELRoaming-Agreement template.

ADD CAMELROAMTPL

Add the CAMELInterrogation-Agreement template.

ADD CAMELINTERTPL

Set the default NCC template for the VLR and the SGSN.

SET DEFNCC

Set the FTN segment restriction.

SET BWFTN

Set the short message center (SMC) address restriction.

SET BWADDR

Set the roaming restriction state of the subscribers defined in the HLR.

MOD HLRRR

Configure the service entity list.

SET SELIST

Configure the alternative handling of unsupported services.

SET NONSUPHND

3.3 Data Configuration Example 3.3.1 Description 3.3.2 Example 3-4


Issue 04 (2009-01-15)



3.3.1 Description Table 3-2 lists the data configuration of the local office. Table 3-2 Data configuration of the local office Configuratio n Item

Data Configuration

HLRSN

2

SP

National network code

National reserved network valid

International network valid

International reserved network valid

EE0000

NO

NO

NO

Mobile network information

Local GT

Country code

Local area code

-

86138755

86

755

-

MAP information

Support USSD

Support MAP protocol of 0902 620 version

CAMEL supported by VLR

Maximum times of call forwarding

TRUE

FALSE

PHASE1

3

Support message waiting information

Cancel short message center address

Repetition times of ALERT_SC failure

Forwarded-to area limitation

TRUE

FALSE

3

NORESTRICTIO N

Number structure limitation

MAP version

Support ATI

Support GPRS short message

NORESTRICTI ON

GSMPHASE3

TRUE

TRUE

3.3.2 Example NOTE

l

If the HLR supports the redundancy configuration or virtual HLR function, the HLR serial number must be specified for running certain commands.

l

If the HLR does not support the redundancy configuration or virtual HLR function, the HLR serial number need not be specified for running certain commands.

Data configuration here assumes that the HLR supports the redundancy configuration or virtual HLR function. /*On the LMT, configure the information of the local SP.*/ SET OFI: OFN="HLR", LOT=CMPX, IN=NO, IN2=NO, NN=YES, NN2=NO, SN1=NAT,

Issue 04 (2009-01-15)


3-5



SN2=NAT, SN3=NAT, SN4=NAT, NPC="EE0000", NNS=SP24, LAC=K'755, LNC=K'86, LOCGT="86138755"; /*Data configuration on the SMU client---BEGIN*/ /*Add the local office information.*/ SET INTROFF: LHLRNO="86138755", CCODE="86"; /*Set the MAP service parameters.*/ SET MAPSERV: MAXTIMECALLFWD=3, ALERTSCREP=3, FWDAREALIMIT=NORESTRICTION, NUMSTRUCTLIMIT=NORESTRICTION, MAPVER=GSMPHASE3, CMCCSUPP=PHASE1; /*Add a domestic long distance area code.*/ ADD DAREA: HLRSN=2, AREACODE="755",CNAME="SHENZHEN"; /*Add a country code.*/ ADD CNTRCD: CNTRCODE="86", CNAME="China"; /*Add a VLR type.*/ ADD VLRTYP: HLRSN=2, VLRPREFIX="86136111", VLRNAME="VLR1", TYPE=LOCALDOMESTIC; /*Set the MAP configuration parameters.*/ SET MAPCONF: MWISUPP=TRUE, CANCELSC=FALSE, TIMEINTRSUPP=TRUE, GPRSSMSUPP=TRUE, USSDSUPP=TRUE, MAPVERSUPP=FALSE; /*Add a forbidden forwarded-to number.*/ ADD FRFWDNO: HLRSN=2, FWDNO="112"; /*Add the mapping between an MSISDN and an area code.*/ ADD ISDNARC: HLRSN=2, ISDNPREFIX="138755", AREACODE="755"; /*Add the mapping between an IMSI and an area code.*/ ADD IMSIARC: HLRSN=2, IMSIPREFIX="46007755", AREACODE="755"; /*Add the USSD control data.*/ ADD USSDDAT: HLRSN=2, SRCODE="168", FUNCTION=GSMMODE, FWDADD="86123999"; /*Add the called number analysis data.*/ ADD CALLEDNA: HLRSN=2, CALLPREFIX="138", SERPROP=PLMN, INFOFLAG=FALSE, ENTERFLAG=FALSE; ADD CALLEDNA: HLRSN=2, CALLPREFIX="168", SERPROP=LOCAL, INFOFLAG=FALSE, ENTERFLAG=TRUE; ADD CALLEDNA: HLRSN=2, CALLPREFIX="1860", SERPROP=LOCAL, INFOFLAG=TRUE, ENTERFLAG=FALSE; ADD CALLEDNA: HLRSN=2, CALLPREFIX="0", SERPROP=NATIONAL, INFOFLAG=FALSE, ENTERFLAG=FALSE; ADD CALLEDNA: HLRSN=2, CALLPREFIX="1", SERPROP=LOCAL, INFOFLAG=FALSE, ENTERFLAG=FALSE; ADD CALLEDNA: HLRSN=2, CALLPREFIX="2", SERPROP=LOCAL, INFOFLAG=FALSE, ENTERFLAG=FALSE; ADD CALLEDNA: HLRSN=2, CALLPREFIX="3", SERPROP=LOCAL, INFOFLAG=FALSE, ENTERFLAG=FALSE; ADD CALLEDNA: HLRSN=2, CALLPREFIX="4", SERPROP=LOCAL, INFOFLAG=FALSE, ENTERFLAG=FALSE; ADD CALLEDNA: HLRSN=2, CALLPREFIX="5", SERPROP=LOCAL, INFOFLAG=FALSE, ENTERFLAG=FALSE; ADD CALLEDNA: HLRSN=2, CALLPREFIX="6", SERPROP=LOCAL, INFOFLAG=FALSE, ENTERFLAG=FALSE; ADD CALLEDNA: HLRSN=2, CALLPREFIX="7", SERPROP=LOCAL, INFOFLAG=FALSE, ENTERFLAG=FALSE; ADD CALLEDNA: HLRSN=2, CALLPREFIX="8", SERPROP=LOCAL, INFOFLAG=FALSE, ENTERFLAG=FALSE;

3-6


Issue 04 (2009-01-15)



ADD CALLEDNA: HLRSN=2, CALLPREFIX="9", SERPROP=LOCAL, INFOFLAG=FALSE, ENTERFLAG=FALSE; /*Data configuration on the SMU client---END*/

Issue 04 (2009-01-15)


3-7


4


Signaling Data Configuration

About This Chapter The signaling data refers to the data such as the SP, link, and routing data configured for different networking modes (TDM, ATM-2M, or IP). The configuration of the signaling data guarantees the communication between the HLR and other network elements. 4.1 Basic Concepts 4.2 Data Configuration Procedures 4.3 MTP Data Configuration Procedure 4.4 MTP3B Data Configuration Procedure 4.5 M3UA Data Configuration Procedure 4.6 SCCP Data Configuration Procedure 4.7 Data Configuration Examples

Issue 04 (2009-01-15)


4-1



4.1 Basic Concepts 4.1.1 MTP-Specific Concepts 4.1.2 MTP3B-Specific Concepts 4.1.3 SIGTRAN-Specific Concepts 4.1.4 SCCP-Specific Concepts 4.1.5 Signaling Data Configuration Principles

4.1.1 MTP-Specific Concepts MTP Protocol Stack The Message Transfer Part (MTP) of narrowband is based on the conventional TDM transmission system. MTP implements the following functions: l

Providing reliable transfer of signaling messages

l

Taking measures to reduce message loss, repetition, and out-of-sequence in the case of a signaling network failure, thus ensuring reliable message transfer

MTP comprises three parts: l

Signaling data link (MTP1)

l

Signaling link (MTP2)

l

Signaling network (MTP3)

Figure 4-1 shows the structure of the MTP protocol stack. Figure 4-1 Structure of the MTP protocol stack

ISUP

SCCP

MTP3 MTP2 MTP1 MTP

4-2

ISUP: Integrated Services Digital Network User Part

SCCP: Signaling Connection Control Part

MTP1: Message Transfer Part Level 1



Issue 04 (2009-01-15)




MTP OSP In the HLR9820, a local SP is an OSP. To define an MTP OSP, you need to specify the following information: l

SPC of the OSP

l

Network indicator (NI) of the OSP

l

Whether the OSP provides SCCP-layer functions

l

Whether the OSP provides the STP function

The HLR9820 provides the multi-SP function. In the same signaling network, a maximum of 16 originating signaling point codes (OPCs) can be defined for one HLR9820. Therefore, the SPs of the local office can map the same DSP. If a physical node is classified into N SPs, because 16 links can be set between an OPC and a DSP, the total number of inks between the physical node and the remote SP is up to N×16.

MTP DSP To define an MTP DSP, you need to specify the following information: l

SPC of the DSP

l

NI of the DSP

l

OSPs relating to the DSP

l

Adjacent flag (whether the DSP and the OSP are directly connected through a link)

l

Selection mask of the link set in the route destined for this DSP

l

Whether the DSP provides the STP function

Generally, the HLR and MSC adopt 14-bit SPC. The DSPs that need to be set in the local office and the network topology are determined by the carrier. The DSPs that connect to the local office through direct links must be set, such as DPC 1 and the STP in Figure 4-2. For the DSPs that have no direct link connection with the local office, for example, DPC 2 in Figure 4-2, whether the DSPs should be set depends on the addressing mode specified by the carrier. If the DPC or DPC + SSN addressing is used, the DSPs must be set in the local office. If the GT addressing is used, the DSPs need not be set.

Issue 04 (2009-01-15)


4-3



Figure 4-2 Configuration of the DSPs

DPC1

DPC2

STP

Local office Signaling link No signaling connecyion but with signaling association DPC: Destination Signaling Point Code

STP: Signaling Transfer Point

If the DSP is an adjacent SP, that is, the DSP has a direct link connection with the local office, you also need to define a link set.

Associated and Quasi-Associated Modes In the associated mode, signaling messages are transmitted between two SPs through a direct link, as shown in Figure 4-3. Figure 4-3 Associated mode

SPA OPC:=SPA DPC:=SPB

SPB OPC:=SPB DPC:=SPA

SP: Signaling Point

OPC: Originating Signaling Point Code

DPC: Destination Signaling Point Code

In the quasi-associated mode, signaling messages are transmitted between two SPs through multiple series links, as shown in Figure 4-4. In the quasi-associated mode, the STP does not change the OPC and DPC in the signaling message. If the DPC or DPC + SSN addressing is adopted to transfer MAP messages between two SPs without a direct link, the quasi-associated mode must be used between the two SPs. If the GT addressing is adopted to transfer MAP messages, the MAP messages are transferred through the STP after GT translation, as shown in Figure 4-5. 4-4


Issue 04 (2009-01-15)



Figure 4-4 Quasi-Associated mode STP

OPC:=SPA DPC:=SPB

OPC:=SPA DPC:=SPB OPC:=SPB DPC:=SPA OPC:=SPB DPC:=SPA

SPA

SPB

Figure 4-5 Inter-SP communication through the STP STP

OPC:=STP DPC:=SPB OPC:=SPA DPC:=STP OPC:=SPB DPC:=STP OPC:=STP DPC:=SPA SPA

SPB

MTP Link An MTP link is a physical link that connects various SPs and STPs and transmits signaling messages. MTP uses the signaling link code (SLC) to identify different links in a link set. The signaling link code send (SLCS) is the code sent to the remote signaling entity for identifying the link. In the normal case, the SLC and the SLCS should be configured with the same value. In addition, the remote signaling entity link connected with the local end should also be configured with the same SLC and SLCS. The SLCs in the same link set must be uniformly numbered, no matter whether they are allocated to the same WCSU. During the self-loop test of the link, the SLC is different from the SLCS. The SLC of link 1 must be the same as the SLCS of link 2. The SLC of link 2 must be the same as the SLCS of link 1. Issue 04 (2009-01-15)


4-5



MTP Link Set A number of parallel MTP links that directly connect two SPs constitute an MTP link set. To define an MTP link set, you need to specify the following information: l

Link set number

l

Adjacent DSPs connecting by the link set

l

Link selection mask

Each link set contains up to 16 links. The link selection mask applies to implementation of loadsharing among the links in the same link set. NOTE

l

At most one link set can be set between two adjacent SPs.

l

A link is the basic unit in a link set.

l

A link set can contain one or more links.

MTP Route An MTP route is the path through which signaling messages are transferred between two SPs. To define an MTP route, you need to specify the following information: l

DSP index

l

Link set number

l

Route priority

A route specifies the mapping between the DSP and the link set. That is, the route determines which link set is used to transmit signaling messages to the DSP. One route maps only one link set, and one link set can map multiple routes. The routes destined for one DSP can be classified into direct routes and alternative routes. The direct route indicates that no STP is on the route between the local office and the DSP. The alternative route is the route on which signaling messages are transferred to the DSP through STPs. The link set mapping the direct route is the one between the OSP and the DSP. The link set mapping the alternative route is the one between the OSP and the STP. If the routes destined for a DSP contain direct routes and alternative routes, you can specify the priorities of the routes to enable the signaling messages to use the direct route as the first choice and the alternative route as the second one. The smaller the value is, the higher the priority will be. At most 16 routes with the same priority level can be set for a DSP. These routes can perform load sharing. As shown in Figure 4-6, two routes exist between SP A and SP C, including a direct route AC and an alternative route A-B-C. Direct route A-C maps link set 1, and alternative route A-BC maps link set 2.

4-6


Issue 04 (2009-01-15)



Figure 4-6 Direct route and alternative route

Li

nk

se

t1

C

A

B Link set 2

Load Sharing The load-sharing modes can be classified into: l

Load sharing of links in one link set

l

Load sharing of links among different link sets

For the load sharing of links in one link set, the traffic is shared by the links in the same link set. The links are selected according to the Signaling Link Selection Code (SLS). Figure 4-7 shows the load sharing in one link set. Figure 4-7 Load sharing in one link set

SLS=XXX0 B

A SLS=XXX1 SLS: Signaling Link Selection Code

For the load sharing of links among different link sets, the traffic is shared by the links in different link sets. The links are selected according to the signaling link selection mask. Figure 4-8 shows the load sharing among different link sets. Figure 4-8 Load sharing among different link sets

A

D

XXX0

E

B Link fault between E and C

Link destined for B Link destined for C

Issue 04 (2009-01-15)

XXX1 XXXX


F

C

4-7



Although the same link set is used, the signaling messages destined for different DSPs can be distributed by different load-sharing modes. As shown in Figure 4-8, the same link sets (DE and DF) are used for the traffic from A to B and C. The traffic to B is shared by DE and DF according to the SLS, and only DF is used for the traffic to C because of the fault of EC. To realize the preceding two load-sharing modes, the HLR9820 uses the signaling link set selection mask and signaling link selection mask to evenly distribute signaling messages according to the SLS.

Mask Setting Principles The principles of setting the signaling link selection mask and signaling link set selection mask are as follows: l

The signaling link selection mask depends on the number of links in the same link set, and the signaling link set selection mask depends on the number of link sets. Table 4-1 lists the mapping between the number of 1s in the mask and the number of links or the number of link sets. Table 4-1 Mapping between the number of the links/link sets and the number of 1s in the mask

l

Number of Link Sets or Number of Links

Number of 1s in the Mask

1

0

2

1

3-4

2

5-8

3

9 - 16

4

The SLS plays the same role in the allocation of links and link sets. To ensure that all links in a link set can be selected, the same bit cannot simultaneously be set to 1 in the signaling link selection mask and in the signaling link set selection mask. For example, if the signaling link set selection mask is 0011 and the link set contains four links, the signaling link selection mask should be 1100. If the link set contains two links, the signaling link selection mask should be 1000 or 0100.

Mask Setting Example If there are four link sets (0, 1, 2, and 3) to one DSP and each link set has two links, the link set selection mask can be set to 1010 and the link selection mask can be set to 0100. According to the link set selection algorithm, the routing of signaling services is as shown in Figure 4-9.

4-8


Issue 04 (2009-01-15)



Figure 4-9 Routing of signaling services SLS

1

1

1

1

Mask

1

0

1

0 0 skipped over Lowest digit (bit) 2nd lowest digit (bit)

1

1 0011

００１１＝０ｘ３

% 4

Remainder Number of available signaling routes of same priority

4th signaling route 3 Conclusion: The 4th signaling route will be used to transfer signaling traffic with SLS of 1111.

The link selection algorithm is similar to the link set selection algorithm, except that the link selection mask is used instead of the link set selection mask, and the number of links is used instead of the number of routes. Table 4-2 is an example of the selection of link set and link by SLS in the case of the link set mask being 1010 and the link mask being 0100. Table 4-2 Example of the selection of link set and link by SLS Link Set Number

SLS

Link Number

SLS

0

0, 1, 4, 5

0

0, 1

1

4, 5

0

2, 3

1

6, 7

0

8, 9

1

12, 13

0

10, 11

1

14, 15

1

2

3

2, 3, 6, 7

8, 9, 12, 13

10, 11, 14, 15

The load sharing previously mentioned is implemented by the link sets of the same priority. The traffic is carried by the link sets of the lower priority only when all the link sets of the higher priority are unavailable. If multiple masks are available, you need to select one based on the actual condition. It is assumed that there are two link sets destined for a DSP. The available link set selection masks are 0001, 0010, 0100, and 1000. The SLS for TUP message is determined by the lowest Issue 04 (2009-01-15)


4-9



4 bits of the Circuit Identification Code (CIC). When the even circuit of the local office is the controlling circuit, the CICs in the TUP messages transferred are mostly even numbers. Therefore, the SLSs are mostly even numbers. l

When the link set selection mask is 0001 and SLSs are 0, 2, 4, 6, 8, 10, 12, and 14, the first link set is selected. When the link set selection mask is 0001 and SLSs are 1, 3, 5, 7, 9, 11, 13, and 15, the second link set is selected. Since the SLSs are mostly even numbers, the TUP messages from the local office cannot be evenly distributed between the two link sets.

l

When the link set selection mask is 0010 and SLSs are 0, 1, 4, 5, 8, 9, 12, and 13, the first link set is selected. When the link set selection mask is 0010 and SLSs are 2, 3, 6, 7, 10, 11, 14, and 15, the second link set is selected. In this case, the TUP messages from the local office can be evenly distributed between the two link sets.

4.1.2 MTP3B-Specific Concepts Broadband MTP Structure The broadband MTP provides signaling transmission services through the ATM network. It comprises MTP3B and SAAL, as shown in Figure 4-10. Figure 4-10 Broadband MTP structure

SCCP/BICC/H.248 User part MTP3B

Broadband MTP

SSCF AT NNI LM SSCOP SAAL AAL5

ATM SCCP: Signaling Connection Control Part

MTP3B: Message Transfer Part Level 3 (Broadband)

SSCF: Service Specific Coordination Function

SSCOP: Service Specific Connection Oriented Protocol

SAAL: Signaling ATM Adaptation Layer

AAL5: ATM Adaptation Layer 5

ATM: Asynchronous Transfer Mode

SAAL is a general term for SSCF and SSCOP. It provides reliable data transmission services for the upper-layer protocol. 4-10


Issue 04 (2009-01-15)



AAL5 implements the following two functions: l

Splitting the user data from the upper layer into fixed length (48 bytes) and adding an ATM header to each message

l

Removing the ATM headers of the ATM cells sent from the lower layer, reassembling the data, and submitting the complete data to the user part

When the ATM-2M mode is used, two signaling entities communicate with each other through the E1 cable.

MTP3B Function MTP3B is responsible for transferring signaling messages and managing signaling networks and signaling links. It uses the services provided by SAAL to exchange messages. In other words, MTP3B transfers the signaling messages from SAAL to the corresponding link or transfers the messages from the link layer to the upper-level SCCP. The MTP3B function module comprises the following two parts: l

Signaling message management It guarantees that the signaling messages from the user part of a certain SP are sent to the destination user part specified by the specific field in the message signaling unit.

l

Signaling network management It provides the capabilities of reconstructing the signaling network in the case of a network failure. The capabilities include the use and positioning of new signaling links.

MTP3B implements the following functions: l

Managing networks, such as link prohibition, link activation, and SP status query

l

Identifying link failures through signaling monitoring

MTP3B OSP An OSP is also a local SP. To define an MTP3B OSP, you need to specify the following information: l

SPC of the OSP

l

NI of the OSP

MTP3B DSP To define an MTP3B DSP, you need to specify the following information: l

SPC of the DSP

l

NI of the DSP

l

OSPs relating to the DSP

l

Adjacent flag (whether the DSP and the OSP are directly connected through a link)

l

Selection mask of the link set in the route destined for this DSP

l

Whether the DSP provides the STP function

The MTP3B DSPs construct the signaling network topology that the local MTP3B SP resides. Issue 04 (2009-01-15)


4-11



According to the location of the local SP, the DSPs can be classified into adjacent DSPs and non-adjacent DSPs. Two SPs connecting by a direct signaling link are called adjacent SPs, and two SPs without a direct signaling link but with a direct speech channel are called non-adjacent SPs. The DPC, a hexadecimal number, refers to the code of a specific SP in the international, international reserved, national, or national reserved network. The DSPs that need to be set in the local office and the network topology are determined by the carrier. The DSPs that connect to the local office through direct links must be set, such as DPC 1 and the STP in Figure 4-11. For the DSPs that have no direct link connection with the local office, for example, DPC 2 in Figure 4-11, whether the DSPs should be set depends on the addressing mode specified by the carrier. If the DPC addressing is used, the DSPs must be set in the local office. If the GT addressing is used, the DSPs need not be set. Figure 4-11 Configuration of the DSPs

DPC2

STP

DPC1

Local office

Signaling link No signaling link connection but with signaling association

SP: Signaling Point




If the DSP is an adjacent SP, that is, the DSP has a direct link connection with the local office, you also need to define a link set.

MTP3B Link To define an MTP3B link, you need to specify the following information:

4-12

l

Link set number

l

SLC

l

PVC link number

l

Link priority


Issue 04 (2009-01-15)



NOTE

l

The link set number and SLC uniquely identify an MTP3B link.

l

The SLC is unique in a link set.

The MTP3B Link table describes static features of links from a local MTP3B OSP to an adjacent MTP3B SP. After adding an MTP3B link set, you must add MTP3B links for the link set. The SLCs of the SPs connected by a link must be the same.

MTP3B Link Set To define an MTP3B link set, you need to specify the following information: l

Link set index

l

Adjacent DSPs connecting by the link set

l

Link selection mask

The MTP3B Link Set table describes the common static features of all links from a local SP to an adjacent MTP3B SP. An MTP3B link set is a collection of the parallel links connecting two adjacent SPs. The mask in the link set is used to implement load sharing among links.

MTP3B Route To define an MTP3B route, you need to specify the following information: l

DSP index

l

Link set index

l

Route priority

An MTP3B route transfers signaling messages between two SPs.

4.1.3 SIGTRAN-Specific Concepts The Signaling Transport (SIGTRAN) protocol supports transmission of the switched circuit network (SCN) signaling across the IP network. This protocol supports the inter-layer standard primitive interface defined in the SCN signaling protocol hierarchy model to ensure the utilization of the existing SCN signaling application without modification. It uses the standard IP transport protocol as the transmission bottom layer and satisfies the special transmission requirements of the SCN signaling by adding extra functions. The SIGTRAN protocol stack comprises two types of protocols: l

Transmission protocols: including SCTP and IP

l

Adaptation protocols: including M3UA

Figure 4-12 shows the model of the SIGTRAN protocol stack.

Issue 04 (2009-01-15)


4-13



Figure 4-12 Model of the SIGTRAN protocol stack

M3UA adaptation layer SCTP IP MAC M3UA: SS7 MTP3-User Adaptation Layer

SCTP: Stream Control Transmission Protocol

IP: Internet Protocol

MAC: Media Access Control

Client/Server Working Mode of the SCTP Association The SIGTRAN protocol uses the SCTP as the transport layer. Since the SCTP association works in client/server mode, to ensure normal function of the SIGTRAN protocol, the working mode of each device in the SCTP association must be specified. In the normal situation, when a device serves as a signaling gateway, in an SCTP association, configure the device as the server and the peer device as the client.

Symmetry and Asymmetry Networking Modes of the M3UA Protocol It is assumed that two devices communicate with each other through the SIGTRAN protocol. If the application server (AS) is used at the local end and the signaling gateway (SG) is used at the peer end, this type of networking is called asymmetry networking mode. If the AS or SG is used at both ends, this type of networking is called symmetry networking mode. In the SIGTRAN protocol family, the protocols such as M2UA, V5UA, and IUA support only the asymmetry networking mode. The M3UA protocol supports both the symmetry and asymmetry networking modes.

M3UA Local Entity An M3UA local entity is a logical entity. It implements some special functions at the local end. An M3UA local entity includes the configuration information that affects its own functional features. For example, you can configure an M3UA local entity as an SG. An M3UA local entity is identified by an SPC and a unique local entity number. As the SS7 MTP3-user adaptation layer, M3UA provides basic call services for MTP3 users over IP network. It applies to the access device such as an SG at the edge of a network. M3UA implements the interworking between TDM SS7 and IP. In addition, it provides end-to-end communication between MTP3 users, thus implementing signaling interaction in the IP core network.

4-14


Issue 04 (2009-01-15)



M3UA Destination Entity An M3UA destination entity is a logical entity connecting with an M3UA local entity. According to the link connection mode, M3UA destination entities can be classified into: l

Adjacent M3UA destination entity

l

Non-adjacent M3UA destination entity

An M3UA destination entity can be an AS, SG, or SP. Similar to an M3UA local entity, an M3UA destination entity is identified by an SPC and a unique destination entity number.

M3UA Link Set An M3UA link set is the collection of all M3UA links between a local entity and an adjacent destination entity.

M3UA Route An M3UA route is a transmission path between a local entity and a destination entity. In the local end, an M3UA route maps an M3UA link set. Thus, the M3UA route sets up the association between an M3UA destination entity and an M3UA link set. Each configured M3UA destination entity sets up an M3UA route to an adjacent destination entity through the specified M3UA link set. When an M3UA link set is active, its mapping M3UA route is available. Otherwise, the M3UA route is unavailable.

M3UA Link An M3UA link is a communication path established after an SCTP connection is set up. Each M3UA link connects two SCTP endpoints. The IP addresses and the port numbers of the two SCTP endpoints uniquely identify an SCTP connection and also an M3UA link. An M3UA link can be configured as a client link or a server link. The configuration mode determines the setup of an SCTP connection. The link at the client end sets up SCTP connections, and the link at the server end receives connection requests. Therefore, to set up an SCTP connection successfully, you must configure one SCTP end as a client and the other end as a server. An M3UA link belongs to an M3UA link set.

Application Server An AS is a logical entity serving the specific routing keyword. l

If an AS serves as a virtual switching unit, it processes the calls from all SCN trunks identified by the DPC, OPC, and CIC in the SS7 network.

l

If an AS serves as a virtual database, it processes the transactions identified by the DPC, OPC, and SCCP_SSN combination in the SS7 network.

Each AS contains a set of unique application server processes (ASPs), of which one or more active ASPs process services.

Application Server Process An ASP is a process instance of an AS. Each ASP can be an active or a standby process of an AS. For example, an ASP can be an MGC, IP SCP, or IP HLR process. Each ASP contains an SCTP endpoint and can serve a number of ASs. Issue 04 (2009-01-15)


4-15



IP Server Process An IP service process (IPSP) is an IP-based process instance. The IPSP is essentially the same as the ASP. The difference is that the IPSP uses point-to-point M3UA rather than SG services.

Signaling Gateway A signaling gateway (SG) receives or sends SS7 upper-layer user messages at the edge of the IP and SS7 networks. An SG is an SP in the SS7 network. It contains one or more signaling gateway processes (SGPs). When an SG contains several SGPs, it is a logical entity. The SGPs of the SG are coordinated to independent management views for the SS7 network and the supported AS.

Signaling Gateway Process An SGP is a process instance of an SG. It can serve as an active, a standby, or a load-sharing process of an SG.

4.1.4 SCCP-Specific Concepts Working Mode of an SCCP DSP An SCCP DSP can work in the following three modes: l

Independent working mode In this mode, the DSP does not have a standby DSP.

l

Active/standby working mode In this mode, the DSP is configured with a standby SP. During routing, if the DSP is available, SCCP sends messages to the DSP directly. If the DSP is unavailable, SCCP sends messages to the standby DSP.

l

Load-sharing working mode In this mode, the DSP is also configured with a standby SP. During routing, if the two DSPs are available, SCCP sends messages to them alternatively. If only one DSP is available, SCCP sends all the messages to that DSP.

An SCCP DSP can map multiple virtual OSPs in the local office. SCCP uses the cyclic mode for processing the messages destined for the DSP. That is, SCCP sequentially selects the virtual OSPs mapping the DSP, one at a time, as the OPC for the MTP message.

SCCP Subsystem As the local addressing information used by SCCP, a subsystem number (SSN) identifies the SCCP users of the same network node. If the network node does not serve as an STP only, you must assign an SSN to each SCCP subsystem (SCCP user). The SSN is unique in the entire network. Inside a signaling network, an SSN is used as the address of a subsystem. SCCP users can be classified into two types: l

SCCP users of the local SP, that is, local subsystems

l

SCCP users of other SPs, that is, remote subsystems

For different network nodes, you need to assign subsystems based on users. In addition, you need to set up subsystems for the remote SCCP users under the control of the local SCCP. 4-16


Issue 04 (2009-01-15)



Table 4-3 presents the number assignment for the subsystems related to the HLR. Table 4-3 Number assignment for the subsystems related to the HLR Subsystem

Number

HLR

00000110

VLR

00000111

MSC

00001000

AuC

00001010

SMC

11101110

SCP

11101111

SCCP Route l

Address information The address formats available for SCCP are as follows: –

DPC

–

DPC + SSN/GT (or both)

A DPC is the destination point code used by MTP. An SSN identifies the SCCP users of the same node. A GT is usually a dial-up number, for example, an international phone number, a national phone number, or a mobile directory number (MDN). The GT does not directly reflect the routing information in the signaling network. Thus, the address information can only be obtained through GT translation. Different from the DPC, which is valid only in the defined signaling network, the GT is valid globally. The address scope of the GT is much larger than that of the DPC. The GT enables transmission of circuit-unrelated messages between two SPs worldwide. The powerful addressing capability of the GT is an important feature of SCCP. l

GT type The type of a GT is indicated by the GT indicator in the SCCP calling and called addresses. Table 4-4 lists an example of the GT indicator. Table 4-4 GT indicator 8

7

6543

2

1

Reserved

Routing indicator

GT indicator

SSN indicator bit

SPC indicator bit

Bit 1: indicates whether an SPC is present in the address. –

1: An SPC is present.

–

0: No SPC is present.

Bit 2: indicates whether an SSN is present in the address. Issue 04 (2009-01-15)


4-17


4 Signaling Data Configuration –

1: An SSN is present.

–

0: No SSN is present.

Bits 6, 5, 4, and 3: indicate the composition of a GT. The following table lists the composition of a GT. 0000

The address does not contain the GT.

0001

The GT contains only the address nature indicator.

0010

The GT contains only the translation type.

0011

The GT contains the translation type, numbering plan, and encoding scheme.

0100

The GT contains the translation type, numbering plan, encoding scheme, and address nature indicator.

0101-0111

International reserved.

1000-1110

National reserved.

1111

Reserved for expansion.

Bit 7: indicates the routing mode SCCP should use. –

0: SCCP selects the routing mode according to the GT in the address field.

–

1: SCCP selects the routing mode according to the DPC in the MTP routing identifier and the SSN in the called address.

Bit 8: reserved. l

SCCP routing principles Both the MTP and SCCP layers have the signaling routing function. The MTP layer selects routes according to the SPC, and the SCCP layer obtains the SPC of the peer end through GT translation and then sends the SPC to the MTP layer for routing. The following describes routing of the connectionless messages: –

Messages from the MTP layer If the routing indicator bit is 1 (routing based on DPC + SSN), the current node is the destination of the message. If the SSN is found existing, the message is sent to the corresponding user part according to its type. If the routing indicator bit is 0 (routing based on GT), the GT is translated. After the GT translation, the called address is in the format of DPC + SSN (or new GT).

–

Messages from the SCCP layer If the address of the message contains a DPC, and the DPC does not denote the current node, the message is sent to the MTP. If the address of the message contains a DPC, and the DPC denotes the current node, the message is sent to the SCCP user according to the SSN. If the message does not contain a DPC, GT translation is required.

GT Translation All signaling messages are transmitted through the MTP layer of an SS7 network. In the SS7 network, the MTP address comprises the SPC and network identifier. In the PLMN network, 4-18


Issue 04 (2009-01-15)



however, the destination addresses of signaling messages are usually indicated by other information such as the HLR number and MDN. In addition, the addresses are also used in the networks of other countries. Therefore, a function is required to translate the information into signaling addresses. The conversion process is called GT translation, which is a function provided by SCCP. SCCP can use the information to obtain the called address of an SCCP message and provide an address addressable by MTP. The GT is a universally unique address. SCCP can use the GT for message addressing. Table 4-5 lists the possible components of a GT. Table 4-5 GT components Component

Value

GT value

A number that contains up to 24 digits

Numbering plan

0001: ISDN/phone code plan (E.164)

Encoding scheme

0001: BCD code (odd numbers) 0010: BCD code (even numbers)

Address natures

0000001: subscriber number 0000011: national number 0000100: international number

Translation type

0000: not defined

These components determine how to translate GT numbers. The GT translation produces a new DPC and possibly an SSN (or a GT). The new SSN or GT is contained in a called address, and the new DPC is transferred to MTP for message routing. Table 4-6 lists the mapping between the translation result and the routing indicator. Table 4-6 Mapping between the translation result and the routing indicator Translation Result

Routing Indicator

Description

DPC

1

SSN addressing

DPC + SSN

1

SSN addressing

DPC + GT

0

GT addressing

DPC + new GT

0

GT addressing

GT Addressing When two SPs transfer MAP messages through GT addressing, the two SPs are not connected in quasi-associated mode. Instead, an STP is configured between the two SPs. The STP performs GT translation to the signaling messages before sending them out, as shown in Figure 4-13. Issue 04 (2009-01-15)


4-19



Figure 4-13 Inter-SP communication through the STP STP

OPC:=STP DPC:=SPB OPC:=SPA DPC:=STP OPC:=SPB DPC:=STP OPC:=STP DPC:=SPA SPA

SPB

SP: Signaling Point




Figure 4-14 shows the signaling processing between SPs in DPC + GT addressing mode. Figure 4-14 DPC + GT addressing

SPA

STP

SPB

SubSystem

SubSystem

SubSystem

SCCP

SCCP

SCCP

MTP

MTP

MTP

DPC+GT

DPC+SSN

SP: Signaling Point

SCCP: Signaling Connection Control Part

MTP: Message Transfer Part

GT: Global Title

SSN: Subsystem Number


As shown in Figure 4-14, SP A sends out a message in DPC + GT mode, the DPC is the signaling point code of the STP, and the GT is the global title of SP B. After receiving the MTP message from SP A, the MTP layer of the STP sends the message to the SCCP layer, which then translates the GT. The translation result is in the DPC + SSN format. The DPC is the signaling point code of SP B, and the SSN is the subsystem number of SP B. The SCCP layer of the STP sends the message to the MTP layer of the STP, which then transfers the message to SP B. 4-20


Issue 04 (2009-01-15)



NOTE

l

Whether GT addressing or DPC addressing is adopted between two SPs depends on the actual requirements of the carrier.

l

The DPC addressing mode imposes fewer load on the STP than the GT addressing mode. If the DPC addressing mode is adopted, you need to configure more data.

l

The functional entities that need to exchange MAP messages with the HLR include the MSC, SMC, and SCP.

4.1.5 Signaling Data Configuration Principles To ensure the security of the network, observe the following principles when configuring the link and routing data: 1.

The links belonging to the same office must be evenly configured on different modules. The number of links configured on a module cannot exceed the maximum number of links.

2.

When multiple routes are configured, correctly configure the selection masks of link sets and links, thus avoiding the unbalanced load among links.

3.

Configure at least two routes working in load-sharing or active/standby mode for a DSP. Avoid configuring a single route for a DSP.

4.2 Data Configuration Procedures 4.2.1 Data Configuration Procedure in TDM Networking 4.2.2 Data Configuration Procedure in ATM-2M Networking 4.2.3 Data Configuration Procedure in IP Networking

4.2.1 Data Configuration Procedure in TDM Networking Figure 4-15 shows the procedure for configuring the signaling data in TDM networking.

Issue 04 (2009-01-15)


4-21



Figure 4-15 Procedure for configuring the signaling data in TDM networking

Start

Quasi-associated connection

Add an MTP DSP ADD N7DSP Associated connection

Non-associated connection (GT)

Add an MTP link set ADD N7LKS

Add an MTP route ADD N7RT

Add an MTP route ADD N7RT Add an MTP link ADD N7LNK Add an SCCP DSP ADD SCCPDPC Add an SCCP subsystem ADD SCCPSSN Add a new GT (optional) ADD SCCPNGT Add a GT ADD SCCPGT End

4.2.2 Data Configuration Procedure in ATM-2M Networking Figure 4-16 shows the procedure for configuring the signaling data in ATM-2M networking.

4-22


Issue 04 (2009-01-15)



Figure 4-16 Procedure for configuring the signaling data in ATM-2M networking Start Add an MTP3B OSP SET MTP3BOSP


Add an MTP3B DSP ADD MTP3BDSP Associated connection

Non-associated connection (GT)

Add an MTP3B link set ADD MTP3BLKS Add an MTP3B route ADD MTP3BRT

Add an MTP3B route ADD MTP3BRT Add an MTP3B link ADD MTP3BLNK Add an SCCP DSP ADD SCCPDPC Add an SCCP subsystem ADD SCCPSSN Add a new GT (optional) ADD SCCPNGT Add a GT ADD SCCPGT End

4.2.3 Data Configuration Procedure in IP Networking Figure 4-17 shows the procedure for configuring the signaling data in IP networking.

Issue 04 (2009-01-15)


4-23



Figure 4-17 Procedure for configuring the signaling data in IP networking Start Add an M3UA local entity ADD M3LE


Add an M3UA destination entity ADD M3DE Non-associated Associated connection

connection (GT)

Add an M3UA link set ADD M3LKS Add an M3UA route ADD M3RT

Add an M3UA route ADD M3RT Add an M3UA link ADD M3LNK Add an SCCP DSP ADD SCCPDPC Add an SCCP subsystem ADD SCCPSSN Add a new GT (optional) ADD SCCPNGT Add a GT ADD SCCPGT End

4.3 MTP Data Configuration Procedure Table 4-7 lists the procedure for configuring the MTP data through the E1 interface. Table 4-7 Procedure for configuring the MTP data

4-24

Step

Operation

Command

1

Add an MTP DSP.

ADD N7DSP

2

Add an MTP link set.

ADD N7LKS

3

Add an MTP route.

ADD N7RT


Issue 04 (2009-01-15)



Step

Operation

Command

4

Add an MTP link.

ADD N7LNK

Figure 4-18 shows the relations between the MTP data tables. Figure 4-18 MTP data table relation

ADD N7DSP [DSP Index] [NI] [DPC] … ADD N7LKS [LinkSet Index] [Adjacent DSP Index] [Link Select Mask]

ADD N7LNK [Module No.] [Link No.] [Start Circuit No.] [LinkSet Index] …

ADD N7RT [LinkSet Index] [DSP Index] [Route Priority]

Issue 04 (2009-01-15)


4-25



4.4 MTP3B Data Configuration Procedure Table 4-8 lists the procedure for configuring the MTP3B data through the E1 interface. Table 4-8 Procedure for configuring the MTP3B data Step

Operation

Command

1

Add an MTP3B OSP.

SET MTP3BOSP

2

Add an MTP3B DSP.

ADD MTP3BDSP

3

Add an MTP3B link set.

ADD MTP3BLKS

4

Add an MTP3B route.

ADD MTP3BRT

5

Add an MTP3B link.

ADD MTP3BLNK

Figure 4-19 shows the relations between the MTP3B data tables. Figure 4-19 MTP3B data table relation

SET MTP3BOSP

ADD MTP3BLKS [LinkSet index] [DSP index] [Link select mask]

[OPC] [NI]

… ADD MTP3BDSP [DSP index] [DPC] [NI]

[Signal Link code] [PVC link number] [LinkSet index]

…

…

SET OFI

ADD MTP3BRT

[NI] [National network valid] [National network code] …

4-26

ADD MTP3BLNK


[Route name] [DSP index] [LinkSet index] …

Issue 04 (2009-01-15)



4.5 M3UA Data Configuration Procedure Table 4-9 lists the procedure for configuring the M3UA data through the IP interface. Table 4-9 Procedure for configuring the M3UA data Step

Operation

Command

1

Add an M3UA local entity.

ADD M3LE

2

Add an M3UA destination entity.

ADD M3DE

3

Add an M3UA link set.

ADD M3LKS

4

Add an M3UA route.

ADD M3RT

5

Add an M3UA link.

ADD M3LNK

Figure 4-20 shows the relations between the M3UA data tables. Figure 4-20 M3UA data table relation

ADD M3LE

ADD M3LKS

[Local Entity Index]

[LinkSet Index]

[NI]

[Adjacent Entity Index]

[Local Entity Point Code] …

[Link Select Mask] …

ADD M3DE

ADD M3LNK

[Destination Entity Index]

[Module No.]

[Local Entity Index]

[Link No.]

[NI]

[LinkSet Index] …

…

ADD M3RT [Route Name] [Destination Entity Index] [LinkSet Index] …

Issue 04 (2009-01-15)


4-27



4.6 SCCP Data Configuration Procedure 4.6.1 SCCP Data Configuration Principles 4.6.2 SCCP Data Table Relation

4.6.1 SCCP Data Configuration Principles When configuring the SCCP data, observe the following principles: l

If the DPC addressing is adopted, set the SCCP DSP first and then the SCCP Subsystem table. In addition, ensure that the data configured in the SCCP DSP table and SCCP Subsystem table matches that configured at the peer end.

l

Ensure that the DPCs in the SCCP Subsystem table are valid values defined in the SCCP DSP table or in the Local Office Information table.

l

If the GT addressing is adopted, add GTs as follows:

l

–

Configure the SCCP DSP table and SCCP Subsystem table (if necessary).

–

Add a New GT table (optional).

–

Set GTs based on the translation type.

Ensure that the DPCs in the GT Translation table are valid values defined in the SCCP DSP table or in the Local Office Information table.

4.6.2 SCCP Data Table Relation Figure 4-21 shows the relations between the SCCP data tables.

4-28


Issue 04 (2009-01-15)



Figure 4-21 SCCP data table relation

ADD SCCPDPC

ADD N7DSP [DSP Index]

[DPC Index]

[NI]

[NI]

[DPC]

[DPC] …

…

ADD SCCPSSN

ADD M3DE [Destination Entity Index] [Local Entity Index] [DPC]

[SSN Index] [SSN] [DPC]

…

…

ADD MTP3BDSP

ADD SCCPNGT [New GT Index] [GT Indicator] [Translation Type]

[DSP Index] [NI] [DPC] …

… ADD SCCPGT [GT Index] [SSN] [DPC] [New GT Index] …

Table 4-10 lists the procedure for configuring the SCCP data. Table 4-10 Procedure for configuring the SCCP data Step

Operation

Command

1

Add an SCCP DSP.

ADD SCCPDPC

2

Add an SCCP subsystem.

ADD SCCPSSN

3

Add a new SCCP GT (optional).

ADD SCCPNGT

4

Add an SCCP GT.

ADD SCCPGT

4.7 Data Configuration Examples Issue 04 (2009-01-15)


4-29



4.7.1 Data Configuration in TDM Networking 4.7.2 Data Configuration in ATM-2M Networking 4.7.3 Data Configuration in IP Networking

4.7.1 Data Configuration in TDM Networking Description The OPC of the HLR (local office) is 088080. The SPCs of the NEs that are connected with the HLR are as follows: l

SPC of the STP: 512027

l

SPC of MSC 1: 640022

l

SPC of MSC 2: 640023

Figure 4-22 shows the signaling networking. Figure 4-22 Signaling networking

MSC1:640022

No.7

HLR:088080 No.7 STP:512027 No.7 MSC2:640023

MSC: Mobile Switching Center

HLR: Home Location Register


Example /*Configure the STP as a DSP of the HLR. */ ADD N7DSP: DPX=0, DPC="512027", DPNAME="STP", STPF=TRUE; /*Add an MTP link set. */ ADD N7LKS: LSX=0, ASPX=0, LSNAME="STP"; /*Add an MTP route.*/ ADD N7RT: LSX=0, DPX=0, RTNAME="STP"; /*Add an MTP signaling link (assume that the module number of the WCSU is 22).*/ ADD N7LNK: MN=22, LNKN=0, LNKNAME="STP", LNKTYPE=0, TS=1, LSX=0, SLC=0, SLCS=0; /*Add the STP as an SCCP DSP. */

4-30


Issue 04 (2009-01-15)



ADD SCCPDPC: DPX=0, NI=NAT, DPC="512027", OPC="088080", DPNAME="STP", SHAREFLAG=NONE; /*Add SCCP subsystems. */ ADD SCCPSSN: SSNX=0, NI=NAT, SSNNAME="HLR-SCMG"; ADD SCCPSSN: SSNX=1, NI=NAT, SSNNAME="HLR-HLR"; ADD SCCPSSN: SSNX=2, NI=NAT, SSNNAME="STP"; ADD SCCPSSN: SSNX=9, NI=NAT, SSNNAME="HLR-MSC";

SSN=SCMG, DPC="088080", OPC="088080", SSN=HLR, DPC="088080", OPC="088080", SSN=SCMG, DPC="512027", OPC="088080", SSN=MSC, DPC="088088", OPC="088088",

/*Configure MSC 1 as a DSP of the HLR. */ ADD N7DSP: DPX=1, DPC="640022", DPNAME="MSC1"; /*Add an MTP link set. */ ADD N7LKS: LSX=1, ASPX=1, LSNAME="MSC1"; /*Add an MTP route.*/ ADD N7RT: LSX=1, DPX=1, RTNAME="MSC1"; /*Add an MTP signaling link (assume that the module number of the WCSU is 22).*/ ADD N7LNK: MN=22, LNKN=1, LNKNAME="MSC1", LNKTYPE=0, TS=2, LSX=1, SLC=0, SLCS=0; /*Add MSC 1 as an SCCP DSP. */ ADD SCCPDPC: DPX=1, NI=NAT, DPC="640022", OPC="088080", DPNAME="MSC1", SHAREFLAG=NONE; /*Add SCCP subsystems. */ ADD SCCPSSN: SSNX=3, NI=NAT, SSN=MSC, DPC="640022", OPC="088080", SSNNAME="MSC1-MSC"; ADD SCCPSSN: SSNX=4, NI=NAT, SSN=SCMG, DPC="640022", OPC="088080", SSNNAME="MSC1-SCMG"; ADD SCCPSSN: SSNX=5, NI=NAT, SSN=VLR, DPC="640022", OPC="088080", SSNNAME="MSC1-VLR"; /*Add SCCP GTs.*/ ADD SCCPGT: GTX=0, GTNAME="HLR", GTI=GT4, ADDR=K'861392345000, RESULTT=LSPC2, DPC="088080"; ADD SCCPGT: GTX=1, GTNAME="MSC1", GTI=GT4, ADDR=K'86138755, RESULTT=LSPC2, DPC="640022"; /*Configure MSC 2 as a DSP of the HLR. */ ADD N7DSP: DPX=2, DPC="640023", DPNAME="MSC2"; /*Add an MTP route.*/ ADD N7RT: LSX=0, DPX=2, RTNAME="MSC2"; /*Add MSC 2 as an SCCP DSP. */ ADD SCCPDPC: DPX=2, NI=NAT, DPC="640023", OPC="088080", DPNAME="MSC2", SHAREFLAG=NONE; /*Add SCCP subsystems. */ ADD SCCPSSN: SSNX=6, NI=NAT, SSN=MSC, DPC="640023", OPC="088080", SSNNAME="MSC2-MSC"; ADD SCCPSSN: SSNX=7, NI=NAT, SSN=SCMG, DPC="640023", OPC="088080",

Issue 04 (2009-01-15)


4-31


4 Signaling Data Configuration SSNNAME="MSC2-SCMG";

ADD SCCPSSN: SSNX=8, NI=NAT, SSN=VLR, DPC="640023", OPC="088080", SSNNAME="MSC2-VLR"; /*Add SCCP GTs.*/ ADD SCCPGT: GTX=2, GTNAME="MSC2", GTI=GT4, ADDR=K'86138756, RESULTT=STP1, DPC="640023";

4.7.2 Data Configuration in ATM-2M Networking Description The OPC of the HLR (local office) is 088080. The STP is a DSP of the HLR, and the DPC is 512027. The MSC is connected to the HLR through the STP, and the DPC is 640022. The HLR number is 861392345000, and the MSC number is 861391234000. Figure 4-23 shows the signaling networking. Figure 4-23 Signaling networking

HLR:088080 ATM-2M STP:512027

MSC:640022

Example /*Set the OPC of the HLR. */ SET MTP3BOSP: OPC="088080"; /*Configure the STP and the MSC as the DSPs of the HLR. */ ADD MTP3BDSP: DPX=0, DPNAME="STP", DPC="512027", STPF=TRUE; ADD MTP3BDSP: DPX=1, DPNAME="MSC", DPC="640022", ADJF=FALSE; /*Add an MTP3B link set. */ ADD MTP3BLKS: LSX=0, LSNAME="STP", DPX=0; /*Add MTP3B routes.*/ ADD MTP3BRT: RTNAME="STP", DPX=0, LSX=0; ADD MTP3BRT: RTNAME="MSC", DPX=1, LSX=0; /*Add MTP3B links (assume that PVC links 0 and 16 are used). */ ADD MTP3BLNK: LNKNAME="STP-1", LSX=0, SLC=0, PLN=0; ADD MTP3BLNK: LNKNAME="STP-2", LSX=0, SLC=1, PLN=16; /*Add SCCP DSPs. */

4-32


Issue 04 (2009-01-15)



ADD SCCPDPC: DPX=0, NI=NAT, DPC="512027", OPC="088080", DPNAME="STP", SHAREFLAG=NONE; ADD SCCPDPC: DPX=1, NI=NAT, DPC="640022", OPC="088080", DPNAME="MSC", SHAREFLAG=NONE; /*Add SCCP subsystems. */ ADD SCCPSSN: SSNX=0, NI=NAT, SSNNAME="HLR-SCMG"; ADD SCCPSSN: SSNX=1, NI=NAT, SSNNAME="HLR-HLR"; ADD SCCPSSN: SSNX=6, NI=NAT, SSNNAME="HLR-MSC"; ADD SCCPSSN: SSNX=2, NI=NAT, SSNNAME="STP"; ADD SCCPSSN: SSNX=3, NI=NAT, SSNNAME="MSC-MSC"; ADD SCCPSSN: SSNX=4, NI=NAT, SSNNAME="MSC-SCMG"; ADD SCCPSSN: SSNX=5, NI=NAT, SSNNAME="MSC-VLR";

SSN=SCMG, DPC="088080", OPC="088080", SSN=HLR, DPC="088080", OPC="088080", SSN=MSC, DPC="088088", OPC="088088", SSN=SCMG, DPC="512027", OPC="088080", SSN=MSC, DPC="640022", OPC="088080", SSN=SCMG, DPC="640022", OPC="088080", SSN=VLR, DPC="640022", OPC="088080",

/*Add SCCP GTs.*/ ADD SCCPGT: GTX=0, GTNAME="HLR", GTI=GT4, ADDR=K'861392345000, RESULTT=LSPC2, DPC="088080"; ADD SCCPGT: GTX=1, GTNAME="MSC", GTI=GT4, ADDR=K'86138755, RESULTT=LSPC2, DPC="640022";

4.7.3 Data Configuration in IP Networking Description The OPC of the HLR (local office) is 088080. The STP is a DSP of the HLR, and the DPC is 512027. The MSC is connected to the HLR through the STP, and the DPC is 640022. The HLR number is 861392345000, and the MSC number is 861391234000. On the HLR, the module number of the WBSG used to process the M3UA protocol is 133. The IP address of the FE port used to distribute M3UA messages is 10.124.0.22. The IP address of the STP is 10.124.0.20. Figure 4-24 shows the signaling networking. Figure 4-24 Signaling networking

HLR:088080 IP STP:512027

MSC:640022

Issue 04 (2009-01-15)


4-33



Example /*Add an M3UA local entity.*/ ADD M3LE: LEX=0, LENAME="HLR", OPC="088080", LET=AS; /*Configure the STP and the MSC as the DSPs of the HLR. */ ADD M3DE: DEX=0, DENAME="STP", DPC="512027", STPF=TRUE, DET=SG; ADD M3DE: DEX=1, DENAME="MSC", DPC="640022", DET=SP; /*Add an M3UA link set. */ ADD M3LKS: LSX=0, LSNAME="STP", ADX=0, WM=ASP; /*Add M3UA routes.*/ ADD M3RT: RTNAME="STP", DEX=0, LSX=0; ADD M3RT: RTNAME="MSC", DEX=1, LSX=0; /*Add an M3UA link. */ ADD M3LNK: MN=133, LNKN=0, LNKNAME="STP", LOCIP1="10.124.0.22", LOCPORT=2905, PEERIP1="10.124.0.20", PEERPORT=2905, CS=C, LSX=0; /*Add SCCP DSPs. */ ADD SCCPDPC: DPX=0, NI=NAT, DPC="512027", OPC="088080", DPNAME="STP", SHAREFLAG=NONE; ADD SCCPDPC: DPX=1, NI=NAT, DPC="640022", OPC="088080", DPNAME="MSC", SHAREFLAG=NONE; /*Add SCCP subsystems. */ ADD SCCPSSN: SSNX=0, NI=NAT, SSNNAME="HLR-SCMG"; ADD SCCPSSN: SSNX=1, NI=NAT, SSNNAME="HLR-HLR"; ADD SCCPSSN: SSNX=6, NI=NAT, SSNNAME="HLR-MSC"; ADD SCCPSSN: SSNX=2, NI=NAT, SSNNAME="STP"; ADD SCCPSSN: SSNX=3, NI=NAT, SSNNAME="MSC-MSC"; ADD SCCPSSN: SSNX=4, NI=NAT, SSNNAME="MSC-SCMG"; ADD SCCPSSN: SSNX=5, NI=NAT, SSNNAME="MSC-VLR";

SSN=SCMG, DPC="088080", OPC="088080", SSN=HLR, DPC="088080", OPC="088080", SSN=MSC, DPC="088088", OPC="088088", SSN=SCMG, DPC="512027", OPC="088080", SSN=MSC, DPC="640022", OPC="088080", SSN=SCMG, DPC="640022", OPC="088080", SSN=VLR, DPC="640022", OPC="088080",

/*Add SCCP GTs.*/ ADD SCCPGT: GTX=0, GTNAME="HLR", GTI=GT4, ADDR=K'861392345000, RESULTT=LSPC2, DPC="088080"; ADD SCCPGT: GTX=1, GTNAME="MSC", GTI=GT4, ADDR=K'86138755, RESULTT=LSPC2, DPC="640022";

4-34


Issue 04 (2009-01-15)


A Abbreviations

A

Abbreviations

3 3G

The Third Generation

3GPP

3rd Generation Partnership Project

A

Issue 04 (2009-01-15)

A3

Authentication Algorithm A3

AAA

Authentication, Authorization and Accounting

AAL0

ATM Adaptation Layer Type 0

AAL1


AAL2


AAL5


ALS

Alternative Line Service

AMR

Adaptive MultiRate

ANSI

American National Standard Institute

AoCC

Advice of Charge Charging

AoCI

Advice of Charge Information

APN

Access Point Name

ARD

Access Restriction Data

ARP

Allocation Retention Priority

AS

Application Server

ASP

Application Server Process

ATCA

Advanced Telecom Computing Architecture

ATI

Any Time Interrogation

ATM

Asynchronous Transfer Mode Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

A-1


A Abbreviations

AuC

Authentication Center

AV

Authentication Vector

B BAIC

Barring of All Incoming Calls

BIC-Roam

Barring of Incoming Calls when Roaming Outside the Home PLMN Country

BAM

Back Administration Module

BAOC

Barring of All Outgoing Calls

BCD

Binary-Coded Data

BE

Back End

BHCA

Busy Hour Call Attempt

BITS

Building Integrated Timing Supply System

BNH

Business Hall

BOIC

Barring of Outgoing International Calls

BOIC-exHC

Barring of Outgoing International Calls except those directed to the Home PLMN Country

BOM

Bill of Material

BOSS

Business and Operation Support System

BS

Base Station

BS

Bearer Service

BSC

Base Station Controller

BSG

Basic Service Group

BSS

Base Station Subsystem

BSSAP

Base Station System Application Part

BSSMAP

Base Station System Management Application Part

BSU

BAM and SMU Unit

BTS

Base Transceiver Station

C

A-2

CAMEL

Customized Application for Mobile Network Enhanced Logic

CAP

CAMEL Application Part

CARP

CS Allocation/Retention Priority

CC

Country Code

CCF

Conditional Call Forwarding


Issue 04 (2009-01-15)


Issue 04 (2009-01-15)

A Abbreviations

CCF

Call Control Function

CDMA

Code Division Multiple Access

CEPT

Conference of European Postal and Telecommunications Administrations

CF

Call Forwarding

CFB

Call Forwarding on Mobile Subscriber Busy

CFD

Call Forwarding Default

CFNRc

Call Forwarding on Mobile Subscriber Not Reachable

CFNRy

Call Forwarding on No Reply

CFU

Call Forwarding Unconditional

CGF

Charging Gateway Functionality

CGL

Carrier Grade Linux

CIC

Carrier Identification Code

CKSN

Ciphering Key Sequence Number

CLI

Calling Line Identity

CLI

Command Line Interface

CLIP

Calling Line Identification Presentation

CLIR

Calling Line Identification Restriction

CLK

Clock

COA

Changeover Acknowledgement Signal

COLI

Connected line identity

COLP

Connected Line Identification Presentation

COLR

Connected Line Identification Restriction

CPC

Central Processing Card

CPCI

Compact Peripheral Component Interconnect

CPU

Central Processing Unit

CRBT

Color Ring Back Tone

CRC

Cyclic Redundancy Check

CS

Circuit Switched

CS

Core Network

CSCF

Call Session Control Function

CSI

CAMEL Subscription Information

CUG

Closed User Group Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

A-3


A Abbreviations

CW

Call Waiting

D DB

Database

DBC

Data Base client

DBU

Data Base Unit

DC

Direct Current

D-CSI

Dialed Services Camel Subscription Information

DID

Disk ID

DMU

Data Management Unit

DNS

Domain Name Server

DP

Detection Point

DPC

Destination Point Code

DRU

Data Routing Unit

DSP

Destination Signaling Point

DST

Daylight Saving Time

DSU

Data Service Unit

E ECATEGORY

Enhanced Category

ECT

Explicit Call Transfer

EIR

Equipment Identity Register

ESD

Electrostatic Discharge

ESN

Electronic Serial Number

ETS

European Telecommunication Standard

ETSI

European Telecommunications Standards Institute

F

A-4

FAM

Front Administration Module

FC

Fiber Channel

FE

Fast Ethernet

FE

Front End

FM

Follow Me

FTN

Forwarded-to number

FTP

File Transfer Protocol


Issue 04 (2009-01-15)


A Abbreviations

G GGSN

Gateway GPRS Support Node

GMLC

Gateway Mobile Location Center

GMSC

Gateway Mobile Switching Center

GPRS

General Packet Radio Service

GPRS-CSI

GPRS CAMEL Subscription Information

GPWS

General Power Supply Board

GSM

Global System for Mobile Communications

gsmSCF

Service Control Function

gsmSRF

Specialized Resource Function

gsmSSF

Service Switching Function

GSN

GPRS Support Node

GT

Global Title

GUI

Graphic User Interface

GUP

General User Profile

H HA

High Availability

HACMP

High Availability Cluster Multi-Processing

HDLC

High Level Data Link Control

HDU

HLR Database Unit

HLR

Home Location Register

HOLD

Call Hold

HPLMN

Home PLMN

HSS

Home Subscriber Server

HW

Highway

I

Issue 04 (2009-01-15)

IA

Intel Architecture

ICB

Incoming Calls Barred (within the CUG)

ID

Identity

IMA

Inverse Multiplexing for ATM

IMSI

International Mobile Subscriber Identity

IN

Intelligent Network


A-5


A Abbreviations

INAP

Intelligent Network Application Protocol

INU

Installation Unit

IP

Internet Protocol

IP

Intelligent Peripheral

IP TOS

IP Type of Service

IPLMN

Interrogating PLMN

IPMB

Intelligent Platform Management BUS

IPSP

IP Service Process

IPv4

Internet Protocol Version 4

IPv6

Internet Protocol Version 6

ISDN

Integrated Services Digital Network

ISUP

ISDN User Part

ITC

Information Transfer Capability

ITU-T

International Telecommunication Union - Telecommunication Standardization Sector

IUA

ISDN Q.921-User Adaptation Layer

IWF

Interworking Function

J JRE

JAVA Runtime Environment

K Kc

Ciphering Key

Ki

Individual Subscriber Authentication key

KVM

Keyboard&Video&Mouse

L

A-6

LA

Location Area

LAC

Location Area Code

LAI

Location Area Identity

LAN

Local Area Network

LCS

Location Service

LIA

Link Inhibit Acknowledgement Signal

LIC

Lawful Interception Center

LIN

Link Inhibit Signal

LLC

Logic Link Control Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 04 (2009-01-15)


A Abbreviations

LMSI

Local Mobile Station Identity

LMT

Local Maintenance Terminal

LPLMN

Location PLMN

LUA

Link Uninhibit Acknowledgement Signal

M

Issue 04 (2009-01-15)

M2UA

MTP2 User Adaptation layer

M3UA

MTP3 User Adaptation layer

MAC

Media Access Control

MAC

Message Authentication Code

MAP

Mobile Application Part

MCC

Mobile Country Code

M-CSI

Mobility Management Camel Subscription Information

MGCF

Media Gateway Control Function

MGMT

Management System

MM

Mobility Management

MML

Human Machine Language

MNC

Mobile Network Code

MNP

Mobile Number Portability

MO

Mobile Originated

MPTY

Multi-Party Service

MRTIE

Maximum Relative Time Interval Error

MS

Mobile Station

MSC

Mobile Switching Center

MSISDN

Mobile Station International ISDN Number

MSRN

Mobile Station Roaming Number

MSU

Message Signal Unit

MT

Mobile Terminated

MTBF

Mean Time Between Failures

MTC

Mobile Terminated Call

MTP

Message Transfer Part

MTP1

Message Transfer Part Layer 1

MTP2



A-7


A Abbreviations

MTP3


MTP3B

Message Transfer Part (Broadband)

MTTR

Mean Time to Repair

MVNO

Mobile Virtual Network Operator

MVPN

Mobile Virtual Private Network

MWI

Message Waiting Information

N NAEA

North American Equal Access

NAM

Network Access Mode

NCC

Network Capability Configuration

NE

Network Equipment

NE

Network Entity

NEBS

Network Equipment Building Specification

NF

Network Function

NLR

Number Location Register

NM

Network Management

NMC

Network Management Center

NMS

Network Management System

NNI

Network Node Interface

NPI

Numbering Plan Identification

NSAPI

Network Service Access Point Identifier

O

A-8

OAM

Operation, Administration, and Maintenance

OAMAgent

Operation, Administration, and Maintenance Agent

O-CSI

Originating CAMEL Subscription Information

ODB

Operator Determined Barring

OFA

Origin for Forwarded-to Number Analysis

OM

Operations and Maintenance

OMC

Operations & Maintenance Center

OPC

Originating Signaling Point Code

OSI

Open System Interconnection

OSTA

Open Standards Telecom Architecture


Issue 04 (2009-01-15)


A Abbreviations

P PAD

Packet Assembly/Disassembly Facility

PBX

Private Branch Exchange

PC

Personal Computer

PCA

Password Call Access

PCI

Peripheral Component Interconnect

PCM

Pulse Code Modulation

PCU

Packet Control Unit

PDB

Power Distribution Box

PDF

Power Distribution Frame

PDH

Plesiochronous Digital Hierarchy

PDN

Packet Data Network

PDP

Packet Data Protocol

PDU

Protocol Data Unit

PEM

Power Entry Module

PGND

Protect Ground

PICMG

PCI Industrial Computer Manufacturers Group

PID

Process Identification

PIN

Personal Identification Number

PL

Preferred Language

PLMN

Public Land Mobile Network

PLMNSS

PLMN-Specific

PMC

Protocol Management and Control Board

PRN

Provide Roaming Number

PS

Packet Switched

PSI

Provide Subscriber Information

PSTN

Public Switched Telephone Network

PVC

Permanent Virtual Connection

Q QoS

Quality of Service

R RAB

Issue 04 (2009-01-15)

Radio Access Bearer


A-9


A Abbreviations

RAID

Redundant Access Independent Disk

RANAP

Radio Access Network Application Part

RAND

RANDom number(used for authentication)

RBT

Ring Back Tone

RDI

Restricted digital information

RFC

Remote Feature Control

RNC

Radio Network Controller

S

A-10

SAAL

Signaling ATM Adaptation Layer

SAB

Subscriber Application Barring

SAP

Service Access Point

SAR

Segmentation and Reassembly

SAS

Serial Attached Small Computer System Interface

SAU

Signaling Access Unit

SBP

Selective by Pass

SCA

Selective Call Acceptance

SCCP

Signaling Connection and Control Part

SCDF

Service Control Data Function

SCF

Service control function

SCMG

SCCP Management

SCN

Switched Circuit Network

SCP

Service Control Point

SCSI

Small Computer Systems Interface

SCTP

Streaming Control Transmission Protocol

SCU

Service Process Unit

SDF

Service Data Function

SDH

Synchronous Digital Hierarchy

SDU

Service Data Unit

SG

Signaling Gateway

SGP

Signaling Gateway Process

SGSN

Serving GPRS Support Node

SID

System Identification


Issue 04 (2009-01-15)


Issue 04 (2009-01-15)

A Abbreviations

SIF

Signaling Information Filed

SIGTRAN

Signaling Transport

SIM

Subscriber Identity Module

SIO

Service Information Octet

SLC

Signaling Link Code

SLCS

Signaling Link Code Send

SLS

Signaling Link Selection

SLTA

Signaling Link Test Acknowledge

SLTM

Signaling Link Test Message

SMB

System Management Board

SMC

Short Message Center

SMF

Service Management Function

SMFAgent

Subscriber Management Function Agent

SMM

Shelf Management Module

SMS

Short Message Service

SMS-CSI

Short Message Service Camel Subscription Information

SMU

Subscriber Management Unit

SN

Serial Number

SNTP

Simple Network Time Protocol

SOL

Serial over LAN

SOR

Support of Optimal Routing

SP

Signaling Point

SPC

Signaling Point Code

SPINA

Subscriber Personal Identification Number Access

SPINI

Subscriber Personal Identification Number Interception

SQL

Structured Query Language

SQN

Sequence Number

SRI

Send Routing Information

SS

Supplementary Service

SS7

Signaling System Number 7

SSCF

Service Specific Coordination Function

SSCOP

Service Specific Connection Oriented Protocol


A-11


A Abbreviations

SS-CSI

Supplementary service invocation notification CAMEL subscription information

SSD

Shared Secret Data

SSF

Service Switching Function

SSN

Sub-System Number

SSP

Service Switching Point

STP

Signaling Transfer Point

SUA

SCCP User Adapter

SVC

Switched Virtual Channel

SWI

Switch Interface Unit

SWU

Switch Unit

T TC

Terminal Concentrator

TCAP

Transaction Capabilities Application Part

TCP

Transmission Control Protocol

T-CSI

Terminating Camel Subscription Information

TDD

Time Division Duplex

TDM

Time Division Multiplexing

TDMA

Time Division Multiple Access

TIF-CSI

Translation Information Fag Camel Subscription Information

TMG

Trunk Media Gateway

TMSI

Temporary Mobile Subscriber Identity

TUP

Telephone User Part

U

A-12

U-CSI

USSD CAMEL Subscription Information

UDP

User Datagram Protocol

UDT

Unit Data

UE

User Equipment

UI

User Interface

UMTS

Universal Mobile Telecommunications System

UNI

User Network Interface

UPB

Universal Process Blade

UPWR

UMSC PSM Power Module Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 04 (2009-01-15)


A Abbreviations

USAU

Universal Signaling Access Unit

USC

Unified Subscriber Center

USI

Universal Service Interface Unit

USIM

UMTS Subscriber Identity Module

USSD

Unstructured Supplementary Service Data

UTRAN

Universal Terrestrial Radio Access Network

UUS

User-to-User Signaling

V V5UA

V5 User Adapter

VBS

Voice Broadcast Service

VCI

Virtual Channel Identifier

VCS

VERITAS Cluster Server

VGCS

Voice Group Call Service

VLAN

Virtual LAN

VLR

Visitor Location Register

VM

Voice Mailbox

VMR

Voice Message Retrieval

VMSC

Visited Mobile Switching Center

VoIP

Voice over IP

VP

Visual Phone

VPI

Virtual Path Identifier

VPLMN

Visited PLMN

VPN

Virtual Private Network

VT-CSI

VMSC terminating CAMEL subscription information

VVDN

Voice&Videophone Dual Number

VxVM

VERITAS Volume Manager

W

Issue 04 (2009-01-15)

WALU

Wireless Alarm Unit

WAP

Wireless Access Protocol

WBFI

Wireless Back Insert FE Interface Unit

WBSG

Wireless Broadband Signaling Gateway

WCCU

Wireless Calling Control Unit


A-13


A Abbreviations

A-14

WCDMA

Wideband Code Division Multiple Access

WCKI

Wireless Clock Interface Unit

WCSU

Wireless Calling Control Unit and Signaling Process Unit

WEAM

Wireless E1 ATM Forward Module

WEPI

Wireless E1_Pool Interface Unit

WHSC

Wireless Hot-Swap and Control Unit

WIFM

Wireless IP Forward Module

WIN

Wireless Intelligent Network

WLAN

Wireless Local Area Network

WS

Work Station

WSIU

Wireless System Interface Unit

WSMU

Wireless System Management Unit


Issue 04 (2009-01-15)


Index

Index board restarting, 1-8 maximum number of tuple, 1-6 software parameter, 1-8 value ranges of software parameter, 1-7

B basic concept called prefix, 3-2 cluster, 2-6 local office information, 3-2 MTP-Specific, 4-2 MTP3B-Specific, 4-10 node, 2-6 rack number, 2-2 SCCP-Specific, 4-16 SIGTRAN-Specific, 4-13 slot number, 2-4 SPC, 3-2

L local office data configuration example, 3-5

M MML command data setting procedure, 1-4 meaning, 1-2 rule, 1-3

D data configuration process, 1-2 hardware data configuration, 2-1 local office data configuration, 3-1 signaling data configuration, 4-1

H hardware data configuration adding cluster configuration information, 2-13 adding node configuration, 2-14 adding OSTA 1.0 board, 2-12 adding OSTA 1.0 subrack, 2-12 adding OSTA 2.0 board, 2-13 adding OSTA 2.0 subrack, 2-13 adding rack, 2-12 flow chart, 2-7 generating SAU data loading file, 2-14 hardware data table relation, 2-9 setting local office information, 2-13 synchronizing HDU configuration, 2-14 hardware data configuration example ATM-2M networking, 2-19 TDM networking, 2-15

S signaling data configuration M3UA data configuration, 4-27 MTP data configuration, 4-24 MTP3B data configuration, 4-26 SCCP data configuration, 4-28 signaling data configuration example ATM-2M networking, 4-32 IP networking, 4-33 TDM networking, 4-30 signaling data configuration procedure ATM-2M networking, 4-22 IP networking, 4-23 TDM networking, 4-21

I impact on data configuration

Issue 04 (2009-01-15)


i-1

HLR9820-Configuration Guide(V900R003C02 04,Db2)

Recommend Documents