60578261 3 MSOFTX3000 Operation Manual Data Configuration

Chapter 1 Overview of Data Configuration ...................................................

1-1

1.1 Introduction to the Manual ...................................................................... 1.2 Introduction to the Chapter ..................................................................... 1.3 Situations Requiring Data Configuration ................................................ 1.4 Data Configuration Procedures .............................................................. 1.4.1 Global Configuration Procedures ................................................... 1.4.2 Configuring Internal Data ............................................................... 1.4.3 Configuring Interface Data ............................................................. 1.4.4 Configuring Service Data ............................................................... 1.5 Overview of MML Application ................................................................. 1.5.1 Using MML Command ................................................................... 1.5.2 Using Data Script ........................................................................... 1.6 Precautions ............................................................................................ 1.6.1 Before Data Configuration ............................................................. 1.6.2 During Data Configuration ............................................................. 1.7 Data Preparation .................................................................................... 1.7.1 Prerequisites for Data Preparation ................................................. 1.7.2 Data Preparation Operations .........................................................

1-1 1-1 1-1 1-2 1-2 1-2 1-3 1-3 1-4 1-4 1-4 1-5 1-5 1-5 1-6 1-6 1-6

Chapter 2 Configuring Equipment Data ........................................................

2-1

2.1 Introduction to the Chapter ..................................................................... 2.2 Concepts Related to Equipment Data .................................................... 2.2.1 Equipment Numbering ................................................................... 2.2.2 Clock Plan ...................................................................................... 2.3 Collecting Equipment Data ..................................................................... 2.4 Configuring Equipment Data .................................................................. 2.4.1 Before Configuration ...................................................................... 2.4.2 Adding Shelf ................................................................................... 2.4.3 Adding Frame ................................................................................ 2.4.4 Adding Board ................................................................................. 2.4.5 Adding CDB Function .................................................................... 2.4.6 Adding FE Port Information of WIFM ............................................. 2.5 Locking Clock Reference Source through E1 ........................................ 2.5.1 Before Configuration ...................................................................... 2.5.2 Adding WEPI and WCKI ................................................................ 2.5.3 Setting Clock Reference Source .................................................... 2.5.4 Adding E1 Information ................................................................... 2.5.5 Adding Clock Reference from WEPI .............................................. 2.5.6 Checking Clock Reference Source ................................................ 2.6 Locking Clock Reference Source through BITS .....................................

2-1 2-1 2-1 2-4 2-4 2-5 2-5 2-6 2-8 2-9 2-12 2-13 2-14 2-14 2-15 2-15 2-16 2-17 2-18 2-19

2.6.1 Before Configuration ...................................................................... 2.6.2 Adding WEPI and WCKI ................................................................ 2.6.3 Setting Clock Reference Source .................................................... 2.6.4 Adding E1 Information ................................................................... 2.6.5 Checking Clock Reference Source ................................................ 2.6.6 Loading Equipment Data ............................................................... 2.7 Configuration Example ........................................................................... 2.7.1 Example Description ...................................................................... 2.7.2 Configuration Description...............................................................

2-19 2-19 2-20 2-20 2-21 2-21 2-21 2-21 2-24

Chapter 3 Configuring Office Data .................................................................

3-1

3.1 Introduction to the Chapter ..................................................................... 3.2 Concepts Related to Office Data ............................................................ 3.2.1 Local Office Information ................................................................. 3.2.2 MSC Number and VLR Number .................................................... 3.2.3 Multiple Signaling Points ................................................................ 3.2.4 Mutual-Assistant Nodes ................................................................. 3.3 Collecting Office Data ............................................................................. 3.4 Configuring Office Data .......................................................................... 3.4.1 Before Configuration ...................................................................... 3.4.2 Setting Local Office Information ..................................................... 3.4.3 Setting Local Mobile Network Information ..................................... 3.4.4 Adding Local VLR Information ....................................................... 3.4.5 Adding MAP Information ................................................................ 3.4.6 Adding Local SCCP Subsystem .................................................... 3.4.7 Adding Local SCCP GT ................................................................. 3.5 Setting MSRN/HON Allocation Mode ..................................................... 3.5.1 Introduction to MSRN/HON Allocation ........................................... 3.5.2 Adding MSRN/HON Prefix ............................................................. 3.5.3 Adding MSRN/HON Suffix ............................................................. 3.5.4 Adding Corresponding Relationship Between LAI and MSRN ...... 3.5.5 Adding Corresponding Relationship Between MSC and MSRN .... 3.6 Configuration Example ........................................................................... 3.6.1 Example Description ...................................................................... 3.6.2 Configuration Description...............................................................

3-1 3-1 3-1 3-1 3-2 3-2 3-2 3-4 3-4 3-5 3-7 3-9 3-11 3-14 3-15 3-17 3-17 3-18 3-19 3-20 3-21 3-22 3-22 3-24

Chapter 4 Configuring Data for Interworking with MGW .............................

4-1

4.1 Introduction to the Chapter ..................................................................... 4.2 Concepts Related to Data Configuration for Interworking with MGW .... 4.2.1 Relationship Between MSC Server and MGW .............................. 4.2.2 Networking Between MSOFTX3000 and MGW .............................

4-1 4-1 4-1 4-1

4.2.3 Parameter Relationship ................................................................. 4.2.4 General Configuration Procedures ................................................ 4.3 Collecting Data for Interworking with MGW ............................................ 4.4 Configuring Data for Interworking with MGW ......................................... 4.4.1 Adding MGW .................................................................................. 4.4.2 Adding SCTP Link to MGW ........................................................... 4.4.3 Setting SCTP Checksum Algorithm (Optional) .............................. 4.4.4 Setting Tone Playing Capability of MGW (Optional) ...................... 4.5 Configuration Example ........................................................................... 4.5.1 Example Description ...................................................................... 4.5.2 Configuration Description...............................................................

4-2 4-3 4-3 4-4 4-4 4-8 4-10 4-11 4-13 4-13 4-14

Chapter 5 Configuring Data for Interworking with RNC ...............................

5-1

5.1 Introduction to the Chapter ..................................................................... 5.2 Related Concepts ................................................................................... 5.2.1 Basic Concepts of M3UA ............................................................... 5.2.2 Networking between MSOFTX3000 and RNC ............................... 5.2.3 Parameter Relationship ................................................................. 5.2.4 General Configuration Procedures ................................................ 5.3 Collecting Data for Interworking with RNC ............................................. 5.4 Configuring Data for Interworking with RNC .......................................... 5.4.1 Negotiating and Preparing Data ..................................................... 5.4.2 Adding M3UA Local Entity ............................................................. 5.4.3 Adding M3UA Destination Entity .................................................... 5.4.4 Adding M3UA Link Set ................................................................... 5.4.5 Adding M3UA Route ...................................................................... 5.4.6 Adding M3UA Link ......................................................................... 5.4.7 Adding SCCP Remote Signaling Point .......................................... 5.4.8 Adding SCCP Subsystem .............................................................. 5.4.9 Adding RNC Office Direction ......................................................... 5.4.10 Adding RNC Global Indicator ....................................................... 5.4.11 Adding 3G Service Area .............................................................. 5.4.12 Adding Access Media Gateway ................................................... 5.5 Configuration Example ........................................................................... 5.5.1 Example Description ...................................................................... 5.5.2 Configuration Description...............................................................

5-1 5-1 5-1 5-1 5-2 5-3 5-4 5-5 5-5 5-6 5-7 5-9 5-10 5-11 5-14 5-16 5-18 5-19 5-20 5-22 5-23 5-23 5-24

Chapter 6 Configuring Data for Interworking with BSC ...............................

6-1

6.1 Introduction to the Chapter ..................................................................... 6.2 Related Concepts ................................................................................... 6.2.1 Networking Between MSOFTX3000 and BSC ...............................

6-1 6-1 6-1

6.2.2 MTP Link Configuration ................................................................. 6.2.3 Trunk Circuit and TID Configuration .............................................. 6.2.4 Number Analysis Process .............................................................. 6.2.5 Parameter Relationship ................................................................. 6.2.6 General Configuration Procedures ................................................ 6.3 Collecting Data for Interworking with BSC ............................................. 6.4 Configuring Data for Interworking with BSC ........................................... 6.4.1 Negotiating and Preparing Data ..................................................... 6.4.2 Adding MTP Destination Signaling Point ....................................... 6.4.3 Adding MTP Link Set ..................................................................... 6.4.4 Adding MTP Route ......................................................................... 6.4.5 Adding MTP Link ............................................................................ 6.4.6 Adding SCCP Remote Signaling Point .......................................... 6.4.7 Adding SCCP Subsystem .............................................................. 6.4.8 Adding Office Direction to BSC ...................................................... 6.4.9 Adding BSC Global Indicator ......................................................... 6.4.10 Adding LAI or CGI ........................................................................ 6.4.11 Adding Access Media Gateway ................................................... 6.4.12 Adding A-interface Circuit Pool .................................................... 6.4.13 Adding A-interface Trunk Group .................................................. 6.4.14 Adding A-interface Trunk Circuit .................................................. 6.5 Configuration Example ........................................................................... 6.5.1 Example Description ...................................................................... 6.5.2 Configuration Description...............................................................

6-2 6-4 6-5 6-6 6-7 6-8 6-9 6-9 6-10 6-11 6-13 6-14 6-17 6-19 6-20 6-22 6-23 6-25 6-26 6-26 6-28 6-30 6-30 6-31

Chapter 7 Configuring Data for Interworking with HLR ...............................

7-1

7.1 Introduction to the Chapter ..................................................................... 7.2 Related Concepts ................................................................................... 7.2.1 HLR ................................................................................................ 7.2.2 Principles for Configuring GT Data ................................................ 7.2.3 Principles for Naming Signaling Links ............................................ 7.2.4 Principles for Numbering MTP Data .............................................. 7.2.5 Networking Between MSOFTX3000 and HLR ............................... 7.2.6 Parameter Relationship ................................................................. 7.2.7 General Configuration Procedures ................................................ 7.3 Collecting Data for Interworking with HLR .............................................. 7.4 Configuring Data for Interworking with HLR ........................................... 7.4.1 Adding MTP Layer Data ................................................................. 7.4.2 Adding SCCP DSP ........................................................................ 7.4.3 Adding SCCP Subsystem .............................................................. 7.4.4 Adding SCCP GT ...........................................................................

7-1 7-1 7-1 7-9 7-10 7-10 7-10 7-11 7-11 7-12 7-12 7-12 7-13 7-14 7-15

7.5 Configuration Example ........................................................................... 7.5.1 Example Description ...................................................................... 7.5.2 Configuration Description...............................................................

7-18 7-18 7-19

Chapter 8 Configuring Data for Interworking with MSC (MTP) ...................

8-1

8.1 Introduction to the Chapter ..................................................................... 8.2 Related Concepts ................................................................................... 8.2.1 Networking Between MSOFTX3000 and MSC Server .................. 8.2.2 Parameter Relationship ................................................................. 8.2.3 General Configuration Procedures ................................................ 8.3 Collecting Data for Interworking with Other MSC Server ....................... 8.4 Configuring Data for Interworking with Other MSC Server..................... 8.4.1 Negotiating and Preparing Data ..................................................... 8.4.2 Configuring MTP Data ................................................................... 8.4.3 Configuring SCCP Data ................................................................. 8.4.4 Adding Routing Information ........................................................... 8.4.5 Adding SS7 Trunk Circuit............................................................... 8.5 Configuration Example ........................................................................... 8.5.1 Example Description ...................................................................... 8.5.2 Configuration Description...............................................................

8-1 8-1 8-1 8-2 8-3 8-4 8-5 8-5 8-5 8-5 8-6 8-6 8-6 8-6 8-8

Chapter 9 Configuring Data for Interworking with MSC (ISUP/M3UA) .......

9-1

9.1 Related Concepts ................................................................................... 9.1.1 Networking Between MSOFTX3000 and MSC .............................. 9.1.2 Parameter Relationship ................................................................. 9.1.3 Collecting Data ............................................................................... 9.2 General Configuration Procedures ......................................................... 9.3 Procedures ............................................................................................. 9.3.1 Negotiating and Preparing Data ..................................................... 9.3.2 Adding M3UA Local Entity ............................................................. 9.3.3 Adding M3UA Destination Entity .................................................... 9.3.4 Adding M3UA Link Set ................................................................... 9.3.5 Adding M3UA Route ...................................................................... 9.3.6 Adding M3UA Link ......................................................................... 9.3.7 Adding Office Direction .................................................................. 9.3.8 Adding Sub-Route .......................................................................... 9.3.9 Adding Route ................................................................................. 9.3.10 Adding Route Analysis Data ........................................................ 9.3.11 Adding SS7 Trunk Group ............................................................. 9.3.12 Adding SS7 Trunk Circuit ............................................................. 9.4 Configuration Example ...........................................................................

9-1 9-1 9-1 9-3 9-4 9-5 9-5 9-6 9-7 9-9 9-10 9-11 9-14 9-15 9-17 9-18 9-20 9-22 9-24

9.4.1 Description of Example .................................................................. 9.4.2 Configuration Description...............................................................

9-24 9-25

Chapter 10 Configuring Data for Interworking with PSTN ...........................

10-1

10.1 Introduction to the Chapter ................................................................... 10.2 Concepts Related to Data Configuration for Interworking with PSTN ............................................................................................................ 10.2.1 MTP ............................................................................................. 10.2.2 Route and Trunk .......................................................................... 10.2.3 Networking Between MSOFTX3000 and PSTN .......................... 10.2.4 Parameter Relationship ............................................................... 10.2.5 General Configuration Principles ................................................. 10.3 Collecting Data for Interworking with PSTN ......................................... 10.4 Configuring Data for Interworking with PSTN....................................... 10.4.1 Negotiating and Preparing Data................................................... 10.4.2 Configuring MTP Data ................................................................. 10.4.3 Adding Office Direction ................................................................ 10.4.4 Adding Subroute .......................................................................... 10.4.5 Adding Route ............................................................................... 10.4.6 Adding Route Analysis Data ........................................................ 10.4.7 Adding SS7 Trunk Group ............................................................. 10.4.8 Adding SS7 Trunk Circuit ............................................................. 10.5 Configuration Example ......................................................................... 10.5.1 Example Description .................................................................... 10.5.2 Configuration Description .............................................................

10-1 10-1 10-1 10-1 10-4 10-5 10-7 10-7 10-8 10-8 10-9 10-9 10-10 10-11 10-12 10-14 10-22 10-24 10-24 10-26

Chapter 11 Configuring Data for Interworking with SMC ............................

11-1

11.1 Introduction to the Chapter ................................................................... 11.2 Related Concepts ................................................................................. 11.2.1 SMC ............................................................................................. 11.2.2 Networking Between MSOFTX3000 and SMC ............................ 11.2.3 Parameter Relationship ............................................................... 11.2.4 General Configuration Procedures .............................................. 11.3 Collecting Data for Interworking with SMC ........................................... 11.4 Configuring Data for Interworking with SMC ........................................ 11.4.1 Configuring MTP Data ................................................................. 11.4.2 Configuring SCCP Data ............................................................... 11.4.3 Modifying MAP Parameter Table ................................................. 11.5 Configuration Example ......................................................................... 11.5.1 Example Description .................................................................... 11.5.2 Configuration Description .............................................................

11-1 11-1 11-1 11-1 11-2 11-3 11-3 11-4 11-4 11-4 11-4 11-6 11-6 11-7

Chapter 12 Configuring Data for Interworking with SCP .............................

12-1

12.1 Introduction to the Chapter ................................................................... 12.2 Concepts Related to Data Configuration for Interworking with SCP .... 12.2.1 SCP .............................................................................................. 12.2.2 Networking Between MSOFTX3000 and SCP ............................. 12.2.3 Parameter Relationship ............................................................... 12.2.4 General Configuration Procedures .............................................. 12.3 Collecting Data for Interworking with SCP ........................................... 12.4 Configuring Data for Interworking with SCP ......................................... 12.4.1 Configuring MTP Data ................................................................. 12.4.2 Configuring SCCP Data ............................................................... 12.4.3 Configuring SSP Capability .......................................................... 12.4.4 Adding SCP Addressing Information ........................................... 12.4.5 Adding SCP Parameter Information............................................. 12.5 Configuration Example ......................................................................... 12.5.1 Example Description .................................................................... 12.5.2 Configuration Description .............................................................

12-1 12-1 12-1 12-1 12-2 12-2 12-3 12-4 12-4 12-4 12-4 12-5 12-6 12-7 12-7 12-9

Chapter 13 Configuring Data for Interworking with SGSN ..........................

13-1

13.1 Introduction to the Chapter ................................................................... 13.2 Related Concepts ................................................................................. 13.2.1 SGSN ........................................................................................... 13.2.2 Networking Between MSOFTX3000 and SGSN .......................... 13.2.3 Parameter Relationship ............................................................... 13.2.4 General Configuration Procedures .............................................. 13.3 Collecting Data for Interworking with SGSN ......................................... 13.4 Configuring Data for Interworking with SGSN ...................................... 13.4.1 Configuring MTP Data ................................................................. 13.4.2 Configuring SCCP Data ............................................................... 13.4.3 Configuring SGSN Number .......................................................... 13.4.4 Modifying Mobile Soft Parameter ................................................. 13.4.5 Modifying MAP Parameter Table ................................................. 13.5 Configuration Example ......................................................................... 13.5.1 Example Description .................................................................... 13.5.2 Configuration Description .............................................................

13-1 13-1 13-1 13-1 13-2 13-3 13-3 13-4 13-4 13-4 13-4 13-5 13-5 13-7 13-7 13-8

Chapter 14 Configuring Data for Interworking with GMLC ..........................

14-1

14.1 Introduction to the Chapter ................................................................... 14.2 Related Concepts ................................................................................. 14.2.1 GMLC ........................................................................................... 14.2.2 Networking Between MSOFTX3000 and GMLC ..........................

14-1 14-1 14-1 14-1

14.2.3 Parameter Relationship ............................................................... 14-2 14.2.4 General Configuration Procedures .............................................. 14-3 14.3 Collecting Data for Interworking with GMLC ........................................ 14-4 14.4 Configuring Data for Interworking with GMLC ...................................... 14-5 14.4.1 Configuring MTP Data ................................................................. 14-5 14.4.2 Configuring SCCP Data ............................................................... 14-5 14.4.3 Adding GMLC Number ................................................................. 14-5 14.4.4 Adding Client GMLC Information ................................................. 14-6 14.4.5 Adding Emergency Call LCS Client ............................................. 14-7 14.4.6 Adding Called Analysis Data (Optional) ....................................... 14-8 14.5 Configuration Example ......................................................................... 14-9 14.5.1 Example Description .................................................................... 14-9 14.5.2 Configuration Description ............................................................. 14-10 Chapter 15 Configuring Number Analysis Data ............................................

15-1

15.1 Related Concepts ................................................................................. 15.1.1 Call Source, Dialed Number Set, Route Selection Code ............. 15.1.2 Secondary Number Analysis ........................................................ 15.1.3 Number Conversion ..................................................................... 15.1.4 Service Check .............................................................................. 15.1.5 EARLY ACM ................................................................................ 15.1.6 Forwarded-to Number, Original Called Number, Connected Number ................................................................................................... 15.2 Procedures of Number Analysis Processing ........................................ 15.2.1 Incoming Number Pretreatment ................................................... 15.2.2 Number Analysis .......................................................................... 15.2.3 Outgoing Number Preprocessing ................................................. 15.3 Configuration Procedures..................................................................... 15.3.1 Overview of Configuration Procedures ........................................ 15.3.2 Procedures for Configuring Number Analysis Preset Data .......... 15.3.3 Procedures for Configuring Incoming Number Pretreatment Data ........................................................................................................ 15.3.4 Procedures for Configuring Number Analysis and Routing Data ........................................................................................................ 15.3.5 Procedures for Configuring Outgoing Number Preprocessing Data ........................................................................................................ 15.3.6 Other Number Data Configurations ............................................. 15.4 Configuring Preset Data Before Number Analysis ............................... 15.4.1 Adding Call Source ...................................................................... 15.4.2 Configuring Number Conversion Data ......................................... 15.5 Configuring Incoming Call Number Preprocessing Data ......................

15-1 15-1 15-3 15-3 15-3 15-3 15-4 15-4 15-5 15-6 15-6 15-6 15-6 15-6 15-7 15-8 15-10 15-12 15-13 15-13 15-15 15-22

15.5.1 Configuring Incoming Calling Number Associated Process Data ........................................................................................................ 15.5.2 Configuring Correlation Processing Data of Incoming Original Called Number ........................................................................................ 15.5.3 Configuring Incoming Number Pretreatment Data ....................... 15.6 Route Selection Data Configuration ..................................................... 15.6.1 Configuring Call Prefix ................................................................. 15.6.2 Configuring Enhanced Route Processing Data ........................... 15.6.3 Configuring Call Authority Original Called Correlation Processing Data ...................................................................................... 15.6.4 Configuring Call Authority Check Data ........................................ 15.6.5 Configuring Service Check Data .................................................. 15.6.6 Configuring Calling Number Analysis Data .................................. 15.6.7 Configuring Calling Feature Processing Data .............................. 15.6.8 Configuring Calling Feature Analysis Data .................................. 15.6.9 Configuring Dialed Number Special Processing Data ................. 15.6.10 Configuring Failure Processing Data ......................................... 15.7 Configuring Outgoing Number Preprocessing Data ............................. 15.7.1 Configuring Outgoing Calling Number Correlation Processing Data ........................................................................................................ 15.7.2 Configuring Outgoing Original Called Number Correlation Processing Data ...................................................................................... 15.7.3 Configuring Outgoing Number Preprocessing Data..................... 15.7.4 Configuring Trunk Group Bearer Data ......................................... 15.7.5 Configuring Trunk Group Bearer Index Data ............................... 15.8 Configuring Other Number Conversion Data ....................................... 15.8.1 Configuring CLIP Called Correlation Processing Data ................ 15.8.2 Configuring CLIP Processing Data .............................................. 15.8.3 Configuring Auxiliary Number Processing Data ........................... 15.8.4 Configuring MAP Interface Number Processing Data.................. 15.8.5 Configure Bill Processing Information .......................................... 15.8.6 Configuring Bill Control Data ........................................................ 15.9 Configuration Examples ....................................................................... 15.9.1 Planning of Number Analysis Data .............................................. 15.9.2 Planning of Call Prefix Data ......................................................... 15.9.3 Planning of Call Special Processing Data.................................... 15.9.4 Examples of Call Special Processing Data Configuration ...........

15-22 15-24 15-26 15-29 15-29 15-32 15-33 15-35 15-37 15-39 15-42 15-43 15-45 15-47 15-49 15-49 15-51 15-53 15-55 15-56 15-57 15-57 15-59 15-60 15-61 15-62 15-63 15-64 15-64 15-65 15-70 15-71

Chapter 16 Configuring Mobile Service Data ................................................

16-1

16.1 Introduction to the Chapter ................................................................... 16.2 Related Concepts ................................................................................. 16.3 Configuring Location Update Data .......................................................

16-1 16-1 16-4

16.3.1 General Configuration Procedures .............................................. 16.3.2 Setting LAI or CGI/SAI ................................................................. 16.3.3 Setting Global Title Table ............................................................. 16.3.4 Setting SCCP GT ......................................................................... 16.3.5 Setting Local Office SCCP Subsystem ........................................ 16.4 Configuring Enhanced Roaming Restriction Data ................................ 16.4.1 Configuration Description ............................................................. 16.4.2 Starting Enhanced Roaming Restriction Function ....................... 16.4.3 Configuring LAI Grouping Information ......................................... 16.4.4 Configuring LAI ............................................................................ 16.4.5 Configuring Roaming Restriction User Group.............................. 16.4.6 Configuring Roaming Subscriber Type ........................................ 16.5 Configuring Roaming Zone Code Service ............................................ 16.5.1 Service Description ...................................................................... 16.5.2 Configuration Description ............................................................. 16.5.3 Starting Zone Code Restriction Function ..................................... 16.5.4 Adding Zone Code ....................................................................... 16.5.5 Configuring the Relationship Between ZC and LAI ...................... 16.5.6 Configuring LAI ............................................................................ 16.6 Configuration Examples ....................................................................... 16.6.1 Configuring Enhanced Roaming Restriction to Number Segment by LAI ...................................................................................... 16.6.2 Configuring Zone Code Restriction .............................................. 16.6.3 Configuring Location Service Data .............................................. 16.6.4 Adding International Roaming Data of a Newly Subscribed Country or Region ...................................................................................

16-4 16-5 16-5 16-6 16-7 16-8 16-8 16-10 16-10 16-11 16-12 16-13 16-14 16-14 16-16 16-17 16-17 16-18 16-19 16-20

Chapter 17 Configuring IN Service Data ........................................................

17-1

17.1 Introduction to the Chapter ................................................................... 17.2 Related Concepts ................................................................................. 17.2.1 Modes for Triggering IN Services ................................................ 17.2.2 Triggering of Overlay Outgoing Intelligent Call ............................ 17.2.3 Triggering of IN Service by Number Segment ............................. 17.2.4 Triggering of Standard CAMEL 3 IN Service ............................... 17.3 Data Configuration Principles ............................................................... 17.4 Procedures for Configuring IN Service Data ........................................ 17.4.1 Configuring Basic Data of Local Office with SSP Function .......... 17.4.2 Configuring Data for Triggering N-CSI DP2 ................................. 17.4.3 Configuring Data for Triggering N-CSI DP12 ............................... 17.4.4 Configuring Data for Triggering N-CSI DP4 ................................. 17.4.5 Configuring Data for Triggering N-CSI DP3 ................................. 17.4.6 Configuring Data for Triggering DCSI ..........................................

17-1 17-1 17-1 17-1 17-1 17-5 17-6 17-7 17-7 17-7 17-7 17-7 17-7 17-8

16-20 16-20 16-21 16-21

17.4.7 Configuring Data in Overlay Mode ............................................... 17.4.8 Configuring Special Intelligent Resource Capability Data............ 17.4.9 Managing Special Number Information ........................................ 17.5 Configuration Examples ....................................................................... 17.5.1 IN Services Triggered by N-CSI DP3 ........................................... 17.5.2 IN Services Triggered by N-CSI DP4 ........................................... 17.5.3 Overlay Outgoing .........................................................................

17-9 17-10 17-10 17-10 17-10 17-11 17-11

Chapter 18 Debugging ....................................................................................

18-1

18.1 Introduction to the Chapter ................................................................... 18.2 Debugging of SCTP ............................................................................. 18.2.1 Background Information ............................................................... 18.2.2 Debugging Methods ..................................................................... 18.2.3 FAQ .............................................................................................. 18.3 Debugging of M3UA ............................................................................. 18.3.1 Background Information ............................................................... 18.3.2 Debugging Methods ..................................................................... 18.3.3 FAQ .............................................................................................. 18.4 Debugging of Mc (H.248) ..................................................................... 18.4.1 Background Information ............................................................... 18.4.2 Debugging Methods ..................................................................... 18.4.3 FAQ ..............................................................................................

18-1 18-1 18-1 18-1 18-2 18-3 18-3 18-3 18-3 18-8 18-8 18-8 18-9

Appendix A An Example on Global Data Configuration ..............................

A-1

A.1 Introduction to the Appendix .................................................................. A.2 Configuration Example........................................................................... A.2.1 Example Description ...................................................................... A.2.2 Data Collection .............................................................................. A.2.3 Data Configuration .........................................................................

A-1 A-1 A-1 A-3 A-11

Index .................................................................................................................

HUAWEI

HUAWEI MSOFTX3000 Mobile SoftSwitch Center Operation Manual - Data Configuration V100R002

HUAWEI MSOFTX3000 Mobile SoftSwitch Center Operation Manual Volume

Data Configuration

Manual Version

T2-031622-20041115-C-2.00

Product Version

V100R002

BOM

31161422

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. Please feel free to contact our local office or company headquarters.

Huawei Technologies Co., Ltd. Address: Administration Building, Huawei Technologies Co., Ltd., Bantian, Longgang District, Shenzhen, P. R. China Postal Code: 518129 Website: http://www.huawei.com Email: [email protected]

Copyright © 2004 Huawei Technologies Co., Ltd.

All Rights Reserved No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks

, HUAWEI, C&C08, EAST8000, HONET,

, ViewPoint, INtess, ETS, DMC,

TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium, M900/M1800, TELESIGHT, Quidview, Musa, Airbridge, Tellwin, Inmedia, VRP, DOPRA, iTELLIN, HUAWEI OptiX, C&C08 iNET, NETENGINE, OptiX, iSite, U-SYS, iMUSE, OpenEye, Lansway, SmartAX, infoX, TopEng are trademarks of Huawei Technologies Co., Ltd. All other trademarks mentioned in this manual are the property of their respective holders.

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

About This Manual Release Notes This manual applies to HUAWEI MSOFTX3000 Mobile SoftSwitch Center V100R002 (hereinafter referred to as MSOFTX3000).

Organization The manual introduces the basic data configuration procedure of before system operation. There are seventeen chapters and an appendix in the manual. Chapter 1 Overview of Data Configuration profiles an overall description of the configuration procedures, precautions and data preparation to be done before data configuration. Chapter 2 Configuring Equipment Data focuses on the configuration procedures and background concepts to be grasped before configuring the equipment data of MSOFTX3000. This chapter covers locking the clock reference source through E1 and BITS. Chapter 3 Configuring Office Data elaborates the configuration procedures and background concepts to be grasped before configuring the office data of MSOFTX3000. This chapter describes the configuration of basic office information and setting of MSRN/HON allocation mode. Chapter 4 Configuring Data for Interworking with MGW presents the configuration procedures, related concepts and configuration examples for configuring data to interwork with MGW. Chapter 5 Configuring Data for Interworking with RNC focuses on the configuration procedures, related concepts and configuration examples for configuring data to interwork with RNC. Chapter 6 Configuring Data for Interworking with BSC describes the configuration procedures, related concepts and configuration examples for configuring data to interwork with BSC.

Chapter 7 Configuring Data for Interworking with HLR elaborates the configuration procedures, related concepts and configuration examples for configuring data to interwork with HLR. Chapter 8 Configuring Data for Interworking with MSC (MTP) describes the configuration procedures, related concepts and configuration examples for configuring data to interwork with MSC Server. Chapter 9 Configuring Data for Interworking with MSC (ISUP-M3UA) details the configuration procedures, related concepts and configuration examples for configuring data to interwork with MSC (ISUP-M3UA). Chapter 10 Configuring Data for Interworking with PSTN concentrates on the configuration procedures, related concepts and configuration examples for configuring data to interwork with PSTN. Chapter 11 Configuring Data for Interworking with SMC describes the configuration procedures, related concepts and configuration examples for configuring data to interwork with SMC. Chapter 12 Configuring Data for Interworking with SCP features the configuration procedures, related concepts and configuration examples for configuring data to interwork with SCP. Chapter 13 Configuring Data for Interworking with SGSN is about the configuration procedures, related concepts and configuration examples for configuring data to interwork with SGSN. Chapter 14 Configuring Data for Interworking with GMLC introduces the configuration procedures, related concepts and configuration examples for configuring data to interwork with GMLC. Chapter 15 Configuring Number Analysis Data focuses on the configuration procedures and background concepts to be grasped before configuring the number analysis data of MSOFTX3000. This chapter describes the configuration of basic service prefix, toll area code, and country/region code. It also tells you on how to convert intra-office number and trunk number. Chapter 16 Configuring Mobile Service Data elaborates the configuration procedures and background concepts to be grasped before configuring the mobile service data of MSOFTX3000. Chapter 17 Configuring IN Service Data is about the basic concepts and data configuration procedures of Intelligent Network (IN) services. Chapter 18 Debugging features the debugging methods for SCTP, M3UA and Mc (H.248) messages.

Appendix A An Example on Global Data Configuration gives an example for the deployment of a new office site. This chapter describes the configuration idea of different entities

Intended Audience The manual is intended for the following readers: z

Mobile network engineering specialists

z

Operation and Maintenance engineers

z

Mobile network system engineers

Conventions The manual uses the following conventions:

I. General conventions Convention

Description

Arial

Normal paragraphs are in Arial.

Arial Narrow

Warnings, Cautions, Notes and Tips are in Arial Narrow.

Boldface

Headings are in Boldface.

Courier New

Terminal Display is in Courier New.

II. GUI conventions Convention

Description

<>

Button names are inside angle brackets. For example, click the button.

[]

Window names, menu items, data table and field names are inside square brackets. For example, pop up the [New User] window.

/

Multi-level menus are separated by forward slashes. For example, [File/Create/Folder].

III. Keyboard operation Format

Description Press the key with the key name inside angle brackets. For example, , , , or .

Format

Description

Press the keys concurrently. For example, means the three keys should be pressed concurrently.

Press the keys in turn. For example, means the two keys should be pressed in turn.

IV. Mouse operation Action

Description

Click

Press the left button or right button quickly (left button by default).

Double Click

Press the left button twice continuously and quickly.

Drag

Press and hold the left button and drag it to a certain position.

V. Symbols Eye-catching symbols are also used in the manual to highlight the points worthy of special attention during the operation. They are defined as follows:

Caution Means reader be extremely careful during the operation. Note: Means a complementary description.

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Table of Contents

Table of Contents Chapter 1 Overview of Data Configuration................................................................................. 1-1 1.1 Introduction to the Manual ................................................................................................. 1-1 1.2 Introduction to the Chapter ................................................................................................ 1-1 1.3 Situations Requiring Data Configuration ........................................................................... 1-1 1.4 Data Configuration Procedures ......................................................................................... 1-2 1.4.1 Global Configuration Procedures ............................................................................ 1-2 1.4.2 Configuring Internal Data ........................................................................................ 1-2 1.4.3 Configuring Interface Data ...................................................................................... 1-3 1.4.4 Configuring Service Data ........................................................................................ 1-3 1.5 Overview of MML Application ............................................................................................ 1-4 1.5.1 Using MML Command ............................................................................................ 1-4 1.5.2 Using Data Script .................................................................................................... 1-4 1.6 Precautions ........................................................................................................................ 1-5 1.6.1 Before Data Configuration....................................................................................... 1-5 1.6.2 During Data Configuration....................................................................................... 1-5 1.7 Data Preparation................................................................................................................ 1-6 1.7.1 Prerequisites for Data Preparation.......................................................................... 1-6 1.7.2 Data Preparation Operations .................................................................................. 1-6 Chapter 2 Configuring Equipment Data ...................................................................................... 2-1 2.1 Introduction to the Chapter ................................................................................................ 2-1 2.2 Concepts Related to Equipment Data ............................................................................... 2-1 2.2.1 Equipment Numbering ............................................................................................ 2-1 2.2.2 Clock Plan ............................................................................................................... 2-4 2.3 Collecting Equipment Data ................................................................................................ 2-4 2.4 Configuring Equipment Data.............................................................................................. 2-5 2.4.1 Before Configuration ............................................................................................... 2-5 2.4.2 Adding Shelf ............................................................................................................ 2-6 2.4.3 Adding Frame.......................................................................................................... 2-8 2.4.4 Adding Board........................................................................................................... 2-9 2.4.5 Adding CDB Function............................................................................................ 2-12 2.4.6 Adding FE Port Information of WIFM .................................................................... 2-13 2.5 Locking Clock Reference Source through E1.................................................................. 2-14 2.5.1 Before Configuration ............................................................................................. 2-14 2.5.2 Adding WEPI and WCKI ....................................................................................... 2-15 2.5.3 Setting Clock Reference Source ........................................................................... 2-15 2.5.4 Adding E1 Information........................................................................................... 2-16 2.5.5 Adding Clock Reference from WEPI ..................................................................... 2-17

i


Table of Contents

2.5.6 Checking Clock Reference Source ....................................................................... 2-18 2.6 Locking Clock Reference Source through BITS .............................................................. 2-19 2.6.1 Before Configuration ............................................................................................. 2-19 2.6.2 Adding WEPI and WCKI ....................................................................................... 2-19 2.6.3 Setting Clock Reference Source ........................................................................... 2-20 2.6.4 Adding E1 Information........................................................................................... 2-20 2.6.5 Checking Clock Reference Source ....................................................................... 2-21 2.6.6 Loading Equipment Data....................................................................................... 2-21 2.7 Configuration Example .................................................................................................... 2-21 2.7.1 Example Description ............................................................................................. 2-21 2.7.2 Configuration Description...................................................................................... 2-24 Chapter 3 Configuring Office Data .............................................................................................. 3-1 3.1 Introduction to the Chapter ................................................................................................ 3-1 3.2 Concepts Related to Office Data ....................................................................................... 3-1 3.2.1 Local Office Information .......................................................................................... 3-1 3.2.2 MSC Number and VLR Number.............................................................................. 3-1 3.2.3 Multiple Signaling Points ......................................................................................... 3-2 3.2.4 Mutual-Assistant Nodes .......................................................................................... 3-2 3.3 Collecting Office Data ........................................................................................................ 3-2 3.4 Configuring Office Data ..................................................................................................... 3-4 3.4.1 Before Configuration ............................................................................................... 3-4 3.4.2 Setting Local Office Information .............................................................................. 3-5 3.4.3 Setting Local Mobile Network Information .............................................................. 3-7 3.4.4 Adding Local VLR Information ................................................................................ 3-9 3.4.5 Adding MAP Information ....................................................................................... 3-11 3.4.6 Adding Local SCCP Subsystem............................................................................ 3-14 3.4.7 Adding Local SCCP GT ........................................................................................ 3-15 3.5 Setting MSRN/HON Allocation Mode .............................................................................. 3-17 3.5.1 Introduction to MSRN/HON Allocation .................................................................. 3-17 3.5.2 Adding MSRN/HON Prefix .................................................................................... 3-18 3.5.3 Adding MSRN/HON Suffix .................................................................................... 3-19 3.5.4 Adding Corresponding Relationship Between LAI and MSRN ............................. 3-20 3.5.5 Adding Corresponding Relationship Between MSC and MSRN........................... 3-21 3.6 Configuration Example .................................................................................................... 3-22 3.6.1 Example Description ............................................................................................. 3-22 3.6.2 Configuration Description...................................................................................... 3-24 Chapter 4 Configuring Data for Interworking with MGW........................................................... 4-1 4.1 Introduction to the Chapter ................................................................................................ 4-1 4.2 Concepts Related to Data Configuration for Interworking with MGW ............................... 4-1 4.2.1 Relationship Between MSC Server and MGW ....................................................... 4-1 4.2.2 Networking Between MSOFTX3000 and MGW...................................................... 4-1 4.2.3 Parameter Relationship........................................................................................... 4-2 ii


Table of Contents

4.2.4 General Configuration Procedures.......................................................................... 4-3 4.3 Collecting Data for Interworking with MGW....................................................................... 4-3 4.4 Configuring Data for Interworking with MGW .................................................................... 4-4 4.4.1 Adding MGW ........................................................................................................... 4-4 4.4.2 Adding SCTP Link to MGW..................................................................................... 4-8 4.4.3 Setting SCTP Checksum Algorithm (Optional) ..................................................... 4-10 4.4.4 Setting Tone Playing Capability of MGW (Optional) ............................................. 4-11 4.5 Configuration Example .................................................................................................... 4-13 4.5.1 Example Description ............................................................................................. 4-13 4.5.2 Configuration Description...................................................................................... 4-14 Chapter 5 Configuring Data for Interworking with RNC ............................................................ 5-1 5.1 Introduction to the Chapter ................................................................................................ 5-1 5.2 Concepts Related to Data Configuration for Interworking with RNC................................. 5-1 5.2.1 Basic Concepts of M3UA ........................................................................................ 5-1 5.2.2 Networking between MSOFTX3000 and RNC........................................................ 5-1 5.2.3 Parameter Relationship........................................................................................... 5-2 5.2.4 General Configuration Procedures.......................................................................... 5-3 5.3 Collecting Data for Interworking with RNC ........................................................................ 5-4 5.4 Configuring Data for Interworking with RNC...................................................................... 5-5 5.4.1 Negotiating and Preparing Data.............................................................................. 5-5 5.4.2 Adding M3UA Local Entity ...................................................................................... 5-6 5.4.3 Adding M3UA Destination Entity ............................................................................. 5-7 5.4.4 Adding M3UA Link Set ............................................................................................ 5-9 5.4.5 Adding M3UA Route ............................................................................................. 5-10 5.4.6 Adding M3UA Link ................................................................................................ 5-11 5.4.7 Adding SCCP Remote Signaling Point ................................................................. 5-14 5.4.8 Adding SCCP Subsystem ..................................................................................... 5-16 5.4.9 Adding RNC Office Direction................................................................................. 5-18 5.4.10 Adding RNC Global Indicator .............................................................................. 5-19 5.4.11 Adding 3G Service Area...................................................................................... 5-20 5.4.12 Adding Access Media Gateway .......................................................................... 5-22 5.5 Configuration Example .................................................................................................... 5-23 5.5.1 Example Description ............................................................................................. 5-23 5.5.2 Configuration Description...................................................................................... 5-24 Chapter 6 Configuring Data for Interworking with BSC ............................................................ 6-1 6.1 Introduction to the Chapter ................................................................................................ 6-1 6.2 Concepts Related to Data Configuration for Interworking with BSC ................................. 6-1 6.2.1 Networking Between MSOFTX3000 and BSC........................................................ 6-1 6.2.2 MTP Link Configuration........................................................................................... 6-2 6.2.3 Trunk Circuit and TID Configuration ....................................................................... 6-4 6.2.4 Number Analysis Process ....................................................................................... 6-5 6.2.5 Parameter Relationship........................................................................................... 6-6 iii


Table of Contents

6.2.6 General Configuration Procedures.......................................................................... 6-7 6.3 Collecting Data for Interworking with BSC......................................................................... 6-8 6.4 Configuring Data for Interworking with BSC ...................................................................... 6-9 6.4.1 Negotiating and Preparing Data.............................................................................. 6-9 6.4.2 Adding MTP Destination Signaling Point .............................................................. 6-10 6.4.3 Adding MTP Link Set ............................................................................................ 6-11 6.4.4 Adding MTP Route................................................................................................ 6-13 6.4.5 Adding MTP Link ................................................................................................... 6-14 6.4.6 Adding SCCP Remote Signaling Point ................................................................. 6-17 6.4.7 Adding SCCP Subsystem ..................................................................................... 6-19 6.4.8 Adding Office Direction to BSC ............................................................................. 6-20 6.4.9 Adding BSC Global Indicator ................................................................................ 6-22 6.4.10 Adding LAI or CGI ............................................................................................... 6-23 6.4.11 Adding Access Media Gateway .......................................................................... 6-25 6.4.12 Adding A-interface Circuit Pool ........................................................................... 6-26 6.4.13 Adding A-interface Trunk Group ......................................................................... 6-26 6.4.14 Adding A-interface Trunk Circuit ......................................................................... 6-28 6.5 Configuration Example .................................................................................................... 6-30 6.5.1 Example Description ............................................................................................. 6-30 6.5.2 Configuration Description...................................................................................... 6-31 Chapter 7 Configuring Data for Interworking with HLR ............................................................ 7-1 7.1 Introduction to the Chapter ................................................................................................ 7-1 7.2 Concepts Related to Data Configuration for Interworking with HLR ................................. 7-1 7.2.1 HLR ......................................................................................................................... 7-1 7.2.2 Principles for Configuring GT Data ......................................................................... 7-9 7.2.3 Principles for Naming Signaling Links................................................................... 7-10 7.2.4 Principles for Numbering MTP Data...................................................................... 7-10 7.2.5 Networking Between MSOFTX3000 and HLR...................................................... 7-10 7.2.6 Parameter Relationship......................................................................................... 7-11 7.2.7 General Configuration Procedures........................................................................ 7-12 7.3 Collecting Data for Interworking with HLR....................................................................... 7-12 7.4 Configuring Data for Interworking with HLR .................................................................... 7-13 7.4.1 Adding MTP Layer Data........................................................................................ 7-13 7.4.2 Adding SCCP DSP................................................................................................ 7-13 7.4.3 Adding SCCP Subsystem ..................................................................................... 7-14 7.4.4 Adding SCCP GT .................................................................................................. 7-16 7.5 Configuration Example .................................................................................................... 7-18 7.5.1 Example Description ............................................................................................. 7-18 7.5.2 Configuration Description...................................................................................... 7-20 Chapter 8 Configuring Data for Interworking with MSC (MTP)................................................. 8-1 8.1 Introduction to the Chapter ................................................................................................ 8-1 8.2 Concepts Related to Data Configuration for Interworking with Other MSC Server........... 8-1 iv


Table of Contents

8.2.1 Networking Between MSOFTX3000 and MSC Server ........................................... 8-1 8.2.2 Parameter Relationship........................................................................................... 8-2 8.2.3 General Configuration Procedures.......................................................................... 8-3 8.3 Collecting Data for Interworking with Other MSC Server .................................................. 8-4 8.4 Configuring Data for Interworking with Other MSC Server................................................ 8-5 8.4.1 Negotiating and Preparing Data.............................................................................. 8-5 8.4.2 Configuring MTP Data............................................................................................. 8-5 8.4.3 Configuring SCCP Data .......................................................................................... 8-5 8.4.4 Adding Routing Information..................................................................................... 8-6 8.4.5 Adding SS7 Trunk Circuit........................................................................................ 8-6 8.5 Configuration Example ...................................................................................................... 8-6 8.5.1 Example Description ............................................................................................... 8-6 8.5.2 Configuration Description........................................................................................ 8-8 Chapter 9 Configuring Data for Interworking with MSC (ISUP/M3UA)..................................... 9-1 9.1 Related Concepts .............................................................................................................. 9-1 9.1.1 Networking Between MSOFTX3000 and MSC ....................................................... 9-1 9.1.2 Parameter Relationship........................................................................................... 9-1 9.1.3 Collecting Data ........................................................................................................ 9-3 9.2 General Configuration Procedures .................................................................................... 9-4 9.3 Procedures......................................................................................................................... 9-5 9.3.1 Negotiating and Preparing Data.............................................................................. 9-5 9.3.2 Adding M3UA Local Entity ...................................................................................... 9-6 9.3.3 Adding M3UA Destination Entity ............................................................................. 9-7 9.3.4 Adding M3UA Link Set ............................................................................................ 9-9 9.3.5 Adding M3UA Route ............................................................................................. 9-10 9.3.6 Adding M3UA Link ................................................................................................ 9-11 9.3.7 Adding Office Direction ......................................................................................... 9-14 9.3.8 Adding Sub-Route................................................................................................. 9-15 9.3.9 Adding Route......................................................................................................... 9-17 9.3.10 Adding Route Analysis Data ............................................................................... 9-18 9.3.11 Adding SS7 Trunk Group .................................................................................... 9-20 9.3.12 Adding SS7 Trunk Circuit.................................................................................... 9-22 9.4 Configuration Example .................................................................................................... 9-24 9.4.1 Description of Example ......................................................................................... 9-24 9.4.2 Configuration Description...................................................................................... 9-25 Chapter 10 Configuring Data for Interworking with PSTN ...................................................... 10-1 10.1 Introduction to the Chapter ............................................................................................ 10-1 10.2 Concepts Related to Data Configuration for Interworking with PSTN ........................... 10-1 10.2.1 MTP..................................................................................................................... 10-1 10.2.2 Route and Trunk ................................................................................................. 10-1 10.2.3 Networking Between MSOFTX3000 and PSTN ................................................. 10-4 10.2.4 Parameter Relationship....................................................................................... 10-5 v


Table of Contents

10.2.5 General Configuration Principles ........................................................................ 10-7 10.3 Collecting Data for Interworking with PSTN .................................................................. 10-7 10.4 Configuring Data for Interworking with PSTN................................................................ 10-8 10.4.1 Negotiating and Preparing Data.......................................................................... 10-8 10.4.2 Configuring MTP Data......................................................................................... 10-9 10.4.3 Adding Office Direction ....................................................................................... 10-9 10.4.4 Adding Sub-Route............................................................................................. 10-10 10.4.5 Adding Route..................................................................................................... 10-11 10.4.6 Adding Route Analysis Data ............................................................................. 10-12 10.4.7 Adding SS7 Trunk Group .................................................................................. 10-14 10.4.8 Adding SS7 Trunk Circuit.................................................................................. 10-15 10.5 Configuration Example ................................................................................................ 10-17 10.5.1 Example Description ......................................................................................... 10-17 10.5.2 Configuration Description.................................................................................. 10-19 Chapter 11 Configuring Data for Interworking with SMC........................................................ 11-1 11.1 Introduction to the Chapter ............................................................................................ 11-1 11.2 Concepts Related to Data Configuration for Interworking with SMC............................. 11-1 11.2.1 SMC .................................................................................................................... 11-1 11.2.2 Networking Between MSOFTX3000 and SMC ................................................... 11-1 11.2.3 Parameter Relationship....................................................................................... 11-2 11.2.4 General Configuration Procedures...................................................................... 11-3 11.3 Collecting Data for Interworking with SMC .................................................................... 11-3 11.4 Configuring Data for Interworking with SMC ................................................................. 11-4 11.4.1 Configuring MTP Data......................................................................................... 11-4 11.4.2 Configuring SCCP Data ...................................................................................... 11-4 11.4.3 Modifying MAP Parameter Table ........................................................................ 11-4 11.5 Configuration Example .................................................................................................. 11-6 11.5.1 Example Description ........................................................................................... 11-6 11.5.2 Configuration Description.................................................................................... 11-7 Chapter 12 Configuring Data for Interworking with SCP ........................................................ 12-1 12.1 Introduction to the Chapter ............................................................................................ 12-1 12.2 Concepts Related to Data Configuration for Interworking with SCP ............................. 12-1 12.2.1 SCP ..................................................................................................................... 12-1 12.2.2 Networking Between MSOFTX3000 and SCP.................................................... 12-1 12.2.3 Parameter Relationship....................................................................................... 12-2 12.2.4 General Configuration Procedures...................................................................... 12-2 12.3 Collecting Data for Interworking with SCP..................................................................... 12-3 12.4 Configuring Data for Interworking with SCP .................................................................. 12-4 12.4.1 Configuring MTP Data:configuring MTP data ..................................................... 12-4 12.4.2 Configuring SCCP Data:configuring SCCP data ................................................ 12-4 12.4.3 Configuring SSP Capability:configuring SSP capability...................................... 12-4 12.4.4 Adding SCP Addressing Information:adding SCP addressing information ........ 12-5 vi


Table of Contents

12.4.5 Adding SCP Parameter Information:adding SCP parameter information ........... 12-6 12.5 Configuration Example .................................................................................................. 12-7 12.5.1 Example Description ........................................................................................... 12-7 12.5.2 Configuration Description.................................................................................... 12-9 Chapter 13 Configuring Data for Interworking with SGSN...................................................... 13-1 13.1 Introduction to the Chapter ............................................................................................ 13-1 13.2 Concepts Related to Data Configuration for Interworking with SGSN .......................... 13-1 13.2.1 SGSN .................................................................................................................. 13-1 13.2.2 Networking Between MSOFTX3000 and SGSN................................................. 13-1 13.2.3 Parameter Relationship....................................................................................... 13-2 13.2.4 General Configuration Procedures...................................................................... 13-3 13.3 Collecting Data for Interworking with SGSN.................................................................. 13-3 13.4 Configuring Data for Interworking with SGSN ............................................................... 13-4 13.4.1 Configuring MTP Data......................................................................................... 13-4 13.4.2 Configuring SCCP Data ...................................................................................... 13-4 13.4.3 Configuring SGSN Number................................................................................. 13-4 13.4.4 Modifying Mobile Soft Parameter ........................................................................ 13-5 13.4.5 Modifying MAP Parameter Table ........................................................................ 13-5 13.5 Configuration Example .................................................................................................. 13-7 13.5.1 Example Description ........................................................................................... 13-7 13.5.2 Configuration Description.................................................................................... 13-8 Chapter 14 Configuring Data for Interworking with GMLC ..................................................... 14-1 14.1 Introduction to the Chapter ............................................................................................ 14-1 14.2 Concepts Related to Data Configuration for Interworking with GMLC .......................... 14-1 14.2.1 GMLC .................................................................................................................. 14-1 14.2.2 Networking Between MSOFTX3000 and GMLC................................................. 14-1 14.2.3 Parameter Relationship....................................................................................... 14-2 14.2.4 General Configuration Procedures...................................................................... 14-3 14.3 Collecting Data for Interworking with GMLC.................................................................. 14-4 14.4 Configuring Data for Interworking with GMLC ............................................................... 14-5 14.4.1 Configuring MTP Data......................................................................................... 14-5 14.4.2 Configuring SCCP Data ...................................................................................... 14-5 14.4.3 Adding GMLC Number........................................................................................ 14-5 14.4.4 Adding Client GMLC Information ........................................................................ 14-6 14.4.5 Adding Emergency Call LCS Client .................................................................... 14-7 14.4.6 Adding Called Analysis Data (Optional).............................................................. 14-8 14.5 Configuration Example .................................................................................................. 14-9 14.5.1 Example Description ........................................................................................... 14-9 14.5.2 Configuration Description.................................................................................. 14-10 Chapter 15 Configuring Number Analysis Data ....................................................................... 15-1 15.1 Concepts Related to Number Analysis Data ................................................................. 15-1

vii


Table of Contents

15.1.1 Call Source, Dialed Number Set, Route Selection Code.................................... 15-1 15.1.2 Secondary Number Analysis............................................................................... 15-3 15.1.3 Number Conversion ............................................................................................ 15-3 15.1.4 Service Check ..................................................................................................... 15-3 15.1.5 EARLY ACM........................................................................................................ 15-3 15.1.6 Forwarded-to Number, Original Called Number, Connected Number ................ 15-4 15.2 Procedures of Number Analysis Processing ................................................................. 15-4 15.2.1 Incoming Number Pretreatment .......................................................................... 15-5 15.2.2 Number Analysis ................................................................................................. 15-6 15.2.3 Outgoing Number Preprocessing........................................................................ 15-6 15.3 Configuration Procedures .............................................................................................. 15-6 15.3.1 Overview of Configuration Procedures ............................................................... 15-6 15.3.2 Procedures for Configuring Number Analysis Preset Data................................. 15-6 15.3.3 Procedures for Configuring Incoming Number Pretreatment Data ..................... 15-7 15.3.4 Procedures for Configuring Number Analysis and Routing Data........................ 15-8 15.3.5 Procedures for Configuring Outgoing Number Preprocessing Data................. 15-10 15.3.6 Other Number Data Configurations .................................................................. 15-12 15.4 Configuring Preset Data Before Number Analysis ...................................................... 15-13 15.4.1 Adding Call Source ........................................................................................... 15-13 15.4.2 Configuring Number Conversion Data .............................................................. 15-15 15.5 Configuring Incoming Call Number Preprocessing Data ............................................. 15-22 15.5.1 Configuring Incoming Calling Number Associated Process Data..................... 15-22 15.5.2 Configuring Correlation Processing Data of Incoming Original Called Number 15-24 15.5.3 Configuring Incoming Number Pretreatment Data............................................ 15-26 15.6 Route Selection Data Configuration ............................................................................ 15-29 15.6.1 Configuring Call Prefix ...................................................................................... 15-29 15.6.2 Configuring Enhanced Route Processing Data ................................................ 15-32 15.6.3 Configuring Call Authority Original Called Correlation Processing Data .......... 15-33 15.6.4 Configuring Call Authority Check Data ............................................................. 15-35 15.6.5 Configuring Service Check Data ....................................................................... 15-37 15.6.6 Configuring Calling Number Analysis Data....................................................... 15-39 15.6.7 Configuring Calling Feature Processing Data................................................... 15-42 15.6.8 Configuring Calling Feature Analysis Data ....................................................... 15-43 15.6.9 Configuring Dialed Number Special Processing Data ...................................... 15-45 15.6.10 Configuring Failure Processing Data .............................................................. 15-47 15.7 Configuring Outgoing Number Preprocessing Data .................................................... 15-49 15.7.1 Configuring Outgoing Calling Number Correlation Processing Data ................ 15-49 15.7.2 Configuring Outgoing Original Called Number Correlation Processing Data ... 15-51 15.7.3 Configuring Outgoing Number Preprocessing Data.......................................... 15-53 15.7.4 Configuring Trunk Group Bearer Data .............................................................. 15-55 15.7.5 Configuring Trunk Group Bearer Index Data .................................................... 15-56 15.8 Configuring Other Number Conversion Data............................................................... 15-57

viii


Table of Contents

15.8.1 Configuring CLIP Called Correlation Processing Data ..................................... 15-57 15.8.2 Configuring CLIP Processing Data ................................................................... 15-59 15.8.3 Configuring Auxiliary Number Processing Data................................................ 15-60 15.8.4 Configuring MAP Interface Number Processing Data....................................... 15-61 15.8.5 Configure Bill Processing Information ............................................................... 15-62 15.8.6 Configuring Bill Control Data............................................................................. 15-63 15.9 Configuration Examples............................................................................................... 15-64 15.9.1 Planning of Number Analysis Data ................................................................... 15-64 15.9.2 Planning of Call Prefix Data .............................................................................. 15-65 15.9.3 Planning of Call Special Processing Data......................................................... 15-70 15.9.4 Examples of Call Special Processing Data Configuration ................................ 15-71 Chapter 16 Configuring Mobile Service Data ........................................................................... 16-1 16.1 Introduction to the Chapter ............................................................................................ 16-1 16.2 Concepts Related to Mobile Service Data..................................................................... 16-1 16.3 Configuring Location Update Data................................................................................. 16-4 16.3.1 General Configuration Procedures...................................................................... 16-4 16.3.2 Setting LAI or CGI/SAI ........................................................................................ 16-5 16.3.3 Setting Global Title Table.................................................................................... 16-5 16.3.4 Setting SCCP GT ................................................................................................ 16-6 16.3.5 Setting Local Office SCCP Subsystem ............................................................... 16-7 16.4 Configuring Enhanced Roaming Restriction Data ......................................................... 16-8 16.4.1 Configuration Description.................................................................................... 16-8 16.4.2 Starting Enhanced Roaming Restriction Function ............................................ 16-10 16.4.3 Configuring LAI Grouping Information .............................................................. 16-10 16.4.4 Configuring LAI.................................................................................................. 16-11 16.4.5 Configuring Roaming Restriction User Group................................................... 16-12 16.4.6 Configuring Roaming Subscriber Type ............................................................. 16-13 16.5 Configuring Roaming Zone Code Service ................................................................... 16-14 16.5.1 Service Description ........................................................................................... 16-14 16.5.2 Configuration Description.................................................................................. 16-16 16.5.3 Starting Zone Code Restriction Function .......................................................... 16-17 16.5.4 Adding Zone Code ............................................................................................ 16-17 16.5.5 Configuring the Relationship Between ZC and LAI........................................... 16-18 16.5.6 Configuring LAI.................................................................................................. 16-19 16.6 Configuration Examples............................................................................................... 16-20 16.6.1 Configuring Enhanced Roaming Restriction to Number Segment by LAI ........ 16-20 16.6.2 Configuring Zone Code Restriction ................................................................... 16-20 16.6.3 Configuring Location Service Data.................................................................... 16-21 16.6.4 Adding International Roaming Data of a Newly Subscribed Country or Region16-21 Chapter 17 Configuring IN Service Data ................................................................................... 17-1 17.1 Introduction to the Chapter ............................................................................................ 17-1 17.2 Concepts Related to IN Service Data ............................................................................ 17-1 ix


Table of Contents

17.2.1 Modes for Triggering IN Services........................................................................ 17-1 17.2.2 Triggering of Overlay Outgoing Intelligent Call ................................................... 17-1 17.2.3 Triggering of IN Service by Number Segment .................................................... 17-1 17.2.4 Triggering of Standard CAMEL 3 IN Service ...................................................... 17-5 17.3 Data Configuration Principles ........................................................................................ 17-6 17.4 Procedures for Configuring IN Service Data ................................................................. 17-7 17.4.1 Configuring Basic Data of Local Office with SSP Function................................. 17-7 17.4.2 Configuring Data for Triggering N-CSI DP2........................................................ 17-7 17.4.3 Configuring Data for Triggering N-CSI DP12...................................................... 17-7 17.4.4 Configuring Data for Triggering N-CSI DP4........................................................ 17-7 17.4.5 Configuring Data for Triggering N-CSI DP3........................................................ 17-7 17.4.6 Configuring Data for Triggering DCSI ................................................................. 17-8 17.4.7 Configuring Data in Overlay Mode ...................................................................... 17-9 17.4.8 Configuring Special Intelligent Resource Capability Data ................................ 17-10 17.4.9 Managing Special Number Information............................................................. 17-10 17.5 Configuration Examples............................................................................................... 17-10 17.5.1 IN Services Triggered by N-CSI DP3................................................................ 17-10 17.5.2 IN Services Triggered by N-CSI DP4................................................................ 17-11 17.5.3 Overlay Outgoing .............................................................................................. 17-11 Chapter 18 Debugging ................................................................................................................ 18-1 18.1 Introduction to the Chapter ............................................................................................ 18-1 18.2 Debugging of SCTP....................................................................................................... 18-1 18.2.1 Background Information ...................................................................................... 18-1 18.2.2 Debugging Methods ............................................................................................ 18-1 18.2.3 FAQ ..................................................................................................................... 18-2 18.3 Debugging of M3UA ...................................................................................................... 18-3 18.3.1 Background Information ...................................................................................... 18-3 18.3.2 Debugging Methods ............................................................................................ 18-3 18.3.3 FAQ ..................................................................................................................... 18-3 18.4 Debugging of Mc (H.248)............................................................................................... 18-8 18.4.1 Background Information ...................................................................................... 18-8 18.4.2 Debugging Methods ............................................................................................ 18-8 18.4.3 FAQ ..................................................................................................................... 18-9 Appendix A An Example on Global Data Configuration............................................................A-1 A.1 Introduction to the Appendix..............................................................................................A-1 A.2 Configuration Example ......................................................................................................A-1 A.2.1 Example Description...............................................................................................A-1 A.2.2 Data Collection........................................................................................................A-3 A.2.3 Data Configuration................................................................................................A-11 Index ................................................................................................................................................ i-1

x


Chapter 1 Overview of Data Configuration

Chapter 1 Overview of Data Configuration 1.1 Introduction to the Manual Office data is essential to the MSOFTX3000 system. Excellent quality of service provided by a network operator is based on successful data configuration. MSOFTX3000 adopts man machine language (MML) for data configuration. The operator should have a basic knowledge of MSOFTX3000, and know the operation rules of MML. A global example on data configuration is given in Appendix A so that you can more easily understand how to do data configuration. The contents of this manual are based on the networking model in Figure A-1 and the preset data in Appendix A. The configuration examples in Chapters 1 to 13 are also based on the same networking model.

1.2 Introduction to the Chapter This chapter contains the following sections: z

Situations Requiring Data Configuration

z

Data Configuration Procedures

z

Overview of MML Application

z

Precautions

z

Data Preparation

1.3 Situations Requiring Data Configuration You need to configure data in two cases: z

If it is the office deployment for the first time, you need to configure global data.

z

During equipment operation, you need to modify certain data for adding new network elements or changing links.

This manual focuses on the first situation, describing globally all aspects of data configuration. In routine operation and maintenance, data configuration refers to that of a certain aspect. For instance, add a radio network controller (RNC) to the office. Please refer to Chapter 5 “Interworking with RNC”.

1-1



1.4 Data Configuration Procedures 1.4.1 Global Configuration Procedures Figure 1-1 shows global data configuration procedures. For configuration of specific data, refer to corresponding chapters listed in the figure. Start Data preparation Internal data configuration

External interface data configuration

Configuring hardware data

Refer to Chapter 2 Hardware Data Configuration

Configuring local office information

Refer to Chapter 3 Local Office Data Configuration

Configuring data of interface to MGW

Refer to Chapter 4 Interworking with MGW

Configuring data of interface to RNC

Refer to Chapter 5 Interworking with RNC

Configuring data of interface to BSC

Refer to Chapter 6 Interworking with BSC

Configuring data of interface to HLR

Refer to Chapter 7 Interworking with HLR

Configuring data of interface to other MSC

Refer to Chapter 8 Interworking with MSC or Chapter 9 Interworking with SCP Refer to Chapter 10 Interworking with PSTN

Configuring data of interface to PSTN

Service data configuration

Configuring data of interface to SMC

Refer to Chapter 11 Interworking with SMC

Configuring data of interface to SCP

Refer to Chapter 12 Interworking with SCP

Configuring data of interface to SGSN

Refer to Chapter 13 Interworking with SGSN

Configuring data of interface to GMLC

Refer to Chapter 14 Interworking with GMLC

Configuring number analysis data

Refer to Chapter 15 Number Analysis Configuration

Configuring mobile service data

Refer to Chapter 16 Mobile Service Data Configuration

Configuring IN service data

Refer to Chapter 17 IN Service Data Configuration

End

Figure 1-1 Procedures for configuring data in MSOFTX3000 The basic principle is to first configure internal data, then interface data, and finally service data.

1.4.2 Configuring Internal Data This stage covers the hardware data settings and basic information settings. It is further divided into three phases: z

Before data configuration

1-2


1)


Get to know the networking and equipment settings in details, such as board setting and link configuration.

2)

Get such interfacing and negotiation data as SS7 links, IP address, and port number.

3)

Illustrate all these data in tables or figures.Configuring hardware data

The hardware data is vital to the operation of the MSOFTX3000 system. It covers board, subrack and rack configuration data. z

Configuring local office data

It covers the configuration of basic information, such as signaling point code of MSOFTX3000 in public land mobile network (PLMN).

1.4.3 Configuring Interface Data It covers interface data configuration of MSOFTX3000 interconnecting with other network elements (NEs) in PLMN. The NEs and interfaces include: z

To media gateway (MGW), through Mc interface

z

To RNC, through Iu-CS interface

z

To base station controller (BSC), through A interface

z

To MGW, through Mc interface

z

To other (G)MSC Server, through E interface

z

To service control point (SCP), through CAP and L interface

z

To short message center (SMC), through E interface

z

To public switched telephone network (PSTN), through PSTN trunk interface

z

To serving GPRS support node (SGSN), through Gs interface

z

To gateway mobile location center (GMLC), through Lg interface

Note: None of the above interface data is mandatory to be configured. You need to choose some items according to specific networking requirement. The data configurations of the interfaces are independent from one another. However, it is recommended to follow the sequence provided in this manual. As multiple transport layer protocols can be applied to MSOFTX3000 external interfaces, clarify it before data configuration starts.

1.4.4 Configuring Service Data It covers data configuration of number analysis, mobile service, and wireless intelligent network (WIN) service.

1-3



1.5 Overview of MML Application 1.5.1 Using MML Command Generally, data configuration is conducted through local maintenance terminal (LMT). Once you enter a command, the relevant parameters will be shown. The parameters in red are mandatory, but the rest are optional, that is, they can adopt the default values without any interference to other configurations. When setting data, look for the contents according to the configuration in "MML Command" in the [MSOFTX3000 Operation and Maintenance Center] window, and double-click the corresponding command to display the command window. To know the detailed execution of a command, you may press or click [Help Information] above the pane for command input. If you are not familiar with a command, you may enter the key words of the command in the [Search] tab page to locate it quickly.

1.5.2 Using Data Script I. Situations for Using Data Script You can configure data by loading data script in the following cases: z

The data configuration is conducted for the first time at the initial stage of the implementation.

z

There are a big number of data to be configured for expansion and upgrade.

II. Compilation of Script To compile a piece of script, do the following: 1)

Select [System/Save Input Commands] in the [MSOFTX3000 Operation and Maintenance Center] window.

2)

Select the name of the file.

3)

Select the directory to save the command.

4)

Enter the command in the command input window.

5)

Execute the command.

6)

After execution of the command, select [System/Stop Save Input Commands].

III. Use of Script To use the script, proceed as follows: 1)

Directly use the data script file in TXT format.

2)

After modifying the data based on the specific situations, set the system to the offline state by executing the command LOF.

3)

Select [System/Execute Batch Commands].

4)

Select the needed data script in TXT format in the pop-up dialogue box. 1-4



5)

Execute the format conversion command FMT.

6)

Execute the LON command.

7)

Finally, power on the system and load the data.

If there are only a few batch commands, you can execute them directly without setting the MML client offline. For the method of using script, refer to HUAWEI MSOFTX3000 Mobile Switching Center Installation Manual – System Commissioning.

IV. Classification of Commands Refer to Table 1-1 for detailed meaning of commands. Table 1-1 Classification of commands Command

Description

ADD

To add data

MOD

To modify data

RMV

To remove data

LST

To list BAM data

DSP

To display host data, state of equipment, or resource consumption

SET

To set data or state

LOF

Offline

LON

Online

1.6 Precautions 1.6.1 Before Data Configuration Before configuring data, complete the following: z

Obtain the office networking and configuration details.

z

Understand the requirements raised during the project design phase of the office.

z

Read data information about this office carefully and contact related personnel once a defect is found.

1.6.2 During Data Configuration When configuring data, note the following: z

For MML commands, the parameters in red are mandatory.

z

When deploying a new site, a)

Set data offline.

b)

Prepare online setting data. 1-5

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center c)


Reload data.

Refer to Table 1-2 for details. Table 1-2 Data configuration procedures for deploying a new site Command

Description

LOF

To set data offline

SET CWSON: SWT=OFF

To disable the alarm switch

SET FMT: STS=OFF

To disable the format conversion switch

LON

To set data online

SET CWSON: SWT=ON

To enable the alarm switch

SET FMT: STS=ON

To enable the format conversion switch

FMT

To format data

Power off, power on, and start loading

z

In routine maintenance, implement data configuration in online state, except when executing the command MOD MAXT to modify maximum tuple number in offline state.

z

To open online help for detailed information of commands and parameters, press .

1.7 Data Preparation 1.7.1 Prerequisites for Data Preparation The prerequisites of this step are: z

Hardware installation has been completed.

z

The system has been powered on.

1.7.2 Data Preparation Operations

Important Note: To ensure a quick and secure data configuration process, you need to collect the following data and make corresponding planning in advance.

I. Determining Networking Model Draw the networking diagram of MSOFTX3000 and the related functional entities.

1-6



II. Collecting Information of Adjacent Location and Service Areas After determining the networking mode, you can collect information about the adjacent location areas and service areas.

III. Determining Parameters z

Interface parameters

Calculate or negotiate all interface parameters according to the planned network capacity. For instance, determine how many signaling system number 7 (SS7) links for HLR, how many signaling ATM adaptation layer (SAAL) links for RNC, how many links for MGW, and how many signaling points assigned for all functional entities. z

Internal parameters

Determine subrack configuration within the designed capacity, including number of subracks and boards. The key internal parameters should also be determined, as data for compulsory subracks displayed in Table 1-3. Table 1-3 Subrack information table Subrack type

Subrack number

Site number

Row number

Column number

Board type

Subrack number

Slot number

Front/back

Module number

Slot number of assistant board

IP address of fast Ethernet (FE) port

IP address of the router that connects to MSOFTX3000

Link type (64 kbit/s or 2 Mbit/s)

Balance mode of E1 port (balance or non-balance)

Frame format of E1 port (DF/CRC4)

Subrack/slot/E1 number of the E1-pool interface board (WEPI) that provides clock reference

1-7



IV. Determining Interworking Parameters Refer to the following tables for data required for MSOFTX3000 interworking with other adjacent entities r interfaces. In the shadowy columns are the parameters that require consistency between two ends, or those to be informed to the peer end. The rest are internal parameters in MSOFTX3000. Record the configured data for future troubleshooting or query. Table 1-4 Local office information table Item Signaling point

Data International network valid

International reserved network valid

Country code

Area code

ODB_SS

Authorize during service access and location update procedure?

Cipher algorithm?

Reallocate temporary mobile subscriber identifier (TMSI) during service access and location update procedure?

Support visitor location register (VLR) location update?

Check international mobile station equipment identity (IMEI) or contain IMEI in bill during service access and location update procedure?

Support home PLMN (HPLMN) call forwarding on mobile subscriber not reachable (CFNRC)?

Support zone code restriction?

Support short message mobile originated (SMMO)/short message mobile terminated (SMMT) function?

Support prepage?

MAP version/ customized applications for mobile network enhanced logic (CAMEL) version

National valid

network

National reserved network valid

Local number

MSC

Local number

VLR

Mobile network code (MNC)

Network (NC)

code

/ Mobile network data / / / Mobile application part (MAP) information

Identify user?

/

/

/

/

/

1-8



Item /

Data Support call hold?

Support interface?

Gs

Support enhanced roaming restriction?

/

Table 1-5 MGW information table Item

Basic information

Data

MGW index

Transmission protocol

Voice encoding/ decoding mode

SCTP connection number 1

Local IP forward module (WIFM) address of Link 1

Local WIFM port of Link 1

Checksum mode

Encryption algorithm and secret key (optional) of MGW

Remote MGW address of Link 1

Remote MGW port of Link 1

Server or client

/ Stream control transmission protocol (SCTP) connection information /

Table 1-6 RNC information table Item RNC basic information

Data RNC ID

Signaling point code

Network ID

Service mode

Routing context (optional)

WIFM module No.

M3UA link number

Local address LINK 1

Prefix (local office)

Route selection code

Location area identity (LAI)

Service area identify (SAI)

AMR LIST

IP address of the peer MGW of LINK 1

Port of peer MGW

Server or client

/ M3UA basic signaling / M3UA link information

IP of

/ Prefix /

1-9

Local port



Table 1-7 BSC information table Item

Data Network ID of signaling point code

Location area identity (LAI)

Global cell identification (GCI)

Intra-module link number

Signaling link code (SLC)

Intra-module circuit number (E1 number/ timeslot number)

Link type

Termination ID (the number of the physical circuit from MGW to base station controller (BSC))

Circuit identification code (CIC)

MGW index

Office direction

Trunk group

Circuit type



Intra-module circuit number (E1 number/times lot number)

Link type

Basic informatio n


/

Signaling link

Wireless call control and signaling processing unit (WCSU) module number

Link set

/

Circuit

/ Trunk route / Prefix /

Table 1-8 MSC information table Item

Data

Basic information


NI signaling point

of

MSC Server number (E.164 code)

/

Signaling link

WCSU module number

Link set


/

1-10

SLC and SLC sending



Item

Circuit

Data

CIC

Wireless call control unit (WCCU)/WC SU module number

MGW index

Route number

Sub-route number

Trunk group

Circuit type


Route selection source code

Termination ID (the number of the physical circuit from MGW to MSC Server)

Office direction

Prefix


Table 1-9 PSTN information table Item

Data

Basic information


NI of signaling point

/

Signaling link


SLC and SLC sending

Intra-module circuit number (E1 number/ timeslot number)Data

Termination ID (the number of the physical circuit from MGW to PSTN)

CIC

WCCU/W CSU module number

MGW index

Office direction

Route number

Sub-route number

Trunk group

Circuit type

Prefix



WCSU module number

Link set

/

Circuit


1-11

Link type



Table 1-10 HLR information table Item

Data

Basic information

NI signaling point


of

HLR number (E.164 code)

/

Signaling link

WCSU module number

Link set


SLC and SLC sending

Encoding description

Numbering plan

Address information

Destination point code (DPC)


Link type

/ Signaling connection control part (SCCP) global title (GT) translation /

Table 1-11 SCP information table Item

Data

Basic information


NI signaling point

of

E.164 code

/

Signaling link

WCSU module number

Link set


/

1-12

SLC and SLC sending


Link type



Table 1-12 SMC information table Item

Data Signaling point code

Basic information

NI signaling point

of

E.164 code

/

Signaling link

WCSU module number/WC CU/WSGU

SLC and SLC sending


Link set


Link type


Link type

/

Table 1-13 SGSN information table Item

Data

Basic information


NI signaling point

of

E.164 code

/

Signaling link

WCSU module number

Link set


SLC and SLC sending

/

Table 1-14 GMLC information table Item

Data

Basic information


NI signaling point

of

Link set


E.164 code

/ Signaling link

WCSU module number

/

1-13

SLC and SLC sending

Intra-module circuit number (E1 number/ timeslot number) Data

Link type


Chapter 2 Configuring Equipment Data

Chapter 2 Configuring Equipment Data 2.1 Introduction to the Chapter The equipment data is the prerequisite of configuring other MSOFTX3000 data. It defines the hardware data and physical setting of MSOFTX3000. This chapter contains the following sections: z

Concepts Related to Equipment Data

z

Collecting Equipment Data

z

Configuring Equipment Data

z z

Locking Clock Reference Source through E1

z

Locking Clock Reference Source through BITS

z

Configuration Example

2.2 Concepts Related to Equipment Data 2.2.1 Equipment Numbering

Important Note: To identify and locate the devices of MSOFTX3000 correctly and quickly, it is necessary to number the devices of the same type based on the following numbering rules.

I. Shelf Number Each shelf is assigned with a shelf number uniquely in the system. There is a one-to-one corresponding relationship between shelf numbers and site numbers, as well as between row numbers and column numbers. A shelf number should be consistent with the actual position of a shelf when configured, so that the system can generate correct alarm information if a failure occurs to the shelf during operation. MSOFTX3000 can be configured with a maximum of three shelves, numbered from 0 to 2. The shelf with the basic frame is numbered as 0.

2-1



Note: Site number, row number, and column number are provided as location information. If the numbering plan for shelves is the same as the actual condition, a fault can be located quickly.

II. Frame Number Each service processing frame is allocated with a frame number uniquely in the system. MSOFTX3000 can support up to 10 frames, numbered from 0 to 9. The basic frame is numbered as 0 and the other frames are numbered from 1 to 9 from bottom upward. The configuration data for MSOFTX3000 frame numbers must be consistent with the hardware settings. You can set service processing frame numbers through the dual-in-line package (DIP) switch of the WSIU in the frame. Table 2-1 shows the corresponding relationships between settings of the 8-digit DIP switch S3 of the WSIU and frame numbers (off=1, on=0). Table 2-1 Corresponding relationships between DIP switch settings of the WSIU and frame numbers Switch

8

7

6

5

4

3

2

1

0

on

on

on

on

on

on

on

on

1

on

on

on

on

on

on

on

off

2

on

on

on

on

on

on

off

on

3

on

on

on

on

on

on

off

off

4

on

on

on

on

on

off

on

on

5

on

on

on

on

on

off

on

off

6

on

on

on

on

on

off

off

on

7

on

on

on

on

on

off

off

off

8

on

on

on

on

off

on

on

on

9

on

on

on

on

off

on

on

off

Frame number

III. Slot Number All frames are universal in MSOFTX3000. The boards are inserted in the backplane from front and back. Some front boards and back boards are configured in pair.

2-2



Table 2-2 List of boards in MSOFTX3000 Front board

Back board

WSMU

System management unit

WSIU

System interface unit

WCCU

Moble call control unit

-

-

WCSU

Wireless Call control and Signaling processing unit

WEPI

E1-pool interface board

WBSG

Broadband signaling processing unit

-

-

WIFM

IP forward module

WBFI

Back FE interface board

WAFM

ATM forward module board

WBAI

Back ATM interface board

WCDB

Central database board

-

-

WVDB

VLR database board

-

-

WMGC

Media gateway contorl board

WALU

Alarm unit

UPWR

Secondary power board

UPWR

Secondary power board

-

-

WHSC

Hot-swap control board

-

-

WCKI

Clock interface board

Some boards must be configured in each frame, such as the WSMU, WSIU, WHSC, UPWR, and WALU; while the others are optional, such as the WIFM, WVDB, and WAFM. When the capacity of the system is relatively small, a single WIFM can provide all features of the WBSG, WMGC and WIFM. A frame is designed to contain 21 boards numbered from 0 to 20. The front boards are numbered from left to right, and the back boards are numbered from right to left. The relations between boards and slots are shown as follows: z

The WSMUs (and back boards WSIUs) must be inserted in slots 6 and 8.

z

The WALU must be inserted in front slot 16.

z

The WHSC must be inserted in back slots 7 and 9, and front panels are installed in corresponding front slots.

z

Each UPWR occupies two slots, and there are two front UPWR boards and two back UPWR boards. The slot numbers designated are 17 and 19.

z

Other slots (0–5, 10–15) are inserted with service processing boards (including the WCCU, WCSU, WBSG, WIFM, WAFM, WCDB, WVDB, and WMGC).These slots are compatible with one another.

2-3



Important Note: Such boards as the WSMU, WSIU, WHSC, WALU, and UPWR are not to be configured, but will be automatically added by the system.

IV. Module Number MSOFTX3000 regards BAM, iGWB, and boards as modules, and numbers them accordingly from 0 to 255. 0 is for BAM, 1 is for iGWB, and the others are allocated to boards. Module number starts from 2 according to board type. The module number of a board is unique in the system. The numbering rules are as follows: z

WSMU module number: 2–21 (allocated automatically by the system)

z

WCCU/WCSU module number: 22–101

z

WCDB/WVDB module number: 102–131

z

WMGC/WAFM/WIFM/WBSG/WSGU module number: 132–211

2.2.2 Clock Plan For clock plan of MSOFTX3000, refer to Chapter 4 in HUAWEI MSOFTX3000 Hardware Description Manual. For cable connections, refer to Chapter 6 “Installation of Signal Cables” in HUAWEI MSOFTX3000 Hardware Installation Manual for details.

2.3 Collecting Equipment Data Before configuring equipment data, you need to collect the equipment data of MSOFTX3000 as listed in Table 2-3. In the shadowy columns are the parameters that require consistency between two ends, and the others are internal parameters of MSOFTX3000.

2-4



Table 2-3 List of equipment data to be collected Frame type

Frame number

Site number

Row number

Column number

Basic frame

0

1

1

1

Board type

Frame number

Slot number

Front/back

Module number


WCSU

0

0

Front

22

1

WCSU

0

1

Front

22

0

…

… IP address of FE port

IP address of the router connecting to MSOFTX3000




Frame/slot/E1 number of the WEPI providing clock reference

2.4 Configuring Equipment Data 2.4.1 Before Configuration I. Significance of Equipment Data Equipment data is the prerequisite of configuring other MSOFTX3000 data. It defines the hardware data and physical setting of MSOFTX3000.

II. Parameter Relationship in Hardware Configuration The commands for configuring equipment data and their parameter relations are shown in Figure 2-1.

2-5


ADD SHF


ADD FRM

ADD EPICFG

[Shelf Number]

[Shelf Number]

[Connect E1 EPI Frame Number]

[Location Title]

[Frame Number]

[Connect E1 EPI Slot Number]

[Position Number]

[Position Number]

ADD BRD

ADD FECFG

[Frame Number]

[IFM Module Number]

[Slot Number]

[IP Address]

[Board Type] [Module Number]

ADD CDBFUNC [CDP Module Number] [Function]

Figure 2-1 Parameter relationship of commands for configuring equipment data

III. General Configuration Procedures See Table 2-4 for the procedures and commands for adding equipment data. Table 2-4 Procedures for configuring equipment data Procedure

Command

1: Add shelf

ADD SHF

2: Add frame

ADD FRM

3: Add board

ADD BRD

4: Add CDB Function

ADD CDBFUNC

5: Add FE port information of the WIFM

ADD FECFG

6: Load equipment data

/

2.4.2 Adding Shelf I. Background Information MSOFTX3000 can be configured with up to three cabinets, and these cabinets can be added one by one according to the actual configuration.

2-6



II. Command ADD SHF

III. Major Parameters [Shelf Number] This parameter is used to identify a shelf uniquely. The integrated configuration cabinet is numbered as 0, and the rest two are numbered as 1 and 2 respectively from left to right. [Location Title] It describes the position of a shelf. It is in character string. [Position Number] It defines the number of the equipment in which a shelf resides. [Row Number] [Column Number] It specifies the row and column in which a shelf resides. [PDB Location] These two parameters are used to describe the location number (that is, "Position Number” in ADD BRD) of the WSMU that manages the power distribution box (PDB). Physically, it refers to the location number of the frame in which the WSIU connecting to the PDB serial cable resides. It must conform to actual setting, or the PDB state will not be reported.

IV. Related Commands See Table 2-5 for the commands related to shelf configuration. Table 2-5 List of commands related to shelf configuration Command ADD SHF

Description To add shelf To remove an existing shelf from the system

RMV SHF

Before removing a shelf, you must ensure that the related module, board and frame have been removed. To modify the properties of a shelf

MOD SHF

You can use this command to modify the position (location title, position number, row number and column number) of a shelf.

2-7



Command

Description To list the properties of the specified shelf

LST SHF

If you expect to browse the properties of all shelves in the system, just set the parameter "shelf number" to "ALL".

2.4.3 Adding Frame I. Background Information None

II. Command ADD FRM

III. Major Parameters [Frame Number] This parameter is used to identify a frame uniquely. A frame number is unique in the system, and they range from 0 to 9. Frame numbered as 0 is the basic frame, and the expansion frames are numbered from 1 to 9 from bottom upward. Before configuring the expansion frames, configure the basic frame first. The settings of frame numbers must be consistent with those on the DIP switch of the WSIU. [Shelf Number] This parameter identifies a shelf. This parameter is defined in the ADD SHF command. [Position Number] This parameter is used to identify the position of a frame in a shelf. This parameter must be consistent with the actual hardware condition; otherwise, the frame information cannot be shown correctly on the maintenance console. The position numbers in each shelf from bottom upward are 0 to 3 according to the following allocation rules: z

In Shelf 0 (integrated configuration cabinet), position numbers 0 and 1 are for BAM and iGWB server, and position numbers 2 and 3 are for service frames.

z

In Shelves 1 and 2, the position numbers are allocated from 0 to 3 according to the actual configuration.

2-8



IV. Related Commands See Table 2-6 for the commands related to frame configuration. Table 2-6 List of commands related to frame configuration Command ADD FRM

Description To add a frame To remove an existing frame

RMV FRM

Before removing a frame, you must ensure that the related module and board have been removed. To modify the properties of a frame

MOD FRM

You can use this command to modify the position information (shelf number and position number) of a frame. To list the properties of the specified frame

LST FRM

If you expect to browse the properties of all frames in a shelf, just specify the parameter "frame number" to "ALL".

DSP FRM

To display the information of a frame

2.4.4 Adding Board I. Background Information By default, when you add a frame with the ADD FRM command, the WSMU, WSIU, WHSC, WALU and UPWR of the frame will be configured automatically. In this case, it is only required to use the LST BRD command to verify the slot numbers of these boards. You need to manually configure such boards as the WCCU, WCCU, WCSU, WCDB, WVDB, WBSG, WSGU, WMGC, WIFM, WEPI, and WCKI. To modify the message transfer part (MTP) link type (64 kbit/s by default) of the central processing board (CPC) on the WCSU, use the command MOD CPCCFG.

II. Command ADD BRD

III. Major Parameters [Frame Number]

2-9



This parameter refers to the number of a frame where a board resides. This parameter is associated with the frame number set in the ADD FRM command. [Slot Number] [Location] These two parameters are used to determine the physical position (slot and front/back) of a board in a frame. [Board Type] This parameter is used to specify the type of a board to be added. [Module Number] This parameter is used to specify the module number corresponding to the board to be added. It should be configured according to the rule mentioned previously, and it will be used in later configuration.

Note: The range of module numbers is: WSMU: 2–21 (automatically assigned by the system) WCCU/WCSU: 22–101 WCDB/WVDB: 102–131 WMGC/WAFM/WIFM/WBSG: 132–211

[Assist slot number] It indicates the slot number of the assistant board. When the added board works in active-standby mode, this parameter enhances system security by indicating the slot number of the assistant board. It is only valid to boards working in active-standby mode. If you enter “255”, it means that no assistant board is needed.

Important Note: The slot pairs of 0 and 1, 2 and 3, 4 and 5, 10 and 11, 12 and 13, 14 and 15 are adjacent slots by default. To set the assistant board to be inserted in the non-default adjacent slot, just enter the slot number of the assistant board. It is recommended to use the default setting. After you specify the assistant board with this parameter, you don’t have to add the board using the command ADD BRD. The WCCU, WCSU, WCDB, WVDB, and WIFM are all working in active-standby mode.

2-10



[Link type] When the added board is WCSU, this parameter specifies the type of CPC sub-board—one processing 64 kbit/s MTP links, and the other processing 2Mbit/s MTP links.

IV. Related Commands See Table 2-7 for the commands related to board configuration. Table 2-7 List of commands related to board configuration Command

Description

ADD BRD

To add a board

RMV BRD

To remove an existing board

LST BRD

To list the configuration information of a board

DSP BRD

To display the state of a board

DSP BRDVER

To display the version information of a board

SWP BRD

To switch over the active and standby boards

RST BRD

To reset a board

MOD LSS

To modify the loading switching of a board

LST LSS

To list the loading properties of a board

DSP COMM

To display communication port state

MOD CPCCFG

To modify the link type of the CPC sub-board on the WCSU

LST CPCCFG

To list the link type of the CPC sub-board on the WCSU

Important Note: The LST commands are used to list configuration data, while the DSP commands are used to display state. You cannot remove the boards/frames that are configured with subscriber data or functions. When you use the RMV BRD command to remove a board, you must specify whether the board to be removed is a front board or a back board.

2-11



2.4.5 Adding CDB Function I. Background Information Functioning as the central database of MSOFTX3000, the WCDB stores all functional data like VLR agent functional data, gateway resource management data, outgoing trunk routing data, and so on. MSOFTX3000 cannot operate normally without the WCDB.

II. Command ADD CDBFUNC

III. Major Parameters [Function] This parameter is used to configure the functions for the WCDB based on the actual requirements. To save resources, only the functions used by the local office are configured. z

TK: Used for selecting outgoing trunks

z

MGWR: Used for managing media gateway resources

z

VDB: Used for managing VLR database (VDB) allocation parameters, including allocation of mobile station roaming number (MSRN) and transferring of VDP maintenance commands

z

CGAP: Used for managing call gapping resources, including allocation and management of global call gapping in the WIN

Generally, the TK, MGWR, and VDB functions are compulsory; the rest are optional. [CDP Module Number] It refers to the module number of the WCDB. This parameter is associated with the module number defined in the ADD BRD command, and can be queried with the LST MDU command.

Important Note: When one pair of WCDBs is configured, all database functions must be configured. When two pairs of WCDBs are configured, allocate the database functions on the two pairs based on the load-sharing principle. In the networking mode of time division multiplexing (TDM), TK and MGWR must be configured on the same pair.

2-12



IV. Related Commands See Table 2-8 for the commands related to CDB function configuration. Table 2-8 List of commands related to CDB function configuration Command

Description

ADD CDBFUNC

To add function information of the WCDB

RMV CDBFUNC

To remove function information of the WCDB

LST CDBFUNC

To list function information of the WCDB

2.4.6 Adding FE Port Information of WIFM I. Background Information The WIFM interfaces MSOFTX3000 with IP network, and it also processes IP bottom-layer protocols. The WIFM dispatches messages to the WBSG for further processing according to the IP address and port number in IP packets. In this case, you need to set FE port connection type for the WIFM to support the maximum number of call connections.

II. Command ADD FECFG

III. Major Parameters [IFM Module Number] This parameter refers to the module number of the WIFM where FE is configured. It is associated with the module number defined in the ADD BRD command. [IP Address], [Mask Address] These parameters are used to identify the WIFM in external communication. [Default Gateway] It defines the IP address of the router to which the FE port connects. When MSOFTX3000 directly connects to MGW, enter the IP address of the WIFM here. [Ethernet Attribute] This parameter is used to specify Ethernet attributes, such as Auto negotiation, HT, FT, HH and FH. The default value is Auto negotiation.

2-13



IV. Related Commands See Table 2-9 for the commands related to FE port configuration. Table 2-9 List of commands related to FE port configuration Command

Description

ADD FECFG

To add FE port information (IP address) of the WIFM

RMV FECFG

To remove FE port information of the WIFM

MOD FECFG

To modify FE port information of the WIFM

LST FECFG

To list FE port information of the WIFM

2.5 Locking Clock Reference Source through E1 2.5.1 Before Configuration I. Introduction to E1 Port Data and Clock Data E1 port data and clock data are both equipment data, and will be configured when MSOFTX3000 provides MTP links to connect a SS7 signaling network. In the clock plan of MSOFTX3000, MSOFTX3000 can lock the line clocks provided by external devices. Such devices as MGW, HLR and PSTN can provide stable stratum-3 or higher clock sources.

II. General Configuration Procedures Table 2-10 lists the procedures and commands for configuring E1 port data and clock data. Table 2-10 Configuration procedures Procedure

Command

1: Add WEPI and WCKI

ADD BRD

2: Set clock reference source

SET CKICFG

3: Add E1 information

ADD EPICFG

4: Extract clock reference data from WEPI

ADD BOSRC

2-14



2.5.2 Adding WEPI and WCKI I. Background Information The WEPI and WCKI are both back boards. The WCKI can be inserted in slot 13 or 15 at the back of the basic frame (frame 0).

II. Command ADD BRD

III. Major Parameters Refer to 2.4.4 Adding Board for details.

IV. Related Commands Refer to 2.4.4 Adding Board for details.

2.5.3 Setting Clock Reference Source I. Background Information None

II. Command SET CKICFG

III. Major Parameters [Clock Level] Set it to stratum-2 clock or stratum-3 clock according to the requirement. [Work Mode] Set it to auto mode or manual mode for clock reference source. z

Auto: The WCKI will automatically select the clock reference source with the highest priority.

z

Manual: The WCKI will lock the specified clock reference source.

[BITS1 Priority] [BITS2 Priority] [Line Clock1 Priority] [Line Clock2 Priority] When the clock work mode is set to "Manual", and the priorities of two reference sources are the same, the clock boards will extract the clock reference source from clock source 1 to clock source 4.

2-15



[BITS1 Clock Source Type], [BITS2 Clock Source Type] These two parameters are used to define the external clock reference source synchronizing the WCKI. They are only available when MSOFTX3000 extracts the clock reference source imported from BITS. There are two types of clock reference sources of BITS: z

CLK_2M: E1(2 Mbit/s)

z

CLK_E1: 2M(2 MHZ)

IV. Related Commands See Table 2-11 for the commands related to clock reference source configuration. Table 2-11 List of commands related to clock reference source configuration Command

Description

SET CKICFG

To set clock reference source

LST CKICFG

To list clock reference source information

2.5.4 Adding E1 Information I. Background Information When MSOFTX3000 processes the narrowband SS7 over TDM, it is required to add the WEPI and configure its E1 information.

II. Command ADD EPICFG

III. Major Parameters [Frame Number] This parameter refers to the frame number of the WEPI to which E1 belongs. It is associated with the frame number set in the ADD FRM command. [Slot Number] This parameter refers to the slot number of the WEPI to which E1 belongs. It is used to locate the WEPI. This parameter is associated with the slot number involved in the ADD BRD command. [E1_0 Config] [E1_1 Config]……[E1_7 Config]

2-16



This parameter is used to define whether an E1 is configured in the WEPI. Each WEPI provides eight E1s, which are numbered from E1_0 to E1_7. There are three options: z

Double frame (DF): default value

z

CRC4: multi-frame format

z

Not Config: not configured

Generally, select DF in interconnection with Huawei MGW. [Balance Mode] This parameter is used to define E1 transmission mode. Two options are provided for the actual modes of transmission line: z

BALANCE indicates that the transmission line is 120-ohm balanced twisted pair.

z

NON_BALANCE indicates that the transmission line is 75-ohm non-balanced coaxial cable.

Generally, NON_BALANCE is selected.

IV. Related Commands See Table 2-12 for the commands related to E1 configuration. Table 2-12 List of commands related to E1 configuration Command

Description

ADD EPICFG

To add E1 information of the WEPI

MOD EPICFG

To modify E1 information of the WEPI

RMV EPICFG

To remove E1 information of the WEPI

LST EPICFG

To list E1 information of the WEPI

2.5.5 Adding Clock Reference from WEPI I. Background Information In the basic frame, you need to extract a 2-Mbit/s or 2-MHz clock reference source from the peer office equipment through E1 in the WEPI. Execute the command DSP BRD to display the E1 port state specified by the parameter “E1 number”. If the state is not normal, the clock reference data cannot be extracted. Before executing the command ADD BOSRC, execute LST BOSRC to check if there is a pre-defined setting; if so, remove the setting with the command RMV BOSRC.

2-17



II. Command ADD BOSRC

III. Major Parameters [Frame Number] It specifies the number of the frame in which the WEPI locates. This parameter must be defined in the command ADD FRM and referenced here. [Slot Number] It specifies the number of the slot in which the WEPI locates. This parameter must be defined in the command ADD FRM and referenced here. [E1 Number] It specifies the port number of the E1 in the WEPI through which the clock reference is extracted.

IV. Related Commands See Table 2-13 for the commands related to clock reference source configuration. Table 2-13 List of commands related to clock reference source configuration Command

Description

ADD BOSRC

To add clock reference source data of board

RMV BOSRC

To remove clock reference source data of board

LST BOSRC

To list clock reference source data of board

Note: When a pair of two adjacent WEPIs works in active-standby mode, the clock reference source can only be extracted from the E1 connected to the active one. If there are four WEPIs in the basic frame, two 2-Mbit/s clock signals can be extracted from the two WEPIs providing E1 cables, thus four clock reference source signals are provided to the active and standby WCKIs (two signals for each WCKI).

2.5.6 Checking Clock Reference Source To check the clock reference source, do the following:

2-18


1)


Execute the command DSP BRD to check if the present clock reference source of the WCKI is extracted from the peer office equipment.

2)

Execute the command DSP CLKPH to check the phase-lock state.

The phase-lock state should be “Trace Mode”. The phase-lock duration of the WCKI is relatively long, about half an hour.

2.6 Locking Clock Reference Source through BITS 2.6.1 Before Configuration I. Introduction to Clock Reference Source of MSOFT3000 MSOFTX3000 serves as the clock reference source and connects to Building Integrated Timing Supply System (BITS). The WCKI can output stable stratum-2 clock signal to synchronize other equipment.

II. General Configuration Procedures Table 2-14 lists the general procedures for configuring E1 port and clock data in locking clock reference source through BITS. Table 2-14 Configuration procedures Procedure

Command

1: Add WEPI and WCKI

ADD BRD

2: Set clock reference source

SET CKICFG

3: Add E1 information

ADD EPICFG

2.6.2 Adding WEPI and WCKI I. Background Information The WEPI and WCKI are both back boards. The WCKI can be inserted in slot 13 or 15 at the back of basic frame (frame 0).

II. Command ADD BRD

2-19



III. Major Paramters Refer to 2.4.4 Adding Board for details.

IV. Related Commands Refer to 2.4.4 Adding Board for details.

2.6.3 Setting Clock Reference Source I. Background Information None

II. Command SET CKICFG

III. Major Parameters Refer to 2.5.3 Setting Clock Reference Source for details.

Important Note: You must set the parameter “Clock Level” in the command to Level Two.

IV. Related Commands Refer to 2.5.3 Setting Clock Reference Source for details.

2.6.4 Adding E1 Information I. Background Information None

II. Command ADD EPICFG

III. Major Parameters Refer to 2.5.4 Adding E1 Information for details. 2-20



IV. Related Commands Refer to 2.5.4 Adding E1 Information for details.

2.6.5 Checking Clock Reference Source To check the clock reference source, do the following: 1)

Execute the command DSP BRD to check if the present clock reference source of the WCKI is extracted from MGW.

2)

Execute the command DSP CLKPH to check the phase-lock state.

The phase-lock state should be “Trace Mode”. The phase-lock duration of the WCKI is relatively long, at least half an hour.

2.6.6 Loading Equipment Data If the equipment data is added in offline state, you need to format all data of all modules to generate data loading files (dbxxx.dat files) after the preceding configurations. The procedures of generating data loading files are shown in Table 2-15. Table 2-15 Procedures of generating data loading files Command or procedure

Description

LON

To set online

SET CWSON: SWT=ON

To enable alarm switch

SET FMT: STS=ON

To enable format conversion switch

FMT

To format data

Power off and load data

To reset all boards or unplug the WSMU

After loading data, check the working state of all boards. If all boards are working normally, it indicates that the equipment data has been configured successfully and completely.

2.7 Configuration Example 2.7.1 Example Description Suppose a single cabinet is configured, whose configurations are as follows: z

One integrated configuration cabinet.

z

One basic frame.

z

Subscriber capacity: 150,000. 2-21



The WIFM of the control unit frame integrates the functions of the WBSG, WMGC

z

and WIFM. The WEPI must be installed in the back slots 0, 1, 2 and 3. The ones in back slots

z

0 and 2 are active, providing E1 interface; the others in back slots 1 and 3 are standby without interfaces. It locks the clock reference source from MGW through E1 6 of slot 0 and E1 0 of slot 2 of the two WEPIs providing E1 cables, providing four 2-Mbit/s clock signals to the active/standby WCKIs (two signals for each WCKI). See Figure 2-2 for the board positions. MGW UNIT(Clock 2) HLR

MGW UNIT(Clock 1)

SCP

MSC SERVER

SMC

PSTN

SGSN

BSC

GMLC

RNC 0

1

2

3

W E P I

W E P I

W E P I

W E P I

W C Front S U

W C S U

W C S U

W C S U

W C C U

W C C U

W S M U

1

2

3

4

5

6

Back

0

4

5

6

7

8

9

10 11 12 13 14 15 16 17 18 19 20

W S I U

W H S C

W S I U

W H S C

W B F I

W B F I

W I F M

W I F M

W S M U 7

8

9

Figure 2-2 Board positions in MSOFTX3000

2-22

W C K I W V D B

W V D B

W C D B

W C K I W C D B

W A L U

U P W R

U P W R

U P W R

U P W R

10 11 12 13 14 15 16 17 18 19 20

Backplan e



Refer to Table 2-16 for the equipment data table. Table 2-16 Equipment data table Frame type

Frame number

Site number

Row number

Column number

Basic frame

0

1

1

1

Board type

Frame number

Slot number

Front/back

Module number


WCSU

0

0

Front

22

1

WCSU

0

1

Front

22

0

WCSU

0

2

Front

23

3

WCSU

0

3

Front

23

2

WCCU

0

4

Front

25

5

WCCU

0

5

Front

25

4

WIFM

0

10

Front

132

11

WIFM

0

11

Front

132

10

WVDB

0

12

Front

102

13

WVDB

0

13

Front

102

12

WCDB

0

14

Front

103

15

WCDB

0

15

Front

103

14

WEPI

0

0

Back

WEPI

0

1

Back

WEPI

0

2

Back

WEPI

0

3

Back

WCKI

0

13

Back

WCKI

0

15

Back

IP address of FE port

IP address of router connecting to MSOFTX3000


173.20.200.132

173.20.200.253

64 kbit/s



Frame/slot/E1 number of the WEPI providing clock reference

Non-balanced

DF

0/0/6, 0/2/0

2-23



2.7.2 Configuration Description //Set offline. LOF:;

//Turn off alarm switch. SET CWSON: SWT=OFF;

//Turn off format conversion switch. SET FMT: STS=OFF;

//Add shelf. ADD SHF: SN=0, LT=" SX4", PN=1, RN=1, CN=1;

//Add frame. ADD FRM: FN=0, SN=0, PN=2;

//Add board and module number. ADD BRD: FN=0, SN=0, LOC=FRONT, BT=WCSU, MN=22, ASS=1, LNKT=LINK_64K; ADD BRD: FN=0, SN=2, LOC=FRONT, BT=WCSU, MN=23, ASS=3, LNKT=LINK_64K; ADD BRD: FN=0, SN=4, LOC=FRONT, BT=WCCU, MN=25, ASS=5;

ADD BRD: FN=0, SN=10, LOC=FRONT, BT=WIFM, MN=132, ASS=11; ADD BRD: FN=0, SN=12, LOC=FRONT, BT=WVDB, MN=102, ASS=13; ADD BRD: FN=0, SN=14, LOC=FRONT, BT=WCDB, MN=103, ASS=15;

ADD BRD: FN=0, SN=0, LOC=BACK, BT=WEPI; ADD BRD: FN=0, SN=1, LOC=BACK, BT=WEPI; ADD BRD: FN=0, SN=2, LOC=BACK, BT=WEPI; ADD BRD: FN=0, SN=3, LOC=BACK, BT=WEPI; ADD BRD: FN=0, SN=13, LOC=BACK, BT=WCKI; ADD BRD: FN=0, SN=15, LOC=BACK, BT=WCKI;

//Add FE interface information of the WIFM. ADD

FECFG:

MN=132,

IP="173.20.200.132",

DGW="173.20.200.253";

//Set E1 and clock data. 2-24

MSK="255.255.0.0",



SET CKICFG: CL=LEVEL2, WM=AUTO, B1P=L3, B2P=L4, L1P=L1, L2P=L2; ADD EPICFG: FN=0, SN=0, E0=DF, E1=DF, E2=DF, E3=DF, E4=DF, E5=DF, E6=DF, E7=DF, BM=NONBALANCED; ADD EPICFG: FN=0, SN=2, E0=DF, E1=DF, E2=DF, E3=DF, E4=DF, E5=DF, E6=DF, E7=DF, BM=NONBALANCED; ADD BOSRC: FN=0, SN=0, EN=6; ADD BOSRC: FN=0, SN=2, EN=0;

//Set online. LON:;

//Turn on alarm switch. SET FMT: STS=ON;

//Format the data. FMT:;

Power off and on, and load data of all modules.

2-25


Chapter 3 Configuring Office Data

Chapter 3 Configuring Office Data 3.1 Introduction to the Chapter This chapter describes the information that needs to be configured when MSOFTX3000 serves as an MSC Server. This chapter contains the following sections: z

Concepts Related to Office Data

z

Collecting Office Data

z

Configuring Office Data

z

Setting MSRN/HON Allocation Mode

z


3.2 Concepts Related to Office Data 3.2.1 Local Office Information Before configuring service data, you need to set the local office information, that is, to set the properties of the local MSC Server, including office type, signaling point (SP) code of the local office, signaling network to which the office belongs, whether the office is a signaling transfer point (STP), whether the office supports signaling connection control part (SCCP), and so on.

3.2.2 MSC Number and VLR Number MSC/VLR number adopts E.164 coding mode, and the coding format is country code (CC) + national destination code (NDC) + locally significant part (LSP). In this format, the meanings of CC and NDC are consistent with the specifications of mobile station international ISDN number (MSISDN), and LSP is the number used in SS7 signaling messages to stand for MSC. Currently, MSC and VLR are configured together in the network. Therefore, MSC number is the same as VLR number.

3-1



3.2.3 Multiple Signaling Points One physical node can be logically divided into multiple SPs, each of which can separately connect with other SPs. Because there are a maximum of 16 signaling links between two SPs, the multi-SP mode can be used to break through the limitation to 16 signaling links between two offices.

3.2.4 Mutual-Assistant Nodes For local SPs, multiple virtual SPs to the same destination are the mutual-assistant nodes. If a fault occurs to the link between one of the local SPs and the peer office, the link of the mutual-assistant node can be used to transmit signaling messages, thus enhancing the reliability of the system.

3.3 Collecting Office Data Before configuring office data, you need to collect the office data of MSOFTX3000 as listed in Table 3-1. In the shadowy columns are the parameters that require consistency between two ends, and the others are internal parameters of MSOFTX3000.

3-2



Table 3-1 List of MSC Server office data to be collected Item Signaling point

Data National valid

network

National reserved network

International network

International reserved network

Local MSC number

Local VLR number


Network (NC)

Nation code

Region code

ODB_SS


Cipher algorithm?

Reallocate TMSI during service access and location update procedure?

Support VLR location update?

Check IMEI or contain IMEI in bill during service access and location update procedure?

Support HPLMN CFNRC?


Support SMMO/SMMT function?

Support prepage?

MAP/CAMEL version

Support call hold?

Support interface?

/ Mobile network data / /

code

/ MAP information

Identify user?

/

/

/ / / /

Gs

Support enhanced roaming restriction?

/

Note: During installation process, set the IP address of iGWB (the billing gateway) to “172.20.200.1”. Select “True” for the parameter “BILLSERVEREXIST” in the command SET INOFFMSC and billing function is enabled. For further information on iGWB, refer to iGateway Bill User Manual.

3-3



3.4 Configuring Office Data 3.4.1 Before Configuration I. Parameter Relationship in Local Office Data The commands for configuring office data and their parameter relations are shown in Figure 3-1. SET OFI/ADD OFI

[National Network Code] [National Reserved Network Code] [Local Area Code]

ADD SCCPSSN [Network indicator] [SSN] [SPC] [OPC]

[Nation/Region] [Inter MGW Media Type] ADD SCCPGT

SET INOFFMSC/ADD INOFFMSC [MSC Number] [VLR Number]

[SPC]

[MCC] [MNC]

[Network indicator] [GT address information]

ADD VLRCFG [MCC] [MNC] [CC]

Figure 3-1 Parameter relationship of commands for configuring office data

II. General Configuration Procedures See Table 3-2 for the procedures and commands for adding office data. Table 3-2 Procedures for configuring office data Procedure

Command

1: Set local office information

SET OFI/ADD OFI

2: Set local mobile network information

SET INOFFMSC/ADD INOFFMSC

3: Set local VLR information

ADD VLRCFG

4: Set local MAP information

ADD MAPACCFG

5: Set local SCCP subsystem

ADD SCCPSSN

6: Set GT of local SCCP subsystem

ADD SCCPGT

3-4



3.4.2 Setting Local Office Information I. Background Information Currently, MSOFTX3000 supports multi-SP configuration at the local office. The local office data index added for the first time is "0". If there are more than 16 signaling links between two offices, use the command ADD OFI to add SPs to break the number limitation of signaling links. In addition, signaling load sharing can be achieved. When using the command ADD OFI to add other SP codes, the local office SP index is incremented from 1.

II. Command SET OFI/ADD OFI

III. Major Parameters [Local type] This parameter is used to define the office type of MSOFTX3000 in the network. Select the office type according to the actual conditions of the local office. For an end office, usually LOCMSC(MSC local office) is selected. [International Network Valid] [International Reserved Network Valid]] [National Network Valid] [National Reserved Network Valid] MSOFTX3000 supports that the local office exists in four networks at the same time: international network, international reserved network, national network, and national reserved network. When MSOFTX3000 serves as an end office in the national network and national reserved network at the same time, set the parameters "National Network Valid" and "National Reserved Network Valid" to "YES" and the other two parameters to "NO". When MSOFTX3000 serves as a gateway office in the national network, set "National Network Valid" to "YES". [Network 1] [Network 2] [Network 3] [Network 4] These parameters are used to set the order of network search. After the order is set, only the valid networks will be searched to avoid wasting system resources. When MSOFTX3000 serves as an end office in the national network and national reserved network at the same time, set "Network 1" and "Network 3" to "National" and the other two parameters to "National Reserved". When MSOFTX3000 serves as a

3-5



gateway office in the national network, set the four parameters to "National". The NI in the ADD OFI command is consistent with that in the SET OFI command. [International Network Code] [International Reserved Network Code] [National Network Code] [National Reserved Network Code] These parameters are used to set the codes of SPs with hexadecimal notation. When setting signaling codes, you only need to enter the valid signaling code defined previously. [International Network Structure] [International Reserved Structure] [National Network Structure] [National Reserved Structure] These parameters are used to indicate the signaling code structures in various networks. The length of a SP code in a national network is 24 bits, and the length of a SP code in an international network and a national reserved network is 14 bits. [Transmission Allowed Delay] This parameter is set only for ultra-long distance circuit and satellite circuit. The default value is 0 second. [SP Function] This parameter is used to set whether the office provides SP function. The MSC Server must have the SP function for transmitting SS7 messages. In this case, set this parameter to "YES". [STP Function] This parameter is used to set whether the office provides STP function. Generally, set this parameter to "NO". If the local office is an STP, set this parameter to "YES". [Restart Function] This parameter is used to set whether the MTP links of the office support restart function. This parameter is valid only when "STP Function" is set to "YES". Generally, it is set to "NO". [Local Area Code] [Nation/Region Code] These parameters are used to set the code of the country or area where the office is. For example, the country code of China is 86. Set the area code based on different regions. [Packet Network Access Code] This parameter is used to indicate the packet access function provided by the office. [CFNR To Voice Mailbox], [CFB To Voice Mailbox]

3-6



These two parameters specify the voice mailbox as the destination for call forwarding on no reply (CFNR) and call forwarding busy (CFB). They are not used in mobile network. [InterMGWMediaType] This parameter indicates the bearer type among multiple MGWs connected to MSOFTX3000. The bearer types include Internet protocol (IP), asynchronous transfer mode (ATM) and TDM. Set one among them according to the actual networking. For bearer over ATM, select "AAL2".

IV. Related Commands See Table 3-3 for the commands related to office information configuration. Table 3-3 List of commands related to office information configuration Command

Description

SET OFI

To set local office information

ADD OFI

To add a set of local SP codes

RMV OFI

To remove a set of local SP codes

LST OFI

To list local office information

MOD OFI

To modify local office information

Note: The commands ADD OFI, RMV OFI, MOD OFI are used only to configure multiple SP code data, but are not used for configuring local office data.

You can use the MOD OFI command to modify the mutual-assistant node information of the local SP, such as modifying the mutual-assistance relationship between local SPs. If a fault occurs to the MTP3 signaling link between one of the local SPs and the peer office, the link of the mutual-assistant node can be used to transmit signaling messages, thus enhancing the reliability of the system. One SP can have a maximum of two mutual-assistant SPs.

3.4.3 Setting Local Mobile Network Information I. Background Information None

3-7



II. Command SET INOFFMSC/ADD INOFFMSC

Important Note: When adding multiple SPs, you need to add relevant MSC data as well. One MSOFTX3000 can be configured with 16 MSCs in maximum, and each MSC has its own local office information. Use the command SET INOFFMSC to configure the first MSC and ADD INOFFMSC to configure the other MSCs.

III. Major Parameters [MSC Number] [VLR Number] These parameters are used to set the MSC number and VLR number of the local office. Generally, these two numbers are the same. The MSC number set in the ADD INOFFMSC command is consistent with that set in the SET INOFFMSC command. [EIR Number] This parameter is used to set equipment identity register (EIR) number of the local office. Currently, the EIR function is not provided, so enter no value for this parameter. [Mobile Country Code]( MCC) This parameter is used to set the mobile country code (MCC) of the office. For example, the mobile country code of China is 460. [Mobile Network Code]( MNC) This parameter is used to set the code of the mobile network to which the office belongs. For example, the MNC of China Mobile is 00. [Location Number] This parameter represents the zone code of the area in which the office is configured. It is used for zone code restriction service. [International Number Prefix] This parameter is used to set the prefix of international toll calls. For example, the international prefix of China is 00. [National Prefix] This parameter is used to set the prefix of national toll calls. For example, the national prefix of China is 0. 3-8



[BillServerExist] Generally, set this parameter to "TRUE" as the MSC Server needs bill server.

IV. Related Commands See Table 3-4 for the commands related to the configuration of local mobile network information. Table 3-4 List of commands related to local mobile network information configuration Command

Description

ADD INOFFMSC

To add local mobile network information

RMV INOFFMSC

To remove existing local mobile network information

MOD INOFFMSC

To modify existing local mobile network information

LST INOFFMSC

To list local mobile network information

3.4.4 Adding Local VLR Information I. Background Information None

II. Command ADD VLRCFG

III. Major Parameters [Maximum No of Users] This parameter is used to set the maximum user number allowed by each VLR module. If an office supports up to 350,000 users, two VLR modules are required as each one supports up to 200,000 users. If the maximum user number of each module is set to 180,000, set this number for the parameter "Max. user". [Mobile Country Code], [Mobile Network Number] MCC and MNC refer to mobile country code and mobile network code respectively. Their values are the same as those set in the SET INOFFMSC command. [Country Code]

3-9



This parameter is used to set country code. For example, the country code of China is 86. [MSRN Release Timeout(sec)] This parameter refers to the roaming number auto-release time. The default value is 90 seconds. A timer shall be started when a roaming number is allocated. If the VLR does not receive any release command, the roaming number will be automatically released by the timer, so that this number can be used again. [User Purge Timer(hrs)] This parameter is used to define the time for deleting subscribers. The default value is 24 hours. User purge time is the time during which a subscriber in the VLR has not made any call for a long time, and there is no periodic location update either (that is, the subscriber does not perform any message interaction with the VLR), the VLR is allowed to delete the subscriber. For example, if this parameter is set to 24 hours, when the subscriber’s mobile phone is powered off for more than 24 hours, VLR will delete this subscriber automatically. The time set here must be larger than the periodic location update time. [Implicit IMSI Detach Timer(min)] The default value is 120 minutes. The implicit international mobile subscriber identity (IMSI) detach timer is to set the duration after which the mobile phone should initiate periodic location update if a subscriber has no service interaction. If the MS has not performed a location update within the implicit IMSI detach time, the system will set the subscriber to IMSI-DETACH state. The periodic location update time is set in BSC or RNC, and the value should be smaller than the implicit IMSI detach time set in VLR. [Authent Param Reuse Times] This parameter is used to define the times allowed to use the authentication set. Generally, its value is set to "0". [MSRN Allocation Mode] It defines roaming number allocation mode. The MSRN can be allocated according to MSC number, LAI number, or randomly. [HON Allocation Mode] It defines handover number (HON) allocation mode. The handover number can be allocated according to MSC number, LAI number, or randomly. [IMEI Reuse Times]

3-10



It defines the reuse times of IMEI. To reduce the traffic of message interactions with the mobile station side, the network side can reuse the IMEI within its valid range instead of obtaining IMEI from the mobile station every time.

Important Note: The commands involving [MSRN Allocation Mode] and [HON Allocation Mode] also include: ADD/MOD/RMV/LST MHPREFIX, ADD/MOD/RMV/LST MHSUFFIX, ADD/ RMV/LST MHMSCCFG, ADD/ RMV/LST MHLAICFG If [MSRN Allocation Mode] and [HON Allocation Mode] was not configured, it would be impossible to allocate MSRN and HON.

IV. Related Commands See Table 3-5 for the commands related to VLR information configuration. Table 3-5 List of commands related to VLR information configuration Command

Description

ADD VLRCFG

To add VLR information

LST VLRCFG

To list VLR information

MOD VLRCFG

To modify VLR information

3.4.5 Adding MAP Information I. Background Information None

II. Command ADD MAPACCFG

III. Major Parameters [Identify User] If it is set to “Yes”, it means that IMSI authentication is required if TMSI authentication fails during service access or location update procedure. The value shall be specified according to the actual requirement.

3-11



[ODB_SS] It is used to decide supplementary services to be barred. There are 10 fields for this parameter and multiple fields can be selected to indicate the operator determined barring (ODB) services supported by the local office. z

All outgoing calls barred

z

International outgoing calls allowed or barred

z

International outgoing calls except those to the home PLMN country barred

z

Premium rate information outgoing calls barred

z

Premium rate entertainment outgoing calls barred

z

Supplementary service access barred

z

Operator Determined Barring Type 1–4 (user-defined fields)

[Cipher] This parameter indicates whether the information to be transferred needs encrypting. The MSOFTX3000 can control whether to cipher 2G and 3G respectively. [Cipher Algorithm] Select a cipher algorithm if it is needed. There are eight 2G cipher algorithm options (NOCIPH2G, A5_1 to A5_7) and two 3G cipher algorithm options (NOCIPH3G and UEA1) available. You can select several of them simultaneously. If you select “CIPHER FOR 2G” for the parameter “Cipher”, you must select a 2G cipher algorithm. Similarly, if you select “CIPHER FOR 3G” for “Cipher”, you must select a 3G cipher algorithm. If both 3G cipher algorithms are selected, UEA1 has higher priority. If 2G cipher is not needed, select “CIPHER FOR 2G” for the parameter “Cipher” and “NOCIPH2G” for the parameter “Cipher Algorithm”. If 3G cipher is not needed, select “CIPHER FOR 3G” for the parameter “Cipher” and “NOCIPH3G” for the parameter “Cipher algorithm”. [Allocate TMSI When Update Location] This parameter defines whether TMSI reallocation is performed in location update procedure. The value can be specified according to the actual conditions. [Allocate TMSI When Service Access] This parameter indicates whether TMSI reallocation is performed in call services, supplementary services, and short message services. [Support VLR Update Location] It defines whether location update is supported in VLR. If this parameter is set to “Yes”, it means that the location update procedure can be continued in VLR, when the session establishment to HLR fails and HLR terminates the session or HLR response duration times out during a normal location update procedure.

3-12



[Support HPLMN CFNRC] It defines whether home PLMN (HPLMN) call forwarding on mobile subscriber not reachable (CFNRC) is supported. When a called party is not reachable, “Yes” means forwarding in GMSC and “No” means forwarding in visited mobile switching center (VMSC). The default selection is “Yes". [Support Zone Code Restriction] It defines whether the roaming restriction of zone code is supported. “Yes” means that when a subscriber roams to an area with a zone code that does not match any of the subscribed zone codes, MSC will restrict the roaming. [Support SMMO Function] It defines whether short message mobile originated (SMMO) function is supported on mobile phones. [Support SMMT Function] It defines whether short message mobile terminated (SMMT) function is supported on mobile phones. [Support Prepage] It defines whether prepaging is supported. Prepaging means that VLR starts paging immediately after receiving the message “provide roaming number” (PRN), and then it returns “PRN_ACK” to HLR after receiving “PAGING RESPONSE”. [MAP Version] It defines MAP versions: MAP_PHASE1, MAP_PHASE2, and MAP_PHASE2+. It is recommended to select “MAP PHASE 2+”. [CAMEL Version] It

defines

CAMEL

versions:

CAMEL_PHASE1,

CAMEL_PHASE2,

and

CAMEL_PHASE3. If CAMEL subscribers are not supported, select “Not Supported”. Select it according to the actual networking mode. [Support Call Hold] It defines whether call hold is supported in the local office. [Support Gs Interface] It defines whether the Gs interface is supported between SGSN and MSC/VLR. Select “Yes”. [Use Enhanced Roaming Restriction] It defines the roaming restriction for specific areas, for instance, location area. 3-13



[Use AC Buffer] This parameter defines whether to use AC version buffer system. If "Yes" is set, add the valid bit length for some numbers because the version buffer system has upper limit (10) and lower limit (7) for valid bits.

IV. Related Commands See Table 3-6 for the commands related to MAP information configuration. Table 3-6 List of commands related to MAP information configuration Command

Description

ADD MAPACCFG

To add MAP information

MOD MAPACCFG

To modify existing MAP information

LST MAPACCFG

To list existing MAP information

3.4.6 Adding Local SCCP Subsystem I. Background Information When MSOFTX3000 functions as a visited MSC, configure the local MSC, VLR and SCCP management subsystem (SCMG). When MSOFTX3000 functions as a gateway mobile switching center (GMSC), configure the local MSC and SCMG subsystems. To add local SCCP subsystems, run the command ADD SCCPSSN repeatedly.

II. Command ADD SCCPSSN

III. Major Parameters [SSN Index] It indicates the SCCP subsystem index, which is uniquely numbered throughout the entire system. [NI] This parameter is used to set the indicator of the network where the SCCP subsystem is located. Generally, select "NATIONAL NETWORK" for the local MSC and VLR subsystems.

3-14



[SSN] This parameter refers to a subsystem. Select MSC, VLR, or SCMG subsystem according to the requirement. [SPC] [OPC] Both of the parameters are national network SP codes of the local office for local MSC and VLR subsystems. They are associated with the parameters defined in the SET OFI command. [local concerned SSN1] – [local concerned SSN5] Because there is no related subsystem, select “Undefined”. [Backup SSN Index] Because there is no backup subsystem, select the default value “65535”.

IV. Related Commands See Table 3-7 for the commands related to SCCP subsystem configuration. Table 3-7 List of commands related to SCCP Subsystem configuration Command

Description

ADD SCCPSSN

To add SCCP subsystem

RMV SCCPSSN

To remove existing SCCP subsystem

MOD SCCPSSN

To modify existing SCCP subsystem

LST SCCPSSN

To list SCCP subsystem

SET SCCPSSN

To set SCCP subsystem status. This command is used during maintenance.

DSP SCCPSSN

To display SCCP subsystem in the host

3.4.7 Adding Local SCCP GT I. Background Information It is necessary to set the local MSC GT and VLR GT for addressing. For more information about configuring SCCP GT to HLR, refer to Chapter 7 of this manual.

II. Command ADD SCCPGT 3-15



Important Note: Because MSC and VLR are integrated, the MSC GT and VLR GT are the same. In this case, it is only required to execute the command ADD SCCPGT once.

III. Major Parameters [NI] For the local MSC/VLR, set this parameter to "National Network". The network indicator is associated with that defined in the ADD SCCPSSN command. [GT indicator] There are four classes of GTs in the mobile network. Select "GT4 (TYPE4)” generally. [Translation type] Select the default value "00" for the mobile network. [Numbering Plan] Select "ISDN (ISDN/TELEPHONY NUMBERING PLAN)" for MSC/VLR. [GT address information] Enter MSC number/VLR number for this parameter. [Translation result type] For local SCCP users, set it to "SPC". [SPC] For the local MSC/VLR subsystem, enter the national network SP code. This parameter is associated with the "SPC" defined in the SET OFI command.

IV. Related Commands See Table 3-8 for the commands related to SCCP GT configuration. Table 3-8 List of commands related to SCCP GT configuration Command

Description

ADD SCCPGT

To add SCCP global title

RMV SCCPGT

To remove existing SCCP global title

3-16



Command

Description

MOD SCCPGT

To modify existing SCCP global title

LST SCCPGT

To list SCCP global title

3.5 Setting MSRN/HON Allocation Mode 3.5.1 Introduction to MSRN/HON Allocation I. Allocation Modes MSOFTX3000 can flexibly implement the following MSRN/HON allocation modes: z

Allocating MSRN/HON based on LAI number

z

Allocating MSRN/HON based on MSC number

z

Allocating MSRN/HON randomly

You can set MSRN/HON prefixes and segments respectively corresponding to LAI and MSC.

II. Parameter Relationship See Figure 3-2 for the relationship between MSRN/HON allocation parameters. The former two tables must be configured, and the latter two correspond to different allocation modes, which need to be customized according to requirement. The dotted line indicates that MSRN/HON allocation mode is determined by the parameters of the ADD VLRCFG command, and indicates that whether the subsequent command used is ADD MHLAICFG or ADD MHMSCCFG. ADD VLRCFG [MSRN Allocation Mode] [HON Allocation Mode]

ADD MHLAICFG ADD MHPREFIX [MSRNHON Prefix Index] [MSRNHON Prefix] [MSRNHON Suffix Length]

ADD MHSUFFIX [MSRNHON Suffix Index] [MSRNHON Prefix Index] [MSRNHON Suffix Start] [MSRNON Suffix End] [MSRNHON Number Type]

[LAI Number] [MSRNHON Suffix ID]

ADD MHMSCCFG [MSC Number] [MSRNHON Suffix ID]

Figure 3-2 Relationship between MSRN/HON allocation parameters

3-17



III. General Configuration Procedures Table 3-9 lists the procedures and commands for configuring MSRN/HON allocation mode. Table 3-9 Procedures for setting MSRN/HON allocation mode Procedure

Command

1: Add MSRN prefix

ADD MHPREFIX

2: Add MSRN suffix

ADD MHSUFFIX

3: Add corresponding relationship between MSC and MSRN

ADD MHMSCCFG

4: Add corresponding relationship between LAI and MSRN

ADD MHLAICFG

3.5.2 Adding MSRN/HON Prefix I. Background Information None

II. Command ADD MHPREFIX

III. Major Parameters [ID] It is the MSRN/HON prefix index. [MSRNHON Prefix] MSRN/HON prefix is composed of binary coded decimal (BCD) codes of 1–14 digits, for example, 861390000. This parameter is associated with the parameter “Call Prefix” in the ADD CNACLD command when the parameter “Called Number Type” in the ADD CNACLD command is set to "MSRN/HON". The MSRN prefix here can contain the prefix of the called number analysis table, but its total length (MSRN prefix length plus suffix length) is between the minimum length and maximum lenth of the prefix of the called number analysis table. The MSRN prefix includes country code and network access code. The former is added in the command SET OFI, and the latter is added in the command ADD NACODE.

3-18



[MSRNHON Suffix Length] The length of MSRN/HON suffix is 2–4 digits.

IV. Related Commands See Table 3-10 for the commands related to MSRN prefix configuration. Table 3-10 List of commands related to MSRN prefix configuration Command

Description

ADD MHPREFIX

To add MSRN prefix

MOD MHPREFIX

To modify MSRN prefix

LST MHPREFIX

To list MSRN prefix

RMV MHPREFIX

To remove MSRN prefix

3.5.3 Adding MSRN/HON Suffix I. Background Information None

II. Command ADD MHSUFFIX

III. Major Parameters [ID] It is the MSRN/HON suffix index. [MSRNHON Prefix ID] This parameter is already defined in the ADD MHPREFIX command. You can query it with the command LST MHPREFIX. [MSRNHON Suffix Start] This parameter is used to set the specific start digit of the MSRN/HON number. The 2to 4-digit suffix is composed of BCD codes ranging from 0 to 9, for example, 111. [MSRNHON Suffix End] This parameter is used to set the specific end digit of the MSRN/HON number. The 2- to 4-digit suffix is composed of BCD codes ranging from 0 to 9, for example, 999. 3-19



[MSRNHON Number Type] This parameter is used to set the type of the added number. It may be MSRN, HON or MSRN/HON.

IV. Related Commands See Table 3-11 for the commands related to MSRN suffix configuration. Table 3-11 List of commands related to MSRN suffix configuration Command

Description

ADD MHSUFFIX

To add MSRN suffix

MOD MHSUFFIX

To modify MSRN suffix

LST MHSUFFIX

To list MSRN suffix

RMV MHSUFFIX

To remove MSRN suffix

3.5.4 Adding Corresponding Relationship Between LAI and MSRN I. Background Information None

II. Command ADD MHLAICFG

III. Major Parameters [LAI Number] It is already defined in the command ADD LAIGCI/ADD LAISAI. [MSRNHON Suffix ID] You can query this parameter with the command LST MHSUFFIX.

IV. Related Commands See Table 3-12 for the commands related to the configuration of corresponding relationship between LAI and MSRN.

3-20



Table 3-12 List of commands related to configuration of corresponding relationship between LAI and MSRN Command

Description

ADD MHLAICFG

To add corresponding relationship between LAI and MSRN

LST MHLAICFG

To list corresponding relationship between LAI and MSRN

RMV MHLAICFG

To remove corresponding relationship between LAI and MSRN

3.5.5 Adding Corresponding Relationship Between MSC and MSRN I. Background Information None

II. Command ADD MHMSCCFG

III. Major Parameters [MSC Number] It is already defined in the command ADD INOFFMSC. [MSRNHON Suffix ID] You can query this parameter with the command LST MHSUFFIX.

IV. Related Commands See Table 3-13 for the commands related to the configuration of corresponding relationship between MSC and MSRN. Table 3-13 List of commands related to configuration of corresponding relationship between MSC and MSRN Command

Description

ADD MHMSCCFG

To add corresponding relationship between MSC and MSRN

LST MHMSCCFG

To list corresponding relationship between MSC and MSRN

RMV MHMSCCFG

To remove corresponding relationship between MSC and MSRN

3-21



3.6 Configuration Example 3.6.1 Example Description Suppose the networking model is as shown in Figure 3-3.

SCP

SMC

MSC Server

MAP/ TDM

MAP/ TDM

MAP/ TDM

MAP/ TDM

MSOFTX 3000

ISUP/ TDM

GMLC

HLR

H.248,RANAP /IP

BSSAP+

SGSN

/TDM

ISUP,BSSAP / TDM SPC

MGW

MGW

IP/TDM

ISUP/TDM

PSTN

(SG)

RANAP/ AAL2 /ATM

BSSAP/ TDM

RNC

BSC

Figure 3-3 Networking of MSOFTX3000 If MSOFTX3000 serves as a VMSC Server, the local office information is as shown in Table 3-14.

3-22



Table 3-14 Local office information table Item Signaling point

Mobile network data

Data National network valid

National reserved network valid

CC0004

C04

Local number

MSC

International network valid

International reserved network valid

Nation code

Region code

Local VLR number

/

8613600004

8613600004

/


Network (NC)

/

460

00

86

755

Identify user?

ODB_SS


Cipher algorithm?

/

No

All

No

No

/

Reallocate TMSI during service access and location update procedure?

Support VLR location update?

Check IMEI or contain IMEI in bill during service access and location update procedure?

Support HPLMN CFNRC?

/

No

No

No

No

/


Support SMMO/SMMT function?

Support prepage?

MAP/CAMEL version

/

No

Yes

No

MAP_PHASE2+/ CAMEL_PHASE 3

/

Support call hold?

Support interface?

/

Yes

No

MAP information

3-23

code

Gs

Support enhanced roaming restriction? No



LAI number allocation mode is used for MSRN/HON, which includes two number segments, as shown in Table 3-15. Table 3-15 An example of MSRN/HON numbering Cell

MSRN/HON

Prefix index

Suffix index

LAI number

2G cell

86136000040001–86136000040999

0

0

460000001

3G cell

86136000041000–86136000041999

0

1

460000003

3.6.2 Configuration Description //Set local SP information. SET OFI: OFN="SX4", LOT=CMPX, NN=YES, NN2=YES, SN1=NAT, SN2=NAT2, SN3=NAT, SN4=NAT2, NPC="CC0004", NP2C="C04", NNS=SP24, NN2S=SP14, LAC=K'755, LNC=K'86, GAC=K'139;

//Set local mobile office information. SET INOFFMSC: MSCN=K'8613600004, VLRN=K'8613600004, MCC=K'460, MNC=K'00, INNATIONPFX=K'00, NATIONPFX=K'0;

//Add VLR information and MSRN/HON number allocation mode. ADD

VLRCFG:

MAXUSR=12000,

MCC=K'460,

MNC=K'00,

CC=K'86,

MSRNAM=LAI,

HONAM=LAI;

//Add MAP data. ADD

MAPACCFG:

IFIDPROC=NO,

ODBSS=ACOB-1&ICOB-1&ICOBNHP-1&ICB-1&ECB-1&SSAB-1&PSBT1-1&PSBT2-1&PSBT3-1&P SBT4-1, IFCIPH=CIPH2G-0&CIPH3G-0, IFALTMSILU=NO, IFALTMSISA=NO, IFVLRLU=NO, IFFWD=YES,

IFSZCD=NO,

ISSSMMO=YES,

ISSSMMT=YES,

MAPVER=PHASE3,

CAMELVER=PHASE3, SUPGSIE=YES, IFUSROAMR=NO, IFUSACBUF=NO;

//Add local SCCP subsystem, including MSC, VLR and SCMG subsystems. ADD

SCCPSSN:

SSNX=0,

NI=NAT,

SSN=MSC,

SPC="CC0004",

OPC="CC0004",

NI=NAT,

SSN=VLR,

SPC="CC0004",

OPC="CC0004",

NI=NAT,

SSN=SCMG,

SPC="CC0004",

OPC="CC0004",

SSNNAME="LOCAL-MSC"; ADD

SCCPSSN:

SSNX=1,

SSNNAME="LOCAL-VLR"; ADD

SCCPSSN:

SSNX=2,

SSNNAME="LOCAL-SCMG";

3-24

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center ADD

SCCPSSN:

SSNX=3,


NI=NATB,

SSN=SCMG,

SPC="C04",

OPC="C04",

SSNNAME="LOCAL-NATB-SCMG";

//Add local SCCP GT. ADD

SCCPGT:

GTX=0,

GTNAME="LOCAL-MSC",

NI=NAT,

TRANSLATETYPE="00",

NUMPLAN=ISDN, ADDR=K'8613600004, RESULTT=LSPC2, SPC="CC0004";

//Add call source code. ADD CALLSRC: CSC=0;

//Add MSRN/HON number allocation relationship: Number segments are allocated based on LAI. ADD NACODE: NAC=K'136;

ADD MHPREFIX: ID=0, HPFX=K'8613600004, SFXL=4; ADD MHSUFFIX: ID=0, PFXIDX=0, SFXS="0001", SFXE="0999", MSRNT=MSRNHON;

//The

index is 0 for suffix 0001~0999. ADD MHSUFFIX: ID=1, PFXIDX=0, SFXS="1000", SFXE="1999", MSRNT=MSRNHON;

//The

index is 1 for suffix 1000–1999. LST MHSUFFIX;

//List the index relationship between prefix and suffix.

ADD MHLAICFG: LAI="460000001", PRESFX=0; //The MSRN/HON for 2G cell is from 86136000040001 to 86136000040999, and the cell should be added first. ADD MHLAICFG: LAI="460000003", PRESFX=1; //The MSRN/HON for 3G cell is from 86136000041000 to 86136000041999, and the cell should be added first.

3-25


Chapter 4 Configuring Data for Interworking with MGW

Chapter 4 Configuring Data for Interworking with MGW 4.1 Introduction to the Chapter This chapter describes how to configure data for MSOFTX3000 interworking with MGW. It contains the following sections: z

Concepts Related to Data Configuration for Interworking with MGW

z

Collecting Data for Interworking with MGW

z

Configuring Data for Interworking with MGW

z


4.2 Concepts Related to Data Configuration for Interworking with MGW 4.2.1 Relationship Between MSC Server and MGW MGW cooperates with MSC Server to implement mobile switching functions of the core network. In R4 network, MGW responsible for service bearer and MSC Server responsible for call control are detached physically to implement different functions. MGW applies H.248 protocol (MGW control protocol) to communicate with MSC Server through the Mc interface.

4.2.2 Networking Between MSOFTX3000 and MGW MSOFTX3000 provides H.248 with three transport layer protocols: user datagram protocol (UDP), stream control transmission protocol (SCTP), and message transfer part 3 (broadband) (MTP3B). UDP and SCTP are based on IP, and MTP3B is based on ATM. In the current networking, bearer over IP/SCTP is adopted, of which the protocol stack structure is shown in Figure 4-1.

4-1


Chapter 4 Configuring Data for Interworking with MGW IP IP Mc

MSOFTX3000

MGW

H.248 SCTP IP MAC

Figure 4-1 Interface protocol structure between MSOFTX3000 and MGW

4.2.3 Parameter Relationship Figure 4-2 illustrates the referencing relationship between the parameters of MSOFTX3000 internal commands. ADD MGW [Transport Protocol] [MGW index] [Codec List] [Device Name] [Server/Client] [...]

ADD MCLNK ADD FECFG

[MGW index] [BSG/IFM/AFM/SGU/MGC Module No.]

[IFM Module Number]

[Local IP1] [Local Port]

[IP Address ] [Mask Address]

[Remote IP1] [Remote Port] [Transport Protocol]

SET SCTPPARA [Checksum Arithmeticr]

Figure 4-2 Parameter relationship between MSOFTX3000 internal commands

4-2



4.2.4 General Configuration Procedures Table 4-1 shows the procedures and commands for configuring interworking data between MSOFTX3000 and MGW. Table 4-1 Procedures and commands for configuring interworking data between MSOFTX3000 and MGW Procedure

Command

1: Negotiate and prepare data

/

2: Add MGW

ADD MGW

3: Add SCTP link to MGW

ADD MCLNK

4: Set SCTP Checksum Algorithm (optional)

SET SCTPPARA

5: Set tone playing capability of MGW (optional)

ADD/MOD TONECFG

4.3 Collecting Data for Interworking with MGW Before configuring data, you need to collect the data for interworking between MSOFTX3000 and MGW as listed in Table 4-2. In the shadowy columns are the parameters requiring consistency between two ends or notification to the peer end. Other fields are internal parameters of MSOFTX3000. Table 4-2 MGW information table Item Basic information

Data MGW index

Transport protocol

Voice coding/deco ding mode

Checksum mode

MGW ciphering algorithm and ciphering key (optional)

SCTP link No.

Local IP address of the WIFM

Local port number of the WIFM

Remote IP address of MGW

Remote port number of MGW

/ SCTP link information /

4-3

Server /client



4.4 Configuring Data for Interworking with MGW 4.4.1 Adding MGW I. Background Information None

II. Command ADD MGW

Note: This command is used to add a MGW, and to set its basic information and MGW capability.

III. Major Parameters [MGW Index] This parameter uniquely identifies an MGW in the system. [Control Module No.] This parameter sets the module number of the WMGC managing the gateway. The module number is set in the ADD BRD command, and you can query it with the command LST MDU. This parameter is used in gateway registration, link state maintenance, gateway state auditing, and handling of gateway faults. If the WIFM, WBSG and WMGC are combined into one board, set this parameter to the module number of the WIFM. [Transport protocol] Set this parameter according to the actual networking requirement. MSOFTX3000 provides such three transport protocols as UDP, SCTP, and MTP3B for the H.248 protocol. In the mobile network applications, you can select one of the following based on the actual networking conditions: z

Bearer over IP: SCTP and UDP

z

Bearer over ATM: MTP3B

Currently, IP/SCTP bearer mode is used. [BCU ID]

4-4



It specifies the identifier of the bearer control unit (BCU), and it identifies a physical MGW. It is unique and global in the network. It is used in bearer independent call control protocol (BICC). For H.248-based MGW, it is a mandatory parameter. [BNC character] It defines the bearer category supported by MGW. According to different service categories, it can be divided into TDM, IP, ATM adaptation layer type 1 (AAL1), AAL2, and AAL1Struct. z

ATM network: AAL1Struct, AAL1 or AAL2

z

IP network: IP

z

TDM network: TDM

[Special Attributes] It defines the special attributes of MGW in specific networking. The meanings of the options are as follows: z

SDP HEX: It defines whether the SDP packets sent by the MSOFTX3000 to the MG are in HEX format. Select this option only when the MG is the TMG8010 manufactured by Huawei. In the other cases, do not select it.

z

No BNC Character: Set it to “Yes” for universal media gateway (UMG), which means that UMG carries backbone network connection (BNC) character packet. As BNC character packet is not supported on access media gateway (AMG), TMG, integrated access device (IAD), or media resource server (MRS), this option is not configured.

z

No Echo Cancellation: It defines whether the MGCP/H.248 messages sent by the MSOFTX3000 to the MG contain no echo cancellation (EC) field.

z

No Jitter: It defines whether the MGCP/H.248 messages sent by the MSOFTX3000 to the MG contain no jitter buffer field.

z

No Fax: It defines whether to detect fax.

z

No Modem: It defines whether to detect modem.

z

Local SDP Address Present: It defines whether a local IP address is included when modifying a local codec. This parameter is mandatory only when MGW is IAD.

This parameter need not be set in the mobile network. The default value is used. [MGW Attribute] This parameter is used to set office type, such as local office and remote office. For different transport layer protocols supported by MGW, there are different configurations: z

SCTP configuration

[Device Name]

4-5



It specifies the device name. It should be the same as that defined in MGW. The parameter is valid only when MGW uses SCTP. [Server/Client] It specifies whether MGW acts as a server or client. Note that you must set one end of the SCTP link to Client, and the other end to Server; otherwise, the SCTP link cannot be established. Therefore, negotiation with MGW is necessary. Generally, set MSOFTX3000 to Server, and MGW to Client. The parameter is available when MGW uses SCTP. z

UDP configuration

[Domain Name] It specifies the domain name. It should be the same as that defined in MGW. The parameter is valid only when MGW uses UDP. z

MTP3B configuration

[MTP Name] It specifies the MTP name. It should be the same as that defined in MGW. The parameter is valid only when MGW applies MTP3B. The following parameters are used to encrypt stack information: [Encryption type] This parameter is used to set encryption type, including MD5, SHA1 and Not Supported. It is used to encrypt or decrypt protocol stack information. Use the default value. [Security Parameters Index] [Sequence Number] [Key length] They are parameters for interconnection between MSOFTX3000 and MGW, used for encrypting stack information. The following parameters are used to set MGW capability set: [Capability] It specifies the MGW capabilities, including Tone, Playing Announcement, Sending dual tone multi-frequency (DTMF), Detecting DTMF, Multiparty, and interworking function (IWF). [Rate of EC] This parameter is used to control echo cancellation capability. Set it according to the actual capability of MGW, and it should be larger than 0. The recommended value is 300. [Rate of IWF]

4-6



This parameter refers to the IWF capability. Set it according to the actual capability of MGW, and it should be larger than 0. The recommended value is 300. [Rate of TC] This parameter is used to set the coding/decoding capability. Set it according to the actual capability of MGW, and it should be larger than 0. [Rate of TONE] MGW supports playing tone. Set the parameter according to the actual capability of MGW, and it should be larger than 0. The recommended value is 300. [Rate of Multiparty] This parameter is used to set the multiparty service capability of MGW. Set it according to the actual capability of MGW, and it should be larger than 0. [Rate of Detect DTMF] Set this parameter according to the actual capability of MGW, and it should be larger than 0. The recommended value is 300. [Rate of Send DTMF] Set it according to the actual capability of MGW, and it should be larger than 0. The recommended value is 300. [HR AMR Rate] It specifies the rate of the half rate (HR) adaptive multi-rate (AMR). [UMTS AMR2 Rate] It specifies the rate of UMTS AMR2. [FR AMR Rate] It specifies the rate of full rate (FR) AMR. [UMTS AMR Rate] It specifies the rate of UMTS AMR. [IWF Modem List] This parameter is used to define the types of modems supported by MGW. You can select according to the actual situation. [Codec List] This parameter is used to define the codec types supported by MGW, such as PCMA, PCMU, and G7231. You can select according to the actual situation.

4-7



[Main Type] This parameter is used in dual-homing configuration to configure the master/slave type of the MGW. In case of dual-homing, configure according to the actual situation; otherwise, use the default value, that is, TRUE (Master MGW).

IV. Related Commands See Table 4-3 for the commands related to MGW configuration. Table 4-3 List of commands related to MGW configuration Command

Description

ADD MGW

To add MGW

RMV MGW

To remove MGW

MOD MGW

To modify attributes of MGW

LST MGW

To list attributes of all MGWs

DSP MGW

To display attributes of MGW of the host

4.4.2 Adding SCTP Link to MGW I. Background Information None

II. Command ADD MCLNK

Important Note: This command is used to add a link used by the Mc interface configured to certain MGW based on corresponding transport protocol (UDP, MTP3B, or SCTP). For UDP/MTP3B, execute this command only once. For SCTP, you can set five links to one MGW.

III. Major Parameters [MGW Index]

4-8



This parameter is used to identify the MGW to which an SCTP link is to be established. It is associated with the parameter "MGW Index" defined in the ADD MGW command. [Transport Protocol] Set this parameter according to the actual networking requirement. MSOFTX3000 provides such three transport protocols as UDP, SCTP, and MTP3B for H.248 protocol. In the mobile network applications, you can use one of the following types based on the actual networking conditions: z

Bearer over IP: SCTP and UDP

z

Bearer over ATM: MTP3B

Currently, IP/SCTP bearer mode is used. This parameter is defined in the ADD MGW command. When using IP bearer mode, set the SCTP links as follows: [Link No.] This parameter identifies an SCTP link. The links are numbered from 0. MSOFTX3000 supports up to five SCTP links to MGW. It is required to set the attributes of them one by one. [BSG/IFM/AFM/SGU Module] It defines the module number of BSG/AFM/IFM/SGU processing SCTP links. You can query it with the command LST MDU. The specified module will process the H248 messages on this MCLNK. [Local IP1] This parameter refers to the local IP address, that is, the external IP address of the WIFM. Since transmission between the MSOFTX3000 and the MGW is based on IP, and signaling is borne on SCTP/IP, you need to specify a corresponding IP address for every link. This IP address needs to be negotiated with MGW. It has been defined in the ADD FECFG command. [Local IP2] This parameter refers to the second local IP address. This parameter specifies the second local IP address. It is used for the multi-homing function of the MSOFTX3000. It is optional. [Local Port] This parameter refers to the local port number It is used to define the local communication port for SCTP connection. When transmission control is implemented based on SCTP, you need to specify a SCTP port number. This parameter needs to be negotiated with MGW. 4-9



[Remote IP1] This parameter refers to the remote IP address, that is, the external IP address of the peer MGW. This IP address needs to be negotiated with MGW. [Remote IP2] This parameter specifies the second remote IP address. It refers to the second external IP address of the peer MGW. It is used for the multi-homing function of the MSOFTX3000. This parameter is optional. [Remote Port] This parameter refers to the remote port number, that is, the number of the communication port through which the specified SCTP link is connected to the peer MGW. It needs to be negotiated with MGW. [Max Incoming Flow] This parameter is used to define the maximum number of flows received by the first SCTP link. Use the default value. [Max Outgoing Flow] This parameter is used to define the maximum number of flows sent by the first SCTP link. Use the default value.

IV. Related Commands See Table 4-4 for the commands related to the configuration of SCTP links to MGW. Table 4-4 List of commands related to configuration of SCTP links to MGW Command

Description

ADD MCLNK

To add SCTP link to MGW

LST MCLNK

To list the information of SCTP link to MGW

RMV MCLNK

To remove SCTP link to MGW

DSP MCLNK

To display the information of SCTP link mode to MGW

4.4.3 Setting SCTP Checksum Algorithm (Optional) I. Background Information There are two SCTP checksum algorithms supported in MSOFTX3000: ADLER32 and CRC32. If the checksum algorithm of MSOFTX3000 is inconsistent with that of MGW,

4-10



the messages sent from one end will be regarded as invalid at the other end and then discarded.

II. Command SET SCTPPARA

Important Note: First execute the command LST SCTPPARA on MSOFTX3000 to query the parameter “Checksum Arithmetic”. Then check if the algorithm at the peer end is the same as that on MSOFTX3000. If not, modify the algorithm of MSOFTX3000 with the command SET SCTPPARA.

III. Major Parameters [Checksum Arithmetic] It defines the checksum algorithm to be ADLER32 or CRC32. Select the same choice with MGW.

IV. Related Command See Table 4-5 for the command related to the configuration of SCTP checksum algorithm. Table 4-5 Command related to configuration of SCTP checksum algorithm Command LST SCTPPARA

Description To list SCTP parameters

4.4.4 Setting Tone Playing Capability of MGW (Optional) I. Background Information None

II. Command ADD/MOD TONECFG

4-11



Important Note: This command is used to define the tone file record. During system initialization, the default setting that language is English and cycle number is 2 is loaded. If you need to modify language and cycle number of the tone file, use the MOD TONECFG command; or you can delete the original record and then use the ADD TONECFG command to add a tone file record.

III. Major Parameters [Internal Tone Type] It refers to the tone type defined in the MSOFTX3000. [MGW Tone ID] It refers to the tone ID defined in the MGW. [Language1]–[Language5] It defines the priority of languages in which tone files are played. [Cycle Number] It defines the repeat times of tone playing. The default value is 2. [Duration(sec)] It refers to the duration of playing the tone file (in seconds). Generally, you do not need to set it, and the duration depends on the length of the tone file. [Interval Time (sec)] It refers to the interval time between two playings of the tone file. [Use Dummy T] It specifies whether to use dummy T. Generally, it is set to "Yes". This parameter is used to guarantee the continuity of tone playing in the process of switchover.

IV. Related Commands See Table 4-6 for the command related to the configuration of tone playing capability of MGW.

4-12



Table 4-6 Command related to configuration of tone playing capability of MGW Command

Description

ADD TONECFG

To define the tone playing capability of MGW

LST TONECFG

To list the tone playing capability of MGW

MOD TONECFG

To modify the tone playing capability of MGW

RMV TONECFG

To remove the tone playing capability of MGW


SCP

SMC

GMLC

HLR

MAP/TDM

MAP/TDM

MAP/TDM

MAP/TDM

MSC Server

MSOFTX 3000

ISUP/TDM

BSSAP+/TDM

SGSN

ISUP,BSSAP/ TDM

H.248,RANAP/ IP

SPC

MGW

ISUP/TDM

MGW IP/TDM (SG)

RANAP/AAL2 /ATM

RNC

BSSAP/ TDM

BSC

Figure 4-3 Networking of MSOFTX3000

4-13

PSTN



This example is to add an MGW. For the local office information, refer to Table 3-14 in Chapter 3. For MGW information table, see Table 4-7. Table 4-7 MGW information table Item Basic information / SCTP link information /

Data MGW index

Transport layer protocol

Tone coding/dec oding mode

Checksu m mode

Server /client

MGW ciphering algorithm and ciphering key (optional)

1

SCTP

All

CRC32

Server

None

SCTP link No.

Local IP address of the WIFM

Local port number of the WIFM

Remote IP address of MGW

Remote port number of MGW

0

173.20.200. 132

2945

173.20.200.132

2945

Since the SCTP checksum algorithm on MSOFTX3000 differs from that on MGW, one of them is to be modified to the same as the other one. The times of cyclic playing of the 117 time announcement tone (TID_0X0002) is to be set to 3.

4.5.2 Configuration Description //Check the WIFM module number and IP address and WMGC module number. This example is for the integrated configuration of WIFM, WMGC and WBSG. LST FECFG:; LST MDU:;

//Add basic information of MGW. ADD

MGW:

MGWIDX=1,

BNCC=IP-1&AAL1-1,

TRNST=SCTP,

CTRLMN=132,

DEVNAME="MGW1",

MGWDESC="MGW1",

SVRCLIENT=SVR,

BCUID=1, ENCT=NSUP,

CPB=TONE-1&PA-1&SENDDTMF-1&DETECTDTMF-1&MPTY-1&IWF-1, ECRATE=0, IWFRATE=1, TCRATE=1,

TONERATE=12,

MPTYRATE=0,

DETDTMFRATE=0,

SNDDTMFRATE=0,

HRAMRR=RATE795-1&RATE740-1&RATE670-1&RATE590-1&RATE515-1&RATE475-1, TC=GSMEFR-1&GSMHR-1&TDMAEFR-1&PDCEFR-1&HRAMR-1&UMTSAMR2-1&FRAMR-1&FRAMRWB1&UMTSAMRWB-1&PCMA-1&PCMU-1&UMTSAMR-1&G7231-1&G729A-1;

//Add SCTP link to MGW. ADD MCLNK: MGWIDX=1, TRNST=SCTP, LNKN=0, BSGMN=132, SLOCIP1="173.20.200.132",

4-14



SRMTIP1="173.20.200.93";

//Modify SCTP checksum algorithm (optional). LST SCTPPARA:; SET SCTPPARA: CHKSUMTYPE=CRC32;

//Set tone playing capability of MGW (optional). MOD TONECFG: INTTID=TID_0X0002, CYCN=3;

4-15


Chapter 5 Configuring Data for Interworking with RNC

Chapter 5 Configuring Data for Interworking with RNC 5.1 Introduction to the Chapter This chapter describes how to configure data for MSOFTX3000 interworking with Radio Network Controller (RNC). It contains the following sections: z

Related Concepts

z

Collecting Data for Interworking with RNC

z

Configuring Data for Interworking with RNC

z


5.2 Related Concepts 5.2.1 Basic Concepts of M3UA For basic concepts and terminologies of MTP3-user adaptation layer (M3UA), such as application server, signaling gateway, M3UA link, M3UA link set, M3UA route, and M3UA entity, see Chapter 4

“M3UA of Transport Protocols Part” in HUAWEI

MSOFTX3000 Mobile SoftSwitch Center Technical Manual-Signaling & Protocols.

5.2.2 Networking between MSOFTX3000 and RNC Radio access network application part (RANAP) protocol is used between MSOFTX3000 and RNC, which can be based on either ATM or IP. MGW is typically used as a signaling transfer point in current networking applications. Signaling messages between MSOFTX3000 and MGW are carried over IP, and signaling messages between MGW and RNC are carried over ATM. See Figure 5-1 for the networking.

5-1



ATMbearer ATM 承载

IPIP bearer 承载 MSOFTX3000

RNC

MGW

(SG)

RANAP

RANAP SCCP

SCCP M3UA

M3UA

MTP3B

MTP3B

SCTP

SCTP

SAAL

SAAL

IP

IP

ATM

ATM

MAC

MAC

PHY

PHY

Figure 5-1 Networking relationship between MSOFTX3000 and RNC RNC uploads RANAP signaling carried over MTP3B. MGW is configured with built-in SG function to adapt MTP3B to M3UA and transfer it to MSOFTX3000 over IP. M3UA implements IP bearer through SCTP, and M3UA links are identified by IP addresses plus port numbers. Therefore, you need to specify a port number that is different from the one for bearing H.248 protocol when you are configuring an M3UA link. In this networking structure, the working mode of M3UA is SGP-ASP. Here, the networking is illustrated under the conditions that M3UA adopts transfer mode, the application server (AS) independently occupies signaling point codes, MSOFTX3000 is defined as an AS, and MGW (built-in SG) is defined as a signaling gateway (SG).

5.2.3 Parameter Relationship Figure 5-2 illustrates the parameter referencing relationship at MSOFTX3000 side during configuration. The parameter “NI” in the figure must be assigned with the same attributes.

5-2



ADD M3LE

ADD SCCPDSP

[Local Entity Index]

[NI] [OPC]

[Local Entity Point Code] [NI]

[DPC] (of RNC) ---

[Local Entity Type] [Route Context](optional) ---

ADD SCCPSSN

ADD M3DE

[NI ]

[Local Entity Index]

[SSN]

[Destination Entity Index]

[SPC]

[NI]

[OPC] ---

[Destination Entity Point Code] [Destination Entity Type] [Adjacent Flag] ---

ADD OFC [NI]

ADD M3LKS

[Office directioin]

[Adjacent Entity Index]

[Destination Point Code] ---

[Work Mode] [Link Set Index] ---

ADD RNC

ADD M3RT

[Destination Point Code]

[Destination Entity Index]

[RNC ID]

[Link Set Index ]

[Network ID] [Oragination Point Code] ---

ADD M3LNK [Linkset Index]

ADD LAISAI

[Module No](ADD FECFG)

[RNC ID]

[Local IP Address ](ADD FECFG)]

[MSC/VLR Number of 3G Service Area]

[Local Port] [Peer IP Address

[Call Source Code]

[Peer Port]

[Office No.]

[C/S Mode] ---

---

ADD RANMGW [Office Number] [Media Gateway Index] (ADD RANMGW)

Figure 5-2 Parameter relationship between MSOFTX3000 and RNC/MGW

5.2.4 General Configuration Procedures Table 5-1 shows the procedures and commands for configuring interworking data if MGW is used for transferring signaling messages between MSOFTX3000 and RNC and that IP bearer is used for networking.

5-3



Table 5-1 Procedures and commands for configuring interworking data between MSOFTX3000 and RNC (based on IP) Procedure

Command

1: Negotiate and prepare data to be configured at MGW side 2: Add M3UA local entity

ADD M3LE

3: Add M3UA destination entity

ADD M3DE

4: Add M3UA link set

ADD M3LKS

5: Add M3UA route

ADD M3RT

6: Add M3UA link

ADD M3LNK

7: Add SCCP remote signaling point

ADD SCCPDSP

8: Add RANAP subsystem

ADD SCCPSSN

9: Add RNC office direction

ADD OFC

10 Add RNC global indicator

ADD RNC

11: Add 3G service area

ADD LAISAI

12: Add access media gateway

ADD RANMGW

5.3 Collecting Data for Interworking with RNC Before configuring data, you need to collect the data for interworking between MSOFTX3000, MGW (SG), and RNC, as shown in Table 5-2. In the shadowy columns are the parameters that must be negotiated between two ends for consistency or of which one end must notify the other end. The other parameters are the internal ones of MSOFTX3000.

5-4



Table 5-2 Table of data collected for MSOFTX3000 interworking with RNC Item Basic RNC information

Data RNC ID


Network indicator

LAI

Service mode

Route context (optional)

WIFM module number

SG signaling point code

M3UA link number

Local IP

Local port

IP address of the peer MGW

Local prefix


SAI

AMR LIST

Port number of the peer MGW

Server/Cli ent

/ Basic M3UA signaling / M3UA link information / Prefix /

5.4 Configuring Data for Interworking with RNC 5.4.1 Negotiating and Preparing Data I. Mc Interface Data For the data configuration about the Mc interface between MSOFTX3000 and MGW, refer to Chapter 4 “Configuring Data for Interworking with MGW”.

II. Data to be Configured at MGW Side 1)

Interface configuration

Signaling messages of MGW are sent to MSOFTX3000 through the Mc interface (10/100 Mbit/s adaptive Ethernet interface) provided by the MPPU. What need be configured are the IP address and route of the Mc interface. 2)

M3UA link configuration

It includes the configuration of M3UA entity, flow, route, link set, route, and link. For more information, see HUAWEI UMG8900 Universal Media Gateway Operation Manual-Data Configuration.

5-5



5.4.2 Adding M3UA Local Entity I. Background Information Before adding M3UA local entity for MSOFTX3000, execute LST OFI command to check whether the local original point code (OPC in national reserved network) is configured. If not, configure it first.

II. Command ADD M3LE

III. Major Parameters [Local Entity Index] It is used to uniquely identify an M3UA local entity. [NI] It is used to indicate the network type. A signaling point can simultaneously appear in international network, international reserved network, national network, and national reserved network. It is the same as the network indicator of RNC. [Local Entity Point Code] It is used to define the signaling point code of a local entity. This code is associated with the parameter in the command SET OFI. [Local Entity Type] It is used to define the type of a local entity. It may be SG or AS. For the SGP-ASP mode, set the entity type at MSOFTX3000 side to “AS”, and that at peer MGW side to “SG”. [Route Context] (optional) It is used to specify the index value of a group of SS7 parameters. This parameter can be configured when the entity type is AS. The route context at AS side must be the same as that at SG side.

IV. Related Commands See Table 5-3 for the commands related to M3UA local entity configuration

5-6



Table 5-3 List of commands related to M3UA local entity configuration Command

Description

ADD M3LE

To add M3UA local entity

RMV M3LE

To remove M3UA local entity

MOD M3LE

To modify M3UA local entity

LST M3LE

To list M3UA local entity

5.4.3 Adding M3UA Destination Entity I. Background Information You must set the destination entity before a path from the local entity to the destination entity becomes available. As the SG function is integrated in MGW, MGW resident office shall allocate a signaling point code for the built-in SG. In this case, it appears that MGW has a signaling point code which in fact is allocated to SG. You need to add two types of destination entity: one is MGW (with built-in SG), functioning as SG and to be configured with the DSP of SG; the other is RNC, functioning as SP and to be configured with the DSP of RNC.

II. Command ADD M3DE

III. Major Parameters [Destination Entity Index] It is used to identify a destination entity uniquely. [Local Entity Index] It is used to identify a local entity to which the destination entity corresponds. This index is already defined in the ADD M3LE command. [NI] It is used to indicate the network type. A signaling point can simultaneously appear in international network, international reserved network, national network, and national reserved network. [Destination Entity Point Code]

5-7



It is used to specify the signaling point code of a destination entity. Its value is determined by the actual destination entity type to be configured. [STP Flag] It is used to set whether a DSP has STP function. To set the destination entity to SG type, select “TRUE”; to set it to SP type, select “FALSE”. [Link set select mask] This parameter indicates how to achieve load sharing among all routes to an M3UA destination entity. [Destination Entity Type] It is used to define the type of a destination entity. There are three types of destination entity, namely SP, SG, and AS. As MGW also functions as an SG, add MGW as SG and RNC as SP. [Adjacent Flag] It is used to set whether a DSP is adjacent to the local office signaling point, that is, whether there is a signaling link directly associated with the local office signaling point. Select “YES” when there is such a direct signaling link with the local office signaling point; otherwise, select “NO”. This parameter is only valid whenthe parameter “Destination Entity Type” is set to “AS” or “SG”. [Network Mode] This parameter is used to specify the network mode between SG and AS. This field is used only when the destination entity type is AS (MSOFTX3000 acts as SG) to specify whether the AS interconnecting with MSOFTX3000 is an exclusive signaling point code or a signaling point code shared with other ASs. By default, the AS is an exclusive SPC. It includes two modes: z

INCLUSIVE: The traffic that belongs to this point code of a destination entity is shared with other destination entities.

z

EXCLUSIVE: The traffic that belongs to this point code of a destination entity is not shared with any other destination entity.

You need not set it here. [Protocol Version] It is a parameter for interconnection between MSOFTX3000 and a destination entity. MSOFTX3000 supports the interconnection with the M3UA destination entity specified in DRAFT10 or RFC3332. By default, it is RFC3332. You need to set it to DRAFT10 when adding the SG destination entity.

5-8



IV. Related Commands See Table 5-4 for the commands related to M3UA destination entity configuration. Table 5-4 List of commands related to M3UA destination entity configuration Command

Description

ADD M3DE

To add M3UA destination entity

RMV M3DE

To remove M3UA destination entity

MOD M3DE

To modify M3UA destination entity

LST M3DE

To list M3UA destination entity

DSP M3DE

To display the state of M3UA destination entity of the host

5.4.4 Adding M3UA Link Set I. Background Information This section describes how to establish a link set between two M3UA adjacent entities.

II. Command ADD M3LKS

III. Major Parameters [LinkSet Index] It is used to specify the logical number of a link set in the system. The index is numbered globally in ascending order from 0. The index is used in the M3UA routing table. [Adjacent Entity Index] It is used to identify the adjacent destination entity interconnected by the associated signaling link set. This index is related to the parameter “destination entity index” in the ADD M3DE command. Set the parameter “adjacent flag” of the corresponding destination entity to “adjacent". [Link Select Mask] It indicates how to share signaling traffic among the multiple signaling links in the same signaling link set. The value of this parameter is actually the load-sharing mask code of signaling links.

5-9



[Traffic Mode] It is used to determine the service mode of the link set is “Load-Share Mode” or “Over-Ride Mode”. The traffic modes at two ends must be the same. That is, the two ends must be in load-share mode or over-ride mode at the same time; otherwise, the corresponding link cannot be activated. The default option (load-share mode) is recommended. [Work Mode] It is used to indicate the attributes of the home end of a link set, such as ASP, IPSP, and SGP, according to the working mode of the link set. It is associated with the parameter “Local Entity Type” in the ADD M3LE command. z

In the non-peer networking mode, the M3UA destination entity type is SG, and the corresponding local entity type is AS, that is, "Local Entity Type” in the ADD M3LE command is “AS”. In this case, select “ASP”.

z

In the non-peer networking mode, the M3UA destination entity type is AS, and the corresponding local entity type is SG, that is, "Local Entity Type” in the ADD M3LE command is “AS”. In this case, select “SGP”.

z

In the peer networking mode, the M3UA destination entity type is the same as the local entity type, that is, AS or SG, select “IPSP".

IV. Related commands See Table 5-5 for the commands related to M3UA link set configuration. Table 5-5 List of commands related to M3UA link set configuration Command

Description

ADD M3LKS

To add M3UA link set

RMV M3LKS

To remove M3UA link set

MOD M3LKS

To modify M3UA link set

LST M3LKS

To list M3UA link set

DSP M3LKS

To display M3UA link set of the host

5.4.5 Adding M3UA Route I. Background Information This section describes how to determine a signaling route to a destination entity by specifying a link set that can reach this destination entity. You can set priority for the route for carrying signaling traffic.

5-10



II. Command ADD M3RT

III. Major Parameters [Destination Entity Index] It is used to identify a destination entity to which a signaling route is destined. It is already defined in the ADD M3DE command. [LinkSet Index] It is used to specify a signaling link set used by the signaling link reaching a destination entity. This parameter is defined in the ADD M3LKS command. [Priority] “0” indicates the highest priority. Among the several signaling routes to the DSP, the one with the highest priority is preferentially used to carry signaling traffic. A signaling route will carry signaling traffic unless none of signaling routes with higher priority is available.

IV. Related Commands See Table 5-6 for the commands related to M3UA route configuration. Table 5-6 List of commands related to M3UA route configuration Command

Description

ADD M3RT

To add M3UA route

RMV M3RT

To remove M3UA route

MOD M3RT

To modify M3UA route

LST M3RT

To list M3UA route

DSP M3RT

To display M3UA route of the host

5.4.6 Adding M3UA Link I. Background Information You need to negotiate such parameters as “Local IP Address1”, “Local Port", “Peer IP Address1”, and “Peer Port” with the peer end to uniquely determine an M3UA link.

5-11



II. Command ADD M3LNK

III. Major Parameters [Module Number] It is used to define the module number of the WIFM/WBSG where M3UA links are resident. You can query it with the LST MDU command. If the WIFM and WBSG are integrated into one board, enter the module number of the WIFM here. If the WIFM and WBSG are separately configured, the module number is determined according to the board configured with M3UA links. If M3UA links are configured in the WIFM, enter the WIFM module number here. If M3UA links are configured in the WBSG, enter the WBSG module number here. [Link No.] It is used to identify a physical signaling link in a module. Each link of the same module has a unique link number. [Local IP Address1] IP based transmission is used between MGW and MSOFTX3000, and signaling messages are transmitted over IP/SCTP. It is necessary to specify an IP address for each link. Local IP address 1 is the external IP address of the local WIFM. This IP has to be negotiated with MGW. It is already defined in the ADD FECFG command. [Local IP address2] This parameter is used to specify the second local IP address to which this link corresponds. Set it only when it supports SCTP multi-homing functionality. [Local Port] It is used to define the SCTP port of the local signaling point. It is necessary to specify the SCTP port number when SCTP is used for transmission control. Ensure that the local port number specified here is consistent with the SCTP peer port number set at MGW side. [Peer IP Address1] It is used to specify the external IP address of the peer MGW. This IP has to be negotiated with MGW. [Peer IP Address2] This parameter is used to specify the second remote IP address to which the link corresponds. Set it only when it supports SCTP multi-homing functionality.

5-12



[Peer Port] It is used to specify the communication port of the peer MGW. It has to be negotiated with MGW. [C/S Mode] It is used to set whether a link is at the client side or server side. This parameter must be negotiated with the peer end. Set one end to client and the other end to server; otherwise, M3UA links cannot be set up normally. You can set MSOFTX3000 to either client or server as long as it is not the same as MGW (SG). [Linkset Index] It is used to identify a link set to which a link belongs. It is associated with the link set index number in the ADD M3LKS command. [Active/Standby Flag] This parameter is used to set the work state for this M3UA link in the normal situation. The configuration of this parameter is closely related to the service mode of the link set: z

If you adopt the active/standby mode, only one of all M3UA links in the same link set can be set to active, while others must be set to standby.

z

If you adopt the load sharing mode, you must set all M3UA links in the same link set to active.

[Priority] This parameter is used to specify the priority of a link in a link set. Select the link with the highest priority first. 0 indicates the highest priority. [Main Type] It is used to set the dual homing function of MSOFTX3000. It indicates if a link is active or standby. When MSOFTX3000 supports the dual homing function, set it based on the actual situation. If no dual homing function is applied for MSOFTX3000, use the default setting, that is, ”TRUE”. Set other parameters to the default values.

IV. Related Commands See Table 5-7 for the commands related to M3UA link configuration. Table 5-7 List of commands related to M3UA link configuration Command

Description

ADD M3LNK

To add M3UA link

RMV M3LNK

To remove M3UA link

5-13



Command

Description

MOD M3LNK

To modify M3UA link

LST M3LNK

To list M3UA link

DSP M3LNK

To display M3UA link of the host

EST M3LNK

To establish M3UA link

REL M3LNK

To release M3UA link

LCK M3LNK

To block M3UA link

ULK M3LNK

To unblock M3UA link

DEA M3LNK

To deactivate M3UA link

ACT M3LNK

To activate M3UA link

5.4.7 Adding SCCP Remote Signaling Point I. Background Information One SCCP DSP is uniquely identified by NI, OPC, and DPC. The originating point code (OPC) and destination point code (DPC) must be consistent with those of the lower layer (MTP3/MTP3B/M3UA) when an SCCP DSP is configured. As IP bearer mode is adopted between the local office and RNC, the DPC of RNC must be first configured in the destination entity table of M3UA. Use the LST M3DE command to check whether the RNC DPC specified is consistent with that in the M3UA destination entity table.

II. Command ADD SCCPDSP

III. Major Parameters [DSP Index] It uniquely identifies an SCCP DSP, ranging from 0 to 511. It must be noted that the “DSP Index” defined here is different from the “DSP Index” defined in ADD N7DSP and “Destination Entity Index” defined in ADD M3DE, and there is no reference relation among them. [NI] It identifies the network where the SCCP subsystem is resident.

5-14



[DPC] Set it to the SPC of the RNC at the peer end. It must be defined in ADD N7DSP or ADD M3DE first and then referenced here. [OPC] It is used to specify the OPC of the local office with the same network indicator. You can query it with the command LST OFI. It must be specified in the command SET OFI first and then referenced here.[Load Sharing Function Flag] It is used to set whether MSOFTX3000 supports the load sharing function or backup function of SCCP DSP. The meaning of the options are as follows: z

No Standby DSP: Not support backup function

z

Backup DSP: Support active/standby function

z

Loadshare DSP: Support load sharing function

[Standby DSP Index] It is valid only when MSOFTX3000 supports the load sharing function or backup function of SCCP DSP. It is used to specify the standby DSP of SCCP.

IV. Related Commands See Table 5-8 for the commands related to SCCP DSP configuration.

5-15



Table 5-8 List of commands related to SCCP DSP configuration Command

Description

ADD SCCPDSP

To add SCCP DSP

RMV SCCPDSP

To remove SCCP DSP

MOD SCCPDSP

To modify SCCP DSP

LST SCCPDSP

To list information about all configured SCCP DSPs

DSP SCCPDSP

To display information about all configured SCCP DSPs of BAM

SET SCCPDSP

To set the state of SCCP DSP

5.4.8 Adding SCCP Subsystem I. Background Information This section describes how to add SCCP subsystems of MSOFTX3000 (local) and RNC (remote). Subsystem number (SSN) provides local addressing information for SCCP. SSN identifies SCCP users at a signaling point. Subsystems to be configured locally and remotely include: z

SSN of the MSOFTX3000 at the local end is RANAP.

z

SSN to be configured for RNC at the remote end is SCCP management subsystem (SCMG), RANAP.

MSC, VLR, and SCMG of the local office need also to be configured. If they have been configured in the local office information, they need not to be configured here. You must first run LST SCCPSSN to have a check for avoiding repetition.


III. Major Parameters [SSN Index] It is used to set the index of the SCCP subsystem, and it is unique in the system. [NI] It is used to identify the network where the SCCP subsystem is resident. [SSN]

5-16



It is used to set the subsystem number. SCMG and RANAP are configured for both local and remote ends. [SPC] It is used to specify the destination SPC of the corresponding subsystem, that is, the recipient of SCCP messages. You need to set RNC SPC and OPC here. [OPC] It is used to specify the originating SPC of the corresponding subsystem, that is, the sender of SCCP messages. For each subsystem, this OPC is a local SPC. It must be defined in the command SET OFI first and then referenced here. [Local concerned SSN1]–[Local concerned SSN5] It is used to define the index of a subsystem which is related to the specified subsystem and has the same DPC as the subsystem. You can define a maximum of five indexes. If there is no related subsystem, use the default option “UNDEFINED”. [Backup SSN index] It is used to specify the index of the backup subsystem of the specified subsystem. It is valid only when MSOFTX3000 supports the load sharing function or backup function of SCCP DSP. If there is no subsystem, use the default value “65535”.

IV. Related Commands See Table 5-9 for the commands related to SCCP subsystem configuration. Table 5-9 List of commands related to SCCP subsystem configuration Command

Description

ADD SCCPSSN


RMV SCCPSSN


MOD SCCPSSN


LST SCCPSSN


SET SCCPSSN

To set SCCP subsystem status for maintenance purpose

DSP SCCPSSN

To display SCCP subsystem of the host

5-17



5.4.9 Adding RNC Office Direction I. Background Information This section describes how to set an office direction from MSC Server to RNC.

II. Command ADD OFC

III. Major Parameters [Office Direction] It is allocated uniquely in the system to identify an office direction. [Office Direction Name] It is recommended to use a canonical name for the sake of easier identification, for example, "TO-SZ_RNC". [Opposition Office Type] For this parameter, select “RNC”. [Peer Office Level] As RNC is in a lower level than MSC Server, select “LOW (INFERIOR)”. [Peer Office Attribute] For this parameter, select “RNC”. [Network ID] This parameter of the MSOFTX3000 must be consistent with that set at the peer end of the network. [Destination Point Code1]–[Destination Point Code16] These parameters have to be negotiated with RNC. They are associated with RNC signaling point codes in the ADD SCCPDSP command. For other parameters, use the default values.

IV. Related Commands See Table 5-10 for the commands related to office direction configuration.

5-18



Table 5-10 List of commands related to office direction configuration Command

Description

ADD OFC

To add an office direction

RMV OFC

To remove an existing office direction

MOD OFC

To modify attributes of an existing office direction

LST OFC

To list information about configured office direction

5.4.10 Adding RNC Global Indicator I. Background Information None.

II. Command ADD RNC

III. Major Parameters [RNC ID] It is allocated uniquely across the network to identify an RNC. It is used to configure a QAAL2 path. [Network ID] This parameter of the MSOFTX3000 must be consistent with that set at the peer end of the network. [Origination Point Code] It is used to define the local signaling point code in the office information table. Currently, OPC must be the same for all RNCs. [Destination Point Code] It is used to set the destination signaling point code of RNC. It is associated with the RNC DPC in the ADD SCCPDSP command. [List of Net Support AMR Rate] It is used to specify the list of AMR rates supported by the network. This parameter needs to be negotiated with RNC. [Location Area ID]

5-19



Configure the unique LAI to which RNC belongs. If [Location Area Not Unique Flag] is set to “FALSE”, you must set this parameter. This LAI is used to complement the incomplete cell ID which is sent from RNC. For other parameters, use the default values.

IV. Related Commands See Table 5-11 for the commands related to RNC configuration. Table 5-11 List of commands related to RNC configuration Command

Description

ADD RNC

To add a RNC

RMV RNC

To remove an existing RNC

MOD RNC

To modify attributes of an existing RNC

LST RNC

To list information about configured RNC

5.4.11 Adding 3G Service Area I. Background Information This section describes how to configure a location area or a 3G service area. “LA category” parameter is used to distinguish them.

II. Command ADD LAISAI

III. Major Parameters [3G Service Area No.] It is a 9-bit location area code if what is configured is a location area or a 13-bit cell number if what is configured is a 3G service area. The following “LA category” parameter is used to identify the type. The concerned code or number is given in the network planning phase. [MSC No. of 3G Service Area] It is used to set the MSC number to which the 3G service area belongs. It is provided by the serving operator. It is already defined in the ADD INOFFMSC command. [VLR No. of 3G Service Area]

5-20



It is used to set the VLR number to which the 3G service area belongs. It is provided by the serving operator. It is already defined in the ADD INOFFMSC command. [Perform Roaming Analysis] Roaming analysis is performed on a specific location area. Set this parameter to YES if roaming restriction is required for a location area. [LA Category] It is used to set the category of a location area. Select “LAI” if the current entry is set for a location area. Select “SAI” if the current entry is set for a 3G service area. [3G Service Area Type] It is used to distinguish whether the current location area/3G service area is in the coverage of the local VLR or the adjacent VLR. Generally, MSC and VLR are integrated together. To guarantee external handover of mobile stations between MSCs, you need to record the information about the 3G service area of the adjacent MSC bordering on the local MSC when MSC related data is configured. If the location area/3G service area is in the coverage of the local MSC/VLR, set this parameter to “in local VLR”’; otherwise, set this parameter to “in adjacent VLR”. The following parameters are enabled when the concerned area is in the coverage of the local VLR: [Early Assignment Flag] It is used to set when circuit assignment happens. For a calling party, an early assignment is initiated by sending a request when the network receives CALL PROCEEDING from the calling party; a late assignment is initiated after the network sends ALERTING to the calling party. For a called party, an early assignment is initiated by sending a request when the network receives CALL CONFIRMED from the called party; a late assignment is initiated when the network receives CONNECT from the called party. [Location No.] It is used to specify the corresponding identity of an area. It is used for roaming restriction. [RNCID1]–[RNCID10] These parameters are used to set the RNC ID of 10 RNCs to which an area belongs. They are associated with the parameter “RNC ID” in the ADD RNC command. [Call Source Code]

5-21



It is used to set the call source code when a call is originated from the concerned location area/3G service area. This parameter is already defined in the ADD CALLSRC command. [Office No.] It is used to set the corresponding office direction number of RNC. This parameter is already defined in the ADD OFC command.

IV. Related Commands See Table 5-12 for the commands related to 3G service area configuration. Table 5-12 List of commands related to 3G service area configuration Command

Description

ADD LAISAI

To add location area identity or cell global identification

MOD LAISAI

To modify location area identity or cell global identification

LST LAISAI

To list location area identity or cell global identification

RMV LAISAI

To remove location area identity or cell global identification

5.4.12 Adding Access Media Gateway I. Background Information None

II. Command ADD RANMGW

III. Major Parameters [Office Number] It is used to identify an office direction of the particular entity interconnected with MGW. It is already defined in the ADD OFC command. [Media Gateway Index] It is defined in the ADD MGW command.

IV. Related Commands See Table 5-13 for the commands related to access media gateway configuration.

5-22



Table 5-13 List of commands related to access media gateway configuration Command

Description

ADD RANMGW

To add RAN-MGW connection information

RMV RANMGW

To remove an existing RAN-MGW connection information

MOD RANMGW

To modify attributes of an existing RAN-MGW connection information

LST RANMGW

To list information about configured RAN-MGW connection information


SCP

SMC

GMLC

HLR

MAP/TDM

MAP/TDM

MAP/TDM

MAP/TDM

MSC Server

MSOFTX 3000

ISUP/TDM

H.248,RANAP /IP

BSSAP+/TDM

SGSN


MGW

MGW

IP/TDM

ISUP/TDM

(SG)

RANAP/AAL2/ATM

RNC

BSSAP/TDM

BSC

Figure 5-3 Networking of MSOFTX3000

5-23

PSTN



As shown in the figure, there is an MGW used for transfer between MSOFTX3000 and RNC; IP based bearer is used between MSOFTX3000 and MGW; It is also assumed that Mc protocol data have been already configured. This example adds an RNC, which is connected to MGW. The related information is shown in Table 5-14. For the local office information, see Table 3-14 in Chapter 3. Table 5-14 RNC information table Item

Data

Basic RNC information

RNC ID


Network indicator

LAI

SAI

AMR LIST

/

4

D04

National reserved

460000003

4600000 030004

All

Basic M3UA signaling

Service mode


WIFM module number


/

Load sharing

NULL

132

1004

M3UA link information

M3UA link number

Local IP

Local port


Port of peer MGW

Server/Clie nt

/

0

173.20.200.1 32

2905

173.20.200.9 3

2905

Client

Prefix

Local prefix


/

1360755

65535

5.5.2 Configuration Description //Add M3UA. LST OFI:; //Query the OPC whose NI = NATB. LST FECFG:; //Query the local IP address of WIFM. ADD M3LE: LEX=0, LENAME="MscM3UA", NI=NATB, OPC="C04", LET=AS; ADD M3DE: DEX=0, DENAME="MgwM3ua", NI=NATB, DPC="1004", STPF=TRUE, DET=SG, DEVER=DRAFT10; ADD M3DE: DEX=1, DENAME="RncM3ua", NI=NATB, DPC="D04", DET=SP; ADD M3LKS: LSX=0, LSNAME="ToMGW1", ADX=0, WM=ASP; ADD M3RT: RTNAME="ToRNC4", DEX=1, LSX=0; ADD M3RT: RTNAME="ToMGW1", DEX=0, LSX=0; ADD

M3LNK:

MN=132,

LNKN=0,

LNKNAME="TO-MGW1",

LOCIP1="173.20.200.132",

LOCPORT=2905, PEERIP1="173.20.200.93", PEERPORT=2905 CS=C, LSX=0, ASF=YES;

5-24



//Add SCCP. ADD

SCCPDSP:

DPX=4,

NI=NATB,

DPC="D04",

OPC="C04",

DPNAME="RNC4",

SHAREFLAG=NONE; ADD

SCCPSSN:

SSNX=4,

NI=NATB,

SSN=RANAP,

SPC="C04",

OPC="C04",

NI=NATB,

SSN=SCMG,

SPC="D04",

OPC="C04",

NI=NATB,

SSN=RANAP,

SPC="D04",

OPC="C04",

SSNNAME="LOCAL-RANAP"; ADD

SCCPSSN:

SSNX=5,

SSNNAME="RNC4-SCMG"; ADD

SCCPSSN:

SSNX=6,

SSNNAME="RNC4-RANAP";

//Add the office direction, global title and service zone of RNC. LST INOFFMSC:; //Query MSC/VLR number ADD OFC: OFFICEDIR=4, ON="RNC4", OOFFICT=RNC, DOL=LOW, DOA=RNC, NI=NAT2, DPC1="D04", SIG=MTP3; ADD

RNC:

RNCID=4,

NI=NATIONBK,

OSP="C04",

SARL=A-1&B-1&C-1&D-1&E-1&F-1&G-1&H-1&SID-1&RATE0-1,

MLAIF

DPC="D04", =FALSE

,

LAI="460000003"; ADD

LAISAI:

SAI="460000003",

VLRN="8613600004",

LAICAT=LAI,

LAIGCINAME="RNC4", LAIT=HVLR,

MSCN="8613600004",

LOCNO=65535,

RNCID1=4,

OFFICNUM="4"; ADD

LAISAI:

SAI="4600000030004",

VLRN="8613600004",

LAICAT=SAI,

OFFICNUM="4";

//Add access media gateway. LST MGW:; //Query MGW Index. ADD RANMGW: OFFICENO=4, MGWIDX=1;

5-25


MSCN="8613600004",

LOCNO=65535,

RNCID1=4,


Chapter 6 Configuring Data for Interworking with BSC

Chapter 6 Configuring Data for Interworking with BSC 6.1 Introduction to the Chapter MSOFTX3000 and MGW are integrated to provide MSC/VLR entity functions, and they interwork with Base Station Controller (BSC) through A interface. This chapter describes the data configuration process at MSOFTX3000 for interworking with a BSC after MSOFTX3000 and MGW are integrated. This chapter contains the following sections: z

Related Concepts

z

Collecting Data for Interworking with BSC

z

Configuring Data for Interworking with BSC

z


6.2 Related Concepts 6.2.1 Networking Between MSOFTX3000 and BSC This networking mode takes MSOFTX3000 and MGW as an integrated entity. The semi-permanent connection is created at MGW, which transparently transmits the A interface messages between BSC and MSOFTX3000 over TDM. See Figure 6-1 for the networking mode.

6-1



MSOFTX3000

TDM bearer

Semi-permenant connection TDM bearer BSC

MGW

BSSAP SCCP MTP TDM

Figure 6-1 Networking between MSOFTX3000 and BSC

6.2.2 MTP Link Configuration One link set can contain a maximum of 16 links. You can select different timeslots on the same E1 or timeslots on different E1s to form a link set. Timeslot 0 of each E1 is the synchronization timeslot, so it cannot be used as a link. The following is an example with WCSU+WEPI configuration. The WCSUs are front board and the WEPIs are back boards, and they are the same in quantity. Besides, the numbers of circuits configured on the WEPI correspond to that of the links configured on the WCSU, as shown in Figure 6-2.The following describes the details with 64-kbit/s link as an example.

6-2


E1/TDM 0 ~ 3/0 ~ 127 4 ~ 7/128 ~ 255


WEPI

WEPI

Links 16 ~ 31 Upper

CPC

CPC

Links 0 ~ 15 Lower

CPC

CPC

WCSU0

WCSU1

Backplane

Figure 6-2 Corresponding relations between configured circuits and links The WCSU processes SS7 links through its sub-board CPC, and each WCSU can be configured with a upper CPC and a lower CPC. The lower one processes links 0–15 and the upper one processes links 16–31. The WCSUs work in active-standby mode, so their sub-board CPCs also work in active-standby mode, though CPCs originally work in load sharing mode. The WCSUs in pair (active and standby) can process thirty-two 64-kbit/s links or two 2-Mbit/s links. The WEPIs in pair (active and standby) can process eight E1s (0–7), that is TDM timeslots 0–255. It is required that the WEPIs corresponding to the WCSUs (1+1 backup) must be in position. However, it is only necessary to connect the E1 lines (8 in quantity) to any one of the WEPIs, and use the ADD EPICFG command to configure the WEPI slots to which the E1 lines are connected. The configuration information must be consistent with the actual hardware connection. The following describes the corresponding relations between circuit numbers and link numbers: z

Links 0–15 correspond to circuits (E1/TDM) 0–3/0–127. That is, for links 0–15, only TDM timeslots 0–127 can be used. Timeslot 0 of each E1 is the synchronization timeslot, which cannot be used as link.

z

Links 16–31 correspond to circuits (E1/TDM) 4–7/128–255. That is, for links 16–31, only TDM timeslots 128–255 can be used. Timeslot 0 of each E1 is the synchronization timeslot, which cannot be used as a link.

For example, if MSOFTX3000 is connected to MGW through E1 numbered as 4, adopting the 15 timeslot of the E1 as a link and the link number is 16, enter “Link No.” 6-3



with “16” and “Start Circuit No” with “143” (4×32+15=143) when you use the ADD N7LNK command.

6.2.3 Trunk Circuit and TID Configuration I. Configuration Description The following describes the method to configure the circuits adopting MGW semi-permanent connection as shown in Figure 6-3. As the configuration methods for MSC9880 interworking with BSC, PSTN and MSOFTX3000 are the same, here only the method for MSC9880 interworking with BSC is presented. CIC:0~31

CIC:0~31

M TID: 96~127 MSOF SERV SC TXER 3000 Physical circuit Physical circuit (E1) :4/16

(E1) :1/16

MGW

Physical circuit Semi-permanent (E1) :3/16 connection 96~127

BS BSC C Physical circuit (E1) :9/16

Figure 6-3 Configuring link and circuit for MSC9880 interworking with BSC MSOFTX3000 and MGW are connected through E1 and so are MGW and BSC. Because MSOFTX3000 and BSC assign circuits through circuit identification code (CIC), and MSOFTX3000 specifies which circuit MGW uses to establish bearer through termination ID (TID), the TID of MGW and the CIC of BSC can correspond to the same physical circuit. For example, the configuration data is as follows: z

Physical circuit (E1): 4/16, where 4 means E1 number and 16 indicates the timeslot number used by the link.

z

TID: Termination ID, which must be consistent with the number of the physical circuit of MGW to BSC. Here the value range is 96–127.

z

CIC: Circuit Identification Code, which must be consistent with that of BSC. Here the value range is 0–31.

II. Configuration Example In this example, there are 32 circuits available from MGW to BSC, and the circuit number ranges from 3*32=96 to 127. In MSOFTX3000, use the command ADD AIETKC, and enter “96” for “Start Circuit Termination ID”, the start physical circuit from MGW to BSC. Enter “0” for “Start CIC”. The numbers of TIDs and CICs can be obtained by “End Circuit” minus “Start Circuit”. The parameters “Start Circuit” and “End Circuit” are internally used in MSOFTX3000, and they correspond to TID and CIC one by one. They should be unique within the office and it is recommended that the values be consistent with those of TIDs. Here, the

6-4



start circuit is 96 and the end circuit is 127. There are 32 TIDs ranging from 96 to 127, and there are 32 CICs, ranging from 0 to 31.

6.2.4 Number Analysis Process

Important Note: For the mobile subscribers of the local office, routing to the local BSC is to find the LAI where a subscriber is resident. Because route, sub-route and route analysis data are used for routing to other offices, it is not necessary to configure them here.

I. Calling Number Analysis The calling number analysis process is as follows: 1)

A mobile subscriber initiates a call, sending CM_SERVICE-REQ (with IMSI) to MSC9880 mobile switching center.

2)

MSC9880 searches through VDB to get the LAI to which the calling subscriber is subject (stored in VDB because location update has been successful).

3)

MSC9880 searches through the LAI table to get the call source code according to the LAI.

4)

MSC9880 searches through the call source table to complete number analysis at calling subscriber side.

II. Called Number Analysis The called number analysis process is as follows: 1) 2)

A calling subscriber initiates SETUP message. MSC9880 implements called number analysis (searching through the CNACLD table) according to the called MSISDN in the message.

3)

If MSC9880 confirms that the called number is of MSISDN type, it will initiate the process to get MSRN.

4)

MSC9880 gets MSRN and IMSI in the local VLR to perform second number analysis. If it finds that the called subscriber is in the local office, it will search for the LAI to which the called subscriber is subject according to the IMSI.

5)

MSC9880 sends a paging message to the LAI.

6)

The called subscriber returns a paging response message (with the DPC of the home BSC).

7)

MSC9880 searches through the trunk group table according to the DPC of the BSC to get the trunk group and trunk circuit. Thus, the called number analysis process is completed.

Figure 6-4 illustrates the called number analysis process.

6-5

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center MS


MSC server Setup [MSISDN]

HLR

VLR

BSC-T

Number Analysis => MSISDN MAP_SRI_Req [MSISDN]

MAP_SRI_Rsp

MAP_PRN_Req [IMSI] MAP_PRN_Rsp [MSRN]

[MSRN、IMSI] the second Number Analysis => LAI Paging [LAI] Paging Response [DPC、LAIGCII]

Figure 6-4 Called number analysis process

6.2.5 Parameter Relationship Figure 6-5 illustrates the parameter relationships between MSOFTX3000 internal commands.

6-6


BSC parameter


MSOFTX3000 parameter ADD N7DSP

Signaling network ID BSC OPC

ADD N7LKS [Link Set]

[DSP index]

[Adjacent Point Index]

[Network Indicator] [Destination Point Code]

Peer end MSC DPC

ADD N7RT

[Original Point Code]

[Link Set]

ADD SCCPDSP

[DSP index] [Priority]

[Network Indicator] [DPC] [OPC]

ADD N7LNK

ADD SCCPSSN

[Link No]

aling link code (SLC)

ADD AIETG

[ Start Circuit No]

[Network Indicator] [SSN Code] [Signaling Point Code]

[ Link Set ] Code [ Signaling Link Code]

[OPC]

[Trunk Group] [Destination Point Code] [OriginaL Point Code] [MGW INDEX] ADD AIETKC

ADD OFC

[Trunk Group]

[Network ] [signal bearer type] [Destination Point Code] [Office directioin number]

[Start CIC] [START CIRCUIT TERMINATION ID] ADD RANMGW

ADD BSC [Destination Point Code] [Home Module No.1] [Network ID] [Location area ID]

[Media Gateway Index] [Office number]

ADD LAIGCI [Global Cell ID] [MSC Number of the LAI or Cell] [VLR Number of the LAI or Cell]

Figure 6-5 Parameter relationships

6.2.6 General Configuration Procedures As MSOFTX3000 and MGW are integrated, it is necessary to configure the data for interconnecting MSOFTX3000 and MGW, create semi-permanent connections on MGW, and then configure the data at the MSOFTX3000 side to BSC. See Table 6-1 for the procedures and commands for configuring the data at MSOFTX3000 to interwork with BSC.

6-7



Table 6-1 Procedures for configuring data at MSOFTX3000 for interworking with BSC Procedure

Command

1: Negotiate and prepare data 1) Configure interworking data between MSOFTX3000 and MGW 2) Add semi-permanent connection at MGW

ADD MGW (LST FECFG) SET DPA ADD TDMIU ADD SPC

2. Configure MTP3 data for interworking with BSC 1) Add MTP DSP

ADD N7DSP

2) Add MTP link set

ADD N7LKS

3) Add MTP route

ADD N7RT

4) Add MTP link

ADD N7LNK

3. Configure SCCP data for interworking with BSC 1) Add SCCP remote signaling point

ADD SCCPDSP

2) Add SCCP subsystems (including local subsystem and remote subsystem)

ADD SCCPSSN

4. Configure BSSAP 1) Add office direction to BSC

ADD OFC

2) Add BSC global indicator

ADD BSC

3) Add location area

ADD LAIGCI (LAI)

4) Add cell

ADD LAIGCI (GCI)

5) Add connection between BSC and MGW

ADD RANMGW

5. Configure A interface trunk circuit 1) Add A interface circuit pool.

ADD ACPOOL

2) Add A interface circuit group.

ADD AIETG

3) Add A interface circuit./Mod A interface circuit state

ADD AIETKC/ MOD AIETKC

6.3 Collecting Data for Interworking with BSC Before configuring data, you need to collect the data for interworking between MSC9880, MGW, and BSC, as shown in Table 6-2. The shadowy columns indicate the parameters that must be negotiated between the two ends for consistency or of which one end must notify the other end. The other parameters are the internal ones of MSOFTX3000.

6-8



Table 6-2 Data for interworking with BSC Item

Data

Basic information

Signaling point network indicator


LAI

GCI



Intra-modul e circuit number (E1 number/tim eslot number)

Circuit

Termination ID (the number of the physical circuit from MGW to BSC)

CIC

MGW index

Trunk route

Office direction

Trunk group

Circuit type

Prefix

Local prefix


Signaling link

WCSU module number

Link set

Link type

6.4 Configuring Data for Interworking with BSC 6.4.1 Negotiating and Preparing Data I. Configuring Interworking Data between MSOFTX3000 and MGW For detailed procedures to configure interworking data between MSOFTX3000 and MGW, refer to Chapter 4 of this manual.

II. Adding Semi-Permanent Connection at MGW z

Add interface board with the command ADD TDMIU.

z

Add semi-permanent connection with the command ADD SPC.

The information of the source TDM and destination TDM to be configured includes frame No., slot No., port No. (E1 No.) and timeslot No. of the ME32 board. You need not configure the optical port.

6-9



6.4.2 Adding MTP Destination Signaling Point I. Background Information Before configuring MTP DSP for BSC, you need to use the LST OFI command to query whether the local MTP OPC has been configured. If not, configure local MTP OPC first. Currently, MSOFTX3000 supports local office multi-signaling-point configuration. However, for 2G network, only No. 0 record in the OFI table is valid. That is, we can only use SPC No.0 in the OFI table to connect the BSC; otherwise, interface A cannot be initialized normally. The network ID used between MSOFTX3000 and BSC (national/active/standby) is to be determined by the No. 96 software parameter. The current default setting of software parameters is to use No. 0 of the national standby network to connect the BSC.

II. Command ADD N7DSP

Important Note: The local office signaling point codes interconnecting BSC must be 14 bits, not 24 bits. Set the network indicator according to the actual networking conditions. The default value is “NATIONAL RESERVED NETWORK”.

III. Major Parameters [DSP Index] This parameter is used to define the index of a DSP, which is allocated uniquely in the system. In SS7 signaling point table, only remote signaling points are configured, while local signaling points cannot be configured. [NI] Set the parameter according to the actual networking. The default option is “National Reserved Network”. [DPC] For BSC, specify the DPC of BSC here. [OPC] It is the signaling point code of the local office available in the nation reserved network. It must be defined in the command SET OFI or ADD OFI first. , and it is the local office signaling point code in the corresponding network indicator of local office signaling point index 0. [STP Flag] 6-10



This parameter is used to set whether the DSP provides STP function. Generally, set this field to "NO". If the DSP has STP function, set this parameter to "YES". [DSP Name] For this parameter, use standard and easily-identified name, for example "BSC-1". [Adjacent Flag] It is used to indicate whether a DSP is a directly connected SP of the local office. For BSC, set it to “TRUE”. [Linkset Select Mask] It indicates how to achieve load sharing of signaling services between multiple MTP link sets to the specified DSP. It is a four-bit binary digit. Unless otherwise specified, it is recommended to use the default value “B1111”, that is, no matter how many MTP link sets exist between the local office and the DSP, MSOFTX3000 will allocate the signaling services among these link sets in load sharing mode. Use the default values for the other parameters.

IV. Related Commands See Table 6-3 for the commands related to MTP DSP configuration. Table 6-3 List of commands related to MTP DSP configuration Command

Description

ADD N7DSP

To add MTP DSP

RMV N7DSP

To remove MTP DSP

MOD N7DSP

To modify MTP DSP attributes

LST N7DSP

To list MTP route data in the MTP route data table of BAM

DSP N7DSP

To display MTP route state

6.4.3 Adding MTP Link Set I. Background Information None

II. Command ADD N7LKS

6-11



Important Note: This command is used to configure MTP link set at MSOFTX3000 for interworking with BSC according to the actual SS7 link configuration conditions. The DSP index of the MTP link set must be valid in the MTP DSP table.

III. Major Parameters [LinkSet Index] You can set it as needed, and the index should be unique globally. To keep consistency and maintainability of the data, set it the same as the parameter “DSP index” in the ADD N7DSP command. [Adjacent DSP Index] It refers to the index of a DSP to which a link set belongs. Here it is the DSP index of the peer BSC It must be defined in the command ADD N7DSP first and then referenced here. . [Linkset Name] You can set it as needed. It is recommended to use a standard name with unique characteristics for the sake of identification, for example, "BSC1". It is recommended that the name used here be the same as the paraemter “DSP name” defined in the ADD N7DSP command. [Link Select Mask] It indicates how to achieve load sharing of signaling services between multiple MTP links in the specified MTP link set. It is a four-bit binary digit. Unless otherwise specified, it is recommended to use the default value “B1111”, that is, no matter how many MTP links are in the link set, MSOFTX3000 will allocate the signaling services among these links in load sharing mode.

IV. Related Commands See Table 6-4 for the commands related to MTP link set configuration. Table 6-4 List of commands related to MTP link set configuration Command

Description

ADD N7LKS

To add an MTP link set

RMV N7LKS

To remove an existing MTP link set

MOD N7LKS

To modify an existing MTP link set

LST N7LKS

To list MTP link set data in the MTP link set data table of BAM

6-12



6.4.4 Adding MTP Route I. Background Information None

II. Command ADD N7RT

III. Major Parameters [Linkset Index] It is used to set the link set to which a link belongs. This parameter must be defined in the command ADD N7LKS and then referenced here. . [DSP Index] It is used to identify the DSP of the specified MTP routeHere it is the DSP index of the peer BSC, and has been defined in the ADD N7DSP command. [Route Priority] It is used to set the routing priority of an MTP link set (signaling route). The link set with the highest priority will be selected first; while that with lower priority will be selected only after all signaling routes with higher priority are unavailable. ”0” stands for the highest priority, ”1” stands for the second, and so on. Generally the default value "0" is used. [Route Name] It is recommended to use a standard name with unique characteristics for the sake of identification, for example, "BSC-1". It is recommended that the name used here be the same as the parameter “DSP name” defined in the ADD N7DSP command.

IV. Related Commands See Table 6-5 for the commands related to MTP route configuration. Table 6-5 List of commands related to MTP route configuration Command

Description

ADD N7RT

To add an MTP route

RMV N7RT

To remove an existing MTP route

MOD N7RT

To modify an existing MTP route

LST N7RT

To list MTP route data in the MTP route data table of BAM

DSP N7RT

To display MTP route state

6-13



6.4.5 Adding MTP Link I. Background Information Because MSOFTX3000 can provide MTP links in different ways, you need to select different link types according to the actual networking when you set the MTP link data. z

If MSOFTX3000 provides MTP links through E1 (born over TDM), select ”TDM 64K LINK” or “TDM 2M LINK”.

z

If MSOFTX3000 provides MTP links through built-in SG (born over M2UA), select ”M2UA 64K LINK” or “M2UA 2M LINK”.

For detailed information about MTP link configuration, see Section 6.2.2 MTP Link Configuration.

II. Command ADD N7LNK

III. Major Parameters [Moudle Number] If MSOFTX3000 provides an MTP link through E1 (born over TDM), this parameter is used to specify the module number of the WCSU or WSGU processing this MTP protocol. If MSOFTX3000 provides an MTP link through built-in SG (born over M2UA), this parameter is used to specify the module number of the WBSG, WSGU, or WIFM processing this MTP protocol. This parameter must be defined in the command ADD BRD first and then referenced here. [Link No.] It specifies the MTP link number in the following two cases: 1)

If MSOFTX3000 provides an MTP link through E1 (born over TDM), this parameter is used to specify the physical number of this MTP link in the WCSU or WSGU. One WCSU or WSGU can be inserted with two CPC sub-boards and each CPC sub-board can process sixteen 64-kbit/s MTP links (due to the restriction of the CPC signaling processing capability) or one 2-Mbit/s MTP link. Therefore, set this parameter as follows:

z

If 64-kbit/s MTP links are provided, the link number will range from 0 to 31. 0–15 are allocated for the lower CPC sub-board and 16–31 are for the upper CPC sub-board.

z

If a 2-Mbit/s MTP link is provided, the link number can only be set to 0 or 16. Set it to “0” for the lower CPC sub-board, and to “16” for the upper CPC sub-board.

2)

If MSOFTX3000 provides an MTP link through built-in SG (born over M2UA), this parameter is used to specify the logical number of this MTP link in the WBSG, WSGU or WIFM. The link number ranges from 0 to 31. In the same WBSG, WSGU or WIFM, all MTP links must be numbered uniformly, that is, one WBSG, WSGU or WIFM can support a maximum of 32 MTP links. 6-14



[Link Type] It specifies the type of an MTP link. You must set it correctly based on the actual networking; otherwise, the MTP link will not function well. The meaning of the options are as follows: z

TDM 64K link: 64-kbit/s MTP links born over TDM. It is provided by MSOFTX3000 directly.

z

TDM 2M link: 2-Mbit/s MTP links born over TDM. It is provided by MSOFTX3000 directly.

z

M2UA 64K link: 64-kbit/s MTP links born over M2UA. It is provided by bulilt-in SG (UMG8900, for example).

z

M2UA 2M link: 2-Mbit/s MTP links born over M2UA. It is provided by bulilt-in SG (UMG8900, for example).

For the BSC, a 64-kbit/s MTP link is provided. [Link Name] It is recommended to use a standard name with unique characteristics for the sake of identification and that the name is the same as the parameter “DSP name” defined in the ADD N7DSP command, for example "BSC-1". [Start Circuit No.] It specifies the number of the E1 timeslot seized by an MTP link. It is valid only when the MTP link is born over TDM. Set it by the following principles (with the WCSU+WEPI configuration as an example): z

Because you have designated the module number of the WCSU processing the MTP protocol, and the WCSU and WEPI have one-to-one corresponding relationship in slot position, the E1 timeslot seized by this MTP link can only be provided by the WEPI (back board) in the same slot as the WCSU. One pair of active and standby WEPIs can provide eight active E1 ports. The timeslots are numbered from timeslot 0 of the first E1 in ascending order, ranging from 0 to 255.

z

MTP links cannot seize timeslot 0 of each E1 (synchronization timeslot), that is, among the above timeslots, timeslots 0, 32, 64, 96, 128, 160, 192, and 224 are unavailable.

z

For 64-kbit/s MTP links, if the link number ranges from 0 to 15, the start circuit number will range from 1 to 127. If the link number ranges from 16 to 31, the start circuit number will range from 129 to 255.

z

For a 2-Mbit/s MTP link, if the link number is 0, the start circuit number can only be 1, 33, 65 or 97. If the link number is 16, the start circuit number can only be 129, 161, 193 or 225.

[Linkset Index] It is used to set the link set to which a link belongs. It must be defined in the command ADD N7LKS first and then referenced here. [Time Slot Number] 6-15



It defines the number of the seized timeslots. It is valid only when “Link Type” is set to ”TDM 2Mbit/s” for specifying how many 64-kbit/s timeslots are seized by a 2-Mbit/s link. It must be consistent with the setting at the peer end. By default, it is 31. [Signalling Link Code] It is a parameter for MSOFTX3000 to interconnect with the peer end, specifying the logical number of an MTP link in its MTP link set. This parameter should be consistent with that of the peer end. As described in the MTP protocol, signaling link code (SLC) is a four-bit field ranging from 0 to 15, and the SLC of each signaling link in one link set must be numbered uniquely in sequence. [Signaling Link Code Send] It is used for self-loop test on two MTP links in the local office. Set it by the following principle: z

When the self-loop test on the MTP links is not started, you must set this parameter and SLC to the same value. Otherwise, signaling interconnection will fail. When this parameter is not configured, its default must be consistent with the signaling link code.

z

When the self-loop test on the MTP links is started, you must set this parameter and SLC to different values complying with the principles of ”SLC of link 1=SLC Send of link” and “SLC of link 2=SLC Send of link 1”.

[Link Priority] It is used to set the routing priority of an MTP link. The link with the highest priority will be selected first; while that with lower priority will be selected only after all signaling links with higher priority are unavailable. ”0” stands for the highest priority, ”1” stands for the second, and so on. [Satellite Flag] It identifies whether an MTP link is born over the satellite circuit. You need to set it according to the actual situation. Generally, set it to “No". [Link Congestion Begin] It is expressed in percentage. When the signaling load on an MTP link reaches the preset threshold, congestion control will be started. At this time, this MTP link cannot be used for transmission until the congestion is unblocked. By default, it is 80. [Link Congestion End] It is expressed in percentage. When the signaling load on an MTP link is lower than the preset threshold, congestion control will be stopped. At this time, this MTP link can be used for transmission again. By default, it is 70. [Test Code] and [Test Code Length] These two parameters are used for test on MTP links. [Handle Module Number]

6-16



It defines the module for processing signaling messages above the MTP layer. If you specify a handle module number, the subscriber messages above the MTP layer will be processed by this module. Otherwise, when MTP links are configured on the WCSU or WSGU, the subscriber messages above the MTP layer will be processed by the WCSU or WCCU; when MTP links are configured on the WBSG, WSGU or WIFM, the subscriber messages above the MTP layer will be dispatched by the WBSG, WSGU or WIFM to the corresponding module for processing automatically based on the load sharing principle. Generally, you need not set it at all and the MSOFTX3000 will dispatch them automatically. Use default values for the other parameters.

IV. Related Commands See Table 6-6 for the commands related to MTP signaling link configuration. Table 6-6 List of commands related to MTP signaling link configuration Command

Description

ADD N7LNK

To add an N7 signaling link

RMV N7LNK

To remove an existing N7 signaling link

MOD N7LNK

To modify an exiting N7 signaling link

LST N7LNK

To list the information of all configured N7 signaling links

DSP N7LNK

To display N7 link state

DSP N7DLNK

To display N7 link state of DSP

INH N7LNK

To inhibit an N7 signaling link to block the management of the N7 link

UIN N7LNK

To enable an N7 signaling link to unblock the management of the N7 link

ACT N7LNK

To activate an N7 signaling link

DEA N7LNK

To deactivate an N7 signaling link

6.4.6 Adding SCCP Remote Signaling Point I. Background Information This command is used to configure the signaling point information for the peer BSC. One SCCP DSP record is uniquely identified by NI, OPC and DPC. It is required that the OPC and DPC must be consistent with those of the lower layer (MTP3/MTP3B/M3UA) when SCCP DSP is configured. As MTP3 signaling bearer mode is adopted between local office and BSC, the DPC of the BSC must be first configured in the MTP3 DSP table. Use the LST N7DSP

6-17



command to check whether the BSC DPC is consistent with that in the MTP3 DSP table.


III. Major Parameters [DPC Index] It uniquely identifies an SCCP DSP, ranging from 0 to 511. It must be noted that the “DSP Index” defined here is different from the “DSP Index” defined in ADD N7DSP and “Destination Entity Index” defined in ADD M3DE, and there is no reference relation among them. [NI] It identifies the signaling network where the SCCP DSP is resident. [DPC] It refers to destination signaling point code. Use the DPC of the peer BSC. It must be defined in ADD N7DSP or ADD M3DE first and then referenced here. For BSC, the DPC is the national reserved 14-bit SPC. [OPC] It refers to the originating point code of the local office in the same network indicator. You can query it with the LST OFI command. It must be specified in the command SET OFI first and then referenced here. For BSC, it is the national reserved network signaling point code of No. 0 record in the OFI table. [Load Sharing Function Flag] It is used to set whether MSOFTX3000 supports the load sharing function or backup function of SCCP DSP. The meaning of the options are as follows: z

No Standby DSP: Not support backup function

z

Backup DSP: Support active/standby function

z

Loadshare DSP: Support load sharing function

[Standby DSP Index] It is valid only when MSOFTX3000 supports the load sharing function or backup function of SCCP DSP. It is used to specify the standby DSP of SCCP.

IV. Related Commands See Table 6-7 for the commands related to SCCP DSP configuration.

6-18



Table 6-7 List of commands related to SCCP DSP configuration Command

Description

ADD SCCPDSP

To add an SCCP DSP

RMV SCCPDSP

To remove an existing SCCP DSP

MOD SCCPDSP

To modify an existing SCCP DSP

LST SCCPDSP

To list the information of all configured SCCP DSPs

DSP SCCPDSP

To display statuses of all configured SCCP DSPs

SET SCCPDSP

To manage and maintain SCCP DSPs

6.4.7 Adding SCCP Subsystem I. Background Information The following command ADD SCCPSSN is used to add SCCP subsystems in MSOFTX3000 (local end) and the BSC (remote end). Subsystem number (SSN) is the local addressing information used by SCCP to identify the SCCP users under a SP. z

SSN of the MSOFTX3000 at the local end is base station subsystem application part (BSSAP)/intelligent network application protocol (INAP).

z

The configured SSN at the BSC side includes SCCP Management Subsystem (SCMG) and BSSAP/INAP.

The local MSC, VLR, and SCMG must be configured. If they have been configured, they need not to be configured here. Be sure to use the LST SCCPSSN command to have a check for avoiding repeated configuration.


III. Major Parameters [SSN] It is used to identify the SCCP subsystem, and it is unique in the system. [NI] It is used to set the indicator of the network where the SCCP subsystem is located. [SSN] This parameter refers to subsystem number. For both MSOFTX3000 and BSC, you need to add SCMG and BSCAP/INAP subsystems. [SPC]

6-19



It is used to specify the destination SPC of the corresponding subsystem, that is, the recipient of SCCP messages. For configuring local and remote SCCP subsystems, you need to set BSC SPC and OPC here. [OPC] It is used to specify the originating SPC of the corresponding subsystem, that is, the sender of SCCP messages. For each subsystem, this OPC is a local SPC. It must be defined in the command SET OFI first and then referenced here. [Local Concerned SSN1]–[Local Concerned SSN5] It is used to define the index of a subsystem which is related to the specified subsystem and has the same DPC as the subsystem. You can define a maximum of five indexes. If there is no related subsystem, use the default option “UNDEFINED”. Generally, the default value is used. [Backup SSN index] It is used to specify the index of the backup subsystem of a specified subsystem. It is valid only when MSOFTX3000 supports the load sharing function or backup function of SCCP DSP. If there is no subsystem, use the default value “65535”.


Description

ADD SCCPSSN

To add an SCCP subsystem

RMV SCCPSSN

To remove an existing SCCP subsystem

MOD SCCPSSN

To modify an existing SCCP subsystem

LST SCCPSSN

To list SCCP subsystems

SET SCCPSSN


DSP SCCPSSN

To display SCCP subsystems in the host

6.4.8 Adding Office Direction to BSC I. Background Information II. Command ADD OFC

6-20



Note: This command is used to set the office direction from MSOFTX3000 to BSC.

III. Major Parameters [Office Direction] It is allocated uniquely in the system and used to identify an office direction. [Office Direction Name] It is recommended to use a standard name for the sake of identification, for example, BSC4. [Opposition Office Type] Select “BSC (BSC)" here. [Peer Office Level] It specifies the level of the peer office, High (upstream office), Same (office of the same level), or Low (downstream office). Set it according to the actual situation. The level of BSC is lower than MSOFTX3000 in the network. Here select "LOW (INFERIOR)". [Peer Office Attribute] It specifies the equipment type used by the peer office. For this parameter, select "BSC (BSC)" here. [Network ID] The network ID of the MSOFTX3000 must be consistent with that of the peer end. [Destination Point Code1]–[Destination Point Code16] For these parameters, enter the DPCs of BSC. They must be negotiated with BSC for consistency, and they are associated with the DPCs of BSC in the ADD SCCPDSP command. For the other parameters, use the default values.

IV. Related Commands See Table 6-9 for the commands related to office direction configuration. Table 6-9 List of commands related to office direction configuration Command

Function

ADD OFC

To add a new office direction

RMV OFC


MOD OFC


LST OFC

To list attributes of a configured office direction

6-21



6.4.9 Adding BSC Global Indicator I. Background Information None

II. Command ADD BSC

III. Major Parameters [Network ID] The network ID of the MSOFTX3000 must be consistent with that of the peer end. [Destination Point Code] It refers to DPC. For this parameter, enter the BSC DSP code. [Home Module Number1]–[Home Module Number10] It refers to the module number of the WCCU or WCSU controlling BSC. Note that we do not mean to specify the processing module of the BSC, but to define the maintenance module of the BSC. [Route Select Source Code] The route selection source code is the category No. of outgoing route selection strategy of different call sources. This parameter has been defined in the ADD RTANA command. [Location Area ID] It specifies the unique LAI to which BSC belongs. If [Location Area Not Unique Flag] is set to “FALSE (ONLY ONE)”, you must set this parameter.

IV. Related Commands See Table 6-10 for the commands related to BSC configuration. Table 6-10 List of commands related to BSC configuration Command

Description

ADD BSC

To add a BSC

RMV BSC

To remove an existing BSC

MOD BSC

To modify the attributes of an existing BSC

LST BSC

To list BSC information configured

6-22



6.4.10 Adding LAI or CGI I. Backgrond Information None

II. Command ADD LAIGCI

Note: This command is used to configured location area and cell, and the "LA Category" of this command is used distinguish location area and cell.

III. Major Parameters [Global Cell ID] It refers to location area ID or cell ID. If adding a location area, set a 9-bit LAI. If adding a cell, set a 13-bit GCI. Whether a location area or a cell is to be configured is determined by the parameter “LA Category”. These IDs are given during network planning. [MSC Number of the LAI or Cell] It refers to the number of the MSC to which a location area or cell belongs. This number is provided by the operator, and defined in the ADD INOFFMSC command. [VLR Number of the LAI or Cell] It refers to the number of the VLR to which a location area or cell belongs. This number is provided by the operator, and defined in the ADD INOFFMSC command. [Perform Roaming Analysis] Roaming analysis is performed toward a specific LAI. Set this parameter to YES if roaming restriction is needed for an LAI. [LA Category] When the current record is a location area, set this parameter to "LAI"; if the current record is a cell, set this parameter to "GCI". [LA Type] This parameter is used to decide whether the current LAI/CGI belongs to the local VLR or adjacent VLR. Generally, MSC and VLR are set together. To guarantee handover of mobile stations between MSCs, the information on the cell of the adjacent MSC bordering on the local MSC should be recorded. The LAI/CGI of the local MSC/VLR is

6-23



marked "Local VLR" and the location area/cell of non-local MSC/VLR is marked as "Adjacent VLR". The following parameters are available only when the parameter "LA Type" is set to "Local VLR". [Early Assignment Flag] This parameter is used to indicate the circuit assignment time. For calling subscribers, early assignment means that an assignment request is initiated right after the network receives the CALL PROCEEDING message from the calling party, while late assignment means that an assignment request is initiated after the network sends ALERTING message to the calling party. For called subscribers, early assignment means that an assignment request is initiated right after the network receives the CALLCONFIRMED message from the called party, while late assignment means that an assignment request is initiated after the network receives the CONNECT message from the called party. [Location No.] It is the indicator corresponding to a location area, and it is used to enhance roaming restriction. [Home BSC Network Indicator 1]–[Home BSC Network Indicator 10] If a location area contains multiple BSCs, enter the network indicators of all BSCs for this parameter. If a location area only corresponds to one BSC, set this parameter to the network indicator of the BSC corresponding to the location area. When adding a cell, set this parameter to the network indicator of the BSC to which the cell belongs. [Home BSC DPC 1]–[Home BSC DPC 10] If a location area contains multiple BSCs, enter the DPCs of all BSCs for this parameter. If a location area only corresponds to one BSC, set this parameter to the DPC of the BSC corresponding to the location area. When adding a cell, set this parameter to the DPC of the BSC to which the cell belongs. [Call Source Code] If refers to the call source code used when the current location area/cell initiates a call. This parameter is defined in the ADD CALLSRC command. [Office No.] Set it to the number of the office direction corresponding to BSC. This parameter is defined in the ADD OFC command. For the other parameters, use the default values.

IV. Related Commands See Table 6-11 for the commands related to LAI/CGI configuration.

6-24



Table 6-11 List of commands related to LAI/CGI configuration Command

Description

ADD LAIGCI

To add LAI or CGI

MOD LAIGCI

To modify LAI or CGI

LST LAIGCI

To list LAI or CGI

RMV LAIGCI

To remove LAI or CGI

6.4.11 Adding Access Media Gateway I. Background Information None

II. Command ADD RANMGW

Note: This command is used to create the connection between the BSC office direction and MGW.

III. Major Parameters [Office Number] It is used to identify an office direction of an entity that a specific MGW is connected to. It is defined in the ADD OFC command. [Media Gateway Index] It is defined in the ADD MGW command.

IV. Related Commands See Table 6-12 for the commands related to the configuration of access media gateway. Table 6-12 List of commands related to the configuration of access media gateway Command

Function

ADD RANMGW

To add a new connection between RAN entity and MGW

RMV RANMGW

To remove an existing connection between RAN entity and MGW

LST RANMGW

To list connections between RAN entity and MGW

6-25



6.4.12 Adding A-interface Circuit Pool I. Background Information None.

II. Command ADD ACPOOL

Important Note: This command is used to set the bearer capability of A-interface circuit. You can configure multiple A-interface circuit pools with different bearer capabilities. In this way, when you add A-interface circuit group by designating the circuit group into different circuit pools, you can configure the A interface circuits in different office directions with different bearer capabilities.

III. Major Parameters [Circuit Pool No.] The parameter refers to the orderly number of an A interface circuit pool. [GSM Bearer Capability] For this parameter, use the default option "Select All".

IV. Related Commands See Table 6-13 for the commands related to the configuration of A-interface circuit pool. Table 6-13 List of commands related to the configuration of A-interface circuit pool Command

Description

ADD ACPOOL

To add an A-interface circuit pool

MOD ACPOOL

To modify an A-interface circuit pool

RMV ACPOOL

To remove an A-interface circuit pool

LST ACPOOL

To list A-interface circuit pools

6.4.13 Adding A-interface Trunk Group I. Background Information None.

6-26



II. Command ADD AIETG

III. Major Parameters [Trunk Group] The parameter refers to the number of an A interface trunk group. [MGW Index] The parameter indicates the index number of an MGW to which a trunk group belongs. The MGW has been defined in the ADD MGW command. [OPC] For this parameter, enter the national reserved network SPC of the local office. It is associated with this parameter in the SET OFI command. [DPC] For this parameter, enter the DPC of the peer end. This parameter is the same as that set in the ADD N7DSP command. [Call-in Authority] This parameter is used to control the authorities of the calling-in trunk circuits. Only those allowed types of calls can get through. You can specify this parameter as needed, or select all default values. [Call-out Authority] This parameter is used to control the authorities of the calling-out trunk circuits. Only those allowed types of calls can get through. You can specify this parameter as needed. Generally, set it to "All allowed" because the calling-out authorities are controlled at the subscriber end. [Circuit Pool No.] It refers to the circuit pool number of A interface in the local office, and the value is defined in the ADD ACPOOL command.

IV. Related Commands See Table 6-14 for the commands related to the configuration of A-interface trunk group. Table 6-14 List of commands related to the configuration of A-interface trunk group Command

Description

ADD AIETG

To add an A-interface trunk group

MOD AIETG

To modify an A-interface trunk group

LST AIETG

To list A-interface trunk group information

6-27



Command RMV TG

Description To remove a trunk circuit group (including A-interface trunk group)

6.4.14 Adding A-interface Trunk Circuit I. Background Information When adding a trunk circuit, note that the trunk group to which the trunk circuit belongs should have existed. For detailed information about relationships between “Start CIC”, “Start Circuit Termination ID”, “Start Circuit”, and “End Circuit”, see section 6.2.3

“Trunk Circuit and

TID Configuration” in this chapter.

II. Command ADD/MOD AIETKC

III. Major Parameters [Module] It refers to the module number of the WCCU or WCSU to which the A interface trunk circuit belongs. You can query this parameter with the LST MDU command. [Trunk Group] It refers to the number of the A interface trunk group to which a trunk circuit belongs. This parameter is defined in the ADD AIETG command. [Start Circuit] It is used internally in MSOFTX3000, and corresponds to TID and CIC. It must be unique within the office and it is recommended that the value be consistent with that of TID. [End Circuit] It is used internally in MSOFTX3000, and corresponds to TID and CIC. It must be unique within the office and it is recommended that the value be consistent with that of TID. [Start CIC] This parameter refers to the unique indicator of an A interface circuit. It must correspond to the Start CIC at the BSC side. [Circuit State] This parameter defines the state of a circuit or a batch of circuits added. Use the default value “Available”. [Start Circuit Termination ID]

6-28



This parameter refers to the ID of a termination corresponding to the start circuit. It is an important parameter to identify a physical circuit, and is used to indicate through which E1 the MGW is connected to BSC. This parameter needs to be configured in MGW to make Termination ID correspond to E1 timeslot one to one, so as to get the start termination ID of the E1 connecting with BSC.

IV. Related Commands See Table 6-15 for the commands related to the configuration of A-interface trunk circuit. Table 6-15 List of commands related to the configuration of A-interface trunk circuit Command

Description

ADD AIETKC

To add an A-interface trunk circuit

MOD AIETKC

To modify an A interface trunk circuit

DSP AIETKC

To display the status of A-interface trunk circuits of the host

RMV TKC

To remove a trunk circuit (including A-interface trunk circuit)

BLK AIETKC

To block an A interface trunk circuit

UBL AIETKC

To unblock an A interface trunk circuit

RST AIETKC

To reset an A interface trunk circuit

Important Note: After adding a circuit, use the MOD AIETKC command to set timeslot 0 (synchronization timeslot) of the E1 and set the timeslot configured as a link to “Unavailable”. Select timeslot 0 of the E1 and the timeslot configured as a link (associated with “Start Circuit No.” in the ADD N7LNK command) for the parameters “Start Circuit” and “End Circuit”. Select “Unavailable” for the parameter “Circuit State”.

6-29




SCP

SMC

GMLC

HLR

MAP/TDM

MAP/TDM

MAP/TDM

MAP/TDM

MSC Server

MSOFTX 3000

ISUP/TDM

H.248,RANAP /IP

BSSAP+/TDM

SGSN


MGW

MGW (SG)

IP/TDM

RANAP/AAL2/ATM

ISUP/TDM

PSTN

BSSAP/TDM

RNC

BSC

Figure 6-6 Networking of MSOFTX3000 As shown in the figure, MSOFTX3000 and MGW are integrated; The semi-permanent connection is created on MGW, which transparently transmits A-interface messages between BSC and MSOFTX3000; TDM bearer is adopted between MSOFTX3000 and MGW as well as between MGW and BSC. This example adds a BSC, which is connected to MGW. Table 6-16 shows the related information. For the local office information, refer to Table 3-14 in Chapter 3.

6-30



Table 6-16 BSC information table Item

Data

Basic information / Signaling link

/ Circuit

/ Trunk route

Prefix

/



LAI

GCI

C03

National reserved

460 00 0001

460 00 0001 0001 Intra-module circuit number (E1 number/time slot number)

Link type

112 (3/16)

64 kbit/s

WCSU module number

Link set



22

3

3

0


CIC

MGW index

96–127

0–31

1

Office direction

Trunk group

Circuit type

3

3

BSSAP

Local prefix


1390752

65535

6.5.2 Configuration Description //Query the information. LST OFI:;

//Query the OPC whose NI=NATB

LST SCCPSSN: NI=NATB, SPC="C04"; //Query whether the local end has been configured with SCMG subsystem LST BRD: BT=WCSU; //Query the type of the signaling link configured on WCSU

//Add MTP data. ADD N7DSP: DPX=3, NI=NATB, DPC="C03", OPC="C04", DPNAME="BSC-3"; ADD N7LKS: LSX=3, ASPX=3, LSNAME="BSC-3"; ADD N7RT: LSX=3, DPX=3, RTNAME="BSC-3"; ADD N7LNK: MN=22, LNKN=3, LNKNAME="BSC3-1", LNKTYPE=0, TS=112, LSX=3, SLC=0;

//Add SCCP data.

6-31


SCCPDSP:

DPX=3,


NI=NATB,

DPC="C03",

OPC="C04",

DPNAME="BSC-3",

SHAREFLAG=NONE; ADD

SCCPSSN:

SSNX=7,

NI=NATB,

SSN=BSSAP/INAP,

SPC="C04",

OPC="C04",

SSNNAME="LOCAL-SCMG"; ADD

SCCPSSN:

SSNX=8,

NI=NATB,

SSN=SCMG,

SPC="C03",

OPC="C04",

SSNNAME="BSC-SCMG"; ADD

SCCPSSN:

SSNX=9,

NI=NATB,

SSN=BSSAP/INAP,

SPC="C03",

OPC="C04",

SSNNAME="BSC-BSSAP";

//Add BSSAP data. LST INOFFMSC:; //Query MSC/VLR number LST MGW:; //Query MGW index

ADD OFC: OFFICEDIR=3, ON="BSC-3", OOFFICT=BSC, DOL=LOW, DOA=BSC, NI=NAT2, DPC1="C03", SIG=MTP3; ADD BSC: DPC="C03", BSCNM="BSC-3", MSCMN1=22, RSSC=0, BTSNUM=1, MLAIF=FALSE, LAI="460000001";

ADD

LAIGCI:

GCI="460000001",

LAIGCINAME="BSC3-LAI",

MSCN="8613600004",

VLRN="8613600004", LAICAT=LAI, LAIT=HVLR, BSCDPC1="C03", OFFICNUM="3"; ADD LAIGCI: GCI="4600000010001", LAIGCINAME="BSC3-GCI", MSCN="8613600004", VLRN="8613600004", LAICAT=GCI, LAIT=HVLR, BSCDPC1="C03",OFFICNUM="3"; ADD RANMGW: OFFICENO=3, MGWIDX=1;

//Add trunk data. ADD

ACPOOL:

BCR=SFR1-1&SFR2-1&SFR3-1&SHR1-1&SHR2-1&SHR3-1&DFR-1&DHR-1; ADD AIETG: TG=3, MGW=1, SOPC="C04", SDPC="C03", TGN="BSC-3", CPN=0; ADD AIETKC: MN=22, TG=3, SC=96, EC=127, SCIC=0, SCF=TRUE, TID=96; MOD AIETKC: MN=22, SC=112, EC=112, CS=UNU; MOD AIETKC: MN=22, SC=96, EC=96, CS=UNU;

6-32

CPNO=0,


Chapter 7 Configuring Data for Interworking with HLR

Chapter 7 Configuring Data for Interworking with HLR 7.1 Introduction to the Chapter This chapter describes the data configuration process at MSOFTX3000 for interworking with a Home Location Register (HLR). This chapter contains the following sections: z

Related Concepts

z

Collecting Data for Interworking with HLR

z

Configuring Data for Interworking with HLR

z


7.2 Related Concepts 7.2.1 HLR I. Overview of HLR HLR is used to store subscription information and provide service support, enhanced authentication,

and

management

of

subscription

information

(including

adding/deleting/modifying subscribers). MSC Server interworks with HLR through the C/D interface and applies Mobile Application Part (MAP) protocol. Each HLR has an integrated service digital network (ISDN) number used to identify the HLR during signaling exchange. This number can be used to identify an HLR worldwide. The structure of an MSISDN number is CC+MAC+H0H1H2H3+ABCD, so the structure of an HLR ISDN number can be CC+MAC+H0H1H2H3+0000.

II. Originating Signaling Point In the system, a local signaling point is also called an OSP. To define an OSP, the following data shall be confirmed: z

SPC

z

ID of the network where the SP is located

z

Whether to provide SCCP layer function

z

Whether the STP function is available

MSOFTX3000 is designed with the multi-SP function, that is, in the same signaling network, and one MSOFTX3000 can define up to 16 OPCs instead of 1 in general cases. After the introduction of the multi-SP function, there can be multiple SPs at the 7-1



local office corresponding to the same DSP. In this way, the protocol restriction that only 16 signaling links can exist between two network nodes becomes invalid.

III. Destination Signaling Point The DSPs and network structure to be set for the local office are determined by the operation department. Those SPs connected with the local office through signaling links, such as DPC1 and STP as shown in Figure 7-1, must be configured. For DPC2 in Figure 7-1, as it has no direct signaling link to the local office, whether to configure it is determined by the addressing mode of the operator. If this SP employs DPC for addressing, it shall be configured; if GT is used, it shall not. DPC2

STP

DPC1

Signaling link· Local office

No signaling link but signaling relation

Figure 7-1 DSP configuration To add a DSP, you need to determine the following data: z

SPC

z

ID of the network where the SP is located

z

The OPC related to this SP

z

Whether it is the adjacent SP, that is, whether the DSP is directly connected through the link

z

Selection mask of the link set in the signaling route to this SP

z

Whether the SP has STP function

If the DSP is an adjacent SP (that is, an associated signaling link exists between this DSP and the local office), you must define the signaling link set. In this case, the following data have to be determined: z

Signaling link set number

z

The adjacent DSP to which the signaling link set is connected

z

Signaling link selection mask

Each link set can contain up to 16 signaling links. The signaling link selection mask is used to implement load sharing between signaling links in a link set. The coding schemes of RNC and BSC are related to the networking mode. For example, RNC and BSC adopt National Reserved Network Code, that is, 14-digit SPC in China. Other entities connected with MSC, such as, HLR, PSTN and other MSCs, all adopt National Network Code, that is, 24-digit SPC. 7-2



IV. Signaling Link Set All parallel signaling links between two adjacent SPs form a signaling link set, as shown in Figure 7-2: Signaling link set

Signaling point 1

Signaling point 2

Figure 7-2 Signaling link set

Note: From the above definitions, it can be concluded that there is one and only one signaling link set between two adjacent DSPs. The basic unit composing the signaling link set is the signaling link. One signaling link set can contain one or multiple signaling links.

V. Signaling Route The signaling route to one DSP can be classified as direct route and alternative route. The direct route indicates that there is no STP on the signaling route between the local office and the DSP. The alternative route is the signaling route on which signaling messages are transferred to the DSP through STPs. To define a signaling route, you must define the following data: z

DSP index

z

Link set number

z

Priority

It can be seen that the signaling route specifies the correspondence between the DSP and the link set. In other words, the signaling route determines which link set is applied for transmitting signaling messages to the DSP. One signaling route only corresponds to one link set; while one link set can correspond to multiple signaling routes. The link set corresponding to the direct route is the one between the OSP and the DSP. The link set corresponding to the alternative route is the one between the OSP and the STP.

7-3



If both the direct route and alternative route exist for a DSP, you can enable the signaling messages to take the direct route as the first priority and the alternative route as the second choice by specifying priorities of the signaling routes. The smaller the value is, the higher the priority will be. There can be at most 16 routes with the same priority level, which can perform load sharing as well. As shown in Figure 7-3, there are two routes from SP A to SP C, including a direct route A-C and an alternative route A-B-C. Direct route A-C corresponds to link set 1; while alternative route A-B-C corresponds to link set 2.

Link set 2 B A

Link set 3 Link set 1 C

Figure 7-3 Direct route and alternative route

VI. Signaling Link The signaling link is composed of the signaling data link and the signaling terminal. The signaling data link is a kind of physical medium for signaling transmission. Any timeslot in the pulse code modulation (PCM) system can be specified as the signaling data link, except for timeslot 0. In the PCM primary group, timeslot 16 is generally specified as the signaling data link. The signaling terminal is responsible for the MTP layer 2 processing of the data in a specified signaling data link. MTP identifies different links in a link set using the signaling link code (SLC). The sent signaling link code (SSLC) is the code sent to the remote signaling entity for identifying the signaling link. Normally, SLC and SSLC should be configured with the same value. Moreover, the remote signaling entity link connected with the local end should also be configured with the same SLC and SSLC. The SLCs in the same link set will be numbered uniformly no matter whether they are in the same WCSU. SLC is different from SSLC during self-loop test of the signaling link. The SLC of the link at the self-looped E1 should be equal to the SSLC at the other end; while the SLC at the other end should be equal to the SSLC at the local end.

VII. MTP Load Sharing Load sharing comprises two types:

7-4



z

Load sharing among links in one link set

z

Load sharing among links in different link sets

In the first type, the load in one link set is shared among the links within the link set according to the signaling link selection (SLS) code, as shown in Figure 7-4. There are two signaling links between SP A and SP B. The signaling messages are allocated to these two links according to whether the last bit of the SLS of the signaling message is 0 or 1. SLS=XXX0 A

SLS=XXX1

B

Figure 7-4 Load sharing within one link set In the second type, the signaling services are shared among links in different link sets, as shown in Figure 7-5. XXX0 A

D

E

B

F

C

XXX1 XXXX

Figure 7-5 Load sharing among different link sets Communication through different signaling connections of one signaling link set does not need to comply with the same signaling sharing principle. For example, in Figure 7-5, the services to B are shared between link sets DE and DF based on SLS while the services to C are only undertaken by link set DF because of EC fault. To achieve the above two signaling sharing modes, MSOFTX3000 utilizes signaling link set selection mask and SLS mask to evenly distribute signaling messages according to SLS. There are two sources for the SLS code. In the telephone user part (TUP)/ISDN user part (ISUP) message, it is the lower four bits of the CIC; while in the SCCP message, it is allocated by SCCP circularly. Since SLS changes circularly, it can be ensured that the load of links or between link sets is equal if the load is shared according to SLS.

VIII. SCCP DSP The SCCP DSP to be defined at the local office must first have SCCP signaling relation with the local office. Besides, its corresponding data must have been defined at the MTP layer. Generally speaking, the SCCP DSPs to be defined include SCCP SPs that

7-5



have direct signaling routes to the local office, SCCP STPs (SPs supporting the SCCP transfer function), and the DSPs addressing in DPC + SSN mode.

C

D

A

B

Figure 7-6 SCCP DSP As shown in Figure 7-6, A is the local office, B and D are the SPs that have the SCCP signaling relation with the local office, and C is the SCCP STP. If the addressing mode from the local office to D is DPC+SSN, the SCCP DSPs to be configured for the local office are B, C and D. Suppose the addressing mode from the local MSC to D is DPC+GT, the SCCP DSPs to be configured for the local office are B and C. Therefore, GT translation shall be performed for C. To define the SCCP DSP, you must set the following data: z

SPC

z

Local SPC

z

Load sharing SP index

IX. SCCP DSP Working Mode SCCP remote SPs can work in three modes: independent mode, active-standby mode, and load sharing mode. z

Independent mode indicates that there is no standby SP for the remote SP.

z

Active-standby mode indicates that the remote SP has standby SP, and when SCCP routes the messages, if this SP is "Available", the messages will be sent to it; otherwise, the messages will be sent to its standby SP.

z

Load sharing mode indicates that the remote SP is configured with standby SP, and when SCCP routes messages, if both SPs are "Available", the messages will be sent to both of them in turn. If only one SP is available, th messages will be sent to the available one.

The messages that SCCP sends to the remote SP will be sent to two remote load-sharing SPs in polling mode. When one of the two SPs is faulty, the signaling messages will be completely processed by the other. Usually the two STPs that transfer the SCCP signaling messages are set as SPs in load sharing mode. One remote SP can correspond to multiple virtual OSPs in the local office. When processing the messages sent to the remote SP, SCCP selects one virtual SP of the local office corresponding to the remote SP in cyclic mode, which will be used as the OPC in the MTP message. 7-6



X. SCCP Subsystem The subsystem number (SSN) is the local addressing information used by SCCP. It is used to identify multiple SCCP subscribers in a network node. If the network node serves not only as an STP, a subsystem number must be specified for each SCCP subsystem (SCCP user). In the entire network, each subsystem number is unique. The subsystem number is used as the address of the subsystem inside the signaling network. To define a subsystem, you must set the following data: z

Indicator of the network to which the subsystem belongs

z

Local SPC

z

SSN

z

DPC

SCCP users can be users (local subsystem) located in the local SP and users (remote subsystems) located in other SPs. For different network nodes, the subsystems must be allocated according to users. For the remote SCCP users that need the local SCCP management, the relevant subsystem must be established.

XI. Global Title GT is generally composed of numbers, such as international and national phone numbers. It is used mostly in the case when the originating node does not know the network address of the destination node. Since MTP cannot route messages according to the GT, SCCP has to translate the called GT to DPC or DPC+SSN or DPC+GT before transferring it to MTP. Besides, it is necessary to notify the next SP of the coding scheme that GT adopts.

XII. Associated Mode of Signaling The associated mode of signaling refers to transmitting messages between two SPs interconnected by a signaling link. See Figure 7-7 for the associated mode of signaling. OPC:=SPB DPC:=SPA SPA

OPC:=SPA DPC:=SPB

SPB

Figure 7-7 Associated mode of signaling In the associated mode, the office direction that has trunk circuits connected with MSC adopts this mode to create a direct signaling connection with MSC. Besides, this mode also applies to the signaling connections between MSC and such functional entities as local HLR and STP.

7-7



XIII. Quasi-Associated Mode of Signaling The quasi-associated mode of signaling refers to transmitting messages between two SPs through a signaling link on which multiple transfer points are preset. See Figure 7-8 for the quasi-associated mode of signaling. STP

B SP A : = SP PC := O PC D

PA =S P B : C =S OP PC: D

PB =S P A : C =S OP PC: D

O DP PC: C : =S =S PA PB

SPA

SPB

Figure 7-8 Quasi-associated mode of signaling In the quasi-associated mode, if MTP of STP finds out the DPC in the message is a remote DPC, MTP will transfer the signaling message according to the DPC without changing the OPC and DPC in the message. When DPC addressing mode is employed to transmit MAP and CAP messages between two SPs and there are no associated links, the quasi-associated mode will be used.

XIV. GT Addressing for Communication among SPs When GT addressing mode is employed to transmit MAP and CAMEL application part (CAP) messages between two SPs, the messages shall be transferred after the STP performs GT over the signaling messages instead of a quasi-associated connection, as shown in Figure 7-9. STP

B SP P : = ST PC := O PC D

PA =S TP : C =S OP PC: D

TP =S P A : C =S OP PC: D

O DP PC: C : =S =S TP PB

SPA

SPB

Figure 7-9 Inter-SP communication through STP instead of quasi-associated connection In this mode, the DPC and OPC of the message will be changed. The processing process is as follows if the SPs adopt DPC+GT addressing mode: 1)

SP A sends a signaling message in DPC (of STP) +GT (of SP B) mode.

2)

After MTP of STP receives the MTP message from SP A, it sends the message to its own SCCP.

7-8


3)


SCCP performs GT translation to obtain DPC+SSN, in which DPC and SSN are both of SPB.

4)

SCCP distributes the message to the MTP layer.

5)

MTP sends the message to SP B according to the DPC.

Figure 7-10 illustrates the whole process. SPA

STP

SubSystem

SPB

SubSystem

SubSystem

SCCP

SCCP

SCCP

MTP

MTP

MTP

DPC+GT

DPC+SSN

Figure 7-10 DPC+GT addressing mode

Note: The operators determine whether to transmit MAP and CAP messages between two SPs in GT addressing mode or DPC addressing mode. Some may want to transmit messages in DPC addressing mode among SPs within a province, while for the SPs located outside the province, GT addressing mode is used for message transmission. However, some operators may want to transmit messages in GT addressing no matter the SPs are within or outside a province. When DPC is used for addressing, the load of STP is relatively light while much more data is configured for STP. When GT addressing is used, the load of STP is heavy but much less data is configured. HLR is a functional entity that needs to transmit MAP messages with GMSCs. The functional entities that need to transmit MAP messages with VMSCs include the adjacent VMSC, HLR, local SGSN, and SMC. If MSC processes intelligent network (IN) services, CAP messages are transmitted between MSC and SCP.

7.2.2 Principles for Configuring GT Data GT data is applied in handset location update, calling, and signaling stream direction after handover between offices. The principles for configuring GT data are as follows: z

For signaling messages transferred through STP, set the corresponding “Translation Result Type” to "DPC + GT"; while for those transferred through direct links, set the corresponding “Translation Result Type” to "DPC".

z

The signaling messages between the local office and other MSCs/HLRs in a province or those in other provinces are transferred by STP through DPC+GT addressing mode. Therefore, you need not set MTP route data. 7-9

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center z


Since location update is not performed at GMSC, set IMSI data for GMSC. While for VMSC, besides the IMSI data, the VMSC must be configured with the GT data of the adjacent VMSC if handovers occur between two VMSCs.

7.2.3 Principles for Naming Signaling Links The principles for naming signaling links are as follows: z

DSP name: Name DSP with the peer office name.

z

MTP route name: Name outgoing routes with the peer office name. For non-direct routes, name them with ”office name_alternative route office name”.

z

Link set name: Name outgoing link sets with the peer office name.

z

Link name: Name outgoing links with the peer office name (location+NE ID+NE serial No.-Link No).

7.2.4 Principles for Numbering MTP Data The principles for numbering MTP data are as follows: z

DPC indexes are numbered in an ascending sequence. It is recommended to number the BSC first, then RNC, HSTP, LSTP, HLR, local VMSC, local GMSC, office directions in other networks, and then non-adjacent office directions. Moreover, the numbers shall correspond to office direction numbers.

z

Numbers of the MTP link sets shall correspond to DSP indexes and be numbered in an ascending sequence (starting from 0).

SS7 route sets shall be numbered in an ascending sequence according to the sequence of the DSP indexes.

7.2.5 Networking Between MSOFTX3000 and HLR The MAP interface is used between MSOFTX3000 and HLR. MAP may be based on ATM or IP. The current networking is generally based on TDM, as shown in Figure 7-11. TDM TDM based C/D MSOFTX3000 MAP TCAP SCCP MTP3 MTP2 MTP1

Figure 7-11 Networking and protocols between MSOFTX3000 and HLR

7-10

HLR



7.2.6 Parameter Relationship The parameter relationships for interworking between MSOFTX3000 and HLR are illustrated in Figure 7-12. The solid lines represent the relationships with external entities (HLR) and the dotted lines represent the relationships between internal commands. HLR parameters MSOFTX3000 parameters

Signaling network indicator HLR OPC Peer end MSC DPC

ADD N7DSP

ADD N7LKS

[DSP index]

[LinkSet Index] [Adjacent DSP Index]

[NI] [DPC] [OPC]

ADD SCCPDSP

ADD N7RT [Linkset index] [DSP index]

[NI] [DPC] [OPC] SLC

ADD SCCPSSN [NI ] [SSN] [SPC] [OPC]

ADD N7LNK [Link No.] [Start Circuit No.] [Linkset index] [Signaling Link Code]

ADD SCCPGT [NI] [GT Address Information] [SPC]

HLR number IMSI number segment MSISDN number segment

Figure 7-12 Parameter relationship between MSOFTX3000 and HLR

7.2.7 General Configuration Procedures The procedures and commands for configuring data for interworking between MSOFTX3000 and the HLR are listed in Table 7-1. Table 7-1 Procedures and commands for configuring data at MSOFTX3000 for interworking with HLR Procedure

Command

1. Configure MTP

ADD N7DSP

1) Add MTP DSP

ADD N7LKS

2) Add MTP link set

ADD N7RT

3) Add MTP route

ADD N7LNK

4) Add MTP link

7-11



Procedure

Command

2. Configure SCCP

ADD SCCPDSP

1) Add SCCP remote SP

ADD SCCPSSN

2) Add SCCP subsystem

ADD SCCPGT

3) Add SCCP GT

7.3 Collecting Data for Interworking with HLR Before configuring data for interworking with HLR, you need to collect the interfacing data between MSOFTX3000 and HLR, as shown in Table 7-2. In the shadowy columns are the parameters that must be negotiated between both ends for consistency or of which one end must notify the other. The other parameters are the internal ones of MSOFTX3000. Table 7-2 Data for interworking with HLR Item

Data

Basic information




/

Signaling link

WCSU module number

Link set


Signaling link code (SLC) and SLC sending

Coding description

Numbering plan

Address information

DPC

Intra-module circuit number (E1 number/time slot number)

Link type

/ SCCP GT translation / /

7.4 Configuring Data for Interworking with HLR 7.4.1 Adding MTP Layer Data I. Background Information When the TDM mode is used for signaling transmission to the HLR, it is required to configure MTP related data, including MTP DSP, link set, route, and link information.

II. Command The procedures to add MTP link data are as follows: 7-12



1)

Add MTP DSP (ADD N7DSP)

2)

Add MTP link set (ADD N7LKS)

3)

Add MTP route (ADD N7RT)

4)

Add an MTP link (ADD N7LNK)

III. Major Parameters Refer to sections 6.4.2– 6.4.5 in Chapter 6.

IV. Related Commands Refer to sections 6.4.2– 6.4.5 in Chapter 6.

7.4.2 Adding SCCP DSP I. Background Information None


Note: This command is used to configure the SP information for the peer HLR.

III. Major Parameters [DPC Index] It is used to identify a remote DSP. This index must be the unique one identifying a remote DSP among all remote DSPs. [NI] For HLR, set this parameter to "NAT (National Network)". [DPC] It refers to destination signaling point code. Here set it to the DPC of the peer HLR. The DPC of the HLR is the national reserved 24-bit SPC. This parameter is the same as that set in the ADD N7DSP command. [OPC] It refers to the local office's SPC in the same network indicator. You can query it with the LST OFI command. For HLR, the OPC is the national network SPC of record No. 0 in the OFI table.

IV. Related Commands 7-13



See Table 7-3 for the commands related to SCCP DSP configuration. Table 7-3 List of commands related to SCCP DSP configuration Command

Description

ADD SCCPDSP

To add an SCCP DSP

RMV SCCPDSP

To remove an existing SCCP DSP

MOD SCCPDSP

To modify an existing SCCP DSP

LST SCCPDSP

To list the information of all configured SCCP DSPs

DSP SCCPDSP

To display the information of all configured SCCP DSPs

7.4.3 Adding SCCP Subsystem I. Background Information This following command ADD SCCPSSN is used to add SCCP subsystems in MSOFTX3000 (local end) and the HLR (remote end). Subsystem number (SSN) is the local addressing information used by SCCP to identify the SCCP users under a SP. Local MSC and VLR subsystems are already added in the local office information. z

The network indicator of MSOFTX3000 is "National Network", and the configured SSN is SCCP management subsystem (SCMG).

z

The SSN to be configured at the HLR side includes SCMG and HLR.

Since the local MSC, VLR, and SCMG subsystems have been configured in the local office information, execute the LST SCCPSSN command to have a check to avoid repeated configuration. For any entity (local end or remote end), it may be required to run this command repeatedly to configure multiple SCCP subsystems.


III. Major Parameters [SSN Index] It is used to identify the SCCP subsystem, and it is unique in the system. [NI] It is used to set the indicator of the network to which the SCCP subsystem belongs. The devices to be interconnected should be in the same signaling network. For the subsystem interworking with HLR, set it to "National Network". [SSN] It is required to add SCMG at the local end, and to add SCMG and HLR subsystems at the remote end. 7-14



[SPC] It is used to specify the destination SPC of the corresponding subsystem, that is, the recipient of SCCP messages. You need to set HLR SPC and OPC here. The HLR SPC must be correlated with that defined in the command ADD SCCPDSP. [OPC] Enter the national reserved network SPC of the local office. It is associated with the parameter “OPC” in the SET OFI command. [Local Concerned SSN1]–[Local Concerned SSN5] It is used to define the index of a subsystem which is related to a specified subsystem and has the same DPC as the subsystem. You can define a maximum of 5 indexes. If there is no related subsystem, use the default option “Undefined”. [Backup SSN Index] It is used to specify the index of the backup subsystem of a specified subsystem. It is valid only when MSOFTX3000 supports the load sharing function or backup function of SCCP DSP. If there is no subsystem, use the default value “65535”.


Description

ADD SCCPSSN

To add an SCCP subsystem

RMV SCCPSSN

To remove an existing SCCP subsystem

MOD SCCPSSN

To modify an existing SCCP subsystem

LST SCCPSSN

To list SCCP subsystems

SET SCCPSSN


DSP SCCPSSN

To display SCCP subsystems in the host

7.4.4 Adding SCCP GT I. Background Information When MSOFTX3000 is directly connected to HLR, it is required to configure the following global title (GT) data for the three cases: z

IMSI GT and HLR-NUMBER GT for location update.

z

Ordinary GT (HLR-MSISDN GT) when the subscriber is called.

z

Local MSC GT to be queried when the local office performs second-stage number analysis.

7-15



The following gives detailed description: 5)

IMSI GT and HLR-NUMBER GT for location update

z

IMSI GT configuration: It is performed for location update to find the corresponding HLR according to the GT translation code of the HLR obtained through the IMSI number.

When a mobile station initiates location update request, it sends the IMSI number. Because IMSI number cannot build GT, it is required to use the ADD IMSIGT command to translate GT. For example, use the command ADD IMSIGT: MCCMNC="46000", CCNDC="86139"

to

translate

46000××××××××

into

86139××××××××.

(note:

86139×××××××× is not a phone number). Then use the following command (supposing that the SP of the HLR is 12345): ADD

SCCPGT:

GTX=1,

GTNAME="IMSI-GT",

NI=NAT,

NUMPLAN=ISDNMOV,

ADDR=K'86139××××××××, RESULTT=STP1, SPC="12345";

Where, the length of the parameter “ADDR” can be set according to the actual condition, and the parameter “NUMPLAN” must be mobile numbering plan “ISDNMOV”. z

HLR-NUMBER GT configuration: It is performed for location update when VLR inserts subscriber information response to HLR to find corresponding HLR.

According to the analysis in 1), MSC/VLR can find HLR. However, the location update has not yet completed after those two commands are executed, because VLR needs to insert subscriber response PRN-ACK to HLR. In the last step, VLR obtains the HLR destination address through analyzing HLR number, which is carried in the called number on SCCP layer when HLR inserts subscriber data message. Supposing the HLR number is 8613907551234, it is required to execute the following command: ADD

SCCPGT:

GTX=2,

GTNAME="HLR-GT",

ADDR=K'8613907551234,

RESULTT=STP1,

SPC="12345";

The numbering plan here is the telephone numbering plan. After the above IMSI GT and HLR-NUMBER GT configurations, the GT configuration related to location update has been completed. 1)

HLR-MSIDSN GT configuration: It is performed for the routing information fetching process to find the corresponding HLR according to the GT translation code of the HLR obtained through the MSISDN of the called number.

When a subscriber is called, MSC needs to get his/her roaming number in the HLR and gets the HLR SPC through analyzing the MSISDN of the called number. Assuming that IMSI 46000×××××××× in the HLR is assigned with MSISDN 861390755×××××, it is required to execute the following command: ADD SCCPGT: GTX=3, GTNAME="HLR NUMBER", ADDR=K'861390755, RESULTT=STP1, SPC="12345";

2)

Local MSC GT configuration

When a subscriber is called, MSC needs to get his/her roaming number in the HLR. 7-16



After getting the roaming number, the HLR sends SRI-RSP message with MSC GT address information to MSC, which checks whether it is the local MSC GT. If yes, MSC will initiate paging. The GT translation code of the local MSC has been described in local office information configuration, so it is not necessary to configure it here.

II. Command ADD SCCPGT

III. Major Parameters [GT Index] GT index: It uniquely identifies a GT code. [NI] For the local MSC/VLR, set this parameter to "NAT (NATIONAL NETWORK)". It is associated with that defined in the ADD SCCPSSN command. [GT Indicator] There are four classes of GTs in the mobile network. Select "GT4 (TYPE4) generally. [Translation Type] In the mobile network, set this parameter to "00". [Numbering Plan] To set this parameter, refer to GT data configuration analysis of this section. [Nature of Address Indicator] This parameter specifies the property of an address indicator. [GT Address Information] To set this parameter, refer to GT data configuration analysis of this section. [Translation Result Type] Set this parameter according to the actual conditions. See section 7.2.2 “Principles for Configuring GT Data” [SSN] It is used to specify a subsystem. If “LSPC1 (SPC + SSN)" is selected in “Translation Result Type”, it is required to select a related subsystem. You can add subsystems with the ADD SCCPSSN command. [SPC] It is used to uniquely indicate a translation code in the GT table.

IV. Related Commands See Table 7-5 for the commands related to SCCP GT configuration.

7-17



Table 7-5 List of commands related to SCCP GT configuration Command

Description

ADD SCCPGT

To add an SCCP GT

RMV SCCPGT

To remove an existing SCCP GT

MOD SCCPGT

To modify an existing SCCP GT

LST SCCPGT

To list SCCP GT


SCP

SMC

GMLC

HLR

MAP/TDM

MAP/TDM

MAP/TDM

MAP/TDM

MSC Server

MSOFTX 3000

ISUP/TDM

H.248,RANAP / IP

BSSAP+/TDM

SGSN


MGW

MGW (SG)

IP/ TDM

RANAP/AAL2/ATM

ISUP/TDM

PSTN

BSSAP/TDM

RNC

BSC

Figure 7-13 Networking of MSOFTX3000 This example is to add a local HLR, which is directly connected to MSOFTX3000 through E1 line. The HLR information is shown in Table 7-6. For the local office information, refer to Table 3-14 in Chapter 3.

7-18



Table 7-6 HLR information table Item

Data

Basic information /



HLR number (E.164 number)

12345

National network

8613907550 000 Intra-module circuit number (E1 number/times lot number)

Link type

48 (1/16)

64 kbit/s

WCSU module number

Link set



23

11

1

0

SCCP GT translation

Coding descripti on

Numberin g plan

Address information

DPC

/

IMSI GT

ISDNMOV

86139

12345

/

HLR NUMBE R

ISDN

86139075500 00

12345

/

MSIDSN

ISDN

861390755

12345

Signaling link

/

7.5.2 Configuration Description //Add MTP layer data. ADD N7DSP: DPX=11, DPC="12345", OPC="CC0004", DPNAME="HLR"; ADD N7LKS: LSX=11, ASPX=11, LSNAME="HLR"; ADD N7RT: LSX=11, DPX=11, RTNAME="HLR"; ADD N7LNK: MN=23, LNKN=1, LNKNAME="HLR",LNKTYPE=0, TS=48, LSX=11, SLC=0;

//Add SCCP layer data. ADD

SCCPDSP:

DPX=11,

NI=NAT,

DPC="12345",

OPC="CC0004",

DPNAME="HLR",

SHAREFLAG=NONE; ADD

SCCPSSN:

SSNX=10,

NI=NAT,

SSN=SCMG,

SPC="12345",

OPC="CC0004",

NI=NAT,

SSN=HLR,

SPC="12345",

OPC="CC0004",

SSNNAME="HLR-SCMG"; ADD

SCCPSSN:

SSNX=11,

SSNNAME="HLR-HLR";

ADD IMSIGT: MCCMNC="46000", CCNDC="86139"; ADD

SCCPGT:

GTX=8,

GTNAME="HLR-IMSIGT",

7-19

NUMPLAN=ISDNMOV,

ADDR=K'86139,



RESULTT=LSPC2, SPC="12345"; ADD SCCPGT: GTX=9, GTNAME="HLR-NUMBER", NUMPLAN=ISDN, ADDR=K'8613907550000, RESULTT=LSPC2, SPC="12345"; ADD SCCPGT: GTX=10, GTNAME="HLR-MSIDSN", ADDREXP=INTER, ADDR=K'861390755, RESULTT=STP1, SPC="12345";

7-20


Chapter 8 Configuring Data for Interworking with MSC

Chapter 8 Configuring Data for Interworking with MSC (MTP) 8.1 Introduction to the Chapter This chapter describes the data configuration process at MSOFTX3000 for interworking with other MSC Server. This chapter contains the following sections: z

Concepts Related to Data Configuration for Interworking with Other MSC Server

z

Collecting Data for Interworking with Other MSC Server

z

Configuring Data for Interworking with Other MSC Server

z


8.2 Related Concepts 8.2.1 Networking Between MSOFTX3000 and MSC Server When using BICC protocol, MSOFTX3000 and MSC Server are connected through the Nc interface. When using ISUP and MAP (for handover), they are connected through the E/G interface. This section introduces the networking with the E/G interface as example. ISUP can be carried over multiple transmission media, such as TDM and IP. Generally, the current networking modes are carried over TDM and ISUP is used in trunk signaling. See Figure 8-1.

8-1



MSOFTX3000

TDM bearer

Semi-permenant connection TDM bearer MSC

MGW

ISUP MTP3 MTP2 MTP1

Figure 8-1 Networking and protocols between MSOFTX3000 and MSC Server

8.2.2 Parameter Relationship The parameter relationships for interworking between MSOFTX3000 and MSC Server are illustrated in Figure 8-2 and Figure 8-3. The dotted lines represent the relationships of MSOFTX3000 with external entities (MSC Server) and the solid lines represent the relationships between internal commands. MSC SERVER parameters

MSOFTX3000 parameters ADD N7DSP

Signaling network indicator Local MSC OPC Peer MSC DPC


[DSP index] [NI] [DPC] [OPC] ADD SCCPDSP

[NI] [DPC] [OPC] ADD SCCPSSN

[NI] [SSN] [SPC] [OPC]

ADD N7LKS

linkSet Index [Adjacent DSP Index] ADD N7RT

[LinkSet Index] [DSP index] ADD N7LNK

[Link No.] [Start Circuit No.] [LinkSet] Index] [Signaling Link Code]

ADD SCCPGT

MSC number

[NI [GT Address Information] [SPC]

Figure 8-2 Parameter relationship between MSOFTX3000 and other MSC Server (MTP and SCCP)

8-2

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Parameters pertaining to peer route trunk


MSOFTX3000 Parameters

ADD OFC [NI ] [Office direction number] [Destination Point Code]

Destination entity's SPC

[signal bearer type]

ADD SRT [Office Direction Number] [Sub-route Number]

ADD RT [1st sub-route] [Route Number]

ADD RTANA [Route Number] [Route Selection Code] [Route Selection Source Code] (LST CALLSRC)

ADD N7TG [Trunk Group] [MGW INDEX] (ADD MGW) [Sub-route number] [OPC] (SET OFI) [DPC] [Call source] (ADD CALLSRC)

ADD N7TKC [Trunk Group] [Start CIC]

Start CIC

[Start circuit termination ID]

Figure 8-3 Parameter relationship between MSOFTX3000 and other MSC Server (trunk)

8.2.3 General Configuration Procedures The procedures and commands for configuring data for interworking between MSOFTX3000 and other MSC Server are listed in Table 8-1.

8-3



Table 8-1 Procedures and commands for configuring data at MSOFTX3000 for interworking with other MSC Server Procedure

Command

1. Configure MTP

ADD N7DSP

1) Add MTP DSP

ADD N7LKS

2) Add MTP link set

ADD N7RT

3) Add MTP route

ADD N7LNK

4) Add MTP link 2. Configure SCCP

ADD SCCPDSP

1) Add SCCP remote signaling point

ADD SCCPSSN


ADD SCCPGT

3) Add SCCP GT 3. Configure routing information 1) Add office direction to MSC Server

ADD OFC

2) Add sub-route

ADD SRT

3) Add route

ADD RT

4) Add route analysis

ADD RTANA

4. Configure trunk circuit

ADD N7TG

1) Add SS7 trunk group

ADD N7TKC

2) Add SS7 trunk circuit

Mod N7TKC

3) Mod SS7 trunk circuit

8.3 Collecting Data for Interworking with Other MSC Server Before configuring data for interworking with other MSC server, you need to collect the interfacing data between MSOFTX3000, MGW, and the peer MSC server, as shown in Table 8-2. In the shadowy columns are the parameters that must be negotiated between both ends for consistency or of which one end must notify the other end. The other parameters are the internal ones of MSOFTX3000. Table 8-2 Data for interworking with other MSC server Item

Basic information



/

8-4




Item

Signaling link

Data





CIC

WCCU/WC SU module number

MGW Index

Office direction

Route number

Sub route number

Trunk group

Circuit type

Prefix



WCSU module number

Link set

Link type

/

Circuit


8.4 Configuring Data for Interworking with Other MSC Server 8.4.1 Negotiating and Preparing Data For detailed procedures to configure interworking data between MSOFTX3000 and MGW, refer to Chapter 4 “Configuring Data for Interworking with MGW”of this manual.

8.4.2 Configuring MTP Data Refer to sections 6.4.2–6.4.5 in Chapter 6 “Configuring Data for Interworking with BSC” to configuration data for the MTP layer. The steps to add MTP links are as follows: 1)

Add MTP DSP (ADD N7DSP).

2)

Add MTP link set (ADD N7LKS).

3)

Add MTP route (ADD N7RT).

4)

Add MTP link (ADD N7LNK).

8.4.3 Configuring SCCP Data As MAP is required between MSC Servers to interchange mobile management information, you need to set SCCP layer data. Refer to sections 7.4.2–7.4.4 in Chapter 7 “Configuring Data for Interworking with

8-5



HLR” to configure data for the SCCP layer. The steps to add SCCP data are as follows: 1)

Add a DSP of SCCP (ADD SCCPDSP): Select “National Network” for the parameter “Network Indicator” of the SCCP DPC to MSC.

2)

Add SCCP subsystems (ADD SCCPSSN): Add MSC, VLR, MAP, and SCMG subsystems to the remote MSC server. Because the local MSC, VLR and SCMG subsystems have been configured in the local office information table, use the LST SCCPSSN command to have a check to avoid repeated configuration.

3)

Add SCCP GT (ADD SCCPGT): It is only required to configure MSC server GT. Select "National Network" for NI, "ISDN (ISDN/TELEPHONY NUMBERING PLAN)" for numbering plan, and enter SMC number for GT address information. Interpretation result type: select “LSPC2(SPC)”.

8.4.4 Adding Routing Information Refer to sections 10.3.3–10.3.6 in Chapter 10 “Configuring Data for Interworking with PSTN” to configure routing data. The steps to add routing information are as follows: 1)

Add office direction from MSOFTX3000 to MSC Server (ADD OFC): Select “MSC” for “Opposition Office Type”, ”SAME (PEER)” for “Peer Office Level”, ”MSC” for “Peer Office Attribute”, “NAT (NATIONAL)” for “Network Indicator” and enter the DPC of the MSC for the parameter “Destination Point Code”.

2)

Add subroute (ADD SRT).

3)

Add route (ADD RT).

4)

Add route analysis data (ADD RTANA).

8.4.5 Adding SS7 Trunk Circuit Refer to sections 10.3.7–10.3.8 in Chapter 10, “Configuring Data for Interworking with PSTN” to configure SS7 trunk circuit information. The steps to add SS7 trunk circuit information are as follows: 1)

Add SS7 trunk group (ADD N7TG).

2)

Add SS7 trunk circuit (ADD N7TKC).

3)

Modify SS7 trunk circuit state (MOD N7TKC)


8-6


SCP


SMC

GMLC

HLR

MAP/TDM

MAP/TDM

MAP/TDM

MAP/TDM

MSC Server

MSOFTX 3000

ISUP/TDM

H.248,RANAP /IP

BSSAP+/TDM

SGSN


MGW

MGW

IP/TDM

ISUP/TDM

PSTN

(SG)

RANAP/AAL2/ATM

BSSAP/TDM

RNC

BSC

Figure 8-4 Networking of MSOFTX3000 This example is to add an MSC server, which is connected to MSOFTX3000 through E1 line. The MSC server information is listed in Table 8-3. For the local office information, refer to Table 3-14 in Chapter 3.

8-7



Table 8-3 MSC server information table Item

Data

Basic information

/

Signaling link

/

Circuit





AA0001

National network

861350000 1 Intra-module circuit number (E1 number/time slot number)

Link type

48 (1/16)

64 kbit/s

WCSU module number

Link set



22

1

1

0


CIC

WCCU/WC SU module number

32–63

0–32

25

Office direction

Route number

Sub route number

Trunk group

Circuit type

1

1

1

1

ISUP

Prefix



13910

1

0

8.5.2 Configuration Description //Add MTP layer data. ADD N7DSP: DPX=1, DPC="AA0001", OPC="CC0004", DPNAME="MSC-1"; ADD N7LKS: LSX=1, ASPX=1, LSNAME="MSC-1"; ADD N7RT: LSX=1, DPX=1, RTNAME="MSC-1"; ADD N7LNK: MN=22, LNKN=1, LNKNAME="MSC-1", LNKTYPE=0, TS=48, LSX=1, SLC=0;

//Add SCCP layer data. ADD SCCPDSP: DPX=1, NI=NAT, DPC="AA0001", OPC="CC0004", DPNAME="MSC-1", SHAREFLAG=NONE; ADD

SCCPSSN:

SSNX=12,

NI=NAT,

SSN=SCMG,

SPC="AA0001",

OPC="CC0004",

SSN=MSC,

SPC="AA0001",

OPC="CC0004",

SSNNAME="MSC-SCMG"; ADD

SCCPSSN:

SSNX=13,

NI=NAT,

8-8



SSNNAME="MSC1-MSC"; ADD

SCCPSSN:

SSNX=14,

NI=NAT,

SSN=VLR,

SPC="AA0001",

OPC="CC0004",

SSNNAME="MSC1-VLR"; ADD

SCCPGT:

GTX=1,

GTNAME="MSC1-GT",

NI=NAT,

GTI=GT4,

NUMPLAN=ISDN,

ADDREXP=INTER, ADDR=K'8613500001, RESULTT=LSPC2, SPC="AA0001";

//Configure the office direction to MSC. ADD OFC: OFFICEDIR=1, ON="MSC-1", OOFFICT=MSC, DOL=SAME, DOA=MSC, NI=NAT, DPC1="AA0001", SIG=MTP3; ADD SRT: SRC=1, O=1, SRN="MSC-1"; ADD RT: R=1, RN="MSC-1", SR1=1; ADD RTANA: RSC=1, RSSC=0, RUT=ALL, ADI=ALL, TP=ALL, TMX=0, R=1, ISUP=ISUP_F;

//Configure the SS7 link to MSC. ADD

N7TG:

TG=1,

MGW=1,

G=INOUT,

SRC=1,

SOPC="CC0004",

SDPC="AA0001",

TGN="MSC-1", CT=ISUP; ADD N7TKC: MN=22, TG=1, SC=32, EC=63, SCIC=0, SCF=TRUE, TID=32; MOD N7TKC: MN=22, SC=48, EC=48, CS=UNU; MOD N7TKC: MN=22, SC=32, EC=32, CS=UNU;

8-9


Chapter 9 Configuring Data for Interworking with MSC (ISUP/M3UA)

Chapter 9 Configuring Data for Interworking with MSC (ISUP/M3UA) This chapter describes the data configuration process at the MSOFTX3000 for interworking with the peer end MSC. The networking from the MSOFTX3000 to the peer end MSC uses the MGW concurrently as the signaling gateway for signaling transferring between the MSOFTX3000 and the peer end MSC. Currently, this networking mode can be used for connecting the MSOFTX3000 with the remote tandem office. This chapter introduces the data configuration for this networking mode.

9.1 Related Concepts 9.1.1 Networking Between MSOFTX3000 and MSC ISUP signaling is used between MSOFTX3000 and the remote MSC. Signaling from the MSOFTX3000 to MGW is carried over IP. The MGW fulfills signaling transferring from IP bearer to TMD bearer. Refer to Figure 9-1 for the networking and interface protocols. This networking mode is applicable to the connection between the MSOFTX3000 end office and the peer tandem office. This chapter describes the data configuration procedures for the networking mode as shown in Figure 9-1. IP bearer

TDM bearer MGW(SG)

MSOFTX3000

ISUP

MSC

ISUP

M3UA

M3UA

MTP3

MTP3

SCTP

SCTP

MTP2

MTP2

IP

IP

MTP1

MTP1

Figure 9-1 Networking and interface protocols between MSOFTX3000 and MSC

9.1.2 Parameter Relationship Figure 9-2 illustrates the parameter referencing relationship at the MSOFTX3000 side during configuration. The parameter “NI” in the figure must be assigned with the same attributes.

9-1



ADD M3LE [Local entity index] [Local entity point code] [NI] [Local entity type ] [Route context](optional) ---

ADD M3DE [Local entity index] [Destination entity index] [NI] [Destination entity point code] [Destination Entity Type] [Adjacent flag] ---

ADD M3LKS [Adjacent entity index] [Work mode] [LinkSet index] ---

ADD M3RT [Destination entity index] [LinkSet index ]

ADD M3LNK [LinkSet index] [Module number](ADD FECFG) [Local IP Address1] (ADD FECFG) [Local port] [Peer IP address1] [Peer port] [C/S mode] ---

Figure 9-2 Parameter relationship between MSOFTX3000 and MGW (M3UA)

9-2



Peer end route trunk parameter Local end route trunk parameter

ADD OFC [Network ID] [Office direction] [Destination point code]

Destination entity SPC

[BICC signaling bearer type]

ADD SRT [Office direction] [Sub-route number]

ADD RT [Sub-route1] [Route number]

ADD RTANA [Route number] [Route selection code] [Route selection source code ](LST CALLSRC)

ADD N7TG [Trunk group] [MGW index] (ADD MGW) [Sub-Route number] [OPC](SET OFI) [DPC] [Call source code] (ADD CALLSRC)

ADD N7TKC [Trunk group] [Start CIC]

Starting CIC


Figure 9-3 Parameter relationship between MSOFTX3000 and peer end MSC (route trunk)

9.1.3 Collecting Data Before configuring data, you need to collect interface data for interworking between MSOFTX3000, MGW and peer end MSC, as shown in Table 9-1. In the shadowy columns are the parameters that must be negotiated between two ends for consistency or of which one end must notify the other end. The other parameters are the internal ones of the MSOFTX3000.

9-3



Table 9-1 Table of data collected for the MSOFTX3000 interworking with MSC Item


Network indicator

Service mode


WIFM module number


SPC of peer MSC

M3UA link number

Local IP

Local port


Port number of the peer MGW

Termination ID (the physical circuit number at MGW for interworking with MSC Server)

CIC

WCCU/WCSU module number

MGW Index

Office direction

Route number

Sub-route number

Trunk group

Circuit type

Prefix



Basic information



Circuit

Trunk circuit

Prefix

Server/Client

9.2 General Configuration Procedures The procedures and commands for configuring data for interworking between MSOFTX3000 and MSC are listed in Table 9-2.

9-4



Table 9-2 Procedures and commands for configuring data at MSOFTX3000 for interworking with MSC Procedure

Command

1. Configure M3UA (for interworking with MGW) 1) Add M3UA local entity

ADD M3LE

2) Add M3UA destination entity

ADD M3DE

3) Add M3UA link set

ADD M3LKS

4) Add M3UA route

ADD M3RT

5) Add M3UA link

ADD M3LNK

2. Configure M3UA (for interworking with MSC) 1) Add M3UA destination entity

ADD M3DE ADD M3RT

2) Add M3UA route 3. Configure route information 1) Add office direction to MSC Server

ADD OFC

2) Add sub-route information

ADD SRT

3) Add route information

ADD RT

4) Add route analysis data

ADD RTANA

4. Configure trunk circuit 1) Add SS7 trunk group

ADD N7TG

2) Add/modify SS7 trunk circuit

ADD/MOD N7TKC

9.3 Procedures 9.3.1 Negotiating and Preparing Data I. Mc Interface Date for Interworking between MSOFTX3000 and MGW For the data about the Mc interface between MSOFTX3000 and MGW, refer to Chapter 4 “Configuring Data for Interworking with MGW”.

II. Data to Be Configured at MGW Side z

Interface configuration

Signaling messages of the MGW are sent to the MSOFTX3000 through the Mc interface (10/100 Mbit/s adaptive Ethernet interface) provided by the MPPU. What need to be configured are the IP address and route of the Mc interface. z

M3UA link configuration 9-5



It includes the configuration of M3UA entity, flow, route, link set, route, and link. For more information, see HUAWEI UMG8900 Universal Media Gateway Operation Manual – Data Configuration.

9.3.2 Adding M3UA Local Entity I. Background Information Before adding M3UA local entity for the MSOFTX3000, execute the LST OFI command to check whether the local originating signaling point code (OPC) is configured. If not, configure it first.

II. Command ADD M3LE

III. Major Parameters [Local Entity Index] It is used to uniquely identify an M3UA local entity [NI] It is used to indicate the network type. A signaling point can simultaneously appear in international network, international reserved network, national network, and national reserved network. [Local Entity Point Code] It is used to define the local office point code. [Local Entity Type] It is used to define the type of a local entity. It may be SG or AS. For the SGP-ASP mode, set the entity type at MSOFTX3000 side to “AS”, and that at peer MGW side to “SG”. [Route Context] (optional) It is used to specify the index value of a group of SS7 parameters. This parameter can be configured when the entity type is AS. The route context at AS side must be the same as that at SG side.

IV. Related Commands Table 9-3 lists the commands related to the M3UA local entity configuration.

9-6



Table 9-3 Commands for M3UA local entity configuration Command

Description

ADD M3LE

To add M3UA local entity

RMV M3LE

To remove M3UA local entity

MOD M3LE

To modify M3UA local entity

LST M3LE

To list M3UA local entity

9.3.3 Adding M3UA Destination Entity I. Background Information You must set the destination entity before a path from the local entity to the destination entity becomes available. As the SG is integrated in the MGW, the MGW resident office must allocate a signaling point code for the built-in SG. In this case, it appears that MGW has a signaling point code which in fact is allocated to the SG. You need to add two types of destination entity: one is MGW as SG, to be configured with the DSP of SG; the other is MGW as SP, to be configured with the signaling point of the peer office.

II. Command ADD M3DE

III. Major Parameters [Destination Entity Index] It is used to identify a destination entity uniquely for referencing internally. [Local Entity Index] It is used to identify a local entity to which the destination entity corresponds. This index is already defined in the ADD M3LE command. [NI] It is used to indicate the network type. A signaling point can simultaneously appear in international network, international reserved network, national network, and national reserved network. Set this parameter to “National active”. [Destination Entity Point Code]

9-7



It is used to specify the signaling point code of a destination entity. Its value is determined by the actual destination entity type to be configured. [STP Flag] It is used to set whether a DSP has STP function. To set the destination entity to SG type, select “TRUE”; to set it to SP type, select “FALSE”. [Link set select mask] This parameter indicates how to achieve load sharing among all routes to an M3UA destination entity. [Destination Entity Type] It is used to define the type of a destination entity. There are three types of destination entity, namely SP, SG, and AS. As MGW also functions as an SG, add MGW as SG and peer MSC as SP. [Adjacent flag] It is used to set whether a DSP is adjacent to the local office signaling point, that is, whether there is a signaling link directly associated with the local office signaling point. Select “YES” when there is such a direct signaling link with the local office signaling point; otherwise, select “NO”. This parameter is valid only when the parameter “Destination Entity Type” is set to “AS” or “SG”. [Network Mode] This parameter is used to specify the network mode between SG and AS. This field is used only when the destination entity type is AS (MSOFTX3000 acts as SG) to specify whether the AS interconnecting with MSOFTX3000 is an exclusive signaling point code or a signaling point code shared with other ASs. By default, the AS is an exclusive SPC. This parameter need not to be configured. [Protocol Version] It is a parameter for interconnection between MSOFTX3000 and a destination entity. The MSOFTX3000 supports the interconnection with the M3UA destination entity specified in DRAFT10 or RFC3332. By default, it is RFC3332. The default is used.

IV. Related Commands See Table 9-4 for the commands related to M3UA destination entity configuration.

9-8



Table 9-4 List of commands related to M3UA destination entity configuration Command

Description

ADD M3DE

To add M3UA destination entity

RMV M3DE

To remove M3UA destination entity

MOD M3DE

To modify M3UA destination entity

LST M3DE

To list M3UA destination entity

DSP M3DE

To display the state of M3UA destination entity of the host

9.3.4 Adding M3UA Link Set I. Background Information This section describes how to establish a link set between two adjacent M3UA entities.

II. Command ADD M3LKS

III. Major Parameters [LinkSet Index] It is used to specify the logical number of a link set in the system. The index is numbered globally in an ascending order from 0. The index is used in the M3UA routing table. [Adjacent Entity Index] It is used to identify the adjacent destination entity interconnected by the associated signaling link set. This index is related to the parameter “destination entity index” in the ADD M3DE command. Set the parameter “adjacent flag” of the corresponding destination entity to “adjacent". [Link Select Mask] It indicates how to share signaling traffic among the multiple signaling links in the same signaling link set. The value of this parameter is actually the load-sharing mask code of signaling links. [Traffic Mode] It is used to determine the service mode of the link set is “Load-Share Mode” or “Over-Ride Mode”. The traffic modes at two ends must be the same. That is, the two

9-9



ends must be in load-share mode or over-ride mode at the same time; otherwise, the corresponding link cannot be activated. The default option (load-share mode) is recommended. [Work Mode] It is used to indicate the attributes of the home end of a link set, such as ASP, IPSP, and SGP, according to the working mode of the link set. It is associated with the parameter “Local Entity Type” in the ADD M3LE command. z

In the non-peer networking mode, the M3UA destination entity type is SG, and the corresponding local entity type is AS, that is, "Local Entity Type” in the ADD M3LE command is “AS”. In this case, select “ASP”.

z

In the non-peer networking mode, the M3UA destination entity type is AS, and the corresponding local entity type is SG, that is, "Local Entity Type” in the ADD M3LE command is “AS”. In this case, select “SGP”.

z

In the peer networking mode, the M3UA destination entity type is the same as the local entity type, that is, AS or SG. In this case, select “IPSP".

IV. Related commands See Table 9-5 for the commands related to M3UA link set configuration. Table 9-5 List of commands related to M3UA link set configuration Command

Description

ADD M3LKS

To add M3UA link set

RMV M3LKS

To remove M3UA link set

MOD M3LKS

To modify M3UA link set

LST M3LKS

To list M3UA link set

DSP M3LKS

To display M3UA link set state of the host

9.3.5 Adding M3UA Route I. Background Information This section describes how to determine a signaling route to a destination entity by specifying a link set that can reach this destination entity. You can set priority for the route for carrying signaling traffic. You need to configure M3UA routes for interworking with MGW (built-in SG) and peer end MSC respectively.

9-10



II. Command ADD M3RT

III. Major Parameters [Destination Entity Index] It is used to identify a destination entity to which a signaling route is destined. It is already defined in the ADD M3DE command. [LinkSet Index] It is used to specify a signaling link set used by the signaling link reaching a destination entity. This parameter is defined in the ADD M3LKS command. [Priority] “0” indicates the highest priority. Among the several signaling routes to the DSP, the one with the highest priority is preferentially used to carry signaling traffic. A signaling route will carry signaling traffic unless none of signaling routes with higher priority is available.

IV. Related Commands See Table 9-6 for the commands related to M3UA route configuration. Table 9-6 List of commands related to M3UA route configuration Command

Description

ADD M3RT

To add M3UA route

RMV M3RT

To remove M3UA route

MOD M3RT

To modify M3UA route

LST M3RT

To list M3UA route

DSP M3RT

To display M3UA route state of the host

9.3.6 Adding M3UA Link I. Background Information You need to negotiate such parameters as “Local IP Address1”, “Local Port", “Peer IP Address1”, and “Peer Port” with the peer end to uniquely determine an M3UA link.

9-11



II. Command ADD M3LNK

III. Major Parameters [Module Number] It is used to define the module number of the WIFM/WBSG where M3UA links are resident. You can query it with the LST MDU command. If the WIFM and WBSG are integrated into one board, enter the module number of the WIFM here. If the WIFM and WBSG are separately configured, the module number is determined according to the board configured with M3UA links. If M3UA links are configured in the WIFM, enter the WIFM module number here. If M3UA links are configured in the WBSG, enter the WBSG module number here. [Link No.] It is used to identify a physical signaling link in a module. Each link of the same module has a unique link number. [Local IP Address1] IP based transmission is used between MGW and MSOFTX3000, and signaling messages are transmitted over IP/SCTP. It is necessary to specify an IP address for each link. Local IP address 1 is the external IP address of the local WIFM. This IP has to be negotiated with MGW. It is already defined in the ADD FECFG command. [Local IP Address2] This parameter is used to specify the second local IP address to which this link corresponds. Set it only when it supports SCTP multi-homing functionality. [Local Port] It is used to define the SCTP port used by the M3UA message at the MSOFTX3000 side. It is necessary to specify the SCTP port number when SCTP is used for transmission control. Ensure that the local port number specified here is consistent with the SCTP peer port number set at the MGW side. [Peer IP Address1] It is used to specify the IP address of the built-in signaling gateway of the peer MGW. This IP has to be negotiated with the MGW. [Peer IP Address2]

9-12



This parameter is used to specify the second remote IP address of the built-in signaling gateway of the peer MGW. Set it only when it supports SCTP multi-homing functionality. [Peer Port] It is used to specify the SCTP port used by the M3UA message of the peer MGW. It has to be negotiated with MGW. [C/S Mode] It is used to set whether a link is at the client side or server side. This parameter must be negotiated with the peer end. Set one end to client and the other end to server; otherwise, M3UA links cannot be set up normally. You can set the MSOFTX3000 to either client or server as long as it is not the same as MGW (SG). [Linkset Index] It is used to identify a link set to which a link belongs. It is associated with the link set index number in the ADD M3LKS command. [Active/Standby Flag] This parameter is used to set the work state for this M3UA link in the normal situation. The configuration of this parameter is closely related to the service mode of the link set: z

If you adopt the active/standby mode, only one of all M3UA links in the same link set can be set to active, while others must be set to standby.

z

If you adopt the load sharing mode, you must set all M3UA links in the same link set to active.

[Priority] This parameter is used to specify the priority of a link in a link set. Select the link with the highest priority first. 0 indicates the highest priority. [Main Type] It is used to set the dual homing function of the MSOFTX3000. It indicates what state a link is in, active or standby. When the MSOFTX3000 supports the dual homing function, set it based on the actual situation. If no dual homing function is applied for the MSOFTX3000, use the default setting, that is, ”TRUE”. Set other parameters to the default values.

IV. Related Commands See Table 9-7 for the commands related to M3UA link configuration.

9-13



Table 9-7 List of commands related to M3UA link configuration Command

Description

ADD M3LNK

To add M3UA link

RMV M3LNK

To remove M3UA link

MOD M3LNK

To modify M3UA link

LST M3LNK

To list M3UA link

DSP M3LNK

To display M3UA link state of the host

EST M3LNK

To establish M3UA link

REL M3LNK

To release M3UA link

LCK M3LNK

To block M3UA link

ULK M3LNK

To unblock M3UA link

DEA M3LNK

To deactivate M3UA link

ACT M3LNK

To activate M3UA link

9.3.7 Adding Office Direction I. Background Information This section describes how to set an office direction from the MSOFTX3000 to the peer MSC. Before adding an office direction, you must configure the call source.

II. Command ADD OFC

III. Major Parameters [Office Direction] It is allocated uniquely in the system to identify an office direction. [Office Direction Name] It is recommended to use a standard name for easy identification, for example, "MSC-1". [Opposition Office Type] Select this parameter according to the type of the peer office exchange. For this parameter, select “MSC”.

9-14



[Peer Office Level] It specifies the level of the peer office, “SAME (PEER)”, “LOW (INFERIOR)” or “HIGH (SUPERIOR)”. Set it according to the actual situation. Here select "LOW (INFERIOR)". [Peer Office Attribute] For this parameter, select “MSC (MSC)”. [Network ID] Select “NATIONAL”. [Destination Point Code1]–[Destination Point Code16] Enter the destination point code of MSC. [BICC Signal Bearer Type] Select “MTP3”. For other parameters, select system default values.


Description

ADD OFC

To add an office direction

RMV OFC


MOD OFC


LST OFC

To list information about configured office direction

9.3.8 Adding Sub-Route I. Background Information To add a sub-route, first ensure that the office direction of this sub-route exists. Use the LST OFC command to query whether there is such an office direction. If the office direction does not exist, add it. After adding the sub-route, add the route to which the sub-route belongs and then a trunk group for the sub-route.

9-15



II. Command ADD SRT

III. Major Parameters [Sub-Route Number] It identifies a sub-route, which is numbered globally. [Office Direction Number] It refers to the number of an office direction to which a sub-route points, and it has been defined in the ADD OFC command. [Sub-Route Title] A sub-route should be titled as clearly as possible to indicate the route features. It is recommended that this title be the same as the office direction name. [Group Selection] In a sub-route, a trunk group should be selected according to the trunk group number (including maximum number, minimum number, loop mode, and random mode). Generally, select "Loop" by default. "Loop" here means to select the group number from the one next to the last selected. "Minimum" means to select the group number always from the minimum one. "Maximum" means to select the group number always from the maximum one. "Random" means to select a group number from all trunk groups (of a sub-route) randomly. In addition, you need to set it according to the customer's requirement.

IV. Related Commands See Table 9-9 for the commands related to sub-route configuration. Table 9-9 List of commands related to sub-route configuration Command

Description

LST SRT

To list sub-route information

ADD SRT

To add sub-route

MOD SRT

To modify sub-route

RMV SRT

To remove sub-route

9-16



9.3.9 Adding Route I. Background Information This section is for configuring a route from the MSOFTX3000 to the peer MSC. A route is a set of all sub-routes from the local office to a certain office direction. To add a route, you must ensure that the sub-routes composing the route have existed.

II. Command ADD RT

III. Major Parameters [Route Number] The route numbers are planned according to the numbering principles. [Route Type] There are two route types: ordinary routing and queued routing. Ordinary routing means that a call will not be queued if the routing fails. Queued routing means that a call will wait for an idle circuit at the subscriber side if the routing fails. Generally, set it to ordinary route. [Sub-Route Selection Mode] The sub-route selection modes include order-based selection and percentage-based selection. Order-based selection means that the sub-routes are selected from sub-route 1 to sub-route 12, that is, when sub-route 1 is busy or unavailable, sub-route 2 will be selected, and so on. Percentage-based selection means that when the traffic on a sub-route reaches its preset percentage, the next route will be selected in sequence, so that the sub-route selection probability follows a certain rule. Generally, set it to order-based selection mode. [sub-route1]–[sub-route12] They represent the numbers of twelve sub-routes respectively. The sub-route numbers correspond to the data in the sub-route table. When you enter a sub-route number, follow the order: sub-route 1 to sub-route 12. [Percentage of Sub-Route1]–[Percentage of Sub-Route12] The value range is 1–100. They are available when the sub-route selection mode is percentage-based selection. If the sub-route selection mode is order-based selection, set this parameter to 0; if the sub-route selection mode is percentage-based selection, the sub-route will be selected according to the given percentage.

9-17



Caution: z

One trunk route can have a maximum of 12 sub-routes.

z

If it is expected that sub-route 1 is selected in prior, and sub-routes 2 and 3 share load only when sub-route 1 is fully busy, you can use the percentage-based selection mode. Their percentages are set to 100, 50, and 50 respectively.

IV. Related Commands See Table 9-10 for the commands related to route configuration. Table 9-10 List of commands related to route configuration Command

Description

LST RT

To list route information

ADD RT

To add route

MOD RT

To modify existing route

RMV RT

To remove existing route

9.3.10 Adding Route Analysis Data I. Background Information This command is used to add a record to the route analysis table. Before adding route analysis data, check if the corresponding route selection code, route selection source code, route number, and time index data have been configured. The MSC obtains the route number and signaling priority flag by querying the route analysis table with such call attributes as route selection code, route selection source code, caller type identification, transmission capability, time index data, and callee address indicator. The route analysis table associates number analysis with trunk routing. Therefore, it makes a preparation for outgoing routing.

II. Command ADD RTANA

III. Major Parameters [Route Selection Code]

9-18



It specifies the outgoing routing mode of a call prefix, corresponding to the route selection code in the call prefix. It must be defined in the command ADD CNACLD first and then referenced here. [Route Selection Source Code] It specifies the outgoing routing mode of a call source, corresponding to the route selection source code of the call source. It must be defined in the command ADD CALLSRC first and then referenced here. [Caller Subscriber Category] It indicates the type to which a subscriber belongs. Generally, set it to "ALL (ALL CATEGORIES)". [Address Information Indicator] This parameter indicates the service attributes of a called subscriber. It includes "International Toll", "National Toll", "Local Call", and "All Categories". Generally, set it to "ALL (ALL CATEGORIES)". [Transmission Capability] The parameter indicates the transfer capability of a route. You can select different transfer capabilities as needed. Generally, set it to "ALL (ALL CATEGORIES)". [Time Index] The parameter corresponds to the time index number in the corresponding time index table. [Route Number] It defines the route number used by the route analysis table. It must be defined in the command ADD RT first and then referenced here. [Signalling as Prior] It defines the network signaling capability of an outgoing route. "FIRST" means that a circuit is selected preferentially; "MUST" means that a circuit must be selected, and if there is no such idle circuit, the routing will fail. "NOCHG (NOT CHANGE)" means that the circuit selection mode will not be changed. Set it according to the network signaling capability at the caller side. Generally, set it to "NOCHG (NOT CHANGE)" or "FIRST".

IV. Related Commands See Table 9-11 for the commands related to the configuration of route analysis data.

9-19



Table 9-11 List of commands related to the configuration of route analysis data Command

Description

LST RTANA

To list route analysis record

ADD RTANA

To add route analysis record

MOD RTANA

To modify route analysis record

RMV RTANA

To remove route analysis record

Caution: z

Route selection source code is the same as that of a call source, therefore the corresponding call source data must have been configured before route analysis data is added

z

Before adding any route analysis data, you must have configured the callee analysis data of the peer MSC (including [Route Selection Code]). You can run the LST CNACLD command to have a check. If the callee analysis data has been configured, you need not to configure it again. If not, add it by using the ADD CNACLD command.

9.3.11 Adding SS7 Trunk Group I. Background Information None.

II. Command ADD N7TG

III. Major Parameters [Trunk Group] Trunk group number. [MGW Index] This parameter indicates the index number of MGW to which a trunk group belongs. The MGW index has been defined in the ADD MGW command. [Group Direction] Select this parameter according to the actual conditions.

9-20



[Sub-Route Number] It specifies the sub-route to which a trunk group belongs, and it has been defined in the command ADD SRT. [OPC] This parameter refers to the local signaling point code, and has been defined in the SET OFI command. [DPC] This parameter refers to the signaling point code of the peer entity. Its default value is [Destination point code 1] of the office direction table that [Sub-route number] corresponds to. Set it to the signaling point code of the peer MSC. [Circuit Type] Select this parameter according to actual conditions. Here select "ISUP". [Incoming Call Authority] This parameter is used to control the authorities for using incoming trunk circuits. Only the calls of the allowed types can be connected. You can specify this parameter as needed, or select all default values. [Outgoing Call Authority] This parameter is used to control the authorities for using outgoing trunk circuits. Only the call of the allowed types can go through. You can specify this parameter as needed. Generally, set it to "All allowed", because call authorities are controlled at the subscriber end. [Call Source Code] Its value is defined in the ADD CALLSRC command. For the other parameters, adopt their default values.

IV. Related Commands See Table 9-12 for the commands related to SS7 trunk group configuration. Table 9-12 List of commands related to SS7 trunk group configuration Command

Description

ADD N7TG

To add SS7 trunk group

MOD N7TG

To modify SS7 trunk group

LST TG

To list trunk circuit groups (including SS7 trunk group)

9-21



Command RMV TG

Description To remove trunk circuit group (including SS7 trunk group)

9.3.12 Adding SS7 Trunk Circuit I. Background Information To add a trunk circuit, you must ensure that the trunk group to which the trunk circuit belongs must exist. If not, add the trunk group first. If the board on which the trunk circuit is located does not exist, add the trunk circuit board according to the circuit type (TUP/ISUP) and obtain the trunk circuit number according to the board number.

II. Command ADD/MOD N7TKC

III. Major Parameters [Module Number] This parameter indicates the module number of the WCCU/WCSU to which this trunk circuit belongs. You can query it with the LST MDU command. [Trunk Group] This parameter indicates the number of the SS7 trunk group to which a trunk circuit belongs. Its value has been defined in the ADD N7TG command. [Start Circuit] This parameter indicates the start circuit number. It is an internal parameter of the MSOFTX3000 and corresponds to TID and CIC. There is no strict limit on its value, except that it should be unique in the office. It is recommended to set it to the value of TID. [End Circuit] This parameter indicates the end circuit number. It is an internal parameter of the MSOFTX3000, and corresponds to TID and CIC. There is no strict limit on its value, except that it should be unique in the office. It is recommended to set it to the value of TID. [Start CIC] This parameter corresponds to the start CIC at the peer MSC side.

9-22



[Master ID of Start Circuit] It is used to set whether the trunk circuit defined in the parameter “Start Circuit” is primarily controlled by the MSC. It must be negotiated with the peer office. [Circuit State] This parameter defines the state of a circuit or some circuits added. Use the default value “Available”. [Start Circuit Termination ID] This parameter indicates the ID of a termination corresponding to the start circuit. It is an important parameter to identify a physical circuit and is used to indicate which E1 of MGW is connected to the peer MSC. Set this parameter on MGW. You can make termination IDs to correspond to E1 timeslots one to one, to obtain the starting termination ID of the E1 connected to the peer MSC.

IV. Related Commands See Table 9-13 for the commands related to SS7 trunk circuit configuration. Table 9-13 List of commands related to SS7 trunk circuit configuration Command

Description

ADD N7TKC

To add SS7 trunk circuit

MOD N7TKC

To modify SS7 trunk circuit

RST N7TKC

To reset SS7 trunk circuit

SRS N7TKC

To stop resetting SS7 trunk circuit

BLK N7TKC

To block SS7 trunk circuit

SBL N7TKC

To stop blocking SS7 trunk circuit

UBL N7TKC

To unblock SS7 trunk circuit

SUL N7TKC

To stop unblocking SS7 trunk circuit

DSP N7TKC

To display SS7 trunk circuit

LST TKC

To list SS7 trunk circuits

RMV TKC

To remove SS7 trunk circuit

9-23



Caution: After adding a circuit, you need to set the timeslot configured as link to “UNAVAILABLE” with the command MOD N7TKC. For “Start Circuit” and “End Circuit”, select the timeslot configured as link in this E1. For “Circuit State”, select “UNAVAILABLE”.

9.4 Configuration Example 9.4.1 Description of Example An MSC is added. Between the MSOFTX3000 and the peer MSC; ISUP signaling is used. The MGW concurrently serves as the signaling gateway to fulfill the signaling adaptation from IP bearer to TMD bearer. Related information of the MSOFTX3000 is shown in Table 9-14. For the local office information, see the part “Configuration Example” in Chapter 3.

9-24



Table 9-14 Information table Item


Network indicator

AA0001

National active

Service mode


WIFM module number


Peer MSC signaling point code

Load sharing

NULL

132

1004

AA0001

M3UA link number

Local IP

Local port


Port of peer MGW

Server/Cli ent

0

173.20.200.1 32

2905

173.20.200.93

2905

Client

Termination ID (physical circuit for interworking of MGW with MSC server)

CIC


MGW Index

32–63

0–32

22

1

Basic information


M3UA link information Circuit

Trunk route

Prefix

Office direction

Route number

Sub-route number

Trunk group

Circuit type

1

1

1

1

ISUP

Prefix



13910

1

0

9.4.2 Configuration Description //Add M3UA. LST OFI:; LST FECFG:; //Query the local IP address of WIFM ADD M3LE: LEX=0, LENAME="MscM3UA", NI=NAT, OPC=" CC0004", LET=AS; ADD M3DE: DEX=0, DENAME="MgwM3ua", NI=NAT, DPC="1004", STPF=TRUE, DET=SG; ADD M3DE: DEX=1, DENAME="MSCM3ua", NI=NAT, DPC=" AA0001", DET=SP; ADD M3LKS: LSX=0, LSNAME="ToMGW1", ADX=0, WM=ASP; ADD M3RT: RTNAME="ToMGW1", DEX=0, LSX=0; ADD M3RT: RTNAME="ToMSC", DEX=1, LSX=0;

ADD

M3LNK:

MN=132,

LNKN=0,

LNKNAME="TO-MGW1",

LOCIP1="173.20.200.132",


9-25



//Configure the office direction to MSC. ADD OFC: OFFICEDIR=1, ON="MSC-1", OOFFICT=MSC, DOL=SAME, DOA=MSC, NI=NAT, DPC1="AA0001", SIG=MTP3; ADD SRT: SRC=1, O=1, SRN="MSC-1"; ADD RT: R=1, RN="MSC-1", SR1=1; ADD RTANA: RSC=1, RSSC=0, RUT=ALL, ADI=ALL, TP=ALL, TMX=0, R=1, ISUP=ISUP_F;

//Configure the SS7 trunk circuit to MSC. ADD

N7TG:

TG=1,

MGW=1,

G=INOUT,

SRC=1,

SOPC="CC0004",

SDPC="AA0001",


9-26


Chapter 10 Configuring Data for Interworking with PSTN

Chapter 10 Configuring Data for Interworking with PSTN 10.1 Introduction to the Chapter This chapter describes the data configuration process at MSOFTX3000 for interworking with the public switched telephone network (PSTN). This chapter contains the following sections: z

Concepts Related to Data Configuration for Interworking with PSTN

z

Collecting Data for Interworking with PSTN

z

Configuring Data for Interworking with PSTN

z


10.2 Concepts Related to Data Configuration for Interworking with PSTN 10.2.1 MTP For the concepts about MTP, refer to Chapter 7 “Configuring Data for Interworking with HLR”.

10.2.2 Route and Trunk I. Office Direction If there is a direct voice channel between the local exchange and another exchange, it is taken that there is an office direction. SCP

HLR

GMSC 0

SMC

1

MSC 3 BSC

2 RNC

Figure 10-1 Office direction

10-1

MSC2



As shown in Figure 10-1, there are four offices having traffic with the local MSC: GMSC, MSC2, BSC, and RNC. Therefore, the local MSC has four office directions to GMSC, MSC2, BSC, and RNC, which are numbered 0, 1, 2, and 3 respectively. Because the HLR, SCP, and SMC have no traffic with the local MSC and there are only signaling messages between them, they are not the office directions of the local MSC.

II. Route, Subroute, and Load Sharing 1)

Route and subroute

For an office direction, the set of all subroutes to it is called a route. If there is a direct voice channel between two offices, it is taken that there is a subroute between them. One route may contain multiple subroutes, and different routes may contain the same subroutes. Through these subroutes, a call can finally reach the specified office. The concepts about route and subroute are illustrated in Figure 10-2. Subroute 1

A

B Subroute 2

C Subroute 3

D Figure 10-2 Routes A, B, C, and D represent four exchanges (offices). A has three office directions to B, C, and D respectively. As shown in the figure, the route from A to B contains three subroutes: subroute 1, subroute 2, and subroute 3. Subroute 1 is a direct subroute, while subroute 2 and subroute 3 are alternative subroutes. The subroute allocation depends on the network planning. For example, for subroutes 2 and 3 of office A, office C needs to be configured with subroute C—B, and office D needs to be configured with subroute D—B. 2)

Load sharing

One route can contain twelve subroutes in maximum. Proper allocation and selection of subroutes can help achieve load sharing of a route. The load sharing mode is described as follows: The subroutes are selected based on percentage or order for carrying traffic.

10-2



III. Route Selection Source Code and Route Selection Code 1)


The route selection source code is determined by call source, and it is employed in route selection. For the calls with the same prefix, if it is necessary to select different outgoing routes for different call sources, multiple route selection source codes may be set. Different call sources can correspond to one route selection source code, so that it can be determined that the same call prefix (for example, special service number) is in different routes of different offices. For a special service number, you can set corresponding route selection codes for different call sources to use different outgoing routes. In this way, an emergency call can be connected to the nearest processing center in time. 2)


The route selection code is determined by DN set and call prefix, and is employed in route selection. It refers to the route selection policy code used when calls with a certain prefix are originated.

IV. Trunk Group and Trunk Circuit 1)

Trunk group

The SS7 trunk group is generally bi-directional, and used to carry outgoing or incoming traffic. The trunk group is the component building a subroute, and it is a set of trunk circuits with the same properties. It can be composed of one or multiple PCM systems. The trunk circuits to the same office direction are grouped into one trunk group. 2)

Trunk circuit

The trunk circuit is the component constituting a trunk group, and one trunk circuit corresponds to one timeslot in E1 line. In SS7, one E1 has 32 timeslots, numbered from 0 to 31. Timeslot 0 is used for synchronization. To ensure that an outgoing call will not use timeslot 0 as the trunk circuit, use the command MOD N7TKC to modify timeslot 0 to "Unavailable". The other timeslots in E1 can be used for signaling transmission, that is, to serve as links. In this case, it is required to set the circuits to be used as links to "Unavailable".

V. Circuit Identification Code The circuit identification code (CIC) is used to identify a circuit between two SPs. CIC fields only exist in the TUP and ISUP messages of circuit switched services. Because a CIC field is 12 bits long, there can be 4096 circuits between two SPs in maximum.

VI. CIC Numbering Principles The principles for numbering CICs are as follows:

10-3



CIC is used when the local office is interconnected with PSTN/TMSC/GMSC, and it should be negotiated with the peer office.

z

The allocated trunk CICs in one E1 should be consecutive and in ascending order.

VII. Principles for Naming Trunk/Route

Important Note: You must number SS7 trunks uniformly in an office direction. If some modules are added or the trunk circuits of an office direction are expanded, you must number the newly added trunk groups within the original number range, thus keeping the consecutiveness and sticking to the original principle.

The principles for numbering trunks/routes are as follows: z

The office direction name is the same as the office name. It can be the name of a city where the office is resident.

z

The subroute name and direct office direction have one-to-one correspondence relationship. For example, if an office is a toll exchange, the subroute name is toll exchange. If an office direction contains multiple subroutes, the subroute names are differentiated by the suffixes 1, 2, and so on.

z

If a route contains only one subroute, its name can be the subroute name. If a route contains multiple subroutes, its name will be the name of subroute 1 + the name of subroute 2. If subroute names are similar, for example, TMSC1 and TMSC2, the route name can be TMSC.

z

A trunk group name should indicate outgoing trunk, incoming trunk, or bi-directional trunk: "IN" stands for incoming trunk, "OUT" stands for outgoing trunk, and no indicator means bi-directional trunk.

10.2.3 Networking Between MSOFTX3000 and PSTN MSOFTX3000 and the PSTN exchange use ISUP protocol, which may be TDM based or IP based. In the current networking mode, a semi-permanent connection is established on MGW, which transparently transmits ISUP messages between PSTN and MSOFTX3000 over TDM. See Figure 10-3.

10-4



MSOFTX 3000 TDM bearer Semi-permanent connection TDM bearer

MGW

PSTN

ISUP MTP3 MTP2 MTP1

Figure 10-3 Networking and protocols between MSOFTX3000 and PSTN In MSOFTX3000, you can only set the signaling data. The trunk circuit data should be set in MGW.

10.2.4 Parameter Relationship The parameter relationships for interworking between MSOFTX3000 and PSTN are illustrated in Figure 10-4 and Figure 10-5 . The solid lines represent the relationships with external entities (PSTN exchange) and the dotted lines represent the relationships between internal commands. PSTN parameters


Peer end MSC DPC Signaling network indicator Local OPC

ADD N7LKS ][LinkSet Index]

[DSP index] [Original Point Code]


[IN]

ADD N7RT

[DPC]

[LinkSet Index [DSP index] [Priority]

ADD N7LNK [Link No.] [Start Circuit No.] [LinkSet Index] SLC

[Signaling Link Code]

Figure 10-4 Parameter relationship (MTP) between MSOFTX3000 and PSTN

10-5

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Peer office parameters


MSOFTX3000 parameters ADD OFC [Network ID] [Office directioin]

Destination entity signaling point code

[Destination Point Code] [signal bearer type] ADD SRT [Office Direction Number] [Sub-route Number]

ADD RT [1st sub-route] [Route Number] ADD RTANA [Route Number] [Route Selection Code] [Route Selection Source Code](LST CALLSRC) ADD N7TG [Trunk Group] [MGW Index] (ADD MGW) [Sub-route number] [OPC] (SET OFI) [DPC] [Call source] (ADD CALLSRC) ADD N7TKC [Trunk Group] [Start CIC]

Start CIC


Figure 10-5 Parameter relationship (route and trunk) between MSOFTX3000 and PSTN

10-6



10.2.5 General Configuration Principles The procedures and commands for configuring data for interworking between MSOFTX3000 and PSTN equipment are listed in Table 10-1. Table 10-1 Procedures and commands for configuring data at MSOFTX3000 for interworking with PSTN Procedure

Command

1. Negotiate and prepare data

ADD MGW (LST FECFG)

1) Configure interworking data between MSOFTX3000 and MGW

SET DPA

2) Add semi-permanent connection at MGW

ADD SPC

2. Configure MTP

ADD TDMIU

ADD N7DSP

1) Add MTP DSP

ADD N7LKS

2) Add MTP link set

ADD N7RT

3) Add MTP route

ADD N7LNK

4) Add MTP link 3. Configure routing information

ADD OFC

1) Add office direction to PSTN

ADD SRT

2) Add subroute

ADD RT

3) Add route

ADD RTANA

4) Add route analysis data 4. Configure trunk circuit

ADD N7TG

1) Add SS7 trunk group

ADD N7TKC

2) Add SS7 trunk circuit

10.3 Collecting Data for Interworking with PSTN Before configuring data for interworking with PSTN, you need to collect the interfacing data between MSOFTX3000 and PSTN, as listed in Table 10-2. The shadowy columns are the parameters that need be negotiated between both ends for consistency or of which one end must notify the other end. Other parameters are the internal ones of the MSOFTX3000.

10-7



Table 10-2 Data for interworking with PSTN Item

Data

Basic information


Network indicator of signaling point

/

Signaling link

Link number


Termination ID (number of the physical circuit through which MGW reaches PSTN)

CIC

WCCU/W CSU module number

Office direction

Route number

Subroute number

Trunk group

Prefix



WCSU module number

Link set

Intra-module circuit number (E1/timeslot)

Link type

/

Circuit

/ Trunk route

Circuit type

/

Prefix

/

10.4 Configuring Data for Interworking with PSTN 10.4.1 Negotiating and Preparing Data I. Adding Interworking Data Between MSOFTX3000 and MGW For detailed steps to configure interworking data between MSOFTX3000 and MGW, refer to Chapter 4 “Configuring Data for Interworking with MGW” of this manual.

II. Adding Semi-Permanent Connection at MGW The steps to add a semi-permanent connection are as follows: 1)

Add interface board (ADD TDMIU).

2)

Add semi-permanent connection (ADD SPC).

10-8



10.4.2 Configuring MTP Data Refer to sections 6.4.2–6.4.5 in Chapter 6 “Configuring Data for Interworking with BSC” to configuration data for the MTP layer. The steps to add MTP links are as follows: 1)


2)


3)


4)


10.4.3 Adding Office Direction I. Background Information None

II. Command ADD OFC

III. Major Parameters [Office Direction] It is allocated uniquely in the system and used to identify an office direction. [Office Direction Name] It is recommended to use standard name for the sake of identification, for example, "PSTN-1". [Opposition Office Type] Set the value according to the opposite PSTN exchange type. [Peer Office Level] The level of the PSTN exchange is the same as that of MSOFTX3000 in the network. Select "SAME (PEER)" here. [Peer Office Attribute] For this parameter, select "PSTN (PSTN)". [Network ID] Set it to "National" here. [Destination Point Code1]–[Destination Point Code16] Set it to the DPC of the PSTN exchange. For the other parameters, use the default values.

10-9




Description

ADD OFC

To add office direction

RMV OFC

To remove existing office direction

MOD OFC

To modify attributes of existing office direction

LST OFC

To list office direction configured

10.4.4 Adding Subroute I. Background Information To add a subroute, first ensure that the office direction of this subroute exists. Use the LST OFC command to query whether there is such an office direction. If the office direction does not exist, use the ADD OFC command to add it. After adding the subroute, add the route to which the subroute belongs before adding a trunk group for the subroute.

II. Command ADD SRT

III. Major Parameters [Subroute Number] It identifies a subroute, which is numbered globally. [Office Direction Number] It refers to the number of an office direction to which a subroute points. It has been defined in the ADD OFC command. [Subroute Title] A subroute should be titled as clearly as possible to indicate the route features. It is recommended that this title be the same as the office direction name. [Group Selection] In a subroute, a trunk group should be selected according to the trunk group number (including maximum number, minimum number, loop mode, and random mode). Generally, select "Loop" by default. "Loop" here means to select the group number from the next one to the last selected. "Minimum" means to select the group number always from the minimum one. "Maximum" means to select the group number always from the maximum one. "Random" means to select the group number from all trunk groups (of a 10-10



subroute) randomly. In addition, you need to set it according to the customer's requirement.

IV. Related Commands See Table 10-4 for the commands related to subroute configuration. Table 10-4 List of commands related to subroute configuration Command

Description

LST SRT

To list subroute information

ADD SRT

To add subroute

MOD SRT

To modify subroute

RMV SRT

To remove subroute

10.4.5 Adding Route I. Background Information A route is a set of all subroutes from the local office to a certain office direction. To add a route, you must ensure that the subroutes composing the route should have existed.

II. Command ADD RT

III. Major Parameters

Important Note: One trunk route can have five subroutes in maximum. If it is expected that subroute 1 is selected with highest priority, and subroutes 2 and 3 share load only when subroute 1 is fully busy, you can use the percentage-based selection mode. Their percentages are set to 100, 50, and 50 respectively.

[Route Number] The route numbers are planned according to the numbering principles. [Route Type] There are two route types: ordinary routing and queued routing. Ordinary routing means that a call will not be queued if the routing fails. Queued routing means that a call will wait for an idle circuit at the subscriber side if the routing fails. Generally, set it to ordinary route.

10-11



[Subroute Selection Mode] The subroute selection modes include order-based selection and percentage-based selection. Order-based selection means that the subroutes are selected from subroute 1 to subroute 12, that is, when subroute 1 is busy or unavailable, subroute 2 will be selected. Percentage-based selection means that when the traffic on a subroute reaches its preset percentage, the next route will be selected according to the order, so that the subroute selection probability follows a certain regulation. Generally, set it to order-based selection mode. [subroute1]–[subroute12] They represent the numbers of twelve subroutes respectively. The subroute numbers correspond to the data in the subroute table. When you enter a subroute number, follow the order: subroute 1–subroute 12. [Percentage of Subroute1]–[Percentage of Subroute12] The value range is 1–100. They are available when the subroute selection mode is percentage-based selection. If the subroute selection mode is order-based selection, set this parameter to 255 (which means unavailability); if the subroute selection mode is percentage-based selection, the subroute will be selected according to the given percentage.

IV. Related Commands See Table 10-5 for the commands related to route configuration. Table 10-5 List of commands related to route configuration Command

Description

LST RT

To list route information

ADD RT

To add route

MOD RT

To modify existing route

RMV RT

To remove existing route

10.4.6 Adding Route Analysis Data I. Background Information This command is used to add a record to the route analysis table. Before adding route analysis data, check if the corresponding route selection code, route selection source code, route number, and time index data have been configured. Route selection source code is the same as that of a call source, so the corresponding call source data must have been configured before route analysis data is to be added.

10-12



II. Command ADD RTANA

III. Major Parameters [Route Selection Code] It specifies the outgoing routing mode of a call prefix, corresponding to the route selection code in the call prefix. It must be defined in the command ADD CNACLD first and then referenced here. [Route Selection Source Code] It specifies the outgoing routing mode of a call source, corresponding to the route selection source code of the call source. It must be defined in the command ADD CALLSRC first and then referenced here. [Caller Subscriber Category] It indicates the type to which a subscriber belongs. Generally, set it to "ALL (ALL CATEGORIES)". [Address Information Indicator] This parameter indicates the service attributes of a called subscriber. It includes "International Toll", "National Toll", "Local Call", and "All Categories". Generally, set it to "ALL (ALL CATEGORIES)". [Transmission Capability] The parameter indicates the transfer capability of a route. You can select different transfer capabilities as needed. Generally, set it to "ALL (ALL CATEGORIES)". [Time Index] The parameter corresponds to the time index number in the corresponding time index table. [Route Number] It defines the route number used by the route analysis table. It must be defined in the command ADD RT first and then referenced here. [Signalling as Prior] It defines the network signaling capability of an outgoing route. "FIRST" means that a circuit is selected preferentially; "MUST" means that a circuit must be selected, and if there is no such idle circuit, the routing will fail. "NOCHG (NOT CHANGE)" means that the circuit selection mode will not be changed. Set it according to the network signaling capability at the caller side. Generally, set it to "NOCHG (NOT CHANGE)" or "FIRST".

IV. Related Commands See Table 10-6 for the commands related to the configuration of route analysis data.

10-13



Table 10-6 List of commands related to the configuration of route analysis data Command

Description

LST RTANA

To list route analysis record

ADD RTANA

To add route analysis record

MOD RTANA

To modify route analysis record

RMV RTANA

To remove route analysis record

10.4.7 Adding SS7 Trunk Group I. Background Information None

II. Command ADD N7TG

III. Major Parameters [Trunk Group] For the specific settings, see the numbering principles. Because SS7 trunk groups, A interface trunk groups, and R2 signaling trunk groups are all numbered uniformly in the trunk group table, every one of them should be numbered uniquely. [MGW Index] It indicates the index number of the MGW to which a trunk group belongs. The MGW index has been defined in the ADD MGW command. [Group Direction] It defines whether a trunk serves as an incoming channel or outgoing channel. If you select “Bidirectional trunk”, a trunk can serve as both an incoming and outgoing channel. SS7 trunk groups are bidirectional generally. [Subroute Number] It specifies the subroute to which a trunk group belongs, and it has been defined in the command ADD SRT. MSOFTX3000 references the corresponding record in the subroute data table through this parameter. [OPC] It is one of the parameters for MSOFTX3000 to interwork with the opposite office. It specifies the originating point code of the No. 7 trunk group. The default code is the signaling point code of the local office in the national network defined in the SET OFI command. If it is required to use a signaling point code in other signaling network, for example, international network, you must specify it separately.

10-14



Due to the limitation of the SS7 CIC length (12 bits), two offices can enable a maximum of 4096 No. 7 trunk circuits in the case of using a single signaling point code. If it is necessary to enable more trunk circuits, multi-signaling-point-code is required. If the multi-signaling-point-code is used in the local office, this parameter must be defined in the ADD OFI command before being referenced here. [DPC] It is one of the parameters for MSOFTX3000 to interwork with the opposite office. It is used to specify the destination point code of the SS7 trunk group. The system uses the “DPC1” defined in the ADD OFC command by default. Due to the limitation of the SS7 CIC length (12 bits), two offices can enable a maximum of 4096 No. 7 trunk circuits in the case of using single signaling point code. If it is necessary to enable more trunk circuits, multi-signaling-point-code is required. If the multi-signaling-point-code is used in the opposite office, this parameter must be defined in the ADD OFC command before being referenced here. [Call source code] It has been defined in the ADD CALLSRC command. [Circuit Type] It specifies the signaling type used by the SS7 trunk group, including ISUP and TUP. The default type is “ISUP”. [Circuit selection] It specifies the policy for selecting the trunk circuits in a trunk group. There are seven options: z

MIN: The system always selects a trunk circuit from the minimum number. The preferential selection of the trunk circuits can be realized through this mode.

z

MAX: The system always selects a trunk circuit from the maximum number. The preferential selection of the trunk circuits can be realized through this mode.

z

CYC: The system selects a circuit from the next one to the last selected circuit number each time. If the last selected number is the maximum one, the next one is the minimum number.

z

FIFO: For all the circuits of the trunk group, the system selects a circuit according to the “first in, first out” principle.

z

CTRL: For the circuits controlled by the local office, the system selects a circuit according to the “first in, first out” principle. For the circuits not controlled by the local office, the system selects a circuit according to the “first in, last out” principle.

z

RNDM: The system selects a trunk circuit randomly. This mode is seldom used.

z

USR: The system selects a circuit according to the instruction from the user side.

If the SS7 trunk group is a bidirectional one, it is recommended to set “Circuit selection mode” to “CTRL” for the purpose to prevent two offices occupying the same circuit at the same time.

10-15



[Reserved circuit number] It specifies the number of circuits reserved for prior calls. For common calls, routing will fail if all common trunk circuits are busy. For prior calls, reserved circuits can be used if all common trunk circuits are busy. Generally, call priority is not set, so keep the default value “0” of the parameter. [Connect satellite circuit] It identifies whether the SS7 trunk is carried over a satellite circuit. Satellite circuits are used for international offices only, so set the parameter to “No”. [Incoming call authority] It controls the authorities for using incoming trunk circuits. Only those allowed types of calls can be connected. You can specify this parameter as needed, or select all default values. [Outgoing call authority] It controls the authorities for using outgoing trunk circuits. Only those allowed types of calls can be connected. You can specify this parameter as needed. Generally, set it to "All allowed", because the calling-out authorities are controlled at the subscriber end. [DOD2] It indicates whether outgoing trunks send secondary dial tone. It is applicable to the PBX in the fixed network only. In the mobile network, set it to “No” [CLIR flag] It sets the value of “CLIP” in the Initial Address Message (IAM) or Initial Address Message with Information (IAI) of the incoming call signaling or outgoing call signaling, that is, the original value of “CLIP” in the call signaling is invalid. z

If the value is “INCOMING CLIR”, it indicates that the calling line identification presentation is restricted in the incoming call signaling.

z

If the value is “OUTGOING NO CLIR”, it indicates that the calling line identification presentation is not restricted in the outgoing call signaling.

This flag is used for the fixed switch. For MSOFTX3000, use the default value. [Send initial tone] It is available only when the register uses MFP, PULSE, or DTMF. With this parameter set to “YES”, after an incoming trunk is seized, the switch sends the initial tone to the opposite end and then stops it after receiving the forward register signal. Because SS7 does not use the register signaling, this parameter is invalid. Generally, the default value “No” is used. [Abnormal send tone] It controls whether to play the recorded announcement to the opposite office when the call of the trunk group triggers the call failure procedure in MSOFTX3000. [Charging source code] 10-16



It is one of the charging attributes of the incoming trunk group. Its value ranges from 0 to 255. 255 indicates no charging of incoming trunk. [Out-Trunk charging source code] It is one of the charging attributes of the outgoing trunk group. Its value ranges from 0 to 255. 255 indicates no charging of outgoing trunk. [Use opposite pulse] It is used for the inter-office trunk cooperation in the immediate charging. When it is set to “YES”, its meanings for outgoing trunks and incoming trunks are different. z

Outgoing trunk: When there is an outgoing call from the trunk group, the local office needs to receive the charging pulse sent back from the opposite office, and the opposite office needs to cooperate to send the charging pulse to the local office.

z

Incoming trunk: When there is an incoming call to the trunk group, the local office needs to send the charging pulse to the opposite office, and the opposite office needs to cooperate to receive the charging pulse sent from the local office

[Charging complaint] It is one of the charging attributes of the trunk group. It sets whether to generate a complaint ticket when the trunk group is charged. The default value is “NO”, indicating that the system will not generate a complaint ticket. If it is set to “YES”, complaint tickets will be generated for both incoming and outgoing trunk calls. [CAMA] It is available only to incoming trunks, used to set whether the local office performs the centralized charging on incoming trunks. If it is set to “YES”, the local office performs the centralized charging on the incoming trunks. In this case, when the opposite office originates a call through an incoming trunk and the call signaling does not carry the caller number, the local office requests the caller number through signaling. [Can request caller number] It is available only to incoming trunks. When it is set to “YES”, the local office can request the caller number from the opposite office on initiative if the incoming call signaling through the trunk contains no caller number. The default value is “YES”. However, if this feature affects call completion rate or connection time, you can set the option to “NO”. [CLI provision mode] It is valid only for incoming trunks. When the opposite office originates a call through the incoming trunk, this parameter indicates how the local office obtains the caller number from the incoming trunk if the call signaling from the opposite office contains no caller number. [Default caller number]

10-17



It is available only to incoming trunks. If the “CLI provision mode” is “Default number”, the local office will use the default caller number for all calls. [Call barring group] It specifies the call barring group to which a trunk group belongs. If you do not type any value or type “65535”, call barring function is disabled. [Occupancy upper threshold] It defines the maximum seizure duration of a trunk circuit. If a trunk circuit has been seized for longer than this threshold, the system will check the circuit status and generates an alarm. Its value ranges from 0 to 65535 with the unit as second. 0 or 65535 indicates that the threshold is invalid. [Occupancy lower threshold] It defines the minimum seizure duration of a trunk circuit. If a trunk circuit has been seized for shorter than this threshold, the system will count one over-short seizure. If the number of over-short seizures is bigger than the value of the lower 8 bits in the TUP operation reserved parameter 1, the system will generate an alarm. Its value ranges from 0 to 65535 with the unit as second. 0 or 65535 indicates that the threshold is invalid. [Continuity-check] It sets whether the continuity check is conducted to a trunk group. Currently, only response but not start of the continuity check is supported, so set this parameter to “No”. [Time delay value] It sets the maximum transmission delay allowed by the circuits of a trunk group. Its value ranges from 0 to 1023 with the unit as second. If the transmission delay of a call through the circuit segments is larger than the maximum transmission delay allowed by the system, it is required to configure echo canceller. This parameter is generally used for the case of connecting satellite circuits. In other cases, set it to “0”. [GRS timeout to single] It indicates whether to change a group reset message re-transmitted due to timeout to a single circuit reset message. The default value “YES” is used generally. [Transmission capability], [Transmission mode] They define the transmission capability and mode of a trunk group depending on different services. Because MSOFTX3000 trunk groups have no restrictions on the transmission capablity and mode, set these two parameters to the default value “ALL” generally. [CIC change type]

10-18



It is mainly used for the self-loop test of the two SS7 trunk groups (outgoing trunk E1 and incoming trunk E1) with the same office direction in the local office. The configuration principle is described as follows: z

When the self-loop test is not enabled, you must set this parameter to “No change”; otherwise, the trunk interconnection will fail.

z

When the self-loop test is enabled, if the "CIC change type” of the outgoing trunk group is set to “Increase”, the "CIC change type” of the incoming trunk group must be set to “Decrease”, and conversely the same.

z

Generally, this parameter is set to “No change”.

[CIC change value] It is valid only when CIC change is necessary. Because the self-loop test is performed between two E1s, the CIC change value must be an integral multiple of 32. [Availability] It defines the times that a trunk group can be selected in the corresponding subroute. Its value ranges from 0 to 255. In a subroute, every time the system selects the trunk group, the available times of the trunk group will be decreased by 1. When the available times become 0, the system cannot select the trunk group. If the available times of all trunk groups in the corresponding subroute become 0, those times will be assigned with new values, which intend to distribute the traffic over all trunk groups of the subroute according to the expected principle. The default value is 255, indicating that the parameter is invalid. [Soft para of service CTRL] It sets whether a trunk group supports some special services or applications. [Network management source code] It defines the network management attributes of a trunk group. This parameter is available only to incoming trunks and will be referenced when the network management data is configured. [Idle NUM for weak CLIR] Reserved. [Idle NUM for forced CLIR] Reserved. [Barring forwarded call] It sets whether forwarded calls are barred unconditionally. The default value is “No”, indicating that forwarded calls are not barred. If it is set to “Yes”, the system will bar all the calls forwarded through the trunk group. [Default connect]

10-19



During discrimination of a caller number, if the caller number is not found in the caller number discrimination group table, this parameter is used to set whether the call is connected or all. The default value is “Yes”, indicating that the call is connected. [Request CLI] It is available only to incoming trunks. If the incoming call signaling through the trunk does not contain caller number, it is used to define whether the local office requests caller number from the opposite office on initiative. The default option is “NO”, indicating that the local office will not request caller number on initiative. [Request original called number] This parameter is available only to incoming trunks. It sets whether to request the original called number. In a forwarded call (the call redirection indicator is 1), if the incoming call signaling through the trunk does not contain the original called number, this parameter is used to tell the local office whether to request the original called number from the opposite office. The default option is “NO”, indicating that the local office will not request the original called number on initiative. [Connect without ORGCLD] This parameter is available only to incoming trunks. It sets whether the local office gets a call through if the incoming call signaling through the trunk does not contain the original called number or the contained number is invalid in a forwarded call (the call redirection indicator in the signaling message is 1). The default option is “YES”. [Discrimination group No] This parameter is available only to incoming trunks. It defines the corresponding caller discrimination group when it is necessary to discriminate the caller number of a call through the incoming trunk. The default value is “65535” indicating no discrimination. [Overlap send CLD] It specifies whether a trunk group supports overlap code sending mode. MSOFTX3000 supports the following two code sending modes: z

Overlap code sending: When the system receives enough digits of the called number for judging the route, it sends them to the opposite office through the signaling Initial Address Message (IAM) or Initial Address Message with Information (IAI), and then sends the remained digits of the called number one by one through other signaling messges, for example, Subsequent Address Message with One signal (SAO) or Subsequent Address Message (SAM).

z

Group code sending: After the system collects all the digits of the called number, it sends them to the opposite office through one signaling message.

The overlap code sending mode features fast connection but it occupies a plenty of CPU resources. The group code sending mode occupies a few of CPU resources, but the connection is slow, which may affect the quality of the telecom services. Generally, the default mode is the overlap code sending.

10-20



[Circuit Pool No] Reserved. [ECHO CTRL CAPABILITY] It indicates whether the local office provides the EC resources. For the calls of the trunk group, if this parameter is set to “No”, MSC will automatically filter the echo control information in the TUP/ISUP signaling message sent to the opposite office. To be more specific, for the TUP signaling, bit G in the IAI/IAM and bit D in the ACM are both set to “0”; for the ISUP signaling, bit E in the IAM and bit N in the ACM are both set to “0”. If this parameter is set to “Yes”, MSC will set the echo control information in the signaling message according to the echo control procedure. Therefore, when the opposite office supports the echo control procedure, you can set this parameter to "Yes”; otherwise, set it to “No". [EC INITIATIVE] It defines whether to enable the EC function. When “ECHO CTRL CAPABILITY” and “EC INITIATIVE” are enabled simultaneously, they are in AND relationship. To enable the EC function, you must set both parameters to “Yes”. [Generate Bill For Unsuccessful Trunk Calls] It defines whether the system generates call attempt bills when the calls occupying the trunk group fail. Generally, it is not required for MSOFTX3000 to generate call attempt bills, so the default value “NO” is used. For the other parameters, adopt the default values.

IV. Related Commands See Table 10-7 for the commands related to SS7 trunk group configuration. Table 10-7 List of commands related to SS7 trunk group configuration Command

Description

ADD N7TG

To add SS7 trunk group

MOD N7TG

To modify SS7 trunk group

LST TG

To list trunk circuit groups (including SS7 trunk group)

RMV TG

To remove trunk circuit group (including SS7 trunk group)

10-21



10.4.8 Adding SS7 Trunk Circuit I. Background Information For the relationships among “Start CIC”, “Start Circuit Termination ID”, “Start Circuit”, and “End Circuit”, refer to section 6.2.3 of Chapter 6. To add a trunk circuit, you must ensure that the trunk group to which the trunk circuit belongs must exist; otherwise, add the trunk group. If the board on which the trunk circuit is located does not exist, add the trunk circuit board according to the circuit type (TUP/ISUP) and obtain the trunk circuit number according to the board number.

10-22



II. Command ADD/MOD N7TKC

Important Note: After adding a circuit, you need to set timeslot 0 (synchronization timeslot) and the timeslot configured as link of E1 to “UNAVAILABLE” with the command MOD N7TKC. Set timeslot 0 for “Start Circuit” and the timeslot configured as link for “END Circuit” (related to the “Start Circuit No.” in the command ADD N7LNK). Set “Circuit State” to “UNAVAILABLE”.

III. Major Parameters [Module Number] This parameter indicates the module number of the WCCU/WCSU to which a trunk circuit belongs. You can query it with the LST MDU command. [Trunk Group] This parameter indicates the number of the SS7 trunk group to which a trunk circuit belongs. Its value has been defined in the ADD N7TG command. [Start Circuit] This parameter indicates the start circuit number. It is an internal parameter of MSOFTX3000 and corresponds to TID and CIC. It is valid within the module. The range of circuit numbers shall not exceed the limitation of the maximum numbers of tuples (by default, 8000 for each WCCU module). There is no strict limit on its value. It is recommended to set it to the value of TID. [End Circuit] This parameter indicates the end circuit number. It is an internal parameter of MSOFTX3000. It is valid within the module. The range of circuit numbers shall not exceed the limitation of the maximum numbers of tuples (by default, 8000 for each WCCU module). It corresponds to TID and CIC. There is no strict limit on its value. It is recommended to set it to the value of TID. [Start CIC] This parameter corresponds to the start CIC at the peer MSC side. CIC is valid within the office. It cannot be larger than 4096 for the same signaling point. [Master ID of Start Circuit] It is used to set whether the trunk circuit defined in the parameter “Start Circuit” is primarily controlled by the MSC. It must be negotiated with the peer office. [Circuit State]

10-23



This parameter defines the state of a circuit or some circuits added. Use the default value “Available”. [Start Circuit Termination ID] This parameter indicates the ID of a termination corresponding to the start circuit. It is an important parameter to identify a physical circuit and is used to indicate which E1 of MGW is connected to PSTN. Set this parameter on MGW. You can obtain the start termination ID of the E1 connected to PSTN by corresponding termination IDs with E1 timeslots one to one.

IV. Related Commands See Table 10-8 for the commands related to SS7 trunk circuit configuration. Table 10-8 List of commands related to SS7 trunk circuit configuration Command

Description

ADD N7TKC

To add SS7 trunk circuit

MOD N7TKC

To modify SS7 trunk circuit

RST N7TKC

To reset SS7 trunk circuit

SRS N7TKC

To stop the resetting of SS7 trunk circuit

BLK N7TKC

To block SS7 trunk circuit

SBL N7TKC

To stop the blocking of SS7 trunk circuit

UBL N7TKC

To unblock SS7 trunk circuit

SUL N7TKC

To stop the unblocking of SS7 trunk circuit

DSP N7TKC

To display SS7 trunk circuit

LST TKC

To list SS7 trunk circuits

RMV TKC

To remove SS7 trunk circuit


10-24


SCP


SMC

GMLC

HLR

MAP/TDM

MAP/TDM

MAP/TDM

MAP/TDM

MSC Server

MSOFTX 3000

ISUP/TDM

H.248,RANAP /IP

BSSAP+/TDM

SGSN


MGW

MGW

IP/TDM

ISUP/TDM

PSTN

(SG)

RANAP/AAL2 /ATM

BSSAP/TDM

RNC

BSC

Figure 10-6 Networking of MSOFTX3000 As shown in the figure, MSOFTX3000 and MGW are integrated as a whole; a semi-permanent connection (SPC) is established in MGW for transparently transmitting PSTN messages between PSTN and MSOFTX3000; TDM bearer is used between MSOFTX3000 and MGW, as well as between MGW and PSTN. This example is to add a PSTN, which is connected with MGW. The related data to be collected is listed in Table 10-9. For the local office information, refer to Table 3-14 of Chapter 3.

10-25



Table 10-9 PSTN information table Item

Data

Basic information


NI of the signaling point

/

BB0002

National network

WCSU/WSGU module No.

Link set

Intra-module link No.

SLC and SLC sending

Intra-module circuit number (E1 /timeslot )

Link type

22

2

2

1

80 (2/16)

64 kbit/s

Termination ID (number of the physical circuit through which MGW reaches PSTN)

CIC

WCCU/WCS U module No.

MGW Index

64–95

32–63

25

1

Signaling link / / Circuit / Trunk circuit

Office direction

Route numb er

Subroute number

Trunk group

Circuit type

/

2

2

2

2

ISUP

Prefix

Prefix

Route selecti on code


/

666

2

0

10.5.2 Configuration Description /Add MTP layer data. ADD N7DSP: DPX=2, NI=NAT, DPC="BB0002", DPNAME="PSTN-2"; ADD N7LKS: LSX=2, ASPX=2, LSNAME="PSTN-2"; ADD N7RT: LSX=2, DPX=2, RTNAME="PSTN-2"; ADD N7LNK: MN=22, LNKN=2, LNKNAME="PSTN1-2", LNKTYPE=0, TS=80, LSX=1, SLC=1, SLCS=2;

//Add the data of the route to PSTN. ADD OFC: OFFICEDIR=2, ON="PSTN-2", OOFFICT=NATT, DOL=SAME, DOA=PSTN, NI=NAT, DPC1="BB0002", SIG=MTP3; ADD SRT: SRC=2, O=2, SRN="PSTN-2"; ADD RT: R=2, RN="PSTN-2", SR1=2; ADD RTANA: RSC=2, RSSC=0, RUT=ALL, ADI=ALL, TP=ALL, TMX=0, R=2, ISUP=ISUP_F;

10-26



//Add the data of the SS7 trunk circuit leading to PSTN. ADD

N7TG:

TG=2,

MGW=1,

G=INOUT,

SRC=2,

SOPC="CC0004",

SDPC="BB0002",

TGN="PSTN-2", ICR=LCO-1&LC-1&LCT-1&NTT-1&ITT-1, CRF=B0-1&B1-1; ADD N7TKC: MN=25, TG=2, SC=64, EC=95, SCIC=32, SCF=TRUE, TID=64; MOD N7TKC: MN=25, SC=80, EC=80, CS=UNU; MOD N7TKC: MN=25, SC=64, EC=64, CS=UNU;

10-27


Chapter 11 Configuring Data for Interworking with SMC

Chapter 11 Configuring Data for Interworking with SMC 11.1 Introduction to the Chapter This chapter describes the data configuration process at MSOFTX3000 for interworking with a Short Message Center (SMC). This chapter contains the following sections: z

Related Concepts

z

Collecting Data for Interworking with SMC

z

Configuring Data for Interworking with SMC

z


11.2 Related Concepts 11.2.1 SMC SMC is used to control and forward short messages over the MAP layer. In this case, the interaction between MSOFTX3000 and SMC is on the MAP peer layer through the E/G interface. To configure data at MSOFTX3000 for interworking with SMC, you need to add signaling related data instead of voice channel. For the concepts about MTP and SCCP, refer to Chapter 7 “Configuring Data for Interworking with HLR”.

11.2.2 Networking Between MSOFTX3000 and SMC MSOFTX3000 and the SMC apply the MAP protocol to communicate with each other, and the MAP protocol may be based on TDM or IP. The current networking mode is TDM based, as shown in Figure 11-1.

11-1



TDM TDM based E

MSOFTX3000

SMC

MAP TCAP SCCP MTP3 MTP2 MTP1

Figure 11-1 Networking and protocols between MSOFTX3000 and SMC

11.2.3 Parameter Relationship The parameter relationships for interworking between MSOFTX3000 and SMC are illustrated in Figure 11-2. The solid lines represent the relationships with external entities (SMC) and the dotted lines represent the relationships between internal commands. SMC parameters


Signaling network indicator

[DSP index]

[LinkSet Index]

[NI ]

[Adjacent DSP Index]

[DPC]

SMC OPC Peer end MSC DPC

[O PC]

[LinkSet Index] [DSP index]

[NI]

[Priority]

[OPC]

ADD SCCPSSN [NI] [SSN] [SPC] [OPC]

ADD SCCPGT [NI ] SMC NUMBER

ADD N7RT

ADD SCCPDSP [DPC] SLC

ADD N7LKS

[GT Address Information] [SPC]

Figure 11-2 Parameter relationship between MSOFTX3000 and SCP

11-2

ADD N7LNK [Link No.] No] [Start Circuit No.] No ] [[LinkSet ]Index [Signaling Link Code]



11.2.4 General Configuration Procedures The procedures and commands for configuring data for interworking between MSOFTX3000 and SMC equipment are listed in Table 11-1. Table 11-1 Procedures and commands for configuring data at MSOFTX3000 for interworking with SMC Procedure

Command

1. Configure MTP 1) Add MTP3 DSP

ADD N7DSP

2) Add MTP3 link set

ADD N7LKS

3) Add MTP3 route

ADD N7RT

4) Add MTP link

ADD N7LNK

2. Configure SCCP 1) Add SCCP DSP

ADD SCCPDSP

2) Add SCCP subsystem (SMC subsystem)

ADD SCCPSSN

3) Add SCCP GT

ADD SCCPGT

3. Modify MAP parameter table

MOD MAPACCFG

11.3 Collecting Data for Interworking with SMC Before configuring data for interworking with SMC, you need to collect the interfacing data between MSOFTX3000 and the peer SMC, as shown in Table 11-2. In the shadowy columns are the parameters that must be negotiated between both ends for consistency or of which one end must notify the other end. The other parameters are the internal ones of MSOFTX3000. Table 11-2 Data for interworking with SMC Item

Data

Basic information



E.164 number

Link set

Intra-modul e link number


/

Signaling link

WCSU module number

/

11-3


Link type



11.4 Configuring Data for Interworking with SMC 11.4.1 Configuring MTP Data Refer to sections 6.4.2–6.4.5 in Chapter 6 “Configuring Data for Interworking with BSC” to configuration data for the MTP layer. The steps to add MTP links are as follows: 1)


2)


3)


4)


11.4.2 Configuring SCCP Data Refer to sections 7.4.2–7.4.4 in Chapter 7 “Configuring Data for Interworking with HLR” to configure data for the SCCP layer. The steps to add SCCP data are as follows: 1)

Add a DSP of SCCP (ADD SCCPDSP): Select "NAT (NATIONAL NETWORK)" for the parameter “Network Indicator” of the SCCP DSP to the SMC.

2)

Add SCCP subsystems (ADD SCCPSSN): Add MSC and SCMG subsystems to the remote SMC. As the local MSC, VLR and SCMG subsystems have been configured in the local office information table, use the LST SCCPSSN command to have a check to avoid repeated configuration.

3)

Add SCCP GT (ADD SCCPGT): It is only required to configure ordinary GT. Select "NAT (National Network)" for network indicator, "ISDN (ISDN/TELEPHONY NUMBERING PLAN)" for numbering plan, and enter SMC number, for example, 8613900007, for GT address information.

11.4.3 Modifying MAP Parameter Table I. Background Information None

II. Command MOD MAPACCFG

Important Note: This command is used to check or modify the MAP parameter table to enable MAP to support short message mobile originated (SMMO) and short message mobile terminated (SMMT) functions. Generally, you need not modify the MAP parameter table.

11-4



III. Major Parameters [Support SMMO Function] Set this parameter to "Yes". [Support SMMT Function] Set this parameter to "Yes".

IV. Related Commands See Table 11-3 for the commands related to MAP parameter configuration. Table 11-3 List of commands related to MAP parameter configuration Command

Description

MOD MAPACCFG

To modify MAP parameter table

ADD MAPACCFG

To add MAP parameter table

LST MAPACCFG

To list MAP parameter table

11-5




SCP

SMC

GMLC

HLR

MAP/TDM

MAP/TDM

MAP/TDM

MAP/TDM

MSC Server

MSOFTX 3000

ISUP/TDM

H.248,RANAP /IP

BSSAP+/TDM

SGSN


MGW

MGW

IP/TDM

ISUP/TDM

PSTN

(SG) RANAP/AAL2 /ATM

BSSAP/TDM

RNC

BSC

Figure 11-3 Networking of MSOFTX3000 This example is to add an SMC, which is directly connected to MSOFTX3000 through E1 line. The SMC information is shown in Table 11-4. For the local office information, refer to Table 3-14 in Chapter 3.

11-6



Table 11-4 SMC information table Item

Data

Basic information

/

Signaling link

WCSU module number

/

23



E.164 code

D02303

National network

8613600013

Link set



Intra-module circuit number (E1 number/timeslot number)

Link type

13

3

0

112 (3/16)

64 kbit/s

11.5.2 Configuration Description //Add MTP layer data. ADD N7DSP: DPX=13, DPC="D02303", OPC="CC0004", DPNAME="SMC-13"; ADD N7LKS: LSX=13, ASPX=13, LSNAME="SMC-13"; ADD N7RT: LSX=13, DPX=13, RTNAME="SMC-13"; ADD N7LNK: MN=23, LNKN=3, LNKNAME="SMC-13", LNKTYPE=0,TS=112, LSX=13, SLC=0;

//Add SCCP layer data. ADD SCCPDSP: DPX=13, NI=NAT, DPC="D02303", OPC="CC0004", DPNAME="SMC-13", SHAREFLAG=NONE; ADD

SCCPSSN:

SSNX=18,

NI=NAT,

SSN=SCMG,

SPC="D02303",

OPC="CC0004",

NI=NAT,

SSN=MSC,

SPC="D02303",

OPC="CC0004",

SSNNAME="SMC-SCMG"; ADD

SCCPSSN:

SSNX=19,

SSNNAME="SMC-MSC";

ADD

SCCPGT:

GTX=13,

GTNAME="SMC

GT",

NI=NAT,

ADDR=K'8613600013, RESULTT=LSPC2, SPC="D02303";

//Modify MAP parameter table. MOD MAPACCFG: ISSSMMO=YES, ISSSMMT=YES;

11-7

GTI=GT4,

NUMPLAN=ISDN,


Chapter 12 Configuring Data for Interworking with SCP

Chapter 12 Configuring Data for Interworking with SCP 12.1 Introduction to the Chapter This chapter describes the data configuration process at MSOFTX3000 for interworking with a server control point (SCP). For the information on IN service data configuration, refer to Chapter 17 “Configuring IN Service Data” of this manual. This chapter contains the following chapters: z

Concepts Related to Data Configuration for Interworking with SCP

z

Collecting Data for Interworking with SCP

z

Configuring Data for Interworking with SCP

z


12.2 Concepts Related to Data Configuration for Interworking with SCP 12.2.1 SCP Refer to Chapter 7, “Configuring Data for Interworking with HLR” for concepts about MTP and SCCP.

12.2.2 Networking Between MSOFTX3000 and SCP To implement mobile IN services, it is required to add SCP equipment. SCP database entity is transferred through its signaling access unit SAU (front end processor) to MSOFTX3000 instead of being connected to MSOFTX3000 directly. In the current networking, SAU and MSOFTX3000 are connected through E1 line. See Figure 12-1 for the networking mode and protocol stack on the interface.

12-1



TDM TDM CAP

SAU

MSOFTX3000

SCP

CAP TCAP SCCP MTP3 MTP2 MTP1

Figure 12-1 Networking relationship between MSOFTX3000 and SCP

12.2.3 Parameter Relationship The parameter relationships for interworking between MSOFTX3000 and SCP are illustrated in Figure 12-2. The solid lines represent the relationships with external entities. The dotted lines represent the relationships between internal commands. SCP parameters


Signaling network indicator SCP OPC Peer end MSC DPC

[DSP index] [NI ]

ADD N7LKS

[LinkSet Index] [Adjacent DSP Index]

[DPC]

ADD N7RT

[OPC]

[LinkSet Index] [DSP index] [Priority]

ADD SCCPDSP

[NI] [DPC] [OPC]

SLC

ADD N7LNK

[Link No.]

ADD SCCPSSN

[NI] [SSN] [SPC] [OPC] ADD SCCPGT

[NI ] [GT Address Information]

[Start Circuit No.] [LinkSet Index] [Signaling Link Code]

ADD SCPINFO

[SCP Address ] [SCP Address]

[SPC]

Local SCP address

ADD SCPPARA ADD SSPCAPA

[Service Key]

[SCP Address Index] [Service Key]

Figure 12-2 Parameter relationship between MSOFTX3000 and SCP

12.2.4 General Configuration Procedures The procedures and commands for configuring data for interworking between MSOFTX3000 and SCP equipment are listed in Table 12-1. Table 12-1 Procedures and commands for configuring data at MSOFTX3000 for interworking with SCP 12-2



Procedure

Command

1. Configure MTP 1) Add MTP DSP

ADD N7DSP

2) Add MTP link set

ADD N7LKS

3) Add MTP route

ADD N7RT

4) Add MTP link

ADD N7LNK


ADD SCCPDPC

2) Add SCCP subsystems

ADD SCCPSSN

3) Add SCCP GT

ADD SCCPGT

3. Configure SCP basic information 1) Add SSP capability

ADD SSPCAPA

2) Add SCP addressing information

ADD SCPINFO

3) Add SCP parameter information

ADD SCPPARA

12.3 Collecting Data for Interworking with SCP Before configuring data for interworking with SCP, you need to collect the interfacing data between MSOFTX3000 and the peer SCP, as shown in Table 12-2. In the shadowy columns are the parameters that must be negotiated between both ends for consistency or of which one end must notify the other end. The other parameters are the internal ones of MSOFTX3000. Table 12-2 Data for interworking with SCP Item


Basic information


E.164 number

/

Signaling link

WCSU/ WCCU/ WSGU module number

Link set


/

12-3


Intra-module circuit number (E1 number/times lot number)

Link type



12.4 Configuring Data for Interworking with SCP 12.4.1 Configuring MTP Data Refer to sections 6.4.2–6.4.5 in Chapter 6 “Configuring Data for Interworking with BSC” to configuration data for the MTP layer. The steps to add MTP links are as follows: 1)


2)


3)


4)


12.4.2 Configuring SCCP Data Refer to sections 7.4.2–7.4.4 in Chapter 7 “Configuring Data for Interworking with HLR” to configure data for the SCCP layer. The steps for adding SCCP data are as follows (MSOFTX3000 is connected with SCP through the networking mode illustrated in Figure 12-1): 1)

Add a DSP of SCCP (ADD SCCPDSP): Select “National Network” for the parameter “Network Indicator” of the SCCP DSP to SCP.

2)

Add SCCP subsystems (ADD SCCPSSN): Add a CAP subsystem to the local MSOFTX3000, and add SCMG and CAP subsystems to the remote SCP. As the local MSC, VLR and SCMG subsystems have been configured in the local office information, use the LST SCCPSSN command to have a check to avoid repeated configuration.

3)

Add SCCP GT (ADD SCCPGT): It is only required to configure ordinary GT. Select "National Network" for NI, "ISDN (ISDN/TELEPHONY NUMBERING PLAN)" for numbering plan, and enter SCP number, for example, 8613900007, for GT address information. For the translation result type, select “LSPC2 (SPC)”.

12.4.3 Configuring SSP Capability This section describes how to configure the service key supported by the MSOFTX3000. The service key is used for traffic statistics of IN service. It is recommended to configure the service key.

I. Command ADD SSPCAPA

12-4



Important Note: This command is used to configure the service keys supported by MSOFTX3000. Only when a service key is supported by MSOFTX3000 (use the LST SRVKEY command to query the configured key), can the intelligent call corresponding to this key be triggered at the local office; otherwise, the SCP will send establish temporary connection (ETC) messages to route the IN services to the auxiliary SSP for implementation.

II. Major Parameters [Service Key] It is used to define IN services. This parameter should be negotiated with SCP. In the same intelligent network, the service keys should be consistent. [IPSSP Capability] It is used to report the IP/SSP capability to SCP. Several capabilities in the list are not supported currently. Select ”CLEAR ALL” here.

III. Related Commands See Table 12-3 for the commands related to SSP capability configuration. Table 12-3 List of commands related to SSP capability configuration Command

Description

ADD SSPCAPA

To add SSP service support capability

RMV SSPCAPA

To remove existing SSP service support capability

MOD SSPCAPA

To modify existing SSP service support capability

LST SSPCAPA

To list SSP service support capabilities

12.4.4 Adding SCP Addressing Information I. Command ADD SCPINFO

II. Major Parameters [SCP Address Index] It is used to identify an SCP uniquely in the system. [SCP Address] It refers to the SCP address information, for example, "8613600006".

12-5



[CAP Version] It refers to the supported CAP version. This parameter should be negotiated and be consistent with that of the peer SCP. [SCF ID] This parameter is defined by the network operator, and used to identify an SCP.

III. Related Commands See Table 12-4 for the commands related to the configuration of SCP addressing information. Table 12-4 List of commands related to the configuration of SCP addressing information Command

Description

ADD SCPINFO

To add SCP address information

RMV SCPINFO

To remove existing SCP address information

MOD SCPINFO

To modify existing SCP address information

LST SCPINFO

To list SCP address information

12.4.5 Adding SCP Parameter Information This command maps “SCP Parameter Index” to “SCP Address Index” and configures the service key required by the IN service and the default call processing mode.

I. Command ADD SCPPARA

Important Note: This command is used to map SCP parameter indexes to SCP address indexes, and obtain the service keys required for triggering IN services and the default call processing mode.

II. Major Parameters [SCP Parameter Index] It is used to identify an SCP parameter uniquely in the system. [SCP Address Index] This parameter is defined in the ADD LKINDPOS command. [Service Key]

12-6



This parameter is defined in the ADD SSPCAPA command (used for IN announcement). PPS and MVPN are common IN services for the present. Their service keys are 1 and 3 respectively. The system has default data configuration for service keys 1 and 3. Each service supports Chinese and English in combination. Normally, there is no need to configure these service keys with the ADD LKINDPOS command. [Default Call Handling] If it is set to "RELESCALL (RELEASE CALL)", an exceptional call will be released during IN service triggering process. If it is set to "CTNUCALL (CONTINUE CALL)", when exception occurs during IN service triggering process, the IN service will not be processed and the call will be connected as an ordinary call instead.

III. Related Commands See Table 12-5 for the commands related to SCP parameter configuration. Table 12-5 List of commands related to SCP parameter configuration Command

Description

ADD SCPPARA

To add SCP parameter

RMV SCPPARA

To remove existing SCP parameter

MOD SCPPARA

To modify existing SCP parameter

LST SCPPARA

To list SCP parameters


12-7


SCP


SMC

GMLC

HLR

MAP/TDM

MAP/TDM

MAP/TDM

MAP/TDM

MSC Server

MSOFTX 3000

ISUP/TDM

H.248,RANAP /IP

BSSAP+/TDM

SGSN


MGW

ISUP/TDM

MGW

IP/TDM

PSTN

(SG)

RANAP/AAL2/ATM

BSSAP/TDM

RNC

BSC

Figure 12-3 Networking of MSOFTX3000 This example is to add a local SCP, which is directly connected to MSOFTX3000 through E1 line. The SCP information is shown in Table 12-6. For the local office information, refer to Table 3-14 in Chapter 3.

12-8



Table 12-6 SCP information table Item

Data

Basic information /

Signaling link

/

WCSU/WC CU/WSGU module number 23



E.164 code

D02302

National network

8613600012

Link set



Intra-module circuit number (E1 number/timeslot number)

Link type

12

2

0

80 (2/16)

64 kbit/s

12.5.2 Configuration Description //Add MTP layer data. ADD N7DSP: DPX=12, DPC="D02302", OPC="CC0004", DPNAME="SCP-12"; ADD N7LKS: LSX=12, ASPX=12, LSNAME="SCP-12"; ADD N7RT: LSX=12, DPX=12, RTNAME="SCP-12"; ADD N7LNK: MN=23, LNKN=2, LNKNAME="SCP-12", LNKTYPE=0,TS=80, LSX=12, SLC=0;

//Add SCCP layer data. ADD SCCPDSP: DPX=12, NI=NAT, DPC="D02302", OPC="CC0004", DPNAME="SCP-12", SHAREFLAG=NONE; ADD

SCCPSSN:

SSNX=15,

NI=NAT,

SSN=CAP,

SPC="CC0004",

OPC="CC0004",

NI=NAT,

SSN=SCMG,

SPC="D02302",

OPC="CC0004",

NI=NAT,

SSN=CAP,

SPC="D02302",

OPC="CC0004",

SSNNAME="MSC-CAP"; ADD

SCCPSSN:

SSNX=16,

SSNNAME="SCP-SCMG"; ADD

SCCPSSN:

SSNX=17,

SSNNAME="SCP-CAP";

ADD SCCPGT: GTX=12, GTNAME="SCP-NUMBER ", NI=NAT, GTI=GT4, NUMPLAN=ISDN, ADDREXP=INTER, ADDR=K'8613600012, RESULTT=LSPC2, SPC="D02302";

//Add SCP data.

ADD

SSPCAPA:

SRVKEY=1,

SSPCAPA=IPRA-1&VOICEBACK-1&SPREC-1&VOICEREC-1&TEXTTOV-1; ADD SCPINFO: SCPADDRIDX=0, SCPADDR=K'8613600012, CAPVER=2, SCFID="1"; ADD SCPPARA: SCPPARAIDX=1, SCPADDRIDX=0, SRVKEY=1, DCH=CTNUCALL;

12-9


Chapter 13 Configuring Data for Interworking with SGSN

Chapter 13 Configuring Data for Interworking with SGSN 13.1 Introduction to the Chapter This chapter describes the data configuration process at MSOFTX3000 for interworking with a serving GPRS support node (SGSN). This chapter contains the following sections: z

Related Concepts

z

Collecting Data for Interworking with SGSN

z

Configuring Data for Interworking with SGSN

z


13.2 Related Concepts 13.2.1 SGSN SGSN implements access control, mobility management, and session management functions of the MS/UE packet domain. In addition, it creates packet data protocol (PDP) context of MS/UE to provide channels for mobile stations to access Internet. For the concepts about MTP and SCCP, refer to Chapter 7 “Configuring Data for Interworking with HLR”.

13.2.2 Networking Between MSOFTX3000 and SGSN MSOFTX3000 and SGSN apply the Gs interface and run in BSSAP+ protocol, which may be based on TDM or IP. In the current networking mode, it is TDM based, as shown in Figure 13-1. TDM TDM 承载 TDM based Gs MSOFTX3000 BSSAP+ SCCP MTP3 MTP2 MTP1

Figure 13-1 Networking and protocols between MSOFTX3000 and SGSN 13-1

SGSN



13.2.3 Parameter Relationship The parameter relationships for interworking between MSOFTX3000 and SGSN are illustrated in Figure 13-2. The solid lines represent the relationships with external entities. The dotted lines represent the relationships between internal commands. SGSN parameters


Signaling network indicator SGSN OPC Peer MSC DPC

[DSP index] [NI] [DPC] [OPC] ADD SCCPDSP

SLC

[NI] [DPC] [OPC] ADD SCCPSSN [NI] [SSN] [SPC] [OPC]

ADD N7LKS [LinkSet Index] [Adjacent Point Index] ADD N7RT [LinkSet Index] [DSP index] [Priority] ADD N7LNK [Link No.] [Start Circuit No.] [LinkSet Index] [Signaling Link Code]

ADD SCCPGT [NI] [GT Address Information] [SPC] ADD SGSNNO

SGSN number

[SGSN NUMBER]

Figure 13-2 Parameter relationship between MSOFTX3000 and SGSN

13-2



13.2.4 General Configuration Procedures The procedures and commands for configuring data for interworking between MSOFTX3000 and SGSN are listed in Table 13-1. Table 13-1 Procedures and commands for configuring data at MSOFTX3000 for interworking with SGSN Procedure

Command

1. Configure MTP 1) Add MTP DSP

ADD N7DSP

2) Add MTP link set

ADD N7LKS

3) Add MTP route

ADD N7RT

4) Add MTP link

ADD N7LNK


ADD SCCPDPC


ADD SCCPSSN

3) Configure SCCP GT

ADD SCCPGT

3. Configure SGSN 1) Configure SGSN number

ADD SGSNNO

2) Configure Gs interface network indicator

MOD MSFP

3) Modify MAP parameter table

MOD MAPACCFG

13.3 Collecting Data for Interworking with SGSN Before configuring data for interworking with SGSN, you need to collect the interfacing data between MSOFTX3000 and the peer SGSN, as shown in Table 13-2. In the shadowy columns are the parameters that must be negotiated between both ends for consistency or of which one end must notify the other end. The other parameters are the internal ones of MSOFTX3000. Table 13-2 Data for interworking with SGSN Item

Data Signaling Point Code

Basic information


E.164 number

/ Signaling link

WCSU module number

Link number

Link set

/

13-3

SLC and SLC sending

Circuit number (E1/timeslot)

Link type



13.4 Configuring Data for Interworking with SGSN 13.4.1 Configuring MTP Data Refer to sections 6.4.2–6.4.5 in Chapter 6 “Configuring Data for Interworking with BSC” to configuration data for the MTP layer. The steps to add MTP links are as follows: 1)


2)


3)


4)



Add a DSP of SCCP (ADD SCCPDSP): Select "NAT (NATIONAL NETWORK)" for the parameter “Network Indicator” of the SCCP DSP to SGSN.

2)

Add SCCP subsystems (ADD SCCPSSN): Add the local Gs subsystem, and add SCMG and Gs subsystems for the remote SGSN. Because the local MSC, VLR, and SCMG subsystems have been configured in the local office information table, use the LST SCCPSSN command to have a check to avoid repeated configuration.

3)

Add SCCP GT (ADD SCCPGT): It is only required to configure ordinary GT. Select "NAT (National Network)" for network indicator, "ISDN (ISDN/TELEPHONY NUMBERING PLAN)" for numbering plan, and enter SGSN number, for example, 8613900123, for GT address information. Set the translation result type to “LSPC1 (SPC+SSN)” and the newly added parameter "SSN" to "Gs".

13.4.3 Configuring SGSN Number I. Background Information None

II. Command ADD SGSNNO

III. Major Parameters [SGSN NUMBER] For this parameter, enter the peer SGSN number in E.164 coding format, for example, 8613900123. 13-4



IV. Related Commands See Table 13-3 for the commands related to SGSN number configuration. Table 13-3 List of commands related to SGSN number configuration Command

Description

ADD SGSNNO

To add SGSN number

RMV SGSNNO

To remove existing SGSN number

LST SGSNNO

To list SGSN numbers

13.4.4 Modifying Mobile Soft Parameter I. Background Information None

II. Command MOD MSFP

III. Major Parameters [Param] For this parameter, select “P106 (GS INTERFACE NETWORK INDICATOR)”. [Value] Set this parameter according to the actual networking mode.

IV. Related Commands See Table 13-4 for the commands related to the configuration of mobile soft parameters. Table 13-4 List of commands related to the configuration of mobile soft parameters Command

Description

MOD MSFP

To modify mobile soft parameter

LST MSFP

To list mobile soft parameters

13.4.5 Modifying MAP Parameter Table I. Background Information Check or modify MAPACCFG (usually, you need not modify the MAP parameter table) to make MAP support the GS interface. 13-5




III. Major Parameters [SUPPORT GS INTERFACE] Set this parameter to "Yes".

IV. Related Commands See Table 13-5 for the commands related to the configuration of MAP parameter table. Table 13-5 List of commands related to the configuration of MAP parameter table Command

Description

MOD MAPACCFG

To modify MAP parameter table

ADD MAPACCFG

To add MAP parameter table

LST MAPACCFG

To list MAP parameter table

13-6




SCP

SMC

GMLC

HLR

MAP/TDM

MAP/TDM

MAP/TDM

MAP/TDM

MSC Server

MSOFTX 3000

ISUP/TDM

H.248,RANAP /IP

BSSAP+/TDM

SGSN


MGW

ISUP/TDM

MGW

IP/TDM

PSTN

(SG)

RANAP/AAL2/ATM

BSSAP/TDM

RNC

BSC

Figure 13-3 Networking of MSOFTX3000 This example is to add a local SGSN, which is directly connected to MSOFTX3000 through E1 line. The SGSN information is shown in Table 13-6. For the local office information, refer to Table 3-14 in Chapter 3.

13-7



Table 13-6 SGSN information table Item

Data

Basic information


NI signaling point

of

/

D02304

National network

86136000 14

E.164 number

Signaling link

WSGU module number

Link set


SLC and SLC sending


Link type

/

23

14

16

0

144 (4/16)

64 kbit/s

13.5.2 Configuration Description //Add MTP layer data. ADD N7DSP: DPX=14, DPC="D02304", OPC="CC0004", DPNAME="SGSN-14"; ADD N7LKS: LSX=14, ASPX=14, LSNAME="SGSN-14"; ADD N7RT: LSX=14, DPX=14, RTNAME="SGSN-14"; ADD N7LNK: MN=23, LNKN=16, LNKNAME="SGSN-14", LNKTYPE=0, TS=144, LSX=14, SLC=0;

//Add SCCP layer data. ADD SCCPDSP: DPX=14, NI=NAT, DPC="D02304", OPC="CC0004", DPNAME="SGSN-14", SHAREFLAG=NONE;

ADD

SCCPSSN:

SSNX=20,

NI=NAT,

SSN=GS,

SPC="CC0004",

OPC="CC0004",

SSN=SCMG,

SPC="D02304",

OPC="CC0004",

SSN=GS,

SPC="D02304",

OPC="CC0004",

SSNNAME="MSC-GS"; ADD

SCCPSSN:

SSNX=21,

NI=NAT,

SSNNAME="SGSN-SCMG"; ADD

SCCPSSN:

SSNX=22,

NI=NAT,

SSNNAME="SGSN-GS";

ADD

SCCPGT:

GTX=14,

GTNAME="SGSN

GT",

NI=NAT,

GTI=GT4,

ADDR=K'8613600014, RESULTT=LSPC1, SSN=GS,SPC="D02304";

//Configure SGSN number. ADD SGSNNO: SGSN=K'8613600014; MOD MSFP: ID=P106, VAL="2"; MOD MAPACCFG: SUPGSIE=YES;

13-8

NUMPLAN=ISDN,


Chapter 14 Configuring Data for Interworking with GMLC

Chapter 14 Configuring Data for Interworking with GMLC 14.1 Introduction to the Chapter This chapter focuses on the data configuration process at MSOFTX3000 for interworking with a gateway mobile location center (GMLC). This chapter contains the following sections: z

Related Concepts

z

Collecting Data for Interworking with GMLC

z

Configuring Data for Interworking with GMLC

z


14.2 Related Concepts 14.2.1 GMLC GMLC implements location service (LCS). An authorized subscriber accesses the mobile network through GMLC and obtains location information of a destination subscriber. Authorized by HLR, GMLC interacts with MSC Server through the Lg interface to complete LCS procedure. GMLC numbers and authorized LCS client IDs are stored in HLR as subscription data, which should also be configured in MSC Server. For concepts about MTP and SCCP, refer to Chapter 7

“Configuring Data for

Interworking with HLR”.

14.2.2 Networking Between MSOFTX3000 and GMLC The MAP protocol is used between MSOFTX3000 and GMLC. The MAP protocol can be based on TDM or IP. By default, it is TDM based, as shown in Figure 14-1.

14-1



TDM承载 TDM based MAP

MSOFTX3000

GMLC

MAP TCAP SCCP MTP3 MTP2 MTP1

Figure 14-1 Networking and protocols between MSOFTX3000 and GMLC

14.2.3 Parameter Relationship The parameter relationships for interworking between MSOFTX3000 and GMLC are illustrated in Figure 14-2.The solid lines represent the relationships with external entities (GMLC) and the dotted lines represent the relationships between internal commands.

14-2

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center GMLC parameter


MSOFTX3000 parameter ADD N7DSP

ADD N7LKS

[DSP index]

[Link Set]

Signaling NI

[Network Indicator]


GMLC OPC

[Destination Point Code] [Original Point Code]

Peer MSC DPC

ADD SCCPDSP

[DSP index]

[Network Indicator]

[Priority]

[DPC]

ADD N7LNK

[OPC] Signaling link code (SLC)

ADD N7RT [Link Set]

[Link No]

ADD SCCPSSN [Network Indicator] [SSN Code] [Signaling Point Code]

[Start Circuit No ] [Link Set] [Signaling Link Code ]

[OPC]

ADD SCCPGT

ADD CLTGMLC

[Network Indicator] [Global Title Address Information] [Signaling Point Code]

[GMLC No.]

ADD ECLLCSCLT

ADD GMLC

[GCI OR LAI] [LCS CLIENT ID]

[GMLC No.]

Local GMLC number

[GMLC CLIENT ID]

[Emergency Call Number]

ADD ESRVCAT [EMR_SRVCI] [SCDN]

Figure 14-2 Parameter relationship between MSOFTX3000 and GMLC

14.2.4 General Configuration Procedures The procedures and commands for configuring data for interworking between MSOFTX3000 and GMLC are listed in Table 14-1 . Table 14-1 Procedure and commands for configuring data at MSOFTX3000 for interworking with GMLC Procedure

Command

1. Configure MTP 1) Add MTP3 DSP

ADD N7DSP

2) Add MTP3 link set

ADD N7LKS

3) Add MTP3 route

ADD N7RT

4) Add MTP3 link

ADD N7LNK

14-3



Procedure

Command


ADD SCCPDSP


ADD SCCPSSN

3) Add SCCP GT to GMLC

ADD SCCPGT

3. Configure LCS data 1) Add GMLC number

ADD GMLC

2) Add client GMLC information

ADD GMLCCLT

3) Add emergency call LCS Client

ADD ECLLCSCLT

4) Add called analysis data (optional)

ADD CNACLD

14.3 Collecting Data for Interworking with GMLC Before configuring data for interworking with GMLC, you need to collect the interfacing data between MSOFTX3000 and the peer GMLC, as shown in Table 14-2. Table 14-2 Data for interworking with GMLC Item

Data

Basic information

Signaling Point Code


E.164 number

Link set

Link number

SLC and SLC sending

/ Signaling link

WCSU module number

/

14-4


Link type



14.4 Configuring Data for Interworking with GMLC 14.4.1 Configuring MTP Data Refer to sections 6.4.2–6.4.5 in Chapter 6 “Configuring Data for Interworking with BSC” to configuration data for the MTP layer. The steps to add MTP links are as follows: 1)


2)


3)


4)



Add a DSP of SCCP (ADD SCCPDSP): Select “NAT (National Network)” for the parameter “Network Indicator”.

2)

Add SCCP subsystems (ADD SCCPSSN): Add SCMG(SCCP Management Subsystem)and GMLC subsystem to the remote GMLC. As the local MSC, VLR, and SCMG subsystems have been configured in the local office information table, use the LST SCCPSSN command to have a check to avoid repeated configuration.

3)

Add SCCP GT (ADD SCCPGT): Select “NAT (National Network)” for NI, “ISDN (ISDN/TELEPHONY NUMBERING PLAN)” for numbering plan, and enter GMLC number for GT address information, for example 8613900128.

14.4.3 Adding GMLC Number I. Background Information A GMLC number must be authorized by the local office. Only the authorized GMLC can invoke LCS requests or receives LCS reports.

II. Command ADD GMLC

III. Major Parameters [GMLC Number] It is an authorized GMLC number.

14-5



IV. Related Commands See Table 14-3 for the commands related to GMLC number configuration. Table 14-3 List of commands related to GMLC number configuration Command

Description

RMV GMLC

To remove an existing GMLC number

LST GMLC

To list the configured GMLC number

14.4.4 Adding Client GMLC Information I. Background Information This command is used to configure the table of corresponding relationships between GMLC authorized clients and GMLC numbers. You can query the corresponding GMLC number at the local office by searching for the client ID. If an LCS request does not contain a GMLC number, MSC can use this table to obtain the GMLC number and return the LCS result to GMLC for related processing.

II. Command ADD GMLCCLT

III. Major Parameters [GMLC Client ID] It is a GMLC client ID, namely the LCS client. Each client ID can correspond to one authorized GMLC number only, and one GMLC can be used by multiple users. Enter parameters here. [GMLC Number] It is a GMLC number, which is already defined in command ADD GMLC. It must be pre-defined in the ADD GMLC command. Enter parameters here.

IV. Related Commands See Table 14-4 for the commands related to the configuration of client GMLC information.

14-6



Table 14-4 List of commands related to the configuration of client GMLC information Command

Description

ADD GMLCCLT

To add client GMLC information

MOD GMLCCLT

To modify client GMLC information

RMV GMLCCLT

To remove client GMLC information

LST GMLCCLT

To list client GMLC information

14.4.5 Adding Emergency Call LCS Client I. Background Information It covers the configuration of the corresponding relationship between authorized LCS Client ID and emergency call numbers. When you initiate an emergency call in a certain service area, your location information will be reported to the designated LCS Client.

II. Command ADD ECLLCSCLT

Important Note: You can use this command to add LCS Client only for the emergency call numbers that can originate emergency call location service. The GMLC number and LCS Client ID configured at the local MSC should be consistent with those defined by the operator who provides the location service.

III. Major Parameters [Emergency Call Number] It is the called number in an emergency call. If LCS is invoked in an emergency call, when the location procedure completes, the system will report the location information to GMLC. Enter parameters here. [GCI OR LAI] It refers to global cell identification (GCI) or location area identity (LAI). It must pre-defined in the command ADD LAIGCI. [LCS Client ID] It specifies the ID of the LCS client. It has been defined in the command ADD GMLCCLT, that is “GMLC CLIENT ID”. Enter parameters here.

14-7



IV. Related Commands See Table 14-5 for the commands related to the configuration of GMLC numbers for emergency calls. Table 14-5 List of commands related to the configuration of GMLC numbers for emergency calls Command

Description

ADD ECLLCSCLT

To add a LCS Client information for emergency calls

MOD ECLLCSCLT

To modify the attributes of the existing LCS Client information for emergency calls

RMV ECLLCSCLT

To remove an existing LCS Client information for emergency call

LST ECLLCSCLT

To list the configured LCS Client information for emergency calls

14.4.6 Adding Called Analysis Data (Optional) I. Background Information None.

II. Command ADD CNACLD

III. Major Parameters [Call Prefix] You need to configure the call prefix that the emergency call number corresponds to. It is associated with the emergency call number in the ADD ECLLCSCLT command. [Emergency Call Observe Flag] The flag indicates whether an LCS procedure has been invoked to locate a subscriber initiating an emergency call. For other description, refer to Chapter 15 “Configuring Number Analysis Data”.

14-8




SCP

SMC

GMLC

HLR

MAP/TDM

MAP/TDM

MAP/TDM

MAP/TDM

MSC Server

MSOFTX 3000

ISUP/TDM

H.248,RANAP /IP

BSSAP+/TDM

SGSN


MGW

MGW (SG)

IP/TDM

RANAP/AAL2/ATM

ISUP/TDM

PSTN

BSSAP/TDM

RNC

BSC

Figure 14-3 Networking of MSOFTX3000 This example is to add a local GMLC, which is interconnected with MSOFTX3000 through E1 cable. The information about GMLC is shown in Table 14-6. For the information of the local office, refer to Table 3-14 in Chapter 3.

14-9



Table 14-6 GMLC information table Item

Data

Basic information / Signaling link



E.164 number

D02305

National

8613600015

WSGU module No.

Link set

Intra-module link No.

23

15

17

Intra-module E1 timeslot No.

Link type

176 (5/16)

64 kbit/s

SLC and sending

/

SLC

0

14.5.2 Configuration Description //Add MTP layer data. ADD N7DSP: DPX=15, DPC="D02305", OPC="CC0004", DPNAME="GMLC-15"; ADD N7LKS: LSX=15, ASPX=15, LSNAME="GMLC-15"; ADD N7RT: LSX=15, DPX=15, RTNAME="GMLC-15"; ADD N7LNK: MN=23, LNKN=17, LNKNAME="GMLC-15", LNKTYPE=0, TS=176, LSX=15, SLC=0;

//Add SCCP layer data. ADD SCCPDSP: DPX=15, NI=NAT, DPC="D02305", OPC="CC0004", DPNAME="GMLC-15", SHAREFLAG=NONE;

ADD

SCCPSSN:

SSNX=23,

NI=NAT,

SSN=SCMG,

SPC="D02305",

OPC="CC0004",

NI=NAT,

SSN=GMLC,

SPC="D02305",

OPC="CC0004",

SSNNAME="GMLC-SCMG"; ADD

SCCPSSN:

SSNX=24,

SSNNAME="GMLC-GMLC";

ADD

SCCPGT:

GTX=15,

GTNAME="GMLC

GT",

NI=NAT,

GTI=GT4,

NUMPLAN=ISDN,


//Add LCS data. ADD GMLC: GMLC=K'8613600015; ADD GMLCCLT: CLTID=K'0, GMLC=K'8613600015;

ADD ECLLCSCLT: DN=K'113, GCI="460000003", CLTID=K'0; ADD CNACLD: P=1, PFX=K'113, CSTP=BASE, CSA=lc, MINL=3, MAXL=6, ECOS=YES;

14-10


Chapter 15 Configuring Number Analysis Data

Chapter 15 Configuring Number Analysis Data 15.1 Related Concepts 15.1.1 Call Source, Dialed Number Set, Route Selection Code I. Call Source and Call Source Code Call source refers to a subscriber or incoming trunk originating a call. Each call source has an integral number, called call source code. For the MSOFTX3000, incoming calls may come from A interface, Iu interface and incoming trunk. Analysis of call source refers to searching the call source code according to the physical port of the incoming equipment. The analysis process is as follows: 1)

If an incoming call is connected to the MSOFTX3000 through A or Iu interface (that is, the call is originated by a mobile subscriber in the local office), the MSOFTX3000 will check the associated local area identification (LAI) and cell global identification (CGI) based on BSC/RNC DPC to obtain the call source code.

2)

If an incoming call is connected to the MSOFTX3000 through the trunk (that is, the call is originated by a PSTN subscriber or subscriber of other mobile offices), the MSOFTX3000 will check the trunk group data to obtain the call source code.

The call source code reflects the call source, based on which different processing methods are decided.

II. Call Prefix Call prefix is a number segment cut from a called number; the cut starts with the first digit of the called number. Its length is not longer than the called number. The MSOFTX3000 adopts the principle of the longest number matching while analyzing the called numbers. According to this principle, the call prefix that is most similar to the called number will be found among all the call prefixes, and it will act as a basis to determine the attributes such as service type and route selection code. For example, if the configured "Call Prefixes" include 139 and 13900278, while the called number is 13900278310, the system will match the number with the call prefix 13900278 automatically.

III. Dialed Number Set Dialed number set (DN set) is a set of dialed numbers/prefixes. It is associated with the called number prefix. By introducing the dialed number set, the system can analyze an identical called prefix differently. It has developed into a flexible means to analyze called prefixes. One DN set may correspond to multiple call sources, while one call source should correspond only to one DN set. 15-1



IV. Route Selection Source Code and Route Selection Code The route selection source code identifies different outgoing routing strategies of different call sources. The route selection source code corresponds to the call source. The local subscribers with different outgoing strategies can be defined as different call sources and assigned with different route selection source codes. A route selection code indicates a routing strategy for calls with a certain prefix. It will be used together with the route selection source code to select the outgoing route during route analysis. The route selection source code is related to the calling party, while the route selection code is related to the called party.

V. Failure Source Code and Failure Processing The failure source code numbers different processing methods for the connection failure of calls from different call sources. Different causes may correspond to different connection failure processing methods, such as route reselection, signal tone playing, or triggering NCSIDP4.

VI. Wildcards Usually, the MSOFTX3000 matches numbers in the maximum prefix mode. It queries related number analysis tables and performs analyzing and processing according to the querying results. In addition, the MSOFTX3000 uses wildcards to fulfill call processing. Most popular wildcards used in number analysis are "eeeeeeee" and "65534". The former is a call prefix, representing any call prefix; the latter is the wildcard of call source, representing all call sources. For call source, number type and service attribute, usually the wildcard is 254. The matching of wildcards is in the following way: z

Query the corresponding record by specific field (such as prefix and call source code) first.

z

If no matched record is found, replace fields that have wildcards with wildcards in sequence.

z

Re-query.

For example, in Table 15-1 (with two records), the MSOFTX3000 queries the table with call source and prefix. Table 15-1 Wildcard matching Call source

Call prefix

65534

1390

2

13

15-2



According to the wildcard matching princilple, for a call whose call source is 2 and call prefix is 1390000, the MSOFTX3000 will match the second record without using a wildcard for processing the call. This is because the second record has specific fields for call source and call prefix. For a call whose call source is 0 and call prefix is 1390000, the MSOFTX3000 can match neither record in the table by using a specific field. When “Call source” is replaced with a wildcard, the MSOFTX3000 matches the first record.

15.1.2 Secondary Number Analysis If a number is changed during the number analysis process, the secondary number analysis is necessary in order to determine the outgoing route. The secondary number analysis can be done in the following two ways: 1)

If a called number is an MSISDN after analysis, the MSOFTX3000 will obtain the route information of the called party from HLR. If HLR returns a roaming number or forwarded-to number, the MSOFTX3000 will conduct a second number analysis (that is, it will analyze the call prefix again according to the number that HLR returned) to find the outgoing route.

2)

A called number is converted through the prefix processing process. If the processing type is "reanalysis” (conduct number analysis again), the MSOFTX3000 will also carry out the secondary number analysis, that is, to analyze the converted number with the call prefix analysis table to find the outgoing route.

15.1.3 Number Conversion The MSOFTX3000 supports 32 kinds of number conversion. Refer to “Configuring Number Conversion Data” in this chapter for details.

15.1.4 Service Check Check whether a calling subscriber is authorized to make the corresponding calls. You can set the service check type, check mode, and conversation duration restriction.

15.1.5 EARLY ACM During the call connection, a call may be disconnected as the previous office has not received an address complete message (ACM) within a certain duration due to long time of signaling transmission within the call. In the MSOFTX3000, this can be avoided: Upon receiving Initial Address Message (IAM) from the previous office, the local office confirms that the called number is received completly and promptly sends ACM back to the previous office before the response of called party. This is called the EARLY ACM procedure.

15-3



This function is generally realized through Call Control Block (CCB). Upon confirming that the address is complete, CCB sends Alerting information to the trunk side, which in turn sends ACM to the peer office so as to start the EARLY ACM procedure.

15.1.6 Forwarded-to Number, Original Called Number, Connected Number A forwarded-to number: When the local office is the terminating office, if a call is forwarded at the local office, the number to which the call is forwarded is called the forwarded-to number at the local office. Original called number: When a call is forwarded for once or times, the first called number is called the original called number. Connected number: When a call is originated from the local office (originating office) and is forwarded at terminating office B to office C, the final called number sent by terminating office B to the local office is the connected number. The format control of the connected number is accomplished at the call originating office, while that of the forwarded-to number is accomplished only at the office where the forwarding is initiated. If the calling party has subscribed to the connected line ddentification presentation (CoLP) service, the format control of the received forwarded-to number may be accomplished at the call terminating office, and the number is sent to the call originating office in the form of a connected number. At the call originating office, the connected number received can also be converted so as to meet the requirement of the calling line identification presentation (CLIP) service, as shown in Figure 15-1. Call originating office

Connected number

Call terminating office

Format control of connected number

Forwarded-to number

Call forwarding office

Format control of forwarded-to number

Figure 15-1 Procedures for number format control in a forwarding call

15.2 Procedures of Number Analysis Processing The following introduces the number analysis processing of the MSOFTX3000 in a normal call procedure. Number analysis processing includes three parts: incoming number pretreatment, number analysis and outgoing number preprocessing, as shown in Figure 15-2.

15-4



CM

PRA BICC MAP SSF Forwarded-to side

Outgoing Number Preprocessing

TK

Internal Number Analysis

TUP

Incoming Number Preprocessing

ISUP

ISUP TUP TK PRA BICC

Figure 15-2 Processing of number analysis

Note: z

Outgoing number processing will be used for outgoing trunk.

z

There may be some number processing procedures before and after number analysis. For example, there may be a called number preprocessing procedure before number analysis. These procedures will be explained later.

15.2.1 Incoming Number Pretreatment During incoming number pretreatment, numbers entered throguh various interfaces will be initially analyzed and converted to implement the following functions: z

Normalize the format of incoming calls of different sources or modify the DN set called.

Incoming number processing is not invoked merely by certain incoming trunks. Therefore, it is meant for incoming numbers in the wide sense. It is required before every number analysis, for example, the processing of the number coming from the CM side, the processing before number analysis when MAP retrieves the roaming number, the processing before number analysis when MAP retrieves the redirecting number, and the processing before analysis of numbers incoming from the trunk side. z

Ensure the completeness of numbers entered

This is to adapt to channel associated signaling such as R2, implementing receive-number delay in the incoming number processing part by office direction or call prefix.

15-5



15.2.2 Number Analysis After incoming number pretreatment or other number pretreatment is the main procedure of the called number analysis. This procedure processes various results of number analysis in different modes: z

For a local MSRN, the MSOFTX3000 pages the called mobile subscriber.

z

For an ordinary MSISDN, the MSOFTX3000 requests the roaming number of the subscriber from HLR.

z

For an ordinary PSTN or an MSRN of other offices, the MSOFTX3000 performs routing and leads the number out of the office.

15.2.3 Outgoing Number Preprocessing Outgoing number processing is done during trunk outgoing according to corresponding trunk group numbers, making the format of the outgoing number conformant with inter-office number transfer specifications. Outgoing number processing does not affect the number format of the exchange and bills. In this respect, it differs from incoming number processing and number conversion of number analysis. The type of outgoing number processing is relatively simple. Outgoing number processing is to normalize numbers. Number conversion can be done either with the attributes of the specified number or according to the specific data configuration.

15.3 Configuration Procedures 15.3.1 Overview of Configuration Procedures This section introduces the configuration of data tables in ordinary call flow. The configuration of IN call processing data is not included here. Based on the number analysis of the MSOFTX3000 introduced above, the data configuration of number analysis can be divided into five parts: preset data for number analysis, preprocessing data of incoming numbers, outgoing routing data of number analysis, preprocessing data of outgoing numbers, and other number data.

15.3.2 Procedures for Configuring Number Analysis Preset Data Configuration of number analysis preset data comprises call source configuration, called number preprocessing and number conversion configuration. The procedures are shown in Figure 15-3.

15-6



Call source configuration

Called number pre-processing

Number convesion configuration

End

Figure 15-3 Procedures of number analysis preset data configuration Call source configuration is used to designate call sources to various trunk groups and LAs and cells. Called number analysis is to analyze called numbers according to call sources, address attributes of called numbers and the roaming type of callers, and determines whether to perform called number conversion and whether to change the DN set. Number conversion configuration is to set number analysis routing and determine the mode of number conversion in the follow-up number analysis. Number conversion configuration can be referenced through number conversion indexes.

Note: Called number preprocessing can be replaced with incoming number pretreatment (the called number pretreatment table will be introduced in later sections). The called number preprocessing table may not be configured. The original called number preprocessing table may not be used during incoming processing. You can close the original called number preprocessing table with software parameters, and move the contents of the table to the incoming number pretreatment table. Currently, it is recommended to replace the called number preprocessing table with the incoming number pretreatment table. The configuration of the called number preprocessing table is no longer introduced in this manual.

15.3.3 Procedures for Configuring Incoming Number Pretreatment Data The configuration of incoming number pretreatment data comprises incoming calling number associated process data configuration, incoming original called number correlation processing data configuration and incoming number pretreatment data configuration. The corresponding data configuration tables are incoming calling number associated process table, incoming original called number correlation processing table and incoming number pretreatment table. The procedures are shown in Figure 15-4.

15-7


Configure Incoming Calling Number Correlation Processing Data


Configure Incoming Original Called Number Correlation Processing Data

Configure Incoming Number Preprocessing Data

Figure 15-4 Procedures of incoming number pretreatment data configuration During the above procedures, the purpose of incoming number pretreatment data configuration is to normalize called numbers of incoming calls (from trunks) and Mobile-Originated (MO) calls, MSRNs or forwarded-to numbers transmitted by MAP signaling, and called numbers changed in IN procedure. In this way, the format of input numbers can meet the relevant internal specifications of the MSOFTX3000 so as to facilitate the unified number analysis of the system. Besides, the configuration also helps to realize the receive-number delay according to a certain call prefix, and the flexible number conversion processing over incoming numbers according to calling/called numbers and original called numbers.

15.3.4 Procedures for Configuring Number Analysis and Routing Data The configuration comprises the parts as shown in Figure 15-5.

15-8



Configure call prefix data

Enhanced route processing?

Y

Check call authority/original called number corelation?

Y

Configure enhanced route processing data

Check call authority/ configure original call corelation processing data

Configure call authority check data

Configure service check data

Calling number analysis?

Need number initial processing or not?

Y

Y

Configure calling number analysis data

Configure calling number attribute processing data

Configure calling number attribute analysis data

Configure special DN processing data

Configure failure processing data

End

Figure 15-5 Procedures of number analysis and routing data configuration The role of each part of data configuration is as follows: z

Call prefix data configuration is not only the core of number analysis and routing data configuration, but also that of entire number analysis data configuration. This part completes the functions of call analysis and routing.

z

Enhanced route processing data is used to select different outgoing route for the same call prefix, with different call types or different number length.

z

Call authority check data is used to set that a certain class of subscribers is only allowed to dial specified numbers, or that some subscribers are not allowed to dial certain numbers. It is also used to play announcements to the caller when the call is forwarded in the local office. 15-9



Service check data is used to check whether the caller has the corresponding call authority.

z

Calling number analysis, calling feature analysis and calling feature processing help to normalize the calling numbers of incoming calls from trunks, or to conduct various processing over different calling parties who dial the same call prefix (for example, to select different routes according to calling features). Calling number analysis is used to process information such as calling numbers. Calling subscriber attribute analysis is used for special processing when the caller has some special serivce attributes (for example, whether the subscriber has subscribed to forwarding and service barring services). Calling subscriber attribute processing is used to map a subscriber’s special service attributes respectively to a series of keywords, which form a keyword–calling feature index. This index corresponds to the calling feature index in the calling feature analysis table. The MSOFTX3000 searches the calling feature analysis table through this index and performs special follow-up processing of calls in the call subscriber attribute analysis.

z

DN processing helps to conduct failure processing over the call in which the related call prefix is dialed, announcement playing or to reanalyze numbers.

z

Failure processing data configuration helps to define the processing modes when both call authority check and DN processing are failed.

15.3.5 Procedures for Configuring Outgoing Number Preprocessing Data Outgoing number processing is done during trunk outgoing according to corresponding trunk group numbers, making the format of the outgoing number conformant with inter-office number transfer specifications. Outgoing number processing does not affect the number format of the exchange and bills. In this respect, it differs from incoming number processing and number conversion of number analysis. The type of outgoing number processing is relatively simple. Outgoing number processing is to normalize numbers. Number conversion can be done either with the attributes of the specified number or according to the specific data configuration. Outgoing number processing is implemented in three processes. Number conversion is performed to the sent calling number and called number according to the calling number and the original called number. Data configuration is shown in Figure 15-6.

15-10


Configure Outgoing Calling Number Correlation Processing Data


Configure Outgoing Original Called Number Correlation Processing Data

Configure Outgoing Number Preprocessing Data

Figure 15-6 Procedures of outgoing number preprocessing data configuration The role of each part of data configuration is as follows: Outgoing calling number correlation processing data are used to convert the transmitted calling/called numbers and original called numbers or redesignate their formats according to calling number prefixes and their related attributes. Correlation processing data of the outgoing original called number is used to convert calling/called numbers and original called numbers or redesignate their formats according to original called prefixes and their related attributes. Outgoing number preprocessing data are used to convert calling/called numbers and original called numbers or redesignate their formats according to call sources, outgoing trunks, called prefixes and related attributes.

Note: Original called correlation parameters and data are configured only when a call is forwarded, requiring number conversion to other numbers during the call according to the original called number or to the original called number.

Apart from number conversion to outgoing numbers through the configuration of outgoing number preprocessing data introduced above, you can also convert numbers on certain trunk groups after trunk routing, by configuring trunk group bearer data. But because that outgoing number preprocessing is more powerful than trunk group bearer data configuration, it is recommended to use outgoing number preprocessing. Here, we introduce trunk group bearer data configuration in brief. If you need to convert calling/caller number according to trunk group number and call prefix, refer to Figure 15-7.

15-11



Configure trunk group bearer data

Configure trunk group bearer index data

End

Figure 15-7 Procedures for trunk group bearer data configuration

15.3.6 Other Number Data Configurations I. Background Information Besides its powerful number normalization functions based on number analysis, the system offers other number conversion functions, for example, caller identification processing data configuration, MAP interface number processing data configuration, auxiliary number processing data configuration and bill processing data configuration.

II. Format Normalization of Caller Identification If the MSRN analysis result returned from the HLR shows that the called party is a local office subscriber, the system will initiate the call. For those who have subscribed to CLIP, the system will call them with the calling number presented. The system can also control the formats of calling numbers to meet the requirements of CLIP service. To realize this function, CLIP processing data should be configured. Tables related to the configuration include CLIP Processing table and CLIP Called Correlation table, both of which are associated through parameter [Callee Number Correlation Index]. In general, only CLIP processing data needs to be configured. If calling number conversion is associated with called subscriber attribute, CLIP called correlation processing data should be configured. Figure 15-8 shows the specific sequence. Configure CLIP Called Correlation Processing Data

Configure CLIP Preprocessing Processing Data Data

Figure 15-8 Procedures of calling number correlation processing data configuration

15-12



III. Forwarded-to/Connected Number Normalization When the call originated at the local office is forwarded at the terminating office, the local office can convert the connected number returned and send it back to the calling subscriber who has subscribed to CoLP service. When the call is forwarded at the local office, the local office can control the format of the forwarded-to number to be returned and send it back to the call originating office. Normalization (including number conversionation and number attribute designation) of forwarded-to/connected numbers can be realized through the configuration of auxiliary number conversion data.

IV. Normalization of MAP Interface Number MAP interface number processing data are used to normalize the format of the called number contained in the Send Routing Information (SRI) message when a mobile subscriber is called and the system sends SRI message to the HLR of this subscriber.

V. Control of Bill Number Format (ADD BILLPROC) The system can convert the calling number, called number and third party number in bills and limit their length according to call source, bill type and number prefix.

15.4 Configuring Preset Data Before Number Analysis 15.4.1 Adding Call Source I. Background Information This command is used to set a call source code according to calling party attributes. Cells or trunks having the same calling party call attributes are classified into the same call source. Corresponding call source codes must be added before configuring number analysis or route analysis.

II. Command ADD CALLSRC

III. Major Parameters [Call Source] It is also called [Call Source Code]. Call source is referenced in the LAI/CGI table, route analysis data, and trunk group data. Different call source codes must be set according to different call attributes of the caller. These attributes include the DN set, outgoing route selection for calls to the same prefix, failure processing mode, and number pre-analysis mode. It is recommended to group the local office subscribers and trunk groups without special requirements to the same call source.

15-13



The call source code set here will be referenced in data tables such as SS7 trunk group data (ADD N7TG) and LAI/CGI information (ADD LAIGCI). [Prereceive Number Digits] Start the number analysis after "N" digits of the number are received. [DnSet] Dialed number set (DN set) is used to categorize subscribers uniformly according to different understandings of the called number (or call prefix). It is numbered from 0. Set one DN set for one office usually. [Route Selection Source Code] The code is used to classify route selection methods of subscribers of this call source. The data is cited during route analysis. Callers with different call attributes have different route selection source codes. Suppose the subscribers of two call sources belonging to the same DN set dial the same outgoing prefix of the DN set. If the route selection methods are different, different route selection source codes can be allocated to the two call sources. Usually, route selection source code and call source code are the same. [Fail Source Code] The code is used to classify call sources according to the failure processing method and cited by the failure processing table. [Intelligent Number Local ACode Index] If Overlay mode is not adopted for the outgoing IN calls at the local office, this parameter is set to "255", the default value. If Overlay mode is adopted for the outgoing of IN calls at the local office, the value set for this parameter must be consistent with that set for [Intelligent Number Area Index] in PPS Subscriber Number Segment table so as to query this table for IN call processing during the number analysis. Before configuring this parameter, make sure that the index has been defined in PPS Subscriber Number Segment table. For details, refer to Chapter 17 “Configuring IN Service Data”. [Toll Area Code] The toll area code of the area where the related call source is located. If an MSC is in charge of multiple areas, calling numbers from different call sources can be differentiated through the setting of this parameter. If the home MSC covers one area only, the value of the parameter is the area code. When the MSC triggers the IN service, the value of this parameter will be sent to the SCP as "Location Number". Therefore, any setting error may affect the normal operation of IN service. Values set for this parameter must contain no toll area code prefixes. [Receive_Number Delay Value (0.1 Second)] If the office direction that the call source corresponds to is not the channel associated signaling office direction, this parameter need not be configured. When the peer office 15-14



communicates with this office through channel associated signaling, this parameter must be set in the corresponding call source data of the peer office so as to ensure the integrity of numbers received.

Note: The maximum value of call source code depends on the set value for the call source code table in the maximum tuple number table.

IV. Related Commands See Table 15-2 for the commands related to the configuration of call source code. Table 15-2 List of commands related to the configuration of call source code Command

Description

LST CALLSRC

To list call source code

ADD CALLSRC

To add call source code

MOD CALLSRC

To modify call source code

RMV CALLSRC

To remove call source code

15.4.2 Configuring Number Conversion Data I. Background Information This command is used to add records to Number Change table which defines various types of transformation modes performed by the MSOFTX3000 over numbers. Before converting a number, the MSOFTX3000 queries this table according to the number conversion index in other data tables so as to obtain the specific conversion mode.

II. Command ADD DNC

III. Major Parameters [Number Conversion Index] It serves as the index identifying records in Number Change table. Other data tables cite corresponding records in Number Conversion table through this parameter. [Number Conversion Type]

15-15



There are 32 types of conversions in this parameter. Therefore, configurations of subsequent parameters vary with the conversion modes selected for this parameter, as shown in Table 15-3: Table 15-3 Correspondence between number conversion type and parameter setting Number Conversion Type

Designated Chars

Conversion Start Position

Number Conversion Length

New Number

Other Conversion Number Source

No Conversion Insert number at designated position Insert after number end

⊕

the

⊕

⊕

⊕

⊕

Insert number after designated character

⊕

⊕

⊕

Insert number before designated character

⊕

⊕

⊕

Delete All Delete number in positive sequence according to designated position

⊕

⊕

Delete number in positive sequence according to designated character (Designated character included)

⊕

⊕

Delete number in positive sequence according to designated character (Designated character excluded)

⊕

⊕

Delete number in inverted sequence according to designated position

⊕

⊕

15-16

New Number Address Nature


Number Conversion Type

Designated Chars




Delete number in inverted sequence according to designated character (Designated character included)

⊕

⊕

Delete number in inverted sequence according to designated character (Designated character excluded)

⊕

⊕

Change All Change number in positive sequence according to designated position

⊕

New Number


⊕

⊕

⊕

⊕

⊕

Change number in positive sequence according to designated character (Designated character included)

⊕

⊕

⊕

⊕

Change number in positive sequence according to designated character (Designated character excluded)

⊕

⊕

⊕

⊕

⊕

⊕

⊕

⊕

⊕

⊕

Change number in inverted sequence according to designated position Change number in inverted sequence according to designated character (Designated character included)

⊕

⊕

15-17



Number Conversion Type Change number in inverted sequence according to designated character (Designated character excluded)

Designated Chars


⊕

Extract and delete number in positive sequence according to designated position



⊕

⊕

⊕

Extract and delete number in positive sequence according to designated character (Designated character included)

⊕

⊕

Extract and delete number in positive sequence according to designated character (Designated character excluded)

⊕

⊕

Extract and delete number in inverted sequence according to designated position

⊕

⊕

Extract and delete number in inverted sequence according to designated character (Designated character included)

⊕

⊕

Extract and delete number in inverted sequence according to designated character (Designated character excluded)

⊕

⊕

15-18

New Number

⊕


⊕



Number Conversion Type

Designated Chars

Extract but not delete number in positive sequence according to designated position


⊕



⊕

⊕

Extract but not delete number in positive sequence according to designated character (Designated character excluded)

⊕

⊕

⊕



⊕

Extract but not delete number in positive sequence according to designated character (Designated character included)

Extract but not delete number in inverted sequence according to designated position

New Number

⊕

Extract but not delete number in inverted sequence according to designated character (Designated character included)

⊕

⊕

Extract but not delete number in inverted sequence according to designated character (Designated character excluded)

⊕

⊕

Change number address attribute

⊕

[Designated Chars Length], [Designated Chars]

15-19



They are used together to determine the conversion (extracting number in positive/inverted sequence, changing number in inverted sequence, etc.) of numbers of certain length containing the designated character string. For example, when a number contains "2xxx", to realize the "Insert number after designated character" function, set [Designated Chars Length] to "4" and [Designated Chars] to "2", and enter the value of [New Number]. In this way, the designated new number can be added to the original number after the character string "2xxx". [Conversion Start Position] It is used to set the start position (counting from position 0 of the number) of the number conversion. [Number Conversion Length] If the designated character string has been given, the length is calculated starting from the first digit after the designated character string. For example, if you need to delete four digits starting from the second digit, you can set [Number Conversion Length] as 4. [New Number] Number after change. [New Number Priority Flag] It sets the priority of the new number generated from the conversion. During the conversion, there may be more than one conversion sources available for the conversion of the same number. Therefore, it is required to determine the sequence of conversions over this number based on these conversion sources. By default, the priority of other sources is higher than the current one. To set higher priority for the current conversion, set this parameter to "True". [Other Conversion Number Source] It helps to apply the strings cut from other numbers to the current number conversion, so as to accomplish the insertion, deletion of substrings to or from the current number and the modification of this number in positive/inverted sequence of the designated position. Through this parameter, the number processing capability of the system has been enhanced, the conversions for numbers in CAP interface signaling can be accomplished according to several number conversion sources. [New Number Address Nature] This parameter is valid only when [Number Conversion Type] is set to "Change number address attribute". When it is valid, you can change the number address attribute without changing number contents.

15-20



Note: Number Change table must be first defined according to the principle of “referenced contents first defined," because it may be invoked in every process of number analysis. It is hard to make an arrangement for the MSOFTX3000 to perform various types of number conversion in sequence. You can add records for corresponding types of number conversion before configuring data of new types of number conversion. When the parameter “Number Conversion Index” is set to "0" by default, no conversion will be conducted. That is, the current number cannot be modified or deleted.

Additional remarks: The MSOFTX3000 can convert calling number, called number and original called number, and number attributes for different stages of a call (incoming stage/outgoing stage). It can convert outgoing forwarded-to numbers and connected numbers. It can convert the CLIP format. It supports number format conversion for the CAP signaling interface. In this way, the system provides flexible conversion of various types of number and number attributes: z

Extract substring from a number; add substring extracted from other number to the suffix of calling/called number.

z

Process a number whose length is not specified; add substring to the end of a number whose length is not specified or replace this number with another number.

z

Support the insertion, deletion (by inverted/positive sequence), modification (by inverted/positive sequence), and extraction (by inverted/positive sequence) of numbers according to the designated character.

z

Support the insertion, deletion (by inverted/positive sequence), modification (by inverted/positive sequence) and extraction (in inverted/positive sequence) according to the designated position.

z

Extract substring from calling/called number according to trunk group type (TUP/ISUP), called number type, original called number type and calling subscriber type.

z

Add the saved substring to a number according to trunk type (TUP/ISUP), called number type (local/foreign/simulation network and PSTN) and calling subscriber type (local/foreign/simulation network and PSTN) when sending calling/called numbers.

IV. Related Commands See Table 15-4 for the commands related to the number conversion.

15-21



Table 15-4 List of commands related to number conversion Command

Description

LST DNC

To list number conversion

ADD DNC

To add number conversion

MOD DNC

To modify attributes of number conversion

RMV DNC

To remove number conversion

15.5 Configuring Incoming Call Number Preprocessing Data 15.5.1 Configuring Incoming Calling Number Associated Process Data I. Background Information This command is used to add records to Incoming Calling Number Associated Process table, which sets the conversions of calling numbers, called numbers and original called numbers according to calling numbers and their attributes related. The table also contains the information of receive-number delay interval and new DN set. Upon obtaining the "Calling Number Associated Process Index" from Incoming Number Pretreatment table, the MSOFTX3000 queries Incoming Calling Number Assicaited Process table according to this index, "Calling Subscriber Prefix", "Calling Subscriber Type", "Calling Number Address Attribute", and "Calling Number Max. Length". Then the MSOFTX3000 obtains the conversion indexes of calling/called/original called numbers, and normalizes these numbers according to the conversion indexes obtained. If the receive-number delay interval has been set in Incoming Calling Number Assicaited Process table, the MSOFTX3000 will not start incoming number pretreatment procedures until the complete number has been received.

II. Command ADD INCLRIDX

III. Major Parameters [Calling Number Associated Process Index] It is used to identify a calling number correlation processing record. Values set for this parameter referenced in Incoming Number Pretreatment table must be defined in Incoming Calling Number Assicaited Process table; that is, there should be corresponding records of these values. [Calling Subscriber Prefix], [Calling Subscriber Type], [Calling Number Address Attribute], [Calling Number Max. Length]

15-22



They determine the relevant attributes of calling number. The MSOFTX3000 queries Incoming Number Pretreatment table and obtains the "Calling Number Associated Process Index", then queries Incoming Calling Number Assicaited Process table according to the index and the relevant attributes of calling subscriber who originates the call. Therefore, the corresponding number can be converted. [Calling Number Conversion Index] It is set only when conversions are to be conducted over the calling number according to calling features. It is associated with [Number Conversion Index] in Number Change table so as to set the conversion index of the calling number determined according to calling features. [Called Number Conversion Index] This parameter is specified when it is required to convert the called number according to calling feature in the system. This parameter is associated with [Number Conversion Index] in Number Change table so as to set the index of the conversion (determined by calling feature mentioned above) to be conducted over the called number. [Original Called Number Conversion Index] It is specified when the call is forwarded and conversion is to convert the original called number according to calling feature. It is associated with [Number Conversion Index] in Number Change table so as to realize the conversion of the original called number. [Receive-Number Delay Interval] It determines whether to conduct receive-number delay processing over the call whose calling number contains the prefix related. The setting of this parameter is the same as that of [Receive-Number Delay Interval] in Call Source table. [New Number Initial Set] This parameter is used to specify the DN set related to current call processing when it is required to process the call in different DN sets.

Note: z

Incoming Calling Number Assicaited Process table serves as an auxiliary table of Incoming Number Pretreatment table. It is configured only when the preprocessing of the incoming number is associated with the calling feature.

z

The MSOFTX3000 conducts receive-number delay processing once at most. If the processing has been accomplished in call source analysis, the system will set "Receive-Number Delay Processing Flag" as "Yes". In this case, even when [Receive-Number Delay Interval] is set to "Yes" during the subsequent table-query procedures, the receive-number delay processing will not be conducted.

15-23



IV. Related Commands See Table 15-5 for the commands related to incoming calling number correlation data. Table 15-5 List of commands related to incoming calling number correlation data Command

Description

LST INCLRIDX

To list incoming calling number correlation

ADD INCLRIDX

To add incoming calling number correlation

MOD INCLRIDX

To modify incoming calling number correlation

RMV INCLRIDX

To remove incoming calling number correlation

15.5.2 Configuring Correlation Processing Data of Incoming Original Called Number I. Background Information This command is executed to add records to Incoming Original Called Number Correlation Processing table. This table is used to set the conversions performed over calling/called/original called numbers according to original called number and its attributes related, and to define new DN set. The MSOFTX3000 obtains the [Original Called Number Associated Process Index] from Incoming Number Pretreatment table. And according to this index, the original called prefix, the original called number address nature, and the original called number maximum

length,

the

MSOFTX3000

obtains

the

conversion

indexes

of

calling/called/original called numbers from Incoming Original Called Number Correlation Processing table. Based on the conversion indexes, the MSOFTX3000 normalizes calling/called/original called numbers accordingly.

II. Command ADD INORICLDIDX

III. Major Parameters [Original Called Number Associated Process Index] It is used to identify an original called correlation processing record. All original called number associated process indexes referenced in Incoming Number Pretreatment table must be defined in Incoming Original Called Number Correlation Processing table; that is, each index must correspond to a record in this table. [Original Called Prefix], [Original Called Number Address Nature], [Original Called Number Maximum Length]

15-24



They are used to specify the relevant attributes of the original called number. The MSOFTX3000 obtains original called number associated process index from Incoming Number Pretreatment table, then queries Incoming Original Called Number Correlation Processing table according to the relevant attributes of the original called party. In this way, the MSOFTX3000 can convert calling/called/original called numbers involved in current call according to the relevant attributes of the original called party. [Calling Number Conversion Index] It is associated with [Number Conversion Index] in Number Change table so as to specify the index of the conversion to the calling number. [Called Number Conversion Index] It is associated with [Number Conversion Index] in Number Change table so as to specify the index of the conversion to the called number. [Original Called Number Conversion Index] It is associated with [Number Conversion Index] in Number Change table so as to specify the index of the conversion to the original called number. [New Number Initial Set] This parameter determines new DN set for call processing if it is required to conduct call processing in different DN sets in terms of attributes of original called subscriber.

Note: This table is an auxiliary table of Incoming Number Pretreatment table. It is configured when the call is forwarded and the calling/called/original called numbers need to be processed according to the relevant attributes of original called number during the incoming number pretreatment procedures.

IV. Related Commands See Table 15-6 for the commands related to incoming original called number correlation

15-25



Table 15-6 List of commands related to incoming original called number correlation Command

Description

LST INORICLDIDX

To list incoming original called number correlation

ADD INORICLDIDX

To add incoming original called number correlation

MOD INORICLDIDX

To modify incoming original called number correlation

RMV INORICLDIDX

To remove incoming original called number correlation

15.5.3 Configuring Incoming Number Pretreatment Data I. Background Information This command is used to add records to Incoming Number Pretreatment table. The table is used to normalize called numbers. These called numbers may be involved in incoming trunk calls and MO calls. They can also be MSRNs or forwarded-to numbers transmitted by MAP signaling, and called numbers changed in IN procedures. After the normalization, their formats can meet the internal specifications in the MSOFTX3000. Besides, the table also provides the capability for receive-number delay processing based on called prefix to ensure that numbers are inputted completely and processed correctly. The MSOFTX3000 queries Incoming Number Pretreatment table according to call source code, call source, called prefix, called number address attribute and max. length of called number, to obtain the incoming calling number associated process index and incoming original called number associated process index. When both indexes are invalid, the MSOFTX3000 directly converts the corresponding number according to the conversion index of calling/called/original called number in this record. When both indexes are valid, the MSOFTX3000 queries Incoming Calling Number Assicaited Process table and Incoming Original Called Number Correlation Processing table respectively according to these indexes to obtain more number normalization information.

II. Command ADD INNUMPREPRO

III. Major Parameters [Call Source Code] Requirements for incoming number pretreatment may vary with different call sources. Set different processing modes according to different call sources through this parameter. [Call Source]

15-26



It is used to define different call sources so as to provide flexible incoming processings capabilities

for

calls

from

the

following

sources:

trunks

(including

TUP/ISUP/R2/PRA/BICC), mobile subscribers, MAP, SCP, and Call Forwarding (CF). [Called Prefix] It determines the first several digits that should be cut from the called number. The principle of "maximum matching" is adopted for prefixes in system number analysis. Wide matching is applied here. [Called Number Address Attribute] It is an input parameter used to set the address attributes of called parties, so that the system can provide different processing capabilities in terms of called address attributes. For example, it is required in the number analysis procedures that the called number should be of international number format. In this case, if a national number is entered, its called number address attribute should be converted. If the called number entered meets the requirements, no conversion is needed. [Max. Length of Called Number] It is used to set the maximal length of the called number received. The excessive part of the called number is rejected. [Calling Number Associated Process Index], [Original Called Number Associated Process Index] Both parameters are output index parameters. They should be set when the incoming number pretreatment procedures are associated with the calling number or original called number. The MSOFTX3000 queries Incoming Calling Number Assicaited Process table and Incoming Original Called Number Correlation Processing table according to these two parameters. Then corresponding processing will be conducted according to the result. Be sure that the indexes used have been defined in these two tables. [Calling Number Conversion Index] It is associated with [Number Conversion Index] in Number Change table and used to designate the index of the conversion to the calling number. [Called Number Conversion Index] It is associated with [Number Conversion Index] in Number Change table and used to designate the type of number conversion to the called number. [Original Called Number Conversion Index] It is associated with [Number Conversion Index] in Number Change table and used to designate the index of the conversion to the original called number in a forwarded incoming call. [Number Receiving Minimum Length] It is an output parameter, indicating the minimum length of the called prefix.

15-27



[Receive-Number Delay Interval] When the call is of trunk incoming type (that is, the call source is "TUP", "ISUP", "R2", "PRA" or “BICC”, or a combination of some of these types), there may be some excessive-long called numbers (such as IP toll prefix "17951" in China). As a result, the complete called number might not be transmitted through inter-office call signaling at a time. Set proper [Receive-Number Delay Interval] to ensure that the called number data is completely received. For numbers sent by SCP, forwarded-to numbers or MSRNs sent by HLR, this parameter is invalid. In this case, it is not necessary to set the parameter.

Note: z

If incoming number processing is associated with calling numbers or original called numbers, please add the corresponding records to Incoming Calling Number Assicaited Process table or Incoming Original Called Number Correlation Processing table first. Then set index parameters in Incoming Number Pretreatment table to realize calling/original called number correlation processing of incoming numbers.

z

In incoming number processing procedures, it is recommended to query Incoming Number Pretreatment table, Incoming Calling Number Assicaited Process table, Incoming Original Called Number Correlation Processing table in turn through data configuration. The final calling/called/original called number conversion index is determined by the valid conversion index obtained in the last query.

IV. Related Commands See Table 15-7 for the commands related to incoming number pretreatment.

15-28



Table 15-7 List of commands related to incoming number pretreatment Command

Description

LST INNUMPREPRO

To list incoming number pretreatment

ADD INNUMPREPRO

To add incoming number pretreatment

MOD INNUMPREPRO

To modify incoming number pretreatment

RMV INNUMPREPRO

To remove incoming number pretreatment

15.6 Route Selection Data Configuration 15.6.1 Configuring Call Prefix I. Background Information Call prefix is the start point of a number analysis process. Its basic attributes include service attribute, route selection code, release control mode, minimum number length, and maximum number length. To set related attribute data of call prefix such as calling number analysis, and DN special processing, the corresponding flag in the call prefix must be set to “YES”.

II. Command ADD CNACLD MOD CNACLD

III. Major Parameters [DnSet] It indicates the DN set to which a call prefix belongs. It corresponds to the DN set defined in the ADD CALLSRC command. [Call Prefix] It refers to a called number prefix or called number. [Service Category] It indicates the service category of a prefix. Depending on different categories, it can be set to “basic service”, “new service/supplementary service”, “test”, “intelligent service”, or “Internet access code”. Generally, select “basic service” for common call prefix, and “new service/supplementary service” for service services. [Service Attribute] It is used to set the service attribute of a prefix. You can select “intra-office”, “local”, “local toll”, “national toll”, “international toll”, or various new services. [Route Selection Code]

15-29



The route selection code is used for identifying the route selection method for a call to the prefix. It is already defined in the ADD RTANA command. Select 65535 (invalid) for the local office prefix, and valid route selection code for the outgoing call. [Minimum Number Length] It indicates the minimum number length allowed by this type of call. If the length of a dialed number is less than the minimum number length, the switch will not process it. [Maximum Number Length] It indicates the maximum number length allowed by this type of call, which should be set according to the actual situation. If the length of a dialed number is longer than the maximum number length, the switch will not process the excessive digits. [Query Toll Area Code] It determines whether to query the Toll Area Code table when a subscriber dials a number whose prefix has been defined in the parameter “Call Prefix”. If it is set to "Yes", the MSOFTX3000 will query the Toll Area Code table and intercept toll calls after subscribers dial the local area code. The MSOFTX3000 also intercepts MSISDN call after subscribers dial the toll area code. Set this parameter to "TRUE" for call prefixes involved in calls whose service attributes are "NTT", "ITT", or "PLMN Other MSC". If the corresponding data preventing subscribers from nest-dialing have been configured in number analysis, this setting is not necessary even for toll prefixes. [Release Mode] This parameter is used to set the release control mode. Release control mode may be first party release, calling party release, called party release, or last party release. Usually set it to first party release. [Emergency Call Observe Flag] It indicates whether a call of this class is an emergency call and is observed. Usually use the default value, “NO”. Configuration of this parameter will not affect number analysis procedures, but it will be marked in the bill. [Called Number Type] It defines the type of the called number. For prefixes whose related routing information is obtained from the local office (including the prefixes of IN calls triggered by number segment at the local office), set this parameter to "MSISDN". For MSRN prefixes, PSTN call prefixes, and other types of prefixes, set this parameter respectively to "MSRN/HON", "PSTN", and "PSTN" or "Unknown Number". In the case of an Overlay outgoing PPS call prefix, set this parameter to "PPS (PPS Number)". For other prefixes, set this parameter according to the actual situations. [EARLY ACM Flag], [EARLY ACM Delay Value (0.1S)] These two parameters are used together to realize the EARLY ACM function at the local office. Set [EARLY ACM Flag] to "TRUE" and set [EARLY ACM Delay Value (0.1S)] properly. 15-30



[Gain] Usually, this parameter needs not to be configured. [Toll Prefix Length] Length of a toll prefix is 1: for national toll call PSTN; 2: for international toll call; 0: for other cases. [Destination] It refers to the call destination, used in destination traffic measurement. [Enhance Route Processing Flag] When subscribers dial the numbers with the same prefix, this parameter can be set to "TRUE" to select different outgoing routes according to the varied length of called numbers or different types of calls. Besides, the data of Enhanced Route Processing table should also be configured. [Service Check Index] It is associated with [Service Check Index] in Service Check table. Through this parameter, the calling subscriber can originate certain restricted services by dialing certain special prefixes. If this parameter is not set to "65535", the default value, the MSOFTX3000 will query Service Check table through this parameter and then perform service check before number analysis. [Supplementary Signaling Flag] It determines whether to send information necessary for number analysis such as calling numbers and original called numbers to the next office through trunk signaling. Usually, the MSOFTX3000 automatically sends the calling number and original called number to the next office and does not send the calling number for calls to local area and local office. If you do not need the MSOFTX3000 to send those information to the next office, set this parameter to “YES”. When this parameter is set to "YES", data in Supplementary Signaling table must also be configured. Normally calls to the local area and local office require sending calling numbers and original called number to the next office. Therefore, this parameter can be set to "NO" by default. [Calling Number Analyzing] It determines whether to conduct different processing over calls according to their various call prefixes and attributes. Calling subscriber attributes are determined by the configuration of corresponding call source codes. Therefore, when it is necessary to configure different call source attribute for a specified calling subscriber, set this parameter to "TRUE", and configure corresponding analysis data of calling numbers and calling features. Through the configuration of analysis data of calling numbers and calling features, calling/called numbers can be converted in terms of calling attributes.

15-31



To analyze calling numbers (such as normalizing calling numbers), set this parameter to "TRUE". In this case, the MSOFTX3000 queries Calling Number Analysis table and Calling Number Analysis table to analyze the calling number. [Number Initial Processing] Set this parameter to "TRUE" if special processing is required for the DN set, for example, number conversion and failure processing. In this case, the MSOFTX3000 will query DN Set Processing table for special processing on the DN set.

Caution: The number of records for call prefix cannot be greater than the set value for this table in the maximum tuple number table; otherwise, the table will overflow. If the service attribute has been set to outgoing calls, the route selection code must be set and must have been defined in the route analysis table.

IV. Related Commands See Table 15-8 for the commands related to call prefix configuration. Table 15-8 List of commands related to call prefix configuration Command

Description

ADD CNACLD

To add call prefix

MOD CNACLD

To modify call prefix

RMV CNACLD

To remove call prefix

LST CNACLD

To list call prefix

LST RT

To list route information (corresponding prefix of route can be found)

15.6.2 Configuring Enhanced Route Processing Data I. Background Information This command is associated with call prefix data configuration and is applied to add records to Enhanced Route Processing table when [Enhance Route Processing Flag] is set to "TRUE". The table supports flexible routing function for call prefixes. It selects different outgoing routes according to the length of called numbers and call types.

II. Command ADD SUPERRT

15-32



III. Major Parameters [Number Initial Set], [Call Prefix] These two parameters are used to set the called prefix to be conducted for enhanced route processing, and the DN set in which this called prefix is contained. [Call Type] When it is required that the outgoing route of a prefix of a normal call and the outgoing route forwarded in this office to the prefix are different, select different call types through this parameter and define different Route Selection Code to implement it. [Max. Length of Prefix] It helps to select different outgoing routes for called numbers with the same call prefix but different number length. Route selection can also be done according to the length of the called number prefix. [Route Selection Code] It helps to modify the outgoing route selection information of the prefix defined in Called Number Analysis table, and obtain a new route selection code. If table-query fails, the MSOFTX3000 will still use Called Number Analysis table to obtain route selection code for route selection.

IV. Related Commands See Table 15-9 for the commands related to enhanced route processing data configuration. Table 15-9 List of commands related to enhanced route processing data configuration Command

Description

LST SUPERRT

To list enhanced route

ADD SUPERRT

To add enhanced route

MOD SUPERRT

To modify enhanced route

RMV SUPERRT

To remove enhanced route

15.6.3 Configuring Call Authority Original Called Correlation Processing Data I. Background Information This command is used to add records to Call Authority Check Original Called Correlation Processing table. This table is used to check forwarding calls according to their original called prefixes and roaming types, and determine the corresponding call processing modes and measures related according to results of the check. The MSOFTX3000 queries Call Authority Check table and obtains the "Authority Check 15-33



Original Called Correlation Processing Index". Then according to this index, original called prefix and roaming type, the MSOFTX3000 queries Call Authority Check Original Called Correlation Processing table to obtain the processing mode for forwarding calls. If no corresponding records are matched, the MSOFTX3000 directly goes to the next procedures.

II. Command ADD PRICHKORICLDIDX

III. Major Parameters [Authority Check Original Called Correlation Processing Index] It is used to identify the records in Call Authority Check Original Called Correlation Processing table. And other data tables can use these records through this parameter. [Original Called Prefix], [Original Called Party Roaming Type] These two parameters are the relevant attributes of the original called party. Together with [Processing Type], they can realize the restriction or processing of forwarding calls according to the original called prefix or roaming type. For example, to restrict the forwarding of calls when the called party is an other-mobile-network subscriber and roams to the local office, set [Original Called Party Roaming Type] to "Other Mobile Network", and [Processing Type] to "Prohibit". [Processing Type] It determines the processing modes for various calls. In terms of various call authority check results, there are the following processing modes available: 1) The call meets the system analysis requirements after the check; and it will be connected; that is, set this parameter to "passon (Continue Proceeding)". 2) The call is forwarded at the local office. Set this parameter to "contplay (Continue and play announcement)" or "notecontinue (Connect after playing announcement)" according to actual conditions. 3) Set the parameter to "Inhibited (Prohibit)" for calls that cannot meet system analysis requirements or are restricted in the system. In this case, the corresponding failure processing data should be configured. [Failure Cause Code] It is valid only when [Processing Type] is set to "Inhibited (Prohibit)". It is used to define the cause value of the call release. In the case of a failed check, the MSOFTX3000 will query Failure Processing table through this parameter for corresponding processing. [Tone Code] It is valid only when [Processing Type] is set to "Continue and play announcement" or "Connect after playing announcement". It is used to designate the code of the announcement to be played.

15-34



Note: The configuration of call authority original called correlation processing data will be conducted only when it is required to check forwarding calls according to the original called prefixes and roaming attributes.

IV. Related Commands See Table 15-10 for the commands related to call authority original called correlation processing data configuration. Table 15-10 List of commands related to call authority original called correlation processing data configuration Command

Description

LST PRICHKORICLDIDX

To list call authority original called correlation

ADD PRICHKORICLDIDX

To add call authority original called correlation

MOD PRICHKORICLDIDX

To modify call authority original called correlation

RMV PRICHKORICLDIDX

To remove call authority original called correlation

15.6.4 Configuring Call Authority Check Data I. Background Information This command is used to add records to Call Authority Check table. The table supports the flexible announcement processing of four types of supplementary services, including: Call Forwarding Unconditional (CFU), Call Forwarding on mobile subscriber Busy (CFB), Call Forwarding on No Reply (CFNRy) and Call Forwarding on mobile subscriber Not Reachable (CFNRC). It also supports the check and restriction of ordinary incoming calls, forwarded incoming calls and local forwarding calls. The MSOFTX3000 queries this table respectively during the incoming number analysis and when the call is forwarded at the local office. And then the MSOFTX3000 determines the call processing mode by the result of the query. For forwarding calls, if the corresponding original called correlation processing data have been configured, it is still required to query Call Authority Check Original Called Correlation Processing table. Both tables are applied in cooperation with Failure Processing table, so as to conduct failure processing over calls that do not pass the check.

II. Command ADD CALLPRICHK

15-35



III. Major Parameters [Call Source Code] It is associated with [Call Source Code] in Call Source table and used to conduct call authority check over calls originated from various call sources. All call sources should be configured with call authority check data. [Call Type] It helps to set various call authority check data for various types of calls (ordinary or forwarded calls). [Called Prefix], [Max. Length of Called Number] These two parameters determine the relevant attributes of the called party; that is, the prefix of called number to be checked and its maximal length. When a subscriber dials the number with such a prefix, the check will be conducted or the call will be barred. [Calling Subscriber Prefix], [Calling Subscriber Type], [Calling Party Roaming Type] These two parameters determine the relevant attributes of calling subscriber. The first two parameters support maximum matching. [Calling Party Roaming Type] is used to set different call authorities for subscribers with different calling subscriber types so as to realize the corresponding restrictions (for example, restrict the forwarding of the call in which the other-mobile-network subscriber roaming to the local network is called). The options of [Calling Party Roaming Type] include "Local Mobile Network", "National Mobile Network", "International Mobile Network", "Other National Mobile Network", "Other International Mobile Network", and "PSTN_SUBSCRIBER". [Authority Check Original Called Correlation Processing Index] It is an output index parameter. It is configured when the call is forwarded and a call authority check should be conducted according to the attributes of the original callee/called party. This parameter is used to query Call Authority Check Original Called Correlation Processing table for the corresponding processing mode. This parameter is valid when [Call Type] is not "COMMON (Ordinary Call)". [Processing Type] It determines the mode to process the call after the check. In terms of various call authority check results, there are processing modes available as follows: 1) The call meets the system analysis requirements after the check, and it will be connected; that is, set this parameter to "passon (Continue Proceeding)". 2) The call is forwarded at the local office. Set this parameter to "contplay (Continue and play announcement)" or "notecontinue (Connect after playing announcement)" according to actual conditions. 3) Set the parameter to "Inhibited (Prohibit)" for calls that cannot meet system analysis requirements or are restricted in the system. In this case, the corresponding failure processing data should be configured. [Failure Cause Code]

15-36



It is valid only when [Processing Type] is set to "Inhibited (Prohibit)". This parameter is used to define cause why the call is released, and to set proper failure processing records in Failure Processing table, so as to play proper announcement to the subscriber. When the call authority check fails, the MSOFTX3000 queries Failure Processing table through this parameter for the corresponding processing. [Tone Code] It is valid only when [Processing Type] is set to "Continue and play announcement" or " Connect after playing announcement". It is used to designate the code of the announcement to be played.

Note: z

According to the sequence of number analysis, incoming number pretreatment procedures have been conducted before the call authority check. Therefore, the called number in the check should be the number that has been converted, instead of the number dialed by the calling subscriber.

z

Call authority check is carried out during number analysis. For an one-stage call, call authority check is done once only when number analysis starts. The check will not be conducted during the analysis of the MSRN prefix.

z

If Authority Check table must be queried during data configuration, the call processing shall be based on the query result of Authority Check table. If Authority Check Original Called Correlation Processing table is also queried, the call processing shall be based on the result of the final query.

IV. Related Commands See Table 15-11 for the commands related to call authority check. Table 15-11 List of commands related to call authority check Command

Description

LST CALLPRICHK

To list call authority check

ADD CALLPRICHK

To add call authority check

MOD CALLPRICHK

To modify call authority check

RMV CALLPRICHK

To remove call authority check

15.6.5 Configuring Service Check Data I. Background Information This command is used to add records to Service Check table, which is used to realize the flexible control over service attribute check of calling subscribers. The

15-37



MSOFTX3000 queries the records in this table according to the call source and [Service Check Index] in Called Number Analysis table, and processes the call according to the settings in the records.

II. Command ADD SRVCHK

III. Major Parameters [Call Source Code] It determines the call source to be conducted for service check. It is associated with [Call Source Code] in Call Source table and generally set to "65534", indicating that service check may be carried out over all call sources. [Service Check Index] It is used to identify the records in Service Check table and corresponds to [Service Check Index] in Called Number Analysis table. The MSOFTX3000 queries Called Number Analysis table in number analysis procedures. If [Service Check Index] is not blank, the relevant records in Service Check table will be referenced through this parameter. [IWF Application Mode], [Forced EC Request] These two parameters determine the modes to apply for IWF and EC resources for the call being checked. Both of them are generally set by default; that is, the former is set to "Automatic Application for IWF", and the latter to "No". [Restricted Session Duration(sec)] It is used to set the maximal conversation duration during the service restricted. Its unit is second. When the call in session is checked and found to have reached the restricted session duration, the call will not be disconnected by default. [Perform Service Check] It determines whether to carry out service check over the service attribute of the call. [Service Check Type] and [Service Check Mode] are valid only when this parameter is set to "Yes". [Service Check Type], [Service Check Mode] These two parameters indicate repsectively whether a service is to be checked and the mode of check. They determine the mode to check the service, as shown in Table 15-12. Table 15-12 Service check processing mode Service check type

Service check mode

Meaning

0

0

Services related will be processed according to the default modes stipulated in GSM specifications.

15-38


Service check type


Service check mode

Meaning

0

1

Calls of corresponding services will be processed as ordinary calls (for example, when the service type is "ODB_BAOC", set the two parameters aforementioned to "SCC=ODB_BAOC-0, SCM=ODBBAOC-1", the call will be connected; that is, the subscriber being barred can still make calls.)

1

0

Calls of corresponding services will be rejected.

1

Only calls requesting for such service will be connected, for example, when service type is "ODB_BAOC" and the two parameters are configured as "SCC=ODB_BAOC-1, SCM=ODBACOC-1", the calls will be checked. If the check fails, the call will be disconnected directly and corresponding announcement will be played for the subscriber.

1

Note: When a certain service is set to "1" in [Service Check Type], it may result in the rejection of the call containing (or not containing) this service. Therefore, announcements should be played for the failures of such calls. The command ADD CST can be used to add service check tone records for the announcements.

IV. Related Commands See Table 15-13 for the commands related to service check. Table 15-13 List of commands related to service check Command

Description

LST SRVCHK

To list service check

ADD SRVCHK

To add service check

MOD SRVCHK

To modify service check

RMV SRVCHK

To remove service check

15.6.6 Configuring Calling Number Analysis Data I. Background Information Calling number analysis is used to normalize the formats of calling numbers, or to perform various special processing (for example, rerouting) over calls according to

15-39



different attributes of calling numbes involved. It is a processing method for calling number, including how to route, failure processing, and calling/called number change. The call source attribute is defined in call source code. Multiple call sources (local subscribers or trunk users) are allowed to use the same call source code; that is, they have the same call attributes. If it is required to give a particular caller different call source attributes, the calling number analysis table can be used to define new call source attributes.

Note: When “Calling Number Analysis flag” in the call prefix table is set to “YES”, the MSOFTX3000 first queries Calling Attribute Analysis table (this table will be introduced in later sections) based on the attributes of the calling subscriber. Upon the success of querying Calling Attribute Analysis table, the MSOFTX3000 terminates calling number analysis. If there is no matching record in Calling Attribute Analysis table, the MSOFTX3000 will query Calling Number Analysis table.

II. Command ADD CNACLR

III. Major Parameters [Call Source Code], [Calling Party Roaming Attribute], [Calling Number] These parameters are used for the MSOFTX3000 to query Calling Number Analysis table so as to determine the call that needs the calling analysis. [Calling Subscriber Type] It determines the new calling subscriber type: ordinary subscriber, data subscriber, operator, and so on. [Caller Minimum Length] It indicates how many digits the calling number must at least have. [Call Source] It indicates whether the call is initiated from the mobile side or PSTN, or is a forwarded-to call. [Number Initial Set] It indicates in which DN set the analysis is conducted. [Call Prefix] It is the prefix of the called number. [Route Selection Source Code]

15-40



It is an output parameter used to redesignate the outgoing route in terms of calling subscribers. When this parameter is specified, the route selection source code obtained by querying Called Number Analysis table is invalid. [Route Selection Code] It is an output parameter, indicating the code of the new route selection scheme of a called number. [Failure Source Code] This parameter is used to set the new failure source code that the call corresponds to. When a subsequent failure occurs, the new failure source code is used to query Failure Processing table, determining how to deal with the failure. [Called Number Change Index] It indicates the change index of the called number. It is defined in the ADD DNC command. [Calling Number Change Index] It indicates the change index of the calling number. It is defined in the ADD DNC command. [Processing Type] It indicates how to process the number when the analysis is successful. It includes failure processing, triggering NCSI DP2, outgoing after instant route selection. [New Service Property] If the processing type of the current processing is outgoing after route selection, you can configure service attributes for instant outgoing, including “national”, “international” and “local service”. [Failure Cause Code] It indicates the failure cause when [Processing Type] is “Failure Processing”. [SCP Parameter Table Index] If the NCSI DP2 service is triggered, this index will be used to obtain related information of SCP.

15-41



Caution: z

Calling Number Analysis table is valid only when [Calling Number Analysis Flag] of the call is “YES”.

z

Before configuring calling number analysis data, you must have defined parameters cited in Calling Number Analysis table, including [Call Source Code], [Route Selection Source Code], [Failure Source Code], and [Calling Number Change Index].

z

The number of records in Calling Number Analysis table cannot be greater than the set for this table in the maximum tuple number table.

IV. Related Commands See Table 15-14 for the commands related to calling number analysis. Table 15-14 List of commands related to calling number analysis Command

Description

LST CNACLR

To list calling number analysis

ADD CNACLR

To add calling number analysis

MOD CNACLR

To modify calling number analysis

RMV CNACLR

To remove calling number analysis

15.6.7 Configuring Calling Feature Processing Data I. Background Information This command is used to add records in Calling Feature Processing table. When defining records in Calling Feature Processing table, one or more service check types in the table will be mapped to a calling feature index. Calling feature index corresponds to that in calling feature analysis. Calling Feature Processing table is referenced to Calling Feature Analysis table through this parameter. During calling feature analysis process, special processing of the call will be conducted according to [Calling Feature Index]. If [Calling Number Analysis Flag] exists during called number analysis, special processing of the call must be done by querying Calling Feature Processing table.

II. Command ADD CLICRTPRO

III. Major Parameters [Index] 15-42



It is used within the system. Set no duplicate indexes. [Service Check Type] It is an output parameter. [Calling Feature] It is an output parameter. It corresponds to one or more service check types. [Description] Description of the features of the calling subscriber.

IV. Related Commands See Table 15-15 for the commands related to calling feature processing. Table 15-15 List of commands related to calling feature processing Command

Description

LST CLICRTPRO

To list calling feature processing

ADD CLICRTPRO

To add calling feature processing

MOD CLICRTPRO

To modify calling feature processing

RMV CLICRTPRO

To remove calling feature processing

15.6.8 Configuring Calling Feature Analysis Data I. Background Information This command is used to add records in Calling Feature Analysis table. Calling Feature Analysis table is used for conducting special processing of the call according to the calling features (for example, whether the subscriber has subscribed to forwarding and service restriction). Calling Feature Processing table is referenced to Calling Feature Analysis table through this parameter.

II. Command ADD CLICRTANA

III. Major Parameters [Call Source Code] Call source code of the calling subscriber. [Calling Feature] It is the calling feature index. It corresponds to [Calling Feature] in Calling Feature Processing table. Calling Feature Processing table is referenced to Calling Feature Analysis table through this parameter.

15-43



[Calling Subscriber Type] It determines the calling subscriber type: ordinary subscriber, data subscriber, operator, and so on. [Calling Number Max. Length] It indicates how many digits the calling number can have at most. [Call Source] It indicates whether the call is initiated from the mobile side or PSTN, or is a forwarded-to call. [Number Initial Set] It indicates in which DN set the analysis is conducted. [Call Prefix] It is the prefix of the called number. [Route Selection Source Code] It is an output parameter used to redesignate the outgoing route in terms of calling subscribers. When this parameter is specified, the route selection source code obtained by querying Called Number Analysis table is invalid. [Route Selection Code] It is an output parameter, indicating the code of the new route selection scheme of a called number. [Failure Source Code] This parameter is used to set the new failure source code that the call corresponds to. When subsequent failure occurs, the new failure source code is used to query Failure Processing table, determining how to deal with the failure. [Called Number Change Index] It indicates the change index of the called number. It is defined in the ADD DNC command. [Calling Number Change Index] It indicates the change index of the calling number. It is defined in the ADD DNC command. [Processing Type] It indicates how to process the number when the analysis is successful. It includes failure processing, triggering NCSI DP2, outgoing after instant route selection. [New Service Property] If the processing type of the current processing is outgoing after route selection, you can configure service attributes for instant outgoing, including “national”, “international” and “local service”.

15-44



[Failure Cause Code] It indicates the failure cause when [Processing Type] is “Failure Processing”. [SCP Access Mode] There are two SCP access modes: HSCP (HOME SCP) and AC (ACCESS CODE). HSCP means that SCP is fixed on HOME SCP. AC means that SCP is not connected to another single SCP. It is connected to multiple SCPs through ACCESS CODE. [SCP Parameter Table Index] If the NCSI DP2 service is triggered, this index will be used to obtain related information of SCP.

Caution: Calling Number Analysis table is valid only when [Calling Number Analysis Flag] in Call Prefix table is “YES”.

IV. Related Commands See Table 15-16 for the commands related to calling number analysis. Table 15-16 List of commands related to calling number analysis Command

Description

LST CLICRTANA

To list calling number analysis

ADD CLICRTANA

To add calling number analysis

MOD CLICRTANA

To modify calling number analysis

RMV CLICRTANA

To remove calling number analysis

15.6.9 Configuring Dialed Number Special Processing Data I. Background Information This command is used to set various modes for the MSOFTX3000 to process calls. Such modes include calling/called number converting, failure processing, reanalysing, and the type of signal tone sent. Besides, these modes are classified in terms of call source codes, called numbers and DN sets. Calls that have no corresponding processing modes in DN Special Processing table will be processed as usual.

II. Command ADD PFXPRO 15-45



III. Major Parameters [Call Source Code] It identifies the call source to which a calling subscriber belongs. DN processing happens when subscribers of this call source originate calls to a specified prefix. [Call Source] It is the category to which a calling subscriber belongs. [Number Initial Set] It is the DN set to which a called prefix belongs. [Call Prefix] It is the called prefix on which DN processing happens. Call prefix is the number used for indicating call connection. During number analysis, the called number tries to match the call prefix according to the maximum matching principle, for the purposes of determining attributes of the call. Call prefix reflects information about numbering schemes, billing specifications, and routing methods pertaining to the MSOFTX3000. [New Number Initial Set] It is the new DN set after DN processing, used to achieve conversion between DN sets during a call. [Called Number Change Index] It indicates the number change index of a called number. It is valid only when the parameter [Called Number Change Flag] is set to “YES”. Its value is defined in the ADD DNC command. [Calling Number Change Index] It indicates the number change index of a calling number. It is valid only when the parameter [Calling Number Change Flag] is set to “YES”. Its value is defined in the ADD DNC command. [Process Type] This parameter refers to the call processing type after the success of number analysis. These types are failure processing, triggering NCSI DP12, reanalyzing and so on. [Failure Cause Code] It indicates the cause when [Process Type] is “Failure Processing”. [Tone Sending Mode] This parameter is used to configure whether to play ordinary announcement, connect call and play an announcement at the same time, connect call after playing announcement, or do not play an announcement. [Tone Type] It indicates the type of signal tone to be sent, such as 117 time reporting and call barring tone. 15-46



[SCP Parameter Table Index] This parameter indicates the intelligent parameter index. If the NCSI DP12 service is triggered, this parameter will be used to obtain related information of SCP.

Caution: Before adding DN special processing data, you must have set the DN set, call prefix, call source, call change index and the new DN set that are referenced.

IV. Related Commands See Table 15-17 for the commands related to DN special process. Table 15-17 List of commands related to DN special process Command

Description

LST PFXPRO

To list DN special process

ADD PFXPRO

To add DN special process

MOD PFXPRO

To modify DN special process

RMV PFXPRO

To remove DN special process

15.6.10 Configuring Failure Processing Data I. Background Information Failure Processing table can be referenced from DN Special Processing table through [Failure Cause Code] in the latter table. It can also be referenced through [Failure Cause Code] in Call Source table and [Call Failure Cause Code] detected by the exchange. Special processing after call failure includes sending special signal tone, re-routing, and reanalyzing after number conversion.

II. Command ADD CFPRO

III. Major Parameters [Failure Cause Code] A set of codes that are defined in the MSOFTX3000 and correspond to failure cause values. Through these codes, the MSOFTX3000 queries Failure Processing table and obtains the corresponding call failure processing mode.

15-47



[Failure Source Code] It indicates failure source code in call source. Together with [Call Failure Cause Code] detected by the MSOFTX3000, this parameter determines a failure processing record. [Caller Category] It indicates the subscriber category to which the calling party must belong for the purposes of starting a failure processing process. [Service Attribute] It indicates the service attribute that the concerned call must have for the purposes of starting a failure processing process. [Processing Type] It specifies the processing way when the calls of this class fail. The processing ways may be sending signal tone, queuing, re-selecting sub-route, interrupting, inserting or re-analyzing after number change, and so on. [Signal Tone Type] This parameter is enabled when the failure processing type is sending signal tone. If a call failure meets preset conditions, signal tone selected in this parameter will be sent to the calling party. Number change tone with the number attached will be sent only when the failure cause code is number changed. [Trigger Type of IN Service] These types include DP4, DP13, DP14 and not to trigger.

IV. Related Commands See Table 15-18 for the commands related to failure processing. Table 15-18 List of commands related to failure processing Command

Description

LST CFPRO

To list failure processing

ADD CFPRO

To add failure processing

MOD CFPRO

To modify failure processing

RMV CFPRO

To remove failure processing

15-48



15.7 Configuring Outgoing Number Preprocessing Data 15.7.1 Configuring Outgoing Calling Number Correlation Processing Data I. Background Information This command is used to add records to Outgoing Calling Number Correlation Processing table. The table helps to normalize the calling/called/original called numbers involved in outgoing calls according to the calling number and relevant attributes. The MSOFTX3000 obtains [Calling Number Associated Process Index] from Outgoing Number Preprocessing table, then queries Outgoing Calling Number Correlation Processing table according to this index, calling subscriber prefix, calling subscriber type, calling number address attribute, calling party roaming attribute, and calling number maximum length. Then the MSOFTX3000 obtains the conversion index of calling/called/original called numbers being sent, and normalize these numbers according to the conversion mode corresponding to the conversion index.

II. Command ADD OUTCLRIDX

III. Major Parameters [Calling Number Associated Process Index] It uniquely identifies an outgoing calling number correlation processing record. The MSOFTX3000 queries Outgoing Calling Number Correlation Processing table through [Calling Number Associated Process Index] in Outgoing Number Preprocessing table during the outgoing number preprocessing. [Calling Subscriber Prefix], [Calling Subscriber Type], [Calling Number Address Attribute], [Calling Party Roaming Attribute], [Calling Number Max. Length] They are all parameters related to the calling subscriber. The MSOFTX3000 queries Outgoing Calling Number Correlation Processing table according to these parameters entered during the analysis. If a record is matched, the MSOFTX3000 will process the call as specified in the record. Otherwise, the MSOFTX3000 will process the call as usual. [Calling Number Conversion Index], [Designated Calling Number Format] They determine the mode to convert the calling number. Note that one number conversion mode can be used only at a time; that is, only one of the two parameters should be specified at a time. When [Designated Calling Number Format] is valid, the calling number is converted as specified. When [Designated Calling Number Format] is invalid, the MSOFTX3000 will query Number Change table by [Calling Number Conversion Index] and finds the mode to convert the calling number. [Called Number Conversion Index], [Designated Called Number Format]

15-49



These two parameters determine the mode to convert the called number. Note that only one conversion mode can be adopted at a time; that is, two parameters cannot be configured at the same time. When [Designated Called Number Format] is valid, the called number is converted as specified. When [Designated Called Number Format] is invalid, the MSOFTX3000 queries Number Change table by [Called Number Conversion Index] and locates the corresponding mode to convert the number. [Original Called Number Conversion Index], [Designated Original Called Number Format] These two parameters are used to determine the mode to convert the original called number. Note that only one conversion mode can be used at a time; that is, only one of two parameters should be specified at a time.When [Designated Original Called Number Format] is valid, the original called number is converted as specified. When [Designated Original Called Number Format] is invalid, the MSOFTX3000 queris Number Change table by [Original Called Number Conversion Index] and finds the mode to convert the original called number. [Redirecting Conversion Index], [Designated Redirecting Number Format] These two parameters are used to set the mode for redirecting conversion. Note that only one mode of number conversion can be configured once, namely only one of these parameters can be configured. When [Designated Redirecting Number Format] is valid, the conversion mode that designates number format takes precedence. When [Designated Redirecting Number Format] is invalid, the MSOFTX3000 queries Number Change table based on [Redirecting Conversion Index] to convert the original called number.

Note: The configuration of this part will be made only when it is required to normalize outgoing calling/called/original called numbers according to both calling and called numbers and their attributes. If conversion is done only based on the called number, you need not to configure calling number correlation processing data.

IV. Related Commands See Table 15-19 for the commands related to outgoing calling number correlation. Table 15-19 List of commands related to outgoing calling number correlation Command

Description

LST OUTCLRIDX

To list outgoing calling number correlation

ADD OUTCLRIDX

To add outgoing calling number correlation

15-50



Command

Description

MOD OUTCLRIDX

To modify outgoing calling number correlation

RMV OUTCLRIDX

To remove outgoing calling number correlation

15.7.2 Configuring Outgoing Original Called Number Correlation Processing Data I. Background Information This command is used to add records to Outgoing Original Called Number Correlation Processing table. The table is used to normalize the calling/called/original called numbers involved in outgoing calls accroding to original called number and its relevant attributes. The MSOFTX3000 obtains the original called number associated process index, and then queries Outgoing Original Called Number Correlation Processing table according to this index, original called prefix, original called number address nature, original called party roaming attribute, and original called number maximum length, to obtain the conversion indexes of the outgoing calling/called/original called numbers. Then the MSOFTX3000 normalizes these numbers according to the conversion mode corresponding to these conversion indexes.

II. Command ADD OUTORICLDIDX

III. Major Parameters [Original Called Number Associated Process Index] It identifies records in Outgoing Original Called Number Correlation Processing table. Outgoing Number Preprocessing table references the corresponding records in Outgoing Original Called Number Correlation table through this parameter. [Calling Number Conversion Index], [Designated Calling Number Format] These two parameters determine the mode to convert the calling number. Note that only one mode of conversion can be conducted over the calling number at a time; that is, only one of the two parameters should be configured. When [Designated Calling Number Format] is invalid, the MSOFTX3000 queries Number Change table according to [Calling Number Conversion Index] and finds the corresponding mode to convert the calling number. When [Designated Calling Number Format] is valid, the MSOFTX3000 converts the number in the mode with a specified format first. [Called Number Conversion Index], [Designated Called Number Format] These two parameters determine the mode to convert the called number. Note that only one conversion mode can be adopted at a time; that is, only one of the two parameters can be configured. When [Designated Called Number Format] is invalid, the

15-51



MSOFTX3000 queries Number Change table according to [Called Number Conversion Index] and locates the correspond mode to convert the called number. When [Designated Called Number Format] is valid, the MSOFTX3000 converts the number in the mode with a specified format first. [Original Called Number Conversion Index], [Designated Original Called Number Format] These two parameters determine the mode to convert the original called number. Note that only one conversion mode can be adopted to convert the original called number at a time; that is, only one of the two parameters should be configured. When [Designated Original Called Number Format] is invalid, the MSOFTX3000 queries Number Change table by [Original Called Number Conversion Index] and locates the corresponding mode to convert the number. When [Designated Original Called Number Format] is valid, the MSOFTX3000 converts the number in the mode with a specified format first. [Redirecting Conversion Index], [Designated Redirecting Number Format] These two parameters are used to set mode for redirecting conversion. Note that only one mode of number conversion can be configured once, namely only one of these parameters can be configured. When [Designated Redirecting Number Format] is valid, the conversion mode that designates number format takes precedence. When [Designated Redirecting Number Format] is invalid, the MSOFTX3000 queries Number Change table based on [Redirecting Conversion Index] to convert the original called number.

Note: The configuration of Outgoing Original Called Number Correlation Processing table will be made only when calls are forwarded to the local office and it is required to process calling/called/original called numbers according to called/original called number attribute.

IV. Related Commands See Table 15-20 for the commands related to outgoing original called number correlation. Table 15-20 List of commands related to outgoing original called number correlation Command

Description

LST OUTORICLDIDX

To list outgoing original called number correlation

ADD OUTORICLDIDX

To add outgoing original called number correlation

MOD OUTORICLDIDX

To modify outgoing original called number correlation

RMV OUTORICLDIDX

To remove outgoing original called number correlation

15-52



15.7.3 Configuring Outgoing Number Preprocessing Data I. Background Information This command is used to add records to Outgoing Number Preprocessing table. The table is used to preprocess (perform format control over calling/called/original called numbers) various numbers sent to outgoing trunks, so as to ensure these numbers meet the signaling transmission requirements of the interface. The MSOFTX3000 queries Outgoing Number Preprocessing table according to call source code, outgoing trunk group No., DN set, called prefix, called number address attribute, and maximum length of called number. Then it obtains the values of [Calling Number Associated Process Index] and [Original Called Number Associated Process Index].

If

both

parameters

are

invalid,

the

MSOFTX3000

converts

the

calling/called/original called numbers directly. Otherwise, the MSOFTX3000 queries Outgoing Calling Number Correlation Processing table and Outgoing Original Called Number Correlation Processing table through the two indexes to obtain number normalization information.

II. Command ADD OUTNUMPREPRO

III. Major Parameters [Call Source Code], [Outgoing Trunk Group No.], [Number Initial Set], [Called Prefix], [Called Number Address Attribute], [Max. Length of Called Number] During the outgoing of calls, these parameters are used for the MSOFTX3000 to query Outgoing Number Preprocessing table and obtain the conversion modes for calling/called/original called numbers involved. [Calling Number Associated Process Index] It should be configured when the conversions of calling/called/original called numbers are associated with calling number and its attributes. It is the index to query Outgoing Calling Number Correlation Processing table. [Original Called Number Associated Process Index] This parameter is set for the MSOFTX3000 to query Outgoing Original Called Number Correlation Processing table and obtain corresponding modes to convert trunk numbers. You can set index data in this parameter for referencing Outgoing Original Called Number Correlation Processing table to perform number conversion. [Calling Number Conversion Index], [Designated Calling Number Format] These two parameters determine the mode to convert the calling number. Note that only one conversion mode can be adopted at a time; that is, only one of the two parameters should be configured at the same time. When [Designated Calling Number Format] is invalid, the MSOFTX3000 queries Number Change table by [Calling Number

15-53



Conversion Index] and locates the mode to convert the calling number. When [Designated Calling Number Format] is valid, the MSOFTX3000 convert the number in the mode with a specified format first. [Called Number Conversion Index], [Designated Called Number Format] These two parameters are used to determine the mode to convert the called number. Note that only one conversion mode can be adopted at a time; that is, only one of the two parameters can be configured simultaneously. When [Designated Called Number Format] is invalid, the MSOFTX3000 queries Number Change table by [Called Number Conversion Index] and obtains the corresponding mode to convert the called number. When [Designated Called Number Format] is valid, the MSOFTX3000 converts the number in the mode with a specified format first. [Original Called Number Conversion Index], [Designated Original Called Number Format] These two parameters determine the mode to convert the original called number. Note that only one conversion mode can be adopted at a time; that is, only one of the two parameters can be configured. When [Designated Original Called Number Format] is invalid, the MSOFTX3000 queries Number Change table by [Original Called Number Conversion Index] and obtains the corresponding mode to convert the original called number. When [Designated Original Called Number Format] is valid, the MSOFTX3000 converts the number in the mode with a specified format first. [Redirecting Conversion Index], [Designated Redirecting Number Format] These two parameters are used to set mode for redirecting conversion. Note that only one mode of number conversion can be configured once, namely only one of these parameters can be configured. When [Designated Redirecting Number Format] is valid, the conversion mode that designates number format takes precedence. When [Designated Redirecting Number Format] is invalid, the MSOFTX3000 queries Number Change table based on [Redirecting Conversion Index] to convert the original called number.

IV. Note z

If it is required to conduct correlation processing over outgoing numbers according to calling numbers, first configure outgoing calling number correlation processing data. Similarly, if it is required to conduct correlation processing over outgoing numbers according to original called numbers, first configure outgoing original called number correlation processing data, then set corresponding index parameters in Outgoing Number Preprocessing table so as to realize the calling/original called number correlation processing.

z

During outgoing number preprocessing procedures, the MSOFTX3000 queries in turn Outgoing Number Preprocessing table, Outgoing Calling Number Correlation Processing table, and Outgoing Original Called Number Correlation Processing

15-54



table. And the final conversion indexes of calling/called/original called numbers are the valid conversion indexes obtained in the last query.

V. Related Commands See Table 15-21 for the commands related to outgoing number preprocessing. Table 15-21 List of commands related to outgoing number preprocessing Command

Description

LST OUTNUMPREPRO

To list outgoing number preprocessing

ADD OUTNUMPREPRO

To add outgoing number preprocessing

MOD OUTNUMPREPRO

To modify outgoing number preprocessing

RMV OUTNUMPREPRO

To remove outgoing number preprocessing

15.7.4 Configuring Trunk Group Bearer Data I. Background Information This command is used to add records to Trunk Group Bearer table. The table is used to set the number conversion index information for outgoing calls, to convert the calling/called numbers related in some calls from certain trunk group, then to route to the peer office by routes selected.

II. Command ADD TGLD

III. Major parameters [Bearer Index] It identifies the records in Trunk Group Bearer table and corresponds to [Bearer Index No.] in Trunk Group Bearer Index table. The MSOFTX3000 uses the corresponding records in Trunk Group Bearer table through [Bearer Index No.] in Trunk Group Bearer Index table. [Trunk Seizure Point] It determines the number of digits of the called number received by the trunk side from the call control block (CCB) before sending Seize message to the next office. [Caller Number Sending Change Index], [Called Number Sending Change Index] These parameters are associated with [Number Conversion Index] in Number Change table. The MSOFTX3000 queries Number Change table through these two parameters to obtain the mode to convert calling/called outgoing numbers. [New Calling Party Cat]

15-55



It redesignates the calling number type to meet the requirements of calling number formats in various countries. The function of this parameter is similar to that of number conversion.

Note: Number conversion in trunk group bearer is carried out over calling/called numbers after the number analysis and routing procedures.

IV. Related Commands See Table 15-22 for the commands related to trunk group bearer. Table 15-22 List of commands related to trunk group bearer Command

Description

LST TGLD

To list trunk group bearer

ADD TGLD

To add trunk group bearer

MOD TGLD

To modify trunk group bearer

RMV TGLD

To remove trunk group bearer

15.7.5 Configuring Trunk Group Bearer Index Data I. Background Information This command is used to add records to Trunk Group Bearer Index table. The table functions in cooperation with Trunk Group Bearer table to process the outgoing numbers involved in some calls to certain trunk group. The MSOFTX3000 queries Trunk Group Bearer Index table according to the trunk group number (obtained through outgoing route selection), the call source code and called number, and obtains the corresponding bearer index number. Then it queries Trunk Group Bearer table through the bearer index number to obtain the processing information of the outgoing number. For outgoing calls, the numbers sent by the local office will be normalized according to the number analysis of the peer office through trunk group bearer data configuration. In this way, the requirements of numebr analysis at the next office can be satisfied.

II. Command ADD TGLDIDX

III. Major parameters [Trunk Group] 15-56



It determines the trunk group to bear the outgoing call. [Call Source] It determines the call source code requiring trunk group bearer conversion. [Call Prefix] The prefix of the called number; that is, it is required to query Trunk Group Bearer table for the call whose called number contains such prefix for further processing. [Call Source Code] and [Call Prefix] together determine the calls to be conducted for trunk group bearer processing. [Bearer Index] It is the result obained after the query of Trunk Group Bearer Index table. The MSOFTX3000 queries Trunk Group Bearer table through this parameter to obtain the detailed information of the trunk group bearer.

IV. Related Commands See Table 15-23 for the commands related to trunk group bearer index. Table 15-23 List of commands related to trunk group bearer index Command

Description

LST TGLDIDX

To list trunk group bearer index

ADD TGLDIDX

To add trunk group bearer index

MOD TGLDIDX

To modify trunk group bearer index

RMV TGLDIDX

To remove trunk group bearer index

15.8 Configuring Other Number Conversion Data 15.8.1 Configuring CLIP Called Correlation Processing Data I. Background Information This command is used to add records to CLIP Called Correlation Processing table. The table is used to normalize the calling numbers to be presented according to called numbers and their attributes. By [Callee Number Correlation Index] obtained from CLIP Processing table, dialed number prefix set, called number, and called address naturer, the MSOFTX3000 queries CLIP Called Correlation Processing table and obtains the calling number conversion index. Then according to the calling number conversion index, it normalizes the calling number to be presented. But note that, the [Callee Number Correlation Index] referenced by CLIP Processing table should have corresponding record in CLIP Called Correlation Processing table and have been configured before being referenced.

15-57



II. Command ADD CLCRPRO

III. Major Parameters [Callee Number Correlation Index] It identifies the records in CLIP Called Correlation Processing table. Through this parameter, the MSOFTX3000 references the corresponding records of this table during the number analysis. [Callee Number Prefix], [Callee Number Address Type] These two parameters determine the relevant attributes of the called subscriber. When CLIP is associated with the called subscriber attribute, the MSOFTX3000 queries CLIP Called Correlation Processing table according to the above attributes and [Callee Number Correlation Index]. If one matched record is found, the MSOFTX3000 will convert the calling number or re-designate the calling number format as specified in this record. Otherwise, it will conduct the next procedure for processing. [Caller Number Change Index], [Designated Caller Number Format] If the system requires the caller number to be displayed in the specified format, just set [Designated Caller Number Format]. If more flexible conversion is required for the caller number, you can first set corresponding conversion data in Number Change table, and then reference Number Change table through [Caller Number Change Index]. In the above CLIP processing, only one conversion mode can be adopted. If there is a conflict in data configuration, the conversion mode with a specified format presides.

Note: This table should be configured only when it is required to normalize the calling number in CLIP according to the calling/called subscriber attributes.

IV. Related Commands See Table 15-24 for the commands related to CLIP called correlation. Table 15-24 List of commands related to CLIP called correlation Command

Description

LST CLCRPRO

To list CLIP called correlation

ADD CLCRPRO

To add CLIP called correlation

MOD CLCRPRO

To modify CLIP called correlation

RMV CLCRPRO

To remove CLIP called correlation

15-58



15.8.2 Configuring CLIP Processing Data I. Background Information This command is used to add records to CLIP Processing table. The calling number is displayed according to the setting of this field. The MSOFTX3000 queries CLIP Processing table according to call source code, calling number, calling number address nature, and calling number length. The MSOFTX3000 will perform the corresponding number conversion over the presentation of the calling number according to the setting of [Caller Number Change Index] or [Designated Caller Number Format] in the record. In addition, when the caller displays the “Callee Number Correlation Index” other than 65535, the MSOFTX3000 will query CLIP Called Correlation Processing table according to the setting of [CLIP Callee Number Correlation Index] in the record to obtain the number normalization information.

II. Command ADD CLIPRO

III. Major Parameters [Call Source Code], [Caller Number Prefix], [Caller Number Address Type], [Caller Number Maximum Length] These parameters determine the relevant attributes of the calling subscriber. The MSOFTX3000 queries CLIP Processing table according to the attributes specified by above parameters. Then it processes (convert the caller number or query CLIP Called Correlation Processing table for processing) the calling number according to the modes defined in the matched record. [Callee Number Correlation Index] It is associated with the “Callee Number Correlation Index” in CLIP Called Correlation Processing table and is used to query records in this table to realize number conversion for the CLIP according to caller/callee numbers. This parameter is valid only when it is set to values other than 65535. “65535” indicates that no callee correlation processing is conducted. [Caller Number Change Index], [Designated Caller Number Format] If the calling number is to be presented in the designated format only, just set [Designated Caller Number Format] accordingly. If the calling number is to be converted more flexibly, it is required to set the corresponding data for the conversion in Number Change table. Then the MSOFTX3000 queries this table through [Caller Number Change Index] and obtains the mode to convert the number. In the above processing over the presentation of calling number, only one mode can be adopted to convert the number. If the data configurations conflict, convert the number by the designated number format.

15-59



Note: This command is used only when the MSOFTX3000 serves as a visited mobile switching center (VMSC). If it is required to normalize the calling number being presented according to the called number and its attributes, the configuration of CLIP called number correlation processing data should be accomplished first.

IV. Related Commands See Table 15-25 for the commands related to CLIP. Table 15-25 List of commands related to CLIP Command

Description

LST CLIPRO

To list CLIP

ADD CLIPRO

To add CLIP

MOD CLIPRO

To modify CLIP

RMV CLIPRO

To remove CLIP

15.8.3 Configuring Auxiliary Number Processing Data I. Background Information This command is used to add records to Auxiliary Number Processing table. The table is used to convert number prefixes according to forwarded-to numbers or connected numbers, or designate number attribute. Data that should be configured for a call originating office and a forwarding originating office are different. When the local office serves as the call originating office, it can be configured with the format control data of connected numbers; while if the call is forwarded at the local office, it needs to configure format control data for forwarded-to numbers.

II. Command ADD AIDNUMPRO

III. Major Parameters [Call Source] The call source code. In terms of connected numbers or forwarded-to numbers from various call sources, the system can conduct processing accordingly through the setting of this parameter. [Number Type]

15-60



It comprises two types of numbers, namely, connected number and forwarded-to number. If the local office has originated the call, set this parameter to "Connected Number"; if the call is forwarded at the local office, set it to "Forwarded-to Number". [Number Prefix] It determines the prefix of the number specified in [Number Type]. The MSOFTX3000 determines the number conversion index according to [Call Source], [Number Type] and this parameter. [Number Conversion Index] It is associated with [Number Conversion Index] in Number Change table and is used to set the number conversions based on call source, number type and number prefix, so as to index Number Change table and realize the format normalization of connected numbers or forwarded-to numbers.

IV. Related Commands See Table 15-26 for the commands related to auxiliary number processing. Table 15-26 List of commands related to auxiliary number processing Command

Description

LST AIDNUMPRO

To list auxiliary number processing data configuration

ADD AIDNUMPRO

To add auxiliary number processing data configuration

MOD AIDNUMPRO

To modify auxiliary number processing data configuration

RMV AIDNUMPRO

To remove auxiliary number processing data configuration

15.8.4 Configuring MAP Interface Number Processing Data I. Background Information This command is used to add records to MAP Interface Number Processing table. If the MSOFTX3000 finds that the called subscriber is a mobile subscriber (whose called number type is "MSISDN") during the number analysis procedures, it will send SRI message to the HLR requesting for the route information of the called (called MSRN information) through MAP interface. This table is used to control the addressing format of the called number before the MAP sends out the SRI message. After the recombination of the called number, it will be addressed to the HLR.

II. Command ADD MAPIFNP

III. Major Parameters [NUMBER PREFIX] 15-61



It defines the prefix of the MSISDN to be converted when this MSISDN is sent to the HLR. [CHANGE ON MAP, SCCP OR SMMO] It is an output parameter, determining the address nature of the MSISDN to be converted. [CHANGE INDEX], [NUMBER FORMAT] These two parameters determine the mode to convert the MSISDN which is defined in [Number Prefix] and [Change on Map, SCCP or SMMO]. Note that only one conversion mode can be adopted for a number at a time; that is, two parameters cannot be set at the same time. If the data configurations of two parameters conflict, convert the number into the designated number format.

IV. Note z

The format of all mobile subscriber numbers have been normalized into international number format during the incoming number pretreatment. So generally, MSISDNs contained in SRI message sent by MAP are of international number format. In this case, the configuration of MAP Interface Number Processing table is no longer necessary.

z

However, if there are different needs for the format of MSISDNs sent to the HLR, such as national number or subscriber number, data in this table should be configured.

V. Related Commands See Table 15-27 for the commands related to MAP interface number processing. Table 15-27 List of commands related to MAP interface number processing Command

Description

LST MAPIFNP

To list MAP interface number processing

ADD MAPIFNP

To add MAP interface number processing

MOD MAPIFNP

To modify MAP interface number processing

RMV MAPIFNP

To remove MAP interface number processing

15.8.5 Configure Bill Processing Information I. Background Information This command is used to add records to Bill Processing table. The table is used to realize the flexible number conversion over numbers on the bill when it is generated, that is, to normalize the numbers to be entered to bills, including calling numbers, called numbers, the third-party numbers, MSRNs and charging MSISDNs. In details, formats 15-62



of numbers on bills can be converted according to bill types, number types, prefixes, maximum length of numbers, and address nature of numbers. And the basic conversion or replacement of numbers are supported. Moreover, the maximum length of numbers entered to bills can be restricted. Therefore, number format requirements of types of bills in different countries can be satisfied.

II. Command ADD BILLPROC

III. Major Parameters [Bill Type], [Number Type], [Number Prefix], [Address Nature], [Input Number Maximum Length] These parameters are used for the MSOFTX3000 to query Bill Processing table so as to determine numbers to be normalized on the bill. [Number Change Index] It corresponds to [Number Change Index] in Number Change table. The MSOFTX3000 will convert the numbers of bill set in [Number Type] field according to this parameter. [Output Number Maximum Length] It determines the maximum length of the number outputted after the conversion. If the length of the number is more than that specified, the MSOFTX3000 will delete the excessive digits automatically.

IV. Related Commands See Table 15-28 for the commands related to bill information processing. Table 15-28 List of commands related to bill information processing Command

Description

LST BILLPROC

To list bill information processing

ADD BILLPROC

To add bill information processing

MOD BILLPROC

To modify bill information processing

RMV BILLPROC

To remove bill information processing

15.8.6 Configuring Bill Control Data I. Background Information This command is used to add records to Bill Control table. The table is used to control the MSOFTX3000 to generate gateway mobile switching center (GMSC) bills and roaming bills for certain office directions.

15-63



When the local office serves as a GMSC, bill control data should be configured for the office direction which is connected with the local office through speech channels if the inter-network settlement is required. In this way, the GMSC can provide bill control information related to this office direction. When the local office serves as a VMSC, it is unnecessary to configure bill control data.

II. Command ADD BILLCTRL

III. Major Parameters [Office Direction] It is used to set the office direction that needs bill control. Through this parameter, the MSOFTX3000 can references the records in Bill Control table. [Opposition Office Type] When it is set as "Other Networks", the MSOFTX3000 will generate roaming bills for incoming calls from this office direction. On the contrary, if it is set to "Home Network", no roaming bill will be generated.

Note: Bill control information must be configured for all non-home network office directions.

IV. Related Commands See Table 15-29 for the commands related to bill control. Table 15-29 List of commands related to bill control Command

Description

LST BILLPROC

To list bill control data configuration

ADD BILLPROC

To add bill control data configuration

MOD BILLPROC

To modify bill control data configuration

RMV BILLPROC

To remove bill control data configuration

15.9 Configuration Examples 15.9.1 Planning of Number Analysis Data Before the configuration of number analysis data, data planning should be accomplished first. The planning comprises two parts: One is to determine call prefix 15-64



data, that is, to select outgoing routes according to certain call prefixes; the other is to determine call special processing data, including normalization of irregular numbers, intercept of certain calls, or other special processing. The following takes China as the example to detail the planning of number analysis data.

15.9.2 Planning of Call Prefix Data I. VMSC Call Prefix Data Most of the prefix data configured for VMSCs are consistent except those configured to meet certain special requirements, as shown in Table 15-30. Table 15-30 VMSC call prefix data configuration Route Selection Code

Call Prefix

Service Attribute

0

International toll prefix

International toll

0

National toll prefix

National Toll

GMSC

0

1

Local

0

2

0

DN Set

Minimum Number Length

Called Number Type

Description of other parameters

PSTN

Set [Query Toll Area Code table] to "Yes", [Toll Prefix Length] to "2", and [Gain] to "Toll Gain".

6

PSTN

Set [Query Toll Area Code table] to "Yes", [Toll Prefix Length] to "1", and [Gain] to "Toll Gain".

GMSC

3

PSTN

Local

GMSC

3

PSTN

3

Local

GMSC

3

PSTN

0

4

Local

GMSC

3

PSTN

0

5

Local

GMSC

3

PSTN

0

6

Local

GMSC

3

PSTN

0

7

Local

GMSC

3

PSTN

0

8

Local

GMSC

3

PSTN

0

9

Local

GMSC

3

PSTN

0

Local MSISDN number segment

PLMN Local MSCs

65535

11

MSISDN

0

National Roaming MSIDSN number segment

PLMN National Toll MSC

65535

11

MSISDN

GMSC

6

15-65



Route Selection Code


Called Number Type

Call Prefix

Service Attribute

0

Local office MSRN prefix

PLMN Home MSC

65535

11

MSRN/HO N

0

MSRN prefix of VMSC connecting with local office directly

PLMN Local MSC

VMSC

11

MSRN/HO N

0

National MSRN prefix


TMSC

11

MSRN/HO N

0

Police emergency call/ambulan ce call/fire emergency call number

Local

GMSC

Length of fire call number

PSTN

0

Other special service number

Local

GMSC/TMS C

Length of special service number

PSTN

0

IP call prefix

Local Toll

TMSC/IP front end processor

IP call prefix length

PSTN

9

PLMN international toll prefix

PLMN Intl Toll MSC

GMSC

13

MSRN/HO N

DN Set


Set [Emergency Call Observation] to "Yes" and [Charging] to "No Chanrging".

Note: z

Table 15-30 contains only the basic call prefix data, excluding those data of call configured for special processing and particular requirements of offices.

z

GMSC, TMSC, etc. listed in [Route Selection Code] respectively stand for the route selection codes corresponding to specific office directions.

z

National roaming MSIDSN number segment refers to the national universal roaming number segment used by operators.

II. GMSC Call Prefix Data Most of the prefix data configured for GMSCs are consistent except those configured to meet certain special requirements, as shown in Table 15-31.

15-66



Table 15-31 GMSC call prefix data configuration DN Set

0

Call Prefix

International toll prefix

toll

Service Attribute


International toll

PSTN gateway exchange (TMSC for remote access and PSTN for local access, mostly TMSC)

National Toll

PSTN gateway exchange (TMSC for remote access and PSTN for local access, mostly TMSC)


Number Type


PSTN

Set [Query Toll Area Code table] to "Yes" and [Gain] to "Toll Gain". Set international toll prefix based on actual conditions.

6

PSTN

Set [Query Toll Area Code table] to "Yes" and [Gain] to "Toll Gain". Set national toll prefix based on actual conditions

6

0

National prefix

0

1

Local

PSTN gateway exchange

3

PSTN

0

2

Local


3

PSTN

0

3

Local


3

PSTN

0

4

Local


3

PSTN

0

5

Local


3

PSTN

0

6

Local


3

PSTN

0

7

Local


3

PSTN

15-67


DN Set

Call Prefix

Service Attribute




Number Type

0

8

Local


3

PSTN

0

9

Local


3

PSTN

Length of fire call number

PSTN

0

Fire alarm call

Local


0

National toll prefix + Local area code + 1

Local


3

PSTN

0


Local


3

PSTN

0


Local


3

PSTN

0


Local


3

PSTN

0

National toll prefix + local area code + 5

Local


3

PSTN

0


Local


3

PSTN

0


Local


3

PSTN

0


Local


3

PSTN

0


Local


3

PSTN

0

Local MSISDN number segment

PLMN Local MSC

65535

11

MSISDN

15-68


Set [Emergency Call Observation] to "Yes", and [Charging] to "No Charging".


DN Set

Call Prefix

Service Attribute




Number Type

0

National roaming MSIDSN number segment


65535

11

MSISDN

0

MSRN prefix (MSC No.) of VMSC connecting local office directly

PLMN Local MSC

VMSC

11

MSRN/HO N

0

National roaming prefix


TMSC

11

MSRN/HO N

0

National toll prefix + local area code + police emergency call/ambulanc e call/fire emergency call nmber


National toll prefix length + local area code length + fire alarm number length

PSTN

Special service number length + National toll prefix length + Local area code length

PSTN

Local

0

National toll prefix + Local area code + special service number

Local

PSTN gateway exchange/T MSC

0

IP call prefix

Local Toll

TMSC/IP front end processor

IP call prefix length

PSTN

9

PLMN international toll prefix

PLMN Intl Toll MSC


13

MSRN/HO N

15-69


Set [Emergency Call Observation] to "Yes", and [Charging] to "No Charging".



Note: z

Table 15-31 contains only the basic call prefix data in GMSC, excluding those configured for call special processing and for particular requirements of offices.

z

In Table 15-31, GMSC, TMSC, etc. given in [Route Selection Code] respectively stand for the route selection codes corresponding to specific office directions.

z

In Table 15-31, there are two modes available to process the prefixes of PSTN local calls (including emergency calls). One is to configure call prefix with local area code as called numbers of PSTN local calls from both VMSC and TMSC have contained local area code. The other is to configure call prefixes without local area codes in case called numbers of PSTN local calls from TMSC or VMSC contain no local area codes, or the codes have been deleted (the deletion is controlled by software parameters) from the forwarded-to numbers.

z

National roaming MSIDSN number segment refers to the national universal roaming number segment.

15.9.3 Planning of Call Special Processing Data I. Configuration Principles Besides basic routing data of call prefixes, call special processing data are important for the number analysis data configuration. Therefore, certain processing principles should be mastered so as to ensure the correctness and standard of the configuration. Table 15-32 lists the basic principles for call special processing data configuration: Table 15-32 Call special processing configuration principles Call processing requirements

Data configuration

Normalize incoming forwarded-to numbers

If the forwarded-to numbers are required to be normalized according to the original called attributes during incoming number pretreatment data configuration, configure incoming original called number correlation processing data first, and then configure incoming number pretreatment data.

Normalize forwarded-to numbers, redirecting numbers and connected numbers after their outgoing route selection (forwarded-to numbers are contained in the forwarded-to notification messages sent to the caller, redirecting numbers are contained in SETUP messages sent to the trunk side).

Normalize forwarded-to numbers, connected numbers and redirecting numbers accordingly during auxiliary number analysis data configuration.

Select different routes for call prefixes in terms of various call types.

Configure corresponding route selection codes in terms of various call types (basic all and forwarded call) during the enhanced route processing data configuration.

Select different routes in terms of various call prefix length.

Configure corresponding route selection codes in terms of various call prefix length during enhanced route processing data configuration.

15-70



Call processing requirements

Data configuration

Intercept calls in which the format of the numbers dialed are incorrect.

Set corresponding interception data according to the called party and corresponding failure processing data during call authority check data configuration.

Allow subscribers, who have been prohibited from originating calls, to make special service calls, for example, emergency call.

Set not to conduct service check over barring service in service check configuration. And configure corresponding service check indexes for special service call prefixes in call prefix configuration.

Realize number-receive delay at the local office for incoming numbers from other offices.

Set number-receive delay interval in Call Source table.

Realize number-receive delay based on certain call prefix.

Set number-receive delay interval in incoming number pretreatment data configuration.

Select routes right after converting called numbers.

Configure corresponding conversion data for called numbers in DN processing data configuration.

Convert call prefixes and then reselect routes through converted prefixes.

Convert corresponding called numbers and set [Reanalyze] to "True" during DN processing data configuration.

Normalize calling numbers (calling numbers being presented, outgoing calling numbers and calling numbers in bills are all determined by normalized numbers).

Normalize calling numbers accordingly during calling number analysis data configuration.

Normalize calling/called/original numbers of outgoing calls.

Normalize calling/called/original called numbers accordingly during outgoing number preprocessing data configuration. If the normalization should be carried out by calling features, configure outgoing calling number correlation processing data first; if the normalization should be conducted through original called subscriber attributes, configure outgoing original called number correlation processing data first.

called

Normalize calling numbers being presented.

If it is required to normalize calling numbers being displayed according to called prefixes, configure CLIP called number correlation processing data first.

15.9.4 Examples of Call Special Processing Data Configuration I. Requiring PSTN Subscriber to Dial National Toll Prefix "0" to Connect a Foreign Mobile Subscriber at GMSC [Requirement Analysis]: It is required to conduct call authority check configuration to determine the format of numbers dialed by subscribers. However, if the dialed number is "0+MSISDN", the MSOFTX3000 cannot obtain the corresponding MSRN through the number of this format. Therefore, it is required to configure DN processing data so as to delete "0" through DN processing and then re-analyse the number. [Realization Script Example]: /* In the script, PSTN subscriber is required to dial "0" to connect a foreign MS at the GMSC of certain mobile operator in China. Suppose call source code related to this

15-71



PSTN subscriber is 7, local MSISDN number segment comprises "139111", "139222", …, local PPS number segment comprises "138111", "139222", … */ /* To intercept calls to a foreign MS, the MSOFTX3000 will connect calls in which the local mobile subscriber number segment is dialed, but intercept those in which the universal MSISDN number segment is dialed. Therefore, during the configuration of corresponding data, besides the configuration of local MSISDN and PPS number segment, that of national universal MSISDN special service numbers should be accomplished.*/ /*Set call authority check over local MSISDN number segment. The processing type is "Continue Proceeding".*/ ADD

CALLPRICHK:

CSC=7,

CALLTY=COMMON,

PFX=K'139111,

CPFX=K'eeeeeeee, CLITP=ALL, CLIRP=ALL, PROCTY=PASSON; ADD

CALLPRICHK:

CSC=7,

CALLTY=COMMON,

PFX=K'139222,

CPFX=K'eeeeeeee, CLITP=ALL, CLIRP=ALL, PROCTY=PASSON; …………………………

/* Set call authority check over local PPS number segment. The pocessing type is "Continue Proceeding".*/ ADD

CALLPRICHK:

CSC=7,

CALLTY=COMMON,

PFX=K'138111,


CALLPRICHK:

CSC=7,

CALLTY=COMMON,

PFX=K'138222,

CPFX=K'eeeeeeee, CLITP=ALL, CLIRP=ALL, PROCTY=PASSON; ……………………. /*Set call authority check over national universal MSISDN special numbers of this mobile operator. The processing type is "Continue Proceeding" */ ADD

CALLPRICHK:

CSC=7,

CALLTY=COMMON,

PFX=K'13800138000,


CALLPRICHK:

CSC=7,

CALLTY=COMMON,

PFX=K'13800138007,

CPFX=K'eeeeeeee, CLITP=ALL, CLIRP=ALL, PROCTY=PASSON; /*Set call authority check over other national universal MSISDN number segment of the mobile operator. Processing type: Prohibit. Failure cause code: UD13 ("0" is not added when dialing a foreign mobile subscriber) */ ADD CALLPRICHK: CSC=7, CALLTY=COMMON, PFX=K'135, CPFX=K'eeeeeeee, CLITP=ALL, CLIRP=ALL, PROCTY=INHIBITED, FCC=UD13; ADD CALLPRICHK: CSC=7, CALLTY=COMMON, PFX=K'135, CPFX=K'eeeeeeee, CLITP=ALL, CLIRP=ALL, PROCTY=INHIBITED, FCC=UD13; ADD CALLPRICHK: CSC=7, CALLTY=COMMON, PFX=K'136 CPFX=K'eeeeeeee, CLITP=ALL, CLIRP=ALL, PROCTY=INHIBITED, FCC=UD13;

15-72



ADD CALLPRICHK: CSC=7, CALLTY=COMMON, PFX=K'137, CPFX=K'eeeeeeee, CLITP=ALL, CLIRP=ALL, PROCTY=INHIBITED, FCC=UD13; ADD CALLPRICHK: CSC=7, CALLTY=COMMON, PFX=K'138, CPFX=K'eeeeeeee, CLITP=ALL, CLIRP=ALL, PROCTY=INHIBITED, FCC=UD13; ADD CALLPRICHK: CSC=7, CALLTY=COMMON, PFX=K'139, CPFX=K'eeeeeeee, CLITP=ALL, CLIRP=ALL, PROCTY=INHIBITED, FCC=UD13; /*Play an announcement for a failed call whose failure cause code is "UD13" (Calling party did not dial "0" when calling a foreign MS)*/ ADD CFPRO: FCC=UD13, RUT=ALL, RMT=ALL, CSA=ALL, FPT=SIG, TT= ADD0; /*Configure call prefix data and conduct DN processing for the national universal MSISDN number segments with toll prefix "0" of this mobile operator, such as 0135, 0136, 0137, 0138, 0139. But route selection will not be carried out. */ ADD CNACLD: P=0, PFX=K'0135, CSTP=BASE, CSA=MNTT, RSC=65534, MINL=12, MAXL=15, ICLDTYPE=MS; MOD CNACLD: P=0, PFX=K'0135, DNPREPARE=TRUE; ADD CNACLD: P=0, PFX=K'0136, CSTP=BASE, CSA=MNTT, RSC=65534, MINL=12, MAXL=15, ICLDTYPE=MS; MOD CNACLD: P=0, PFX=K'0136, DNPREPARE=TRUE; ……………………. /* Configure DN processing data for number segments like 0135, 0136, 0137, 0138, 0139. Delete "0" before each number segment and then re-analyse these numbers. */ ADD DNC: DCX=10, DCT=TYPE6, DCL=1, DAI=NONE; ADD PFXPRO: CSC=7, CS=ALL, P=0, PFX=K'0135, CLDNCX=10, STF=NSDT, PT=REANA; ADD PFXPRO: CSC=7, CS=ALL, P=0, PFX=K'0136, CLDNCX=10, STF=NSDT, PT=REANA; ………………….

II. Requiring Local Office Mobile Subscriber Not to Dial National Toll Prefix (Supposed as "0") before Called Number to Connect a Mobile Subscriber [Requirement Analysis]: It is required to conduct call authority check data configuration to determine the format of numbers dialed by subscribers. [Realization Script Example]: /* Call source code of the call from this local mobile subscriber is "0".*/ /*Set call authority check over national universal MSISDN number segment. Processing Type: Prohibit. Failure cause code: CS0 */ ADD CALLPRICHK: CSC=0 CALLTY=COMMON, PFX=K'0135, CPFX=K'eeeeeeee, CLITP=ALL, CLIRP=ALL, PROCTY=INHIBITED, FCC= CS0; 15-73



...... /* Set playing of announcement "No 0 should be added before the local mobile number you dialed" when the failure cause code is "CS0 (Cause Value 96). */ ADD CFPRO: FCC=CS0, FSC=0, RUT=ALL, RMT=ALL, CSA=ALL, FPT=SIG, TT=NODSTRB;

III. Requiring MSOFTX3000 to Normalize MSRNs to the Format "International Toll Prefix (Supposed as “00”) + International Number" [Requirement Analysis]: The GSM network of a company requires that MSRNs transmitted among networks should be of the format "International toll prefix (for example, 00) + International number". However, the MSRNs returned from the HLR are of international number format. In this case, the MSOFTX3000 will automatically add the international number prefix beofore international MSRNs and convert national MSRNs into national numbers through trunk group bearers. The conversion is done in the outgoing number preprocessing mode. In addition, when the local office serves as a VMSC, it will convert such local MSRNs sent from other offices into national numbers and then re-analyse them. Thus the call to PLMN Home MSC subscriber can be connected. [Realization Script Example]: /* The No. of a local MSOFTX3000 in China is 13000222. The MSOFTX3000 is connected directly with a VMSC (No. 13000111) only. Trunk group Nos are 10 and 11. Nos of trunk groups from the local MSOFTX3000 to TMSC are 12 and 13. So there are 4 call sources that obtain route information from the local office, numbered respectively as 1, 2, 3 and 4.*/ ADD DNC: DCX=4, DCT=TYPE1, DCP=0, ND=K'0086; ADD

OUTNUMPREPRO:

CSC=65534,

TG=11,

P=254,

PFX=K'13000111,

CSC=65534,

TG=10,

P=254,

PFX=K'13000111,

CSC=65534,

TG=12,

P=254,

PFX=K'13000111,

CSC=65534,

TG=13,

P=254,

PFX=K'13000111,

CLDADDR=ALL, DDX=4; ADD

OUTNUMPREPRO:


OUTNUMPREPRO:


OUTNUMPREPRO:

CLDADDR=ALL, DDX=4; /*Re-analyse VMSC local numbers after the DN processing*/ ADD DNC: DCX=5, DCT=TYPE6, DCL=4; ADD CNACLD: P=0, PFX=K'008613000222, CSTP=BASE, CSA=MSLO, MINL=11, MAXL=18, CLDT=MSRN; MOD CNACLD: P=0, PFX=K'008613000222, ADDSIG=TRUE, CLIANA=FALSE;

15-74



ADD PFXPRO: CSC=65534, CF=ALL, P=0, PFX="008613000222", NP=0, CLDNCX =5, PT=REANA;

IV. Requiring VMSC to Allow Subscriber Being Barred to Make Emergency Calls (such as 110, 122, 119) [Requirement Analysis]: To satisfy this requirement, the MSOFTX3000 is required not to conduct corresponding service check when such call prefixes are dialed; that is, configure corresponding service check data to disable call barring service for certain subscribers, then configure corresponding service check indexes for such call prefixes during call prefix data configuration. [Realization Script Example]: ADD

SRVCHK:

CSC=65534,

SCI=0,

IFSC=YES,

SCC=ODB_BAOC-0&BAOC-0&ODB_BOIC-0, SCM=ODBBAOC-1&BAOC-1&ODBBOIC-1; ADD CNACLD: P=0, PFX=K'110, CSA=LC, RSC=2, MINL=3, MAXL=15, ICLDTYPE =PSTN, SCIDX=0; ADD

CNACLD:

P=0,

PFX=K'120,

CSA=LC,

RSC=2,

MINL=3,

MAXL=15,

ICLDTYPE=PS, ISERVICECHECKINDEX= =0; ADD CNACLD: P=0, PFX=K'122, CSA=LCT, RSC=2, MINL=3, MAXL=15, ICLDTYPE =PSTN, ISERVICECHECKINDEX =0; ADD CNACLD: P=0, PFX=K'119, CSA=LCT, RSC=2, MINL=3, MAXL=15, ICLDTYPE =PSTN, ISERVICECHECKINDEX =0;

15-75


Chapter 16 Configuring Mobile Service Data

Chapter 16 Configuring Mobile Service Data 16.1 Introduction to the Chapter Mobile service data provides mobility management function performed on mobile subscribers of the local office and those who are roaming to the local office. This chapter contains the following sections: z

Related Concepts

z

Configuring Location Update Data

z

Configuring Enhanced Roaming Restriction Data

z

Configuring Roaming Zone Code Service

z

Configuration Examples

16.2 Related Concepts I. Location Area, Cell, Service Area Location area refers to a covering scope where mobile subscribers can roam. If a subscriber roams from one cell to another cell (within the same location area), new location update is not required. A location area is divided into several cells. When a mobile subscriber is called, a paging message will be sent to all the base stations within a location area. Base station identity code (BSIC) or cell global identification (CGI) is used to identify a radio covering region of GSM. A cell is a base station area when omni-directional antenna is used. Service area identifier (SAI) is used to uniquely identify the coverage of one or more cells in one location area in wideband code division multiple access (WCDMA).

II. Roaming Services Roaming services include VLR list based on roaming restriction, zone code based on roaming area restriction, and enhanced roaming restriction. z

Roaming restriction based on VLR list

VLR list is the subscription data of a mobile subscriber in HLR. The data defines a subscriber’s roaming scope that is based on VLR serving coverage. This roaming restriction can be achieved in HLR. A mobile subscriber registers permitted roaming VLR list when the subscriber is defined in HLR. A mobile subscriber will be roaming restricted if the mobile subscriber is roaming in a VLR, which is not included in the VLR list. It is only required to configure data in HLR, instead of in MSC.

16-1



Roaming area restriction based one zone code

z

Zone code is subscription data of a subscriber in HLR. The data can restrict roaming area of the mobile subscriber. Customized location areas covered by a zone code can be defined in MSC, so that cooperation between MSC and HLR makes it possible to flexibly specify location scope allowed for the mobile subscriber to roam. Enhanced roaming restriction

z

Enhanced roaming restriction service is one of special services provided by the product. It is possible for MSC to independently provide LAI based roaming restriction function for particular user group without help of HLR.

III. Location Service Location service (LCS) refers to handling procedures where the mobile communication system originates a request for providing location of a mobile subscriber, performs location measurement and calculation, and transfers location outcome. See Figure 16-1 for the structure of the LCS system in 3GPP.

CBC Note 1)

{LMU Type A}

Uu

HLR

{3GSGSN }

Iu BC

Lh Node B

Iub

{(LMU Type B)}

UE

SRNC (SMLC functionality) Iur

Node B {(LMU

Iub RNC

Iu

3G MSC Server

Lg

Le

Lg GMLC

External LCS client

Lc

GMLC

Type B)}

gsmSCF Other PLMN

Figure 16-1 LCS system structure in 3GPP The external LCS Client is responsible for specific services. When location information of a mobile subscriber is needed, the request is originated to GMLC through the Le interface. There is not a direct association between LCS Client service procedures and the LCS system. GMLC is the gateway for LCS Client to access the network. GMLC is responsible for LCS Client authorization, subscriber authentication, and local geographical change according to the longitude and latitude. The external LCS Client originates location request to MSC through GMLC. MSC can also report location information to LCS Client through GMLC. 16-2



Networking model between MSOFTX3000 and GMLC is shown in Figure 16-2.

Lg

MSOFTX 3000

GMLC

Le

External LCS Client

MAP Protocol stack structure

TCAP SCCP MTP3

Figure 16-2 Networking between MSOFTX3000 and GMLC

IV. MSISDN Numbering Principles MSISDN is mobile subscriber international ISDN number which is used to call a mobile subscriber by dialing it. They are allocated from recommendation E.164 numbering format. It is stored in HLR and conveyed on the MAP interface to VLR. Its structure is shown in Figure 16-3.

CC

NDC SN National (significant) Mobile number Mobile station international ISDN number

Figure 16-3 MSISDN structure CC: country code. For example, the country code of China is 86. NDC: national destination code. SN: subscriber number. A subscriber number consists of the following parts: z

HLR identification number: H0H1H2H3

z

Mobile subscriber number: ABCD, allocated by respective HLR.

The general format for MSISDN is “CC-NDC-H0H1H2H3-ABCD”.

V. LAI Numbering Principles LAI is used to identify the VLR serving coverage where a roaming subscriber is residing currently. It is a paging area in WCDMA system. The LAI structure is shown in Figure 16-4.

16-3

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center MCC


MNC

LAC

Location Area Identification Figure 16-4 LAI structure MCC: mobile country code. For example, the mobile country code of China is 460. MNC: mobile network code. Hexadecimal location area code (LAC) of two bytes presents itself as X1X2X3X4. X1X2 is globally allocated by the telecommunication administration authorities. X3X4 is customized by the serving operator. Note that neither 0000 nor FFFE can be used. The SAI is used to identify an area consisting of one or more cells belonging to the same location area. The service area code (SAC) together with the PLMN-ID and the LAC will constitute the SAI. SAI = PLMN-ID + LAC + SAC The cell identification (CI) is of two bytes represented in Hex and can be customized in respective MSC. CI must be unique within a location area.

VI. MSC/VLR Numbering Principles E.164 numbering plan is used for MSC/VLR numbers. The format is “CC+NDC+LSP”. In this numbering plan, CC and NDC are the same as those defined in MSISDN. LSP is customized by the serving operator and the national numbering authority in the PLMN's country. It is used in SS7 signaling messages for the purposes of representing MSC number. Currently MSC and VLR are physically integrated together. MSC-Number is basically the same as VLR-Number.

16.3 Configuring Location Update Data 16.3.1 General Configuration Procedures The procedures for configuring location update data are as follows: 1)

Add LAI or CGI/SAI data (ADD LAIGCI or ADD LAISAI).

2)

Add IMSI-GT data (ADD IMSIGT).

3)

Add GT data (ADD SCCPGT).

4)

Add SCCP subsystem data (ADD SCCPSSN).

16-4



16.3.2 Setting LAI or CGI/SAI I. Background Information None.

II. Command ADD LAIGCI or ADD LAISAI.

Note: MSC number is already defined in the SET INOFFMSC command. For more information about this command, refer to Chapter 5, “Configuring Data for Interworking with RNC” or Chapter 6, “Configuring Data for Interworking with BSC”.

III. Related Commands None.

16.3.3 Setting Global Title Table I. Background Information This section describes how to establish mapping relationship between mobile country code + mobile network code and country code + mobile access code, so that HLR can be found according to subscriber's IMSI. Mobile access code is actually the national destination code.

II. Command ADD IMSIGT

III. Major Parameters [MCC + MNC] It refers to mobile country code + mobile network code. Mobile country code is used to identity the country to which the mobile subscriber belongs. Mobile network code is used to identify the mobile network to which the mobile subscriber belongs. [CC + NDC] It refers to country code + national destination code. The data is contained in the address information field of the global title.

IV. Related Commands None.

16-5



16.3.4 Setting SCCP GT I. Background Information Global titles of both local MSC and HLR must be set in MSOFTX3000 for the purposes of addressing. You have to configure the following data: z

Global title of HLR obtained according to IMSI, used to look for the corresponding HLR during location update.

z

Global title of HLR obtained according to the called MSISDN, used to look for the corresponding HLR during routing information provision procedure triggered by called number analysis.

z

Global title of the local MSC.

II. Command ADD SCCPGT

III. Major Parameters [GT Index] It identifies a GT code uniquely. [NI] Set this parameter to “NATIONAL NETWORK”. It is associated with the parameter in the ADD SCCPSSN command. [GT Indicator] In the mobile network, select GT4(TYPE4)”. [Translation Type] The default value “00” is used in the mobile network. [Numbering Plan] Set this parameter to “ISDNMOV (ISDN/mobile numbering plan)” for the GT mentioned in 1). Set it to “ISDN (ISDN/telephony numbering plan)” for the GT mentioned in 2) and 3). [GT address information] This field accommodates the specific address information. For the GT mentioned in 1), it is the same as “CC+NDC” in ADD IMSIGT command. For the GT mentioned in 2), set this parameter to the prefix at the front of the called MSISDN. For the GT mentioned in 3), set this parameter to MSC/VLR number which is already defined in the SET INOFFMSC command. [Translation Result Type]

16-6



Global title of local office SCCP users is translated to “DPC”. The GT translation result, DPC, must be configured in the SCCP DSP table (using LST SCCPDSP for query) or in the local office information table (using LST INOFFMSC for query). The general configuration principles are described as follows: z

Set “Translation result type” to “SPC + OLD GT” or “SPC + NEW GT” if signaling is transferred by STP, whereas set it to “SPC” if there is a directly associated link to carry signaling.

z

The calls from the local office to the MSC/HLR in the same province or in a different province are addressed through “SPC + OLD GT” or “SPC + NEW GT” and transferred by STP. It is unnecessary to set the MTP routing data.

z

As GMSC location update does not happen here, it is unnecessary to configure IMSI data. However, for VMSC, IMSI must be configured and it is also required to configure the global title of the adjacent VMSC for the purposes of handover.

IV. Related Commands See Table 16-1 for the commands related to SCCP GT configuration. Table 16-1 List of commands related to SCCP GT configuration Command

Description

ADD SCCPGT

To add SCCP global title

RMV SCCPGT

To remove existing SCCP global title

MOD SCCPGT

To modify existing SCCP global title

LST SCCPGT

To list SCCP global title

16.3.5 Setting Local Office SCCP Subsystem I. Background Information When MSOFTX3000 functions as GMSC, it is required to configure SCCP subsystems relating to MSC and HLR for location update procedure. The data might be already configured as part of the local office information. Use the LST SCCPSSN command to have a check to avoid repeated work.


III. Major Parameters [SSN Index] It specifies the unique number of the SCCP subsystem. [Network Indicator] 16-7



Network indicator identifies the network where the SCCP subsystem is resident. Usually set this parameter to “NAT(National Network)” for MSC and HLR. [SPC][ OPC] SPC and local OPC are set for the local office in the national network for related subsystems of MSC. The codes are already defined in the SET OFI command. For related subsystems of HLR, SPC is the point code of HLR; OPC is the point code of MSC used in the national network. [Local Concerned SSN1]–[Local Concerned SSN5] Default values are used as there are no related subsystems. [Backup SSN Index] It is used to specify the index of the backup subsystem of the specified subsystem. It is valid only when MSOFTX3000 supports the load sharing function or backup function of SCCP DSP. Default value is used as there are no backup subsystems.


Description

ADD SCCPSSN


RMV SCCPSSN


MOD SCCPSSN


LST SCCPSSN


SET SCCPSSN

To set SCCP subsystem status for maintenance purpose

DSP SCCPSSN

To display SCCP subsystem of the host

16.4 Configuring Enhanced Roaming Restriction Data 16.4.1 Configuration Description The example for 2G-MSC enhanced roaming restriction is as follows. In 3G enhanced roaming restriction, only setting LAISAI (using the ADD/MOD LAISAI command) is different from 2G. The relationship between the parameters of the commands of enhanced roaming restriction is shown in Figure 16-5.

16-8



ADD LOCGRP

ADD USROAMRT

[Location No.]

[Roaming Restriction]

[Location Group No.]

[Location Group No.]

...

[User Group No.]

ADD LAIGCI

ADD ROAMRESTGRP

[Global Cell ID]

[Restricted By]

[Location No.]

[Start User Number]

[Perform Roaming

[End User Number]

Analysis]

[User Group No.]

[LA Category] ...

[Roaming Subscriber Type]

MOD MAPACCFG ADD ROAMUSRTP

[Use Enhanced Roaming Restrict]

[IMSI Prefix]

...

[Roaming Subscriber Type]

Figure 16-5 Parameter relationship of Enhanced roaming restriction The parameters displayed in the figure must be configured, and the configuration procedures are as follows: 1)

Group LAIs according to “Location Group No.”, implemented by the commands in the left column in Figure 16-5 (used to set location number to LAI, define the relationship between location number and location group number, and open the enhanced roaming restriction function to special LAI ).

2)

Group the user groups according to some common characters through “User Group No.”, implemented by the lower two commands in the right column in Table 16-5.

3)

Associate “User Group No.” with “Location Group No.” by the command ADD ROAMUSRT, to implement special user group roaming in special LAIs.

There are two conditions for grouping users: z

When “MSISDN” or “IMSI” is specified for the parameter “Restricted by” with the command ADD ROAMRESTGRP, user groups will be divided through “Start User Number” and “End User Number”.

z

When “Roaming Subscriber Type” is specified for the parameter “Restricted by” with the command ADD ROAMRESTGRP, the command ADD ROAMUSRT must be used to confirm the IMSI number segment through “Roaming Subscriber Type”.

16-9



The parameter “Use Enhanced Roaming Restrict” in the command MOD MAPACCF controls roaming restriction to all location areas in the local office, while the parameter “Perform Roaming Analysis” in the command ADD/MOD LAIGCI controls roaming restriction to one special location area. For instance, to implement roaming restriction to all LAIs except LAI1, you can select “Yes” for the parameter “Use Enhanced Roaming Restrict” in the command MOD MAPACCFG, and then select “No” for the parameter “Perform Roaming Analysis” in the command ADD/MOD LAIGCI.

16.4.2 Starting Enhanced Roaming Restriction Function I. Background Information This section describes how to enable MSC to support enhanced roaming restriction services.


III. Major Parameters [Use Enhanced Roaming Restrict] Set this parameter to YES if the enhanced roaming restriction services of an MSC are expected.

Important Note: This step is not required if “Use Enhanced Roaming Restrict” in MAP information is already set to YES. This parameter controls roaming restriction to all location areas in the local office.

16.4.3 Configuring LAI Grouping Information I. Background Information This section describes how to add LAI grouping information. Different location numbers can belong to the same location group.

II. Command ADD LOCGRP

III. Major Parameters [Location No.]

16-10



Location number identifies the LAI. When adding LAI, use enhanced roaming restriction to the special LAI through location number. [Location Group No.] Location group number identifies the LAI grouping information. One or more LAIs can share one location group number. [Zone Code] Zone code identifies the LAI code. Configure it if the zone code roaming restriction service is expected. This parameter is not necessary in enhanced roaming restriction data configuration. You can input “65535”.

IV. Related Commands See Table 16-3 for the commands related to LAI grouping information configuration. Table 16-3 List of commands related to LAI grouping information configuration Command

Description

MOD LOCGRP

To modify LAI grouping information

RMV LOCGRP

To remove LAI grouping information

LST LOCGRP

To list LAI grouping information

16.4.4 Configuring LAI I. Background Information None.

II. Command ADD/MOD LAIGCI

Note: This command is used to configure location area, and the "LA Category" must be set to LAI.

III. Major Parameters [Perform Roaming Analysis] Roaming analysis is performed to the special LAI, This parameter is set to YES if the LAI is required with roaming restriction. [LA Type]

16-11



This parameter is used to decide whether the current LAI belongs to local VLR or adjacent VLR. The LAI of the local MSC/VLR is marked "HVLR" and the location area of non-local MSC/VLR is marked as "NBVLR". Here, set it to "HVLR". [LA Category] Roming restriction is performed only to LAI, so set this parameter to "LAI" only. [Location No.] It is the indicator corresponding to a location area, and it is used for roaming restriction and to group multiple location areas into different location groups. It is related to the parameter “Location No.” in the command ADD LOCGRP. If the LAI is already added, you can only use the command MOD LAIGCI to set the parameters “Perform Roaming Analysis” and “Location No.”.

IV. Related Commands See Table 16-4 for the commands related to LAI/GCI configuration. Table 16-4 List of commands related to LAI/CGI configuration Command

Description

ADD LAIGCI

To add LAI or CGI

MOD LAIGCI


LST LAIGCI

To list LAI or CGI

RMV LAIGCI

To remove LAI or CGI

16.4.5 Configuring Roaming Restriction User Group I. Background Information This section describes how to add a roaming restriction user group. You can set roaming restriction to a specific number segment based on user group.

II. Command ADD ROAMRESTGRP

III. Major Parameters [Restricted By] Roaming restriction user group can be grouped based on IMSI, MSIDSN, or roaming user type. [Start User Number]

16-12



When the parameter “Restricted By” is set to “IMSI” or “MSIDSN”, this parameter is used to set the start user number of the number segment for roaming restriction purposes. It is necessary to enter the whole number with the country code. [End User Number] When the parameter “Restricted By” is set to “IMSI” or “MSIDSN”, this parameter is used to set the end user number of the number segment for roaming restriction purposes. It is necessary to enter the whole number with the country code. [User Group No.] This parameter is used to set the user group number. The same user group number accommodates subscribers with the same roaming restriction attribute. [Roaming Subscriber Type] When the parameter “Restricted by” is set to “Roaming Subscriber Type”, select the classification of different subscriber roaming in the local MSC.

IV. Related Commands See Table 16-5 for the commands related to the configuration of roaming restriction user group. Table 16-5 List of commands related to the configuration of roaming restriction user group Command

Description

MOD ROAMRESTGRP

To modify roaming restriction user group

RMV ROAMRESTGRP

To remove roaming restriction user group

LST ROAMRESTGRP

To list roaming restriction user group

16.4.6 Configuring Roaming Subscriber Type I. Background Information None.

II. Command ADD ROAMUSRT

16-13



III. Major Parameters

Important Note: When selecting “Roaming Subscriber Type” for the parameter “Restricted by” in the command ADD ROAMRESTGRP, you need to set the command ADD ROAMUSRT. Define the IMSI number segment through “Roaming Subscriber Type”.

[IMSI Prefix] This parameter is the international mobile subscriber identity prefix. It is a 15-bit exclusive number in the digital PLMN to identify an MS. Here you can enter proper bits as required. [MSC Number] It specifies the number of the local MSC. [Roaming Subscriber Type] Classify different subscriber roaming in the local MSC. There are five types of roaming users: local MS, national HPLMN MS, international HPLMN MS, national inter-work MS, and international inter-work MS. This parameter is related to the parameter “Roaming Subscriber Type” in the command ADD ROAMRESTGRP.

IV. Related Commands See Table 16-6 for the commands related to the configuration of roaming subscriber type. Table 16-6 List of commands related to the configuration of roaming subscriber type Command

Description

MOD ROAMUSRT

To modify user group roaming authority

RMV ROAMUSRT

To remove user group roaming authority

LST ROAMUSRT

To list user group roaming authority

16.5 Configuring Roaming Zone Code Service 16.5.1 Service Description Zone code is subscription data of a subscriber in HLR. The data can restrict roaming area of the mobile subscriber. Customized location areas covered by a zone code can be defined in MSOFTX3000, so that cooperation between MSOFTX3000 and HLR

16-14



makes it possible to flexibly specify location scope allowed for the mobile subscriber to roam. Zone code area roaming restriction service is a kind of roaming and services access restriction service based on LAI. That is, the subscriber is restricted when roamed-to LAI does not match the subscribed zone codes. To implement ZC restriction service regional subscription data is provided for mobile subscriber in HLR. The regional subscription data is composed of 10 ZCs which restrict the available areas at most. The subscriber can access the service in the subscribed area. Otherwise, the subscriber is restricted except the emergence service. If there is no regional subscription data, the subscriber can access the services. ZC is defined by operator in the MSC, and the level of ZC is related to LAI. A ZC might be shared by one and more LAIs, and different areas can be overlapped through different ZCs. ZC defined by the local office is unique in PLMN. The example is to define zone codes in MSC coverage, as shown Figure 16-6. MSC

ZC=1110

LAI1=460-00-270 LAI1

ZC=1120

LAI3=460-00-280

LAI2=460-00-271

Figure 16-6 Zone Code definition in MSC The above relationship is illustrated in Figure 16-7. ZC=1110 ZC=1120 LAI1 LAI3 LAI2

Figure 16-7 The relationship between Zone code and LAI

16-15



According to the restriction principles of zone code restriction services, if User A has subscribed ZC=1110 service, z

User A can access the network and enjoy provided services when User A is in LAI1 or LAI2 currently.

z

User A can neither access the network nor enjoy provided services when User A is in LAI3 currently.

16.5.2 Configuration Description Here is an example for 2G-MSC ZC restriction. In 3G ZC restriction, only setting LAISAI (using the ADD/MOD LAISAI command) is different from 2G. The parameters displayed in Figure 16-8 must be configured, and the configuration procedures are as follows: 1)

Define ZC for LAIs in MSC.

2)

Configure LAI grouping information to associate location number of LAIs and ZC.

3)

Configure LAI information to define location number of LAIs.

4)

Open ZC restriction function flag to configure ZC restriction support function in MAP function table.

ADD ZC Zone Code Zone Name

ADD LOCGRP Zone Code Location No. Location Group No. ADD LAIGCI Global Cell ID Location No. Perform Roaming Analysis ... MOD MAPACCFG Support Zone Code Restriction

Figure 16-8 Parameter relationship of ZC restriction 16-16



16.5.3 Starting Zone Code Restriction Function I. Background Information This section describes how to enable MSC to support zone code restriction services.


III. Major Parameters [Support Zone Code Restriction] Set this parameter to YES if the zone code restriction services of an MSC are expected.

Important Note: This step is not required if “support zone code restriction” in MAP information is already set to YES. This parameter controls ZC restriction to all location areas in the local office.

IV. Related Commands None.

16.5.4 Adding Zone Code I. Background Information This section describes how to allocate zone codes to MSC controlled LAIs. The same zone code can be allocated for different LAIs. It is required to use the ADD ZC command to configure all zone codes of MSC. Consequently, this table will be queried once a zone code from HLR is received. If the zone code is not found in the table, the concerned subscriber will be restricted to access. That is, the subscriber is restricted when roamed-to LAI does not match the zone code.

II. Command ADD ZC

III. Major Parameters [Zone Code] Zone code is used for ZC area restriction service. It is unique in the PLMN. [Zone Name] It identifies an area. 16-17



IV. Related Commands See Table 16-7 for the commands related to roaming zone code configuration. Table 16-7 List of commands related to roaming zone code configuration Command

Description

ADD ZC

To add roaming zone code

RMV ZC

To remove roaming zone code

LST ZC

To list roaming zone code

16.5.5 Configuring the Relationship Between ZC and LAI I. Background Information This section describes how to configure the relationship between ZC and LAI. Different location numbers can belong to the same ZC.

II. Command ADD LOCGRP

III. Major Parameters [Location No.] Location number identifies the LAI. When adding LAI, use ZC roaming restriction to the special LA through special location number. [Location group No.] Location group number identifies the LAI grouping information. One or more LAIs can share one location group number. It is used for enhanced roaming restriction. Here you need not set it. [Zone code] Zone code is already defined in the ADD ZC command.

IV. Related Commands See Table 16-8 for the commands related to LAI grouping information configuration. Table 16-8 List of commands related to LAI grouping information configuration Command

Description

MOD LOCGRP

To modify LAI grouping information

RMV LOCGRP

To remove LAI grouping information

LST LOCGRP

To list LAI grouping information

16-18



16.5.6 Configuring LAI I. Background Information None.

II. Command ADD/MOD LAIGCI

Note: This command is used to configure location area, and the "LA Category" must be set to LAI.

III. Major Parameters [Perform Roaming Analysis] Roaming analysis is performed to the special LAI. Set this parameter to YES if the LAI is required with roaming restriction. [LA Type] This parameter is used to decide whether the current LAI belongs to local VLR or adjacent VLR. The LAI of the local MSC/VLR is marked as "HVLR" and the location area of non-local MSC/VLR is marked as "NBVLR". Here, set it to "Local VLR". [LA Category] Roming restriction is performed only to LAI, so set this parameter to "LAI" only. [Location No.] It is the indicator corresponding to a location area, and it is used for roaming restriction. It is related to the parameter “Location No.” in the command ADD LOCGRP. If the LAI is already added, you can use the command MOD LAIGCI to configure the parameters “Perform Roaming Analysis” and “Location No.”.

IV. Related Commands See Table 16-9 for the commands related to LAI/CGI configuration. Table 16-9 List of commands related to LAI/CGI configuration Command

Description

ADD LAIGCI

To add LAI or CGI

MOD LAIGCI


LST LAIGCI

To list LAI or CGI

RMV LAIGCI

To remove LAI or CGI 16-19



16.6 Configuration Examples 16.6.1 Configuring Enhanced Roaming Restriction to Number Segment by LAI I. Data Description Assume that the MSISDN number segment of the local office is from 8613911901000 to 8613911901100, and the user group number is 11. The task is to add enhanced roaming restriction to mobile subscribers in the LA 460010066. It is assumed that the corresponding location number of the LA is 9, and the location group number is 8. Note that roaming analysis flag of the LA shall be set to YES and enhanced roaming restriction support flag in MAP information shall be set to YES.

II. Data Configuration MOD MAPACCFG: IFUSROAMR=YES; ADD LOCGRP: LOCNO=9, LOCGPNO=8; MOD LAIGCI: GCI="460010066", IFROAMANA=YES, LAIT=HVLR, LOCNO =9; ADD USROAMRT: USRGRP=11, LOCGRPNO=8, ROAMREST=YES; ADD

ROAMRESTGRP:

RSTRIBY=MSISDN,

BEGINNUM=K'8613911901000,

ENDNUM=K'8613911901100, USRGRP=11;

16.6.2 Configuring Zone Code Restriction I. Data Description The task is to define zone codes in 2G MSC coverage according to Figure 16-9. MSC

ZC=1110

LAI1=460-00-270

ZC=1120

LAI2=460-00-271

LAI3=460-00-280

Figure 16-9 Definition of zone codes

II. Data Configuration According to Figure 16-9, zone codes of LAIs under MSC are configured as follows: 1)

Open the ZC restriction flag.

MOD MAPACCFG: IFSZCD=YES;

16-20


2)


Configure ZC.

ADD ZC: ZC=K'1110, ZCNAME="zc1_LAI1_and_LAI2"; ADD ZC: ZC=K'1120, ZCNAME="zc2_LAI3";

3)

Configure the relationship between ZC and LAI.

ADD LOCGRP: LOCNO =1, ZC="1110"; ADD LOCGRP: LOCNO =2, ZC="1120";

4)

Configure LAI.

MOD LAIGCI: GCI="46000270", IFROAMANA=YES, LAIT=HVLR, LOCNO =1; MOD LAIGCI: GCI="46000271", IFROAMANA=YES, LAIT=HVLR, LOCNO =1; MOD LAIGCI: GCI="46000280", IFROAMANA=YES, LAIT=HVLR, LOCNO =2;

16.6.3 Configuring Location Service Data I. Data Description It is assumed that GMLC number is 8613900128, and GMLC client ID is 8613800001111. When a mobile subscriber in LAI 460009999 dials a special service number “110”, it is required to report location information to GMLC.

II. Data Configuration ADD GMLC: GMLC=K'8613900128; ADD GMLCCLT: CLTID=K'8613800001111, GMLC=K'8613900128; ADD ECLLCSCLT: DN=K'110, GCI="460009999", CLTID =K'8613800001111;

16.6.4 Adding International Roaming Data of a Newly Subscribed Country or Region I. Data Description The task is to add international roaming data for roaming to England. The local MSC number is 861390001. It is assumed that England’s country code is 44, MCCMNC is 23401, CCNDC is 44236, signaling point code of the international gateway is 222222, and prefix of the roaming subscriber’s IMSI is 2340126.

II. Data Configuration First query whether or not the country code for England is already set. If not, add it. LST NCODE: LST NCODE: NC=K'44; ADD ROAMUSRT: IMSIPFX="2340126", MSCN="861390001", MSTP=INTOTHMS; ADD IMSIGT: MCCMNC="23401", CCNDC="44236";

16-21



ADD SCCPGT: GTX=1, GTI=GT4, NUMPLAN=ISDNMOV, ADDREXP=INTER, ADDR=K'44236, RESULTT=STP1, SPC="222222";

16-22


Chapter 17 Configuring IN Service Data

Chapter 17 Configuring IN Service Data 17.1 Introduction to the Chapter This chapter describes basic concepts and data configuration procedures of Intelligent Network (IN) services. This chapter contains the following sections: z

Related Concepts

z

Data Configuration Principles

z

Procedures for Configuring IN Service Data

z

Configuration Examples

17.2 Related Concepts 17.2.1 Modes for Triggering IN Services Three modes are used to trigger IN services: overlay outgoing, number segment triggering, and standard CAMEL3 service triggering.

17.2.2 Triggering of Overlay Outgoing Intelligent Call In the wireless intelligent network in which overlay mode is implemented, when the local office is an MSC/GMSC without SSP/IP function and receives Mobile Originated (MO) or Mobile Terminated (MT) calls, MSC/GMSC will route these calls to the corresponding SSP/IP if the calling subscribers or the called subscribers are in the special number segment for intelligent subscribers. In addition, MSC/GMSC will add 1or 2-digit area prefix before the called numbers to indicate the present area of MSC/GMSC.

17.2.3 Triggering of IN Service by Number Segment I. Classification In terms of call source, intelligent calls triggered by number segment are divided into two types: overlay incoming intelligent calls and the calls triggered by the local office number segment.

II. Overlay Incoming Intelligent Call Upon receiving a call from GMSC, SSP/IP judges whether an IN subscriber is related in this call according to the calling/called number. If so, SSP/IP will query data configurations according to the number segment to obtain the intelligent subscriber’s service key and SCP address. SSP/IP will also obtain the calling subscriber location 17-1



information according to the special prefix of the called number. If the called party is a mobile subscriber, SSP/IP will get from HLR the roaming number (MSRN) related to the called subscriber, and then obtain the location information according to the roaming number of the called subscriber. SSP/IP triggers the appropriate calling/called IN service procedure, and reports to SCP the service key, calling number, called number, and location information of the calling or called subscriber. Subsequently, SSP/IP conducts intelligent call handling based on the call control instructions from the SCP.

III. Intelligent Calls Triggered by Local Office Number Segment When VMSC or GMSC functions as an SSP/IP, upon receiving a call originated by a local office subscriber or PSTN subscriber, the VMSC or GMSC will determine whether to trigger the IN service through calling number analysis (or calling number attribute analysis) and number initial processing over calling/called subscribers during number analysis. In addition, even when the call fails, the VMSC or GMSC can still determine whether to trigger IN service according to the failure cause and calling number. If it is necessary to trigger the IN service, the VMSC or GMSC will obtain the service key and SCP address information corresponding to the IN service according to the data configuration, then trigger the IN service, and complete the intelligent call according to SCP call control instructions. Number segment triggering of calling subscriber corresponds to N-CSI DP2/DP4, and that of called subscriber corresponds to N-CSI DP12/DP13/DP14. You can control whether to trigger NCSI DP2 before obtaining MSRN or after obtaining MSRN by configuring the intelligent trigger point configuration table. z

N-CSI DP2

The table query flow for N-CSI DP2 triggering is shown in Figure 17-1.

17-2



Calling number analysis

N

Record matched and NCSI_DP2 triggered?

Calling attribute analysis table Y Y

Record matched and NCSI_DP2 triggered? N

SCP parameter information table

SCP address information table

IN service not triggered

Figure 17-1 Table query flow for DP2 triggering During calling number analysis, the VMSC or GMSC will query the calling number analysis table. If the number is matched and the “Processing Type” is set to "Trigger N-CSI DP2", the VMSC or GMSC will refer to the SCP parameter information table according to the parameter “SCP Parameter Index” to obtain the service key and SCP addressing index, then query the SCP addressing information table to obtain the SCP address and SCP ID according to “SCP Addressing Index”. If the number is not matched or N_CSI DP2 is not triggered, the VMSC or GMSC will continue to search the calling characteristics analysis table. If a record is matched and N_CSI DP 2 is triggered, the VMSC or GMSC will refer to the SCP parameter information table according to the parameter “SCP Parameter Index” to obtain the service key and SCP addressing index, and then query the SCP addressing information table to obtain the SCP address and SCP ID according to “SCP Addressing Index”. z

N-CSI DP4

The table query flow triggered by N-CSI DP4 is shown in Figure 17-2.

17-3



Failure processing table

N


Y

Failure processing IN service parameter table




Figure 17-2 Table query flow triggered by DP4 If the call fails, the VMSC or GMSC will query the failure processing table according to the failure cause. If the failure cause code is matched and “Processing Type” is set to "Trigger N-CSI DP4", the VMSC or GMSC will refer to the failure processing IN service parameter table for the SCP parameter index. According to the parameter “SCP Parameter Index”, the VMSC or GMSC will then query the SCP parameter information table for service key and SCP addressing index, and then the SCP address information table to obtain the information such as SCP address and SCP ID based on the parameter “SCP Addressing Index”. z

N-CSI DP12

The table query flow triggered by N-CSI DP12 is shown in Figure 17-3.

17-4



Number initial special processing table


N

Y




Figure 17-3 Table query flow triggered by DP12 Before obtaining the roaming number of the called subscriber and conducting the secondary analysis, the VMSC or GMSC will query the number initial special processing table. If the corresponding called number is found, and the parameter “Processing Type” is set to "Trigger N-CSI DP12", the VMSC or GMSC will obtain the service key and SCP addressing index by querying the SCP parameter information table based on the parameter “SCP Parameter Index”. Then the VMSC or GMSC will obtain the information such as SCP address and SCP ID by querying the SCP address information table based on the parameter “SCP Addressing Index”.

17.2.4 Triggering of Standard CAMEL 3 IN Service I. Introduction to Standard CAMEL 3 IN Service In the standard mobile intelligent network, IN services are triggered according to the CAMEL subscription information (CSI) of the subscriber data. CAMEL subscription information includes: z

Originating CAMEL subscription information (O-CSI).

z

Dialed services CAMEL subscription information (D-CSI).

z

Terminating CAMEL subscription information (T-CSI).

z

VMSC terminating CAMEL subscription information (VT-CSI).

z

Network CAMEL service information (N-CSI).

z

Supplementary service invocation notification CAMEL subscription information (SS-CSI).

z

Short message service CAMEL subscription information (SMS-CSI).

z

Mobility management CAMEL subscription information (M-CSI).

This chapter covers only N-CSI data configuration.

17-5



N-CSI, which is usually stored in the MSC, provides the function for triggering IN services by dialing special access numbers in the network. For the standard CAMEL3 IN service triggering, the data to be configured for MSOFT3000 includes N-CSI DP3 information and D-CSI information.

II. N-CSI DP3 The table query flow for N-CSI DP3 is shown in Figure 17-4. N-CSI Home SCP mode

Access code mode

Access code index TDP access code table

SCP parameter index

Office TDP configuration

Access code index and database field length

Service key SCP parameter information

SCP configuration table

SCP address information

SCP address information

Figure 17-4 Table query flow for N-CSIDP3 triggering If the calling number and the dialed prefix match the record of NCSI information, N-CSI DP3 IN service will be triggered.

III. D-CSI If the subscriber has subscribed D-CSI data, the conversion over the called number dialed by this subscriber will be conducted through D-CSI auxiliary configuration during the IN service triggering, so as to achieve flexible rule matching. For example, the D-CSI subscribed by the subscriber is "666 Triggering". When the subscriber dials "0755666", the IN service will still be triggered by deleting "0755 (area code)" through the D-CSI auxiliary configuration.

17.3 Data Configuration Principles General principles for configuring IN service data are as follows: z

SCP signaling data shall be configured correctly, including MTP signaling data and SCCP signaling data.

z

If the local MSC also functions as an overlay SSP, the data related to IN service attributes shall be configured.

z

Special resource capability data of SSP service shall be configured correctly. 17-6



If the local office provides SSP function, all the data related to SCP shall be negotiated with the SCP. For IN services, such data includes SCP address, service key, and database index.

17.4 Procedures for Configuring IN Service Data 17.4.1 Configuring Basic Data of Local Office with SSP Function Steps for configuring the basic data of the local office with SSP function are as follows: 1)

Add SCP addressing information (ADD SCPINFO).

2)

Add SCP parameter information (ADD SCPPARA).

3)

Add SSP service specialized resource capability data (ADD SSPCAPA).

The specific data configuration steps may vary with different triggering modes.

17.4.2 Configuring Data for Triggering N-CSI DP2 Steps for configuring data for triggering N-CSI DP2 are as follows: 1)


2)


3)

Add calling number analysis (ADD CNACLR).



2)


3)

Add number initial special processing (ADD PFXPRO).



2)


3)

Add failure processing (ADD CFPRO).

4)

Add IN service failure processing parameter information (ADD INFLPRO).

17.4.5 Configuring Data for Triggering N-CSI DP3 I. IN Services Triggered by Access Code Steps for configuring data for triggering N-CSI DP3 are as follows: 1)


2)

Add SCP configuration information (ADD SCPCFG).

3)

Add TDP access code (ADD TDPAC). 17-7


4)


Add TDP configuration information (ADD ITDPCFG).

Note: In this step, detection points (DPs) used to trigger subscriber recharge and service query are set; corresponding relationship between access code and service key is established through the parameters “access code index” and “service key”. Access code index “Access Code Index” corresponds to the “access code index” ACIDX in the ADD TDPAC command.

5)

Add N-CSI (ADD NCSICFG). The access mode is set to “access code”.

II. IN Services Triggered by HOME SCP Steps for configuring data for triggering N-CSI DP3 are as follows: 1)


2)


3)

Add N-CSI (ADD NCSICFG). The access mode is set to “home SCP”.

Note: If the parameter “Calling Number” in the ADD NCSICFG command is set to "eeeeeeee", N-CSI DP3 will be triggered when any caller makes a call to the concerned number.

The differences between "access code" mode and "home SCP" mode lie in: z

By the "home SCP" mode, the specific SCP will be indexed according to "SCP Parameter Index".

z

By the "access code" mode, location of the database is found based on the parameter “Access Code Index” in office TDP configuration information. Multiple SCPs can be found according to database location and service key. When there is large amount of traffic, different SCPs can be selected in turn.

17.4.6 Configuring Data for Triggering DCSI In some cases, the number dialed by a subscriber should be converted. For example, symbols in the number like "*", "#" have to be deleted. This can be achieved by the configuration of D-CSI. Data configuration flow is as follows: 1)

Add number conversion (ADD DNC).

2)

Add D-CSI information (ADD DCSICFG). “Number conversion index” is used to query the number conversion table.

17-8



17.4.7 Configuring Data in Overlay Mode I. Calling Overlay Outgoing The analysis process of a calling overlay outgoing intelligent call is as follows: 1)

The calling number analysis table is queried.

2)

If it is found that called number conversion is required, a prefix is added at the front of the called number.

3)

A proper route is selected for outgoing.

For MSC without service switching function (SSF), an area prefix is added before the called number when the call involves an intelligent subscriber. The corresponding data configuration steps are as follows: 1)

Add number conversion (ADD DNC). An area prefix is added before the number.

2)

Add calling number analysis (ADD CNACLR). Conversion is performed on the called number. "Processing type” is set to "immediacy route selection". The route selection code is the route number from the local office to MSC with SSF.

II. Called Overlay Outgoing The analysis process of a called overlay outgoing intelligent call is as follows: 1)

The call prefix table is queried.

2)

The number initial special processing table is queried.

3)

It is found that called number conversion is required and re-analysis after conversion is necessary.

4)

An area prefix is added at the front of the called number.

5)

Number analysis is conducted again.

6)

A suitable route is selected for outgoing.

The corresponding data configuration steps are as follows: 1)

Add number conversion (ADD DNC). When A calls B and in case either is an intelligent subscriber, the called number shall be added with area prefix. In this case, number conversion is necessary for the called number.

2)

Add call prefix (ADD CNACLD)

3)

Add number initial special processing (ADD PFXPRO). Number conversion is performed, and the parameter [Processing Type] shall be specified as "number re-analysis".

III. Overlay Incoming The analysis process of an overlay incoming intelligent call is as follows: 1)

The IN service attribute table is queried.

2)

If the parameter “Trigger” is specified as YES, overlay calls from a certain call source are allowed.

3)

The number is handled after the prefix has been removed.

17-9



For the MSC with SSF, the data configuration steps are as follows: 1)

Add number conversion (ADD DNC). Remove the area prefix from the number of the overlay incoming call.

2)

Add IN service attribute information (ADD INSATTR). The prefix before the called number is removed. Area code where the calling subscriber locates is obtained. The parameter “Trigger” is set to YES if triggering of IN services is required. Otherwise, set the parameter to NO.

For different data configuration of N-CSI triggering, refer to the relevant part in 17.4.1 “Configuring Basic Data of Local Office with SSP Function”.

17.4.8 Configuring Special Intelligent Resource Capability Data When IN service is triggered, various special resources shall be employed for the interactions with subscribers. To describe the special resource capabilities of the services supported by the local MSC, special resource capability data of SSP service shall be configured correctly to ensure that correct tones will be sent to subscribers and digit collection can be conducted error-free. In addition, special intelligent resource capability data is also used for the traffic measurement of IN service, and used to judge whether the current module supports the corresponding service logic when other modules apply for the special resources of the current module. You can configure the data by executing the command ADD SSPCAPA.

17.4.9 Managing Special Number Information During actual operation, emergency calls such as fire call and police call will be connected quickly without triggering IN service. For such numbers, relevant data will be set to the special number information. When the system judges that a special number is dialed, the IN service processing procedure will not be triggered. ADD SPCLDN: SPCLDN=K'112;

17.5 Configuration Examples 17.5.1 IN Services Triggered by N-CSI DP3 I. Data Description It is assumed that the access code of charging and querying flow of a certain pre-paid service is "13800138000". "Home SCP” is set as the access mode for mobile subscribers, whose number prefix is 1390231. The local MSC is interconnected with the SCP whose address is "8613900123". Version Number of the CAP supported by the SCP is 3, and the service key is 2. SCP parameter index is 2. SCP addressing index is 1. The local office possesses SSP function. Intelligent calls are triggered by local office number segment directly.

17-10



II. Data Configuration ADD SCPINFO: SCPADDRIDX=1, SCPADDR=K'8613900123, CAPVER=3, SCFID="1"; ADD

SSPCAPA:

SRVKEY=2,

SSPCAPA=IPRA-1&VOICEBACK-1&SPREC-1&VOICEREC-1&TEXTTOV-1; ADD SCPPARA: SCPPARAIDX=2, SCPADDRIDX=1, SRVKEY=2, DCH=RELESCALL; ADD

NCSICFG:

CLIPFX=K'1390231,

CLDPFX=K'13800138000,

AMODE=HOMESCP,

SCPPARAIDX=2;

17.5.2 IN Services Triggered by N-CSI DP4 I. Data Description It is assumed that the access code of charging and querying flow of a certain pre-paid service is "13800138000". "Home SCP” is set as the access mode for mobile subscribers, whose number prefix is 1390231. N-CSI DP4 is triggered when a call, originated by any subscriber with the local office number segment "1390231", fails due to call barring. The intelligent call will be processed by the service key 4 of the SCP with the number "8613900123".

II. Data Configuration ADD SCPINFO: SCPADDRIDX=1, SCPADDR=K'8613900123, CAPVER=3, SCFID="1"; ADD

SSPCAPA:

SRVKEY=4,

SSPCAPA=IPRA-1&VOICEBACK-1&SPREC-1&VOICEREC-1&TEXTTOV-1; ADD SCPPARA: SCPPARAIDX=1, SCPADDRIDX=1, SRVKEY=4, DCH=RELESCALL; ADD CFPRO: FCC=CAN, FSC=0, RUT=ALL, CSA=ALL, FPT=RSRT, INST=DP4; ADD INFLPRO: DPNUM=DP4, FCC=CAN, CLIPFX=K'1390231, SCPPARAIDX=1;

17.5.3 Overlay Outgoing I. Data Cescription It is assumed that the access code of charging and querying flow of a certain pre-paid service is "13800138000". "Home SCP” is set as the access mode for mobile subscribers, whose number prefix is 1390231. The local office is a VMSC that shall be configured with overlay outgoing data. The serving area of the VMSC includes areas A and B. According to the plan, it is required to add "40" at the beginning of called numbers for intelligent calls from area A (call source code: 1) and then route them to the SSP1. It is required to add "80" at the beginning of called numbers for intelligent calls from area B (call source code: 2) and then route them to SSP1, too. The route selection source code of the route to SSP1 is 0 and the route selection code is 5. The call source and routing data have been set.

17-11



II. Data Configuration z

ADD

Calling overlay outgoing data configuration DNC:

DCX=3,

DCT=TYPE1,

ND=K'40,

NDPRI=FALSE,

OTHERSRC=UNDIRECTED,

DCX=4,

DCT=TYPE1,

ND=K'80,

NDPRI=FALSE,


DAI=NONE; ADD

DNC:

DAI=NONE; ADD CALLSRC: CSC=1, CSCNAME="overlay_A"; ADD CALLSRC: CSC=2, CSCNAME="overlay_B"; ADD CNACLR: CSC=1, CLIN=K'1390231, CS=ALL, PFX=K'6666, RSC=5, CAT=NO, CLINCX=3, PT=IMRS; ADD CNACLR: CSC=2, CLIN=K'1390230, CS=ALL, PFX=K'6666, RSC=5, CAT=NO, CLINCX=4, PT=IMRS;

z

ADD

Called overlay outgoing data configuration DNC:

DCX=3,

DCT=TYPE1,

ND=K'40,

NDPRI=FALSE,


DCX=4,

DCT=TYPE1,

ND=K'80,

NDPRI=FALSE,


DAI=NONE; ADD

DNC:

DAI=NONE; ADD CALLSRC: CSC=1, CSCNAME="overlay_A"; ADD CALLSRC: CSC=2, CSCNAME="overlay_B"; ADD CNACLD: PFX=K'401380000, CSTP=BASE, CSA=MLC, RSC=5, MINL=7, MAXL=11, IAC=NO,

GAIN=LGN,

RCM=NOC,

ECOS=NO,

ICLDTYPE=UN,

ISEACM=FALSE,

SDESCRIPTION="IN-CALL-40"; ADD CNACLD: PFX=K'801380000, CSTP=BASE, CSA=MLC, RSC=5, MINL=9, MAXL=11, IAC=NO,

GAIN=LGN,

RCM=NOC,

ECOS=NO,

ICLDTYPE=UN,

ISEACM=FALSE,

SDESCRIPTION="IN-CALL-80";

ADD PFXPRO: CSC=1, CS=ALL, PFX="1380000", NP=0, CLDNCX=3, STF=NSDT, PT=REANA; ADD PFXPRO: CSC=2, CS=ALL, PFX="1380000", NP=0, CLDNCX=4, STF=NSDT, PT= REANA;

17-12


Chapter 18 Debugging

Chapter 18 Debugging 18.1 Introduction to the Chapter This chapter focuses on the debugging methods of SCTP, M3UA, and H.248 protocols applied in MSOFTX3000. This chapter contains the following sections: z

Debugging of SCTP

z

Debugging of M3UA

z

Debugging of Mc (H.248)

18.2 Debugging of SCTP 18.2.1 Background Information An example of a typical SCTP message interaction process is as shown in Figure 18-1.

Figure 18-1 SCTP message interaction process To locate an SCTP issue, start the SCTP message trace, check if the message flow is correct, and analyze if the message content is valid. Decide based on trace results if other debugging methods are required as checking parameters.

18.2.2 Debugging Methods Follow the steps below for debugging: 1)

Check if the MGW can be pinged successfully.

2)

Check if the physical connection is normal.

3)

Use the command LST FECFG to check if the interface IP address of MSOFTX3000 is consistent with the data configuration plan. If inconsistent, correct it.

4)

If MSOFTX3000 and MGW are not directly connected, use the command LST FECFG to check if the gateway IP address is correctly configured.

18-1


5)


Use the Traceroute program to trace the route and determine where the packet is lost by specifying the WIFM module number and IP address of MGW.

6)

Use the command LST MCLNK to check if the client and server ends of the SCTP connection conform to the data plan. The two ends cannot be server or client at the same time, or the connection cannot be established.

7)

Generally, MSOFTX3000 is configured as a server, and MGW is configured as a client. If not correctly configured, use the command MOD MGW to modify the configuration.

18.2.3 FAQ I. No Response from the Local SCTP Server End for INIT Message z

Fault description

The local SCTP end is configured as a server. Observed in message trace that it receives INIT message, but it does not respond. z

Cause analysis

SCTP supports two checksum modes: ADLER32 and CRC32, which are both supported in the MSOFTX3000. If the configured SCTP checksum algorithm differs at the two ends, the sent message from one end to the other will be regarded as invalid and discarded. Use LST SCTPPARA to check if the two ends are consistent in checksum algorithm. z

Solution

Modify the checksum algorithm at local end with MOD SCTPPARA. Be sure not to affect other SCTP connections. z

Summary and suggestions

This problem is generally caused by inconsistency of checksum algorithm between local and peer end.

II. Response with Abort Message from the Local SCTP Server End for INIT Message z

Fault description

The local SCTP end is configured as a server. Observed in message trace that it receives INIT message, but it responds with the Abort message. z

Cause analysis

The establishment of listening port fails. If the SCTP upper layer user provides the maintenance command to query z

Solution

Modify the configured parameters. z

Summary and suggestions

18-2



This problem is generally caused by inconsistency of checksum algorithm between local and peer ends.

18.3 Debugging of M3UA 18.3.1 Background Information An example of a typical M3UA message interaction process is as shown in Figure 18-2 .

Figure 18-2 M3UA message interaction process SCTP reports UP message. ASP sends ASP UP message to SG, and SG responds with ASP UP ACK message. ASP sends ASP ACTIVE message to SG, and SG responds with ASP ACTIVE ACK message. Then, the M3UA link is activated.

18.3.2 Debugging Methods Follow the steps below for debugging: 1)

Check if the MGW can be pinged successfully.

2)


3)

Check if the link state is Active with the command DSP M3LNK.

4)

Check if the link set state is Active with the command DSP M3LKS.

5)

Check if the destination entity state is Accessible with the command DSP M3DE.

If all states are correct, the debugging of M3UA layer completes. Otherwise, start the SCTP and M3UA message trace and check the message interaction.

18.3.3 FAQ I. Unable to Establish M3UA Link z

Fault description 18-3



The M3UA link state is displayed as Link Unestablished, as shown below: %%DSP M3LNK: MN=133, M3LNK=0,CONFIRM=Y;%% RETCODE = 0 Operation succeeded

M3UA Link Status ----------------

Module Number = 133 Link Number = 0 SCTP Association ID = 4294967295 Lock Information = Unlocked Local Inactive Info = Link Not Inactivated Manually Local Release Info = Release Ungracefully Link Congestion Info = Not Congested Real In Stream Num = 0 Real Out Stream Num = 0

Status = Link Unestablished. z

Cause analysis

Cause A: incorrect data configuration. Check if the following parameters are correctly configured: Route context in ADD M3LE Work mode in ADD M3LKS C/S mode, local IP address, peer IP address, local port number, and peer port number in ADD M3LNK Cause B: M3UA link is manually disconnected at client end. Check as follows: %%DSP M3LNK: MN=133, M3LNK=0,CONFIRM=Y;%% RETCODE = 0 Operation succeeded

M3UA Link Status ----------------

Module Number = 133 Link Number = 0 SCTP Association ID = 4294967295 Lock Information = Unlocked Local Inactive Info = Link Not Inactivated Manually Local Release Info = Release Ungracefully Link Congestion Info = Not Congested Real In Stream Num = 0

18-4



Real Out Stream Num = 0 Status = Link Unestablished.

If Local Release Info is Release Ungracefully or Release Gracefully, it means that the M3UA link has been manually released. Cause C: SCTP abnormality causes M3UA link state to be Link Unestablished. Refer to Chapter 8, Interworking with MSC Server for details. z

Solution

Cause A: Modify the data configuration of two ends. Cause B: Establish the M3UA link with EST M3LNK at client end as follows: %%EST M3LNK: MN=133, M3LNK=0,CONFIRM=Y;%% RETCODE = 0 Operation succeeded

Cause C: Refer to Chapter 8, Interworking with MSC Server for details.

II. M3UA Link Displayed as Link DOWN at ASP Side z

Fault description

The M3UA link state is displayed as Link DOWN, as shown below: %%DSP M3LNK: MN=133, M3LNK=0,CONFIRM=Y;%% RETCODE = 0 Operation succeeded

M3UA Link Status -------------------------

Module Number = 133 Link Number = 0 SCTP Association ID = 15 Lock Information = Unlocked Local Inactive Info = Link Not Inactivated Manually Local Release Info = Link Not Released Manually Link Congestion Info = Not Congested Real In Stream Num = 0 Real Out Stream Num = 0 Status = Link Down.

z

Cause analysis

Cause A: The M3UA link is locked by the SG. %%DSP M3LNK: MN=132, M3LNK=0,CONFIRM=Y;%% RETCODE = 0 Operation succeeded

M3UA Link Status

18-5



-------------------------

Module Number = 133 Link Number = 0 SCTP Association ID = 101 Lock Information = Locked Local Inactive Info = Link Not Inactivated Manually Local Release Info = Link Not Released Manually Link Congestion Info = Not Congested Real In Stream Num = 0 Real Out Stream Num = 0 Status = Link Down.

--- END

Cause B: SG and AS are abnormal, and vary in state. For instance, it is Link Active at ASP side, but Link Down at SG side. z

Solution

Cause A: Execute the command ULK M3LNK to unlock the M3UA link at SG side. %%ULK M3LNK: MN=133, M3LNK=0,CONFIRM=Y;%% RETCODE = 0 Operation succeeded

Cause B: Manually release and re-establish the M3UA link at the client end. %%REL M3LNK: MN=133, M3LNK=0,CONFIRM=Y;%% RETCODE = 0 Operation succeeded

--- END

%%EST M3LNK: MN=133, M3LNK=0,CONFIRM=Y;%% RETCODE = 0 Operation succeeded

--- END

III. M3UA Link Cannot Be Activated z

Fault description

The M3UA link state is displayed as Link Inactive, as shown below: %%DSP M3LNK: MN=133, M3LNK=0,CONFIRM=Y;%% RETCODE = 0 Operation succeeded

M3UA Link Status -------------------------

18-6



Module Number = 133 Link Number = 0 SCTP Association ID = 108 Lock Information = Unlocked Local Inactive Info = Link Inactivated Manually Local Release Info = Link Not Released Manually Link Congestion Info = Not Congested Real In Stream Num = 17 Real Out Stream Num = 17 Status = Link Inactive --- END z

Cause analysis

Cause A: incorrect data configuration. Check if the following parameters are correctly configured: Route context in ADD M3LE Work mode in ADD M3LKS C/S mode, local IP address, peer IP address, local port number and peer port number in ADD M3LNK In addition, start the M3UA message trace flow, and locate the fault from the error message. Cause B: The M3UA link is deactivated at ASP end. %%DSP M3LNK: MN=132, M3LNK=0,CONFIRM=Y;%% RETCODE = 0 Operation succeeded

M3UA Link Status -------------------------

Module Number = 132 Link Number = 0 SCTP Association ID = 108 Lock Information = Unlocked Local Inactive Info = Link Inactivated Manually Local Release Info = Link Not Released Manually Link Congestion Info = Not Congested Real In Stream Num = 17 Real Out Stream Num = 17 Status = Link Inactive

--- END

18-7



Solution

Cause A: Modify the data configuration based on the error code type in the error message. When the error code is Invalid Routing Context, modify the routing context of the two ends into the same. When the error code is Unsupported Traffic Handling Mode, the work mode of the two ends are different, modify it of the two ends in the link set table into the same. Cause B: Manually activate the M3UA link with ACT M3LNK at ASP end as follows. %%ACT M3LNK: MN=132, M3LNK=0,CONFIRM=Y;%% RETCODE = 0 Operation succeeded --- END

18.4 Debugging of Mc (H.248) 18.4.1 Background Information When the MSOFTX3000 and MGW are configured, and the equipment is fully operational, MGW will first send the registration request to the active MSOFTX3000, who will return the registration successful message. The registration completes. Then the MGW can fully function under the supervision of MSOFTX3000. The debugging of MSOFTX3000 is to check if MGW is successfully registered.

18.4.2 Debugging Methods During the startup of MSOFTX3000, MGW will register to it and start the establishment of SCTP link. Follow the steps below for debugging: 1)

Firstly, ensure the intact physical connection between MSOFTX3000 and MGW.

2)

If all boards are functioning normally, check if the network interface indicator of the WIFM flashes normally.

3)

Then, trace the interface interaction between the WIFM and the MPPB. If not connected, check the physical connection between them.

4)

Start the SCTP and H.248 trace on messages interacting in the Mc interface.

5)

Query the SCTP link state with the command DSP MCLNK. if it is valid, the link state is normal.

6)

Observe the SCTP interface trace results to ensure the message interaction: MSOFTX3000 receives the INTI message and returns the INTI ACK message. Then

MSOFTX3000

and

MGW

both

receive

HEARTBEAT

and

HEARTBEAT-ACK message. All together there are four messages in both directions. 7)

Display the MGW state with the command DSP MGW. If it is Normal, MGW has registered successfully. 18-8


8)


Observe the H.248 interface trace results to ensure the message interaction: MSOFTX3000 receives the service change request and sends the service change reply. If MGW state is not normal, analyze the Mc interface message interaction.

18.4.3 FAQ The Mc interface is blocked due to physical connection or data configuration errors. The following are solutions to some frequently arising issues: z

Check if the MGW can be pinged.

z

Check if the physical connection is normal.

z


z

If MSOFTX3000 and MGW are not directly connected, use the command LST FECFG to check if the gateway IP address is correctly configured.

z

Use the Traceroute program to trace the route and determine where the packet is lost by specifying WIFM module number and IP address of MGW.

z

Use the command LST MGW to check the client and server ends of the MGW to the data plan. The two ends cannot be server or client at the same time, or the connection cannot be established. Generally, MSOFTX3000 is configured as a server, and MGW is configured as a client. If not correctly configured, use the command MOD MGW to modify the configuration.

z

Observed in message trace that the local SCTP server end (MSOFTX3000) receives INIT message, it does not respond. Verify the consistency of Checksum Arithmetic of the local and peer end with LST SCTPPARA. Modify the configuration of MSOFTX3000 with MOD SCTPPARA.

z

Use DEA MGW to log off the VMGW on MGW. Initiate MGW with ACT MGW. During the initialization of MGW, it will register to MSC SERVER, and establish the SCTP link. Observe the SCTP and H.248 message interaction.

z

If it is an SCTP issue, refer to section 18.2 Debugging of SCTP.

18-9


Appendix A An Example on Global Data Configuration

Appendix A An Example on Global Data Configuration A.1 Introduction to the Appendix The example is for the deployment of a new office site after hardware installation. MSOFTX3000 starts with global data configuration from none. This chapter describes the ideas and methods for configuring different entities, excluding networking plan. The configuration examples in Chapters 1 to 13 are independent parts of this example, and the configuration of service data is rather simple.

A.2 Configuration Example A.2.1 Example Description Here, an example of a single cabinet configuration will be introduced for explanation. Figure A-1 is the networking diagram of MSOFTX3000 and other functional entities. Figure A-2 tells the hardware configuration of MSOFTX3000. The configurations are as follows: z

One integrated configuration cabinet.

z

One basic frame.

z

Subscriber capacity: 150,000.

z

The MSOFTX3000 locks the line clock of the MGW. The WEPI board of the MSOFTX3000 frame must be installed in the back slots 0, 1, 2 and 3. The two in back slots 0 and 2 are active boards, providing E1 interfaces, and the other two in back slots 1 and 3 are standby boards without interface. The two active WEPIs (No.6 E1 of slot 0 and No.0 E1 in slot 2) can lock the clock of MGW, so as to provide four channels of 2Mbit/s clock signals and lead them into the active and standby WCKIs.

z

The MSRN/HON numbers are all in LAI number allocation mode, which include two number segments: The MSRN/HON numbers of 2G cell range from 86136000040001 to 86136000040999 (the prefix index of the number segment is “0”, the postfix index is “0”, and the corresponding LAI number is “460000001”). The MSRN/HON numbers of 3G cell range from 86136000041000 to 86136000041999 (the prefix index of the number segment is “0”, the postfix index is “1”, and the corresponding LAI number is “460000003”).

A-1



Since the SCTP verification and algorithm of MSOFTX3000 is different from that of MGW, modifications are needed. Set the circular broadcast times of the time reporting announcement (TID_0X0002) to 3.

z

In this example, the integrated configuration of WIFM/WBSG/WMG is adopted. Therefore, when filling the module number of WIFM/WBSG/WMGC, you should select that of WIFM. If WIFM, WBSG and WMGC are configured separately, you should note the following: Add the corresponding boards and configure the corresponding module number. For WMGC board, the WMGC module number should be configured in the parameter [Control Module No.] of command ADD MGW. For WBSG, the parameter [Module No.] in command ADD M3UA should be chosen according to the actual configuration of M3UA link. If it is configured on the WIFM board, the module number should be that of WIFM. If it is configured on WBSG, the module number should be that of the WBSG.

SCP

SMC

GMLC

HLR

MAP/TDM

MAP/TDM

MAP/TDM

MAP/TDM

MSC Server

MSOFTX 3000

ISUP/TDM

H.248,RANAP /IP

BSSAP+

SGSN

/TDM


MGW

MGW

IP/TDM

ISUP/TDM

(SG)

RANAP/AAL2 /ATM

BSSAP/TDM

RNC

BSC

Figure A-1 Networking of MSOFTX3000

A-2

PSTN


MGW(CLOCK RESOURCE2) HLR

MGW(CLOCK RESOURCE1)

SCP

MSC SERVER

SMC

PSTN

SGSN

BSC

GMLC

RNC

Back

Front


0

1

2

3

4

5 6

W E P I

W E P I

W E P I

W E P I

W C S U

W C S U

W C S U

W C S U

W C C U

W C C U

0

1

2

3

4

5 6

W S I U

7

8

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

W H S C

W S I U

M H S C

W S M U

W S M U 7

8

W B F I

W B F I

W I F M

W I F M

W C K I W V D B

W V D B

W C D B

W C K I W C D B

W A L U

U P W R

U P W R

U P W R

U P W R

Backplane

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

Figure A-2 Hardware configuration of MSOFTX3000

A.2.2 Data Collection The data configurations of MSOFTX3000 and its ambient entities or interfaces are as shown in Table A-1 to Table A-13. The shaded parts indicate the parameters that need to be negotiated by both sides or need to inform the peer side. Other fields are the internal parameters of MSOFTX3000. Table A-1 Table of hardware data Frame type

Frame No.

Location

Basic frame

0

1

1

1

Board type

Frame No.

Slot number

Front/back

Module No.

Slot No. of mutual aid board

WCSU

0

0

Front

22

1

WCSU

0

1

Front

22

0

WCSU

0

2

Front

23

3

WCSU

0

3

Front

23

2

WCCU

0

4

Front

25

5

WCCU

0

5

Front

25

4

WIFM

0

10

Front

132

11

WIFM

0

11

Front

132

10

WVDB

0

12

Front

102

13

WVDB

0

13

Front

102

12

A-3

Row

Column



Frame type

Frame No.

Location

Row

Column

WCDB

0

14

Front

103

15

WCDB

0

15

Front

103

14

WEPI

0

0

Back

WEPI

0

1

Back

WEPI

0

2

Back

WEPI

0

3

Back

WCKI

0

13

Back

WCKI

0

15

Back

IP address of FE interface

IP address of the router connected with MSOFTX3000

Link type (64Kbit/s, 2Mbit/s)

173.20.200.132

173.20.200.253

64Kbit/s

Balance mode of E1 interface (non-balance mode/ balance mode)

Frame format of E1 interface (DF/CRCR)

Numbers of the frame/ slot/ E1 of the WEPI board, from which the clock is extracted.

Non-balance mode

DF

0/0/6, 0/2/0

Table A-2 Local office information table Item

Data

Signaling point

National

National reserved

/

CC0004

C04

Mobile network information

Local office MSC number

Local office VLR number

/

8613600004

8613600004

/

Mobile Network Code (MNC)

/

460

MAP information

Whether check identity

/

No

the

Remark

International

Internation al reserved

Network Code (NC)

Country code

Area code

00

86

755

ODB_SS

Whether perform authorization in the service access process/ position updating process

Whether encrypt/ encryption algorithm

ALL

No

No

A-4



Item

Data

MAP information

Whether reallocate TMSI in service access process/positi on updating process

Whether support position updating VLR

/

No Whether support restriction on roaming zone

/

(Zone code

Remark

Whether take IMEI or reserve IMEI in BILL during the service access process/position updating process

Whether support the call forwarding on HPLMN not reachable

No

No

Yes

Whether provide SMMO/SMMT function

Whether support pre-paging

MAP version/ CAMEL version

No

MAP_PHA SE2+/ CAMEL_P HASE3

/

No

Yes

/

Whether support call hold

Whether support interface

/

Yes

No

the of

Gs

Whether use the reinforced roaming restriction None

Table A-3 Table of MGW information Item

Data

Checksu m mode

Encryption algorithm and secret key (optional) of MGW

Server or client

Server

Basic information

MGW Index

Transmission layer protocol

Voice encoding/d ecoding mode

/

1

SCTP

ALL

CRC32

NO

SCTP connection information

SCTP connectio n number 1

Local WIFM address of Link1

Local WIFM port of Link1

Remote MGW address of Link1

Remote MGW port of Link1

/

1

173.20.200.13 2

2945

173.20.2 00.93

2945

Table A-4 RNC information table Item RNC basic information

Data RNC ID


Network ID

A-5

LAI

SAI

AMR LIST



Item

Data 460000003 0004

All


Port of peer MGW

Server/c lient

173.20.200.93

2905

Client

/

4

D04

National reserved

460000003

M3UA basic signaling

Service mode

Routing context (optional)

WIFM module No.

Signaling point code of SG

/

Load sharing

NULL

132

1004


M3UA link number

Local address

Local port

/

0

173.20.200.1 32

2905

Prefix



/

1360755

65535

IP

Table A-5 BSC information table Item

Configure Data

Basic information /


NI of signaling point code

LAI

GCI

C03

National reserved

460 00 0001

460 00 0001 0001

Link type

64 kbit/s

WCSU module number

Link set


SLC


22

3

3

0

112(3/16)


CIC

MGW index

96~127

0~31

1

Trunk route

Office direction

Trunk group

Circuit type

/

3

3

BSSAP

Prefix



Signaling link

/

Circuit /

A-6



Item /

Configure Data 1390752

65535

Table A-6 MSC information table (MTP) Item

Data

Basic information /


NI signaling point

of

AA0001

National

8613500001 Intra-module circuit number (E1 number/time slot number)

Link type

64 kbit/s

MSC server number (E.164 code)

WCSU module number

Link set


Signaling link code (SLC) and signaling link code sending

22

1

1

0

48 (1/16)

Termination ID (the number of the physical circuit from MGW to MSC server)

CIC


MGW Index

/

32~63

0~32

25

1

Trunk route

Office directio n

Route number

Sub-route number

Trunk group

Circuit type

/

1

1

1

1

ISUP

Prefix

Prefix



/

13910

1

0

Signaling link

/

Circuit

Table A-7 PSTN information table Item

Data

Basic information /

Signaling link

WCSU module number


NI signaling point

BB0002

National

Link set

of


A-7



Link type



Item /

Circuit

/

Data 22

2

2

1

80(2/16)

Termination ID (the number of the physical circuit from MGW to PSTN)

CIC

WCCU/WCS U module number

MGW Index

64~95

32~63

25

1

Trunk route

Office direction

Route number

Sub-route number

Trunk group

Circuit type

/

2

2

2

2

ISUP

Prefix

Prefix



/

666

2

0

64 kbit/s

Table A-8 HLR information table Item

Data

Basic information /




12345

National

86139075500 00 Intra-modul e circuit number (E1 number/ timeslot number)

Link type

48(1/16)

64 kbit/s

WCSU module number

Link set



23

11

1

0

Encoding description

Numbering plan

Address information

DPC

/

IMSI GT

ISDNMOV

86139

12345

/

HLR number

ISDN

8613907550 000

12345

/

MSIDSN

ISDN

861390755

12345

Signaling link

/ SCCP GT translation

A-8



Table A-9 SCP information table Item

Data

Basic information /

Signaling link

/


NI signaling point

of

D02302

National

8613600012 Intra-module circuit number (E1 number/ timeslot number)Data

Link type

80(2/16)

64 kbit/s

E.164 code

WCSU module number/ WCCU/W SGU

Link set



23

12

2

0

Table A-10 SMC information table Item

Data

Basic information /

Signaling link

/


NI signaling point

of

D02303

National


Link type

112(3/16)

64 kbit/s

E.164 code

WCSU module number

Link set



23

13

3

0

Table A-11 SGSN information table Item

Data

Basic information /

Signaling link

/



E.164 code

D02304

National


Link type

144 (4/16)

64 kbit/s

WCSU module number

Link set

Intra-mod ule link number


23

14

16

0

A-9



Table A-12 GMLC information table Item

Data

Basic informati on



E.164 code

D02305

National

8613600015

WCSU module number

Link set

Intra-mod ule link number


Intra-module circuit number (E1 number/ timeslot number) Data

Link type

23

15

17

0

176 (5/16)

64 kbit/s

/

Signaling link

/

Table A-13 Information table of SCCP subsystem Entity

Network ID

SSN configured on peer end

SSN configured on local end

MSC/VLR of local office

National

[MSC] [VLR] [SCMG]

MSC/VLR of local office

National reserved

[SCMG]

RNC

National reserved

[SCMG], [RANAP]

[RANAP]

BSC

National reserved

[SCMG], [BSSAP/INAP]

[BSSAP/INAP]

HLR

National

[HLR] [SCMG]

MSC SERVER

National

[MSC] [VLR] [SCMG]

SCP

National

[SCMG] [CAP]

SMC

National

[SCMG] [MSC]

SGSN

National

[SCMG] [GS]

GMLC

National

[SCMG] [GMLC]

[CAP]

[GS]

Note: The configurations of SSNs configured for the local MSC/VLR are described in Chapter 3 Local Office Data Configuration. The SSN data serves as the global data. The SSNs configured in other entities are presented in corresponding chapters.

A-10



A.2.3 Data Configuration I. Configuring Hardware Data //Set offline. LOF:;

//Turn off alarm switch. SET CWSON: SWT=OFF;

//Turn off format conversion switch. SET FMT: STS=OFF;

//Add subrack. ADD SHF: SN=0, LT=" SX4", PN=1, RN=1, CN=1;

//Add frame. ADD FRM: FN=0, SN=0, PN=2;

//Add board and module number. ADD BRD: FN=0, SN=0, LOC=FRONT, BT=WCSU, MN=22, ASS=1, LNKT=LINK_64K; ADD BRD: FN=0, SN=2, LOC=FRONT, BT=WCSU, MN=23, ASS=3, LNKT=LINK_64K; ADD BRD: FN=0, SN=4, LOC=FRONT, BT=WCCU, MN=25, ASS=5;

ADD BRD: FN=0, SN=10, LOC=FRONT, BT=WIFM, MN=132, ASS=11; ADD BRD: FN=0, SN=12, LOC=FRONT, BT=WVDB, MN=102, ASS=13; ADD BRD: FN=0, SN=14, LOC=FRONT, BT=WCDB, MN=103, ASS=15;

ADD BRD: FN=0, SN=0, LOC=BACK, BT=WEPI; ADD BRD: FN=0, SN=1, LOC=BACK, BT=WEPI; ADD BRD: FN=0, SN=2, LOC=BACK, BT=WEPI; ADD BRD: FN=0, SN=3, LOC=BACK, BT=WEPI; ADD BRD: FN=0, SN=13, LOC=BACK, BT=WCKI; ADD BRD: FN=0, SN=15, LOC=BACK, BT=WCKI;

//Configuring CDB function. ADD CDBFUNC: FUNC=TK, CDPMN=103; ADD CDBFUNC: FUNC=MGWR, CDPMN=103; ADD CDBFUNC: FUNC=VDB, CDPMN=103; ADD CDBFUNC: FUNC=CGAP, CDPMN=103;

A-11



//Configure FE interface information of WIFM. ADD

FECFG:

MN=132,

IP="173.20.200.132",

MSK="255.255.0.0",

DGW="173.20.200.253";

//Configure E1 and clock data. SET CKICFG: CL=LEVEL2, WM=AUTO, B1P=L3, B2P=L4, L1P=L1, L2P=L2; ADD EPICFG: FN=0, SN=0, E0=DF, E1=DF, E2=DF, E3=DF, E4=DF, E5=DF, E6=DF, E7=DF, BM=NONBALANCED; ADD EPICFG: FN=0, SN=2, E0=DF, E1=DF, E2=DF, E3=DF, E4=DF, E5=DF, E6=DF, E7=DF, BM=NONBALANCED; ADD BOSRC: FN=0, SN=0, EN=6; ADD BOSRC: FN=0, SN=2, EN=0;

II. Configuring Office Data //Configure local signaling point information. SET OFI: OFN="SX4", LOT=CMPX, NN=YES, NN2=YES, SN1=NAT, SN2=NAT2, SN3=NAT, SN4=NAT2, NPC="CC0004", NP2C="C04", NNS=SP24, NN2S=SP14, SPF=YES, LAC=K'755, LNC=K'86;

//Configure local mobile office information. SET INOFFMSC: MSCN=K'8613600004, VLRN=K'8613600004, MCC=K'460, MNC=K'00, INNATIONPFX=K'00, NATIONPFX=K'0;

//Configure VLR information, and MSRN/HON number allocation. ADD VLRCFG: MAXUSR=12000, MCC=K'460, MNC=K'00, CTRYCODE=K'86, MSRNAM=LAI, HONAM=LAI;

//Configure MAP data. ADD

MAPACCFG:

IFIDPROC=NO,

ODBSS=ACOB-1&ICOB-1&ICOBNHP-1&ICB-1&ECB-1&SSAB-1&PSBT1-1&PSBT2-1&PSBT3-1&P SBT4-1, IFCIPH=NO,

IFAUTHSA=NO,

IFAUTHLU=IFAUTHLUP-0&IFAUTHPLUP-0&IFAUTHIA-0,

CIPHALG=NOCIPH2G-0&A5_1-0&A5_2-0&A5_3-0&NOCIPH3G-0&UEA1-0,

IFALTMSILU=NO, IFALTMSISA=NO, IFVLRLU=NO, IFFWD=YES, IFSZCD=NO, ISSSMMO=YES, ISSSMMT=YES,

MAPVER=PHASE3,

CAMELVER=PHASE3,

IFSCH=YES,

SUPGSIE=YES,

IFUSROAMR=NO, IFUSACBUF=NO;

//Configure local SCCP subsystem, including MSC, VLR and SCMG subsystems.

A-12


SCCPSSN:

SSNX=0,


NI=NAT,

SSN=MSC,

SPC="CC0004",

OPC="CC0004",

NI=NAT,

SSN=VLR,

SPC="CC0004",

OPC="CC0004",

NI=NAT,

SSN=SCMG,

SPC="CC0004",

OPC="CC0004",

SSNNAME="LOCAL-MSC"; ADD

SCCPSSN:

SSNX=1,

SSNNAME="LOCAL-VLR"; ADD

SCCPSSN:

SSNX=2,


SCCPSSN:

SSNX=3,

NI=NATB,

SSN=SCMG,

SPC="C04",

OPC="C04",

SSNNAME="LOCAL-NATB-SCMG";

//Configure local SCCP GT. ADD

SCCPGT:

GTX=0,

GTNAME="LOCAL-MSC",

NI=NAT,

TRANSLATETYPE="00",

NUMPLAN=ISDN, ADDR=K'8613600004, RESULTT=LSPC2, SPC="CC0004";

//Add call source code. ADD CALLSRC: CSC=0;

III. Adding a MGW //Check the WIFM module number, IP address and WMGC module number. LST FECFG:; LST MDU:;

//Configure basic information of MGW. ADD

MGW:

MGWIDX=1,

BNCC=IP-1&AAL1-1,

TRNST=SCTP,

CTRLMN=132,

DEVNAME="MGW1",

MGWDESC="MGW1",

SVRCLIENT=SVR,

BCUID=1, ENCT=NSUP,

CPB=TONE-1&PA-1&SENDDTMF-1&DETECTDTMF-1&MPTY-1&IWF-1, ECRATE=0, IWFRATE=1, TCRATE=1,

TONERATE=12,

MPTYRATE=0,

DETDTMFRATE=0,

SNDDTMFRATE=0,

HRAMRR=RATE795-1&RATE740-1&RATE670-1&RATE590-1&RATE515-1&RATE475-1, TC=GSMEFR-1&GSMHR-1&TDMAEFR-1&PDCEFR-1&HRAMR-1&UMTSAMR2-1&FRAMR-1&FRAMRWB1&UMTSAMRWB-1&PCMA-1&PCMU-1&UMTSAMR-1&G7231-1&G729A-1;

//Configure MGW SCTP connection information. ADD MCLNK: MGWIDX=1, TRNST=SCTP, LNKN=0, BSGMN=132, SLOCIP1="173.20.200.132", SRMTIP1="173.20.200.93";

//Modify SCTP check and algorithm (optional). LST SCTPPARA:; SET SCTPPARA: CHKSUMTYPE=CRC32;

A-13



//Set playing capability of MGW voice (optional). MOD TONECFG: INTTID=TID_0X0002, CYCN=3;

IV. Adding a RNC //Add M3UA. LST OFI:;

//Query the OPC whose NI = NATB

LST FECFG:; //Query the local IP address of WIFM ADD M3LE: LEX=0, LENAME="MscM3UA", NI=NATB, OPC="C04", LET=AS; ADD M3DE: DEX=0, DENAME="MgwM3ua", NI=NATB, DPC="1004", STPF=TRUE, DET=SG, DEVER=DRAFT10; ADD M3DE: DEX=1, DENAME="RncM3ua", NI=NATB, DPC="D04", DET=SP; ADD M3LKS: LSX=0, LSNAME="ToMGW1", ADX=0, WM=ASP; ADD M3RT: RTNAME="ToRNC4", DEX=1, LSX=0; ADD M3RT: RTNAME="ToMGW1", DEX=0, LSX=0; ADD

M3LNK:

MN=132,

LNKN=0,

LNKNAME="TO-MGW1",

LOCIP1="173.20.200.132",


//Add SCCP. ADD

SCCPDSP:

DPX=4,

NI=NATB,

DPC="D04",

OPC="C04",

DPNAME="RNC4",

SHAREFLAG=NONE; ADD

SCCPSSN:

SSNX=4,

NI=NATB,

SSN=RANAP,

SPC="C04",

OPC="C04",

NI=NATB,

SSN=SCMG,

SPC="D04",

OPC="C04",

NI=NATB,

SSN=RANAP,

SPC="D04",

OPC="C04",

SSNNAME="LOCAL-RANAP"; ADD

SCCPSSN:

SSNX=5,

SSNNAME="RNC4-SCMG"; ADD

SCCPSSN:

SSNX=6,

SSNNAME="RNC4-RANAP";

//Add the office direction, global title and service zone of RNC. LST INOFFMSC:; //Query MSC/VLR number ADD OFC: OFFICEDIR=4, ON="RNC4", OOFFICT=RNC, DOL=LOW, DOA=RNC, NI=NAT2, DPC1="D04", SIG=MTP3; ADD

RNC:

RNCID=4,

NI=NATIONBK,

OSP="C04",

SARL=A-1&B-1&C-1&D-1&E-1&F-1&G-1&H-1&SID-1&RATE0-1,

MLAIF

DPC="D04", =FALSE

,

LAI="460000003"; ADD

LAISAI:

SAI="460000003",

VLRN="8613600004",

LAICAT=LAI,


MSCN="8613600004",

LOCNO=65535,

RNCID1=4,

OFFICNUM="4"; ADD

LAISAI:

SAI="4600000030004",

VLRN="8613600004",

LAICAT=SAI,

A-14


MSCN="8613600004",

LOCNO=65535,

RNCID1=4,



OFFICNUM="4";

//Add access MGW. LST MGW:; //Query MGW Inex ADD RANMGW: OFFICENO=4, MGWIDX=1;

V. Adding a BSC //Query the information. LST OFI:;

//Query the OPC whose NI=NATB

LST SCCPSSN: NI=NATB, SPC="C04"; //Query whether the local end has been configured with SCMG subsystem LST BRD: BT=WCSU; //Query the type of the signaling link configured on WCSU

//Add MTP data. ADD N7DSP: DPX=3, NI=NATB, DPC="C03", OPC="C04", DPNAME="BSC-3"; ADD N7LKS: LSX=3, ASPX=3, LSNAME="BSC-3"; ADD N7RT: LSX=3, DPX=3, RTNAME="BSC-3"; ADD N7LNK: MN=22, LNKN=3, LNKNAME="BSC3-1", LNKTYPE=0, TS=112, LSX=3, SLC=0;

//Add SCCP data. ADD

SCCPDSP:

DPX=3,

NI=NATB,

DPC="C03",

OPC="C04",

DPNAME="BSC-3",

SHAREFLAG=NONE; ADD

SCCPSSN:

SSNX=7,

NI=NATB,

SSN=BSSAP/INAP,

SPC="C04",

OPC="C04",


SCCPSSN:

SSNX=8,

NI=NATB,

SSN=SCMG,

SPC="C03",

OPC="C04",

SSNNAME="BSC-SCMG"; ADD

SCCPSSN:

SSNX=9,

NI=NATB,

SSN=BSSAP/INAP,

SPC="C03",

OPC="C04",

SSNNAME="BSC-BSSAP";

//Add BSSAP data. LST INOFFMSC:; //Query MSC/VLR number LST MGW:; //Query MGW index

ADD OFC: OFFICEDIR=3, ON="BSC-3", OOFFICT=BSC, DOL=LOW, DOA=BSC, NI=NAT2, DPC1="C03", SIG=MTP3; ADD BSC: DPC="C03", BSCNM="BSC-3", MSCMN1=22, RSSC=0, BTSNUM=1, MLAIF=FALSE, LAI="460000001";

ADD

LAIGCI:

GCI="460000001",

LAIGCINAME="BSC3-LAI",

A-15

MSCN="8613600004",



VLRN="8613600004", LAICAT=LAI, LAIT=HVLR, BSCDPC1="C03", OFFICNUM="3"; ADD LAIGCI: GCI="4600000010001", LAIGCINAME="BSC3-GCI", MSCN="8613600004", VLRN="8613600004", LAICAT=GCI, LAIT=HVLR, BSCDPC1="C03",OFFICNUM="3"; ADD RANMGW: OFFICENO=3, MGWIDX=1;

//Add trunk data. ADD

ACPOOL:

CPNO=0,

BCR=SFR1-1&SFR2-1&SFR3-1&SHR1-1&SHR2-1&SHR3-1&DFR-1&DHR-1; ADD AIETG: TG=3, MGW=1, SOPC="C04", SDPC="C03", TGN="BSC-3", CPN=0; ADD AIETKC: MN=22, TG=3, SC=96, EC=127, SCIC=0, SCF=TRUE, TID=96; MOD AIETKC: MN=22, SC=112, EC=112, CS=UNU; MOD AIETKC: MN=22, SC=96, EC=96, CS=UNU;

VI. Adding a HLR //Add MTP layer data. ADD N7DSP: DPX=11, DPC="12345", OPC="CC0004", DPNAME="HLR"; ADD N7LKS: LSX=11, ASPX=11, LSNAME="HLR"; ADD N7RT: LSX=11, DPX=11, RTNAME="HLR"; ADD N7LNK: MN=23, LNKN=1, LNKNAME="HLR",LNKTYPE=0, TS=48, LSX=11, SLC=0;

//Add SCCP layer data. ADD

SCCPDSP:

DPX=11,

NI=NAT,

DPC="12345",

OPC="CC0004",

DPNAME="HLR",

SHAREFLAG=NONE; ADD

SCCPSSN:

SSNX=10,

NI=NAT,

SSN=SCMG,

SPC="12345",

OPC="CC0004",

NI=NAT,

SSN=HLR,

SPC="12345",

OPC="CC0004",

SSNNAME="HLR-SCMG"; ADD

SCCPSSN:

SSNX=11,

SSNNAME="HLR-HLR";

ADD IMSIGT: MCCMNC="46000", CCNDC="86139"; ADD

SCCPGT:

GTX=8,

GTNAME="HLR-IMSIGT",

NUMPLAN=ISDNMOV,

ADDR=K'86139,

RESULTT=LSPC2, SPC="12345"; ADD SCCPGT: GTX=9, GTNAME="HLR-NUMBER", NUMPLAN=ISDN, ADDR=K'8613907550000, RESULTT=LSPC2, SPC="12345"; ADD SCCPGT: GTX=10, GTNAME="HLR-MSIDSN", ADDREXP=INTER, ADDR=K'861390755, RESULTT=STP1, SPC="12345";

VII. Adding a MSC Server //Add MTP layer data. ADD N7DSP: DPX=1, DPC="AA0001", OPC="CC0004", DPNAME="MSC-1";

A-16



ADD N7LKS: LSX=1, ASPX=1, LSNAME="MSC-1"; ADD N7RT: LSX=1, DPX=1, RTNAME="MSC-1"; ADD N7LNK: MN=22, LNKN=1, LNKNAME="MSC-1", LNKTYPE=0, TS=48, LSX=1, SLC=0;

//Add SCCP layer data. ADD SCCPDSP: DPX=1, NI=NAT, DPC="AA0001", OPC="CC0004", DPNAME="MSC-1", SHAREFLAG=NONE; ADD

SCCPSSN:

SSNX=12,

NI=NAT,

SSN=SCMG,

SPC="AA0001",

OPC="CC0004",

NI=NAT,

SSN=MSC,

SPC="AA0001",

OPC="CC0004",

NI=NAT,

SSN=VLR,

SPC="AA0001",

OPC="CC0004",

SSNNAME="MSC-SCMG"; ADD

SCCPSSN:

SSNX=13,

SSNNAME="MSC1-MSC"; ADD

SCCPSSN:

SSNX=14,

SSNNAME="MSC1-VLR";

ADD

SCCPGT:

GTX=1,

GTNAME="MSC1-GT",

NI=NAT,

GTI=GT4,

NUMPLAN=ISDN,

ADDREXP=INTER, ADDR=K'8613500001, RESULTT=LSPC2, SPC="AA0001";

//Configure the office direction directing to MSC. ADD OFC: OFFICEDIR=1, ON="MSC-1", OOFFICT=MSC, DOL=SAME, DOA=MSC, NI=NAT, DPC1="AA0001", SIG=MTP3; ADD SRT: SRC=1, O=1, SRN="MSC-1"; ADD RT: R=1, RN="MSC-1", SR1=1; ADD RTANA: RSC=1, RSSC=0, RUT=ALL, ADI=ALL, TP=ALL, TMX=0, R=1, ISUP=ISUP_F;

//Configure the SS7 link directing to MSC. ADD

N7TG:

TG=1,

MGW=1,

G=INOUT,

SRC=1,

SOPC="CC0004",

SDPC="AA0001",


VIII. Adding a SCP //Add MTP layer data. ADD N7DSP: DPX=12, DPC="D02302", OPC="CC0004", DPNAME="SCP-12"; ADD N7LKS: LSX=12, ASPX=12, LSNAME="SCP-12"; ADD N7RT: LSX=12, DPX=12, RTNAME="SCP-12"; ADD N7LNK: MN=23, LNKN=2, LNKNAME="SCP-12", LNKTYPE=0,TS=80, LSX=12, SLC=0;

//Add SCCP layer data.

A-17



ADD SCCPDSP: DPX=12, NI=NAT, DPC="D02302", OPC="CC0004", DPNAME="SCP-12", SHAREFLAG=NONE; ADD

SCCPSSN:

SSNX=15,

NI=NAT,

SSN=CAP,

SPC="CC0004",

OPC="CC0004",

NI=NAT,

SSN=SCMG,

SPC="D02302",

OPC="CC0004",

NI=NAT,

SSN=CAP,

SPC="D02302",

OPC="CC0004",

SSNNAME="MSC-CAP"; ADD

SCCPSSN:

SSNX=16,

SSNNAME="SCP-SCMG"; ADD

SCCPSSN:

SSNX=17,

SSNNAME="SCP-CAP";

ADD SCCPGT: GTX=12, GTNAME="SCP-NUMBER ", NI=NAT, GTI=GT4, NUMPLAN=ISDN, ADDREXP=INTER, ADDR=K'8613600012, RESULTT=LSPC2, SPC="D02302";

//Add SCP data. ADD

SSPCAPA:

SRVKEY=1,

SSPCAPA=IPRA-1&VOICEBACK-1&SPREC-1&VOICEREC-1&TEXTTOV-1; ADD SCPINFO: SCPADDRIDX=0, SCPADDR=K'8613600012, CAPVER=2, SCFID="1"; ADD SCPPARA: SCPPARAIDX=1, SCPADDRIDX=0, SRVKEY=1, DCH=CTNUCALL;

IX. Adding a SMC //Add MTP layer data. ADD N7DSP: DPX=13, DPC="D02303", OPC="CC0004", DPNAME="SMC-13"; ADD N7LKS: LSX=13, ASPX=13, LSNAME="SMC-13"; ADD N7RT: LSX=13, DPX=13, RTNAME="SMC-13"; ADD N7LNK: MN=23, LNKN=3, LNKNAME="SMC-13", LNKTYPE=0,TS=112, LSX=13, SLC=0;

//Add SCCP layer data. ADD SCCPDSP: DPX=13, NI=NAT, DPC="D02303", OPC="CC0004", DPNAME="SMC-13", SHAREFLAG=NONE; ADD

SCCPSSN:

SSNX=18,

NI=NAT,

SSN=SCMG,

SPC="D02303",

OPC="CC0004",

NI=NAT,

SSN=MSC,

SPC="D02303",

OPC="CC0004",

SSNNAME="SMC-SCMG"; ADD

SCCPSSN:

SSNX=19,

SSNNAME="SMC-MSC";

ADD

SCCPGT:

GTX=13,

GTNAME="SMC

GT",

NI=NAT,


//Modify MAP configuration parameter table. MOD MAPACCFG: ISSSMMO=YES, ISSSMMT=YES;

A-18

GTI=GT4,

NUMPLAN=ISDN,



X. Adding a PSTN //Add MTP layer data. ADD N7DSP: DPX=2, NI=NAT, DPC="BB0002", DPNAME="PSTN-2"; ADD N7LKS: LSX=2, ASPX=2, LSNAME="PSTN-2"; ADD N7RT: LSX=2, DPX=2, RTNAME="PSTN-2"; ADD N7LNK: MN=22, LNKN=2, LNKNAME="PSTN1-2", LNKTYPE=0, TS=80, LSX=1, SLC=1, SLCS=2;

//ADD the data of the route to PSTN. ADD OFC: OFFICEDIR=2, ON="PSTN-2", OOFFICT=NATT, DOL=SAME, DOA=PSTN, NI=NAT, DPC1="BB0002", SIG=MTP3; ADD SRT: SRC=2, O=2, SRN="PSTN-2"; ADD RT: R=2, RN="PSTN-2", SR1=2; ADD RTANA: RSC=2, RSSC=0, RUT=ALL, ADI=ALL, TP=ALL, TMX=0, R=2, ISUP=ISUP_F;

//ADD the data of the SS7 trunk circuit leading to PSTN. ADD

N7TG:

TG=2,

MGW=1,

G=INOUT,

SRC=2,

SOPC="CC0004",

SDPC="BB0002",

TGN="PSTN-2", ICR=LCO-1&LC-1&LCT-1&NTT-1&ITT-1, CRF=B0-1&B1-1; ADD N7TKC: MN=25, TG=2, SC=64, EC=95, SCIC=32, SCF=TRUE, TID=64; MOD N7TKC: MN=25, SC=80, EC=80, CS=UNU; MOD N7TKC: MN=25, SC=64, EC=64, CS=UNU;

XI. Adding a SGSN //Add MTP layer data. ADD N7DSP: DPX=14, DPC="D02304", OPC="CC0004", DPNAME="SGSN-14"; ADD N7LKS: LSX=14, ASPX=14, LSNAME="SGSN-14"; ADD N7RT: LSX=14, DPX=14, RTNAME="SGSN-14"; ADD N7LNK: MN=23, LNKN=16, LNKNAME="SGSN-14", LNKTYPE=0, TS=144, LSX=14, SLC=0;

//Add SCCP layer data. ADD SCCPDSP: DPX=14, NI=NAT, DPC="D02304", OPC="CC0004", DPNAME="SGSN-14", SHAREFLAG=NONE;

ADD

SCCPSSN:

SSNX=20,

NI=NAT,

SSN=GS,

SPC="CC0004",

OPC="CC0004",

SSN=SCMG,

SPC="D02304",

OPC="CC0004",

SSN=GS,

SPC="D02304",

OPC="CC0004",

SSNNAME="MSC-GS"; ADD

SCCPSSN:

SSNX=21,

NI=NAT,

SSNNAME="SGSN-SCMG"; ADD

SCCPSSN:

SSNX=22,

NI=NAT,

A-19



SSNNAME="SGSN-GS";

ADD

SCCPGT:

GTX=14,

GTNAME="SGSN

GT",

NI=NAT,

GTI=GT4,

NUMPLAN=ISDN,

ADDR=K'8613600014, RESULTT=LSPC1, SSN=GS,SPC="D02304";

//Configure SGSN number. ADD SGSNNO: SGSN=K'8613600014; MOD MSFP: ID=P106, VAL="2"; MOD MAPACCFG: SUPGSIE=YES;

XII. Adding a GMLC //Add MTP layer data. ADD N7DSP: DPX=15, DPC="D02305", OPC="CC0004", DPNAME="GMLC-15"; ADD N7LKS: LSX=15, ASPX=15, LSNAME="GMLC-15"; ADD N7RT: LSX=15, DPX=15, RTNAME="GMLC-15"; ADD N7LNK: MN=23, LNKN=17, LNKNAME="GMLC-15", LNKTYPE=0, TS=176, LSX=15, SLC=0;

//Add SCCP layer data. ADD SCCPDSP: DPX=15, NI=NAT, DPC="D02305", OPC="CC0004", DPNAME="GMLC-15", SHAREFLAG=NONE;

ADD

SCCPSSN:

SSNX=23,

NI=NAT,

SSN=SCMG,

SPC="D02305",

OPC="CC0004",

NI=NAT,

SSN=GMLC,

SPC="D02305",

OPC="CC0004",

SSNNAME="GMLC-SCMG"; ADD

SCCPSSN:

SSNX=24,

SSNNAME="GMLC-GMLC";

ADD

SCCPGT:

GTX=15,

GTNAME="GMLC

GT",

NI=NAT,

GTI=GT4,

NUMPLAN=ISDN,


//Configure LCS data. ADD GMLC: GMLC=K'8613600015; ADD GMLCCLT: CLTID=K'8613900111, GMLC=K'8613600015; ADD ECLLCSCLT: DN=K'8613975500008, GCI="460000003", CLTID=K'8613900111; ADD ESRVCAT: EMRSRV=EMG PLC, SRVDN=K'8613975500008; ADD CNACLD: P=1, PFX=K'139755, CSTP=BASE, CSA=MLCO, MINL=11, MAXL=11, GAIN=LGN, RCM=NOC, ECOS=YES, ICLDTYPE=MS, ISEACM=FALSE;

A-20



XIII. Configuring basic number analysis //Configure MSRN/HON number allocation, number segment allocated by LAI. ADD NACODE: NAC=K'136;

ADD MHPREFIX: ID=0, HPFX=K'8613600004, SFXL=4; ADD

MHSUFFIX:

ID=0,

PFXIDX=0,

SFXS="0001",

SFXE="0999",

MSRNT=MSRNHON;

SFXE="1999",

MSRNT=MSRNHON;

//index is 0 for suffix 0001~0999 ADD

MHSUFFIX:

ID=1,

PFXIDX=0,

SFXS="1000",

//index is 1 for suffix 1000~1999 LST MHSUFFIX:;

// list the index relationship between prefix and suffix

ADD MHLAICFG: LAI="460000001", PRESFX=0; //MSRN/HON number of 2G cell is 86136000040001~86136000040999, and the cell should be added first. ADD MHLAICFG: LAI="460000003", PRESFX=1; //MSRN/HON number of 3G cell is 86136000041000~86136000041999, and the cell should be added first.

//Configure the data of called number analysis. ADD CNACLD: PFX=K'8613910, CSTP=BASE, CSA=MLC, RSC=1, MINL=11, MAXL=11, GAIN=LGN, RCM=NOC, ICLDTYPE=MSRH, ISEACM=FALSE, SDESCRIPTION="TO MSC-1"; ADD CNACLD: PFX=K'861390752, CSTP=BASE, CSA=MLCO, MINL=11, MAXL=11, GAIN=LGN, RCM=NOC, ICLDTYPE=MS, ISEACM=FALSE; ADD CNACLD: PFX=K'861390755, CSTP=BASE, CSA=MLCO, MINL=11, MAXL=11, GAIN=LGN, RCM=NOC, ICLDTYPE=MS, ISEACM=FALSE; ADD CNACLD: PFX=K'666, CSTP=BASE, CSA=LCO, RSC=2, MINL=6, MAXL=7, GAIN=LGN, RCM=CLRC, ICLDTYPE=PS, IOUTROUTE=YES, ISEACM=FALSE, SDESCRIPTION="TOPSTN";

XIV. Loading preparation //Set online. LON:;

//Turn on alarm switch. SET FMT: STS=ON;

//Format the data. FMT:;

//Power off and on, and load data of all modules.

A-21


Index

Index general procedures, 7-12

A

networking, 7-11

associated mode of signaling, 7-7

parameter relationship, 7-11 configure data for interworking with MGW

B

example, 4-14 general procedures, 4-3

BSC adding access media gateway, 6-26

networking, 4-1

adding A-interface circuit pool, 6-27

parameter relationship, 4-2

adding A-interface trunk circuit, 6-30

relationship between MSC server and MGW, 4-1

adding A-interface trunk group, 6-28

configure data for interworking with MSC

adding BSC global indicator, 6-23

(ISUP/M3UA) example, 9-24

adding LAI or CGI, 6-24 adding MTP destination signaling point, 6-10

general procedures, 9-4

adding MTP link, 6-14

networking, 9-1

adding MTP link set, 6-12

parameter relationship, 9-1 configure data for interworking with MSC (MTP)

adding MTP route, 6-13 adding office direction to BSC, 6-21

example, 8-7

adding SCCP remote signaling point, 6-18


adding SCCP subsystem, 6-20

networking, 8-1

negotiating and preparing data, 6-9

parameter relationship, 8-2 configure data for interworking with PSTN

C

example, 10-20

call prefix, 15-1

general principles, 10-8

call source, 15-1

networking, 10-4

call source code, 15-1

parameter relationship, 10-5 configure data for interworking with RNC

circuit identification code, 10-3

example, 5-25

configure data for interworking with BSC example, 6-32



networkinge, 5-1

networking, 6-1

parameter relationship, 5-2 configure data for interworking with SCP


example, 12-8

configure data for interworking with GMLC example, 14-8



networking, 12-1

networking, 14-1

parameter relationship, 12-2 configure data for interworking with SGSN


example, 13-7

configure data for interworking with HLR


example, 7-19 i-1


Index

networking, 13-1

trunk group bearer, 15-55


trunk group bearer index, 15-56 configure preset data before number analysis

configure data for interworking with SMC example, 11-6

call source, 15-13


number conversion, 15-15 configure route selection data

networking, 11-1

call authority check, 15-35


call authority original called correlation processing,

configure equipment data example, 2-21

15-33


call prefix, 15-29


calling feature analysis, 15-43 calling feature processing, 15-42

configure in service data

calling number analysis, 15-40

examples, 17-10

enhanced route processing, 15-32

configure incoming call number preprocessing incoming calling number correlation processing,

failure processing, 15-47

15-22

number initial special processing, 15-45

incoming number preprocessing, 15-26

service check, 15-38

incoming original called number correlation

configure service data, 1-3

processing, 15-24

configure trunk circuit and TID, 6-4 connected number, 15-4

configure interface data, 1-3 configure mobile service data

D

examples, 16-20 configure MTP link, 6-2

data collection

configure number analysis data

BSC, 6-8

examples, 15-65

equipment data, 2-4

configure office data

GMLC, 14-3

example, 3-22

HLR, 7-13


MGW, 4-3


MSC (ISUP/M3UA), 9-3

configure other number conversion data

MSC Server(MTP), 8-5

auxiliary number processing, 15-60

office data, 3-2

bill control, 15-64

PSTN, 10-8

bill processing information, 15-63

RNC, 5-4

CLIP called correlation processing, 15-57

SCP, 12-4

CLIP processing, 15-59

SGSN, 13-3

MAP interface number processing, 15-62

SMC, 11-3

configure outgoing number preprocessing data

data preparation, 1-6

outgoing calling number correlation processing,

debug M3UA

15-49

FAQ, 18-3

outgoing number preprocessing, 15-53

methods, 18-3

outgoing original called number correlation

debug Mc (H.248)

processing, 15-51

FAQ, 18-9

i-2


Index

methods, 18-8

failure source code, 15-2

debug SCTP

forwarded-to number, 15-4

FAQ, 18-2

G

methods, 18-1 destination signaling point, 7-2

global configuration procedures, 1-2

dialed number set, 15-1

Global Title. see also GT GMLC, 14-1

E

adding called analysis data, 14-7

early ACM, 15-3

adding client GMLC information, 14-5

enhanced roaming restriction

adding emergency call LCS client, 14-6

configuration description, 16-8

adding GMLC number, 14-4

LAI, 16-11

configuring MTP data, 14-4

LAI grouping information, 16-10

configuring SCCP data, 14-4

roaming restriction user group, 16-12

GT, 7-7

roaming subscriber type, 16-13

GT addressing for communication among SPs, 7-8

starting enhanced roaming restriction function,

H

16-10 equipment data

HLR

adding board, 2-9

adding MTP layer data, 7-13

adding CDB function, 2-11

adding SCCP DSP, 7-14

adding FE port information of WIFM, 2-13

adding SCCP GT, 7-16

adding rack, 2-6


adding subrack, 2-8

I

example on global data configuration adding a BSC, A-18

IN service

adding a GMLC, A-23

configuring basic data of local office with SSP

adding a HLR, A-19

function, 17-7

adding a MGW, A-16

configuring data for triggering DCSI, 17-8

adding a MSC Server, A-20

configuring data for triggering N-CSI DP12, 17-7

adding a PSTN, A-22


adding a RNC, A-17


adding a SCP, A-20


adding a SGSN, A-22

configuring data in overlay mode, 17-9

adding a SMC, A-21

configuring special intelligent resource capability

configuring basic number analysis, A-24

data, 17-10

configuring hardware data, A-14

data configuration principles, 17-6

configuring office data, A-15

managing special number information, 17-10

data collection, A-3

incoming number preprocessing, 15-5

description, A-1

incoming number preprocessing data configuration procedures, 15-7

F failure processing, 15-2

i-3


Index

L

adding M3UA link set, 9-9, 9-10 adding M3UA local entity, 9-6

LAI numbering principles, 16-3

adding office direction, 9-14

load sharing, 10-2

adding route, 9-17

local office information, 3-1

adding route analysis data, 9-18

location area, cell, service area, 16-1

adding SS7 trunk circuit, 9-22

location service, 16-2

adding SS7 trunk group, 9-20

location update

adding sub-route, 9-15



setting global title table, 16-5

MSC (MTP)

setting LAI or CGI/SAI, 16-5

adding routing information, 8-6

setting local office SCCP subsystem, 16-7

adding SS7 trunk circuit, 8-7

setting SCCP GT, 16-6


lock clock reference source through BITS


checking clock reference source, 2-21

MSC number, 3-1

clock reference source, 2-20

MSC/VLR numbering principles, 16-4

E1 information, 2-20

MSISDN numbering principles, 16-3


MSRN/HON allocation mode

loading equipment data, 2-21

adding corresponding relationship between LAI

WEPI and WCKI, 2-19

and MSRN, 3-20

lock clock reference source through E1

adding corresponding relationship between MSC

checking clock reference source, 2-18

and MSRN, 3-21

clock reference from WEPI, 2-17

adding MSRN/HON prefix, 3-18

clock reference source, 2-15

adding MSRN/HON suffix, 3-19

E1 information, 2-16

MTP, 10-1


MTP load sharing, 7-5

WEPI and WCKI, 2-14

multiple signaling points, 3-2

M

mutual-assistant nodes, 3-2

MGW

N

adding MGW, 4-4

number analysis, 15-6

adding SCTP link to MGW, 4-8

number analysis and routing data configuration

setting SCTP checksum algorithm, 4-11

procedures, 15-8

setting tone playing capability of MGW, 4-12

number analysis preset data configuration

MML

procedures, 15-6

classification of commands, 1-5

number analysis process, 6-5

using data script, 1-4

number conversion, 15-3

using MML command, 1-4 modes for triggering in services, 17-1

O

module number, 2-4

office data

MSC (ISUP/M3UA) adding M3UA destination entity, 9-7

adding local SCCP GT, 3-15

adding M3UA link, 9-11

adding local SCCP subsystem, 3-14

i-4


Index

adding local VLR information, 3-9

adding zone code, 16-17

adding MAP information, 3-11

configuration description, 16-16

setting local mobile network information, 3-7

configuring LAI, 16-19

setting local office information, 3-5

configuring the relationship between ZC and LAI,

office direction, 10-1

16-18

original called number, 15-4

starting zone code restriction function, 16-17

originating signaling point, 7-1

route and sub-route, 10-2

outgoing number preprocessing, 15-6

route selection code, 10-3, 15-2

outgoing number preprocessing data configuration

route selection source code, 10-3, 15-2

procedures, 15-10

S P

SCCP DSP, 7-6

PSTN

SCCP DSP working mode, 7-6

adding office direction, 10-10

SCCP subsystem, 7-7

adding route, 10-12

SCP

adding route analysis data, 10-14

adding SCP addressing information, 12-6

adding ss7 trunk circuit, 10-16

adding SCP parameter information, 12-7

adding ss7 trunk group, 10-15


adding sub-route, 10-11



configuring SSP capability, 12-5 secondary number analysis, 15-3


service check, 15-3

Q

set MSRN/HON allocation mode general procedures, 3-18

quasi-associated mode of signaling, 7-8

MSRN/HON allocation modes, 3-17

R

parameter relationship, 3-17 SGSN, 13-1

rack number, 2-1


RNC


adding 3G service area, 5-21

configuring SGSN number, 13-4

adding access media gateway, 5-23

modifying map parameter table, 13-5

adding M3UA destination Entity, 5-7

modifying mobile soft parameter, 13-5

adding M3UA link, 5-12

signaling link, 7-4

adding M3UA link set, 5-10

signaling link set, 7-3

adding M3UA local entity, 5-6

signaling route, 7-3

adding M3UA route, 5-11

situations requiring data configuration, 1-1

adding RNC global indicator, 5-20

slot number, 2-2

adding RNC office direction, 5-19

SMC, 11-1

adding SCCP remote signaling point, 5-15





modifying MAP parameter table, 11-4

roaming services, 16-1

subrack number, 2-2

roaming zone code service

i-5


Index

T

W

triggering of IN service by number segment, 17-1

wildcards, 15-2

triggering of overlay outgoing intelligent call, 17-1 triggering of standard CAMEL 3 IN service, 17-5

Z

trunk circuit, 10-3

ZC. see also zone code

trunk group, 10-3

zone code, 16-14

V VLR number, 3-1

i.

i-6

60578261 3 MSOFTX3000 Operation Manual Data Configuration

Recommend Documents