Академический Документы
Профессиональный Документы
Культура Документы
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 ......................................................... Chapter 2 Configuring Equipment Data ........................................................ 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 .....................................
1-1 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 2-1 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............................................................... Chapter 3 Configuring Office Data ................................................................. 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............................................................... Chapter 4 Configuring Data for Interworking with MGW ............................. 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 .............................
2-19 2-19 2-20 2-20 2-21 2-21 2-21 2-21 2-24 3-1 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 4-1 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............................................................... Chapter 5 Configuring Data for Interworking with RNC ............................... 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............................................................... Chapter 6 Configuring Data for Interworking with BSC ............................... 6.1 Introduction to the Chapter ..................................................................... 6.2 Related Concepts ................................................................................... 6.2.1 Networking Between MSOFTX3000 and BSC ...............................
4-2 4-3 4-3 4-4 4-4 4-8 4-10 4-11 4-13 4-13 4-14 5-1 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 6-1 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............................................................... Chapter 7 Configuring Data for Interworking with HLR ............................... 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 ...........................................................................
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 7-1 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............................................................... Chapter 8 Configuring Data for Interworking with MSC (MTP) ................... 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............................................................... Chapter 9 Configuring Data for Interworking with MSC (ISUP/M3UA) ....... 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 ...........................................................................
7-18 7-18 7-19 8-1 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 9-1 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............................................................... Chapter 10 Configuring Data for Interworking with PSTN ........................... 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 ............................................................. Chapter 11 Configuring Data for Interworking with SMC ............................ 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 .............................................................
9-24 9-25 10-1 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 11-1 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 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 ............................................................. Chapter 13 Configuring Data for Interworking with SGSN .......................... 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 ............................................................. Chapter 14 Configuring Data for Interworking with GMLC .......................... 14.1 Introduction to the Chapter ................................................................... 14.2 Related Concepts ................................................................................. 14.2.1 GMLC ........................................................................................... 14.2.2 Networking Between MSOFTX3000 and GMLC ..........................
12-1 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 13-1 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 14-1 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 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-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 ........... Chapter 16 Configuring Mobile Service Data ................................................ 16.1 Introduction to the Chapter ................................................................... 16.2 Related Concepts ................................................................................. 16.3 Configuring Location Update Data .......................................................
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 16-1 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 ................................................................................... Chapter 17 Configuring IN Service Data ........................................................ 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 ..........................................
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 16-20 16-20 16-21 16-21 17-1 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
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 ......................................................................... Chapter 18 Debugging .................................................................................... 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 .............................................................................................. Appendix A An Example on Global Data Configuration .............................. 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 ......................................................................... Index .................................................................................................................
17-9 17-10 17-10 17-10 17-10 17-11 17-11 18-1 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 A-1 A-1 A-1 A-1 A-3 A-11
HUAWEI
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Operation Manual - Data Configuration V100R002
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. Please feel free to contact our local office or company headquarters.
Trademarks
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.
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: Mobile network engineering specialists Operation and Maintenance engineers Mobile network system engineers
Conventions
The manual uses the following conventions:
I. General conventions
Convention Arial Arial Narrow Boldface Courier New Description Normal paragraphs are in Arial. Warnings, Cautions, Notes and Tips are in Arial Narrow. Headings are in Boldface. Terminal Display is in Courier New.
Description Press the keys concurrently. For example, <Ctrl+Alt+A> means the three keys should be pressed concurrently. Press the keys in turn. For example, <Alt, A> means the two keys should be pressed in turn.
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.
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
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
1-1
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-2
1) 2) 3)
Get to know the networking and equipment settings in details, such as board setting and link configuration. Get such interfacing and negotiation data as SS7 links, IP address, and port number. 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. Configuring local office data It covers the configuration of basic information, such as signaling point code of MSOFTX3000 in public land mobile network (PLMN).
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-3
5) 6) 7)
Execute the format conversion command FMT. Execute the LON command. 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.
1.6 Precautions
1.6.1 Before Data Configuration
Before configuring data, complete the following: Obtain the office networking and configuration details. Understand the requirements raised during the project design phase of the office. Read data information about this office carefully and contact related personnel once a defect is found.
Reload data.
Refer to Table 1-2 for details. Table 1-2 Data configuration procedures for deploying a new site Command LOF SET CWSON: SWT=OFF SET FMT: STS=OFF LON SET CWSON: SWT=ON SET FMT: STS=ON FMT Power off, power on, and start loading To set data offline To disable the alarm switch To disable the format conversion switch To set data online To enable the alarm switch To enable the format conversion switch To format data Description
In routine maintenance, implement data configuration in online state, except when executing the command MOD MAXT to modify maximum tuple number in offline state. To open online help for detailed information of commands and parameters, press <F1>.
Important Note: To ensure a quick and secure data configuration process, you need to collect the following data and make corresponding planning in advance.
1-6
Board type
Subrack number
Slot number
Front/back
Module number
Subrack/slot/E1 number of the E1-pool interface board (WEPI) that provides clock reference
1-7
Identify user?
ODB_SS
Support home PLMN (HPLMN) call forwarding on mobile subscriber not reachable (CFNRC)?
/ Support short message mobile originated (SMMO)/short message mobile terminated (SMMT) function? MAP version/ customized applications for mobile network enhanced logic (CAMEL) version
Support prepage?
1-8
Table 1-5 MGW information table Item Data Voice encoding/ decoding mode Encryption algorithm and secret key (optional) of MGW Server or client
Basic information
MGW index
Transmission protocol
Checksum mode
/ Stream control transmission protocol (SCTP) connection information / Local IP forward module (WIFM) address of Link 1
Table 1-6 RNC information table Item RNC basic information / M3UA basic signaling / M3UA link information / Prefix / Prefix (local office) Route selection code M3UA link number Local address LINK 1 IP of Local port IP address of the peer MGW of LINK 1 Port of peer MGW Server or client Service mode Routing context (optional) WIFM module No. RNC ID Signaling point code Network ID Data Location area identity (LAI) Service area identify (SAI) AMR LIST
1-9
Table 1-7 BSC information table Item Basic informatio n / Wireless call control and signaling processing unit (WCSU) module number Intra-module circuit number (E1 number/ timeslot number) Signaling point code Data Network ID of signaling point code Location area identity (LAI) Global cell identification (GCI)
Signaling link
Link set
Link type
/ Termination ID (the number of the physical circuit from MGW to base station controller (BSC)) Circuit identification code (CIC) MGW index
Circuit
/ Trunk route / Prefix / Prefix (local office) Route selection code Office direction Trunk group Circuit type
Table 1-8 MSC information table Item Basic information / WCSU module number Intra-module circuit number (E1 number/times lot number) Signaling point code NI signaling point Data of MSC Server number (E.164 code)
Signaling link
Link set
Link type
1-10
Item Termination ID (the number of the physical circuit from MGW to MSC Server)
Circuit
CIC
MGW index
/ Trunk route / Prefix / Prefix Route selection code Route selection source code Office direction Route number Sub-route number Trunk group Circuit type
Table 1-9 PSTN information table Item Basic information / Intra-module circuit number (E1 number/ timeslot number)Data Signaling point code Data NI of signaling point
Signaling link
Link set
Link type
/ Termination ID (the number of the physical circuit from MGW to PSTN) WCCU/W CSU module number
Circuit
CIC
MGW index
/ Trunk route / Prefix / Prefix Route selection code Route selection source code Office direction Route number Sub-route number Trunk group Circuit type
1-11
Table 1-10 HLR information table Item Basic information / WCSU module number SLC and SLC sending Intra-module circuit number (E1 number/ timeslot number) Signaling point code NI signaling point Data of HLR number (E.164 code)
Signaling link
Link set
Link type
Encoding description
Numbering plan
Address information
Table 1-11 SCP information table Item Basic information / WCSU module number Intra-module circuit number (E1 number/ timeslot number)Data Signaling point code NI signaling point of Data E.164 code
Signaling link
Link set
Link type
1-12
Table 1-12 SMC information table Item Basic information / WCSU module number/WC CU/WSGU SLC and SLC sending Intra-module circuit number (E1 number/ timeslot number)Data Signaling point code NI signaling point Data of E.164 code
Signaling link
Link set
Link type
Table 1-13 SGSN information table Item Basic information / Intra-module circuit number (E1 number/ timeslot number)Data Signaling point code NI signaling point Data of E.164 code
Signaling link
Link set
Link type
Table 1-14 GMLC information table Item Basic information / Signaling link / WCSU module number Intra-module link number SLC and SLC sending Intra-module circuit number (E1 number/ timeslot number) Data Link type Signaling point code NI signaling point of Data E.164 code
Link set
1-13
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.
2-2
Table 2-2 List of boards in MSOFTX3000 Front board WSMU WCCU WCSU WBSG WIFM WAFM WCDB WVDB WMGC WALU UPWR System management unit Moble call control unit Wireless Call control and Signaling processing unit Broadband signaling processing unit IP forward module ATM forward module board Central database board VLR database board Media gateway contorl board Alarm unit Secondary power board UPWR WHSC WCKI Secondary power board Hot-swap control board Clock interface board WSIU WEPI WBFI WBAI Back board System interface unit E1-pool interface board Back FE interface board Back ATM 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: The WSMUs (and back boards WSIUs) must be inserted in slots 6 and 8. The WALU must be inserted in front slot 16. The WHSC must be inserted in back slots 7 and 9, and front panels are installed in corresponding front slots. 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. Other slots (05, 1015) 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.
2-4
Table 2-3 List of equipment data to be collected Frame type Basic frame Board type WCSU WCSU IP address of FE port IP address of the router connecting to MSOFTX3000 Link type (64 kbit/s or 2 Mbit/s) Frame number 0 0 Slot number 0 1 Front/back Front Front Module number 22 22 Slot number of assistant board 1 0 Frame number 0 Site number 1 Row number 1 Column number 1
2-5
ADD SHF
[Shelf Number] [Location Title] [Position Number]
ADD FRM
[Shelf Number] [Frame Number] [Position Number]
ADD EPICFG
[Connect E1 EPI Frame Number] [Connect E1 EPI Slot Number]
ADD BRD
[Frame Number] [Slot Number] [Board Type] [Module Number]
ADD FECFG
[IFM Module Number] [IP Address]
ADD CDBFUNC
[CDP Module Number] [Function]
2-6
II. Command
ADD SHF
2-7
Description To list the properties of the specified shelf If you expect to browse the properties of all shelves in the system, just set the parameter "shelf number" to "ALL".
II. Command
ADD FRM
2-8
II. Command
ADD BRD
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: 221 (automatically assigned by the system) WCCU/WCSU: 22101 WCDB/WVDB: 102131 WMGC/WAFM/WIFM/WBSG: 132211
[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 dont 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-boardone processing 64 kbit/s MTP links, and the other processing 2Mbit/s MTP links.
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
II. Command
ADD CDBFUNC
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
II. Command
ADD FECFG
2-13
2-14
II. Command
ADD BRD
II. Command
SET CKICFG
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: CLK_2M: E1(2 Mbit/s) CLK_E1: 2M(2 MHZ)
II. Command
ADD EPICFG
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: Double frame (DF): default value CRC4: multi-frame format 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: BALANCE indicates that the transmission line is 120-ohm balanced twisted pair. NON_BALANCE indicates that the transmission line is 75-ohm non-balanced coaxial cable. Generally, NON_BALANCE is selected.
2-17
II. Command
ADD BOSRC
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-18
1) 2)
Execute the command DSP BRD to check if the present clock reference source of the WCKI is extracted from the peer office equipment. 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.
II. Command
ADD BRD
2-19
II. Command
SET CKICFG
Important Note: You must set the parameter Clock Level in the command to Level Two.
II. Command
ADD EPICFG
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.
The WIFM of the control unit frame integrates the functions of the WBSG, WMGC and WIFM. The WEPI must be installed in the back slots 0, 1, 2 and 3. The ones in back slots 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) MGW UNIT(Clock 1) MSC SERVER PSTN BSC RNC 0 Back 1 2 3 4 5 HLR SCP SMC SGSN GMLC 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
W E P I
W E P I W C S U
1
W E P I W C S U
2
W E P I W C S U
3
W S I U W C C U
4
W H S C
W S I U W S M U
W H S C
W B F I W I F M
W B F I W I F M W V D B
W C K I 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
Backplan e
W C Front S U
0
W C C U
5
W S M U
6 7
10 11 12 13 14 15 16 17 18 19 20
2-22
Refer to Table 2-16 for the equipment data table. Table 2-16 Equipment data table Frame type Basic frame Board type WCSU WCSU WCSU WCSU WCCU WCCU WIFM WIFM WVDB WVDB WCDB WCDB WEPI WEPI WEPI WEPI WCKI WCKI Frame number 0 Frame number 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Site number 1 Slot number 0 1 2 3 4 5 10 11 12 13 14 15 0 1 2 3 13 15 Row number 1 Front/back Front Front Front Front Front Front Front Front Front Front Front Front Back Back Back Back Back Back Link type (64 kbit/s or 2 Mbit/s) 64 kbit/s Frame/slot/E1 number of the WEPI providing clock reference 0/0/6, 0/2/0 Column number 1 Module number 22 22 23 23 25 25 132 132 102 102 103 103 Slot number of assistant board 1 0 3 2 5 4 11 10 13 12 15 14
2-23
//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 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;
DGW="173.20.200.253";
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:;
2-25
3-1
3-2
Table 3-1 List of MSC Server office data to be collected Item Signaling point / Mobile network data / / / MAP information / Reallocate TMSI during service access and location update procedure? Check IMEI or contain IMEI in bill during service access and location update procedure? Authorize during service access and location update procedure? Mobile network code (MNC) Network (NC) code Nation code Region code Local MSC number Local VLR number National valid network Data National reserved network International network International reserved network
Identify user?
ODB_SS
Cipher algorithm?
/ / / / / Support call hold? Support interface? Gs Support enhanced roaming restriction? Support zone code restriction? Support SMMO/SMMT function? Support prepage? MAP/CAMEL version
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
[National Network Code] [National Reserved Network Code] [Local Area Code] [Nation/Region] [Inter MGW Media Type]
SET INOFFMSC/ADD INOFFMSC
[MSC Number] [VLR Number] [MCC] [MNC]
ADD SCCPGT
[SPC] [Network indicator] [GT address information]
ADD VLRCFG
[MCC] [MNC] [CC]
3-4
II. Command
SET OFI/ADD OFI
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".
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-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.
[BillServerExist] Generally, set this parameter to "TRUE" as the MSC Server needs bill server.
II. Command
ADD VLRCFG
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 subscribers 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.
II. Command
ADD MAPACCFG
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. All outgoing calls barred International outgoing calls allowed or barred International outgoing calls except those to the home PLMN country barred Premium rate information outgoing calls barred Premium rate entertainment outgoing calls barred Supplementary service access barred Operator Determined Barring Type 14 (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.
II. Command
ADD SCCPSSN
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.
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.
3-16
Description To modify existing SCCP global title To list SCCP global title
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]
3-17
II. Command
ADD MHPREFIX
3-18
II. Command
ADD MHSUFFIX
[MSRNHON Number Type] This parameter is used to set the type of the added number. It may be MSRN, HON or MSRN/HON.
II. Command
ADD MHLAICFG
3-20
Table 3-12 List of commands related to configuration of corresponding relationship between LAI and MSRN Command ADD MHLAICFG LST MHLAICFG RMV MHLAICFG Description To add corresponding relationship between LAI and MSRN To list corresponding relationship between LAI and MSRN To remove corresponding relationship between LAI and MSRN
II. Command
ADD MHMSCCFG
3-21
SCP
SMC
HLR
GMLC
MAP/ TDM
MAP/ TDM
MAP/ TDM
MAP/ TDM
MSC Server
ISUP/ TDM
MSOFTX 3000
BSSAP+ /TDM
SGSN
H.248,RANAP /IP
MGW
IP/TDM
MGW (SG)
ISUP/TDM
PSTN
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 National network valid CC0004 Mobile network data / / / Local number 8613600004 Mobile network code (MNC) 460 MSC Data National reserved network valid C04 Local VLR number 8613600004 Network (NC) 00 code Nation code 86 Authorize during service access and location update procedure? No Check IMEI or contain IMEI in bill during service access and location update procedure? No Support prepage? Region code 755 International network valid International reserved network valid
MAP information
Identify user?
ODB_SS
Cipher algorithm?
No Reallocate TMSI during service access and location update procedure? No Support zone code restriction?
All
No
/ /
No
/ /
Support interface? No
Gs
3-23
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 2G cell 3G cell MSRN/HON 8613600004000186136000040999 8613600004100086136000041999 Prefix index 0 0 Suffix index 0 1 LAI number 460000001 460000003
HONAM=LAI;
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,
//Add local SCCP subsystem, including MSC, VLR and SCMG subsystems.
ADD SCCPSSN: SSNX=0, NI=NAT, SSN=MSC, SPC="CC0004", OPC="CC0004",
SSNNAME="LOCAL-SCMG";
3-24
SSNNAME="LOCAL-NATB-SCMG";
//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; index is 0 for suffix 0001~0999. ADD MHSUFFIX: ID=1, PFXIDX=0, SFXS="1000", SFXE="1999", MSRNT=MSRNHON; index is 1 for suffix 10001999. LST MHSUFFIX; //List the index relationship between prefix and suffix. //The //The
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
4-1
Mc
MGW
ADD MCLNK
[MGW index] [BSG/IFM/AFM/SGU/MGC Module No.] [Local IP1] [Local Port] [Remote IP1] [Remote Port] [Transport Protocol]
ADD FECFG
[IFM Module Number] [IP Address ] [Mask Address]
SET SCTPPARA
[Checksum Arithmeticr]
4-2
4-3
II. Command
ADD MGW
Note: This command is used to add a MGW, and to set its basic information and MGW capability.
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. ATM network: AAL1Struct, AAL1 or AAL2 IP network: IP TDM network: TDM [Special Attributes] It defines the special attributes of MGW in specific networking. The meanings of the options are as follows: 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. 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. No Echo Cancellation: It defines whether the MGCP/H.248 messages sent by the MSOFTX3000 to the MG contain no echo cancellation (EC) field. No Jitter: It defines whether the MGCP/H.248 messages sent by the MSOFTX3000 to the MG contain no jitter buffer field. No Fax: It defines whether to detect fax. No Modem: It defines whether to detect modem. 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: 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. 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. 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).
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.
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: Bearer over IP: SCTP and UDP 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.
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.
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.
4-12
Table 4-6 Command related to configuration of tone playing capability of MGW Command ADD TONECFG LST TONECFG MOD TONECFG RMV TONECFG Description To define the tone playing capability of MGW To list the tone playing capability of MGW To modify the tone playing capability of MGW To remove the tone playing capability of MGW
SCP
SMC
HLR
GMLC
MAP/TDM MAP/TDM
MAP/TDM
MAP/TDM
MSC Server
ISUP/TDM
MSOFTX 3000
BSSAP+/TDM
SGSN
H.248,RANAP/ IP
MGW
ISUP/TDM
PSTN
RANAP/AAL2 /ATM
BSSAP/ TDM
RNC
BSC
4-13
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 / MGW index Transport layer protocol SCTP Local IP address of the WIFM 173.20.200. 132 Data Tone coding/dec oding mode All Local port number of the WIFM 2945 Checksu m mode
Server /client
MGW ciphering algorithm and ciphering key (optional) None Remote port number of MGW 2945
CRC32
Server
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.
BNCC=IP-1&AAL1-1,
DEVNAME="MGW1",
SVRCLIENT=SVR,
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;
4-14
4-15
5-1
(SG)
RANAP SCCP MTP3B SAAL ATM PHY MTP3B SAAL ATM 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
ADD SCCPDSP
[NI] [OPC] [DPC] (of RNC) ---
ADD SCCPSSN
[NI ] [SSN] [SPC] [OPC] ---
ADD M3DE
[Local Entity Index] [Destination Entity Index] [NI] [Destination Entity Point Code] [Destination Entity Type] [Adjacent Flag] ---
ADD OFC
[NI] [Office directioin] [Destination Point Code] ---
ADD M3LKS
[Adjacent Entity Index] [Work Mode] [Link Set Index] ---
ADD M3RT
[Destination Entity Index] [Link Set Index ]
ADD RNC
[Destination Point Code] [RNC ID] [Network ID] [Oragination Point Code] ---
ADD M3LNK
[Linkset Index] [Module No](ADD FECFG) [Local IP Address ](ADD FECFG)] [Local Port] [Peer IP Address [Peer Port] [C/S Mode] ---
ADD LAISAI
[RNC ID] [MSC/VLR Number of 3G Service Area] [Call Source Code] [Office No.] ---
ADD RANMGW
[Office Number] [Media Gateway Index] (ADD RANMGW)
5-3
Table 5-1 Procedures and commands for configuring interworking data between MSOFTX3000 and RNC (based on IP) Procedure 1: Negotiate and prepare data to be configured at MGW side 2: Add M3UA local entity 3: Add M3UA destination entity 4: Add M3UA link set 5: Add M3UA route 6: Add M3UA link 7: Add SCCP remote signaling point 8: Add RANAP subsystem 9: Add RNC office direction 10 Add RNC global indicator 11: Add 3G service area 12: Add access media gateway ADD M3LE ADD M3DE ADD M3LKS ADD M3RT ADD M3LNK ADD SCCPDSP ADD SCCPSSN ADD OFC ADD RNC ADD LAISAI ADD RANMGW Command
5-4
Table 5-2 Table of data collected for MSOFTX3000 interworking with RNC Item Basic RNC information / Basic M3UA signaling / M3UA link information / Prefix / Local prefix Route selection code M3UA link number Local IP Local port IP address of the peer MGW Port number of the peer MGW Server/Cli ent Service mode Route context (optional) WIFM module number SG signaling point code RNC ID Signaling point code Network indicator Data LAI SAI AMR LIST
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
II. Command
ADD M3LE
5-6
Table 5-3 List of commands related to M3UA local entity configuration Command ADD M3LE RMV M3LE MOD M3LE LST M3LE To add M3UA local entity To remove M3UA local entity To modify M3UA local entity To list M3UA local entity Description
II. Command
ADD M3DE
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: INCLUSIVE: The traffic that belongs to this point code of a destination entity is shared with other destination entities. 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
II. Command
ADD M3LKS
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. 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. 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. 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".
5-10
II. Command
ADD M3RT
5-11
II. Command
ADD M3LNK
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: 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. 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.
5-13
Command MOD M3LNK LST M3LNK DSP M3LNK EST M3LNK REL M3LNK LCK M3LNK ULK M3LNK DEA M3LNK ACT M3LNK To modify M3UA link To list M3UA link
Description
To display M3UA link of the host To establish M3UA link To release M3UA link To block M3UA link To unblock M3UA link To deactivate M3UA link To activate M3UA link
II. Command
ADD SCCPDSP
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: No Standby DSP: Not support backup function Backup DSP: Support active/standby function 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.
5-15
Table 5-8 List of commands related to SCCP DSP configuration Command ADD SCCPDSP RMV SCCPDSP MOD SCCPDSP LST SCCPDSP DSP SCCPDSP SET SCCPDSP To add SCCP DSP To remove SCCP DSP To modify SCCP DSP To list information about all configured SCCP DSPs To display information about all configured SCCP DSPs of BAM To set the state of SCCP DSP Description
II. Command
ADD SCCPSSN
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.
5-17
II. Command
ADD OFC
5-18
Table 5-10 List of commands related to office direction configuration Command ADD OFC RMV OFC MOD OFC LST OFC Description To add an office direction To remove an existing office direction To modify attributes of an existing office direction To list information about configured office direction
II. Command
ADD RNC
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.
II. Command
ADD LAISAI
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.
II. Command
ADD RANMGW
5-22
Table 5-13 List of commands related to access media gateway configuration Command ADD RANMGW RMV RANMGW MOD RANMGW LST RANMGW Description To add RAN-MGW connection information To remove an existing RAN-MGW connection information To modify attributes of an existing RAN-MGW connection information To list information about configured RAN-MGW connection information
SCP
SMC
HLR
GMLC
MAP/TDM MAP/TDM
MAP/TDM
MAP/TDM
MSC Server
ISUP/TDM
MSOFTX 3000
BSSAP+/TDM
SGSN
H.248,RANAP /IP
MGW
IP/TDM
MGW (SG)
ISUP/TDM
PSTN
RANAP/AAL2/ATM
BSSAP/TDM
RNC
BSC
5-23
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 Basic RNC information / Basic M3UA signaling / M3UA link information / RNC ID 4 Service mode Load sharing M3UA link number 0 Signaling point code D04 Route context (optional) NULL Network indicator National reserved WIFM module number 132 Data LAI 460000003 SG signaling point code 1004 IP address of the peer MGW 173.20.200.9 3 Port of peer MGW 2905 Server/Clie nt Client SAI 4600000 030004 AMR LIST All
Local port
2905
Prefix /
5-24
//Add SCCP.
ADD SCCPDSP: DPX=4, NI=NATB, DPC="D04", OPC="C04", DPNAME="RNC4",
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", MLAIF DPC="D04", =FALSE ,
MSCN="8613600004", RNCID1=4,
LOCNO=65535,
SAI="4600000030004", LAICAT=SAI,
LAIGCINAME="RNC4", LAIT=HVLR,
MSCN="8613600004", RNCID1=4,
VLRN="8613600004", OFFICNUM="4";
LOCNO=65535,
5-25
6-1
MSOFTX3000
TDM bearer
6-2
WEPI
WEPI
CPC
CPC
CPC
CPC
WCSU0
WCSU1
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 015 and the upper one processes links 1631. 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 (07), that is TDM timeslots 0255. 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: Links 015 correspond to circuits (E1/TDM) 03/0127. That is, for links 015, only TDM timeslots 0127 can be used. Timeslot 0 of each E1 is the synchronization timeslot, which cannot be used as link. Links 1631 correspond to circuits (E1/TDM) 47/128255. That is, for links 1631, only TDM timeslots 128255 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 (432+15=143) when you use the ADD N7LNK command.
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: Physical circuit (E1): 4/16, where 4 means E1 number and 16 indicates the timeslot number used by the link. TID: Termination ID, which must be consistent with the number of the physical circuit of MGW to BSC. Here the value range is 96127. CIC: Circuit Identification Code, which must be consistent with that of BSC. Here the value range is 031.
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.
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.
6-5
MAP_SRI_Req [MSISDN]
6-6
BSC parameter
MSOFTX3000 parameter
ADD N7DSP ADD N7LKS [Link Set] [Adjacent Point Index] ADD N7RT [Link Set] [DSP index] [Priority] ADD N7LNK [Link No] [ Start Circuit No] [ Link Set ] Code [ Signaling Link Code] ADD OFC [Network ] [signal bearer type] [Destination Point Code] [Office directioin number] ADD BSC [Destination Point Code] [Home Module No.1] [Network ID] [Location area ID] ADD LAIGCI [Global Cell ID] [MSC Number of the LAI or Cell] [VLR Number of the LAI or Cell]
[DSP index] [Network Indicator] [Destination Point Code] [Original Point Code] ADD SCCPDSP [Network Indicator] [DPC] [OPC]
aling link code (SLC) ADD SCCPSSN [Network Indicator] [SSN Code] [Signaling Point Code] [OPC]
ADD AIETG [Trunk Group] [Destination Point Code] [OriginaL Point Code] [MGW INDEX] ADD AIETKC [Trunk Group] [Start CIC] [START CIRCUIT TERMINATION ID] ADD RANMGW [Media Gateway Index] [Office number]
6-7
Table 6-1 Procedures for configuring data at MSOFTX3000 for interworking with BSC Procedure 1: Negotiate and prepare data 1) Configure interworking data between MSOFTX3000 and MGW 2) Add semi-permanent connection at MGW 2. Configure MTP3 data for interworking with BSC 1) Add MTP DSP 2) Add MTP link set 3) Add MTP route 4) Add MTP link 3. Configure SCCP data for interworking with BSC 1) Add SCCP remote signaling point 2) Add SCCP subsystems (including local subsystem and remote subsystem) 4. Configure BSSAP 1) Add office direction to BSC 2) Add BSC global indicator 3) Add location area 4) Add cell 5) Add connection between BSC and MGW 5. Configure A interface trunk circuit 1) Add A interface circuit pool. 2) Add A interface circuit group. 3) Add A interface circuit./Mod A interface circuit state ADD ACPOOL ADD AIETG ADD AIETKC/ MOD AIETKC ADD OFC ADD BSC ADD LAIGCI (LAI) ADD LAIGCI (GCI) ADD RANMGW ADD SCCPDSP ADD SCCPSSN ADD N7DSP ADD N7LKS ADD N7RT ADD N7LNK Command ADD MGW (LST FECFG) SET DPA ADD TDMIU ADD SPC
6-8
Table 6-2 Data for interworking with BSC Item Basic information Signaling point code Signaling point network indicator Data LAI GCI
Signaling link
Link set
Link type
Circuit
CIC
MGW index
Trunk route
Office direction
Trunk group
Circuit type
Prefix
Local prefix
6-9
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.
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.
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.
6-12
II. Command
ADD N7RT
6-13
II. Command
ADD N7LNK
[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: TDM 64K link: 64-kbit/s MTP links born over TDM. It is provided by MSOFTX3000 directly. TDM 2M link: 2-Mbit/s MTP links born over TDM. It is provided by MSOFTX3000 directly. M2UA 64K link: 64-kbit/s MTP links born over M2UA. It is provided by bulilt-in SG (UMG8900, for example). 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): 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. 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. 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. 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: 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. 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.
6-17
command to check whether the BSC DPC is consistent with that in the MTP3 DSP table.
II. Command
ADD SCCPDSP
6-18
Table 6-7 List of commands related to SCCP DSP configuration Command ADD SCCPDSP RMV SCCPDSP MOD SCCPDSP LST SCCPDSP DSP SCCPDSP SET SCCPDSP To add an SCCP DSP To remove an existing SCCP DSP To modify an existing SCCP DSP To list the information of all configured SCCP DSPs To display statuses of all configured SCCP DSPs To manage and maintain SCCP DSPs Description
II. Command
ADD SCCPSSN
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.
6-20
Note: This command is used to set the office direction from MSOFTX3000 to BSC.
6-21
II. Command
ADD BSC
6-22
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.
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.
6-24
Table 6-11 List of commands related to LAI/CGI configuration Command ADD LAIGCI MOD LAIGCI LST LAIGCI RMV LAIGCI To add LAI or CGI To modify LAI or CGI To list LAI or CGI To remove LAI or CGI Description
II. Command
ADD RANMGW
Note: This command is used to create the connection between the BSC office direction and MGW.
6-25
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.
6-26
II. Command
ADD AIETG
6-27
Command RMV TG
II. Command
ADD/MOD AIETKC
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.
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
HLR
GMLC
MAP/TDM MAP/TDM
MAP/TDM MAP/TDM
MSC Server
ISUP/TDM
MSOFTX 3000
BSSAP+/TDM
SGSN
H.248,RANAP /IP
MGW
IP/TDM
MGW (SG)
ISUP/TDM
PSTN
RANAP/AAL2/ATM
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 Basic information / Signaling link Signaling point code C03 Signaling point network indicator National reserved Data LAI GCI
460 00 0001 0001 Intra-module circuit number (E1 number/time slot number) 112 (3/16)
Link set
Link type
/ Circuit
3 CIC
64 kbit/s
Termination ID (the number of the physical circuit from MGW to BSC) 96127 Office direction 3
/ Trunk route
Prefix
Local prefix
1390752
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
6-31
SSNNAME="BSC-BSSAP";
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;
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
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.
STP
DPC1
Figure 7-1 DSP configuration To add a DSP, you need to determine the following data: SPC ID of the network where the SP is located The OPC related to this SP Whether it is the adjacent SP, that is, whether the DSP is directly connected through the link Selection mask of the link set in the signaling route to this SP 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: Signaling link set number The adjacent DSP to which the signaling link set is connected 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
Signaling point 1
Signaling point 2
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: DSP index Link set number 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
7-4
Load sharing among links in one link set 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
XXX1 F XXXX C
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.
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 A
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: SPC Local SPC Load sharing SP index
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: Indicator of the network to which the subsystem belongs Local SPC SSN 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.
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
A SP := SPB C = OP PC: D
B SP A : = SP PC := O PC D
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.
A SP := STP C = OP PC: D
B SP P : = ST PC := O PC D
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) 2) SP A sends a signaling message in DPC (of STP) +GT (of SP B) mode. After MTP of STP receives the MTP message from SP A, it sends the message to its own SCCP.
7-8
3) 4) 5)
SCCP performs GT translation to obtain DPC+SSN, in which DPC and SSN are both of SPB. SCCP distributes the message to the MTP layer. MTP sends the message to SP B according to the DPC.
SCCP
SCCP
SCCP
MTP DPC+GT
MTP DPC+SSN
MTP
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.
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-10
ADD N7LKS
[LinkSet Index] [Adjacent DSP Index]
ADD N7RT
[Linkset index] [DSP index]
ADD SCCPDSP
[NI] [DPC] [OPC] SLC
ADD N7LNK
[Link No.] [Start Circuit No.] [Linkset index] [Signaling Link Code]
ADD SCCPSSN
[NI ] [SSN] [SPC] [OPC]
ADD SCCPGT
[NI] HLR number IMSI number segment MSISDN number segment [GT Address Information] [SPC]
7-11
Procedure 2. Configure SCCP 1) Add SCCP remote SP 2) Add SCCP subsystem 3) Add SCCP GT
Signaling link
Link set
Link type
II. Command
The procedures to add MTP link data are as follows:
7-12
1) 2) 3) 4)
Add MTP DSP (ADD N7DSP) Add MTP link set (ADD N7LKS) Add MTP route (ADD N7RT) Add an MTP link (ADD N7LNK)
II. Command
ADD SCCPDSP
Note: This command is used to configure the SP information for the peer HLR.
See Table 7-3 for the commands related to SCCP DSP configuration. Table 7-3 List of commands related to SCCP DSP configuration Command ADD SCCPDSP RMV SCCPDSP MOD SCCPDSP LST SCCPDSP DSP SCCPDSP To add an SCCP DSP To remove an existing SCCP DSP To modify an existing SCCP DSP To list the information of all configured SCCP DSPs To display the information of all configured SCCP DSPs Description
II. Command
ADD SCCPSSN
[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.
7-15
The following gives detailed description: 5) IMSI GT and HLR-NUMBER GT for location update 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,
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. 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)
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
7-17
Table 7-5 List of commands related to SCCP GT configuration Command ADD SCCPGT RMV SCCPGT MOD SCCPGT LST SCCPGT To add an SCCP GT To remove an existing SCCP GT To modify an existing SCCP GT To list SCCP GT Description
SCP
SMC
HLR
GMLC
MAP/TDM MAP/TDM
MAP/TDM MAP/TDM
MSC Server
ISUP/TDM
MSOFTX 3000
BSSAP+/TDM
SGSN
H.248,RANAP / IP
MGW
IP/ TDM
MGW (SG)
ISUP/TDM
PSTN
RANAP/AAL2/ATM
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 Basic information / Signaling point code 12345 Data Signaling point network indicator National network HLR number (E.164 number) 8613907550 000 Signaling link code (SLC) and SLC sending 0 Intra-module circuit number (E1 number/times lot number) 48 (1/16)
Signaling link
Link set
Link type
/ SCCP GT translation / / /
64 kbit/s
SSNNAME="HLR-HLR";
ADD IMSIGT: MCCMNC="46000", CCNDC="86139"; ADD SCCPGT: GTX=8, GTNAME="HLR-IMSIGT", NUMPLAN=ISDNMOV, ADDR=K'86139,
7-19
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
8-1
MSOFTX3000
TDM bearer
Figure 8-1 Networking and protocols between MSOFTX3000 and MSC Server
[Link No.] [Start Circuit No.] ] [LinkSet Index] [Signaling Link Code]
MSC number
Figure 8-2 Parameter relationship between MSOFTX3000 and other MSC Server (MTP and SCCP)
8-2
MSOFTX3000 Parameters
ADD OFC
[NI ] [Office direction number] Destination entity's SPC [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] [Start circuit termination ID]
Figure 8-3 Parameter relationship between MSOFTX3000 and other MSC Server (trunk)
8-3
Table 8-1 Procedures and commands for configuring data at MSOFTX3000 for interworking with other MSC Server Procedure 1. Configure MTP 1) Add MTP DSP 2) Add MTP link set 3) Add MTP route 4) Add MTP link 2. Configure SCCP 1) Add SCCP remote signaling point 2) Add SCCP subsystem 3) Add SCCP GT 3. Configure routing information 1) Add office direction to MSC Server 2) Add sub-route 3) Add route 4) Add route analysis 4. Configure trunk circuit 1) Add SS7 trunk group 2) Add SS7 trunk circuit 3) Mod SS7 trunk circuit ADD OFC ADD SRT ADD RT ADD RTANA ADD N7TG ADD N7TKC Mod N7TKC ADD N7DSP ADD N7LKS ADD N7RT ADD N7LNK ADD SCCPDSP ADD SCCPSSN ADD SCCPGT Command
Basic information
8-4
Data Signaling link code (SLC) and SLC sending Intra-module circuit number (E1 number/time slot number)
Signaling link
Link set
Link type
/ Termination ID (the number of the physical circuit from MGW to MSC Server) WCCU/WC SU module number
Circuit
CIC
MGW Index
/ Trunk route / Prefix / Prefix Route selection code Route selection source code Office direction Route number Sub route number Trunk group Circuit type
8-5
HLR to configure data for the SCCP layer. The steps to add SCCP data are as follows: 1) 2) Add a DSP of SCCP (ADD SCCPDSP): Select National Network for the parameter Network Indicator of the SCCP DPC to MSC. 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-6
SCP
SMC
HLR
GMLC
MAP/TDM MAP/TDM
MAP/TDM MAP/TDM
MSC Server
ISUP/TDM
MSOFTX 3000
BSSAP+/TDM
SGSN
H.248,RANAP /IP
MGW
IP/TDM
MGW (SG)
ISUP/TDM
PSTN
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 Basic information Signaling point code Signaling point network indicator National network Data MSC Server number (E.164 code) 861350000 1 Signaling link code (SLC) and SLC sending 0 WCCU/WC SU module number 25 Trunk group 1 Circuit type ISUP Intra-module circuit number (E1 number/time slot number) 48 (1/16)
AA0001
Signaling link
Link set
Link type
64 kbit/s
Circuit
Termination ID (the number of the physical circuit from MGW to MSC Server) 3263 Office direction 1 Prefix Route number 1 Route selection code 1
CIC
13910
8-8
NI=NAT,
SSN=VLR,
SPC="AA0001",
OPC="CC0004",
8-9
Figure 9-1 Networking and interface protocols between MSOFTX3000 and MSC
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] ---
9-2
Peer end route trunk parameter Local end route trunk parameter
ADD OFC
[Network ID] [Office direction] Destination entity SPC [Destination point code] [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] Starting CIC [Start CIC] [Start circuit termination ID]
Figure 9-3 Parameter relationship between MSOFTX3000 and peer end MSC (route trunk)
9-3
Table 9-1 Table of data collected for the MSOFTX3000 interworking with MSC Item Basic information Signaling point code Network indicator Data
Service mode
Local IP
Local port
Server/Client
Circuit
Termination ID (the physical circuit number at MGW for interworking with MSC Server)
CIC
MGW Index
Trunk circuit
Office direction
Route number
Sub-route number
Trunk group
Circuit type
Prefix
Prefix
9-4
Table 9-2 Procedures and commands for configuring data at MSOFTX3000 for interworking with MSC Procedure 1. Configure M3UA (for interworking with MGW) 1) Add M3UA local entity 2) Add M3UA destination entity 3) Add M3UA link set 4) Add M3UA route 5) Add M3UA link 2. Configure M3UA (for interworking with MSC) 1) Add M3UA destination entity 2) Add M3UA route 3. Configure route information 1) Add office direction to MSC Server 2) Add sub-route information 3) Add route information 4) Add route analysis data 4. Configure trunk circuit 1) Add SS7 trunk group 2) Add/modify SS7 trunk circuit ADD N7TG ADD/MOD N7TKC ADD OFC ADD SRT ADD RT ADD RTANA ADD M3LE ADD M3DE ADD M3LKS ADD M3RT ADD M3LNK ADD M3DE ADD M3RT Command
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.
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.
II. Command
ADD M3LE
9-6
Table 9-3 Commands for M3UA local entity configuration Command ADD M3LE RMV M3LE MOD M3LE LST M3LE To add M3UA local entity To remove M3UA local entity To modify M3UA local entity To list M3UA local entity Description
II. Command
ADD M3DE
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.
9-8
Table 9-4 List of commands related to M3UA destination entity configuration Command ADD M3DE RMV M3DE MOD M3DE LST M3DE DSP M3DE Description To add M3UA destination entity To remove M3UA destination entity To modify M3UA destination entity To list M3UA destination entity To display the state of M3UA destination entity of the host
II. Command
ADD M3LKS
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. 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. 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. 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".
9-10
II. Command
ADD M3RT
9-11
II. Command
ADD M3LNK
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: 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. 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.
9-13
Table 9-7 List of commands related to M3UA link configuration Command ADD M3LNK RMV M3LNK MOD M3LNK LST M3LNK DSP M3LNK EST M3LNK REL M3LNK LCK M3LNK ULK M3LNK DEA M3LNK ACT M3LNK To add M3UA link To remove M3UA link To modify M3UA link To list M3UA link To display M3UA link state of the host To establish M3UA link To release M3UA link To block M3UA link To unblock M3UA link To deactivate M3UA link To activate M3UA link Description
II. Command
ADD OFC
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.
9-15
II. Command
ADD SRT
9-16
II. Command
ADD RT
9-17
Caution: One trunk route can have a maximum of 12 sub-routes. 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.
II. Command
ADD RTANA
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".
9-19
Table 9-11 List of commands related to the configuration of route analysis data Command LST RTANA ADD RTANA MOD RTANA RMV RTANA To list route analysis record To add route analysis record To modify route analysis record To remove route analysis record Description
Caution: 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 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.
II. Command
ADD N7TG
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.
9-21
Command RMV TG
II. Command
ADD/MOD N7TKC
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.
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-24
Table 9-14 Information table Item Basic information Signaling point code AA0001 Service mode Load sharing M3UA link number 0 Route context (optional) NULL Local IP 173.20.200.1 32 Network indicator National active WIFM module number 132 Local port 2905 CIC SG signaling point code 1004 IP address of the peer MGW 173.20.200.93 WCCU/WCSU module number 22 Trunk group 1 Peer MSC signaling point code AA0001 Port of peer MGW 2905 MGW Index Server/Cli ent Client Data
Termination ID (physical circuit for interworking of MGW with MSC server) 3263
032 Route number 1 Route selection code 1 Sub-route number 1 Route selection source code 0
Trunk route
Office direction 1
Prefix
Prefix
13910
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",
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;
9-26
10-1
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.
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
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 CB, and office D needs to be configured with subroute DB. 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
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) Route selection code
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.
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".
10-3
CIC is used when the local office is interconnected with PSTN/TMSC/GMSC, and it should be negotiated with the peer office. The allocated trunk CICs in one E1 should be consecutive and in ascending order.
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: The office direction name is the same as the office name. It can be the name of a city where the office is resident. 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. 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. 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-4
MSOFTX 3000 TDM bearer Semi-permanent connection MGW TDM bearer PSTN
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.
ADD N7LKS
] [LinkSet Index] [Adjacent Point Index]
ADD N7RT
[LinkSet Index [DSP index] [Priority]
ADD N7LNK
[Link No.] [Start Circuit No.] [LinkSet Index] SLC [Signaling Link Code]
10-5
MSOFTX3000 parameters
ADD OFC [Network ID] [Office directioin] [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
Figure 10-5 Parameter relationship (route and trunk) between MSOFTX3000 and PSTN
10-6
10-7
Table 10-2 Data for interworking with PSTN Item Data Network indicator of signaling point
Basic information
/ WCSU module number Signaling link code (SLC) and SLC sending Intra-module circuit number (E1/timeslot)
Signaling link
Link set
Link number
Link type
/ Termination ID (number of the physical circuit through which MGW reaches PSTN) WCCU/W CSU module number
Circuit
CIC
/ Trunk route / Route selection code Route selection source code Office direction Route number Subroute number Trunk group Circuit type
Prefix
Prefix
10-8
II. Command
ADD OFC
10-9
II. Command
ADD SRT
subroute) randomly. In addition, you need to set it according to the customer's requirement.
II. Command
ADD RT
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 1subroute 12. [Percentage of Subroute1][Percentage of Subroute12] The value range is 1100. 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.
10-12
II. Command
ADD RTANA
10-13
Table 10-6 List of commands related to the configuration of route analysis data Command LST RTANA ADD RTANA MOD RTANA RMV RTANA To list route analysis record To add route analysis record To modify route analysis record To remove route analysis record Description
II. Command
ADD N7TG
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: 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. 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. 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. FIFO: For all the circuits of the trunk group, the system selects a circuit according to the first in, first out principle. 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. RNDM: The system selects a trunk circuit randomly. This mode is seldom used. 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. If the value is INCOMING CLIR, it indicates that the calling line identification presentation is restricted in the incoming call signaling. 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. 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. 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: When the self-loop test is not enabled, you must set this parameter to No change; otherwise, the trunk interconnection will fail. 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. 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: 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). 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.
10-21
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.
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.
10-24
SCP
SMC
HLR
GMLC
MAP/TDM MAP/TDM
MAP/TDM MAP/TDM
MSC Server
ISUP/TDM
MSOFTX 3000
BSSAP+/TDM
SGSN
H.248,RANAP /IP
MGW
IP/TDM
MGW (SG)
ISUP/TDM
PSTN
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 Basic information / Signaling link / / Circuit / Trunk circuit / Signaling point code BB0002 Data NI of the signaling point National network Intra-module link No. 2 SLC and SLC sending 1 CIC 3263 Route numb er 2 Route selecti on code 2 Subroute number 2 Route selection source code 0 Trunk group 2 Intra-module circuit number (E1 /timeslot ) 80 (2/16) WCCU/WCS U module No. 25 Circuit type ISUP
Link set
Link type
Termination ID (number of the physical circuit through which MGW reaches PSTN) 6495 Office direction 2
Prefix
Prefix
666
10-26
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
11-1
MSOFTX3000
ADD N7LKS
[LinkSet Index] [Adjacent DSP Index]
ADD N7RT
[LinkSet Index] [DSP index] [Priority]
ADD SCCPDSP
[NI] [DPC] [OPC] SLC
ADD N7LNK
[Link No.] No] [Start Circuit No ] No.] [ [LinkSet ] Index [Signaling Link Code]
ADD SCCPSSN
[NI] [SSN] [SPC] [OPC]
ADD SCCPGT
[NI ] SMC NUMBER [GT Address Information] [SPC]
11-2
Signaling link
Link set
Link type
11-3
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
11-5
SCP
SMC
HLR
GMLC
MAP/TDM MAP/TDM
MAP/TDM MAP/TDM
MSC Server
ISUP/TDM
MSOFTX 3000
BSSAP+/TDM
SGSN
H.248,RANAP /IP
MGW
IP/TDM
MGW (SG)
ISUP/TDM
PSTN
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 Basic information Signaling point code Signaling point network indicator National network Intra-modul e link number 3 Data E.164 code
D02303
Signaling link
Link set
Link type
13
64 kbit/s
SSNNAME="SMC-MSC";
ADD
SCCPGT:
GTX=13,
GTNAME="SMC
GT",
NI=NAT,
GTI=GT4,
NUMPLAN=ISDN,
11-7
12-1
SAU
SCP
SLC
ADD SCCPSSN
[Link No.] [Start Circuit No.] [LinkSet Index] [Signaling Link Code]
ADD SCPINFO
ADD SSPCAPA
[Service Key]
Procedure 1. Configure MTP 1) Add MTP DSP 2) Add MTP link set 3) Add MTP route 4) Add MTP link 2. Configure SCCP 1) Add SCCP DSP 2) Add SCCP subsystems 3) Add SCCP GT 3. Configure SCP basic information 1) Add SSP capability 2) Add SCP addressing information 3) Add SCP parameter information ADD SSPCAPA ADD SCPINFO ADD SCPPARA ADD SCCPDPC ADD SCCPSSN ADD SCCPGT ADD N7DSP ADD N7LKS ADD N7RT ADD N7LNK
Command
Signaling link
Link set
Link type
12-3
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.
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.
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.
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.
12-7
SCP
SMC
HLR
GMLC
MAP/TDM MAP/TDM
MAP/TDM MAP/TDM
MSC Server
ISUP/TDM
MSOFTX 3000
BSSAP+/TDM
SGSN
H.248,RANAP /IP
MGW
IP/TDM
MGW (SG)
ISUP/TDM
PSTN
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 Basic information / WCSU/WC CU/WSGU module number 23 Signaling point code D02302 Signaling point network indicator National network Intra-module link number 2 Data E.164 code
Signaling link
Link set
12
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
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
SLC
SGSN number
[SGSN NUMBER]
13-2
13-3
II. Command
ADD SGSNNO
II. Command
MOD MSFP
II. Command
MOD MAPACCFG
13-6
SCP
SMC
HLR
GMLC
MAP/TDM MAP/TDM
MAP/TDM MAP/TDM
MSC Server
ISUP/TDM
MSOFTX 3000
BSSAP+/TDM
SGSN
H.248,RANAP /IP
MGW
IP/TDM
MGW (SG)
ISUP/TDM
PSTN
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 Basic information / Signaling link / WSGU module number 23 Signaling point code D02304 NI signaling point National network Intra-module link number 16 of Data E.164 number 86136000 14 SLC and SLC sending 0 Circuit number (E1/timeslot) 144 (4/16) Link type 64 kbit/s
Link set 14
ADD
SCCPSSN:
SSNX=20,
NI=NAT,
SSN=GS,
SPC="CC0004",
OPC="CC0004",
SSNNAME="SGSN-GS";
ADD
SCCPGT:
GTX=14,
GTNAME="SGSN
GT",
NI=NAT,
GTI=GT4,
NUMPLAN=ISDN,
13-8
14-1
14-2
ADD N7LKS
[Link Set] [Adjacent Point Index]
ADD N7RT
[Link Set] [DSP index] [Priority]
ADD SCCPDSP
[Network Indicator] [DPC] [OPC] Signaling link code (SLC)
ADD N7LNK
[Link No] [Start Circuit No ] [Link Set] [Signaling Link Code ]
ADD SCCPSSN
[Network Indicator] [SSN Code] [Signaling Point Code] [OPC]
ADD SCCPGT
[Network Indicator] [Global Title Address Information] [Signaling Point Code]
ADD CLTGMLC
[GMLC CLIENT ID] [GMLC No.]
ADD GMLC
Local GMLC number [GMLC No.]
ADD ECLLCSCLT
[GCI OR LAI] [LCS CLIENT ID] [Emergency Call Number]
ADD ESRVCAT
[EMR_SRVCI] [SCDN]
14-3
Procedure 2. Configure SCCP 1) Add SCCP DSP 2) Add SCCP subsystem 3) Add SCCP GT to GMLC 3. Configure LCS data 1) Add GMLC number 2) Add client GMLC information 3) Add emergency call LCS Client 4) Add called analysis data (optional) ADD GMLC
14-4
II. Command
ADD GMLC
14-5
II. Command
ADD GMLCCLT
14-6
Table 14-4 List of commands related to the configuration of client GMLC information Command ADD GMLCCLT MOD GMLCCLT RMV GMLCCLT LST GMLCCLT Description To add client GMLC information To modify client GMLC information To remove client GMLC information To list client GMLC information
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.
14-7
II. Command
ADD CNACLD
14-8
SCP
SMC
HLR
GMLC
MAP/TDM MAP/TDM
MAP/TDM
MAP/TDM
MSC Server
ISUP/TDM
MSOFTX 3000
BSSAP+/TDM
SGSN
H.248,RANAP /IP
MGW
IP/TDM
MGW (SG)
ISUP/TDM
PSTN
RANAP/AAL2/ATM
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 Basic information / Signaling link Signaling point code D02305 WSGU module No. 23 SLC and sending 0 SLC Data NI of signaling point National Link set 15 Intra-module E1 timeslot No. 176 (5/16) E.164 number 8613600015 Intra-module link No. 17 Link type 64 kbit/s
ADD
SCCPSSN:
SSNX=23,
NI=NAT,
SSN=SCMG,
SPC="D02305",
OPC="CC0004",
SSNNAME="GMLC-GMLC";
ADD
SCCPGT:
GTX=15,
GTNAME="GMLC
GT",
NI=NAT,
GTI=GT4,
NUMPLAN=ISDN,
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
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: Query the corresponding record by specific field (such as prefix and call source code) first. If no matched record is found, replace fields that have wildcards with wildcards in sequence. 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 65534 2 Call prefix 1390 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-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-4
Note: Outgoing number processing will be used for outgoing trunk. 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-5
15-6
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-7
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-8
End
Figure 15-5 Procedures of number analysis and routing data configuration The role of each part of data configuration is as follows: 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. Enhanced route processing data is used to select different outgoing route for the same call prefix, with different call types or different number length. 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. 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 subscribers special service attributes respectively to a series of keywords, which form a keywordcalling 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. DN processing helps to conduct failure processing over the call in which the related call prefix is dialed, announcement playing or to reanalyze numbers. Failure processing data configuration helps to define the processing modes when both call authority check and DN processing are failed.
15-10
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
End
15-12
II. Command
ADD CALLSRC
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.
II. Command
ADD DNC
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 No Conversion Insert number at designated position Insert after number end the Designated Chars Conversion Start Position Number Conversion Length New Number Other Conversion Number Source New Number Address Nature
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
Number Conversion Type 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 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)
Designated Chars
New Number
15-17
Number Conversion Type Change number in inverted sequence according to designated character (Designated character excluded) 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)
Designated Chars
New Number
15-18
Number Conversion Type 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 included) Extract but not delete number in positive sequence according to designated character (Designated character excluded) Extract but not delete number in inverted sequence according to designated position 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
New Number
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: Extract substring from a number; add substring extracted from other number to the suffix of calling/called number. 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. 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. Support the insertion, deletion (by inverted/positive sequence), modification (by inverted/positive sequence) and extraction (in inverted/positive sequence) according to the designated position. Extract substring from calling/called number according to trunk group type (TUP/ISUP), called number type, original called number type and calling subscriber type. 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.
15-21
Table 15-4 List of commands related to number conversion Command LST DNC ADD DNC MOD DNC RMV DNC To list number conversion To add number conversion To modify attributes of number conversion To remove number conversion Description
II. Command
ADD INCLRIDX
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: 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. 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
Description To list incoming calling number correlation To add incoming calling number correlation To modify incoming calling number correlation To remove incoming calling number correlation
II. Command
ADD INORICLDIDX
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.
15-25
Table 15-6 List of commands related to incoming original called number correlation Command LST INORICLDIDX
ADD INORICLDIDX MOD INORICLDIDX RMV INORICLDIDX
Description To list incoming original called number correlation To add incoming original called number correlation To modify incoming original called number correlation To remove incoming original called number correlation
II. Command
ADD INNUMPREPRO
15-26
It is used to define different call sources so as to provide flexible incoming processings capabilities [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. for calls from the following sources: trunks (including TUP/ISUP/R2/PRA/BICC), mobile subscribers, MAP, SCP, and Call Forwarding (CF).
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: 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. 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.
15-28
Table 15-7 List of commands related to incoming number pretreatment Command LST INNUMPREPRO ADD INNUMPREPRO MOD INNUMPREPRO RMV INNUMPREPRO Description To list incoming number pretreatment To add incoming number pretreatment To modify incoming number pretreatment To remove incoming number pretreatment
II. Command
ADD CNACLD MOD CNACLD
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.
II. Command
ADD SUPERRT
15-32
Description To list enhanced route To add enhanced route To modify enhanced route To remove enhanced route
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
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.
Description To list call authority original called correlation To add call authority original called correlation To modify call authority original called correlation To remove call authority original called correlation
II. Command
ADD CALLPRICHK
15-35
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: 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. 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. 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.
Description To list call authority check To add call authority check To modify call authority check To remove call authority check
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
15-38
Meaning 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.) Calls of corresponding services will be rejected. 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.
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.
Description To list service check To add service check To modify service check To remove service check
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
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: Calling Number Analysis table is valid only when [Calling Number Analysis Flag] of the call is YES. 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]. The number of records in Calling Number Analysis table cannot be greater than the set for this table in the maximum tuple number table.
Description To list calling number analysis To add calling number analysis To modify calling number analysis To remove calling number analysis
II. Command
ADD CLICRTPRO
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.
Description To list calling feature processing To add calling feature processing To modify calling feature processing To remove calling feature processing
II. Command
ADD CLICRTANA
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.
Description To list calling number analysis To add calling number analysis To modify calling number analysis To remove calling number analysis
II. Command
ADD PFXPRO
15-45
[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.
Description To list DN special process To add DN special process To modify DN special process To remove DN special process
II. Command
ADD CFPRO
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.
Description To list failure processing To add failure processing To modify failure processing To remove failure processing
15-48
II. Command
ADD OUTCLRIDX
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.
15-50
Command
MOD OUTCLRIDX RMV OUTCLRIDX
Description To modify outgoing calling number correlation To remove outgoing calling number correlation
II. Command
ADD OUTORICLDIDX
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.
Description To list outgoing original called number correlation To add outgoing original called number correlation To modify outgoing original called number correlation To remove outgoing original called number correlation
15-52
II. Command
ADD OUTNUMPREPRO
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
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. 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 LST OUTNUMPREPRO ADD OUTNUMPREPRO
MOD OUTNUMPREPRO RMV OUTNUMPREPRO
Description To list outgoing number preprocessing To add outgoing number preprocessing To modify outgoing number preprocessing To remove outgoing number preprocessing
II. Command
ADD TGLD
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.
Description To list trunk group bearer To add trunk group bearer To modify trunk group bearer To remove trunk group bearer
II. Command
ADD TGLDIDX
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.
Description To list trunk group bearer index To add trunk group bearer index To modify trunk group bearer index To remove trunk group bearer index
15-57
II. Command
ADD CLCRPRO
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.
Description To list CLIP called correlation To add CLIP called correlation To modify CLIP called correlation To remove CLIP called correlation
15-58
II. Command
ADD CLIPRO
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.
II. Command
ADD AIDNUMPRO
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.
Description To list auxiliary number processing data configuration To add auxiliary number processing data configuration To modify auxiliary number processing data configuration To remove auxiliary number processing data configuration
II. Command
ADD MAPIFNP
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
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. 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 LST MAPIFNP ADD MAPIFNP
MOD MAPIFNP RMV MAPIFNP
Description To list MAP interface number processing To add MAP interface number processing To modify MAP interface number processing To remove MAP interface number processing
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
Description To list bill information processing To add bill information processing To modify bill information processing To remove bill information processing
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
Note: Bill control information must be configured for all non-home network office directions.
Description To list bill control data configuration To add bill control data configuration To modify bill control data configuration To remove bill control data configuration
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.
International toll
GMSC
PSTN
National toll prefix 1 2 3 4 5 6 7 8 9 Local MSISDN number segment National Roaming MSIDSN number segment
National Toll
GMSC
PSTN
0 0 0 0 0 0 0 0 0
Local Local Local Local Local Local Local Local Local PLMN Local MSCs
3 3 3 3 3 3 3 3 3
65535
11
MSISDN
65535
11
MSISDN
15-65
DN Set
Call Prefix Local office MSRN prefix MSRN prefix of VMSC connecting with local office directly National MSRN prefix Police emergency call/ambulan ce call/fire emergency call number Other special service number
VMSC
11
MSRN/HO N
TMSC
11
MSRN/HO N
Local
GMSC
PSTN
Local
PSTN
Local Toll
PSTN
13
MSRN/HO N
Note: Table 15-30 contains only the basic call prefix data, excluding those data of call configured for special processing and particular requirements of offices. GMSC, TMSC, etc. listed in [Route Selection Code] respectively stand for the route selection codes corresponding to specific office directions. National roaming MSIDSN number segment refers to the national universal roaming number segment used by operators.
15-66
Table 15-31 GMSC call prefix data configuration DN Set Call Prefix Service Attribute Route Selection Code PSTN gateway exchange (TMSC for remote access and PSTN for local access, mostly TMSC) PSTN gateway exchange (TMSC for remote access and PSTN for local access, mostly TMSC) PSTN gateway exchange PSTN gateway exchange PSTN gateway exchange PSTN gateway exchange PSTN gateway exchange PSTN gateway exchange PSTN gateway exchange Minimum Number Length Number Type Description of other parameters
International toll
PSTN
Set [Query Toll Area Code table] to "Yes" and [Gain] to "Toll Gain". Set international toll prefix based on actual conditions.
National prefix
toll
National Toll
PSTN
Set [Query Toll Area Code table] to "Yes" and [Gain] to "Toll Gain". Set national toll prefix based on actual conditions
Local
PSTN
Local
PSTN
Local
PSTN
Local
PSTN
Local
PSTN
Local
PSTN
Local
PSTN
15-67
DN Set
Call Prefix
Service Attribute
Route Selection Code PSTN gateway exchange PSTN gateway exchange PSTN gateway exchange PSTN gateway exchange PSTN gateway exchange PSTN gateway exchange PSTN gateway exchange PSTN gateway exchange PSTN gateway exchange PSTN gateway exchange PSTN gateway exchange PSTN gateway exchange 65535
Number Type
Local
PSTN
Local
PSTN Set [Emergency Call Observation] to "Yes", and [Charging] to "No Charging".
Local
PSTN
National toll prefix + Local area code + 1 National toll prefix + Local area code + 2 National toll prefix + Local area code + 3 National toll prefix + Local area code + 4 National toll prefix + local area code + 5 National toll prefix + local area code + 6 National toll prefix + local area code + 7 National toll prefix + local area code + 8 National toll prefix + Local area code + 9 Local MSISDN number segment
Local
PSTN
Local
PSTN
Local
PSTN
Local
PSTN
Local
PSTN
Local
PSTN
Local
PSTN
Local
PSTN
Local
PSTN
11
MSISDN
15-68
DN Set
Call Prefix National roaming MSIDSN number segment MSRN prefix (MSC No.) of VMSC connecting local office directly National roaming prefix National toll prefix + local area code + police emergency call/ambulanc e call/fire emergency call nmber
Service Attribute
Number Type
65535
11
MSISDN
VMSC
11
MSRN/HO N
TMSC
11
MSRN/HO N
Local
National toll prefix length + local area code length + fire alarm number length Special service number length + National toll prefix length + Local area code length IP call prefix length
PSTN
Local
PSTN
Local Toll
PSTN
13
MSRN/HO N
15-69
Note: 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. In Table 15-31, GMSC, TMSC, etc. given in [Route Selection Code] respectively stand for the route selection codes corresponding to specific office directions. 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. National roaming MSIDSN number segment refers to the national universal roaming number segment.
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). Select different routes for call prefixes in terms of various call types. Select different routes in terms of various call prefix length.
Normalize forwarded-to numbers, connected numbers and redirecting numbers accordingly during auxiliary number analysis data configuration.
Configure corresponding route selection codes in terms of various call types (basic all and forwarded call) during the enhanced route processing data configuration. Configure corresponding route selection codes in terms of various call prefix length during enhanced route processing data configuration.
15-70
Call processing requirements Intercept calls in which the format of the numbers dialed are incorrect. Allow subscribers, who have been prohibited from originating calls, to make special service calls, for example, emergency call. Realize number-receive delay at the local office for incoming numbers from other offices. Realize number-receive delay based on certain call prefix. Select routes right after converting called numbers. Convert call prefixes and then reselect routes through converted prefixes. Normalize calling numbers (calling numbers being presented, outgoing calling numbers and calling numbers in bills are all determined by normalized numbers).
Data configuration Set corresponding interception data according to the called party and corresponding failure processing data during call authority check data configuration. 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.
Set number-receive delay interval in Call Source table. Set number-receive delay interval in incoming number pretreatment data configuration. Configure corresponding conversion data for called numbers in DN processing data configuration. Convert corresponding called numbers and set [Reanalyze] to "True" during DN processing data configuration. Normalize calling numbers accordingly during calling number analysis data configuration. 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. If it is required to normalize calling numbers being displayed according to called prefixes, configure CLIP called number correlation processing data first.
called
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 ADD CALLPRICHK: CALLPRICHK: CSC=7, CSC=7, CALLTY=COMMON, CALLTY=COMMON, PFX=K'139111, PFX=K'139222, CPFX=K'eeeeeeee, CLITP=ALL, CLIRP=ALL, PROCTY=PASSON; 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 ADD CALLPRICHK: CALLPRICHK: CSC=7, CSC=7, CALLTY=COMMON, CALLTY=COMMON, PFX=K'138111, PFX=K'138222, CPFX=K'eeeeeeee, CLITP=ALL, CLIRP=ALL, PROCTY=PASSON; 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 ADD CALLPRICHK: CALLPRICHK: CSC=7, CSC=7, CALLTY=COMMON, CALLTY=COMMON, PFX=K'13800138000, PFX=K'13800138007, CPFX=K'eeeeeeee, CLITP=ALL, CLIRP=ALL, PROCTY=PASSON; 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 ADD ADD ADD OUTNUMPREPRO: OUTNUMPREPRO: OUTNUMPREPRO: OUTNUMPREPRO: CSC=65534, CSC=65534, CSC=65534, CSC=65534, TG=11, TG=10, TG=12, TG=13, P=254, P=254, P=254, P=254, PFX=K'13000111, PFX=K'13000111, PFX=K'13000111, PFX=K'13000111, CLDADDR=ALL, DDX=4; CLDADDR=ALL, DDX=4; CLDADDR=ALL, DDX=4; 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
16-1
Roaming area restriction based one zone code 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 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.
{LMU Type A}
CBC Note 1)
Uu
Iu BC
HLR
Iub
Lg GMLC
Le
Lg
Lc
Iub RNC
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
MSOFTX 3000
Lg
GMLC
Le
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: HLR identification number: H0H1H2H3 Mobile subscriber number: ABCD, allocated by respective HLR. The general format for MSISDN is CC-NDC-H0H1H2H3-ABCD.
16-3
LAC
16-4
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.
II. Command
ADD IMSIGT
16-5
II. Command
ADD SCCPGT
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: 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. 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. 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.
II. Command
ADD SCCPSSN
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.
16-8
ADD LOCGRP [Location No.] [Location Group No.] ... ADD LAIGCI [Global Cell ID] [Location No.] [Perform Roaming Analysis] [LA Category] ... MOD MAPACCFG [Use Enhanced Roaming Restrict] ...
ADD ROAMRESTGRP [Restricted By] [Start User Number] [End User Number] [User Group No.] [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: 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. 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.
II. Command
MOD MAPACCFG
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.
II. Command
ADD LOCGRP
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.
II. Command
ADD/MOD LAIGCI
Note: This command is used to configure location area, and the "LA Category" must be set to LAI.
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..
II. Command
ADD ROAMRESTGRP
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.
II. Command
ADD ROAMUSRT
16-13
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.
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
ZC=1120
LAI1=460-00-270 LAI1
LAI2=460-00-271
LAI3=460-00-280
Figure 16-6 Zone Code definition in MSC The above relationship is illustrated in Figure 16-7.
ZC=1110 ZC=1120 LAI1 LAI3 LAI2
16-15
According to the restriction principles of zone code restriction services, if User A has subscribed ZC=1110 service, User A can access the network and enjoy provided services when User A is in LAI1 or LAI2 currently. User A can neither access the network nor enjoy provided services when User A is in LAI3 currently.
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
II. Command
MOD MAPACCFG
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.
II. Command
ADD ZC
II. Command
ADD LOCGRP
16-18
II. Command
ADD/MOD LAIGCI
Note: This command is used to configure location area, and the "LA Category" must be set to LAI.
Description
ENDNUM=K'8613911901100, USRGRP=11;
ZC=1110
ZC=1120
LAI1=460-00-270
LAI2=460-00-271
LAI3=460-00-280
16-20
2)
Configure ZC.
3)
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-21
16-22
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.
17-2
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. N-CSI DP4 The table query flow triggered by N-CSI DP4 is shown in Figure 17-2.
17-3
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. N-CSI DP12 The table query flow triggered by N-CSI DP12 is shown in Figure 17-3.
17-4
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-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.
Access code index TDP access code table Access code index and database field length SCP configuration table Office TDP configuration Service key
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.
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.
The specific data configuration steps may vary with different triggering modes.
4)
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.
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: By the "home SCP" mode, the specific SCP will be indexed according to "SCP Parameter Index". 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-8
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) 3) Add call prefix (ADD CNACLD) Add number initial special processing (ADD PFXPRO). Number conversion is performed, and the parameter [Processing Type] shall be specified as "number re-analysis".
17-9
For the MSC with SSF, the data configuration steps are as follows: 1) 2) Add number conversion (ADD DNC). Remove the area prefix from the number of the overlay incoming call. 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-10
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;
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-11
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;
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: Debugging of SCTP Debugging of M3UA Debugging of Mc (H.248)
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-1
Chapter 18 Debugging
5) 6)
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. 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
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. 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. Solution Modify the checksum algorithm at local end with MOD SCTPPARA. Be sure not to affect other SCTP connections. 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
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. Cause analysis The establishment of listening port fails. If the SCTP upper layer user provides the maintenance command to query Solution Modify the configured parameters. Summary and suggestions
18-2
Chapter 18 Debugging
This problem is generally caused by inconsistency of checksum algorithm between local and peer ends.
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.
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
Fault description
18-3
Chapter 18 Debugging
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. 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
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
Chapter 18 Debugging
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. 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
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.
18-5
Chapter 18 Debugging
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. 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
--- END
18-6
Chapter 18 Debugging
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
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
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
Chapter 18 Debugging
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
Chapter 18 Debugging
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: Check if the MGW can be pinged. Check if the physical connection is normal. 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. If MSOFTX3000 and MGW are not directly connected, use the command LST FECFG to check if the gateway IP address is correctly configured. 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. 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. 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. 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. If it is an SCTP issue, refer to section 18.2 Debugging of SCTP.
18-9
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. 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
HLR
GMLC
MAP/TDM MAP/TDM
MAP/TDM MAP/TDM
MSC Server
ISUP/TDM
MSOFTX 3000
BSSAP+ /TDM
SGSN
H.248,RANAP /IP
MGW
IP/TDM
MGW (SG)
ISUP/TDM
PSTN
RANAP/AAL2 /ATM
BSSAP/TDM
RNC
BSC
A-2
Backplane
Front
5 6
9 10 11 12 13 14 15 16 17 18 19 20
A-3
Frame type WCDB WCDB WEPI WEPI WEPI WEPI WCKI WCKI
Frame No. 0 0 0 0 0 0 0 0 14 15 0 1 2 3 13 15
Location
IP address of FE interface 173.20.200.132 Balance mode of E1 interface (non-balance mode/ balance mode) Non-balance mode
IP address of the router connected with MSOFTX3000 173.20.200.253 Frame format of E1 interface (DF/CRCR) DF
Link type (64Kbit/s, 2Mbit/s) 64Kbit/s Numbers of the frame/ slot/ E1 of the WEPI board, from which the clock is extracted. 0/0/6, 0/2/0
Table A-2 Local office information table Item Signaling point / Mobile network information / / / National CC0004 Local office MSC number 8613600004 Mobile Network Code (MNC) 460 Whether check identity No National reserved C04 Local office VLR number 8613600004 Network Code (NC) 00 Country code 86 Whether perform authorization in the service access process/ position updating process No Area code 755 Whether encrypt/ encryption algorithm No Data International Internation al reserved Remark
MAP information
the
ODB_SS
ALL
A-4
Item Whether reallocate TMSI in service access process/positi on updating process No Whether support restriction on roaming zone (Zone code
Data Whether take IMEI or reserve IMEI in BILL during the service access process/position updating process No Whether support the call forwarding on HPLMN not reachable Yes MAP version/ CAMEL version MAP_PHA SE2+/ CAMEL_P HASE3
Remark
MAP information
the of
No
Yes
No
/ /
Gs
Table A-3 Table of MGW information Item Data Voice encoding/d ecoding mode ALL Local WIFM port of Link1 2945 Encryption algorithm and secret key (optional) of MGW NO Remote MGW port of Link1
Basic information
MGW Index
Checksu m mode
Server or client
Server
2945
Table A-4 RNC information table Item RNC basic information RNC ID Signaling point code Network ID Data LAI SAI AMR LIST
A-5
Item / M3UA basic signaling / M3UA link information / 4 Service mode Load sharing M3UA link number 0 Prefix (local office) 1360755 D04 Routing context (optional) NULL Local address IP National reserved WIFM module No. 132
Data 460000003 Signaling point code of SG 1004 IP address of the peer MGW 173.20.200.93 Port of peer MGW 2905 Server/c lient Client 460000003 0004 All
Local port
2905
Prefix /
Table A-5 BSC information table Item Basic information / Signaling point code C03 Configure Data NI of signaling point code National reserved LAI GCI 460 00 0001 0001 Intra-module circuit number (E1 number/ timeslot number) 112(3/16)
460 00 0001
Signaling link
Link set
SLC
Link type
22
64 kbit/s
Termination ID (the number of the physical circuit from MGW to BSC) 96~127 Office direction 3 Prefix (local office)
A-6
Item / 1390752
Table A-6 MSC information table (MTP) Item Basic information / WCSU module number 22 Signaling point code AA0001 NI signaling point National of Data MSC server number (E.164 code) 8613500001 Signaling link code (SLC) and signaling link code sending 0 WCCU/WCSU module number 25 Trunk group 1 Intra-module circuit number (E1 number/time slot number) 48 (1/16)
Signaling link
Link set
Link type
64 kbit/s
Circuit
Termination ID (the number of the physical circuit from MGW to MSC server) 32~63 Office directio n 1 Prefix 13910 Route number 1 Route selection code 1
CIC
MGW Index
Table A-7 PSTN information table Item Basic information / WCSU module number Signaling point code BB0002 NI signaling point National Signaling link code (SLC) and signaling link code sending Intra-module circuit number (E1 number/ timeslot number)Data of Data
Signaling link
Link set
Link type
A-7
Item / 22 2 2
Circuit
Termination ID (the number of the physical circuit from MGW to PSTN) 64~95 Office direction 2 Route number 2 Route selection code 2
CIC
MGW Index
/ Trunk route /
Prefix
Prefix
666
Table A-8 HLR information table Item Basic information / Signaling point code 12345 Data NI of signaling point National HLR number (E.164 code) 86139075500 00 Signaling link code (SLC) and signaling link code sending 0 DPC 12345 12345 12345 Intra-modul e circuit number (E1 number/ timeslot number) 48(1/16)
Signaling link
Link set
Link type
/ SCCP GT translation / / /
64 kbit/s
A-8
Table A-9 SCP information table Item Basic information / WCSU module number/ WCCU/W SGU 23 Signaling point code D02302 NI signaling point National of Data E.164 code 8613600012 Signaling link code (SLC) and signaling link code sending 0 Intra-module circuit number (E1 number/ timeslot number)Data 80(2/16)
Signaling link
Link set
Link type
12
64 kbit/s
Table A-10 SMC information table Item Basic information / Signaling point code D02303 NI signaling point National of Data E.164 code 8613600013 Signaling link code (SLC) and signaling link code sending 0 Intra-module circuit number (E1 number/ timeslot number)Data 112(3/16)
Signaling link
Link set
Link type
23
13
64 kbit/s
Table A-11 SGSN information table Item Basic information / Signaling point code D02304 NI of signaling point National Data E.164 code 8613600014 Signaling link code (SLC) and signaling link code sending 0 Intra-module circuit number (E1 number/ timeslot number)Data 144 (4/16)
Signaling link
Link set
Link type
23
14
16
64 kbit/s
A-9
Table A-12 GMLC information table Item Basic informati on / WCSU module number 23 Signaling point code D02305 NI of signaling point National Intra-mod ule link number 17 Data E.164 code 8613600015 Signaling link code (SLC) and signaling link code sending 0 Intra-module circuit number (E1 number/ timeslot number) Data 176 (5/16)
Signaling link
Link set
Link type
15
64 kbit/s
Table A-13 Information table of SCCP subsystem Entity MSC/VLR of local office MSC/VLR of local office Network ID National National reserved SSN configured on peer end SSN configured on local end [MSC] [VLR] [SCMG] [SCMG]
[RANAP] [BSSAP/INAP]
[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
//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 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;
A-11
DGW="173.20.200.253";
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
NI=NAT,
SSNNAME="LOCAL-NATB-SCMG";
BNCC=IP-1&AAL1-1,
DEVNAME="MGW1",
SVRCLIENT=SVR,
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;
A-13
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",
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", MLAIF DPC="D04", =FALSE ,
MSCN="8613600004", RNCID1=4,
LOCNO=65535,
SAI="4600000030004", LAICAT=SAI,
LAIGCINAME="RNC4", LAIT=HVLR,
MSCN="8613600004", RNCID1=4,
VLRN="8613600004",
LOCNO=65535,
A-14
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
SSNNAME="BSC-BSSAP";
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",
A-15
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;
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;
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";
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;
SSNNAME="MSC1-VLR";
ADD
SCCPGT:
GTX=1,
GTNAME="MSC1-GT",
NI=NAT,
GTI=GT4,
NUMPLAN=ISDN,
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;
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",
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";
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;
SSNNAME="SMC-MSC";
ADD
SCCPGT:
GTX=13,
GTNAME="SMC
GT",
NI=NAT,
GTI=GT4,
NUMPLAN=ISDN,
A-18
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;
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;
ADD
SCCPSSN:
SSNX=20,
NI=NAT,
SSN=GS,
SPC="CC0004",
OPC="CC0004",
A-19
ADD
SCCPGT:
GTX=14,
GTNAME="SGSN
GT",
NI=NAT,
GTI=GT4,
NUMPLAN=ISDN,
ADD
SCCPSSN:
SSNX=23,
NI=NAT,
SSN=SCMG,
SPC="D02305",
OPC="CC0004",
SSNNAME="GMLC-GMLC";
ADD
SCCPGT:
GTX=15,
GTNAME="GMLC
GT",
NI=NAT,
GTI=GT4,
NUMPLAN=ISDN,
A-20
ADD MHPREFIX: ID=0, HPFX=K'8613600004, SFXL=4; ADD MHSUFFIX: ID=0, PFXIDX=0, SFXS="0001", SFXE="0999", MSRNT=MSRNHON;
//index is 0 for suffix 0001~0999 ADD MHSUFFIX: ID=1, PFXIDX=0, SFXS="1000", SFXE="1999", MSRNT=MSRNHON;
//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.
A-21
Index
Index
A
associated mode of signaling, 7-7 general procedures, 7-12 networking, 7-11 parameter relationship, 7-11 configure data for interworking with MGW example, 4-14 general procedures, 4-3 networking, 4-1 parameter relationship, 4-2 relationship between MSC server and MGW, 4-1 configure data for interworking with MSC (ISUP/M3UA) example, 9-24 general procedures, 9-4 networking, 9-1 parameter relationship, 9-1 configure data for interworking with MSC (MTP) example, 8-7 general procedures, 8-3 networking, 8-1 parameter relationship, 8-2 configure data for interworking with PSTN example, 10-20 general principles, 10-8 networking, 10-4 parameter relationship, 10-5 configure data for interworking with RNC example, 5-25 general procedures, 5-3 networkinge, 5-1 parameter relationship, 5-2 configure data for interworking with SCP example, 12-8 general procedures, 12-2 networking, 12-1 parameter relationship, 12-2 configure data for interworking with SGSN example, 13-7 general procedures, 13-3 adding access media gateway, 6-26 adding A-interface circuit pool, 6-27 adding A-interface trunk circuit, 6-30 adding A-interface trunk group, 6-28 adding BSC global indicator, 6-23 adding LAI or CGI, 6-24 adding MTP destination signaling point, 6-10 adding MTP link, 6-14 adding MTP link set, 6-12 adding MTP route, 6-13 adding office direction to BSC, 6-21 adding SCCP remote signaling point, 6-18 adding SCCP subsystem, 6-20 negotiating and preparing data, 6-9
B
BSC
C
call prefix, 15-1 call source, 15-1 call source code, 15-1 circuit identification code, 10-3 configure data for interworking with BSC example, 6-32 general procedures, 6-7 networking, 6-1 parameter relationship, 6-6 configure data for interworking with GMLC example, 14-8 general procedures, 14-3 networking, 14-1 parameter relationship, 14-2 configure data for interworking with HLR example, 7-19 i-1
Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center networking, 13-1 parameter relationship, 13-2 configure data for interworking with SMC example, 11-6 general procedures, 11-3 networking, 11-1 parameter relationship, 11-2 configure equipment data example, 2-21 general procedures, 2-6 parameter relationship, 2-5 configure in service data examples, 17-10 configure incoming call number preprocessing incoming calling number correlation processing, 15-22 incoming number preprocessing, 15-26 incoming original called number correlation processing, 15-24 configure interface data, 1-3 configure mobile service data examples, 16-20 configure MTP link, 6-2 configure number analysis data examples, 15-65 configure office data example, 3-22 general procedures, 3-4 parameter relationship, 3-4 configure other number conversion data auxiliary number processing, 15-60 bill control, 15-64 bill processing information, 15-63 CLIP called correlation processing, 15-57 CLIP processing, 15-59 MAP interface number processing, 15-62 configure outgoing number preprocessing data outgoing calling number correlation processing, 15-49 outgoing number preprocessing, 15-53 outgoing original called number correlation processing, 15-51 trunk group bearer, 15-55 trunk group bearer index, 15-56 configure preset data before number analysis call source, 15-13 number conversion, 15-15 configure route selection data call authority check, 15-35
Index
call authority original called correlation processing, 15-33 call prefix, 15-29 calling feature analysis, 15-43 calling feature processing, 15-42 calling number analysis, 15-40 enhanced route processing, 15-32 failure processing, 15-47 number initial special processing, 15-45 service check, 15-38 configure service data, 1-3 configure trunk circuit and TID, 6-4 connected number, 15-4
D
data collection BSC, 6-8 equipment data, 2-4 GMLC, 14-3 HLR, 7-13 MGW, 4-3 MSC (ISUP/M3UA), 9-3 MSC Server(MTP), 8-5 office data, 3-2 PSTN, 10-8 RNC, 5-4 SCP, 12-4 SGSN, 13-3 SMC, 11-3 data preparation, 1-6 debug M3UA FAQ, 18-3 methods, 18-3 debug Mc (H.248) FAQ, 18-9
i-2
Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center methods, 18-8 debug SCTP FAQ, 18-2 methods, 18-1 destination signaling point, 7-2 dialed number set, 15-1 failure source code, 15-2 forwarded-to number, 15-4
Index
G
global configuration procedures, 1-2 Global Title. see also GT GMLC, 14-1 adding called analysis data, 14-7 adding client GMLC information, 14-5 adding emergency call LCS client, 14-6 adding GMLC number, 14-4 configuring MTP data, 14-4 configuring SCCP data, 14-4 GT, 7-7 GT addressing for communication among SPs, 7-8
E
early ACM, 15-3 enhanced roaming restriction configuration description, 16-8 LAI, 16-11 LAI grouping information, 16-10 roaming restriction user group, 16-12 roaming subscriber type, 16-13 starting enhanced roaming restriction function, 16-10 equipment data adding board, 2-9 adding CDB function, 2-11 adding FE port information of WIFM, 2-13 adding rack, 2-6 adding subrack, 2-8 example on global data configuration adding a BSC, A-18 adding a GMLC, A-23 adding a HLR, A-19 adding a MGW, A-16 adding a MSC Server, A-20 adding a PSTN, A-22 adding a RNC, A-17 adding a SCP, A-20 adding a SGSN, A-22 adding a SMC, A-21 configuring basic number analysis, A-24 configuring hardware data, A-14 configuring office data, A-15 data collection, A-3 description, A-1
H
HLR adding MTP layer data, 7-13 adding SCCP DSP, 7-14 adding SCCP GT, 7-16 adding SCCP subsystem, 7-15
I
IN service configuring basic data of local office with SSP function, 17-7 configuring data for triggering DCSI, 17-8 configuring data for triggering N-CSI DP12, 17-7 configuring data for triggering N-CSI DP2, 17-7 configuring data for triggering N-CSI DP3, 17-7 configuring data for triggering N-CSI DP4, 17-7 configuring data in overlay mode, 17-9 configuring special intelligent resource capability data, 17-10 data configuration principles, 17-6 managing special number information, 17-10 incoming number preprocessing, 15-5 incoming number preprocessing data configuration procedures, 15-7
F
failure processing, 15-2
i-3
Index adding M3UA link set, 9-9, 9-10 adding M3UA local entity, 9-6 adding office direction, 9-14 adding route, 9-17 adding route analysis data, 9-18 adding SS7 trunk circuit, 9-22 adding SS7 trunk group, 9-20 adding sub-route, 9-15 negotiating and preparing data, 9-5 MSC (MTP) adding routing information, 8-6 adding SS7 trunk circuit, 8-7 configuring MTP data, 8-6 configuring SCCP data, 8-6 MSC number, 3-1 MSC/VLR numbering principles, 16-4 MSISDN numbering principles, 16-3 MSRN/HON allocation mode adding corresponding relationship between LAI and MSRN, 3-20 adding corresponding relationship between MSC and MSRN, 3-21 adding MSRN/HON prefix, 3-18 adding MSRN/HON suffix, 3-19 MTP, 10-1 MTP load sharing, 7-5 multiple signaling points, 3-2 mutual-assistant nodes, 3-2
L
LAI numbering principles, 16-3 load sharing, 10-2 local office information, 3-1 location area, cell, service area, 16-1 location service, 16-2 location update general procedures, 16-4 setting global title table, 16-5 setting LAI or CGI/SAI, 16-5 setting local office SCCP subsystem, 16-7 setting SCCP GT, 16-6 lock clock reference source through BITS checking clock reference source, 2-21 clock reference source, 2-20 E1 information, 2-20 general procedures, 2-19 loading equipment data, 2-21 WEPI and WCKI, 2-19 lock clock reference source through E1 checking clock reference source, 2-18 clock reference from WEPI, 2-17 clock reference source, 2-15 E1 information, 2-16 general procedures, 2-14 WEPI and WCKI, 2-14
M
MGW adding MGW, 4-4 adding SCTP link to MGW, 4-8 setting SCTP checksum algorithm, 4-11 setting tone playing capability of MGW, 4-12 MML classification of commands, 1-5 using data script, 1-4 using MML command, 1-4 modes for triggering in services, 17-1 module number, 2-4 MSC (ISUP/M3UA) adding M3UA destination entity, 9-7 adding M3UA link, 9-11
N
number analysis, 15-6 number analysis and routing data configuration procedures, 15-8 number analysis preset data configuration procedures, 15-6 number analysis process, 6-5 number conversion, 15-3
O
office data adding local SCCP GT, 3-15 adding local SCCP subsystem, 3-14
i-4
Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center adding local VLR information, 3-9 adding MAP information, 3-11 setting local mobile network information, 3-7 setting local office information, 3-5 office direction, 10-1 original called number, 15-4 originating signaling point, 7-1 outgoing number preprocessing, 15-6 outgoing number preprocessing data configuration procedures, 15-10 adding zone code, 16-17 configuration description, 16-16 configuring LAI, 16-19
Index
configuring the relationship between ZC and LAI, 16-18 starting zone code restriction function, 16-17 route and sub-route, 10-2 route selection code, 10-3, 15-2 route selection source code, 10-3, 15-2
S P
PSTN adding office direction, 10-10 adding route, 10-12 adding route analysis data, 10-14 adding ss7 trunk circuit, 10-16 adding ss7 trunk group, 10-15 adding sub-route, 10-11 configuring MTP data, 10-10 negotiating and preparing data, 10-9 SCCP DSP, 7-6 SCCP DSP working mode, 7-6 SCCP subsystem, 7-7 SCP adding SCP addressing information, 12-6 adding SCP parameter information, 12-7 configuring MTP data, 12-4 configuring SCCP data, 12-4 configuring SSP capability, 12-5 secondary number analysis, 15-3 service check, 15-3 set MSRN/HON allocation mode general procedures, 3-18 MSRN/HON allocation modes, 3-17 parameter relationship, 3-17 SGSN, 13-1 configuring MTP data, 13-4 configuring SCCP data, 13-4 configuring SGSN number, 13-4 modifying map parameter table, 13-5 modifying mobile soft parameter, 13-5 signaling link, 7-4 signaling link set, 7-3 signaling route, 7-3 situations requiring data configuration, 1-1 slot number, 2-2 SMC, 11-1 configuring MTP data, 11-4 configuring SCCP data, 11-4 modifying MAP parameter table, 11-4 subrack number, 2-2
Q
quasi-associated mode of signaling, 7-8
R
rack number, 2-1 RNC adding 3G service area, 5-21 adding access media gateway, 5-23 adding M3UA destination Entity, 5-7 adding M3UA link, 5-12 adding M3UA link set, 5-10 adding M3UA local entity, 5-6 adding M3UA route, 5-11 adding RNC global indicator, 5-20 adding RNC office direction, 5-19 adding SCCP remote signaling point, 5-15 adding SCCP subsystem, 5-17 negotiating and preparing data, 5-5 roaming services, 16-1 roaming zone code service
i-5
Index
T
triggering of IN service by number segment, 17-1 triggering of overlay outgoing intelligent call, 17-1 triggering of standard CAMEL 3 IN service, 17-5 trunk circuit, 10-3 trunk group, 10-3
W
wildcards, 15-2
Z
ZC. see also zone code zone code, 16-14
V
VLR number, 3-1
i.
i-6