SG7000 Feature Description (V200R005C02 - 02)

U-SYS SG7000 Signaling Gateway
V200R005C02
Feature Description
Issue 02
Date 2009-12-14
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2009. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 02 (2009-12-14) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
Feature Description About This Document
About This Document
Purpose
This document describes the data configuration, management, and maintenance operation on
the U-SYS SG7000 Signaling Gateway. The services in this manual must be used together with
the license file, that is, the services can be configured only when they are purchased.
Related Versions
The following table lists the product versions related to this document.
Product Name Version
U-SYS SG7000 V200R005C02
Intended Audience
The intended audiences of this document are:
l Network planning engineers

l Installation engineers
l Maintenance engineers
l Commissioning engineers
l On-site engineers
l Routine attendants
Organization
Chapter Description
1 Configuring Called SMR Describes how to configure the called SMR service data.
Service Data
Issue 02 (2009-12-14) Huawei Proprietary and Confidential iii

About This Document Feature Description
Chapter Description
2 Configuring Calling SMR Describes how to configure the calling SMR service data.
Service Data
3 Configuring IMEI Catch Describes how to configure the IMEI Catch service data.
Service Data
4 Configuring MNP Service Describes how to configure the MNP service data.
Data
5 Configuring CRBT Service Describes how to configure the CRBT service data.
Data
6 Configuring B&W Lists Describes how to configure the B&W lists and number
and Number Change Service change service data.
Data
7 Configuring Protocol Describes how to configure the protocol translation service

Translation Service Data data.
8 Configuring Firewall Describes how to configure the firewall service data.

Service Data
9 Configuring MC Service Describes how to configure the MC service data.

Data
10 Configuring FNR Service Describes how to configure the FNR service data for a
Data - General general use.
11 Configuring SMI Service Describes how to configure the SMI service data.
Data
12 Configuring CDMA and Describes how to configure the MNP service data for the
GSM MNP Service Data CDMA and the GSM networks.
Conventions
Symbol Conventions
The following symbols may be found in this document. They are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk which, if not

avoided, will result in death or serious injury.
DANGER
Indicates a hazard with a medium or low level of risk which,

if not avoided, could result in minor or moderate injury.
WARNING
iv Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Feature Description About This Document
Symbol Description
Indicates a potentially hazardous situation that, if not

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

supplement important points of the main text.
General Conventions
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users are in boldface. For
example, log in as user root.
Italic Book titles are in italics.

Courier New Terminal display is in Courier New.
Command Conventions
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italic.
[] Items (keywords or arguments) in square brackets [ ] are

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

vertical bars. One is selected.
[ x | y | ... ] Optional alternative items are grouped in square brackets

and separated by vertical bars. One or none is selected.
{ x | y | ... } * Alternative items are grouped in braces and separated by

vertical bars. A minimum of one or a maximum of all can
be selected.
Issue 02 (2009-12-14) Huawei Proprietary and Confidential v

About This Document Feature Description
GUI Conventions
Boldface Buttons, menus, parameters, tabs, window, and dialog titles are in
boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">" signs. For
example, choose File > Create > Folder.
Keyboard Operation
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt+A means the
three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means the two keys
should be pressed in turn.
Mouse Operation
Action Description
Click Select and release the primary mouse button without moving the pointer.
Double-click Press the primary mouse button twice continuously and quickly without
moving the pointer.
Drag Press and hold the primary mouse button and move the pointer to a certain
position.
Update History
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
Updates in Issue 02 (2009-12-14)

The PDB (DPD100-2-20) is added.
Updates in Issue 01 (2009-09-27)

Initial commercial release.
vi Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Feature Description Contents
Contents
About This Document...................................................................................................................iii

1 Configuring Called SMR Service Data..................................................................................1-1
1.1 Called SMR Service........................................................................................................................................1-2
1.2 Service Flow....................................................................................................................................................1-2
1.2.1 Networking Structure.............................................................................................................................1-2
1.2.2 Service Implementation..........................................................................................................................1-3
1.3 Configuration Preparations.............................................................................................................................1-4
1.3.1 Terms......................................................................................................................................................1-4
1.3.2 Configuration Principles........................................................................................................................1-4
1.3.3 Relation Between Data Tables...............................................................................................................1-5
1.3.4 Data Collection.......................................................................................................................................1-6
1.3.5 General Steps..........................................................................................................................................1-6
1.4 Configuration Steps.........................................................................................................................................1-6
1.4.1 Setting Short Message Routing Number Type.......................................................................................1-7
1.4.2 Adding Virtual SMSC Address Table....................................................................................................1-8
1.4.3 Adding New SMSC Address Mapping Table........................................................................................1-8
1.4.4 Adding SMSC GT Translation Data......................................................................................................1-9
1.4.5 Adding VSMSC GT Translation Data.................................................................................................1-12
1.5 Configuration Examples................................................................................................................................1-12
2 Configuring Calling SMR Service Data................................................................................2-1

2.1 Calling SMR Service.......................................................................................................................................2-2
2.1.1 Service Definition..................................................................................................................................2-2
2.1.2 Service Advantages................................................................................................................................2-2
2.1.3 Version Requirement..............................................................................................................................2-2
2.2 Service Flow....................................................................................................................................................2-2
2.3.1 Terms......................................................................................................................................................2-4
2.3.4 Data Collection.......................................................................................................................................2-5
Issue 02 (2009-12-14) Huawei Proprietary and Confidential vii

Contents Feature Description
2.3.5 General Steps..........................................................................................................................................2-6

2.4 Configuration Procedures................................................................................................................................2-6
2.4.1 Setting Short Message Routing Number Type.......................................................................................2-6
2.4.2 Setting Default SMSC Address..............................................................................................................2-7
2.4.3 Adding SMSC Address Mapping Table.................................................................................................2-8
2.4.4 Adding SMSC GT Translation Data......................................................................................................2-9
3 Configuring IMEI Catch Service Data...................................................................................3-1

3.1 IMEI Catch Service.........................................................................................................................................3-2
3.2 Service Flow....................................................................................................................................................3-2
3.2.3 Service Flow...........................................................................................................................................3-4
3.2.4 Equipment Coordination Requirements.................................................................................................3-5
3.3.1 Terms......................................................................................................................................................3-6
3.3.4 Data Collection.......................................................................................................................................3-7
3.3.5 General Steps..........................................................................................................................................3-8
3.4.1 Adding Network Information Configuration Table...............................................................................3-9
3.4.2 Adding the SDUI..................................................................................................................................3-10
3.4.3 Setting IMEI Catch Service Software Parameter Table.......................................................................3-11
3.4.4 Adding Service User Data....................................................................................................................3-12
4 Configuring MNP Service Data..............................................................................................4-1

4.1 MNP Service...................................................................................................................................................4-2
4.2 Service Flow....................................................................................................................................................4-3
4.2.3 Calling Flow...........................................................................................................................................4-5
4.2.4 Impact on IN Services..........................................................................................................................4-17
4.2.5 Impact on Supplementary Services......................................................................................................4-17
4.2.6 Interworking Requirements..................................................................................................................4-18
4.3 Configuration Preparations...........................................................................................................................4-18
4.3.1 Terms....................................................................................................................................................4-19
4.3.2 Configuration Principles......................................................................................................................4-20
4.3.3 Relations Between Data Tables............................................................................................................4-22
4.3.4 Data Collection.....................................................................................................................................4-24
4.3.5 General Steps........................................................................................................................................4-24
4.4 Configuration Procedures..............................................................................................................................4-25
viii Huawei Proprietary and Confidential Issue 02 (2009-12-14)

4.4.1 Configuring MNP Software Parameters..............................................................................................4-26

4.4.2 Configuring HLR Address Table.........................................................................................................4-35
4.4.3 Configure MNP Route Number Table.................................................................................................4-36
4.4.4 Configuring MNP Foreign Number Range Table................................................................................4-37
4.4.5 Configuring Service User Data Table..................................................................................................4-38
4.4.6 Setting SCCP GT Translation Table....................................................................................................4-40
4.5.1 MNP Service in PLMN........................................................................................................................4-40
4.5.2 Other MNP Services.............................................................................................................................4-44
5 Configuring CRBT Service Data.............................................................................................5-1

5.1 CRBT Service................................................................................................................................................. 5-2
5.1.1 Service Advantages................................................................................................................................5-2
5.1.2 Service Features..................................................................................................................................... 5-3
5.2 Service Flow....................................................................................................................................................5-3
5.2.2 Service Triggering..................................................................................................................................5-5
5.2.4 Calling Flow...........................................................................................................................................5-6
5.2.5 Registration and Deregistration Flow.................................................................................................... 5-8
5.2.6 CRBT Customization Flow....................................................................................................................5-9
5.2.7 CRBT Query Flow.................................................................................................................................5-9
5.2.8 Service Charging..................................................................................................................................5-11
5.2.9 Deployment Scope...............................................................................................................................5-12
5.2.10 Support to IN Services.......................................................................................................................5-12
5.2.11 Support to Supplementary Services...................................................................................................5-13
5.2.12 Device Coordination Requirements...................................................................................................5-14
5.3.1 Terms....................................................................................................................................................5-15
5.3.3 Relation Between Data Tables.............................................................................................................5-17
5.3.4 Data Collection.....................................................................................................................................5-19
5.3.5 General Steps........................................................................................................................................5-20
5.4.1 Adding Virtual Roaming Number........................................................................................................5-21
5.4.2 Setting CRBT Software Parameters.....................................................................................................5-22
5.4.3 Setting Prefix Analysis Table...............................................................................................................5-26
5.4.4 Setting Provincial VMSC Number Range...........................................................................................5-27
5.4.5 Setting User Number Range.................................................................................................................5-27
5.4.6 Setting CRBT User Data......................................................................................................................5-28
5.5 Configuring CRBT Shielding Data...............................................................................................................5-29
5.5.1 Configuring CRBT GT Number Range Shielding...............................................................................5-30
5.5.2 Configuring CRBT User Number Range Shielding.............................................................................5-31
Issue 02 (2009-12-14) Huawei Proprietary and Confidential ix

6 Configuring B&W Lists and Number Change Service Data.............................................6-1

6.1 B&W Lists and Number Change Service.......................................................................................................6-2
6.2 Service Flow....................................................................................................................................................6-2
6.3.1 Terms......................................................................................................................................................6-6
6.3.4 Data Collection.......................................................................................................................................6-9
6.3.5 General Steps........................................................................................................................................6-12
6.4.1 Adding MTP Link Set..........................................................................................................................6-13
6.4.2 Adding Operator Number Range Table...............................................................................................6-14
6.4.3 Adding Dummy Number Table............................................................................................................6-15
6.4.4 Adding DSP Index Reference..............................................................................................................6-15
6.4.5 Adding Calling B&W List...................................................................................................................6-16
6.4.6 Adding Called B&W List.....................................................................................................................6-17
6.4.7 Adding Number Operation...................................................................................................................6-18
6.4.8 Adding Calling Number Transform.....................................................................................................6-19
6.4.9 Adding Called Number Transform......................................................................................................6-21
6.4.10 Adding CPC.......................................................................................................................................6-21
7 Configuring Protocol Translation Service Data...................................................................7-1

7.1 Protocol Translation Service...........................................................................................................................7-2
7.2 Service Flow....................................................................................................................................................7-2
7.3.1 Terms......................................................................................................................................................7-3
7.3.2 Configuration Principle..........................................................................................................................7-3
7.3.4 Data Collection.......................................................................................................................................7-4
7.3.5 General Steps..........................................................................................................................................7-4
7.4.1 Setting SPC Translation Management Table.........................................................................................7-5
7.4.2 Setting Protocol Translation DSP Set Table..........................................................................................7-5
7.5 Configuration Examples..................................................................................................................................7-6
8 Configuring Firewall Service Data.........................................................................................8-1

8.1 Firewall Service...............................................................................................................................................8-2
x Huawei Proprietary and Confidential Issue 02 (2009-12-14)

8.1.1 Service Functions...................................................................................................................................8-2

8.1.2 Service Features..................................................................................................................................... 8-2
8.2 Service Flow....................................................................................................................................................8-2
8.2.2 Mask Function of Firewall.....................................................................................................................8-3
8.2.3 Testing the Firewall Mask Rules............................................................................................................8-9
8.2.4 Alarm Function of Firewall....................................................................................................................8-9
8.2.5 Message Statistics Function of Firewall...............................................................................................8-10
8.2.6 Statistics of SMSC Addresses..............................................................................................................8-11
8.3.1 Terms ...................................................................................................................................................8-11
8.3.3 Relation Between Data Tables.............................................................................................................8-14
8.3.4 Data Collection.....................................................................................................................................8-16
8.3.5 General Steps........................................................................................................................................8-16
8.4.1 Configuring the Firewall Software Configuration Parameter..............................................................8-18
8.4.2 Configuring the MAP Content Mask Management.............................................................................8-20
8.4.3 Configuring Operation Code Set Management....................................................................................8-21
8.4.4 Configuring the Subsystem Set Management......................................................................................8-22
8.4.5 Setting the MAP Operation Code Mask Management.........................................................................8-23
8.4.6 Configuring the Called GT Mask Management...................................................................................8-24
8.4.7 Configuring the Calling GT Mask Management..................................................................................8-26
8.4.8 Configuring the DPC Mask Management............................................................................................8-28
8.4.9 Configuring the OPC Mask Management............................................................................................8-30
8.4.10 Configuring Link Set Public Default Mask Management..................................................................8-31
8.4.11 Configuring Link Set Public Mask Management...............................................................................8-32
8.4.12 Configuring the Initial Mask Management........................................................................................8-33
8.4.13 Configuring the MTP Link Set...........................................................................................................8-35
8.5 Firewall Maintenance and Test.....................................................................................................................8-35
8.6 Firewall Alarm Configuration.......................................................................................................................8-36
8.6.1 Configuring the Software Configuration Parameter............................................................................8-36
8.6.2 Configuring FW Alarm Table..............................................................................................................8-37
8.7 Firewall Statistics Configuration...................................................................................................................8-38
8.7.1 Configuring the Software Configuration Parameter............................................................................8-39
8.7.2 Configuring FW Statistics Table..........................................................................................................8-39
8.7.3 Configuring FW SMSC Address Statistics Table................................................................................8-40
8.7.4 Querying the Permanent Statistics Data...............................................................................................8-41
9 Configuring MC Service Data.................................................................................................9-1

9.1 MC Service......................................................................................................................................................9-2
9.2 Service Flow....................................................................................................................................................9-2
Issue 02 (2009-12-14) Huawei Proprietary and Confidential xi


9.3.2 Data Collection.......................................................................................................................................9-5
9.3.3 General Steps..........................................................................................................................................9-5
9.4.1 Setting Software Parameters for MC Service........................................................................................9-6
9.4.2 Adding MC Routing Number.................................................................................................................9-7
9.4.3 Adding MC Local SMSC Address.........................................................................................................9-8
9.4.4 Adding Service User Data......................................................................................................................9-9
9.4.5 Adding Sub MSISDN numbers............................................................................................................9-10
9.4.6 Setting SCCP GT Translation Table....................................................................................................9-11
10 Configuring FNR Service Data - General..........................................................................10-1

10.1 FNR Service................................................................................................................................................10-2
10.2 Service Flow................................................................................................................................................10-2
10.2.1 Networking Structure.........................................................................................................................10-2
10.2.2 Service Implementation......................................................................................................................10-4
10.3 Configuration Preparations.........................................................................................................................10-5
10.3.1 Terms..................................................................................................................................................10-5
10.3.2 Configuration Principles....................................................................................................................10-6
10.3.3 Relation Between Data Tables...........................................................................................................10-6
10.3.4 Data Collection...................................................................................................................................10-7
10.3.5 General Steps......................................................................................................................................10-8
10.4 Configuration Procedures............................................................................................................................10-8
10.4.1 Adding HLR Address.........................................................................................................................10-9
10.4.2 Setting MNP Software Configuration Parameter.............................................................................10-10
10.4.3 Setting MNP Prefix Mapping Management.....................................................................................10-11
10.4.4 Adding Service User Data................................................................................................................10-11
10.4.5 Setting SCCP GT Translation Table................................................................................................10-12
10.5 Configuration Examples............................................................................................................................10-13
11 Configuring SMI Service Data............................................................................................11-1

11.1 SMI Service.................................................................................................................................................11-2
11.2 Service Flow................................................................................................................................................11-2
11.2.2 Device Coordination Requirements...................................................................................................11-3
11.3.1 Relation Between Data Tables...........................................................................................................11-4
11.3.2 Data Collection...................................................................................................................................11-5
11.3.3 General Steps......................................................................................................................................11-5
11.4 Configuring SMI Service Data....................................................................................................................11-5
xii Huawei Proprietary and Confidential Issue 02 (2009-12-14)

11.5 Configuration Examples..............................................................................................................................11-6
12 Configuring CDMA and GSM MNP Service Data.........................................................12-1

12.1 Overview.....................................................................................................................................................12-2
12.1.1 MNP Service......................................................................................................................................12-2
12.1.2 Purpose of Configuring CDMA and GSM MNP Service Data.........................................................12-2
12.1.3 Terms..................................................................................................................................................12-2
12.1.4 MNP Service Advantages..................................................................................................................12-4
12.1.5 MNP Service Features........................................................................................................................12-4
12.1.6 Version Requirement..........................................................................................................................12-4
12.2 Service Flow................................................................................................................................................12-5
12.2.3 Calling Flow.......................................................................................................................................12-7
12.2.4 Device Coordination Requirements.................................................................................................12-11
12.2.5 Service Interaction............................................................................................................................12-12
12.3 Configuration Preparations.......................................................................................................................12-12
12.3.1 Configuration Principles..................................................................................................................12-12
12.3.2 Relations Between Data Tables........................................................................................................12-14
12.3.3 Data Collection.................................................................................................................................12-16
12.3.4 General Steps....................................................................................................................................12-17
12.4 Configuration Procedures..........................................................................................................................12-18
12.4.1 Setting Software Configuration Parameter......................................................................................12-18
12.4.2 Setting MNP Software Configuration Parameter.............................................................................12-19
12.4.3 Configuring HLR Address...............................................................................................................12-20
12.4.4 Configuring MNP Route Number....................................................................................................12-21
12.4.5 Configuring MNP Local Network Number Range..........................................................................12-22
12.4.6 Configuring MNP Foreign Number Range......................................................................................12-23
12.4.7 Configuring Service User Data........................................................................................................12-24
13 Configuring IPR Service Data.............................................................................................13-1

13.1 IPR Service..................................................................................................................................................13-2
13.1.1 Service Overview...............................................................................................................................13-2
13.1.2 Terms..................................................................................................................................................13-2
13.1.3 Service Advantages............................................................................................................................13-3
13.1.4 Service Features.................................................................................................................................13-3
13.2 Service Flow................................................................................................................................................13-3
13.2.3 Call Flow............................................................................................................................................13-6
13.2.4 Interworking Requirements..............................................................................................................13-10
Issue 02 (2009-12-14) Huawei Proprietary and Confidential xiii


13.3.2 Mapping Between Data Tables........................................................................................................13-11
13.3.3 Data Collection.................................................................................................................................13-12
13.3.4 General Steps....................................................................................................................................13-13
13.4.1 Configuring IPR Service Software Parameters................................................................................13-14
13.4.2 Configuring the IPR User Group Table...........................................................................................13-16
13.4.3 Configuring the IPR Network Table................................................................................................13-17
13.4.4 Configuring the Outbound Roaming User Group Table..................................................................13-18
13.4.5 Configuring the Inbound Roaming User Group Table.....................................................................13-19
14 Configuring IRVAS Service Data.......................................................................................14-1

14.1 Brief Introduction........................................................................................................................................14-2
14.1.1 Service Definition.............................................................................................................................. 14-2
14.1.2 Terms..................................................................................................................................................14-2
14.1.3 Service Advantages............................................................................................................................14-3
14.2 Service Flow................................................................................................................................................14-3
14.2.3 Calling Flow.......................................................................................................................................14-6
14.2.4 Requirements on Cooperating Equipment.......................................................................................14-11
14.3.3 Data Collection.................................................................................................................................14-13
14.3.4 General Steps....................................................................................................................................14-14
14.4 Configuring the IRVAS Service ..............................................................................................................14-14
14.4.1 Configuring the IRVAS Software Parameters ................................................................................14-14
14.4.2 Configuring the MSC Number Segment Supporting the CAMEL Capabilities..............................14-16
15 Configuring IN BYPASS Service Data..............................................................................15-1

15.1 Service Introduction....................................................................................................................................15-2
15.1.2 Terms..................................................................................................................................................15-2
15.1.3 Service Interaction..............................................................................................................................15-2
15.1.4 Service Benefits..................................................................................................................................15-3
xiv Huawei Proprietary and Confidential Issue 02 (2009-12-14)

15.1.6 Equipment Cooperation Requirement................................................................................................15-3

15.2 Service Processing Flow.............................................................................................................................15-3
15.2.2 Service Implementation Principle......................................................................................................15-4
15.2.3 Calling Flow.......................................................................................................................................15-5
15.3.1 Relations Between Data Tables..........................................................................................................15-7
15.3.2 Data Configuration Requirements on Interworking Equipment........................................................15-7
15.3.3 Data Collection...................................................................................................................................15-8
15.3.4 Configuration Principle......................................................................................................................15-8
15.3.5 General Procedures............................................................................................................................15-8
15.4 Data Configuration......................................................................................................................................15-9
15.4.1 Setting the SMS Software Parameter.................................................................................................15-9
15.4.2 Adding the SCP Address..................................................................................................................15-12
15.4.3 Adding the MNP Local Network Number Range............................................................................15-12
15.4.4 Adding the Filter Time Segment......................................................................................................15-14
15.4.5 Adding the Service User Data..........................................................................................................15-14
15.5.1 Example Description........................................................................................................................15-16
15.5.2 Configuration Description................................................................................................................15-17
15.5.3 Configuration Verification...............................................................................................................15-18
15.6 Troubleshooting........................................................................................................................................15-20
16 Configuring MRS Service Data...........................................................................................16-1

16.1.1 Service Definition..............................................................................................................................16-2
16.1.2 Terms..................................................................................................................................................16-2
16.2 Service Processing Flow.............................................................................................................................16-4
16.2.3 Calling Flow.......................................................................................................................................16-5
16.3.2 Data Configuration Requirements on Interworking Equipment........................................................16-9
16.3.3 Data Collection...................................................................................................................................16-9
16.3.4 Configuration Description................................................................................................................16-10
16.3.5 General Procedures..........................................................................................................................16-11
16.4 General Procedures...................................................................................................................................16-12
16.4.1 Adding the M3UA and MTP Link Sets...........................................................................................16-13
Issue 02 (2009-12-14) Huawei Proprietary and Confidential xv

16.4.2 Adding the Reroute OPC..................................................................................................................16-16

16.4.3 Adding the Reroute DPC..................................................................................................................16-17
16.4.4 Adding the Reroute Called GT.........................................................................................................16-19
16.4.5 Adding the Reroute Calling GT.......................................................................................................16-21
16.4.6 Adding the Reroute Operation Code................................................................................................16-23
16.4.7 Adding the Reroute Rule..................................................................................................................16-25
16.4.8 Setting the Software Configuration Parameter.................................................................................16-28
16.4.9 Adding the Reroute Called GT Range.............................................................................................16-30
16.4.10 Adding the Reroute Calling GT Range..........................................................................................16-31
16.4.11 Adding the Reroute Number..........................................................................................................16-31
16.5 Configuration Example.............................................................................................................................16-32
16.5.1 Example Description (SCCP Reroute).............................................................................................16-33
16.5.2 Configuration Description(SCCP Reroute)......................................................................................16-33
16.5.3 Example Description (MAP Reroute)..............................................................................................16-34
16.5.4 MAP Reroute Configuration for the SRI_For_SM Message...........................................................16-35
16.5.5 MAP Reroute Configuration for the IMSI Addressing Message.....................................................16-36
17 Configuring CFS Black&White Lists Data........................................................................17-1

17.1.2 Terms..................................................................................................................................................17-2
17.2 Service Processing Flow............................................................................................................................. 17-4
17.2.3 Call Flow............................................................................................................................................17-6
17.3.2 Data Configuration Requirements on Interworking Equipment......................................................17-17
17.3.3 Data Collection.................................................................................................................................17-17
17.3.4 Configuration Principle....................................................................................................................17-20
17.3.5 General Steps....................................................................................................................................17-20
17.4.1 Setting Service Common Software Configuration Parameters........................................................17-22
17.4.2 Setting Software Configuration Parameters (Two)..........................................................................17-22
17.4.3 Adding the MTP DSP......................................................................................................................17-23
17.4.4 Adding the MTP Link Set................................................................................................................17-25
17.4.5 Adding the Number Analysis Prefix................................................................................................17-26
17.4.6 Adding the CFS Call Type...............................................................................................................17-28
17.4.7 Adding the CFS Shielding Release Cause.......................................................................................17-29
xvi Huawei Proprietary and Confidential Issue 02 (2009-12-14)

17.4.8 Adding the CFS Personal List..........................................................................................................17-30

17.4.9 Adding the CFS Common List.........................................................................................................17-31
17.4.10 Adding the CFS Public List...........................................................................................................17-32
17.4.11 Adding the CFS Service User........................................................................................................17-33
17.4.12 Adding the CFS User Number Range............................................................................................17-35
17.4.13 Setting CFS Service Software Parameters.....................................................................................17-37
17.5.1 Example Description (Black List Service).......................................................................................17-40
17.5.2 Example Description (White List Service)......................................................................................17-44
18 Configuring Message Duplication Service Data.............................................................18-1

18.1 Message Duplication Service......................................................................................................................18-2
18.2 Network Structure.......................................................................................................................................18-2
18.3 Service Implementation Principle...............................................................................................................18-3
18.4 Call Flow.....................................................................................................................................................18-4
18.5.2 Data Configuration Requirement on Interconnected Equipment.......................................................18-7
18.5.3 Data Collection...................................................................................................................................18-7
18.5.4 Configuration Description..................................................................................................................18-7
18.5.5 General Procedures............................................................................................................................18-8
18.6 Data Configuration......................................................................................................................................18-8
18.6.1 Adding the Reroute OPC....................................................................................................................18-9
18.6.2 Adding the Reroute DPC..................................................................................................................18-10
18.6.3 Adding the Reroute Called GT.........................................................................................................18-12
18.6.4 Adding the Reroute Calling GT.......................................................................................................18-14
18.6.5 Adding the Reroute Operation Code................................................................................................18-16
18.6.6 Adding the Reroute Rule..................................................................................................................18-18
18.6.7 Adding the Reroute Called GT Range.............................................................................................18-21
18.6.8 Adding the Reroute Calling GT Range............................................................................................18-22
18.6.9 Adding the Reroute Number............................................................................................................18-23
18.6.10 Adding M3UA and MTP Link Set Data........................................................................................18-24
18.7 Configuration Example.............................................................................................................................18-27
18.7.1 Example............................................................................................................................................18-27
Issue 02 (2009-12-14) Huawei Proprietary and Confidential xvii

Feature Description Figures
Figures
Figure 1-1 Networking structure of the called SMR service................................................................................1-3

Figure 1-2 Relation between SMR service data tables.........................................................................................1-5
Figure 2-1 Networking of the calling SMR service.............................................................................................2-3
Figure 2-2 Relation between SMR service data tables.........................................................................................2-5
Figure 3-1 Networking structure of the IMEI Catch service................................................................................3-3
Figure 3-2 Not being connected with the EIR......................................................................................................3-4
Figure 3-3 Being connected with the EIR............................................................................................................3-5
Figure 3-4 Reference relation between IMEI service data...................................................................................3-7
Figure 4-1 PLMN networking structure with the MNP service...........................................................................4-3
Figure 4-2 PSTN networking structure with the MNP service............................................................................4-4
Figure 4-3 Calling a foreign number not ported in user.......................................................................................4-5
Figure 4-4 Calling a foreign number ported in user or an own number not ported out user................................4-6
Figure 4-5 Calling an own number ported out user..............................................................................................4-7
Figure 4-6 Sending non-call-related messages to a foreign number ported in user or an own number not ported out
user (1)...................................................................................................................................................................4-8
Figure 4-7 Sending non-call-related messages to a foreign number ported in user or an own number not ported out
user (2)...................................................................................................................................................................4-8
Figure 4-8 Sending non-call-related messages to an own number ported out or a foreign number user (1).......4-9
Figure 4-9 Sending non-call-related messages to an own number ported out or a foreign number user (2).....4-10
Figure 4-10 An IN service user calling an own number not ported out user or a foreign number ported in user
.............................................................................................................................................................................4-11
Figure 4-11 An IN service user calling an own number ported out user, a foreign number ported to a foreign
network user, or a foreign network unknown user..............................................................................................4-12
Figure 4-12 A local network ordinary user calling an MNP user...................................................................... 4-13
Figure 4-13 A local network ordinary user calling a mobile non-NP user........................................................ 4-13
Figure 4-14 A local network pre-paid user calling an MNP user.......................................................................4-14
Figure 4-15 A local network pre-paid user calling a mobile non-NP user.........................................................4-15
Figure 4-16 A foreign network ordinary user calling an MNP user ..................................................................4-16
Figure 4-17 A foreign network ordinary user calling a mobile non-NP user.....................................................4-16
Figure 4-18 MNP query service flow in ATI mode...........................................................................................4-17
Figure 4-19 Mapping between MNP service data tables....................................................................................4-23
Figure 5-1 Networking structure of CRBT service..............................................................................................5-4
Figure 5-2 CRBT calling flow based on virtual roaming.....................................................................................5-6
Figure 5-3 CRBT calling flow based on AIP prefix............................................................................................5-7
Issue 02 (2009-12-14) Huawei Proprietary and Confidential xix

Figures Feature Description
Figure 5-4 Modifying setting or querying CRBT through WEB.......................................................................5-10

Figure 5-5 Modifying setting or querying CRBT through phone......................................................................5-11
Figure 5-6 Relation between CRBT data tables.................................................................................................5-18
Figure 6-1 Networking for the B&W lists and number change service...............................................................6-3
Figure 6-2 Flow of the B&W lists and number change service...........................................................................6-4
Figure 6-3 Relation between data tables for B&W lists and number change......................................................6-9
Figure 7-1 Networking of protocol translation service........................................................................................7-2
Figure 8-1 Firewall networking structure.............................................................................................................8-3
Figure 8-2 Mask rule tree 1..................................................................................................................................8-7
Figure 8-3 Mask rule tree 2..................................................................................................................................8-7
Figure 8-4 Mask conditions and reference numbers............................................................................................8-9
Figure 8-5 Relation between firewall data tables...............................................................................................8-15
Figure 9-1 Networking structure of MC service..................................................................................................9-3
Figure 9-2 Relation between MC service data tables...........................................................................................9-4
Figure 10-1 Networking structure of the FNR service - subscriber migration among networks of different carriers
.............................................................................................................................................................................10-3
Figure 10-2 Networking structure of the FNR service - subscriber migration among different HLRs within the
same network.......................................................................................................................................................10-4
Figure 10-3 Relation between FNR service data tables.....................................................................................10-7
Figure 11-1 A typical SMI service networking structure...................................................................................11-3
Figure 12-1 Networking structure of CDMA and GSM MNP service..............................................................12-6
Figure 12-2 Flow of a CDMA user calling a CDMA user ................................................................................12-7
Figure 12-3 Flow of a CDMA user calling a GSM user....................................................................................12-8
Figure 12-4 Flow of a GSM user calling a GSM user........................................................................................12-9
Figure 12-5 Flow of a GSM user calling a CDMA user..................................................................................12-10
Figure 12-6 Flow of querying the NPDB in the CDMA network by the NPREQ message............................12-11
Figure 12-7 Relations between MNP service data tables.................................................................................12-15
Figure 13-1 Networking structure of the IPR service........................................................................................13-5
Figure 13-2 An outbound subscriber accesses the preferential network directly...............................................13-6
Figure 13-3 An outbound subscriber accesses the preferential network by preferred roaming function...........13-7
Figure 13-4 An inbound subscriber accesses this network by anti-preferred roaming function........................13-9
Figure 13-5 Mapping between data tables related to the IPR service..............................................................13-12
Figure 14-1 Networking of the IRVAS Service.................................................................................................14-5
Figure 14-2 Location Updating Flow Chart.......................................................................................................14-6
Figure 14-3 VLR Error Recovery Flow Chart...................................................................................................14-8
Figure 14-4 Subscriber Data Insertion Flow of the HLR...................................................................................14-9
Figure 14-5 Call Routing Flow........................................................................................................................14-10
Figure 15-1 Networking structure of the IN BYPASS service..........................................................................15-4
Figure 15-2 Signaling flow of the IN BYPASS service.....................................................................................15-5
Figure 15-3 General signaling flow....................................................................................................................15-6
Figure 15-4 Relations between data tables in the IN BYPASS service.............................................................15-7
Figure 16-1 Networking structure of the message reroute service ....................................................................16-4
Figure 16-2 Signaling flow of the message reroute service...............................................................................16-6
xx Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Feature Description Figures
Figure 16-3 Relations between the data tables related to the message reroute service .....................................16-8
Figure 17-1 Networking structure for implementing the CFS black&white lists service..................................17-5
Figure 17-2 Call release flow for the ISUP-IAM message................................................................................ 17-7
Figure 17-3 Call release flow for the INAP-IDP message.................................................................................17-7
Figure 17-4 Call connection flow for the ISUP-IAM message..........................................................................17-9
Figure 17-5 Call connection flow for the INAP-IDP message...........................................................................17-9
Figure 17-6 Call release flow for the ISUP-IAM message..............................................................................17-11
Figure 17-7 Call connection flow for the ISUP-IAM message........................................................................17-12
Figure 17-8 Relations between the data tables for configuring the black list service......................................17-15
Figure 17-9 Relations between the data tables for configuring the white list service......................................17-16
Figure 18-1 Typical network structure for implementing the message duplication service.............................. 18-3
Figure 18-2 Message processing flow of the message duplication service........................................................18-4
Figure 18-3 Relations between the data tables related to the message duplication service...............................18-6
Issue 02 (2009-12-14) Huawei Proprietary and Confidential xxi

Feature Description Tables
Tables
Table 1-1 Data to be collected..............................................................................................................................1-6

Table 1-2 General steps........................................................................................................................................1-6
Table 1-3 Related commands for configuring the software configuration parameter..........................................1-7
Table 1-4 Related commands for configuring the virtual SMSC address............................................................1-8
Table 1-5 Related commands for configuring new SMSC address mapping table..............................................1-9
Table 1-6 Related commands for configuring the GT........................................................................................1-11
Table 1-7 SMR service data collected................................................................................................................1-12
Table 1-8 GT translation data collected.............................................................................................................1-13
Table 2-1 Data to be collected..............................................................................................................................2-6
Table 2-3 Related commands for configuring the software configuration parameter..........................................2-7
Table 2-4 Related commands for configuring the SMS configuration................................................................2-8
Table 2-5 Related commands for configuring the new SMSC address mapping table........................................2-9
Table 2-6 Related commands for configuring the GT........................................................................................2-11
Table 2-7 SMR service data collected................................................................................................................2-12
Table 2-8 GT translation data collected.............................................................................................................2-13
Table 3-1 Data collection table.............................................................................................................................3-7
Table 3-2 GT translation data configured on VMSC and SGSN.........................................................................3-8
Table 3-3 VMSC and SGSN data configured on the SG.....................................................................................3-8
Table 3-4 EIR data configured on the SG............................................................................................................3-8
Table 3-5 Steps to configure IMEI Catch service data.........................................................................................3-8
Table 3-6 Related commands for configuring the net information configuration table.....................................3-10
Table 3-7 Related commands for configuring the board....................................................................................3-11
Table 3-8 Related commands for configuring the IMEI Catch configuration table...........................................3-12
Table 3-9 Related commands for configuring the service user data..................................................................3-12
Table 3-10 Data collection table.........................................................................................................................3-13
Table 4-1 Local office information data.............................................................................................................4-24
Table 4-2 User information data.........................................................................................................................4-24
Table 4-3 Steps of configuring the MNP service data........................................................................................4-24
Table 4-4 Related commands for configuring the MNP software configuration parameter..............................4-35
Table 4-5 Related commands for configuring the HLR address........................................................................4-36
Table 4-6 Related commands for configuring the MNP route number..............................................................4-37
Table 4-7 Related commands for configuring the foreign number range..........................................................4-38
Issue 02 (2009-12-14) Huawei Proprietary and Confidential xxiii

Tables Feature Description
Table 4-8 Related commands for configuring the service user data..................................................................4-39
Table 4-9 Local office information collection table...........................................................................................4-40
Table 4-10 User data collection table.................................................................................................................4-41
Table 5-1 Differences between original ring back tone and CRBT.....................................................................5-2
Table 5-2 Data to be collected............................................................................................................................5-19
Table 5-3 Steps for configuring the CRBT data.................................................................................................5-20
Table 5-4 Related commands for configuring the dummy ramble number........................................................5-21
Table 5-5 Mapping between PMC number and rack number, service frame number, and slot number............5-25
Table 5-6 Related commands for configuring the CRBT software parameter...................................................5-26
Table 5-7 Related commands for configuring the prefix analysis table.............................................................5-26
Table 5-8 Related commands for configuring the provincial VMSC number range.........................................5-27
Table 5-9 Related commands for configuring the user number range...............................................................5-28
Table 5-10 Related commands for configuring the CRBT user data.................................................................5-29
Table 5-11 Related commands for configuring the RBT GT number range......................................................5-30
Table 5-12 Related commands for configuring the CRBT user number range..................................................5-31
Table 6-1 Data collection table...........................................................................................................................6-10
Table 6-2 Steps for configuring the data of the B&W lists and number change................................................6-12
Table 6-3 Related commands for configuring the MTP link set........................................................................6-14
Table 6-4 Related commands for configuring the operator number range table................................................6-14
Table 6-5 Related Commands for configuring the dummy number table..........................................................6-15
Table 6-6 Related commands for configuring the DSP index reference............................................................6-16
Table 6-7 Related commands for configuring the calling B&W list..................................................................6-17
Table 6-8 Related commands for configuring the called B&W list...................................................................6-18
Table 6-9 Related commands for configuring the number operation.................................................................6-19
Table 6-10 Related commands for configuring the calling number transform..................................................6-21
Table 6-11 Related commands for configuring the called number transform....................................................6-21
Table 6-12 Related commands for configuring the CPC...................................................................................6-22
Table 7-1 Protocol translation service data to be collected..................................................................................7-4
Table 7-3 Related commands for configuring the MTP pc convert.....................................................................7-5
Table 7-4 Related commands for configuring the ...............................................................................................7-6
Table 7-5 Data collection table.............................................................................................................................7-6
Table 8-1 Mask table structure.............................................................................................................................8-5
Table 8-2 Structure of the mask rule link.............................................................................................................8-5
Table 8-3 Initial mask table..................................................................................................................................8-6
Table 8-4 OPC mask table....................................................................................................................................8-6
Table 8-5 MAP content mask table......................................................................................................................8-6
Table 8-6 The description of subsystem numbers..............................................................................................8-12
Table 8-8 Steps to configure the firewall mask data..........................................................................................8-16
xxiv Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Table 8-9 Relation between the PMC number and the slot number ..................................................................8-19
Table 8-10 Related commands for configuring the firewall software configuration parameter........................8-20
Table 8-11 Related commands for configuring the FW MAP content masking................................................8-21
Table 8-12 Related commands for configuring the FW operation code set.......................................................8-22
Table 8-13 Related commands for configuring the ...........................................................................................8-22
Table 8-14 Related commands for configuring the FW operation code masking..............................................8-24
Table 8-15 Related commands for configuring the FW called GT masking......................................................8-26
Table 8-16 Related commands for configuring the FW calling GT masking....................................................8-28
Table 8-17 Related commands for configuring the ...........................................................................................8-29
Table 8-18 Related commands for configuring the FW OPC masking..............................................................8-31
Table 8-19 Related commands for configuring the FW link set public default masking...................................8-32
Table 8-20 Related commands for configuring the FW link set public masking...............................................8-33
Table 8-21 Related commands for configuring the FW initial masking............................................................8-34
Table 8-22 Related commands for configuring the MTP link set......................................................................8-35
Table 8-24 Related commands for configuring the FW alarm configuration....................................................8-38
Table 8-26 Related commands for configuring the FW statistics configuration................................................8-40
Table 8-27 Related commands for configuring the FW SMSC address statistics configuration.......................8-41
Table 9-1 MC service data to be collected...........................................................................................................9-5
Table 9-2 Configuration steps..............................................................................................................................9-5
Table 9-3 Related commands for configuring the SMS intercept configuration..................................................9-7
Table 9-4 Related commands for configuring the MC routing number...............................................................9-8
Table 9-5 Related commands for configuring the MC local SMSC address.......................................................9-9
Table 9-6 Related commands for configuring the service user data....................................................................9-9
Table 9-7 Related commands for configuring the sub MSISDN.......................................................................9-11
Table 10-1 The MNP software configuration parameter to be collected...........................................................10-7
Table 10-2 MNP prefix mapping management to be collected..........................................................................10-7
Table 10-3 Service user data to be collected......................................................................................................10-8
Table 10-4 Configuration steps..........................................................................................................................10-8
Table 10-5 Related commands for configuring the HLR address......................................................................10-9
Table 10-6 Related commands for configuring the MNP software configuration parameter..........................10-10
Table 10-7 Related commands for configuring the MNP prefix mapping management.................................10-11
Table 10-8 Related commands for configuring the service user data..............................................................10-12
Table 10-9 The MNP software configuration parameter to be collected.........................................................10-13
Table 10-10 MNP prefix mapping management to be collected......................................................................10-13
Table 10-11 Service user data to be collected..................................................................................................10-13
Table 11-2 General steps....................................................................................................................................11-5
Table 11-3 Related commands for configuring the SMS intercept configuration..............................................11-6
Issue 02 (2009-12-14) Huawei Proprietary and Confidential xxv

Table 12-1 Local office information data table................................................................................................12-16

Table 12-2 User information data table............................................................................................................12-17
Table 12-3 Steps of configuring the MNP service data....................................................................................12-17
Table 12-4 Related commands for configuring the software configuration parameter....................................12-19
Table 12-5 Related commands for configuring the MNP software configuration parameter..........................12-20
Table 12-6 Related commands for configuring the HLR address....................................................................12-21
Table 12-7 Related commands for configuring the MNP route number..........................................................12-22
Table 12-8 Related commands for configuring the MNP local network number range.................................. 12-23
Table 12-9 Related commands for configuring the MNP foreign number range.............................................12-24
Table 12-10 Related commands for configuring the service user data............................................................ 12-26
Table 12-11 Local office information collection table.....................................................................................12-26
Table 12-12 User data collection table.............................................................................................................12-27
Table 13-1 Table for collecting the preferred roaming public data..................................................................13-12
Table 13-2 Table for collecting the preferred roaming data.............................................................................13-13
Table 13-3 Table for collecting the anti-preferred roaming data..................................................................... 13-13
Table 13-4 General steps for configuring the IPR service data........................................................................13-13
Table 13-5 Related commands for configuring the IPR user group table........................................................13-17
Table 13-6 Related commands for configuring the IPR network table............................................................13-18
Table 13-7 Related commands for configuring the outbound roaming user group table.................................13-19
Table 13-8 Related commands for configuring the inbound roaming user group table...................................13-20
Table 13-9 Table for collecting the preferred roaming public data..................................................................13-21
Table 13-10 Table for collecting the preferred roaming data...........................................................................13-21
Table 13-11 Table for collecting the anti-preferred roaming data................................................................... 13-21
Table 14-1 Local office data collection table...................................................................................................14-13
Table 14-2 Subscriber data collection table (Camel MSC Number Range Table)...........................................14-14
Table 14-3 Steps for configuring the IRVAS service. .....................................................................................14-14
Table 14-4 Commands for Setting Software Parameters................................................................................. 14-16
Table 14-5 Commands for setting MNP software parameters.........................................................................14-17
Table 14-6 Commands for configure the HLR address. ..................................................................................14-19
Table 14-7 Local office data collection table...................................................................................................14-20
Table 14-8 Subscriber data collection table (CAMEL MSC Number Range Table).......................................14-20
Table 15-2 General procedures for configuring the IN BYPASS service data..................................................15-9
Table 15-3 Related commands for configuring the SMS software parameter................................................. 15-11
Table 15-4 Related commands for configuring the SCP address.....................................................................15-12
Table 15-5 Related commands for configuring the MNP local network number range.................................. 15-13
Table 15-6 Related commands for configuring the filter time segment...........................................................15-14
Table 15-7 Related commands for configuring the service user data ............................................................. 15-16
Table 15-8 Data collection table.......................................................................................................................15-17
Table 16-1 Matching relations between the data tables related to the SCCP reroute.........................................16-9
Table 16-2 Data collection table.......................................................................................................................16-10
Table 16-3 General procedures for configuring the message reroute service data ..........................................16-11
xxvi Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Table 16-4 Related commands for configuring the M3UA and MTP link sets............................................... 16-15
Table 16-5 Related commands for configuring the reroute OPC ....................................................................16-17
Table 16-6 Related commands for configuring the reroute DPC ....................................................................16-19
Table 16-7 Related commands for configuring the reroute called GT ............................................................16-21
Table 16-8 Related commands for configuring the reroute calling GT ...........................................................16-23
Table 16-9 Related commands for configuring the reroute operation code ....................................................16-25
Table 16-10 Related commands for configuring the reroute rule ....................................................................16-28
Table 16-11 Related commands for configuring the software configuration parameter .................................16-30
Table 16-12 Related commands for configuring the reroute called GT range table........................................16-30
Table 16-13 Related commands for configuring the reroute calling GT range table.......................................16-31
Table 16-14 Related commands for configuring reroute number table ...........................................................16-32
Table 16-15 SCCP reroute data collection table .............................................................................................16-33
Table 16-16 MAP reroute data collection table................................................................................................16-35
Table 17-1 Data to be collected for configuring the black list service.............................................................17-17
Table 17-2 Data to be collected for configuring the white list service.............................................................17-19
Table 17-3 General steps for configuring the black list service.......................................................................17-20
Table 17-4 General steps for configuring the white list service.......................................................................17-20
Table 17-5 Related commands for configuring service common software configuration parameters.............17-22
Table 17-6 Related commands for configuring software configuration parameters (two)..............................17-23
Table 17-7 Related commands for configuring the MTP DSP........................................................................17-24
Table 17-8 Related commands for configuring the number distinguishing type.............................................17-26
Table 17-9 Related commands for configuring the number analysis prefix....................................................17-28
Table 17-10 Related commands for configuring the CFS call type.................................................................17-29
Table 17-11 Related commands for configuring the CFS shielding release cause..........................................17-30
Table 17-12 Related commands for configuring the CFS personal list...........................................................17-31
Table 17-13 Related commands for configuring the CFS common list...........................................................17-32
Table 17-14 Related commands for configuring the CFS public list...............................................................17-33
Table 17-15 Related commands for configuring the CFS service user............................................................17-35
Table 17-16 Related commands for configuring the CFS user number range.................................................17-36
Table 17-17 Related commands for configuring CFS service software parameters........................................17-40
Table 17-18 Data collected for configuring the CFS black list service............................................................17-40
Table 17-19 Data collected for configuring the CFS white list service...........................................................17-44
Table 18-2 General procedures for configuring the message duplication service data......................................18-8
Table 18-3 Related commands for configuring the reroute OPC ....................................................................18-10
Table 18-4 Related commands for configuring the reroute DPC ....................................................................18-12
Table 18-5 Related commands for configuring the reroute called GT ............................................................18-14
Table 18-6 Related commands for configuring the reroute calling GT ...........................................................18-16
Table 18-7 Related commands for configuring the reroute operation code ....................................................18-18
Table 18-8 Related commands for configuring the reroute rule ......................................................................18-21
Table 18-9 Related commands for configuring the reroute called GT range table..........................................18-22
Table 18-10 Related commands for configuring the reroute calling GT range table.......................................18-23
Issue 02 (2009-12-14) Huawei Proprietary and Confidential xxvii

Table 18-11 Related commands for configuring reroute number table ...........................................................18-24
Table 18-12 Related commands for configuring the M3UA and MTP link set data.......................................18-26
Table 18-13 Data collected for configuring the message duplication service..................................................18-27
xxviii Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Feature Description 1 Configuring Called SMR Service Data
1 Configuring Called SMR Service Data
About This Chapter
In the called short message routing (SMR) service, short messages can be routed to different
short message service centers (SMSCs) for processing based on different called numbers. Before
configuring the called SMR service data, make sure that the hardware data, MTP data, and SCCP
data are configured.
1.1 Called SMR Service
In a network, the operator allocates a virtual SMSC (VSMSC) number to end users. All short
messages are sent to this VSMSC. The network then forwards the messages to their
corresponding SMSCs for processing based on the called numbers.
1.2 Service Flow
This section describes the networking structure for the called SMR service and the
implementation of the service.
1.3 Configuration Preparations
This section describes the background information, technical terms, and configuration steps to
be studied before data configuration.
1.4 Configuration Steps
Configuring the called SMR service including setting short message routing number type, adding
virtual SMSC address table, adding new SMSC address mapping table, adding SMSC GT
translation data, and adding VSMSC GT translation data.
1.5 Configuration Examples
This section provides examples to describe how to configure the called SMR service data.
Issue 02 (2009-12-14) Huawei Proprietary and Confidential 1-1

1 Configuring Called SMR Service Data Feature Description
1.1 Called SMR Service

Through the SMR service, operations of end users, network equipment maintenance, signaling
routing, and signaling flow are optimized, as specified below:
l Operations of end users are simplified. The configured SMSC addresses are no longer
affected by address or equipment change of the SMSC. Only one or a few general VSMSC
addresses are required for all terminals in the entire network.
l Network equipment maintenance is reduced. When adding, reducing, combining the SMSC
or changing the address of the SMSC, you do not need to change the SMSC addresses for
end users but only relevant data of the called numbers.
l Short message signaling routing is optimized. Through data configuration, short messages
can be directly routed to the home SMSC of the callees. In this way, the signaling routing
for the SMSC to query the home location register (HLR) is optimized.
l Signaling network traffic is reduced during short message retransmission. In the case of
message retransmission, because most of subscribers reside in the home locations, stored
messages are most probably retransmitted in home locations, thus reducing inter-network
signaling traffic.
1.2 Service Flow

This section describes the networking structure for the called SMR service and the
1.2.1 Networking Structure
This section describes the networking structure for configuring the called SMR service.
1.2.2 Service Implementation
This section describes the implementation of the called SMR service.

This section describes the networking structure for configuring the called SMR service.
Figure 1-1
1-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Figure 1-1 Networking structure of the called SMR service
VMSC: Visited Mobile Switching Center SG: U-SYS SG7000 Signaling Gateway
SMSC: Short Message Service Center
The devices in the networking and their functions are as follows:
l VMSC: When a user roams from a home MSC to another MSC, the latter is called the
VMSC. The VMSC implements short message signaling interaction between mobile
terminals.
l SG: The SG routes short message signaling based on the called number in the short message.
l SMSC: The SMSC stores and transfers short messages.

This section describes the implementation of the called SMR service.
The process of service implementation is as follows:
1. The VMSC transfers a short message to the SG.

2. Based on the called number in the message, the SG searches the configuration data for the
SMSC address.

3. The SG routes the short message to the SMSC.

1.3.1 Terms
The VSMSC stands for the virtual short message service center. Operators use the VSMSC to
replace the SMSC. End users send messages to the VSMSC. The virtual SMSC address table
lists VSMSCs of the entire network.
1.3.2 Configuration Principles
You must follow certain principles to configure the called SMR service data.
1.3.3 Relation Between Data Tables
Parameters in the virtual SMSC address table, SMSC address mapping table, SMSC GT
translation, and VSMSC GT translation can be configured respectively regardless of the
sequence.
1.3.4 Data Collection
Before configuring the called SMR service data, you must collect the data including the virtual
SMSC number, actual SMSC number, and actual SMSC DPC index.
1.3.5 General Steps
You must follow certain procedures to configure the called SMR service data.
1.3.1 Terms

You must follow certain principles to configure the called SMR service data.
Configuring Short Message Routing Number Type
Short message routing number type is configured in the software configuration parameter table
with the command SET SOFTCFG.
Configuring Virtual SMSC Address Table
VSMSC addresses are used to filter the signaling of short messages. Different VSMSC addresses
can be configured in a network at the same time. If the SMSC address in a message is not in the
virtual SMSC address table, the message is discarded.
Configuring SMSC Address Mapping Table

The SMSC address mapping table configures the called number range and its corresponding
SMSC address.

l When the called number contained in a message belongs to this number range, the message
to this number is routed to the corresponding SMSC based on this number.
l When the called number contained in a message does not belong to this number range, the
system processes the message based on the settings of the Special user SMR switch
parameter in the SMS service software parameter table.
– When Special user SMR switch is set to Close, the SMSC transparently transfers the
message.
– When Special user SMR switch is set to Open, the SMSC queries the user attribute
table based on the called number. The subsequent processing flow is determined by user
services configured in the user attributed table.
Configuring SMSC GT Translation

In this part, you must configure the GT translation data which maps the SMSC address.
Each SMSC needs to be configured with relevant GT translation data.
NOTE
The translation result type is determined depending on the actual conditions. This chapter considers DPC
+GT type as an example.
Configuring VSMSC GT Translation

In this part, you must configure the GT translation data mapping the VSMSC address for
translating a VSMSC address to an operator-determined SMSC address. If the SG7000 cannot
find the called number in the configured VSMSC, it performs the GT translation based on the
SMSC address carried in the message, and then sends the translation result to an SMSC.
Each VSMSC needs to be configured with relevant GT translation data.
NOTE
l The system does not process the XUDT message, so the VSMSC GT translation is directly executed
on the XUDT message.
l The GT translation result type is determined according to the actual conditions. This chapter considers
DPC+GT type as an example.

Parameters in the virtual SMSC address table, SMSC address mapping table, SMSC GT
translation, and VSMSC GT translation can be configured respectively regardless of the
sequence.
Relation Between SMR Service Data Tables
Figure 1-2 Relation between SMR service data tables

Relation Between SMR Service Data Table and Other Data Table
The SMR service data uses the DSP index related to the MTP data. The VSMSC GT translation
and SMSC GT translation use the index in the command ADD N7DSP. For details, see chapter
Configuring MTP Data.

Before configuring the called SMR service data, you must collect the data including the virtual
SMSC number, actual SMSC number, and actual SMSC DPC index.
Before data configuration, you must collect the data listed in Table 1-1.
Table 1-1 Data to be collected

VSMSC address Start End SMSC address SMSC DPC
number number index
range range
The GT translation data to be collected is determined based on the actual GT translation result
type. For details, see chapter Configuring SCCP Data.
1.3.5 General Steps

You must follow certain procedures to configure the called SMR service data.
Table 1-2 lists the general steps to configure the called SMR service data.
Table 1-2 General steps

Step Operation
1 To set short message routing number type
2 To add virtual SMSC address table
3 To add new SMSC address mapping table
4 To add SMSC GT translation data
5 To add VSMSC GT translation data
1.4 Configuration Steps

Configuring the called SMR service including setting short message routing number type, adding
virtual SMSC address table, adding new SMSC address mapping table, adding SMSC GT
translation data, and adding VSMSC GT translation data.

1.4.1 Setting Short Message Routing Number Type

This section describes the command, parameter, and related commands for configuring the called
SMR service data.
1.4.2 Adding Virtual SMSC Address Table
This section describes the command, parameter, and related commands for adding the virtual
SMSC address table.
1.4.3 Adding New SMSC Address Mapping Table
This command is used to add an SMSC address in a network and bind the called number range
to the SMSC address.
1.4.4 Adding SMSC GT Translation Data
This command is used to add the SMSC GT translation data.
1.4.5 Adding VSMSC GT Translation Data
Adding VSMSC GT translation is similar to adding the SMSC GT translation. Note that DPC
index maps an SMSC and Address message should be configured with the VSMSC address.

SMR service data.
After configuration, the system checks whether the switch of Called number is enabled. If yes,
the SMR service is the called SMR service.
Command
SET SOFTCFG
Parameter
Paramete Paramete Parameter Description
r ID r Name
ISMRTY SMS It can be set to Calling number or Called number. Here, you must
PE routing select Called number.
type
Related Commands
Table 1-3 Related commands for configuring the software configuration parameter
Command Function
SET SOFTCFG To set the software configuration parameter
LST SOFTCFG To query the software configuration parameter

1.4.2 Adding Virtual SMSC Address Table

SMSC address table.
After configuration, the system checks the SMSC in a short message to ensure that it is
configured with this command.
Command
ADD SMRVSMSC
Parameter
r ID r Name
VNUM Virtual It defines a VSMSC address for an end user in a network. Multiple
SMSC VSMSCs can be configured in a network based on network
address planning.
This parameter requires the support of the GT translation data.
Related Commands
Table 1-4 Related commands for configuring the virtual SMSC address
Command Function
ADD SMRVSMSC To add virtual SMSC address
MOD SMRVSMSC To modify virtual SMSC address
RMV SMRVSMSC To delete virtual SMSC address
LST SMRVSMSC To query virtual SMSC address
1.4.3 Adding New SMSC Address Mapping Table

This command is used to add an SMSC address in a network and bind the called number range
After configuration, messages can be routed to the SMSC based on the called numbers.
Command
ADD SMRSMCMAP

Parameter
r ID r Name
CNUMS Start They define a called number range. Multiple number ranges can
number be configured for an SMSC based on network planning.
range Number ranges cannot be overlapped.
CNUME End
number
range
SNUM SMSC It defines an SMSC address. Multiple SMSC addresses can be

address configured in a network based on network planning. SMSC
addresses can be identical among called number ranges. One called
number range, however, maps one SMSC only.
Related Commands
Table 1-5 Related commands for configuring new SMSC address mapping table
Command Function
ADD SMRSMCMAP To add new SMSC address mapping table
MOD SMRSMCMAP To modify new SMSC address mapping table
RMV SMRSMCMAP To delete new SMSC address mapping table
LST SMRSMCMAP To query new SMSC address mapping table

Command
ADD SCCPGT
Parameter
r ID r Name
NI Network It specifies a network for the DPC in the GT translation result. The
indication "Network indication + DPC" configured here must be defined in
the MTP DSP table before being used here.


r ID r Name
RT Translatio It specifies a type of GT translation result, which includes the

n result following:
type l STP1: indicating the type is "DPC + GT".
l LSPC1: indicating the type is "DPC + SSN".
l STP2: indicating the type is "DPC + NEWGT".
l LSPC2: indicating the type is DPC.
This chapter specifies the type "DPC + GT" as an example.
WM GT work It defines a work mode of GT translation, which includes the

mode following:
l Single point work mode: In this mode, Index of SCCP
Addressing Policy is not required.
l Multi-point work mode: In this mode, Index of SCCP
Addressing Policy is required.
NOTE
When GT work mode is set to Multi-point work mode, parameters DPC
index and SSN code are not required.
This chapter specifies single point work mode as an example.
DX DPC It specifies a DPC indexed after translation, which is configured

index in the MTP DSP table.
Here, you must enter the DPC of the SMSC.
GT GT It specifies GT indicators, which includes the following:

indicator l GT1 (ITU GT1)
l GT2 (ITU GT2)
l GT3 (ITU GT3)
l GT4 (ITU GT4)
l GT5 (ANSI GT1)
l GT6 (ANSI GT2)
It is generally set to GT4.


r ID r Name
CP Numberin It is the numbering plan of the GT. It specifies the coding mode of
g plan the address, which includes the following:
l UNDEF (undefined)
l ISDN (ISDN/telephone code plan)
l STANDBY (Standby)
l DATA (Data code plan)
l TELEX (Telex code plan)
l MARINE (Marine move code plan)
l LAND (Land move code plan)
l ISDNMOV (ISDN/move code plan)
This chapter specifies ISDN mode as an example.
AI Nature of It specifies the nature of the address indicator, which includes the
Address following:
indicator l FREE (Idle)
l USRCODE (Subscriber number)
l NS (National reserved)
l NM (National valid number)
l INTER (International number)
Generally, INTER is adopted. This chapter specifies INTER as
an example.
AF Address It specifies a user number to be translated based on the GT. This

message number is composed of country code, area code, and user number.
The number can be up to 24 digits. Take "(86) (755) 2896-0132"
as an example. Here, 86 is the country code, 755 is the area code,
and 2896-0132 is the user number.
Wildcard characters "E" or "e" can be used in the address message
to represent all numbers. For example, "(86) (755) 2896-EEEE"
represents all numbers with the prefix "(86) (755) 2896".
Here, you must enter the SMSC address.
Related Commands
Table 1-6 Related commands for configuring the GT

Command Function
ADD SCCPGT To add the GT
MOD SCCPGT To modify the GT

Command Function
RMV SCCPGT To remove the GT
LST SCCPGT To query the GT table
1.4.5 Adding VSMSC GT Translation Data

Adding VSMSC GT translation is similar to adding the SMSC GT translation. Note that DPC
index maps an SMSC and Address message should be configured with the VSMSC address.

This section provides examples to describe how to configure the called SMR service data.
SMR Service Networking

The networking structure is as shown in Figure 1-1.
Collecting SMR Service Data

This chapter specifies the data related to the SMR service only.
Suppose there are VSMSC-A, SMSC-A, and SMSC-B.
After the GT translation, the address of VSMSC-A is translated to SMSC address A.
Table 1-7 lists the SMR service data collected.
Table 1-7 SMR service data collected

Address of SMSC-A
VSMSC-A
Start number End number Address of DPC index

range range SMSC-A
134001001000 134001001100 132001001001 1
132001001000 SMSC-B
Start number End number Address of DPC index

range range SMSC-B
134001001101 134001001200 132001001002 2
GT Configuration Parameters
Configure the parameters based on the actual situations. Here, take the type "DPC + GT" as an
example.
Table 1-8 lists the parameters collected for configuring the GT translation.

Table 1-8 GT translation data collected

Network Translation result GT work GT indicator
indicator type mode
National DPC+GT Single point GT4

work mode
Numbering plan Nature of Address

indicator
ISDN International
number
Procedure
Step 1 Add virtual SMSC address table.
To add a record in the virtual SMSC address table, set Description to VSMSC-A and Virtual
SMSC address to 132001001000, run the following command:
ADD SMRVSMSC: DESC="VSMSC-A", VNUM="132001001000";
After the command is run, a VSMSC address is added.

Step 2 Add new SMSC address mapping table.
1. To add a record in the SMSC address mapping table, set Description to SMSC-A, Start
number range A to 134001001000, End number range A to 134001001100, and SMSC
address A to 132001001001, run the following command:
ADD SMRSMCMAP: DESC="SMSC-A", CNUMS="134001001000",
CNUME="134001001100", SNUM="132001001001";
After the command is run, the address of SMSC-A and its corresponding called number
range are added.
2. Similarly, to set Description to SMSC-B, Start number range B to 134001001101, End
number range B to 134001001200, and SMSC address B to 132001001002, run the
following command:
ADD SMRSMCMAP: DESC="SMSC-B", CNUMS="134001001101",
CNUME="134001001200", SNUM="132001001002";
After the command is run, the address of SMSC-B and its corresponding called number
range are added.
Step 3 Add SMSC GT translation.
1. To add a GT translation record, set Description to SMSC-A-GT, Network indicator to
National, Translation result type to DPC + GT, GT work mode to Single point work
mode, DPC index to 1, GT indicator to GT4, Numbering plan to ISDN, Nature of
address indicator to International number, and Address message to 132001001001, run
the following command:
ADD SCCPGT: DESC="SMSC-A-GT", NI=NM, RT=STP1, WM=SGWM, DX=1, GT=GT4,
CP=ISDN, AI=INTER, AF="132001001001";
After the command is run, a GT translation record of SMSC-A is added.

2. Similarly, set Description to SMSC-B-GT, Network indicator to National, Translation
result type to DPC + GT, GT work mode to Single point work mode, DPC index to 2,

GT indicator to GT4, Numbering plan to ISDN, Nature of address indicator to

International number, and Address message to 132001001002, run the following
command:
ADD SCCPGT: DESC="SMSC-B-GT", NI=NM, RT=STP1, WM=SGWM, DX=2, GT=GT4,
After the command is run, a GT translation record of SMSC-B is added.

Step 4 Add VSMSC GT translation.
To add a GT translation record, set Description to VSMSC-A-GT, Network indicator to
mode, DPC index to 1, GT indicator to GT4, Numbering plan to ISDN, Nature of address
indicator to International number, and Address message to 132001001000, run the following
command:
ADD SCCPGT: DESC="VSMSC-A-GT", NI=NM, RT=STP1, WM=SGWM, DX=1, GT=GT4,
After the command is run, a VSMSC GT translation record is added, which maps SMSC-A.
----End
Verifying the Short Message Routing Number Type

This step must be performed after you set the short message routing number type. To verify the
short message routing number type, run LST SOFTCFG on the MML client.
LST SOFTCFG:;
The results are displayed as follows:

The Software Configuration Parameter
------------------------------------
……
SMS routing type = called number

CDMA message routeing on DPC in self PC processed by MNP = call-related
message<ON>,short message<ON>
CDMA message routeing on DPC not in self PC processed by MNP = call-
related message<ON>,short message<ON>
CDMA message routeing on GT processed by MNP = call-related
SBPI SWAP SWITCH = OFF
--- END
In the displayed result, SMS routing type is Called number. The results are the same as the
configured data through the command, which indicates that the configuration is successful.
Verifying the Virtual SMSC Address

This step must be performed after you set the virtual SMSC address. To verify the virtual SMSC
address, run LST SMRVSMSC on the MML client.
LST SMRVSMSC:;

Virtual SMSC address table
--------------------------

IndexDescriptionVirtual SMSC address

0VSMSC-A132001001000
(Number of results = 1)
--- END
In the displayed result, Index is 1, Description is VMSC-A, and Virtual SMSC address is
132001001000. The results are the same as the configured data through the command, which
indicates that the configuration is successful.
Verifying SMSC Address Mapping

This step must be performed after you set the SMSC address mapping. To verify the SMSC
address mapping, run LST SMRSMCMAP on the MML client.
LST SMRSMCMAP:;

SMSC address mapping table
--------------------------
Index Description Start number range End number range
SMSC address
0 SMSC-A 134001001000 134001001100
132001001001
1 SMSC-B 134001001101 134001001200
132001001002
--- END
In the displayed result, Index is 0, Description is SMSC-A, Start number range A is

134001001000, End number range A is 134001001100, and SMSC address A is
132001001001.
In the displayed result, Index is 0, Description is SMSC-B, Start number range B is
134001001101, End number range B is 134001001200, and SMSC address B is
132001001002.
The results are the same as the configured data through the command, which indicates that the
configuration is successful.
Verifying the SMSC GT Translation

This step must be performed after you set the SMSC GT translation. To verify the SMSC GT
translation, run LST SCCPGT on the MML client.
LST SCCPGT: MAXNUM=1000;

The GT table
------------
Index Description Network indication Translation result type
GT indicator Translation type Numbering plan Nature
of Address indicator Address message convert prefix GT work
mode Index of SCCP Addressing Policy SSN
code DPC index New GT
index
310 SMSC-A-GT National DPC+GT
ITU GT4 0 ISDN/telephone code plan
International number 132001001001 Single point

work mode <NULL> 0-Not

defined 1 Not
used-65535
311 SMSC-B-GT National DPC+GT
defined 2 Not
used-65535
312 VSMSC-A-GT National DPC+GT
defined 1 Not
used-65535
--- END
In the displayed result, Index is 310, Description is SMSC-A-GT, Network indicator is

National, Translation result type is DPC + GT, GT work mode is Single point work
mode, DPC index is 1, GT indicator is ITU GT4, Numbering plan is ISDN/TELEPHONE
CODE PLAN, Nature of address indicator is International number, and Address
message is 132001001001
In the displayed result, Index is 311, Description is SMSC-B-GT, Network indicator is
mode, DPC index is 2, GT indicator is GT4, Numbering plan is ISDN, Nature of address
indicator is International number, and Address message is 132001001002.
In the displayed result, Index is 312, Description is VSMSC-A-GT, Network indicator is

Feature Description 2 Configuring Calling SMR Service Data
2 Configuring Calling SMR Service Data
About This Chapter
In the calling short message routing (SMR) service, short messages can be routed to different
short message service centers (SMSCs) for processing based on different calling numbers.
Before configuring the calling SMR service data, make sure that the hardware data, MTP data,
and SCCP data are configured.
2.1 Calling SMR Service
With the calling SMR service, the system can perform the load sharing function based on the
calling number in the short message.
2.2 Service Flow
This section describes the networking structure for the calling SMR service and the
2.4 Configuration Procedures
Configuring the calling SMR service includes setting the short message routing number type,
setting the virtual SMSC address, and setting the actual SMSC GT translation.
This section provides examples to describe how to configure the calling SMR service data.

2 Configuring Calling SMR Service Data Feature Description
2.1 Calling SMR Service

With the calling SMR service, the system can perform the load sharing function based on the
calling number in the short message.
2.1.1 Service Definition
The calling SMR service provides the load sharing function based on the calling number in the
message. In a network, the network operator allocates an SMSC number to end users. All short
messages are sent to this SMSC. The network then forwards the messages to their corresponding
SMSCs for processing based on the calling numbers.
2.1.2 Service Advantages
Through the calling SMR service, operations of end users and network equipment maintenance
are optimized.
2.1.3 Version Requirement
The calling SMR service has no special requirements on the hardware system.

The calling SMR service provides the load sharing function based on the calling number in the
message. In a network, the network operator allocates an SMSC number to end users. All short
messages are sent to this SMSC. The network then forwards the messages to their corresponding
SMSCs for processing based on the calling numbers.

Through the calling SMR service, operations of end users and network equipment maintenance
are optimized.
Operations of end users are simplified. The configured SMSC numbers are not affected by
address or equipment change of the SMSC. Only one or several SMSC numbers are required
for all the terminals in the entire network.
Network equipment maintenance is reduced. When adding, reducing, combining an SMSC or

changing the address of the SMSC, do not change the SMSC number for end users but only
relevant data of the calling numbers.

The calling SMR service has no special requirements on the hardware system.
2.2 Service Flow

This section describes the networking structure for the calling SMR service and the
This section describes the networking structure for configuring the calling SMR service.
This section describes the implementation of the calling SMR service.


This section describes the networking structure for configuring the calling SMR service.
The networking of the calling SMR service is as shown in Figure 2-1.
Figure 2-1 Networking of the calling SMR service
SMSC: Short Message Service Center
The devices in the networking and their functions are as follows:
l VMSC: When a user roams from a home MSC to another MSC, the latter is called the
VMSC. The VMSC implements short message signaling interaction with mobile terminals.
l SG: The SG routes short message signaling based on the calling number in the short
message.
l SMSC: The SMSC stores and transfers short messages.

This section describes the implementation of the calling SMR service.

The process of service implementation is as follows:
1. After receiving a short message, the VMSC transfers the message to the SG.
2. Based on the calling number in the message, the SG searches the configured data for the
SMSC number.
3. The SG routes the short message to the SMSC.

2.3.1 Terms
You must follow certain principles to configure the calling SMR service data.
Parameters in the SMSC address mapping table and SMSC GT translation can be configured
respectively regardless of the sequence.
Before configuring the calling SMR service, you must collect the data including the SMSC
address and the SMSC DPC index.
2.3.5 General Steps
You must follow certain procedures to configure the calling SMR service data
2.3.1 Terms

You must follow certain principles to configure the calling SMR service data.
Configuring Short Message Routing Number Type
Short message routing number type is configured in the software configuration parameter table
with the command SET SOFTCFG.
Configuring Default SMSC Address

The default SMSC address is configured in the short message software configuration parameter
table with the command SET SMSICSOFTCFG.

Configuring SMSC Address Mapping Table

The SMSC address mapping table configures the calling number range and its corresponding
SMSC number. When a user in this number range acts as a caller, the message sent by this user
is routed to the corresponding SMSC based on the calling number.
Configuring SMSC GT Translation

In this part, you must configure the GT translation data which maps the SMSC address.
Each SMSC needs to be configured with relevant GT translation data.
NOTE
The translation result type is determined depending on the actual conditions. This chapter considers "DPC
+ GT" type as an example.

Parameters in the SMSC address mapping table and SMSC GT translation can be configured
respectively regardless of the sequence.
Relation Between SMR Service Data Tables
Figure 2-2 Relation between SMR service data tables
Relation Between SMR Service Data Table and Other Data Table
The SMR service data uses the DSP index related to the MTP data. The SMSC GT translation
uses the index defined with the command ADD N7DSP. For details, see chapter Configuring
MTP Data.

Before configuring the calling SMR service, you must collect the data including the SMSC
address and the SMSC DPC index.

Start number End number SMSC number SMSC DPC index

range range
The GT translation data to be collected is determined based on the actual GT translation result
type, so it is not listed in the table. For details, see chapter Configuring SCCP Data.
2.3.5 General Steps

You must follow certain procedures to configure the calling SMR service data
Table 2-2 lists the general steps to configure the calling SMR service data.
Step Action
1 To set short message routing number type
2 To set default SMSC address
3 To add SMSC address mapping table
4 To add SMSC GT translation data

Configuring the calling SMR service includes setting the short message routing number type,
setting the virtual SMSC address, and setting the actual SMSC GT translation.
This section describes the command, parameter, and related commands for setting the short
message routing number type.
2.4.2 Setting Default SMSC Address
This section describes the command, parameter, and related commands for setting the default
SMSC address.
2.4.3 Adding SMSC Address Mapping Table
This command is used to add an SMSC address in a network and bind the calling number range

This section describes the command, parameter, and related commands for setting the short
message routing number type.

You can set SMS routing type to Calling number through the MML command.
After configuration, the system checks whether the switch of Calling number is enabled. If yes,
the SMR service is the calling SMR service.
Command
SET SOFTCFG
Parameter
r ID r Name
ISMRTY SMS It can be set to Calling number or Called number. Here, you must
PE routing select Calling number.
type
Related Commands
Command Function
2.4.2 Setting Default SMSC Address

This section describes the command, parameter, and related commands for setting the default
SMSC address.
You can set Service type to MO Load-share based on calling number through the MML
command.
Command
SET SMSICSOFTCFG

Parameter
r ID r Name
NTERMO Service It can be set to:

DE type l MT mode
l MC mode
l MO Load-share based on calling number
Here, you must select MO Load-share based on calling
number.
SDEFAU Default It specifies the default SMSC address. After being processed, the
LTSMSC SMS messages with the calling numbers that are not in the configured
center number range are sent to this default SMSC.
address
Related Commands
Table 2-4 Related commands for configuring the SMS configuration
Command Function
SET SMSICSOFTCFG To set SMS configuration
LST SMSICSOFTCFG To query SMS configuration
2.4.3 Adding SMSC Address Mapping Table

This command is used to add an SMSC address in a network and bind the calling number range
After configuration, messages can be routed to the SMSC based on the calling numbers.
Command
ADD SMRSMCMAP
Parameter
r ID r Name
CNUMS Start They define a calling number range. Multiple number ranges can
number be configured for an SMSC based on network planning.
range Number ranges cannot be overlapped.


r ID r Name
CNUME End
number
range
SNUM SMSC It defines an SMSC number. SMSC addresses can be identical

address among calling number ranges. One calling number range,
however, maps one SMSC only.
Related Commands
Table 2-5 Related commands for configuring the new SMSC address mapping table
Command Function
ADD SMRSMCMAP To add new SMSC address mapping table
MOD SMRSMCMAP To modify new SMSC address mapping table
RMV SMRSMCMAP To delete new SMSC address mapping table
LST SMRSMCMAP To query new SMSC address mapping table

Command
ADD SCCPGT
Parameter
r ID r Name
NI Network It specifies a network for the DPC in the GT translation result. The
indication "Network indication + DPC" configured here must be defined in
the MTP DSP table before being used here.
This chapter specifies the applications in China for examples.


r ID r Name
RT Translatio It specifies a type of GT translation result, which includes the

n result following:
type l STP1: indicating the type is "DPC + GT"
l LSPC1: indicating the type is "DPC + SSN"
l STP2: indicating the type is "DPC + NEWGT"
l LSPC2: indicating the type is DPC
This chapter specifies the type "DPC + GT" as an example.
WM GT work It defines a work mode of GT translation, which includes the

mode following:
l Single point work mode: In this mode, Index of SCCP
Addressing Policy is not required.
l Multi-point work mode: In this mode, Index of SCCP
Addressing Policy is required.
NOTE
When GT work mode is set to Multi-point work mode, parameters DPC
index and SSN code are not required.
This chapter specifies single point work mode as an example.
DX DPC It specifies a DPC indexed after translation, which is configured

index in the MTP DSP table.
Here, you must enter the DPC of the SMSC.
GT GT It specifies GT indicators, which includes the following:

indicator l GT1 (ITU GT1)
l GT2 (ITU GT2)
l GT3 (ITU GT3)
l GT4 (ITU GT4)
l GT5 (ANSI GT1)
l GT6 (ANSI GT2)
This chapter specifies GT4 as an example.


r ID r Name
CP Numberin It is the numbering plan of the GT. It specifies the coding mode of
g plan the address, which includes the following:
l UNDEF (undefined)
l STANDBY (Standby)
This chapter specifies ISDN mode as an example.
AI Nature of It specifies the nature of the address indicator, which includes the
Address following:
indicator l FREE (Idle)
Generally, INTER is adopted. This chapter specifies INTER as
an example.
AF Address It specifies a user number to be translated based on the GT. This

message number is composed of country code, area code, and user number.
The number can be up to 24 digits. Take "(86) (755) 2896-0132"
as an example. Here, 86 is the country code, 755 is the area code,
and 2896-0132 is the user number.
Wildcard characters "E" or "e" can be used in the address message
to stand for all numbers. For example, "(86) (755) 2896-EEEE"
stands for all numbers with the prefix "(86) (755) 2896".
Here, you must enter the SMSC address.
Related Commands
Table 2-6 Related commands for configuring the GT

Command Function
ADD SCCPGT To add the GT
MOD SCCPGT To modify the GT

Command Function
RMV SCCPGT To remove the GT
LST SCCPGT To query the GT table

This section provides examples to describe how to configure the calling SMR service data.
Calling SMR Service Networking

The networking structure is as shown in Figure 2-1.
Collecting Calling SMR Service Data

This chapter specifies the data related to the calling SMR service only.
Suppose there are VMSC-A, SMSC-A and SMSC-B. GT translation data of SMSC-A is
configured on the VMSC-A.
Table 2-7 lists the calling SMR service data collected.
Table 2-7 SMR service data collected

SMSC-A
Start number End number range Address of SMSC-A DPC index

range
134001001000 134001001100 132001001001 1
SMSC-B
Start number End number range Address of SMSC-B DPC index

range
134001001101 134001001200 132001001002 2
GT Configuration Parameters
Configure the parameters based on the actual situations. Here, take the type "DPC + GT" as an
example.
Table 2-8 lists the parameters collected for configuring the GT translation.

Table 2-8 GT translation data collected
Network Translation result GT work GT indicator

indicator type mode
National DPC+GT Single point GT4

work mode
Numbering plan Nature of Address

indicator
ISDN International
number
Procedure
Step 1 Adding SMSC Address Mapping Table
1. To add a record in the SMSC address mapping table, set Description to SMSC-A, Start
number range A to 134001001000, End number range A to 134001001100, and SMSC
address A to 132001001001, run the following command:
ADD SMRSMCMAP: DESC="SMSC-A", CNUMS="134001001000",
CNUME="134001001100", SNUM="132001001001";
After the command is run, the address of SMSC-A and its corresponding calling number
range are added.
2. Similarly, set Description to SMSC-B, Start number range B to 134001001101, End
number range B to 134001001200, and SMSC address B to 132001001002, run the
following command:
ADD SMRSMCMAP: DESC="SMSC-B", CNUMS="134001001101",
CNUME="134001001200", SNUM="132001001002";
After the command is run, the address of SMSC-B and its corresponding calling number
range are added.
Step 2 Adding SMSC GT Translation

1. To add a GT translation record, set Description to SMSC-A-GT, Network indicator to
mode, DPC index to 1, GT indicator to GT4, Numbering plan to ISDN, Nature of
address indicator to International number, and Address message to 132001001001, run
ADD SCCPGT: DESC="SMSC-A-GT", NI=NM, RT=STP1, WM=SGWM, DX=1, GT=GT4,
After the command is run, a GT translation record of SMSC-A is added.

2. Similarly, to set Description to SMSC-B-GT, Network indicator to National,
Translation result type to DPC + GT, GT work mode to Single point work mode, DPC
index to 2, GT indicator to GT4, Numbering plan to ISDN, Nature of address
indicator to International number, and Address message to 132001001002, run the
following command:
ADD SCCPGT: DESC="SMSC-B-GT", NI=NM, RT=STP1, WM=SGWM, DX=2, GT=GT4,

After the command is run, a GT translation record of SMSC-B is added.
----End
Verifying the SMS Routing Number Type

This step must be performed after you set the SMS routing number type. To verify the SMS
routing number type, run LST SOFTCFG on the MML client.
LST SOFTCFG:;

------------------------------------
……
SMS routing type = calling number

--- END
In the displayed result, SMS routing type is Calling number, The results are the same as the
Verifying the SMSC Address Mapping Table

This step must be performed after you set the SMSC address mapping table. To verify the SMSC
address mapping table, run LST SMRSMCMAP on the MML client.
LST SMRSMCMAP:;

SMSC address mapping table
--------------------------
Index Description Start number range End number range
SMSC address
0 SMSC-A 134001001000
134001001100 132001001001
1 SMSC-B 134001001101
134001001200 132001001002
--- END
In the displayed result, Index is 0, Description is SMSC-A, Start number range A is

134001001000, End number range A is 134001001100, and SMSC address A is
132001001001.
In the displayed result, Index is 0, Description is SMSC-B, Start number range B is

134001001101, End number range B is 134001001200, and SMSC address B is
132001001002.

Verifying the SMSC GT Translation

This step must be performed after you set the SMSC GT translation. To verify the SMSC GT
translation, run LST SCCPGT on the MML client.
LST SCCPGT: MAXNUM=1000;

The GT table
------------
Index Description Network indication Translation result type
GT indicator Translation type Numbering plan Nature
of Address indicator Address message convert prefix GT work
mode Index of SCCP Addressing Policy SSN
code DPC index New GT
index
310 SMSC-A-GT National DPC+GT
defined 1 Not
used-65535
311 SMSC-B-GT National DPC+GT
defined 2 Not
used-65535
312 VSMSC-A-GT National DPC+GT
defined 1 Not
used-65535
--- END
In the displayed result, Index is 310, Description is SMSC-A-GT, Network indicator is

In the displayed result, Index is 311, Description is SMSC-B-GT, Network indicator is
In the displayed result, Index is 312, Description is VSMSC-A-GT, Network indicator is

Feature Description 3 Configuring IMEI Catch Service Data
3 Configuring IMEI Catch Service Data
About This Chapter
This chapter describes the IMEI Catch service. With this service, the SG7000 can collect the
information of user terminals and then provide customized services to users according to the
types and locations of the terminals. Before configuring the IMEI Catch service data, make sure
that the hardware data, MTP data, and SCCP data are already configured.
3.1 IMEI Catch Service
With the development of mobile services, to auto obtain the information of mobile stations is a
crucial factor for the service development of a network. Network operators can get the IMEI
information of mobile stations through the network to get the types and functions of the phones.
This helps the operators to provide better services.
3.2 Service Flow
This section describes the networking structure for the IMEI Catch service and the
implementation and service flow of the service.
Configuring the IMEI Catch service includes adding network information, adding the SDUI,
and setting the IMEI Catch software parameter.
This section provides examples to describe how to configure the IMEI Catch service data.

3 Configuring IMEI Catch Service Data Feature Description
3.1 IMEI Catch Service

With the development of mobile services, to auto obtain the information of mobile stations is a
crucial factor for the service development of a network. Network operators can get the IMEI
information of mobile stations through the network to get the types and functions of the phones.
This helps the operators to provide better services.
For example, based on the types of mobile stations, the operators can:
l Send text or multimedia short messages to mobile stations.
l Configure GPRS data to mobile stations.
l Push related services to mobile stations.
This service enables operators to provide satisfactory and differentiated services.
3.2 Service Flow

This section describes the networking structure for the IMEI Catch service and the
implementation and service flow of the service.
This section describes the networking structure for configuring the IMEI Catch service.
This section describes the implementation of the IMEI Catch service.
3.2.3 Service Flow
This section describes the service flow of the IMEI Catch service.
3.2.4 Equipment Coordination Requirements
This section describes the cooperation requirements between equipment.

This section describes the networking structure for configuring the IMEI Catch service.
Figure 3-1 shows the networking structure of the IMEI Catch service.

Figure 3-1 Networking structure of the IMEI Catch service
SGSN: Serving GPRS Support Node -
Each SG7000 is connected with both the active and the standby TMSs. The networking structure
is for reference only. You must construct the network based on the capacity of the TMS and the
actual conditions.
The devices in the networking structure and their functions are as follows:
l VMSC: It is used to report the extended CHECK_IMEI message of the user to the SG.
l SG: It is used to extract user IMSI, MSISDN, and location information to the TMS.
l SGSN: It is used to report the extended CHECK_IMEI message of the user to the SG.
l TMS: It is used to manage and store user information.
The networking structure of the SG is as follows:
l It is located between the MSC/SGSN and the TMS/EIR.

l It is connected with the VMSC and SGSN through SS7 links.
l It is connected with the TMS through TCP/IP links.
l It is connected with the EIR through SS7 links and interacts with the EIR through standard
CHECK_IMEI messages.
l If there is no EIR, it simulates EIR messages to communicate with the MSC/SGSN.

l The addressing from the MSC and SGSN to the SG can be a load sharing mode over SCCP
layer.

This section describes the implementation of the IMEI Catch service.
The IMEI Catch service is implemented as follows:
1. The SG intercepts the CHECK_IMEI messages between the MSC/SGSN and the EIR.
2. The SG extracts from or queries the database to obtain the user IMSI, MSISDN, and location
information and then reports to the TMS.
3. The TMS collects the user information and then provides users with relevant services.
4. If there is no EIR, the SG should simulate the EIR.
3.2.3 Service Flow

This section describes the service flow of the IMEI Catch service.
The service flow is classified into two cases depending on whether there is the EIR, as shown
in Figure 3-2 and Figure 3-3.
Signaling Flow without EIR
Figure 3-2 Not being connected with the EIR
1. The VMSC or SGSN sends a CHECK_IMEI_EXT message to the SG.

2. The SG queries the CHECK_IMEI_EXT to obtain the IMSI and then checks whether the
MSISDN mapping to the IMSI is configured on the SG. If yes, the SG reports the IMSI
and MSISDN to the information unit of the TMS. If not, the SG reports only the IMSI to
the TMS.
3. The SG responds a CHECK_IMEI_ACK message to the VMSC or SGSN and sets the user
to be a white list user at the same time.
NOTE
The CHECK_IMEI_EXT message is the extended CHECK_IMEI message.

Service Flow with EIR Connected
Figure 3-3 Being connected with the EIR
1. The VMSC or SGSN sends a CHECK_IMEI_EXT message to the SG.

2. The SG queries the CHECK_IMEI_EXT to obtain the IMSI and then checks whether the
MSISDN mapping to the IMSI is configured on the SG7000. If yes, the SG reports the
IMSI and MSISDN to the information unit of the TMS. If not, the SG7000 reports only the
IMSI to the TMS.
3. The SG sends a standard CHECK_IMEI message to the EIR.
4. The EIR responds the CHECK_IMEI_ACK message to the VMSC or SGSN.
3.2.4 Equipment Coordination Requirements

This section describes the cooperation requirements between equipment.
Addressing Mode
The messages are sent by the MSC or SGSN depending on the GT addressing mode and are
processed at the MTP layer of the SG. The SG does not adopt the GT addressing mode, so set
any available GT on the VMSC and SGSN. That is, configure the GT translation data "DPC
+GT" on the MSC and SGSN. The DPC is that of the SG.
Signaling Format
l The VMSC and SGSN must send the CHECK_IMEI_EXT message.
l The TCP/IP interface provided by the SG can be adopted by the TMS.

3.3.1 Terms
As the equipment identification register, the EIR stores the international mobile station
equipment identity (IMEI) of all mobile stations and classifies the IMEI into three types: use
granted, use denied due to stolen, and monitored due to abnormal status.


You must follow certain principles to configure the IMEI Catch service data.
This section describes the relations between data tables related to IMEI Catch data configuration.
Before configuring the IMEI Catch service, you must collect the data including the user IMSI
number, MSISDN, and whether to enable related service information.
3.3.5 General Steps
You must follow certain procedures to configure the IMEI Catch service data.
3.3.1 Terms
As the equipment identification register, the EIR stores the international mobile station
equipment identity (IMEI) of all mobile stations and classifies the IMEI into three types: use
granted, use denied due to stolen, and monitored due to abnormal status.

You must follow certain principles to configure the IMEI Catch service data.
Configure SDUI Connected with TMS
Configure one SDUI for one SG only. The symmetrical slot of the SDUI cannot be configured
with other boards.
The SG can only be connected with a pair of TMSs through the SDUI. Two TMSs are numbered
TMS0 and TMS1. When TMS0 is normal, the SG sends data to the TMS0. The SDUI and TMS
can be located in a same network segment or in different segments. If they are in different network
segments, a gateway data should be configured.
Configure Address Translation of VMSC and SGSN

When there is the EIR in the networking, the SG transfers the CHECK_IMEI_ACK message to
the VMSC and SGSN. When there is no EIR in the networking, the SG acts as the EIR to respond
the CHECK_IMEI_ACK message to the VMSC or SGSN. In this case, the GT translation data
of the VMSC and SGSN must be configured on the SG. That is, if the messages adopt GT
addressing, the GT translation data that is acceptable to the VMSC and SGSN should be
configured on the SG. Generally, the addressing mode is "DPC+GT".
Configure Data on EIR

l When there is no EIR in the networking, you must use the MML command SET
IMEICFG to set the SG to disconnect from the EIR.
l When there is the EIR in the networking, the GT translation data must be configured on
the EIR.

This section describes the relations between data tables related to IMEI Catch data configuration.
Figure 3-4 shows the reference relations between the service data.

Figure 3-4 Reference relation between IMEI service data
NOTE
You must configure the SDUI before configuring network information. Other data can be configured
regardless of the sequences.

Before configuring the IMEI Catch service, you must collect the data including the user IMSI
number, MSISDN, and whether to enable related service information.
Before configuring the IMEI Catch service data, you must collect the data as listed in Table
3-1.
Table 3-1 Data collection table

If SG connect MSISDN User IMSI Whether enable related
with EIR number services
Table 3-2 lists the SG GT translation data configured on the VMSC and SGSN.
The GT translation type configured on the VMSC and SGSN is "DPC+GT".

Table 3-2 GT translation data configured on VMSC and SGSN

DPC of SG GT (can be set
freely)
If there is no EIR in the networking, the data related to the VMSC and SGSN should be
configured on the SG. Consider "DPC+GT" type as an example.
Table 3-3 VMSC and SGSN data configured on the SG

DPC of VMSC GT of VMSC DPC of SGSN GT of SGSN
If there is EIR in the networking, the GT translation data of the EIR must be configured on the
SG. Consider "DPC+GT" type as an example.
Table 3-4 EIR data configured on the SG

DPC of EIR GT of EIR
3.3.5 General Steps

You must follow certain procedures to configure the IMEI Catch service data.
Table 3-5 lists the steps to configure the IMEI Catch service data. Methods and commands in
steps 3, 4, and 5 should be chosen according to the actual networking structure. This chapter
describes the data configuration in a typical networking structure.
Table 3-5 Steps to configure IMEI Catch service data

Step Action
1 To configure SS7 link to VMSC
2 To configure SS7 link to SGSN
3 To add network information configuration table
4 To add SDUI
5 To set IMEI Catch service software parameter table
6 To set GT translation to VMSC (without being connected with EIR)
7 To set GT translation to SGSN (being connected with EIR)

Step Action
8 To set GT translation to EIR (being connected with EIR)
9 To add service user data
NOTE
Steps 1, 2, 6, 7, and 8 are specified in the MTP data configuration. For details, see relevant chapters.

Configuring the IMEI Catch service includes adding network information, adding the SDUI,
and setting the IMEI Catch software parameter.
3.4.1 Adding Network Information Configuration Table
The network information configuration table records the configuration information of the
interconnections between the SDUI and the TMS.
3.4.2 Adding the SDUI
This command is used to add the SDUI that is interconnected with the TMS.
3.4.3 Setting IMEI Catch Service Software Parameter Table
This command is used to set whether the SG is connected with the EIR.
3.4.4 Adding Service User Data
This command is used to add the user data of the IMEI Catch service. The SG converts the IMSI
to MSISDN and reports to the TMS depending on this data added.
3.4.1 Adding Network Information Configuration Table

The network information configuration table records the configuration information of the
interconnections between the SDUI and the TMS.
When a record is added to this table, the system allocates an idle index to this record. This index
is referenced when you add the SDUI.
Command
ADD NETINFO
Parameter
r ID r Name
LOCALIP Local IP It specifies the local IP address of the SDUI.

0 address 1
PEERIP0 Remote IP They specify IP addresses of the peer TMS.

address 1


r ID r Name
PEERIP1 Remote IP
address 2
PEERPO Remote They specify IP port numbers of the peer TMS.

RT0 port 1
PEERPO Remote
RT1 port 2
ROUTER Gateway It specifies the IP address of the gateway that is in the same network
IP address segment with the SDUI.
MASK Subnet It specifies the subnet mask of the network segment to which the
mask SDUI belongs.
Related Commands
Table 3-6 Related commands for configuring the net information configuration table
Command Function
ADD NETINFO To add net information configuration table
MOD NETINFO To modify net information configuration table
RMV NETINFO To delete net information configuration table
LST NETINFO To query net information configuration table
3.4.2 Adding the SDUI

This command is used to add the SDUI that is interconnected with the TMS.
Command
ADD BRD
Parameter
r ID r Name
SHN Shelf They specify the location of the SDUI. You must set Location to
number Front board.
FN Frame
number


r ID r Name
FT Frame
type
SN Slot
number
LOC Location
BT Board It is set to SDUI board.

type
PI Board It specifies the network information configuration table

property corresponding to the SDUI.
indicator
Related Commands
Table 3-7 Related commands for configuring the board
Command Function
ADD BRD To add the board
MOD BRD To modify the board
RMV BRD To remove the board
LST BRD To query the board
3.4.3 Setting IMEI Catch Service Software Parameter Table

This command is used to set whether the SG is connected with the EIR.
Command
SET IMEICFG
Parameter
r ID r Name
EIRVALI If SG It is set according to the actual networking structure.

D connect
with EIR

Related Commands
Table 3-8 Related commands for configuring the IMEI Catch configuration table
Command Function
SET IMEICFG To set IMEI Catch configuration table
LST IMEICFG To query IMEI Catch configuration table

This command is used to add the user data of the IMEI Catch service. The SG converts the IMSI
to MSISDN and reports to the TMS depending on this data added.
Command
ADD SERUATTR
Parameter
r ID r Name
USRNUM MSISDN It defines the MSISDN number of a user.
IMSINU User IMSI It defines the IMSI number of a user.

M number
SERVAT Whether Here, set the parameter to Enable IMEI service.

TR enable
related
services
Related Commands
Table 3-9 Related commands for configuring the service user data
Command Function
ADD SERUATTR To add service user data
MOD SERUATTR To modify service user data
RMV SERUATTR To delete service user data
LST SERUATTR To query service user data


This section provides examples to describe how to configure the IMEI Catch service data.
Networking Structure
The networking structure for configuring the IMEI Catch service is as shown in Figure 3-1.
Data Collection Table

Table 3-10 lists the data collected for configuring the IMEI Catch service.

If SG connect MSISDN User IMSI Whether enable related
with EIR number services
No 8621980082 865833672 IMEI Catch service
Procedure
Step 1 Add network information configuration table.
To add the network information configuration table, set Local IP address 1 to 10.70.35.118,
Remote IP address 1 to 10.70.35.119, Remote port 1 to 9000, Gateway IP address to
10.70.35.1, and Subnet mask to 255.255.255.0, run the following command:
ADD NETINFO: LOCALIP0="10.70.35.118", PEERIP0=10.70.35.119,
PEERPORT0=9000, ROUTER="10.70.35.1", MASK="255.255.255.0";
Step 2 Add an SDUI board.

To add an SDUI board, set Shelf number to 0, Frame number to 0, Frame type is Main service
frame, Slot number to 4, Location to Front board, Board type to SDUI, and Board property
indicator to 1, run the following command:
ADD BRD: SHN=0, FN=0, FT=MAIN, SN=4, LOC=FPB, BT=SDUI, PI=1;
NOTE
The data referenced by Board property indicator is the index generated when the command ADD
NETINFO is executed. Here, suppose the index is 1.
Step 3 Set IMEI Catch service software parameter table.

To set the IMEI Catch service software parameter table, set If connect with EIR to No, run the
following command:
SET IMEICFG: EIRVALID=INVALID;
Step 4 Add the service user data.

To add the service user data, set MSISDN to 8621980082, User IMSI number to 965833672,
and Whether to enable related services to Enable IMEI CATCH, run the following
command:

ADD SERUATTR: USRNUM="8621980082", IMSINUM="965833672", SERVATTR=OIMEI-1;
----End

Feature Description 4 Configuring MNP Service Data
4 Configuring MNP Service Data
About This Chapter
This chapter describes the mobile number portability (MNP) service. A user registered with the
MNP service can move from one subscribed network to another without changing the original
mobile station international ISDN number (MSISDN). Before configuring the MNP service data,
make sure that the hardware data, MTP data, SCCP data, and M3UA data are already configured.
4.1 MNP Service
The MNP service enables a user to move from one subscribed network to another without
changing the original mobile station international ISDN number (MSISDN).
4.2 Service Flow
This section describes the networking structure for the MNP service and the implementation and
service flow of the service.
Configuring the MNP service data includes setting the MNP software parameter, configuring
the HLR address, and configuring the MNP routing number.
This section provides examples to describe how to configure the MNP data.

4 Configuring MNP Service Data Feature Description
4.1 MNP Service

The MNP service enables a user to move from one subscribed network to another without
changing the original mobile station international ISDN number (MSISDN).
After the move, the newly subscribed network allocates a new IMSI (SIM) to this MNP user.
All services of the MNP user are provided by the newly subscribed network and are not affected
by the original network. There is no difference in the services provided to the MNP users and
non-MNP users, who are in the same subscribed network. In service quality, however, there is
a little difference to MNP users, for example, supplementary call setup delay.
Service Advantages
The advantages of the MNP service are as follows:
l To network operators: This service enables network operators (especially those who run
small-sized networks) to attract new users. Thus, extra management fee is obtained by
operators, operation revenue is increased, and competitiveness is enhanced.
l To users: This service enables users to choose proper networks and services depending on
their locations, without changing the original MSISDNs. A user can choose any network
among those run by the same network operator in different locations without changing the
original MSISDN. For example, a user is registered in city A with the number belonging
to the number range of city A. When the user moves to city B, this user can be registered
in city B without changing the original MSISDN.
l This service creates a competitive environment among different network operators to
ensure the customer satisfaction.
l This service ensures a balanced competition of number resources among network operators.
l This service enables network operators to improve network performance and service
quality.
Service Features
The features of the MNP service are as follows:
l Portable MSISDN: When moving from one network to another, or moving from one
location to another, a user can retain the original MSISDN.
l Independent service subscription: The services provided by a newly subscribed network
will not be affected by the original network. If the newly subscribed network does not
support the services that are provided by the original network, it cannot provide these
services to the users.
l Repeated portability: The MSISDNs can be moved out of a network as well as moved in.
The same MSISDN can be registered and deregistered repeatedly in the same network.
l Independent service: The MNP service does not conflict with mobile services.
The service flow and data configuration depend on the actual networking modes and
applications. The service flow complies with the standards specified in the ETSI 03.66 protocol.

4.2 Service Flow

This section describes the networking structure for the MNP service and the implementation and
service flow of the service.
This section describes the networking structure for configuring the MNP service.
This section describes the implementation of the MNP service.
4.2.3 Calling Flow
This section describes the call flow of the MNP service.
4.2.4 Impact on IN Services
The MNP service does not affect the IN services.
4.2.5 Impact on Supplementary Services
The MNP service does not affect the supplementary services.
4.2.6 Interworking Requirements
This section describes the cooperation requirements between equipment in the MNP service.

This section describes the networking structure for configuring the MNP service.
Figure 4-1 shows the public land mobile network (PLMN) networking structure with the MNP
service.
Figure 4-1 PLMN networking structure with the MNP service
Foreign NPDB: foreign number SG: U-SYS SG7000 Signaling PLMN: public land mobile network
portability database Gateway

PLMN: public land mobile network GMSC: gateway mobile switching SMSC: short message service
center center
VMSC: visited mobile switching SCP: service control point
center
In the networking, the SG acts as the MNP-SRF (signaling relay function) and the NPDB. The
SG is logically located before the HLR. The SGs are configured in pairs. All E.164 addressing
signaling messages that are sent to the HLR must be forwarded by the SG. The network must
adopt the "Route on GT" mode for addressing and the SG as the translation point.
Figure 4-2 shows the public switched telephone network (PSTN) networking structure with the
MNP service.
Figure 4-2 PSTN networking structure with the MNP service
LS: local switch U-SYS SG7000 Signaling Gateway PSTN: public switched telephone network
SCP: service control point POI: point of interconnects SSP: service switching point
In this networking structure, the SG acts as the unique NPDB in the entire network to connect
with other network elements (NEs).

This section describes the implementation of the MNP service.
To implement the MNP service, the following two devices must be added:

l MNP-SRF: It forwards all call-related and non-call-related signaling messages to the HLR,
SCP, or other NEs. It is located between the other NEs and the HLR. It can be used
independently or combined with the LSTP.
l NPDB: It stores the data of all portable numbers.
If a user is registered with the MNP service, an NE cannot judge the HLR of a user through the
MSISDN. The implementation of the MNP service is as follows:
1. A message that is sent from an NE to the HLR is sent to the MNP-SRF first.
2. The MNP-SRF queries the NPDB based on the MSISDN to find the actual HLR of the
user.
3. The MNP-SRF forwards the message depending on the query result.
In this way, the message sent to a number portability (NP) user is forwarded to the correct HLR,
and thus the MNP service is implemented.
The MNP service supports MAP, CAP, and INAP protocol messages. When a user registers IN
services in the system, the MNP service processes the CAP and INAP protocols.
4.2.3 Calling Flow

This section describes the call flow of the MNP service.
The MNP service flow is embodied in the PSTN and the PLMN network structures.
The MNP service flow embodied in the PLMN networking structure includes calling non-IN
user MNP and calling IN user MNP.
In the following service flow, types I-V belong to the calling non-IN user MNP. Here, types I-
IV are call-related service flows, while type V is non-call-related service flow.
Types VI-VII are call related service flows and belong to the calling IN user MNP. The non-
call-related service flow of a calling IN user is the same as that of a calling non-IN user.
Types VIII-XIII belong to the MNP service flow embodied in the PSTN networking structure.
Type XIV belongs to the MNP query service flow in ATI mode.
Calling a Foreign Number Not Ported In User
Figure 4-3 Calling a foreign number not ported in user

When a local user calls a "foreign number not ported in" user, the service flow is as follows:
1. The caller initiates a call. The VMSC sends the SRI message to the HLR to query the
location of the callee. The message contains the MSISDN of the callee. The message is
obtained by the SG.
2. The SG queries the user information in its database based on the SCCP CdPA (it is MSISDN
here) in the message.
3. When the SG identifies that the callee is a "foreign number not ported in" user, it returns
the SRI_ACK message to the VMSC. The message contains the route number and MSISDN
of the callee.
4. After number analysis, the VMSC sends the IAM that contains the "RN + MSISDN" of the
callee to the GMSC.
5. The GMSC removes the RN and then sends the IAM that contains the MSISDN of the
callee to the foreign GMSC.
The subsequent service flow is irrelevant to the SG.
Calling a Foreign Number Ported In User or an Own Number Not Ported Out User
Figure 4-4 Calling a foreign number ported in user or an own number not ported out user
When a local user calls a "foreign number ported in" user or an "own number not ported out"
user, the service flow is as follows:
obtained by the SG.
2. The SG queries the user information in its database based on the SCCP CdPA in the
message.
3. When the SG identifies that the callee is a "foreign number ported in" user or an "own
number not ported out" user, it modifies the SCCP CdPA in the SRI message to the
corresponding HLR address and then sends the message to the HLR.

4. The HLR returns the SRI_ACK message that contains the mobile subscriber roaming
number (MSRN) of the callee to the VMSC.
5. The VMSC sends the IAM that contains the MSRN of the callee to the MSC.
Calling an Own Number Ported Out User
Figure 4-5 Calling an own number ported out user
When a local user calls an "own number ported out" user, the service flow is as follows:
obtained by the SG.
message.
3. When the SG identifies that the callee is an "own number ported out" user, it returns the
SRI_ACK message to the VMSC. The message contains the route number and the MSISDN
of the callee.
4. After number analysis, the VMSC sends the IAM that contains the "RN + MSISDN" of the
callee to the GMSC.
5. The GMSC removes the RN and then sends the IAM that contains the MSISDN of the
callee to the foreign GMSC.

Sending Non-Call-Related Messages to a Foreign Number Ported In User or an

Own Number Not Ported Out User
Figure 4-6 Sending non-call-related messages to a foreign number ported in user or an own
number not ported out user (1)
Figure 4-7 Sending non-call-related messages to a foreign number ported in user or an own
number not ported out user (2)
SMSC SG HLR
SRI_FOR_SM(MSISDN=B;cdGT=B)
SRI_FOR_SM ack(IMSI=fakeimsi)
SRI_FOR_SM(MSISDN=RN+B;cdGT=RN+B)
MT_FORWARD_SM
MT_FORWARD_SM
When a local user sends a non-call-related message to a "foreign number ported in" user or an
"own number not ported out" user, the service flow is as follows:
1. The local user sends a non-call-related message. The SMSC sends the SRI_for_SM
message to the HLR to query the location of the callee. The message that contains the
MSISDN of the callee is obtained by the SG.

message.
3. When the SG identifies that the callee is a "foreign number ported in" user or an "own
number not ported out" user, and the "Fake IMSI solution switch" is enabled, the SG checks
whether the network that the callee resides interworks with this signaling network.
l If not, the SG returns the SRI_FOR_SM_ACK message.
l If yes, the SG forwards the SRI_FOR_SM message to the HLR. The MSISDN in the
message is filled with the number of subscriber B and the called GT is replaced with
the HLR address.
4. When any of the following cases occurs on the callee, the SG transparently forwards the
message instead of performing the NP processing:
l The callee is a fixed-network subscriber.
l The SRI_FOR_SM message contains no MSISDN parameter or the subscriber type
cannot be identified.
l The addressing mode of the SRI_FOR_SM message is of the DPC addressing mode.
Sending Non-Call-Related Messages to an Own Number Ported Out or a Foreign

Number User
Figure 4-8 Sending non-call-related messages to an own number ported out or a foreign number
user (1)

Figure 4-9 Sending non-call-related messages to an own number ported out or a foreign number
user (2)
SMSC SG GMSC
SRI_FOR_SM(MSISDN=B;cdGT=B)
SRI_FOR_SM ack(IMSI=fakeimsi)
SRI_FOR_SM(MSISDN=RN+B;cdGT=RN+B)
MT_FORWARD_SM
MT_FORWARD_SM
When a local user sends a non-call-related message to an "own number ported out" user or a
foreign number user, the service flow is as follows:
1. The local user sends a non-call-related message. The SMSC sends the SRI_for_SM
message to the HLR to query the location of the callee. The message that contains the
MSISDN of the callee is obtained by the SG.
2. The SG analyzes the SCCP CdPA (MSISDN) contained in the message.
3. When the SG identifies that the callee is an "own number ported out" user or a foreign
number user, and the "Fake IMSI solution switch" is enabled, the SG checks whether the
network that the callee resides interworks with this signaling network.
l If not, the SG returns the SRI_FOR_SM_ACK.
l If yes, the SG modifies the called MSISDN and called GT to RN+B's number and then
transmits the message to a foreign GMSC.

An IN Service User Calling an Own Number not Ported Out User or a Foreign
Number Ported In User
Figure 4-10 An IN service user calling an own number not ported out user or a foreign number
ported in user
When an IN service user calls an "own number not ported out" user or a "foreign number ported
in" user, the service flow is as follows:
1. An IN service user initiates a call. The VMSC sends an initial detection point (IDP) message
to the SG. The message contains the CalledPartyNumber (CdPN).
2. The SG obtains the message and queries the user information in its database based on the
CdPN in the IDP message.
3. When the SG identifies that the callee is an "own number not ported out" or a "foreign
number ported in" user, it replaces the CdPN in the IDP message with "local RN +
MSISDN" and at the same time modifies the nature of address (NoA) to national.
4. The SG sends the modified IDP message to the SCP.
5. The SCP returns the Connect message. The message contains "local RN + MSISDN".

An IN Service User Calling an Own Number Ported Out User or a Foreign Number
Ported to a Foreign Network User
Figure 4-11 An IN service user calling an own number ported out user, a foreign number ported
to a foreign network user, or a foreign network unknown user
When an IN service user calls an "own number ported out" user, a "foreign number ported to a
foreign network" user, or a "foreign network unknown" user, the service flow is as follows:
1. An IN service user initiates a call. The VMSC sends an IDP message to the SG. The message
contains the CdPN.
2. The SG obtains the message and queries user information in its database depending on the
CdPN in the IDP message.
3. When the SG identifies that the callee is an "own number ported out" user, a "foreign
number ported to a foreign network" user, or a "foreign network unknown" user, it replaces
the CdPN in the IDP message with "local RN + MSISDN" and at the same time, it modifies
the NoA depending on the configured data. The foreign RN is configured in the MNP
routing number table.
4. The SG sends the modified IDP message to the SCP.
5. The SCP returns the Connect message. The message contains "foreign RN + MSISDN".
When receiving the Connect message, the VMSC sends an IAM to the GMSC (The SG
does not intercept the IAM).

A Local Network Ordinary User Calling an MNP User
Figure 4-12 A local network ordinary user calling an MNP user
When a local network ordinary user calls an MNP user, the service flow is as follows:
1. The local network ordinary user initiates a call. The LS sends an IDP message to the SG.
The message contains the called MSISDN.
2. The SG queries the database to obtain the routing number of the callee and returns the
Connect message to the LS. The message contains "called RN + MSISDN".
3. The LS sends an IAM to the GMSC for call connection. The IAM contains "called RN +
MSISDN".
A Local Network Ordinary User Calling a Mobile Non-NP User
Figure 4-13 A local network ordinary user calling a mobile non-NP user
When a local network ordinary user calls a mobile non-NP user, the service flow is as follows:

1. The local network ordinary user initiates a call. The LS sends an IDP message to the SG.
The message contains the called MSISDN.
2. The SG queries the database but cannot find the callee's information. Then the SG returns
the Continue message to the LS.
3. The LS sends an IAM to the GMSC for call connection. The IAM contains called MSISDN.
A Local Network Pre-Paid User Calling an MNP User
Figure 4-14 A local network pre-paid user calling an MNP user
When a local network pre-paid user calls an MNP user, the service flow is as follows:
1. The LS sends an IAM to the SSP to trigger the IN service. The message contains "called
Service Key + MSISDN".
2. The SSP sends an IDP message to the SCP to query the IN service. The message contains
"called AC + MSISDN".
3. The SCP processes the query request and returns the Connect message. The message
contains the IN service access code.
4. After the query, the SSP sends an IDP message to the SG for query. The message contains
the called MSISDN and is terminated on the SG.
Connect message to the SSP. The message contains "called RN + MSISDN".
6. The SSP sends an IAM to the SG for call connection. The message contains "called RN +
MSISDN".

A Local Network Pre-Paid User Calling a Mobile Non-NP User
Figure 4-15 A local network pre-paid user calling a mobile non-NP user
LS SSP SG/NPDB SCP POI GMSC
IAM
(AC+MSISDN)
IDP
(ServiceKey+MSISDN)
Connect
IDP(MSISDN)
Continue
IAM(MSISDN)
IAM(MSISDN)
IAM(MSISDN)
When a local network pre-paid user calls a mobile non-NP user, the service flow is as follows:
1. The LS sends an IAM to the SSP to trigger the IN service. The message contains "called
Service Key + MSISDN".
2. The SSP sends an IDP message to the SCP to query the IN service. The message contains
the IN service access code.
3. The SCP and SSP process the query request and return the Connect message. The message
contains the called MSISDN.
4. After the query, the SSP sends an IDP message to the SG for query. The message contains
the called MSISDN and is terminated on the SG.
5. The SG queries the database but cannot find the callee's information. Then the SG returns
the Continue message to the SSP.
6. The SSP sends an IAM to the SG for call connection. The message contains the called
MSISDN.

A Foreign Network Ordinary User Calling an MNP User
Figure 4-16 A foreign network ordinary user calling an MNP user
When there is no NPDB equipment in the foreign network, all MNP services use the third-party
network for the query and call connection. Figure 4-16 and Figure 4-17 shows the query and
call connection flow provided by the local network which acts as a third-party network.
When a foreign network ordinary user calls an MNP user, the service flow is as follows:
1. The gateway office POI receives an IAM sent from the LS of a foreign network. The
message contains the called MSISDN.
2. The POI sends an IDP message to the SG for query. The message contains the called
MSISDN.
Connect message to the POI. The message contains "called RN + MSISDN".
4. The POI sends an IAM for call connection. The message contains "called RN + MSISDN".
A Foreign Network Ordinary User Calling a Mobile Non-NP User
Figure 4-17 A foreign network ordinary user calling a mobile non-NP user

When a foreign network ordinary user calls a mobile non-NP user, the service flow is as follows:
1. The gateway office POI receives an IAM sent from the LS of a foreign network. The
2. The POI sends an IDP message to the SG for query. The message contains the called
MSISDN.
3. The SG queries the database but cannot find callee's information. Then the SG returns the
Continue message to the POI.
4. The POI sends an IAM for call connection. The message contains the called MSISDN.
MNP Query in ATI Mode
Figure 4-18 MNP query service flow in ATI mode
The service flow of MNP query in ATI mode is as follows:
1. The VMSC sends the MNP query message in ATI mode to the SG.
2. After receiving the message, the SG queries the NPDB based on the called number in the
ATI message.
3. The SG obtains the routing number and NP status corresponding to the called number.
4. The SG sends the ATI_ACK message that contains the MSISDN and queried results to the
VMSC.
4.2.4 Impact on IN Services

The MNP service does not affect the IN services.
4.2.5 Impact on Supplementary Services

The MNP service does not affect the supplementary services.


This section describes the cooperation requirements between equipment in the MNP service.
Network Requirements
Network requirements are as follows:
l The IAM must support the route number (RN).
l The data to be negotiated with other networks in the NP domain is the RN. The RN cannot
be the prefix of a user number.
Interworking Data Between NEs

The interworking data between NEs must be set before configuring the MNP service data in the
following ways:
l On the SG
The data that must be set on the SG includes the following:
– Local HLR address and translation type: DPC + SSN. The DPC is that of the local HLR
and the SSN attribute is HLR.
– Foreign RN and translation type: DPC + GT. The DPC is that of a foreign GT translation
device and the GT attribute is RN.
– Local GMSC address and translation type: DPC + SSN. The DPC is that of the local
GMSC and the SSN attribute is MSC.
l On the HLR
Based on the networking mode, if the SRI_ACK message returned by the HLR is forwarded
by the SG, the data "DPC + GT" must be added. The DPC must be set to that of the SG
and the GT must be set to that of the VMSC. If the message is not forwarded by the SG,
the data on the HLR must not be changed.
l On the VMSC
– E.164 address and translation type: DPC + GT. The DPC is that of the SG.
– Foreign RN and translation type: DPC + GT. The DPC is that of the GMSC.
l On the GMSC
The foreign RN analysis data must be set on the GMSC to connect the call to the foreign
GMSC.
l On foreign GMSC
For an incoming IAM, the foreign GMSC needs to remove the RN from the IAM. The RN
is the number of the network to which the foreign GMSC is homed.

4.3.1 Terms
This section describes the terms used during configuring the MNP service.

You must follow certain principles to configure the MNP service data.
4.3.3 Relations Between Data Tables
This section describes the relations between data tables related to the MNP service data
configuration.
Before configuring the MNP service, you must collect the data including the country code, MNP
working mode, and local network routing number.
4.3.5 General Steps
You must follow certain procedures to configure the MNP service data.
4.3.1 Terms
This section describes the terms used during configuring the MNP service.
MNP
The MNP refers to the NP function of mobile numbers. The MSISDN of an MNP user need not
be changed when the user moves out of a network. A new international mobile subscriber identity
(IMSI) is allocated to an NP user when the user moves into a new network.
The MNP function of the SG complies with the ETSI GSM 03.66 standard and implements some
functions of the MNP-SRF (MNP function entity) and NPDB function defined in the standard.
The SG implements the following functions:
l MNP function of call-related and non-call-related services in the GSM network
When the user moves into a foreign network, this function enables the user to reserve the
MSISDNs. The user also enjoys the services (including supplementary services and value-
added services) provided by the newly subscribed network. These services are not affected
by the previous network.
l MNP function among HLRs managed by the same network operator
This function enables the MNP between 2G HLR and 3G HLR. With this function, a 2G
user can move into a 3G network without changing the MSISDN.
MSISDN
Each mobile station (MS) has the following two numbers:
l MSISDN: directory number and open to the public
l IMSI: provided by the network operator to uniquely identify an MS
IMSI
An IMSI uniquely identifies an MS. An IMSI is consists of three parts:
l MCC: mobile country code
l MNC: mobile network code
l MSIN: mobile subscriber identification number
The IMSI enables the network operator to identify an MS, search for the address of an MS, and
authenticate an MS. When an MS is registered, it is allocated to both the MSISDN and IMSI.

After registering the MNP service, a user can move to a foreign network without changing the
MSISDN. The newly subscribed network operator allocates a new IMSI to the user.
INAP
The Intelligent Network Application Protocol (INAP) is an important protocol in the intelligent
network field. The protocol is the base of a smooth communication between the SCP and the
SSP. INAP is used to decode the INAP IDP message in the MNP service and construct the
Connect message (when the information is queried) and the Continue message (when the
information is not queried).

You must follow certain principles to configure the MNP service data.
Number Type
The MNP service concerns the following six types of users:
l An own number not ported out: It indicates users who have not moved from the local
network to foreign networks. These users however, can move among HLRs in the local
network.
l An own number ported out: It indicates users who have moved from the local network to
foreign networks. The networks in which the users reside after the move are not the
networks their MSISDNs represent.
l A foreign number ported in: It indicates users who have moved from foreign networks to
the local network. These users enjoy the services provided by the local network.
l A foreign number ported to a foreign network: It indicates users who have moved from one
foreign network to another foreign network.
l Foreign network unknown: It indicates users who have foreign network numbers but the
transfer status is unknown. This type contains all foreign users who have not moved to any
other network.
l Local network unknown: It indicates users who have local network numbers. These users
have not moved to foreign networks, even among the HLRs in the local network.
The data of the first four types of users must be set in the user attribute table.
l If a user number cannot be found in the user attribute table (not configured in the table),
but the number belongs to the foreign network number range that is set in the MNP route
number table, the user is a "foreign network unknown" user.
l If a user number cannot be found in the user attribute table (not configured in the table),
and the number does not belong to the foreign network number range that is set in the MNP
route number table, the user is a "local network unknown" user.
You must configure the MNP service data based on the services provided. For the PSTN
networking structure, only "a foreign number ported to a foreign network" is used.
MNP Service - Own Number Not Ported Out

For users who have not moved from the local network to foreign networks, configure the relevant
data in the following manner:

l Enable the FN function

When setting the MNP software configuration information table, run SET
MNPSOFTCFG to enable the MNP_FN function.
l Configure MNP address attribute management
When configuring the MNP address attribute management, run ADD MNPHLRADDR to
configure the HLR that corresponds to the user number.
l Configure service user data
Run ADD SERUATTR to set Number type to An own number not ported out and
Route index type to HLR number index in the service user data table. This index maps
the HLR address number configured in the MNP address attribute management.
MNP Service - Foreign Number Ported In

For users who have moved to the local network from foreign networks, configure the relevant
l Enable the MNP function

l Configure MNP address attribute management
When configuring the MNP address attribute management, run ADD MNPHLRADDR to
configure the HLR that corresponds to the user number.
Run ADD SERUATTR to set Number type to A foreign number ported in and Route
index type to HLR number index in the service user data table. This index maps the HLR
address number configured in the MNP address attribute management.
MNP Service - Own Number Ported Out

For users who have moved to foreign networks from the local network, configure the relevant
l Enable the MNP function

l Configure MNP route number management
Run ADD MNPROUTENUM to configure the route number mapping the user number in
the MNP route number management.
Run ADD SERUATTR to set Number type to An own number ported out and Route
index type to Route number index in the service user data table. This index maps the
routing number index configured in the MNP route number management.
MNP Service - Foreign Number Ported to a Foreign Network

l Enable MNP function

l Configure MNP route number management

Run ADD MNPROUTENUM to configure the route number mapping the user number in
the MNP route number management.
Run ADD SERUATTR to set Number type to A foreign number ported to a foreign
network and Route index type to Route number index in the service user data table. This
index maps the routing number index configured in the MNP route number management.

This section describes the relations between data tables related to the MNP service data
configuration.
Relations Between MNP Data Tables

Figure 4-19 shows the relations between MNP data tables.

Figure 4-19 Mapping between MNP service data tables

SET MNPSOFTCFG
the RN configure parameter of foreign

[ MNP mode ] [ ]
not known ported
Message type of MNP service the RN configure parameter of local
[ ] [ ]
processing regular user
[ Country code ] [ MNP noa parameter ]
[ Local network route number ] [ Seven configuration switches mapping ]

MNP noa parameter
[ Number amend switch ] [ Convert UDT into XUDT ]
CDMA message configuration ]
[ Multi-rn switch ] [
parameter
[ RN fill type ] [ SMSC sub-system ]
ORREQ expansion IN trigger type ] [ ATI MODE ]
[
1-6
[ Local GT address ] [ SMA switch ]
[ MNP QUERY SERVICE KEY ] [ SMA called process switch ]
ADD MNPHLRADDR
[ HLR Address index ]
[ HLR Address number ]
ADD MNPROUTENUM
[ MNP Route Number index ]
[ Route number ]
[ IMSI number ]
SMS signaling
[ ]
intercommunicate flag
ADD MNPFRGNRNG
[ Foreign number range index ]
[ Min foreign number ]
[ Max foreign number ]
[ Route number index ]
ADD SERUATTR
[ MSISDN ]
Whether enable related
[ ]
services ADD SCCPGT
[ Number type ] [ Translation type ]
[ Route index type ] [ DPC index ]

[ Address message ]
[ NP route index ]
Internal Reference Relations of MNP Data

The internal reference relations of the MNP data are as follows:
l The value of Route number index defined in the MNP foreign number range table
references the value of Index defined in the MNP route number table. The index indicates
the number of the route directed to a foreign network.

l During the configuration, if Route index type is set to HLR number index, the value of
NP route index references the HLR address number. If Route index type is set to Route
number index, the value of NP route index references the MNP route number index.
l When configuring the MNP software parameter table, Called NoA of the INAP CONNECT
message is valid only when MNP parameter is set to Indicator of modifying the called NoA
of the INAP message.
Reference Relations Between MNP Data and Other Data

SCCP GT translation table needs to use the index configured with ADD N7DSP.

Before configuring the MNP service, you must collect the data including the country code, MNP
working mode, and local network routing number.
Before data configuration, you need to collect the data as listed in Table 4-1 and Table 4-2.
Table 4-1 Local office information data
Country code MNP mode Local network route Convert UDT into
number XUDT
Table 4-2 User information data
Min. foreign Max. foreign MNP route number HLR address

number number number
MSISDN Number type
4.3.5 General Steps

You must follow certain procedures to configure the MNP service data.
Table 4-3 lists the steps of configuring the MNP service data.
Table 4-3 Steps of configuring the MNP service data
Step Operation
1 To configure the MNP software parameters
2 To configure the HLR address table
3 To configure the MNP route number table

Step Operation
4 To configure the MNP foreign number range table
5 To configure the MNP service user data table
6 To configure the SCCP GT translation table
Configuration requirements are as follows:
l Configure the MNP route number table before configuring the MNP foreign number range
table and the service user data table.
l Configure the HLR address table before configuring the service user data table.
Two examples are provided as follows:
Example 1: Add an MNP service user.
Perform the operations in the following order:
l Add an HLR address.

l Add an MNP route number.
l Add the MNP foreign number range.
l Add the service user data.
Example 2: Remove an HLR address.
Perform the operations in the following order:
l Remove the service user data that references this HLR address.
l Remove the HLR address.

Configuring the MNP service data includes setting the MNP software parameter, configuring
the HLR address, and configuring the MNP routing number.
4.4.1 Configuring MNP Software Parameters
This section describes the command, parameter, and related commands for configuring the MNP
software parameters.
4.4.2 Configuring HLR Address Table
This command is used to set the GT address of the local HLR. When Number type is set to An
own number not ported out, A foreign number ported in, or FN user, the system needs to
query the HLR based on the user number.
4.4.3 Configure MNP Route Number Table
This command is used to set the routing information of a foreign network. When Number
type is set to An own number ported out or A foreign number ported to a foreign
network, the system needs to query the route of the foreign network based on the user number.
4.4.4 Configuring MNP Foreign Number Range Table

When a user number cannot be found in the service user data table, the system must query the
MNP foreign number range table to obtain the route number, and route the messages correctly
to the corresponding network.
4.4.5 Configuring Service User Data Table
This section describes the command, parameter, and related commands for configuring the
service user data table.
4.4.6 Setting SCCP GT Translation Table
This section describes the command, parameter, and related commands for configuring the SCCP
GT translation table.
4.4.1 Configuring MNP Software Parameters

Command
SET MNPSOFTCFG
Parameter
Paramet Param Parameter Description
er ID eter
Name
MNPMO MNP It can be set to any of the following values:

DE mode l FN mode: It refers to the flexible number routing mode, that is, the
intra-carrier NP. It is selected when the service user is required to
be set to the NN or RN user.
l MNP-FN mode: It refers to the complete processing mode, including
the intra-carrier and inter-carrier NP. It complies with the 3GPP
23066 protocol. It is selected when the service user is required to be
set to the user type other than the NN or RN user type.
l Reserve: It indicates the reserved processing mode. You cannot
configure this mode.
It is suggested to select MNP-FN mode here.


er ID eter
Name
MNPMS Messag It indicates the type of the messages intercepted for processing in the
GTYPE e type MNP service. It can be set to one or more of the following values:
of l BIT0 (MAP): The messages intercepted for processing in the MNP
MNP service include the SRI, SRI_FOR_SM, LOC_REQ/SMS_REQ,
service ATI/SOR_SRI/CCBS_REQ, SEND_IMSI,
process REPORT_SM_DELIVERY_STATUS/SRI_FOR_LCS, MO, SAI/
ing LU, GPRS_LU/USSD, REG_SS, ERASE_SS, ACT_SS, DEA_SS/
REG_PASSWORD, INTERROGATE_SS, and
RESTORE_DATA/READY_FOR_SM/PURGE_MS messages.
l BIT1 (CAP): The system intercepts the CAP-IDP message for
processing in the MNP service.
l BIT2 (INAP): The system intercepts the INAP-IDP message for
processing in the MNP service.
l BIT3 (ISUP): The system intercepts the ISUP IAM and SAM
messages for processing in the MNP service.
l BIT4 (ANLYZD): The system intercepts the ANLYZD message
coming from the CDMA network for processing in the MNP service.
l BIT5 (ORREQ): The system intercepts the ORREQ message
l BIT6 (SMDPP_MO): The system intercepts the SMDPP message
l BIT7(MAP_ISD)
l BIT8(ANSI_REGNOT_RR)
l BIT9(LOCREQ)
l BIT10(SMSREQ)
l BIT11(NPREQ)
l BIT12(PROCESS USSR)
l BIT13(CAP_IDPSMS)
l BIT14(MAP_SEND_PARAMETERS)
l BIT15(Prepaid INAP IDP): It determines whether the system
processes the prepaid INAP IDP message.
It is set based on the actual networking conditions. If the office is
enabled with the CDMA IN call NP service, the switches of the
ORREQ and ANLYZD messages must be enabled.
NC Countr It indicates the country code of the equipment. It is used to exclude the
y code country code when a user number is queried. A user number has no
country code by default. It must be set based on the actual conditions.


er ID eter
Name
LOCAL Local It is used to mark a local network. When a foreign number is ported to
RNCD networ the local network, the foreign network routes the message to the local
k route network based on this route number, and then the local network
number processes the message based on the ported-in number. It is valid only
when Multi-RN switch is disabled. It must be set based on the actual
conditions. It is set to 0 by default.
ISNUM Numbe It determines whether to amend the number before querying the NPDB.
AMEND r
amend
switch
ISMULT Multi- It determines whether multiple RNs are allowed in the local network.
INRN RN When it is enabled, multiple RNs are allowed in the local network;
switch when it is disabled, only one RN is allowed in the local network.
FILLTY RN fill Four options are available for this parameter. It is set based on the actual
P type networking conditions. CC stands for country code.


er ID eter
Name
FNUNK The RN It is valid only when the message source is a foreign network unknown
NSUB configu user. It controls whether to add the RN to the foreign network unknown
re user. It can be set to one or more of the following values:
parame l G1 (CAP IDP): When it is selected, the CAP IDP message contains
ter of the relevant RN after being applied with the MNP service.
foreign
not l G2 (MO): When it is selected, the MO message contains the relevant
known RN after being applied with the MNP service.
ported l G3 (MAP NON CALL RELATED): When it is selected, the MAP
non-call-related message contains the relevant RN after being
applied with the MNP service.
l G4 (MAP CALL RELATED): When it is selected, the MAP call-
related message contains the relevant RN after being applied with
the MNP service.
l G5 (INAP IDP): When it is selected, the INAP IDP message
contains the relevant RN after being applied with the MNP service.
l G6 (ATI): When it is selected, the ATI message contains the relevant
RN after being applied with the MNP service.
l G7 (ISUP IAM): When it is selected, the ISUP IAM message
l G8 (LOCREQ): When it is selected, the LOCREQ message contains
the relevant RN after being applied with the MNP service.
l G9 (ANLYZD): When it is selected, the ANLYZD message
l G10 (ORREQ): When it is selected, the ORREQ message contains
l G11 (PROCESS USER): When it is selected, the USSD message
contains relevant RN after being applied with the MNP service.
l G12(CAP IDPSMS): When it is selected, the CAP IDPSMS
message contains relevant RN after being applied with the MNP
service.
l G13(MAP SEND PARAMETERS): When it is selected, the MAP
SEND PARAMETERS message contains relevant RN after being
l G14(Prepaid INAP IDP): When it is selected, the prepaid INAP IDP
message from an ordinary subscriber in the external network


er ID eter
Name
LOCRN The RN It is valid only when the message source is an ordinary user in the local
PARA configu network. It controls whether to add the RN to the local network
re unknown user. It can be set to one or more of the following values:
parame l G1 (CAP IDP): When it is selected, the CAP IDP message contains
ter of the relevant RN after being applied with the MNP service.
local
regular l G2 (MO): When it is selected, the MO message contains the relevant
user RN after being applied with the MNP service.
l G3 (ATI): When it is selected, the ATI message contains the relevant
l G4 (ANLYZD): When it is selected, the ANLYZD message
l G5 (ORREQ): When it is selected, the ORREQ message contains
l G6 (ISUP IAM): When it is selected, the ISUPIAM message
l G7 (LOCREQ): When it is selected, the LOCREQ message contains
relevant RN after being applied with the MNP service.
l G8 (PROCESS USER): When it is selected, the USSD message
l G9(CAP IDPSMS): When it is selected, the CAP IDPSMS message
l G10 (Prepaid INAP IDP): When it is selected, the prepaid INAP
IDP message contains relevant RN after being applied with the MNP
service.


er ID eter
Name
MNPPA MNP It determines the mode by which the nature of address (NoA) of
RA NOA different messages is modified in the MNP service. It can be set to one
parame or more of the following values:
ter l G1 (Modifying NoA of non-call related message of number ported
out): It controls whether to modify the NoA of the callee after the
RN is added.
l G2 (NOA of CAP_IDP called party number): It controls whether to
modify the NoA of the called number in the CAP IDP message.
During the call connection through the MNP message, there is no
country code added before the MSISDN. In this case, the system
must judge whether to set the NoA to a special value in order to
prevent the network equipment performing the operation of
removing the country code.
l G3 (NOA of CAP_IDP called party BCD number): It controls
whether to modify the NoA of the BCD number of the called party
in the CAP IDP message.
l G4 (Indicator of modifying the called NoA of the MAP call-related
message): It controls whether to modify the NoA of the called
number in the MAP call-related message. During the call connection
through the MNP message, there is no country code added before
the MSISDN. In this case, the system must judge whether to set the
NoA to a special value in order to prevent the network equipment
performing the operation of removing the country code.
l G5 (Indicator of modifying the called NoA of the INAP message):
It controls whether to modify the NoA of the called number in the
INAP message.
l G6 (Modifying NoA of called number of ISUP message): It controls
whether to modify the NoA of the called number in the ISUP
message.
l G7 (Modifying NoA of called number of MO message): It controls
whether to modify the NoA of the called number in the MO message.
l G8 (Modifying NoA of called number of ORREQ message): It
controls whether to modify the called NoA in the ORREQ message.
l G9 (Modifying NoA of called number of ANLYZD message): It
controls whether to modify the called NoA in the ANLYZD
message.
l G10 (Modify NoA of CAP_IDPSMS called party BCD number): It
controls whether to modify the BCD NoA in the called number in
the CAP_IDPSMS message.
l G11 (Modify NoA of prepaid INAP IDP called party BCD number):
It controls whether to modify the BCD NoA in the called number in
the prepaid INAP IDP message.


er ID eter
Name
MNPOU NoA They must be set based on the actual networking conditions. The
T for parameter is valid only when the corresponding switch in MNP NOA
non- parameter is enabled.
call
related
messag
e of
own
ported
out
CAPMF NOA
NA of
CAP_I
DP
called
party
number
CAPMO NOA
NA of
CAP_I
DP
called
party
BCD
number
MAPNA NoA of
called
number
of
MAP
call
related
messag
e
INAPNO Called
A NoA of
the
INAP
CONN
ECT
messag
e


er ID eter
Name
ISUPAD NoA of
DRNOA called
number
of
ISUP
messag
e
MOADD NoA of
RNOA called
number
of MO
messag
e
CONVT Conver When it is set to Open, the inter-network NP messages are converted
OXUDI t UDT to the XUDT messages, thus avoiding message cycling. It is set to
T into Close by default.
XUDT
MCSSN SMSC It is the parameter for processing the SMDPP message in the CDMA
sub- NP service. When it is configured, this equipment obtains the sub-
system system from the message and compares it with this parameter. If they
are the same, this equipment processes the message; otherwise, this
equipment does not process the message.
LOCAL Local It indicates the corresponding GT address of the SG in the networking

GTADD GT structure. It is set based on the actual networking structure. This
R address parameter is designed for the PSTN networking structure.
If the called subsystem at the SCCP layer of a message is INAP and
the addressing is GT mode, the called GT code must be the same as
that in the MNP software parameter table; otherwise, the message is
not processed.
If the called subsystem at the SCCP layer of a message is INAP and
the addressing is SSN mode, the local network directly processes the
message instead of matching the called GT code.
MNPSE MNP This parameter is designed for the PSTN networking structure. It is set
RVICEK query after negotiations with the peer end based on the actual conditions. The
EY service service key contained in the query message of the peer end must be the
key same as that in the MNP software parameter table; otherwise the
message is not processed.
ATIMO ATI It is designed for the ATI query service.

DE mode It can be set to:
l MODE0 (SCCP relay): The system does not perform the MNP query
for all ATI query messages.
l MODE1 (TC relay): The system performs the MNP query for all
ATI query messages and returns the query results.


er ID eter
Name
SMASW SMA It is the general switch for message authentication.

ITCH switch When it is set to Close, all messages from MOforward are not
authenticated. When it is set to Open, the system intercepts the MO
message, analyzes the calling number type, screens the messages
coming from a foreign network caller, and then returns the ERROR
message.
SMASC SMA It is the general switch for message authentication.

HCALL called It can be set to:
ED process
switch l SWITCH1 (Open): For the callee who enables the NP service, the
system adds the RN to the called number contained in the message
and then sends the message to the SMC.
l SWITCH0 (Close): No matter the callee enables the NP service or
not, the messages are sent to the SMC directly rather than sending
to the callee.
LOCOT RN It is valid only when the message source is a local network common
HERUS configu user. It is optional and its value is of enumeration type. It can be set to:
R re l BIT0 (LOCREQ): When it is selected, the LOCREQ message
parame contains relevant RN after being applied with the MNP service.
ter of
local l BIT1 (CAP IDP): When it is selected, the CAPIDP message contains
other relevant RN after being applied with the MNP service.
regular l BIT2 (SRI): When it is selected, the SRI message contains relevant
user RN after being applied with the MNP service.
l BIT3 (MO): When it is selected, the MO message contains relevant
l BIT4 (IAM): When it is selected, the IAM message contains relevant
l BIT5 (Process USSR): When it is selected, the USSD message
l BIT6 (CAP IDPSMS): When it is selected, the CAP IDPSMS
message contains relevant RN after being applied with the MNP
service.
l BIT7 (MAP SEND PARAMETERS): When it is selected, the MAP
SEND PARAMETERS message contains relevant RN after being
l BIT8 (Prepaid INAP IDP): When it is selected, the prepaid INAP
IDP message contains relevant RN after being applied with the MNP
service.


er ID eter
Name
FORWA Forwar It determines whether the system authenticates the forwarded-to

RDAUC d number subscribed by the subscriber.
number l OPEN (Open): The system authenticates the forwarded-to number.
check If the forwarded-to number belongs to the network that allows the
current network to forward messages to the network, the system
transparently forwards the INAP IDP/CAP IDP message; if the
forwarded-to number belongs to the network that does not allow the
current network to forward messages to the network, the system
returns ERROR.
l CLOSE (Close): The system transparently forwards the INAP IDP/
CAP IDP message without authenticating the forwarded-to number.
The other parameters are not required and you do not need to configure them.
Related Commands
Table 4-4 Related commands for configuring the MNP software configuration parameter
Command Function
SET MNPSOFTCFG To set the MNP software configuration parameter
LST MNPSOFTCFG To query the MNP software configuration parameter
4.4.2 Configuring HLR Address Table

Command
ADD MNPHLRADDR
Parameter
r ID r Name
ADDR HLR It specifies the GT address of the HLR in the local network.
address
number


r ID r Name
DPC HLR SPC It specifies the signaling point code of the HLR. It is mandatory.
It contains characters 0-F. It maps the active/standby code of the
international or national network in the MTP DSP table.
Related Commands
Table 4-5 Related commands for configuring the HLR address

Command Function
ADD MNPHLRADDR To add HLR address
MOD MNPHLRADDR To modify HLR address
RMV MNPHLRADDR To delete HLR address
LST MNPHLRADDR To query HLR address
4.4.3 Configure MNP Route Number Table

Command
ADD MNPROUTENUM
Parameter
r ID r Name
NUM Route It specifies the route number of the peer network to which a user
number number belongs. The value must be consistent with that set on the
device of the peer network.
IMSICD IMSI This parameter maps the IMSI number of the peer network. It must
number be in E.201 format. It can be set flexibly. The recommended format
is: MCC + MNC of the peer network.


r ID r Name
SMSINC SMS It specifies whether the network to which a subscriber belongs can
OM signaling communicate with this signaling network.
intercom It is optional. Its value is of the enumeration type. It can be set to
municate one or more of the following values:
flag
l G1 (SRI_FOR_SM signaling intercommunicate flag)
l G2 (SMSREQ signaling intercommunicate flag)
Related Commands
Table 4-6 Related commands for configuring the MNP route number
Command Function
ADD MNPROUTENUM To add MNP route number
MOD MNPROUTENUM To modify MNP route number
RMV MNPROUTENUM To delete MNP route number
LST MNPROUTENUM To query MNP route number
4.4.4 Configuring MNP Foreign Number Range Table

When a user number cannot be found in the service user data table, the system must query the
MNP foreign number range table to obtain the route number, and route the messages correctly
to the corresponding network.
Command
ADD MNPFRGNRNG
Parameter
r ID r Name
MINNUM Min. They specify the number range of a foreign network.

foreign This number range cannot be identical, overlapped, and
number intersected.
MAXNU Max. The length of Min. foreign number and that of Max. foreign
M foreign number must be the same.
number


r ID r Name
RNIDX Route It maps a record in the MNP route number table. It indicates the
number route directed to the foreign network. It must be defined by ADD
index MNPROUTENUM before being referenced here.
Related Commands
Table 4-7 Related commands for configuring the foreign number range
Command Function
ADD MNPFRGNRNG To add foreign number range
MOD MNPFRGNRNG To modify foreign number range
RMV MNPFRGNRNG To delete foreign number range
LST MNPFRGNRNG To query foreign number range
4.4.5 Configuring Service User Data Table

service user data table.
Command
ADD SERUATTR
Parameter
r ID r Name
USRNUM MSISDN It specifies the logical number of an MS. It carries no country code,
for example, 13X12345678.
SERVAT Whether Here, set the parameter to Enable MNP service.

TR enable
related
services


r ID r Name
NUMTYP Number It specifies the type of an MNP user. It can be set to:
E type l An own number not ported out
l An own number ported out
l A foreign number ported in
l A foreign number ported to a foreign network
It is set to An own number not ported out by default.
RNIDXT Route It specifies the index type of the user-mapped route. It can be set
YPE index type to:
l HLR (HLR address index): The value for TYPE0 (In local
network), TYPE2 (Moved in from external network),
TYPE4 (flexible number), and TYPE6 (NN number) is HLR
(HLR number index).
l RN (Route number index): The value for TYPE1 (Moved out
of local network) and TYPE3 (Moved to another non-local
network number) is RN (Route number index).
l ALL (HLR+RN): The value for TYPE5 (GSM number ported
to CDMA), TYPE7 (RN number), and TYPE8 (CDMA
number ported to GSM) is ALL (HLR+RN).
l TIME (Filter time segment index): It is selected when the
prepaid premium service is enabled.
It must be set based on the actual conditions.
RNIDX NP route It is configured when Route index type is set to Route number
index index and Route number index is not configured or configured
to the same value as this parameter. NP route index must be a valid
value. It must be set based on the actual conditions.
HLRIDX HLR It is set when Route index type is set to HLR number index or
address ALL. It must be a valid index existing in the MNP HLR address
index table.
RNIDX2 Route It is set when Route index type is set to ALL and NP route
number index is not configured. It must be a valid index existing in the
index MNP route number table.
Related Commands
Command Function

Command Function

This section describes the command, parameter, and related commands for configuring the SCCP
GT translation table.
Configure the following data:
l Local HLR address and translation type: DPC + SSN. The DPC is that of the local HLR.
l Foreign RN and translation type: DPC + GT. The DPC is that of a foreign HLR.
l Local GMSC address and translation type: DPC + SSN. The DPC is that of the local GMSC.
For details about the configuration, refer to chapter Configuring SCCP Data.

This section provides examples to describe how to configure the MNP data.
4.5.1 MNP Service in PLMN
This section provides examples to describe how to configure the MNP data in the PLMN.
4.5.2 Other MNP Services
For different MNP services, data configuration flows are the same but the MNP software
parameter settings are different.
4.5.1 MNP Service in PLMN

This section provides examples to describe how to configure the MNP data in the PLMN.
Assumption
These examples are related only to the PLMN networking structure. Figure 4-1 shows the PLMN
networking structure with the MNP service.
Table 4-9 and Table 4-10 list the MNP data that is collected.
Table 4-9 Local office information collection table
Country MNP mode Local network Convert UDT into XUDT

code route number
852 MNP_FN mode E134 No

Table 4-10 User data collection table
Min foreign Max foreign Route number SMS signaling

number number intercommunicate flag
66 69 E252 G1 (SRI_FOR_SM
signaling
intercommunicate flag)
HLR address MSISDN Number type MSISDN

number
11111 13928940000 In local network 13928940011
Number type MSISDN Number type MSISDN
Move out of local 13928940022 Moved in from 13928940033

network external network
Number type
Moved to another
non-local number
Based on the data collected, configure the MNP service data in the following manner.
Procedure
Step 1 Set the MNP service switch.
To set Country code to 852, MNP mode to MNP_FN mode, Local network route number
to E134, and Convert UDT into XUDT to Close, run the following command:
SET MNPSOFTCFG: NC="852", MNPMODE=MNPFN, LOCALRNCD="E134",
CONVTOXUDIT=CLOSE;
Step 2 Set the HLR number.
To set HLR address number to 1392894, run the following command:

ADD MNPHLRADDR: ADDR="1392894";
The index 0 is obtained after the command is run. This index is used as the route index when
you configure the NP user data.
Step 3 Set the MNP route number.
To set Route number to E252 and IMSI number to 8521392894 (MCC

+CC),SMSINCOM=G1-1, run the following command:
ADD MNPROUTENUM: NUM="E252", IMSICD="8521392894",SMSINCOM=G1-1;
The index 0 is obtained after the command is run. This index is used as the route index when
you configure the NP user data.
Step 4 Set the local network not ported out user.

To set MSISDN to 13428940000, Whether enable related services to Enable MNP service,
Number type to In local network, Route index type to HLR address index, and HLR address
index to 0, run the following command:
ADD SERUATTR: USRNUM="13428940000", SERVATTR=OMNP-1, NUMTYPE=TYPE0,
RNIDXTYPE=HLR, HLRIDX=0;
Step 5 Set the local network ported out user.

Number type to Move out of local network, Route index type to Route number index, and
NP route index to 0, run the following command:
RNIDXTYPE=RN, RNIDX=0;
Step 6 Set the foreign number ported in user.

Number type to Moved in from external network, Route index type to HLR address
index, and HLR address index to 0, run the following command:
Step 7 Set the foreign network ported to another foreign network user.
Number type to Moved to another non-local number, Route index type to Route number
index, and NP route index to 0, run the following command:
Step 8 Set the MNP foreign network number segment.

To set Min foreign number to 66, Max foreign number to 69, and Route number index to
0, run the following command:
ADD MNPFRGNRNG: MINNUM="66", MAXNUM="69", RNIDX=0;
----End
Verifying the MNP Service Switch

This step must be performed after you set the MNP service switch. To verify the MNP service
switch, run LST MNPSOFTCFG on the MML client.
LST MNPSOFTCFG:;

MNP Software Configuration Parameter
------------------------------------
Country code = 852
MNP Mode = MNP_FN mode
Local network route number = E134
Convert UDT into XUDT = Close
……

--- END
In the displayed result, Country code is 852, MNP Mode is MNP_FN mode, Local network
route number is E134, and Convert UDT into XUDT is Close. The results are the same as the
LST MNPHLRADDR:;

MNP HLR Address table
---------------------
Index Description HLR Address number HLR SPC
0 <NULL> 5555555555555555 1B0802

1 <NULL> 111 1B0602
2 <NULL> 861392 000009
3 ansi24 222 111111
4 itu14 333 001111
5 JK TEXT 1111 BBBBBB
--- END
In the displayed result, Index of the sixth record is 5, Description is JK TEXT, HLR address
number is 11111, HLR SPC is BBBBBB. The results are the same as the configured data
through the command, which indicates that the configuration is successful.
Verifying the MNP Route Number

This step must be performed after you set the MNP route number. To verify the MNP route
number, run LST MNPROUTENUM on the MML client.
LST MNPROUTENUM:;

MNP route number
----------------
Index Description Route number IMSI number SMS
signaling intercommunicate flag
0 <NULL> 123 123456789876
G_2<OFF>G_1<ON>
1 <NULL> 55 0123456789ABCDEF
G_2<OFF>G_1<ON>
2 <NULL> E252 8521392894
G_2<OFF>G_1<ON>
--- END
In record 3, Index is 2, Description is NULL, Route number is E252, and IMSI number is
8521392894,SMS signaling intercommunicate flag is G_2<OFF>G_1<ON>. The results are
the same as the data configured for the MNP routing number, which indicates that the
Verifying User Information

This step must be performed after you set the service user data. To verify the user information,
run LST SERUATTR on the MML client.

Check whether the configured service user data is displayed in the query results. If yes, the
service user data is successfully configured; if not, you must configure the service user data
again.
Verifying MNP Foreign Number Range

This step must be performed after you set the MNP foreign number range. To verify the MNP
foreign number range, run LST MNPFRGNRNG on the MML client.
LST MNPFRGNRNG:;

Foreign number range table
--------------------------
Index Description Min foreign number Max foreign number Route
number index
0 <NULL> 8613899998888 8613988889999 0

1 <NULL> 11
12 0
……
10 <NULL> 66
69 0
--- END
In record 11, Index is 10, Description is NULL, Min foreign number is 66, Max foreign
number is 69, and Route number is 0. The results are the same as the data configured for the
MNP foreign number range, which indicates that the configuration is successful.
4.5.2 Other MNP Services

For different MNP services, data configuration flows are the same but the MNP software
parameter settings are different.
NOTE
The MNP software parameters can be repeatedly configured. When you perform the settings to the newly
added service, the settings of the previous services are still effective.
MNP Function of the INAP Message

The message type on the SG can be configured, that is, the MNP function can be implemented
on different messages. The message type can be:
l MAP
l CAP
l INAP
l ISUP
To set the MNP function of the INAP message, set Message type of MNP service
processing to INAP, Country code to 86, Local GT address to 86139000001, and MNP query
service key to 2146, run the following command:

SET MNPSOFTCFG: MNPMSGTYPE=BIT2-1, NC="86", LOCALGTADDR="86139000001",

MNPSERVICEKEY=2146;
Other data configurations are the same as those of the MNP service in the PLMN. For details,
see chapter 4.5.1 MNP Service in PLMN.
MNP Function of the ISUP Message

It is used to control whether the SG supports the MNP function of the ISUP message.
To set the MNP function of the ISUP message, set Message type of MNP service processing
to ISUP, Country code to 86, Latency time of the collecting digits(s) to 4, and The fresh
method of collecting digits timer to For IAM , and for SAM resetting timer, run the following
command:
SET MNPSOFTCFG: MNPMSGTYPE=BIT3-1, NC="86", LATENCYTIME=4,
COLDIGTYPE=IAM1;
NOTE
Because MNP software parameters can be repeatedly configured, if the MNP function of the ISUP message
is configured based on the settings specified in MNP Function of the INAP Message, the SG supports
the MNP function of the INAP and ISUP messages at the same time.
Short Message Authentication Service

It is used to control whether the SG supports the short message authentication service.
To set the short message authentication service, set The RN configure parameter of foreign
not known ported to MO, The RN configure parameter of local regular user to MO, SMA
switch to Open and SMA called process switch to Open, run the following command:
SET MNPSOFTCFG: FNUNKNSUB=G2-1, LOCRNPARA=G2-1, SMASWITCH=SWITCH1,
SMASCHCALLED=SWITCH1;
MNP Function of ATI Mode

It is used to control whether the SG supports the MNP service in ATI mode.
To configure the MNP function in ATI mode, set The RN configure parameter of foreign not
known ported to ATI, The RN configure parameter of local regular user to ATI, and ATI
mode to TC relay, run the following command:
SET MNPSOFTCFG: FNUNKNSUB=G6-1, LOCRNPARA=G3-1, ATIMODE=MODE1;
Number Amendment Function

It is used to control whether the SG supports the number amendment function.
To set the number amendment function, set Message type of MNP service processing to
MAP, CAP, INAP, and ISUP, Country code to 86, and Number amend switch to Open, run
SET MNPSOFTCFG: MNPMSGTYPE=BIT0-1&BIT1-1&BIT2-1&BIT3-1, NC="86",
ISNUMAMEND=OPEN;
Call Anti-Loop Function

It is used to control whether the SG supports the call anti-loop function.

To set the call anti-loop function, set Country code to 86, Local network route number to
c333, and Loop_detection to Call Related Message, run the following command:
SET MNPSOFTCFG: NC="86", LOCALRNCD="c333", LOOPDETECT=G1-1;
Forwarded-To Number Authentication

It determines whether the system authenticates the forwarded-to number.
To enable this function, you must set Forward number check to Open.
SET MNPSOFTCFG: MNPMODE=MNPFN, FORWARDAUC=OPEN, AUCERROR=100, CONFIRM=Y;
INAP-Supported Prepaid Service

It determines whether the prepaid service is supported by the INAP protocol.
To enable this service, you must set Message type of MNP service processing to BIT15
(Prepaid INAP IDP). The following parameters can be set based on the actual networking
conditions:
l Set The RN configure parameter of foreign not known ported to G14(Prepaid INAP
IDP).
l Set The RN configure parameter of local regular user to G10(Prepaid INAP IDP).
l Set MNP NOA parameter to G11(Modify NoA of prepaid INAP IDP called party BCD
number).
l Set RN configure parameter of local other regular user to BIT8(Prepaid INAP IDP).
The following is an example for processing the INAP IDP message received from an ordinary
subscriber in the external network:
SET MNPSOFTCFG: MNPMODE=MNPFN, MNPMSGTYPE=BIT15, FNUNKNSUB=G14, CONFIRM=Y;

Feature Description 5 Configuring CRBT Service Data
5 Configuring CRBT Service Data
About This Chapter
With the customized ring back tone (CRBT) service, users can use customized music or ring
tones to replace the traditional and boring ring back tones. Before configuring the CRBT service
data, make sure that the hardware data, MTP data, and SCCP data are already configured.
5.1 CRBT Service
In the traditional communication service, when user A calls user B, user A hears boring beeps
before user B answers the phone. With the CRBT service, users can use customized music or
ring tones to replace the boring ring back tones. When a user enables the CRBT service and
customizes a ring back tone, a caller who calls this user can hear the customized tone rather than
the original boring beeps.
5.2 Service Flow
This section describes the networking structure for the CRBT service and the implementation
and service flow of the service.
Configuring the CRBT service data includes setting the CRBT software parameter, user number,
and the prefix analysis table.
5.5 Configuring CRBT Shielding Data
Configuring the CRBT shielding data includes setting the CRBT GT number range shielding
management and setting the CRBT user number range shielding management.
This section provides examples to describe how to configure the CRBT service data.

5 Configuring CRBT Service Data Feature Description
5.1 CRBT Service

In the traditional communication service, when user A calls user B, user A hears boring beeps
before user B answers the phone. With the CRBT service, users can use customized music or
ring tones to replace the boring ring back tones. When a user enables the CRBT service and
customizes a ring back tone, a caller who calls this user can hear the customized tone rather than
the original boring beeps.
A user can enable the CRBT service in a business hall, by dialing the customer service number,
or through the website of the service provider. After the CRBT service is enabled, the user can
subscribe new ring back tones through a phone or the website. In addition, the user can set
incoming calls to different groups and set different ring back tones for different groups. The user
can also play different ring back tones at different periods during the day.
The CRBT service supports various charging modes. The service fee is charged every month
and the ring back tone is charged each time it is subscribed.
With the CRBT service, network operators can provide customized and varied services to
increase the satisfaction of their users and promote the image of network operators. In addition,
network operators can deploy other services based on the CRBT service, such as mobile adverts.
5.1.2 Service Features
This section describes the service features of the CRBT service.

With the CRBT service, network operators can provide customized and varied services to
increase the satisfaction of their users and promote the image of network operators. In addition,
network operators can deploy other services based on the CRBT service, such as mobile adverts.
Table 5-1 compares the original ring back tone and the CRBT.
Table 5-1 Differences between original ring back tone and CRBT
Compared item Original ring back tone Customized ring back tone
What the caller The caller hears boring The caller hears new ring back tones,
hears? beeps. such as popular music, classical songs,
or pre-recorded announcement.
Whether the user The user cannot customize The user can customize the ring back
can customize the the ring back tone. tone or even record ring back tones.
ring back tone?
Is the subscriber It is not charged. User By paying a nominal fee, the user can
satisfied and do satisfaction cannot be met. enjoy differentiated services. The user
network operators gets satisfied and the network operator
benefit? benefits.


This section describes the service features of the CRBT service.
Implementation of CRBT Service

The CRBT service can be implemented based on the following schemes:
l Based on the SG7000
You can add an SG7000 to implement the CRBT service.
l Based on the IN network
You can add a dedicated SCP or platform, or upgrade the current SCP to implement the
CRBT service.
l Based on switch
You can upgrade or rebuild the current NEs, such as the switch and the HLR to implement
the CRBT service.
Features of SG7000 Service Implementation Scheme

The SG7000 CRBT service implementation scheme has the following features:
l You need not upgrade the current NEs for deploying the CRBT service. You only need to
add an SG to the current network. This reduces cost and network construction time, and
enhances competition.
l The scheme can adapt well to complex network environments and various NEs.
l The SG dual-plane mode is a reliable solution. The failure of one SG does not affect the
CRBT service. The AIP failure affects only the CRBT service but not the call connection.
l The location does not affect the CRBT service. That is, the caller can be any user and the
callee can roam to any area, but the CRBT service is not affected.
5.2 Service Flow

This section describes the networking structure for the CRBT service and the implementation
This section describes the networking structure for configuring the CRBT service data.
5.2.2 Service Triggering
This section describes the user identification mode and service triggering mode of the CRBT
service.
This section describes the implementation of the CRBT service.
5.2.4 Calling Flow
The CRBT service can be implemented based on virtual roaming or AIP prefix.
5.2.5 Registration and Deregistration Flow
This section describes how to register and deregister the CRBT service.
5.2.6 CRBT Customization Flow
This section describes how to customize a CRBT.

5.2.7 CRBT Query Flow

This section describes how to query the CRBT.
5.2.8 Service Charging
This section describes the different charging modes for the CRBT service.
5.2.9 Deployment Scope
For IN services implemented through overlapped networks, the SCP charges are based on the
MSRN. Thus, the CRBT service is charged depending on the actual network conditions.
5.2.10 Support to IN Services
In the signaling processing scheme, the SCP processes only the MSRN returned by the HLR.
To other signaling flow including the IN service flow, the SCP is transparent and thus it
completely supports the CRBT service of IN service users, including those with subscribed
service triggering mode and number segment triggering mode.
5.2.11 Support to Supplementary Services
This section describes the interaction between the CRBT service and the supplementary service.
5.2.12 Device Coordination Requirements
This section describes the requirements on device cooperation.

This section describes the networking structure for configuring the CRBT service data.
Figure 5-1 shows the networking structure of the CRBT service.
Figure 5-1 Networking structure of CRBT service
HLR: home location register AIP: advanced intelligent peripheral MSC: mobile switching center
GMSC: gateway mobile switching SP: service provider SG: U-SYS SG7000 Signaling
center Gateway

The functions of the devices in the networking are as follows:
l SG: It is used to process the signaling messages transferred between the GMSC/MSC and
the HLR.
l AIP: It is used to exchange signaling message between the GMSC/MSC and the HLR, store
the CRBT service data, play CRBTs to users, and customize and manage the ring back
tones.
l HLR: It is used to interact with the GMSC/MSC to return the forwarded-to numbers, and
interact with the AIP to return the mobile station IDs and the destination MSC address.
l GMSC/MSC: It is used as the calling party office. It transfers the call directly to the AIP
depending on the forwarded-to number.
l VMSC: When a user roams from a home MSC to another MSC, the latter MSC is called
the visited mobile switching center (VMSC).
l Portal: It is used to provide the access interface for CRBT users, the SP, and the
administrator. They can access the web page that is provided by the Portal over HTTP, and
customize and manage services through simple and clear operations.
l SP: The SP provides CRBT users with new ring back tones and the web page through the
Portal for managing the tones.
5.2.2 Service Triggering

This section describes the user identification mode and service triggering mode of the CRBT
service.
Identifying CRBT User

The SG7000 can identify a CRBT user. The CRBT service attribute of a user is stored in the
database of the SG7000. During a call setup, the SG7000 intercepts the signaling message and
analyzes whether the callee has enabled the CRBT service. If yes, the SG7000 triggers the CRBT
service. If not, the SG7000 transparently transfers the message.
Triggering CRBT Service

To trigger the CRBT service, the SG7000 needs to change the number in the signaling message
that is related to a CRBT user. The call with the changed number is then routed to the CRBT
service platform.
An SRI_ACK message sent from the HLR to the MSC contains the mobile station roaming
number (MSRN), which is used by the switch to page the callee. The SG7000 intercepts the
SRI_ACK message that is related to a CRBT user and changes the MSRN in the message to the
MSRN that is homed to the AIP. The SG7000 then sends the modified message to the switch.
The switch routes the call to the CRBT service platform depending on the modified MSRN.
To avoid all messages that are returned from the HLR to the VMSC from being terminated at
the SG7000, the SG7000 analyzes the SRI messages. For the SRI_ACK messages that are related
to CRBT users, the SG7000 changes the SCCP calling address to that of the SG7000. For the
SRI_ACK messages that are not related to CRBT users, the SG7000 does not change the SCCP
calling address.

This section describes the implementation of the CRBT service.

Storing and Managing CRBTs

The AIP stores and manages the CRBTs.
Playing CRBTs
When a CRBT user acts as the callee, the switch routes the call to the AIP after paging the callee
and receiving the response. Then the AIP plays the CRBT to the caller depending on the attribute
of the CRBT user, and screens the normal ring back tone coming from the called party switch
at the same time.
5.2.4 Calling Flow

The CRBT service can be implemented based on virtual roaming or AIP prefix.
CRBT Calling Flow Based on Virtual Roaming

Figure 5-2 shows the CRBT calling flow based on virtual roaming.
Figure 5-2 CRBT calling flow based on virtual roaming
O_MSC: origin mobile switching center T_MSC: terminal mobile switching center
The calling flow is described as follows:

1. User A calls CRBT user B. The O_MSC/GMSC sends an SRI message to the HLR. The
SG intercepts the SRI message and replaces the calling address in the message with the
SG address if the message is related to CRBT user B.
2. The SG intercepts the SRI_ACK message and changes the MSRN in the message to the
virtual MSRN.
3. The O_MSC/GMSC routes the call to the AIP depending on the virtual MSRN.
4. The SG changes the virtual MSRN in the IAM to the actual MSRN (original MSRN) and
adds the original called MSISDN to the message.
5. The AIP registers the incoming call as a CRBT call and connects the call to the T_MSC
depending on the IAM.
6. After identifying the callee, the T_MSC returns an ACM to the AIP. Then the AIP plays
the CRBT to the caller depending on the calling and called MSISDNs. At the same time,
the AIP screens the normal ring back tone coming from the called party switch.
7. When the callee answers the call, the AIP receives the signal and stops playing the CRBT.
The session begins.
CRBT Calling Flow Based on AIP Prefix
Figure 5-3 CRBT calling flow based on AIP prefix
The calling flow is described as follows:
1. User A calls CRBT user B. The O_MSC/GMSC sends an SRI message to the HLR.

2. If the callee is a CRBT user, the SG intercepts the SRI message and replaces the message
response address in the message with the SG address.
3. The SG intercepts the SRI_ACK message and changes the MSRN in the message to "AIP
+ MSRN".
4. After receiving the SRI_ACK message, the O_MSC/GMSC routes the call to the T_MSC
depending on the MSRN.
5. The O_MSC/GMSC sends an IAM message to the T_MSC.
6. The T_MSC returns an ACM.
7. The O_MSC sends an IAM that contains the called MSISDN to the AIP.
8. The AIP returns an ACM and plays the CRBT at the same time.
9. When the callee answers the call, the T_MSC returns an ANM.
10. The O_MSC/GMSC sends an REL message to the AIP to release the call and stop playing
the CRBT.
5.2.5 Registration and Deregistration Flow

This section describes how to register and deregister the CRBT service.
Registration or Deregistration Through Billing System

The billing system provides interfaces to connect with the business hall, web business hall,
customer service center, and short message center (SMC). In this case, users can register or
deregister the CRBT service in various ways through the billing system.
After receiving a request of registration or deregistration from a user, the billing system proceeds
as follows:
1. The billing system authenticates the request.

2. The billing system notifies the CRBT service platform through the MML interface of the
SG, and the SG adds or removes the user data. After successful operation, the CRBT
platform notifies the SMC to send a message to the user.
3. The CRBT platform sends the operation result to the billing system.
4. The billing system stores the record for further querying or charging.
Registration or Deregistration Through Service Management Flow

The registration or deregistration flow is described as follows:
1. A user dials the CRBT service number to trigger the CRBT service platform through the
service management flow. The service platform notifies the billing system.
2. The billing system (or the CRBT service platform) authenticates the user and modifies the
user data in the SG.
3. The billing system notifies the CRBT service platform that the user is successfully
registered or deregistered.
4. The CRBT platform adds or removes the user data depending on the information returned
by the billing system.
5. The CRBT platform notifies the user the result through a message.

Registration or Deregistration Through CRBT Service Platform

1. A user logs in to the CRBT service platform, and then enters the MSISDN.
2. The CRBT service platform sends a message containing the password to the user.
3. With the password, the user can register or deregister the CRBT service on the platform.
4. The CRBT service platform notifies the SG or the billing system to add or remove the user
data.
5.2.6 CRBT Customization Flow

This section describes how to customize a CRBT.
Customizing CRBT Through Voice Management Flow

The customization flow is described as follows:
1. The end office of the calling party triggers the CRBT service from the CRBT service
platform based on the access code of the voice management flow.
2. The CRBT service platform guides the user to complete the CRBT customization through
voice assistant.
3. The CRBT service platform instructs the Web Server to finish the operation.
4. The CRBT service platform returns the result to the user through the voice assistant.
5. The CRBT service platform notifies the billing system to generate the bill, informs the user
with a message, and modifies the user data in the database.
Customizing CRBT Through CRBT Service Platform

The customization flow is described as follows:
1. A user can send the request of customizing the CRBT service to the CRBT platform through
WEB, WAP or a message.
2. The CRBT service platform authenticates the user.
3. The CRBT service platform submits the request to the Web Server of the AIP.
4. The Web Server customizes the CRBT and returns the result to the user through the CRBT
service platform.
5. The CRBT service platform sends the charging request to the billing system.
6. The CRBT service platform informs the user through a message.
5.2.7 CRBT Query Flow

This section describes how to query the CRBT.

Modifying, Setting or Querying CRBT Through WEB
Figure 5-4 Modifying setting or querying CRBT through WEB
The flow is as follows:

1. A user sends the request to the Portal/CRBT service platform.
2. The Portal/CRBT service platform sends the operation request to the AIP.
3. The AIP returns the result to the Portal/CRBT service platform.
4. The Portal/CRBT service platform determines whether to send a message based on the
result returned from the AIP.
5. The Portal/CRBT service platform determines whether to send the charging request to the
billing system based on the result returned from the AIP.

Modifying, Setting or Querying CRBT Through Phone
Figure 5-5 Modifying setting or querying CRBT through phone
The flow is as follows:
1. A user sends the request to the AIP/Portal/CRBT service platform.

2. The AIP/Portal/CRBT service platform guides the user in completing the CRBT
customization through voice assistant.
3. The Portal/CRBT service platform determines whether to send a message based on the
result returned from the AIP.
4. The Portal/CRBT service platform determines whether to send the charging request to the
billing system based on the result returned from the AIP.
5.2.8 Service Charging

This section describes the different charging modes for the CRBT service.
Post-Paid and Non-IN Pre-Paid VPN Users

The user is charged a monthly fee for the CRBT service.
For a defaulting user, the billing system suspends the service. In this case, the CRBT service is
disabled until the user pays the fee.
A user is also charged for changing a CRBT.
When a user changes a CRBT on the web, a web bill is generated based on WEB charging mode.
At the same time, a message is sent to the user to inform the successful change. When a user
changes a CRBT through the voice assistant, the AIP generates the bill and sends it to the billing
system.
IN Pre-Paid Users
The user is charged a monthly fee for the CRBT service.

When a user changes a CRBT in WEB mode, the SCP deducts the fee and generates the bill.
CRBT Library Charging Mode

If a user uses a CRBT library, the user can download CRBTs to the library and set CRBTs in
the library. Downloading CRBTs refers to adding CRBTs to the library. Setting CRBTs refers
to customizing a CRBT among those in the library.
In this mode, each time the user downloads a CRBT to the library, the fee is charged. The user
is not required to pay the fee for setting the CRBTs.
5.2.9 Deployment Scope

For IN services implemented through overlapped networks, the SCP charges are based on the
MSRN. Thus, the CRBT service is charged depending on the actual network conditions.
l For IN services implemented in target networks, the VLR information is contained in the
T_CSI message returned by the HLR and the SCP charges the callee based on the VLR
information. In this case, the implementation of the CRBT service does not affect the
charging.
l For IN services implemented in non-target networks, the SCP charges the caller based on
the MSRN. In this case, if the CRBT service is implemented through virtual roaming
number mode, the SCP must process the virtual MSRN based on different number
segments.
5.2.10 Support to IN Services

In the signaling processing scheme, the SCP processes only the MSRN returned by the HLR.
To other signaling flow including the IN service flow, the SCP is transparent and thus it
completely supports the CRBT service of IN service users, including those with subscribed
service triggering mode and number segment triggering mode.
You must note that, during the signaling processing of China Unicom PPS service, the SCP
charges the callee based on the MSRN. However, the virtual MSRN obtained by the MSC/SSP
cannot indicate the VLR of the callee, so the SCP cannot charges the callee correctly. Consider
the following aspects:
l If there is only one AIP or a few AIPs in a province, a local call to a local CRBT service
user should also be transferred by the AIP. In this case, if the SCP charges the callee based
on the virtual MSRN, it may charge the roaming fee.
l When a user roams out of the AIP to which the user belongs, the SCP cannot charge the
toll fee and the roaming fee based on the virtual MSRN.
l When a user roams out of the province to which the user belongs, the SCP cannot accurately
charges the toll fee and the roaming fee based on the virtual MSRN.
There are two schemes for mitigating and solving the problems:
l Scheme one: Do not provide the CRBT service to the PPS users.
l Scheme two: Allocate an MSRN segment to each local network. This segment is used by
the SG as virtual MSRNs. It is required that the local MSC is able to route a call with any
MSRN in this MSRN segment to the TMSC or AIP, and the local SCP charges the local
fee for the call. When a user roams out of a homed province, the user is allocated a special
MSRN which is the charged provincial roaming fee by the SCP. At the same time, the
switch of the visited province connects the call to the visited TMSC based on this special

MSRN. In this case, the allocated MSRN segment must comply with the current coding
rules and special charging data must be configured on the SCP.
5.2.11 Support to Supplementary Services

This section describes the interaction between the CRBT service and the supplementary service.
Call Hold, Call Waiting, and Multi-Way Calling

Supplementary services including call hold, call waiting, and multi-way calling are supported
no matter the CRBT service is registered or not.
If user B has registered the CRBT service and call hold service, the signaling process of a call
connection is as follows:
1. User A calls user B and the session is set up.
2. User C calls B and the call is routed to the AIP.
3. The AIP calls B and the end office of B plays call hold announcement.
4. The AIP finds that the end office of B does not play the normal ring back tone to C.
5. The AIP transfers the announcement transparently to C instead of playing the CRBT.
6. After the announcement, C hears the normal ring back tone played by the end office of B.
The signaling process of the call waiting and multi-way calling is the same as that of the call
hold.
Call Forwarding in Calling Office

If the forwarded-to user has registered the CRBT service, the caller hears the CRBT. If the user
has not registered the CRBT service, the caller hears the normal ring back tone.
The signaling process of a call connection is as follows:
1. User A calls user B.
2. The SG judges from the SRI_ack message that B has set call forwarding to user C.
3. The SG transfers the message directly to the MSC/GMSC instead of processing it.
4. The SG processes the SRI and SRI_ack messages sent to C and then connects the call to
the AIP.
5. A (the caller) hears the CRBT if C has registered the CRBT service; otherwise, A hears the
normal ring back tone.
Call Forwarding in Called Office

For call forwarding in the called office (including call forwarding busy, call forwarding on no
reply, call forwarding on paging no reply, and call forwarding on allocation failure), the signaling
process of a call connection is as follows:
1. User A calls user B and B has set call forwarding to user C.
2. The call is connected to C.
3. If C has not registered the CRBT service, the end office of C plays normal ring back tone
to the AIP. The AIP suppresses the normal tone and plays the CRBT of B to A. If C has
registered the CRBT service, the end office of C plays the CRBT to the AIP. Through the
voice recognition function, the AIP finds that the tone played by the end office of C is not

a standard ring back tone. The AIP can either transfer the CRBT of C to A transparently
or screens the CRBT of C and plays the CRBT of B.
There is an exception for call forwarding on no reply (CFNR) service in the above signaling
process. In the CFNR service, the AIP suppresses the standard ring back tone played by the end
office of B and plays the CRBT of B. When the call is forwarded to C, the AIP does not perform
the voice recognition to the CRBT of C. Therefore, A still hears the CRBT of B.
NOTE
The signaling interface between the SG and the AIP directly affects the call forwarding service. If the
SG adopts the IAI message of the TUP to carry the called number and places this number in the information
element (IE) of the "original called number", the actual forwarded-to number is overwritten. If the AIP
clears the forwarding flag when processing the IAI message, there is a risk of voice channel loop, for the
forwarding flag of the call that has been forwarded is cleared. In this case, the processing mode of the AIP
must be clear.

This section describes the requirements on device cooperation.
Requirement on Data Configuration of Devices

l Data configuration of MSC/GMSC
For the MSC/GMSC, you must modify the GT in E.164 code addressing mode. The user
number segment is then translated to the SG7000 by preference, or translated to the HLR
of the callee. (For the GMSC, multiple HLRs can work as the standby translation points.)
The signaling point code (SPC) of the AIP must be configured on the MSC, and the
signaling route to the AIP through the SG7000 must be set up.
The MSRN segment data of the AIP must be configured on the MSC.
Voice channel trunk must be configured between the MSC and the AIP.
l Data configuration of TMSC
The SPC of the AIP must be configured on the TMSC, and the signaling route to the AIP
through the SG7000 must be set up.
The MSRN segment data of the AIP must be configured on the TMSC.
Voice channel trunk must be configured between the TMSC and the AIP.
l Data configuration of AIP
The AIP must be allocated with an MSRN segment.
Voice channel trunk must be configured between the AIP and the TMSC.
The signaling route to the TMSC must be configured on the AIP.
l Data configuration of HSTP
Modify the GT in E.164 code addressing mode on the HSTP. The signaling messages of
the user number segment are translated to the SG7000.
Requirement on AIP
Upon receiving an incoming call from the MSC/TMSC, the AIP connects the call based on the
MSRN.
If the AIP is shared by the GSM and the CDMA networks, the AIP determines whether the call
is from the GSM network or the CDMA network based on the CRBT prefix in the IAI message,
and then processes the call.

The AIP can intercept common RBT and sends the CRBT to the caller based on the calling and
called numbers in the IAI message.
If the callee rejects the call, there is no corresponding signaling identification at the end office
of the callee and the end office of the callee plays the busy tone. The AIP must be able to identify
the busy tone and stop playing the CRBT, and then transmit the busy tone transparently.
The AIP can be connected to the voice channel.
The Portal can be connected to the SG7000s (configured in pair) through the TCP/IP-based
MML interface, and can send service subscription and cancellation information to the
SG7000.
If the AIP is shared by the GSM and CDMA networks, the Portal must support the subscription
in the GSM and CDMA networks.

5.3.1 Terms
This section describes the terms used during configuring the CRBT service data.
You must follow certain principles to configure the CRBT service data.
This section describes the relations between data tables related to CRBT data configuration.
Before configuring the CRBT service, you must collect the data including the start virtual
roaming number, end virtual roaming number, and GSM local GT number.
5.3.5 General Steps
You must follow certain procedures to configure the CRBT service data.
5.3.1 Terms
This section describes the terms used during configuring the CRBT service data.
Logical Number
It is the number of the mobile phone of the user.
Virtual Roaming Number

In virtual roaming mode, it is the virtual number used by the SG to replace the real number of
the user.
AIP (Advanced Intelligent Peripheral)

It is the equipment responsible for performing the CRBT service flow and playing the CRBT.

Virtual Roaming Mode

When processing the MSC messages, the SG replaces the real number of the user with a virtual
roaming number. Therefore, the subsequent call messages are transmitted through the SG. The
SG replaces the virtual roaming number with the real number and connects the call to the AIP
to complete the CRBT service flow.
AIP Prefix Mode

When processing the MSC messages, the SG adds the AIP prefix on the real number of the user.
Therefore, the subsequent call messages are transmitted to the AIP after being processed by the
MSC. Then the CRBT service flow is completed.

You must follow certain principles to configure the CRBT service data.
Data configuration of the CRBT service can be divided into the following parts:
l Configuring CRBT service parameters

l Configuring the provincial VMSC data
l Configuring user data
Configuring CRBT Service Parameters

The configuration of the CRBT service parameters includes: configuration of the CRBT virtual
roaming number resource and configuration of the CRBT software parameters.
In the virtual roaming mode, the virtual roaming number resource is used to connect the signaling
and identify the location of the call source. When used for configuring the provincial VMSC
number segment, a virtual roaming number segment identifies a charging area (usually a local
network). Therefore, when configuring the provincial VMSC number segment data, a charging
area must be configured with the same virtual roaming number index. In the virtual roaming
mode, the virtual roaming number is also used to identify a CRBT user roaming out of a province.
The CRBT software parameters refer to various software parameters used to configure the CRBT
service. The resource board PMC number, Resource time out, and RBT system
parameters are the common parameters and must be configured in both the AIP prefix mode
and virtual roaming mode. For details, see the following section about the data configuration of
the CRBT service.
In the AIP prefix mode, the GSM prefix number and CDMA prefix number must be configured
to the AIP prefix number adopted in the network. If the CRBT service is supported when the
caller is roaming out of a province, the mode of the CRBT must be configured to the AIP prefix
mode. In the virtual roaming mode, the GSM prefix number and CDMA prefix number must be
configured to the AIP prefix number adopted in the network. If the CRBT service is supported
when the caller is roaming out of a province, the mode of the CRBT must be configured to the
virtual roaming mode. You must configure whether to trigger the CRBT service if the subsequent
messages contain the original called number (for configuring whether to support the CRBT
service when the callee has call forwarding service), and whether the CRBT supports the
parameter for testing the available trunks. For details, see the following section about the data
configuration of the CRBT service.

Configuring Provincial VMSC Data

The configuration of the provincial VMSC data includes: configuration of the provincial VMSC
data, configuration of the CRBT implementation mode when the VMSC in the number segment
acts as the calling office. In virtual roaming mode, the virtual roaming number index must also
be configured.
In the AIP prefix mode, you must configure the provincial VMSC data based on the start GT
number and end GT number. You must set the implementation mode of the CRBT service to
the AIP prefix mode, indicating that the CRBT service is to be implemented in the AIP prefix
mode if the provincial VMSC acts as the calling office in the number segment.
In the virtual roaming mode, you must set the provincial VMSC data based on the start GT
number and end GT number. You must set the implementation mode of the CRBT service to
the virtual roaming mode, indicating that CRBT service is to be implemented in the virtual
roaming mode if the provincial VMSC acts as the calling office in the number segment. You
must configure the virtual roaming number index used by the VMSC. One virtual roaming
number segment identifies a charging area (usually a local network). Therefore, the VMSCs in
a charging area must be configured with the same virtual roaming number index.
Configuring User Data

Configuring user data refers to configure the data of the CRBT user, including: configuration
of the user number segment and configuration of CRBT user data.
The configuration of the user number segment includes: the configuration of the user number
segment and the configuration of the active/standby AIP signaling point index corresponding to
the user number segment.
The configuration of the CRBT user data includes: configuring the user logical number and
configuring whether the user can use the CRBT service when roaming out of a province.
The user logical number to be configured must be within the range set in the user number segment
table.
In addition, the parameter Whether support RBT when roaming out of province is valid only
when the CRBT software parameter table (configured by SET CRSOFTCFG) supports
roaming out of a province.

This section describes the relations between data tables related to CRBT data configuration.
Relation Between CRBT Data Tables

Figure 5-6 shows the data configuration sequence from top to bottom. When you add records
to the tables, conduct the operations from the upper tables to the lower ones. When you remove
records from the tables, conduct the operations from the lower tables to the upper tables.

Figure 5-6 Relation between CRBT data tables
Relation Between CRBT Data Tables and Other Data Tables
The reference relation between the parameters of the MTP data and local office data is shown
in Figure 5-6. The destination signaling point (DSP) table of the MTP references the index
number of ADD LN. The link set table of the MTP references the index number of SET OFI.

For configuration of the logical network through ADD LN and local office information through
SET OFI, see chapter Configuring Local Office Data.

Before configuring the CRBT service, you must collect the data including the start virtual
roaming number, end virtual roaming number, and GSM local GT number.
Before data configuration, you need to collect the data as listed in Table 5-2.
If support GSM Start dummy End dummy Local GSM GT

and CDMA ramble number ramble number number
Local CDMA GT GSM prefix number CDMA prefix GSM virtual

number number roaming number
index out of
province
CDMA virtual GSM virtual roaming If GSM support If CDMA support

roaming number number index for rambling RBT rambling RBT
index out of international
province roaming
Resource board Resource time out Whether trigger Resource board

PMC number RBT when the PMC number
following msg has Resource time out
original called Whether trigger
number RBT when the
following msg has
original called
number Whether
support checking
for available relay
RBT system Country Code Wait for number The time waiting for
parameters or not number
Start GT number End GT number RBT realizing Virtual roaming

mode number index
Start user logic End user logic Main AIP point Standby AIP point
number number code index code index


MSISDN Whether support

RBT when roaming
out of province
5.3.5 General Steps

You must follow certain procedures to configure the CRBT service data.
Table 5-3 shows the steps for configuring the CRBT data.
Table 5-3 Steps for configuring the CRBT data
Step Operation
1 To add virtual roaming number
2 To set CBRT software parameters
3 To set provincial VMSC number range
4 To set user number range
5 To set CRBT user data

Configuring the CRBT service data includes setting the CRBT software parameter, user number,
and the prefix analysis table.
5.4.1 Adding Virtual Roaming Number
roaming number.
5.4.2 Setting CRBT Software Parameters
This section describes the command, parameter, and related commands for setting the CRBT
5.4.3 Setting Prefix Analysis Table
When the collecting digits function is started, the system obtains the length of the collected digits
of the number prefix from this table. If this function is started, but there is no relevant prefix
configured in the table, the CRBT service of the relevant number is not triggered.
5.4.4 Setting Provincial VMSC Number Range
This section describes the command, parameter, and related commands for setting the provincial
VMSC number range.

5.4.5 Setting User Number Range

This section describes the command, parameter, and related commands for setting the user
number range.
5.4.6 Setting CRBT User Data
user data.
5.4.1 Adding Virtual Roaming Number

roaming number.
Command
ADD CRVMSRN
Parameter
r ID r Name
GSMCD If support It specifies whether the virtual roaming number can be used in the
MA GSM and GSM or CDMA network.
CDMA
SVMSRN Start They specify a virtual roaming number range.

dummy
ramble
number
EVMSRN End
dummy
ramble
number
Related Commands
Table 5-4 Related commands for configuring the dummy ramble number
Command Function
ADD CRVMSRN To add dummy ramble number
MOD CRVMSRN To modify dummy ramble number
RMV CRVMSRN To delete dummy ramble number
LST CRVMSRN To query dummy ramble number

5.4.2 Setting CRBT Software Parameters

Command
SET CRSOFTCFG
Parameter
r ID r Name
LGGT Local They specify the local GT number used by the equipment in the
GSM GT network. The number must be allocated in the network.
number
LCGT Local
CDMA
GT
number
GPRE GSM The parameters are used to trigger the number prefix added in the
prefix message by the AIP. The value must be consistent with that set on
number the AIP.
CPRE CDMA
prefix
number
GSMOVI GSM The parameters specify the virtual roaming number resource used
DX virtual in the system when the user is roaming out of a province.
roaming
number
index out
of
province
CDMAO CDMA
VIDX virtual
roaming
number
index out
of
province


r ID r Name
GSMIRID GSM In the virtual roaming mode, it specifies the virtual roaming
X virtual number index allocated to the GSM user for international roaming.
roaming
number
index for
internatio
nal
roaming
GSRCR If GSM The parameters specify the supported types of the roaming CRBT.
support The options are:
rambling l Support called roaming in other network
RBT
l Support calling roaming in other network
CSRCR If CDMA l AIP-Prefix-RBT Mode or virtual roaming mode when calling
support roaming in other network
rambling l Support RBT when calling roaming in home network and called
RBT roaming in other network
l Support RBT when called roaming abroad
When it is set to Support calling roaming in other network, you
must configure whether the caller CRBT mode is the AIP prefix
mode or roaming number mode.
When the parameter is set to Support called roaming in other
network, the option Support RBT when calling roaming in home
network and called roaming in other network is invalid, and the
CRBT is supported when the callee is roaming out of a province.
When the parameter is not set to Support called roaming in other
network, but is set to Support RBT when calling roaming in home
network and called roaming in other network, the CRBT is
supported when the caller is in the province and the callee is
roaming out of a province. When the parameter is not set to Support
called roaming in other network or Support RBT when calling
roaming in home network and called roaming in other network, the
CRBT is not supported in this mode.


r ID r Name
RBDPMC Resource It specifies the PMC number of the active SBPU/SBPE resource
board board used by the equipment in the system. The corresponding
PMC relations between the PMC number and the shelf number, service
number frame number, slot number is as listed in Table 5-5.
The PMC number is the logical number of the board in the service
frame. The PMC logical number of the SYS board in slot 6 of
service frame 0 rack 0 is 0. The PMC logical number of the SYS
board in slot 8 of service frame 0 rack 0 is 1.The PMC logical
numbers of the SBPU/SBPE boards in the slots from bottom to top
of the left half of service frame 0 rack 0 are 12, 10, ... 2. The PMC
logical numbers of the SBPU/SBPE boards in the slots from
bottom to top of the right half of service frame 0 rack 0 are 3, 5, ...
13.
The PMC numbers of the SYS boards and SBPU/SBPE boards in
the rest service frames follow the PMC numbers of the preceding
service frame. For example, if the PMC number of the SYS board
in slot 6 of service frame 1 rack 0 is 14, the PMC number of the
SYS board in slot 8 is 15. The PMC logical numbers of the
SBPU/SBPE boards in the slots from bottom to top of the left half
of the service frame are 26-16. The PMC logical numbers of the
SBPU/SBPE boards in the slots from bottom to top of the right half
of the service frame are 17-27.
When the SBPU/SBPE boards work as the CRBT service resource
boards, they are configured in pairs in the left and right half of the
service frame. The slot numbers of the active and standby
SBPUs/SBPEs in the service frame are in pairs. For example, the
SBPUs/SBPEs with PMC numbers of 2 and 3 are active and
standby SBPUs/SBPEs and the SBPUs/SBPEs with PMC numbers
of 4 and 5 are active and standby SBPUs/SBPEs.
SRCTOU Resource It specifies the time out threshold of the CRBT resources
T time out configured in the resource board.
ISENCR Whether It determines whether the CRBT service is supported when the
trigger called number is forwarded.
RBT when
the
following
msg has
original
called
number


r ID r Name
ENCRCR Whether It determines whether to detect the available trunk to the AIP
L support during the CRBT connection.
checking If the trunk detection is supported, the system checks whether there
for is available trunk to the AIP during the CRBT connection. If there
available is available trunk, the CRBT is connected; if not, the common RBT
relay is connected.
If the trunk detection is not supported, the CRBT is connected
directly.
SENSTC RBT It is the internal parameter of the system. You need not set this
system parameter. It is set to PARAMETER2 by default.
parameter
s
CYCODE Country It specifies the country code of the local area.

Code
WAITIN Wait for It determines whether the CRBT is supported when the switch
GNUM number or sends the SAM/SAO message.
not
WAITTI The time It specifies the duration of the timer when the SG is waiting for the
ME waiting SAM/SAO message.
for
number
Table 5-5 Mapping between PMC number and rack number, service frame number, and slot
number
Slot number 0 1 2 3 4 5 6 8 10 11 12 14 15 16
Service frame 0 12 10 8 6 4 2 0 1 3 5 7 9 11 13
of rack 0
Service frame 1 26 24 22 20 18 16 14 15 17 19 21 23 25 27
of rack 0
Service frame 0 40 38 36 34 32 30 28 29 31 33 35 37 39 41
of rack 1
Service frame 1 54 52 50 48 46 44 42 43 45 47 49 51 53 55
of rack 1

Related Commands
Table 5-6 Related commands for configuring the CRBT software parameter
Command Function
SET CRSOFTCFG RBT soft configuration
LST CRSOFTCFG To query RBT soft configuration
5.4.3 Setting Prefix Analysis Table

When the collecting digits function is started, the system obtains the length of the collected digits
of the number prefix from this table. If this function is started, but there is no relevant prefix
configured in the table, the CRBT service of the relevant number is not triggered.
Command
ADD NUMPFX
Parameter
r ID r Name
NUMPFX Number It specifies the number prefix to be performed with digits

prefix collecting.
NUMLEN Match It specifies the length of the collected digits corresponding to the
length field. It cannot be less than the length of the prefix because it
contains the prefix.
Related Commands
Table 5-7 Related commands for configuring the prefix analysis table
Command Function
ADD NUMPFX To add word crest Analysis table
MOD NUMPFX To modify word crest Analysis table
RMV NUMPFX To delete word crest Analysis table
LST NUMPFX To query word crest Analysis table

5.4.4 Setting Provincial VMSC Number Range

This section describes the command, parameter, and related commands for setting the provincial
VMSC number range.
Command
ADD CRVMSCRNG
Parameter
r ID r Name
SGADDR Start GT They specify the GT number range of the equipments in each local
number network in a province.
NOTE
EGADDR End GT The same record with Start GT number and End GT number cannot be
number configured in the VMSC number range of a province.
CRKIND RBT It specifies the realizing mode of the CRBT of the corresponding
realizing local network. It can be set to AIP prefix or dummy ramble.
mode
VMSRNI Virtual It specifies the virtual roaming number index used by the number
DX roaming range when configuring the virtual roaming mode. The VMSC
number number range with the same virtual roaming number index
index corresponds to a local network.
Related Commands
Table 5-8 Related commands for configuring the provincial VMSC number range
Command Function
ADD CRVMSCRNG To add province VMSC range
MOD CRVMSCRNG To modify province VMSC range
RMV CRVMSCRNG To delete province VMSC range
LST CRVMSCRNG To query province VMSC range
5.4.5 Setting User Number Range

This section describes the command, parameter, and related commands for setting the user
number range.
Command
ADD SERUSERNG

Parameter
r ID r Name
SUMSIS Start user They specify the logical number range of the user's terminal in the
DN logic local network. The number is in the form of a common user number
number without country code.
EUMSIS End user

DN logic
number
MSTAIPS Main AIP They specify the signaling point indexes of the active and standby
P point code AIPs used in the user number range. They correspond to the
index indexes in the DSP table. The signaling points of the active and
standby AIPs must be configured in the DSP table in advance.
BCKAIPS Standby
P AIP point
code index
Related Commands
Table 5-9 Related commands for configuring the user number range
Command Function
ADD SERUSERNG To add user range
MOD SERUSERNG To modify user range
RMV SERUSERNG To delete user range
LST SERUSERNG To query user range
5.4.6 Setting CRBT User Data

user data.
Command
ADD SERUATTR

Parameter
r ID r Name
USRNUM MSISDN It is the number of the mobile phone of the user. It must be in the
range set in the user number range table (configured by ADD
SERUSERNG).
SERVAT Whether It must be set to Enable RBT service.

TR enable
related
services
USRATT Whether It determines whether the CRBT service is supported when the user
R support is roaming out of a province. If the CRBT service is not supported
RBT when when the user is roaming (configured by SET CRSOFTCFG), the
roaming value Support here is invalid.
out of
province
Related Commands
Table 5-10 Related commands for configuring the CRBT user data
Command Function
5.5 Configuring CRBT Shielding Data

Configuring the CRBT shielding data includes setting the CRBT GT number range shielding
management and setting the CRBT user number range shielding management.
The following are the two cases for the messages that determine not to perform the CRBT
processing:
l When C link is set up between the SGs, the signaling transferred between the load sharing
SGs must be shielded to avoid repeated processing of the CRBT. The messages sent from
the SG are transmitted directly and transparently.
l When the end office mode CRBT and SG mode CRBT are both adopted in the networking
solution, the MSC and HLR used in the end office mode must be configured to avoid conflict
of the two modes. The MSC can be identified through the GT number range shielding. The
HLR is identified through the GT number range shielding. Therefore, the two types of

CRBT services can be processed separately. The messages in the end office mode are
transmitted directly and transparently.
5.5.1 Configuring CRBT GT Number Range Shielding
The configuration of this table enables you to specify the CRBT service in certain office
directions and identify the signaling transferred between the load sharing SGs.
5.5.2 Configuring CRBT User Number Range Shielding
This operation shields the HLR number range used in the end office mode. You can determine
the CRBT user in the end office mode though user number range shielding and the GT number
range shielding table of the CRBT.
5.5.1 Configuring CRBT GT Number Range Shielding

The configuration of this table enables you to specify the CRBT service in certain office
directions and identify the signaling transferred between the load sharing SGs.
Command
ADD SERGTNUMRNG
Parameter
r ID r Name
EQPTYP Equipmen When it is set to SG, it indicates that the signaling is transferred
E t type from the load sharing SG.
When it is set to MSC, it specifies the MSC in the network used to
realize the CRBT service in the end office mode. The number range
to be shielded must be determined by this parameter and the user
number range shielding table.
STARTG Start GT The parameters specify the GT number range to be shielded.

T number
ENDGT End GT
number
Related Commands
Table 5-11 Related commands for configuring the RBT GT number range
Command Function
ADD SERGTNUMRNG To add RBT GT number range
MOD SERGTNUMRNG To modify RBT GT number range
RMV SERGTNUMRNG To delete RBT GT number range
LST SERGTNUMRNG To query RBT GT number range

5.5.2 Configuring CRBT User Number Range Shielding

This operation shields the HLR number range used in the end office mode. You can determine
the CRBT user in the end office mode though user number range shielding and the GT number
range shielding table of the CRBT.
Command
ADD SERUSRNUMRNG
Parameter
r ID r Name
STARTN Start user The parameters specify the user number range to be shielded.
UM number
ENDNU End user

M number
Related Commands
Table 5-12 Related commands for configuring the CRBT user number range
Command Function
ADD SERUSRNUMRNG To add RBT user number range
MOD SERUSRNUMRNG To modify RBT user number range
RMV SERUSRNUMRNG To delete RBT user number range
LST SERUSRNUMRNG To query RBT user number range

This section provides examples to describe how to configure the CRBT service data.
The networking structure for configuring the CRBT service data is as shown in Figure 5-1.
Data Collection
The data collected for configuring the CRBT service is as listed in Table 5-13.


GSM 13798585850 13798585860 1350000
Local CDMA GT GSM prefix number CDMA prefix GSM virtual

number number roaming number
index out of
province
- 9 - -
CDMA virtual GSM virtual roaming If GSM support If CDMA support

roaming number number index for rambling RBT rambling RBT
index out of international
province roaming
- - - -
Resource board Resource time out Whether trigger Resource board

PMC number RBT when the PMC number
following msg has Resource time out
original called Whether trigger
number RBT when the
following msg has
original called
number Whether
support checking
for available relay
2 60 Not support Support
RBT system Country Code Wait for number The time waiting for
parameters or not number
- - Not collect number -
Start GT number End GT number RBT realizing Virtual roaming

mode number index
- - - -
Start user logic End user logic Main AIP point Standby AIP point
number number code index code index
13798585859 13798585860 6 -
MSISDN Whether support

RBT when roaming
out of province
13798585859 No

Procedure
Step 1 Adding the virtual roaming number.
To add the virtual roaming number, set If support GSM and CDMA to GSM, Start dummy
ramble number to 13798585850, and End dummy ramble number to 13798585860, run the
following command:
ADD CRVMSRN: GSMCDMA=GSM-1, SVMSRN="13798585850", EVMSRN="13798585860";
Step 2 Set the CRBT software parameters.
To set the CRBT software parameters, set Local GSM GT number to 1350000, GSM prefix
number to 9, and Resource board PMC number to 2, run the following command:
SET CRSOFTCFG: LGGT="1350000", GPRE="9", RBDPMC=2, SRCTOUT=60,
ISENCR=UNSUPPORT, ENCRCRL=SUPPORT, WAITINGNUM=NOTWAITING;
NOTE
In this example, only the basic function of the local GSM network of the CRBT service is configured.
Step 3 Add the user number range.
To add the user number range, set Start user logic number to 13798585859, End user logic
number to 13798585860, and Main AIP point code index to 6, run the following command:
ADD SERUSERNG: SUMSISDN="13798585859", EUMSISDN="13798585860", MSTAIPSP=6;
Step 4 Add the CRBT service user data.
To add the CRBT service user data, set MSISDN to 13798585859, and Whether enable related
services to Enable RBT service, run the following command:
ADD SERUATTR: USRNUM="13798585859", SERVATTR=OCR-1;
----End
Verifying the Virtual Roaming Number

This step must be performed after you set the virtual roaming number. To verify the virtual
roaming number, run LST CRVMSRN on the MML client.
LST CRVMSRN:;

dummy ramble number table
-------------------------
index = 0
description = <ULL>
if support GSM and CDMA = GSM<YES>, CDMA<NO>
start dummy ramble number = 13798585850
end dummy ramble number = 13798585860
--- END
In the displayed result, If support GSM and CDMA is GSM, Start dummy ramble
number is 13798585850, and End dummy ramble number is 13798585860. The results are
the same as the configured data through the command, which indicates that the configuration is
successful.

Verifying the CRBT Software Parameters

This step must be performed after you set the CRBT software parameters. To verify the CRBT
software parameters, run LST CRSOFTCFG on the MML client.
LST CRSOFTCFG:;

RBT soft configuration table
----------------------------
local GSM GT number =
1350000
local CDMA GT number =
0
GSM prefix number =
9
CDMA prefix number =
0
GSM virtual roaming number index out of province =
65535
GSM virtual roaming number index for international roaming =
0
CDMA virtual roaming number index out of province =
65535
if GSM support rambling RBT =
G_5<OFF>G_4<ON>G_3<OFF>G_2<ON>G_1<ON>
if CDMA support rambling RBT =
G_4<ON>G_3<OFF>G_2<ON>G_1<ON>
resource board PMC number =
2
resource time out =
60
Whether trigger RBT when the following msg has original called number =
Unsupport
Whether support checking for available relay =
Support
RBT system parameters =
PARAMETER2
Country Code =
0086
Wait for number or not =
NotWaiting
The time waiting for number =
4
--- END
In the displayed result, Local GSM GT number is 1350000, GSM prefix number is 9,
Resource board PMC number is 2, and the values of other parameters are the default values.
Verifying the User Number Range

This step must be performed after you set the user number range. To verify the user number
range, run LST SERUSERNG on the MML client.
LST SERUSERNG: MODE=IDX, IDX=0;

RBT user range table

--------------------
index = 0
description = <NULL>
start user logic number = 13798585859
end user logic number = 13798585860
main AIP point code index = 6
standby AIP point code index = 65535
--- END
In the displayed result, Start user logic number is 13798585859, End user logic number is
13798585860, and Main AIP point code index is 6. The results are the same as the configured
data through the command, which indicates that the configuration is successful.
Verifying the CRBT Service User Data

This step must be performed after you set the CRBT service user data. To verify the CRBT
service user data, run LST SERUATTR on the MML client.
LST SERUATTR: MODE=IDX, IDX=32;

Service user number segment table
---------------------------------
Index = 32
Description = <NULL>
MSISDN = 13798585859
User IMSI number = 0
Whether enable Related services =
G_6<OFF>G_5<OFF>G_4<OFF>G_3<OFF>G_2<OFF>G_1<ON>
Whether support RBT when roaming out of province = Unsupport
Number type = In local network
Route index type = HLR number index
HLR address index = 65535
Routing Number Index = 65535
MC routing index = 255
Filter time segment index = 255
--- END
In the displayed result, MSISDN is 13798585859, and Whether enable related services is
Enable RBT service. The results are the same as the configured data through the command,
which indicates that the configuration is successful.

Feature Description 6 Configuring B&W Lists and Number Change Service Data
6 Configuring B&W Lists and Number

Change Service Data
About This Chapter
The black & white lists (hereinafter referred to as B&W lists) service is a call control function
based on the calling and called numbers. The number change service is used to change the
subscriber numbers in the IAM according to the principle of subscriber numbers and data
configuration. The B&W lists and number change data must be configured only after configuring
the hardware data and the MTP data.
6.1 B&W Lists and Number Change Service
Network operators must restrict the services of some subscribers, for example, to control the
outgoing and incoming calls of some subscribers in different time segments. In this case, the
B&W lists service can be adopted.
6.2 Service Flow
This section describes the networking structure for the B&W lists service and the implementation
Configuring the B&W lists and number change service includes configuring the MTP link set,
local number range table, and virtual number table.
This section provides examples to describe how to configure the B&W lists and number change
service data.

6 Configuring B&W Lists and Number Change Service Data Feature Description
6.1 B&W Lists and Number Change Service

Network operators must restrict the services of some subscribers, for example, to control the
outgoing and incoming calls of some subscribers in different time segments. In this case, the
B&W lists service can be adopted.
During call connection and charging, the special charging and other services are enabled based
on the calling and called numbers. For example, through the calling number change of
subscribers, the charging can be imposed on only one subscriber. With the called number change
in different time segment, the call of a subscriber can be connected to the phone set in the office
during work, and connected to the subscriber's mobile phone after work.
In addition, the system provides calling party category (CPC) change and ISUP anti-fraud
function.
l By replacing the CPC field, the special charging and other services can be enabled.
l With the ISUP anti-fraud function, after replacing the calling number in the IAM (in which
the calling and called numbers are not in the local network) with a specific number, the
message can be further processed.
This service, however, is not universal. The configuration method must be determined by the
actual requirements of the network.
6.2 Service Flow

This section describes the networking structure for the B&W lists service and the implementation
This section describes the networking structure for configuring the B&W lists service data.
This section describes the implementation of the B&W lists service on the SG.

This section describes the networking structure for configuring the B&W lists service data.
Figure 6-1 shows the networking structure for the B&W lists and number change service.

Figure 6-1 Networking for the B&W lists and number change service
SG: U-SYS SG7000 Signaling Gateway
In the networking structure, the SG works as the signaling transfer point (STP) and provides the
B&W lists and number change service.

This section describes the implementation of the B&W lists service on the SG.
Figure 6-2 shows the flow of the B&W lists and number change service.

Figure 6-2 Flow of the B&W lists and number change service
Message
receiving
No Is the switch of No Is the switch of No

Is the switch of
black & white lists number change
ISUP anti-fraud
switched on? switched on?
switched on?
Yes
Yes Yes
Yes Calling black & Calling number

Are calling and white lists operation change
called numbers in
the network?
No
Called black & Called number
white lists operation change
ISUP anti-fraud
operation
CPC change
Message
sending
The service flow is described in the following steps:

1. Checking whether the ISUP anti-fraud function is enabled
The system determines whether the ISUP anti-fraud function of the link set is enabled. If
the ISUP anti-fraud function is enabled, the system performs the ISUP anti-fraud function
analysis; otherwise, the system determines whether the B&W lists switch is switched on.
2. Determining whether the calling and called numbers in the IAM are in the network
The system extracts the calling and called numbers in the IAM. If the numbers are not in
the network, the system performs the calling number change; otherwise, the system
determines whether the B&W lists switch is switched on.
3. Performing the ISUP anti-fraud operation
The system finds the corresponding dummy number based on the source destination
signaling point (DSP) in the IAM. It then replaces the calling number in the message with
a dummy number. If the corresponding dummy number of the source DSP cannot be found,
the system performs the next step.
4. Checking whether the B&W lists switch is switched on
The system determines whether the B&W lists switch of the link set is switched on. If yes,
the system performs the B&W lists analysis on the calling number; otherwise, the system
performs the ISUP anti-fraud operation.
5. Performing B&W lists operation on the calling number

The system extracts the calling number from the IAM and compares it with the calling
restriction conditions. The system shields the message complying with the conditions and
returns an REL message.
If the message cannot be shielded, the system sends the messages to the B&W lists of the
called number for processing.
6. Performing B&W lists operation on the called number
The system extracts the called number in the IAM and compares it with the calling
restriction conditions. The system shields the message complying with the conditions and
returns an REL message.
If the message cannot be shielded, the system determines whether the number change switch
of the link set is switched on.
7. Checking whether the number change switch is switched on
The system determines whether the number change switch of the link set is switched on.
If the number change switch is switched on, the system performs the calling number change
analysis; otherwise, the system sends the message directly.
8. Performing calling number change
The system extracts the calling number in the IAM and compares it with the calling
restriction conditions. The system performs the number change on the message complying
with the restriction conditions and sends the message.
If the calling number change cannot be performed, the system sends the message to the
called number change for processing.
9. Performing called number change
The system extracts the called number in the IAM and compares it with the calling
restriction conditions. The system performs number change on the message complying with
the restriction conditions and sends the message.
If the called number change cannot be performed, the system sends the message to the CPC
change for processing.
10. Performing CPC change
The system extracts the CPC and DSP in the IAM and compares it with the calling
restriction conditions. The system modifies the CPC in the message complying with the
restriction conditions and sends the message. If the called number change cannot be
performed, the system sends the message to the CPC change for processing. If the CPC
change cannot be performed, the system sends the message directly.

6.3.1 Terms
This section describes the terms used during configuring the B&W service data.
You must follow certain principles to configure the B&W lists service data.
This section describes the relations between data tables related to B&W service data
configuration.

Before configuring the B&W service, you must collect the data including the DSP index, local
SP index, and virtual number.
6.3.5 General Steps
You must follow certain procedures to configure the B&W lists service data.
6.3.1 Terms
This section describes the terms used during configuring the B&W service data.
Black and White Lists

The system stops the call message from being sent based on conditions, such as the calling and
called numbers, office direction, and time contained in the IAM. It then returns a specified REL
message to enable the call restriction function.
Number Change
The system changes the calling and called numbers in the call based on conditions, such as the
calling and called numbers, office direction, and time contained in the IAM to enable the special
charging and other services.
CPC Change
The system replaces the CPC field based on conditions, such as the CPC field and time contained
in the IAM to enable the special charging and other services.
ISUP Anti-Fraud Function

If the calling and called numbers contained in the IAM are not in the network, the system replaces
the calling number in the message with a dummy number to enable the special charging and
other services.

You must follow certain principles to configure the B&W lists service data.
Configuration Contents
The configuration of the B&W lists and number change service is classified into the following:
l Configuring the service process switch of the link set

l Configuring the ISUP anti-fraud function
l Configuring the B&W lists
l Configuring the number change
l Configuring the CPC change
NOTE
The service process switch of the link set is enabled only when the assemble switch of the B&W lists and
number change is switched on. The assemble switch of the B&W lists and number change is controlled by
the License file.

Configuring Service Process Switch of the Link Set

Set the service process switch of the link set to configure the B&W lists and number change
switches.
The operation sequence of the ISUP anti-fraud function, B&W lists, number change, and CPC
change is as follows:
l The ISUP anti-fraud function, B&W lists, and number change are independent of each
other. They can be controlled by the switches in the commands ADD N7LKS and ADD
M3ASSOS. The CPC change function is a part of the number change function, both
controlled by one switch.
l The service processing is performed in the following sequence: ISUP anti-fraud function,
B&W lists, and number change.
l When performing the number change and CPC change, the system changes the numbers
in the messages complying with the number change conditions. After that, the system
performs the CPC change to the messages complying with the CPC change conditions but
not with the number change conditions.
Configuring ISUP Anti-Fraud Function

The configuration of the ISUP anti-fraud function includes the configuration of the network
number segment table and dummy number table.
l The network number segment table lists the configuration of all the number segments in
the network. It is used to determine whether the calling and called numbers are in the
network.
l The dummy number management table lists the mapping between the source DSP and the
dummy number. It is used to replace the calling number.
Configuring B&W Lists

The configuration of the B&W lists includes the configuration of the DSP reference index,
calling B&W lists parameter, and called B&W lists parameter.
l The configuration of the DSP reference index provides a reference index for the DSPs
performed with the same operation. The DSP index is also used in number change
configuration.
l The configuration of the calling B&W lists is used to restrict the call of the calling number
and return the specified REL message. The parameters to be configured include: Calling
screen function, Calling number, Calling number length, Index of DSP reference, Time
type, Start time, End time, and Cause of REL message.
The configuration of the called B&W lists is similar to that of the calling B&W lists.
If the calling B&W lists function is performed on a message, the called B&W lists function
cannot be performed on the message again. If the B&W lists function is performed on the
signaling, the number change or CPC change cannot be performed on the signaling.
Configuring Number Change

The configuration of the number change is to change the calling and called numbers in the
message complying with the restriction conditions, including: configuring number operation
strategy, configuring calling number change, and configuring called number change.

l The configuration of number operation strategy includes deleting and adding the calling
and called number. When adding and deleting the numbers, the higher digits of the calling/
called number are deleted in descending order. The number to be added is then added to
the position of the higher digits in the number.
l The parameters for configuring the calling number change include: Calling transform
number function, Calling number, Calling number length, Index of DSP reference, CPC
configuration, Time type, Start time, End time, and Index of number operation table.
l The configuration of the called number change is similar to that of the calling number
change.
If a message is performed with the calling number change operation, it cannot be performed
with the called number change operation; the signaling performed with the calling number
change or called number change cannot be performed with the CPC change.
Configuring CPC Change

Set the number change to perform the CPC change on the signaling complying with the
restriction conditions.
If the IAM is not performed with the calling and called number change but it complies with the
CPC change restriction function, then the IAM on the link set that enables the number change
function is performed with the CPC change.

This section describes the relations between data tables related to B&W service data
configuration.
Mapping Between Data Tables for B&W Lists and Number Change
Figure 6-3 shows the relation between data tables for B&W lists and number change.

Figure 6-3 Relation between data tables for B&W lists and number change
Reference Relation Between Data of B&W Lists and Number Change and Other
Data
The data of B&W lists and number change references the DSP index in the MTP data. The DSP
index reference and dummy number table references the index number of ADD N7DSP.

Before configuring the B&W service, you must collect the data including the DSP index, local
SP index, and virtual number.
Table 6-1 lists the information to be collected for configuring the B&W lists and number change
data.


Service process DSP index Local SP index Index of DSP
switch reference
Start number End number range DSP index Dummy number

range
Calling screen Calling number Calling number Index of DSP

function length reference of calling
black & white lists
CPC Calling number of Calling number Index of DSP

configuration of calling black & length of calling black reference of calling
calling black & white lists & white lists black & white lists
white lists
Time type of Start time of End time of calling Cause of REL

calling black & calling black & black & white lists message of calling
white lists white lists black & white lists
Called screen Called number Called number length Index of DSP

function reference of called
black & white lists
CPC Calling number of Called number length Index of DSP

configuration called black & of called black & white reference of called
white lists lists black & white lists
Time type of Start time of called End time of called Cause of REL
called black & black & white lists black & white lists message of called
white lists black & white lists
Length of Whether append The calling number -

Deleted Calling calling number or being added
number not
Length of Whether append The called number -

Deleted called called number or being added
number not


switch reference
Calling trans Calling number of Calling number Index of DSP

number function calling trans length of calling trans reference of calling
number function number function trans number
function
CPC Time type of Start time of calling End time of calling

configuration of calling trans trans number trans number
calling trans number function function function
number function
Number change - - -
operation
strategy index of
calling trans
number function
Called trans Calling number of Calling number Index of DSP

number function called trans length of called trans reference of called
function
CPC Time type of called Start time of called End time of called
configuration of trans number trans number trans number
called trans function function function
number function
Number change - - -
operation
strategy index of
called trans
number function
CPC modifying original CPC Time type of CPC Start time of CPC
function change change
End time of CPC Changed CPC - -

change


switch reference
6.3.5 General Steps

You must follow certain procedures to configure the B&W lists service data.
Table 6-2 lists the steps for configuring the data of the B&W lists and number change service.
Step 3 and step 4 are for the B&W lists function. Step 5 to step 8 are for the number change
function. You can configure the two services based on whether the service process switch in
step 1 is switched on. There is no specific order for the configuration of the two services.
Table 6-2 Steps for configuring the data of the B&W lists and number change
Step Operation
1 To add the MTP link set
2 To add the operator number range table
3 To add the dummy number table
4 To add the DSP index reference
5 To add the calling B&W list
6 To add the Called B&W list
7 To add the number operation
8 To add the calling number transform
9 To add the called number transform
10 To add the CPC

Configuring the B&W lists and number change service includes configuring the MTP link set,
local number range table, and virtual number table.
6.4.1 Adding MTP Link Set
This section describes the command, parameter, and related commands for adding the MTP link
set.
6.4.2 Adding Operator Number Range Table
This section describes the command, parameter, and related commands for adding the operator
number range table.
6.4.3 Adding Dummy Number Table

This section describes the command, parameter, and related commands for adding the dummy
number table.
6.4.4 Adding DSP Index Reference
This section describes the command, parameter, and related commands for adding the DSP index
reference.
6.4.5 Adding Calling B&W List
This section describes the command, parameter, and related commands for configuring the IUA
data.
6.4.6 Adding Called B&W List
data.
6.4.7 Adding Number Operation
This section describes the command, parameter, and related commands for adding the number
operation.
6.4.8 Adding Calling Number Transform
This section describes the command, parameter, and related commands for adding the calling
number transform.
6.4.9 Adding Called Number Transform
This section describes the command, parameter, and related commands for adding the called
number transform.
6.4.10 Adding CPC
This section describes the command, parameter, and related commands for adding the CPC.
6.4.1 Adding MTP Link Set

This section describes the command, parameter, and related commands for adding the MTP link
set.
Command
ADD N7LKS
Parameter
r ID r Name
SRVPRO Service It specifies whether to perform B&W lists and number change
SWT process operations to the link set.
switch

Related Commands
Table 6-3 Related commands for configuring the MTP link set
Command Function
ADD N7LKS To add the MTP link set
MOD N7LKS To modify the MTP link set
RMV N7LKS To delete the MTP link set
LST N7LKS To query the MTP link set
6.4.2 Adding Operator Number Range Table

This section describes the command, parameter, and related commands for adding the operator
number range table.
Command
ADD LNUMRNG
Parameter
r ID r Name
NUMS Start The two parameters specify the number segment of the network.
number
range
NUME End
number
range
Related Commands
Table 6-4 Related commands for configuring the operator number range table
Command Function
ADD LNUMRNG To add operator number range table
MOD LNUMRNG To modify operator number range table
RMV LNUMRNG To delete operator number range table
LST LNUMRNG To query operator number range table

6.4.3 Adding Dummy Number Table

This section describes the command, parameter, and related commands for adding the dummy
number table.
Command
ADD ISUPDUMMYNUM
Parameter
r ID r Name
DIDX DSP index It corresponds to the source DSP in the IAM and determines
whether to replace the calling number.
DNUM Dummy It replaces the calling number in the IAM if the source DSP in the
number IAM is the same with the DSP configured in this table.
Related Commands
Table 6-5 Related Commands for configuring the dummy number table
Command Function
ADD ISUPDUMMYNUM To add dummy number table
MOD ISUPDUMMYNUM To modify dummy number table
RMV ISUPDUMMYNUM To delete dummy number table
LST ISUPDUMMYNUM To query dummy number table
6.4.4 Adding DSP Index Reference

This section describes the command, parameter, and related commands for adding the DSP index
reference.
Command
ADD DSPIDXREF

Parameter
r ID r Name
REFIDX Index of It specifies the DSP reference index corresponding to the DSP. The
DSP same DSP reference index can be allocated to the DSPs with the
reference same operations.
DSPIDX DSP index It specifies the DSP index configured on the equipment. One DSP
can be configured with multiple DSP reference indexes.
Related Commands
Table 6-6 Related commands for configuring the DSP index reference
Command Function
ADD DSPIDXREF To add DSP index reference
MOD DSPIDXREF To modify DSP index reference
RMV DSPIDXREF To delete DSP index reference
LST DSPIDXREF To query DSP index reference
6.4.5 Adding Calling B&W List

data.
Command
ADD CALLINGBW
Parameter
r ID r Name
FUNCSW Calling It indicates whether to open this configuration record.

screen
function
CALGNU Calling It specifies the calling number segment in the calling B&W lists
M number operation. The calling B&W lists operation is performed only
when the parameter is the same with calling number segment in
the IAM.
NOTE
The number must contain a minimum of three BCD codes.


r ID r Name
CALLGL Calling It specifies the requirement on the length of the calling number in
EN number the message. The calling B&W lists operation is performed only
length when the required length is met.
REFDSP Index of It specifies the DSP reference index corresponding to the B&W
DSP lists. The calling B&W lists operation is performed only when the
reference DSP in the IAM is corresponds to the DSP reference index. It
corresponds to DSP reference index set in the management of the
DSP reference index.
TIMETY Time type These parameters specify the time for the calling B&W lists
PE operation. The calling B&W lists operation is performed to the
messages only during the configuration time.
STIME Start time
The time type can be cyclic or continuous.
ETIME End time If the time type is cyclic, the duration lasts from the start day to the
end day. The durations from the start time to end time in each day
are discontinuous.
If the time type is continuous, the duration lasts from the start time
in the start day to the end time in the end day.
RELCAU Cause of It specifies the REL message type returned after message
REL interruption.
message
Related Commands
Table 6-7 Related commands for configuring the calling B&W list
Command Function
ADD CALLINGBW To add calling B&W list
MOD CALLINGBW To modify calling B&W list
RMV CALLINGBW To delete calling B&W list
LST CALLINGBW To query calling B&W list
6.4.6 Adding Called B&W List

data.
Command
ADD CALLINGBW

Parameter
The parameters are similar to those in the management of calling B&W lists. For details, see
6.4.5 Adding Calling B&W List.
Related Commands
Table 6-8 Related commands for configuring the called B&W list
Command Function
ADD CALLEDBW To add Called B&W list
MOD CALLEDBW To modify Called B&W list
RMV CALLEDBW To delete Called B&W list
LST CALLEDBW To query Called B&W list
6.4.7 Adding Number Operation

This section describes the command, parameter, and related commands for adding the number
operation.
Command
ADD NUMOPER
Parameter
r ID r Name
DCGLEN Length of It specifies the first four digits of the deleted calling number.
Deleted
Calling
number
ACGNU Whether The parameters specify whether to append the calling number.
M append The first four digits of the calling number in the message are
calling deleted first, and then the new calling number is appended to the
number or first four digits.
not
Assume that the calling number in the original message is
CGNUM the calling 123456789. If the number of digits deleted is four, and the calling
number number to be added is 987, then the operation is as follows:
being 1. Delete the first four digits of the calling number. The calling
added number changes from 123456789 to 56789.
2. Add the calling number 987 to the higher digits of the converted
number. The calling number changes from 56789 to 98756789.


r ID r Name
DCDLEN Length of These parameters are similar to those of the calling number.
deleted
called
number
ACDNU whether
M append
called
number or
not
CDNUM the called

number
being
added
Related Commands
Table 6-9 Related commands for configuring the number operation

Command Function
ADD NUMOPER To add number operation
MOD NUMOPER To modify number operation
RMV NUMOPER To delete number operation
LST NUMOPER To query number operation
6.4.8 Adding Calling Number Transform

This section describes the command, parameter, and related commands for adding the calling
number transform.
Command
ADD CALLINGTN

Parameter
r ID r Name
FUNCSW Calling It specifies whether to open this configuration record.

trans
number
function
CALGNU Calling It specifies the calling number segment in the calling number
M number change operation. The calling number change operation is
performed only when the parameter is the same with the calling
number segment in the IAM.
NOTE
The number must contain a minimum of three BCD codes.
CALLGL Calling It specifies the requirement on the length of the calling number in
EN number the message. The operation is performed only when the length
length meets the requirement.
REFDSP Index of It specifies the DSP reference index corresponding to the calling
DSP number change. The calling number change operation is performed
reference only when the DSP in the IAM corresponds to the DSP reference
index.
CPC CPC It specifies the requirements on the CPC in the message. The
configurat calling number change operation is performed only when the CPC
ion in the message is identical to the set one. This parameter is optional.
If it is set to 255, it means the CPC value is not concerned.
TIMETY Time type These parameters specify the time for the calling number change
PE operation. The calling number change operation is performed to
the messages only in the configuration time.
STIME Start time
The time type can be cyclic or continuous.
are discontinuous.
IDXNUM Index of It specifies the number operation strategy for the messages meeting
OP number the conditions. It corresponds to the record index in the
operation management of number operation strategy.
table

Related Commands
Table 6-10 Related commands for configuring the calling number transform
Command Function
ADD CALLINGTN To add calling number trans
MOD CALLINGTN To modify calling number trans
RMV CALLINGTN To delete calling number trans
LST CALLINGTN To query calling number trans
6.4.9 Adding Called Number Transform

This section describes the command, parameter, and related commands for adding the called
number transform.
Command
ADD CALLEDTN
Parameter
The parameters are similar to those in the management of calling number change. For details,
see 6.4.8 Adding Calling Number Transform.
Related Commands
Table 6-11 Related commands for configuring the called number transform
Command Function
ADD CALLEDTN To add called number trans
MOD CALLEDTN To modify called number trans
RMV CALLEDTN To delete called number trans
LST CALLEDTN To query called number trans
6.4.10 Adding CPC

This section describes the command, parameter, and related commands for adding the CPC.
Command
ADD CPC

Parameter
r ID r Name
CPCSW CPC It specifies whether to open this configuration record.

modifying
function
ORIGCP Original It specifies the value of the CPC to which the CPC change is
C CPC performed. The CPC change is performed only when the CPC in
the message is identical to the original one.
REFDSP Index of It specifies the DSP reference index corresponding to the DSP. The
DSP CPC change operation is performed only when the DSP in the IAM
reference corresponds to the DSP reference index.
TIMETY Time type These parameters specify the time for the CPC change operation.
PE The CPC change operation is performed to the messages only in
the configuration time.
STIME Start time
The time type can be cyclic type or continuous type.
are discontinuous.
CHGEDC Changed For the message that meets the conditions, its CPC is changed to
PC CPC the value of this parameter.
Related Commands
Table 6-12 Related commands for configuring the CPC

Command Function
ADD CPC To add CPC
MOD CPC To modify CPC
RMV CPC To delete CPC
LST CPC To query CPC

This section provides examples to describe how to configure the B&W lists and number change
service data.

The networking structure for configuring the B&W lists and number change service is as shown
in Figure 6-1.
Data Collection
The data collected for configuring the B&W lists and number change service is as listed in Table
6-13.

switch reference
Enable BW 1 0 11
switch and
Number switch
Start number End number range DSP index Dummy number

range
21980000 21981000 1 250250250
Calling screen Calling number Calling number Index of DSP

function length reference of calling
black & white lists
Open 21980082 8 11
Time type of Start time of End time of calling Cause of REL

calling black & calling black & black & white lists message of calling
white lists white lists black & white lists
Continuous 2006-01-01-08:00: 2009-01-01-08:00:00 Default value

00
Called screen Called number Called number length Index of DSP

function reference of called
black & white lists
Open 21980082 8 11
Time type of Start time of called End time of called Cause of REL
called black & black & white lists black & white lists message of called
white lists black & white lists
Segment 2006-01-01-00:00: 2009-01-01-08:00:00 Default value

00
Length of Whether append The calling number -

Deleted Calling calling number or being added
number not
3 Not add Not add


switch reference
Length of Whether append The called number -

Deleted called called number or being added
number not
4 Not add Not add
Calling trans Calling number of Calling number Index of DSP

number function calling trans length of calling trans reference of calling
function
Open 21980090 8 11
CPC Time type of Start time of calling End time of calling

configuration of calling trans trans number trans number
calling trans number function function function
number function
Default value Continuous 2006-01-01-00:00:00 2009-01-01-00:00:00
Number change - - -
operation
strategy index of
calling trans
number function
Called trans Calling number of Calling number Index of DSP

number function called trans length of called trans reference of called
function
Open 21980080 8 11
CPC Time type of called Start time of called End time of called
configuration of trans number trans number trans number
called trans function function function
number function
Default value Continuous 2006-01-01-00:00:00 2009-01-01-00:00:00
Number change - - -
operation
strategy index of
called trans
number function
CPC modifying original CPC Time type of CPC Start time of CPC
function change change
Open Default value Segment 2006-01-01-08:00:00


switch reference
End time of CPC Changed CPC - -

change
2006-01-01-16:00 245
:00
Procedure
Step 1 Add the MTP link set.
To add the MTP link set, set Adjacent SP index to 1, Local SP index to 0, Network
indication to National, and Service process switch to BW switch and Number change, run
ADD N7LKS: APX=1, OFX=0, NI=NM, SRVPROSWT=BW-1&NS-1;
Step 2 Add the local network number range.
To add the local network number range, set Start number range to 21980000 and End number
range to 21981000, run the following command:
ADD LNUMRNG: NUMS="21980000", NUME="21981000";
Step 3 Add the dummy number table.
To add the dummy number table, set DSP index to 1, and Dummy number to 250250250, run
ADD ISUPDUMMYNUM: DIDX=1, DNUM="250250250";
Step 4 Add the DSP index reference.
To add the DSP index reference, set Index of DSP reference to 11, and DSP index to 1, run
ADD DSPIDXREF: REFIDX=11, DSPIDX=1;
Step 5 Add the calling B&W list.
To add the calling B&W list, set Calling screen function to Open, Calling number to
21980082, Calling number length to 10, Index of DSP reference to 11, Time type to
Continuous, Start time to 2006-01-01-08:00:00, and End time to 2009-01-01-08:00:00, run
ADD CALLINGBW: FUNCSW=OPEN, CALGNUM="21980082", CALLGLEN=10, REFDSP=11,
TIMETYPE=CYCLE, STIME="2006&01&01&08&00&00", ETIME="2009&01&01&08&00&00";
Step 6 Add the called B&W list.
To add the called B&W list, set Called screen function to Open, Called number to
21980082, Called number length to 10, Index of DSP reference to 11, Time type to
Segment, Start time to 2006-01-01-00:00:00, and End time to 2009-01-01-06:00:00, run the
following command:

ADD CALLEDBW: FUNCSW=OPEN, CALGNUM="21980082", CALLGLEN=10, REFDSP=11,

TIMETYPE=CYCLE, STIME="2006&01&01&00&00&00", ETIME="2009&01&01&06&00&00";
Step 7 Add the number operation policy.

To add the number operation policy, set Length of Deleted Calling number to 3, and Length
of Deleted Called number to 4, run the following command:
ADD NUMOPER: DCGLEN=3, ACGNUM=NOADD, DCDLEN=4;
Step 8 Add the calling number transform.

To add the calling number transform, set Calling trans number function to Open, Calling
number to 21980090, Calling number length to 10, Index of DSP reference to 11, Time
type to Continuous, Start time to 2006-01-01-00:00:00, End time to 2009-01-01-00:00:00,
and Index of number operation table to 0, run the following command:
ADD CALLINGTN: FUNCSW=OPEN, CALGNUM="21980090", CALLGLEN=10, REFDSP=11,
TIMETYPE=CYCLE, STIME="2006&01&01&00&00&00",
ETIME="2009&01&01&00&00&00", IDXNUMOP=0;
Step 9 Add the called number transform.

To add the called number transform, set Called trans number function to Open, Called
number to 21980080, Called number length to 10, Index of DSP reference to 11, Time
type to Continuous, Start time to 2006-01-01-00:00:00, End time to 2009-01-01-00:00:00,
and Index of number operation table to 0, run the following command:
ADD CALLEDTN: FUNCSW=OPEN, CALGNUM="21980080", CALLGLEN=10, REFDSP=11,
TIMETYPE=CYCLE, STIME="2006&01&01&00&00&00",
ETIME="2009&01&01&00&00&00", IDXNUMOP=0;
Step 10 Add the CPC management.

To add the CPC management, set CPC modifying function to Open, Original CPC to 2, Index
of DSP reference to 1, Time type to Segment, Start time to 2006-01-01-08:00:00, End
time to 2009-01-01-16:00:00, and Changed CPC to 245, run the following command:
ADD CPC: CPCSW=OPEN, REFDSP=11, TIMETYPE=CYCLE,
STIME="2006&01&01&08&00&00", ETIME="2009&01&01&16&00&00", CHGEDCPC=245;
----End
Verifying the MTP Link Set

This step must be performed after you set the MTP link set. To verify the MTP link set, run
LST N7LKS on the MML client.
LST N7LKS:;

The MTP Link set
----------------
Link set index = 3
Link set title = <NULL>
Adjacent SP index = 1
Link selection field = 0
Alarm threshold index = 0
Incoming shielding table index = 65535
Outgoing shielding table index = 65535
Timer index = 0

Congestion threshold index = 0

Start link set index = 65535
End link set index = 65535
Local SP index = 0
Network indication = National
Start association set index = 65535
End association set index = 65535
masking function = off
masking reference = 65535
default masking reference = 65535
Service process switch = G_4<OFF>G_3<OFF>G_2<ON>G_1<ON>
Reroute policy = All DPC not processed
Type of next reroute table = Void
Next reroute reference = 65535
--- END
Verifying the Local Network Number Range

This step must be performed after you set the local network number range. To verify the local
network number range, run LST LNUMRNG on the MML client.
LST LNUMRNG:;

operator number range table
---------------------------
Index = 0
Start number range = 21980000
End number range = 21980010
--- END
In the displayed result, Start number range is 21980000 and End number range is
21981000. The results are the same as the configured data through the command, which indicates
that the configuration is successful.
Verifying the Dummy Number Table

This step must be performed after you set the dummy number table. To verify the dummy number
table, run LST ISUPDUMMYNUM on the MML client.
LST ISUPDUMMYNUM:;

Dummy number table
------------------
Index = 0
DPC index = 1
Dummy number = 250250250
--- END

In the displayed result, DSP index is 1, and Dummy number is 250250250. The results are the
same as the configured data through the command, which indicates that the configuration is
successful.
Verifying the DSP Index Reference

This step must be performed after you set the DSP index reference. To verify the DSP index
reference, run LST DSPIDXREF on the MML client.
LST DSPIDXREF:;

DSP index reference table
-------------------------
Index = 0
Index of DSP reference = 11
DSP index = 1
--- END
In the displayed result, Index of DSP reference is 11, and DSP index is 1. The results are the
successful.
Verifying the Calling B&W List

This step must be performed after you set the calling B&W list. To verify the calling B&W list,
run LST CALLINGBW on the MML client.
LST CALLINGBW:;

Calling B&W table
-----------------
Index = 0
Calling screen function = Open
Calling number = 21980082
Calling number length = 10
Time type = Continuous
Start time = 2006&01&01&08&00&00
End time = 2009&01&01&08&00&00
Cause of REL message = 0-UNKNOWN
--- END
In the displayed result, Calling screen function is Open, Calling number is 21980082, Calling
number length is 10, Index of DSP reference is 11, Time type is Continuous, Start time is
2006-01-01-08:00:00, End time is 2009-01-01-08:00:00, and the values of other parameters
are default values. The results are the same as the configured data through the command, which
Verifying the Called B&W List

This step must be performed after you set the called B&W list. To verify the called B&W list,
run LST CALLEDBW on the MML client.

LST CALLEDBW:;

Called B&W table
----------------
Index = 0
Called screen function = Open
Called number = 21980082
Called number length = 10
Time type = Cycle
Start time = 2006&01&01&00&00&00
End time = 2009&01&01&06&00&00
Cause of REL message = 0-UNKNOWN
--- END
In the displayed result, Called screen function is Open, Called number is 21980082, Called
number length is 10, Index of DSP reference is 11, Time type is Segment, Start time is
2006-01-01-00:00:00, End time is 2009-01-01-06:00:00, and the values of other parameters
are default values. The results are the same as the configured data through the command, which
Verifying the Number Operation Policy

This step must be performed after you set the number operation policy. To verify the number
operation policy, run LST NUMOPER on the MML client.
LST NUMOPER:;

Number operation table
----------------------
Index = 0
Length of Deleted Calling number = 3
Whether append calling number or not = Not append
The calling number being added = <NULL>
Length of Deleted called number = 4
Whether append called number or not = Not append
The called number being added = <NULL>
--- END
In the displayed result, Length of Deleted Calling number is 3, Length of Deleted Called
number is 4, and other parameters are not configured. The results are the same as the configured
Verifying the Calling Number Transform

This step must be performed after you set the calling number transform. To verify the calling
number transform, run LST CALLINGTN on the MML client.
LST CALLINGTN:;

Calling number trans table
--------------------------

Index = 0
Calling trans number function = Open
Calling number = 21980090
Calling number length = 10
CPC configuration = 255-Invalid
Time type = Cycle
Start time = 2006&01&01&00&00&00
End time = 2009&01&01&00&00&00
Index of number operation table = 0
--- END
In the displayed result, Calling trans number function is Open, Calling number is
21980090, Calling number length is 10, Index of DSP reference is 11, Time type is
Continuous, Start time is 2006-01-01-00:00:00, End time is 2009-01-01-00:00:00, Index of
number operation table is 0, and other parameters are not configured. The results are the same
as the configured data through the command, which indicates that the configuration is successful.
Verifying the Called Number Transform

This step must be performed after you set the called number transform. To verify the called
number transform, run LST CALLEDTN on the MML client.
LST CALLEDTN:;

Called number trans table
-------------------------
Index = 0
Called trans number function = Open
Called number = 21980080
Called number length = 10
CPC configuration = 255-Invalid
Time type = Cycle
Start time = 2006&01&01&00&00&00
End time = 2009&01&01&00&00&00
Index of number operation table = 0
--- END
In the displayed result, Called trans number function is Open, Called number is 21980080,
Called number length is 10, Index of DSP reference is 11, Time type is Continuous, Start
time is 2006-01-01-00:00:00, End time is 2009-01-01-00:00:00, Index of number operation
table is 0, and other parameters are not configured. The results are the same as the configured
Verifying the CPC Management

This step must be performed after you set the CPC management. To verify the CPC management,
run LST CPC on the MML client.
LST CPC:;

CPC table
---------
Index = 0
CPC modifing function = Open
original CPC = 255-Invalid
Time type = Cycle
Start time = 2006&01&01&08&00&00
End time = 2009&01&01&16&00&00
Changed CPC = 245-PriorityPeriodic
--- END
In the displayed result, CPC modifying function is Open, Original CPC is 2, Index of DSP
reference is 1, Time type is Segment, Start time is 2006-01-01-08:00:00, End time is
2009-01-01-16:00:00, and Changed CPC is 245, and other parameters are not configured. The
results are the same as the configured data through the command, which indicates that the

Feature Description 7 Configuring Protocol Translation Service Data
7 Configuring Protocol Translation Service

Data
About This Chapter
The protocol translation service enables the mutual transfer of signaling messages between the
network using ITU-T protocol (14 bits) and the network using ANSI protocol (24 bits). Before
configuring the protocol translation service data, make sure that the hardware data, MTP data,
and SCCP data are already configured.
7.1 Protocol Translation Service
In the networking, some equipment supports only the ITU-T protocol and does not support the
ANSI protocol on the MTP layer. The upper MAP layer, however, adopts the ANSI protocol.
In this case, the equipment adopts the ANSI message sent from the MAP layer to the ITU-T
message that can be transmitted on the ITU-T links. When this equipment interworks with a
network device that supports the ANSI links, a signaling point code (SPC) translation device is
required to translate the two protocols. The SG is an SPC translation device.
7.2 Service Flow
This section describes the networking structure for configuring the protocol translation service
and the implementation of the service.
Configuring the protocol translation service includes setting the SPC translation management
table and configuring the protocol translation DSP set table.
This section provides examples to describe how to configure the protocol translation service.

7 Configuring Protocol Translation Service Data Feature Description
7.1 Protocol Translation Service

In the networking, some equipment supports only the ITU-T protocol and does not support the
ANSI protocol on the MTP layer. The upper MAP layer, however, adopts the ANSI protocol.
In this case, the equipment adopts the ANSI message sent from the MAP layer to the ITU-T
message that can be transmitted on the ITU-T links. When this equipment interworks with a
network device that supports the ANSI links, a signaling point code (SPC) translation device is
required to translate the two protocols. The SG is an SPC translation device.
Note that this service is not universal. The method of configuring the service is determined by
the actual conditions of the network.
7.2 Service Flow

This section describes the networking structure for configuring the protocol translation service
and the implementation of the service.
This section describes the networking structure for configuring the protocol translation service.
This section describes the implementation of the protocol translation service.

This section describes the networking structure for configuring the protocol translation service.
Figure 7-1 shows the networking structure of the SG in this service.
Figure 7-1 Networking of protocol translation service

This section describes the implementation of the protocol translation service.
Converting ANSI Message to ITU-U Message

1. The SG receives an SCCP message (24 bits) sent from the ANSI network.
2. The SG queries the mapping table of 14-bit and 24-bit SPCs and judges whether to translate
the protocol and then forwards the message to the ITU-U network (using 14-bit SPC).
3. If yes, the SG translates the protocol and transfers the message to the ITU-T network. If
not, the SG does not translate the protocol and transfers the message to the ANSI network.

Converting ITU-U Message to ANSI Message

1. The SG receives an SCCP message (14 bits) sent from the ITU-T network.
2. The SG queries the mapping table of 14-bit and 24-bit SPCs and judges whether to translate
the protocol and then forwards the message to the ANSI network (using 24-bit SPC).
3. If yes, the SG translates the protocol and transfers the message to the ANSI network. If not,
the SG does not translate the protocol and transfers the message to the ITU-T network.

7.3.1 Terms
This section describes the terms used during configuring the protocol translation data.
7.3.2 Configuration Principle
This section describers the principles for configuring the protocol translation service data.
This section describes the relations between data tables related to protocol translation data
configuration.
Before configuring the protocol translation service, you must collect the data including the ITU-
T SPC, ANSI SPC, and ITU-T DSP index.
7.3.5 General Steps
You must follow certain procedures to configure the protocol translation data.
7.3.1 Terms
This section describes the terms used during configuring the protocol translation data.
l ITU-T: International Telecommunication Union-Telecommunication Standardization

Sector, with the protocol adopting 14-bit SPC
l ANSI: American National Standard Institute, with the protocol adopting 24-bit SPC

This section describers the principles for configuring the protocol translation service data.
l All the ANSI signaling points (SPs) that may send messages to the ITU-T SPs must be
configured in the SPC translation management table. The SPs that can be converted through
default adding or deleting 0x80 cannot be configured in the table.
l All the ITU-T SPs to be performed with protocol translation must be set in the protocol
translation DSP set table. These devices must be distinguished from each other.

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

Relation Between Protocol Translation Service Data Tables

The data tables of the protocol translation service have no reference relations, so you can
configure them regardless of their sequences.
Relation Between Protocol Translation Service Data Table and Other Data Table
The protocol translation data references the DSP index in the MTP data. The protocol translation
DSP set table references the index of ADD N7DSP.

Before configuring the protocol translation service, you must collect the data including the ITU-
T SPC, ANSI SPC, and ITU-T DSP index.
Before data configuration, you must collect the data as listed in Table 7-1.
Table 7-1 Protocol translation service data to be collected
ITU SPC ANSI SPC DSP index of ITU-T equipment
7.3.5 General Steps

You must follow certain procedures to configure the protocol translation data.
Table 7-2 lists the steps to configure this service data. The two steps in the table can be in any
order.
Step Operation
1 To set SPC translation management table
2 To set protocol translation DSP set table

Configuring the protocol translation service includes setting the SPC translation management
table and configuring the protocol translation DSP set table.
7.4.1 Setting SPC Translation Management Table
This section describes the mapping between the 14-bit SPCs in the ITU-T network and the actual
24-bit SPCs in the ANSI network. Do not configure the SPs that can be converted by the system
simply through increasing or decreasing 0x80.
7.4.2 Setting Protocol Translation DSP Set Table

The signaling processing of some devices in the network is so special that these devices transmit
the ANSI messages on the ITU-T link. For these devices, their ITU-T SPC index must be
identified.
7.4.1 Setting SPC Translation Management Table

This section describes the mapping between the 14-bit SPCs in the ITU-T network and the actual
24-bit SPCs in the ANSI network. Do not configure the SPs that can be converted by the system
simply through increasing or decreasing 0x80.
Command
ADD N7PCCVT
Parameter
r ID r Name
ITUPC ITU pc It specifies the 14-bit SPC of the SP in the ITU-T network.
ANSIPC ANSI pc It specifies the 24-bit SPC of the SP in the ANSI network.
Related Commands
Table 7-3 Related commands for configuring the MTP pc convert
Command Function
ADD N7PCCVT To add MTP pc convert
MOD N7PCCVT To modify MTP pc convert
RMV N7PCCVT To delete MTP pc convert
LST N7PCCVT To query MTP pc convert
7.4.2 Setting Protocol Translation DSP Set Table

The signaling processing of some devices in the network is so special that these devices transmit
the ANSI messages on the ITU-T link. For these devices, their ITU-T SPC index must be
identified.
The system performs protocol translation on the messages transferred between these special
devices and the ANSI network.
Command
ADD N7PRTTRSDSP

Parameter
r ID r Name
DSPIDX DSP index It specifies the SP index of the special device in the MTP DSP
table.
Related Commands
Table 7-4 Related commands for configuring the
Command Function
ADD N7PRTTRSDSP To add MTP protocol change DSP set
MOD N7PRTTRSDSP To modify MTP protocol change DSP set
RMV N7PRTTRSDSP To delete MTP protocol change DSP set
LST N7PRTTRSDSP To query MTP protocol change DSP set

This section provides examples to describe how to configure the protocol translation service.
The networking for configuring the protocol translation service is as shown in Figure 7-1.
Data Collection
The data collected for configuring the protocol translation service is as listed in Table 7-5.
ITU-T SPC ANSI SPC DPC index of ITU-T equipment
1111 111111 9
Procedure
Step 1 Add the SPC translation management table.
To add the SPC translation management table, set ITU pc to 1111 and ANSI pc to 111111, run
ADD N7PCCVT: ITUPC="1111", ANSIPC="111111";

Step 2 Add the protocol translation DSP set table.

To add the protocol translation DSP set table, set DSP index to 9, run the following command:
ADD N7PRTTRSDSP: DSPIDX=9;
----End
Verifying the SPC Translation Management Table

This step must be performed after you set the SCP translation management table. To verify the
SCP translation management table, run LST N7PCCVT on the MML client.
LST N7PCCVT:;

PC conversion table
-------------------
Index = 0
ITU pc = 001111
ANSI pc = 111111
--- END
In the displayed result, ITU pc is 1111 and ANSI pc is 111111. The results are the same as the
Verifying the Protocol Translation DSP Set Table

This step must be performed after you set the protocol translation DSP set table. To verify the
protocol translation DSP set table, run LST N7PRTTRSDSP on the MML client.
LST N7PRTTRSDSP:;

Mtp protocol change dsp set table
---------------------------------
Index = 0
DSP index = 9
--- END
In the displayed result, DSP index is 9. The results are the same as the configured data through
the command, which indicates that the configuration is successful.

Feature Description 8 Configuring Firewall Service Data
8 Configuring Firewall Service Data
About This Chapter
The firewall service masks specified type of messages and traces them. Before configuring the
firewall data, make sure that the hardware data, MTP data, and SCCP data are configured.
8.1 Firewall Service
This section describes the functions and features related to the Firewall service.
8.2 Service Flow
This section describes the networking structure, implementation, and service flow of the Firewall
service.
Configuring the Firewall service includes setting the Firewall software parameter, MAP content
masking management, and operation code set management.
8.5 Firewall Maintenance and Test
This section describes the processing result of the key information contained in the user input
message by the test system.
8.6 Firewall Alarm Configuration
When a message is masked, an alarm is reported if the SPC or GT in the message is configured
with the alarm data.
8.7 Firewall Statistics Configuration
The SG7000 provides the message statistics function.

8 Configuring Firewall Service Data Feature Description
8.1 Firewall Service

This section describes the functions and features related to the Firewall service.
8.1.1 Service Functions
With this function, a device can mask illegal signaling messages in the signaling network, and
mask messages all messages from a certain signaling point or of a certain type. This ensures the
security and reliability of the signaling network.
This section describes the functions of the Firewall service.
8.1.1 Service Functions

With this function, a device can mask illegal signaling messages in the signaling network, and
mask messages all messages from a certain signaling point or of a certain type. This ensures the
security and reliability of the signaling network.
The interworking between the signaling networks of different telecom operators makes it easier
for the operators to cooperate with each other. On the other hand, this becomes a means for some
operators to misuse the interworking to earn illegal profits.
How to better use the interworking to enhance cooperation and at the same time protect the
legitimate interests of all parties?
In the Internet, firewall is a familiar concept. The major function of a firewall is to detect illegal
packets and prevent them from accessing a certain system, and at the same time to ensure
authorized access to the system.

This section describes the functions of the Firewall service.
The firewall function describes the following:
l The signaling messages on the MTP layer, SCCP layer, TCAP layer, and MAP application
layer can be masked. The signaling messages can be masked depending on the signaling
point code, message type, GT code, subsystem number, address information, MAP
operation code, MAP application layer information, or the combination of them.
l The system supports large-capacity mask rules.
l The mask rules can be set in a flexible way. The mask rules are set in a tree structure to
reduce the redundant data.
l The mask alarm function can be configured.
l The mask statistics function can be configured.
l The specific rules to mask certain messages can be detected.
8.2 Service Flow

This section describes the networking structure, implementation, and service flow of the Firewall
service.

This section describes the networking structure for configuring the Firewall service data.
8.2.2 Mask Function of Firewall
This section describes the Firewall masking function, including masking mode and masking
layer.
8.2.3 Testing the Firewall Mask Rules
The mask rules can be tested. After setting the mask rules, you can emulate a message to test
whether the rules work.
8.2.4 Alarm Function of Firewall
For a message that is masked, if the applicable alarm data is configured, an alarm is reported.
8.2.5 Message Statistics Function of Firewall
This section describes the Firewall message statistics function based on message types.
8.2.6 Statistics of SMSC Addresses
If SMSC report switch is enabled, the system counts the SMSC addresses in the messages and
stores the result in the TeleNum.csv file in the path D:\MSSQL\SGDATA. "D:\MSSQL"
represents the installation path of MS SQL Server 2000.

This section describes the networking structure for configuring the Firewall service data.
In the firewall networking, a pair of SG7000s that work in the mutual backup mode are inserted
on the border between a local signaling network and a peer one. See Figure 8-1.
Figure 8-1 Firewall networking structure
8.2.2 Mask Function of Firewall

This section describes the Firewall masking function, including masking mode and masking
layer.
Mask Mode
The key function of the firewall is to resolve the key information in a message that intends to
access the local device. By comparing with the preset mask rules, the SG7000 can determine
whether to mask the message.
l If no, the message is treated as a normal SS7 message and sent to the destination.

l If yes, the SG7000 discards the message, without informing the source.
Four Mask Layers

The SG7000 supports four layers of mask:
l MTP layer mask: to mask messages according to the OPC and DPC.
l SCCP layer mask: to mask messages according to the calling GT and called GT.
l MAP operation code layer: to mask messages according to the MAP operation code.
l MAP content layer: to mask the TON, NPI, and OA fields in the SMMO signaling, and the
OA and IMSI fields in the SMMT signaling according to the MAP content.
Four Mask Levels of Firewall

A complete mask process consists of four levels of mask:
l Link set mask
l Link set public mask
l Link set default mask
l Link set public default mask
If a signaling message meets the mask conditions of a level, it is treated accordingly, and will
not be compared against the other mask conditions of the same level or the mask conditions of
any other level.
If a signaling message does not meet the mask conditions of any level, the system determines
whether to mask the message according to the no match rule.
Mask Tables of Firewall

To implement the mask rules, the system provides a number of mask tables. These tables are
combined into various mask rules. The mask rules can be set in a tree structure. Each node in
the tree structure represents a mask table.
The following are the mask tables:
l Initial mask table
l Link set public mask table
l Link set public default mask table
NOTE
The preceding three tables can only serve as the root node in the tree structure.
l OPC mask table
l DPC mask table
l Calling GT mask table
l Called GT mask table
l MAP operation code mask table
l MAP content mask table
l Property mask table

NOTE
Each branch in the tree structure must end with the property mask table.
The structure of the OPC mask table, DPC mask table, calling GT table, called GT table, MAP
operation code mask table, and MAP content mask table is listed in Table 8-1.
Table 8-1 Mask table structure

Referenced by Information in this table References
Local masking reference * Type of next masking table, and

number 0, 1, 2, and 3 next masking reference number
Local masking reference number in the initial mask table is referenced by the link set table,
similar to the reference relation of the mask rules.
The link set public mask table and link set public default mask table affect all link sets, so they
contain values Information in this table and References, but not Referenced by.
The property mask table has two items: Block and Pass.
The structure of the mask rule link is shown in Table 8-2.
Table 8-2 Structure of the mask rule link

Mask node Mask table type Mask table index
Node 1 in the mask rule Initial mask table 0
Node 2 in the mask rule OPC mask table 2
Node 3 in the mask rule MAP content mask table 3
Node 4 in the mask rule Property mask table None
In this instance, the rule has four nodes. These nodes enter into relationship by referencing Type
of next masking reference, Next masking reference number, and Local masking reference
number of the next mask table.
Mask tables of the same type can have a common Local masking reference number. Thus, a
table that references this number can have more than one subsequent node. In this way, a tree
structure is created. Each branch in the tree represents mask rules with the same root node.
The following is an instance to show how the mask rules are set.
Table 8-3, Table 8-4, and Table 8-5 list the assumed data.

Table 8-3 Initial mask table
Index Local Local Local Local Type of Next

masking masking masking masking next masking
reference reference reference reference masking reference
number 0 number 1 number 2 number 3 table number
0 0 1 2 None OPC mask 0

table
1 6 3 4 None OPC mask 4

table
Table 8-4 OPC mask table
Index Local Local Local Local Mask Type of Next

maskin maskin maskin maskin table next maskin
g g g g content maskin g
referen referen referen referen g table referenc
ce ce ce ce e
number number number number number
0 1 2 3
0 0 1 4 None * MAP 1
content
mask
table
1 0 3 5 None * MAP 2
content
mask
table
2 4 None None None * Pass None
Table 8-5 MAP content mask table
Index Local Local Local Local Mask Type of Next

maskin maskin maskin maskin table next maskin
g g g g content maskin g
referen referen referen referen g table referen
ce ce ce ce ce
number number number number number
0 1 2 3
0 0 1 2 None * Block None
1 0 2 5 None * Block None
2 1 2 None None * Pass None

These three tables indicate two trees of mask rule.
Mask rule tree 1 is shown in Figure 8-2.
Figure 8-2 Mask rule tree 1
Mask rule tree 2 is shown in Figure 8-3.
Figure 8-3 Mask rule tree 2
Search Sequence
A message is first compared with the root node, then the subnode, and then the leaf node. If the
message finds a node where the message does not meet the conditions, the message returns to
the father node for search.
The search process is as follows:

1. The system first judges whether the message mask function is enabled. If yes, the system
decodes the message to obtain all fields in the message that needs to run through the mask
process.
2. The system searches the initial mask table for the records whose mask reference number
is the same as the mask reference number of the link set.
3. The system searches for the next mask table mapping each record in the initial mask table.
l If the next mask table is an OPC mask table, DPC mask table, calling GT mask table,
called GT mask table, MAP operation code mask table, or MAP content mask table, the
system searches in the next mask table for the records according to the next masking
reference number in the initial mask table.
l If the next mask table is an OPC table, the searched records are compared with the mask
rules. If a record meets the mask rules and is set with a next mask table and next masking
reference number, the system searches the next mask table. If the record does not meet
the mask rules, another searched record is compared with the mask rules.
l In the next mask table of the OPC mask table, the records whose mask reference number
is the same as the next masking reference number in the OPC mask table are treated in
the same way as a record in the OPC mask table mapping the next masking reference
number in the initial mask table. This process continues until a mask table is found that
meets the mask rules and has next mask table as Block or Pass.
l If a mask table meets the mask rules and has next mask table as Pass, the message is
transmitted. If a mask table meets the mask rules and has next mask table as Block, the
message is discarded.
l If no such mask table is found, the system uses the same method to a same-level branch.
After the system performs the mechanism to all the same-level branches, it goes back
to the upper-level node.
l If a record in the OPC mask table whose mask reference number is the same as the next
masking reference number in the initial mask table does not meet the mask rules, the
system examines another such record in the OPC mask table. When the system
completes examining all records in the OPC mask table, processing on the initial mask
table ends.
4. The system checks whether the link set public mask table is enabled. If yes, the system
searches for its next mask table. The follow-up processing is the same as the initial mask
table.
5. The system searches the initial shield table for the records whose mask reference number
is the same as the default masking reference of the link set. The follow-up processing is
the same as the initial mask table.
6. The system checks whether the public default mask table is enabled. If yes, the system
searches for its next mask table. The follow-up processing is the same as the initial mask
table.
7. If no table is found that meets the mask rules and has next mask table as Block or Pass, the
system determines whether to mask the message according to the no match rule.
Combination of Mask Rules

A message that reaches the SG7000 must go through the following mask processes:
l Link set mask

l Public mask

l Link set default mask

l Public default mask
In any of the four mask processes, the system can mask a message according to the OPC, DPC,
calling GT, called GT, MAP code, and MAP content in sequence. The system can also skip
certain mask tables. Generally, you can evenly distribute the mask conditions on the four levels
to reduce the total volume of data.
Each mask condition has four mask reference numbers. Mask conditions on the same level can
have a public mask reference number, as shown in Figure 8-4. The four mask reference numbers
allow a mask condition to be referenced by four mask tables. In this way, some mask conditions
can be reused and the total volume of data is reduced.
Figure 8-4 Mask conditions and reference numbers
8.2.3 Testing the Firewall Mask Rules

The mask rules can be tested. After setting the mask rules, you can emulate a message to test
whether the rules work.
With this function, you can also obtain the mask rules that are applied to a message.
8.2.4 Alarm Function of Firewall

For a message that is masked, if the applicable alarm data is configured, an alarm is reported.

8.2.5 Message Statistics Function of Firewall

This section describes the Firewall message statistics function based on message types.
Statistics of MAP Messages from a Specific Initial Address

The system supports statistics of MAP messages from a specific initial address. Do not create a
statistics task, but run SET FWSOFTCFG to set the statistics switch and run ADD
FWSTATCFG to set the statistics conditions.
There can be 12 types of statistics results:
l Number of SMMT_MAPV1_PASS messages
l Number of SMMT_MAPV1_NOPASS messages
l Number of SMMO_MAPV1_PASS messages
l Number of SMMO_MAPV1_NOPASS messages
Statistics of SMSC Messages

The system supports statistics of SMSC messages. Do not create a statistics task, but run SET
FWSOFTCFG to set the statistics switch and run ADD FWSMSCAC to set the statistics
conditions.
There can be 10 types of statistics results:
l Number of SMSC_SCCP_SMMT_PASS messages
l Number of SMSC_SCCP_SMMT_BLOCK messages
l Number of SMSC_SCCP_SMMO_PASS messages
l Number of SMSC_SCCP_SMMO_BLOCK messages
l Number of SMSC_SCCP_SRI_FOR_SM_PASS messages
l Number of SMSC_SCCP_SRI_FOR_SM_BLOCK messages
l Number of SMSC_MAP_SMMT_PASS messages
l Number of SMSC_MAP_SMMT_BLOCK messages
l Number of SMSC_MAP_SMMO_PASS messages
l Number of SMSC_MAP_SMMO_BLOCK messages
Statistics of MAP Messages

The system supports statistics of MAP messages without involving any switch.

The statistics result is the number of MAP_OTHER_MESSAGE messages except MO, MT, and
SFM messages.
8.2.6 Statistics of SMSC Addresses

If SMSC report switch is enabled, the system counts the SMSC addresses in the messages and
stores the result in the TeleNum.csv file in the path D:\MSSQL\SGDATA. "D:\MSSQL"
represents the installation path of MS SQL Server 2000.

8.3.1 Terms
This section describes the terms used during configuring the Firewall service data.
You must follow certain principles to configure the Firewall service data.
This section describes the relations between data tables related to Firewall service data
configuration.
Before configuring the Firewall service, you must collect the data including the C7MTP screen
level, final default screen rule, and screen alarm time interval.
8.3.5 General Steps
You must follow certain procedures to configure the Firewall service data.
8.3.1 Terms
This section describes the terms used during configuring the Firewall service data.
Mask Condition
A mask condition is a mask rule that is effective to an MTP link set. The mask conditions are
grouped into six types:
l OPC mask condition
l DPC mask condition
l Calling GT mask condition
l Called GT mask condition
l MAP operation code mask condition
l MAP content mask condition
Each mask condition can have up to four mask reference numbers. The mask reference number
can identify and invoke a mask condition.

Mask Table
A mask table is a set of mask conditions on the same mask level. The mask tables are grouped
into six types:
l OPC mask table

l DPC mask table
Configure the six types of mask tables in the following order: OPC mask table, DPC mask table,
calling GT mask table, called GT mask table, MAP operation code mask table, and MAP content
mask table. A table can reference only a table that follows it, but not one that precedes it.
OPC and DPC

l OPC is the code of the signaling point where a message originates.
l DPC is the code of the signaling point where a message terminates.
Both OPC and DPC can be in the 14-bit or 24-bit format.
Calling GT and Called GT

l Calling GT is the GT of the calling signaling point or subsystem.
l Called GT is the GT of the called signaling point or subsystem.
Subsystem
The SCCP identifies an upper-layer user through the subsystem number. The SG7000 provides
255 subsystem numbers for choice. The commonly used subsystem numbers are listed in Table
8-6.
Table 8-6 The description of subsystem numbers
Sub System Description
1-SCMG SCCP management
2-Backup Backup
3-ISUP ISDN user part
4-OMAP Operation maintenance and administration part
5-MAP Mobile application part
6-HLR Home location register
7-VLR Visit location register
8-MSC Mobile switching center

Sub System Description
9-EIC Equipment identity center
10-AUC Authentication center
11-SPARE1 Spare 1
12-INAP IP application part
146-CAP CAMEL application part
MAP Operation Code

The SG7000 provides all operation codes as defined in Phase 1, Phase 2, and Phase 2+.
MAP Content
The SG7000 supports masking the TON, NPI, and OA fields in the MO messages, and the TON,
NPI, OA and IMSI fields in the MT messages.

You must follow certain principles to configure the Firewall service data.
Mask Reference
Mask reference is used to mask a specific MTP link set. The mask reference that is applied to
an MTP link set is set in the MTP link set management data.
Mask reference is implemented through the initial mask table.
For the initial mask table, Type of next masking table can be an OPC table, DPC table, calling
GT table, called GT table, MAP operation code table, MAP content table, Block, or Pass.
Link Set Public Mask

Link set public mask is used to mask the MTP link sets that do not meet the mask conditions in
the mask reference data.
Link set public mask is implemented through the link set public mask table. The link set public
mask table applies to all MTP link sets that are set with mask conditions. Records in this table
can be set to Used or Unused.
For the link set public mask table, Type of next masking table can be an OPC table, DPC table,
calling GT table, called GT table, MAP operation code table, MAP content table, Block, or
Pass.
Default Mask Reference

Default mask reference is used to mask the MTP link sets that do not meet the mask conditions
in the mask reference data and link set public mask data. The default mask reference that is
applied to an MTP link set is set in the MTP link set management data.

Similar to the mask reference, the default mask reference is implemented through the initial
mask table.
Link Set Public Default Mask

Link set public default mask is used to mask the MTP link sets that do not meet the mask
conditions in the mask reference data, link set public mask data, and default mask reference data.
Link set public default mask is implemented through the link set public default mask table. The
link set public default mask table applies to all MTP link sets that are set with mask conditions.
Records in this table can be set to Used or Unused.
For the link set public mask table, Type of next masking table can be an OPC table, DPC table,
calling GT table, called GT table, MAP operation code table, MAP content table, Block, or
Pass.
No Match Rule
The no match rule applies to a message that does not meet the mask conditions set in mask
reference, link set public mask, default mask reference, or link set public default mask.
Firewall Software Parameter Configuration Table

With this table, you can decide whether to enable the mask function, alarm function, and statistics
function. You can also set the final default mask rules.

This section describes the relations between data tables related to Firewall service data
configuration.
The reference relation between the firewall data tables is shown in Figure 8-5. Configure the
data to be referenced.
The statistics function, alarm function, SMSC address statistics function, and mask rule test
function do not have reference relation with other data.

Figure 8-5 Relation between firewall data tables

SET FWSOFTCFG ADD FWMAPCNBLK
C7MTP screen level ] Local masking reference number
[ [ ]
0、1、2、3
[ No match rule ] [ ...... ]
[ Screen alarm interval ] [ Type of next masking table ]
FIREWALL alarm ADD FWOPCODE

[ ]
switch [ Index ]
[ SMSC report switch ] [ ...... ]
[ SMSC stat switch ] ADD FWSSN

[ Index ]
ADD FWIM [ ...... ]
[ Whether used ]
ADD FWMAPCODEBLK
Local masking reference Local masking reference number
[ ]
number 0、1、2、3 [ 0、1、2、3 ]
Type
[ of next masking table]
[ Calling SSN index ]
Next masking
[ ]
reference number [ Called SSN index ]
[ Operation code set index ]

ADD N7LKS
[ ...... ]
[ Masking function ]
[ Type of next masking table ]
[ Masking reference ] [ Next masking reference number ]
Default masking
[ ]
reference ADD FWCDGTBLK
Local masking reference number
[ 0、1、2、3 ]
ADD FWSHR
[ ...... ]
[ Whether used ] [ Type of next masking table ]
Type of next masking [ Next masking reference number ]
[ ]
table
Next masking reference
[ ] ADD FWCGGTBLK
number
Local masking reference
[ ]
number 0、1、2、3
ADD FWDEFSHR [ ...... ]
[ Whether used ] [ Type of next masking table ]
Type of next masking [ Next masking reference number ]

[ ]
table
Next masking reference ADD FWDPCBLK
[ ]
number
[ ]
0、1、2、3
[ ...... ]
[ Next masking reference number ]
ADD FWOPCBLK
[ ]
0、1、2、3
[ ...... ]
[ Next masking reference number]


Before configuring the Firewall service, you must collect the data including the C7MTP screen
level, final default screen rule, and screen alarm time interval.
The data to be collected before you configure the firewall mask data is listed in Table 8-7.
C7MTP screen No match rule Screen alarm Firewall stat switch

level interval
Firewall alarm SMSC report SMSC stat switch Source PMC

switch switch
MAP content Operation code set Subsystem set MAP operation code
mask management management management mask management
parameters parameters parameters parameters
Called GT mask Calling GT mask DPC mask OPC mask

management management management management
parameters parameters parameters parameters
Link set public Link set public Initial mask MTP link set
default mask mask management management
management parameters parameters
parameters
The other parameters are easy to configure, and thus are not listed here.
8.3.5 General Steps

You must follow certain procedures to configure the Firewall service data.
Configure the firewall mask data from step 1 to step 13 as shown in Table 8-8.
Table 8-8 Steps to configure the firewall mask data
Step Action Command
1 To configure the firewall software configuration SET FWSOFTCFG

parameter

Step Action Command
2 To configure the MAP content mask management ADD FWMAPCNBLK
3 To configure the operation code set management ADD FWOPCODE
4 To configure the subsystem set management ADD FWSSN
5 To set the MAP operation code mask management ADD FWMAPCODEBLK
6 To configure the called GT mask management ADD FWCDGTBLK
7 To configure the calling GT mask management ADD FWCGGTBLK
8 To configure the DPC mask management ADD FWDPCBLK
9 To configure the OPC mask management ADD FWOPCBLK
10 To configure the link set public default mask ADD FWDEFSHR

management
11 To configure the link set public mask management ADD FWSHR
12 To configure the initial mask management ADD FWIM
13 To configure the MTP link set ADD N7LKS

Configuring the Firewall service includes setting the Firewall software parameter, MAP content
masking management, and operation code set management.
8.4.1 Configuring the Firewall Software Configuration Parameter
Firewall software configuration parameter.
8.4.2 Configuring the MAP Content Mask Management
This section describes the command, parameter, and related commands for configuring the MAP
content mask management.
8.4.3 Configuring Operation Code Set Management
This section describes the command, parameter, and related commands for configuring operation
code set management.
8.4.4 Configuring the Subsystem Set Management
subsystem set management.
8.4.5 Setting the MAP Operation Code Mask Management
This section describes the command, parameter, and related commands for setting the MAP
operation code mask management.
8.4.6 Configuring the Called GT Mask Management
GT mask management.
8.4.7 Configuring the Calling GT Mask Management

calling GT mask management.
8.4.8 Configuring the DPC Mask Management
This section describes the command, parameter, and related commands for configuring the DPC
mask management.
8.4.9 Configuring the OPC Mask Management
This section describes the command, parameter, and related commands for configuring the OPC
mask management.
8.4.10 Configuring Link Set Public Default Mask Management
This section describes the command, parameter, and related commands for configuring link set
public default mask management.
8.4.11 Configuring Link Set Public Mask Management
public mask management.
8.4.12 Configuring the Initial Mask Management
This section describes the command, parameter, and related commands for configuring the initial
mask management.
8.4.13 Configuring the MTP Link Set
This section describes the command, parameter, and related commands for configuring the MTP
link set.
8.4.1 Configuring the Firewall Software Configuration Parameter

Firewall software configuration parameter.
Command
SET FWSOFTCFG
Parameters
r ID r Name
SCRNLE C7MTP The value options are as follows:

VEL screen l NONE: Not to implement masking
level
l MTP masking: To mask the MTP messages received at and
forwarded by the SG7000
l SCCP masking: To mask the SCCP messages whose DSP is the
local SG7000
NOMAT No match It specifies whether to block the messages that do not meet the
CHRULE rule mask conditions.
ALMINT Screen It is the interval to report the firewall alarms. The value range is
ERVAL alarm 0-65535, expressed in seconds. The value 0 indicates 0.5 second.
interval


r ID r Name
STATSW Firewall It specifies whether to start the firewall statistic function.

ITCH stat switch
WARNS Firewall It specifies whether to start the firewall alarm function.

WITCH alarm
switch
SMSCRP SMSC It specifies whether to start the SMSC report function.

TSWT report
switch
SMSCST SMSC stat It specifies whether to start the SMSC address statistics function.
ATSWT switch
RSCBRD Source It is the PMC number of the active SBPU/SBPE.

PMC PMC PMC number is the logical number of a board in a service frame.
The PMC number is set to 0 for the HSYS in slot 6 of frame 0 in
shelf 0. It is set to 1 for the SHYS in slot 8 of frame 0 in shelf 0.
For the SBPU/SBPE in the left half of frame 0 in shelf 0, the PMC
logical numbers are 12, 10...2. They correspond to the slot numbers
from 0 to 5 in sequence. For the SBPU/SBPE in the right of frame
0 shelf 0, the PMC logical numbers are 3, 5...13 in sequence. They
correspond to the slot numbers from 10 to 16 in sequence.
As service source boards, the SBPUs/SBPEs are configured in
pairs. Meanwhile, the slot numbers in the left frame of the active
and standby SBPUs/SBPEs mirror those in the right frame. For
example, the SBPUs/SBPEs with PMCs 2 and 3 are configured as
active and standby boards. It is the same to the SBPUs/SBPEs with
PMCs 4 and 5.
Table 8-9 Relation between the PMC number and the slot number
Slot 0 1 2 3 4 5 6 8 10 11 12 14 15 16
No.
PM 12 10 8 6 4 2 0 1 3 5 7 9 11 13
CNu
mber
Related Commands
Table 8-10 lists the related commands.

Table 8-10 Related commands for configuring the firewall software configuration parameter
Command Function
SET FWSOFTCFG To set the firewall software configuration parameter
LST FWSOFTCFG To query the firewall software configuration parameter
8.4.2 Configuring the MAP Content Mask Management

This section describes the command, parameter, and related commands for configuring the MAP
content mask management.
Command
ADD FWMAPCNBLK
Parameters
r ID r Name
MR0-3 Local A mask rule is identified by its number. The mask reference
masking number ranges from 1 to 4. Each rule is referenced through the
reference mask reference number.
number
0-3
MAPTY MAP The value options are as follows:

message l Mobile Origination (MO): It is the short message service
type originated by the mobile station.
l Mobile Termination (MT): It is the short message service
terminated by the mobile station.
MINTON MIN_TO These are the configuration data of the MAP messages. For OA
N value and IMSI number, the wildcard is e, representing a digit.
The wildcard has the same function in other commands. The length
MAXTO MAX_TO of OA value and IMSI number adopts the precise match
N N approach. The other commands adopt the same method.
MINNPI MIN_NPI
MAXNPI MAX_NP
I
OA OA value
IMSI IMSI
number


r ID r Name
NTYPE Type of It specifies whether to pass a message.

next
masking
table
Related Commands
Table 8-11 Related commands for configuring the FW MAP content masking
Command Function
ADD To add the FW MAP content masking

FWMAPCNBLK
MOD To modify the FW MAP content masking

FWMAPCNBLK
RMV To delete the FW MAP content masking

FWMAPCNBLK
LST FWMAPCNBLK To query the FW MAP content masking
8.4.3 Configuring Operation Code Set Management

This section describes the command, parameter, and related commands for configuring operation
code set management.
Command
ADD FWOPCODE
Parameters
r ID r Name
MAPC0-1 Operation They are the values of the operation codes to be masked.
5 code 0-15
Related Commands

Table 8-12 Related commands for configuring the FW operation code set
Command Function
ADD FWOPCODE To add FW operation code set
MOD FWOPCODE To modify FW operation code set
RMV FWOPCODE To delete FW operation code set
LST FWOPCODE To query FW operation code set
8.4.4 Configuring the Subsystem Set Management

subsystem set management.
Command
ADD FWSSN
Parameters
r ID r Name
RLS0-15 Related They are the local subsystems related to the message.
local
subsystem
0-15
Related Commands

Command Function
ADD FWSSN To add FW subsystem set
MOD FWSSN To modify FW subsystem set
RMV FWSSN To delete FW subsystem set
LST FWSSN To query FW subsystem set

8.4.5 Setting the MAP Operation Code Mask Management

This section describes the command, parameter, and related commands for setting the MAP
operation code mask management.
Command
ADD FWMAPCODEBLK
Parameters
r ID r Name
number
0-3
CGSSNIN Calling The value options are as follows:

D SSN l SINGLE SSN: calling subsystem set indicator
indicator
l ALL SSN: all subsystems
l NO SSN: no subsystem
CGSSNID Calling It is the record of the corresponding subsystem set.

X SSN index
CDSSNIN Called The value options are as follows:

D SSN l SINGLE SSN: calling subsystem set indicator
indicator
l ALL SSN: all subsystems
l NO SSN: no subsystem
CDSSNID Called It is the record of the corresponding subsystem set.

X SSN index
CODEIN Operation The value options are as follows:

D code l SINGLE CODE: operation code set index
indicator
l ALL CODE: all operation codes
l NO CODE: no operation code
CODEID Operation It is the record of the corresponding operation code set.

X code set
index
NTYPE Type of The value options are as follows:

next l MAP content mask table
masking
table l Pass
l Block


r ID r Name
NMR Next It is the mask reference number of the MAP mask table when Type
masking of next masking table is set to MAP content mask table.
reference
number
Related Commands
Table 8-14 Related commands for configuring the FW operation code masking
Command Function
ADD To add FW operation code masking

FWMAPCODEBLK
MOD To modify FW operation code masking

FWMAPCODEBLK
RMV To delete FW operation code masking

FWMAPCODEBLK
LST To query FW operation code masking

FWMAPCODEBLK
8.4.6 Configuring the Called GT Mask Management

GT mask management.
Command
ADD FWCDGTBLK
Parameters
r ID r Name
number
0-3


r ID r Name
GT GT TYPE The value options are as follows:

l GT1 (CLASS 1 GT)
l GT2 (CLASS 2 GT)
l GT3 (CLASS 3 GT)
l GT4 (CLASS 4 GT)
MINTT MIN The value range is 0-255. It is set to 0 by default.

translation
type
MAXTT MAX
translation
type
MINCP MIN It is the numbering plan of GT codes, indicating how the addresses
number are numbered. The value options are as follows:
plan l UMDEF (0-not defined)
MAXCP MAX l ISDN (1-ISDN/telephome)

number l STANDBY (2-standby)
plan
l DATA (3-data X.121)
l TELEX (4-TelexF.69)
l MARINE (5-marine mobile)
l LAND (6-land mobile)
l ISDNMOV (7-ISDN/mobile)
l FREE1 (8-idle)
l FREE6 (13-idle)
l PRIV (14-number plan used by private network or special
network)
l SPARE (15-standby)
It is set to UMDEF by default.
MINAI MIN The value options are as follows:

address l FREE (0-IDLE)
attribute
l USRCODE (1-SUBSCRIBER NUMBER)
indicator
l NS (2-NATIONAL RESERVED)
MAXAI MAX
l NM (3-NATIONAL VALID NUMBER)
address
attribute l INTER (4-INTERNATIONAL NUMBER)
indicator l RSV5 (5-RESERVE) RSV255 (255-RESERVE)
It is set to FREE by default.
SAI GT_AI It is the mask range of the GT address information. The length of
start value GT address adopts the precise match approach in this command
and the following ones.


r ID r Name
EAI GT_AI
end value
NTYPE Type of The value options are as follows:

next l MAP operation code mask table
masking
table l MAP content mask table
l Pass
l Block
reference
number
Related Commands
Table 8-15 Related commands for configuring the FW called GT masking

Command Function
ADD FWCDGTBLK To add FW called GT masking
MOD FWCDGTBLK To modify FW called GT masking
RMV FWCDGTBLK To delete FW called GT masking
LST FWCDGTBLK To query FW called GT masking
8.4.7 Configuring the Calling GT Mask Management

calling GT mask management.
Command
ADD FWCGGTBLK

Parameters
r ID r Name
number
0-3
GT GT TYPE The value options are as follows:

l GT1 (CLASS 1 GT)
l GT2 (CLASS 2 GT)
l GT3 (CLASS 3 GT)
l GT4 (CLASS 4 GT)
MINTT MIN The value range is 0-255. It is set to 0 by default.

translation
type
MAXTT MAX
translation
type
MINCP MIN It is the numbering plan of GT codes, indicating how the addresses
number are numbered. The value options are as follows:
plan l UMDEF (0-not defined)
MAXCP MAX l ISDN (1-ISDN/telephome)

number l STANDBY (2-standby)
plan
l DATA (3-data X.121)
l TELEX (4-TelexF.69)
l MARINE (5-marine mobile)
l LAND (6-land mobile)
l ISDNMOV (7-ISDN/mobile)
l FREE1 (8-idle)
l FREE6 (13-idle)
l PRIV (14-number plan used by private network or special
network)
l SPARE (15-standby)
It is set to UMDEF by default.
MINAI MIN The value options are as follows:

address l FREE (0-IDLE)
attribute
l USRCODE (1-SUBSCRIBER NUMBER)
indicator
l NS (2-NATIONAL RESERVED)
l NM (3-NATIONAL VALID NUMBER)


r ID r Name
MAXAI MAX l INTER (4-INTERNATIONAL NUMBER)

address
l RSV5 (5-RESERVE) RSV255 (255-RESERVE)
attribute
indicator It is set to FREE by default.
SAI GT_AI It is the mask range of the GT address information. The length of
start value GT address adopts the precise match approach in this command
and the following ones.
EAI GT_AI
end value
NTYPE Type of It is the next step operation if a message meets the mask conditions.
next The value options are as follows:
masking l Called GT mask table
table
l Pass
l Block
reference
number
Related Commands
Table 8-16 Related commands for configuring the FW calling GT masking

Command Function
ADD FWCGGTBLK To add FW calling GT masking
MOD FWCGGTBLK To modify FW calling GT masking
RMV FWCGGTBLK To delete FW calling GT masking
LST FWCGGTBLK To query FW calling GT masking
8.4.8 Configuring the DPC Mask Management

This section describes the command, parameter, and related commands for configuring the DPC
mask management.

Command
ADD FWDPCBLK
Parameters
r ID r Name
number
0-3
NET Network It indicates the network to which a link set belongs. The value
indicator options are as follows:
l IM (International active network)
l IS (International standby network)
l NM (National active network)
l NS (National standby network)
SDPC Start DPC It is the DPC mask range.
EDPC End DPC
masking l Calling GT mask table
table
l Pass
l Block
NMR Next It is the mask reference number of the mask table when Type of
masking next masking table is set to Calling GT mask table, Called GT mask
reference table, MAP operation code mask table, or MAP content mask table.
number
Related Commands
Command Function
ADD FWDPCBLK To add FW DPC masking

Command Function
MOD FWDPCBLK To modify FW DPC masking
RMV FWDPCBLK To delete FW DPC masking
LST FWDPCBLK To query FW DPC masking
8.4.9 Configuring the OPC Mask Management

This section describes the command, parameter, and related commands for configuring the OPC
mask management.
Command
ADD FWOPCBLK
Parameters
r ID r Name
number
0-3
NET Network It indicates the network to which a link set belongs. The value
indicator options are as follows:
l IM (International active network)
l IS (International standby network)
l NM (National active network)
l NS (National standby network)
SOPC Start OPC It is the OPC mask range.
EOPC End OPC
masking l DPC mask table
table
l Pass
l Block


r ID r Name
masking next masking table is set to DPC mask table, Calling GT mask
reference table, Called GT mask table, MAP operation code mask table, or
number MAP content mask table.
Related Commands
Table 8-18 Related commands for configuring the FW OPC masking

Command Function
ADD FWOPCBLK To add FW OPC masking
MOD FWOPCBLK To modify FW OPC masking
RMV FWOPCBLK To delete FW OPC masking
LST FWOPCBLK To query FW OPC masking
8.4.10 Configuring Link Set Public Default Mask Management

public default mask management.
Command
ADD FWDEFSHR
Parameters
r ID r Name
VALID Whether It specifies whether link set public default mask is enabled.
used


r ID r Name
masking l OPC mask table
table
l DPC mask table
l Pass
l Block
masking next masking table is set to OPC mask table, DPC mask table,
reference Calling GT mask table, Called GT mask table, MAP operation
number code mask table, or MAP content mask table.
Related Commands
Table 8-19 Related commands for configuring the FW link set public default masking
Command Function
ADD FWDEFSHR To add FW link set public default masking
MOD FWDEFSHR To modify FW link set public default masking
RMV FWDEFSHR To delete FW link set public default masking
LST FWDEFSHR To query FW link set public default masking
8.4.11 Configuring Link Set Public Mask Management

public mask management.
Command
ADD FWSHR

Parameters
r ID r Name
VALID Whether It specifies whether link set public mask is enabled.

used
table
l DPC mask table
l Pass
l Block
Related Commands
Table 8-20 Related commands for configuring the FW link set public masking
Command Function
ADD FWSHR To add FW link set public masking
MOD FWSHR To modify FW link set public masking
RMV FWSHR To delete FW link set public masking
LST FWSHR To query FW link set public masking
8.4.12 Configuring the Initial Mask Management

This section describes the command, parameter, and related commands for configuring the initial
mask management.
Command
ADD FWIM

Parameters
r ID r Name
VALID Whether It specifies whether initial mask is enabled.

used
number
0-3
table
l DPC mask table
l Pass
l Block
Related Commands
Table 8-21 Related commands for configuring the FW initial masking

Command Function
ADD FWIM To add FW initial masking
MOD FWIM To modify FW initial masking
RMV FWIM To delete FW initial masking
LST FWIM To query FW initial masking

8.4.13 Configuring the MTP Link Set

This section describes the command, parameter, and related commands for configuring the MTP
link set.
Command
ADD N7LKS
Parameters
r ID r Name
SCRN Masking It specifies whether to enable the mask function to the link set.
function
REF Masking It is the mask reference number of the link set, referencing the
reference initial mask table.
DFTREF Default It is the default mask reference number of the link set, referencing
masking the initial mask table.
reference
Related Commands
Table 8-22 Related commands for configuring the MTP link set
Command Function
RMV N7LKS To delete the MTP link set
8.5 Firewall Maintenance and Test

This section describes the processing result of the key information contained in the user input
message by the test system.
Command
TST FWMSG

Parameters
r ID r Name
SHN Shelf They specify the location of a board.

number
FN Frame
number
SN Slot
number
LOC Location
LNKS Link set It is the index of the link set to be tested.

index
Logic network index, Network indication, OPC, DPC, Calling GT type, Calling translation
type, Calling number plan, Calling nature of address indicator, Calling address message,
Called GT type, Called translation type, Called number plan, Called nature of address
indicator, Called address message, Calling SSN, Called SSN, Operation code, MAP message
type, TON, NPI
They are all parameters for the test.
Related Command
None.
8.6 Firewall Alarm Configuration

When a message is masked, an alarm is reported if the SPC or GT in the message is configured
with the alarm data.
8.6.1 Configuring the Software Configuration Parameter
software configuration parameter.
8.6.2 Configuring FW Alarm Table
This section describes the command, parameter, and related commands for configuring the FW
alarm table.

Command
SET FWSOFTCFG

Parameters
r ID r Name
WARNS Firewall It enables or disables the firewall alarm function.

WITCH alarm
switch
ALMINT Screen It sets the interval to report firewall alarms.

ERVAL alarm
interval
Related Commands
Command Function
SET FWSOFTCFG To configure the firewall software configuration

parameter
8.6.2 Configuring FW Alarm Table

alarm table.
Command
ADD FWALMCFG
Parameters
r ID r Name
VALID Whether It specifies whether to enable the FW alarm function.

used
LNI Logic They are all alarm parameters and can be divided into two types
network as follows:
index l Intersection relation: Start OPC and End OPC, Start DPC and
End DPC, Calling GT_AI start value and Calling GT_AI end
NET1 OPC
value, Called GT_AI start value and Called GT_AI end
network
value
indicator


r ID r Name
SOPC Start OPC l Aggregation relation: parameters except those in the

intersection relation
EOPC End OPC
NET2 DPC
network
indicator
SDPC Start DPC
EDPC End DPC
Related Commands
Table 8-24 Related commands for configuring the FW alarm configuration

Command Function
ADD FWALMCFG To add FW alarm configuration
MOD FWALMCFG To modify FW alarm configuration
RMV FWALMCFG To delete FW alarm configuration
LST FWALMCFG To query FW alarm configuration
8.7 Firewall Statistics Configuration

The SG7000 provides the message statistics function.
8.7.2 Configuring FW Statistics Table
statistics table.
8.7.3 Configuring FW SMSC Address Statistics Table
SMSC address statistics table.
8.7.4 Querying the Permanent Statistics Data
This section describes the command, parameter, and related commands for querying the
permanent statistics data.


Command
SET FWSOFTCFG
Parameters
r ID r Name
STATSW Firewall It enables or disables the firewall statistics function.

ITCH stat switch
SMSCST SMSC stat It enables or disables the SMSC statistics function.

ATSWT switch
SMSCRP SMSC If it is set to ON, the statistics result is saved in the TeleNum.csv
TSWT report file in the path D:\MSSQL\SGDATA. "D:\MSSQL" represents
switch the installation path of MS SQL Server 2000.
Related Commands
Command Function
SET FWSOFTCFG To configure the firewall software configuration

parameter
8.7.2 Configuring FW Statistics Table

statistics table.
Command
ADD FWSTATCFG

Parameters
r ID r Name
VALID Whether It specifies whether to enable the FW statistics function.

used
OA Initial It is the initial address information of a message.

address
informatio
n
Related Commands
Table 8-26 Related commands for configuring the FW statistics configuration

Command Function
ADD FWSTATCFG To add FW statistics configuration
MOD FWSTATCFG To modify FW statistics configuration
RMV FWSTATCFG To delete FW statistics configuration
LST FWSTATCFG To query FW statistics configuration
8.7.3 Configuring FW SMSC Address Statistics Table

SMSC address statistics table.
Command
ADD FWSMSCAC
Parameters
r ID r Name
VALID Whether It specifies whether to enable the FW SMSC address statistics

used function.
SMSCAD SMSC It is the SMSC address information of a message.

DR address
informatio
n

Related Commands
Table 8-27 Related commands for configuring the FW SMSC address statistics configuration
Command Function
ADD FWSMSCAC To add FW SMSC address statistics configuration
MOD FWSMSCAC To modify FW SMSC address statistics configuration
RMV FWSMSCAC To delete FW SMSC address statistics configuration
LST FWSMSCAC To query FW SMSC address statistics configuration
8.7.4 Querying the Permanent Statistics Data

This section describes the command, parameter, and related commands for querying the
permanent statistics data.
Command
DSP TRFPERMDATA
Parameter
r ID r Name
ITM Statistics It is the statistics item to be queried.

item
Related Command
None.

Feature Description 9 Configuring MC Service Data
9 Configuring MC Service Data
About This Chapter
This chapter tells how to configure the message center (MC) service data. Before configuring
the MC service data, make sure that the hardware data, MTP data, and SCCP data are already
configured.
9.1 MC Service
The MC service is a message forwarding service through which messages are forwarded to a
specified message center. The earlier networks only allowed calls to be forwarded. With the MC
service enabled, messages can also be forwarded.
9.2 Service Flow
This section describes the networking structure and service flow of the MC service.
Configuring the MC service includes setting the MC software parameter, adding the MC routing
number, and adding the MC local SMSC number.
This section provides examples to describe how to configure the MC service data.

9 Configuring MC Service Data Feature Description
9.1 MC Service
The MC service is a message forwarding service through which messages are forwarded to a
specified message center. The earlier networks only allowed calls to be forwarded. With the MC
service enabled, messages can also be forwarded.
With the MC service, you can:
l Forward messages to another mobile phone.
l Forward and save all messages to an account registered on the website of the operator. You
can log in to the website and browse your messages.
The MC service solves the problem of message processing when mobile phones cannot receive
messages. In addition, messages are saved on the website, which greatly enlarges the message
storage capacity for users.
9.2 Service Flow

This section describes the networking structure and service flow of the MC service.
This section describes the networking structure for configuring the MC service data.
This section describes the implementation of the MC service.

This section describes the networking structure for configuring the MC service data.
Figure 9-1 shows the networking structure of the MC service.

Figure 9-1 Networking structure of MC service
GMSC: Gateway Mobile Switching Center HLR:Home Location Register MC: Message Center
The devices in the above networking structure and their functions are as follows:
l SG: It is used to process and transfer signaling messages between network devices. It routes
messages coming from external networks to relevant network elements (NEs).
l HLR: It is used to return user location area information after interacting with other
equipment.
l GMSC: It is used to process messages coming from external networks.
l VMSC: It is used to connect calls for roaming terminals.
l MC: It is used to process non-call-related services.

This section describes the implementation of the MC service.
On receiving the "SRI for sm" message, the SG queries whether it is sent from an external
network and whether it is sent to a user registered with the MC service.
l If both answers are "Yes", the SG inserts the route number in the message according to the
route number configured for each user, and then forwards the message to the specific MC
for processing.
l If either answer is "No", the SG transparently forwards the message to the HLR for
addressing.


This section describes the relations between data tables related to MC service data configuration.
Before configuring the MC service, you must collect the data including the interception mode,
country code, and user MSISDN.
9.3.3 General Steps
You must follow certain procedures to configure the MC service data.

This section describes the relations between data tables related to MC service data configuration.
Relation Between MC Service Data Tables

Figure 9-2 shows the configuration sequences and referenced relations of parameters.
Generally, the sequence is from top to bottom. The referenced parameters must be configured
and then referenced.
Figure 9-2 Relation between MC service data tables

Relation Between MC Service Data Table and Other Data Table

SCCP GT translation table must use the index configured with the command ADD N7DSP.

Before configuring the MC service, you must collect the data including the interception mode,
country code, and user MSISDN.
Table 9-1 MC service data to be collected

Intercept MT Country code MC MAP MC SCCP
mode Modification Modification
indicator indicator
MC process SMSC address MSISDN User IMSI number

indicator
Whether enable MC routing MC routing number Sub IMSI

related services index
Sub MSISDN MSISDN Type Whether enable MC routing number

9.3.3 General Steps

You must follow certain procedures to configure the MC service data.
Table 9-2 lists the steps for configuring the MC service data.
Table 9-2 Configuration steps

Step Operation
1 To set the software parameters for MC service
2 To add the MC routing number
3 To add the MC local SMSC address
4 To add the service user data
5 To add the sub MSISDN numbers

Step Operation
6 To set the SCCP GT translation table
The requirements on the sequence are as follows:

l You must add the MC routing number before configuring the service user data.
l You must add the service user data before configuring sub MSISDN numbers.
l Adding the sub MSISDN numbers is optional.
l Adding the MC local SMSC addresses is a step without sequence restriction.

Configuring the MC service includes setting the MC software parameter, adding the MC routing
number, and adding the MC local SMSC number.
9.4.1 Setting Software Parameters for MC Service
MC software parameters include MC switches and basic parameters.
9.4.2 Adding MC Routing Number
This section describes the command, parameter, and related commands for adding the MC
routing number.
9.4.3 Adding MC Local SMSC Address
This function is used to add SMSC addresses for the entire local network.
This section describes the command, parameter, and related commands for adding the service
user data.
9.4.5 Adding Sub MSISDN numbers
This section describes the command, parameter, and related commands for adding the sub
MSISDN numbers.
This step is optional according to the actual conditions of the current network. It is not specified
here.
9.4.1 Setting Software Parameters for MC Service

MC software parameters include MC switches and basic parameters.
Command
SET SMSICSOFTCFG

Parameters
r ID r Name
COUNTR Country It defines the country code of an operator's network.

YCODE code
INTERM Service It defines the mode of the message center.

ODE type
MAPSWI MC MAP It controls whether to modify the MSISDN at the MAP layer
TCH modificati through the MC function.
on
indicator
SCCPSWI MC SCCP It controls whether to modify the called number in the SCCP
TCH modificati message through the MC function. The MC service requires this
on parameter to be enabled.
indicator
MCPROC MC It controls whether to consider the called number in the SCCP

ESS process message or the MSISDN on the MAP layer as the called number
indicator in the MC service. When the called number in the SCCP message
is modified, the MSISDN on the MAP layer must be considered
as the called number.
Related Commands
Table 9-3 lists the related commands for setting software parameters for the MC service.
Table 9-3 Related commands for configuring the SMS intercept configuration
Command Function
SET SMSICSOFTCFG To set SMS intercept configuration
LST SMSICSOFTCFG To query SMS intercept configuration
9.4.2 Adding MC Routing Number

This section describes the command, parameter, and related commands for adding the MC
routing number.
Command
ADD MCROUTE

Parameters
r ID r Name
ISVALID Is valid It controls whether this MC route is valid.
MCROUT MC It defines the number of a route directing to the MC.

ENUM routing
number
Related Commands
Table 9-4 lists the related commands for adding the MC routing number.
Table 9-4 Related commands for configuring the MC routing number
Command Function
ADD MCROUTE To add MC routing number
MOD MCROUTE To modify MC routing number
RMV MCROUTE To delete MC routing number
LST MCROUTE To query MC routing number
9.4.3 Adding MC Local SMSC Address

This function is used to add SMSC addresses for the entire local network.
Command
ADD MCSMSCADDR
Parameters
r ID r Name
MCSMSC SMSC It defines a local SMSC address.

ADDR Address
Related Commands
Table 9-5 lists the related commands for adding the MC local SMSC address.

Table 9-5 Related commands for configuring the MC local SMSC address
Command Function
ADD MCSMSCADDR To add MC local SMSC address
MOD MCSMSCADDR To modify MC local SMSC address
RMV MCSMSCADDR To delete MC local SMSC address
LST MCSMSCADDR To query MC local SMSC address

This section describes the command, parameter, and related commands for adding the service
user data.
This function is used to add service user data.
Command
ADD SERUATTR
Parameters
r ID r Name
USRNUM MSISDN It defines the MSISDN number for a user.
IMSINU User IMSI It defines the IMSI number for a user.

M number
SERVAT Whether It defines a related service. Here, set the parameter to Enable MC
TR enable service.
related
services
RTIDX MC It defines the MC routing index mapping a user.

Routing
Index
Related Commands
Table 9-6 lists the related commands for adding service user data.
Command Function

Command Function
9.4.5 Adding Sub MSISDN numbers

This section describes the command, parameter, and related commands for adding the sub
MSISDN numbers.
This function is used to add sub MSISDN numbers.
Command
ADD SUBUSR
Parameters
r ID r Name
SUBNUM MSISDN It defines a sub MSISDN number for a user.
IMSI IMSI It defines the IMSI number for a user. It must be the same as the
host MSISDN number.
SUBNUM MSISDN It can be the following:

TYP Type l Line2: the second user number.
l FAX: fax.
l CDA: data service user.
The types of the three sub MSISDN numbers mapping a same IMSI
cannot be identical.
SERVTY Service It controls whether to enable the MC service.

P type
MCRTID MC It defines an MC routing index mapping a user.

X routing
number
index
Related Commands
Table 9-7 lists the related commands for adding the sub MSISDN number.

Table 9-7 Related commands for configuring the sub MSISDN
Command Function
ADD SUBUSR To add sub MSISDN
MOD SUBUSR To modify sub MSISDN
RMV SUBUSR To delete sub MSISDN
LST SUBUSR To query sub MSISDN

This step is optional according to the actual conditions of the current network. It is not specified
here.
For users whose data is not configured in the user attribute table, the system transparently
transfers the message to the SCCP layer. You must, therefore, configure data in the SCCP GT
translation table to define the default HLR (maximum matching) for the MSISDN based on
number segments.

This section provides examples to describe how to configure the MC service data.
The networking for configuring the MC service is as shown in Figure 9-1.
Data Collection
The data collected for configuring the MC service is as listed in Table 9-8.

indicator indicator
MC mode 86 Open Open
MC process SMSC address MSISDN User IMSI number

indicator
MAP layer 23 13798585850 21980000
Whether enable MC routing MC routing number Sub IMSI

Enable MC 1 23 21980000
service


indicator indicator
Sub MSISDN MSISDN Type Whether enable related MC routing number

services index
13798585859 LINE2 Enable MC service 1
Procedure
Step 1 Set software parameters for the MC service.
To set software parameters for the MC service, set country code to 86, Service type to MC
mode, MC MAP Modification indicator to Open, MC SCCP Modification indicator to
Open, and MC process indicator to MAP layer, run the following command:
SET SMSICSOFTCFG: COUNTRYCODE="86", INTERMODE=MODE1, MAPSWITCH=SWITCH1,
SCCPSWITCH=SWITCH1, MCPROCESS=PRO0;
Step 2 Add the MC routing number.

To add the MC routing number, set Is valid to Valid and MC routing number to 23, run the
following command:
ADD MCROUTE: ISVALID=VALID1, MCROUTENUM="23";
Step 3 Add the MC local SMSC address.

To add the MC local SMSC address, set SMSC address to 23, run the following command:
ADD MCSMSCADDR: SMSCADDR="23";

To add the service user data, set MSISDN to 13798585850, User IMSI number to 21980000,
Whether enable related services to Enable MC service, and MC routing index to 1, run the
following command:
ADD SERUATTR: USRNUM="13798585850", IMSINUM="21980000", SERVATTR=OMC-1,
RTIDX=1;
Step 5 Add the sub MSISDN number.

To add the sub MSISDN number, set MSISDN to 13798585859, User IMSI number to
21980000, MSISDN type to LINE2, Whether enable related services to Enable MC
service, and MC routing index to 1, run the following command:
ADD SUBUSR: SUBNUM="13798585859", IMSI="21980000", SUBNUMTYP=TYP0,
SERVTYP=TYP0-1, MCRTIDX=1;
----End
Verifying Software Parameters for the MC Service

This step must be performed after you set the software parameters for the MC service. To verify
the software parameters for the MC service, run LST SMSICSOFTCFG on the MML client.
LST SMSICSOFTCFG:;


SMS configuration table
-----------------------
IN filter type = G_3<OFF>G_2<OFF>G_1<OFF>
Country Code = 86
Local GT address = 92630630
Charge control for Different Brands = G_4<OFF>G_3<OFF>G_2<OFF>G_1<OFF>
Special User SMR Switch = CLOSE
Mode of relaying message = Relay to original signal point
MC MAP Modification indicator = OPEN
MC SCCP Modification indicator = OPEN
MC Process indicator = MAP layer
Service type = MC mode
Default HLR Index = 65535
--- END
In the displayed result, country code is 86, Service type is MC mode, MC MAP Modification
indicator is Open, MC SCCP Modification indicator is Open, and MC process indicator is
MAP layer. The results are the same as the configured data through the command, which
Verifying the MC Routing Number

This step must be performed after you set the MC routing number. To verify the MC routing
number, run LST MCROUTE on the MML client.
LST MCROUTE:;

MC Routing Number Table
-----------------------
Index = 1
Is Valid = Valid
MC Routing Number = 23
--- END
In the displayed result, Is valid is Valid and MC routing number is 23. The results are the
successful.
Verifying the MC Local SMSC Address

This step must be performed after you set the MC local SMSC address. To verify the MC local
SMSC address, run LST MCSMSCADDR on the MML client.
LST MCSMSCADDR:;

MC Local SC Address Table
-------------------------
Index = 0
SMSC Address = 23
--- END

In the displayed result, SMSC address is 23. The results are the same as the configured data
through the command, which indicates that the configuration is successful.
Verifying the Service User Data

This step must be performed after you set the service user data. To verify the service user data,
LST SERUATTR:;

---------------------------------
Index = 0
MSISDN = 13798585850
G_6<OFF>G_5<OFF>G_4<ON>G_3<OFF>G_2<OFF>G_1<OFF>
--- END
In the displayed result, MSISDN is 13798585850, User IMSI number is 21980000, Whether
enable related services is Enable MC service, MC routing index is 1, and the values of other
parameters are default values. The results are the same as the configured data through the
command, which indicates that the configuration is successful.
Verifying the Sub MSISDN Number

This step must be performed after you set the sub MSISDN number. To verify the sub MSISDN
number, run LST SUBUSR on the MML client.
LST SUBUSR:;

Sub Msisdn Table
----------------
Index = 0
MSISDN = 13798585859
IMSI Number = 21980000
MSISDN type = LINE2
Service Type = MC service<ON>
MC Routing Number Index = 1
--- END
In the displayed result, MSISDN is 13798585859, User IMSI number is 21980000, MSISDN
type is LINE2, Whether enable related services is Enable MC service, and MC routing
index is 1. The results are the same as the configured data through the command, which indicates

Feature Description 10 Configuring FNR Service Data - General
10 Configuring FNR Service Data - General
About This Chapter
This chapter tells how to configure the flexible number routing (FNR) service data. Before
configuring the FNR service data, make sure that the hardware data, MTP data, and SCCP data
are configured.
10.1 FNR Service
The FNR service enables subscribers to migrate among HLRs of the same carrier without
changing subscriber mobile numbers. The FNR service is an application of the MNP service.
10.2 Service Flow
This section describes the networking structure and service flow of the FNR service.
Configuring the FNR service includes setting the HLR address table, and MNP software
parameter and so on.
This section provides examples to describe how to configure the FNR service data.

10 Configuring FNR Service Data - General Feature Description
10.1 FNR Service

The FNR service enables subscribers to migrate among HLRs of the same carrier without
changing subscriber mobile numbers. The FNR service is an application of the MNP service.
The FNR service is applicable in the following conditions:
l When a subscriber migrates between 2G and 3G networks of the same carrier, the mobile
number of the subscriber does not point to the actual HLR.
l When a subscriber migrates among HLRs of the same carrier, the mobile number of the
subscriber does not point to the actual HLR.
NOTE
l When MNP work mode in the MNP software parameter table is set to MNP_FN mode, the FNR service
is a sub-function of the MNP service and can be enabled together with the MNP service. For details about
subscriber migration among the networks of different carriers, refer to 4 Configuring MNP Service
Data.
l When MNP work mode in the MNP software parameter table is set to FN mode, the FNR service conflicts
with the MNP service and cannot be enabled together with the MNP service on the SG7000. Thus, this
mode is not specified.
10.2 Service Flow

This section describes the networking structure and service flow of the FNR service.
This section describes the networking structure for configuring the FNR service data.
This section describes the implementation of the FNR service on the SG7000.

This section describes the networking structure for configuring the FNR service data.
Figure 10-1 and Figure 10-2 shows the networking structure of FNR service.

Figure 10-1 Networking structure of the FNR service - subscriber migration among networks
of different carriers
2G NETWORK 3G NETWORK
HLR SMSC HLR SMSC
SG SG SG
2G MSC 3G MSC
PSTN/Other PLMN
Circuit
SS7 link

Figure 10-2 Networking structure of the FNR service - subscriber migration among different
HLRs within the same network
HLR: Home Location Register MSC: Mobile Switching Center SMSC: Short Message Service Center
SG: U-SYS SG7000 Signaling
Gateway
The devices and their functions in the network are as follows:

l SG: It is used to process and forward signaling messages between inter-network or intra-
network signaling equipment.
l HLR: It is used to return user location area number after interacting with the MSC.
l MSC: It is used to connect calls.
l SMSC: It is used to process, store, and transfer short messages.

This section describes the implementation of the FNR service on the SG7000.
When MNP work mode in the MNP software parameter table is set to MNP_FN mode, the
FNR service is implemented in the following way:
l In the call or SMS processing flow, the SG obtains the MSISDN of a subscriber and
forwards the message to the specified HLR based on the configured subscriber data.

– Based on user MSISDN number, the equipment transfers call-related messages to the
specified HLR according to the configured data of the user who is in the virtual operator's
network.
– Based on user MSISDN number, the equipment transfers non-call-related messages to
the specified HLR according to the configured user data.
l In the location update processing (such as subscriber power-off, subscriber power-on,
authentication, registration, and cancellation of a supplementary service), the SG obtains
the IMSI number of a subscriber and forwards the message to the specified HLR based on
the configured subscriber data. In the case that the SIM is not replaced, the mapping relation
between the IMSI number and the homed HLR of the subscriber cannot be established. In
this condition, other NEs cannot address the homed HLR of the subscriber through number
analysis. In this case, the implementation of the FNR service is to address the HLR based
on a single IMSI number.

10.3.1 Terms
This section describes the terms used during configuring the FNR service data.
You must follow certain principles to configure the FNR service data.
This section describes the relations between data tables related to FNR service data
configuration.
Before configuring the FNR service, you must collect the data including the country code, The
number prefix of E214, and The number prefix of E212.
10.3.5 General Steps
You must follow certain procedures to configure the FNR service data.
10.3.1 Terms
This section describes the terms used during configuring the FNR service data.
FN User
In the FNR service, a user who can directly locate the HLR is called an FN user.
MNP
The MNP refers to the NP function of mobile numbers. The MSISDN of an MNP user need not
be changed when the user moves out of a network.
MSISDN
Each mobile station (MS) has the following two numbers:

l MSISDN: directory number and open to the public

l IMSI: provided by the network operator to uniquely identify an MS
IMSI
An IMSI uniquely identifies an MS. An IMSI is consists of three parts:

You must follow certain principles to configure the FNR service data.
The configuration parameters are based on actual situations including networking, signaling
message structure, and difference of network devices. This section only specifies the typical
configuration.
For FN users, the following items must be configured:
l HLR address
l MNP software configuration parameter
l MNP prefix mapping management
l Service user data
l SCCP GT translation table

This section describes the relations between data tables related to FNR service data
configuration.
Relation Between FNR Service Data Tables

Figure 10-3 shows the configuration sequences and referenced relations of parameters.
Generally, the sequence is from top to bottom. The referenced parameters must be configured
first and then be referenced.

Figure 10-3 Relation between FNR service data tables
Relation Between FNR Service Data Table and Other Data Table
SCCP GT translation table must use the index configured with the command ADD N7DSP.

Before configuring the FNR service, you must collect the data including the country code, The
number prefix of E214, and The number prefix of E212.
Before data configuration, you must collect the data as listed in Table 10-1, Table 10-2, and
Table 10-3.
Table 10-1 The MNP software configuration parameter to be collected
Parameter Name Parameter Value
Country code
Table 10-2 MNP prefix mapping management to be collected
The number prefix of E214
The number prefix of E212

Table 10-3 Service user data to be collected
MSISDN
User IMSI number
HLR address index

You must follow certain procedures to configure the FNR service data.
Table 10-4 lists the steps for configuring the FNR service data.
Table 10-4 Configuration steps
Step Operation
1 To add the HLR address
2 To set the MNP software configuration parameter
3 To add the MNP prefix mapping management
4 To add the service user data
Step 1 must be performed before step 4.

Configuring the FNR service includes setting the HLR address table, and MNP software
parameter and so on.
10.4.1 Adding HLR Address
This section describes the command, parameter, and related commands for adding the HLR
address.
10.4.2 Setting MNP Software Configuration Parameter
This section describes the command, parameter, and related commands for setting the MNP
10.4.3 Setting MNP Prefix Mapping Management
prefix mapping management.
This section describes the command, parameter, and related commands for adding service user
data.


This step is determined according to the actual situations of the current network, and it is not
detailed here.
10.4.1 Adding HLR Address

This section describes the command, parameter, and related commands for adding the HLR
address.
The location area information of mobile terminals in a network is stored in the HLR.
The address numbers of all HLRs in a network must be configured, and subsequently this data
is used through the HLR address index.
The address numbers configured include the address numbers of HLRs used by RN and FN
users.
Command
ADD MNPHLRADDR
Parameters
r ID r Name
ADDR HLR It defines GT codes of an HLR in the operator's network.

Address
number
DPC HLR SPC It specifies the signaling point code of a local HLR. It maps the
international/national active/reserved network code in the DSP
table. HLR SPC must be configured in the DSP table.
Related Commands
Table 10-5 lists the related commands for adding the HLR address.
Command Function
RMV MNPHLRADDR To delete HLR address


Command
SET MNPSOFTCFG
Parameters
r ID r Name
NC Country It defines the country code of an operator's network.

code
MNPMO MNP Set this parameter to FN mode for processing the FNR service.
DE mode
IMSIMO FNR IMSI It can be set to:

DE switch l SWITCH0 (Close)
l SWITCH1 (Open)
It is set to Open when the system processes the IMSI addressing
message.
IMSIMO IMSI It can be set to:

DE match l MODE0 (Full match mode)
mode
l MODE1 (The first 14 code match mode)
It is set to The first 14 code match mode when FNR IMSI
switch is set to Open and the last digits are lost due to extra-long
length of the number during code conversion from E212 to E214.
It is set to Full match mode in any other condition.
HLRIND Default You must only use the default value.

EX HLR
index
Related Commands
Table 10-6 lists the related commands for setting the MNP software configuration parameter.
Command Function
LST MNPSOFTCFG To query the software configuration parameter

10.4.3 Setting MNP Prefix Mapping Management

prefix mapping management.
Command
This table is used to configure the prefix mapping relations between E214 numbers and E212
numbers. This table is used only when E212 numbers cannot be used as the GT codes at the
SCCP layer.
ADD MNPPFXMAP
Parameters
r ID r Name
E214NU E214 It specifies the prefix of an E214 number in the process of number
MPRE number conversion. It cannot exceed 7 digits.
prefix
E212NU E212 It specifies the prefix of an E212 number in the process of number
MPRE number conversion. It cannot exceed 6digits.
prefix
Related Commands
Table 10-7 Related commands for configuring the MNP prefix mapping management
Command Function
ADD MNPPFXMAP To add the MNP prefix mapping management
RMV MNPPFXMAP To remove the MNP prefix mapping management
MOD MNPPFXMAP To modify the MNP prefix mapping management
LST MNPPFXMAP To query the MNP prefix mapping management

This section describes the command, parameter, and related commands for adding service user
data.
This command is used to add information for FN users.
Command
ADD SERUATTR

Parameters
r ID r Name
USRNUM MSISDN It defines the MSISDN number.
IMSINU User IMSI It refers to the international mobile subscriber identity and
M number uniquely identifies a subscriber.
The IMSI number in E212 format must be configured in the case
of addressing based on the IMSI number.

TR enable
related
services
NUMTYP Number This parameter defines the number type. You can set it to FN
E type number .
RNIDXT Route It is set to HLR number index for the FNR service.
YPE index type
HLRIDX HLR It defines the address index of a real HLR.

Address
Index
Related Commands
Table 10-8 lists the related commands for adding the service user data.
Command Function

This step is determined according to the actual situations of the current network, and it is not
detailed here.
For the user whose user data is not configured in the user attribute data table, the equipment
cannot locate the HLR to which the user belongs. Therefore, the equipment transparently
transfers the message to the SCCP layer. In this case, you must configure data in the SCCP GT
translation table to define the default HLR (maximum matching) corresponding to the MSISDN
based on number segments.


This section provides examples to describe how to configure the FNR service data.
The networking for configuring the FNR service is as shown in Figure 10-1, and Figure 10-2.
Data Collection
The data collected for configuring the FNR service is as listed in Table 10-9.
Table 10-9 The MNP software configuration parameter to be collected
Country code 86
Table 10-10 MNP prefix mapping management to be collected
The number prefix of E214 1234
The number prefix of E212 5678
Table 10-11 Service user data to be collected
MSISDN 13678911245
User IMSI number 13678911
HLR address index 0
Procedure
Step 1 Add the HLR address.
To add the HLR address, set HLR address number to 131000 and HLR SPC to B00010, run
ADD MNPHLRADDR: ADDR="131000", DPC="B00010";
Step 2 Set the MNP software configuration parameter.

To set the MNP software configuration parameter, set MNP mode to MNP_FN mode, Country
code to 86, FNR IMSI switch to SWITCH1 (Open) and IMSI match mode to MODE0 (Full
match mode), run the following command:
SET MNPSOFTCFG: MNPMODE=MNPFN, NC="86", FNRSWITH=SWITCH1, IMSIMODE=MODE0;
Step 3 Add MNP prefix mapping management.

To add MNP prefix mapping management,set The number prefix of E214 to 1234, The
number prefix of E212 to 5678,run the following command:
ADD MNPPFXMAP: E214NUMPRE="1234", E212NUMPRE="5678";

To add the service user data, set MSISDN to 13678911245, IMSI number to 13678911,
Whether enable related services to Enable MNP service, Number type to Flexible
number, Route index type to HLR address index, and HLR address index to 0, run the
following command:
ADD SERUATTR: USRNUM="13678911245", IMSINUM="13678911", SERVATTR=OMNP-1,
NUMTYPE=TYPE4, RNIDXTYPE=HLR, HLRIDX=0;
----End
Verifying the HLR Address

This step must be performed after you set the HLR address. To verify the HLR address, run
LST MNPHLRADDR on the MML client.
LST MNPHLRADDR:;

---------------------
Index = 0
HLR Address number = 131000
HLR SPC = B00010
--- END
In the displayed result, HLR address number is 131000and HLR SPC is B00010. The results
are the same as the configured data through the command, which indicates that the configuration
is successful.
Verifying the MNP software configuration parameter

This step must be performed after you set the MNP software configuration parameter. To verify
the MNP software configuration parameter, run LST MNPSOFTCFG on the MML client.
LST MNPSOFTCFG:;

------------------------------------
Message type of MNP service processing =
G_4<OFF>G_3<OFF>G_2<OFF>G_1<ON>

Country code = 86
Local network route number = 0
number amend switch = Close
multi-rn switch = Close
RN fill type = RN+MSIN type
the RN configure parameter of foreign not known ported =
G_8<OFF>G_7<OFF>G_6<OFF>G_5<OFF>G_4<OFF>G_3<OFF>G_2<OFF>G_1<OFF>
the RN configure parameter of local regular user =
G_3<OFF>G_2<OFF>G_1<OFF>
MNP noa parameter =
G_7<OFF>G_6<OFF>G_5<OFF>G_4<OFF>G_3<OFF>G_2<OFF>G_1<OFF>
NoA for non_call related message of own ported out = unknown
NOA of CAP_IDP Called party number = national-
number
NOA of CAP_IDP Called party BCD number = national-
number
NoA of called number of MAP call related message = national-
significant-number
Called NoA of the INAP CONNECT message = National
significant number
NOA OF CALLED NUMBER OF ISUP MESSAGE = subscriber-
number
NOA OF CALLED NUMBER OF MO MESSAGE = national-
number
configuration parameter of SRI_ACK of phase 2 plus =
G_3<OFF>G_2<OFF>G_1<OFF>
Loop_detection = G_1<OFF>
MSC TYPE SWITCH = Close
Unkonwn NP Subscriber Diagnostic Value = 20
SMS Access Denied Reason = 224
MNP QUERY SERVICE KEY = 0
Latency time of the collecting digits(s) = 4
The fresh method of collecting digits timer = for IAM
ATI MODE = SCCP RELAY
SMA switch = close
SMA called process switch = close
FNR IMSI switch = OPEN
IMSI match mode = Full match
mode
Default HLR Index = NULL
Whether processing all E.164 messages in FNR service = Close
--- END
In the displayed result, MNP mode to MNP_FN mode, Country code to 86, FNR IMSI
switch to SWITCH1 (Open) and IMSI match mode to MODE0 (Full match mode). The
results are the same as the configured data through the command, which indicates that the
Verifying the MNP prefix mapping management

This step must be performed after you set the MNP prefix mapping management. To verify the
the MNP prefix mapping management, run LST MNPPFXMAP on the MML client.
LST MNPPFXMAP: IDX=0;

MNP prefix mapping management
----------------

Index = 0
The number prefix of E214 = 1234
The number prefix of E212 = 5678
--- END
In the displayed result, The number prefix of E214 to 1234, The number prefix of E212 to
5678. The results are the same as the configured data through the command, which indicates

This step must be performed after you set the service user data. To verify the service user data,

---------------------------------
Index = 0
MSISDN = 13678911245
G_6<OFF>G_5<OFF>G_4<OFF>G_3<OFF>G_2<ON>G_1<OFF>
Number type = Flexible Number
--- END
In the displayed result, MSISDN to 13678911245, IMSI number to 13678911, Whether

enable related services to Enable MNP service, Number type to Flexible number, Route
index type to HLR address index, and HLR address index to 0. The results are the same as
the configured data through the command, which indicates that the configuration is successful.

Feature Description 11 Configuring SMI Service Data
11 Configuring SMI Service Data
About This Chapter
This chapter tells how to configure the short message interception (SMI) service data. Before
configuring the SMI service data, make sure that the hardware data, MTP data, and SCCP data
are configured.
11.1 SMI Service
The short message service (SMS) is a popular value-added service. It brings convenience to
users and profits to network operators. The SMS can also be used to perform illegal activities
and send junk messages, thus bringing inconvenience to users.
11.2 Service Flow
This section describes the networking structure, implementation, and equipment cooperation
requirements of the SMI service.
11.4 Configuring SMI Service Data
This section describes the command, parameter, and related commands for configuring the SMI
service data.
This section provides examples to describe how to configure the SMI service data.

11 Configuring SMI Service Data Feature Description
11.1 SMI Service

The short message service (SMS) is a popular value-added service. It brings convenience to
users and profits to network operators. The SMS can also be used to perform illegal activities
and send junk messages, thus bringing inconvenience to users.
The SMI service is designed to prevent illegal activities and junk messages from reaching the
users. Through checking and monitoring messages, some illegal contents or junk messages are
filtered.
Advantages of implementing the SMI service are as follows:
l To users: avoiding inconvenience and antipathy brought by junk messages
l To network operators: providing customized and differentiated services, implementing
social responsibilities, and winning excellent branding effect
The SMI service can only affect messages sent from the non-local users to the local users or to
the users who have roamed from other areas to the local area. When a local user roams to a non-
local area, the messages sent to this user will not be intercepted.
In the SMI service, the SG forwards the messages to the local SMSC that has the SMI function.
Then the SMSC checks and filters the messages.
11.2 Service Flow

requirements of the SMI service.
This section describes the networking structure for configuring the SMI service data.
This section describes the device cooperation requirements in the typical networking structure
of the MC service.
This section describes the implementation of the SMI service on the SG7000.

This section describes the networking structure for configuring the SMI service data.
The SMI service has different networking modes; the typical one is as shown in Figure 11-1.

Figure 11-1 A typical SMI service networking structure
HSTP: High-level signaling Transfer LSTP: Low Level Signalling MSC: Mobile Switching Center
Point Transfer Point
SMSC:Short Message Service Center SG: U-SYS SG7000 Signaling
Gateway
The devices in the networking structure and their functions are as follows:
l HSTP: It is used to forward messages in the MSC-ID addressing mode to the SG.
l LSTP: It is used to forward local signaling messages.
l SG: It is used to process and forward signaling messages between network devices. It also
forwards MT messages from the HSTP to the local SMSC for processing.
l MSC: It is used to send short messages.
l SMSC: It is used to intercept and filter messages.

This section describes the device cooperation requirements in the typical networking structure
of the MC service.
According to the networking mode, device coordination is as follows:
l The GT translation data of the MSC-Number must be configured on the HSTP. After GT
translation, the message must be forwarded to the SG.
l The local MTP3 transfer data must be configured on the LSTP.
l The GT translation data of the MSC-Number must be configured on the SG. After GT
translation, the message must be forwarded to the MSC.

l The MTP3 route to the local MSC must be configured on the SG.
Different networking modes have different device coordination requirements.

This section describes the implementation of the SMI service on the SG7000.
The SMI service is implemented as follows:
l A non-local SMSC sends an MT message to a local user or a user who has roamed from a
non-local area to the local area.
l The HSTP identifies that the message is addressed, based on the MSC-Number and then
performs GT translation according to the modified route data to forward the message to the
SG.
l The SG identifies that the message is an MT message and then forwards it to the local
SMSC that has the SMI function.
l If the SMSC identifies that the message is a junk message through the monitoring system,
it imitates the mobile station (MS) to return a message to the non-local SMSC, indicating
the message is successfully received.
l If the SMSC identifies that the message is a normal message, it forwards the MT message
to the destination MSC through the LSTP. Then the destination MSC forwards the message
to the MS.
l The destination MSC returns a message to the local SMSC through the LSTP, indicating
that the MS has successfully received the message.
l The local SMSC sends a message to the non-local SMSC, indicating that the MS has
successfully received the message.

This section describes the relations between data tables related to SMI service data configuration.
Before configuring the SMI service, you must collect the data including the interception mode
and DSP index.
You must follow certain procedures to configure the SMI service data.

This section describes the relations between data tables related to SMI service data configuration.
Relation Between SMI Service Data Tables

The SMI service has one command only, so there is no reference relation between internal data
tables.

Relation Between SMI Service Data Table and Other Data Table
The index configured in ADD N7DSP is referenced by the index in SET SMSICSOFTCFG.
It is the index of the local SMSC that has the SMI function.

Before configuring the SMI service, you must collect the data including the interception mode
and DSP index.
Table 11-1 lists the data to be collected before data configuration.

Intercept MT mode DSP index

You must follow certain procedures to configure the SMI service data.
Table 11-2 lists the step to configure the SMI service data.

Step Action
1 To configure SMI service data
11.4 Configuring SMI Service Data

This section describes the command, parameter, and related commands for configuring the SMI
service data.
Command
SET SMSICSOFTCFG
Parameters
r ID r Name
INTERM Service It specifies an MT mode.

ODE type
DSPINDE DSP index It is the index of the local SMSC that has the SMI function.
X

Related Commands
Table 11-3 Related commands for configuring the SMS intercept configuration
Command Function
SET SMSICSOFTCFG To set SMS intercept configuration
LST SMSICSOFTCFG To query SMS intercept configuration

This section provides examples to describe how to configure the SMI service data.
The networking for configuring the protocol translation service is as shown in Figure 11-1.
Data Collection
The data collected for configuring the protocol translation service is as listed in Table 11-4.

Intercept MT mode DSP index
MT mode 1
Procedure
Step 1 Set the SMI service data.
To set the SMI service data, set Service type to MT mode and DPS index to 1, run the following
command:
SET SMSICSOFTCFG: INTERMODE=MODE0, DSPINDEX=1;
----End
Verifying the SMI Service Data

This step must be performed after you set the SMI service data. To verify the SMI service data,
run LST SMSICSOFTCFG on the MML client.
LST SMSICSOFTCFG:;

-----------------------
IN filter type = G_3<OFF>G_2<OFF>G_1<OFF>

Country Code = 86
Mode of relaying message = Global translate
Service type = MT mode
Dsp index = 1
--- END
In the displayed result, Service type is MT mode, DPS index is 1, and the values of other
parameters are the default values. The results are the same as the configured data through the
command, which indicates that the configuration is successful.

Feature Description 12 Configuring CDMA and GSM MNP Service Data
12 Configuring CDMA and GSM MNP

Service Data
About This Chapter
This chapter describes the mobile number portability (MNP) service. A user registered with the
MNP service can move from one subscribed network to another without changing the original
mobile station international ISDN number (MSISDN). Before configuring the MNP service data,
make sure that the hardware data, MTP data, SCCP data, and M3UA data are already configured.
12.1 Overview
This section describes the service definition, service advantages, and terms used when
configuring the service.
12.2 Service Flow
requirements of the CDMA and GSM MNP service.
Configuring the CDMA and GSM MNP service includes setting the MNP software parameter,
configuring the HLR address, and configuring the MNP routing number.
This section provides examples to describe how to configure the CDMA and GSM MNP service
data.

12 Configuring CDMA and GSM MNP Service Data Feature Description
12.1 Overview
This section describes the service definition, service advantages, and terms used when
configuring the service.
12.1.1 MNP Service
The MNP service enables a user to transfer from one subscribed network to another without
changing the original MSISDN.
12.1.2 Purpose of Configuring CDMA and GSM MNP Service Data
After the MNP service data is configured for the CDMA network (C network for short) and the
GSM network (G network for short) that are owned by the same network operator, users can
freely choose a network without affecting the current services.
12.1.3 Terms
This section describes the terms used during configuring the CDMA and GSM MNP service
data.
12.1.4 MNP Service Advantages
This section describes the advantages of the CDMA and GSM MNP service.
12.1.5 MNP Service Features
This section describes the features of the CDMA and GSM MNP service.
The MNP service is provided in V200R001 and later versions.
12.1.1 MNP Service

The MNP service enables a user to transfer from one subscribed network to another without
changing the original MSISDN.
After the transfer, the newly subscribed network allocates a new IMSI (SIM) to this MNP user.
All services of the MNP user are provided by the newly subscribed network and not affected by
the original network. In a same subscribed network, there is no difference in service provision
between the MNP users and non-MNP users. However, in service quality there is a little
difference, for example, supplementary call setup delay.
12.1.2 Purpose of Configuring CDMA and GSM MNP Service Data

After the MNP service data is configured for the CDMA network (C network for short) and the
GSM network (G network for short) that are owned by the same network operator, users can
freely choose a network without affecting the current services.
12.1.3 Terms
This section describes the terms used during configuring the CDMA and GSM MNP service
data.
C network
It is short for the CDMA network.

G network
It is short for the GSM/WCDMA network.
Local network
It refers to the network that is owned by a network operator. A network operator can own multiple
local networks.
MNP
The MNP function is the number portability (NP) function of mobile numbers. The MSISDN
of an MNP user need not be changed when the user transfers out of a network. A new international
mobile subscriber identity (IMSI) is allocated to an NP user when the user transfers into a
network.
The MNP function of the SG complies with the ETSI GSM 03.66 standard and implements some
functions of the MNP-SRF (MNP function entity) and the NPDB function defined in the
standard. The SG implements the following functions:
l MNP function of call-related and non-call-related services in the GSM network
This function enables a user to reserve the MSISDNs when the user transfers into a foreign
network. After the transfer, the user enjoys the same services (including supplementary
services and value-added services) provided by the newly subscribed network as other
users. These services are not affected by the previous network.
l MNP function among HLRs managed by a same network operator
This function enables users to flexibly change their home locations without changing their
MSISDNs.
MSISDN
Each mobile station (MS) has two numbers. One is the directory number opened to the public,
that is the MSISDN; the other is provided by the network operator to uniquely identify an MS,
that is IMSI.
MDN
A mobile directory number (MDN) is a CDMA number that can be directly dialed. An MDN
has the same function as an MSISDN in the GSM network.
IMSI
An IMSI uniquely identifies an MS. An IMSI consists of three parts:
The IMSI enables the network operator to identify an MS, search for the address of an MS, and
authenticate an MS. When an MS is registered, it will be allocated with both the MSISDN and
the IMSI. After registering the MNP service, a user can transfer into a foreign network without
changing the MSISDN. The newly subscribed network operator will allocate a new IMSI to the
user.

12.1.4 MNP Service Advantages

This section describes the advantages of the CDMA and GSM MNP service.
To network operators
l The MNP service enables network operators to attract users. Thus, the extra management
fee is added and operation income is increased.
l The MNP service ensures a balanced competition of number resources among network
operators.
l The MNP service promotes network operators to improve network performance and service
quality.
l Under the coexistence of the C and G networks, users can transfer from one network to the
other regardless of network types. Thus, it is very easy to abolish the fruitless network.
To users
The MNP service enables users to choose proper networks and services according to the locations
without changing the original MSISDNs. Especially, a user can choose any network among those
that are run by a same network operator in different locations without changing the original
MSISDN. For example, a user is registered in city A with the number belonging to the number
range of city A. When moved to city B, this user can be registered in city B without changing
the original MSISDN.
12.1.5 MNP Service Features

This section describes the features of the CDMA and GSM MNP service.
The features of the MNP service are as follows:
l Portable MSISDN: When transferring from one network to another, or moving from one
location to another, a user need not change the MSISDN.
l Independent service subscription: The services provided by a newly subscribed network
will not be affected by the original network. If the newly subscribed network does not
support the services that are provided by the original network, it does not provide these
services to users.
l Repeated portability: The MSISDNs can be brought out of a network as well as brought
in. The same MSISDN can be registered and deregistered repeatedly in a same network.
l Independent service: The MNP service does not conflict with mobile services.
l The MNP service supports the ATI message query interface.
l The MNP service supports the authentication by short messages.
According to the actual networking modes and applications, the service flow and data
configuration of the MNP service are different. This document complies with the standards
specified in the ETSI 03.66 protocol.

The MNP service is provided in V200R001 and later versions.
There is no requirement for the hardware.

12.2 Service Flow

requirements of the CDMA and GSM MNP service.
This section describes the networking structure for configuring the CDMA and GSM MNP
service data.
This section describes the implementation of the CDMA and GSM MNP service.
12.2.3 Calling Flow
This section describes the calling flow of the CDMA and GSM MNP service.
This section describes the device cooperation requirements of the CDMA and GSM MNP
service.
12.2.5 Service Interaction
This section describes the impact of the CDMA and GSM MNP service on IN services and
supplementary services.

This section describes the networking structure for configuring the CDMA and GSM MNP
service data.
Figure 12-1 shows the networking structure of the MNP service in the C network and the G
network.

Figure 12-1 Networking structure of CDMA and GSM MNP service
C network: CDMA network G network: GSM/WCDMA SG: U-SYS SG7000 Signaling

network Gateway
HLR: home location register GMSC: gateway mobile switching SMSC: short message service center
center
SMSC GW: SMSC gateway VMSC: visited mobile switching
center
In the networking of the MNP service in the C network and the G network, the SG acts as the
public MNP-SRF (signaling relay function) and the NPDB (number portability database).
Logically, the SG is located before the HLR. The SGs are configured in pairs.

This section describes the implementation of the CDMA and GSM MNP service.
To implement the MNP service, two devices should be added:
l MNP-SRF: It forwards all call-related and non-call-related signaling messages between the
HLR, SCP and other NEs. It is located between the other NEs and the HLR. It can be used
independently or combined with the LSTP.
l NPDB: It stores the data of all portable numbers.
If a user is registered with the MNP service, an NE cannot judge the HLR of a user through the
MSISDN. The implementation of the MNP service is as follows:
1. A message that is sent from an NE to the HLR is sent to the MNP-SRF first.
2. The MNP-SRF queries the NPDB according to the MSISDN to find the actual HLR of the
user.

3. The MNP-SRF forwards the message according to the query result.

In this way, the message sent to a number portability (NP) user is forwarded to the correct HLR,
and thus the MNP service is implemented.
12.2.3 Calling Flow

This section describes the calling flow of the CDMA and GSM MNP service.
The MNP service processing flows are classified into the following types.
A CDMA User Calls a CDMA User
Figure 12-2 Flow of a CDMA user calling a CDMA user
When a CDMA user calls a CDMA user, the calling flow is as follows:
1. The caller initiates a call. The calling VMSC sends the LOCREQ message to the HLR to
query the location of the callee. The message contains the MDN of the callee.
2. When the message is sent to the SG. The SG queries user information in the NPDB
according to the MDN in the message.
3. When the SG finds that the callee is a user in the local CDMA network, it sends the
LOCREQ message to the HLR.
4. The HLR returns the LOCREQ message to the calling VMSC. The message contains the
temporary local directory number (TLDN).
5. The calling VMSC sends the IAM to the called VMSC. The message contains the called
mobile subscriber routing number (MSRN).
The subsequent flow is irrelevant to the SG.

A CDMA User Calls a GSM User
Figure 12-3 Flow of a CDMA user calling a GSM user
When a CDMA user calls a GSM user, the calling flow is as follows:
1. The caller initiates a call. The calling VMSC sends the LOCREQ message to the SG to
query the location of the callee. The message contains the MDN of the callee.
2. The SG queries user information in its database according to the MDN in the message.
When the SG finds that the callee is a user in the GSM network, it returns the LOCREQ
message to the calling VMSC. The message contains "RN+MDN" of the callee.
3. The calling VMSC sends an IAM to the calling GMSC after number analysis. The message
contains "RN+MDN" of the callee.
4. The calling GMSC removes the RN and send the IAM to the called GMSC. The message
contains the called MDN.
5. The called GMSC sends the SRI message to the SG to query the location of the callee. The
6. The SG queries user information in the NPDB according to the MSISDN in the message.
When the SG finds that the callee is a user in the local GSM network, it sends the SRI
message to the called HLR to query the user information.
7. The called HLR returns the SRI ack message to the called GMSC. The message contains
the called MSRN.
8. The called GMSC sends the IAM to the called VMSC. The message contains the called
MSRN.

A GSM User Calls a GSM User
Figure 12-4 Flow of a GSM user calling a GSM user
When a GSM user calls a GSM user, the calling flow is as follows:
1. The caller initiates a call. The calling VMSC sends the SRI message to the HLR to query
the location of the callee. The message contains the MSISDN of the callee.
2. When the message is sent to the SG. The SG queries user information in the NPDB
according to the MSISDN in the message.
3. When the SG finds that the callee is a user in the local GSM network, it forwards the SRI
message to the HLR.
4. The HLR returns the SRI ack message to the calling VMSC. The message contains the
called MSRN.
5. The calling VMSC sends the IAM to the called VMSC. The message contains the called
MSRN.

A GSM User Calls a CDMA User
Figure 12-5 Flow of a GSM user calling a CDMA user
When a GSM user calls a CDMA user, the calling flow is as follows:
1. The caller initiates a call. The calling VMSC sends the SRI message to the HLR to query
the location of the callee. The message contains the MSISDN of the callee.
2. The SG queries user information in its database according to the MSISDN in the message.
When the SG finds that the callee is a user in the local CDMA network, it returns the SRI
ack message to the SG. The message contains "RN+MSISDN" of the callee.
3. The calling VMSC sends an IAM to the calling GMSC after number analysis. The message
contains "RN+MSISDN" of the callee.
4. The calling GMSC removes the RN and send the IAM to the called GMSC. The message
contains the called MSISDN.
5. The called GMSC sends the LOCREQ message to the SG to query the location of the callee.
The message contains the called MDN.
6. The SG queries user information in the NPDB according to the MDN in the message. When
the SG finds that the callee is a user in the local CDMA network, it sends the LOCREQ
message to the called HLR to query the user information.
7. The called HLR returns the LOCREQ message to the called GMSC. The message contains
the called TLDN.
8. The called GMSC sends the IAM to the called VMSC. The message contains the called
TLDN.

Querying the NPDB in the CDMA Network by the NPREQ Message
Figure 12-6 Flow of querying the NPDB in the CDMA network by the NPREQ message
MSC SG
NPREQ(DGTSDIAL)
npreq(ROUTDGTS)
When querying the NPDB in the CDMA network by the NPREQ message, the call flow is as
follows:
1. The caller initiates a call. The calling MSC sends an NPREQ message to the NPDB to query
the subscriber status.
2. After receiving the NPREQ message, the SG (acting as the NPDB) checks whether the
NPREQ message processing switch is enabled.
l If yes, the SG decodes the NPREQ message.
– If the NPREQ message does not contain the DGTSDIAL parameter, the SG returns
the ERROR message.
– If the SG successfully decodes the NPREQ message and obtains the number, it
continues with 3.
l If not, the SG transparently forwards the message.
3. The SG queries the subscriber NP status through the DGTSDIAL parameter.
l When finding that no NP occurs on the subscriber, the SG returns the npreq message
without containing the ROUTDGTS information element.
l When finding that NP occurs on the subscriber, the SG obtains the corresponding routing
number and adds the routing number to the ROUTDGTS information element. After
that, the SG returns the npreq message to the MSC.

This section describes the device cooperation requirements of the CDMA and GSM MNP
service.
Network Requirements
The network requirements are as follows:
l The IAM supports the routing number (RN).

l The data that is negotiated with another network in the NP domain is required, that is, the
RN. An RN cannot be the number prefix.
Data Coordination Between Network Devices

The requirements are made based on the actual networking structure.

This section describes the impact of the CDMA and GSM MNP service on IN services and
supplementary services.
Impact on IN Services
This service does not affect the IN services.
Impact on Supplementary Services

This service does not affect the supplementary services.

You must follow certain principles to configure the CDMA and GSM MNP service data.
This section describes the relations between data tables related to CDMA and GSM MNP service
data configuration.
Before configuring the CDMA and GSM MNP service, you must collect the data including the
MNP working mode, SMS access denied reason, and unknown NP subscriber diagnostic value.
You must follow certain procedures to configure the CDMA and GSM MNP service data.

You must follow certain principles to configure the CDMA and GSM MNP service data.
Number Type
The MNP service between the CDMA and the GSM network concerns the following four types
of numbers:
l GSM number ported to CDMA: It refers to a number ported from the local GSM network
to the local CDMA network.
l CDMA number ported to GSM: It refers to a number ported from the local CDMA network
to the local GSM network.
l GSM FN number: It refers to a number belonging to the FN and the local GSM network.

l CDMA FN number: It refers to a number belonging to the FN and the local CDMA network.
GSM Number Ported to CDMA

l Add HLR address
This command is used to configure the DPC mapping the HLR in the CDMA network.
Command: ADD MNPHLRADDR
l Add MNP route number
This command is used to configure the route number mapping the user number in the MNP
route number table.
Command: ADD MNPROUTENUM
l Add service user data
This command is used to port a CDMA number to the GSM network through data
configuration. That is to say, set Number type to GSM number ported to CDMA.
Command: ADD SERUATTR
CDMA Number Ported to GSM

l Add HLR address
This command is used to configure the DPC mapping the HLR in the GSM network.
route number table.
This command is used to port a GSM number to the CDMA network through data
configuration. That is to say, set Number type to CDMA number ported to GSM.
GSM FN
l Add HLR address
This command is used to configure the DPC mapping the HLR in the GSM network.
route number table.
l Add MNP local network number range
This command is used to add the number range that belongs to the local GSM network.
Command: ADD MNPLOCNRNG
This command is used to add the data of the service user belonging to the FN.

CDMA FN
l Add HLR address
This command is used to configure the DPC mapping the HLR in the CDMA network.
route number table.
l Add MNP local network number range
This command is used to add the number range that belongs to the local CDMA network.
Command: ADD MNPLOCNRNG
This command is used to add the data of the service user belonging to the FN.

This section describes the relations between data tables related to CDMA and GSM MNP service
data configuration.
Relations Between MNP Data Tables

Figure 12-7 shows the relations between MNP data tables.

Figure 12-7 Relations between MNP service data tables
NOTE
When configuring the DSP information with ADD N7DSP, the network code can be set to:
l International network code
l International reserved network code
l National network code
l National reserved network code

Internal Reference Relations of MNP Data

The internal reference relations of the MNP data are as follows:
l The value of Route number index defined in the MNP foreign number range table
references the value of Index defined in the MNP route number table. The index indicates
the number of the route directed to a foreign network. When the system cannot find the
user in the service data table, it queries the MNP foreign number range table to get the route
number and then re-construct the message.
l The value of Route number index defined in the MNP local network number range table
references the value of Index defined in the MNP route number table. When the system
cannot find the user in the MNP foreign number range table, it queries the MNP local
network number range table. If the user belongs to the GSM network, the system gets the
route number index from the MNP local network number range table and then re-constructs
the message.
l The value of Route number index defined in the MNP local network number range table
references the value of HLR address index defined in the MNP address attribute table.
When the system cannot find the user in the MNP foreign number range table, it queries
the MNP local network number range table. If the user belongs to the CDMA network, the
system gets the HLR address index from the MNP local network number range table and
then re-constructs the message.
l During the configuration of service user data, if Route index type is set to HLR number
index, the value of NP route index references the HLR address index. If Route index
type is set to Route number index, the value of NP route index references the MNP route
number index.
l During the configuration of the MNP software parameter table, Called NoA of the INAP
CONNECT message is valid only when MNP parameter is set to Indicator of modifying
the called NoA of the INAP message.
Reference Relations Between MNP Data and Other Data

SCCP GT translation table needs to use the DSP index configured with ADD N7DSP.

Before configuring the CDMA and GSM MNP service, you must collect the data including the
MNP working mode, SMS access denied reason, and unknown NP subscriber diagnostic value.
Before data configuration, you need to collect the data as listed in Table 12-1 and Table 12-2.
Table 12-1 Local office information data table

MNP mode SMS access denied reason Unknown NP subscriber
diagnostic value

Table 12-2 User information data table

Min foreign Max foreign Start local network End local network
number number number number
MSISDN Number type MNP route number HLR address number

You must follow certain procedures to configure the CDMA and GSM MNP service data.
Table 12-3 lists the general steps of configuring the MNP service data.
Table 12-3 Steps of configuring the MNP service data

Step Operation
1 To set the software configuration parameter
2 To set the MNP software configuration parameter
3 To configure the HLR address
4 To configure the MNP route number
5 To configure the MNP local network number range
6 To configure the MNP foreign number range
7 To configure the MNP service user data
Configuration sequence requirements are as follows:

l Configure the MNP route number table before configuring the MNP foreign number range
table and the service user data table.
l Configure the HLR address table before configuring the service user data table.
Here are two examples.

Example 1: Add an MNP service user.
Carry out the operations according to the following order: add an HLR address > add an MNP
route number > add the MNP local network number range > add the MNP foreign number range
> add the service user data.
Example 2: Remove an HLR address.
Carry out the operations according to the following order: remove the service user data that
references this HLR address > remove the HLR address.


Configuring the CDMA and GSM MNP service includes setting the MNP software parameter,
configuring the HLR address, and configuring the MNP routing number.
12.4.1 Setting Software Configuration Parameter
This section describes the command, parameter, and related commands for setting the software
configuration parameter.
12.4.3 Configuring HLR Address
12.4.4 Configuring MNP Route Number
12.4.5 Configuring MNP Local Network Number Range
local network number range.
12.4.6 Configuring MNP Foreign Number Range
foreign number range.
12.4.7 Configuring Service User Data
service user data.
This section describes the command, parameter, and related commands for setting the SCCP GT
translation table.
12.4.1 Setting Software Configuration Parameter

This section describes the command, parameter, and related commands for setting the software
configuration parameter.
This command is used to set the types of various messages supported by the MNP service.
Command
SET SOFTCFG

Parameters
r ID r Name
DPCQUE CDMA It determines the addressing mode for call-related messages and
RY message short messages. When it is enabled, it indicates that the SG can
routing on process the LOCREQ message which is performed DPC
DPC in addressing and terminated on the SG.
self PC
processed
by MNP
DPCPRO CDMA It determines the addressing mode for call-related messages and
CESS message short messages. When it is enabled, it indicates that the SG can
routing on process the LOCREQ message which is performed DPC
DPC not addressing and is not terminated on the SG.
in self PC
processed
by MNP
DPCSEA CDMA It determines the addressing mode for call-related messages and
RCHMSG message short messages. When it is enabled, it indicates that the SG can
routing on process the LOCREQ message which is performed GT addressing.
GT
processed
by MNP
Other parameters are irrelevant to the MNP service of the CDMA and GSM networks. In this
case, keep the default values for them.
Related Commands
Command Function

Command
SET MNPSOFTCFG

Parameters
r ID r Name
MNPMO MNP It can be set to:

DE mode l FN mode: It refers to the flexible number routing mode, that is,
the intra-carrier NP. It is selected when the service user is
required to be set to the NN or RN user.
l MNP-FN mode: It refers to the complete processing mode,
including the intra-carrier and inter-carrier NP. It complies with
the 3GPP 23066 protocol. It is selected when the service user is
required to be set to the user type other than the NN or RN user
type.
l Reserve: It means the reserved processing mode. You cannot
choose this mode.
It is set to MNP-FN mode here.
SMSACC SMS It is an error code sent to the user when the SG fails to send a short
DNYRSN access message to a CDMA user. This error code indicates that the user
denied to which the short message should be routed does not exist. The
reason data configured on the SG must be consistent with that configured
on the SMSC.
UNKSUB Unknown It is an error code sent to the user when the SG fails to send a short
DIGVAL NP message to a GSM user. This error code indicates that the user to
subscriber which the short message should be routed does not exist. The data
diagnostic configured on the SG must be consistent with that configured on
value the SMSC.
Other parameters are irrelevant to the MNP service of the CDMA and GSM networks. In this
case, keep the default values for them.
Related Commands
Command Function
LST MNPSOFTCFG To query the MNP software configuration parameter
12.4.3 Configuring HLR Address


Command
ADD MNPHLRADDR
Parameters
r ID r Name
ADDR HLR It specifies the GT address of the HLR in the local network.
address
number
DPC HLR SPC It maps any of the following:

l International network code
l International reserved network code
l National network code
l National reserved network code
It must be the configured and valid data. You can query the DPC
through LST N7DSP. After obtaining the DPC, enter the
corresponding data.
Related Commands

Command Function
RMV MNPHLRADDR To remove HLR address
12.4.4 Configuring MNP Route Number

Command
ADD MNPROUTENUM

Parameters
r ID r Name
NUM Route It specifies the route number of the peer network to which a user
number number belongs. The value must be consistent with that set on the
device of the peer network.
IMSICD IMSI It maps the IMSI number of the peer network. It should be of E.
number 212 format. It can be set flexibly. The recommended format is:
MCC + MNC of the peer network.
Related Commands
Table 12-7 Related commands for configuring the MNP route number
Command Function
ADD MNPROUTENUM To add MNP route number
MOD MNPROUTENUM To modify MNP route number
RMV MNPROUTENUM To remove MNP route number
LST MNPROUTENUM To query MNP route number
12.4.5 Configuring MNP Local Network Number Range

local network number range.
When a user number cannot be found in the service user data table and the MNP foreign number
range table, the system needs to query the MNP local network number range table to obtain the
route number, and then correctly routes the messages to the corresponding network.
Command
ADD MNPLOCNRNG

Parameters
r ID r Name
NUMTYP Number It indicates the network type to which an MNP local network
E range type number range belongs. It can be set to:
l G (GSM network number range): It indicates that the number
range belongs to the GSM network.
l C (CDMA network number range): It indicates that the number
range belongs to the CDMA network.
It is configured based on the actual conditions.
STARTN Start local They specify the number range of a local network.
UM network This number range cannot be repeated, overlapped, and over-
number crossed.
ENDNU End local
M network
number
number route directed to the local network.
index
HLRIDX HLR It indicates the HLR address corresponding to the local network
address and it maps a record in the MNP HLR address table.
index
Related Commands
Table 12-8 Related commands for configuring the MNP local network number range
Command Function
ADD MNPLOCNRNG To add MNP local network number range
MOD MNPLOCNRNG To modify MNP local network number range
RMV MNPLOCNRNG To remove MNP local network number range
LST MNPLOCNRNG To query MNP local network number range
12.4.6 Configuring MNP Foreign Number Range

foreign number range.
When a user number cannot be found in the service user data table, the system needs to query
the MNP foreign number range table to obtain the route number, and then correctly routes the
messages to the corresponding network.

Command
ADD MNPFRGNRNG
Parameters
r ID r Name
MINNUM Min They specify the number range of a foreign network.

foreign This number range cannot be repeated, overlapped, and over-
number crossed.
MAXNU Max
M foreign
number
number route directed to the foreign network.
index
Related Commands
Table 12-9 Related commands for configuring the MNP foreign number range
Command Function
ADD MNPFRGNRNG To add MNP foreign number range
MOD MNPFRGNRNG To modify MNP foreign number range
RMV MNPFRGNRNG To remove MNP foreign number range
LST MNPFRGNRNG To query MNP foreign number range
12.4.7 Configuring Service User Data

service user data.
Command
ADD SERUATTR

Parameters
r ID r Name
USRNUM MSISDN It specifies the logical number of an MS. It carries no country code,
for example, 13X12345678.

TR enable
related
services
NUMTYP Number It specifies the type of an MNP user. It can be set to An own
E type number not ported out, An own number ported out, A foreign
number ported in, A foreign number ported to a foreign
network, GSM number ported to CDMA, or CDMA number
ported to GSM. It is set to An own number not ported out by
default. Keep other parameters unchanged.
RNIDXT Route It specifies the index type of the user-mapped route. It can be set
YPE index type to:
l HLR (HLR address index): The value for TYPE0 (In local
network), TYPE2 (Moved in from external network),
TYPE4 (flexible number), and TYPE6 (NN number) is HLR
(HLR number index).
l RN (Route number index): The value for TYPE1 (Moved out
of local network) and TYPE3 (Moved to another non-local
network number) is RN (Route number index).
l ALL (HLR+RN): The value for TYPE5 (GSM number ported
to CDMA), TYPE7 (RN number), TYPE8 (CDMA number
ported to GSM) is ALL (HLR+RN).
l TIME (Filter time segment index): It is selected when the
prepaid premium service is enabled.
It must be configured based on the actual conditions.
RNIDX NP route It is configured when Route index type is set to Route number
index index and Route number index is not configured or configured
to the same value as this parameter. NP route index must be a valid
value. It must be set based on the actual conditions.
HLRIDX HLR It is set when Route index type is set to HLR number index or
address ALL. It must be a valid index existing in the MNP HLR address
index table.
RNIDX2 Route It is set when Route index type is set to ALL and NP route
number index is not configured. It must be a valid index existing in the
index MNP route number table.

Related Commands
Command Function
RMV SERUATTR To remove service user data

This section describes the command, parameter, and related commands for setting the SCCP GT
translation table.
Configure the following data on the SG:
l Local HLR address and translation type: DPC + SSN. The DPC is that of the local HLR.
l Foreign RN and translation type: DPC + GT. The DPC is that of a foreign HLR.
l Local GMSC address and translation type: DPC + SSN. The DPC is that of the local GMSC.
For details, see Configuring SCCP Data.

This section provides examples to describe how to configure the CDMA and GSM MNP service
data.
These examples are only related to the PLMN networking structure. Figure 12-1 shows the
PLMN networking structure with the MNP service.
Data Collection
Table 12-11 and Table 12-12 list the MNP data that is collected.
Table 12-11 Local office information collection table
MNP mode SMS access denied reason Unknown NP subscriber

diagnostic value
MNP-FN mode 224 20

Table 12-12 User data collection table
Min foreign Max foreign number Start local End local network
number network number
number
1339860 1339861 1339858 1339859
MSISDN Number type MSISDN Number type
13398580000 GSM number ported to 13398580001 FN number

CDMA
MSISDN Number type MNP route HLR address number

number
13398585859 CDMA number ported 23 1111

to GSM
Procedure
Step 1 Set CDMA Message Processing Switch
To enable the switch to support the processing of all types of CDMA messages, execute the
following command:
SET SOFTCFG: DPCQUERY=BIT0-1&BIT1-1, DPCPROCESS=BIT0-1&BIT1-1,
DPCSEARCHMSG=BIT0-1&BIT1-1;
Step 2 Set MNP Service Switch
To set MNP service switch, set MNP mode to MNP-FN mode, SMS access denied reason to
224, and Unknown NP subscriber diagnostic value to 20, execute the following command:
SET MNPSOFTCFG: MNPMODE=MNPFN, SMSACCDNYRSN=224, UNKSUBDIGVAL=20;
Step 3 Add HLR Address Number
To add an HLR address number, set HLR SPC to bbbbbb and HLR address number to
1111, execute the following command:
ADD MNPHLRADDR: DESC="JK TEXT", ADDR="1111", DPC="bbbbbb";
Step 4 Add MNP Route Number
To add a route number, set IMSI to 132132 and Route number to 23, execute the following
command:
ADD MNPROUTENUM: DESC="Jktest", NUM="23", IMSICD="132132";
Step 5 Add MNP Local Network Number Range
To add an MNP local network number range, set Number range type to C, Start local network
number to 1339858, End local network number to 1339859, Route number index to 3, and
HLR address index to 3, execute the following command:
ADD MNPLOCNRNG: DESC="Jktest", NUMTYPE=C, STARTNUM="1339858",
ENDNUM="1339859", RNIDX=3, HLRIDX=3;

Step 6 Add MNP Foreign Number Range

To add an MNP foreign number range, set Min foreign number to 1339860, Max foreign
number to 1339861, and Route number index to 2, execute the following command:
ADD MNPFRGNRNG: DESC="Jktest", MINNUM="1339860", MAXNUM="1339861",
RNIDX=2;
Step 7 Configure MNP Service User Data

1. Set GSM number ported to CDMA
To set MSISDN to 13398580000, Whether enable related services to Enable MNP
service, Number type to GSM number ported to CDMA, Route index type to All (HLR
+RN), HLR address index to 1, and NP route index to 1, execute the following command:
RNIDXTYPE=ALL, HLRIDX=1;
2. Set CDMA number ported to GSM
service, Number type to CDMA number ported to GSM, Route index type to All (HLR
+RN), HLR address index to 3, and NP route index to 3, execute the following command:
RNIDXTYPE=ALL, HLRIDX=3, RNIDX2=3;
3. Set local network FN user
service, Number type to Flexible number, Route index type to HLR number index,
and HLR address index to 1, execute the following command:
RNIDXTYPE=HLR, HLRIDX=1;
NOTE
The attribute of an FN user is determined by the MNP local network number range table. If the FN
configured in the table belongs to the CDMA number range, you need to configure the user to the
CDMA FN user. If the FN configured in the table belongs to the GSM number range, you need to
configure the user to the GSM FN user.
----End
Verifying CDMA Message Processing Switch

This step must be performed after you set the CDMA message processing switch. To verify the
CDMA message processing switch, run LST SOFTCFG on the MML client.
LST SOFTCFG:;

------------------------------------
……



--- END
In the displayed results, Call-related message and Short message of CDMA message routing
on DPC in self PC processed by MNP, of CDMA message routing on DPC not in self PC
processed by MNP, of CDMA message routing on GT processed by MNP are all set to
ON. All CDMA message processing switches are set to ON, which indicates that the
Verifying the MNP Service Switch

This step must be performed after you set the MNP service switch. To verify the MNP service
switch, run LST MNPSOFTCFG on the MML client.
LST MNPSOFTCFG:;

------------------------------------
Country code = 852
Local network route number = E134
……
--- END
In the displayed results, Country code is 852, MNP mode is MNP_FN mode, Local network
route number is E134, and Convert UDT into XUDT is Close. The results are the same as the
data configured for the MNP service switch, which indicates that the configuration is successful.
Verifying the HLR Number

This step must be performed after you set the HLR number. To verify the HLR number, run
LST MNPHLRADDR on the MML client.
LST MNPHLRADDR:;

---------------------
Index Description HLR Address number HLR SPC
0 <NULL> 5555555555555555 1B0802

1 <NULL> 111 1B0602
2 <NULL> 861392 000009
3 ansi24 222 111111
4 itu14 333 001111
5 JK TEXT 1111 BBBBBB
--- END

In record 6, Index is 5, Description is JK TEXT, HLR Address number is 11111, and HLR
SPC is BBBBBB. The results are the same as the data configured for the HLR number, which
Verifying the MNP Routing Number

This step must be performed after you set the MNP routing number. To verify the MNP routing
number, run LST MNPROUTENUM on the MML client.
LST MNPROUTENUM:;

MNP route number
----------------
Index Description Route number IMSI number
0 <NULL> 123 123456789876

1 <NULL> 55 0123456789ABCDEF
……
10 Jktest 23 132132
--- END
In record 11, Index is 10, Description is Jktest, Route number is 23, and IMSI number is
132132. The results are the same as the data configured for the MNP local network number
range, which indicates that the configuration is successful.
Verifying User Information

This step must be performed after you set the service user data. To verify the user information,
Check whether the configured service user data is displayed in the query results. If yes, the
service user data is successfully configured; if not, you must configure the service user data
again.
Verifying MNP Local Network Number Range

This step must be performed after you set the MNP local network number range. To verify the
MNP foreign number range, run LST MNPLOCNRNG on the MML client.
LST MNPLOCNRNG:;

MNP LOCAL NETWORK NUMBER RANGE TABLE
------------------------------------
Index Description Number range type Start local network
number End local network number Routing number index HLR
address index
0 <NULL> CDMA NETWORK NUMBER RANGE

1339858 1339859
3 3

--- END
In this record, Index is 0, Description is Jktest, Start local network number is 1339858, End
local network number is 1339859, and HLR address index is 3. The results are the same as
the data configured for the MNP local network number range, which indicates that the
Verifying MNP Foreign Number Range

This step must be performed after you set the MNP foreign number range. To verify the MNP
foreign number range, run LST MNPFRGNRNG on the MML client.
LST MNPFRGNRNG:;

Foreign number range table
--------------------------
Index Description Min foreign number Max foreign number Route
number index
0 <NULL> 8613899998888
8613988889999 0
1 <NULL> 11
12 0
……
10 Jktest 1339850
1339861 2
--- END
In record 11, Index is 10, Description is Jktest, Min foreign number is 1339860, Max foreign
number is 1339861, and Route number is 2. The results are the same as the data configured
for the MNP foreign number range, which indicates that the configuration is successful.

Feature Description 13 Configuring IPR Service Data
13 Configuring IPR Service Data
About This Chapter
Before configuring the international preferred roaming (IPR) service data, make sure that the
hardware data, MTP data, SCCP data, and M3UA data are already configured.
13.1 IPR Service
This section describes the definition and advantages of the IPR service, as well as the terms
related to the IPR service.
13.2 Service Flow
This section describes the networking structure of the IPR service, service implementation, and
equipment coordination requirements in the IPR service.
This section describes the background information, table relations, and general steps related to
the configuration of the IPR service.
This section describes the detailed procedures for configuring the IPR service data, including
configuring the IPR service software parameters, IPR user group table, and IPR network table.
This section describes the configuration of the IPR service data based on examples.

13 Configuring IPR Service Data Feature Description
13.1 IPR Service

This section describes the definition and advantages of the IPR service, as well as the terms
related to the IPR service.
13.1.1 Service Overview
The IPR service can be classified into the preferred roaming service and anti-preferred roaming
service.
13.1.2 Terms
This section describes the terms related to the IPR service.
This section describes the advantages of the IPR service.
This section describes the features of the IPR service.
The IPR service is provided in V200R003 and later versions.
13.1.1 Service Overview

The IPR service can be classified into the preferred roaming service and anti-preferred roaming
service.
Preferred Roaming Service

When a local subscriber roams to another country, this system controls and guides the subscriber
to access a preferential subscribed network by simulating the HLR to reject the location update
messages, requiring for accessing a non-preferential network, initiated by the subscriber.
Anti-Preferred Roaming Service

When a foreign subscriber roams from another network to the local network, the subscriber
generates a location update message in the local network. If the location update is rejected by
the HLR of the subscriber, this system re-sends the message to the HLR to make the home
network of the subscriber accept the location update. Thus, the system guides the subscriber to
access the local network.
13.1.2 Terms
This section describes the terms related to the IPR service.
This Network
It identifies the network operated by this carrier. A current network can comprise multiple
network types.
Other Network
It identifies the networks operated by other carriers, including national and international
networks.

Outbound Roaming
When a subscriber roams out of the country where the subscriber resides, it is called outbound
roaming.
Inbound Roaming
When a subscriber roams into the country where this network resides, it is called inbound
roaming.

This section describes the advantages of the IPR service.
For Carriers
For carriers, the IPR service has the following advantages:
l Improving network utilization ratio and increasing operation revenue
l Improving subscriber loyalty to the network
l Helping carriers retain long-term and stable cooperation relationship with the carriers of
other countries
l Helping carriers control international roaming traffic and thus increasing international
roaming revenue
For subscribers
When a subscriber roams to another country, this system helps the subscriber access a rather
preferential network with better QoS based on location change of the subscriber. This ensures
the communication quality and decreases the roaming fee for subscribers.

This section describes the features of the IPR service.
The IPR service has the following features:
l Service independence: The IPR service does not conflict with any other mobile service.
l Equipment independence: The implementation of the IPR service does not require any other
equipment.
l Flow abnormality protection: When abnormality occurs, this system transparently transfers
the message and releases the saved information. This does not affect other services.

The IPR service is provided in V200R003 and later versions.
The IPR service has no special requirements on hardware.
13.2 Service Flow

This section describes the networking structure of the IPR service, service implementation, and
equipment coordination requirements in the IPR service.


This section describes the networking structure of the IPR service.
The IPR service can be classified into the preferred roaming and anti-preferred roaming services.
To implement the IPR service, the SG must be added between the STP and the INGW.
13.2.3 Call Flow
This section describes the call flow of the IPR service.
This section describes the requirements on device interworking for implementing the IPR
service.
This section describes how the IPR service affects intelligent services and supplementary
services.

This section describes the networking structure of the IPR service.
Figure 13-1 shows the networking structure of the IPR service.

Figure 13-1 Networking structure of the IPR service
HLR: Home Location Register VMSC: Visited Mobile Switching SG: U-SYS SG7000 Signaling
Center Gateway
STP: Signaling Transfer Point INGW: International Gateway
The functions of the network elements (NEs) in the networking structure are as follows:
l SG: It processes and transfers signaling messages between NEs, thus implementing the IPR
service.
l HLR: It interacts with any other NE to return subscriber location information.
l VMSC: It connects calls for mobile terminals.
l STP: It transfers signaling messages between NEs.
l INGW: It collects the communication information coming from different countries.

The IPR service can be classified into the preferred roaming and anti-preferred roaming services.
To implement the IPR service, the SG must be added between the STP and the INGW.


To implement the preferred roaming service, the following conditions must be met:
1. When a subscriber roams out of a country, the location update message initiated from the
subscriber is sent to the SG.
2. The preferred roaming switch in the SG is enabled in advance. In addition, the IPR network
table, outbound roaming user group table, and IPR user group table have been configured.
3. When a location update message comes from a non-preferential network, the SG simulates
the HLR to reject the message and guide the subscriber to access a preferential network.

To implement the anti-preferred roaming service, the following conditions must be met:
1. When a foreign subscriber roams into this network, the location update message initiated
from the subscriber is sent to the SG.
2. The SG initiates a location update message to the HLR of the subscriber over the INGW.
3. The anti-preferred roaming switch in the SG is enabled in advance. In addition, the IPR
user group table and inbound roaming user group table have been configured.
4. When the location update message is rejected, the SG re-sends the location update message.
This increases the possibility for the SG to make the HLR accept this network, thus guiding
the internationally roaming subscriber to access this network.
13.2.3 Call Flow

This section describes the call flow of the IPR service.
The IPR service is implemented in any of the following three modes.
An Outbound Subscriber Accesses the Preferential Network Directly
Figure 13-2 An outbound subscriber accesses the preferential network directly

Figure 13-2 shows the signaling flow when an outbound subscriber accesses the preferential
network directly.
The signaling flow is described as follows:
1. An internationally roaming subscriber initiates a location update message to the VMSC

from a preferential network. The VMSC transparently transfers the message to the SG
through the INGW.
2. The SG analyzes the message and finds out that the number of the VLR which the subscriber
requires for accessing belongs to the preferential network number segment of the
subscriber. Then, the SG transfers the location update message to the HLR of the subscriber.
3. The HLR inserts data in the message and then sends the message to the VMSC.
4. The VMSC responds a message to the HLR.
5. The HLR returns a location update response to the HLR. The subscriber successfully
accesses the preferential network.
An Outbound Subscriber Accesses the Preferential Network by Preferred Roaming

Function
Figure 13-3 An outbound subscriber accesses the preferential network by preferred roaming
function

Figure 13-3 shows the signaling flow when an outbound subscriber accesses the preferential
network by preferred roaming function. When a subscriber roams from this network to another
country, if the location update message initiated by the subscriber for accessing a non-
preferential network is sent to the SG, the SG rejects the message and guides the subscriber to
access a preferential network rather than a non-preferential network through the preferred
roaming function. In the figure, blue lines indicate unsuccessful signaling flows and grey lines
indicate successful ones.
NOTE
The SG responds reject messages to the location update messages based on the configured probability.
Beyond the probability, the SG transparently transfers the location update message to the HLR of the
subscriber, thus allowing the subscriber to access the non-preferential network. This signaling flow only
describes how the SG guides a subscriber to access a preferential network.

1. An internationally roaming subscriber initiates a location update message to the VMSC
from a non-preferential network. The VMSC transparently transfers the message to the
SG through the INGW.
requires for accessing does not belong to the preferential network number segment of the
subscriber. In this case, the SG determines whether to reject the location update message
based on the probability. If not, the subscriber accesses the non-preferential network and
the subsequent signaling flow is the same as that of a subscriber accessing a preferential
network. If yes, the subsequent signaling flow is as follows.
3. The SG rejects the location update message based on the probability and returns a location
update reject message to the VMSC. The message contains the error code configured by
the subscriber. In addition, to hide the error source, the SG modifies the calling GT in the
message to a random number in a specified number segment when returning the location
update reject message.
4. When the VLR of the non-preferential network receives the location update message that
contains an error code, it rejects the subscriber to access the network. In this case, the
subscriber selects another network and initiates a location update message again. If the
selected network is still a non-preferential network, the preceding signaling flow is
repeated. If the selected network is a preferential network, the subscriber accesses the
network and the subsequent signaling flow is the same as that of a subscriber accessing a
preferential network.

An Inbound Subscriber Accesses This Network by Anti-Preferred Roaming

Function
Figure 13-4 An inbound subscriber accesses this network by anti-preferred roaming function
Figure 13-4 shows the signaling flow when an inbound subscriber accesses this network by anti-
preferred roaming function. When a subscriber roams to this network from another country, if
the location update message initiated by the subscriber for accessing this network is rejected by
the home network of the subscriber, the SG can successfully guide the home network of the
subscriber to accept the subscriber accessing this network through the anti-preferred roaming
function.
NOTE
When the home network of an internationally roaming subscriber interferes the subscriber to access this
network, the SG repeats the anti-preferred roaming function until the timer is timeout or the times of the
attempts exceeds the preset value. In this case, the anti-preferred roaming function fails, and the SG releases
the buffer messages and does not process any subsequent response from the HLR, that is, the location
update may be successful or unsuccessful.
1. A subscriber roams to this network from another country and initiates a location update
message to the VMSC. The VMSC transfers the message to the SG.
requires for accessing belongs to the number segment of this network. Then, the SG saves
the location update message in the buffer and transfers it to the HLR of the subscriber
through the INGW.

3. Under the interference of the home network of the subscriber, the SG receives the location
update failure response from the home network of the subscriber.
4. The SG analyzes the location update response message and finds out that the location update
fails. In this case, the SG discards the failure message and simulates the VMSC to re-send
the location update message saved in the buffer to the home network of the subscriber.
5. The home network of the subscriber accepts the location update request. Then, the HLR
inserts data in the message and then sends the message to the VMSC of this network.
6. The VMSC responds a message to the HLR of the subscriber.
7. The HLR returns a location update response to the SG.
8. The SG releases the buffer message and transparently transfers the location update response
to the VMSC. Thus, the SG successfully guides an internationally roaming subscriber to
access this network.

This section describes the requirements on device interworking for implementing the IPR
service.
There are no special requirement on device interworking except that all location update messages
passing the INGW must be transferred to the SG7000.

This section describes how the IPR service affects intelligent services and supplementary
services.
Impact on Intelligent Services

The IPR service does not affect any IN service.

The IPR service does not affect any supplementary service.

the configuration of the IPR service.
This section describes the principles to be followed when you configure the IPR service data.
13.3.2 Mapping Between Data Tables
This section describes the mapping between data tables related to the IPR service.
This section describes the data to be collected before you configure the IPR service data,
including the preferred roaming network data and the inbound anti-preferred roaming user data.
This section describes the general steps for configuring the IPR service data.


This section describes the principles to be followed when you configure the IPR service data.
To configure the IPR service, follow the principles below:
l The preferred network data must be planned and configured in the IPR network table.
l For the preferred roaming service:
The preferred roaming user data must be planned based on the following principles:
1. All planned data must be configured in the IPR user group table.
2. The preferred roaming user data must be configured in the outbound roaming user
group table. The outbound roaming user group table must reference the records from
the IPR user group table and the IPR network table.
l For the anti-preferred roaming service:
The anti-preferred roaming user data must be planned based on the following principles:
1. All planned data must be configured in the IPR user group table.
2. The anti-preferred roaming user data must be configured in the outbound roaming
user group table. The outbound roaming user group table must reference the records
from the IPR user group table.
l For the sake of service stability, the standby boards of the SBPUs/SBPEs serving as the
resource boards must be configured.
13.3.2 Mapping Between Data Tables

This section describes the mapping between data tables related to the IPR service.
Figure 13-5 shows the mapping between data tables related to the IPR service.

Figure 13-5 Mapping between data tables related to the IPR service

This section describes the data to be collected before you configure the IPR service data,
including the preferred roaming network data and the inbound anti-preferred roaming user data.
The data to be collected related to the IPR service includes three parts: the preferred roaming
public data, preferred roaming data, and anti-preferred roaming data.
Table 13-1 Table for collecting the preferred roaming public data
Start IMSI number End IMSI number Start HLR number End HLR
number
Country code Mobile country code Default location Update

update attempt times location timer
(s)


Table 13-1 and Table 13-2 list the data to be collected before you configure the preferred
roaming data in the IPR service.
Table 13-2 Table for collecting the preferred roaming data
Start VLR number End VLR number Default preferred

rate
Roaming network User group index Preferred rate

index

Table 13-1 and Table 13-3 list the data to be collected before you configure the anti-preferred
roaming data in the IPR service.
Table 13-3 Table for collecting the anti-preferred roaming data
User group index Location update

attempt times

This section describes the general steps for configuring the IPR service data.
Table 13-4 lists the general steps for configuring the IPR service data.
Table 13-4 General steps for configuring the IPR service data
Step Operation
1 Configure IPR service software parameters (SET IPRSOFTCFG)
2 Configure the IPR user group table (ADD IPRUSRGRP)
3 Configure the IPR network table (preferred roaming) (ADD IPRNET)
4 Configure the outbound roaming user group table (preferred roaming)

(ADD IPROUTGRP)
5 Configure the inbound roaming user group table (anti-preferred roaming)

(ADD IPRINGRP)

Configuration sequences are as follows:

l The IPR service software parameters and the IPR user group table must be configured
before you configure the preferred and anti-preferred roaming data.
l The IPR network table must be configured before the outbound roaming user group table
is configured.
l The preferred and anti-preferred roaming data is configured regardless of the sequence.
You can configure the anti-preferred roaming data before configuring the preferred roaming
data.

This section describes the detailed procedures for configuring the IPR service data, including
configuring the IPR service software parameters, IPR user group table, and IPR network table.
13.4.1 Configuring IPR Service Software Parameters
This section describes the command, parameters, and related commands for configuring the IPR
service software parameters.
13.4.2 Configuring the IPR User Group Table
user group. The configured data is referenced by the inbound and outbound roaming user group
tables to determine the attributes related to the international roaming services.
13.4.3 Configuring the IPR Network Table
network table. The configured data is referenced by the outbound roaming user group table to
determine which network is the preferred network in the IPR service and the probability for
selecting the preferred network.
13.4.4 Configuring the Outbound Roaming User Group Table
This section describes the command, parameters, and related commands for configuring the
outbound roaming user group table.
13.4.5 Configuring the Inbound Roaming User Group Table
inbound roaming user group table.
13.4.1 Configuring IPR Service Software Parameters

service software parameters.
Command
SET IPRSOFTCFG

Parameter
r ID r Name
FUNCSW Function It specifies the function to be enabled on this system.

T switch It is optional and its value is of the enumeration type. It can be set
to one or both of the following values:
l BIT0 (Preferred roaming): The preferred roaming service is
enabled on this system.
l BIT1 (Anti-preferred roaming): The anti-preferred roaming
service is enabled on this system.
REJECTI Reject It specifies the information value returned by this system for
NFO informatio rejecting a location update message.
n of It is optional and its value is of the enumeration type. It can be set
update to:
location
l BIT0 (Unknown subscriber)
l BIT1 (Roaming not allowed-PLMN not allowed)
l BIT2 (Roaming not allowed-ODB)
l BIT3 (System failure)
l BIT4 (Unexpected data value)
l BIT5 (DataMissing)
FROMHL Start HLR When the system rejects a location update message, it generates a
R number random HLR number and fills the number into the calling GT
contained in the message.
TOHLR End HLR
The system compares the HLR number contained in the message
number
with the HLR number segment defined together by Start HLR
number and End HLR number to determine whether to perform
the preferred roaming on the message.
It is optional. Its value is a string of no more than 16 characters and
can contain numbers 0-9.
The rules for configuring the parameters are as follows:
l The length of Start HLR number must be the same as that of
End HLR number.
l Start HLR number cannot be greater than End HLR
number.
l The length of Start HLR number and End HLR number
configured here must be the same as that of the actual HLR
numbers.
COUNTR Country It specifies the code of the country where this system resides.
YCODE code It is optional. Its value is a string of no more than 6 characters and
can contain numbers 0-9.


r ID r Name
MCNTYC Mobile It specifies the mobile code of the country where this system
D country resides.
code It is optional. Its value is a string of 3 characters and can contain
numbers 0-9.
UPFRE Default It specifies the maximum number of attempts for a user group to
location send location update messages in the anti-preferred roaming
update service. When this system fails to query a user group index in the
attempt IPR user group table, the system compares the value of this
times parameter with the update attempt times to determine whether to
transparently transfer the message.
It is optional. Its value is of the numeral type and ranges 0-255.
When it is set to 0, the system transparently transfers the message
without performing the anti-interference operation on the location
update process.
UPTIME Update It is used to control the time for releasing the anti-preferred
R location roaming resources.
timer (s) It is optional. Its value is of the numeral type and ranges 1-30.
SYSPAR System It is used to control the scale of the resource module. To modify
A parameter this parameter, you must reset the resource module. Therefore, run
this command with caution.
This parameter, together with Update location timer(s),
determines the actual available scale of the system resource table.
When the required scale of the resource table exceeds the actual
available scale, the system transparently transfers the extra
messages instead of performing the anti-preferred roaming
processing.
It must be configured based on the subscriber data in the current
network. The rules for configuring this parameter are as follows:
Assume that the number of subscribers in the current network is
M, the value of System parameter must be equal to or greater than
"M/0.5", that is, "N >= M/0.5". The system sup
13.4.2 Configuring the IPR User Group Table

user group. The configured data is referenced by the inbound and outbound roaming user group
tables to determine the attributes related to the international roaming services.
Command
ADD IPRUSRGRP

Parameter
r ID r Name
FROMIM Start IMSI Parameters Start IMSI number and End IMSI number together
SI number determine the IMSI number segment on which the system performs
the IPR processing.
TOIMSI End IMSI
They are mandatory. The value of the parameter is a string of no
number
more than 15 characters and can contain numbers 0-9.
l The length of Start IMSI number must be the same as that of
End IMSI number.
l The value of Start IMSI number cannot be greater than that of
End IMSI number.
l The number segments of different records cannot be overlapped
or intersected.
Related Commands
Table 13-5 Related commands for configuring the IPR user group table
Command Function
ADD IPRUSRGRP To add the IPR user group table
MOD IPRUSRGRP To modify the IPR user group table
RMV IPRUSRGRP To remove the IPR user group table
LST IPRUSRGRP To query the IPR user group table
13.4.3 Configuring the IPR Network Table

network table. The configured data is referenced by the outbound roaming user group table to
determine which network is the preferred network in the IPR service and the probability for
selecting the preferred network.
Command
ADD IPRNET

Parameter
r ID r Name
FROMVL Start VLR Parameters Start VLR number and End VLR number together
R number determine the VLR number segment of a preferred network.
They are mandatory. The value of the parameter is a string of no
TOVLR End VLR
more than 16 characters and can contain numbers 0-9 and
number
characters A-D.
l The length of Start VLR number must be the same as that of
End VLR number.
l The value of Start VLR number cannot be greater than that of
End VLR number.
l The number segments of different records cannot be overlapped
or intersected.
PRERT Default It specifies the probability for selecting a preferred network. It

preferred determines whether the system accepts the location update
rate message.
It is optional. Its value is of the numeral type and ranges 0%-100%.
It is set to 100 by default, indicating the highest probability. When
the number of the VLR initiating the message exists in the IPR
network table, the system directly sends the location update
message to the HLR rather than selecting the preferred network
based on the probability.
Related Commands
Table 13-6 Related commands for configuring the IPR network table
Command Function
ADD IPRNET To add the IPR network table
MOD IPRNET To modify the IPR network table
RMV IPRNET To remove the IPR network table
LST IPRNET To query the IPR network table
13.4.4 Configuring the Outbound Roaming User Group Table

outbound roaming user group table.

Command
ADD IPROUTGRP
Parameter
r ID r Name
ROAMN Roaming It specifies the index of the network that a subscriber roams into.
ETIDX network It references a record in the IPR network table.
index It is mandatory. Its value is of the numeral type and ranges 0-1023.
USRGRPI User It references a record in the IPR user group table.

DX group It is mandatory. Its value is of the numeral type and ranges 0-1023.
index
RATION Preferred It specifies the probability for selecting the preferred network in
rate roaming services.
It is optional. Its value range is 0%-100%. It is set to 100 by default.
It is set to 100 by default, indicating the highest probability. When
the number of the VLR initiating the message exists in the IPR
network table, the system directly sends the location update
message to the HLR rather than selecting the preferred network
based on the probability.
NOTE
When Preferred rate is configured in the outbound roaming user group table, the system uses the value
of Preferred rate to perform the preferred roaming function in the IPR service; if Preferred rate is not
configured in the outbound roaming user group table, the system uses the value of Default preferred
rate configured in the IPR network table to perform the preferred roaming function in the IPR service.
Related Commands
Table 13-7 Related commands for configuring the outbound roaming user group table
Command Function
ADD IPROUTGRP To add the outbound roaming user group table
MOD IPROUTGRP To modify the outbound roaming user group table
RMV IPROUTGRP To remove the outbound roaming user group table
LST IPROUTGRP To query the outbound roaming user group table
13.4.5 Configuring the Inbound Roaming User Group Table

inbound roaming user group table.

Command
ADD IPRINGRP
Parameter
r ID r Name
USRGRPI User It references a record in the IPR user group table.

DX group It is mandatory. Its value is of the numeral type and ranges 0-1023.
index
RATION Location It specifies the number of times of the location update attempts
update initiated by a user group. In a valid period, when the actual number
attempt of times of the attempts originated by a user group is greater than
times the value configured for this parameter, the system transparently
transmits the message and releases the occupied resources rather
than performing the preferred roaming selection again.
It is optional. Its value range is 0-255. It is set to 3 by default.
Related Commands
Table 13-8 Related commands for configuring the inbound roaming user group table
Command Function
ADD IPRINGRP To add the inbound roaming user group table
MOD IPRINGRP To modify the inbound roaming user group table
RMV IPRINGRP To remove the inbound roaming user group table
LST IPRINGRP To query the inbound roaming user group table

This section describes the configuration of the IPR service data based on examples.
Networking Structure of the IPR Service

Figure 13-1 shows the networking structure of the IPR service.
Data Collection for the IPR Service

Table 13-9, Table 13-10, and Table 13-11 list the data collected for configuring the IPR service.

Table 13-9 Table for collecting the preferred roaming public data
Start IMSI number End IMSI number Reject information

of update location
1379858 (preferred 1379860 (preferred BIT3 (system failure)

roaming) roaming)
219890 (anti- 219900 (anti-preferred
preferred roaming) roaming)
Start HLR number End HLR number Country code Mobile

country code
1668 1670 86 460
Default location Update location timer

update attempt (s)
times
4 30
Table 13-10 Table for collecting the preferred roaming data
Start VLR number End VLR number Default preferred

rate
23919 23920 80
Roaming network User group index Preferred rate

index
0 0 50
Table 13-11 Table for collecting the anti-preferred roaming data
User group index Location update

attempt times
15
Procedure
Step 1 Configure IPR service software parameters.
To configure IPR service software parameters, where Function switch is Preferred roaming
and Anti-preferred roaming, Reject information of update location is System faliure, Start
HLR number is 1668, End HLR number is 1670, Country code is 86, Mobile country
code is 460, Default location update attempt times is 4, and Update location timer(s) is 30,
run the following command:

SET IPRSOFTCFG: FUNCSWT=BIT0-1&BIT1-1, REJECTINFO=BIT3, FROMHLR="1668",

TOHLR="1670", COUNTRYCODE="86", MCNTYCD="460", UPFRE=4, UPTIMER=30;
Step 2 Configure the IPR user group table.

l Preferred roaming service
To configure the IPR user group table in the preferred roaming service, where Start IMSI
number is 1379858 and End IMSI number is 1379860, run the following command:
ADD IPRUSRGRP: FROMIMSI="1379858", TOIMSI="1379860";
l Anti-preferred roaming service
To configure the IPR user group table in the anti-preferred roaming service, where Start
IMSI number is 219890 and End IMSI number is 219900, run the following command:
ADD IPRUSRGRP: FROMIMSI="219890", TOIMSI="219900";
NOTE
After the command is executed, record indexes are returned. Record the indexes in the data collection table.
Assume that the indexes generated in this example are 0 and 1.
Step 3 Configure the IPR network table.

To configure the IPR network table, where Start VLR number is 23919, End VLR number
is 23920, and Default preferred rate is 80, run the following command:
ADD IPRNET: FROMVLR="23919", TOVLR="23920", PRERT=80;
Step 4 Configure the outbound roaming user group table.

To configure the outbound roaming user group table, where Roaming network index is 0, User
group index is 0, and Preferred rate is 50, run the following command:
ADD IPROUTGRP: ROAMNETIDX=0, USRGRPIDX=0, RATION=50;
Step 5 Configure the inbound roaming user group table.

To configure the inbound roaming user group table, where User group index is 1 and Location
update attempt times is 5, run the following command:
ADD IPRINGRP: USRGRPIDX=1, UPFREQCY=5;
----End
Verifying IPR Service Software Parameters

This step must be performed after you configure IPR service software parameters. To verify IPR
service software parameters, run LST IPRSOFTCFG on the MML client.
LST IPRSOFTCFG:;

IPR Soft Config Table
---------------------
Function Switch = G_2<ON>G_1<ON>
Reject information of update location = System Faliure
Start HLR number = 1668
End HLR number = 1670
Country Code = 86
Mobile Country Code = 460
Default Location Update Attempt Times = 4
Update Location Timer(s) = 30

System Parameter = 200
--- END
In the displayed results, Function switch is G_2<ON> and G_1<ON>, Reject information of
update location is System failure, Start HLR number is 1668, End HLR number is 1670,
Country code is 86, Mobile country code is 460, Default location update attempt times is
4, Update location timer (s) is 30, and System parameter is the default value 200. The results
are the same as the data configured for the IPR service software parameters, which indicates that
the configuration is successful.
Verifying the IPR User Group Table

This step must be performed after you configure the IPR user group table. To verify the
configuration in the IPR user group table, run LST IPRUSRGRP on the MML client.
LST IPRUSRGRP:;

IPR USR GROUP Table
-------------------
Index Description Start IMSI number End IMSI number
0 <NULL> 1379858 1379860

1 <NULL> 219890 219900
--- END
Two records are displayed:
l In record 1, Description is null, Start IMSI number is 1379858, and End IMSI
number is 1379860.
l In record 2, Description is null, Start IMSI number is 219890, and End IMSI number
is 219900.
The results are the same as the data configured for the IPR user group table, which indicates that
the configuration is successful.
Verifying the IPR Network Table

This step must be performed after you configure the IPR network table. To verify the
configuration in the IPR network table, run LST IPRNET on the MML client.
LST IPRNET:;

IPR Network Table
-----------------
Index = 0
Start VLR number = 23919
End VLR number = 23920
Default Preferred Rate = 80
--- END

In the displayed results, Index is 0, Description is null, Start VLR number is 23919, End
VLR number is 23920, and Default preferred rate is 80. The results are the same as the data
configured for the IPR network table, which indicates that the configuration is successful.
Verifying the Outbound Roaming User Group Table

This step must be performed after you configure the outbound roaming user group table. To
verify the configuration in the outbound roaming user group table, run LST IPROUTGRP on
the MML client.
LST IPROUTGRP: MODE=INDEX, IDX=0;

Outbound Roaming Usr Group Table
--------------------------------
Index = 0
Roaming Network Index = 0
Usr Group Index = 0
Preferred Rate = 50
--- END
In the displayed results, Index is 0, Description is null, Roaming network index is 0, User
group index is 0, and Preferred rate is 50. The results are the same as the data configured for
the outbound roaming user group table, which indicates that the configuration is successful.
Verifying the Inbound Roaming User Group Table

This step must be performed after you configure the inbound roaming user group table. To verify
the configuration in the inbound roaming user group table, run LST IPRINGRP on the MML
client.
LST IPRINGRP: MODE=IDX, IDX=0;

Inbound Roaming Usr Group Table
-------------------------------
Index = 0
Usr Group Index = 1
Location Update Attempt Times = 5
--- END
In the displayed results, Index is 0, Description is null, User group index is 1, Location update
attempt times is 5. The results are the same as the data configured for the inbound roaming user
group table, which indicates that the configuration is successful.

Feature Description 14 Configuring IRVAS Service Data
14 Configuring IRVAS Service Data
About This Chapter
Configure the International Roaming Value Added Service (IRVAS) only after you have finished
the configuration of hardware data, MTP data, SCCP data, and M3UA data.
14.1 Brief Introduction
This section describes the IRVAS service, advantages of the IRVAS service, and terminologies
related to the IRVAS service.
14.2 Service Flow
This section describes the networking and implementation of the IRVAS service, as well as the
equipment required in the implementation of the service.
the configuration of the IRVAS service.
14.4 Configuring the IRVAS Service
The configuration of the IRVAS service involves: configuring the IRVAS software parameters,
configuring the MSC number segment supporting the CAMEL capabilities, and configuring the
SCCP GT translation table.
This section describes examples of configuring the IRVAS service.

14 Configuring IRVAS Service Data Feature Description
14.1 Brief Introduction

This section describes the IRVAS service, advantages of the IRVAS service, and terminologies
related to the IRVAS service.
The IRVAS service is realized through the SG and the IN platform, and is only applicable to the
GSM network. SG intercepts the location update signaling and call routing signalings of a
subscriber, reports the information of the subscriber to the IN platform. Under the instruction of
the IN platform, it modifies the subscriber's Terminating CAMEL Subscription Information
(T_CSI) or MSRN and triggers the callee oriented IN service of the subscriber over the IN
platform so that the subscriber can enjoy individualized IN services during international
roaming. For example, virtual home environment (assistant dialing and adaptation to the
subscriber's dialing habit) and roaming services (realtime charging for pre-paid roaming
subscriber and realtime charging for postpayment subscriber).
14.1.2 Terms
This section introduces the terminologies related to the data configuration of the IPR service.
This section introduces the advantages of the IRVAS service.
The IRVAS service is provided in V200R003 and later versions.

The IRVAS service is realized through the SG and the IN platform, and is only applicable to the
GSM network. SG intercepts the location update signaling and call routing signalings of a
subscriber, reports the information of the subscriber to the IN platform. Under the instruction of
the IN platform, it modifies the subscriber's Terminating CAMEL Subscription Information
(T_CSI) or MSRN and triggers the callee oriented IN service of the subscriber over the IN
platform so that the subscriber can enjoy individualized IN services during international
roaming. For example, virtual home environment (assistant dialing and adaptation to the
subscriber's dialing habit) and roaming services (realtime charging for pre-paid roaming
subscriber and realtime charging for postpayment subscriber).
14.1.2 Terms
This section introduces the terminologies related to the data configuration of the IPR service.
MSISDN
Every Mobile Station (MS) has two numbers: MSISDN and International Mobile Subscriber
Identity (IMSI). The MSISDN is the directory number used for making a phone call. The IMSI
is the identification number used by the service provider for identifying an MS.
IMSI
The IMSI uniquely identifies an MS. It consists of three parts:


The IMSI enables the carrier to identify an MS, search the address of the MS, and authenticate
the MS. When a subscriber applies for the mobile telecommuncation service, two numbers will
be allocated to the subscriber: MSISDN and IMSI.
T_CSI
Not all subscribers can enjoy IN services. The concept of CSI is introduced to indicate whether
a subscriber is an IN service subscriber. If a subscriber has an allocated CSI, the subscriber can
trigger an IN service. The CSI for triggering the IN services mainly includes O_CSI and T_CSI,
which correspond to the caller and the callee respectively. O_CSI, together with other subscriber
data, is saved in the HLR. During the location updating process, it is sent to the VLR. T_CSI is
saved in the HLR. In the process of obtaining the roaming number, it is taken from the HLR.
OUTBOUND
When a subscriber of the local network roams to other areas, the subscriber is referred to as an
outbound subscriber.
INBOUND
When a subscriber of other networks roams to the local network, the subscriber is referred to as
an inbound subscriber.

This section introduces the advantages of the IRVAS service.
For Carriers
The carrier can acquire the information of the international roaming subscriber and control the
callee oriented IN services to realize convenient charges management. In this way, the carrier
can cut the roaming cost, increase revenues from roaming, improve the subscriber's satisfaction
level, and popularize its brandname.
For Subscribers
During international roaming, the subscribers can enjoy individualized IN service conveniently.

The IRVAS service is provided in V200R003 and later versions.
The IRVAS service has no special requirement on hardware.
14.2 Service Flow

This section describes the networking and implementation of the IRVAS service, as well as the
equipment required in the implementation of the service.

This section introduces the networking structure of the IRVAS service.

To implement the IRVAS service, you need to configure the MSC number segment table that
supports the CAMEL function in the STP. The table contains the MSC number segments that
support CAMEL and direct routing. When the calling MSC belongs to the number segment, the
system can trigger the callee oriented IN service in the calling MSC.
14.2.3 Calling Flow
The IRVAS service involves the location updating flow, error recovery flow of the VLR, the
subscriber data insertion flow of the HLR, and the call routing flow.
14.2.4 Requirements on Cooperating Equipment
The ISTP and GMSC send international roaming messages to the SG.
This section describes the impact of the IRVAS service on IN services and supplementary
services.

This section introduces the networking structure of the IRVAS service.
Figure 14-1 shows a typical networking structure of the IRVAS service in the Public Land
Mobile Network (PLMN).

Figure 14-1 Networking of the IRVAS Service
ISG: International Service Gateway IN: IN service platform VMSC: Visited Mobile Switching
Center
HLR: Home Location Register GMSC: Gateway Mobile STP: Signaling Transfer Point
Switching Center
ISTP: International Signaling SSP: Service Switching Point SSP: Service Switching Point
Transfer Point
PLMN: Public Land Mobile Network
In this networking, the SG together with the IN and the SSP (GMSC probably) form the ISG to
provide the cross-carrier international roaming service. The SG adopts redudant configuration
and connects to the GMSC and ISTP in the local network. It is required that signaling related to
location updating, insertion of subscriber data and VLR error recovery in the process of
international roaming must pass through the SG. It is also required that the network adopts the
addressing mode of Route on GT and that the SG serves as the translation point.
In the above figure, the network where the SG is located is referred to as the local network in
the ensuing sections. When a subscriber of the local network roams to a network in a foreign
country, the local network is the home network of the subscriber. When a foreign subscriber
roams to the local network, the local network is the roaming network of the foreign subscriber.


To implement the IRVAS service, you need to configure the MSC number segment table that
supports the CAMEL function in the STP. The table contains the MSC number segments that
support CAMEL and direct routing. When the calling MSC belongs to the number segment, the
system can trigger the callee oriented IN service in the calling MSC.
After the subscriber data is well planned, the implementation of the IRVAS service involves the
following processes:
1. In the process of international roaming, the signaling messages of location updating,
insertion of subscriber data, VLR error recovery, VLR error recovery, and call routing pass
through the SG.
2. The SG obtains the MSISDN, IMSI, MSC_num, VLR_num, supplementary service
information, In service information, and MSRN of the subscriber, and reports them to the
IN platform.
3. The SG modifies the T_CSI or MSRN of the subscriber according to the instructions from
the IN platform, and triggers the callee oriented IN service in the IN platform.
14.2.3 Calling Flow

The IRVAS service involves the location updating flow, error recovery flow of the VLR, the
subscriber data insertion flow of the HLR, and the call routing flow.
NOTE
The subscribers in all flows can be divided into the INBOUND subscribers and OUTBOUND subscribers.
Here, the flows are based on the INBOUND subscribers.
Location Updating Flow

When the location of a subscriber is updated, the VLR initiates the location updating flow and
sends a request for obtaining the subscriber data to the HLR. See Figure 14-2.
Figure 14-2 Location Updating Flow Chart

The flow is described as follows:

1. The INBOUND subscriber initiates the location updating process in the local network. The
VMSC sends the UPDATE_LOCATION message to the HLR. The message carries the
IMSI, MSC_NUM, and VLR_NUM of the subscriber as well as the supported CAMEL
version.
2. When the UPDATE_LOCATION message passes through the SG, the SG obtains the
information from the UPDATE_LOCATION message and transparently transmits the
UPDATE_LOCATION message to the HLR to which the subscriber belongs.
3. The SG reports the information carried in the UPDATE_LOCATION message and the
caller's GT and OTID to the IN platform through the EXECUTE message.
4. The IN platform returns the the response message EXECUTE_ack.
5. The SG receives the INSERT_SUBSCRIBER_DATA messages. The message carries the
MSISDN, supplementary service information, and CAMEL information of the subscriber.
6. The SG transparently sends the INSERT_SUBSCRIBER_DATA message to the VMSC.
7. The SG receives the response message INSERT_SUBSCRIBER_DATA_ack from the
VMSC. The SG transparently transmits the message to the HLR.
8. The SG sends the information carried in the INSERT_SUBSCRIBER_DATA_continue
message to the IN platform through the EXECUTE message.
9. The IN platform returns the response message EXECUTE_ack to the SG.
10. The SG receives the response message UPDATE_LOCATION_ack message from the
HLR. The message carries the GT and DTID of the callee.
11. The SG sends the UPDATE_LOCATION_ack message to the VMSC to end the location
updating process.
12. The SG reports the information carried in the UPDATE_LOCATION_ack message to the
IN platform through the EXECUTE message.
13. The IN platform returns the response message EXECUTE_ack.
NOTE
When the SG sends a message to the IN platform, the system starts the timer. If the IN fails to return a
response message when the timer times out, the SG resends the message. The allowed message resend
event count can be configured in the system.
VLR Error Recovery Flow

When the HLR sends a request for obtaining the MSRN to the VLR but the VLR does not contain
the subscriber's data, the VLR initiates the error recovery flow and sends a request for obtaining
the subscriber's data to the HLR, as shown in Figure 14-3.

Figure 14-3 VLR Error Recovery Flow Chart
1. The INBOUND subscriber initiates the location updating process in the local network. The
VMSC sends the RESTORE_DATA message to the HLR.
2. The RESTORE_DATA message passes through the SG. The SG obtains the information
from the RESTORE_DATA message and transparently transmits the message to the HLR
to which the subscriber belongs.
3. The SG reports the information carried in the RESTORE_DATA message and the caller's
GT and OTID to the IN platform through the EXECUTE message.
5. The SG receives the INSERT_SUBSCRIBER_DATA messages. The message carries the
MSISDN, supplementary service information, and CAMEL information of the subscriber.
6. The SG transparently sends the INSERT_SUBSCRIBER_DATA message to the VMSC.
VMSC, and then transparently transmits the message to the HLR.
8. The SG sends the information carried in the INSERT_SUBSCRIBER_DATA_continue
9. The IN platform returns the response message EXECUTE_ack to the SG,
10. and receives the response message RESTORE_DATA _ack carrying the GT and DTID of
the callee from the HLR.
11. The SG sends the RESTORE_DATA _ack message to the VMSC transparently to terminate
the VLR error recovery flow.
12. The SG reports the information carried in the RESTORE_DATA _ack message to the IN
platform through the EXECUTE message.

Subscriber Data Insertion Flow of the HLR

When the subscriber data in the HLR changes, the HLR sends the
INSERT_SUBSCRIBER_DATA message to the VLR. See Figure 14-4.
Figure 14-4 Subscriber Data Insertion Flow of the HLR
1. After the data of an INBOUND subscriber is modified in the HLR, the HLR sends the
INSERT_SUBSCRIBER_DATA message to the VMSC of the subscriber. The message
carries the IMSI, MSISDN, supplementary service information, and CAMEL information
of the subscriber.
2. When the INSERT_SUBSCRIBER_DATA message passes through the SG, the SG
extracts information from the message, and then sends the message to the VMSC
transparently. The VMSC returns the response message
INSERT_SUBSCRIBER_DATA_ack message.
3. The SG reports the information carried in the INSERT_SUBSCRIBER_DATA_begin
message and the caller's GT and OTID to the IN platform through the EXECUTE message.
VMSC.
6. SG transparently sends the INSERT_SUBSCRIBER_DATA_ack message to the HLR.
7. The SG sends the information carried in the INSERT_SUBSCRIBER_DATA_ack
9. SG receives the MAP_CLOSE message carrying the callee's GT and DTID from the HLR.
10. SG transparently sends the MAP_CLOSE message to the VMSC.
11. The SG sends the information carried in the MAP_CLOSE message to the IN platform
through the EXECUTE message.

NOTE
The location updating flow, error recovery flow of the VLR and the subscriber data insertion flow of the
HLR are related to the subscriber data (including ISMI, MSISDN, VLR_NUM, MSC_NUM,
supplementary service data, and IN service data). The SG intercepts the messages of the flows to obtain
desired information and reports the information to the SCP for processing.
Call Routing Flow (A Local Subscriber Calls an INBOUND Subscriber)

In the calling process, the MSC of the caller sends the SRI message to the HLR of the callee to
obtain the routing information. The HLR returns the MSRN or T_CSI of the callee (if the callee
oriented IN service has been subscribed). The SG intercepts the messages, and reports the MSRN
or T_CSI to the SCP for processing. See Figure 14-5.
Figure 14-5 Call Routing Flow
1. When a local subscriber calls an INBOUND subscriber over a direct route, the VMSC of
the caller sends the SRI message to the HLR of the callee to obtain the routing information.
2. The callee is an IN service subscriber. The HLR returns the SRI_ack message carrying the
callee's IMSI and T_CSI.
3. The SG intercepts the SRI_ACK_TCSI message and reports the callee's IMSI, T_CSI and
GT (caller's VMSC number) to the IN platform through the EXECUTE message.
4. The IN platform returns the EXECUTE_ack message, instructing the SG to change the
T_CSI into T_CSI'.

5. SG changes the T_CSI into T_CSI', and then sends the SRI_ACK message to the VMSC
of the caller.
6. The VMSC of the caller triggers the IN service and sends the SRI (suppression T_CSI)
message to the HLR of the callee for routing information.
7. The HLR of the callee sends the PRN message carrying the callee's IMSI to the VMSC of
the callee to obtain the MSRN.
8. SG transparently sends the received PRN message to the VMSC of the callee and reports
the callee's IMSI and the caller's GT and OTID in the PRN message to the IN platform
through the EXECUTE message.
10. The VMSC of the callee returns the PRN_ack message with the callee's MSRN to the HLR.
11. The SG intercepts the PRN_ack message and reports the callee's MSRN as well as the
callee's GT and DTID in the PRN message to the IN platform through the EXECUTE
message.
12. The IN platform returns the EXECUTE_ack message, instructing the SG to change the
MSRN into #MSRN.
13. The SG changes MSRN into #MSRN and then sends the message to the HLR of the callee.
14. The HLR of the callee returns the SRI_ack message carrying #MSRN to the VMSC of the
caller.
15. The SG intercepts the SRI_ACK_MSRN message and reports the #MSRN through the
EXECUTE message to the IN platform.
16. The IN platform returns the EXECUTE_ack message, instructing the SG to change #MSRN
into MSRN.
17. The SG changes #MSRN into MSRN and then sends the message to the VMSC of the
caller.
14.2.4 Requirements on Cooperating Equipment

The ISTP and GMSC send international roaming messages to the SG.

This section describes the impact of the IRVAS service on IN services and supplementary
services.
Impact on IN Services
Provided that a subscriber has subscribed to the callee oriented IN services. When the SRI_ack
message carrying the T_CSI does not pass through the SG, it does not affect the processing of
the original IN service. When the SRI_ack message carrying the T_CSI passes through the
SG, the IN platform decides whether to modify the T_CSI. After the T_CSI is modified, the
subscriber's orginal IN services will not be triggered.

The IRVAS service does not affect any supplementary service.


the configuration of the IRVAS service.
This section describes the principles that must be followed during the process of configuring the
data of the IRVAS service.
This section describes the relations between data tables involved in the configuration of the
IRVAS service.
Before configuring the IRVADS service, you must collect the related data, including Outbound
Roaming Msg Proc, Country Code, and Info Report Trial Times.
This section describes the general steps for configuring the IRVAS service.

This section describes the principles that must be followed during the process of configuring the
data of the IRVAS service.
Subscriber Types
The IRVAS service involves two types of subscribers:
l Outbound subscriber: Refers to the subscriber who belongs to the local network and has
roamed to the network of a foreign carrier.
l Inbound subscriber: Refers to the subscriber who belongs to the network of a foreign carrier
and has roamed to the local network.
Outbound Subscriber
l Enable the IRVAS function
Enable the IRVAS function, configure the IRVAS software parameter table, and select the
messages that must be processed in the outbound roaming process (including UL, ISD,
RSD, and PRN).
Command: SET IRVASSOFTCFG
l Configure the MSC number segment that supports the CAMEL capabilities
In the CAMEL MSC number segment table, configure the MSC number segment that
supports the CAMEL capabilities and direct routing.
Command: ADD CMLMSCRNG
Inbound Subscriber
l Enable the IRVAS function
Enable the IRVAS function, configure the IRVAS software parameter table, and select the
messages that must be processed in the inbound roaming process (including UL, ISD, RSD,
and PRN).

Command: SET IRVASSOFTCFG

l Configure the MSC number segment that supports the CAMEL capabilities
In the CAMEL MSC number segment table, configure the MSC number segment that
supports the CAMEL capabilities and direct routing.
Command: ADD CMLMSCRNG

This section describes the relations between data tables involved in the configuration of the
IRVAS service.
Relations among RVAS Data Tables

The configuration of the IPVAS service involves three tables: IRVAS Software Configure Table,
MSC number range table supporting CAMEL capabilities and the SCCP GT translation table.
The three tables are independent from each other. There is no relation among them.
Reference Relations Between IRVAS Data Table and Other Data Tables
In the SET IRVASSOFTCFG command, the IN SPC Index parameter adopts the indexes of
the destination signaling points added through the ADD N7DSP command.
The SCCP GT translation adopts the indexes of the destination signaling points added through
the ADD N7DSP command.

Before configuring the IRVADS service, you must collect the related data, including Outbound
Roaming Msg Proc, Country Code, and Info Report Trial Times.
Table 14-1 and Table 14-2 list the data to be collected before you configure the IRVAS service.
Table 14-1 Local office data collection table

Outbound Inbound Roaming Call out SRI_ack Call in
Roaming Msg Proc Msg Proc msg proc ind SRI_ack msg
proc ind
Country code Mobile country code Info report timeout Info report
(s) trial times
IN SPC index System parameter

Table 14-2 Subscriber data collection table (Camel MSC Number Range Table)
Start MSC number End MSC number

This section describes the general steps for configuring the IRVAS service.
Table 14-3 shows the steps for configuring the IRVAS service.
Table 14-3 Steps for configuring the IRVAS service.

Step Operation
1 Configure the IRVAS software parameters.
2 Configure the MSC number segment that supports the CAMEL capabilities.
3 Configure the SCCP GT translation (optional).
14.4 Configuring the IRVAS Service

The configuration of the IRVAS service involves: configuring the IRVAS software parameters,
configuring the MSC number segment supporting the CAMEL capabilities, and configuring the
SCCP GT translation table.
14.4.1 Configuring the IRVAS Software Parameters
In this section, you can configure the parameters of the IRVAS service.
14.4.2 Configuring the MSC Number Segment Supporting the CAMEL Capabilities
You can specify which MSCs support CAMEL and direct routing.
You can configure the GT translation data for the VMSC.
14.4.1 Configuring the IRVAS Software Parameters

In this section, you can configure the parameters of the IRVAS service.
Command
SET IRVASSOFTCFG

Parameter
r ID r Name
OUTMSG Outbound It specifies the messages that must be processed by the SG in the
Roaming outbound roaming process. The options include
Msg Proc UPDATE_LOCATION, RESTORE_DATA,
INSERT_SUBSCRIBER_DATA, and
PROVIDE_ROAMING_NUMBER. When the related switch is
on, the SG intercepts the messages passing through it and reports
the related information to the IN platform.
INMSG Inbound It specifies the messages that must be processed by the SG in the
Roaming inbound roaming process. The options include
Msg Proc UPDATE_LOCATION, RESTORE_DATA,
INSERT_SUBSCRIBER_DATA, and
PROVIDE_ROAMING_NUMBER. When the related switch is
on, the SG intercepts the messages passing through it and reports
the related information to the IN platform.
OUTSRI Call out When a local subscriber calls an inbound subscriber, the parameter
ACK SRI_ack specifies whether the SG needs to report the MSRN or T_CSI to
msg proc the IN platform after the SG receives the SRI_ack message. The
ind options include report MSRN and report T_CSI.
INSRIAC Call in When a foreign subscriber calls an outbound subscriber, the

K SRI_ack parameter specifies whether the SG needs to report the MSRN or
msg proc T_CSI to the IN platform after the SG receives the SRI_ack
ind message. It can be set to Report MSRN, Report T_CSI, or
T_CSI.
COUNTR Country It specifies the country code of the local network. The country code
YCODE code together with the VLR number can be used to identify the
subscriber type (inbound roaming subscriber or outbound
subscriber).
MCNTYC Mobile It specifies the mobile country code of the local network. It is used
D country together with the IMSI to identify the subscriber type (inbound
code roaming subscriber or outbound subscriber).
INFOTIM Info report It specifies the maximum duration during which the SG waits for
ER timeout(s) the response from the IN platform after it sends the EXECUTE
message to the IN platform. The parameter involves the resources
saved in the SG. After the parameter is modified, you need to reset
the resource board.
INFOTRI Info report It specifies whether the SG resends the EXECUTE message if the
AL trial times SG fails to receive response message from the IN platform during
the period of Info report timeout after it has sent the EXECUTE
message. The parameter involves the resources saved in the SG.
After the parameter is modified, you need to reset the resource
board.


r ID r Name
NIDX IN SPC It specifies the signaling point code of the IN platform.

index
SYSPAR System It specifies the frequency (times per second) at which the SG
A parameter processes the location update flow. The parameter together with
Info report timeout(s) and Info report trial times jointly specfies
the quantity of resources in the SG. The values of these parameters
are in direct proportion to the quantity of resources. After this
parameter is modified, you must reset the resource module.
Therefore, run this command with caution.
Related Commands
Table 14-4 Commands for Setting Software Parameters
Command Function
SET IRVASSOFTCFG To configure the IRVAS software parameters
LST IRVASSOFTCFG To query the IRVAS software parameters
14.4.2 Configuring the MSC Number Segment Supporting the

CAMEL Capabilities
You can specify which MSCs support CAMEL and direct routing.
Command
ADD CMLMSCRNG
Parameter
r ID r Name
FROMMS Start MSC Parameters Start MSC number and End MSC number jointly
C number specify the MSCs that have the CAMEL capability. They are
mandatory. The value of every parameter is a string of no more
than 16 characters and can contain digits 0-9 and characters A-D.
l The length of Start MSC number must be the same as that of
End MSC number.
l Start MSC number cannot be larger than End MSC
number.


r ID r Name
TOMSC End MSC l The number segments of different records cannot be overlapped
number or intersected.
Related Commands
Table 14-5 Commands for setting MNP software parameters

Command Function
ADD CMLMSCRNG To add an MSC supporting the CAMEL capabilities
MOD CMLMSCRNG To modify an MSC supporting the CAMEL capabilities
RMV CMLMSCRNG To delete an MSC supporting the CAMEL capabilities
LST CMLMSCRNG To query an MSC supporting the CAMEL capabilities

You can configure the GT translation data for the VMSC.
Command
ADD SCCPGT
Parameter
r ID r Name
DESC Descriptio It describes GT translation configurations. It is recommended to

n adopt meaningful description.
NI Network It specifies the network to which the DPC in the result of GT

indication translation belongs. The Network indication and DPC must have
been defined in the DSP table.


r ID r Name
RT Translatio It specifies the format of the GT translation result, including:

n result l STP1: It means that the translation result adopts the format of
type "DPC + GT".
l LSPC1: It means that the translation result adopts the format of
"DPC + SSN".
l STP2: It means that the translation result adopts the format of
"DPC + NEWGT".
l LSPC2: It means that the adopts the format of DPC.
WM GT work It specifies a work mode of GT translation, including:

mode Single point work mode: In this mode, you do not need to configure
the index of SCCP addressing policy.
Multi-point work mode: In this mode, you must configure the index
of SCCP addressing policy.
DX DPC It specifies a DPC to be referenced after the translation. The

index referenced DPC is in the DSP table.
GT GT It specifies the GT indicator. There are six options for the

indicator parameter, including GT1 (ITU GT1), GT2 (ITU GT2), GT3 (ITU
GT3), GT4 (ITU GT4), GT5 (ANSI GT1), and GT6 (ANSI GT2).
Generally, GT4 is adopted as the GT indicator.
CP Numberin It refers to the numbering plan of the GT. It specifies the coding
g plan mode of the address, including:
l UNDEF (Undefined)
l STANDBY (Standby)
In China, E212, E164, and E214 are mainly applied. E212 is the
coding mode adopted in the communication between the base
station and the MSC; E164 is used for searching the callee; E214
is for updating the location of a roaming subscriber.


r ID r Name
AI Nature of It specifies the nature of the address indicator, including:

address l FREE (Idle)
indicator
INTER is commonly used.
AF Address It specifies a subscriber number to be translated. This number

message consists of country code, toll area code, and subscriber number.
The number can be up to 24 digits. For example, in the address
message of 8675528960132, 86 is the country code, 755 is the area
code, and 28960132 is the user number.
The wildcard of "E" or "e" can be used in the address message to
represent all digits. For example, "(86) (755) 2896-EEEE" stands
for all subscriber numbers with the prefix "(86) (755) 2896".
NOTE
When GT work mode is set to Multi-point work mode, you do not need to configure parameters DPC
index and SSN code.
Related Commands
Table 14-6 Commands for configure the HLR address.
Command Function
ADD SCCPGT To add a GT
MOD SCCPGT To modify a GT
RMV SCCPGT To delete a GT
LST SCCPGT To query a GT

This section describes examples of configuring the IRVAS service.
Example Description
Table 14-7 and Table 14-8 show the data collected for the IRVAS service.

Table 14-7 Local office data collection table

Outbound Inbound Roaming Call out SRI_ack Call in
Roaming Msg Proc Msg Proc msg proc ind SRI_ack msg
proc ind
All messages All messages Report MSRN, report Report MSRN,

T_CSI report and
modify T_CSI
Country code Mobile country code Info report timeout Info report
(s) trial times
86 460 3 1
IN SPC index System parameter
0 400
Table 14-8 Subscriber data collection table (CAMEL MSC Number Range Table)
Start MSC number End MSC number
5701234 5701234
Procedure
Step 1 Configure the IRVAS software parameters.
Select UL, RSD, ISD, and PRN for Outbound Roaming Msg Proc; select UL, RSD, ISD, and
PRN for Inbound Roaming Msg Proc; select Report MSRN and Report T_CSI for Call out
SRI_ack msg proc ind; select Report MSRN, Report T_CSI, and Modify T_CSI for Call in
SRI_ack msg proc ind; set Country Code to 86; set Mobile country code to 460; set Info
report timeout(s) to 3; set Info report trial times to 1; set IN SPC index to 0; set System
parameter to 400. The command is as follows:
SET IRVASSOFTCFG: OUTMSG=BIT0-1&BIT1-1&BIT2-1&BIT3-1,
INMSG=BIT0-1&BIT1-1&BIT2-1&BIT3-1, OUTSRIACK=BIT0-1&BIT1-1,
INSRIACK=BIT0-1&BIT1-1&BIT2-1, COUNTRYCODE="86", MCNTYCD="460",
INFOTIMER=3, INFOTRIAL=1, NIDX=0, SYSPARA=400;
Step 2 Configure the Camel Msc Number Range Table.

Set Start MSC number to 5701234; set End MSC number to 5701234.The command is as
follows:
ADD CMLMSCRNG: FROMMSC="5701234", TOMSC="5701234";
----End
Verify the IRVAS software parameters.

Perform this operation only after you have configured the IRVAS service parameters. To verify
the IRVAS service parameters, run the LST MNPSOFTCFG command on the MML client.

LST IRVASSOFTCFG:;

IRVAS service software parameters
----------------------
Outbound Roaming Msg Proc = G_4<ON>G_3<ON>G_2<ON>G_1<ON>
Inbound Roaming Msg Proc = G_4<ON>G_3<ON>G_2<ON>G_1<ON>
Call out SRI_ack msg proc ind = G_2<ON>G_1<ON>
Call in SRI_ack msg proc ind = G_3<ON>G_2<ON>G_1<ON>
Country Code = 86
Mobile country code = 460
Info report timeout(s) = 3
Info report trial times = 1
IN SPC index = 0
System parameter = 400
--- END
The results are the same as the data configured for the MNP service, indicating that the
Verify the MSC number segment supporting the CAMEL capabilities.

Perform this operation only after you have configured the MSC number segment supporting the
CAMEL capabilities. To verify the MSC number segment supporting the CAMEL capabilities,
run the LST CMLMSCRNG command on the MML client.
LST CMLMSCRNG:;

CAMEL MSC Number Range Table
---------------------- Index Description Start MSC number

End MSC number
0 <NULL> 222 222

1 <NULL> 111 111
2 <NULL> 5701234 5701234
(result count = 3)
--- END
Record 2 is the same as the configuration data. Configuring the CAMEL MSC Number Range
Table succeeds.

Feature Description 15 Configuring IN BYPASS Service Data
15 Configuring IN BYPASS Service Data
About This Chapter
This section describes the service flow, preparations, and general steps for configuring the IN
BYPASS service, and troubleshooting during the configuration.
15.1 Service Introduction

This section describes the definition, terms, service advantages, and version requirements of the
IN BYPASS service.
15.2 Service Processing Flow
This section describes the processing flow of the IN BYPASS service.
This section describes the preparations for configuring the IN BYPASS service.
15.4 Data Configuration
This section describes the detailed procedures for configuring the IN BYPASS service.
The section provides the detailed example to demonstrate how to configure the IN BYPASS
service.
15.6 Troubleshooting
This section describes how to handle the problems during the configuration.

15 Configuring IN BYPASS Service Data Feature Description

This section describes the definition, terms, service advantages, and version requirements of the
IN BYPASS service.

This section describes the definition of the IN BYPASS service.
15.1.2 Terms
This section describes the terms used in the IN BYPASS service.
This section describes the interaction requirement of the IN BYPASS service.
15.1.4 Service Benefits
This section describes the benefits of the IN BYPASS service.
This section describes the version requirement for the IN BYPASS service.
15.1.6 Equipment Cooperation Requirement
This section describes the equipment cooperation requirement for the IN BYPASS service.

This section describes the definition of the IN BYPASS service.
The IN BYPASS service is developed to reduce the load of the intelligent (IN) platform. In a
specific time period, the SG processes the IN messages and voice calls coming from the specific
subscribers instead of forwarding them to the IN platform for charging, thus reducing the load
of the IN platform.
15.1.2 Terms
This section describes the terms used in the IN BYPASS service.
Specific Subscribers
A specific subscriber refers to a prepaid subscriber who has registered the free or premium
services of carriers.
Specific Time Period

A specific time period refers to a period during which the premium services are free of charge.
Carriers are responsible for defining the specific time periods; thus, subscribers can choose
corresponding time periods based on actual requirements.

This section describes the interaction requirement of the IN BYPASS service.
The processing of the MNP service conflicts with that of the prepaid premium service. Therefore,
the system cannot process the INAP IDP and CAP IDP messages at the same time.


This section describes the benefits of the IN BYPASS service.
For Carriers
l This service enables carriers to take the leading position in providing subscribers with
customized and differentiated services, and promotes the enterprise status of carriers.
l With this service, the extra messages sent to the IN platform are filtered, which reduces the
load of the IN platform and saves carriers' investments in expanding the capacity of the IN
platform.
l It is very easy to enable this service by deploying an SG in the network without changing
any other network elements (NEs).
For Subscribers
More customized choices and flexible time segments of the premium service meet the
requirements of different subscribers.

This section describes the version requirement for the IN BYPASS service.
The version requirements are as follows:
l This service is provided in V200R001 B05D210 and later versions.
l There is no special requirement for the hardware.

This section describes the equipment cooperation requirement for the IN BYPASS service.
The messages sent to the MSC must contain the information of charge free or not. The MSC
automatically resolves messages and sends those that require performing the IN filter service to
the SG.

This section describes the processing flow of the IN BYPASS service.

This section describes the networking structure of the IN BYPASS service.
15.2.2 Service Implementation Principle
This section describes the implementation principle of the IN BYPASS service.
15.2.3 Calling Flow
This section describes the calling flow of the IN BYPASS service.

This section describes the networking structure of the IN BYPASS service.

Figure 15-1 shows the networking structure of the IN BYPASS service.
Figure 15-1 Networking structure of the IN BYPASS service
SG: U-SYS SG7000 Signaling Gateway SCP: Service Control Point

MSC: Mobile Switching Center SMSC: Short Message Service Center
l SG: It is used to store the service data for subscribers. It also acts as the filter device to
filter the extra messages sent to the IN platform.
l SCP: It is used to store the user data and service logics. It also controls the IN service
implementation.
l MSC: It is used to distribute the filtered IN service messages to the SG and forward the
SG processed IN messages to the SCP.
l SMSC: It is used to store and distribute short messages.

This section describes the implementation principle of the IN BYPASS service.
To implement the IN BYPASS service, carriers only need to connect the SG with the MSC
through ordinary links rather than adding other NEs. After the SG processes the filtered IN
service messages, the MSC forwards them to the SCP. The implementation process of the IN
BYPASS service is as follows:

1. The network sends a message that contains the charge free information to the MSC.
2. The MSC resolves the message and sends the message to the SG.
3. The SG determines the processing process based on the configuration and returns the
corresponding message to the MSC based on the determination to control whether the IN
service message sent to the MSC by the SG after being processed should be sent to the
SCP.
In this way, the messages meeting the conditions are not sent to the SCP for charging, thus
reducing the load of the IN platform.
15.2.3 Calling Flow

This section describes the calling flow of the IN BYPASS service.
Protocols Supported by IN BYPASS

The IN BYPASS service can be classified into:
l Short message IN BYPASS service
l Voice call IN BYPASS service
The messages processed in the IN BYPASS service are as follows:

l In the short message IN BYPASS service:
l IDPSMS messages with the CAP protocol version of CAP3
l IDP messages with the private expansion INAP protocol
l In the voice call IN BYPASS service:
l CAP-IDP messages with the CAP protocol version of CAP2
IN BYPASS Signaling Flow

Figure 15-2 and Figure 15-3 show the signaling flow of the IN BYPASS service.
Figure 15-2 Signaling flow of the IN BYPASS service
MSC SG
IDP (called number&calling
number)
1
CONTINUE
2

Figure 15-3 General signaling flow
MSC SG SCP
IDP (called number&calling

number)
1
IDP
2
IDP
3
The signaling flow is as follows:

1. After resolving that the message contains the charge free information, the MSC sends an
IDP message to the SG. The IDP message contains the called and calling MSISDNs.
2. The SG queries the configured data to identify the premium time period of the caller and
check whether the caller and callee belong to the same prepaid service brand based on the
configured number range information and filter time segment of the prepaid service brand.
3. The SG transparently forwards the message if the GT is not consistent with the configured
GT.
4. If any other condition except GT is false, the system processes the message according to
the ordinary flow, that is, the SG returns an IDP message to the MSC and the MSC sends
the IDP message to the SCP for charging.
5. The SG directly returns the CONTINUE message to the MSC if the called GT is the same
as the configured GT, the calling service is in the premium time period, and the caller and
callee belong to the same prepaid service brand. That is to say, the message is free of charge
and thus is not sent to the SCP.
NOTE
The preceding flow indicates the short message signaling flow. Messages in the flow vary with message-
related protocols and message types.

This section describes the preparations for configuring the IN BYPASS service.

This section describes the relations between data tables of the IN BYPASS service.
15.3.2 Data Configuration Requirements on Interworking Equipment
This section describes data configuration requirements on interworking equipment in the IN
BYPASS service.
This section describes the data to be collected for configuring the IN BYPASS service.
This section describes the principle for configuring the IN BYPASS service.
15.3.5 General Procedures

This section describes the general steps for configuring the IN BYPASS service.

This section describes the relations between data tables of the IN BYPASS service.
The following five tables are related to the IN BYPASS service:
l The SMS software parameter table

l The SCP address table
l The MNP local number range table
l The service user data table
l The filter time segment table
Figure 15-4 shows the relations between these data tables.
Figure 15-4 Relations between data tables in the IN BYPASS service
15.3.2 Data Configuration Requirements on Interworking

Equipment
This section describes data configuration requirements on interworking equipment in the IN
BYPASS service.
None.


This section describes the data to be collected for configuring the IN BYPASS service.
Table 15-1 lists the data to be collected before the configuration.
IN filter type Country code Local GT address
Charge control for Transfer mode SCP address

different brands
Number range brand type Start local network End local network number
number
MSISDN Whether enable related Route index type (here,

services (here, choose choose Filter time segment
Enable prepaid discount index)
service)
Filter time segment index SCP address index
SMS start time SMS end time VoiceCall start time
VoiceCall end time
NOTE
The data collection table consists of all data to be configured in the five tables.

This section describes the principle for configuring the IN BYPASS service.
Unless otherwise specified, the data must be configured based on actual conditions.

This section describes the general steps for configuring the IN BYPASS service.
Table 15-2 lists the general procedures for configuring the IN BYPASS service data.

Table 15-2 General procedures for configuring the IN BYPASS service data
Step Operation
1 To set the SMS software parameter (SET SMSICSOFTCFG)
2 To add the SCP address (ADD SCPADDR)
3 To add the MNP local network number range (ADD MNPLOCNRNG)
4 To add the filter time segment (ADD FLTM)
5 To add service user data (ADD SERUATTR)

This section describes the detailed procedures for configuring the IN BYPASS service.
15.4.1 Setting the SMS Software Parameter

This section describes how to set the SMS software parameters.
15.4.2 Adding the SCP Address
This section describes how to add the SCP address.
15.4.3 Adding the MNP Local Network Number Range
This section describes how to add the MNP local network number range.
15.4.4 Adding the Filter Time Segment
This section describes how to add the filter time segment.
15.4.5 Adding the Service User Data
This section describes how to add the service user data.
15.4.1 Setting the SMS Software Parameter

This section describes how to set the SMS software parameters.
This section describes how to set the SMS software parameters related to the IN BYPASS
service.
Command
SET SMSICSOFTCFG

Parameter
Parameter ID Parameter Name Parameter Description
SMSINFLTTP IN filter type It indicates the type of the message to be filtered

in the IN BYPASS service. It can be set to one or
more of the following values:
l CAP IDP SMS: When it is selected, the system
filters the IDPSMS message of which CAP
protocol version is CAP3.
l INAP IDP SMS: When it is selected, the
system filters the IDPSMS message in the
INAP protocol.
l CAP IDP: When it is selected, the system
filters the CAP-IDP message of which CAP
protocol version is CAP2.
l INAP IDP: When it is selected, the system
filters the IDP message in the INAP protocol.
It must be set based on actual conditions.
COUNTRYCOD Country code It is used to exclude the country code when you
E query user numbers. By default, no country code
is set. It must be set based on actual conditions.
LOCALGT Local GT address It indicates the actual GT address of the

equipment and is used to compare the called GT
address in the message processing flow. It must
be set based on actual conditions. If the called GT
is the same as this GT, the system sends the
message to the service processing module;
otherwise, the system transparently forwards the
message.
FREETYPE Charge control for It is used to control the premium strategy of voice
different brands calls and short messages between different
service brands. It can be set to one or more of the
following values:
l Free for Brand1 to Brand2 For short message
l Free for Brand2 to Brand1 For short message
l Free for Brand1 to Brand2 For voice call
l Free for Brand2 to Brand1 For voice call

MODRELAYMS Mode of relaying For a short message coming from the MSC in the
G messages IN BYPASS service, the system determines
whether to send the message to the SCP:
l If yes, the system returns a Continue message
to the MSC and the MSC does not send the
message to the SCP.
l If not, the system replaces the called address in
the message with the SCP address (configured
by ADD SCPADDR and referenced by the
MNP local number range table) and then
returns the message to the MSC after
processing the message based on the
configuration of this parameter. After that, the
MSC sends the message to the SCP for
subsequent processing.
Before returning the message to the MSC, the
system can process the message in either of the
following ways:
l GTTRAN (GT translation): The system sends
the message to the SCCP layer. After the GT
translation, the system returns the message to
the MSC.
l BACKDPC (Relay to original signal point):
The system exchanges the calling and called
signaling point code in the message and then
sends the message to the original signaling
point over the MTP layer, that is, the system
returns the message to the original MSC.
Other parameters are irrelevant to this service,
and thus they can be set based on actual
conditions.
Related Commands
Table 15-3 Related commands for configuring the SMS software parameter
Command Function
SET To set the SMS software parameter

SMSICSOFTCFG
LST To query the SMS software parameter

SMSICSOFTCFG

15.4.2 Adding the SCP Address

This section describes how to add the SCP address.
Command
ADD SCPADDR
Parameters
Parameter ID Parameter Parameter Description
Name
SCP SCP address It maps the actual address of an SCP. An SCP

address contains numbers only. Its length cannot
exceed 16 digits.
Related Commands
Table 15-4 Related commands for configuring the SCP address

Command Function
ADD SCPADDR To add the SCP address
MOD SCPADDR To modify the SCP address
RMV SCPADDR To remove the SCP address
LST SCPADDR To query the SCP address
15.4.3 Adding the MNP Local Network Number Range

This section describes how to add the MNP local network number range.
This command is used to distinguish service brands among different number ranges in the IN
BYPASS service.
Command
ADD MNPLOCNRNG

Parameters
Paramete Parameter Name Parameter Description
r ID
NUMTYP Number range type It indicates the type of the brand mapping the MNP local
E network number range added. It must be selected based
on actual conditions.
STARTN Start local network It indicates the start number of a local network number
UM number range. It must be set based on actual conditions.
ENDNU End local network It indicates the end number of a local network number
M number range. It must be set based on actual conditions.
SCPIDX SCP address index It maps a record in the SCP address table. It indicates the
SCP address mapping this number range (defined
together by Start local network numberand End local
network number). In the IN BYPASS service, for the
messages to be sent to the SCP, the system queries the
SCP address based on the SCP address index mapping
the number range to which the calling number belongs.
This index must be defined by ADD SCPADDR before
being referenced here.
NOTE
l The length of Min foreign number must be the same as that of Max foreign number.
l The number ranges in the MNP local network number range table cannot be overlapped or intersected.
l The number ranges in the MNP local network number range table cannot be overlapped or intersected
with those in the MNP foreign number range table.
l The values of Routing number index, HLR address index, and SCP address index must be valid.
Other parameters are irrelevant to this service, and thus they can be set based on actual conditions.
Related Commands
Table 15-5 Related commands for configuring the MNP local network number range
Command Function
ADD MNPLOCNRNG To add the MNP local network number range
MOD To modify the MNP local network number range

MNPLOCNRNG
RMV To remove the MNP local network number range

MNPLOCNRNG
LST MNPLOCNRNG To query the MNP local network number range

15.4.4 Adding the Filter Time Segment

This section describes how to add the filter time segment.
This command is used to add the premium time segment information in the IN BYPASS service.
Command
ADD FLTM
Parameters
STIME SMS start time It indicates the start time of the subscriber short
message bypass in the IN BYPASS service.
ETIME SMS end time It indicates the end time of the subscriber short
message bypass in the IN BYPASS service.
YSTIME VoiceCall start time It indicates the start time of the subscriber voice
call bypass in the IN BYPASS service.
YETIME VoiceCall end time It indicates the end time of the subscriber voice
call bypass in the IN BYPASS service.
NOTE
You must save the index of the added data record for subsequent reference.
Related Commands
Table 15-6 Related commands for configuring the filter time segment
Command Function
ADD FLTM To add the filter time segment
MOD FLTM To modify the filter time segment
RMV FLTM To remove the filter time segment
LST FLTM To query the filter time segment
15.4.5 Adding the Service User Data

This section describes how to add the service user data.
This command is used to add the service user data related to the IN BYPASS service.

Command
ADD SERUATTR
Parameter
Name
USRNUM MSISDN It indicates the logical number that uniquely identifies

a subscriber. It contains no country code, such as,
13312345678. It must be set based on actual
conditions.
SERVATTR Whether enable It indicates the service to be enabled by a subscriber. It

related services can be set to one or more of the following values:
l OCR (Enable RBT service)
l OMNP (Enable MNP service)
l OIMEI (Enable IMEI service)
l OMC (Enable MC service)
l OINBPS (Enable prepaid discount service)
l OSMR (Enable SMR service)
The configuration principles are as follows:
l The MC service and the SMR service cannot be
simultaneously enabled.
l The MNP service and the prepaid premium service
cannot simultaneously choose to process the INAP
IDP or CAP IDP message.
l When the MC service is enabled, MC routing
index references the index configured in the MC
routing number table.
l When the SMR service is enabled, MC routing
index references the index configured in the MC
local SC address table.
In the IN BYPASS service, you cannot select Enable
MNP service but you must select Enable prepaid
discount service. Other services are selected based on
actual conditions.
RNIDXTYPE Route index type It can be set to:

l HLR address index
l Route number index
l HLR+RN
l Filter time segment index
In the IN BYPASS service, you must select Filter time
segment index.


Name
FLTTMIDX Filter time It references the data in the filter time segment table. It
segment index is used in the IN BYPASS service to determine whether
an IN voice call or IN short message is originated
during the preferential time period. You need to run
LST FLTM to confirm the index of the data to be
referenced before configuring this parameter.
Other parameters are irrelevant to this service, and thus
they can be set based on actual conditions.
Related Commands
Command Function
ADD SERUATTR To add the service user data
MOD SERUATTR To modify the service user data
RMV SERUATTR To remove the service user data
LST SERUATTR To query the service user data

The section provides the detailed example to demonstrate how to configure the IN BYPASS
service.
15.5.1 Example Description

This section describes the data collected for configuring the IN BYPASS service.
15.5.2 Configuration Description
This section describes the data configuration in the IN BYPASS service based on the data
collected in the preceding table.
15.5.3 Configuration Verification
This section describes how to verify the configured data through the MML console.
15.5.1 Example Description

This section describes the data collected for configuring the IN BYPASS service.
This example is applicable to the service networking structure as shown in Figure 15-1.
Table 15-8 lists the collected data to be used when you configure the IN BYPASS service.

IN filter type Country code Local GT address
INAP-IDPSMS, CAP- 63 1397002

IDPSMS, INAP-IDP, and
CAP-IDP messages
Charge control for Transfer mode SCP address

different brands
Not free for different brands GT translation 5833000
Number range brand type Start local network End local network number
number
Brand 1 139 139
MSISDN Whether enable related Route index type

services
13975600002 Prepaid discount service Filter time segment index
Filter time segment index SCP address index
Configure based on actual Configure based on actual

conditions conditions
SMS start time SMS end time VoiceCall start time
14 o'clock 16 o'clock 9 o'clock
VoiceCall end time
12 o'clock

This section describes the data configuration in the IN BYPASS service based on the data
collected in the preceding table.
Setting the SMS Software Parameter

To set the SMS software parameter, where IN filter type is INAP-IDPSMS, CAP-IDPSMS,
INAP-IDP, and CAP-IDP, Country code is 63, Local GT address is 1397002, Charge control
for different brands is not free for different brands, and Mode of relaying message is Global
translate, run the following command:
SET SMSICSOFTCFG: SMSINFLTTP=G1-1&G2-1&G3-1&G4-1, COUNTRYCODE="63",
LOCALGT="1397002", FREETYPE=G1-0&G2-0&G3-0&G4-0, MODRELAYMSG=GTTRAN;
Adding the SCP Address

To add the SCP address where SCP address is 5833000, run the following command:
ADD SCPADDR: SCP="5833000";

Suppose that the generated index is 0 after the SCP address is added.
Adding the MNP Local Network Number Range

To add the MNP local network number range, where Number range brand type is Prepaid
brand 1, Start local network number is 139, End local network number is 139, and SCP
address index is 0, run the following command:
ADD MNPLOCNRNG: NUMBRATYPE=BRAND1, STARTNUM="139", ENDNUM="139", SCPIDX=0;
Adding the Filter Time Segment

To add the filter time segment, where SMS start time is 14 o'clock, SMS end time is 16
o'clock, VoiceCall start time is 9 o'clock, and VoiceCall end time is 12 o'clock, run the
following command:
ADD FLTM: STIME="14&00&00", ETIME="16&00&00", YSTIME="09&00&00", YETIME="12&00&00";
Suppose that the generated index is 0 after the filter time segment is added.
Adding the Service User Data

To add the service user data, where MSISDN is 13975600002, Whether enable related
service is Enable prepaid discount service, Route index type is Filter time segment index,
and Filter time segment index is 0, run the following command:
ADD SERUATTR: USRNUM="13975600002", SERVATTR=OINBPS-1, NUMTYPE=TYPE0,
RNIDXTYPE=TIME, FLTTMIDX=0;
15.5.3 Configuration Verification

This section describes how to verify the configured data through the MML console.
Verifying the SMS Software Parameter

Run LST SMSICSOFTCFG to verify whether SMS software parameters are correctly
configured.
LST SMSICSOFTCFG:;

-----------------------
IN filter type = G_4<ON>G_3<ON>G_2<ON>G_1<ON>
Country Code = 63
Mode of relaying message = Global translate
Service type = NULL
--- END
The results comply with the data configured in the example, which indicates that the
Verifying the SCP Address

Run LST SCPADDR to verify whether the SCP address is correctly configured.

LST SCPADDR: IDX=0;

SCP Address Table
-----------------
Index = 0
SCP Address = 5833000
--- END
Verifying the MNP Local Network Number Range

Run LST MNPLOCNRNG to verify whether the MNP local network number range is correctly
configured.
LST MNPLOCNRNG: MODE=IDX, IDX=0;

MNP LOCAL NETWORK NUMBER RANGE TABLE
------------------------------------
Index = 0
Number range type = GSM NETWORK NUMBER RANGE
number range brand type = PREPAID BRAND 1
Length of Start local network number = 3
Start local network number = 139
Length of End local network number = 3
End local network number = 139
Routing number index = 65535
SCP address index = 0
--- END
Verifying the Filter Time Segment

Run LST FLTM to verify whether the filter time segment is correctly configured.
LST FLTM: MODE=IDX, IDX=0;

Filter time segment table
-------------------------
Index = 0
SMS start time = 14&00&00
SMS end time = 16&00&00
VoiceCall start time = 09&00&00
VoiceCall end time = 12&00&00
--- END

Run LST SERUATTR to verify whether the service user data is correctly configured.


---------------------------------
Index = 0
MSISDN = 13975600002
G_6<OFF>G_5<ON>G_4<OFF>G_3<OFF>G_2<OFF>G_1<OFF>
Route index type = Filter time segment index
--- END
15.6 Troubleshooting
This section describes how to handle the problems during the configuration.
WARNING
Do not run MOD FLTM to modify the filter time segment unless you have to modify it, because
the modification affects the application of other subscribers.
If the service processing fails, locate and solve the problem based on the following:
l If services of all brands fail, check whether Charge control for different brands in SET
SMSICSOFTCFG is correctly configured. If not, run SET SMSICSOFTCFG to modify
it.
l If services of the subscribers in a certain number range fail, check whether the number
range is configured in the MNP local network number range table and whether Number
range brand type is correctly configured. If not, run MOD MNPLOCNRNG to modify
accordingly.
l If services of a certain subscriber fail, run LST SERUATTR to check whether the
subscriber has enabled the prepaid premium service:
l If the subscriber has not enabled the prepaid premium service, run MOD SERUATTR to
enable the service.
l If the subscriber has enabled the prepaid premium service, run LST FLTM to check
whether the time segment mapping Filter time segment indexis the expected time. If not,
run MOD SERUATTR to modify Filter time segment index to the index mapping the
expected time segment.
l If the problem remains, contact Huawei engineers for help.

Feature Description 16 Configuring MRS Service Data
16 Configuring MRS Service Data
About This Chapter
This section describes the definition, signaling flow, preparations, general steps, and
configuration examples related to the message reroute service.
This section describes the definition, terms, service interaction, benefits, and configuration
requirements of the message reroute service.
This section describes the processing flow of the message reroute service.
This section describes the preparations for configuring the message reroute service.
16.4 General Procedures
This section provides detailed procedures for configuring the message reroute service.
16.5 Configuration Example
The section provides the detailed example to demonstrate how to configure the message reroute
service.

16 Configuring MRS Service Data Feature Description

This section describes the definition, terms, service interaction, benefits, and configuration
requirements of the message reroute service.

This section gives the definition of the message reroute service.
16.1.2 Terms
This section describes the terms used in the message reroute service.
This section describes the related rules for the message reroute service to interact with other
services.
This section describes the benefits of the message reroute service.
This section describes the version and hardware requirements for the message reroute service.
This section describes the equipment cooperation requirement for the message reroute service.

This section gives the definition of the message reroute service.
The message reroute service is developed to meet the application requirement in the existing
networks. It is used to reroute the special messages, that is, the system routes these messages to
the specified equipment for special processing (for example, triggering supplementary services)
and then sends them back to the SG7000 or other equipment.
16.1.2 Terms
This section describes the terms used in the message reroute service.
Message Reroute
The message reroute indicates that the system changes the original route of a message and
allocates another route for the message based on some special conditions.
SCCP Reroute
The SCCP reroute indicates that the system determines the route of a message based on the
SCCP-layer information of the message. It is used to reroute messages at the network side.
MAP Reroute
The MAP reroute indicates that the system determines the route of a message based on the MAP-
layer information of the message. It is used to reroute messages at the subscriber side.


This section describes the related rules for the message reroute service to interact with other
services.
The message reroute service conflicts with the message screening and internationally roaming
services.

This section describes the benefits of the message reroute service.
For the Carrier

The advantages of the message reroute service for carriers are as follows:
l This service enables carriers to take the leading position in providing subscribers with
customized and differentiated services, and promotes the enterprise status of carriers.
l This service meets the requirements of customers on special services. The newly added
supplementary service is processed on the new service platform, which reduces the change
of the external network element (NE). This also reduces the impact on the services on the
original platform.
l It is easy to enable this service by deploying a signaling gateway (SG) as the message filter
equipment in the network without changing any other NEs.
l It is convenient to add an NE to process the special messages filtered and sent by the SG.
Thus, the special service is implemented, cost is reduced, and customer satisfaction is
improved.
For the Subscriber

Messages can be routed based on customer requirements, which can meet different requirements
of subscribers.

This section describes the version and hardware requirements for the message reroute service.
The version requirements are as follows:
l This service is provided in V200R001 and later versions.

l There is no special requirement on the hardware.

This section describes the equipment cooperation requirement for the message reroute service.
Some segmented messages do not contain operation codes. In this case, when rerouting messages
based on the MAP protocol, the system reroutes only TC_Begin messages containing operation
codes. Other messages are processed according to the original flow. At present, the system does
not support rerouting messages based on the CAP protocol.


This section describes the processing flow of the message reroute service.

This section describes the networking structure of the message reroute service.
This section describes the principle for implementing the message reroute service.
16.2.3 Calling Flow
This section describes the calling flow of the message reroute service.

This section describes the networking structure of the message reroute service.
Figure 16-1 shows the networking structure of the message reroute service.
Figure 16-1 Networking structure of the message reroute service
l SG: It is used to store the service data for subscribers. It also acts as the reroute device to
reroute the specified messages.
l Source Node: It is the source point of a rerouted message.
l Dest Node: It is the destination point of a message. Originally, a message should be sent
to the Dest Node after being processed by the SG.
l Reroute Special Node: It is the message rerouted point. A message is sent to this point after
being rerouted by the SG.


This section describes the principle for implementing the message reroute service.
To implement the message reroute service, you only need to connect the SG to the Source Node
through ordinary links rather than adding other NEs. The SG filters the received messages over
the link set (MTP or M3UA links) configured with the message reroute function.
1. The SG judges whether the received message meets the reroute conditions based on the
information contained in the message.
Reroute conditions contain the following: Whether local termination, OPC, DPC, called
GT, calling GT, and MAP operation codes.
2. If the received message meets the reroute conditions, the SG processes the message
according to the configured processing rules.
Message processing rules contain the following: Reroute on DPC unreachable, whether
modify DPC, rerouted node DPC1, rerouted node DPC2, node failure processing mode,
and whether enable service processing.
3. The SG performs the subsequent processing on the message based on the processing rule.
If the service processing is not required, the SG routes the message to the specified
equipment based on the SCCP reroute result. If required, the SG sends the message to the
service module for the MAP reroute.
4. The service module determines whether to perform the MAP reroute based on the calling
GT (if required), called GT (if required), and IMSI/MSISDN in the message.
The rules for the service module determining whether to perform the MAP reroute are as
follows:
(1) For the MO message: Based on the called GT (SMSC address) in the message, the
service module judges whether the message should be rerouted. If yes, the module
obtains the reroute result based on the calling GT (MSC address) and calling MSISDN.
(2) For the SRI_For_SM message: The module obtains the reroute result based on the
MSISDN.
(3) For the IMSI addressing message: The module obtains the reroute result based on the
calling GT (MSC address) and IMSI.
5. The SG reroutes the message to the specified equipment based on the reroute result.
NOTE
l For a message to be rerouted, you can configure the data to determine whether to modify the
DPC in the message. In the case that the rerouted destination signaling point is unreachable, you
can configure the data to determine whether to discard the message or send the message based
on the original route. For details on data configuration, see subsequent sections.
l The IMSI addressing messages related to the message reroute service include the
sendAuthenticationInfo, purgeMS, readyForSM, restoreData, updateLocation, and
updateGprsLocation messages. In the subsequent context, the IMSI addressing message refers
to all these messages.
l When failing to perform the MAP reroute on the message, the system cannot perform the SCCP
reroute on the message again. Instead, the system sends the message to another service module
or transfers the message based on the original route.
16.2.3 Calling Flow

This section describes the calling flow of the message reroute service.

Protocols Supported by the Message Reroute Service

The message reroute service can be classified into the SCCP and MAP reroute services.
1. The SCCP reroute service supports the SS7 protocol and the M3UA protocol.
2. The MAP reroute service supports the SS7 protocol, the M3UA protocol, and the MAP
protocol.
Signaling Flow of the Message Reroute Service
Figure 16-2 Signaling flow of the message reroute service
The signaling flow of the message reroute service is as follows:

l If message reroute is not required, the SG directly sends the message to the destination
equipment. The signaling flow is as shown by the yellow line in Figure 16-2
l If message reroute is required, the SG sends the message to the specified reroute equipment
(for example, the intelligent value-added platform) based on the information combination
contained in the message. The signaling flow is as shown by the blue lines in Figure 16-2
NOTE
The preceding flow indicates the message signaling flow. Messages in the flow vary with message-related
protocols and message types.
In the SCCP reroute, except for operation codes, other settings are not subject to message types. At present,
the MAP reroute processes only the MO, SRI_For_SM, and IMSI addressing messages.

This section describes the preparations for configuring the message reroute service.

This section describes the relations between data tables of the message reroute service.

This section describes the data configuration requirements on interworking equipment in the
message reroute service.
This section describes the data to be collected for configuring the message reroute service.
This section provides some related descriptions for configuring the message reroute service.
This section describes the general steps for configuring the message reroute service.

This section describes the relations between data tables of the message reroute service.
Figure 16-3 shows the relations between the data tables related to the message reroute service.

Figure 16-3 Relations between the data tables related to the message reroute service
ADD RROPC
[Reroute reference]
Type of next
[ ] SET SOFTCFG
reroute table
[ Next reroute reference ]
Routing redirection
[ service ]
ADD RRDPC
Reroute service
[ Send msg fail proc ]
[Reroute reference]
Type of next Reroute service
[ ] [ ]
reroute table DPC proc
ADD N7LKS ADD RRCDGT
Service process MAP service reroute
[ ]
switch [Reroute reference]
[Reroute Policy] Type of next ADD N7DSP
[ ]
reroute table
Type of next [ Next reroute reference ]
[ reroute table ] [ DPC index ]
[ Next reroute ] ADD RRCGGT

reference ADD RRCDGTRNG
[Reroute reference]
ADD M3ASSOS [Begin GT number]
Type of next
Service process [ ] [End GT number]
[ ] reroute table
switch [ Next reroute reference ]
ADD RRCGGTRNG
[Reroute Policy] ADD RROC
Type of next
[ reroute table ] [Reroute reference] [Begin GT number]
[Operation code] [End GT number]

[ Next reroute ]
reference [Type of next reroute table]
ADD RRUSRNUM
[Next reroute reference]
ADD RRRULE Reroute GT number
[ range index ]
Reroute processing [Reroute number]
[ Rule index
]
[Load-share select mask] [ DPC index ]
[ Destinations 0-15 ]
[Priorities 0-15]
[Reroute rule switch]
[Reroute direction]
The message reroute service can be classified into the SCCP and MAP reroute services. The
SCCP reroute is the basis of the MAP reroute, as shown by the blue lines in Figure 16-3.

The system performs the MAP reroute when all the following parameters are correctly
configured:
l Operation code in the reroute operation code table
l Reroute direction in the reroute direction table
l Routing redirection service in the software parameter configuration table
In the SCCP reroute, Reroute reference is used to match the combination of Type of next
reroute table and Next reroute reference configured in its previous step. Table 16-1 lists the
matching relations between the data tables related to the SCCP reroute.
Table 16-1 Matching relations between the data tables related to the SCCP reroute
Matching Object (Reroute Object for Obtaining Matching Relations
Reference) (Combination of Type of Next Reroute Table and
Next Reroute Reference Configured in its Previous
Step)
Reroute OPC table Link set table (MTP; M3UA)
Reroute DPC table Link set table; Reroute OPC table
Reroute called GT table Link set table; Reroute OPC table; Reroute DPC table
Reroute calling GT table Link set table; Reroute OPC table; Reroute DPC table;
Reroute called GT table
Reroute operation code Link set table; Reroute OPC table; Reroute DPC table;
Reroute called GT table; Reroute calling GT table
Reroute rule table Link set table; Reroute OPC table; Reroute DPC table;
Reroute called GT table; Reroute calling GT table; Reroute
operation code

Equipment
This section describes the data configuration requirements on interworking equipment in the
None.

This section describes the data to be collected for configuring the message reroute service.
Table 16-2 lists the data to be collected before the configuration.


Routing redirection Reroute service send Reroute service DPC proc
service msg fail proc
Reroute link set index Reroute OPC range Reroute DPC range
Reroute called GT range Reroute calling GT range Reroute operation code
Active rerouted DPC Standby rerouted DPC Whether sending service
MAP reroute user IMSI MAP reroute user MAP reroute user calling
number MSISDN GT
MAP reroute user called

GT
NOTE
The data collection table consists of all data to be configured in the data tables.

This section provides some related descriptions for configuring the message reroute service.
Mandatory Configuration for the MAP Reroute

To enable the MAP reroute, you must configure the following data for the SCCP reroute:
1. You must set Operation code to Service reroute in the ADD RROCcommand.
Command: ADD RROC: MAPC=UDF247;
2. You must set Reroute directionto Reroute to service in the ADD RRRULEcommand.
Command: ADD RRRULE: RRDIRECT=BIT1;
NOTE
If the MAP reroute is enabled, the destination of the rerouted message is the DPC that the DPC index in
the reroute number table maps, and the DPC in the SCCP reroute rule table is invalid.
Sequences for Configuring the MAP Reroute

Before configuring the MAP reroute number table, you must configure the MAP reroute calling
GT number range table.
For example:

l Add a MAP reroute user number.

The correct data configuration procedures are:
– Add a record to the MAP reroute calling GT number range table and the index of the
record maps the user number to be added.
– Add a record in the MAP reroute number table.
l Remove a record from the reroute calling GT number range table.
The correct data configuration procedures are:
– Remove the record that references this reroute calling GT number range from the MAP
reroute number table.
– Remove the reroute calling GT number range.
Comparison Between the Reroute Called GT Number Range Table and the Reroute
Called GT Table
The similarity and difference between the reroute called GT number range table and the reroute
called GT table are as follows:
l Similarity
Both of them are GT number range tables. You can configure number ranges or numbers
in the tables.
l Difference
– The reroute called GT table is designed for the SCCP reroute. The records in this table
are used to match and identify the called GT of all messages. When the called GT in a
message complies with the record in the reroute called GT table, the message meets the
requirement for the SCCP reroute.
– The reroute called GT number range table is designed for the MAP reroute. The records
in this table are used to match and identify the called GT of only MO messages. When
the called GT in an MO message complies with the record in the reroute called GT
number range table, the message meets the requirement for the MAP reroute, that is,
the system performs further reroute service processing on the message. Otherwise, the
system transfers the message to another service module.
– The comparison between the reroute calling GT number range table and the reroute
calling GT table are similar to the comparison between the reroute called GT number
range table and the reroute called GT table. The only difference is that the reroute calling
GT number range table is used to match and identify not only the MO message but also
the IMSI addressing message, thus determining the route result of the message.

This section describes the general steps for configuring the message reroute service.
Table 16-3 lists the general procedures for configuring the message reroute service data.
Table 16-3 General procedures for configuring the message reroute service data
Step Operation
1 To add the M3UA and MTP link sets (MOD M3ASSOS/N7LKS)

Step Operation
2 To add the SCCP reroute data, including adding the reroute OPC (ADD
RROPC), adding the reroute DPC (ADD RRDPC), adding the reroute called
GT (ADD RRCDGT), adding the reroute calling GT (ADD RRCGGT), and
adding the reroute operation code (ADD RROC)
3 To add the reroute rule (ADD RRRULE)
4 To set the software configuration parameter (SET SOFTCFG)
5 To add the MAP reroute data, including adding the reroute calling GT
number range table (ADD RRCGGTRNG), adding the reroute called GT
number range table (ADD RRCDGRTNG), and adding the reroute number
table (ADD RRUSRNUM)
16.4 General Procedures

This section provides detailed procedures for configuring the message reroute service.
16.4.1 Adding the M3UA and MTP Link Sets

This section details how to configure the link set on which the message reroute service is
processed. The link set to be added is the source link set of the message.
16.4.2 Adding the Reroute OPC
This section details how to configure the reroute OPC for processing the message reroute service.
16.4.3 Adding the Reroute DPC
This section details how to configure the reroute DPC for processing the message reroute service.
16.4.4 Adding the Reroute Called GT
This section details how to configure the reroute called GT for processing the message reroute
service.
16.4.5 Adding the Reroute Calling GT
This section details how to configure the reroute calling GT for processing the message reroute
service.
16.4.6 Adding the Reroute Operation Code
This section details how to configure the reroute operation code for processing the message
reroute service.
16.4.7 Adding the Reroute Rule
This section details how to configure the reroute rule for processing the message reroute service.
16.4.8 Setting the Software Configuration Parameter
This section details how to configure the software configuration parameters for processing the
16.4.9 Adding the Reroute Called GT Range
This section details how to configure the reroute called GT number range for processing the
16.4.10 Adding the Reroute Calling GT Range

This section details how to configure the reroute calling GT number range for processing the
reroute service.
16.4.11 Adding the Reroute Number
This section details how to configure the reroute number for processing the reroute service.
16.4.1 Adding the M3UA and MTP Link Sets

This section details how to configure the link set on which the message reroute service is
processed. The link set to be added is the source link set of the message.
Command
ADD M3ASSOS;ADD N7LKS
Parameter
Parameter Parameter Parameter Description
ID Name
SRVPROSW Service process It determines the service to be enabled. You need to

T switch choose Reroute switch here.


ID Name
RRT Reroute policy It specifies the mode that the system uses to process
different messages in the message reroute service.
It is valid only when Service process switch is set to
Reroute switch.
It is optional and its value is of the enumeration type. It
can be set to:
l ANP (All DPC not processed): Regardless of the
message type, all MSU messages are processed based
on the original processing flow instead of the reroute
processing flow.
l SPP (DPC in self PC processed): When the MSU
message is the locally terminated message, the system
obtains Type of next reroute table and Next reroute
reference, and then sends the message to the reroute
part for processing. When the MSU message is not the
locally terminated message, the system processes the
message based on the original processing flow instead
of the reroute processing flow.
l NSPP (DPC not in self PC processed): When the MSU
message is not the locally terminated message, the
system obtains Type of next reroute table and Next
reroute reference, and then sends the message to the
reroute part for processing. When the MSU message
is the locally terminated message, the system
processes the message based on the original
processing flow instead of the reroute processing
flow.
l AP (All DPC processed): The system obtains Type of
next reroute table and Next reroute reference, and
then sends the MSU message to the reroute part for
processing regardless of the message type.


ID Name
TTYPE Type of next It specifies the type of the table corresponding to the next
reroute table reroute operation.
Reroute switch and the MSU message meets the
condition set in Reroute policy.
It is optional and its value is of the enumeration type. It
can be set to:
l VOID (Invalid)
l ROT (Reroute OPC table)
l RDT (Reroute DPC table)
l RCDT (Reroute called GT table)
l RCGT (Reroute calling GT table)
l ROCT (Reroute operation code table)
l RRLT (Reroute rule table)
NRR Next reroute It specifies the reroute reference of the table type
reference corresponding to the next reroute operation.
Reroute switch and the MSU message meets the
condition set in Reroute policy. It is used to match the
corresponding data in the reroute table configured in
Type of next reroute table.
It is optional. Its value is of the numeral type and ranges
0-65535. It must be configured based on the actual
conditions.
Related Command
Table 16-4 Related commands for configuring the M3UA and MTP link sets
Command Function
RMV N7LKS To remove the MTP link set
ADD M3ASSOS To add the M3UA association set
MOD M3ASSOS To modify the M3UA association set

Command Function
LST M3ASSOS To list the M3UA association set
RMV M3ASSOS To remove the M3UA association set

Command
ADD RROPC
Parameter
RR Reroute reference It maps the reference of the reroute in the reroute

processing.
It uniquely matches Next reroute reference in
the previous operation during the reroute process.
The object to be matched here is Next reroute
reference in the MTP link set or M3UA link set
table.
NI Network indication It maps the network type to be processed in the

reroute process.
It is used to match the network type information
contained in the MSU message.
FO Minimum OPC It maps the minimum OPC number to be

processed in the reroute process.
It is used to match the OPC information
contained in the MSU message. When the OPC
contained in the message is equal to or larger than
Minimum OPC and is equal to or smaller than
Maximum OPC, the match is successful.
Maximum OPC It maps the maximum OPC number to be


Type of next reroute It specifies the type of the table corresponding to

table the next reroute operation.
It is valid only when the MSU message meets the
It is optional and its value is of the enumeration
type. It can be set to:
VOID (Invalid)
ROT (Reroute OPC table)
RDT (Reroute DPC table)
RCDT (Reroute called GT table)
RCGT (Reroute calling GT table)
ROCT (Reroute operation code table)
RRLT (Reroute rule table)
It is set to Invalid by default. It must be
configured based on the actual conditions.
condition set in Reroute policy. It is used to
match the corresponding data in the reroute table
configured in Type of next reroute table.
Related Command
Table 16-5 Related commands for configuring the reroute OPC
Command Function
ADD RROPC To add the reroute OPC
MOD RROPC To modify the reroute OPC
LST RROPC To query the reroute OPC
RMV RROPC To remove the reroute OPC

Command
ADD RRDPC

Parameter
Name

processing.
It uniquely matches Next reroute reference in the
previous operation during the reroute process. The
object to be matched here is Next reroute
reference in the MTP link set, M3UA link set, or
reroute OPC table.
NI Network It maps the network type to be processed in the

indication reroute process.
FO Minimum DPC It maps the minimum DPC number to be processed

in the reroute process.
It is used to match the DPC information contained
in the MSU message. When the DPC contained in
the message is equal to or larger than Minimum
DPC and is equal to or smaller than Maximum
DPC, the match is successful.
TO Maximum DPC It maps the maximum DPC number to be processed

TTYPE Type of next It specifies the type of the table corresponding to the
reroute table next reroute operation.
It is optional and its value is of the enumeration type.
It can be set to:
l VOID (Invalid)
It is set to Invalid by default. It must be configured
based on the actual conditions.


Name
condition set in Reroute policy. It is used to match
the corresponding data in the reroute table
Related Command
Table 16-6 Related commands for configuring the reroute DPC

Command Function
ADD RRDPC To add the reroute DPC
MOD RRDPC To modify the reroute DPC
LST RRDPC To query the reroute DPC
RMV RRDPC To remove the reroute DPC

service.
Command
ADD RRCDGT
Parameter
Parameter ID Parameter Description
Name
RR Reroute It maps the reference of the reroute in the reroute

reference processing.
object to be matched here is Next reroute reference
in the MTP link set, M3UA link set, reroute OPC, or
reroute DPC table.


Name
GT GT indicator It maps the GT type to be processed in the reroute

process.
It is used to compare and match the GT type in the
MSU message.
TT Translation type It maps the translation type to be processed in the

reroute process.
It is used to compare and match the translation type in
the MSU message.
CP Numbering plan It maps the numbering plan to be processed in the

reroute process.
It is used to compare and match the numbering plan
in the MSU message.
AI Nature of address It maps the address nature indicator to be processed in

indicator the reroute process.
It is used to compare and match the address nature
indicator in the MSU message.
FAF Min. address It maps the information of the minimum address to be

message processed in the reroute process.
It is used to compare and match the information of the
minimum address in the MSU message. The address
information contained in the message must be equal
to or larger than Min. address message and be equal
to or smaller than Max. address message.
TAF Max. address It maps the information of the maximum address to be

maximum address in the MSU message. The address


Name
It can be set to:
VOID (Invalid)
the corresponding data in the reroute table configured
in Type of next reroute table.
Related Command
Table 16-7 Related commands for configuring the reroute called GT

Command Function
ADD RRCDGT To add the reroute called GT
MOD RRCDGT To modify the reroute called GT
LST RRCDGT To query the reroute called GT
RMV RRCDGT To remove the reroute called GT

service.
Command
ADD RRCGGT

Parameter
Name

processing.
reference in the MTP link set, M3UA link set,
reroute OPC, reroute DPC, or reroute called GT
table.

process.
MSU message.

reroute process.
It is used to compare and match the translation type
in the MSU message.

reroute process.
in the MSU message.
AI Nature of address It maps the address nature indicator to be processed

indicator in the reroute process.
FAF Min. address It maps the information of the minimum address to

message be processed in the reroute process.
It is used to compare and match the information of
the minimum address in the MSU message. The
address information contained in the message must
be equal to or larger than Min. address message and
be equal to or smaller than Max. address message.
TAF Max. address It maps the information of the maximum address to

the maximum address in the MSU message. The


Name
It can be set to:
l VOID (Invalid)
Related Command
Table 16-8 Related commands for configuring the reroute calling GT

Command Function
ADD RRCGGT To add the reroute calling GT
MOD RRCGGT To modify the reroute calling GT
LST RRCGGT To query the reroute calling GT
RMV RRCGGT To remove the reroute calling GT

reroute service.
Command
ADD RROC

Parameter
Name
RR Reroute reference It maps the reference of the reroute in the

reroute processing.
the previous operation during the reroute
process. The object to be matched here is Next
reroute reference in the MTP link set, M3UA
link set, reroute OPC, reroute DPC, reroute
called GT, or reroute calling GT table.
MAPC Operation code It maps the operation code to be processed in

the reroute process.
It is used to compare and match the version
number and operation code information of the
MAP message in the MSU message.
When Operation code is set to UDF247(247-
SERVICE_REROUTE), the messages that
can be processed include the following:
l UPDATE_LOCATION
l UPDATE_GPRS_LOCATION
l SEND_AUTHENTICATION_INFO
l RESTORE_DATA
l PURGE_MS
l READY_FOR_SM
l SEND_ROUTING_INFO_FOR_SM
l MO_FORWARD_SM
The system performs message reroute
operation based on not only the operation code,
but also the user number (IMSI/MSISDN).
TTYPE Type of next It specifies the type of the table corresponding

reroute table to the next reroute operation.
It is valid only when the MSU message meets
the condition set in Reroute policy.
VOID (Invalid)


Name
NRR Next reroute It specifies the reroute reference of the table

reference type corresponding to the next reroute
operation.
the condition set in Reroute policy. It is used
to match the corresponding data in the reroute
table configured in Type of next reroute
table.
Related Command
Table 16-9 Related commands for configuring the reroute operation code
Command Function
ADD RROC To add the reroute operation code
MOD RROC To modify the reroute operation code
LST RROC To query the reroute operation code
RMV RROC To remove the reroute operation code
NOTE
l The referenced index from the reroute rule table must be an actual index.
l The parameter Reroute reference is directly used when referencing the indexes from other tables.

Command
ADD RRRULE
Parameter

reroute process.
When the match condition is met, it is used to
replace the network type information in the
MSU message.

LSM Load-share select It specifies how to implement load sharing

mask among multiple signaling points.
It is optional. Its value is of the numeral type
and comprises eight binary bits. Its value range
is 0-15. It is set to 15 by default.
The configuration principle of this parameter
is as follows:
l When there is only one signaling point, the
load-sharing selection mask code is 0.
l When there are two signaling points, set any
bit to 1.
l When there are three or four signaling
points, set any two bits to 1.
l When there are 5-8 signaling points, set any
three bits to 1.
l When there are more than eight signaling
points, set all four bits to 1.
DST0-DST15 Destinations 0-15 It specifies the DSP to be performed load

sharing.
It is optional. Its value is of the numeral type.
Its value range is 0-65535. It is set to 65535 by
default.
PRT0-PRT15 Priorities 0-15 It specifies the priority of a DSP.

default.

RSWT Reroute rule switch It maps the further processing rule after the
successful reroute processing. It is optional
and its value is of the enumeration type. It can
be set to one or both of the following values:
l G1 (Reroute DPC fail discard)
l G2 (Modify DPC switch)
Based on different situations, the processing
principles are as follows:
l G1 enabled and G2 disabled: The system
modifies the route in the message and then
sends the message. When the DSP is
unreachable, the message is discarded.
l G1 enabled and G2 enabled: The system
modifies the DPC in the message and then
l G1 disabled and G2 disabled: The system
unreachable, the failure message is returned
and the system processes the message based
on the original processing flow.
l G1 disabled and G2 enabled: The system
NOTE
l Modifying the route: Based on the destination of
a rerouted message, the system reselects the
route for the message and sends the message to
the destination.
l Modifying the DPC: The system modifies the
DPC in the message to that of the reroute
destination.

RRDIRECT Reroute direction It determines the module to which the re-

routed message is sent. It is optional and its
value is of the enumeration type. It can be set
to:
l BIT0 (Reroute to M3UA/MTP): The
message is sent to the platform module for
the M3UA/MTP reroute processing.
l BIT1 (Reroute to service): The message is
sent to the service processing module for the
M3UA/MTP reroute processing.
It is set to BIT0 by default.
NOTE
To perform the MAP processing, you must set
Reroute direction to BIT1.
Related Command
Table 16-10 Related commands for configuring the reroute rule

Command Function
ADD RRRULE To add the reroute rule
MOD RRRULE To modify the reroute rule
LST RRRULE To query the reroute rule
RMV RRRULE To remove the reroute rule
16.4.8 Setting the Software Configuration Parameter

This section details how to configure the software configuration parameters for processing the
Command
SET SOFTCFG

Parameter
RRSERVICE Routing redirection It indicates the MAP reroute method. It can be

service set to one or more of the following values:
l BIT0 (Message routing on IMSI): For the
received IMSI addressing message, the
system routes the message to the specified
value added service (VAS) platform based
on the calling GT and MAP-layer IMSI
combination.
l BIT1 (MO): For the received MO message,
if the called GT is a specific number or
belongs to a specific number range, the
system routes the message to the specified
VAS platform based on the calling GT and
MAP-layer calling MSISDN combination.
l BIT2 (SRI_FOR_SM): For the received
SRI_For_SM message, the system routes
the message to the specified VAS platform
based on the called GT.
It must be configured based on the actual
conditions.
RRFAIL Reroute service If the message transmission fails after it is

send msg fail proc processed in the message reroute service, the
system determines whether to discard the
message or return the message based on the
setting of this parameter. It can be set to:
l BIT0 (Send on originate route)
l BIT1 (Discard)
conditions.
RRDPC Reroute Service It determines whether to modify the DPC

DPC proc address in the message after the reroute service
processing. It can be set to:
l BIT0 (Modified)
l BIT1 (Unmodified)
conditions.

Related Command
Command Function

Command
ADD RRCDGTRNG
Parameter
FROMGT Begin GT code It indicates the start called number in the GT

number range to be processed in the message
reroute service.
It is mandatory. Its value is of the character
string type and ranges 0-F.
TOGT End GT code It indicates the end called number in the GT

reroute service.
Related Command
Table 16-12 Related commands for configuring the reroute called GT range table
Command Function
ADD RRCDGTRNG To add the reroute called GT range table
MOD RRCDGTRNG To modify the reroute called GT range table
LST RRCDGTRNG To query the reroute called GT range table
RMV RRCDGTRNG To remove the reroute called GT range table


reroute service.
Command
ADD RRCGGTRNG
Parameter
Name
FROMGT Begin GT code It indicates the start calling number in the GT

number range to be processed in the message reroute
service.
It is mandatory. Its value is of the character string
type and ranges 0-F.
TOGT End GT code It indicates the end calling number in the GT number
range to be processed in the message reroute service.
Related Command
Table 16-13 Related commands for configuring the reroute calling GT range table
Command Function
ADD RRCGGTRNG To add the reroute calling GT range table
MOD RRCGGTRNG To modify the reroute calling GT range table
LST RRCGGTRNG To query the reroute calling GT range table
RMV RRCGGTRNG To remove the reroute calling GT range table

Command
ADD RRUSRNUM

Parameter
GTNUMIDX Reroute GT number It maps a record in the reroute calling GT range

range index table.
It is optional and its value is of the numeral
type. Its value range is 0-65535. It is set to
65535 by default, which indicates that the
system performs the reroute matching based on
only Reroute number instead of the
combination of Reroute number and Reroute
GT number range index.
USRNUM Reroute number It indicates the calling user number to be

processed in the re-routing service.
string type and ranges 0-9.
DPCIDX DPC index It maps a record in the MTP DSP table.

It is mandatory. Its value is of the numeral type
and ranges 0-2047.
Related Command
Table 16-14 Related commands for configuring reroute number table

Command Function
ADD RRUSRNUM To add the reroute number table
MOD RRUSRNUM To modify the reroute number table
LST RRUSRNUM To query the reroute number table
RMV RRUSRNUM To remove the reroute number table

The section provides the detailed example to demonstrate how to configure the message reroute
service.
16.5.1 Example Description (SCCP Reroute)

This section describes the data collected for configuring the SCCP reroute service.
16.5.2 Configuration Description(SCCP Reroute)
This section details the data configuration in the SCCP reroute service based on the data
collected.
16.5.3 Example Description (MAP Reroute)

This section describes the data collected for configuring the MAP reroute service.
16.5.4 MAP Reroute Configuration for the SRI_For_SM Message
This section details the data configuration for the SRI_For_SM message in the MAP reroute
service based on the data collected.
16.5.5 MAP Reroute Configuration for the IMSI Addressing Message
This section details the data configuration for the IMSI message in the MAP reroute service
based on the data collected.
16.5.1 Example Description (SCCP Reroute)

This section describes the data collected for configuring the SCCP reroute service.
Table 16-15 lists the collected data to be used when you configure the SCCP reroute service.
Table 16-15 SCCP reroute data collection table
Routing redirection Reroute service send Reroute service DPC proc

- - -
0 111111-999999 555555-888888
8675526888-8675527888 8675526888-8675527888 UPDATE_LOCATION_ARE

A
333333 222222 No
number MSISDN GT
- - -
MAP reroute user called - -

GT
- - -
16.5.2 Configuration Description(SCCP Reroute)

This section details the data configuration in the SCCP reroute service based on the data
collected.
The data collected for configuring the service is as listed in Table 16-15.

Modifying Link Set Related Information

To modify the information related to the M3UA link set, where Association set index is 0,
Service process switch is Reroute switch, Reroute policy is All DPC processed, Type of next
reroute tableis Reroute OPC table, and Next reroute reference is 11, run the following
command:
MOD M3ASSOS: IDX=0, SRVPROSWT=ROSWT-1, RRT=AP, TTYPE=ROT, NRR=11;
Adding Table Information Related to the SCCP Reroute

To add records to the reroute OPC table, reroute DPC table, reroute called GT table, reroute
calling GT table, and reroute operation code table, run the following commands:
ADD RROPC: RR=11, NI=NM, FO="111111", TO="999999", TTYPE=RDT, NRR=12;
ADD RRDPC: RR=12, NI=NM, FO="555555", TO="888888", MTP=FT, TTYPE=RCDT, NRR=13;
ADD RRCDGT: RR=13, GT=GT4, CP=ISDN, AI=FREE, FAF="8675526888", TAF="8675527888",
TTYPE=RCGT, NRR=14;
ADD RRCGGT: RR=14, GT=GT4, CP=ISDN, AI=FREE, FAF="8675526888", TAF="8675527888",
TTYPE=ROCT, NRR=15;
ADD RROC: RR=15, MAPC=UPAREA, TTYPE=RRLT, NRR=1;
You can configure reroute service information based on actual conditions.
Adding the Reroute Rule

To add a record to the reroute rule table, run the following command:
ADD RRRULE: NI=NM, ARD="333333", SRD="222222", RSWT=G1-1;
16.5.3 Example Description (MAP Reroute)

This section describes the data collected for configuring the MAP reroute service.
NOTE
The SCCP reroute function provides filter conditions for the MAP reroute. The system performs the MAP
reroute on only the messages that meet the SCCP reroute conditions. To enable the MAP reroute, you must
set Operation code to Service reroute in the ADD RROC command and Reroute direction to Reroute
to service in the ADD RRRULE command. Otherwise, the system performs only the SCCP reroute on
the messages.
Table 16-16 lists the collected data to be used when you configure the MAP reroute service.

Table 16-16 MAP reroute data collection table

Routing redirection Reroute service send Reroute Service DPC proc
MO message Send based on the original Modify

route
0 111111-999999 555555-888888
8675526888-8675527888 8675526888-8675527888 SERVICE_REROUTE
333333 222222 Yes
number MSISDN GT
- 13812345678 8675512340000-8675512349
999
MAP reroute user called - -

GT
8675513800138-867551380 - -
0139
16.5.4 MAP Reroute Configuration for the SRI_For_SM Message

This section details the data configuration for the SRI_For_SM message in the MAP reroute
service based on the data collected.
The data collected for configuring the service is listed in Table 16-16.
Setting Reroute Software Parameter

To configure the reroute software parameter based on the data collected in Table 16-16, run the
following command:
SET SOFTCFG: RRSERVICE=BIT2-1, RRFAIL=BIT0, RRDPC=BIT0;
Configuring the Reroute Number

The index of the reroute DPC references the previously generated index. You need not configure
the GT number range index.
To configure a reroute number, run the following command:
ADD RRUSRNUM: USRNUM="13812345678", DPCIDX=1;
After the successful configuration, the MSISDN is 13812345678. All SRI_For_SM messages
sent to this MSISDN are rerouted to a special device, of which the DPC is 333333.

16.5.5 MAP Reroute Configuration for the IMSI Addressing

Message
This section details the data configuration for the IMSI message in the MAP reroute service
based on the data collected.
The data collected for configuring the service is as listed in Table 16-16.
Setting Reroute Software Parameter

To configure the reroute software parameter based on the data collected in Table 16-16, run the
following command:
SET SOFTCFG: RRSERVICE=BIT0-1, RRFAIL=BIT0, RRDPC=BIT0;
Configuring the Reroute Number

The indexes of the reroute calling GT number range and DPC reference the previously generated
indexes. Note that the user number configured in the reroute number table must be the IMSI of
the user.
To configure a reroute number, run the following command:
ADD RRUSRNUM: GTNUMIDX=2, USRNUM="460123456789012", DPCIDX=1;
NOTE
The configuration of the signaling point code at the MAP layer is the same as that of the MAP reroute for
the MO message.
After the successful configuration, the IMSI number is 460123456789012. All IMSI addressing
messages are rerouted to a special device, of which the DPC is 333333.

Feature Description 17 Configuring CFS Black&White Lists Data
17 Configuring CFS Black&White Lists

Data
About This Chapter
The black&white lists service is a call filter service (CFS) developed for shielding calls based
on the contents of an intercepted message. With the black list service, the system intercepts a
message and extracts the calling and called numbers from the message. Then, the system
determines whether to shield this call based on the configured rules. With the white list service,
the system intercepts an IAM message from a toll call and extracts the calling or called number
from the message. After that, the system determines whether to shield this call by checking
whether the number is registered in the carrier's network. Before configuring the CFS
black&white lists data, make sure that the hardware data, MTP data, M3UA data, and SCCP
data are already configured.

This topic describes the service definition, terms, service benefits, and version requirements
related to the CFS black&white lists service.
This topic describes the flows for processing the CFS black&white lists service.
The CFS black&white lists service is controlled by the license file, so make sure that the license
resource is sufficient before configuring the service.
This topic describes detailed procedures for configuring the CFS black&white lists service.
This topic describes the examples for configuring the CFS service.

17 Configuring CFS Black&White Lists Data Feature Description

This topic describes the service definition, terms, service benefits, and version requirements
related to the CFS black&white lists service.

This topic describes the definition of the CFS black&white lists service.
17.1.2 Terms
This topic describes the terms used in the CFS black&white lists service.
This topic describes the interaction requirement between the CFS black&white lists service and
other services.
This topic describes the benefits of the CFS black&white lists service.
This topic describes the version requirement of the CFS black&white lists service.
This topic describes the requirements on equipment cooperation for implementing the CFS
black&white lists service.

This topic describes the definition of the CFS black&white lists service.
l With the black list service, the system intercepts an ISUP-IAM or INAP-IDP message and
extracts the calling and called numbers from the message. After that, the system determines
whether to shield this call based on the configured rules. The do-not-disturb function
contained in this service enables subscribers to restrict some specified calls to these
subscribers when they act as callees.
l With the white list service, the system intercepts an IAM message from a toll call and
extracts the calling or called number from the message. After that, the system determines
whether to shield this call by checking whether the subscriber is subscribed to the carrier's
network.
17.1.2 Terms
This topic describes the terms used in the CFS black&white lists service.
Black List
The calls of the subscribers that meet the conditions configured in this list are shielded.
White List
The calls of the subscribers that meet the conditions configured in this list are connected.


This topic describes the interaction requirement between the CFS black&white lists service and
other services.
l The white list service and the black list service cannot be enabled simultaneously.
l In the call flow of the white list service, the call originated from a local switch (LS) must
be connected to the SG.
l If a message requires multiple service processing, the sequences should be CNL > CFS
(black&white lists) > LNP or CNL > CFS (black&white lists) > MNP.
NOTE
The related services are described as follows:

l CNL: It refers to the national location code service. When the CNL service is enabled, the calls
originated between the subscribers who reside in adjacent local call areas are charged as local calls.
l LNP: It refers to the local number portability service. When the LNP service is enabled, fixed-network
subscribers can migrate among different locations or choose the networks of different carriers without
changing their directory numbers.
l MNP: It refers to the mobile number portability service. When the MNP service is enabled, mobile
subscribers can migrate among different subscribed networks in a country without changing their
MSISDN numbers.

This topic describes the benefits of the CFS black&white lists service.
For Carriers
l This service improves the competitiveness of carriers and meets call shielding requirements
of some special subscribers.
l This service enables carriers to restrict the calls originated by or to some subscribers that
maliciously owe the call fees.
l This service enables carriers to restrict some malicious and fraud calls through number
configuration.
For Subscribers
l This service enables subscribers to configure some numbers that cannot be dialed.
l The do-not-disturb function contained in this service enables subscribers to restrict some
specified calls to these subscribers when they act as callees.

This topic describes the version requirement of the CFS black&white lists service.
The CFS black&white lists service has the following version requirements:
l V200R003C02 and all later versions provide the black list service.
l V200R003C05 and all later versions provide the white list service.
l V200R005C02 and all later versions provide the do-not-disturb service.
The CFS black&white lists service has no special requirement for hardware.


This topic describes the requirements on equipment cooperation for implementing the CFS
The CFS black&white lists service has no special requirement on the cooperating equipment.

This topic describes the flows for processing the CFS black&white lists service.

This topic describes the networking structure for implementing the CFS black&white lists
service.
This topic describes the principle for implementing the CFS black&white lists service.
17.2.3 Call Flow
This topic describes the call flow of the CFS black & white lists service.

This topic describes the networking structure for implementing the CFS black&white lists
service.
Figure 17-1 shows the networking structure for implementing the CFS black&white lists
service.

Figure 17-1 Networking structure for implementing the CFS black&white lists service
SG: U-SYS SG7000 Signaling Gateway SCP: Service Control Point

TE: Transit Exchange HLR: Home Location Register
LS: Local Switch
l SG: It stores the service data of subscribers.
l SCP: It charges the call service.
l TE: It transfers data among different locations within a network.
l HLR: It records the access information about mobile subscribers.
l LS: It acts as the end point for sending and receiving messages.

This topic describes the principle for implementing the CFS black&white lists service.

The SG performs the following procedures to identify and process the CFS black list service:
1. Intercepting an ISUP-IAM or INAP-IDP message and checking the calling number length:
The length of the calling number must be in a valid range. This avoids some fraud calls,
for the system cannot normally charge the calls if the calling number is rather short.
2. Checking the call type: The system has certain restrictions on special calls for each
subscriber. For example, some subscribers are not allowed to make toll calls or called party
prepaid calls.
3. Checking the Custom list: The Custom list records the ordinary called party groups that a
subscriber is not allowed to make calls to.
4. Checking the System list: The System list records some commonly-used special numbers
that an ordinary subscriber is not allowed to dial.
5. Checking the General control number list: The General control number list records the
numbers that are not allowed to dial. The subscriber data configuration determines whether
the system restricts calls based on calling numbers or called numbers.
The SG performs the following procedures to identify and process the CFS white list service:
1. The SG intercepts an IAM message and determines whether the call is a toll call based on
the called number. The black list service is applicable to toll calls only.
2. The SG determines whether to distinguish the calling party or the called party based on the
called number and the distinguishing type configured for the link set that sends the message.
3. The SG checks whether the subscriber is in the white list of the carrier. If yes, the system
connects the call. If not, the system returns an REL message based on the announcement
resource or forwards the IAM message after adding a special prefix.
During the service identification, when one of the shielding rules is met, the system shields the
call; otherwise, the system continues the identification.
17.2.3 Call Flow

This topic describes the call flow of the CFS black & white lists service.
The CFS black & white lists service processes the following two types of messages:
l The ISUP-IAM message that is in compliance with the Q.763 protocol
l The INAP-IDP message that is in compliance with the CS1 and CS2 protocols
The white list service processes only the ISUP-IAM message that is in compliance with the CS1
and CS2 protocols.
Call Release Flow in the Black List Service

Figure 17-2 and Figure 17-3 show the call release flow in the black list service.

Figure 17-2 Call release flow for the ISUP-IAM message
Figure 17-3 Call release flow for the INAP-IDP message
Description of the Call Release Flow

1. The LS sends an ISUP-IAM/INAP-IDP message to the SG.
2. Upon receiving the ISUP-IAM/INAP-IDP message, the SG obtains the calling number (or
the redirecting number when Base number when CF in the CFS service software
parameter table is set to Redirecting number) and the called number from the message.
Then, the SG performs the number normalization on these numbers. If the obtained numbers
contain an LRN, the SG changes the LRN to the DN.
3. The SG checks the length of the calling number or redirecting number. If the number length
is not in the valid range configured in the CFS service software parameter table, the SG
releases the call. In addition, it obtains the value of Calling number length block release
cause configured in the CFS service software parameter table, and then proceeds with 11
for subsequent processing. If the number length is in the valid range, the SG proceeds with
4 for subsequent processing.
4. The SG obtains the call type based on the called number, and then matches the call type.

When the call type is matched, the SG determines the call screening mode based on the
value of Call identify base number. To be specific, the SG determines whether to screen
the call based on the calling number or the called number by considering the following
conditions:
l If the call is screened based on the called number, the SG proceeds with 10 for
l If the call is screened based on the calling number, the SG proceeds with 5 for subsequent
processing.
If the matching of call type fails, and Process based on calling number if no call type is
matched in the CFS service software parameter table is set to Open, the SG screens the
call based on the calling number.
5. The SG, based on the calling number, queries the call types to be screened, and then checks
whether this particular call belongs to any of these types. If yes, the SG releases the call.
In addition, it obtains the call release cause configured in the CFS service software
parameter table, and then proceeds with 11 for subsequent processing. If not, the SG
proceeds with 6 for subsequent processing.
6. The SG, based on the value of Personal list ID configured by the calling party, queries the
number segment to be screened, and then checks whether the called number belongs to this
number segment. If yes, the SG releases the call. In addition, it obtains the call release cause
configured in the CFS service software parameter table, and then proceeds with 11 for
subsequent processing. If the called number does not belong to this number segment, the
SG proceeds with 7 for subsequent processing.
7. The SG, based on the value of Public list ID configured by the calling party, queries the
number segment. If yes, the SG releases the call. In addition, it obtains the call release cause
subsequent processing. If the called number does not belong to this number segment, the
SG proceeds with 8 for subsequent processing.
8. The SG checks whether the do-not-disturb ID is configured in the CFS public list table.
l If the do-not-disturb ID is configured, the SG performs the processing based on the
following conditions:
– If the calling party belongs to the do-not-disturb list configured by the called party,
the SG releases the call. In addition, it obtains the call release cause configured in
the CFS service software parameter table, and then proceeds with 11 for subsequent
processing.
– If the calling party does not belong to the do-not-disturb list configured by the called
party, the SG skips the do-not-disturb processing and proceeds with 10 for
l If the do-not-disturb ID is not configured, the SG skips the do-not-disturb processing
and proceeds with 10 for subsequent processing.
9. The SG, based on the value of Public list base number configured in the CFS service
software parameter table, matches the normalized number with that configured in the CFS
public list table. If the normalized number belongs to the CFS public list table, the SG
releases the call. In addition, it obtains the call release cause configured in the CFS service
software parameter table, and then proceeds with 11 for subsequent processing. If the
normalized number does not belong to the CFS public list table, the SG proceeds with 10
for subsequent processing.
10. When Public list block switch in the CFS service software parameter table is set to
Open, the SG determines whether Public list base number (calling number or called

number) configured in the CFS service software parameter table belongs to the CFS public
list table. If yes, the SG releases the call. In addition, it obtains the related call release cause
11. The SG, based on the configuration in the CFS service software parameter table, returns a
RELEASE message that contains the call release cause or redirecting number to instruct
the announcement playing.
NOTE
In the call release flow for the INAP-IDP message as shown in Figure 17-3, the SG returns a TC-ERROR
or CONNECT message based on the configuration.
Call Connection Flow in the Black List Service

Figure 17-4 and Figure 17-5 show the call connection flow in the black list service.
Figure 17-4 Call connection flow for the ISUP-IAM message
Figure 17-5 Call connection flow for the INAP-IDP message
Description of the Call Connection Flow

1. The LS sends an ISUP-IAM/INAP-IDP message to the SG.
2. Upon receiving the ISUP-IAM/INAP-IDP message, the SG obtains the calling number (or
the redirecting number when Base number when CF in the CFS service software
parameter table is set to Redirecting number) and the called number from the message.

Then, the SG performs the number normalization on these numbers. If the obtained numbers
contain an LRN, the SG changes the LRN to the DN.
3. The SG checks whether the length of the calling number or redirecting number is in the
valid range. If yes, the SG skips the call screening processing and proceeds with 4 for
4. The SG obtains the call type based on the called number, and then determines the call
screening mode based on the value of Call identify base number. To be specific, the
SG determines whether to screen the call based on the calling number or the called number.
If the call is screened based on the called number, the SG proceeds with 11 for subsequent
processing. If the call is screened based on the calling number, the SG proceeds with 5 for
5. The SG obtains the call type based on the called number, and then matches the call type.
When the call type is matched, the SG determines the call screening mode based on the
value of Call identify base number. To be specific, the SG determines whether to screen
the call based on the calling number or the called number by considering the following
conditions:
l If the call is screened based on the called number, the SG proceeds with 11 for
l If the call is screened based on the calling number, the SG proceeds with 6 for subsequent
processing.
If the matching of call type fails, the SG determines the call screening mode based on the
value of Process based on calling number if no call type is matched configured in the
CFS service software parameter table.
l If Process based on calling number if no call type is matched is set to Open, the
SG screens the call based on the calling number.
l If Process based on calling number if no call type is matched is set to Close, the
SG skips the call screening processing and proceeds with 12 for subsequent processing.
6. The SG, based on the calling number, queries the call types to be screened, and then checks
whether this particular call belongs to any of these types. If not, the SG skips the call
screening processing and proceeds with 7 for subsequent processing.
7. The SG, based on the value of Personal list ID configured by the calling party, queries the
number segment. If not, the SG skips the call screening processing and proceeds with 8 for
8. The SG, based on the value of Public list ID configured by the calling party, queries the
number segment. If not, the SG skips the call screening processing and proceeds with 9 for
9. The SG checks whether the do-not-disturb ID is configured in the CFS public list table. If
either of the following conditions is met, the SG skips the call screening processing and
proceeds with 11 for subsequent processing:
l The called party has not configured the do-not-disturb list.
l The called party has configured the do-not-disturb list but the calling number does not
belong to the list.
10. The SG, based on the value of Public list base number configured in the CFS service
software parameter table, matches the normalized number with that configured in the CFS
public list table. If the matching fails, the SG skips the call screening processing and
proceeds with 11 for subsequent processing.

11. When Public list block switch in the CFS service software parameter table is set to
Open, the SG determines whether Public list base number (calling number or called
number) configured in the CFS service software parameter table belongs to the CFS public
list table. If not, the SG skips the call screening processing and proceeds with 12 for
12. The call is connected, and the SG transparently forwards the ISUP-IAM/INAP-IDP
message or returns the message to the related NE based on the protocol used.
Call Release Flow in the White List Service

Figure 17-6 show the call release flow in the white list service.
Figure 17-6 Call release flow for the ISUP-IAM message
Description of the Call Release Flow

1. The LS sends an IAM message to the SG.
2. Upon receiving the message, the SG obtains the called number from the message and then
performs number normalization on the called number. If the normalization is successful
and the number carries the carrier identification code (CIC), the SG proceeds with 3 for
3. The SG checks whether the prefix of the normalized number contains the indicator of the
called party payment for a toll call (such as the prefix 90).
l If the prefix contains the indicator, and bit 0 of Parameter1 in the CFS service software
parameter table is set to 1, the SG deletes all other prefixes that are added in front of
the indicator. If the prefix contains the indicator, and bit 0 of Parameter1 in the CFS
service software parameter table is set to 0, the SG does not delete other prefixes that
are added in front of the indicator.
l If the prefix does not contain the indicator, and bit 1 of Parameter1 in the CFS service
software parameter table is set to 1, the SG performs the processing based on the value
of the information element "Forward call indicator" (indicated by bit M).
– If bit M is set to 1, the SG deletes all other prefixes that are added in front of the CIC
and then adds the prefix 90.

– If bit M is set to 0 and bit 0 of Parameter1 in the CFS service software parameter
table is set to 1, the SG deletes all other prefixes that are added in front of the CIC.
table is set to 0, the SG does not delete any prefix.
software parameter table is set to 0 and bit 0 of Parameter1 is set to 1, the SG deletes
all other prefixes that are added in front of the CIC. If the prefix does not contain the
indicator, and bit 1 of Parameter1 in the CFS service software parameter table is set
to 0 and bit 0 of Parameter1 is set to 0, the SG does not delete any prefix.
4. The SG obtains the distinguishing type based on the distinguishing type configured for link
sets and the distinguishing type that is matched by using the number obtained in 3.
5. The SG extracts the related number based on the distinguishing type and checks whether
the number belongs to the CFS user table. If not, the SG continues to check whether the
number belongs to the CFS user number range table. If the number belongs to neither of
the two tables, the SG releases the call.
6. The SG, based on the configuration in the CFS service software parameter table, returns a
RELEASE message that contains the call release cause or redirecting number to instruct
the announcement playing.
Call Connection Flow in the White List Service

Figure 17-7 show the call connection flow in the white list service.
Figure 17-7 Call connection flow for the ISUP-IAM message
Description of the Call Connection Flow

1. The LS sends an IAM message to the SG.
2. Upon receiving the message, the SG obtains the called number from the message and then
performs number normalization on the called number. If the normalization fails or the
number does not carry the CIC, the SG connects the call.
3. The SG checks whether the prefix of the normalized number contains the indicator of the
called party payment for a toll call.
l If the prefix contains the indicator, and bit 0 of Parameter1 in the CFS service software
parameter table is set to 1, the SG deletes all other prefixes that are added in front of
the indicator. If the prefix contains the indicator, and bit 0 of Parameter1 in the CFS
service software parameter table is set to 0, the SG does not delete other prefixes that
are added in front of the indicator.

software parameter table is set to 1, the SG performs the processing based on the value
of the information element "Forward call indicator" (indicated by bit M).
– If bit M is set to 1, the SG deletes all other prefixes that are added in front of the CIC
and then adds the prefix 90.
table is set to 1, the SG deletes all other prefixes that are added in front of the CIC.
table is set to 0, the SG does not delete any prefix.
software parameter table is set to 0 and bit 0 of Parameter1 is set to 1, the SG deletes
all other prefixes that are added in front of the CIC. If the prefix does not contain the
indicator, and bit 1 of Parameter1 in the CFS service software parameter table is set
to 0 and bit 0 of Parameter1 is set to 0, the SG does not delete any prefix.
4. The SG obtains the distinguishing type based on the distinguishing type configured for link
sets and the distinguishing type that is matched by using the number obtained in 3. If the
distinguishing type configured for link sets does not contain the distinguishing type that is
matched by using the number obtained in 3, the SG connects the call.
5. The SG extracts the related number based on the distinguishing type. If the extraction fails,
the SG connects the call. If the extraction is successful, the SG checks whether the number
belongs to the CFS user table. If the number does not belong to the CFS user table, the
SG continues to check whether the number belongs to the CFS user number range table.
The SG connects the call when the number belongs to either of the two tables.
NOTE
The preceding flows are only message flows. The messages transmitted during the processing vary
according to the adopted protocols and types of the messages.

The CFS black&white lists service is controlled by the license file, so make sure that the license
resource is sufficient before configuring the service.

This topic describes the relations between the data tables for configuring the CFS black&white
lists service.
This topic describes data configuration requirements of the CFS black&white lists service on
interworking equipment.
This topic describes the data to be collected for configuring the CFS black&white lists service.
There is no special requirements for configuring the CFS black&white lists service. The service
can be configured according to actual conditions.
This topic describes general steps for configuring the CFS black&white lists service.


This topic describes the relations between the data tables for configuring the CFS black&white
lists service.
Black List Service

The following tables are involved in configuring the black list service: software configuration
parameter table-(two), service common software configuration table, CFS service software
parameter table, CFS user table, CFS personal list table, CFS common list table, CFS public
user table, CFS public list table, CFS call identify table, CFS block release cause table, Prefix
analysis table, and CFS user range table. Figure 17-8 shows the relations between these data
tables.

Figure 17-8 Relations between the data tables for configuring the black list service
ADD CFSRC ADD CFSUSR SET SOFTCFG2
[ Release cause ] [ Directory number ] [ CFS INAP SSN ]

Location routing
[ Process action ] [ ]
number
[ Nature of address ] [ Personal list ID ] ADD PREANALYSIS
Personal list block
[ Number plan ] [ ] [ Prefix analysis ]
release cause number
[ Number ] [Non service attribute]
[ Common list ID ]
ADD CFSPBL Common list block [ Service attribute ]
[ ]
release cause
[ Start number ] ADD CFSCL
[ Call identify prefix 1 ]
[ End number ] Call identify 1 [ Common ID ]
[ ]
[ Release cause ] release cause
[ Call identify prefix 2 ] [ Start number ]
ADD CFSPBL [ Call identify 2 ] [ End number ]
release cause
[ User number ] [ …… ] ADD CFSCI
[ …… ]
[ Release cause ] [ Call identify prefix ]
[Do not disturb list ID] Call identify 20 Call identify
[ ] [ ]
ADD CFSPL release cause base number
[ Personal ID ] ADD CFSUSRRANGE SET CFSSOFTCFG

[ CFS service switch ]
[ Start number ] [ Directory number ]
[ Number ]
[ End number ] [ Location routing ] amendment switch
number CFS process
SET SRVCOMCFG [ Personal list ID ] [ ]
[ Country code ] Personal list block protocol type
[ ]
Global title address release cause [ Base number ]
[ ] when CF
of equipment [ Common list ID ]
[ CFS query ]
[ Standard length for ] Common list block service key
number amend [ ]
release cause Calling number
[ ]
[ Call identify prefix 1 ] length block switch
Call identify 1 Calling number
[ ] [ length block ]
release cause
[ Call identify prefix 2 ] release cause
Call identify 2 Min calling
[ ] [ ]
release cause number length
[ …… ] Max calling
[ ]
number length
[ …… ]
Public list block
[ ]
[ Call identify prefix 20 ] switch
Call identify 20 Public list base
[ ] [ ]
release cause number
White List Service

The following tables are involved in configuring the white list service: service common software
configuration table, CFS service software parameter table, CFS user table, CFS call identify
table, CFS block release cause table, Prefix analysis table, and CFS user range table. Figure
17-8 shows the relations between these data tables.

Figure 17-9 Relations between the data tables for configuring the white list service
ADD CFSUSR
[ Directory number ]
Location routing
[ ]
number
[ Personal list ID ]
Personal list block
[ ]
release cause
[ Common list ID ] ADD PREANALYSIS
SET SRVCOMCFG Prefix analysis ]
Common list block [
[ Country code ] [ ] number
release cause
Global title address [Non service attribute]
[ ] [ Call identify prefix 1 ]
of equipment [ Service attribute ]
[ Call identify 1 ]
[ Standard length for ] release cause
number amend
[ Call identify prefix 2 ] ADD CFSCI
ADD CFSRC [ Call identify 2 ]
release cause [ Call identify prefix ]
[ Process action ]
[ …… ]
[ Release cause ] Call identify
[ …… ] [ ]
[ Nature of address ] base number
[ Number plan ] Call identify 20
[ ]
[ Number ] release cause
SET CFSSOFTCFG ADD CFSUSRRANGE

[ CFS service switch ] [ Directory number ]
Number
[ ] Location routing
amendment switch [ ]
number
[ CFS process ] [ Personal list ID ]
protocol type Personal list block
[ ]
Base number ] release cause
[
when CF [ Common list ID ]
[ CFS query ]
service key Common list block
[ ]
release cause
Calling number
[ ]
length block switch [ Call identify prefix 1 ]
Calling number Call identify 1
[ ]
[ length block ] release cause
release cause [ Call identify prefix 2 ]
Min calling [ Call identify 2 ]
[ ]
number length release cause
Max calling [ …… ]
[ ]
number length [ …… ]
Public list block
[ ] [ Call identify prefix 20 ]
switch
Public list base Call identify 20
[ ] [ release cause ]
number


Equipment
This topic describes data configuration requirements of the CFS black&white lists service on
interworking equipment.
There is no special data configuration requirements for interworking equipment.

This topic describes the data to be collected for configuring the CFS black&white lists service.
Black List Service

Table 17-1 lists the data to be collected for configuring the black list service.
Table 17-1 Data to be collected for configuring the black list service
Parameter Name Parameter Value Parameter Name Parameter Value
Global title address

Country code
of equipment
Standard length for

CFS INAP SSN
number amend
Message type of
Number
CFS service
amendment switch
processing
Base number when CFS query service

CF key
Calling number
Calling number
length block release
length block switch
cause
Min calling number Max calling

length number length
Public list block Public list base

switch number
Process based on
Format of search
calling number if no
number
call type is matched
Release cause Process action
Nature of address Number plan
Number
Start number (ADD

Personal list ID
CFSPBL)

End number (ADD

Common list ID
CFSPBL)
Start number (ADD End number (ADD

CFSCL) CFSCL)

CFSPL) CFSPL)
Public list block

Call identify prefix
release cause
Call identify base

number
Prefix analysis Non service

number attribute
Service attribute User IMSI number
Personal list block

Personal list ID
release cause
Common list block

Common list ID
release cause
Call identify prefix Call identify 1

1 release cause
User number range Personal list ID
Personal list block

Common list ID
release cause
Common list block Call identify prefix

release cause 1
Call identify 1
release cause
Do not disturb list

User number
ID
Release cause value
White List Service

Table 17-2 lists the data to be collected for configuring the white list service.

Table 17-2 Data to be collected for configuring the white list service

Country code
of equipment
Whether have
Standard length for
language resource
number amend
on OPC
Whether have
Link set
language resource
discrimination type
on DPC
Message type of
Number
CFS service
amendment switch
processing
Parameter 1
Base number when (special prefix
CF processing and M
IE determination)
B&W list option Release cause
Release number Special process

prefix category 1
Release cause Process action
Nature of address Number plan
Number
Call identify base

number

number attribute
Service attribute

User IMSI number
1
Call identify 1
release cause

User number range
1
Call identify 1
release cause


There is no special requirements for configuring the CFS black&white lists service. The service
can be configured according to actual conditions.

This topic describes general steps for configuring the CFS black&white lists service.
Black List Service

Table 17-3 lists the general steps for configuring the black list service.
Table 17-3 General steps for configuring the black list service
Step Operation
1 Set service common software configuration parameters (SET

SRVCOMCFG)
2 Set the software configuration parameter-(two) (SET SOFTCFG2)
3 Add the prefix analysis number list (ADD PREANALYSIS)
4 Add the CFS call type (ADD CFSCI)
5 Add the CFS release cause (ADD CFSRC)
6 Add CFS personal list (ADD CFSPL)
7 Add CFS common list (ADD CFSCL)
8 Add CFS public user (ADD CFSPBLUSR)
9 Add CFS public list (ADD CFSPBL)
10 Set CFS service software parameters (SET CFSSOFTCFG)
11 Add the CFS service user (ADD CFSUSR)
12 Add CFS user number range (ADD CFSUSRRANGE)
White List Service

Table 17-4 lists the general steps for configuring the white list service.
Table 17-4 General steps for configuring the white list service
Step Operation
1 Set service common software configuration parameters (SET

SRVCOMCFG)
2 Set DSP announcement resource information (ADD N7DSP)

Step Operation
3 Set the MTP link set (ADD N7LKS)
4 Add the prefix analysis number list (ADD PREANALYSIS)
5 Add the CFS call type (ADD CFSCI)
6 Add the CFS release cause (ADD CFSRC)
7 Set CFS service software parameters (SET CFSSOFTCFG)
8 Add the CFS service user (ADD CFSUSR)
9 Add CFS user number range (ADD CFSUSRRANGE)

This topic describes detailed procedures for configuring the CFS black&white lists service.
17.4.1 Setting Service Common Software Configuration Parameters

This topic describes how to set service common software configuration parameters.
17.4.2 Setting Software Configuration Parameters (Two)
This topic describes how to set software configuration parameters of type two.
17.4.3 Adding the MTP DSP
This topic describes how to add announcement resources for a destination signaling point (DSP).
17.4.4 Adding the MTP Link Set
This topic describes how to set the distinguishing type for a link set.
17.4.5 Adding the Number Analysis Prefix
This topic describes how to add the number analysis prefix.
17.4.6 Adding the CFS Call Type
This topic describes how to add the CFS call type.
17.4.7 Adding the CFS Shielding Release Cause
This topic describes how to add the CFS shielding release cause.
17.4.8 Adding the CFS Personal List
This topic describes how to add the CFS personal shielding number.
17.4.9 Adding the CFS Common List
This topic describes how to add the CFS common shielding number.
17.4.10 Adding the CFS Public List
This topic describes how to add the CFS public shielding number.
17.4.11 Adding the CFS Service User
This topic describes how to add the CFS service subscriber.
17.4.12 Adding the CFS User Number Range
This topic describes how to add the CFS subscriber number range.
17.4.13 Setting CFS Service Software Parameters

This topic describes how to set CFS service software parameters.
17.4.1 Setting Service Common Software Configuration Parameters

This topic describes how to set service common software configuration parameters.
The common software parameters configured here are related to the CFS black&white lists
service.
Command
SET SRVCOMCFG
Parameter
r ID r Name
COUNTR Country It specifies the code of a country. It must be configured according

YCODE code to actual conditions.
GTCODE Global It specifies the actual GT code of this equipment. When the INAP
title interface is configured for this equipment, the GT code of this
address of equipment must be configured in the end office.
equipment
STDNUM Standard It specifies the length of a subscriber number that does not contain
LEN length for the country code, area code, and toll call selection code of a carrier.
number It is optional. Its value is of the numeral type and ranges 1-16.
amend
Related Commands
Table 17-5 Related commands for configuring service common software configuration
parameters
Command Function
SET To set service common software configuration parameters

SRVCOMCFG
LST To query service common software configuration parameters

SRVCOMCFG
17.4.2 Setting Software Configuration Parameters (Two)

This topic describes how to set software configuration parameters of type two.
This is a configuration command and is used to set the software parameters for the CFS

Command
SET SOFTCFG2
Parameter
r ID r Name
MSGTYP CFS INAP It specifies the INAP subsystem in the call filter service. It is
SSN optional. Its value is of the numeral type and ranges 0-255.
When the SSN in an INAP message is not the default value, you
must set the value of CFS INAP SSN the same as the SSN
contained in the INAP message; otherwise, the system cannot
perform CFS processing.
Related Commands
Table 17-6 Related commands for configuring software configuration parameters (two)
Command Function
SET SOFTCFG2 To set software configuration parameters (two)
LST SOFTCFG2 To query software configuration parameters (two)
NOTE
Only the black list service requires configuring software configuration parameters (two).
17.4.3 Adding the MTP DSP

This topic describes how to add announcement resources for a destination signaling point (DSP).
Command
ADD N7DSP

Parameter
r ID r Name
SERFUN Service This switch controls the services that are applied to a DSP.
CSWCH function It is optional. Its value is of the enumeration type. It can be set to
switch one or more of the following values:
l BIT0 (Collecting digits for ISUP message): It determines
according to the office direction whether to collect digits. If yes,
the system sends an IAM and SAM messages to the MNP
service module for processing; if not, the system sends an IAM
message only.
l BIT1 (Avoid Re-querying): When this switch is enabled, the
system determines whether to perform the MNP processing
according to the office direction and the SPC contained in the
message. This prevents repeated query in multiple NPDBs.
l BIT2 (LNP): When this switch is enabled, the system performs
the MAP-layer decoding operation to obtain the MSISDN and
then queries the NP database, thus implementing the local
number portability (LNP) service.
l BIT3 (Whether have language resource): Bit3 of this
parameter is used to determine whether a signaling point has the
announcement resource. If an OPC has the resource, the system
returns an REL message. If an OPC does not have the resource
but the DPC has, the system adds Release number prefix
specified in the CFS service software parameter table to the
called number contained in the IAM message and then forwards
the message according to the original route. This parameter is
applied to only the white list service. The system returns the
REL message or forwards the IAM message in which the release
number prefix is added in the case that the IAM message should
be shielded.
Related Commands
Table 17-7 Related commands for configuring the MTP DSP

Command Function
ADD N7DSP To add the MTP DSP
MOD N7DSP To modify the MTP DSP
RMV N7DSP To remove the MTP DSP
LST N7DSP To query the MTP DSP

NOTE
Only the white list service requires configuring the MTP DSP.
17.4.4 Adding the MTP Link Set

This topic describes how to set the distinguishing type for a link set.
This is a configuration command and is used to set the distinguishing type for a link set.
Command
ADD N7LKS
Parameter
r ID r Name
SRVPRO Service It determines which service is enabled. You can enable any service
SWT process by selecting the service.
switch It is optional. Its value is of the enumeration type. It can be set to
one or more of the following values:
l BW (BW switch)
l NS (Number switch)
l ISUP (ISUP fraud prevention)
l ROSWT (Reroute switch)
l CFSSWT (CFS service switch)
l CNLSWT (CNL service switch)
l LNPSWT (LNP service switch)
l RIAM (IAM reroute switch)
Select CFS service switch to enable the CFS service.


r ID r Name
NUMDIS Number It specifies the number distinguishing type of a link set. The system
MOPT discrimina compares the value of this parameter with the distinguishing type
tion option matching the called number and performs the related processing.
The processing principles are as follows:
l If the distinguishing type matching the called number is the
calling number and the distinguishing type configured for a link
set contains this calling number, the system performs the
l If the distinguishing type matching the called number is the
called number and the distinguishing type configured for a link
set contains this called number, the system performs the
l In other cases, the system forwards the message according to
the original route.
It is optional. Its value is of the enumeration type. It can be set to
one or more of the following values:
l BIT0 (Calling number)
l BIT1 (Called number)
Related Commands
Table 17-8 Related commands for configuring the number distinguishing type
Command Function
RMV N7LKS To remove the MTP link set
NOTE
Only the white list service requires configuring the MTP link set.
17.4.5 Adding the Number Analysis Prefix

This topic describes how to add the number analysis prefix.
A number analysis prefix is used to analyze some special prefixes and call types contained in
numbers, such as the country code, toll call selection code of a carrier, and called party payment
prefix.

Command
ADD PREANALYSIS
Parameter
r ID r Name
PRENUM Prefix It specifies a special number prefix, such as the country code, toll
analysis call selection code of a carrier, and called party payment prefix.
number It is mandatory. Its value is of the character type and contains
numbers 0-9 and upper-case letters A-F. Its value contains a
maximum of 16 bytes. It is null by default.
NUMATT Non It specifies the attribute of the prefix analysis number irrelevant to
A service the service. It can be set to:
attribute l NCLIP (Not clip, return all after RN)
l NQDB (Not query DB)
l ALLAFT (Clip query, return all after RN)
l ALLBEF (Clip query, return all before RN)
l PARTAFT (Clip query, return part after RN)
l PARTBEF (Clip query, return part before RN)
l NRET (Clip query, not return)
l NP (NP query identification)
It is set to Not clip, return all after RN by default. For non-NP
subscribers, the RN is not required.
NUMATT Service It specifies the attribute of the prefix analysis number related to the
B attribute service. It can be set to:
l OTHER (Other)
l AREA (Area code)
l LGCPAY (Service provide code)
l LGCEDPAY (Long distance called paid ID)
l LCEDPAY (Local called paid ID)
l CTRG (IN caller trigger)
l CEDTRG (IN called trigger)
l SPECIAL (Non geographic code)
l LOCSPC (Local special code)
l CNTCODE (Country code)
l SPECODE (Special treatment code)
It is set to Other by default. The value Special treatment code is
reserved.

Related Commands
Table 17-9 Related commands for configuring the number analysis prefix
Command Function
ADD PREANALYSIS To add the number analysis prefix
MOD PREANALYSIS To modify the number analysis prefix
RMV PREANALYSIS To remove the number analysis prefix
LST PREANALYSIS To query the number analysis prefix
17.4.6 Adding the CFS Call Type

This topic describes how to add the CFS call type.
This is a configuration command and is used to add a CFS call type. The system detects the call
type of a subscriber based on the call type table and determines whether to process the call.
Command
ADD CFSCI
Parameter
r ID r Name
CTPYE Call It specifies the prefix of the call type for a CFS subscriber. The
identify prefix contains number type information.
prefix It is mandatory. Its value is of the character string type and can
contain numbers 0-9, upper-case letters A-F, and lower-case letters
a-f. Its value contains a maximum of 8 bytes.
BASENU Call It specifies the shielding number selection reference of a call type.
M identify It is mandatory. Its value is of the enumeration type. It can be set
base to:
number
l CGPN (Calling party number)
l CDPN (Called party number)

Related Commands
Table 17-10 Related commands for configuring the CFS call type
Command Function
ADD CFSCI To add the CFS call type
MOD CFSCI To modify the CFS call type
RMV CFSCI To remove the CFS call type
LST CFSCI To query the CFS call type
17.4.7 Adding the CFS Shielding Release Cause

This topic describes how to add the CFS shielding release cause.
This is a configuration command and is used to add a CFS shielding release cause.
Command
ADD CFSRC
Parameter
r ID r Name
RELCAU Release It specifies the cause for releasing a public shielding number. This
SE cause field must be unique.
It is mandatory. Its value is of the numeral type. Its value range is
0-127.
ACTION Process It specifies the mode in which the system processes a number.
action It is optional. Its value is of the enumeration type. It can be set to:
l CNT (Continue): The system continues the processing.
l FIN (Finish): The system stops the processing.
l RED (Redirect): The system modifies the called number to the
number configured by the subscriber, and modifies the address
attribute to the configured value.
l CHG (Change): The system adds the configured number to the
called number.
l NUM (Only replace number): The system modifies the called
number to the number configured for the subscriber.
It is set to Continue by default. It must be configured according
to actual conditions.


r ID r Name
NUMAD Nature of It specifies the address attribute of a called number. It is valid only
DR address when Process action is set to Redirect.
NUMPLA Number It specifies the numbering plan of a called number. It is valid only
N plan when Process action is set to Redirect.
NUM Number It specifies a modified number. It is valid only when Process

action is set to Redirect, Change, or Only replace number.
It is optional. Its value is of the character string type and can contain
maximum of 20 bytes.
Related Commands
Table 17-11 Related commands for configuring the CFS shielding release cause
Command Function
ADD CFSRC To add the CFS shielding release cause
MOD CFSRC To modify the CFS shielding release cause
RMV CFSRC To remove the CFS shielding release cause
LST CFSRC To query the CFS shielding release cause
17.4.8 Adding the CFS Personal List

This topic describes how to add the CFS personal shielding number.
This is a configuration command and is used to add a CFS personal shielding number.
Command
ADD CFSPL
Parameter
r ID r Name
CID Personal It specifies the personal ID of a CFS subscriber. It is mandatory.

ID Its value is of the numeral type. Its value range is 0-2147483647.


r ID r Name
BEGNU Begin It specifies the start number of a personal ID. It is mandatory. Its
M number value is of the character string type and can contain numbers 0-9
and upper-case letters A-F. Its value contains a maximum of 22
bytes.
ENDNU End It specifies the end number of a personal ID. It is mandatory. Its
M number value is of the character string type and can contain numbers 0-9
and upper-case letters A-F. Its value contains a maximum of 22
bytes.
Related Commands
Table 17-12 Related commands for configuring the CFS personal list
Command Function
ADD CFSPL To add the CFS personal list
MOD CFSPL To modify the CFS personal list
RMV CFSPL To remove the CFS personal list
LST CFSPL To query the CFS personal list
NOTE
Only the black list service requires configuring the CFS personal list.
17.4.9 Adding the CFS Common List

This topic describes how to add the CFS common shielding number.
This is a configuration command and is used to add a CFS common shielding number. The
system checks call numbers according to the common shielding number table to determine
whether to shield the call.
Command
ADD CFSCL
Parameter
r ID r Name
CID Common It specifies the common shielding ID of a subscriber. Common IDs

ID can be identical. It is mandatory. Its value is of the numeral type.
Its value range is 0-2147483647.


r ID r Name
BEGNU Begin It specifies the start number of a common shielding ID.

M number It is mandatory. Its value is of the character string type and contains
ENDNU End It specifies the end number of a common shielding ID.

M number It is mandatory. Its value is of the character string type and contains
Related Commands
Table 17-13 Related commands for configuring the CFS common list
Command Function
ADD CFSCL To add the CFS common list
MOD CFSCL To modify the CFS common list
RMV CFSCL To remove the CFS common list
LST CFSCL To query the CFS common list
NOTE
Only the black list service requires configuring the CFS common list.
17.4.10 Adding the CFS Public List

This topic describes how to add the CFS public shielding number.
This is a configuration command and is used to add a CFS public shielding number. The system
checks call numbers according to the public shielding number table to determine whether to
shield the call.
Command
ADD CFSPBL

Parameter
r ID r Name
BEGNU Begin It specifies the start number of a public ID.

M number It is mandatory. Its value is of the character string type and can
ENDNU End It specifies the end number of a public ID.

M number It is mandatory. Its value is of the character string type and can
RELCAU Release It specifies the cause for releasing a public shielding number. This
SE cause parameter must be defined by using ADD CFSRC before being
referenced here.
It is mandatory. Its value is of the numeral type and ranges 0-127.
Related Commands
Table 17-14 Related commands for configuring the CFS public list
Command Function
ADD CFSPBL To add the CFS public list
MOD CFSPBL To modify the CFS public list
RMV CFSPBL To remove the CFS public list
LST CFSPBL To query the CFS public list
NOTE
Only the black list service requires configuring the CFS public list.
17.4.11 Adding the CFS Service User

This topic describes how to add the CFS service subscriber.
This is a configuration command and is used to add the data related to CFS service subscribers.
Command
ADD CFSUSR

Parameter
r ID r Name
DN Directory It specifies the directory number of a CFS subscriber.

number It is mandatory. Its value is a character string of up to 16 characters.
LRN Location It specifies the location routing number of a CFS subscriber.

routing It is mandatory. Its value is a character string of up to 16 characters.
number
CID Personal It specifies the ID of the personal shielding number table.

list ID It is optional. Its value is of the numeral type and ranges
0-2147483647. When it is set to the default value 2147483647, the
record is invalid. All valid records must be configured in the
personal shielding number table.
CIDREAS Personal It specifies the cause for releasing a personal shielding number.
ON list block The personal shielding number release cause and the common
release shielding number release cause share the same field. The length of
cause the field is 8 bytes and value range is 0-255. The first four bytes
(bits 0-3) of the field indicate the personal shielding number release
cause.
SID Common It specifies the ID of the common shielding number table.

0-2147483647. When it is set to 2147483647, the record is invalid.
All valid records must be configured in the personal shielding
number table.
SIDREAS Common It specifies the cause for releasing a common shielding number.
ON list block The common shielding number release cause and the personal
release shielding number release cause share the same field. The length of
cause the field is 8 bytes and value range is 0-255. The last four bytes
(bits 4-7) of the field indicate the common shielding number
release cause.
CT1-20 Call The system converts a call identity prefix to the index of call type
identify N (N is an integer and ranges 1-20).
prefix They are optional. The value of the parameters is of the character
1-20 string type and contains numbers 0-9 and upper-case letters A-F.
The value contains a maximum of 8 characters. When the value is
null, the system sets the value to 255, indicating an invalid record.


r ID r Name
CT1REA Call They specify the release causes of call types 1-20. The release
SON- identify 1 cause of call type N and the release cause of call type N+1 share
CT20REA release the same field. The length of the field is 8 bytes and value range is
SON cause-Call 0-255. The first four bytes (bits 0-3) of the field indicate the release
identify 20 cause value of call type N (N is an integer and ranges 1-20).
release They are optional. The value of the parameters is of the numeral
cause type and ranges 0-127.
Related Commands
Table 17-15 Related commands for configuring the CFS service user
Command Function
ADD CFSUSR To add the CFS service user
MOD CFSUSR To modify the CFS service user
RMV CFSUSR To remove the CFS service user
LST CFSUSR To query the CFS service user
17.4.12 Adding the CFS User Number Range

This topic describes how to add the CFS subscriber number range.
This is a configuration command and is used to add the data related to CFS subscribers.
Command
ADD CFSUSRRANGE
Parameter
r ID r Name
DN Begin It specifies the start number of a CFS subscriber.

number It is mandatory. Its value is of the character string type. Its value
contains a maximum of 16 characters.
LRN End It specifies the end number of a CFS subscriber.

number It is mandatory. Its value is of the character string type. Its value
contains a maximum of 16 characters.


r ID r Name
CID Personal It specifies the ID of the personal shielding number table.

number table.
CIDREAS Personal It specifies the cause for releasing a personal shielding number.
ON list block It is optional. Its value is of the numeral type. Its value range is
release 0-127. It is set to 0 by default.
cause
SID Common It specifies the ID of the common shielding number table.

number table.
SIDREAS Common It specifies the cause for releasing a common shielding number.
ON list block It is optional. Its value is of the numeral type. Its value range is
release 0-127. It is set to 0 by default.
cause
CT1- Call They specify the call identity prefixes of CFS subscribers.
CT20 identify They are optional. The value of the parameters is of the character
prefix string type and contains numbers 0-9 and upper-case letters A-F.
1-20 The value contains a maximum of 8 characters. When the value is
null, the system automatically sets the value to 255, indicating an
invalid record.
CT1REA Call They specify the release causes of call identity prefixes.
SON- identify It is optional. Its value is of the numeral type. Its value range is
CT20REA release 0-127. It is set to 0 by default.
SON cause 1-20
Related Commands
Table 17-16 Related commands for configuring the CFS user number range
Command Function
ADD CFSUSRRANGE To add the CFS user number range
MOD CFSUSRRANGE To modify the CFS user number range
RMV CFSUSRRANGE To remove the CFS user number range
LST CFSUSRRANGE To query the CFS user number range

17.4.13 Setting CFS Service Software Parameters

This topic describes how to set CFS service software parameters.
This is a configuration command and is used to set the software parameters for the CFS service.
Command
SET CFSSOFTCFG
Parameter
Paramet Paramete Parameter Description
er ID r Name
CFSSWT CFS It specifies the status of the CFS service processing switch.
service It is optional. Its value is of the enumeration type. It can be set to:
switch
l CLOSE (Close)
l OPEN (Open)
It must be configured according to actual conditions.
NUMSW Number It specifies the status of the number amendment switch and
T amendme amendment type.
nt switch It is optional. Its value is of the enumeration type. It can be set to:
l CLOSE (Close): The number amendment function is disabled.
l BASE (Basic number amendment): The system removes the
prefix 00 from the country code, and removes special prefixes
and prefix 0 from the subscriber number.
l EXTEND (Extend number amendment): The system
identifies various prefixes (the special query prefix, NP
identification, called-party payment prefix 90, country code,
CSP, and area code) and removes the prefixes from subscriber
numbers.
PROTOC CFS It specifies the type of the protocol to be processed in the CFS
OL process service.
protocol It is optional. Its value is of the enumeration type. It can be set to
type one or more of the following values:
l BIT0 (ISUP)
l BIT1 (INAP)
l BIT2 (SIP)


er ID r Name
CNUMB Base It specifies the base for selecting the calling number in the case of
ASE number call forwarding.
when CF It is optional. Its value is of the enumeration type. It can be set to:
l CNUM (Calling number)
l RNUM (Redirecting number)
SELKEY CFS query It specifies the key for querying the CFS service. It is valid only
service when CFS process protocol type is set to INAP. It is optional. Its
key value is of the numeral type and ranges 0-2147483647.
CNUMS Calling It specifies the status of the switch for shielding the calling number
WT number length.
length It is optional. Its value is of the enumeration type. It can be set to:
block
switch l CLOSE (Close)
l OPEN (Open)
CNCAU Calling It specifies the cause for shielding the calling number length. It is
SE number optional. Its value is of the numeral type and ranges 0-127.
length
block
release
cause
MINLEN Min It specifies the minimum length of a calling number. It is optional.

calling Its value is of the numeral type and ranges 0-22.
number
length
MAXLE Max It specifies the maximum length of a calling number. It is optional.

N calling Its value is of the numeral type and ranges 0-22.
number
length
PUBSW Public list It specifies the status of the switch for shielding the public number
T block shielding table.
switch It is optional. Its value is of the enumeration type. It can be set to:
l OPEN (Open)
l CLOSE (Close)


er ID r Name
PUBBAS Public list It specifies the type of the base number in the public shielding
E base number table.
number It is optional. Its value is of the enumeration type. It can be set to:
l CGPN (Calling party number)
l CDPN (Called party number)
REVPAR Parameter Bit0 of Parameter 1 controls whether the system removes a

A1 1 special prefix.
Bit1 of Parameter 1 controls whether the system identifies the M
IE and performs the corresponding processing.
TBLBW B&W list It specifies the type of the service to be processed.

LSTOPT option It is mandatory. Its value is of the enumeration type. It can be set
to:
l BLACK0 (Black list): The system processes the black list
service in the CFS service.
l WHITE1 (White list): The system processes the white list
service in the CFS service.
RELCA Release It specifies a release cause in the white list service.

USE cause It is optional. Its value is of the numeral type and ranges 0-127.
RLSNU Release It specifies the number prefix added for message shielding in the
MPFX number white list service.
prefix It is optional. Its value is of the numeral type and ranges 0-20.
CGPNCT Special It specifies a special subscriber type in the white list service.
RY process It is optional. Its value is of the numeral type and ranges 0-255.
category The value 0 indicates an invalid subscriber.
NUMFM Format of It specifies the format of the number for query. Based on the
T search number format specified by this parameter, the system uses the
number original number or the normalized called number to match a record
in the public CFS user table. Then, the system implements
subsequent processing based on the matched record.
It is optional. Its value is of the enumeration type. It can be set to:
l ORINUM (Original number)
l AMENDNUM (Amended number)
It is set to ORINUM (Original number) by default.


er ID r Name
SWTPB Process It specifies whether to process a call according to the calling

NM based on procedure when an IAM or INAP IDP message does not match a
calling call type.
number if It is optional. Its value is of the enumeration type. It can be set to:
no call
type is l OPEN (Open)
matched l CLOSE (Close)
It is set to OPEN (Open) by default.
Related Commands
Table 17-17 Related commands for configuring CFS service software parameters
Command Function
SET CFSSOFTCFG To set CFS service software parameters
LST CFSSOFTCFG To query CFS service software parameters

This topic describes the examples for configuring the CFS service.
17.5.1 Example Description (Black List Service)

This topic describes data configurations related to the CFS black list service.
17.5.2 Example Description (White List Service)
This topic describes data configurations related to the CFS white list service.
17.5.1 Example Description (Black List Service)

This topic describes data configurations related to the CFS black list service.
Collection of Service Data

Table 17-18 lists the data collected for configuring the CFS black list service.
Table 17-18 Data collected for configuring the CFS black list service

Country code 63 138138000000
of equipment

Standard length for

8 CFS INAP SSN 168
number amend
Message type of Select Extend

Enable ISUP and Number
CFS service number
INAP amendment switch
processing amendment.
Base number when CFS query service

Calling number 1193046
CF key
Calling number
Calling number
Enabled length block release 1
length block switch
cause
Min calling number Max calling

2 12
length number length
Public list block Public list base

Enabled Calling number
switch number
Process based on
Format of search
Original number calling number if no Open
number
call type is matched
Release cause 1 Process action Select Redirect
Nature of address 3 Number plan 1
Number 7528420000
Start number (ADD 7528420

Personal list ID 1
CFSPBL)
End number (ADD

7528429 Common list ID 1
CFSPBL)

75284250 75284259
CFSCL) CFSCL)
Start number (ADD End number (ADD 752841

752840
CFSPL) CFSPL)
Public list block

1 Call identify prefix 9090
release cause
Call identify base

Calling number
number
Select ALLAFT
9090 (Clip query, return
number attribute
all after RN)
Select LCEDPAY
Prefix analysis
Service attribute (Local called paid 75
number
ID)

Select ALLAFT
Non service Select AREA (Area
(Clip query, return Service attribute
attribute code)
all after RN)
Calling number
Directory number:
7528422222
Location routing
User IMSI number number: Personal list ID 1
7522222222
The called party is
not configured in the
user property table.
Personal list block

1
release cause
Common list block

Common list ID 1 1
release cause

9090 1
1 release cause
Start number:
User number range 752841 Personal list ID 1
End number: 752849
Personal list block

1 Common list ID 1
release cause
Common list block Call identify prefix

1 9090
release cause 1
Call identify 1
1
release cause
Do not disturb list

User number 121 1
ID
Release cause 1
Based on the preceding data collected, the following parts illustrate data configurations related
to the CFS black list service.
Procedure
Step 1 Set service common software configuration parameters
To set service common software configuration parameters, where Country code is 63, Global
title address of equipment is 138138000000, and Standard length for number amend is 8,

SET SRVCOMCFG: COUNTRYCODE="63", GTCODE="138138000000", STDNUMLEN=8;
Step 2 Set software configuration parameters (two)

To set software configuration parameters (two), where CFS INAP SSN is 168, run the following
command:
SET SOFTCFG2: CFSINAPSSN=168;
Step 3 Add the number analysis prefix

To add a number analysis prefix, where Local called paid ID is 9090 and Area code is 75, run
ADD PREANALYSIS: PRENUM="9090", NUMATTA=ALLAFT, NUMATTB=LGCEDPAY;
ADD PREANALYSIS: PRENUM="75", NUMATTA=ALLAFT, NUMATTB=AREA;
Step 4 Add the CFS call type

To add the CFS call type, where Call identify prefix is 9090 and Call identify base number
is Calling number, run the following command:
ADD CFSCI: CTYPE="9090", BASENUM=CGPN;
Step 5 Add the CFS shielding release cause

To add the CFS shielding release cause, where Release cause is 1, Process action is Redirect,
Nature of address is 3, Number plan is 1, and Number is 7528420000, run the following
command:
ADD CFSRC: RELCAUSE=1, ACTION=RED, NUMADDR=3, NUMPLAN=1, NUM="7528420000";
Step 6 Add the CFS personal list

To add the CFS personal list, where Personal list ID is 1, Start number is 7528420, End
number is 7528429, run the following command:
ADD CFSPL: CID=1, BEGNUM="7528420", ENDNUM="7528429",CONFIRM=Y;
Step 7 Add the CFS common list

To add the CFS common list, where Common list ID is 1, Start number is 75284250, End
number is 75284259, run the following command:
ADD CFSCL: CID=1, BEGNUM="75284250", ENDNUM="75284259";
Step 8 Add the CFS public user

To add the CFS public user, where User number is 121, Do not disturb list ID is 1, and Release
cause is 1, run the following command:
ADD CFSPBLUSR: USRNUM="121", DNDLIST=1, RC=1,CONFIRM=Y;
Step 9 Add the CFS public list

To add the CFS public list, where Start number is 752840, End number is 752841, and Release
cause is 1, run the following command:
ADD CFSPBL: BEGNUM="752840", ENDNUM="752841", RELCAULSE=1;
Step 10 Add the CFS service user

To add the the CFS service user, where Directory number is 7528422222, Location routing
number is 7522222222, Personal list ID is 1, Personal list block release cause is 1, Common

list ID is 1, Common list block release cause is 1, and Call identify prefix 1 is 9090, run the
following command:
ADD CFSUSR: DN="7528422222", LRN="752222222", CID=1, CIDREASON=1, SID=1,
SIDREASON=1, CT1="9090", CT1REASON=1;
Step 11 Set CFS system software parameters
To set CFS system software parameters, where CFS service switch is Open, Number
amendment switch is Extend number amendment, CFS process protocol type is ISUP
+INAP, Base number when CF is Calling number, CFS query service key is 1193046,
Calling number length block switch is Open, Calling number length block release cause is
1, Min calling number length is 2, Max calling number length is 12, Public list block
switch is Open, Public list base number is Calling number, Format of search number is
Original number, and Process based on calling number if no call type is matched is
Open, run the following command:
SET CFSSOFTCFG: CFSSWT=OPEN, NUMSWT=EXTEND, PROTOCOL=BIT0-1&BIT1-1&BIT2-0,
CNUMBASE=CNUM, SELKEY=1193046, CNUMSWT=OPEN, CNCAUSE=1,
MINLEN=2, MAXLEN=12, PUBSWT=OPEN, PUBBASE=CGPN, NUMFMT=ORINUM,
SWTPBNM=OPEN,CONFIRM=Y;
Step 12 Add the CFS user number range
To add the CFS user number range, where Start number is 752841, End number is 752849,
Personal list ID is 1, Personal list block release cause is 1, Common list ID is 1, Common
list block release cause is 1, Call identify prefix 1 is 9012, Call identify 1 release cause is
1, Call identify prefix 2 is 12, and Call identify 2 release cause is 1, run the following
command:
ADD CFSUSRRANGE: DN="752841", LRN="752849", CID=1, CIDREASON=1, SID=1,
SIDREASON=1, CT1="9012", CT1REASON=1, CT2="12", CT2REASON=1;
----End
17.5.2 Example Description (White List Service)

This topic describes data configurations related to the CFS white list service.

Table 17-19 lists the data collected for configuring the CFS white list service.
Table 17-19 Data collected for configuring the CFS white list service

Country code 63 138138000000
of equipment
Whether have
Standard length for
8 language resource 168
number amend
on OPC
Whether have
With announcement Link set Calling number and
language resource
resources discrimination type called number
on DPC

Message type of Select Extend

Number
CFS service Select ISUP number
amendment switch
processing amendment.
Parameter 1
Base number when (special prefix
Calling number 3
CF processing and M
IE determination)
B&W list option White List Release cause 1
Release number Special process

138 8
prefix category 1
Release cause 1 Process action Select Redirect
Nature of address 3 Number plan 1
Number 7528420000
Call identify base Calling number

Call identify prefix 9012
number
Call identify base Called number

Call identify prefix 90
number
Select ALLAFT
number attribute
all after RN)
Select LGCPAY
Service attribute (Service provide
code)
Select ALLAFT
number attribute
all after RN)
Select LGCEDPAY
Service attribute (Long distance
called paid ID)
Select ALLAFT
number attribute
all after RN)
Select AREA (Area

Service attribute
code)

Calling number
Directory number:
7528422222
Location routing Call identify prefix
User IMSI number number: 9012
1
7522222222
The called party is
not configured in the
user property table.
Call identify 1
1
release cause

12 1
1 release cause
Start number:
752841 Call identify prefix
User number range 9012
1
End number: 752849
Call identify 1 Call identify prefix

1 12
release cause 1
Call identify 1
1
release cause
Based on the preceding data collected, the following parts illustrate data configurations related
to the CFS white list service.
Procedure
Step 1 Set service common software configuration parameters
To set service common software configuration parameters, where Country code is 63, Global
title address of equipment is 138138000000, and Standard length for number amend is 8,
SET SRVCOMCFG: COUNTRYCODE="63", GTCODE="138138000000", STDNUMLEN=8;
Step 2 Add the MTP DSP
To add the MTP DSP, where DSP title is BBBBBB and Service function switch is Whether
have language resource, run the following command:
ADD N7DSP: SERFUNCSWCH=BIT0-1&BIT0-3;
Step 3 Add the MTP link set
To add the MTP link set, where Service process switch is CFS service switch and Number
discrimination option is Calling number and Called number, run the following command:
ADD N7LKS: APX=0, OFX=0, NI=NM, SRVPROSWT=CFSSWT-1, NUMDISMOPT=BIT0-1&BIT1-1

Step 4 Add the number analysis prefix

To add the number analysis prefix, where Local called paid ID is 90, Area code is 75, and
Service provide code is 12, run the following command:
ADD PREANALYSIS: PRENUM="90", NUMATTA=ALLAFT, NUMATTB=LGCEDPAY;
ADD PREANALYSIS: PRENUM="75", NUMATTA=ALLAFT, NUMATTB=AREA;
ADD PREANALYSIS: PRENUM="12", NUMATTA=ALLAFT, NUMATTB=LGCPAY;
Step 5 Add the CFS call type

To add the CFS call type, where Call identify prefix is 9090 and Call identify base number
is Calling number, run the following command:
ADD CFSCI: CTYPE="9090", BASENUM=CGPN;
Step 6 Add the CFS shielding release cause

To add the CFS shielding release cause, where Release cause is 1, Process action is Redirect,
Nature of address is 3, Number plan is 1, and Number is 7528420000, run the following
command:
ADD CFSRC: RELCAUSE=1, ACTION=RED, NUMADDR=3, NUMPLAN=1, NUM="7528420000";
Step 7 Add the CFS service user

To add the CFS service user, where Directory number is 7528422222, Location routing
number is 7522222222, Call identify prefix 1 is 9012, Call identify 1 release cause is 1, Call
identify prefix 2 is 12, and Call identify 2 release cause is 1, run the following command:
ADD CFSUSR: DN="7528422222", LRN="752222222", CT1="9012", CT1REASON=1, CT2="12",
CT2REASON=1;
Step 8 Set CFS system software parameters

To set CFS system software parameters, where CFS service switch is Open, Number
amendment switch is Extend number amendment, CFS process protocol type is ISUP,
Base number when CF is Calling number, Parameter 1 is 3, B&W list option is White
list, Release cause is 1, Release number prefix is 138, and Special process category 1 is 5,
SET CFSSOFTCFG: CFSSWT=OPEN, NUMSWT=EXTEND, PROTOCOL=BIT0-1, CNUMBASE=CNUM,
REVPARA1="3", TBLBWLSTOPT=WHITE, RELCAUSE=1, RLSNUMPFX="138", CGPNCTRY1=5;
Step 9 Add the CFS user number range

To add the CFS user number range, where Start number is 752841, End number is 752849,
Call identify prefix 1 is 9012, Call identify 1 release cause is 1, Call identify prefix 2 is 12,
and Call identify 2 release cause is 1, run the following command:
ADD CFSUSRRANGE: DN="752841", LRN="752849", CT1="9012", CT1REASON=1, CT2="12",
CT2REASON=1;
----End
Verifying Service Common Software Configuration Parameters

Run LST SRVCOMCFG to verify whether service common software configuration parameters
are correctly configured.
LST SRVCOMCFG:;
The output is as follows:

Service common software configuration parameter table

--------------
Country code = 63
Local operator CSP = 0
Global title address of equipment = 138138000000
Standard length for number amend = 8
Combination mode of RN = Fix prefix+CO+CL/CI
Latency time of the collecting digits(s) = 4
The fresh method of collecting digits timer = For IAM
SIP message option = G_1<OFF>
Prefix change switch = Close
Number prefix = 0
Clip length of IN prefix in IAM called number = 0
Parameter 1 = 0x00000000
--- END
Verifying Software Configuration Parameters (Two)

Run LST SOFTCFG2 to verify whether software configuration parameters (two) are correctly
configured.
LST SOFTCFG2:;

Software configuration parameter table-(two)
----------------
DSS IP1 = 192.168.1.0
Mask of DSS IP1 = 255.255.128.0
DSS IP2 = 192.168.128.0
Mask of DSS IP2 = 255.255.128.0
M3UA standard = RFC
Switch of flow control = Close
Threshold to start flow control = 70
Threshold to end flow control = 60
Wildcard function in GTT = Open
TCP link count = 3
CFS INAP SSN = 168
CNL INAP SSN = 12
LNP INAP SSN = 12
--- END
Verifying the Number Analysis Prefix

Run LST PREANALYSIS to verify whether the number analysis prefix is correctly configured.
LST PREANALYSIS:;

Prefix analysis number table
----------
Index Description Prefix analysis number Non service attribute Service
attribute
0 (NULL) 9090 Clip query, return all after RN Local called paid
ID

1 (NULL) 75 Clip query, return all after RN Area code

(Number of records = 2)
--- END
Verifying the CFS Call Type

Run LST CFSCI to verify whether the CFS call type is correctly configured.
LST CFSCI:;

CFS call identify table
-------------
Index Description Call identify prefix Call identify base number
0 <NULL> 9090 Calling number
--- END
Verifying the CFS Release Cause

Run LST CFSRC to verify whether the CFS release cause is correctly configured.
LST CFSRC:;

CFS block release cause table
-------------------
Index Description Release cause Process action Nature of address Number plan
Number
0 <NULL> 1 Redirect 3 1
7528420000
--- END
Verifying the CFS Personal Shielding Number

Run LST CFSPL to verify whether the CFS personal shielding number is correctly configured.
LST CFSPL:CONFIRM=Y;

CFS personal list table
---------------------
Index Description Personal list ID Start number End number
0 <NULL> 1 7528420 7528429
--- END

Verifying the CFS Common Shielding Number

Run LST CFSCL to verify whether the CFS common shielding number is correctly configured.
LST CFSCL:;

CFS common list table
-----------------
Index Description Common list ID Start number End number
0 <NULL> 1 75284250 75284259
--- END
Verifying the CFS Public Shielding Number

Run LST CFSPBL to verify whether the CFS public shielding number is correctly configured.
LST CFSPBL:,CONFIRM=Y;

CFS public list table
-----------------
Index Description Start number End number Release cause
0 <NULL> 752840 752841 1
--- END
Verifying the CFS Service User

Run LST CFSUSR to verify whether the CFS service user is correctly configured.
LST CFSUSR:,CONFIRM=Y;

CFS user table
-------------
Index = 1
Directory number = 7528422222
Location routing number = 752222222
Personal list ID = 1
Personal list block release cause = 1
Common list ID = 1
Common list block release cause = 1
Call identify prefix 1 = 9090
Call identify 1 release cause = 1
Call identify prefix 2 = NULL


--- END
Verifying the CFS User Number Range

Run LST CFSUSRRANGE to verify whether the CFS user number range is correctly
configured.
LST CFSUSRRANGE:,CONFIRM=Y;

CFS user table
-----------------
Index = 0
Start number = 752841
End number = 752849
Personal list ID = 1
Personal list block release cause = 1
Common list ID = 1
Common list block release cause = 1


--- END
Verifying CFS Service Software Parameters

Run LST CFSSOFTCFG to verify whether the CFS user number range is correctly configured.
LST CFSSOFTCFG:,CONFIRM=Y;

CFS service software parameter table
-------------
CFS service switch = Open
Number amendment switch = Extend number amendment
CFS process protocol type = G_3<OFF>G_2<OFF>G_1<OFF>
Base number when CF = Calling number
CFS query service key = 0
Calling number length block switch = Close
Calling number length block release cause = 0
Min calling number length = 0
Max calling number length = 22
Public list block switch = Close
Public list base number = Called number
B&W list option = White list
Release cause = 1
Release number prefix = 138
Special process category 1 = 8
--- END

Troubleshooting
If the service processing fails, locate and solve the problem based on the following:
l Run CHK LICENSE to check license information in the system and check whether the
CFS function switch is disabled.
l When Number amendment switch is set to Extend number amendment, run LST
PREANALYSIS to check the data in the prefix analysis table is correctly configured.
l Check whether all other subscriber data are correctly configured.
If the problem remains, contact Huawei engineers for technical support.

Feature Description 18 Configuring Message Duplication Service Data
18 Configuring Message Duplication

Service Data
About This Chapter
This chapter describes the definition of the message duplication service, service signaling flow,
preparations before data configuration, data configuration procedures, and configuration
examples.
18.1 Message Duplication Service

This topic describes service definition, advantages, interaction with other services, and version
requirement.
18.2 Network Structure
This topic describes the typical network structure for implementing the message duplication
service.
18.3 Service Implementation Principle
This topic describes the principles for implementing the message duplication service.
18.4 Call Flow
This topic describes the call flow of the message duplication service.
This topic describes the preparations to be completed before configuring the message duplication
service.
This topic describes the detailed procedures for configuring the message duplication service.
This topic provides the detailed example to demonstrate how to configure the message
duplication service.

18 Configuring Message Duplication Service Data Feature Description
18.1 Message Duplication Service

This topic describes service definition, advantages, interaction with other services, and version
requirement.
Definition
The message duplication service enables the SG7000 to duplicate a required message and sends
it to the third-party platform through the standard SS7 interface. After that, the SG7000 routes
the original message based on the normal flow.
Advantages
l This service enables a carrier to take the leading position in providing subscribers with
customized and differentiated services, and helps a carrier to improve the enterprise image.
l This service meets customers' requirements on special functions. New supplementary
services are processed on the new service platform, which allows the minimum change of
external NEs and reduces the impact on the original service platform.
l A carrier can use the SG7000 as the message duplication device, without changing any
other NEs.
l An NE can be added to process the special messages duplicated and sent by the SG7000.
Thus, a special service is implemented, the cost is reduced, and the customer satisfaction
is improved. For example,
– Cooperating with the HLR to implement the compatibility redundancy solution
– Cooperating with the AS to implement the short message welcome function
Service Interaction
If the rerouting service and message duplication service are simultaneously enabled for a link
set, the message duplication service takes the precedence.
Version Requirements
This service is provided in V200R005C02 and its later versions.
18.2 Network Structure

This topic describes the typical network structure for implementing the message duplication
service.
Figure 18-1 shows the typical network structure for implementing the message duplication
service.

Figure 18-1 Typical network structure for implementing the message duplication service
Dest Node Copy Special Node
SG7000
Source Node
Normal message sending path
Copied message sending path
l Signaling Gateway (SG7000): It stores the service data for subscribers and serves as the
message duplication device to duplicate required messages.
l Source Node: It serves as the source point of the message to be duplicated.
l Dest Node: It serves as the destination point to which the original message is sent after the
SG7000 duplicates the message.
l Copied Special Node: It serves as the destination point to which the duplicated message is
sent by the SG7000.
18.3 Service Implementation Principle

This topic describes the principles for implementing the message duplication service.
To implement the message duplication service, you only need to connect the SG7000 to the
Source Node through ordinary links rather than adding other NEs. The SG7000 filters the
messages received over the MTP or M3UA link set that is configured the message duplication
service.
1. The SG7000 determines whether the received message meets the duplication conditions
based on the information contained in the message.
Message duplication conditions contain the following: message terminating point, OPC,
DPC, called GT, calling GT, and operation code.
2. If the received message meets the duplication conditions, the SG7000 processes the
message according to the configured processing rules.
3. The SG7000 performs the subsequent processing based on the configured processing rules.

NOTE
For a message to be duplicated, you can configure the data to determine whether to modify the DPC in the
message. In the case that the destination of the duplicated message is unreachable, you can configure the
data to determine whether to discard the message or send the message based on the original route.
18.4 Call Flow

This topic describes the call flow of the message duplication service.
Message Processing Flow

Figure 18-2 shows the message processing flow of the message duplication service.
Figure 18-2 Message processing flow of the message duplication service
Source Node SG7000 Dest Node Copied Special Node
Update
Location
Update Location
Update Location
Original signaling flow Copied signaling flow
Message Flow Description

1. The SG7000 determines whether to duplicate the message sent from a specified link set.
2. If the duplication is not required, the SG7000 directly forwards the message to the
destination device. The signaling flow is as shown by the blue line in Figure 18-2.
3. If message duplication is required, the SG7000 duplicates the message and then sends it to
the specified device (for example, the AS of the third-party platform) based on the
information combination contained in the message. The signaling flow is as shown by the
yellow line in Figure 18-2.
NOTE
The updateLocation message in the preceding message flow is an example. The message duplication service
involves six types of messages: sendAuthenticationInfo, purgeMS, readyForSM, restoreData,
updateLocation, and updateGprsLocation.


This topic describes the preparations to be completed before configuring the message duplication
service.

This topic describes the relations between data tables of the message duplication service.
18.5.2 Data Configuration Requirement on Interconnected Equipment
This topic describes data configuration requirements on interconnected equipment involved in
the message duplication service.
This topic describes the data to be collected for configuring the message duplication service.
This topic describes the general configuration concepts of the message duplication service.
This topic describes the general steps for configuring the message duplication service.

This topic describes the relations between data tables of the message duplication service.
Figure 18-3 shows the relations between the data tables related to the message duplication
service.

Figure 18-3 Relations between the data tables related to the message duplication service
ADD RROPC
[Reroute reference]
Type of next
[ ]
reroute table
ADD RRDPC
[Reroute reference]
Type of next
[ ]
reroute table
ADD N7LKS ADD RRCDGT
Service process
[ ]
switch [Reroute reference]
Message copy Type of next
[ Policy
] [ ]
reroute table
Type of next
[ message copy ]
table
ADD RRCGGT
[ Next message ]
copy reference
[Reroute reference]
ADD M3ASSOS
Type of next
[ ]
reroute table
Service process
[ ] [ Next reroute reference ]
switch
Message copy ADD RROC
[ Policy
]
Type of next [Reroute reference]
[ message copy ] [Operation code]
table
Next message [Type of next reroute table]
[ ]
copy reference [Next reroute reference]
ADD RRRULE
Reroute processing
[ Rule index
]
[Load-share select mask]
[ Destinations 0-15 ]
[Priorities 0-15]
[Reroute rule switch]
[Reroute direction]

18.5.2 Data Configuration Requirement on Interconnected

Equipment
This topic describes data configuration requirements on interconnected equipment involved in
the message duplication service.
The message duplication service requires that the SG7000 interconnects with other equipment
through SS7 signaling.

This topic describes the data to be collected for configuring the message duplication service.
Table 18-1 lists the data to be collected before configuring the message duplication service.

Service process switch Message copy policy Type of next message copy
table
Next message copy

reference
NOTE
The configuration of the message duplication service is similar to that of the message rerouting service.
Therefore, this topic specifies only different parameters involved in the message duplication service. For
detailed configuration about other parameters, see 16 Configuring MRS Service Data.

This topic describes the general configuration concepts of the message duplication service.
The configuration of the message duplication service is similar to that of the message rerouting
service. During the configuration of link set data (by running ADD M3ASSOS and ADD
N7LKS), the following parameters are specially specified:
l Service process switch: It determines which service is enabled. The message duplication
service is enabled only when Service process switch is set to Message copy switch.
l Message copy policy: It specifies the policy for duplicating messages. It is valid only when
Service process switch is set to Message copy switch. If the message duplication switch
is enabled, the system checks the message duplication conditions and duplicates the
matching messages based on the configurations in the policy table. Then, the system sends
the duplicated messages to the specified signaling points. After that, the system forwards
the original messages based on the original routing information contained in the messages.
l Type of next message copy table: It specifies the next table whose messages are to be
duplicated in this link. If the message duplication data is not to be queried, set this parameter
to Void. This parameter, together with Next message copy reference, determines the table
item set used for message duplication in the next step.

l Next message copy reference: It specifies the reference of the message duplication in the
next message copy table. This parameter, together with Type of next message copy
table, determines the table item set used for message duplication in the next step. You do
not need to configure this parameter if the message duplication data is not to be queried.

This topic describes the general steps for configuring the message duplication service.
Table 18-2 shows the general procedures for configuring the message duplication service data.
Table 18-2 General procedures for configuring the message duplication service data
Step Operation
1 Add the MAP rerouting data to the rerouting calling GT number segment
table, rerouting called GT number segment table, rerouting number table,
and reroute rule table (ADD RRCGGTRNG, ADD RRCDGTRNG, ADD
RRUSRNUM, and ADD RRRULE).
2 Add the SCCP rerouting data to the OPC table, DPC table, called GT table,
calling GT table, and operation code table (ADD RROPC, ADD
RRDPC, ADD RRCDGT, ADD RRCGGT, and ADD RROC).
3 Add the M3UA or MTP link set (ADD M3ASSOS or ADD N7LKS).

This topic describes the detailed procedures for configuring the message duplication service.

service.
service.
reroute service.


reroute service.
18.6.10 Adding M3UA and MTP Link Set Data
This topic describes how to add the M3UA and MTP link set data.

Command
ADD RROPC
Parameter

processing.
the previous operation during the reroute process.
The object to be matched here is Next reroute
reference in the MTP link set or M3UA link set
table.

reroute process.
FO Minimum OPC It maps the minimum OPC number to be

Maximum OPC It maps the maximum OPC number to be


Type of next reroute It specifies the type of the table corresponding to

table the next reroute operation.
VOID (Invalid)
ROT (Reroute OPC table)
RDT (Reroute DPC table)
RCDT (Reroute called GT table)
condition set in Reroute policy. It is used to
match the corresponding data in the reroute table
Related Command
Table 18-3 Related commands for configuring the reroute OPC
Command Function
ADD RROPC To add the reroute OPC
MOD RROPC To modify the reroute OPC
LST RROPC To query the reroute OPC
RMV RROPC To remove the reroute OPC

Command
ADD RRDPC

Parameter
Name

processing.
reference in the MTP link set, M3UA link set, or
reroute OPC table.
NI Network It maps the network type to be processed in the

indication reroute process.
FO Minimum DPC It maps the minimum DPC number to be processed

TO Maximum DPC It maps the maximum DPC number to be processed

It can be set to:
l VOID (Invalid)


Name
Related Command
Table 18-4 Related commands for configuring the reroute DPC

Command Function
ADD RRDPC To add the reroute DPC
MOD RRDPC To modify the reroute DPC
LST RRDPC To query the reroute DPC
RMV RRDPC To remove the reroute DPC

service.
Command
ADD RRCDGT
Parameter
Name
RR Reroute It maps the reference of the reroute in the reroute

reference processing.
object to be matched here is Next reroute reference
in the MTP link set, M3UA link set, reroute OPC, or
reroute DPC table.


Name

process.
MSU message.

reroute process.
It is used to compare and match the translation type in
the MSU message.

reroute process.
in the MSU message.
AI Nature of address It maps the address nature indicator to be processed in

indicator the reroute process.
FAF Min. address It maps the information of the minimum address to be

minimum address in the MSU message. The address
TAF Max. address It maps the information of the maximum address to be

maximum address in the MSU message. The address


Name
It can be set to:
VOID (Invalid)
the corresponding data in the reroute table configured
in Type of next reroute table.
Related Command
Table 18-5 Related commands for configuring the reroute called GT

Command Function
ADD RRCDGT To add the reroute called GT
MOD RRCDGT To modify the reroute called GT
LST RRCDGT To query the reroute called GT
RMV RRCDGT To remove the reroute called GT

service.
Command
ADD RRCGGT

Parameter
Name

processing.
reference in the MTP link set, M3UA link set,
reroute OPC, reroute DPC, or reroute called GT
table.

process.
MSU message.

reroute process.
It is used to compare and match the translation type
in the MSU message.

reroute process.
in the MSU message.
AI Nature of address It maps the address nature indicator to be processed

indicator in the reroute process.
FAF Min. address It maps the information of the minimum address to

the minimum address in the MSU message. The
TAF Max. address It maps the information of the maximum address to

the maximum address in the MSU message. The


Name
It can be set to:
l VOID (Invalid)
Related Command
Table 18-6 Related commands for configuring the reroute calling GT

Command Function
ADD RRCGGT To add the reroute calling GT
MOD RRCGGT To modify the reroute calling GT
LST RRCGGT To query the reroute calling GT
RMV RRCGGT To remove the reroute calling GT

reroute service.
Command
ADD RROC

Parameter
Name
RR Reroute reference It maps the reference of the reroute in the

reroute processing.
the previous operation during the reroute
process. The object to be matched here is Next
reroute reference in the MTP link set, M3UA
link set, reroute OPC, reroute DPC, reroute
called GT, or reroute calling GT table.
MAPC Operation code It maps the operation code to be processed in

the reroute process.
It is used to compare and match the version
number and operation code information of the
MAP message in the MSU message.
When Operation code is set to UDF247(247-
SERVICE_REROUTE), the messages that
can be processed include the following:
l UPDATE_LOCATION
l UPDATE_GPRS_LOCATION
l SEND_AUTHENTICATION_INFO
l RESTORE_DATA
l PURGE_MS
l READY_FOR_SM
l SEND_ROUTING_INFO_FOR_SM
l MO_FORWARD_SM
The system performs message reroute
operation based on not only the operation code,
but also the user number (IMSI/MSISDN).
TTYPE Type of next It specifies the type of the table corresponding

reroute table to the next reroute operation.
the condition set in Reroute policy.
VOID (Invalid)


Name
NRR Next reroute It specifies the reroute reference of the table

reference type corresponding to the next reroute
operation.
the condition set in Reroute policy. It is used
to match the corresponding data in the reroute
table configured in Type of next reroute
table.
Related Command
Table 18-7 Related commands for configuring the reroute operation code
Command Function
ADD RROC To add the reroute operation code
MOD RROC To modify the reroute operation code
LST RROC To query the reroute operation code
RMV RROC To remove the reroute operation code
NOTE
l The referenced index from the reroute rule table must be an actual index.
l The parameter Reroute reference is directly used when referencing the indexes from other tables.

Command
ADD RRRULE
Parameter

reroute process.
When the match condition is met, it is used to
replace the network type information in the
MSU message.

LSM Load-share select It specifies how to implement load sharing

mask among multiple signaling points.
It is optional. Its value is of the numeral type
and comprises eight binary bits. Its value range
is 0-15. It is set to 15 by default.
The configuration principle of this parameter
is as follows:
l When there is only one signaling point, the
load-sharing selection mask code is 0.
l When there are two signaling points, set any
bit to 1.
l When there are three or four signaling
points, set any two bits to 1.
l When there are 5-8 signaling points, set any
three bits to 1.
l When there are more than eight signaling
points, set all four bits to 1.
DST0-DST15 Destinations 0-15 It specifies the DSP to be performed load

sharing.
default.
PRT0-PRT15 Priorities 0-15 It specifies the priority of a DSP.

default.

RSWT Reroute rule switch It maps the further processing rule after the
successful reroute processing. It is optional
and its value is of the enumeration type. It can
be set to one or both of the following values:
l G1 (Reroute DPC fail discard)
l G2 (Modify DPC switch)
Based on different situations, the processing
principles are as follows:
l G1 enabled and G2 disabled: The system
l G1 enabled and G2 enabled: The system
l G1 disabled and G2 disabled: The system
l G1 disabled and G2 enabled: The system
NOTE
l Modifying the route: Based on the destination of
a rerouted message, the system reselects the
route for the message and sends the message to
the destination.
l Modifying the DPC: The system modifies the
DPC in the message to that of the reroute
destination.

RRDIRECT Reroute direction It determines the module to which the re-

routed message is sent. It is optional and its
value is of the enumeration type. It can be set
to:
l BIT0 (Reroute to M3UA/MTP): The
message is sent to the platform module for
the M3UA/MTP reroute processing.
l BIT1 (Reroute to service): The message is
sent to the service processing module for the
M3UA/MTP reroute processing.
It is set to BIT0 by default.
NOTE
To perform the MAP processing, you must set
Reroute direction to BIT1.
Related Command
Table 18-8 Related commands for configuring the reroute rule

Command Function
ADD RRRULE To add the reroute rule
MOD RRRULE To modify the reroute rule
LST RRRULE To query the reroute rule
RMV RRRULE To remove the reroute rule

Command
ADD RRCDGTRNG

Parameter
FROMGT Begin GT code It indicates the start called number in the GT

reroute service.
TOGT End GT code It indicates the end called number in the GT

reroute service.
Related Command
Table 18-9 Related commands for configuring the reroute called GT range table
Command Function
ADD RRCDGTRNG To add the reroute called GT range table
MOD RRCDGTRNG To modify the reroute called GT range table
LST RRCDGTRNG To query the reroute called GT range table
RMV RRCDGTRNG To remove the reroute called GT range table

reroute service.
Command
ADD RRCGGTRNG
Parameter
Name
FROMGT Begin GT code It indicates the start calling number in the GT

number range to be processed in the message reroute
service.


Name
TOGT End GT code It indicates the end calling number in the GT number
range to be processed in the message reroute service.
Related Command
Table 18-10 Related commands for configuring the reroute calling GT range table
Command Function
ADD RRCGGTRNG To add the reroute calling GT range table
MOD RRCGGTRNG To modify the reroute calling GT range table
LST RRCGGTRNG To query the reroute calling GT range table
RMV RRCGGTRNG To remove the reroute calling GT range table

Command
ADD RRUSRNUM
Parameter
GTNUMIDX Reroute GT number It maps a record in the reroute calling GT range

range index table.
It is optional and its value is of the numeral
type. Its value range is 0-65535. It is set to
65535 by default, which indicates that the
system performs the reroute matching based on
only Reroute number instead of the
combination of Reroute number and Reroute
GT number range index.
USRNUM Reroute number It indicates the calling user number to be

processed in the re-routing service.
string type and ranges 0-9.

DPCIDX DPC index It maps a record in the MTP DSP table.

It is mandatory. Its value is of the numeral type
and ranges 0-2047.
Related Command
Table 18-11 Related commands for configuring reroute number table

Command Function
ADD RRUSRNUM To add the reroute number table
MOD RRUSRNUM To modify the reroute number table
LST RRUSRNUM To query the reroute number table
RMV RRUSRNUM To remove the reroute number table
18.6.10 Adding M3UA and MTP Link Set Data

This topic describes how to add the M3UA and MTP link set data.
The data of the link set for which the message duplication service is implemented must be added.
The added link set is used as the source link set of the message to be duplicated.
Command
ADD M3ASSOS and ADD N7LKS
Parameter
r ID r Name
SRVPRO Service It determines which service is enabled. You can enable any service
SWT process by selecting the related option. Here, you must select MCSWT
switch (Message copy switch).


r ID r Name
CPPOLIC Message It specifies the policy for duplicating messages. It is valid only
Y copy when Service process switch is set to Message copy switch. If
policy the message duplication switch is enabled, the system checks the
message duplication conditions and duplicates the matching
messages based on the configurations in the policy table. Then, the
system sends the duplicated messages to the specified signaling
points. After that, the system forwards the original messages based
on the original routing information contained in the messages.
It is optional. Its value is of the enumeration type. It can be set to:
l ANP (All DPC not processed): When it is selected, the system
does not apply message duplication but directly forwards the
MSU message based on the original flow, regardless of the MSU
message type.
l ISP (DPC in self PC processed): When it is selected, the system
determines whether the MSU message is locally terminated. If
the MSU message is locally terminated, the system obtains
Type of next message copy table and Next message copy
reference and then forwards the MSU message to the related
module for message rerouting processing. If the MSU message
is not locally terminated, the system processes the MSU
message based on the original flow without applying message
duplication.
l NISP (DPC not in self PC processed): When it is selected, the
system determines whether the MSU message is locally
terminated. If the MSU message is not locally terminated, the
system obtains Type of next message copy table and Next
message copy reference and then forwards the MSU message
to the related module for message rerouting processing. If the
MSU message is locally terminated, the system processes the
MSU message based on the original flow without applying
message duplication.
l AP (All DPC processed): When it is selected, the system
obtains Type of next message copy table and Next message
copy reference and then forwards the MSU message to the
related module for message rerouting processing, regardless of
the MSU message type.
It must be configured according to the actual conditions.


r ID r Name
NCPTYP Type of It specifies the next table whose messages are to be duplicated in
E next this link. If the message duplication data is not to be queried, set
message this parameter to Void. This parameter, together with Next
copy table message copy reference, determines the table item set used for
message duplication in the next step.
It can be set to:
l VOID (Void)
l ROT (Reroute OPC table)
l RDT (Reroute DPC table)
It must be configured according to the actual conditions.
NCPREF Next It specifies the reference of the message duplication in the next
message message copy table. This parameter, together with Type of next
copy message copy table, determines the table item set used for
reference message duplication in the next step. You do not need to configure
this parameter if the message duplication data is not to be queried.
Related Commands
Table 18-12 Related commands for configuring the M3UA and MTP link set data
Command Function
ADD N7LKS Add the MTP link set
MOD N7LKS Modify the MTP link set
LST N7LKS Query the MTP link set
RMV N7LKS Remove the MTP link set
ADD M3ASSOS Add the M3UA association set
MOD M3ASSOS Modify the M3UA association set
LST M3ASSOS Query the M3UA association set
RMV M3ASSOS Remove the M3UA association set


This topic provides the detailed example to demonstrate how to configure the message
duplication service.
18.7.1 Example
This topic provides an example to describe how to configure the message duplication service.
18.7.1 Example
This topic provides an example to describe how to configure the message duplication service.

Table 18-13 lists the data to be collected for configuring the message duplication service.
Table 18-13 Data collected for configuring the message duplication service
Service process Message copy Type of next Next message copy
switch policy message copy table reference
Message copy All DPC processed Message copy called 11

switch GT table
NOTE
The configuration of the message duplication service is similar to that of the message rerouting service.
Therefore, this topic specifies only different parameters involved in the message duplication service. For
detailed configuration about other parameters, see 16 Configuring MRS Service Data.
Procedure
Step 1 Modify link set information.
Based on the preceding data collection, the following provides an example of service data
configuration.
To modify link set information, where Service process switch is Message copy switch,
Message copy policy is All DPC processed, and Type of next message copy table is Message
copy called GT table, run the following command:
MOD M3ASSOS: IDX=0, NI=IM, SRVPROSWT=RIAM-1, CPPOLICY=AP, NCPTYPE=CDGT, NCPREF=11;
----End


SG7000 Feature Description (V200R005C02 - 02)

Uploaded by

Copyright:

Available Formats

You might also like

SG7000 Feature Description (V200R005C02 - 02)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SG7000 Feature Description (V200R005C02 - 02)

Uploaded by

Copyright:

Available Formats

U-SYS SG7000 Signaling Gateway

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

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

About This Document

Product Name Version

U-SYS SG7000 V200R005C02

l Network planning engineers

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

7 Configuring Protocol Describes how to configure the protocol translation service

8 Configuring Firewall Describes how to configure the firewall service data.

9 Configuring MC Service Describes how to configure the MC service data.

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

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

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

Indicates a potentially hazardous situation that, if not

NOTE Provides additional information to emphasize or

Times New Roman Normal paragraphs are in Times New Roman.

Italic Book titles are in italics.

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italic.

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

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

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

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

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

Updates in Issue 02 (2009-12-14)

Updates in Issue 01 (2009-09-27)

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

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

2 Configuring Calling SMR Service Data................................................................................2-1

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

2.3.5 General Steps..........................................................................................................................................2-6

3 Configuring IMEI Catch Service Data...................................................................................3-1

4 Configuring MNP Service Data..............................................................................................4-1

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

4.4.1 Configuring MNP Software Parameters..............................................................................................4-26

5 Configuring CRBT Service Data.............................................................................................5-1

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

5.6 Configuration Examples................................................................................................................................5-31

6 Configuring B&W Lists and Number Change Service Data.............................................6-1

7 Configuring Protocol Translation Service Data...................................................................7-1

8 Configuring Firewall Service Data.........................................................................................8-1

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

8.1.1 Service Functions...................................................................................................................................8-2

9 Configuring MC Service Data.................................................................................................9-1

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

9.2.2 Service Implementation..........................................................................................................................9-3

10 Configuring FNR Service Data - General..........................................................................10-1

11 Configuring SMI Service Data............................................................................................11-1

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

11.5 Configuration Examples..............................................................................................................................11-6

12 Configuring CDMA and GSM MNP Service Data.........................................................12-1

13 Configuring IPR Service Data.............................................................................................13-1

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

13.2.5 Service Interaction............................................................................................................................13-10

14 Configuring IRVAS Service Data.......................................................................................14-1