Chapter 1 Overview of Data Configuration ................................................... 1.1 Introduction to the Manual ...................................................................... 1.2 Introduction to the Chapter .............................

........................................ 1.3 Situations Requiring Data Configuration ................................................ 1.4 Data Configuration Procedures .............................................................. 1.4.1 Global Configuration Procedures ................................................... 1.4.2 Configuring Internal Data ............................................................... 1.4.3 Configuring Interface Data ............................................................. 1.4.4 Configuring Service Data ............................................................... 1.5 Overview of MML Application ................................................................. 1.5.1 Using MML Command ................................................................... 1.5.2 Using Data Script ........................................................................... 1.6 Precautions ............................................................................................ 1.6.1 Before Data Configuration ............................................................. 1.6.2 During Data Configuration ............................................................. 1.7 Data Preparation .................................................................................... 1.7.1 Prerequisites for Data Preparation ................................................. 1.7.2 Data Preparation Operations ......................................................... 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

.................................................7..........10 Configuring Failure Processing Data ............................5 Configure Bill Processing Information ..................6....................................................... 15.............. 16..2 Configuring Outgoing Original Called Number Correlation Processing Data ..9 Configuration Examples . 16...........................................................................................1 Configuring CLIP Called Correlation Processing Data . 15...............3 Configuring Outgoing Number Preprocessing Data................3 Configuring Location Update Data ..........................................8.. 15...9.........9..7....................................3 Planning of Call Special Processing Data.............. 15.3 Configuring Call Authority Original Called Correlation Processing Data ..... 15......................6...........7...........................................6 Configuring Bill Control Data ........ 15.......9 Configuring Dialed Number Special Processing Data . 15............................5 Configuring Trunk Group Bearer Index Data ...................... 15.1 Configuring Outgoing Calling Number Correlation Processing Data .................. 15... 15...................1 Configuring Incoming Calling Number Associated Process Data ........................ 15............................. 15...................................................................2 Configuring Enhanced Route Processing Data ......8 Configuring Other Number Conversion Data ..........4 Examples of Call Special Processing Data Configuration .. 15........................ 15........8.......... 15........................ 15........... 15..8 Configuring Calling Feature Analysis Data .................................................................8.... 15................................................5............................................................................................................................................6..............................................................3 Configuring Incoming Number Pretreatment Data ...4 Configuring Call Authority Check Data ...... 15............2 Configuring Correlation Processing Data of Incoming Original Called Number .....2 Related Concepts ............ 15..6........... 15.... 15........................................... 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 ...................6 Configuring Calling Number Analysis Data ......4 Configuring Trunk Group Bearer Data . 15.....2 Planning of Call Prefix Data .6................................................6........................1 Configuring Call Prefix ..6......6....1 Introduction to the Chapter ..5 Configuring Service Check Data .7 Configuring Calling Feature Processing Data ....7 Configuring Outgoing Number Preprocessing Data ..8. Chapter 16 Configuring Mobile Service Data ......5...............................................9............... 15....... 15...5......6 Route Selection Data Configuration ................... 15.........4 Configuring MAP Interface Number Processing Data.......................6...8...... 15.......................................................................2 Configuring CLIP Processing Data ............. 15.....................1 Planning of Number Analysis Data ............7.3 Configuring Auxiliary Number Processing Data .. 16...............8.......................7....... 15..................15........9............................ 15.................................6...... 15.......................

4 Configuring LAI .......5.....2 Configuration Description .........4 Procedures for Configuring IN Service Data ................ 16..................... 16................................2 Related Concepts ............ 17.........6 Configuring Data for Triggering DCSI ........ 17..........................3....5........................4 Configuring Data for Triggering N-CSI DP4 ............... 16.................................................4 Setting SCCP GT ....................4...................................3.................................... 16.............................. 16.........1 Configuration Description ........................................................... 16.. 16.......................... 16..........................4 Adding International Roaming Data of a Newly Subscribed Country or Region .6 Configuration Examples ................................ 16....................... 16....................................2 Configuring Data for Triggering N-CSI DP2 ..............................3 Configuring LAI Grouping Information .........................................................3 Setting Global Title Table .........................4 Adding Zone Code .............................................1 Configuring Enhanced Roaming Restriction to Number Segment by LAI .....5......................................................4..........5 Setting Local Office SCCP Subsystem ........... 17.3 Triggering of IN Service by Number Segment ...... 17............3 Configuring Data for Triggering N-CSI DP12 ............................................3..... 16...................... 16.........3 Data Configuration Principles ....5............... 17.......4 Triggering of Standard CAMEL 3 IN Service .............1 Introduction to the Chapter ................4...... 16..6......6...4................5 Configuring Roaming Zone Code Service ........4..............................2...1 Configuring Basic Data of Local Office with SSP Function .........................2 Setting LAI or CGI/SAI .......4........... 16.........................4........................6....... 17.......................................4 Configuring Enhanced Roaming Restriction Data ...............1 Service Description ................................................... 17........... 16........4.......................... 17.... 16...16.........6 Configuring Roaming Subscriber Type ..................................................... 17.. 17.......... 16...............5 Configuring Data for Triggering N-CSI DP3 ........................... 16.............4..............3........................3............ 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 ...............................1 Modes for Triggering IN Services .............................................2 Starting Enhanced Roaming Restriction Function ............ 16................................................. 17... 16.4.. 17........................ 16.2.....2........ 17...............................5........5 Configuring the Relationship Between ZC and LAI ...5 Configuring Roaming Restriction User Group........1 General Configuration Procedures ............................... 16....4.................3 Configuring Location Service Data ......2 Triggering of Overlay Outgoing Intelligent Call ..2.......2 Configuring Zone Code Restriction .........4...........................................................................................6..... Chapter 17 Configuring IN Service Data .............6 Configuring LAI ............. 17..............................................3 Starting Zone Code Restriction Function ............................ 16...5..................

................................................ 17... 18...2..... 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 .4...................................................... Chapter 18 Debugging .5. 18..................2.............. 17.............5............. Appendix A An Example on Global Data Configuration ....2 Debugging Methods ..........4..................................................................................... A...................3..................................................... 17................................4 Debugging of Mc (H..................... 18.................3 FAQ ............... 17.....2.3 Overlay Outgoing ............. 18.......4...........4................................................................................................................ A...........................3 FAQ .............................17................3................... 18.1 Background Information .................2 Data Collection ...............................5............... A........... 18.........................................2..4......................................................... 17.................................9 Managing Special Number Information ......................................8 Configuring Special Intelligent Resource Capability Data.....1 IN Services Triggered by N-CSI DP3 ............................................1 Introduction to the Appendix .............1 Example Description ........................................................4...........................................................1 Background Information .....................................................................................1 Introduction to the Chapter ............... 18...............................................3 Data Configuration ................2 IN Services Triggered by N-CSI DP4 .... Index ........................................................................5 Configuration Examples ............................................... 17................ 18.............1 Background Information ... A.................................2 Configuration Example.. A............................................2 Debugging Methods ......................................248) ..............................................................2 Debugging Methods ............................ 18.............3 FAQ ................................2.2...............3....3 Debugging of M3UA ...........................................................................................................2 Debugging of SCTP .......... 18.......................... 18............. 18........ 18.....................................7 Configuring Data in Overlay Mode ...............................................

Data Configuration V100R002 .HUAWEI HUAWEI MSOFTX3000 Mobile SoftSwitch Center Operation Manual .

HUAWEI MSOFTX3000 Mobile SoftSwitch Center Operation Manual Volume Manual Version Product Version BOM Data Configuration T2-031622-20041115-C-2. China Postal Code: 518129 Website: http://www. Ltd.com . Longgang District... Please feel free to contact our local office or company headquarters. Address: Administration Building..com Email: support@huawei. R.. Ltd. Ltd. Huawei Technologies Co. P. Bantian. Huawei Technologies Co.00 V100R002 31161422 Huawei Technologies Co.huawei. Shenzhen. provides customers with comprehensive technical support and service.

Inmedia. SmartAX. Every effort has been made in the preparation of this manual to ensure accuracy of the contents. OptiX. HONET. infoX. iTELLIN. ViewPoint. C&C08 iNET. express or implied. NETENGINE. DOPRA. SYNLOCK. Tellwin. Lansway.. TELESIGHT. M900/M1800. C&C08. TopEng are trademarks of Huawei Technologies Co.Copyright © 2004 Huawei Technologies Co. Ltd. and recommendations in this manual do not constitute the warranty of any kind.. . Quidway. but all statements. information. HUAWEI OptiX. DMC. Quidview. U-SYS. VRP. OpenEye. iSite. Radium.. HUAWEI. All other trademarks mentioned in this manual are the property of their respective holders. Ltd. EAST8000. Ltd. Musa. Trademarks . ETS. InfoLink. . iMUSE. Notice The information in this manual is subject to change without notice. Netkey. Airbridge. INtess. TELLIN. All Rights Reserved No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co.

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 1 Overview of Data Configuration profiles an overall description of the configuration procedures. Chapter 3 Configuring Office Data elaborates the configuration procedures and background concepts to be grasped before configuring the office data of MSOFTX3000. . There are seventeen chapters and an appendix in the manual.About This Manual Release Notes This manual applies to HUAWEI MSOFTX3000 Mobile SoftSwitch Center V100R002 (hereinafter referred to as MSOFTX3000). Chapter 2 Configuring Equipment Data focuses on the configuration procedures and background concepts to be grasped before configuring the equipment data of MSOFTX3000. Chapter 6 Configuring Data for Interworking with BSC describes the configuration procedures. precautions and data preparation to be done before data configuration. This chapter describes the configuration of basic office information and setting of MSRN/HON allocation mode. related concepts and configuration examples for configuring data to interwork with BSC. This chapter covers locking the clock reference source through E1 and BITS. Organization The manual introduces the basic data configuration procedure of before system operation. related concepts and configuration examples for configuring data to interwork with RNC. Chapter 5 Configuring Data for Interworking with RNC focuses on the configuration procedures.

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

General conventions Convention Arial Arial Narrow Boldface Courier New Description Normal paragraphs are in Arial. Headings are in Boldface. pop up the [New User] window. Keyboard operation Format <Key> Description Press the key with the key name inside angle brackets. Cautions. For example. GUI conventions Convention <> [] / Description Button names are inside angle brackets. II. Warnings. III. menu items. [File/Create/Folder]. Window names. <Enter>. <Backspace>. Notes and Tips are in Arial Narrow. . or <A>. data table and field names are inside square brackets. For example. 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. Multi-level menus are separated by forward slashes. For example. Terminal Display is in Courier New. For example.Appendix A An Example on Global Data Configuration gives an example for the deployment of a new office site. <Tab>. click the <OK> button.

Press the keys in turn.Format <Key1+Key2> <Key1. Press the left button twice continuously and quickly. A> means the two keys should be pressed in turn. Note: Means a complementary description. <Alt. For example. Symbols Eye-catching symbols are also used in the manual to highlight the points worthy of special attention during the operation. For example. V. . Key2> Description Press the keys concurrently. IV. Press and hold the left button and drag it to a certain position. Mouse operation Action Click Double Click Drag Description Press the left button or right button quickly (left button by default). They are defined as follows: Caution Means reader be extremely careful during the operation. <Ctrl+Alt+A> means the three keys should be pressed concurrently.

..........................1 Global Configuration Procedures ..................4.................... 2-14 2............................................................... 1-4 1....3 Setting Clock Reference Source ..................... 2-16 2.......5 Overview of MML Application ................................................................................ 2-5 2........5.....4........5....4....... 1-3 1.......................................................2............................................................................................5 Adding Clock Reference from WEPI ..............4............... 2-1 2.4.......... 2-6 2..............2 Concepts Related to Equipment Data ................2 Clock Plan . 1-1 1............ 1-4 1..........................................................................................4.............6 Precautions .........................................................4...................................................................................6 Adding FE Port Information of WIFM ................................4.......... 2-13 2.........Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Table of Contents Table of Contents Chapter 1 Overview of Data Configuration....................5....4 Adding E1 Information............................................5.... 1-6 1................................................................ 1-1 1.................................1 Before Configuration .................................................................................... 1-1 1...................1 Prerequisites for Data Preparation........................7......3 Collecting Equipment Data .................5......................................................................7 Data Preparation................................4.................................................................................................................. 2-9 2.................6.......4 Configuring Service Data ............. 1-6 1...................1 Introduction to the Chapter .................................................3 Adding Frame........................................................5........ 2-15 2..........................................................................................................1 Using MML Command ......................................................................................................... 1-1 1..................................... 1-2 1.............2 Adding WEPI and WCKI ............................................................................................................................ 1-2 1................4 Configuring Equipment Data........ 2-12 2............ 1-5 1..1 Before Configuration .........................5 Adding CDB Function...........2....................................................................................................1 Introduction to the Manual .......................................3 Configuring Interface Data ............5........................ 1-5 1..... 2-5 2................1 Equipment Numbering . 1-2 1....................................3 Situations Requiring Data Configuration ....................................................2 Using Data Script ......................6........... 2-4 2....................... 1-6 Chapter 2 Configuring Equipment Data ........................................................................................................ 2-1 2.... 2-4 2...........................................................................................2 During Data Configuration. 2-14 2........................................................................................................................................................ 2-15 2.........................................................................2 Configuring Internal Data ................................. 2-8 2........................................................ 1-5 1........................................................................................... 2-1 2.........................................4.....4 Data Configuration Procedures ......................................... 1-3 1........................................ 2-17 i .........................................................Operation Manual ......................................... 2-1 2................2 Introduction to the Chapter .........4 Adding Board............................................1 Before Data Configuration..2 Data Preparation Operations ......................................................7.......................................................5 Locking Clock Reference Source through E1........................................ 1-4 1............................2 Adding Shelf ................

................ 4-1 4................................. 2-19 2................ 2-21 2................................1 Introduction to MSRN/HON Allocation .......4..5 Adding Corresponding Relationship Between MSC and MSRN............................................................................................5..........................5 Checking Clock Reference Source ..............................4........................................ 4-1 4...........................................................................6................4 Mutual-Assistant Nodes ..... 3-17 3......................................... 2-21 2............................................................................................................................. 2-19 2.................... 4-1 4.......................... 4-1 4.... 2-21 2.......................................... 3-1 3............................................6........6 Checking Clock Reference Source .............................................. 4-2 ii ... 3-20 3..................................................4..............................3 Adding MSRN/HON Suffix ...................................................................2 Setting Local Office Information .................................................2..........................................................................5.4............... 3-18 3.......................... 3-2 3....................... 3-19 3.................................................................................................. 3-24 Chapter 4 Configuring Data for Interworking with MGW.................................5...................7 Adding Local SCCP GT ...................... 3-1 3....................7 Configuration Example .......6.................5........................................4 Adding Corresponding Relationship Between LAI and MSRN .......................................4...........................6 Loading Equipment Data........2 Configuration Description....3 Collecting Office Data ..................................2 Concepts Related to Data Configuration for Interworking with MGW ... 3-4 3............................... 3-22 3..........1 Before Configuration .3 Multiple Signaling Points .............5 Adding MAP Information ....4 Configuring Office Data ...... 3-17 3.... 2-20 2... 3-15 3.........................................................................................................3 Setting Local Mobile Network Information ........................... 3-14 3...............................................2...................2...................Operation Manual ..............1 Introduction to the Chapter .....................................................................................................................3 Parameter Relationship................................................................ 3-1 3...................................6..1 Local Office Information ...................1 Before Configuration ................................................................................................................... 3-5 3..............................................................1 Example Description ................. 3-1 3.....................6.7................6...................................................................2.......5................................................................6.....5...............2... 3-11 3.................................................................................................... 4-1 4.........4 Adding Local VLR Information ....................6............................3 Setting Clock Reference Source ............................................. 2-24 Chapter 3 Configuring Office Data .............................................................................. 3-9 3...2.........1 Introduction to the Chapter .6 Adding Local SCCP Subsystem......... 3-22 3..........................2.....................4 Adding E1 Information............................... 3-4 3.....6 Locking Clock Reference Source through BITS .......................... 3-2 3.............................................2 Concepts Related to Office Data .........1 Relationship Between MSC Server and MGW ................................................ 3-21 3......................................................5 Setting MSRN/HON Allocation Mode ..2 Adding WEPI and WCKI .................... 2-21 2............2 Networking Between MSOFTX3000 and MGW........ 3-7 3.............. 2-18 2..........................................................................4....2 MSC Number and VLR Number.........6 Configuration Example ............2 Adding MSRN/HON Prefix ............................................. 3-2 3................................................................................................2 Configuration Description.................. 2-19 2.. 3-1 3........................7...........................Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Table of Contents 2.............................................................................1 Example Description ......... 2-20 2...4.....

..........3 Setting SCTP Checksum Algorithm (Optional) ..........6 Adding M3UA Link .....................2...................2.......2 Adding M3UA Local Entity ........2......................................................9 Adding RNC Office Direction........................................................... 5-3 5............................2.................................3 Collecting Data for Interworking with RNC ................................................5..2.............1 Adding MGW .3 Adding M3UA Destination Entity ....................................................4..........5.........................................................................................4...............................................3 Parameter Relationship.......................3 Trunk Circuit and TID Configuration .......................................4....2..................... 6-1 6.......................................................Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Table of Contents 4........12 Adding Access Media Gateway .............................................................................................................4........................................................................5 Configuration Example .................................................. 5-14 5................................................................................ 6-4 6................................................... 5-7 5......4 General Configuration Procedures........................................................................................1 Example Description ................................ 5-1 5..... 5-9 5..............................3 Collecting Data for Interworking with MGW...... 5-10 5...............................8 Adding SCCP Subsystem .......... 5-18 5........................11 Adding 3G Service Area........... 5-1 5............................................................... 4-3 4.........................................................................................4..............................4................1 Introduction to the Chapter ..........................................4............................... 4-4 4......................... 4-4 4................ 4-14 Chapter 5 Configuring Data for Interworking with RNC .............................. 5-20 5...................... 6-2 6...............................................................................................................1 Basic Concepts of M3UA ....................................2 MTP Link Configuration.......5.............................. 5-23 5..................................7 Adding SCCP Remote Signaling Point .............................................4........4..................................1 Networking Between MSOFTX3000 and BSC............................2 Configuration Description...............................2........... 4-8 4.......................4 Configuring Data for Interworking with MGW .1 Introduction to the Chapter ................................... 6-1 6......................................1 Negotiating and Preparing Data...1 Example Description .................5...................4..................2.........................................................................................................................5 Configuration Example ............................................................ 4-10 4...... 6-6 iii ........... 5-19 5................ 4-13 4.................................... 4-11 4................................................. 5-6 5......4..................4.........4 Number Analysis Process ..............Operation Manual ...........................4............................................ 5-1 5. 5-2 5.....................................4 Setting Tone Playing Capability of MGW (Optional) ...................................................................5 Adding M3UA Route ........................................4.............................. 4-3 4.......2 Adding SCTP Link to MGW...............5 Parameter Relationship......................... 6-1 6.2............................................. 5-5 5............2 Configuration Description. 5-5 5......4............................................ 5-23 5.............................4 Adding M3UA Link Set .... 6-5 6.................4 General Configuration Procedures.........4 Configuring Data for Interworking with RNC......10 Adding RNC Global Indicator ......... 5-4 5............................... 5-24 Chapter 6 Configuring Data for Interworking with BSC .........................................2 Concepts Related to Data Configuration for Interworking with RNC..................................... 5-16 5... 6-1 6...2............. 5-22 5...................................................................................................4...................... 5-1 5........ 5-11 5....2 Networking between MSOFTX3000 and RNC... 4-13 4.................................................... 5-1 5...........................................2 Concepts Related to Data Configuration for Interworking with BSC .........

............................................................................................4............1 HLR ........................... 6-13 6...........3 Adding SCCP Subsystem .............. 6-14 6......................7 General Configuration Procedures........9 Adding BSC Global Indicator .........4............................................................................ 6-30 6......4 Principles for Numbering MTP Data......4............1 Introduction to the Chapter ..........4 Adding SCCP GT ............. 7-13 7............................4.............................................. 6-8 6.....2.3 Adding MTP Link Set ............................................................................. 6-25 6....5 Networking Between MSOFTX3000 and HLR.....................................8 Adding Office Direction to BSC ......................Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Table of Contents 6....2............................................. 7-1 7.................3 Principles for Naming Signaling Links.........................13 Adding A-interface Trunk Group ........1 Example Description ................. 6-26 6..3 Collecting Data for Interworking with HLR............................4.............................12 Adding A-interface Circuit Pool ............ 6-11 6........................................... 7-10 7.....4.............................................................................3 Collecting Data for Interworking with BSC...................................5...........................................................................................................7 Adding SCCP Subsystem .......................4......................4.............................................2..................... 6-9 6...... 7-1 7... 6-31 Chapter 7 Configuring Data for Interworking with HLR .................................................................................................................................................................1 Example Description .........................................6 Adding SCCP Remote Signaling Point .......................... 8-1 8.......................................... 6-23 6......4....... 8-1 iv ......................................1 Adding MTP Layer Data.... 7-20 Chapter 8 Configuring Data for Interworking with MSC (MTP)..................................................... 6-10 6........................................... 7-11 7..........2 Principles for Configuring GT Data .................................................... 6-22 6..........................................................Operation Manual ..........4...............................................................14 Adding A-interface Trunk Circuit ....................4......................................................5 Adding MTP Link ............................................................................................................................. 6-30 6. 7-12 7.............2. 7-13 7. 6-17 6................................................2...................2 Adding SCCP DSP..4 Configuring Data for Interworking with BSC .......................................................................................... 6-7 6...........................4.......................................................2 Concepts Related to Data Configuration for Interworking with HLR .....................5 Configuration Example ............................................................................................ 6-28 6.........2..........................5 Configuration Example .....................................6 Parameter Relationship.......................... 7-9 7.........4...4...... 7-12 7...4.............4.... 7-16 7........................................................2 Concepts Related to Data Configuration for Interworking with Other MSC Server.......................2........1 Negotiating and Preparing Data.......................................................10 Adding LAI or CGI .... 6-9 6.......................4 Configuring Data for Interworking with HLR ....................................4.......................4........................................2 Adding MTP Destination Signaling Point ...................... 7-1 7.................... 7-18 7..........4 Adding MTP Route.......................................................................................1 Introduction to the Chapter ....................................... 6-26 6.................2....................................... 6-19 6....11 Adding Access Media Gateway ............5...... 7-14 7. 6-20 6.5...................................................................................................... 7-18 7.................5........................................... 8-1 8... 7-10 7................................................................... 7-1 7.................. 7-10 7............................................................6 General Configuration Procedures.............................2 Configuration Description..................................2 Configuration Description........................ 7-13 7..............

.................................................................................4....... 9-18 9.......................................................... 8-5 8... 8-4 8..........3 Collecting Data for Interworking with Other MSC Server ..........................................................................................................Operation Manual .............................................................................................................4.......................................4........ 9-24 9.......................2 Configuration Description........................5 Adding SS7 Trunk Circuit......................7 Adding Office Direction ............4......2........................................................................... 10-5 v .................................3............................................................................2.........................................2 Configuration Description.............. 9-11 9........................................................................................................3 Networking Between MSOFTX3000 and PSTN ......................................................................................................4 Configuring Data for Interworking with Other MSC Server..... 8-6 8..................................2....................................................3........ 10-1 10........................................................1 Networking Between MSOFTX3000 and MSC ...2.......................1 Description of Example ..... 9-20 9................................................1 MTP...................................4 Adding Routing Information....1...............11 Adding SS7 Trunk Group ............................................3.............................................. 9-1 9.................................Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Table of Contents 8.............3......... 9-5 9.....3.................................................................... 9-14 9................................. 8-3 8....................... 9-5 9. 8-5 8...... 9-10 9..6 Adding M3UA Link ...........................3............................................... 8-6 8...........................................................................1 Negotiating and Preparing Data.....1.......3............... 10-1 10..................................................... 10-4 10..... 10-1 10....................................2............. 8-5 8.......................... 9-6 9.2......................................................................5 Configuration Example ......................................2 Parameter Relationship......................................................................1 Introduction to the Chapter ........5 Adding M3UA Route ..........................................................................3................................................................ 9-7 9............................... 8-8 Chapter 9 Configuring Data for Interworking with MSC (ISUP/M3UA).........................1 Related Concepts .......1 Negotiating and Preparing Data...............3 Configuring SCCP Data ......2 Concepts Related to Data Configuration for Interworking with PSTN .................................................. 9-22 9.........................................................4 Adding M3UA Link Set ............. 9-17 9....................... 9-15 9................ 9-1 9........................ 8-1 8........................... 9-1 9..............................................................1 Example Description ...............10 Adding Route Analysis Data ..................................................................................................................................4 Parameter Relationship....4............2 Parameter Relationship.............3 Collecting Data ...........4.....................................4 Configuration Example .......................2 Configuring MTP Data..................................................................................9 Adding Route......................4.............................12 Adding SS7 Trunk Circuit................2 General Configuration Procedures ... 9-1 9......2............................ 9-25 Chapter 10 Configuring Data for Interworking with PSTN ..........3.................3 Adding M3UA Destination Entity ........... 10-1 10........ 9-9 9.................................................. 8-5 8....................................................................3.......................3 Procedures...................................................2 Adding M3UA Local Entity .............. 8-2 8............5..8 Adding Sub-Route............1 Networking Between MSOFTX3000 and MSC Server ........................3............................... 10-1 10......2 Route and Trunk .................................................................................................... 9-3 9...........................................5.... 8-6 8...........1.....3 General Configuration Procedures..............3....................................... 8-6 8.... 9-24 9.......................... 9-4 9............................

.................... 12-4 12..............................................................................1 SMC ...........................................................................................................2....................................................................................... 11-1 11.4...... 10-9 10.... 12-2 12..............................3 Configuring SSP Capability:configuring SSP capability...........1 Configuring MTP Data.............1 Introduction to the Chapter ...............2 Networking Between MSOFTX3000 and SCP...... 10-17 10.......................................5.................. 10-7 10................................2 Configuring SCCP Data:configuring SCCP data ......................................................................4........................................................... 11-4 11............... 11-1 11....................................... 10-12 10....................................................................5 Configuration Example ....5......................................................1 Example Description ..................4..4........5 Configuration Example .............. 10-15 10.5 Adding Route........... 10-10 10..................................... 11-4 11...............................................................3 Collecting Data for Interworking with PSTN ................................................................................................2....... 12-2 12..................................................................................................4 Configuring Data for Interworking with PSTN....................... 10-7 10...1 Introduction to the Chapter .........................6 Adding Route Analysis Data ............................2..............................3 Parameter Relationship..5 General Configuration Principles .... 12-1 12......................1 SCP .......................................2...........4 General Configuration Procedures.............4.......................................4.........................2 Networking Between MSOFTX3000 and SMC ..............................3 Adding Office Direction .............2............................7 Adding SS7 Trunk Group ......................4 Configuring Data for Interworking with SCP ................ 12-1 12............................8 Adding SS7 Trunk Circuit.......................4....................................................................................................4..... 11-7 Chapter 12 Configuring Data for Interworking with SCP ..................2 Concepts Related to Data Configuration for Interworking with SMC.5..................................................... 11-1 11.................................. 10-14 10...........................4.....................................................4 Adding Sub-Route.................................4..........................................................................2..................... 11-3 11..................... 10-11 10......................................2 Configuration Description............................3 Parameter Relationship......................4 Configuring Data for Interworking with SMC .............................2 Concepts Related to Data Configuration for Interworking with SCP ..................... 10-17 10......3 Collecting Data for Interworking with SMC ...........................................................3 Collecting Data for Interworking with SCP..................... 12-5 vi ......................................... 11-4 11........................................ 10-19 Chapter 11 Configuring Data for Interworking with SMC.........1 Example Description ....... 11-2 11..... 10-8 10.......4.. 11-6 11........................ 11-1 11.2 Configuration Description....................................5...............................1 Configuring MTP Data:configuring MTP data ...................................................................................2 Configuring SCCP Data ...2........ 10-8 10............................................ 12-4 12.2.............................4 General Configuration Procedures.................................... 12-4 12... 11-6 11................. 11-4 11......1 Negotiating and Preparing Data................................................................................... 12-1 12. 12-1 12..4..............Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Table of Contents 10... 12-1 12.......................3 Modifying MAP Parameter Table . 11-3 11..........................................................4 Adding SCP Addressing Information:adding SCP addressing information .................2...................... 10-9 10...........................................................................................................................4............ 12-3 12........................................... 12-4 12..........................2 Configuring MTP Data...................4......4........... 11-1 11..............Operation Manual .................................

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

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

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

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

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

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

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Table of Contents

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

x

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Chapter 1 Overview of Data Configuration

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

1.2 Introduction to the Chapter
This chapter contains the following sections: Situations Requiring Data Configuration Data Configuration Procedures Overview of MML Application Precautions Data Preparation

1.3 Situations Requiring Data Configuration
You need to configure data in two cases: If it is the office deployment for the first time, you need to configure global data. During equipment operation, you need to modify certain data for adding new network elements or changing links. This manual focuses on the first situation, describing globally all aspects of data configuration. In routine operation and maintenance, data configuration refers to that of a certain aspect. For instance, add a radio network controller (RNC) to the office. Please refer to Chapter 5 “Interworking with RNC”.

1-1

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Chapter 1 Overview of Data Configuration

1.4 Data Configuration Procedures
1.4.1 Global Configuration Procedures
Figure 1-1 shows global data configuration procedures. For configuration of specific data, refer to corresponding chapters listed in the figure.
Start Data preparation Internal data configuration Configuring hardware data Configuring local office information Configuring data of interface to MGW Configuring data of interface to RNC Configuring data of interface to BSC Configuring data of interface to HLR Configuring data of interface to other MSC Configuring data of interface to PSTN Configuring data of interface to SMC Configuring data of interface to SCP Configuring data of interface to SGSN Configuring data of interface to GMLC Configuring number analysis data Service data configuration Configuring mobile service data Configuring IN service data End Refer to Chapter 2 Hardware Data Configuration Refer to Chapter 3 Local Office Data Configuration Refer to Chapter 4 Interworking with MGW Refer to Chapter 5 Interworking with RNC Refer to Chapter 6 Interworking with BSC Refer to Chapter 7 Interworking with HLR Refer to Chapter 8 Interworking with MSC or Chapter 9 Interworking with SCP Refer to Chapter 10 Interworking with PSTN Refer to Chapter 11 Interworking with SMC Refer to Chapter 12 Interworking with SCP Refer to Chapter 13 Interworking with SGSN Refer to Chapter 14 Interworking with GMLC Refer to Chapter 15 Number Analysis Configuration Refer to Chapter 16 Mobile Service Data Configuration Refer to Chapter 17 IN Service Data Configuration

External interface data configuration

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

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

1-2

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Chapter 1 Overview of Data Configuration

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).

1.4.3 Configuring Interface Data
It covers interface data configuration of MSOFTX3000 interconnecting with other network elements (NEs) in PLMN. The NEs and interfaces include: To media gateway (MGW), through Mc interface To RNC, through Iu-CS interface To base station controller (BSC), through A interface To MGW, through Mc interface To other (G)MSC Server, through E interface To service control point (SCP), through CAP and L interface To short message center (SMC), through E interface To public switched telephone network (PSTN), through PSTN trunk interface To serving GPRS support node (SGSN), through Gs interface To gateway mobile location center (GMLC), through Lg interface

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

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

1-3

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Chapter 1 Overview of Data Configuration

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

1.5.2 Using Data Script
I. Situations for Using Data Script
You can configure data by loading data script in the following cases: The data configuration is conducted for the first time at the initial stage of the implementation. There are a big number of data to be configured for expansion and upgrade.

II. Compilation of Script
To compile a piece of script, do the following: 1) 2) 3) 4) 5) 6) Select [System/Save Input Commands] in the [MSOFTX3000 Operation and Maintenance Center] window. Select the name of the file. Select the directory to save the command. Enter the command in the command input window. Execute the command. After execution of the command, select [System/Stop Save Input Commands].

III. Use of Script
To use the script, proceed as follows: 1) 2) 3) 4) Directly use the data script file in TXT format. After modifying the data based on the specific situations, set the system to the offline state by executing the command LOF. Select [System/Execute Batch Commands]. Select the needed data script in TXT format in the pop-up dialogue box.
1-4

1 Before Data Configuration Before configuring data. Prepare online setting data. IV. Table 1-1 Classification of commands Command ADD MOD RMV LST DSP SET LOF LON To add data To modify data To remove data To list BAM data To display host data.Operation Manual . state of equipment. If there are only a few batch commands. complete the following: Obtain the office networking and configuration details. power on the system and load the data. a) b) Set data offline. When deploying a new site. 1. Read data information about this office carefully and contact related personnel once a defect is found. 1-5 . Classification of Commands Refer to Table 1-1 for detailed meaning of commands.2 During Data Configuration When configuring data. Finally. Understand the requirements raised during the project design phase of the office.6. note the following: For MML commands.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 1 Overview of Data Configuration 5) 6) 7) Execute the format conversion command FMT. refer to HUAWEI MSOFTX3000 Mobile Switching Center Installation Manual – System Commissioning.6. Execute the LON command.6 Precautions 1. or resource consumption To set data or state Offline Online Description 1. For the method of using script. the parameters in red are mandatory. you can execute them directly without setting the MML client offline.

implement data configuration in online state.7 Data Preparation 1. 1. press <F1>. 1. 1-6 . The system has been powered on. Determining Networking Model Draw the networking diagram of MSOFTX3000 and the related functional entities. To open online help for detailed information of commands and parameters.2 Data Preparation Operations Important Note: To ensure a quick and secure data configuration process. power on.7. 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.1 Prerequisites for Data Preparation The prerequisites of this step are: Hardware installation has been completed. I.Operation Manual . 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. Refer to Table 1-2 for details. except when executing the command MOD MAXT to modify maximum tuple number in offline state. you need to collect the following data and make corresponding planning in advance.7.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center c) Chapter 1 Overview of Data Configuration Reload data.

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Chapter 1 Overview of Data Configuration

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

III. Determining Parameters
Interface parameters Calculate or negotiate all interface parameters according to the planned network capacity. For instance, determine how many signaling system number 7 (SS7) links for HLR, how many signaling ATM adaptation layer (SAAL) links for RNC, how many links for MGW, and how many signaling points assigned for all functional entities. Internal parameters Determine subrack configuration within the designed capacity, including number of subracks and boards. The key internal parameters should also be determined, as data for compulsory subracks displayed in Table 1-3. Table 1-3 Subrack information table Subrack type Subrack number Site number Row number Column number

Board type

Subrack number

Slot number

Front/back

Module number

Slot number of assistant board

IP address of fast Ethernet (FE) port

IP address of the router that connects to MSOFTX3000

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

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

Frame format of E1 port (DF/CRC4)

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

1-7

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Chapter 1 Overview of Data Configuration

IV. Determining Interworking Parameters
Refer to the following tables for data required for MSOFTX3000 interworking with other adjacent entities r interfaces. In the shadowy columns are the parameters that require consistency between two ends, or those to be informed to the peer end. The rest are internal parameters in MSOFTX3000. Record the configured data for future troubleshooting or query. Table 1-4 Local office information table Item Signaling point / Mobile network data / / / Mobile application part (MAP) information / Reallocate temporary mobile subscriber identifier (TMSI) during service access and location update procedure? Check international mobile station equipment identity (IMEI) or contain IMEI in bill during service access and location update procedure? Authorize during service access and location update procedure? Cipher algorithm? Mobile network code (MNC) Network (NC) code Country code Area code Local number MSC Local number VLR National valid network Data National reserved network valid International network valid International reserved network valid

Identify user?

ODB_SS

/

Support visitor location register (VLR) location update?

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 zone code restriction?

Support prepage?

/

1-8

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Chapter 1 Overview of Data Configuration

Item / / Support call hold? Support interface?

Data Gs Support enhanced roaming restriction?

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

SCTP connection number 1

Local WIFM port of Link 1

Remote MGW address of Link 1

Remote MGW port 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

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Chapter 1 Overview of Data Configuration

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

Intra-module link number

Signaling link code (SLC)

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

Intra-module link number

SLC and SLC sending

Link type

/

1-10

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Chapter 1 Overview of Data Configuration

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

Data Wireless call control unit (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

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

WCSU module number

Link set

Intra-module link number

SLC and SLC sending

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

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Chapter 1 Overview of Data Configuration

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

Intra-module link number

Link type

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

Encoding description

Numbering plan

Address information

Destination point code (DPC)

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

Intra-module link number

SLC and SLC sending

Link type

/

1-12

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Chapter 1 Overview of Data Configuration

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

Intra-module link number

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

WCSU module number

Link set

Intra-module link number

SLC and SLC sending

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

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Chapter 2 Configuring Equipment Data

Chapter 2 Configuring Equipment Data
2.1 Introduction to the Chapter
The equipment data is the prerequisite of configuring other MSOFTX3000 data. It defines the hardware data and physical setting of MSOFTX3000. This chapter contains the following sections: Concepts Related to Equipment Data Collecting Equipment Data Configuring Equipment Data Locking Clock Reference Source through E1 Locking Clock Reference Source through BITS Configuration Example

2.2 Concepts Related to Equipment Data
2.2.1 Equipment Numbering

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

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

2-1

The basic frame is numbered as 0 and the other frames are numbered from 1 to 9 from bottom upward. The configuration data for MSOFTX3000 frame numbers must be consistent with the hardware settings. and column number are provided as location information.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 2 Configuring Equipment Data Note: Site number. a fault can be located quickly. Table 2-1 Corresponding relationships between DIP switch settings of the WSIU and frame numbers Switch Frame number 0 1 2 3 4 5 6 7 8 9 8 on on on on on on on on on on 7 on on on on on on on on on on 6 on on on on on on on on on on 5 on on on on on on on on on on 4 on on on on on on on on off off 3 on on on on off off off off on on 2 on on off off on on off off on on 1 on off on off on off on off on off III. Table 2-1 shows the corresponding relationships between settings of the 8-digit DIP switch S3 of the WSIU and frame numbers (off=1. numbered from 0 to 9. Slot Number All frames are universal in MSOFTX3000. You can set service processing frame numbers through the dual-in-line package (DIP) switch of the WSIU in the frame. Frame Number Each service processing frame is allocated with a frame number uniquely in the system. II. If the numbering plan for shelves is the same as the actual condition. MSOFTX3000 can support up to 10 frames. row number. Some front boards and back boards are configured in pair.Operation Manual . 2-2 . The boards are inserted in the backplane from front and back. on=0).

and the back boards are numbered from right to left. such as the WIFM. WMGC and WIFM. and WAFM. and WMGC). The WHSC must be inserted in back slots 7 and 9. WIFM. When the capacity of the system is relatively small. and front panels are installed in corresponding front slots. UPWR. The front boards are numbered from left to right.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 2 Configuring Equipment Data 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. Each UPWR occupies two slots. WSIU. The slot numbers designated are 17 and 19. WVDB. The relations between boards and slots are shown as follows: The WSMUs (and back boards WSIUs) must be inserted in slots 6 and 8. WAFM. WCDB.These slots are compatible with one another. 10–15) are inserted with service processing boards (including the WCCU. and WALU. The WALU must be inserted in front slot 16.Operation Manual . Other slots (0–5. A frame is designed to contain 21 boards numbered from 0 to 20. while the others are optional. WVDB. and there are two front UPWR boards and two back UPWR boards. 2-3 . a single WIFM can provide all features of the WBSG. WHSC. WCSU. WBSG. such as the WSMU.

refer to Chapter 4 in HUAWEI MSOFTX3000 Hardware Description Manual. but will be automatically added by the system. and the others are allocated to boards. In the shadowy columns are the parameters that require consistency between two ends. 1 is for iGWB. and UPWR are not to be configured. For cable connections.2 Clock Plan For clock plan of MSOFTX3000. and numbers them accordingly from 0 to 255. WHSC. 2-4 .Operation Manual . and the others are internal parameters of MSOFTX3000. you need to collect the equipment data of MSOFTX3000 as listed in Table 2-3.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 2 Configuring Equipment Data Important Note: Such boards as the WSMU. IV. WALU. iGWB. and boards as modules. The module number of a board is unique in the system. Module number starts from 2 according to board type. 0 is for BAM. refer to Chapter 6 “Installation of Signal Cables” in HUAWEI MSOFTX3000 Hardware Installation Manual for details. Module Number MSOFTX3000 regards BAM. The numbering rules are as follows: WSMU module number: 2–21 (allocated automatically by the system) WCCU/WCSU module number: 22–101 WCDB/WVDB module number: 102–131 WMGC/WAFM/WIFM/WBSG/WSGU module number: 132–211 2. WSIU.2.3 Collecting Equipment Data Before configuring equipment data. 2.

II. Parameter Relationship in Hardware Configuration The commands for configuring equipment data and their parameter relations are shown in Figure 2-1. It defines the hardware data and physical setting of MSOFTX3000.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 2 Configuring Equipment Data 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 Balance mode of E1 port (balance or non-balance) Frame format of E1 port (DF/CRC4) Frame/slot/E1 number of the WEPI providing clock reference 2.4.4 Configuring Equipment Data 2.Operation Manual .1 Before Configuration I. 2-5 . Significance of Equipment Data Equipment data is the prerequisite of configuring other MSOFTX3000 data.

General Configuration Procedures See Table 2-4 for the procedures and commands for adding equipment data. Table 2-4 Procedures for configuring equipment data Procedure 1: Add shelf 2: Add frame 3: Add board 4: Add CDB Function 5: Add FE port information of the WIFM 6: Load equipment data ADD SHF ADD FRM ADD BRD ADD CDBFUNC ADD FECFG / Command 2. 2-6 .2 Adding Shelf I. and these cabinets can be added one by one according to the actual configuration.4.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 2 Configuring Equipment Data 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] Figure 2-1 Parameter relationship of commands for configuring equipment data III. Background Information MSOFTX3000 can be configured with up to three cabinets.Operation Manual .

"Position Number” in ADD BRD) of the WSMU that manages the power distribution box (PDB). it refers to the location number of the frame in which the WSIU connecting to the PDB serial cable resides. you must ensure that the related module. The integrated configuration cabinet is numbered as 0. position number. [Position Number] It defines the number of the equipment in which a shelf resides. Physically. To modify the properties of a shelf MOD SHF You can use this command to modify the position (location title. Major Parameters [Shelf Number] This parameter is used to identify a shelf uniquely. and the rest two are numbered as 1 and 2 respectively from left to right.Operation Manual . row number and column number) of a shelf.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 2 Configuring Equipment Data II. Table 2-5 List of commands related to shelf configuration Command ADD SHF RMV SHF To add shelf To remove an existing shelf from the system Before removing a shelf. It is in character string. IV. or the PDB state will not be reported. It must conform to actual setting. Related Commands See Table 2-5 for the commands related to shelf configuration. [PDB Location] These two parameters are used to describe the location number (that is. Description 2-7 . [Row Number] [Column Number] It specifies the row and column in which a shelf resides. [Location Title] It describes the position of a shelf. Command ADD SHF III. board and frame have been removed.

This parameter is defined in the ADD SHF command.4. 2-8 . The position numbers in each shelf from bottom upward are 0 to 3 according to the following allocation rules: In Shelf 0 (integrated configuration cabinet). Before configuring the expansion frames. the frame information cannot be shown correctly on the maintenance console. This parameter must be consistent with the actual hardware condition.Operation Manual .3 Adding Frame I. In Shelves 1 and 2. The settings of frame numbers must be consistent with those on the DIP switch of the WSIU. Major Parameters [Frame Number] This parameter is used to identify a frame uniquely. and they range from 0 to 9. and the expansion frames are numbered from 1 to 9 from bottom upward. just set the parameter "shelf number" to "ALL". otherwise. and position numbers 2 and 3 are for service frames. configure the basic frame first. Command ADD FRM III. 2. Background Information None II. the position numbers are allocated from 0 to 3 according to the actual configuration.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 2 Configuring Equipment Data Command LST SHF Description To list the properties of the specified shelf If you expect to browse the properties of all shelves in the system. position numbers 0 and 1 are for BAM and iGWB server. [Position Number] This parameter is used to identify the position of a frame in a shelf. [Shelf Number] This parameter identifies a shelf. A frame number is unique in the system. Frame numbered as 0 is the basic frame.

In this case. WIFM. just specify the parameter "frame number" to "ALL". Major Parameters [Frame Number] 2-9 . Table 2-6 List of commands related to frame configuration Command ADD FRM RMV FRM To add a frame To remove an existing frame Before removing a frame. WMGC. when you add a frame with the ADD FRM command. and WCKI. WCSU. To modify the message transfer part (MTP) link type (64 kbit/s by default) of the central processing board (CPC) on the WCSU.4. II. you must ensure that the related module and board have been removed. WHSC. WSIU. WCDB. WBSG. To display the information of a frame Description 2. WSGU. WALU and UPWR of the frame will be configured automatically. You need to manually configure such boards as the WCCU.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 2 Configuring Equipment Data IV.4 Adding Board I. Background Information By default. Command ADD BRD III. WVDB. To list the properties of the specified frame LST FRM DSP FRM If you expect to browse the properties of all frames in a shelf.Operation Manual . Related Commands See Table 2-6 for the commands related to frame configuration. use the command MOD CPCCFG. WEPI. the WSMU. WCCU. it is only required to use the LST BRD command to verify the slot numbers of these boards. To modify the properties of a frame MOD FRM You can use this command to modify the position information (shelf number and position number) of a frame.

this parameter enhances system security by indicating the slot number of the assistant board. If you enter “255”. After you specify the assistant board with this parameter. When the added board works in active-standby mode. Important Note: The slot pairs of 0 and 1. To set the assistant board to be inserted in the non-default adjacent slot. It is only valid to boards working in active-standby mode. you don’t have to add the board using the command ADD BRD. 14 and 15 are adjacent slots by default. It is recommended to use the default setting. WCSU. 4 and 5. 2-10 . and it will be used in later configuration. WVDB. it means that no assistant board is needed. Note: The range of module numbers is: WSMU: 2–21 (automatically assigned by the system) WCCU/WCSU: 22–101 WCDB/WVDB: 102–131 WMGC/WAFM/WIFM/WBSG: 132–211 [Assist slot number] It indicates the slot number of the assistant board. The WCCU. just enter the slot number of the assistant board. 2 and 3. WCDB.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 2 Configuring Equipment Data This parameter refers to the number of a frame where a board resides. [Board Type] This parameter is used to specify the type of a board to be added. 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. 10 and 11. 12 and 13.Operation Manual . and WIFM are all working in active-standby mode. [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.

IV. Related Commands See Table 2-7 for the commands related to board configuration. this parameter specifies the type of CPC sub-board—one processing 64 kbit/s MTP links.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 2 Configuring Equipment Data [Link type] When the added board is WCSU. 2-11 . and the other processing 2Mbit/s MTP links. you must specify whether the board to be removed is a front board or a back board. Table 2-7 List of commands related to board configuration Command ADD BRD RMV BRD LST BRD DSP BRD DSP BRDVER SWP BRD RST BRD MOD LSS LST LSS DSP COMM MOD CPCCFG LST CPCCFG To add a board To remove an existing board To list the configuration information of a board To display the state of a board To display the version information of a board To switch over the active and standby boards To reset a board To modify the loading switching of a board To list the loading properties of a board To display communication port state To modify the link type of the CPC sub-board on the WCSU To list the link type of the CPC sub-board on the WCSU Description Important Note: The LST commands are used to list configuration data. When you use the RMV BRD command to remove a board. while the DSP commands are used to display state. You cannot remove the boards/frames that are configured with subscriber data or functions.Operation Manual .

gateway resource management data.4. the rest are optional. When two pairs of WCDBs are configured. the TK. TK and MGWR must be configured on the same pair. and can be queried with the LST MDU command.Operation Manual . only the functions used by the local office are configured. This parameter is associated with the module number defined in the ADD BRD command. To save resources. including allocation of mobile station roaming number (MSRN) and transferring of VDP maintenance commands CGAP: Used for managing call gapping resources. Major Parameters [Function] This parameter is used to configure the functions for the WCDB based on the actual requirements. MGWR. Command ADD CDBFUNC III. [CDP Module Number] It refers to the module number of the WCDB.5 Adding CDB Function I. 2-12 . the WCDB stores all functional data like VLR agent functional data. MSOFTX3000 cannot operate normally without the WCDB. and VDB functions are compulsory. allocate the database functions on the two pairs based on the load-sharing principle. In the networking mode of time division multiplexing (TDM). Background Information Functioning as the central database of MSOFTX3000. Important Note: When one pair of WCDBs is configured. all database functions must be configured. outgoing trunk routing data. TK: Used for selecting outgoing trunks MGWR: Used for managing media gateway resources VDB: Used for managing VLR database (VDB) allocation parameters. including allocation and management of global call gapping in the WIN Generally. II.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 2 Configuring Equipment Data 2. and so on.

Related Commands See Table 2-8 for the commands related to CDB function configuration. It is associated with the module number defined in the ADD BRD command. enter the IP address of the WIFM here. [Default Gateway] It defines the IP address of the router to which the FE port connects.4. HT. The default value is Auto negotiation.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 2 Configuring Equipment Data IV. such as Auto negotiation. Major Parameters [IFM Module Number] This parameter refers to the module number of the WIFM where FE is configured. 2-13 . II. Command ADD FECFG III. When MSOFTX3000 directly connects to MGW.6 Adding FE Port Information of WIFM I. [Mask Address] These parameters are used to identify the WIFM in external communication. HH and FH. The WIFM dispatches messages to the WBSG for further processing according to the IP address and port number in IP packets. Table 2-8 List of commands related to CDB function configuration Command ADD CDBFUNC RMV CDBFUNC LST CDBFUNC Description To add function information of the WCDB To remove function information of the WCDB To list function information of the WCDB 2. [IP Address]. and it also processes IP bottom-layer protocols. FT.Operation Manual . you need to set FE port connection type for the WIFM to support the maximum number of call connections. In this case. [Ethernet Attribute] This parameter is used to specify Ethernet attributes. Background Information The WIFM interfaces MSOFTX3000 with IP network.

General Configuration Procedures Table 2-10 lists the procedures and commands for configuring E1 port data and clock data. MSOFTX3000 can lock the line clocks provided by external devices. and will be configured when MSOFTX3000 provides MTP links to connect a SS7 signaling network.Operation Manual . Table 2-9 List of commands related to FE port configuration Command ADD FECFG RMV FECFG MOD FECFG LST FECFG Description To add FE port information (IP address) of the WIFM To remove FE port information of the WIFM To modify FE port information of the WIFM To list FE port information of the WIFM 2. In the clock plan of MSOFTX3000. Introduction to E1 Port Data and Clock Data E1 port data and clock data are both equipment data. Such devices as MGW.5. HLR and PSTN can provide stable stratum-3 or higher clock sources.1 Before Configuration I. II.5 Locking Clock Reference Source through E1 2. Related Commands See Table 2-9 for the commands related to FE port configuration.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 2 Configuring Equipment Data IV. Table 2-10 Configuration procedures Procedure 1: Add WEPI and WCKI 2: Set clock reference source 3: Add E1 information 4: Extract clock reference data from WEPI ADD BRD SET CKICFG ADD EPICFG ADD BOSRC Command 2-14 .

Background Information None II. Background Information The WEPI and WCKI are both back boards.4. Major Parameters [Clock Level] Set it to stratum-2 clock or stratum-3 clock according to the requirement. Major Parameters Refer to 2.Operation Manual .5. Auto: The WCKI will automatically select the clock reference source with the highest priority. Related Commands Refer to 2.5.4 Adding Board for details.4. [BITS1 Priority] [BITS2 Priority] [Line Clock1 Priority] [Line Clock2 Priority] When the clock work mode is set to "Manual".Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 2 Configuring Equipment Data 2.4 Adding Board for details. Command SET CKICFG III. II. Manual: The WCKI will lock the specified clock reference source.2 Adding WEPI and WCKI I. and the priorities of two reference sources are the same. the clock boards will extract the clock reference source from clock source 1 to clock source 4. IV. [Work Mode] Set it to auto mode or manual mode for clock reference source. 2-15 .3 Setting Clock Reference Source I. 2. Command ADD BRD III. The WCKI can be inserted in slot 13 or 15 at the back of the basic frame (frame 0).

This parameter is associated with the slot number involved in the ADD BRD command.5. 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) IV. Major Parameters [Frame Number] This parameter refers to the frame number of the WEPI to which E1 belongs. Related Commands See Table 2-11 for the commands related to clock reference source configuration. Background Information When MSOFTX3000 processes the narrowband SS7 over TDM. it is required to add the WEPI and configure its E1 information.Operation Manual . II.4 Adding E1 Information I. [BITS2 Clock Source Type] These two parameters are used to define the external clock reference source synchronizing the WCKI. [Slot Number] This parameter refers to the slot number of the WEPI to which E1 belongs. It is associated with the frame number set in the ADD FRM command. Table 2-11 List of commands related to clock reference source configuration Command SET CKICFG LST CKICFG To set clock reference source To list clock reference source information Description 2.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 2 Configuring Equipment Data [BITS1 Clock Source Type]. Command ADD EPICFG III. It is used to locate the WEPI. [E1_0 Config] [E1_1 Config]……[E1_7 Config] 2-16 .

IV. [Balance Mode] This parameter is used to define E1 transmission mode. There are three options: Double frame (DF): default value CRC4: multi-frame format Not Config: not configured Generally. NON_BALANCE is selected. which are numbered from E1_0 to E1_7.5 Adding Clock Reference from WEPI I.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 2 Configuring Equipment Data This parameter is used to define whether an E1 is configured in the WEPI. Generally. you need to extract a 2-Mbit/s or 2-MHz clock reference source from the peer office equipment through E1 in the WEPI. select DF in interconnection with Huawei MGW. execute LST BOSRC to check if there is a pre-defined setting. Execute the command DSP BRD to display the E1 port state specified by the parameter “E1 number”. if so. the clock reference data cannot be extracted.Operation Manual . If the state is not normal.5. Before executing the command ADD BOSRC. NON_BALANCE indicates that the transmission line is 75-ohm non-balanced coaxial cable. Each WEPI provides eight E1s. Two options are provided for the actual modes of transmission line: BALANCE indicates that the transmission line is 120-ohm balanced twisted pair. remove the setting with the command RMV BOSRC. 2-17 . Related Commands See Table 2-12 for the commands related to E1 configuration. Background Information In the basic frame. Table 2-12 List of commands related to E1 configuration Command ADD EPICFG MOD EPICFG RMV EPICFG LST EPICFG Description To add E1 information of the WEPI To modify E1 information of the WEPI To remove E1 information of the WEPI To list E1 information of the WEPI 2.

6 Checking Clock Reference Source To check the clock reference source.5. Command ADD BOSRC III. do the following: 2-18 . If there are four WEPIs in the basic frame.Operation Manual . This parameter must be defined in the command ADD FRM and referenced here. Table 2-13 List of commands related to clock reference source configuration Command ADD BOSRC RMV BOSRC LST BOSRC Description To add clock reference source data of board To remove clock reference source data of board To list clock reference source data of board Note: When a pair of two adjacent WEPIs works in active-standby mode.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 2 Configuring Equipment Data II. 2. [Slot Number] It specifies the number of the slot in which the WEPI locates. IV. Related Commands See Table 2-13 for the commands related to clock reference source configuration. [E1 Number] It specifies the port number of the E1 in the WEPI through which the clock reference is extracted. Major Parameters [Frame Number] It specifies the number of the frame in which the WEPI locates. the clock reference source can only be extracted from the E1 connected to the active one. 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). This parameter must be defined in the command ADD FRM and referenced here.

Operation Manual .6. The phase-lock state should be “Trace Mode”. General Configuration Procedures Table 2-14 lists the general procedures for configuring E1 port and clock data in locking clock reference source through BITS. The WCKI can be inserted in slot 13 or 15 at the back of basic frame (frame 0). Introduction to Clock Reference Source of MSOFT3000 MSOFTX3000 serves as the clock reference source and connects to Building Integrated Timing Supply System (BITS). Command ADD BRD 2-19 . The WCKI can output stable stratum-2 clock signal to synchronize other equipment. Background Information The WEPI and WCKI are both back boards. The phase-lock duration of the WCKI is relatively long.6 Locking Clock Reference Source through BITS 2.6. Execute the command DSP CLKPH to check the phase-lock state.2 Adding WEPI and WCKI I. Table 2-14 Configuration procedures Procedure 1: Add WEPI and WCKI 2: Set clock reference source 3: Add E1 information ADD BRD SET CKICFG ADD EPICFG Command 2.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 2 Configuring Equipment Data 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. 2.1 Before Configuration I. about half an hour. II. II.

4 Adding E1 Information for details.3 Setting Clock Reference Source for details. IV. Command ADD EPICFG III. Major Parameters Refer to 2.4 Adding Board for details.4 Adding Board for details. Important Note: You must set the parameter “Clock Level” in the command to Level Two.6.5.4. 2-20 .3 Setting Clock Reference Source for details. Major Parameters Refer to 2. IV.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 2 Configuring Equipment Data III. 2. Major Paramters Refer to 2. Related Commands Refer to 2.3 Setting Clock Reference Source I.4. Background Information None II. Background Information None II. 2. Command SET CKICFG III. Related Commands Refer to 2.5.4 Adding E1 Information I.6.5.Operation Manual .

One basic frame.5.6. 2. Execute the command DSP CLKPH to check the phase-lock state. If all boards are working normally. 2.4 Adding E1 Information for details. The phase-lock duration of the WCKI is relatively long.6. The procedures of generating data loading files are shown in Table 2-15.000.7 Configuration Example 2.6 Loading Equipment Data If the equipment data is added in offline state.dat files) after the preceding configurations. 2-21 .1 Example Description Suppose a single cabinet is configured. you need to format all data of all modules to generate data loading files (dbxxx.Operation Manual . whose configurations are as follows: One integrated configuration cabinet. Table 2-15 Procedures of generating data loading files Command or procedure LON SET CWSON: SWT=ON SET FMT: STS=ON FMT Power off and load data To set online To enable alarm switch To enable format conversion switch To format data To reset all boards or unplug the WSMU Description After loading data. it indicates that the equipment data has been configured successfully and completely.7. do the following: 1) 2) Execute the command DSP BRD to check if the present clock reference source of the WCKI is extracted from MGW. check the working state of all boards. Subscriber capacity: 150. 2. at least half an hour. Related Commands Refer to 2. The phase-lock state should be “Trace Mode”.5 Checking Clock Reference Source To check the clock reference source.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 2 Configuring Equipment Data IV.

providing four 2-Mbit/s clock signals to the active/standby WCKIs (two signals for each WCKI). providing E1 interface. the others in back slots 1 and 3 are standby without interfaces. 2 and 3. 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. The WEPI must be installed in the back slots 0. The ones in back slots 0 and 2 are active.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 2 Configuring Equipment Data The WIFM of the control unit frame integrates the functions of the WBSG. 1. See Figure 2-2 for the board positions. WMGC and WIFM.Operation Manual . 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 8 9 10 11 12 13 14 15 16 17 18 19 20 Figure 2-2 Board positions in MSOFTX3000 2-22 .

200.20.132 Balance mode of E1 port (balance or non-balance) Non-balanced IP address of router connecting to MSOFTX3000 173.200. 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.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 2 Configuring Equipment Data Refer to Table 2-16 for the equipment data table. 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 IP address of FE port 173.253 Frame format of E1 port (DF/CRC4) DF 2-23 .Operation Manual .20.

MN=23. BT=WEPI. ADD BRD: FN=0. LOC=FRONT. //Add FE interface information of the WIFM. CN=1. ADD BRD: FN=0. //Turn off alarm switch. ADD BRD: FN=0. MSK="255. LOC=BACK. BT=WVDB.255. SN=0. IP="173. LOC=BACK. LOC=BACK. //Add frame. BT=WEPI. SN=2. BT=WCCU. ASS=3. DGW="173. ASS=5. ASS=15.200. SN=2.253".200. MN=22. ADD BRD: FN=0.0". RN=1.20. LOF:. BT=WCDB. BT=WEPI. ADD BRD: FN=0. LNKT=LINK_64K. MN=25. BT=WIFM.7. LOC=FRONT. ASS=1. ADD BRD: FN=0. BT=WCKI.0. SN=12. //Add board and module number. SN=14. //Add shelf. ADD FECFG: MN=132. PN=2.2 Configuration Description //Set offline. LNKT=LINK_64K.132". ADD BRD: FN=0. ADD FRM: FN=0. ADD BRD: FN=0. ADD BRD: FN=0. SN=0. ADD BRD: FN=0. SET CWSON: SWT=OFF.Operation Manual . ASS=13. MN=103. //Turn off format conversion switch. PN=1. SN=1. SN=13. SN=15. ADD BRD: FN=0. //Set E1 and clock data. ADD SHF: SN=0. SN=3. BT=WCSU. BT=WCSU. LT=" SX4". SN=10. 2-24 . BT=WCKI. SN=0. ADD BRD: FN=0. MN=132. LOC=BACK. LOC=FRONT.20. MN=102. SN=4. SET FMT: STS=OFF. ASS=11. LOC=FRONT.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 2 Configuring Equipment Data 2. LOC=FRONT. LOC=FRONT. LOC=BACK. BT=WEPI. LOC=BACK.

E1=DF. //Turn on alarm switch. E0=DF. E3=DF. E3=DF. //Set online. E5=DF. E5=DF. FMT:. ADD EPICFG: FN=0. Power off and on. SN=2. E6=DF. E7=DF. L2P=L2. E1=DF. SN=2. EN=0. E4=DF. E0=DF. 2-25 . ADD EPICFG: FN=0. BM=NONBALANCED. SN=0. and load data of all modules. E6=DF. B1P=L3. ADD BOSRC: FN=0. BM=NONBALANCED. E7=DF.Operation Manual . ADD BOSRC: FN=0. SET FMT: STS=ON.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 2 Configuring Equipment Data SET CKICFG: CL=LEVEL2. E2=DF. SN=0. LON:. E2=DF. //Format the data. B2P=L4. E4=DF. L1P=L1. WM=AUTO. EN=6.

to set the properties of the local MSC Server. signaling network to which the office belongs. In this format. whether the office is a signaling transfer point (STP). Currently.1 Local Office Information Before configuring service data. you need to set the local office information. including office type.2 MSC Number and VLR Number MSC/VLR number adopts E.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Configuring Office Data Chapter 3 Configuring Office Data 3. and the coding format is country code (CC) + national destination code (NDC) + locally significant part (LSP). 3-1 .2. signaling point (SP) code of the local office. MSC number is the same as VLR number. whether the office supports signaling connection control part (SCCP). and so on.2 Concepts Related to Office Data 3.1 Introduction to the Chapter This chapter describes the information that needs to be configured when MSOFTX3000 serves as an MSC Server. Therefore.164 coding mode. that is. and LSP is the number used in SS7 signaling messages to stand for MSC.2. MSC and VLR are configured together in the network. This chapter contains the following sections: Concepts Related to Office Data Collecting Office Data Configuring Office Data Setting MSRN/HON Allocation Mode Configuration Example 3. 3.Operation Manual . the meanings of CC and NDC are consistent with the specifications of mobile station international ISDN number (MSISDN).

3. In the shadowy columns are the parameters that require consistency between two ends.3 Multiple Signaling Points One physical node can be logically divided into multiple SPs. 3. the link of the mutual-assistant node can be used to transmit signaling messages. 3-2 . Because there are a maximum of 16 signaling links between two SPs.4 Mutual-Assistant Nodes For local SPs.Operation Manual .3 Collecting Office Data Before configuring office data. thus enhancing the reliability of the system. multiple virtual SPs to the same destination are the mutual-assistant nodes. each of which can separately connect with other SPs. you need to collect the office data of MSOFTX3000 as listed in Table 3-1.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Configuring Office Data 3.2. If a fault occurs to the link between one of the local SPs and the peer office.2. the multi-SP mode can be used to break through the limitation to 16 signaling links between two offices. and the others are internal parameters of MSOFTX3000.

refer to iGateway Bill User Manual. set the IP address of iGWB (the billing gateway) to “172.1”.200. 3-3 .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Configuring Office Data 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 VLR location update? Support HPLMN CFNRC? / / / / / 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. For further information on iGWB.Operation Manual . Select “True” for the parameter “BILLSERVEREXIST” in the command SET INOFFMSC and billing function is enabled.20.

Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Configuring Office Data 3.Operation Manual . Table 3-2 Procedures for configuring office data Procedure 1: Set local office information 2: Set local mobile network information 3: Set local VLR information 4: Set local MAP information 5: Set local SCCP subsystem 6: Set GT of local SCCP subsystem Command SET OFI/ADD OFI SET INOFFMSC/ADD INOFFMSC ADD VLRCFG ADD MAPACCFG ADD SCCPSSN ADD SCCPGT 3-4 . SET OFI/ADD OFI ADD SCCPSSN [Network indicator] [SSN] [SPC] [OPC] [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] Figure 3-1 Parameter relationship of commands for configuring office data II.1 Before Configuration I. General Configuration Procedures See Table 3-2 for the procedures and commands for adding office data. Parameter Relationship in Local Office Data The commands for configuring office data and their parameter relations are shown in Figure 3-1.4.4 Configuring Office Data 3.

The local office data index added for the first time is "0". If there are more than 16 signaling links between two offices. use the command ADD OFI to add SPs to break the number limitation of signaling links. II. When MSOFTX3000 serves as a gateway office in the national network. MSOFTX3000 supports multi-SP configuration at the local office. and national reserved network. national network. set the parameters "National Network Valid" and "National Reserved Network Valid" to "YES" and the other two parameters to "NO".4. Major Parameters [Local type] This parameter is used to define the office type of MSOFTX3000 in the network. signaling load sharing can be achieved. usually LOCMSC(MSC local office) is selected. When MSOFTX3000 serves as a 3-5 .Operation Manual . international reserved network. only the valid networks will be searched to avoid wasting system resources. In addition.2 Setting Local Office Information I. [International Network Valid] [International Reserved Network Valid]] [National Network Valid] [National Reserved Network Valid] MSOFTX3000 supports that the local office exists in four networks at the same time: international network. set "National Network Valid" to "YES". [Network 1] [Network 2] [Network 3] [Network 4] These parameters are used to set the order of network search. After the order is set. Select the office type according to the actual conditions of the local office. Command SET OFI/ADD OFI III. When MSOFTX3000 serves as an end office in the national network and national reserved network at the same time. When MSOFTX3000 serves as an end office in the national network and national reserved network at the same time. When using the command ADD OFI to add other SP codes. set "Network 1" and "Network 3" to "National" and the other two parameters to "National Reserved". Background Information Currently. For an end office. the local office SP index is incremented from 1.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Configuring Office Data 3.

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

Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Configuring Office Data These two parameters specify the voice mailbox as the destination for call forwarding on no reply (CFNR) and call forwarding busy (CFB). such as modifying the mutual-assistance relationship between local SPs. thus enhancing the reliability of the system. The bearer types include Internet protocol (IP). [InterMGWMediaType] This parameter indicates the bearer type among multiple MGWs connected to MSOFTX3000. the link of the mutual-assistant node can be used to transmit signaling messages. Set one among them according to the actual networking.4. They are not used in mobile network.3 Setting Local Mobile Network Information I. asynchronous transfer mode (ATM) and TDM. If a fault occurs to the MTP3 signaling link between one of the local SPs and the peer office. RMV OFI. select "AAL2". but are not used for configuring local office data. Background Information None 3-7 . For bearer over ATM. Related Commands See Table 3-3 for the commands related to office information configuration. MOD OFI are used only to configure multiple SP code data. IV. 3.Operation Manual . Table 3-3 List of commands related to office information configuration Command SET OFI ADD OFI RMV OFI LST OFI MOD OFI Description To set local office information To add a set of local SP codes To remove a set of local SP codes To list local office information To modify local office information Note: The commands ADD OFI. You can use the MOD OFI command to modify the mutual-assistant node information of the local SP. One SP can have a maximum of two mutual-assistant SPs.

Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Configuring Office Data II. For example. Currently. For example. and each MSC has its own local office information. the national prefix of China is 0. you need to add relevant MSC data as well. [Mobile Network Code]( MNC) This parameter is used to set the code of the mobile network to which the office belongs. Major Parameters [MSC Number] [VLR Number] These parameters are used to set the MSC number and VLR number of the local office. [Mobile Country Code]( MCC) This parameter is used to set the mobile country code (MCC) of the office. these two numbers are the same.Operation Manual . Command SET INOFFMSC/ADD INOFFMSC Important Note: When adding multiple SPs. the EIR function is not provided. One MSOFTX3000 can be configured with 16 MSCs in maximum. the mobile country code of China is 460. III. [National Prefix] This parameter is used to set the prefix of national toll calls. [EIR Number] This parameter is used to set equipment identity register (EIR) number of the local office. the international prefix of China is 00. Use the command SET INOFFMSC to configure the first MSC and ADD INOFFMSC to configure the other MSCs. Generally. so enter no value for this parameter. For example. the MNC of China Mobile is 00. The MSC number set in the ADD INOFFMSC command is consistent with that set in the SET INOFFMSC command. [International Number Prefix] This parameter is used to set the prefix of international toll calls. [Location Number] This parameter represents the zone code of the area in which the office is configured. It is used for zone code restriction service. For example. 3-8 .

000 users. If an office supports up to 350. Their values are the same as those set in the SET INOFFMSC command. Background Information None II. set this number for the parameter "Max. [Mobile Network Number] MCC and MNC refer to mobile country code and mobile network code respectively.Operation Manual .000. Table 3-4 List of commands related to local mobile network information configuration Command ADD INOFFMSC RMV INOFFMSC MOD INOFFMSC LST INOFFMSC Description To add local mobile network information To remove existing local mobile network information To modify existing local mobile network information To list local mobile network information 3. Major Parameters [Maximum No of Users] This parameter is used to set the maximum user number allowed by each VLR module. set this parameter to "TRUE" as the MSC Server needs bill server.000 users. If the maximum user number of each module is set to 180.4 Adding Local VLR Information I. two VLR modules are required as each one supports up to 200. IV. Related Commands See Table 3-4 for the commands related to the configuration of local mobile network information. [Mobile Country Code]. user". Command ADD VLRCFG III.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Configuring Office Data [BillServerExist] Generally.4. [Country Code] 3-9 .

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. or randomly. The handover number can be allocated according to MSC number. The default value is 90 seconds. and the value should be smaller than the implicit IMSI detach time set in VLR. VLR will delete this subscriber automatically. A timer shall be started when a roaming number is allocated. its value is set to "0". The periodic location update time is set in BSC or RNC. [MSRN Release Timeout(sec)] This parameter refers to the roaming number auto-release time.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Configuring Office Data This parameter is used to set country code. if this parameter is set to 24 hours. so that this number can be used again. LAI number. LAI number. when the subscriber’s mobile phone is powered off for more than 24 hours. [Authent Param Reuse Times] This parameter is used to define the times allowed to use the authentication set. For example. The default value is 24 hours. The time set here must be larger than the periodic location update time. [MSRN Allocation Mode] It defines roaming number allocation mode. the subscriber does not perform any message interaction with the VLR). [HON Allocation Mode] It defines handover number (HON) allocation mode. the roaming number will be automatically released by the timer. Generally. the country code of China is 86.Operation Manual . [IMEI Reuse Times] 3-10 . If the MS has not performed a location update within the implicit IMSI detach time. [User Purge Timer(hrs)] This parameter is used to define the time for deleting subscribers. [Implicit IMSI Detach Timer(min)] The default value is 120 minutes. For example. The MSRN can be allocated according to MSC number. If the VLR does not receive any release command. 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. or randomly. the system will set the subscriber to IMSI-DETACH state. the VLR is allowed to delete the subscriber.

Operation Manual . it means that IMSI authentication is required if TMSI authentication fails during service access or location update procedure.4. ADD/ RMV/LST MHMSCCFG. Table 3-5 List of commands related to VLR information configuration Command ADD VLRCFG LST VLRCFG MOD VLRCFG To add VLR information To list VLR information To modify VLR information Description 3. Major Parameters [Identify User] If it is set to “Yes”. Command ADD MAPACCFG III. 3-11 . 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.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Configuring Office Data It defines the reuse times of IMEI. ADD/ RMV/LST MHLAICFG If [MSRN Allocation Mode] and [HON Allocation Mode] was not configured. ADD/MOD/RMV/LST MHSUFFIX. Background Information None II. it would be impossible to allocate MSRN and HON. To reduce the traffic of message interactions with the mobile station side.5 Adding MAP Information I. IV. Related Commands See Table 3-5 for the commands related to VLR information configuration. The value shall be specified according to the actual requirement.

Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Configuring Office Data [ODB_SS] It is used to decide supplementary services to be barred. and short message services. 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 1–4 (user-defined fields) [Cipher] This parameter indicates whether the information to be transferred needs encrypting. if you select “CIPHER FOR 3G” for “Cipher”. [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. [Allocate TMSI When Update Location] This parameter defines whether TMSI reallocation is performed in location update procedure.Operation Manual . 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. [Cipher Algorithm] Select a cipher algorithm if it is needed. Similarly. The value can be specified according to the actual conditions. 3-12 . you must select a 3G cipher algorithm. you must select a 2G cipher algorithm. There are eight 2G cipher algorithm options (NOCIPH2G. If you select “CIPHER FOR 2G” for the parameter “Cipher”. UEA1 has higher priority. You can select several of them simultaneously. If both 3G cipher algorithms are selected. If 3G cipher is not needed. The MSOFTX3000 can control whether to cipher 2G and 3G respectively. supplementary services. A5_1 to A5_7) and two 3G cipher algorithm options (NOCIPH3G and UEA1) available. select “CIPHER FOR 3G” for the parameter “Cipher” and “NOCIPH3G” for the parameter “Cipher algorithm”. select “CIPHER FOR 2G” for the parameter “Cipher” and “NOCIPH2G” for the parameter “Cipher Algorithm”. when the session establishment to HLR fails and HLR terminates the session or HLR response duration times out during a normal location update procedure. [Allocate TMSI When Service Access] This parameter indicates whether TMSI reallocation is performed in call services. If 2G cipher is not needed.

Select “Yes”. select “Not Supported”. 3-13 . [Support Prepage] It defines whether prepaging is supported. MSC will restrict the roaming.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Configuring Office Data [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. If CAMEL subscribers are not supported. [Support Call Hold] It defines whether call hold is supported in the local office. CAMEL_PHASE2. [Support Zone Code Restriction] It defines whether the roaming restriction of zone code is supported. Prepaging means that VLR starts paging immediately after receiving the message “provide roaming number” (PRN). “Yes” means forwarding in GMSC and “No” means forwarding in visited mobile switching center (VMSC). [CAMEL Version] It defines CAMEL versions: CAMEL_PHASE1. location area. and CAMEL_PHASE3. and then it returns “PRN_ACK” to HLR after receiving “PAGING RESPONSE”. [MAP Version] It defines MAP versions: MAP_PHASE1. [Use Enhanced Roaming Restriction] It defines the roaming restriction for specific areas. [Support Gs Interface] It defines whether the Gs interface is supported between SGSN and MSC/VLR. MAP_PHASE2. Select it according to the actual networking mode. It is recommended to select “MAP PHASE 2+”. [Support SMMT Function] It defines whether short message mobile terminated (SMMT) function is supported on mobile phones. “Yes” means that when a subscriber roams to an area with a zone code that does not match any of the subscribed zone codes. [Support SMMO Function] It defines whether short message mobile originated (SMMO) function is supported on mobile phones. for instance. The default selection is “Yes".Operation Manual . and MAP_PHASE2+.

II.4. configure the local MSC and SCMG subsystems. Related Commands See Table 3-6 for the commands related to MAP information configuration. add the valid bit length for some numbers because the version buffer system has upper limit (10) and lower limit (7) for valid bits. select "NATIONAL NETWORK" for the local MSC and VLR subsystems. 3-14 . which is uniquely numbered throughout the entire system.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Configuring Office Data [Use AC Buffer] This parameter defines whether to use AC version buffer system. Table 3-6 List of commands related to MAP information configuration Command ADD MAPACCFG MOD MAPACCFG LST MAPACCFG To add MAP information To modify existing MAP information To list existing MAP information Description 3. run the command ADD SCCPSSN repeatedly. Major Parameters [SSN Index] It indicates the SCCP subsystem index. When MSOFTX3000 functions as a gateway mobile switching center (GMSC). Background Information When MSOFTX3000 functions as a visited MSC. IV. To add local SCCP subsystems. Generally.Operation Manual . If "Yes" is set. VLR and SCCP management subsystem (SCMG). [NI] This parameter is used to set the indicator of the network where the SCCP subsystem is located.6 Adding Local SCCP Subsystem I. configure the local MSC. Command ADD SCCPSSN III.

or SCMG subsystem according to the requirement. This command is used during maintenance. Related Commands See Table 3-7 for the commands related to SCCP subsystem configuration. To display SCCP subsystem in the host Description 3. [local concerned SSN1] – [local concerned SSN5] Because there is no related subsystem. VLR. Select MSC. select “Undefined”. II. Background Information It is necessary to set the local MSC GT and VLR GT for addressing. [Backup SSN Index] Because there is no backup subsystem. IV. For more information about configuring SCCP GT to HLR.Operation Manual . refer to Chapter 7 of this manual.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Configuring Office Data [SSN] This parameter refers to a subsystem.4. [SPC] [OPC] Both of the parameters are national network SP codes of the local office for local MSC and VLR subsystems.7 Adding Local SCCP GT I. Table 3-7 List of commands related to SCCP Subsystem configuration Command ADD SCCPSSN RMV SCCPSSN MOD SCCPSSN LST SCCPSSN SET SCCPSSN DSP SCCPSSN To add SCCP subsystem To remove existing SCCP subsystem To modify existing SCCP subsystem To list SCCP subsystem To set SCCP subsystem status. select the default value “65535”. Command ADD SCCPGT 3-15 . They are associated with the parameters defined in the SET OFI command.

Related Commands See Table 3-8 for the commands related to SCCP GT configuration. Table 3-8 List of commands related to SCCP GT configuration Command ADD SCCPGT RMV SCCPGT To add SCCP global title To remove existing SCCP global title Description 3-16 . [SPC] For the local MSC/VLR subsystem. enter the national network SP code. [GT indicator] There are four classes of GTs in the mobile network. Select "GT4 (TYPE4)” generally. [Numbering Plan] Select "ISDN (ISDN/TELEPHONY NUMBERING PLAN)" for MSC/VLR. it is only required to execute the command ADD SCCPGT once. [Translation result type] For local SCCP users. III.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Configuring Office Data Important Note: Because MSC and VLR are integrated. [Translation type] Select the default value "00" for the mobile network. the MSC GT and VLR GT are the same. This parameter is associated with the "SPC" defined in the SET OFI command. Major Parameters [NI] For the local MSC/VLR. In this case. [GT address information] Enter MSC number/VLR number for this parameter. set it to "SPC".Operation Manual . The network indicator is associated with that defined in the ADD SCCPSSN command. set this parameter to "National Network". IV.

The dotted line indicates that MSRN/HON allocation mode is determined by the parameters of the ADD VLRCFG command.5. and indicates that whether the subsequent command used is ADD MHLAICFG or ADD MHMSCCFG. Allocation Modes MSOFTX3000 can flexibly implement the following MSRN/HON allocation modes: Allocating MSRN/HON based on LAI number Allocating MSRN/HON based on MSC number Allocating MSRN/HON randomly You can set MSRN/HON prefixes and segments respectively corresponding to LAI and MSC.Operation Manual . The former two tables must be configured. ADD VLRCFG [MSRN Allocation Mode] [HON Allocation Mode] ADD MHLAICFG ADD MHPREFIX [MSRNHON Prefix Index] [MSRNHON Prefix] [MSRNHON Suffix Length] ADD MHSUFFIX [MSRNHON Suffix Index] [MSRNHON Prefix Index] [MSRNHON Suffix Start] [MSRNON Suffix End] [MSRNHON Number Type] [LAI Number] [MSRNHON Suffix ID] ADD MHMSCCFG [MSC Number] [MSRNHON Suffix ID] Figure 3-2 Relationship between MSRN/HON allocation parameters 3-17 . Parameter Relationship See Figure 3-2 for the relationship between MSRN/HON allocation parameters. which need to be customized according to requirement.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Configuring Office Data Command MOD SCCPGT LST SCCPGT Description To modify existing SCCP global title To list SCCP global title 3.5 Setting MSRN/HON Allocation Mode 3. and the latter two correspond to different allocation modes.1 Introduction to MSRN/HON Allocation I. II.

3-18 . Background Information None II. [MSRNHON Prefix] MSRN/HON prefix is composed of binary coded decimal (BCD) codes of 1–14 digits. The MSRN prefix includes country code and network access code. and the latter is added in the command ADD NACODE. 861390000. but its total length (MSRN prefix length plus suffix length) is between the minimum length and maximum lenth of the prefix of the called number analysis table. Command ADD MHPREFIX III. General Configuration Procedures Table 3-9 lists the procedures and commands for configuring MSRN/HON allocation mode. for example.2 Adding MSRN/HON Prefix I. The former is added in the command SET OFI. Table 3-9 Procedures for setting MSRN/HON allocation mode Procedure 1: Add MSRN prefix 2: Add MSRN suffix 3: Add corresponding relationship between MSC and MSRN 4: Add corresponding relationship between LAI and MSRN Command ADD MHPREFIX ADD MHSUFFIX ADD MHMSCCFG ADD MHLAICFG 3. The MSRN prefix here can contain the prefix of the called number analysis table. Major Parameters [ID] It is the MSRN/HON prefix index.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Configuring Office Data III.5. This parameter is associated with the parameter “Call Prefix” in the ADD CNACLD command when the parameter “Called Number Type” in the ADD CNACLD command is set to "MSRN/HON".Operation Manual .

for example. [MSRNHON Prefix ID] This parameter is already defined in the ADD MHPREFIX command. [MSRNHON Suffix Start] This parameter is used to set the specific start digit of the MSRN/HON number.to 4-digit suffix is composed of BCD codes ranging from 0 to 9. IV. [MSRNHON Suffix End] This parameter is used to set the specific end digit of the MSRN/HON number. 111. for example. 999. Table 3-10 List of commands related to MSRN prefix configuration Command ADD MHPREFIX MOD MHPREFIX LST MHPREFIX RMV MHPREFIX To add MSRN prefix To modify MSRN prefix To list MSRN prefix To remove MSRN prefix Description 3. Background Information None II. Command ADD MHSUFFIX III.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Configuring Office Data [MSRNHON Suffix Length] The length of MSRN/HON suffix is 2–4 digits.3 Adding MSRN/HON Suffix I. Related Commands See Table 3-10 for the commands related to MSRN prefix configuration. Major Parameters [ID] It is the MSRN/HON suffix index. You can query it with the command LST MHPREFIX. The 2to 4-digit suffix is composed of BCD codes ranging from 0 to 9. The 2.Operation Manual . 3-19 .5.

Operation Manual . Command ADD MHLAICFG III.5. Related Commands See Table 3-12 for the commands related to the configuration of corresponding relationship between LAI and MSRN. HON or MSRN/HON. 3-20 . Background Information None II. Major Parameters [LAI Number] It is already defined in the command ADD LAIGCI/ADD LAISAI. Table 3-11 List of commands related to MSRN suffix configuration Command ADD MHSUFFIX MOD MHSUFFIX LST MHSUFFIX RMV MHSUFFIX To add MSRN suffix To modify MSRN suffix To list MSRN suffix To remove MSRN suffix Description 3. It may be MSRN. [MSRNHON Suffix ID] You can query this parameter with the command LST MHSUFFIX.4 Adding Corresponding Relationship Between LAI and MSRN I.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Configuring Office Data [MSRNHON Number Type] This parameter is used to set the type of the added number. IV. IV. Related Commands See Table 3-11 for the commands related to MSRN suffix configuration.

[MSRNHON Suffix ID] You can query this parameter with the command LST MHSUFFIX.Operation Manual .5.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Configuring Office Data 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 3. Command ADD MHMSCCFG III. Related Commands See Table 3-13 for the commands related to the configuration of corresponding relationship between MSC and MSRN. IV. Background Information None II.5 Adding Corresponding Relationship Between MSC and MSRN I. Table 3-13 List of commands related to configuration of corresponding relationship between MSC and MSRN Command ADD MHMSCCFG LST MHMSCCFG RMV MHMSCCFG Description To add corresponding relationship between MSC and MSRN To list corresponding relationship between MSC and MSRN To remove corresponding relationship between MSC and MSRN 3-21 . Major Parameters [MSC Number] It is already defined in the command ADD INOFFMSC.

SCP SMC HLR GMLC MAP/ TDM MAP/ TDM MAP/ TDM MAP/ TDM MSC Server ISUP/ TDM MSOFTX 3000 BSSAP+ /TDM SGSN H. 3-22 .BSSAP / TDM SPC MGW IP/TDM MGW (SG) ISUP/TDM PSTN RANAP/ AAL2 /ATM BSSAP/ TDM RNC BSC Figure 3-3 Networking of MSOFTX3000 If MSOFTX3000 serves as a VMSC Server.1 Example Description Suppose the networking model is as shown in Figure 3-3.6. the local office information is as shown in Table 3-14.RANAP /IP ISUP.248.Operation Manual .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Configuring Office Data 3.6 Configuration Example 3.

Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Configuring Office Data 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 / Support VLR location update? Support HPLMN CFNRC? / / No Support SMMO/SMMT function? Yes No MAP/CAMEL version MAP_PHASE2+/ CAMEL_PHASE 3 / No No Support enhanced roaming restriction? No / / Support call hold? Yes Support interface? No Gs 3-23 .Operation Manual .

LOT=CMPX. OPC="CC0004". 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. ISSSMMT=YES. LAC=K'755. NN=YES. which includes two number segments. SN1=NAT. SSNNAME="LOCAL-VLR". //Add VLR information and MSRN/HON number allocation mode. CC=K'86. NATIONPFX=K'0. SUPGSIE=YES. NI=NAT. 3-24 . OPC="CC0004". NNS=SP24. ADD MAPACCFG: IFIDPROC=NO. SPC="CC0004". //Set local mobile office information. including MSC. SSN=VLR. MSRNAM=LAI. IFVLRLU=NO. CAMELVER=PHASE3. SPC="CC0004". NI=NAT. ISSSMMO=YES. NP2C="C04". MAPVER=PHASE3.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Configuring Office Data LAI number allocation mode is used for MSRN/HON. ADD SCCPSSN: SSNX=2. SET INOFFMSC: MSCN=K'8613600004.Operation Manual . ADD SCCPSSN: SSNX=0. SSNNAME="LOCAL-MSC". SSN=MSC.6. SET OFI: OFN="SX4". as shown in Table 3-15. SN3=NAT. IFSZCD=NO. SSN=SCMG. MNC=K'00. INNATIONPFX=K'00. SPC="CC0004". MCC=K'460. ADD VLRCFG: MAXUSR=12000.2 Configuration Description //Set local SP information. NN2S=SP14. NPC="CC0004". GAC=K'139. //Add MAP data. IFFWD=YES. IFUSROAMR=NO. IFALTMSILU=NO. OPC="CC0004". ADD SCCPSSN: SSNX=1. SSNNAME="LOCAL-SCMG". HONAM=LAI. MNC=K'00. LNC=K'86. NN2=YES. Table 3-15 An example of MSRN/HON numbering Cell 2G cell 3G cell MSRN/HON 86136000040001–86136000040999 86136000041000–86136000041999 Prefix index 0 0 Suffix index 0 1 LAI number 460000001 460000003 3. NI=NAT. //Add local SCCP subsystem. SN2=NAT2. SN4=NAT2. MCC=K'460. IFALTMSISA=NO. VLRN=K'8613600004. VLR and SCMG subsystems. IFUSACBUF=NO.

ADD MHSUFFIX: ID=0. ADD MHSUFFIX: ID=1. GTNAME="LOCAL-MSC". NUMPLAN=ISDN. and the cell should be added first. ADD CALLSRC: CSC=0. ADDR=K'8613600004. 3-25 . MSRNT=MSRNHON. //The //The ADD MHLAICFG: LAI="460000001". //Add MSRN/HON number allocation relationship: Number segments are allocated based on LAI. and the cell should be added first. SPC="CC0004". TRANSLATETYPE="00". //Add local SCCP GT. HPFX=K'8613600004. SSNNAME="LOCAL-NATB-SCMG". SPC="C04". SFXS="1000".Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center ADD SCCPSSN: SSNX=3. LST MHSUFFIX. //Add call source code. PFXIDX=0. //The MSRN/HON for 3G cell is from 86136000041000 to 86136000041999. ADD SCCPGT: GTX=0.Operation Manual . //List the index relationship between prefix and suffix. NI=NAT. Chapter 3 Configuring Office Data SSN=SCMG. SFXE="1999". index is 1 for suffix 1000–1999. MSRNT=MSRNHON. ADD MHLAICFG: LAI="460000003". PRESFX=0. ADD MHPREFIX: ID=0. SFXE="0999". //The MSRN/HON for 2G cell is from 86136000040001 to 86136000040999. ADD NACODE: NAC=K'136. PRESFX=1. PFXIDX=0. index is 0 for suffix 0001~0999. OPC="C04". SFXL=4. NI=NATB. SFXS="0001". RESULTT=LSPC2.

UDP and SCTP are based on IP.2. In the current networking.248 protocol (MGW control protocol) to communicate with MSC Server through the Mc interface. bearer over IP/SCTP is adopted.2. In R4 network.2 Concepts Related to Data Configuration for Interworking with MGW 4.1 Introduction to the Chapter This chapter describes how to configure data for MSOFTX3000 interworking with MGW. 4.1 Relationship Between MSC Server and MGW MGW cooperates with MSC Server to implement mobile switching functions of the core network. of which the protocol stack structure is shown in Figure 4-1.248 with three transport layer protocols: user datagram protocol (UDP). It contains the following sections: Concepts Related to Data Configuration for Interworking with MGW Collecting Data for Interworking with MGW Configuring Data for Interworking with MGW Configuration Example 4. and message transfer part 3 (broadband) (MTP3B).2 Networking Between MSOFTX3000 and MGW MSOFTX3000 provides H. stream control transmission protocol (SCTP). 4-1 .Operation Manual . and MTP3B is based on ATM. MGW applies H. MGW responsible for service bearer and MSC Server responsible for call control are detached physically to implement different functions.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Configuring Data for Interworking with MGW Chapter 4 Configuring Data for Interworking with MGW 4.

2.] ADD MCLNK [MGW index] [BSG/IFM/AFM/SGU/MGC Module No.Operation Manual .248 SCTP IP MAC Figure 4-1 Interface protocol structure between MSOFTX3000 and MGW 4.3 Parameter Relationship Figure 4-2 illustrates the referencing relationship between the parameters of MSOFTX3000 internal commands.] [Local IP1] [Local Port] [Remote IP1] [Remote Port] [Transport Protocol] ADD FECFG [IFM Module Number] [IP Address ] [Mask Address] SET SCTPPARA [Checksum Arithmeticr] Figure 4-2 Parameter relationship between MSOFTX3000 internal commands 4-2 . ADD MGW [Transport Protocol] [MGW index] [Codec List] [Device Name] [Server/Client] [..Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center IP IP MSOFTX3000 Chapter 4 Configuring Data for Interworking with MGW Mc MGW H..

4 General Configuration Procedures Table 4-1 shows the procedures and commands for configuring interworking data between MSOFTX3000 and MGW.3 Collecting Data for Interworking with MGW Before configuring data. Local IP address of the WIFM Local port number of the WIFM Remote IP address of MGW Remote port number of MGW MGW index Transport protocol Voice coding/deco ding mode Data Checksum mode MGW ciphering algorithm and ciphering key (optional) Server /client 4-3 . In the shadowy columns are the parameters requiring consistency between two ends or notification to the peer end. Table 4-1 Procedures and commands for configuring interworking data between MSOFTX3000 and MGW Procedure 1: Negotiate and prepare data 2: Add MGW 3: Add SCTP link to MGW 4: Set SCTP Checksum Algorithm (optional) 5: Set tone playing capability of MGW (optional) / ADD MGW ADD MCLNK SET SCTPPARA ADD/MOD TONECFG Command 4.Operation Manual .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Configuring Data for Interworking with MGW 4. Table 4-2 MGW information table Item Basic information / SCTP link information / SCTP link No. you need to collect the data for interworking between MSOFTX3000 and MGW as listed in Table 4-2. Other fields are internal parameters of MSOFTX3000.2.

WBSG and WMGC are combined into one board. and you can query it with the command LST MDU.1 Adding MGW I. and handling of gateway faults. set this parameter to the module number of the WIFM. [Transport protocol] Set this parameter according to the actual networking requirement. you can select one of the following based on the actual networking conditions: Bearer over IP: SCTP and UDP Bearer over ATM: MTP3B Currently.4 Configuring Data for Interworking with MGW 4. gateway state auditing. IP/SCTP bearer mode is used.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Configuring Data for Interworking with MGW 4.] This parameter sets the module number of the WMGC managing the gateway. MSOFTX3000 provides such three transport protocols as UDP. link state maintenance. In the mobile network applications. and to set its basic information and MGW capability. This parameter is used in gateway registration. SCTP. The module number is set in the ADD BRD command. Command ADD MGW Note: This command is used to add a MGW. Background Information None II.248 protocol. If the WIFM. [Control Module No. III.Operation Manual . and MTP3B for the H. Major Parameters [MGW Index] This parameter uniquely identifies an MGW in the system.4. [BCU ID] 4-4 .

For H.248-based MGW. According to different service categories. Local SDP Address Present: It defines whether a local IP address is included when modifying a local codec. It is unique and global in the network. As BNC character packet is not supported on access media gateway (AMG). and it identifies a physical MGW. there are different configurations: SCTP configuration [Device Name] 4-5 . integrated access device (IAD). ATM adaptation layer type 1 (AAL1). TMG. For different transport layer protocols supported by MGW. In the other cases. or media resource server (MRS). No Modem: It defines whether to detect modem. No Jitter: It defines whether the MGCP/H. which means that UMG carries backbone network connection (BNC) character packet. No Echo Cancellation: It defines whether the MGCP/H. This parameter is mandatory only when MGW is IAD. AAL1 or AAL2 IP network: IP TDM network: TDM [Special Attributes] It defines the special attributes of MGW in specific networking. and AAL1Struct. It is used in bearer independent call control protocol (BICC). IP. this option is not configured. do not select it. it is a mandatory parameter. No BNC Character: Set it to “Yes” for universal media gateway (UMG). The default value is used.248 messages sent by the MSOFTX3000 to the MG contain no echo cancellation (EC) field. it can be divided into TDM. No Fax: It defines whether to detect fax. AAL2.Operation Manual . such as local office and remote office. [BNC character] It defines the bearer category supported by MGW. This parameter need not be set in the mobile network.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Configuring Data for Interworking with MGW It specifies the identifier of the bearer control unit (BCU). ATM network: AAL1Struct. Select this option only when the MG is the TMG8010 manufactured by Huawei.248 messages sent by the MSOFTX3000 to the MG contain no jitter buffer field. [MGW Attribute] This parameter is used to set office type. 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.

It should be the same as that defined in MGW. Multiparty. used for encrypting stack information. The recommended value is 300. Playing Announcement. The following parameters are used to encrypt stack information: [Encryption type] This parameter is used to set encryption type. Therefore. [Rate of EC] This parameter is used to control echo cancellation capability. otherwise. and MGW to Client. Generally. The parameter is valid only when MGW uses UDP.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Configuring Data for Interworking with MGW It specifies the device name. and it should be larger than 0. [Security Parameters Index] [Sequence Number] [Key length] They are parameters for interconnection between MSOFTX3000 and MGW. Detecting DTMF. [Server/Client] It specifies whether MGW acts as a server or client. and interworking function (IWF). the SCTP link cannot be established. negotiation with MGW is necessary. UDP configuration [Domain Name] It specifies the domain name. and the other end to Server. It should be the same as that defined in MGW. including MD5. SHA1 and Not Supported. MTP3B configuration [MTP Name] It specifies the MTP name. Set it according to the actual capability of MGW. It is used to encrypt or decrypt protocol stack information. The parameter is valid only when MGW applies MTP3B. [Rate of IWF] 4-6 . The parameter is available when MGW uses SCTP. Sending dual tone multi-frequency (DTMF). It should be the same as that defined in MGW. Note that you must set one end of the SCTP link to Client. Use the default value. including Tone. The following parameters are used to set MGW capability set: [Capability] It specifies the MGW capabilities. set MSOFTX3000 to Server. The parameter is valid only when MGW uses SCTP.Operation Manual .

PCMU. and it should be larger than 0. and it should be larger than 0. The recommended value is 300. and G7231. The recommended value is 300. [Rate of TONE] MGW supports playing tone. [Rate of Detect DTMF] Set this parameter according to the actual capability of MGW.Operation Manual . [Rate of Multiparty] This parameter is used to set the multiparty service capability of MGW. and it should be larger than 0. [UMTS AMR2 Rate] It specifies the rate of UMTS AMR2. such as PCMA. You can select according to the actual situation. The recommended value is 300. You can select according to the actual situation.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Configuring Data for Interworking with MGW This parameter refers to the IWF capability. [UMTS AMR Rate] It specifies the rate of UMTS AMR. 4-7 . Set it according to the actual capability of MGW. and it should be larger than 0. Set the parameter according to the actual capability of MGW. [FR AMR Rate] It specifies the rate of full rate (FR) AMR. Set it according to the actual capability of MGW. and it should be larger than 0. [Codec List] This parameter is used to define the codec types supported by MGW. [Rate of Send DTMF] Set it according to the actual capability of MGW. [IWF Modem List] This parameter is used to define the types of modems supported by MGW. The recommended value is 300. [HR AMR Rate] It specifies the rate of the half rate (HR) adaptive multi-rate (AMR). [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.

you can set five links to one MGW. Background Information None II. IV. MTP3B. III. use the default value. In case of dual-homing. Table 4-3 List of commands related to MGW configuration Command ADD MGW RMV MGW MOD MGW LST MGW DSP MGW To add MGW To remove MGW To modify attributes of MGW To list attributes of all MGWs To display attributes of MGW of the host Description 4. otherwise. execute this command only once. configure according to the actual situation. 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. For UDP/MTP3B. TRUE (Master MGW). or SCTP).Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Configuring Data for Interworking with MGW [Main Type] This parameter is used in dual-homing configuration to configure the master/slave type of the MGW. that is.Operation Manual . Related Commands See Table 4-3 for the commands related to MGW configuration. Major Parameters [MGW Index] 4-8 . For SCTP.4.2 Adding SCTP Link to MGW I.

248 protocol. that is. SCTP. [BSG/IFM/AFM/SGU Module] It defines the module number of BSG/AFM/IFM/SGU processing SCTP links. When transmission control is implemented based on SCTP. This parameter needs to be negotiated with MGW. you need to specify a SCTP port number. The specified module will process the H248 messages on this MCLNK. 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. It has been defined in the ADD FECFG command. It is required to set the attributes of them one by one. [Transport Protocol] Set this parameter according to the actual networking requirement. 4-9 .] This parameter identifies an SCTP link. set the SCTP links as follows: [Link No. IP/SCTP bearer mode is used. Since transmission between the MSOFTX3000 and the MGW is based on IP. and MTP3B for H. [Local IP1] This parameter refers to the local IP address. and signaling is borne on SCTP/IP. It is optional. the external IP address of the WIFM. MSOFTX3000 provides such three transport protocols as UDP. MSOFTX3000 supports up to five SCTP links to MGW. It is used for the multi-homing function of the MSOFTX3000.Operation Manual .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Configuring Data for Interworking with MGW This parameter is used to identify the MGW to which an SCTP link is to be established. This parameter is defined in the ADD MGW command. [Local Port] This parameter refers to the local port number It is used to define the local communication port for SCTP connection. This parameter specifies the second local IP address. When using IP bearer mode. The links are numbered from 0. you need to specify a corresponding IP address for every link. In the mobile network applications. [Local IP2] This parameter refers to the second local IP address. It is associated with the parameter "MGW Index" defined in the ADD MGW command. You can query it with the command LST MDU. This IP address needs to be negotiated with MGW.

Operation Manual . Use the default value. Use the default value. If the checksum algorithm of MSOFTX3000 is inconsistent with that of MGW. [Max Outgoing Flow] This parameter is used to define the maximum number of flows sent by the first SCTP link. that is. that is. This IP address needs to be negotiated with MGW. [Remote Port] This parameter refers to the remote port number. 4-10 . It is used for the multi-homing function of the MSOFTX3000. This parameter is optional. [Max Incoming Flow] This parameter is used to define the maximum number of flows received by the first SCTP link.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Configuring Data for Interworking with MGW [Remote IP1] This parameter refers to the remote IP address. the external IP address of the peer MGW. Table 4-4 List of commands related to configuration of SCTP links to MGW Command ADD MCLNK LST MCLNK RMV MCLNK DSP MCLNK To add SCTP link to MGW To list the information of SCTP link to MGW To remove SCTP link to MGW To display the information of SCTP link mode to MGW Description 4. Background Information There are two SCTP checksum algorithms supported in MSOFTX3000: ADLER32 and CRC32. IV. Related Commands See Table 4-4 for the commands related to the configuration of SCTP links to MGW. the number of the communication port through which the specified SCTP link is connected to the peer MGW. It refers to the second external IP address of the peer MGW.4.3 Setting SCTP Checksum Algorithm (Optional) I. It needs to be negotiated with MGW. [Remote IP2] This parameter specifies the second remote IP address.

IV. III.4. If not. II.4 Setting Tone Playing Capability of MGW (Optional) I. Table 4-5 Command related to configuration of SCTP checksum algorithm Command LST SCTPPARA To list SCTP parameters Description 4. Background Information None II.Operation Manual . Select the same choice with MGW. modify the algorithm of MSOFTX3000 with the command SET SCTPPARA. Then check if the algorithm at the peer end is the same as that on MSOFTX3000. Related Command See Table 4-5 for the command related to the configuration of SCTP checksum algorithm. Command SET SCTPPARA Important Note: First execute the command LST SCTPPARA on MSOFTX3000 to query the parameter “Checksum Arithmetic”.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Configuring Data for Interworking with MGW the messages sent from one end will be regarded as invalid at the other end and then discarded. Major Parameters [Checksum Arithmetic] It defines the checksum algorithm to be ADLER32 or CRC32. Command ADD/MOD TONECFG 4-11 .

Generally. If you need to modify language and cycle number of the tone file. Related Commands See Table 4-6 for the command related to the configuration of tone playing capability of MGW. [Use Dummy T] It specifies whether to use dummy T. the default setting that language is English and cycle number is 2 is loaded. [Language1]–[Language5] It defines the priority of languages in which tone files are played. [Duration(sec)] It refers to the duration of playing the tone file (in seconds). [Interval Time (sec)] It refers to the interval time between two playings of the tone file. [MGW Tone ID] It refers to the tone ID defined in the MGW. This parameter is used to guarantee the continuity of tone playing in the process of switchover. Major Parameters [Internal Tone Type] It refers to the tone type defined in the MSOFTX3000. you do not need to set it. IV. The default value is 2.Operation Manual . During system initialization. use the MOD TONECFG command.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Configuring Data for Interworking with MGW Important Note: This command is used to define the tone file record. it is set to "Yes". and the duration depends on the length of the tone file. 4-12 . III. or you can delete the original record and then use the ADD TONECFG command to add a tone file record. [Cycle Number] It defines the repeat times of tone playing. Generally.

Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Configuring Data for Interworking with MGW 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 4. SCP SMC HLR GMLC MAP/TDM MAP/TDM MAP/TDM MAP/TDM MSC Server ISUP/TDM MSOFTX 3000 BSSAP+/TDM SGSN H.Operation Manual .BSSAP/ TDM SPC MGW MGW IP/TDM (SG) ISUP/TDM PSTN RANAP/AAL2 /ATM BSSAP/ TDM RNC BSC Figure 4-3 Networking of MSOFTX3000 4-13 .5.248.RANAP/ IP ISUP.1 Example Description Suppose the networking model is as shown in Figure 4-3.5 Configuration Example 4.

132". TONERATE=12. CPB=TONE-1&PA-1&SENDDTMF-1&DETECTDTMF-1&MPTY-1&IWF-1. This example is for the integrated configuration of WIFM.20. LST FECFG:. MGWDESC="MGW1".Operation Manual . BNCC=IP-1&AAL1-1. CTRLMN=132. 4-14 . 0 CRC32 Server Remote IP address of MGW 173. WMGC and WBSG.132 Since the SCTP checksum algorithm on MSOFTX3000 differs from that on MGW. For MGW information table. ADD MGW: MGWIDX=1. The times of cyclic playing of the 117 time announcement tone (TID_0X0002) is to be set to 3.200. //Add SCTP link to MGW. refer to Table 3-14 in Chapter 3. LST MDU:. 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.200. MPTYRATE=0. BCUID=1. TCRATE=1.5. SLOCIP1="173.200. one of them is to be modified to the same as the other one. 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. TRNST=SCTP.2 Configuration Description //Check the WIFM module number and IP address and WMGC module number. LNKN=0. DEVNAME="MGW1". HRAMRR=RATE795-1&RATE740-1&RATE670-1&RATE590-1&RATE515-1&RATE475-1.20.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Configuring Data for Interworking with MGW This example is to add an MGW. TRNST=SCTP. ECRATE=0. 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 1 SCTP link No. SVRCLIENT=SVR. BSGMN=132.20. //Add basic information of MGW. see Table 4-7. For the local office information. ENCT=NSUP. 4. IWFRATE=1. DETDTMFRATE=0. ADD MCLNK: MGWIDX=1. SNDDTMFRATE=0.

4-15 . //Set tone playing capability of MGW (optional). LST SCTPPARA:.93". Chapter 4 Configuring Data for Interworking with MGW //Modify SCTP checksum algorithm (optional). SET SCTPPARA: CHKSUMTYPE=CRC32.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center SRMTIP1="173.200. CYCN=3.Operation Manual .20. MOD TONECFG: INTTID=TID_0X0002.

1 Basic Concepts of M3UA For basic concepts and terminologies of MTP3-user adaptation layer (M3UA). MGW is typically used as a signaling transfer point in current networking applications. M3UA link set.2 Related Concepts 5. M3UA link.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Configuring Data for Interworking with RNC Chapter 5 Configuring Data for Interworking with RNC 5. signaling gateway. It contains the following sections: Related Concepts Collecting Data for Interworking with RNC Configuring Data for Interworking with RNC Configuration Example 5.Operation Manual . such as application server. M3UA route. Signaling messages between MSOFTX3000 and MGW are carried over IP.1 Introduction to the Chapter This chapter describes how to configure data for MSOFTX3000 interworking with Radio Network Controller (RNC). which can be based on either ATM or IP. and signaling messages between MGW and RNC are carried over ATM. and M3UA entity.2. see Chapter 4 “M3UA of Transport Protocols Part” in HUAWEI MSOFTX3000 Mobile SoftSwitch Center Technical Manual-Signaling & Protocols.2. 5-1 . See Figure 5-1 for the networking.2 Networking between MSOFTX3000 and RNC Radio access network application part (RANAP) protocol is used between MSOFTX3000 and RNC. 5.

3 Parameter Relationship Figure 5-2 illustrates the parameter referencing relationship at MSOFTX3000 side during configuration.248 protocol when you are configuring an M3UA link. the application server (AS) independently occupies signaling point codes. 5. MGW is configured with built-in SG function to adapt MTP3B to M3UA and transfer it to MSOFTX3000 over IP. The parameter “NI” in the figure must be assigned with the same attributes. the networking is illustrated under the conditions that M3UA adopts transfer mode. and MGW (built-in SG) is defined as a signaling gateway (SG).Operation Manual . the working mode of M3UA is SGP-ASP.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Configuring Data for Interworking with RNC IPIP承载 bearer MSOFTX3000 MGW ATM承载 ATM bearer RNC RANAP SCCP M3UA SCTP IP MAC M3UA SCTP IP MAC (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. 5-2 . M3UA implements IP bearer through SCTP. and M3UA links are identified by IP addresses plus port numbers. In this networking structure. Here. Therefore.2. MSOFTX3000 is defined as an AS. you need to specify a port number that is different from the one for bearing H.

Operation Manual .4 General Configuration Procedures Table 5-1 shows the procedures and commands for configuring interworking data if MGW is used for transferring signaling messages between MSOFTX3000 and RNC and that IP bearer is used for networking.2. 5-3 .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center ADD M3LE [Local Entity Index] [Local Entity Point Code] [NI] [Local Entity Type] [Route Context](optional) --- Chapter 5 Configuring Data for Interworking with RNC 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) Figure 5-2 Parameter relationship between MSOFTX3000 and RNC/MGW 5.

you need to collect the data for interworking between MSOFTX3000. MGW (SG).Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Configuring Data for Interworking with RNC 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. 5-4 . The other parameters are the internal ones of MSOFTX3000. as shown in Table 5-2.Operation Manual .3 Collecting Data for Interworking with RNC Before configuring data. In the shadowy columns are the parameters that must be negotiated between two ends for consistency or of which one end must notify the other end. and RNC.

Mc Interface Data For the data configuration about the Mc interface between MSOFTX3000 and MGW. see HUAWEI UMG8900 Universal Media Gateway Operation Manual-Data Configuration. II. refer to Chapter 4 “Configuring Data for Interworking with MGW”. route. route. and link. Data to be Configured at MGW Side 1) Interface configuration Signaling messages of MGW are sent to MSOFTX3000 through the Mc interface (10/100 Mbit/s adaptive Ethernet interface) provided by the MPPU.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Configuring Data for Interworking with RNC 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 5.1 Negotiating and Preparing Data I. What need be configured are the IP address and route of the Mc interface.Operation Manual . link set.4 Configuring Data for Interworking with RNC 5.4. flow. 2) M3UA link configuration It includes the configuration of M3UA entity. For more information. 5-5 .

and that at peer MGW side to “SG”. II. For the SGP-ASP mode. A signaling point can simultaneously appear in international network. configure it first. and national reserved network. national network. Background Information Before adding M3UA local entity for MSOFTX3000.Operation Manual . set the entity type at MSOFTX3000 side to “AS”. Related Commands See Table 5-3 for the commands related to M3UA local entity configuration 5-6 .4. It may be SG or AS. The route context at AS side must be the same as that at SG side. If not. [Route Context] (optional) It is used to specify the index value of a group of SS7 parameters. IV. This parameter can be configured when the entity type is AS. [NI] It is used to indicate the network type. execute LST OFI command to check whether the local original point code (OPC in national reserved network) is configured. It is the same as the network indicator of RNC.2 Adding M3UA Local Entity I. [Local Entity Type] It is used to define the type of a local entity. [Local Entity Point Code] It is used to define the signaling point code of a local entity.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Configuring Data for Interworking with RNC 5. Major Parameters [Local Entity Index] It is used to uniquely identify an M3UA local entity. This code is associated with the parameter in the command SET OFI. international reserved network. Command ADD M3LE III.

[Destination Entity Point Code] 5-7 . it appears that MGW has a signaling point code which in fact is allocated to SG. Command ADD M3DE III.3 Adding M3UA Destination Entity I. This index is already defined in the ADD M3LE command. [NI] It is used to indicate the network type. Background Information You must set the destination entity before a path from the local entity to the destination entity becomes available. In this case. functioning as SG and to be configured with the DSP of SG. national network. the other is RNC. and national reserved network. II. A signaling point can simultaneously appear in international network. functioning as SP and to be configured with the DSP of RNC. As the SG function is integrated in MGW.Operation Manual . international reserved network. Major Parameters [Destination Entity Index] It is used to identify a destination entity uniquely. You need to add two types of destination entity: one is MGW (with built-in SG).4. MGW resident office shall allocate a signaling point code for the built-in SG.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Configuring Data for Interworking with RNC 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 5. [Local Entity Index] It is used to identify a local entity to which the destination entity corresponds.

select “TRUE”. add MGW as SG and RNC as SP. [Destination Entity Type] It is used to define the type of a destination entity. It includes two modes: INCLUSIVE: The traffic that belongs to this point code of a destination entity is shared with other destination entities. To set the destination entity to SG type. [Network Mode] This parameter is used to specify the network mode between SG and AS. whether there is a signaling link directly associated with the local office signaling point. and AS. SG. This parameter is only valid whenthe parameter “Destination Entity Type” is set to “AS” or “SG”. By default. [Link set select mask] This parameter indicates how to achieve load sharing among all routes to an M3UA destination entity. EXCLUSIVE: The traffic that belongs to this point code of a destination entity is not shared with any other destination entity. [STP Flag] It is used to set whether a DSP has STP function. You need not set it here.Operation Manual . that is. Select “YES” when there is such a direct signaling link with the local office signaling point. Its value is determined by the actual destination entity type to be configured. There are three types of destination entity. otherwise. select “FALSE”. 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. to set it to SP type. it is RFC3332. By default. the AS is an exclusive SPC. namely SP. select “NO”. You need to set it to DRAFT10 when adding the SG destination entity. [Adjacent Flag] It is used to set whether a DSP is adjacent to the local office signaling point. 5-8 . MSOFTX3000 supports the interconnection with the M3UA destination entity specified in DRAFT10 or RFC3332. As MGW also functions as an SG. [Protocol Version] It is a parameter for interconnection between MSOFTX3000 and a destination entity.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Configuring Data for Interworking with RNC It is used to specify the signaling point code of a destination entity.

[Link Select Mask] It indicates how to share signaling traffic among the multiple signaling links in the same signaling link set. Major Parameters [LinkSet Index] It is used to specify the logical number of a link set in the system. Command ADD M3LKS III. This index is related to the parameter “destination entity index” in the ADD M3DE command.4. II. Related Commands See Table 5-4 for the commands related to M3UA destination entity configuration. The index is used in the M3UA routing table. Table 5-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 5. [Adjacent Entity Index] It is used to identify the adjacent destination entity interconnected by the associated signaling link set. The index is numbered globally in ascending order from 0.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Configuring Data for Interworking with RNC IV.Operation Manual . 5-9 .4 Adding M3UA Link Set I. The value of this parameter is actually the load-sharing mask code of signaling links. Background Information This section describes how to establish a link set between two M3UA adjacent entities. Set the parameter “adjacent flag” of the corresponding destination entity to “adjacent".

"Local Entity Type” in the ADD M3LE command is “AS”. The default option (load-share mode) is recommended. In the non-peer networking mode. Table 5-5 List of commands related to M3UA link set configuration Command ADD M3LKS RMV M3LKS MOD M3LKS LST M3LKS DSP M3LKS To add M3UA link set To remove M3UA link set To modify M3UA link set To list M3UA link set To display M3UA link set of the host Description 5. In the peer networking mode. that is. the M3UA destination entity type is the same as the local entity type. That is. the M3UA destination entity type is SG. IPSP. IV. select “ASP”. that is. "Local Entity Type” in the ADD M3LE command is “AS”. In this case. In this case. according to the working mode of the link set. and the corresponding local entity type is AS. 5-10 . and the corresponding local entity type is SG. and SGP.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Configuring Data for Interworking with RNC [Traffic Mode] It is used to determine the service mode of the link set is “Load-Share Mode” or “Over-Ride Mode”.5 Adding M3UA Route I. You can set priority for the route for carrying signaling traffic. such as ASP. [Work Mode] It is used to indicate the attributes of the home end of a link set. The traffic modes at two ends must be the same. Related commands See Table 5-5 for the commands related to M3UA link set configuration. the M3UA destination entity type is AS. select “IPSP". otherwise. Background Information This section describes how to determine a signaling route to a destination entity by specifying a link set that can reach this destination entity.4. the two ends must be in load-share mode or over-ride mode at the same time. It is associated with the parameter “Local Entity Type” in the ADD M3LE command. In the non-peer networking mode. the corresponding link cannot be activated. select “SGP”. AS or SG. that is.Operation Manual .

[Priority] “0” indicates the highest priority. 5-11 .6 Adding M3UA Link I. Among the several signaling routes to the DSP. Related Commands See Table 5-6 for the commands related to M3UA route configuration. “Peer IP Address1”. Command ADD M3RT III. [LinkSet Index] It is used to specify a signaling link set used by the signaling link reaching a destination entity.Operation Manual .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Configuring Data for Interworking with RNC II. It is already defined in the ADD M3DE command. Major Parameters [Destination Entity Index] It is used to identify a destination entity to which a signaling route is destined. Table 5-6 List of commands related to M3UA route configuration Command ADD M3RT RMV M3RT MOD M3RT LST M3RT DSP M3RT To add M3UA route To remove M3UA route To modify M3UA route To list M3UA route To display M3UA route of the host Description 5. IV.4. and “Peer Port” with the peer end to uniquely determine an M3UA link. Background Information You need to negotiate such parameters as “Local IP Address1”. “Local Port". A signaling route will carry signaling traffic unless none of signaling routes with higher priority is available. This parameter is defined in the ADD M3LKS command. the one with the highest priority is preferentially used to carry signaling traffic.

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

0 indicates the highest priority. You can set MSOFTX3000 to either client or server as long as it is not the same as MGW (SG). otherwise. IV. ”TRUE”. set it based on the actual situation. If you adopt the load sharing mode. [Main Type] It is used to set the dual homing function of MSOFTX3000. [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. It indicates if a link is active or standby. Related Commands See Table 5-7 for the commands related to M3UA link configuration.Operation Manual . Set other parameters to the default values. Table 5-7 List of commands related to M3UA link configuration Command ADD M3LNK RMV M3LNK To add M3UA link To remove M3UA link Description 5-13 . When MSOFTX3000 supports the dual homing function.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Configuring Data for Interworking with RNC [Peer Port] It is used to specify the communication port of the peer MGW. [C/S Mode] It is used to set whether a link is at the client side or server side. If no dual homing function is applied for MSOFTX3000. [Priority] This parameter is used to specify the priority of a link in a link set. use the default setting. [Active/Standby Flag] This parameter is used to set the work state for this M3UA link in the normal situation. while others must be set to standby. that is. M3UA links cannot be set up normally. 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. Set one end to client and the other end to server. you must set all M3UA links in the same link set to active. It has to be negotiated with MGW. This parameter must be negotiated with the peer end. Select the link with the highest priority first.

and DPC. Major Parameters [DSP Index] It uniquely identifies an SCCP DSP. Background Information One SCCP DSP is uniquely identified by NI.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Configuring Data for Interworking with RNC 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 5. The originating point code (OPC) and destination point code (DPC) must be consistent with those of the lower layer (MTP3/MTP3B/M3UA) when an SCCP DSP is configured. As IP bearer mode is adopted between the local office and RNC. and there is no reference relation among them.4. 5-14 . [NI] It identifies the network where the SCCP subsystem is resident.Operation Manual . ranging from 0 to 511. II.7 Adding SCCP Remote Signaling Point I. It must be noted that the “DSP Index” defined here is different from the “DSP Index” defined in ADD N7DSP and “Destination Entity Index” defined in ADD M3DE. Use the LST M3DE command to check whether the RNC DPC specified is consistent with that in the M3UA destination entity table. OPC. the DPC of RNC must be first configured in the destination entity table of M3UA. Command ADD SCCPDSP III.

5-15 . Related Commands See Table 5-8 for the commands related to SCCP DSP configuration. It must be specified in the command SET OFI first and then referenced here. IV. [OPC] It is used to specify the OPC of the local office with the same network indicator.Operation Manual . It is used to specify the standby DSP of SCCP.[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 must be defined in ADD N7DSP or ADD M3DE first and then referenced here.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Configuring Data for Interworking with RNC [DPC] Set it to the SPC of the RNC at the peer end. You can query it with the command LST OFI.

If they have been configured in the local office information. You must first run LST SCCPSSN to have a check for avoiding repetition. RANAP. SSN identifies SCCP users at a signaling point. [NI] It is used to identify the network where the SCCP subsystem is resident. II. SSN to be configured for RNC at the remote end is SCCP management subsystem (SCMG).4.Operation Manual . Subsystem number (SSN) provides local addressing information for SCCP. VLR. Subsystems to be configured locally and remotely include: SSN of the MSOFTX3000 at the local end is RANAP. Background Information This section describes how to add SCCP subsystems of MSOFTX3000 (local) and RNC (remote). they need not to be configured here. and SCMG of the local office need also to be configured. [SSN] 5-16 . MSC.8 Adding SCCP Subsystem I. Major Parameters [SSN Index] It is used to set the index of the SCCP subsystem. and it is unique in the system.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Configuring Data for Interworking with RNC 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 5. Command ADD SCCPSSN III.

If there is no subsystem. the recipient of SCCP messages. this OPC is a local SPC. If there is no related subsystem. use the default value “65535”. [OPC] It is used to specify the originating SPC of the corresponding subsystem. [SPC] It is used to specify the destination SPC of the corresponding subsystem. that is. SCMG and RANAP are configured for both local and remote ends. Related Commands See Table 5-9 for the commands related to SCCP subsystem configuration. that is.Operation Manual . It is valid only when MSOFTX3000 supports the load sharing function or backup function of SCCP DSP. use the default option “UNDEFINED”. IV. For each subsystem. It must be defined in the command SET OFI first and then referenced here. You need to set RNC SPC and OPC 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. the sender of SCCP messages. [Backup SSN index] It is used to specify the index of the backup subsystem of the specified subsystem. You can define a maximum of five indexes.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Configuring Data for Interworking with RNC It is used to set the subsystem number. Table 5-9 List of commands related to SCCP subsystem configuration Command ADD SCCPSSN RMV SCCPSSN MOD SCCPSSN LST SCCPSSN SET SCCPSSN DSP SCCPSSN Description To add SCCP subsystem To remove existing SCCP subsystem To modify existing SCCP subsystem To list SCCP subsystem To set SCCP subsystem status for maintenance purpose To display SCCP subsystem of the host 5-17 .

[Network ID] This parameter of the MSOFTX3000 must be consistent with that set at the peer end of the network. [Peer Office Level] As RNC is in a lower level than MSC Server. select “RNC”. select “RNC”. Major Parameters [Office Direction] It is allocated uniquely in the system to identify an office direction. select “LOW (INFERIOR)”. for example. [Destination Point Code1]–[Destination Point Code16] These parameters have to be negotiated with RNC. use the default values. For other parameters. 5-18 . "TO-SZ_RNC". [Office Direction Name] It is recommended to use a canonical name for the sake of easier identification. Related Commands See Table 5-10 for the commands related to office direction configuration.4.9 Adding RNC Office Direction I. IV. [Opposition Office Type] For this parameter. II. They are associated with RNC signaling point codes in the ADD SCCPDSP command.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Configuring Data for Interworking with RNC 5.Operation Manual . [Peer Office Attribute] For this parameter. Background Information This section describes how to set an office direction from MSC Server to RNC. Command ADD OFC III.

It is associated with the RNC DPC in the ADD SCCPDSP command. [Location Area ID] 5-19 . [List of Net Support AMR Rate] It is used to specify the list of AMR rates supported by the network. Major Parameters [RNC ID] It is allocated uniquely across the network to identify an RNC.Operation Manual .4. Currently. II. Command ADD RNC III. It is used to configure a QAAL2 path. OPC must be the same for all RNCs. [Origination Point Code] It is used to define the local signaling point code in the office information table. [Network ID] This parameter of the MSOFTX3000 must be consistent with that set at the peer end of the network.10 Adding RNC Global Indicator I. Background Information None. This parameter needs to be negotiated with RNC. [Destination Point Code] It is used to set the destination signaling point code of RNC.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Configuring Data for Interworking with RNC 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 5.

4. Major Parameters [3G Service Area No.] It is a 9-bit location area code if what is configured is a location area or a 13-bit cell number if what is configured is a 3G service area.Operation Manual . you must set this parameter. If [Location Area Not Unique Flag] is set to “FALSE”. The concerned code or number is given in the network planning phase. [VLR No. This LAI is used to complement the incomplete cell ID which is sent from RNC. II. use the default values. Related Commands See Table 5-11 for the commands related to RNC configuration. IV. of 3G Service Area] It is used to set the MSC number to which the 3G service area belongs. [MSC No. Command ADD LAISAI III. For other parameters. The following “LA category” parameter is used to identify the type. Table 5-11 List of commands related to RNC configuration Command ADD RNC RMV RNC MOD RNC LST RNC To add a RNC To remove an existing RNC To modify attributes of an existing RNC To list information about configured RNC Description 5. It is provided by the serving operator. of 3G Service Area] 5-20 .11 Adding 3G Service Area I. Background Information This section describes how to configure a location area or a 3G service area. It is already defined in the ADD INOFFMSC command.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Configuring Data for Interworking with RNC Configure the unique LAI to which RNC belongs. “LA category” parameter is used to distinguish them.

[Perform Roaming Analysis] Roaming analysis is performed on a specific location area. [RNCID1]–[RNCID10] These parameters are used to set the RNC ID of 10 RNCs to which an area belongs. Generally. If the location area/3G service area is in the coverage of the local MSC/VLR. It is already defined in the ADD INOFFMSC command. Select “LAI” if the current entry is set for a location area. 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. To guarantee external handover of mobile stations between MSCs. It is used for roaming restriction. a late assignment is initiated when the network receives CONNECT from the called party. [LA Category] It is used to set the category of a location area.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Configuring Data for Interworking with RNC It is used to set the VLR number to which the 3G service area belongs. For a calling party. [Call Source Code] 5-21 .] It is used to specify the corresponding identity of an area. an early assignment is initiated by sending a request when the network receives CALL CONFIRMED from the called party. They are associated with the parameter “RNC ID” in the ADD RNC command. It is provided by the serving operator. MSC and VLR are integrated together. Select “SAI” if the current entry is set for a 3G service area. [Location No. For a called party. 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. a late assignment is initiated after the network sends ALERTING to the calling party. otherwise.Operation Manual . Set this parameter to YES if roaming restriction is required for a location area. set this parameter to “in adjacent VLR”. set this parameter to “in local VLR”’. an early assignment is initiated by sending a request when the network receives CALL PROCEEDING from the calling party. [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.

12 Adding Access Media Gateway I. Related Commands See Table 5-12 for the commands related to 3G service area configuration. It is already defined in the ADD OFC command. IV. 5-22 .] It is used to set the corresponding office direction number of RNC. [Media Gateway Index] It is defined in the ADD MGW command.4. [Office No. This parameter is already defined in the ADD OFC command. Related Commands See Table 5-13 for the commands related to access media gateway configuration. Table 5-12 List of commands related to 3G service area configuration Command ADD LAISAI MOD LAISAI LST LAISAI RMV LAISAI Description To add location area identity or cell global identification To modify location area identity or cell global identification To list location area identity or cell global identification To remove location area identity or cell global identification 5. Command ADD RANMGW III.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Configuring Data for Interworking with RNC 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.Operation Manual . IV. Major Parameters [Office Number] It is used to identify an office direction of the particular entity interconnected with MGW. Background Information None II.

Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Configuring Data for Interworking with RNC 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 5.248.Operation Manual .BSSAP / TDM SPC MGW IP/TDM MGW (SG) ISUP/TDM PSTN RANAP/AAL2/ATM BSSAP/TDM RNC BSC Figure 5-3 Networking of MSOFTX3000 5-23 . SCP SMC HLR GMLC MAP/TDM MAP/TDM MAP/TDM MAP/TDM MSC Server ISUP/TDM MSOFTX 3000 BSSAP+/TDM SGSN H.RANAP /IP ISUP.1 Example Description Suppose the networking model is as shown in Figure 5-3.5 Configuration Example 5.5.

LOCPORT=2905.1 32 Route selection code 65535 Local port 2905 Prefix / Local prefix 1360755 5. LOCIP1="173. DPC="1004". LNKN=0. LSX=0. //Query the OPC whose NI = NATB. //Query the local IP address of WIFM. LET=AS. which is connected to MGW. PEERPORT=2905 CS=C. ADD M3LKS: LSX=0. NI=NATB. 5-24 . LST OFI:. LSX=0.2 Configuration Description //Add M3UA.93".20.200. NI=NATB. The related information is shown in Table 5-14. LST FECFG:. ADD M3RT: RTNAME="ToMGW1". DEVER=DRAFT10.5.200. ADD M3RT: RTNAME="ToRNC4". LENAME="MscM3UA". ADD M3DE: DEX=0. ADD M3LE: LEX=0. ADD M3LNK: MN=132. DET=SP. 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.Operation Manual .132". IP based bearer is used between MSOFTX3000 and MGW. DENAME="MgwM3ua".20. OPC="C04". It is also assumed that Mc protocol data have been already configured.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Configuring Data for Interworking with RNC As shown in the figure. DENAME="RncM3ua". there is an MGW used for transfer between MSOFTX3000 and RNC. DET=SG. LSX=0. DPC="D04".20.200. This example adds an RNC. see Table 3-14 in Chapter 3.200. NI=NATB. ADX=0. PEERIP1="173.20. DEX=0.9 3 Port of peer MGW 2905 Server/Clie nt Client SAI 4600000 030004 AMR LIST All Local IP 173. For the local office information. LSNAME="ToMGW1". DEX=1. LNKNAME="TO-MGW1". ASF=YES. WM=ASP. STPF=TRUE. ADD M3DE: DEX=1.

OPC="C04". LAICAT=SAI. SPC="D04". //Add the office direction. SSN=RANAP. NI=NATB. =FALSE . LAIGCINAME="RNC4". NI=NATB. ON="RNC4". OFFICNUM="4". DPNAME="RNC4". MGWIDX=1. NI=NAT2. LAI="460000003". ADD SCCPSSN: SSNX=6. MSCN="8613600004". DOA=RNC. LAICAT=LAI. //Query MSC/VLR number ADD OFC: OFFICEDIR=4. ADD SCCPSSN: SSNX=5. SAI="4600000030004". SHAREFLAG=NONE. VLRN="8613600004". NI=NATB. LAIGCINAME="RNC4".Operation Manual . DPC="D04". MLAIF DPC="D04".Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Configuring Data for Interworking with RNC //Add SCCP. SSN=RANAP. ADD RANMGW: OFFICENO=4. DOL=LOW. RNCID1=4. LST MGW:. SSN=SCMG. ADD LAISAI: LOCNO=65535. 5-25 . OPC="C04". ADD LAISAI: SAI="460000003". SSNNAME="RNC4-SCMG". LOCNO=65535. SSNNAME="RNC4-RANAP". SPC="C04". VLRN="8613600004". OFFICNUM="4". NI=NATIONBK. //Query MGW Index. ADD SCCPSSN: SSNX=4. SARL=A-1&B-1&C-1&D-1&E-1&F-1&G-1&H-1&SID-1&RATE0-1. RNCID1=4. LAIT=HVLR. LAIT=HVLR. SPC="D04". OOFFICT=RNC. SIG=MTP3. OPC="C04". global title and service zone of RNC. DPC1="D04". OSP="C04". ADD SCCPDSP: DPX=4. OPC="C04". LST INOFFMSC:. //Add access media gateway. NI=NATB. SSNNAME="LOCAL-RANAP". MSCN="8613600004". ADD RNC: RNCID=4.

2 Related Concepts 6. The semi-permanent connection is created at MGW. 6-1 . See Figure 6-1 for the networking mode. This chapter contains the following sections: Related Concepts Collecting Data for Interworking with BSC Configuring Data for Interworking with BSC Configuration Example 6.2.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC Chapter 6 Configuring Data for Interworking with BSC 6.1 Introduction to the Chapter MSOFTX3000 and MGW are integrated to provide MSC/VLR entity functions.1 Networking Between MSOFTX3000 and BSC This networking mode takes MSOFTX3000 and MGW as an integrated entity.Operation Manual . This chapter describes the data configuration process at MSOFTX3000 for interworking with a BSC after MSOFTX3000 and MGW are integrated. which transparently transmits the A interface messages between BSC and MSOFTX3000 over TDM. and they interwork with Base Station Controller (BSC) through A interface.

The WCSUs are front board and the WEPIs are back boards. the numbers of circuits configured on the WEPI correspond to that of the links configured on the WCSU. The following is an example with WCSU+WEPI configuration. so it cannot be used as a link. You can select different timeslots on the same E1 or timeslots on different E1s to form a link set. 6-2 .The following describes the details with 64-kbit/s link as an example.2. and they are the same in quantity. as shown in Figure 6-2.2 MTP Link Configuration One link set can contain a maximum of 16 links. Besides.Operation Manual . Timeslot 0 of each E1 is the synchronization timeslot.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC MSOFTX3000 TDM bearer Semi-permenant connection TDM bearer MGW BSC BSSAP SCCP MTP TDM Figure 6-1 Networking between MSOFTX3000 and BSC 6.

” 6-3 .Operation Manual . which cannot be used as a link. adopting the 15 timeslot of the E1 as a link and the link number is 16. The lower one processes links 0–15 and the upper one processes links 16–31. That is. enter “Link No.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC E1/TDM 0 ~ 3/0 ~ 127 4 ~ 7/128 ~ 255 Backplane WEPI WEPI Links 16 ~ 31 Upper Links 0 ~ 15 Lower 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. only TDM timeslots 128–255 can be used. However. The WCSUs in pair (active and standby) can process thirty-two 64-kbit/s links or two 2-Mbit/s links. and each WCSU can be configured with a upper CPC and a lower CPC. It is required that the WEPIs corresponding to the WCSUs (1+1 backup) must be in position. so their sub-board CPCs also work in active-standby mode. The WCSUs work in active-standby mode. Timeslot 0 of each E1 is the synchronization timeslot. The configuration information must be consistent with the actual hardware connection. That is. which cannot be used as link. and use the ADD EPICFG command to configure the WEPI slots to which the E1 lines are connected. only TDM timeslots 0–127 can be used. Timeslot 0 of each E1 is the synchronization timeslot. it is only necessary to connect the E1 lines (8 in quantity) to any one of the WEPIs. Links 16–31 correspond to circuits (E1/TDM) 4–7/128–255. The WEPIs in pair (active and standby) can process eight E1s (0–7). that is TDM timeslots 0–255. For example. for links 16–31. though CPCs originally work in load sharing mode. for links 0–15. if MSOFTX3000 is connected to MGW through E1 numbered as 4. The following describes the corresponding relations between circuit numbers and link numbers: Links 0–15 correspond to circuits (E1/TDM) 0–3/0–127.

the TID of MGW and the CIC of BSC can correspond to the same physical circuit. here only the method for MSC9880 interworking with BSC is presented. the start physical circuit from MGW to BSC.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC with “16” and “Start Circuit No” with “143” (4×32+15=143) when you use the ADD N7LNK command. and the circuit number ranges from 3*32=96 to 127. The numbers of TIDs and CICs can be obtained by “End Circuit” minus “Start Circuit”.3 Trunk Circuit and TID Configuration I. Here the value range is 0–31. They should be unique within the office and it is recommended that the values be consistent with those of TIDs. and enter “96” for “Start Circuit Termination ID”. The parameters “Start Circuit” and “End Circuit” are internally used in MSOFTX3000. 6. TID: Termination ID. As the configuration methods for MSC9880 interworking with BSC. Configuration Example In this example. and they correspond to TID and CIC one by one. use the command ADD AIETKC. where 4 means E1 number and 16 indicates the timeslot number used by the link. which must be consistent with that of BSC. there are 32 circuits available from MGW to BSC.2. For example. Enter “0” for “Start CIC”. Configuration Description The following describes the method to configure the circuits adopting MGW semi-permanent connection as shown in Figure 6-3. PSTN and MSOFTX3000 are the same. Because MSOFTX3000 and BSC assign circuits through circuit identification code (CIC). CIC:0~31 M TID: 96~127 MSOF SERV SC TX 3000 ER Physical circuit Physical circuit (E1) :4/16 (E1) :1/16 MGW CIC:0~31 BS BSC C Physical circuit (E1) :9/16 Physical circuit Semi-permanent (E1) :3/16 connection 96~127 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. II. Here.Operation Manual . In MSOFTX3000. the 6-4 . the configuration data is as follows: Physical circuit (E1): 4/16. Here the value range is 96–127. which must be consistent with the number of the physical circuit of MGW to BSC. CIC: Circuit Identification Code. and MSOFTX3000 specifies which circuit MGW uses to establish bearer through termination ID (TID).

Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC start circuit is 96 and the end circuit is 127.Operation Manual . Figure 6-4 illustrates the called number analysis process. ranging from 0 to 31. Called Number Analysis The called number analysis process is as follows: 1) 2) 3) 4) A calling subscriber initiates SETUP message. Calling Number Analysis The calling number analysis process is as follows: 1) 2) 3) 4) A mobile subscriber initiates a call. MSC9880 searches through the LAI table to get the call source code according to the LAI. 6-5 .4 Number Analysis Process Important Note: For the mobile subscribers of the local office. If MSC9880 confirms that the called number is of MSISDN type. If it finds that the called subscriber is in the local office. Because route. it is not necessary to configure them here. the called number analysis process is completed. II. sub-route and route analysis data are used for routing to other offices. and there are 32 CICs. MSC9880 searches through VDB to get the LAI to which the calling subscriber is subject (stored in VDB because location update has been successful). sending CM_SERVICE-REQ (with IMSI) to MSC9880 mobile switching center. it will search for the LAI to which the called subscriber is subject according to the IMSI. MSC9880 searches through the call source table to complete number analysis at calling subscriber side. 6. MSC9880 searches through the trunk group table according to the DPC of the BSC to get the trunk group and trunk circuit. I. Thus. There are 32 TIDs ranging from 96 to 127. 5) 6) 7) MSC9880 sends a paging message to the LAI. The called subscriber returns a paging response message (with the DPC of the home BSC).2. MSC9880 implements called number analysis (searching through the CNACLD table) according to the called MSISDN in the message. MSC9880 gets MSRN and IMSI in the local VLR to perform second number analysis. routing to the local BSC is to find the LAI where a subscriber is resident. it will initiate the process to get MSRN.

2.5 Parameter Relationship Figure 6-5 illustrates the parameter relationships between MSOFTX3000 internal commands.Operation Manual . 6-6 .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center MS Setup [MSISDN] MSC server Number Analysis => MSISDN Chapter 6 Configuring Data for Interworking with BSC HLR VLR BSC-T MAP_SRI_Req [MSISDN] MAP_PRN_Req [IMSI] MAP_PRN_Rsp [MSRN] MAP_SRI_Rsp [MSRN、IMSI] the second Number Analysis => LAI Paging [LAI] Paging Response [DPC、LAIGCII] Figure 6-4 Called number analysis process 6.

2. See Table 6-1 for the procedures and commands for configuring the data at MSOFTX3000 to interwork with BSC. 6-7 .6 General Configuration Procedures As MSOFTX3000 and MGW are integrated. and then configure the data at the MSOFTX3000 side to BSC.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC 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] Signaling network ID BSC OPC Peer end MSC DPC [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] Figure 6-5 Parameter relationships 6. it is necessary to configure the data for interconnecting MSOFTX3000 and MGW. create semi-permanent connections on MGW.Operation Manual .

MGW. you need to collect the data for interworking between MSC9880. Configure A interface trunk circuit 1) Add A interface circuit pool. 2) Add A interface circuit group. as shown in Table 6-2. 3) Add A interface circuit.Operation Manual .3 Collecting Data for Interworking with BSC Before configuring data. and BSC. The other parameters are the internal ones of MSOFTX3000.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC 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 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. The shadowy columns indicate the parameters that must be negotiated between the two ends for consistency or of which one end must notify the other end./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. 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. 6-8 .

) and timeslot No. (E1 No. Add semi-permanent connection with the command ADD SPC.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC Table 6-2 Data for interworking with BSC Item Basic information Signaling point code Signaling point network indicator Data LAI GCI Signaling link WCSU module number Link set Intra-module link number Signaling link code (SLC) Intra-modul e circuit number (E1 number/tim eslot number) Link type Circuit Termination ID (the number of the physical circuit from MGW to BSC) CIC MGW index Trunk route Office direction Trunk group Circuit type Prefix Local prefix Route selection code 6. refer to Chapter 4 of this manual.4. The information of the source TDM and destination TDM to be configured includes frame No. of the ME32 board. slot No. II. port No.1 Negotiating and Preparing Data I. 6-9 .4 Configuring Data for Interworking with BSC 6.. Adding Semi-Permanent Connection at MGW Add interface board with the command ADD TDMIU.. You need not configure the optical port.Operation Manual . Configuring Interworking Data between MSOFTX3000 and MGW For detailed procedures to configure interworking data between MSOFTX3000 and MGW.

[OPC] It is the signaling point code of the local office available in the nation reserved network. which is allocated uniquely in the system.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC 6. interface A cannot be initialized normally.2 Adding MTP Destination Signaling Point I. and it is the local office signaling point code in the corresponding network indicator of local office signaling point index 0. Command ADD N7DSP Important Note: The local office signaling point codes interconnecting BSC must be 14 bits. III. 96 software parameter. Background Information Before configuring MTP DSP for BSC. specify the DPC of BSC here. 0 record in the OFI table is valid. MSOFTX3000 supports local office multi-signaling-point configuration. for 2G network. In SS7 signaling point table. Major Parameters [DSP Index] This parameter is used to define the index of a DSP. not 24 bits. It must be defined in the command SET OFI or ADD OFI first.0 in the OFI table to connect the BSC.Operation Manual . If not. The default option is “National Reserved Network”. configure local MTP OPC first. . only No. The current default setting of software parameters is to use No. [DPC] For BSC. However. only remote signaling points are configured. we can only use SPC No. Currently. That is. Set the network indicator according to the actual networking conditions. The default value is “NATIONAL RESERVED NETWORK”. while local signaling points cannot be configured. 0 of the national standby network to connect the BSC. you need to use the LST OFI command to query whether the local MTP OPC has been configured. otherwise. [STP Flag] 6-10 . II. [NI] Set the parameter according to the actual networking.4. The network ID used between MSOFTX3000 and BSC (national/active/standby) is to be determined by the No.

3 Adding MTP Link Set I. set this field to "NO".4. Use the default values for the other parameters. Command ADD N7LKS 6-11 . MSOFTX3000 will allocate the signaling services among these link sets in load sharing mode.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC This parameter is used to set whether the DSP provides STP function. Background Information None II. Unless otherwise specified. IV. no matter how many MTP link sets exist between the local office and the DSP. [Linkset Select Mask] It indicates how to achieve load sharing of signaling services between multiple MTP link sets to the specified DSP. [DSP Name] For this parameter. set this parameter to "YES". [Adjacent Flag] It is used to indicate whether a DSP is a directly connected SP of the local office. Related Commands See Table 6-3 for the commands related to MTP DSP configuration. Table 6-3 List of commands related to MTP DSP configuration Command ADD N7DSP RMV N7DSP MOD N7DSP LST N7DSP DSP N7DSP To add MTP DSP To remove MTP DSP To modify MTP DSP attributes To list MTP route data in the MTP route data table of BAM To display MTP route state Description 6. Generally. use standard and easily-identified name. If the DSP has STP function. that is. For BSC. for example "BSC-1".Operation Manual . It is a four-bit binary digit. it is recommended to use the default value “B1111”. set it to “TRUE”.

It is recommended to use a standard name with unique characteristics for the sake of identification. MSOFTX3000 will allocate the signaling services among these links in load sharing mode. Here it is the DSP index of the peer BSC It must be defined in the command ADD N7DSP first and then referenced here.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC 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. It is recommended that the name used here be the same as the paraemter “DSP name” defined in the ADD N7DSP command. [Linkset Name] You can set it as needed.Operation Manual . set it the same as the parameter “DSP index” in the ADD N7DSP command. that is. [Adjacent DSP Index] It refers to the index of a DSP to which a link set belongs. for example. Table 6-4 List of commands related to MTP link set configuration Command ADD N7LKS RMV N7LKS MOD N7LKS LST N7LKS To add an MTP link set To remove an existing MTP link set To modify an existing MTP link set To list MTP link set data in the MTP link set data table of BAM Description 6-12 . To keep consistency and maintainability of the data. It is a four-bit binary digit. Major Parameters [LinkSet Index] You can set it as needed. it is recommended to use the default value “B1111”. Related Commands See Table 6-4 for the commands related to MTP link set configuration. Unless otherwise specified. and the index should be unique globally. . III. "BSC1". no matter how many MTP links are in the link set. IV. [Link Select Mask] It indicates how to achieve load sharing of signaling services between multiple MTP links in the specified MTP link set. The DSP index of the MTP link set must be valid in the MTP DSP table.

Generally the default value "0" is used.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC 6. The link set with the highest priority will be selected first. ”1” stands for the second. for example. Background Information None II. . Command ADD N7RT III. [Route Name] It is recommended to use a standard name with unique characteristics for the sake of identification. ”0” stands for the highest priority. IV. and so on. "BSC-1".4 Adding MTP Route I. It is recommended that the name used here be the same as the parameter “DSP name” defined in the ADD N7DSP command. Related Commands See Table 6-5 for the commands related to MTP route configuration.4. while that with lower priority will be selected only after all signaling routes with higher priority are unavailable.Operation Manual . [DSP Index] It is used to identify the DSP of the specified MTP routeHere it is the DSP index of the peer BSC. Table 6-5 List of commands related to MTP route configuration Command ADD N7RT RMV N7RT MOD N7RT LST N7RT DSP N7RT To add an MTP route To remove an existing MTP route To modify an existing MTP route To list MTP route data in the MTP route data table of BAM To display MTP route state Description 6-13 . This parameter must be defined in the command ADD N7LKS and then referenced here. Major Parameters [Linkset Index] It is used to set the link set to which a link belongs. and has been defined in the ADD N7DSP command. [Route Priority] It is used to set the routing priority of an MTP link set (signaling route).

If a 2-Mbit/s MTP link is provided.Operation Manual . Background Information Because MSOFTX3000 can provide MTP links in different ways. This parameter must be defined in the command ADD BRD first and then referenced here. the link number will range from 0 to 31. see Section 6. If MSOFTX3000 provides an MTP link through built-in SG (born over M2UA). If MSOFTX3000 provides MTP links through E1 (born over TDM). and to “16” for the upper CPC sub-board. Set it to “0” for the lower CPC sub-board. II. all MTP links must be numbered uniformly. WSGU or WIFM. If MSOFTX3000 provides MTP links through built-in SG (born over M2UA). The link number ranges from 0 to 31. Major Parameters [Moudle Number] If MSOFTX3000 provides an MTP link through E1 (born over TDM). 6-14 . Command ADD N7LNK III. you need to select different link types according to the actual networking when you set the MTP link data. For detailed information about MTP link configuration. this parameter is used to specify the module number of the WBSG. In the same WBSG. this parameter is used to specify the module number of the WCSU or WSGU processing this MTP protocol. WSGU or WIFM can support a maximum of 32 MTP links.] It specifies the MTP link number in the following two cases: 1) If MSOFTX3000 provides an MTP link through E1 (born over TDM). this parameter is used to specify the logical number of this MTP link in the WBSG. that is. the link number can only be set to 0 or 16. One WCSU or WSGU can be inserted with two CPC sub-boards and each CPC sub-board can process sixteen 64-kbit/s MTP links (due to the restriction of the CPC signaling processing capability) or one 2-Mbit/s MTP link.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC 6. select ”M2UA 64K LINK” or “M2UA 2M LINK”. one WBSG.2 MTP Link Configuration. this parameter is used to specify the physical number of this MTP link in the WCSU or WSGU. 2) If MSOFTX3000 provides an MTP link through built-in SG (born over M2UA).4. set this parameter as follows: If 64-kbit/s MTP links are provided. select ”TDM 64K LINK” or “TDM 2M LINK”. 0–15 are allocated for the lower CPC sub-board and 16–31 are for the upper CPC sub-board. WSGU or WIFM.5 Adding MTP Link I. [Link No.2. WSGU. or WIFM processing this MTP protocol. Therefore.

for example). that is. 65 or 97. It must be defined in the command ADD N7LKS first and then referenced here. It is provided by bulilt-in SG (UMG8900. TDM 2M link: 2-Mbit/s MTP links 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. 64. For a 2-Mbit/s MTP link. [Linkset Index] It is used to set the link set to which a link belongs. 193 or 225. 160. the start circuit number can only be 129. M2UA 64K link: 64-kbit/s MTP links born over M2UA. It is provided by MSOFTX3000 directly. timeslots 0. the start circuit number can only be 1. 32. It is valid only when the MTP link is born over TDM. The meaning of the options are as follows: TDM 64K link: 64-kbit/s MTP links born over TDM. One pair of active and standby WEPIs can provide eight active E1 ports.] It specifies the number of the E1 timeslot seized by an MTP link. and the WCSU and WEPI have one-to-one corresponding relationship in slot position. for example). For the BSC. The timeslots are numbered from timeslot 0 of the first E1 in ascending order. [Time Slot Number] 6-15 . You must set it correctly based on the actual networking. It is provided by bulilt-in SG (UMG8900. the MTP link will not function well. the start circuit number will range from 1 to 127. 192. If the link number ranges from 16 to 31. [Start Circuit No. For 64-kbit/s MTP links.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC [Link Type] It specifies the type of an MTP link. the E1 timeslot seized by this MTP link can only be provided by the WEPI (back board) in the same slot as the WCSU. if the link number ranges from 0 to 15. MTP links cannot seize timeslot 0 of each E1 (synchronization timeslot). for example "BSC-1". If the link number is 16. M2UA 2M link: 2-Mbit/s MTP links born over M2UA. 96. among the above timeslots. 33. otherwise. if the link number is 0. 161. It is provided by MSOFTX3000 directly. 128. [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. ranging from 0 to 255. and 224 are unavailable. a 64-kbit/s MTP link is provided.Operation Manual . the start circuit number will range from 129 to 255.

By default. Otherwise. This parameter should be consistent with that of the peer end. it is 80. 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”. At this time. [Link Congestion End] It is expressed in percentage. It must be consistent with the setting at the peer end. You need to set it according to the actual situation. while that with lower priority will be selected only after all signaling links with higher priority are unavailable. When the signaling load on an MTP link reaches the preset threshold. Generally. At this time. specifying the logical number of an MTP link in its MTP link set. [Signaling Link Code Send] It is used for self-loop test on two MTP links in the local office. signaling interconnection will fail. its default must be consistent with the signaling link code. it is 31. congestion control will be started. [Link Priority] It is used to set the routing priority of an MTP link. it is 70. [Satellite Flag] It identifies whether an MTP link is born over the satellite circuit. When this parameter is not configured. The link with the highest priority will be selected first. signaling link code (SLC) is a four-bit field ranging from 0 to 15. [Handle Module Number] 6-16 . and the SLC of each signaling link in one link set must be numbered uniquely in sequence. and so on. As described in the MTP protocol. When the self-loop test on the MTP links is started. When the signaling load on an MTP link is lower than the preset threshold. [Link Congestion Begin] It is expressed in percentage. you must set this parameter and SLC to the same value. By default. ”0” stands for the highest priority. this MTP link can be used for transmission again. congestion control will be stopped. [Signalling Link Code] It is a parameter for MSOFTX3000 to interconnect with the peer end. By default. set it to “No". 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. this MTP link cannot be used for transmission until the congestion is unblocked. Set it by the following principle: When the self-loop test on the MTP links is not started.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC It defines the number of the seized timeslots. [Test Code] and [Test Code Length] These two parameters are used for test on MTP links.Operation Manual . ”1” stands for the second.

WSGU or WIFM to the corresponding module for processing automatically based on the load sharing principle. OPC and DPC. It is required that the OPC and DPC must be consistent with those of the lower layer (MTP3/MTP3B/M3UA) when SCCP DSP is configured. the subscriber messages above the MTP layer will be processed by the WCSU or WCCU. As MTP3 signaling bearer mode is adopted between local office and BSC. the DPC of the BSC must be first configured in the MTP3 DSP table. Table 6-6 List of commands related to MTP signaling link configuration Command ADD N7LNK RMV N7LNK MOD N7LNK LST N7LNK DSP N7LNK DSP N7DLNK INH N7LNK UIN N7LNK ACT N7LNK DEA N7LNK To add an N7 signaling link To remove an existing N7 signaling link To modify an exiting N7 signaling link To list the information of all configured N7 signaling links To display N7 link state To display N7 link state of DSP To inhibit an N7 signaling link to block the management of the N7 link To enable an N7 signaling link to unblock the management of the N7 link To activate an N7 signaling link To deactivate an N7 signaling link Description 6.6 Adding SCCP Remote Signaling Point I. you need not set it at all and the MSOFTX3000 will dispatch them automatically. Generally. the subscriber messages above the MTP layer will be dispatched by the WBSG. the subscriber messages above the MTP layer will be processed by this module. IV. when MTP links are configured on the WBSG. Use default values for the other parameters. Use the LST N7DSP 6-17 . If you specify a handle module number.4.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC It defines the module for processing signaling messages above the MTP layer. One SCCP DSP record is uniquely identified by NI. WSGU or WIFM. Otherwise. Background Information This command is used to configure the signaling point information for the peer BSC.Operation Manual . when MTP links are configured on the WCSU or WSGU. Related Commands See Table 6-6 for the commands related to MTP signaling link configuration.

ranging from 0 to 511. [OPC] It refers to the originating point code of the local office in the same network indicator. It must be defined in ADD N7DSP or ADD M3DE first and then referenced here.Operation Manual . II. the DPC is the national reserved 14-bit SPC. For BSC. For BSC. and there is no reference relation among them. IV. It must be noted that the “DSP Index” defined here is different from the “DSP Index” defined in ADD N7DSP and “Destination Entity Index” defined in ADD M3DE. [Load Sharing Function Flag] It is used to set whether MSOFTX3000 supports the load sharing function or backup function of SCCP DSP. it is the national reserved network signaling point code of No. Major Parameters [DPC Index] It uniquely identifies an SCCP DSP. It is used to specify the standby DSP of SCCP. Related Commands See Table 6-7 for the commands related to SCCP DSP configuration. Use the DPC of the peer BSC. [NI] It identifies the signaling network where the SCCP DSP is resident. [DPC] It refers to destination signaling point code. 0 record in the OFI table. 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. 6-18 .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC command to check whether the BSC DPC is consistent with that in the MTP3 DSP table. You can query it with the LST OFI command. It must be specified in the command SET OFI first and then referenced here. Command ADD SCCPDSP III.

II. [SSN] This parameter refers to subsystem number. Subsystem number (SSN) is the local addressing information used by SCCP to identify the SCCP users under a SP. If they have been configured.7 Adding SCCP Subsystem I. they need not to be configured here. SSN of the MSOFTX3000 at the local end is base station subsystem application part (BSSAP)/intelligent network application protocol (INAP). Be sure to use the LST SCCPSSN command to have a check for avoiding repeated configuration.Operation Manual . [SPC] 6-19 . and SCMG must be configured. The local MSC. The configured SSN at the BSC side includes SCCP Management Subsystem (SCMG) and BSSAP/INAP. you need to add SCMG and BSCAP/INAP subsystems. Background Information The following command ADD SCCPSSN is used to add SCCP subsystems in MSOFTX3000 (local end) and the BSC (remote end).4. VLR. Command ADD SCCPSSN III.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC 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 6. and it is unique in the system. For both MSOFTX3000 and BSC. Major Parameters [SSN] It is used to identify the SCCP subsystem. [NI] It is used to set the indicator of the network where the SCCP subsystem is located.

[Backup SSN index] It is used to specify the index of the backup subsystem of a specified subsystem.8 Adding Office Direction to BSC I. It must be defined in the command SET OFI first and then referenced here. use the default option “UNDEFINED”. You can define a maximum of five indexes. the sender of SCCP messages. you need to set BSC SPC and OPC here. For configuring local and remote SCCP subsystems. If there is no subsystem. the default value is used. IV. [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. the recipient of SCCP messages. Generally.4. [OPC] It is used to specify the originating SPC of the corresponding subsystem. To display SCCP subsystems in the host Description 6. This command is used during maintenance. use the default value “65535”.Operation Manual . Background Information II. Table 6-8 List of commands related to SCCP subsystem configuration Command ADD SCCPSSN RMV SCCPSSN MOD SCCPSSN LST SCCPSSN SET SCCPSSN DSP SCCPSSN To add an SCCP subsystem To remove an existing SCCP subsystem To modify an existing SCCP subsystem To list SCCP subsystems To set SCCP subsystem status. Related Commands See Table 6-8 for the commands related to SCCP subsystem configuration. that is.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC It is used to specify the destination SPC of the corresponding subsystem. Command ADD OFC 6-20 . It is valid only when MSOFTX3000 supports the load sharing function or backup function of SCCP DSP. For each subsystem. that is. this OPC is a local SPC. If there is no related subsystem.

For this parameter. High (upstream office). enter the DPCs of BSC. Here select "LOW (INFERIOR)". BSC4. [Destination Point Code1]–[Destination Point Code16] For these parameters. [Peer Office Attribute] It specifies the equipment type used by the peer office. IV. and they are associated with the DPCs of BSC in the ADD SCCPDSP command. for example. Major Parameters [Office Direction] It is allocated uniquely in the system and used to identify an office direction. [Office Direction Name] It is recommended to use a standard name for the sake of identification. III. Set it according to the actual situation. For the other parameters. Table 6-9 List of commands related to office direction configuration Command ADD OFC RMV OFC MOD OFC LST OFC To add a new office direction To remove an existing office direction To modify attributes of an existing office direction To list attributes of a configured office direction Function 6-21 . They must be negotiated with BSC for consistency. [Peer Office Level] It specifies the level of the peer office. select "BSC (BSC)" here.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC Note: This command is used to set the office direction from MSOFTX3000 to BSC. use the default values. The level of BSC is lower than MSOFTX3000 in the network.Operation Manual . Related Commands See Table 6-9 for the commands related to office direction configuration. [Network ID] The network ID of the MSOFTX3000 must be consistent with that of the peer end. or Low (downstream office). [Opposition Office Type] Select “BSC (BSC)" here. Same (office of the same level).

enter the BSC DSP code.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC 6. Note that we do not mean to specify the processing module of the BSC. If [Location Area Not Unique Flag] is set to “FALSE (ONLY ONE)”.Operation Manual . you must set this parameter. Related Commands See Table 6-10 for the commands related to BSC configuration. For this parameter. [Home Module Number1]–[Home Module Number10] It refers to the module number of the WCCU or WCSU controlling BSC. but to define the maintenance module of the BSC. [Destination Point Code] It refers to DPC. Background Information None II.4. This parameter has been defined in the ADD RTANA command. Major Parameters [Network ID] The network ID of the MSOFTX3000 must be consistent with that of the peer end. Table 6-10 List of commands related to BSC configuration Command ADD BSC RMV BSC MOD BSC LST BSC To add a BSC To remove an existing BSC To modify the attributes of an existing BSC To list BSC information configured Description 6-22 .9 Adding BSC Global Indicator I. [Route Select Source Code] The route selection source code is the category No. of outgoing route selection strategy of different call sources. Command ADD BSC III. IV. [Location Area ID] It specifies the unique LAI to which BSC belongs.

To guarantee handover of mobile stations between MSCs. If adding a location area. [MSC Number of the LAI or Cell] It refers to the number of the MSC to which a location area or cell belongs. [LA Type] This parameter is used to decide whether the current LAI/CGI belongs to the local VLR or adjacent VLR. These IDs are given during network planning. and defined in the ADD INOFFMSC command. Generally.Operation Manual . III. and defined in the ADD INOFFMSC command. This number is provided by the operator. [VLR Number of the LAI or Cell] It refers to the number of the VLR to which a location area or cell belongs. and the "LA Category" of this command is used distinguish location area and cell. Whether a location area or a cell is to be configured is determined by the parameter “LA Category”.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC 6. If adding a cell. Major Parameters [Global Cell ID] It refers to location area ID or cell ID. Command ADD LAIGCI Note: This command is used to configured location area and cell. [LA Category] When the current record is a location area. MSC and VLR are set together.4. if the current record is a cell. [Perform Roaming Analysis] Roaming analysis is performed toward a specific LAI. This number is provided by the operator. set a 13-bit GCI. Backgrond Information None II. set this parameter to "LAI". Set this parameter to YES if roaming restriction is needed for an LAI. the information on the cell of the adjacent MSC bordering on the local MSC should be recorded. set a 9-bit LAI. The LAI/CGI of the local MSC/VLR is 6-23 .10 Adding LAI or CGI I. set this parameter to "GCI".

When adding a cell. The following parameters are available only when the parameter "LA Type" is set to "Local VLR". If a location area only corresponds to one BSC. [Location No. set this parameter to the network indicator of the BSC to which the cell belongs. use the default values. For called subscribers.Operation Manual . set this parameter to the DPC of the BSC corresponding to the location area. [Office No. enter the DPCs of all BSCs for this parameter. This parameter is defined in the ADD OFC command. For the other parameters. [Call Source Code] If refers to the call source code used when the current location area/cell initiates a call. early assignment means that an assignment request is initiated right after the network receives the CALL PROCEEDING message from the calling party. IV.] It is the indicator corresponding to a location area. For calling subscribers. If a location area only corresponds to one BSC. early assignment means that an assignment request is initiated right after the network receives the CALLCONFIRMED message from the called party. [Home BSC Network Indicator 1]–[Home BSC Network Indicator 10] If a location area contains multiple BSCs. [Home BSC DPC 1]–[Home BSC DPC 10] If a location area contains multiple BSCs.] Set it to the number of the office direction corresponding to BSC. This parameter is defined in the ADD CALLSRC command. while late assignment means that an assignment request is initiated after the network receives the CONNECT message from the called party. [Early Assignment Flag] This parameter is used to indicate the circuit assignment time. and it is used to enhance roaming restriction. Related Commands See Table 6-11 for the commands related to LAI/CGI configuration. enter the network indicators of all BSCs for this parameter. set this parameter to the network indicator 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.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC marked "Local VLR" and the location area/cell of non-local MSC/VLR is marked as "Adjacent VLR". 6-24 . while late assignment means that an assignment request is initiated after the network sends ALERTING message to the calling party.

Background Information None II.4. Table 6-12 List of commands related to the configuration of access media gateway Command ADD RANMGW RMV RANMGW LST RANMGW Function To add a new connection between RAN entity and MGW To remove an existing connection between RAN entity and MGW To list connections between RAN entity and MGW 6-25 .Operation Manual . Command ADD RANMGW Note: This command is used to create the connection between the BSC office direction and MGW.11 Adding Access Media Gateway I.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC 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 6. Related Commands See Table 6-12 for the commands related to the configuration of access media gateway. III. IV. It is defined in the ADD OFC command. [Media Gateway Index] It is defined in the ADD MGW command. Major Parameters [Office Number] It is used to identify an office direction of an entity that a specific MGW is connected to.

In this way. Related Commands See Table 6-13 for the commands related to the configuration of A-interface circuit pool. Table 6-13 List of commands related to the configuration of A-interface circuit pool Command ADD ACPOOL MOD ACPOOL RMV ACPOOL LST ACPOOL Description To add an A-interface circuit pool To modify an A-interface circuit pool To remove an A-interface circuit pool To list A-interface circuit pools 6. IV. Command ADD ACPOOL Important Note: This command is used to set the bearer capability of A-interface circuit. II.Operation Manual . when you add A-interface circuit group by designating the circuit group into different circuit pools. [GSM Bearer Capability] For this parameter. use the default option "Select All".12 Adding A-interface Circuit Pool I. you can configure the A interface circuits in different office directions with different bearer capabilities.4. Background Information None.13 Adding A-interface Trunk Group I. Background Information None. III.4. Major Parameters [Circuit Pool No.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC 6. You can configure multiple A-interface circuit pools with different bearer capabilities. 6-26 .] The parameter refers to the orderly number of an A interface circuit pool.

Generally. Command ADD AIETG III. [OPC] For this parameter. enter the national reserved network SPC of the local office.] It refers to the circuit pool number of A interface in the local office. set it to "All allowed" because the calling-out authorities are controlled at the subscriber end. IV. [DPC] For this parameter. You can specify this parameter as needed. The MGW has been defined in the ADD MGW command. [Call-in Authority] This parameter is used to control the authorities of the calling-in trunk circuits. This parameter is the same as that set in the ADD N7DSP command. enter the DPC of the peer end. and the value is defined in the ADD ACPOOL command. [MGW Index] The parameter indicates the index number of an MGW to which a trunk group belongs. [Circuit Pool No. Related Commands See Table 6-14 for the commands related to the configuration of A-interface trunk group. Only those allowed types of calls can get through. or select all default values. Major Parameters [Trunk Group] The parameter refers to the number of an A interface trunk group. Table 6-14 List of commands related to the configuration of A-interface trunk group Command ADD AIETG MOD AIETG LST AIETG Description To add an A-interface trunk group To modify an A-interface trunk group To list A-interface trunk group information 6-27 . It is associated with this parameter in the SET OFI command. You can specify this parameter as needed. [Call-out Authority] This parameter is used to control the authorities of the calling-out trunk circuits.Operation Manual .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC II. Only those allowed types of calls can get through.

It must be unique within the office and it is recommended that the value be consistent with that of TID. Command ADD/MOD AIETKC III. [Start Circuit Termination ID] 6-28 . “Trunk Circuit and II. Background Information When adding a trunk circuit. This parameter is defined in the ADD AIETG command.4. You can query this parameter with the LST MDU command. Major Parameters [Module] It refers to the module number of the WCCU or WCSU to which the A interface trunk circuit belongs. and corresponds to TID and CIC. “Start Circuit”. [Start Circuit] It is used internally in MSOFTX3000. It must correspond to the Start CIC at the BSC side. It must be unique within the office and it is recommended that the value be consistent with that of TID. [Start CIC] This parameter refers to the unique indicator of an A interface circuit. For detailed information about relationships between “Start CIC”. [Trunk Group] It refers to the number of the A interface trunk group to which a trunk circuit belongs.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC Command RMV TG Description To remove a trunk circuit group (including A-interface trunk group) 6.Operation Manual . and corresponds to TID and CIC. Use the default value “Available”. see section 6. “Start Circuit Termination ID”. note that the trunk group to which the trunk circuit belongs should have existed. and “End Circuit”.14 Adding A-interface Trunk Circuit I. [Circuit State] This parameter defines the state of a circuit or a batch of circuits added. [End Circuit] It is used internally in MSOFTX3000.3 TID Configuration” in this chapter.2.

Operation Manual . Related Commands See Table 6-15 for the commands related to the configuration of A-interface trunk circuit. IV. Select “Unavailable” for the parameter “Circuit State”. so as to get the start termination ID of the E1 connecting with BSC. It is an important parameter to identify a physical circuit. This parameter needs to be configured in MGW to make Termination ID correspond to E1 timeslot one to one. 6-29 . and is used to indicate through which E1 the MGW is connected to BSC.” in the ADD N7LNK command) for the parameters “Start Circuit” and “End Circuit”.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC This parameter refers to the ID of a termination corresponding to the start circuit. Select timeslot 0 of the E1 and the timeslot configured as a link (associated with “Start Circuit No. use the MOD AIETKC command to set timeslot 0 (synchronization timeslot) of the E1 and set the timeslot configured as a link to “Unavailable”. Table 6-15 List of commands related to the configuration of A-interface trunk circuit Command ADD AIETKC MOD AIETKC DSP AIETKC RMV TKC BLK AIETKC UBL AIETKC RST AIETKC Description To add an A-interface trunk circuit To modify an A interface trunk circuit To display the status of A-interface trunk circuits of the host To remove a trunk circuit (including A-interface trunk circuit) To block an A interface trunk circuit To unblock an A interface trunk circuit To reset an A interface trunk circuit Important Note: After adding a circuit.

For the local office information. 6-30 .RANAP /IP ISUP. SCP SMC HLR GMLC MAP/TDM MAP/TDM MAP/TDM MAP/TDM MSC Server ISUP/TDM MSOFTX 3000 BSSAP+/TDM SGSN H.BSSAP / TDM SPC 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.1 Example Description Suppose the networking model is as shown in Figure 6-6. The semi-permanent connection is created on MGW. which transparently transmits A-interface messages between BSC and MSOFTX3000.5. Table 6-16 shows the related information.5 Configuration Example 6. TDM bearer is adopted between MSOFTX3000 and MGW as well as between MGW and BSC. refer to Table 3-14 in Chapter 3. MSOFTX3000 and MGW are integrated.248.Operation Manual . This example adds a BSC.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC 6. which is connected to MGW.

LSX=3. //Query the OPC whose NI=NATB LST SCCPSSN: NI=NATB. RTNAME="BSC-3". DPNAME="BSC-3". //Query the type of the signaling link configured on WCSU //Add MTP data.Operation Manual . ADD N7DSP: DPX=3. TS=112. LNKTYPE=0. SLC=0. LST OFI:. LNKNAME="BSC3-1".5. SPC="C04". DPC="C03". OPC="C04". LNKN=3. DPX=3. //Add SCCP data. //Query whether the local end has been configured with SCMG subsystem LST BRD: BT=WCSU. ADD N7LKS: LSX=3.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Configuring Data for Interworking with BSC 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 Signaling link code (SLC) 0 MGW index 460 00 0001 0001 Intra-module circuit number (E1 number/time slot number) 112 (3/16) WCSU module number 22 Link set Intra-module link number Link type / Circuit 3 3 CIC 64 kbit/s Termination ID (the number of the physical circuit from MGW to BSC) 96–127 Office direction 3 / Trunk route 0–31 Trunk group 3 Route selection code 65535 1 Circuit type BSSAP Prefix Local prefix / 1390752 6. ASPX=3. ADD N7LNK: MN=22. LSNAME="BSC-3". NI=NATB. 6-31 .2 Configuration Description //Query the information. ADD N7RT: LSX=3.

SCIC=0. SPC="C03". ADD SCCPSSN: SSNX=8. ADD SCCPSSN: SSNX=7. SC=112. LAI="460000001". CS=UNU. NI=NATB. OOFFICT=BSC. OPC="C04". MSCN="8613600004". CPN=0. LAIGCINAME="BSC3-GCI". LAICAT=GCI. EC=112.Operation Manual . LAIGCINAME="BSC3-LAI". DOA=BSC. EC=96. BSCDPC1="C03". MOD AIETKC: MN=22. NI=NAT2. OPC="C04". OFFICNUM="3". SCF=TRUE. BCR=SFR1-1&SFR2-1&SFR3-1&SHR1-1&SHR2-1&SHR3-1&DFR-1&DHR-1. DPNAME="BSC-3". MSCMN1=22. SDPC="C03". SSN=BSSAP/INAP. ADD SCCPSSN: SSNX=9. SPC="C03". MSCN="8613600004". ADD AIETKC: MN=22. VLRN="8613600004". BTSNUM=1. SIG=MTP3. RSSC=0. SSNNAME="LOCAL-SCMG". TG=3. SSNNAME="BSC-SCMG". LST INOFFMSC:. SOPC="C04". ADD BSC: DPC="C03". SHAREFLAG=NONE. SC=96. ADD RANMGW: OFFICENO=3. EC=127. BSCNM="BSC-3". SSN=BSSAP/INAP. CS=UNU. VLRN="8613600004". BSCDPC1="C03". ADD ACPOOL: CPNO=0. SSNNAME="BSC-BSSAP". DOL=LOW. SSN=SCMG. NI=NATB.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center ADD SCCPDSP: DPX=3. MGW=1. MGWIDX=1. LAICAT=LAI. ADD LAIGCI: GCI="460000001". LAIT=HVLR. MLAIF=FALSE. SPC="C04".OFFICNUM="3". ADD LAIGCI: GCI="4600000010001". //Add BSSAP data. LAIT=HVLR. //Query MSC/VLR number LST MGW:. Chapter 6 Configuring Data for Interworking with BSC DPC="C03". OPC="C04". OPC="C04". TGN="BSC-3". NI=NATB. DPC1="C03". //Add trunk data. SC=96. MOD AIETKC: MN=22. NI=NATB. ADD AIETG: TG=3. 6-32 . ON="BSC-3". TID=96. //Query MGW index ADD OFC: OFFICEDIR=3.

2 Related Concepts 7. Originating Signaling Point In the system. that is. To define an OSP. so the structure of an HLR ISDN number can be CC+MAC+H0H1H2H3+0000. in the same signaling network. The structure of an MSISDN number is CC+MAC+H0H1H2H3+ABCD. a local signaling point is also called an OSP. enhanced authentication. there can be multiple SPs at the 7-1 .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 7 Configuring Data for Interworking with HLR Chapter 7 Configuring Data for Interworking with HLR 7.Operation Manual . Each HLR has an integrated service digital network (ISDN) number used to identify the HLR during signaling exchange.1 HLR I. and one MSOFTX3000 can define up to 16 OPCs instead of 1 in general cases.2. This chapter contains the following sections: Related Concepts Collecting Data for Interworking with HLR Configuring Data for Interworking with HLR Configuration Example 7. MSC Server interworks with HLR through the C/D interface and applies Mobile Application Part (MAP) protocol. II. Overview of HLR HLR is used to store subscription information and provide service support. After the introduction of the multi-SP function.1 Introduction to the Chapter This chapter describes the data configuration process at MSOFTX3000 for interworking with a Home Location Register (HLR). This number can be used to identify an HLR worldwide. and management of subscription information (including adding/deleting/modifying subscribers). the following data shall be confirmed: SPC ID of the network where the SP is located Whether to provide SCCP layer function Whether the STP function is available MSOFTX3000 is designed with the multi-SP function.

that is. For example. In this way. Other entities connected with MSC. 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. RNC and BSC adopt National Reserved Network Code. all adopt National Network Code. DPC2 STP DPC1 Signaling link · Local office No signaling link but signaling relation Figure 7-1 DSP configuration To add a DSP. 24-digit SPC.Operation Manual . if GT is used. the protocol restriction that only 16 signaling links can exist between two network nodes becomes invalid. it shall not. 14-digit SPC in China. PSTN and other MSCs. 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. III. that is. you must define the signaling link set. whether to configure it is determined by the addressing mode of the operator. that is. HLR.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 7 Configuring Data for Interworking with HLR local office corresponding to the same DSP. In this case. as it has no direct signaling link to the local office. Destination Signaling Point The DSPs and network structure to be set for the local office are determined by the operation department. such as. 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. such as DPC1 and STP as shown in Figure 7-1. must be configured. Those SPs connected with the local office through 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. it shall be configured. 7-2 . an associated signaling link exists between this DSP and the local office). If this SP employs DPC for addressing. For DPC2 in Figure 7-1.

Operation Manual . One signaling route only corresponds to one link set. Signaling Route The signaling route to one DSP can be classified as direct route and alternative route. The basic unit composing the signaling link set is the signaling link. V. In other words. it can be concluded that there is one and only one signaling link set between two adjacent DSPs. One signaling link set can contain one or multiple signaling links. 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. The link set corresponding to the alternative route is the one between the OSP and the STP. while one link set can correspond to multiple signaling routes.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 7 Configuring Data for Interworking with HLR IV. as shown in Figure 7-2: Signaling link set Signaling point 1 Signaling point 2 Figure 7-2 Signaling link set Note: From the above definitions. To define a signaling 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. the signaling route determines which link set is applied for transmitting signaling messages to the DSP. 7-3 . The link set corresponding to the direct route is the one between the OSP and the DSP. Signaling Link Set All parallel signaling links between two adjacent SPs form a signaling link set.

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. MTP Load Sharing Load sharing comprises two types: 7-4 . The sent signaling link code (SSLC) is the code sent to the remote signaling entity for identifying the signaling link. Moreover. The SLC of the link at the self-looped E1 should be equal to the SSLC at the other end. timeslot 16 is generally specified as the signaling data link. which can perform load sharing as well.Operation Manual . Signaling Link The signaling link is composed of the signaling data link and the signaling terminal. SLC is different from SSLC during self-loop test of the signaling link. Any timeslot in the pulse code modulation (PCM) system can be specified as the signaling data link. There can be at most 16 routes with the same priority level. The signaling terminal is responsible for the MTP layer 2 processing of the data in a specified signaling data link. In the PCM primary group. while the SLC at the other end should be equal to the SSLC at the local end. The smaller the value is. VII. Normally. there are two routes from SP A to SP C. The signaling data link is a kind of physical medium for signaling transmission. except for timeslot 0. the higher the priority will be. Link set 2 B A Link set 3 Link set 1 C Figure 7-3 Direct route and alternative route VI.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 7 Configuring Data for Interworking with HLR If both the direct route and alternative route exist for a DSP. while alternative route A-B-C corresponds to link set 2. including a direct route A-C and an alternative route A-B-C. the remote signaling entity link connected with the local end should also be configured with the same SLC and SSLC. Direct route A-C corresponds to link set 1. The SLCs in the same link set will be numbered uniformly no matter whether they are in the same WCSU. SLC and SSLC should be configured with the same value. As shown in Figure 7-3. MTP identifies different links in a link set using the signaling link code (SLC).

There are two signaling links between SP A and SP B. To achieve the above two signaling sharing modes. while in the SCCP message. For example. 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. as shown in Figure 7-5. MSOFTX3000 utilizes signaling link set selection mask and SLS mask to evenly distribute signaling messages according to SLS. it is the lower four bits of the CIC. Since SLS changes circularly. 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. as shown in Figure 7-4. VIII. In the telephone user part (TUP)/ISDN user part (ISUP) message. Besides. it can be ensured that the load of links or between link sets is equal if the load is shared according to SLS. There are two sources for the SLS code. SCCP DSP The SCCP DSP to be defined at the local office must first have SCCP signaling relation with the local office. its corresponding data must have been defined at the MTP layer.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 7 Configuring Data for Interworking with HLR Load sharing among links in one link set Load sharing among links in different link sets In the first type. the SCCP DSPs to be defined include SCCP SPs that 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. SLS=XXX0 A SLS=XXX1 B Figure 7-4 Load sharing within one link set In the second type. the load in one link set is shared among the links within the link set according to the signaling link selection (SLS) code. Generally speaking. it is allocated by SCCP circularly. the signaling services are shared among links in different link sets. in Figure 7-5.Operation Manual .

When one of the two SPs is faulty. if this SP is "Available". Active-standby mode indicates that the remote SP has standby SP. C and D. Therefore. GT translation shall be performed for C. SCCP DSP Working Mode SCCP remote SPs can work in three modes: independent mode. If the addressing mode from the local office to D is DPC+SSN. and C is the SCCP STP. One remote SP can correspond to multiple virtual OSPs in the local office. Independent mode indicates that there is no standby SP for the remote SP. you must set the following data: SPC Local SPC Load sharing SP index IX. and load sharing mode. the SCCP DSPs to be configured for the local office are B and C. the messages will be sent to its standby SP. SCCP selects one virtual SP of the local office corresponding to the remote SP in cyclic mode. Load sharing mode indicates that the remote SP is configured with standby SP. SCCP STPs (SPs supporting the SCCP transfer function). When processing the messages sent to the remote SP. and when SCCP routes the messages. C A D B Figure 7-6 SCCP DSP As shown in Figure 7-6. if both SPs are "Available". 7-6 . the SCCP DSPs to be configured for the local office are B. Usually the two STPs that transfer the SCCP signaling messages are set as SPs in load sharing mode. Suppose the addressing mode from the local MSC to D is DPC+GT. A is the local office. which will be used as the OPC in the MTP message.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 7 Configuring Data for Interworking with HLR have direct signaling routes to the local office. the messages will be sent to both of them in turn. If only one SP is available. B and D are the SPs that have the SCCP signaling relation with the local office. The messages that SCCP sends to the remote SP will be sent to two remote load-sharing SPs in polling mode. and when SCCP routes messages. To define the SCCP DSP. otherwise. th messages will be sent to the available one. active-standby mode. the messages will be sent to it. and the DSPs addressing in DPC + SSN mode. the signaling messages will be completely processed by the other.Operation Manual .

XI. For the remote SCCP users that need the local SCCP management. In the entire network. the subsystems must be allocated according to users. 7-7 . Since MTP cannot route messages according to the GT. Besides. each subsystem number is unique. a subsystem number must be specified for each SCCP subsystem (SCCP user).Operation Manual . the office direction that has trunk circuits connected with MSC adopts this mode to create a direct signaling connection with MSC. the relevant subsystem must be established. See Figure 7-7 for the associated mode of signaling. 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.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 7 Configuring Data for Interworking with HLR X. It is used to identify multiple SCCP subscribers in a network node. For different network nodes. The subsystem number is used as the address of the subsystem inside the signaling network. XII. such as international and national phone numbers. If the network node serves not only as an STP. Besides. this mode also applies to the signaling connections between MSC and such functional entities as local HLR and STP. To define a subsystem. Global Title GT is generally composed of numbers. Associated Mode of Signaling The associated mode of signaling refers to transmitting messages between two SPs interconnected by a signaling link. SCCP has to translate the called GT to DPC or DPC+SSN or DPC+GT before transferring it to MTP. It is used mostly in the case when the originating node does not know the network address of the destination node. OPC:=SPB DPC:=SPA SPA OPC:=SPA DPC:=SPB SPB Figure 7-7 Associated mode of signaling In the associated mode. SCCP Subsystem The subsystem number (SSN) is the local addressing information used by SCCP. it is necessary to notify the next SP of the coding scheme that GT adopts.

STP P ST := SPA C = OP PC: D O DP PC: C : =S =S TP PB 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. XIV. MTP will transfer the signaling message according to the DPC without changing the OPC and DPC in the message. the quasi-associated mode will be used. the messages shall be transferred after the STP performs GT over the signaling messages instead of a quasi-associated connection. See Figure 7-8 for the quasi-associated mode of signaling. it sends the message to its own SCCP.Operation Manual . Quasi-Associated Mode of Signaling The quasi-associated mode of signaling refers to transmitting messages between two SPs through a signaling link on which multiple transfer points are preset.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 7 Configuring Data for Interworking with HLR XIII. When DPC addressing mode is employed to transmit MAP and CAP messages between two SPs and there are no associated links. if MTP of STP finds out the DPC in the message is a remote DPC. 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. as shown in Figure 7-9. 7-8 . GT Addressing for Communication among SPs When GT addressing mode is employed to transmit MAP and CAMEL application part (CAP) messages between two SPs. STP B SP := SPA C = OP PC: D O DP PC: C : =S =S PA PB 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. the DPC and OPC of the message will be changed.

calling. When DPC is used for addressing. SPA SubSystem STP SubSystem SPB SubSystem SCCP SCCP SCCP MTP DPC+GT MTP DPC+SSN MTP Figure 7-10 DPC+GT addressing mode Note: The operators determine whether to transmit MAP and CAP messages between two SPs in GT addressing mode or DPC addressing mode. SCCP distributes the message to the MTP layer. The functional entities that need to transmit MAP messages with VMSCs include the adjacent VMSC. When GT addressing is used. Some may want to transmit messages in DPC addressing mode among SPs within a province.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 7 Configuring Data for Interworking with HLR 3) 4) 5) SCCP performs GT translation to obtain DPC+SSN. HLR. If MSC processes intelligent network (IN) services. MTP sends the message to SP B according to the DPC. GT addressing mode is used for message transmission. and signaling stream direction after handover between offices. while for those transferred through direct links. 7-9 . Therefore. some operators may want to transmit messages in GT addressing no matter the SPs are within or outside a province. in which DPC and SSN are both of SPB. HLR is a functional entity that needs to transmit MAP messages with GMSCs. The principles for configuring GT data are as follows: For signaling messages transferred through STP.Operation Manual . the load of STP is heavy but much less data is configured. The signaling messages between the local office and other MSCs/HLRs in a province or those in other provinces are transferred by STP through DPC+GT addressing mode. set the corresponding “Translation Result Type” to "DPC". local SGSN. CAP messages are transmitted between MSC and SCP. set the corresponding “Translation Result Type” to "DPC + GT".2 Principles for Configuring GT Data GT data is applied in handset location update. 7. However. while for the SPs located outside the province. Figure 7-10 illustrates the whole process. the load of STP is relatively light while much more data is configured for STP. you need not set MTP route data.2. and SMC.

7. 7.5 Networking Between MSOFTX3000 and HLR The MAP interface is used between MSOFTX3000 and HLR.2. Numbers of the MTP link sets shall correspond to DSP indexes and be numbered in an ascending sequence (starting from 0). Moreover.3 Principles for Naming Signaling Links The principles for naming signaling links are as follows: DSP name: Name DSP with the peer office name. HLR. set IMSI data for GMSC. name them with ”office name_alternative route office name”. Link name: Name outgoing links with the peer office name (location+NE ID+NE serial No. 7. It is recommended to number the BSC first. besides the IMSI data. HSTP. TDM TDM based C/D MSOFTX3000 MAP TCAP SCCP MTP3 MTP2 MTP1 HLR Figure 7-11 Networking and protocols between MSOFTX3000 and HLR 7-10 .-Link No). MTP route name: Name outgoing routes with the peer office name. SS7 route sets shall be numbered in an ascending sequence according to the sequence of the DSP indexes. the VMSC must be configured with the GT data of the adjacent VMSC if handovers occur between two VMSCs. local VMSC. and then non-adjacent office directions.2. local GMSC.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 7 Configuring Data for Interworking with HLR Since location update is not performed at GMSC. While for VMSC. MAP may be based on ATM or IP.2. Link set name: Name outgoing link sets with the peer office name. LSTP.4 Principles for Numbering MTP Data The principles for numbering MTP data are as follows: DPC indexes are numbered in an ascending sequence. then RNC. For non-direct routes. office directions in other networks. The current networking is generally based on TDM. as shown in Figure 7-11. the numbers shall correspond to office direction numbers.Operation Manual .

The solid lines represent the relationships with external entities (HLR) and the dotted lines represent the relationships between internal commands. Table 7-1 Procedures and commands for configuring data at MSOFTX3000 for interworking with HLR Procedure 1.6 Parameter Relationship The parameter relationships for interworking between MSOFTX3000 and HLR are illustrated in Figure 7-12.Operation Manual .2.] [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] Figure 7-12 Parameter relationship between MSOFTX3000 and HLR 7. Configure MTP 1) Add MTP DSP 2) Add MTP link set 3) Add MTP route 4) Add MTP link ADD N7DSP ADD N7LKS ADD N7RT ADD N7LNK Command 7-11 .7 General Configuration Procedures The procedures and commands for configuring data for interworking between MSOFTX3000 and the HLR are listed in Table 7-1.] [Start Circuit No.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 7 Configuring Data for Interworking with HLR 7. HLR parameters MSOFTX3000 parameters ADD N7DSP [DSP index] Signaling network indicator HLR OPC Peer end MSC DPC [NI] [DPC] [OPC] ADD N7LKS [LinkSet Index] [Adjacent DSP Index] ADD N7RT [Linkset index] [DSP index] ADD SCCPDSP [NI] [DPC] [OPC] SLC ADD N7LNK [Link No.2.

you need to collect the interfacing data between MSOFTX3000 and HLR. Background Information When the TDM mode is used for signaling transmission to the HLR.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 7 Configuring Data for Interworking with HLR Procedure 2. and link information. The other parameters are the internal ones of MSOFTX3000.164 code) Signaling link Link set Intra-module link number Link type / SCCP GT translation / / Coding description Numbering plan Address information DPC 7.Operation Manual . route. including MTP DSP.3 Collecting Data for Interworking with HLR Before configuring data for interworking with HLR.1 Adding MTP Layer Data I. Configure SCCP 1) Add SCCP remote SP 2) Add SCCP subsystem 3) Add SCCP GT Command ADD SCCPDSP ADD SCCPSSN ADD SCCPGT 7. as shown in Table 7-2. II. Table 7-2 Data for interworking with HLR Item Basic information / WCSU module number Signaling link code (SLC) and SLC sending Intra-module circuit number (E1 number/time slot number) Signaling point code Data Signaling point network indicator HLR number (E.4.4 Configuring Data for Interworking with HLR 7. In the shadowy columns are the parameters that must be negotiated between both ends for consistency or of which one end must notify the other. link set. Command The procedures to add MTP link data are as follows: 7-12 . it is required to configure MTP related data.

Command ADD SCCPDSP Note: This command is used to configure the SP information for the peer HLR. Major Parameters Refer to sections 6. [DPC] It refers to destination signaling point code. 0 in the OFI table.2 Adding SCCP DSP I. IV.4. You can query it with the LST OFI command. Here set it to the DPC of the peer HLR. For HLR.5 in Chapter 6.4. This parameter is the same as that set in the ADD N7DSP command. III. [OPC] It refers to the local office's SPC in the same network indicator.2– 6. 7. The DPC of the HLR is the national reserved 24-bit SPC. Related Commands Refer to sections 6. Related Commands 7-13 .5 in Chapter 6. Background Information None II.4. set this parameter to "NAT (National Network)". the OPC is the national network SPC of record No.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 7 Configuring Data for Interworking with HLR 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) III. IV.4.2– 6. Major Parameters [DPC Index] It is used to identify a remote DSP. This index must be the unique one identifying a remote DSP among all remote DSPs.Operation Manual . [NI] For HLR.4.

For the subsystem interworking with HLR. The network indicator of MSOFTX3000 is "National Network".4. Subsystem number (SSN) is the local addressing information used by SCCP to identify the SCCP users under a SP. The SSN to be configured at the HLR side includes SCMG and HLR. Command ADD SCCPSSN III. and the configured SSN is SCCP management subsystem (SCMG).3 Adding SCCP Subsystem I. it may be required to run this command repeatedly to configure multiple SCCP subsystems. VLR. and SCMG subsystems have been configured in the local office information. Since the local MSC. 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 7. set it to "National Network".Operation Manual . II. Major Parameters [SSN Index] It is used to identify the SCCP subsystem. 7-14 . and to add SCMG and HLR subsystems at the remote end. [NI] It is used to set the indicator of the network to which the SCCP subsystem belongs. Local MSC and VLR subsystems are already added in the local office information. [SSN] It is required to add SCMG at the local end. execute the LST SCCPSSN command to have a check to avoid repeated configuration. For any entity (local end or remote end). and it is unique in the system. Background Information This following command ADD SCCPSSN is used to add SCCP subsystems in MSOFTX3000 (local end) and the HLR (remote end). The devices to be interconnected should be in the same signaling network.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 7 Configuring Data for Interworking with HLR See Table 7-3 for the commands related to SCCP DSP configuration.

To display SCCP subsystems in the host Description 7. You need to set HLR SPC and OPC here. 7-15 . This command is used during maintenance. It is valid only when MSOFTX3000 supports the load sharing function or backup function of SCCP DSP. use the default value “65535”. [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.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 7 Configuring Data for Interworking with HLR [SPC] It is used to specify the destination SPC of the corresponding subsystem. Background Information When MSOFTX3000 is directly connected to HLR. If there is no subsystem. [Backup SSN Index] It is used to specify the index of the backup subsystem of a specified subsystem. IV. You can define a maximum of 5 indexes. [OPC] Enter the national reserved network SPC of the local office. Table 7-4 List of commands related to SCCP subsystem configuration Command ADD SCCPSSN RMV SCCPSSN MOD SCCPSSN LST SCCPSSN SET SCCPSSN DSP SCCPSSN To add an SCCP subsystem To remove an existing SCCP subsystem To modify an existing SCCP subsystem To list SCCP subsystems To set SCCP subsystem status.4 Adding SCCP GT I. If there is no related subsystem. Related Commands See Table 7-4 for the commands related to SCCP subsystem configuration.4. Ordinary GT (HLR-MSISDN GT) when the subscriber is called. the recipient of SCCP messages. Local MSC GT to be queried when the local office performs second-stage number analysis. use the default option “Undefined”. it is required to configure the following global title (GT) data for the three cases: IMSI GT and HLR-NUMBER GT for location update.Operation Manual . The HLR SPC must be correlated with that defined in the command ADD SCCPDSP. that is. It is associated with the parameter “OPC” in the SET OFI command.

GTNAME="IMSI-GT". Then use the following command (supposing that the SP of the HLR is 12345): ADD SCCPGT: GTX=1. it is required to use the ADD IMSIGT command to translate GT. 2) Local MSC GT configuration When a subscriber is called. it is required to execute the following command: ADD SCCPGT: GTX=3. VLR obtains the HLR destination address through analyzing HLR number. the length of the parameter “ADDR” can be set according to the actual condition. it is required to execute the following command: ADD SCCPGT: GTX=2. the location update has not yet completed after those two commands are executed. In the last step. After the above IMSI GT and HLR-NUMBER GT configurations. HLR-NUMBER GT configuration: It is performed for location update when VLR inserts subscriber information response to HLR to find corresponding HLR. SPC="12345". Where. CCNDC="86139" to translate 46000×××××××× into 86139××××××××. GTNAME="HLR-GT". Supposing the HLR number is 8613907551234. For example. 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. the GT configuration related to location update has been completed.Operation Manual . However. SPC="12345". because VLR needs to insert subscriber response PRN-ACK to HLR. The numbering plan here is the telephone numbering plan. use the command ADD IMSIGT: MCCMNC="46000". ADDR=K'861390755. MSC needs to get his/her roaming number in the HLR. When a mobile station initiates location update request. Because IMSI number cannot build GT. NI=NAT. and the parameter “NUMPLAN” must be mobile numbering plan “ISDNMOV”. 7-16 . MSC needs to get his/her roaming number in the HLR and gets the HLR SPC through analyzing the MSISDN of the called number. NUMPLAN=ISDNMOV.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 7 Configuring Data for Interworking with HLR 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. MSC/VLR can find HLR. GTNAME="HLR NUMBER". (note: 86139×××××××× is not a phone number). it sends the IMSI number. RESULTT=STP1. Assuming that IMSI 46000×××××××× in the HLR is assigned with MSISDN 861390755×××××. which is carried in the called number on SCCP layer when HLR inserts subscriber data message. ADDR=K'86139××××××××. When a subscriber is called. RESULTT=STP1. RESULTT=STP1. According to the analysis in 1). SPC="12345". ADDR=K'8613907551234.

2. MSC will initiate paging. so it is not necessary to configure it here.Operation Manual . set this parameter to "00". Major Parameters [GT Index] GT index: It uniquely identifies a GT code. You can add subsystems with the ADD SCCPSSN command. [Translation Type] In the mobile network. [Numbering Plan] To set this parameter. [GT Address Information] To set this parameter. II. refer to GT data configuration analysis of this section. refer to GT data configuration analysis of this section. [SPC] It is used to uniquely indicate a translation code in the GT table. See section 7. which checks whether it is the local MSC GT. [GT Indicator] There are four classes of GTs in the mobile network. If yes.2 “Principles for Configuring GT Data” [SSN] It is used to specify a subsystem. Select "GT4 (TYPE4) generally. [Nature of Address Indicator] This parameter specifies the property of an address indicator. it is required to select a related subsystem. The GT translation code of the local MSC has been described in local office information configuration. set this parameter to "NAT (NATIONAL NETWORK)". Related Commands See Table 7-5 for the commands related to SCCP GT configuration. It is associated with that defined in the ADD SCCPSSN command. Command ADD SCCPGT III. [Translation Result Type] Set this parameter according to the actual conditions. IV. [NI] For the local MSC/VLR. If “LSPC1 (SPC + SSN)" is selected in “Translation Result Type”. the HLR sends SRI-RSP message with MSC GT address information to MSC. 7-17 .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 7 Configuring Data for Interworking with HLR After getting the roaming number.

7-18 . SCP SMC HLR GMLC MAP/TDM MAP/TDM MAP/TDM MAP/TDM MSC Server ISUP/TDM MSOFTX 3000 BSSAP+/TDM SGSN H.5 Configuration Example 7.248.RANAP / IP ISUP. The HLR information is shown in Table 7-6.1 Example Description Suppose the networking model is as shown in Figure 7-13.BSSAP / TDM SPC 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.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 7 Configuring Data for Interworking with HLR 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 7. refer to Table 3-14 in Chapter 3.5. For the local office information.Operation Manual .

LSX=11. SHAREFLAG=NONE. ADD SCCPSSN: SSNX=11. NUMPLAN=ISDNMOV. SLC=0.5.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 WCSU module number Link set Intra-module link number Link type / SCCP GT translation / / / 23 Coding descripti on IMSI GT HLR NUMBE R MSIDSN 11 Numberin g plan ISDNMOV ISDN ISDN 1 Address information 86139 86139075500 00 861390755 64 kbit/s DPC 12345 12345 12345 7. ADD N7LNK: MN=23. OPC="CC0004". DPNAME="HLR". RTNAME="HLR". GTNAME="HLR-IMSIGT". OPC="CC0004". CCNDC="86139". ADD SCCPDSP: DPX=11. SPC="12345". DPNAME="HLR". DPX=11.LNKTYPE=0. OPC="CC0004". DPC="12345". SPC="12345". 7-19 . SSN=HLR. DPC="12345". ADD N7DSP: DPX=11. OPC="CC0004". ADD SCCPSSN: SSNX=10. SSN=SCMG.Operation Manual . ASPX=11. LNKN=1. ADD IMSIGT: MCCMNC="46000". LSNAME="HLR".2 Configuration Description //Add MTP layer data. //Add SCCP layer data. NI=NAT. ADD N7RT: LSX=11.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 7 Configuring Data for Interworking with HLR Table 7-6 HLR information table Item Basic information / Signaling point code 12345 Data Signaling point network indicator National network HLR number (E. SSNNAME="HLR-HLR". NI=NAT. ADD SCCPGT: GTX=8. ADD N7LKS: LSX=11. TS=48. SSNNAME="HLR-SCMG". NI=NAT. ADDR=K'86139. LNKNAME="HLR".

GTNAME="HLR-MSIDSN".Operation Manual . SPC="12345". ADDREXP=INTER.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center RESULTT=LSPC2. NUMPLAN=ISDN. Chapter 7 Configuring Data for Interworking with HLR ADD SCCPGT: GTX=9. SPC="12345". RESULTT=STP1. GTNAME="HLR-NUMBER". ADD SCCPGT: GTX=10. ADDR=K'861390755. RESULTT=LSPC2. 7-20 . SPC="12345". ADDR=K'8613907550000.

Operation Manual . Generally.1 Introduction to the Chapter This chapter describes the data configuration process at MSOFTX3000 for interworking with other MSC Server. When using ISUP and MAP (for handover).2. such as TDM and IP. This chapter contains the following sections: Concepts Related to Data Configuration for Interworking with Other MSC Server Collecting Data for Interworking with Other MSC Server Configuring Data for Interworking with Other MSC Server Configuration Example 8.2 Related Concepts 8. 8-1 . they are connected through the E/G interface. MSOFTX3000 and MSC Server are connected through the Nc interface. See Figure 8-1. This section introduces the networking with the E/G interface as example.1 Networking Between MSOFTX3000 and MSC Server When using BICC protocol. the current networking modes are carried over TDM and ISUP is used in trunk signaling.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 8 Configuring Data for Interworking with MSC Chapter 8 Configuring Data for Interworking with MSC (MTP) 8. ISUP can be carried over multiple transmission media.

MSC SERVER parameters MSOFTX3000 parameters ADD N7DSP ADD N7LKS Signaling network indicator Local MSC OPC Peer MSC DPC [DSP index] [NI] [DPC] [OPC] ADD SCCPDSP linkSet Index [Adjacent DSP Index] ADD N7RT [LinkSet Index] [DSP index] ADD N7LNK Signaling link code (SLC) [NI] [DPC] [OPC] ADD SCCPSSN [NI] [SSN] [SPC] [OPC] ADD SCCPGT [Link No.] [Start Circuit No.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 8 Configuring Data for Interworking with MSC MSOFTX3000 TDM bearer Semi-permenant connection TDM bearer MGW MSC ISUP MTP3 MTP2 MTP1 Figure 8-1 Networking and protocols between MSOFTX3000 and MSC Server 8.Operation Manual .2 Parameter Relationship The parameter relationships for interworking between MSOFTX3000 and MSC Server are illustrated in Figure 8-2 and Figure 8-3. The dotted lines represent the relationships of MSOFTX3000 with external entities (MSC Server) and the solid lines represent the relationships between internal commands.] ] [LinkSet Index] [Signaling Link Code] MSC number [NI [GT Address Information] [SPC] Figure 8-2 Parameter relationship between MSOFTX3000 and other MSC Server (MTP and SCCP) 8-2 .2.

8-3 .Operation Manual .3 General Configuration Procedures The procedures and commands for configuring data for interworking between MSOFTX3000 and other MSC Server are listed in Table 8-1.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Parameters pertaining to peer route trunk Chapter 8 Configuring Data for Interworking with MSC 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.2.

Table 8-2 Data for interworking with other MSC server Item Signaling point code Data Signaling point network indicator MSC Server number (E. Configure SCCP 1) Add SCCP remote signaling point 2) Add SCCP subsystem 3) Add SCCP GT 3.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 8 Configuring Data for Interworking with MSC Table 8-1 Procedures and commands for configuring data at MSOFTX3000 for interworking with other MSC Server Procedure 1. The other parameters are the internal ones of MSOFTX3000. you need to collect the interfacing data between MSOFTX3000. In the shadowy columns are the parameters that must be negotiated between both ends for consistency or of which one end must notify the other end. Configure MTP 1) Add MTP DSP 2) Add MTP link set 3) Add MTP route 4) Add MTP link 2. and the peer MSC server.3 Collecting Data for Interworking with Other MSC Server Before configuring data for interworking with other MSC server.164 code) Basic information / 8-4 .Operation Manual . Configure routing information 1) Add office direction to MSC Server 2) Add sub-route 3) Add route 4) Add route analysis 4. as shown in Table 8-2. MGW. 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 8.

3 Configuring SCCP Data As MAP is required between MSC Servers to interchange mobile management information.4.2 Configuring MTP Data Refer to sections 6.4.4. Add MTP link set (ADD N7LKS).4 in Chapter 7 “Configuring Data for Interworking with 8-5 . Add MTP link (ADD N7LNK).2–6. you need to set SCCP layer data. 8. 8.4.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 8 Configuring Data for Interworking with MSC Item WCSU module number Data Signaling link code (SLC) and SLC sending Intra-module circuit number (E1 number/time slot number) Signaling link Link set Intra-module link number 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 in Chapter 6 “Configuring Data for Interworking with BSC” to configuration data for the MTP layer.1 Negotiating and Preparing Data For detailed procedures to configure interworking data between MSOFTX3000 and MGW.4.Operation Manual .4. refer to Chapter 4 “Configuring Data for Interworking with MGW”of this manual.4. Add MTP route (ADD N7RT).2–7. The steps to add MTP links are as follows: 1) 2) 3) 4) Add MTP DSP (ADD N7DSP).4 Configuring Data for Interworking with Other MSC Server 8. Refer to sections 7.

Add SCCP subsystems (ADD SCCPSSN): Add MSC. ”MSC” for “Peer Office Attribute”. “NAT (NATIONAL)” for “Network Indicator” and enter the DPC of the MSC for the parameter “Destination Point Code”.4. ”SAME (PEER)” for “Peer Office Level”.1 Example Description Suppose the networking model is as shown in Figure 8-4.Operation Manual . The steps to add SS7 trunk circuit information are as follows: 1) 2) 3) Add SS7 trunk group (ADD N7TG). Interpretation result type: select “LSPC2(SPC)”.5 Configuration Example 8. 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.3. Because the local MSC. use the LST SCCPSSN command to have a check to avoid repeated configuration.3.6 in Chapter 10 “Configuring Data for Interworking with PSTN” to configure routing data. Select "National Network" for NI. Add route analysis data (ADD RTANA).3.4.5 Adding SS7 Trunk Circuit Refer to sections 10. Add route (ADD RT). 8-6 . "ISDN (ISDN/TELEPHONY NUMBERING PLAN)" for numbering plan.5. VLR.7–10. 8. “Configuring Data for Interworking with PSTN” to configure SS7 trunk circuit information. The steps to add routing information are as follows: 1) Add office direction from MSOFTX3000 to MSC Server (ADD OFC): Select “MSC” for “Opposition Office Type”. 3) Add SCCP GT (ADD SCCPGT): It is only required to configure MSC server GT. VLR and SCMG subsystems have been configured in the local office information table. Add SS7 trunk circuit (ADD N7TKC).3.8 in Chapter 10. and SCMG subsystems to the remote MSC server. 2) 3) 4) Add subroute (ADD SRT).4 Adding Routing Information Refer to sections 10.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 8 Configuring Data for Interworking with MSC HLR” to configure data for the SCCP layer. and enter SMC number for GT address information. 8. Modify SS7 trunk circuit state (MOD N7TKC) 8. MAP.3–10.

RANAP /IP ISUP.Operation Manual .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 8 Configuring Data for Interworking with MSC SCP SMC HLR GMLC MAP/TDM MAP/TDM MAP/TDM MAP/TDM MSC Server ISUP/TDM MSOFTX 3000 BSSAP+/TDM SGSN H. refer to Table 3-14 in Chapter 3.248. 8-7 . The MSC server information is listed in Table 8-3. For the local office information.BSSAP / TDM SPC 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.

LSNAME="MSC-1". LNKN=1. LNKNAME="MSC-1". SPC="AA0001". SPC="AA0001".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 WCSU module number 22 Link set Intra-module link number Link type / 1 1 64 kbit/s Circuit Termination ID (the number of the physical circuit from MGW to MSC Server) 32–63 Office direction 1 Prefix Route number 1 Route selection code 1 CIC / Trunk route / Prefix / 0–32 Sub route number 1 Route selection source code 0 13910 8. DPX=1. TS=48. //Add SCCP layer data. ADD N7RT: LSX=1.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 8 Configuring Data for Interworking with MSC Table 8-3 MSC server information table Item Basic information Signaling point code Signaling point network indicator National network Data MSC Server number (E.2 Configuration Description //Add MTP layer data. OPC="CC0004". OPC="CC0004". SSNNAME="MSC-SCMG". ADD SCCPSSN: SSNX=12. NI=NAT.Operation Manual . ADD SCCPDSP: DPX=1. OPC="CC0004". ADD SCCPSSN: SSNX=13. LNKTYPE=0. LSX=1. SLC=0. ASPX=1. SHAREFLAG=NONE. DPC="AA0001".5. RTNAME="MSC-1". NI=NAT. DPNAME="MSC-1". OPC="CC0004". DPNAME="MSC-1". NI=NAT. ADD N7DSP: DPX=1. DPC="AA0001". 8-8 . SSN=MSC. ADD N7LNK: MN=22. SSN=SCMG. ADD N7LKS: LSX=1.

RN="MSC-1". GTI=GT4. SSN=VLR. ADD SCCPSSN: SSNX=14. SOPC="CC0004". SCF=TRUE. DOA=MSC. 8-9 . GTNAME="MSC1-GT". TG=1. SC=32. RUT=ALL. ADDR=K'8613500001. NI=NAT. DOL=SAME. RESULTT=LSPC2. SDPC="AA0001". Chapter 8 Configuring Data for Interworking with MSC NI=NAT. TID=32. NI=NAT. ISUP=ISUP_F. ADI=ALL. CS=UNU. SC=32. G=INOUT. SPC="AA0001". SRN="MSC-1". MOD N7TKC: MN=22. TMX=0. MGW=1. ADD SCCPGT: GTX=1. ADD SRT: SRC=1. TGN="MSC-1". SSNNAME="MSC1-VLR". SR1=1. MOD N7TKC: MN=22. //Configure the office direction to MSC. SPC="AA0001". OPC="CC0004". RSSC=0. DPC1="AA0001". OOFFICT=MSC. TP=ALL. EC=48.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center SSNNAME="MSC1-MSC". ADD OFC: OFFICEDIR=1. ON="MSC-1". O=1. SIG=MTP3. SCIC=0. ADD N7TKC: MN=22. //Configure the SS7 link to MSC. SC=48. ADDREXP=INTER. CT=ISUP. SRC=1. ADD N7TG: TG=1. NUMPLAN=ISDN. EC=63.Operation Manual . R=1. CS=UNU. ADD RT: R=1. ADD RTANA: RSC=1. EC=32.

IP bearer MSOFTX3000 MGW(SG) TDM bearer MSC ISUP M3UA SCTP IP M3UA SCTP IP MTP3 MTP2 MTP1 ISUP MTP3 MTP2 MTP1 Figure 9-1 Networking and interface protocols between MSOFTX3000 and MSC 9. This chapter introduces the data configuration for this networking mode. This chapter describes the data configuration procedures for the networking mode as shown in Figure 9-1.1.1 Related Concepts 9. this networking mode can be used for connecting the MSOFTX3000 with the remote tandem office. Signaling from the MSOFTX3000 to MGW is carried over IP. 9-1 .1 Networking Between MSOFTX3000 and MSC ISUP signaling is used between MSOFTX3000 and the remote MSC. The MGW fulfills signaling transferring from IP bearer to TMD bearer. Currently.Operation Manual . 9.1. The parameter “NI” in the figure must be assigned with the same attributes. The networking from the MSOFTX3000 to the peer end MSC uses the MGW concurrently as the signaling gateway for signaling transferring between the MSOFTX3000 and the peer end MSC. This networking mode is applicable to the connection between the MSOFTX3000 end office and the peer tandem office. Refer to Figure 9-1 for the networking and interface protocols.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 Configuring Data for Interworking with MSC (ISUP/M3UA) Chapter 9 Configuring Data for Interworking with MSC (ISUP/M3UA) This chapter describes the data configuration process at the MSOFTX3000 for interworking with the peer end MSC.2 Parameter Relationship Figure 9-2 illustrates the parameter referencing relationship at the MSOFTX3000 side during configuration.

Operation Manual .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 Configuring Data for Interworking with MSC (ISUP/M3UA) ADD M3LE [Local entity index] [Local entity point code] [NI] [Local entity type ] [Route context](optional) --- ADD M3DE [Local entity index] [Destination entity index] [NI] [Destination entity point code] [Destination Entity Type] [Adjacent flag] --- ADD M3LKS [Adjacent entity index] [Work mode] [LinkSet index] --- ADD M3RT [Destination entity index] [LinkSet index ] ADD M3LNK [LinkSet index] [Module number](ADD FECFG) [Local IP Address1] (ADD FECFG) [Local port] [Peer IP address1] [Peer port] [C/S mode] --- Figure 9-2 Parameter relationship between MSOFTX3000 and MGW (M3UA) 9-2 .

Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 Configuring Data for Interworking with MSC (ISUP/M3UA) 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. The other parameters are the internal ones of the MSOFTX3000.3 Collecting Data Before configuring data. MGW and peer end MSC. In the shadowy columns are the parameters that must be negotiated between two ends for consistency or of which one end must notify the other end. as shown in Table 9-1.Operation Manual .1. you need to collect interface data for interworking between MSOFTX3000. 9-3 .

9-4 .2 General Configuration Procedures The procedures and commands for configuring data for interworking between MSOFTX3000 and MSC are listed in Table 9-2.Operation Manual .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 Configuring Data for Interworking with MSC (ISUP/M3UA) Table 9-1 Table of data collected for the MSOFTX3000 interworking with MSC Item Basic information Signaling point code Network indicator Data Basic M3UA signaling Service mode Route context (optional) WIFM module number SG signaling point code SPC of peer MSC M3UA link information M3UA link number Local IP Local port IP address of the peer MGW Port number of the peer MGW Server/Client Circuit Termination ID (the physical circuit number at MGW for interworking with MSC Server) CIC WCCU/WCSU module number MGW Index Trunk circuit Office direction Route number Sub-route number Trunk group Circuit type Prefix Prefix Route selection code Route selection source code 9.

Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 Configuring Data for Interworking with MSC (ISUP/M3UA) Table 9-2 Procedures and commands for configuring data at MSOFTX3000 for interworking with MSC Procedure 1.Operation Manual . What need to be configured are the IP address and route of the Mc interface. 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.3 Procedures 9. M3UA link configuration 9-5 .1 Negotiating and Preparing Data I. refer to Chapter 4 “Configuring Data for Interworking with MGW”.3. Mc Interface Date for Interworking between MSOFTX3000 and MGW For the data about the Mc interface between MSOFTX3000 and MGW. 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. Configure M3UA (for interworking with MSC) 1) Add M3UA destination entity 2) Add M3UA route 3. Data to Be Configured at MGW Side Interface configuration Signaling messages of the MGW are sent to the MSOFTX3000 through the Mc interface (10/100 Mbit/s adaptive Ethernet interface) provided by the MPPU. II.

and national reserved network.2 Adding M3UA Local Entity I. 9. Major Parameters [Local Entity Index] It is used to uniquely identify an M3UA local entity [NI] It is used to indicate the network type. A signaling point can simultaneously appear in international network. The route context at AS side must be the same as that at SG side.Operation Manual . For the SGP-ASP mode. route. link set. [Local Entity Point Code] It is used to define the local office point code. Related Commands Table 9-3 lists the commands related to the M3UA local entity configuration. flow. set the entity type at MSOFTX3000 side to “AS”. execute the LST OFI command to check whether the local originating signaling point code (OPC) is configured. [Local Entity Type] It is used to define the type of a local entity. Background Information Before adding M3UA local entity for the MSOFTX3000. For more information. 9-6 .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 Configuring Data for Interworking with MSC (ISUP/M3UA) It includes the configuration of M3UA entity. and that at peer MGW side to “SG”. If not. and link. IV. national network. [Route Context] (optional) It is used to specify the index value of a group of SS7 parameters.3. international reserved network. see HUAWEI UMG8900 Universal Media Gateway Operation Manual – Data Configuration. It may be SG or AS. Command ADD M3LE III. II. configure it first. route. This parameter can be configured when the entity type is AS.

[Local Entity Index] It is used to identify a local entity to which the destination entity corresponds.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 Configuring Data for Interworking with MSC (ISUP/M3UA) 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 9. [NI] It is used to indicate the network type.3. You need to add two types of destination entity: one is MGW as SG. the other is MGW as SP. II. Set this parameter to “National active”. to be configured with the DSP of SG.3 Adding M3UA Destination Entity I. national network. international reserved network. In this case. Major Parameters [Destination Entity Index] It is used to identify a destination entity uniquely for referencing internally. This index is already defined in the ADD M3LE command. Command ADD M3DE III. As the SG is integrated in the MGW. A signaling point can simultaneously appear in international network. the MGW resident office must allocate a signaling point code for the built-in SG. [Destination Entity Point Code] 9-7 . Background Information You must set the destination entity before a path from the local entity to the destination entity becomes available.Operation Manual . to be configured with the signaling point of the peer office. and national reserved network. it appears that MGW has a signaling point code which in fact is allocated to the SG.

[STP Flag] It is used to set whether a DSP has STP function. The default is used. select “NO”. To set the destination entity to SG type. This parameter is valid only when the parameter “Destination Entity Type” is set to “AS” or “SG”. There are three types of destination entity. Related Commands See Table 9-4 for the commands related to M3UA destination entity configuration. By default. it is RFC3332. select “TRUE”. By default.Operation Manual . select “FALSE”. As MGW also functions as an SG. 9-8 . [Link set select mask] This parameter indicates how to achieve load sharing among all routes to an M3UA destination entity. SG. the AS is an exclusive SPC. Its value is determined by the actual destination entity type to be configured. The MSOFTX3000 supports the interconnection with the M3UA destination entity specified in DRAFT10 or RFC3332. [Destination Entity Type] It is used to define the type of a destination entity. that is. [Protocol Version] It is a parameter for interconnection between MSOFTX3000 and a destination entity. to set it to SP type. add MGW as SG and peer MSC as SP. and AS. Select “YES” when there is such a direct signaling link with the local office signaling point. namely SP. [Network Mode] This parameter is used to specify the network mode between SG and AS. whether there is a signaling link directly associated with the local office signaling point. This parameter need not to be configured. otherwise. 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.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 Configuring Data for Interworking with MSC (ISUP/M3UA) It is used to specify the signaling point code of a destination entity. IV. [Adjacent flag] It is used to set whether a DSP is adjacent to the local office signaling point.

The index is used in the M3UA routing table.3. Set the parameter “adjacent flag” of the corresponding destination entity to “adjacent".Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 Configuring Data for Interworking with MSC (ISUP/M3UA) 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 9. [Link Select Mask] It indicates how to share signaling traffic among the multiple signaling links in the same signaling link set. [Adjacent Entity Index] It is used to identify the adjacent destination entity interconnected by the associated signaling link set. Background Information This section describes how to establish a link set between two adjacent M3UA entities. the two 9-9 . [Traffic Mode] It is used to determine the service mode of the link set is “Load-Share Mode” or “Over-Ride Mode”. Major Parameters [LinkSet Index] It is used to specify the logical number of a link set in the system. This index is related to the parameter “destination entity index” in the ADD M3DE command. Command ADD M3LKS III. The value of this parameter is actually the load-sharing mask code of signaling links. The traffic modes at two ends must be the same. The index is numbered globally in an ascending order from 0. II. That is.Operation Manual .4 Adding M3UA Link Set I.

AS or SG. In this case. IPSP.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 Configuring Data for Interworking with MSC (ISUP/M3UA) ends must be in load-share mode or over-ride mode at the same time. the M3UA destination entity type is SG. It is associated with the parameter “Local Entity Type” in the ADD M3LE command. In the non-peer networking mode. otherwise. Table 9-5 List of commands related to M3UA link set configuration Command ADD M3LKS RMV M3LKS MOD M3LKS LST M3LKS DSP M3LKS To add M3UA link set To remove M3UA link set To modify M3UA link set To list M3UA link set To display M3UA link set state of the host Description 9. You can set priority for the route for carrying signaling traffic. IV. In this case.5 Adding M3UA Route I. select “IPSP". 9-10 . In the non-peer networking mode. You need to configure M3UA routes for interworking with MGW (built-in SG) and peer end MSC respectively.Operation Manual . select “SGP”. select “ASP”. In the peer networking mode. "Local Entity Type” in the ADD M3LE command is “AS”. In this case. the M3UA destination entity type is the same as the local entity type. that is. that is. such as ASP. that is. [Work Mode] It is used to indicate the attributes of the home end of a link set. according to the working mode of the link set. The default option (load-share mode) is recommended. Background Information This section describes how to determine a signaling route to a destination entity by specifying a link set that can reach this destination entity. and the corresponding local entity type is AS. and the corresponding local entity type is SG. and SGP. the M3UA destination entity type is AS. Related commands See Table 9-5 for the commands related to M3UA link set configuration.3. the corresponding link cannot be activated. "Local Entity Type” in the ADD M3LE command is “AS”.

the one with the highest priority is preferentially used to carry signaling traffic. [LinkSet Index] It is used to specify a signaling link set used by the signaling link reaching a destination entity. “Local Port".3. Major Parameters [Destination Entity Index] It is used to identify a destination entity to which a signaling route is destined. Background Information You need to negotiate such parameters as “Local IP Address1”. This parameter is defined in the ADD M3LKS command. Among the several signaling routes to the DSP. [Priority] “0” indicates the highest priority.6 Adding M3UA Link I.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 Configuring Data for Interworking with MSC (ISUP/M3UA) II. Related Commands See Table 9-6 for the commands related to M3UA route configuration. Table 9-6 List of commands related to M3UA route configuration Command ADD M3RT RMV M3RT MOD M3RT LST M3RT DSP M3RT To add M3UA route To remove M3UA route To modify M3UA route To list M3UA route To display M3UA route state of the host Description 9. It is already defined in the ADD M3DE command. IV. “Peer IP Address1”. A signaling route will carry signaling traffic unless none of signaling routes with higher priority is available. Command ADD M3RT III. and “Peer Port” with the peer end to uniquely determine an M3UA link. 9-11 .Operation Manual .

[Link No. Each link of the same module has a unique link number. This IP has to be negotiated with MGW.] It is used to identify a physical signaling link in a module. enter the WBSG module number here. [Peer IP Address2] 9-12 . and signaling messages are transmitted over IP/SCTP. [Local IP Address2] This parameter is used to specify the second local IP address to which this link corresponds. If M3UA links are configured in the WBSG. enter the WIFM module number here. You can query it with the LST MDU command. If the WIFM and WBSG are integrated into one board. [Local Port] It is used to define the SCTP port used by the M3UA message at the MSOFTX3000 side. Set it only when it supports SCTP multi-homing functionality. Ensure that the local port number specified here is consistent with the SCTP peer port number set at the MGW side. It is necessary to specify an IP address for each link. [Local IP Address1] IP based transmission is used between MGW and MSOFTX3000. Local IP address 1 is the external IP address of the local WIFM. [Peer IP Address1] It is used to specify the IP address of the built-in signaling gateway of the peer MGW. the module number is determined according to the board configured with M3UA links. enter the module number of the WIFM here. Command ADD M3LNK III. This IP has to be negotiated with the MGW. Major Parameters [Module Number] It is used to define the module number of the WIFM/WBSG where M3UA links are resident. It is necessary to specify the SCTP port number when SCTP is used for transmission control. If M3UA links are configured in the WIFM. If the WIFM and WBSG are separately configured. It is already defined in the ADD FECFG command.Operation Manual .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 Configuring Data for Interworking with MSC (ISUP/M3UA) II.

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

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

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.

IV. Related Commands
See Table 9-7 for the commands related to M3UA link configuration.

9-13

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

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

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

9.3.7 Adding Office Direction
I. Background Information
This section describes how to set an office direction from the MSOFTX3000 to the peer MSC. Before adding an office direction, you must configure the call source.

II. Command
ADD OFC

III. Major Parameters
[Office Direction] It is allocated uniquely in the system to identify an office direction. [Office Direction Name] It is recommended to use a standard name for easy identification, for example, "MSC-1". [Opposition Office Type] Select this parameter according to the type of the peer office exchange. For this parameter, select “MSC”.

9-14

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

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

[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.

IV. Related Commands
See Table 9-8 for the commands related to office direction configuration. Table 9-8 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

9.3.8 Adding Sub-Route
I. Background Information
To add a sub-route, first ensure that the office direction of this sub-route exists. Use the LST OFC command to query whether there is such an office direction. If the office direction does not exist, add it. After adding the sub-route, add the route to which the sub-route belongs and then a trunk group for the sub-route.

9-15

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

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

II. Command
ADD SRT

III. Major Parameters
[Sub-Route Number] It identifies a sub-route, which is numbered globally. [Office Direction Number] It refers to the number of an office direction to which a sub-route points, and it has been defined in the ADD OFC command. [Sub-Route Title] A sub-route should be titled as clearly as possible to indicate the route features. It is recommended that this title be the same as the office direction name. [Group Selection] In a sub-route, a trunk group should be selected according to the trunk group number (including maximum number, minimum number, loop mode, and random mode). Generally, select "Loop" by default. "Loop" here means to select the group number from the one next to the last selected. "Minimum" means to select the group number always from the minimum one. "Maximum" means to select the group number always from the maximum one. "Random" means to select a group number from all trunk groups (of a sub-route) randomly. In addition, you need to set it according to the customer's requirement.

IV. Related Commands
See Table 9-9 for the commands related to sub-route configuration. Table 9-9 List of commands related to sub-route configuration Command LST SRT ADD SRT MOD SRT RMV SRT To list sub-route information To add sub-route To modify sub-route To remove sub-route Description

9-16

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

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

9.3.9 Adding Route
I. Background Information
This section is for configuring a route from the MSOFTX3000 to the peer MSC. A route is a set of all sub-routes from the local office to a certain office direction. To add a route, you must ensure that the sub-routes composing the route have existed.

II. Command
ADD RT

III. Major Parameters
[Route Number] The route numbers are planned according to the numbering principles. [Route Type] There are two route types: ordinary routing and queued routing. Ordinary routing means that a call will not be queued if the routing fails. Queued routing means that a call will wait for an idle circuit at the subscriber side if the routing fails. Generally, set it to ordinary route. [Sub-Route Selection Mode] The sub-route selection modes include order-based selection and percentage-based selection. Order-based selection means that the sub-routes are selected from sub-route 1 to sub-route 12, that is, when sub-route 1 is busy or unavailable, sub-route 2 will be selected, and so on. Percentage-based selection means that when the traffic on a sub-route reaches its preset percentage, the next route will be selected in sequence, so that the sub-route selection probability follows a certain rule. Generally, set it to order-based selection mode. [sub-route1]–[sub-route12] They represent the numbers of twelve sub-routes respectively. The sub-route numbers correspond to the data in the sub-route table. When you enter a sub-route number, follow the order: sub-route 1 to sub-route 12. [Percentage of Sub-Route1]–[Percentage of Sub-Route12] The value range is 1–100. They are available when the sub-route selection mode is percentage-based selection. If the sub-route selection mode is order-based selection, set this parameter to 0; if the sub-route selection mode is percentage-based selection, the sub-route will be selected according to the given percentage.

9-17

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

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

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.

IV. Related Commands
See Table 9-10 for the commands related to route configuration. Table 9-10 List of commands related to route configuration Command LST RT ADD RT MOD RT RMV RT To list route information To add route To modify existing route To remove existing route Description

9.3.10 Adding Route Analysis Data
I. Background Information
This command is used to add a record to the route analysis table. Before adding route analysis data, check if the corresponding route selection code, route selection source code, route number, and time index data have been configured. The MSC obtains the route number and signaling priority flag by querying the route analysis table with such call attributes as route selection code, route selection source code, caller type identification, transmission capability, time index data, and callee address indicator. The route analysis table associates number analysis with trunk routing. Therefore, it makes a preparation for outgoing routing.

II. Command
ADD RTANA

III. Major Parameters
[Route Selection Code]

9-18

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

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

It specifies the outgoing routing mode of a call prefix, corresponding to the route selection code in the call prefix. It must be defined in the command ADD CNACLD first and then referenced here. [Route Selection Source Code] It specifies the outgoing routing mode of a call source, corresponding to the route selection source code of the call source. It must be defined in the command ADD CALLSRC first and then referenced here. [Caller Subscriber Category] It indicates the type to which a subscriber belongs. Generally, set it to "ALL (ALL CATEGORIES)". [Address Information Indicator] This parameter indicates the service attributes of a called subscriber. It includes "International Toll", "National Toll", "Local Call", and "All Categories". Generally, set it to "ALL (ALL CATEGORIES)". [Transmission Capability] The parameter indicates the transfer capability of a route. You can select different transfer capabilities as needed. Generally, set it to "ALL (ALL CATEGORIES)". [Time Index] The parameter corresponds to the time index number in the corresponding time index table. [Route Number] It defines the route number used by the route analysis table. It must be defined in the command ADD RT first and then referenced here. [Signalling as Prior] It defines the network signaling capability of an outgoing route. "FIRST" means that a circuit is selected preferentially; "MUST" means that a circuit must be selected, and if there is no such idle circuit, the routing will fail. "NOCHG (NOT CHANGE)" means that the circuit selection mode will not be changed. Set it according to the network signaling capability at the caller side. Generally, set it to "NOCHG (NOT CHANGE)" or "FIRST".

IV. Related Commands
See Table 9-11 for the commands related to the configuration of route analysis data.

9-19

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

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

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.

9.3.11 Adding SS7 Trunk Group
I. Background Information
None.

II. Command
ADD N7TG

III. Major Parameters
[Trunk Group] Trunk group number. [MGW Index] This parameter indicates the index number of MGW to which a trunk group belongs. The MGW index has been defined in the ADD MGW command. [Group Direction] Select this parameter according to the actual conditions.

9-20

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

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

[Sub-Route Number] It specifies the sub-route to which a trunk group belongs, and it has been defined in the command ADD SRT. [OPC] This parameter refers to the local signaling point code, and has been defined in the SET OFI command. [DPC] This parameter refers to the signaling point code of the peer entity. Its default value is [Destination point code 1] of the office direction table that [Sub-route number] corresponds to. Set it to the signaling point code of the peer MSC. [Circuit Type] Select this parameter according to actual conditions. Here select "ISUP". [Incoming Call Authority] This parameter is used to control the authorities for using incoming trunk circuits. Only the calls of the allowed types can be connected. You can specify this parameter as needed, or select all default values. [Outgoing Call Authority] This parameter is used to control the authorities for using outgoing trunk circuits. Only the call of the allowed types can go through. You can specify this parameter as needed. Generally, set it to "All allowed", because call authorities are controlled at the subscriber end. [Call Source Code] Its value is defined in the ADD CALLSRC command. For the other parameters, adopt their default values.

IV. Related Commands
See Table 9-12 for the commands related to SS7 trunk group configuration. Table 9-12 List of commands related to SS7 trunk group configuration Command ADD N7TG MOD N7TG LST TG To add SS7 trunk group To modify SS7 trunk group To list trunk circuit groups (including SS7 trunk group) Description

9-21

Operation Manual - Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center

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

Command RMV TG

Description To remove trunk circuit group (including SS7 trunk group)

9.3.12 Adding SS7 Trunk Circuit
I. Background Information
To add a trunk circuit, you must ensure that the trunk group to which the trunk circuit belongs must exist. If not, add the trunk group first. If the board on which the trunk circuit is located does not exist, add the trunk circuit board according to the circuit type (TUP/ISUP) and obtain the trunk circuit number according to the board number.

II. Command
ADD/MOD N7TKC

III. Major Parameters
[Module Number] This parameter indicates the module number of the WCCU/WCSU to which this trunk circuit belongs. You can query it with the LST MDU command. [Trunk Group] This parameter indicates the number of the SS7 trunk group to which a trunk circuit belongs. Its value has been defined in the ADD N7TG command. [Start Circuit] This parameter indicates the start circuit number. It is an internal parameter of the MSOFTX3000 and corresponds to TID and CIC. There is no strict limit on its value, except that it should be unique in the office. It is recommended to set it to the value of TID. [End Circuit] This parameter indicates the end circuit number. It is an internal parameter of the MSOFTX3000, and corresponds to TID and CIC. There is no strict limit on its value, except that it should be unique in the office. It is recommended to set it to the value of TID. [Start CIC] This parameter corresponds to the start CIC at the peer MSC side.

9-22

[Start Circuit Termination ID] This parameter indicates the ID of a termination corresponding to the start circuit. Table 9-13 List of commands related to SS7 trunk circuit configuration Command ADD N7TKC MOD N7TKC RST N7TKC SRS N7TKC BLK N7TKC SBL N7TKC UBL N7TKC SUL N7TKC DSP N7TKC LST TKC RMV TKC To add SS7 trunk circuit To modify SS7 trunk circuit To reset SS7 trunk circuit To stop resetting SS7 trunk circuit To block SS7 trunk circuit To stop blocking SS7 trunk circuit To unblock SS7 trunk circuit To stop unblocking SS7 trunk circuit To display SS7 trunk circuit To list SS7 trunk circuits To remove SS7 trunk circuit Description 9-23 . Set this parameter on MGW. to obtain the starting termination ID of the E1 connected to the peer MSC. [Circuit State] This parameter defines the state of a circuit or some circuits added. You can make termination IDs to correspond to E1 timeslots one to one. 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. It must be negotiated with the peer office. Use the default value “Available”.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 Configuring Data for Interworking with MSC (ISUP/M3UA) [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.Operation Manual . Related Commands See Table 9-13 for the commands related to SS7 trunk circuit configuration. IV.

Between the MSOFTX3000 and the peer MSC.1 Description of Example An MSC is added.4 Configuration Example 9. select “UNAVAILABLE”. select the timeslot configured as link in this E1.4. For the local office information. Related information of the MSOFTX3000 is shown in Table 9-14. ISUP signaling is used. The MGW concurrently serves as the signaling gateway to fulfill the signaling adaptation from IP bearer to TMD bearer. you need to set the timeslot configured as link to “UNAVAILABLE” with the command MOD N7TKC. 9-24 . For “Start Circuit” and “End Circuit”. For “Circuit State”. 9. see the part “Configuration Example” in Chapter 3.Operation Manual .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 Configuring Data for Interworking with MSC (ISUP/M3UA) Caution: After adding a circuit.

ASF=YES.132". NI=NAT.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. ADD M3RT: RTNAME="ToMSC".20. LSX=0. DEX=0. DEX=1.200. LSX=0.93". LNKN=0. LET=AS. DENAME="MSCM3ua". ADD M3DE: DEX=0. DPC="1004".200. DPC=" AA0001". PEERIP1="173. LSNAME="ToMGW1".Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 Configuring Data for Interworking with MSC (ISUP/M3UA) 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. DET=SP. LNKNAME="TO-MGW1".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 Basic M3UA signaling M3UA link information Circuit Termination ID (physical circuit for interworking of MGW with MSC server) 32–63 0–32 Route number 1 Route selection code 1 Sub-route number 1 Route selection source code 0 1 Circuit type ISUP Trunk route Office direction 1 Prefix Prefix 13910 9. 9-25 . LST OFI:. LSX=0. LST FECFG:.Operation Manual .20.2 Configuration Description //Add M3UA. LENAME="MscM3UA". DET=SG. OPC=" CC0004". NI=NAT. ADD M3LKS: LSX=0. DENAME="MgwM3ua".20.200. LOCIP1="173. ADD M3LNK: MN=132. ADD M3RT: RTNAME="ToMGW1". PEERPORT=2905 CS=C.4. LOCPORT=2905. ADX=0. NI=NAT. STPF=TRUE.200. WM=ASP. ADD M3DE: DEX=1. //Query the local IP address of WIFM ADD M3LE: LEX=0.20.

TP=ALL. EC=48. SIG=MTP3. ADD RT: R=1. SC=32. TGN="MSC-1". CS=UNU. R=1. SCIC=0. SRC=1. EC=63. TMX=0. ISUP=ISUP_F. ADD RTANA: RSC=1. DPC1="AA0001". //Configure the SS7 trunk circuit to MSC. RUT=ALL. DOA=MSC. SC=48. MOD N7TKC: MN=22. EC=32. SOPC="CC0004". ADI=ALL. DOL=SAME. 9-26 . ADD N7TKC: MN=22. NI=NAT. SRN="MSC-1". SDPC="AA0001". SCF=TRUE. OOFFICT=MSC. ON="MSC-1". ADD OFC: OFFICEDIR=1. CS=UNU.Operation Manual . ADD SRT: SRC=1. SR1=1. ADD N7TG: TG=1. MOD N7TKC: MN=22. RSSC=0. G=INOUT. CT=ISUP. O=1.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 Configuring Data for Interworking with MSC (ISUP/M3UA) //Configure the office direction to MSC. MGW=1. TG=1. TID=32. SC=32. RN="MSC-1".

10.2 Concepts Related to Data Configuration for Interworking with PSTN 10. Office Direction If there is a direct voice channel between the local exchange and another exchange. SCP HLR 0 SMC 3 BSC MSC 2 RNC 1 MSC2 GMSC Figure 10-1 Office direction 10-1 . refer to Chapter 7 “Configuring Data for Interworking with HLR”.2. This chapter contains the following sections: Concepts Related to Data Configuration for Interworking with PSTN Collecting Data for Interworking with PSTN Configuring Data for Interworking with PSTN Configuration Example 10.1 MTP For the concepts about MTP.2 Route and Trunk I.2.Operation Manual .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN Chapter 10 Configuring Data for Interworking with PSTN 10. it is taken that there is an office direction.1 Introduction to the Chapter This chapter describes the data configuration process at MSOFTX3000 for interworking with the public switched telephone network (PSTN).

MSC2. BSC. and D respectively. 1. B. The subroute allocation depends on the network planning. and office D needs to be configured with subroute D—B. and Load Sharing 1) Route and subroute For an office direction. there are four offices having traffic with the local MSC: GMSC. MSC2. Because the HLR. subroute 2. Subroute 1 is a direct subroute. while subroute 2 and subroute 3 are alternative subroutes. and D represent four exchanges (offices). Proper allocation and selection of subroutes can help achieve load sharing of a route. and RNC. Therefore. and 3 respectively. The concepts about route and subroute are illustrated in Figure 10-2. Through these subroutes. C. and different routes may contain the same subroutes. the local MSC has four office directions to GMSC. Subroute 1 A Subroute 2 B C Subroute 3 D Figure 10-2 Routes A. the route from A to B contains three subroutes: subroute 1.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN As shown in Figure 10-1. the set of all subroutes to it is called a route. The load sharing mode is described as follows: The subroutes are selected based on percentage or order for carrying traffic. SCP. One route may contain multiple subroutes. Subroute. for subroutes 2 and 3 of office A. BSC. office C needs to be configured with subroute C—B. and SMC have no traffic with the local MSC and there are only signaling messages between them. As shown in the figure. 2. and subroute 3.Operation Manual . it is taken that there is a subroute between them. which are numbered 0. 2) Load sharing One route can contain twelve subroutes in maximum. If there is a direct voice channel between two offices. 10-2 . II. A has three office directions to B. For example. and RNC. a call can finally reach the specified office. Route. C. they are not the office directions of the local MSC.

The trunk circuits to the same office direction are grouped into one trunk group. Circuit Identification Code The circuit identification code (CIC) is used to identify a circuit between two SPs. Trunk Group and Trunk Circuit 1) Trunk group The SS7 trunk group is generally bi-directional. to serve as links. To ensure that an outgoing call will not use timeslot 0 as the trunk circuit. so that it can be determined that the same call prefix (for example. In SS7. there can be 4096 circuits between two SPs in maximum. 2) Route selection code The route selection code is determined by DN set and call prefix. one E1 has 32 timeslots. IV. CIC fields only exist in the TUP and ISUP messages of circuit switched services. It refers to the route selection policy code used when calls with a certain prefix are originated. Route Selection Source Code and Route Selection Code 1) Route selection source code The route selection source code is determined by call source. an emergency call can be connected to the nearest processing center in time. numbered from 0 to 31. Different call sources can correspond to one route selection source code. that is. and is employed in route selection. For a special service number. Because a CIC field is 12 bits long. The other timeslots in E1 can be used for signaling transmission. V. VI. special service number) is in different routes of different offices. It can be composed of one or multiple PCM systems. use the command MOD N7TKC to modify timeslot 0 to "Unavailable". In this case. Timeslot 0 is used for synchronization. you can set corresponding route selection codes for different call sources to use different outgoing routes.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN III. if it is necessary to select different outgoing routes for different call sources. and it is employed in route selection. CIC Numbering Principles The principles for numbering CICs are as follows: 10-3 . and one trunk circuit corresponds to one timeslot in E1 line. and it is a set of trunk circuits with the same properties. The trunk group is the component building a subroute. 2) Trunk circuit The trunk circuit is the component constituting a trunk group. In this way. it is required to set the circuits to be used as links to "Unavailable". multiple route selection source codes may be set. and used to carry outgoing or incoming traffic. For the calls with the same prefix.Operation Manual .

and it should be negotiated with the peer office. 2. its name will be the name of subroute 1 + the name of subroute 2. if an office is a toll exchange. for example. In the current networking mode. 10. the route name can be TMSC. If a route contains multiple subroutes.2. VII. which transparently transmits ISUP messages between PSTN and MSOFTX3000 over TDM. "OUT" stands for outgoing trunk. If an office direction contains multiple subroutes. incoming trunk. It can be the name of a city where the office is resident. or bi-directional trunk: "IN" stands for incoming trunk. The principles for numbering trunks/routes are as follows: The office direction name is the same as the office name. a semi-permanent connection is established on MGW. TMSC1 and TMSC2. The allocated trunk CICs in one E1 should be consecutive and in ascending order. If subroute names are similar. which may be TDM based or IP based. 10-4 . If a route contains only one subroute. 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. and no indicator means bi-directional trunk. For example.Operation Manual . the subroute name is toll exchange.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN CIC is used when the local office is interconnected with PSTN/TMSC/GMSC. See Figure 10-3. its name can be the subroute name. Principles for Naming Trunk/Route Important Note: You must number SS7 trunks uniformly in an office direction. The subroute name and direct office direction have one-to-one correspondence relationship.3 Networking Between MSOFTX3000 and PSTN MSOFTX3000 and the PSTN exchange use ISUP protocol. A trunk group name should indicate outgoing trunk. the subroute names are differentiated by the suffixes 1. and so on.

] [LinkSet Index] SLC [Signaling Link Code] Figure 10-4 Parameter relationship (MTP) between MSOFTX3000 and PSTN 10-5 .4 Parameter Relationship The parameter relationships for interworking between MSOFTX3000 and PSTN are illustrated in Figure 10-4 and Figure 10-5 .2.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN MSOFTX 3000 TDM bearer Semi-permanent connection MGW TDM bearer PSTN ISUP MTP3 MTP2 MTP1 Figure 10-3 Networking and protocols between MSOFTX3000 and PSTN In MSOFTX3000. The solid lines represent the relationships with external entities (PSTN exchange) and the dotted lines represent the relationships between internal commands. 10. The trunk circuit data should be set in MGW. PSTN parameters MSOFTX3000 parameters ADD N7DSP Peer end MSC DPC Signaling network indicator Local OPC [DSP index] [Original Point Code] [IN] [DPC] ADD N7LKS ] [LinkSet Index] [Adjacent Point Index] ADD N7RT [LinkSet Index [DSP index] [Priority] ADD N7LNK [Link No.] [Start Circuit No. you can only set the signaling data.Operation Manual .

Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Peer office parameters Chapter 10 Configuring Data for Interworking with PSTN MSOFTX3000 parameters ADD OFC [Network ID] [Office directioin] [Destination Point Code] [signal bearer type] ADD SRT [Office Direction Number] [Sub-route Number] Destination entity signaling point code 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 10-5 Parameter relationship (route and trunk) between MSOFTX3000 and PSTN 10-6 .Operation Manual .

3 Collecting Data for Interworking with PSTN Before configuring data for interworking with PSTN.2. 10-7 . The shadowy columns are the parameters that need be negotiated between both ends for consistency or of which one end must notify the other end. Table 10-1 Procedures and commands for configuring data at MSOFTX3000 for interworking with PSTN Procedure 1. Other parameters are the internal ones of the MSOFTX3000.5 General Configuration Principles The procedures and commands for configuring data for interworking between MSOFTX3000 and PSTN equipment are listed in Table 10-1.Operation Manual . you need to collect the interfacing data between MSOFTX3000 and PSTN. Configure MTP 1) Add MTP DSP 2) Add MTP link set 3) Add MTP route 4) Add MTP link 3.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN 10. Configure routing information 1) Add office direction to PSTN 2) Add subroute 3) Add route 4) Add route analysis data 4. Negotiate and prepare data 1) Configure interworking data between MSOFTX3000 and MGW 2) Add semi-permanent connection at MGW 2. as listed in Table 10-2. Configure trunk circuit 1) Add SS7 trunk group 2) Add SS7 trunk circuit SET DPA ADD TDMIU ADD SPC ADD N7DSP ADD N7LKS ADD N7RT ADD N7LNK ADD OFC ADD SRT ADD RT ADD RTANA ADD N7TG ADD N7TKC Command ADD MGW (LST FECFG) 10.

Adding Semi-Permanent Connection at MGW The steps to add a semi-permanent connection are as follows: 1) 2) Add interface board (ADD TDMIU).1 Negotiating and Preparing Data I. Adding Interworking Data Between MSOFTX3000 and MGW For detailed steps to configure interworking data between MSOFTX3000 and MGW.Operation Manual . 10-8 .4. II.4 Configuring Data for Interworking with PSTN 10.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN Table 10-2 Data for interworking with PSTN Item Data Network indicator of signaling point Basic information Signaling point code / 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. refer to Chapter 4 “Configuring Data for Interworking with MGW” of this manual. Add semi-permanent connection (ADD SPC).

[Opposition Office Type] Set the value according to the opposite PSTN exchange type. select "PSTN (PSTN)". use the default values.2 Configuring MTP Data Refer to sections 6. [Destination Point Code1]–[Destination Point Code16] Set it to the DPC of the PSTN exchange. The steps to add MTP links are as follows: 1) 2) 3) 4) Add MTP DSP (ADD N7DSP). [Peer Office Attribute] For this parameter.Operation Manual .4.4. for example.5 in Chapter 6 “Configuring Data for Interworking with BSC” to configuration data for the MTP layer.4.3 Adding Office Direction I. 10.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN 10.2–6. Add MTP route (ADD N7RT). Major Parameters [Office Direction] It is allocated uniquely in the system and used to identify an office direction. Background Information None II.4. "PSTN-1". 10-9 . [Office Direction Name] It is recommended to use standard name for the sake of identification. Add MTP link set (ADD N7LKS). Add MTP link (ADD N7LNK). [Peer Office Level] The level of the PSTN exchange is the same as that of MSOFTX3000 in the network. Select "SAME (PEER)" here. [Network ID] Set it to "National" here. For the other parameters. Command ADD OFC III.

Operation Manual . After adding the subroute.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN IV.4. "Loop" here means to select the group number from the next one to the last selected. It is recommended that this title be the same as the office direction name. Generally. use the ADD OFC command to add it. Command ADD SRT III. [Subroute Title] A subroute should be titled as clearly as possible to indicate the route features. II. and random mode). minimum number. select "Loop" by default. Use the LST OFC command to query whether there is such an office direction. loop mode. Background Information To add a subroute. Related Commands See Table 10-3 for the commands related to office direction configuration. Major Parameters [Subroute Number] It identifies a subroute. Table 10-3 List of commands related to office direction configuration Command ADD OFC RMV OFC MOD OFC LST OFC To add office direction To remove existing office direction To modify attributes of existing office direction To list office direction configured Description 10. [Office Direction Number] It refers to the number of an office direction to which a subroute points. add the route to which the subroute belongs before adding a trunk group for the subroute. a trunk group should be selected according to the trunk group number (including maximum number. "Minimum" means to select the group number always from the minimum one. first ensure that the office direction of this subroute exists. "Maximum" means to select the group number always from the maximum one. If the office direction does not exist. "Random" means to select the group number from all trunk groups (of a 10-10 . It has been defined in the ADD OFC command. which is numbered globally. [Group Selection] In a subroute.4 Adding Subroute I.

4.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN subroute) randomly. 50. and 50 respectively. Generally. [Route Number] The route numbers are planned according to the numbering principles. Their percentages are set to 100. IV. Command ADD RT III. If it is expected that subroute 1 is selected with highest priority. you must ensure that the subroutes composing the route should have existed. Related Commands See Table 10-4 for the commands related to subroute configuration. [Route Type] There are two route types: ordinary routing and queued routing. To add a route. 10-11 . and subroutes 2 and 3 share load only when subroute 1 is fully busy. II. set it to ordinary route. you need to set it according to the customer's requirement. Table 10-4 List of commands related to subroute configuration Command LST SRT ADD SRT MOD SRT RMV SRT To list subroute information To add subroute To modify subroute To remove subroute Description 10. In addition.5 Adding Route I. Queued routing means that a call will wait for an idle circuit at the subscriber side if the routing fails.Operation Manual . Ordinary routing means that a call will not be queued if the routing fails. you can use the percentage-based selection mode. Major Parameters Important Note: One trunk route can have five subroutes in maximum. Background Information A route is a set of all subroutes from the local office to a certain office direction.

The subroute numbers correspond to the data in the subroute table. Order-based selection means that the subroutes are selected from subroute 1 to subroute 12. check if the corresponding route selection code.4.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN [Subroute Selection Mode] The subroute selection modes include order-based selection and percentage-based selection. so the corresponding call source data must have been configured before route analysis data is to be added. Related Commands See Table 10-5 for the commands related to route configuration. and time index data have been configured. [Percentage of Subroute1]–[Percentage of Subroute12] The value range is 1–100. if the subroute selection mode is percentage-based selection. IV.Operation Manual . the next route will be selected according to the order. when subroute 1 is busy or unavailable. set this parameter to 255 (which means unavailability). [subroute1]–[subroute12] They represent the numbers of twelve subroutes respectively. When you enter a subroute number. If the subroute selection mode is order-based selection. Generally. Table 10-5 List of commands related to route configuration Command LST RT ADD RT MOD RT RMV RT To list route information To add route To modify existing route To remove existing route Description 10. the subroute will be selected according to the given percentage. Route selection source code is the same as that of a call source. Before adding route analysis data. 10-12 . Percentage-based selection means that when the traffic on a subroute reaches its preset percentage. so that the subroute selection probability follows a certain regulation. They are available when the subroute selection mode is percentage-based selection. set it to order-based selection mode. follow the order: subroute 1–subroute 12.6 Adding Route Analysis Data I. route selection source code. Background Information This command is used to add a record to the route analysis table. that is. route number. subroute 2 will be selected.

"NOCHG (NOT CHANGE)" means that the circuit selection mode will not be changed. Generally. and if there is no such idle circuit. "MUST" means that a circuit must be selected. Generally. set it to "ALL (ALL CATEGORIES)". set it to "ALL (ALL CATEGORIES)". Set it according to the network signaling capability at the caller side. It must be defined in the command ADD CALLSRC first and then referenced here. [Time Index] The parameter corresponds to the time index number in the corresponding time index table. [Address Information Indicator] This parameter indicates the service attributes of a called subscriber.Operation Manual . Command ADD RTANA III. "FIRST" means that a circuit is selected preferentially. IV. corresponding to the route selection source code of the call source.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN II. 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. "National Toll". [Caller Subscriber Category] It indicates the type to which a subscriber belongs. set it to "NOCHG (NOT CHANGE)" or "FIRST". Generally. corresponding to the route selection code in the call prefix. set it to "ALL (ALL CATEGORIES)". Related Commands See Table 10-6 for the commands related to the configuration of route analysis data. It includes "International Toll". You can select different transfer capabilities as needed. the routing will fail. Generally. "Local Call". Major Parameters [Route Selection Code] It specifies the outgoing routing mode of a call prefix. It must be defined in the command ADD CNACLD first and then referenced here. and "All Categories". 10-13 . [Transmission Capability] The parameter indicates the transfer capability of a route. [Route Number] It defines the route number used by the route analysis table. [Route Selection Source Code] It specifies the outgoing routing mode of a call source.

If it is required to use a signaling point code in other signaling network. Background Information None II. you must specify it separately.4. see the numbering principles.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN 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 10. every one of them should be numbered uniquely. Major Parameters [Trunk Group] For the specific settings. It specifies the originating point code of the No. A interface trunk groups. and R2 signaling trunk groups are all numbered uniformly in the trunk group table. and it has been defined in the command ADD SRT. If you select “Bidirectional trunk”. a trunk can serve as both an incoming and outgoing channel.Operation Manual . international network.7 Adding SS7 Trunk Group I. MSOFTX3000 references the corresponding record in the subroute data table through this parameter. The MGW index has been defined in the ADD MGW command. Because SS7 trunk groups. for example. [OPC] It is one of the parameters for MSOFTX3000 to interwork with the opposite office. [Subroute Number] It specifies the subroute to which a trunk group belongs. 7 trunk group. [Group Direction] It defines whether a trunk serves as an incoming channel or outgoing channel. SS7 trunk groups are bidirectional generally. Command ADD N7TG III. [MGW Index] It indicates the index number of the MGW to which a trunk group belongs. 10-14 . The default code is the signaling point code of the local office in the national network defined in the SET OFI command.

first out” principle. including ISUP and TUP. CYC: The system selects a circuit from the next one to the last selected circuit number each time.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN Due to the limitation of the SS7 CIC length (12 bits). this parameter must be defined in the ADD OFC command before being referenced here. If the multi-signaling-point-code is used in the local office. [DPC] It is one of the parameters for MSOFTX3000 to interwork with the opposite office. The system uses the “DPC1” defined in the ADD OFC command by default. last out” principle. This mode is seldom used. 10-15 . 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.Operation Manual . If the SS7 trunk group is a bidirectional one. RNDM: The system selects a trunk circuit randomly. the system selects a circuit according to the “first in. multi-signaling-point-code is required. USR: The system selects a circuit according to the instruction from the user side. For the circuits not controlled by the local office. If the last selected number is the maximum one. Due to the limitation of the SS7 CIC length (12 bits). CTRL: For the circuits controlled by the local office. If it is necessary to enable more trunk circuits. two offices can enable a maximum of 4096 No. The default type is “ISUP”. the system selects a circuit according to the “first in. If the multi-signaling-point-code is used in the opposite office. 7 trunk circuits in the case of using single signaling point code. first out” principle. If it is necessary to enable more trunk circuits. FIFO: For all the circuits of the trunk group. the system selects a circuit according to the “first in. [Circuit Type] It specifies the signaling type used by the SS7 trunk group. this parameter must be defined in the ADD OFI command before being referenced here. 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. 7 trunk circuits in the case of using a single signaling point code. the next one is the minimum number. 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. [Circuit selection] It specifies the policy for selecting the trunk circuits in a trunk group. multi-signaling-point-code is required. two offices can enable a maximum of 4096 No. [Call source code] It has been defined in the ADD CALLSRC command. It is used to specify the destination point code of the SS7 trunk group.

the default value “No” is used. If the value is “OUTGOING NO CLIR”. it indicates that the calling line identification presentation is restricted in the incoming call signaling. You can specify this parameter as needed. or select all default values. [Connect satellite circuit] It identifies whether the SS7 trunk is carried over a satellite circuit. [DOD2] It indicates whether outgoing trunks send secondary dial tone. this parameter is invalid. With this parameter set to “YES”.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN [Reserved circuit number] It specifies the number of circuits reserved for prior calls. so keep the default value “0” of the parameter. routing will fail if all common trunk circuits are busy. If the value is “INCOMING CLIR”. Generally. the switch sends the initial tone to the opposite end and then stops it after receiving the forward register signal. [Send initial tone] It is available only when the register uses MFP. This flag is used for the fixed switch. Generally. For MSOFTX3000. use the default value. after an incoming trunk is seized. For common calls. it indicates that the calling line identification presentation is not restricted in the outgoing call signaling. Because SS7 does not use the register signaling. [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 . Generally. PULSE. 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.Operation Manual . Satellite circuits are used for international offices only. reserved circuits can be used if all common trunk circuits are busy. call priority is not set. set it to "All allowed". You can specify this parameter as needed. so set the parameter to “No”. For prior calls. [Outgoing call authority] It controls the authorities for using outgoing trunk circuits. or DTMF. [Incoming call authority] It controls the authorities for using incoming trunk circuits. It is applicable to the PBX in the fixed network only. Only those allowed types of calls can be connected. In the mobile network. the original value of “CLIP” in the call signaling is invalid. because the calling-out authorities are controlled at the subscriber end. Only those allowed types of calls can be connected. that is.

complaint tickets will be generated for both incoming and outgoing trunk calls. [Default caller number] 10-17 . In this case. [Out-Trunk charging source code] It is one of the charging attributes of the outgoing trunk group. If it is set to “YES”. If it is set to “YES”. However. when the opposite office originates a call through an incoming trunk and the call signaling does not carry the caller number. Its value ranges from 0 to 255. the local office needs to send the charging pulse to the opposite office. if this feature affects call completion rate or connection time. 255 indicates no charging of incoming trunk. its meanings for outgoing trunks and incoming trunks are different. indicating that the system will not generate a complaint ticket.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN It is one of the charging attributes of the incoming trunk group. The default value is “NO”. 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. When it is set to “YES”. the local office requests the caller number through signaling.Operation Manual . 255 indicates no charging of outgoing trunk. The default value is “YES”. the local office needs to receive the charging pulse sent back from the opposite office. the local office performs the centralized charging on the incoming trunks. When the opposite office originates a call through the incoming trunk. Its value ranges from 0 to 255. When it is set to “YES”. used to set whether the local office performs the centralized charging on incoming trunks. 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. you can set the option to “NO”. and the opposite office needs to cooperate to send the charging pulse to the local office. [Can request caller number] It is available only to incoming trunks. 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. [CLI provision mode] It is valid only for incoming trunks. Outgoing trunk: When there is an outgoing call from the trunk group. [CAMA] It is available only to incoming trunks. [Use opposite pulse] It is used for the inter-office trunk cooperation in the immediate charging. Incoming trunk: When there is an incoming call to the trunk group.

[Continuity-check] It sets whether the continuity check is conducted to a trunk group. it is required to configure echo canceller. set it to “0”. Currently. If the “CLI provision mode” is “Default number”. 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 count one over-short seizure. Its value ranges from 0 to 65535 with the unit as second. 0 or 65535 indicates that the threshold is invalid. If a trunk circuit has been seized for shorter than this threshold. the local office will use the default caller number for all calls. [Transmission mode] They define the transmission capability and mode of a trunk group depending on different services. This parameter is generally used for the case of connecting satellite circuits. [Time delay value] It sets the maximum transmission delay allowed by the circuits of a trunk group. 0 or 65535 indicates that the threshold is invalid. [Transmission capability]. call barring function is disabled. If you do not type any value or type “65535”. If a trunk circuit has been seized for longer than this threshold. [GRS timeout to single] It indicates whether to change a group reset message re-transmitted due to timeout to a single circuit reset message. Because MSOFTX3000 trunk groups have no restrictions on the transmission capablity and mode. so set this parameter to “No”. [CIC change type] 10-18 . [Call barring group] It specifies the call barring group to which a trunk group belongs. The default value “YES” is used generally. In other cases. the system will check the circuit status and generates an alarm. [Occupancy lower threshold] It defines the minimum seizure duration of a trunk circuit.Operation Manual . Its value ranges from 0 to 1023 with the unit as second. Its value ranges from 0 to 65535 with the unit as second. set these two parameters to the default value “ALL” generally.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN It is available only to incoming trunks. [Occupancy upper threshold] It defines the maximum seizure duration of a trunk circuit. If the transmission delay of a call through the circuit segments is larger than the maximum transmission delay allowed by the system. only response but not start of the continuity check is supported. the system will generate an alarm.

[Default connect] 10-19 . The configuration principle is described as follows: When the self-loop test is not enabled. Because the self-loop test is performed between two E1s. every time the system selects the trunk group. the "CIC change type” of the incoming trunk group must be set to “Decrease”. [CIC change value] It is valid only when CIC change is necessary. If it is set to “Yes”. [Soft para of service CTRL] It sets whether a trunk group supports some special services or applications. [Idle NUM for forced CLIR] Reserved. this parameter is set to “No change”.Operation Manual . indicating that forwarded calls are not barred.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN 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. [Idle NUM for weak CLIR] Reserved. In a subroute. Its value ranges from 0 to 255. This parameter is available only to incoming trunks and will be referenced when the network management data is configured. [Network management source code] It defines the network management attributes of a trunk group. the trunk interconnection will fail. When the self-loop test is enabled. the available times of the trunk group will be decreased by 1. those times will be assigned with new values. [Availability] It defines the times that a trunk group can be selected in the corresponding subroute. The default value is “No”. if the "CIC change type” of the outgoing trunk group is set to “Increase”. which intend to distribute the traffic over all trunk groups of the subroute according to the expected principle. [Barring forwarded call] It sets whether forwarded calls are barred unconditionally. indicating that the parameter is invalid. you must set this parameter to “No change”. the CIC change value must be an integral multiple of 32. If the available times of all trunk groups in the corresponding subroute become 0. the system will bar all the calls forwarded through the trunk group. otherwise. the system cannot select the trunk group. and conversely the same. When the available times become 0. The default value is 255. Generally.

it sends them to the opposite office through the signaling Initial Address Message (IAM) or Initial Address Message with Information (IAI). indicating that the local office will not request caller number on initiative. The default option is “YES”. 10-20 . If the incoming call signaling through the trunk does not contain caller number. [Connect without ORGCLD] This parameter is available only to incoming trunks. it is used to define whether the local office requests caller number from the opposite office on initiative. [Request CLI] It is available only to incoming trunks. The default value is “Yes”. if the incoming call signaling through the trunk does not contain the original called number. The group code sending mode occupies a few of CPU resources. The overlap code sending mode features fast connection but it occupies a plenty of CPU resources.Operation Manual . Generally. Group code sending: After the system collects all the digits of the called number. The default value is “65535” indicating no discrimination. 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 sets whether to request the original called number. if the caller number is not found in the caller number discrimination group table. it sends them to the opposite office through one signaling message. Subsequent Address Message with One signal (SAO) or Subsequent Address Message (SAM). this parameter is used to set whether the call is connected or all. for example. [Overlap send CLD] It specifies whether a trunk group supports overlap code sending mode. which may affect the quality of the telecom services. and then sends the remained digits of the called number one by one through other signaling messges. The default option is “NO”. It defines the corresponding caller discrimination group when it is necessary to discriminate the caller number of a call through the incoming trunk. but the connection is slow. [Request original called number] This parameter is available only to incoming trunks.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN During discrimination of a caller number. indicating that the call is connected. 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 “NO”. indicating that the local office will not request the original called number on initiative. this parameter is used to tell the local office whether to request the original called number from the opposite office. the default mode is the overlap code sending. [Discrimination group No] This parameter is available only to incoming trunks. In a forwarded call (the call redirection indicator is 1).

Related Commands See Table 10-7 for the commands related to SS7 trunk group configuration. otherwise. MSC will set the echo control information in the signaling message according to the echo control procedure.Operation Manual . set it to “No". [EC INITIATIVE] It defines whether to enable the EC function.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN [Circuit Pool No] Reserved. when the opposite office supports the echo control procedure. When “ECHO CTRL CAPABILITY” and “EC INITIATIVE” are enabled simultaneously. adopt the default values. you must set both parameters to “Yes”. For the calls of the trunk group. To be more specific. bit E in the IAM and bit N in the ACM are both set to “0”. so the default value “NO” is used. If this parameter is set to “Yes”. Table 10-7 List of commands related to SS7 trunk group configuration Command ADD N7TG MOD N7TG LST TG RMV TG To add SS7 trunk group To modify SS7 trunk group To list trunk circuit groups (including SS7 trunk group) To remove trunk circuit group (including SS7 trunk group) Description 10-21 . for the ISUP signaling. MSC will automatically filter the echo control information in the TUP/ISUP signaling message sent to the opposite office. Therefore. for the TUP signaling. if this parameter is set to “No”. it is not required for MSOFTX3000 to generate call attempt bills. Generally. [ECHO CTRL CAPABILITY] It indicates whether the local office provides the EC resources. For the other parameters. [Generate Bill For Unsuccessful Trunk Calls] It defines whether the system generates call attempt bills when the calls occupying the trunk group fail. they are in AND relationship. you can set this parameter to "Yes”. IV. To enable the EC function. bit G in the IAI/IAM and bit D in the ACM are both set to “0”.

8 Adding SS7 Trunk Circuit I.Operation Manual .3 of Chapter 6. 10-22 . “Start Circuit Termination ID”. add the trunk circuit board according to the circuit type (TUP/ISUP) and obtain the trunk circuit number according to the board number. and “End Circuit”. Background Information For the relationships among “Start CIC”.2. If the board on which the trunk circuit is located does not exist.4. To add a trunk circuit. refer to section 6. otherwise.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN 10. add the trunk group. you must ensure that the trunk group to which the trunk circuit belongs must exist. “Start Circuit”.

It is valid within the module. It is an internal parameter of MSOFTX3000. The range of circuit numbers shall not exceed the limitation of the maximum numbers of tuples (by default. It is recommended to set it to the value of TID. It must be negotiated with the peer office. CIC is valid within the office. Set “Circuit State” to “UNAVAILABLE”. Command ADD/MOD N7TKC Important Note: After adding a circuit. Set timeslot 0 for “Start Circuit” and the timeslot configured as link for “END Circuit” (related to the “Start Circuit No. [End Circuit] This parameter indicates the end circuit number. It is valid within the module. 8000 for each WCCU module). Its value has been defined in the ADD N7TG command. [Trunk Group] This parameter indicates the number of the SS7 trunk group to which a trunk circuit belongs. III. There is no strict limit on its value.Operation Manual .” in the command ADD N7LNK). [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. [Start CIC] This parameter corresponds to the start CIC at the peer MSC side. 8000 for each WCCU module). [Start Circuit] This parameter indicates the start circuit number. It corresponds to TID and CIC. It is recommended to set it to the value of TID. [Circuit State] 10-23 . You can query it with the LST MDU command. It cannot be larger than 4096 for the same signaling point. Major Parameters [Module Number] This parameter indicates the module number of the WCCU/WCSU to which a trunk circuit belongs. There is no strict limit on its value.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN II. you need to set timeslot 0 (synchronization timeslot) and the timeslot configured as link of E1 to “UNAVAILABLE” with the command MOD N7TKC. The range of circuit numbers shall not exceed the limitation of the maximum numbers of tuples (by default. It is an internal parameter of MSOFTX3000 and corresponds to TID and CIC.

1 Example Description Suppose the networking model is as shown in Figure 10-6.Operation Manual . Related Commands See Table 10-8 for the commands related to SS7 trunk circuit configuration. Set this parameter on MGW.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN This parameter defines the state of a circuit or some circuits added. IV. 10-24 . [Start Circuit Termination ID] This parameter indicates the ID of a termination corresponding to the start circuit. Use the default value “Available”. You can obtain the start termination ID of the E1 connected to PSTN by corresponding termination IDs with E1 timeslots one to one.5.5 Configuration Example 10. Table 10-8 List of commands related to SS7 trunk circuit configuration Command ADD N7TKC MOD N7TKC RST N7TKC SRS N7TKC BLK N7TKC SBL N7TKC UBL N7TKC SUL N7TKC DSP N7TKC LST TKC RMV TKC To add SS7 trunk circuit To modify SS7 trunk circuit To reset SS7 trunk circuit To stop the resetting of SS7 trunk circuit To block SS7 trunk circuit To stop the blocking of SS7 trunk circuit To unblock SS7 trunk circuit To stop the unblocking of SS7 trunk circuit To display SS7 trunk circuit To list SS7 trunk circuits To remove SS7 trunk circuit Description 10. It is an important parameter to identify a physical circuit and is used to indicate which E1 of MGW is connected to PSTN.

BSSAP / TDM SPC 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. a semi-permanent connection (SPC) is established in MGW for transparently transmitting PSTN messages between PSTN and MSOFTX3000.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN SCP SMC HLR GMLC MAP/TDM MAP/TDM MAP/TDM MAP/TDM MSC Server ISUP/TDM MSOFTX 3000 BSSAP+/TDM SGSN H. 10-25 . For the local office information. MSOFTX3000 and MGW are integrated as a whole.248. which is connected with MGW.RANAP /IP ISUP.Operation Manual . This example is to add a PSTN. TDM bearer is used between MSOFTX3000 and MGW. as well as between MGW and PSTN. The related data to be collected is listed in Table 10-9. refer to Table 3-14 of Chapter 3.

O=2. LNKTYPE=0. TP=ALL. ADD N7DSP: DPX=2. ADI=ALL. DOA=PSTN. RUT=ALL. 22 Link set Link type 2 64 kbit/s MGW Index 1 Termination ID (number of the physical circuit through which MGW reaches PSTN) 64–95 Office direction 2 Prefix Prefix / 666 10. ADD OFC: OFFICEDIR=2. R=2. NI=NAT. 25 Circuit type ISUP WCSU/WSGU module No. DPC1="BB0002".Operation Manual . TMX=0. ON="PSTN-2".Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN 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. NI=NAT. 10-26 . LSNAME="PSTN-2". RSSC=0. ADD SRT: SRC=2. 2 SLC and SLC sending 1 CIC 32–63 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. LNKN=2. DPC="BB0002". DOL=SAME. RN="PSTN-2". SLCS=2. OOFFICT=NATT.5. DPX=2. SR1=2. ADD N7RT: LSX=2. SLC=1. ADD RTANA: RSC=2. ADD N7LKS: LSX=2. DPNAME="PSTN-2". SRN="PSTN-2". //Add the data of the route to PSTN. SIG=MTP3. TS=80.2 Configuration Description /Add MTP layer data. ISUP=ISUP_F. ASPX=2. ADD N7LNK: MN=22. LNKNAME="PSTN1-2". LSX=1. RTNAME="PSTN-2". ADD RT: R=2.

MOD N7TKC: MN=25. TID=64.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Configuring Data for Interworking with PSTN //Add the data of the SS7 trunk circuit leading to PSTN. TG=2. EC=64. CS=UNU. SRC=2. MGW=1. SC=64. SC=80. SOPC="CC0004". SDPC="BB0002". EC=80. 10-27 . MOD N7TKC: MN=25. CS=UNU. ADD N7TG: TG=2. ADD N7TKC: MN=25.Operation Manual . ICR=LCO-1&LC-1&LCT-1&NTT-1&ITT-1. CRF=B0-1&B1-1. SCF=TRUE. G=INOUT. SC=64. TGN="PSTN-2". EC=95. SCIC=32.

To configure data at MSOFTX3000 for interworking with SMC. For the concepts about MTP and SCCP.1 SMC SMC is used to control and forward short messages over the MAP layer. and the MAP protocol may be based on TDM or IP. as shown in Figure 11-1.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 11 Configuring Data for Interworking with SMC Chapter 11 Configuring Data for Interworking with SMC 11. The current networking mode is TDM based. 11-1 . 11.2. refer to Chapter 7 “Configuring Data for Interworking with HLR”.2.2 Networking Between MSOFTX3000 and SMC MSOFTX3000 and the SMC apply the MAP protocol to communicate with each other. the interaction between MSOFTX3000 and SMC is on the MAP peer layer through the E/G interface.1 Introduction to the Chapter This chapter describes the data configuration process at MSOFTX3000 for interworking with a Short Message Center (SMC). In this case.Operation Manual . This chapter contains the following sections: Related Concepts Collecting Data for Interworking with SMC Configuring Data for Interworking with SMC Configuration Example 11. you need to add signaling related data instead of voice channel.2 Related Concepts 11.

The solid lines represent the relationships with external entities (SMC) and the dotted lines represent the relationships between internal commands.] [ [LinkSet ] Index [Signaling Link Code] ADD SCCPSSN [NI] [SSN] [SPC] [OPC] ADD SCCPGT [NI ] SMC NUMBER [GT Address Information] [SPC] Figure 11-2 Parameter relationship between MSOFTX3000 and SCP 11-2 .Operation Manual .2. SMC parameters MSOFTX3000 parameters ADD N7DSP [DSP index] Signaling network indicator SMC OPC Peer end MSC DPC [NI ] [DPC] [O PC] ADD N7LKS [LinkSet Index] [Adjacent DSP Index] ADD N7RT [LinkSet Index] [DSP index] [Priority] ADD SCCPDSP [NI] [DPC] [OPC] SLC ADD N7LNK [Link No.3 Parameter Relationship The parameter relationships for interworking between MSOFTX3000 and SMC are illustrated in Figure 11-2.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 11 Configuring Data for Interworking with SMC TDM TDM based E SMC MSOFTX3000 MAP TCAP SCCP MTP3 MTP2 MTP1 Figure 11-1 Networking and protocols between MSOFTX3000 and SMC 11.] No] [Start Circuit No ] No.

In the shadowy columns are the parameters that must be negotiated between both ends for consistency or of which one end must notify the other end. you need to collect the interfacing data between MSOFTX3000 and the peer SMC.164 number Signaling link Link set Link type / 11-3 .3 Collecting Data for Interworking with SMC Before configuring data for interworking with SMC. Table 11-2 Data for interworking with SMC Item Basic information / WCSU module number Intra-modul e link number Signaling link code (SLC) and SLC sending Intra-module circuit number (E1 number/time slot number) Signaling point code Signaling point network indicator Data E.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 11 Configuring Data for Interworking with SMC 11. Modify MAP parameter table ADD SCCPDSP ADD SCCPSSN ADD SCCPGT MOD MAPACCFG ADD N7DSP ADD N7LKS ADD N7RT ADD N7LNK Command 11.4 General Configuration Procedures The procedures and commands for configuring data for interworking between MSOFTX3000 and SMC equipment are listed in Table 11-1. as shown in Table 11-2.2. Configure SCCP 1) Add SCCP DSP 2) Add SCCP subsystem (SMC subsystem) 3) Add SCCP GT 3. Table 11-1 Procedures and commands for configuring data at MSOFTX3000 for interworking with SMC Procedure 1.Operation Manual . The other parameters are the internal ones of MSOFTX3000. Configure MTP 1) Add MTP3 DSP 2) Add MTP3 link set 3) Add MTP3 route 4) Add MTP link 2.

Add MTP link set (ADD N7LKS).4. 11-4 .1 Configuring MTP Data Refer to sections 6. 8613900007. Add MTP link (ADD N7LNK). The steps to add MTP links are as follows: 1) 2) 3) 4) Add MTP DSP (ADD N7DSP). Add MTP route (ADD N7RT).4 in Chapter 7 “Configuring Data for Interworking with HLR” to configure data for the SCCP layer. for GT address information. you need not modify the MAP parameter table. 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. 11.5 in Chapter 6 “Configuring Data for Interworking with BSC” to configuration data for the MTP layer. VLR and SCMG subsystems have been configured in the local office information table. for example. Select "NAT (National Network)" for network indicator.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 11 Configuring Data for Interworking with SMC 11. 11.2 Configuring SCCP Data Refer to sections 7. Background Information None II.Operation Manual . use the LST SCCPSSN command to have a check to avoid repeated configuration. "ISDN (ISDN/TELEPHONY NUMBERING PLAN)" for numbering plan. The steps to add SCCP data are as follows: 1) 2) Add a DSP of SCCP (ADD SCCPDSP): Select "NAT (NATIONAL NETWORK)" for the parameter “Network Indicator” of the SCCP DSP to the SMC.4.3 Modifying MAP Parameter Table I.4.4.4. Generally. Add SCCP subsystems (ADD SCCPSSN): Add MSC and SCMG subsystems to the remote SMC.2–6.4. As the local MSC.4 Configuring Data for Interworking with SMC 11.2–7. 3) Add SCCP GT (ADD SCCPGT): It is only required to configure ordinary GT.4. and enter SMC number.

IV. Major Parameters [Support SMMO Function] Set this parameter to "Yes". Related Commands See Table 11-3 for the commands related to MAP parameter configuration.Operation Manual .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 11 Configuring Data for Interworking with SMC III. [Support SMMT Function] Set this parameter to "Yes". Table 11-3 List of commands related to MAP parameter configuration Command MOD MAPACCFG ADD MAPACCFG LST MAPACCFG Description To modify MAP parameter table To add MAP parameter table To list MAP parameter table 11-5 .

1 Example Description Suppose the networking model is as shown in Figure 11-3. which is directly connected to MSOFTX3000 through E1 line.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 11 Configuring Data for Interworking with SMC 11. 11-6 .248.BSSAP / TDM SPC 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. For the local office information.5.Operation Manual . refer to Table 3-14 in Chapter 3. SCP SMC HLR GMLC MAP/TDM MAP/TDM MAP/TDM MAP/TDM MSC Server ISUP/TDM MSOFTX 3000 BSSAP+/TDM SGSN H.RANAP /IP ISUP. The SMC information is shown in Table 11-4.5 Configuration Example 11.

RTNAME="SMC-13". ADD N7LNK: MN=23. LSX=13. DPC="D02303". SLC=0. GTI=GT4. LNKTYPE=0. SPC="D02303".TS=112.5. SPC="D02303". NI=NAT. OPC="CC0004".Operation Manual . LNKN=3. GTNAME="SMC GT".2 Configuration Description //Add MTP layer data. ASPX=13. ADD N7LKS: LSX=13. MOD MAPACCFG: ISSSMMO=YES. SSNNAME="SMC-SCMG". OPC="CC0004". //Modify MAP parameter table. ADD N7DSP: DPX=13. LSNAME="SMC-13".164 code / D02303 8613600013 Intra-module circuit number (E1 number/timeslot number) 112 (3/16) Signaling link WCSU module number 23 Link set Signaling link code (SLC) and SLC sending 0 Link type / 13 64 kbit/s 11. ADDR=K'8613600013. DPNAME="SMC-13". RESULTT=LSPC2. ISSSMMT=YES. DPX=13. DPC="D02303". NI=NAT. OPC="CC0004". SSN=MSC. ADD SCCPSSN: SSNX=19. NI=NAT. 11-7 . SSN=SCMG. LNKNAME="SMC-13". ADD N7RT: LSX=13. ADD SCCPSSN: SSNX=18. SHAREFLAG=NONE. OPC="CC0004". SPC="D02303". SSNNAME="SMC-MSC". ADD SCCPDSP: DPX=13.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 11 Configuring Data for Interworking with SMC 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. DPNAME="SMC-13". NI=NAT. //Add SCCP layer data. ADD SCCPGT: GTX=13. NUMPLAN=ISDN.

“Configuring Data for Interworking with HLR” for concepts about MTP and SCCP. 12-1 .2 Concepts Related to Data Configuration for Interworking with SCP 12.2. 12. SAU and MSOFTX3000 are connected through E1 line. refer to Chapter 17 “Configuring IN Service Data” of this manual.1 SCP Refer to Chapter 7. In the current networking. See Figure 12-1 for the networking mode and protocol stack on the interface. it is required to add SCP equipment. SCP database entity is transferred through its signaling access unit SAU (front end processor) to MSOFTX3000 instead of being connected to MSOFTX3000 directly.1 Introduction to the Chapter This chapter describes the data configuration process at MSOFTX3000 for interworking with a server control point (SCP).2.Operation Manual .2 Networking Between MSOFTX3000 and SCP To implement mobile IN services. For the information on IN service data configuration. This chapter contains the following chapters: Concepts Related to Data Configuration for Interworking with SCP Collecting Data for Interworking with SCP Configuring Data for Interworking with SCP Configuration Example 12.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 12 Configuring Data for Interworking with SCP Chapter 12 Configuring Data for Interworking with SCP 12.

4 General Configuration Procedures The procedures and commands for configuring data for interworking between MSOFTX3000 and SCP equipment are listed in Table 12-1.2. The solid lines represent the relationships with external entities. The dotted lines represent the relationships between internal commands.2.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center TDM TDM Chapter 12 Configuring Data for Interworking with SCP CAP MSOFTX3000 CAP TCAP SCCP MTP3 MTP2 MTP1 SAU SCP Figure 12-1 Networking relationship between MSOFTX3000 and SCP 12.] [Start Circuit No.Operation Manual . Table 12-1 Procedures and commands for configuring data at MSOFTX3000 for interworking with SCP 12-2 . SCP parameters MSOFTX3000 parameters ADD N7DSP ADD N7LKS Signaling network indicator SCP OPC Peer end MSC DPC [DSP index] [NI ] [DPC] [OPC] ADD SCCPDSP [LinkSet Index] [Adjacent DSP Index] ADD N7RT [NI] [DPC] [OPC] [LinkSet Index] [DSP index] [Priority] ADD N7LNK SLC ADD SCCPSSN [Link No.3 Parameter Relationship The parameter relationships for interworking between MSOFTX3000 and SCP are illustrated in Figure 12-2.] [LinkSet Index] [Signaling Link Code] [NI] [SSN] [SPC] [OPC] ADD SCCPGT ADD SCPINFO [NI ] [GT Address Information] [SPC] [SCP Address ] [SCP Address] ADD SCPPARA Local SCP address ADD SSPCAPA [Service Key] [SCP Address Index] [Service Key] Figure 12-2 Parameter relationship between MSOFTX3000 and SCP 12.

The other parameters are the internal ones of MSOFTX3000.3 Collecting Data for Interworking with SCP Before configuring data for interworking with SCP. you need to collect the interfacing data between MSOFTX3000 and the peer SCP. Table 12-2 Data for interworking with SCP Item Basic information / WCSU/ WCCU/ WSGU module number Signaling link code (SLC) and SLC sending Intra-module circuit number (E1 number/times lot number) Signaling point code Data Signaling point network indicator E. Configure SCCP 1) Add SCCP DSP 2) Add SCCP subsystems 3) Add SCCP GT 3. Configure MTP 1) Add MTP DSP 2) Add MTP link set 3) Add MTP route 4) Add MTP link 2.Operation Manual .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 12 Configuring Data for Interworking with SCP Procedure 1.164 number Signaling link Link set Intra-module link number Link type / 12-3 . In the shadowy columns are the parameters that must be negotiated between both ends for consistency or of which one end must notify the other end. 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 12. as shown in Table 12-2.

I.4 in Chapter 7 “Configuring Data for Interworking with HLR” to configure data for the SCCP layer.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 12 Configuring Data for Interworking with SCP 12. It is recommended to configure the service key. The steps to add MTP links are as follows: 1) 2) 3) 4) Add MTP DSP (ADD N7DSP). VLR and SCMG subsystems have been configured in the local office information. The service key is used for traffic statistics of IN service. Add MTP link (ADD N7LNK). 12. Command ADD SSPCAPA 12-4 . 8613900007. 12. and enter SCP number. use the LST SCCPSSN command to have a check to avoid repeated configuration.4. Add MTP link set (ADD N7LKS). 3) Add SCCP GT (ADD SCCPGT): It is only required to configure ordinary GT. The steps for adding SCCP data are as follows (MSOFTX3000 is connected with SCP through the networking mode illustrated in Figure 12-1): 1) 2) Add a DSP of SCCP (ADD SCCPDSP): Select “National Network” for the parameter “Network Indicator” of the SCCP DSP to SCP.4.2 Configuring SCCP Data Refer to sections 7. For the translation result type.4.2–7. for example. Add MTP route (ADD N7RT).1 Configuring MTP Data Refer to sections 6. As the local MSC.Operation Manual .4 Configuring Data for Interworking with SCP 12.4.2–6.3 Configuring SSP Capability This section describes how to configure the service key supported by the MSOFTX3000. Select "National Network" for NI. "ISDN (ISDN/TELEPHONY NUMBERING PLAN)" for numbering plan. select “LSPC2 (SPC)”.4.5 in Chapter 6 “Configuring Data for Interworking with BSC” to configuration data for the MTP layer. Add SCCP subsystems (ADD SCCPSSN): Add a CAP subsystem to the local MSOFTX3000.4. and add SCMG and CAP subsystems to the remote SCP.4. for GT address information.

II. "8613600006". Several capabilities in the list are not supported currently. 12-5 . [SCP Address] It refers to the SCP address information.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 12 Configuring Data for Interworking with SCP Important Note: This command is used to configure the service keys supported by MSOFTX3000. can the intelligent call corresponding to this key be triggered at the local office.4. otherwise. Command ADD SCPINFO II. In the same intelligent network. [IPSSP Capability] It is used to report the IP/SSP capability to SCP. Only when a service key is supported by MSOFTX3000 (use the LST SRVKEY command to query the configured key). the service keys should be consistent. Table 12-3 List of commands related to SSP capability configuration Command ADD SSPCAPA RMV SSPCAPA MOD SSPCAPA LST SSPCAPA Description To add SSP service support capability To remove existing SSP service support capability To modify existing SSP service support capability To list SSP service support capabilities 12. III. for example. Select ”CLEAR ALL” here. the SCP will send establish temporary connection (ETC) messages to route the IN services to the auxiliary SSP for implementation. Related Commands See Table 12-3 for the commands related to SSP capability configuration.4 Adding SCP Addressing Information I.Operation Manual . This parameter should be negotiated with SCP. Major Parameters [Service Key] It is used to define IN services. Major Parameters [SCP Address Index] It is used to identify an SCP uniquely in the system.

4. II. Related Commands See Table 12-4 for the commands related to the configuration of SCP addressing information. Table 12-4 List of commands related to the configuration of SCP addressing information Command ADD SCPINFO RMV SCPINFO MOD SCPINFO LST SCPINFO Description To add SCP address information To remove existing SCP address information To modify existing SCP address information To list SCP address information 12. Major Parameters [SCP Parameter Index] It is used to identify an SCP parameter uniquely in the system. and used to identify an SCP. III. [SCP Address Index] This parameter is defined in the ADD LKINDPOS command. I.5 Adding SCP Parameter Information This command maps “SCP Parameter Index” to “SCP Address Index” and configures the service key required by the IN service and the default call processing mode.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 12 Configuring Data for Interworking with SCP [CAP Version] It refers to the supported CAP version. [SCF ID] This parameter is defined by the network operator. Command ADD SCPPARA Important Note: This command is used to map SCP parameter indexes to SCP address indexes. [Service Key] 12-6 . and obtain the service keys required for triggering IN services and the default call processing mode.Operation Manual . This parameter should be negotiated and be consistent with that of the peer SCP.

there is no need to configure these service keys with the ADD LKINDPOS command. Table 12-5 List of commands related to SCP parameter configuration Command ADD SCPPARA RMV SCPPARA MOD SCPPARA LST SCPPARA To add SCP parameter To remove existing SCP parameter To modify existing SCP parameter To list SCP parameters Description 12. 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. [Default Call Handling] If it is set to "RELESCALL (RELEASE CALL)".Operation Manual .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 12 Configuring Data for Interworking with SCP This parameter is defined in the ADD SSPCAPA command (used for IN announcement). PPS and MVPN are common IN services for the present. III. Each service supports Chinese and English in combination. The system has default data configuration for service keys 1 and 3.1 Example Description Suppose the networking model is as shown in Figure 12-3. If it is set to "CTNUCALL (CONTINUE CALL)".5 Configuration Example 12. Their service keys are 1 and 3 respectively. 12-7 . Related Commands See Table 12-5 for the commands related to SCP parameter configuration.5. Normally. an exceptional call will be released during IN service triggering process.

RANAP /IP ISUP. refer to Table 3-14 in Chapter 3. 12-8 . The SCP information is shown in Table 12-6. For the local office information.Operation Manual .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 12 Configuring Data for Interworking with SCP SCP SMC HLR GMLC MAP/TDM MAP/TDM MAP/TDM MAP/TDM MSC Server ISUP/TDM MSOFTX 3000 BSSAP+/TDM SGSN H. which is directly connected to MSOFTX3000 through E1 line.248.BSSAP / TDM SPC 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.

SPC="D02302". ASPX=12.TS=80. CAPVER=2. LSX=12. OPC="CC0004". OPC="CC0004".164 code 8613600012 Intra-module circuit number (E1 number/timeslot number) 80 (2/16) Signaling link Link set Signaling link code (SLC) and SLC sending 0 Link type 64 kbit/s / 12 12. SSPCAPA=IPRA-1&VOICEBACK-1&SPREC-1&VOICEREC-1&TEXTTOV-1. //Add SCP data. LSNAME="SCP-12". LNKNAME="SCP-12". ADD SCCPSSN: SSNX=15.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 12 Configuring Data for Interworking with SCP 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. GTNAME="SCP-NUMBER ". NI=NAT. ADD SCCPSSN: SSNX=17.5. ADD SSPCAPA: SRVKEY=1.2 Configuration Description //Add MTP layer data. DPX=12. ADDREXP=INTER. SSN=CAP. SSNNAME="SCP-CAP". NI=NAT. SPC="D02302". ADD N7RT: LSX=12. ADD SCPPARA: SCPPARAIDX=1. SSN=CAP. SSNNAME="MSC-CAP". NI=NAT. NI=NAT. SLC=0. RTNAME="SCP-12". LNKN=2. ADD N7DSP: DPX=12. GTI=GT4.Operation Manual . //Add SCCP layer data. NUMPLAN=ISDN. OPC="CC0004". SSN=SCMG. DPC="D02302". RESULTT=LSPC2. OPC="CC0004". ADD N7LNK: MN=23. OPC="CC0004". SPC="CC0004". ADDR=K'8613600012. DPC="D02302". DPNAME="SCP-12". ADD N7LKS: LSX=12. NI=NAT. DPNAME="SCP-12". ADD SCCPDSP: DPX=12. ADD SCCPGT: GTX=12. SCFID="1". SHAREFLAG=NONE. LNKTYPE=0. 12-9 . SSNNAME="SCP-SCMG". ADD SCPINFO: SCPADDRIDX=0. ADD SCCPSSN: SSNX=16. SRVKEY=1. DCH=CTNUCALL. SPC="D02302". SCPADDR=K'8613600012. SCPADDRIDX=0.

For the concepts about MTP and SCCP.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 13 Configuring Data for Interworking with SGSN Chapter 13 Configuring Data for Interworking with SGSN 13.1 SGSN SGSN implements access control. In addition. as shown in Figure 13-1.2.2 Related Concepts 13. TDM TDM 承载 TDM based Gs MSOFTX3000 BSSAP+ SCCP MTP3 MTP2 MTP1 SGSN Figure 13-1 Networking and protocols between MSOFTX3000 and SGSN 13-1 . which may be based on TDM or IP.Operation Manual .1 Introduction to the Chapter This chapter describes the data configuration process at MSOFTX3000 for interworking with a serving GPRS support node (SGSN). 13. it creates packet data protocol (PDP) context of MS/UE to provide channels for mobile stations to access Internet. and session management functions of the MS/UE packet domain.2. refer to Chapter 7 “Configuring Data for Interworking with HLR”. In the current networking mode. This chapter contains the following sections: Related Concepts Collecting Data for Interworking with SGSN Configuring Data for Interworking with SGSN Configuration Example 13. mobility management.2 Networking Between MSOFTX3000 and SGSN MSOFTX3000 and SGSN apply the Gs interface and run in BSSAP+ protocol. it is TDM based.

The dotted lines represent the relationships between internal commands.Operation Manual . SGSN parameters MSOFTX3000 parameters ADD N7DSP ADD N7LKS [LinkSet Index] [Adjacent Point Index] ADD N7RT [LinkSet Index] [DSP index] [Priority] ADD N7LNK [Link No.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 13 Configuring Data for Interworking with SGSN 13.2.] [LinkSet Index] [Signaling Link Code] [DSP index] [NI] [DPC] [OPC] ADD SCCPDSP [NI] [DPC] [OPC] ADD SCCPSSN [NI] [SSN] [SPC] [OPC] ADD SCCPGT [NI] [GT Address Information] [SPC] ADD SGSNNO Signaling network indicator SGSN OPC Peer MSC DPC SLC SGSN number [SGSN NUMBER] Figure 13-2 Parameter relationship between MSOFTX3000 and SGSN 13-2 .3 Parameter Relationship The parameter relationships for interworking between MSOFTX3000 and SGSN are illustrated in Figure 13-2.] [Start Circuit No. The solid lines represent the relationships with external entities.

In the shadowy columns are the parameters that must be negotiated between both ends for consistency or of which one end must notify the other end.3 Collecting Data for Interworking with SGSN Before configuring data for interworking with SGSN. Table 13-1 Procedures and commands for configuring data at MSOFTX3000 for interworking with SGSN Procedure 1. The other parameters are the internal ones of MSOFTX3000. Configure MTP 1) Add MTP DSP 2) Add MTP link set 3) Add MTP route 4) Add MTP link 2.4 General Configuration Procedures The procedures and commands for configuring data for interworking between MSOFTX3000 and SGSN are listed in Table 13-1.Operation Manual . as shown in Table 13-2.164 number 13-3 . Table 13-2 Data for interworking with SGSN Item Basic information / Signaling link / WCSU module number Link set Link number SLC and SLC sending Circuit number (E1/timeslot) Link type Signaling Point Code NI of signaling point Data E. you need to collect the interfacing data between MSOFTX3000 and the peer SGSN. Configure SGSN 1) Configure SGSN number 2) Configure Gs interface network indicator 3) Modify MAP parameter table ADD SGSNNO MOD MSFP MOD MAPACCFG ADD SCCPDPC ADD SCCPSSN ADD SCCPGT ADD N7DSP ADD N7LKS ADD N7RT ADD N7LNK Command 13.2.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 13 Configuring Data for Interworking with SGSN 13. Configure SCCP 1) Add SCCP DSP 2) Add SCCP subsystem 3) Configure SCCP GT 3.

4 Configuring Data for Interworking with SGSN 13.2–7. 13. Select "NAT (National Network)" for network indicator. Add SCCP subsystems (ADD SCCPSSN): Add the local Gs subsystem. Set the translation result type to “LSPC1 (SPC+SSN)” and the newly added parameter "SSN" to "Gs". "ISDN (ISDN/TELEPHONY NUMBERING PLAN)" for numbering plan.164 coding format. 3) Add SCCP GT (ADD SCCPGT): It is only required to configure ordinary GT. Add MTP link set (ADD N7LKS). enter the peer SGSN number in E. for GT address information.2 Configuring SCCP Data Refer to sections 7.4. for example.4 in Chapter 7 “Configuring Data for Interworking with HLR” to configure data for the SCCP layer. 8613900123. Background Information None II. Because the local MSC.4.2–6. use the LST SCCPSSN command to have a check to avoid repeated configuration. VLR.Operation Manual .4.3 Configuring SGSN Number I.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 13 Configuring Data for Interworking with SGSN 13. The steps to add MTP links are as follows: 1) 2) 3) 4) Add MTP DSP (ADD N7DSP). 8613900123. 13-4 . and enter SGSN number.4.1 Configuring MTP Data Refer to sections 6. 13. Major Parameters [SGSN NUMBER] For this parameter. for example. Add MTP link (ADD N7LNK). and add SCMG and Gs subsystems for the remote SGSN. Command ADD SGSNNO III.5 in Chapter 6 “Configuring Data for Interworking with BSC” to configuration data for the MTP layer.4. The steps to add SCCP data are as follows: 1) 2) Add a DSP of SCCP (ADD SCCPDSP): Select "NAT (NATIONAL NETWORK)" for the parameter “Network Indicator” of the SCCP DSP to SGSN. and SCMG subsystems have been configured in the local office information table.4.4. Add MTP route (ADD N7RT).

you need not modify the MAP parameter table) to make MAP support the GS interface. 13-5 .4. Major Parameters [Param] For this parameter.4 Modifying Mobile Soft Parameter I. select “P106 (GS INTERFACE NETWORK INDICATOR)”.5 Modifying MAP Parameter Table I. Command MOD MSFP III. Related Commands See Table 13-3 for the commands related to SGSN number configuration.4. Background Information None II. IV. Table 13-3 List of commands related to SGSN number configuration Command ADD SGSNNO RMV SGSNNO LST SGSNNO To add SGSN number To remove existing SGSN number To list SGSN numbers Description 13. Table 13-4 List of commands related to the configuration of mobile soft parameters Command MOD MSFP LST MSFP Description To modify mobile soft parameter To list mobile soft parameters 13. Related Commands See Table 13-4 for the commands related to the configuration of mobile soft parameters.Operation Manual . [Value] Set this parameter according to the actual networking mode. Background Information Check or modify MAPACCFG (usually.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 13 Configuring Data for Interworking with SGSN IV.

IV.Operation Manual . Related Commands See Table 13-5 for the commands related to the configuration of MAP parameter table. Command MOD MAPACCFG III.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 13 Configuring Data for Interworking with SGSN II. Table 13-5 List of commands related to the configuration of MAP parameter table Command MOD MAPACCFG ADD MAPACCFG LST MAPACCFG Description To modify MAP parameter table To add MAP parameter table To list MAP parameter table 13-6 . Major Parameters [SUPPORT GS INTERFACE] Set this parameter to "Yes".

248. For the local office information. refer to Table 3-14 in Chapter 3.Operation Manual .5. The SGSN information is shown in Table 13-6.5 Configuration Example 13. 13-7 .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 13 Configuring Data for Interworking with SGSN 13. SCP SMC HLR GMLC MAP/TDM MAP/TDM MAP/TDM MAP/TDM MSC Server ISUP/TDM MSOFTX 3000 BSSAP+/TDM SGSN H.1 Example Description Suppose the networking model is as shown in Figure 13-3. which is directly connected to MSOFTX3000 through E1 line.RANAP /IP ISUP.BSSAP / TDM SPC 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.

NI=NAT. SHAREFLAG=NONE. ADD SCCPDSP: DPX=14. ASPX=14. GTI=GT4. NI=NAT. OPC="CC0004". ADD N7LKS: LSX=14. DPC="D02304".2 Configuration Description //Add MTP layer data. SSN=GS. ADD N7LNK: MN=23. TS=144. VAL="2". SSN=GS. ADD N7DSP: DPX=14. //Configure SGSN number. ADD SCCPSSN: SSNX=20. OPC="CC0004". ADD N7RT: LSX=14. LNKTYPE=0. OPC="CC0004". SSNNAME="SGSN-SCMG". MOD MAPACCFG: SUPGSIE=YES. RESULTT=LSPC1. MOD MSFP: ID=P106. 13-8 .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 13 Configuring Data for Interworking with SGSN 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. SSNNAME="MSC-GS". OPC="CC0004". NI=NAT. DPNAME="SGSN-14". LNKNAME="SGSN-14". LSNAME="SGSN-14".Operation Manual . OPC="CC0004".164 number 86136000 14 SLC and SLC sending 0 Circuit number (E1/timeslot) 144 (4/16) Link type 64 kbit/s Link set 14 13. ADD SCCPSSN: SSNX=22. NUMPLAN=ISDN. //Add SCCP layer data. SSNNAME="SGSN-GS". SPC="D02304". SSN=GS. SPC="CC0004". ADD SCCPGT: GTX=14. GTNAME="SGSN GT". NI=NAT. LSX=14. SLC=0.5. ADDR=K'8613600014. SPC="D02304". DPNAME="SGSN-14". DPC="D02304". DPX=14. LNKN=16. NI=NAT. RTNAME="SGSN-14".SPC="D02304". ADD SCCPSSN: SSNX=21. SSN=SCMG. ADD SGSNNO: SGSN=K'8613600014.

Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 14 Configuring Data for Interworking with GMLC Chapter 14 Configuring Data for Interworking with GMLC 14. The MAP protocol can be based on TDM or IP. 14-1 . An authorized subscriber accesses the mobile network through GMLC and obtains location information of a destination subscriber. For concepts about MTP and SCCP. GMLC numbers and authorized LCS client IDs are stored in HLR as subscription data.Operation Manual . GMLC interacts with MSC Server through the Lg interface to complete LCS procedure. Authorized by HLR.2 Networking Between MSOFTX3000 and GMLC The MAP protocol is used between MSOFTX3000 and GMLC.1 GMLC GMLC implements location service (LCS). This chapter contains the following sections: Related Concepts Collecting Data for Interworking with GMLC Configuring Data for Interworking with GMLC Configuration Example 14. it is TDM based. refer to Chapter 7 Interworking with HLR”.1 Introduction to the Chapter This chapter focuses on the data configuration process at MSOFTX3000 for interworking with a gateway mobile location center (GMLC). By default.2. “Configuring Data for 14. which should also be configured in MSC Server. as shown in Figure 14-1.2 Related Concepts 14.2.

Operation Manual . 14-2 .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 14 Configuring Data for Interworking with GMLC TDM承载 TDM based MSOFTX3000 MAP GMLC MAP TCAP SCCP MTP3 MTP2 MTP1 Figure 14-1 Networking and protocols between MSOFTX3000 and GMLC 14.3 Parameter Relationship The parameter relationships for interworking between MSOFTX3000 and GMLC are illustrated in Figure 14-2.The solid lines represent the relationships with external entities (GMLC) and the dotted lines represent the relationships between internal commands.2.

Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center GMLC parameter Chapter 14 Configuring Data for Interworking with GMLC MSOFTX3000 parameter ADD N7DSP [DSP index] ADD N7LKS [Link Set] [Adjacent Point Index] Signaling NI GMLC OPC Peer MSC DPC [Network Indicator] [Destination Point Code] [Original Point Code] 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.4 General Configuration Procedures The procedures and commands for configuring data for interworking between MSOFTX3000 and GMLC are listed in Table 14-1 . Table 14-1 Procedure and commands for configuring data at MSOFTX3000 for interworking with GMLC Procedure 1.] ADD ECLLCSCLT [GCI OR LAI] [LCS CLIENT ID] [Emergency Call Number] ADD ESRVCAT [EMR_SRVCI] [SCDN] Figure 14-2 Parameter relationship between MSOFTX3000 and GMLC 14.Operation Manual .2. Configure MTP 1) Add MTP3 DSP 2) Add MTP3 link set 3) Add MTP3 route 4) Add MTP3 link ADD N7DSP ADD N7LKS ADD N7RT ADD N7LNK Command 14-3 .

164 number 14-4 .3 Collecting Data for Interworking with GMLC Before configuring data for interworking with GMLC. you need to collect the interfacing data between MSOFTX3000 and the peer GMLC.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 14 Configuring Data for Interworking with GMLC Procedure 2. Configure SCCP 1) Add SCCP DSP 2) Add SCCP subsystem 3) Add SCCP GT to GMLC 3. Table 14-2 Data for interworking with GMLC Item Basic information / Signaling link / WCSU module number Link set Link number SLC and SLC sending Circuit number (E1/timeslot) Link type Signaling Point Code Data NI of signaling point E. 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 Command ADD SCCPDSP ADD SCCPSSN ADD SCCPGT ADD GMLCCLT ADD ECLLCSCLT ADD CNACLD 14.Operation Manual . as shown in Table 14-2.

The steps to add MTP links are as follows: 1) 2) 3) 4) Add MTP DSP (ADD N7DSP).4 in Chapter 7 “Configuring Data for Interworking with HLR” to configure data for the SCCP layer.2–6. The steps to add SCCP data are as follows: 1) 2) Add a DSP of SCCP (ADD SCCPDSP): Select “NAT (National Network)” for the parameter “Network Indicator”. As the local MSC.4.4. Command ADD GMLC III. “ISDN (ISDN/TELEPHONY NUMBERING PLAN)” for numbering plan. use the LST SCCPSSN command to have a check to avoid repeated configuration. Background Information A GMLC number must be authorized by the local office.2–7. for example 8613900128. Add MTP link set (ADD N7LKS). Only the authorized GMLC can invoke LCS requests or receives LCS reports.4.4. VLR. 14-5 . Add MTP link (ADD N7LNK). 14. and enter GMLC number for GT address information.4.4. Add MTP route (ADD N7RT). Major Parameters [GMLC Number] It is an authorized GMLC number. 14. Add SCCP subsystems (ADD SCCPSSN): Add SCMG(SCCP Management Subsystem)and GMLC subsystem to the remote GMLC.4 Configuring Data for Interworking with GMLC 14. 3) Add SCCP GT (ADD SCCPGT): Select “NAT (National Network)” for NI.5 in Chapter 6 “Configuring Data for Interworking with BSC” to configuration data for the MTP layer. II.1 Configuring MTP Data Refer to sections 6.4.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 14 Configuring Data for Interworking with GMLC 14.Operation Manual .3 Adding GMLC Number I.2 Configuring SCCP Data Refer to sections 7. and SCMG subsystems have been configured in the local office information table.

Background Information This command is used to configure the table of corresponding relationships between GMLC authorized clients and GMLC numbers. which is already defined in command ADD GMLC. It must be pre-defined in the ADD GMLC command. Table 14-3 List of commands related to GMLC number configuration Command RMV GMLC LST GMLC Description To remove an existing GMLC number To list the configured GMLC number 14. and one GMLC can be used by multiple users. Enter parameters here. Related Commands See Table 14-4 for the commands related to the configuration of client GMLC information.4. II. If an LCS request does not contain a GMLC number. Each client ID can correspond to one authorized GMLC number only.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 14 Configuring Data for Interworking with GMLC IV. Major Parameters [GMLC Client ID] It is a GMLC client ID. You can query the corresponding GMLC number at the local office by searching for the client ID. Enter parameters here. 14-6 . Command ADD GMLCCLT III. [GMLC Number] It is a GMLC number.4 Adding Client GMLC Information I. Related Commands See Table 14-3 for the commands related to GMLC number configuration. namely the LCS client. MSC can use this table to obtain the GMLC number and return the LCS result to GMLC for related processing. IV.Operation Manual .

It has been defined in the command ADD GMLCCLT. Major Parameters [Emergency Call Number] It is the called number in an emergency call. 14-7 . II. your location information will be reported to the designated LCS Client. When you initiate an emergency call in a certain service area. III. 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 system will report the location information to GMLC. If LCS is invoked in an emergency call. when the location procedure completes. Enter parameters here. [GCI OR LAI] It refers to global cell identification (GCI) or location area identity (LAI). Background Information It covers the configuration of the corresponding relationship between authorized LCS Client ID and emergency call numbers. [LCS Client ID] It specifies the ID of the LCS client.5 Adding Emergency Call LCS Client I. that is “GMLC CLIENT ID”. Enter parameters here.Operation Manual .4. 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.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 14 Configuring Data for Interworking with GMLC 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 14. It must pre-defined in the command ADD LAIGCI.

4. [Emergency Call Observe Flag] The flag indicates whether an LCS procedure has been invoked to locate a subscriber initiating an emergency call.6 Adding Called Analysis Data (Optional) I. Command ADD CNACLD III. It is associated with the emergency call number in the ADD ECLLCSCLT command. refer to Chapter 15 “Configuring Number Analysis Data”. Table 14-5 List of commands related to the configuration of GMLC numbers for emergency calls Command ADD ECLLCSCLT MOD ECLLCSCLT RMV ECLLCSCLT LST ECLLCSCLT Description To add a LCS Client information for emergency calls To modify the attributes of the existing LCS Client information for emergency calls To remove an existing LCS Client information for emergency call To list the configured LCS Client information for emergency calls 14.Operation Manual . Related Commands See Table 14-5 for the commands related to the configuration of GMLC numbers for emergency calls.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 14 Configuring Data for Interworking with GMLC IV. Major Parameters [Call Prefix] You need to configure the call prefix that the emergency call number corresponds to. Background Information None. 14-8 . II. For other description.

BSSAP / TDM SPC 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. SCP SMC HLR GMLC MAP/TDM MAP/TDM MAP/TDM MAP/TDM MSC Server ISUP/TDM MSOFTX 3000 BSSAP+/TDM SGSN H.5.1 Example Description Suppose the networking model is as shown in Figure 14-3.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 14 Configuring Data for Interworking with GMLC 14.Operation Manual . which is interconnected with MSOFTX3000 through E1 cable. refer to Table 3-14 in Chapter 3.248. 14-9 . The information about GMLC is shown in Table 14-6. For the information of the local office.5 Configuration Example 14.RANAP /IP ISUP.

ADD SCCPDSP: DPX=15. OPC="CC0004". OPC="CC0004". OPC="CC0004". SSNNAME="GMLC-GMLC". SPC="D02305". ADD GMLC: GMLC=K'8613600015. //Add LCS data. DPNAME="GMLC-15". ASPX=15. GTI=GT4. NI=NAT. LSNAME="GMLC-15". SPC="D02305". DPC="D02305". NI=NAT. SSN=SCMG. ADD SCCPSSN: SSNX=24. LNKTYPE=0. NUMPLAN=ISDN. ADD CNACLD: P=1. 17 Link type 64 kbit/s / 14. ADD SCCPSSN: SSNX=23. OPC="CC0004". ADDR=K'8613600015.164 number 8613600015 Intra-module link No. ADD N7DSP: DPX=15. //Add SCCP layer data. MAXL=6. LNKNAME="GMLC-15". GTNAME="GMLC GT". DPX=15. ADD N7LNK: MN=23. SSN=GMLC. ECOS=YES. SPC="D02305". 176 (5/16) E. NI=NAT. SLC=0. RESULTT=LSPC2. TS=176.5. SSNNAME="GMLC-SCMG". GMLC=K'8613600015. MINL=3. PFX=K'113. RTNAME="GMLC-15".Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 14 Configuring Data for Interworking with GMLC Table 14-6 GMLC information table Item Basic information / Signaling link Signaling point code D02305 WSGU module No. LNKN=17. ADD N7RT: LSX=15. DPNAME="GMLC-15". CSTP=BASE.2 Configuration Description //Add MTP layer data. ADD ECLLCSCLT: DN=K'113. CSA=lc. 23 SLC and sending 0 SLC Data NI of signaling point National Link set 15 Intra-module E1 timeslot No. SHAREFLAG=NONE. ADD GMLCCLT: CLTID=K'0. LSX=15. CLTID=K'0. ADD SCCPGT: GTX=15. GCI="460000003". DPC="D02305".Operation Manual . NI=NAT. ADD N7LKS: LSX=15. 14-10 .

1 Call Source. while one call source should correspond only to one DN set. the system can analyze an identical called prefix differently. the MSOFTX3000 will check the trunk group data to obtain the call source code.1. Each call source has an integral number. One DN set may correspond to multiple call sources. Analysis of call source refers to searching the call source code according to the physical port of the incoming equipment. the call prefix that is most similar to the called number will be found among all the call prefixes. called call source code. based on which different processing methods are decided. 2) If an incoming call is connected to the MSOFTX3000 through the trunk (that is.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data Chapter 15 Configuring Number Analysis Data 15. while the called number is 13900278310. and it will act as a basis to determine the attributes such as service type and route selection code. The analysis process is as follows: 1) If an incoming call is connected to the MSOFTX3000 through A or Iu interface (that is. the MSOFTX3000 will check the associated local area identification (LAI) and cell global identification (CGI) based on BSC/RNC DPC to obtain the call source code. II. the system will match the number with the call prefix 13900278 automatically. The MSOFTX3000 adopts the principle of the longest number matching while analyzing the called numbers. incoming calls may come from A interface. It has developed into a flexible means to analyze called prefixes. Dialed Number Set. the cut starts with the first digit of the called number. Call Source and Call Source Code Call source refers to a subscriber or incoming trunk originating a call. By introducing the dialed number set. The call source code reflects the call source. 15-1 . According to this principle. For example. It is associated with the called number prefix. Call Prefix Call prefix is a number segment cut from a called number. Route Selection Code I. Iu interface and incoming trunk.1 Related Concepts 15. Dialed Number Set Dialed number set (DN set) is a set of dialed numbers/prefixes. III.Operation Manual . the call is originated by a mobile subscriber in the local office). the call is originated by a PSTN subscriber or subscriber of other mobile offices). For the MSOFTX3000. if the configured "Call Prefixes" include 139 and 13900278. Its length is not longer than the called number.

usually the wildcard is 254. replace fields that have wildcards with wildcards in sequence. The route selection source code is related to the calling party. representing any call prefix. such as route reselection. Most popular wildcards used in number analysis are "eeeeeeee" and "65534". the latter is the wildcard of call source. Failure Source Code and Failure Processing The failure source code numbers different processing methods for the connection failure of calls from different call sources. Different causes may correspond to different connection failure processing methods. or triggering NCSIDP4.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data IV. For call source. A route selection code indicates a routing strategy for calls with a certain prefix. The local subscribers with different outgoing strategies can be defined as different call sources and assigned with different route selection source codes. Table 15-1 Wildcard matching Call source 65534 2 Call prefix 1390 13 15-2 . Route Selection Source Code and Route Selection Code The route selection source code identifies different outgoing routing strategies of different call sources. If no matched record is found. the MSOFTX3000 queries the table with call source and prefix. Re-query. the MSOFTX3000 uses wildcards to fulfill call processing. Wildcards Usually. It queries related number analysis tables and performs analyzing and processing according to the querying results.Operation Manual . in Table 15-1 (with two records). In addition. the MSOFTX3000 matches numbers in the maximum prefix mode. while the route selection code is related to the called party. V. representing all call sources. It will be used together with the route selection source code to select the outgoing route during route analysis. The matching of wildcards is in the following way: Query the corresponding record by specific field (such as prefix and call source code) first. For example. signal tone playing. VI. number type and service attribute. The former is a call prefix. The route selection source code corresponds to the call source.

If HLR returns a roaming number or forwarded-to number. When “Call source” is replaced with a wildcard. the MSOFTX3000 can match neither record in the table by using a specific field. the MSOFTX3000 will obtain the route information of the called party from HLR. 15-3 . You can set the service check type. the MSOFTX3000 will match the second record without using a wildcard for processing the call. for a call whose call source is 2 and call prefix is 1390000.1. that is.1. In the MSOFTX3000. 2) A called number is converted through the prefix processing process.1. the local office confirms that the called number is received completly and promptly sends ACM back to the previous office before the response of called party. and conversation duration restriction. the MSOFTX3000 will conduct a second number analysis (that is.4 Service Check Check whether a calling subscriber is authorized to make the corresponding calls. the MSOFTX3000 matches the first record. the secondary number analysis is necessary in order to determine the outgoing route.Operation Manual . If the processing type is "reanalysis” (conduct number analysis again). The secondary number analysis can be done in the following two ways: 1) If a called number is an MSISDN after analysis. it will analyze the call prefix again according to the number that HLR returned) to find the outgoing route. Refer to “Configuring Number Conversion Data” in this chapter for details.3 Number Conversion The MSOFTX3000 supports 32 kinds of number conversion. the MSOFTX3000 will also carry out the secondary number analysis.2 Secondary Number Analysis If a number is changed during the number analysis process.5 EARLY ACM During the call connection.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data According to the wildcard matching princilple. this can be avoided: Upon receiving Initial Address Message (IAM) from the previous office. 15. check mode. to analyze the converted number with the call prefix analysis table to find the outgoing route. This is called the EARLY ACM procedure. 15. This is because the second record has specific fields for call source and call prefix. 15.1. 15. For a call whose call source is 0 and call prefix is 1390000. a call may be disconnected as the previous office has not received an address complete message (ACM) within a certain duration due to long time of signaling transmission within the call.

the first called number is called the original called number. 15. while that of the forwarded-to number is accomplished only at the office where the forwarding is initiated. Connected number: When a call is originated from the local office (originating office) and is forwarded at terminating office B to office C.Operation Manual . Connected Number A forwarded-to number: When the local office is the terminating office. the format control of the received forwarded-to number may be accomplished at the call terminating office. Call originating office Connected number Call terminating office Forwarded-to number Call forwarding office Format control of connected number Format control of forwarded-to number Figure 15-1 Procedures for number format control in a forwarding call 15. Upon confirming that the address is complete. 15-4 . the connected number received can also be converted so as to meet the requirement of the calling line identification presentation (CLIP) service. CCB sends Alerting information to the trunk side. if a call is forwarded at the local office. as shown in Figure 15-1.6 Forwarded-to Number. At the call originating office.2 Procedures of Number Analysis Processing The following introduces the number analysis processing of the MSOFTX3000 in a normal call procedure. the number to which the call is forwarded is called the forwarded-to number at the local office. Number analysis processing includes three parts: incoming number pretreatment. The format control of the connected number is accomplished at the call originating office. and the number is sent to the call originating office in the form of a connected number. Original Called Number. the final called number sent by terminating office B to the local office is the connected number. If the calling party has subscribed to the connected line ddentification presentation (CoLP) service. number analysis and outgoing number preprocessing.1.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data This function is generally realized through Call Control Block (CCB). Original called number: When a call is forwarded for once or times. as shown in Figure 15-2. which in turn sends ACM to the peer office so as to start the EARLY ACM procedure.

1 Incoming Number Pretreatment During incoming number pretreatment. It is required before every number analysis. it is meant for incoming numbers in the wide sense. For example.Operation Manual . for example. 15. Ensure the completeness of numbers entered This is to adapt to channel associated signaling such as R2. and the processing before analysis of numbers incoming from the trunk side. implementing receive-number delay in the incoming number processing part by office direction or call prefix. the processing before number analysis when MAP retrieves the roaming number.2. There may be some number processing procedures before and after number analysis. Therefore. there may be a called number preprocessing procedure before number analysis. These procedures will be explained later. 15-5 . the processing of the number coming from the CM side. Incoming number processing is not invoked merely by certain incoming trunks. the processing before number analysis when MAP retrieves the redirecting number. numbers entered throguh various interfaces will be initially analyzed and converted to implement the following functions: Normalize the format of incoming calls of different sources or modify the DN set called.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center CM Incoming Number Preprocessing ISUP TUP TK PRA BICC MAP SSF Forwarded-to side Internal Number Analysis Chapter 15 Configuring Number Analysis Data ISUP TUP TK PRA BICC Outgoing Number Preprocessing Figure 15-2 Processing of number analysis Note: Outgoing number processing will be used for outgoing trunk.

Number conversion can be done either with the attributes of the specified number or according to the specific data configuration. The type of outgoing number processing is relatively simple. called number preprocessing and number conversion configuration. preprocessing data of outgoing numbers. The configuration of IN call processing data is not included here. Outgoing number processing does not affect the number format of the exchange and bills.1 Overview of Configuration Procedures This section introduces the configuration of data tables in ordinary call flow. The procedures are shown in Figure 15-3.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data 15. 15. the MSOFTX3000 requests the roaming number of the subscriber from HLR. 15.3 Outgoing Number Preprocessing Outgoing number processing is done during trunk outgoing according to corresponding trunk group numbers.2 Number Analysis After incoming number pretreatment or other number pretreatment is the main procedure of the called number analysis. outgoing routing data of number analysis. it differs from incoming number processing and number conversion of number analysis.3. making the format of the outgoing number conformant with inter-office number transfer specifications. preprocessing data of incoming numbers. This procedure processes various results of number analysis in different modes: For a local MSRN. 15-6 . Based on the number analysis of the MSOFTX3000 introduced above.2.2.3.Operation Manual . the MSOFTX3000 performs routing and leads the number out of the office. For an ordinary MSISDN. 15. For an ordinary PSTN or an MSRN of other offices.3 Configuration Procedures 15. In this respect.2 Procedures for Configuring Number Analysis Preset Data Configuration of number analysis preset data comprises call source configuration. the MSOFTX3000 pages the called mobile subscriber. Outgoing number processing is to normalize numbers. and other number data. the data configuration of number analysis can be divided into five parts: preset data for number analysis.

Number conversion configuration can be referenced through number conversion indexes. incoming original called number correlation processing data configuration and incoming number pretreatment data configuration. The procedures are shown in Figure 15-4. You can close the original called number preprocessing table with software parameters. Called number analysis is to analyze called numbers according to call sources. 15. The called number preprocessing table may not be configured. address attributes of called numbers and the roaming type of callers.3. The original called number preprocessing table may not be used during incoming processing. Note: Called number preprocessing can be replaced with incoming number pretreatment (the called number pretreatment table will be introduced in later sections).3 Procedures for Configuring Incoming Number Pretreatment Data The configuration of incoming number pretreatment data comprises incoming calling number associated process data configuration. 15-7 . and move the contents of the table to the incoming number pretreatment table. Currently. incoming original called number correlation processing table and incoming number pretreatment table. Number conversion configuration is to set number analysis routing and determine the mode of number conversion in the follow-up number analysis. The configuration of the called number preprocessing table is no longer introduced in this manual.Operation Manual . and determines whether to perform called number conversion and whether to change the DN set.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Call source configuration Chapter 15 Configuring Number Analysis Data Called number pre-processing Number convesion configuration End Figure 15-3 Procedures of number analysis preset data configuration Call source configuration is used to designate call sources to various trunk groups and LAs and cells. The corresponding data configuration tables are incoming calling number associated process table. it is recommended to replace the called number preprocessing table with the incoming number pretreatment table.

15-8 . and called numbers changed in IN procedure. 15. the purpose of incoming number pretreatment data configuration is to normalize called numbers of incoming calls (from trunks) and Mobile-Originated (MO) calls. and the flexible number conversion processing over incoming numbers according to calling/called numbers and original called numbers.3. the configuration also helps to realize the receive-number delay according to a certain call prefix. Besides. 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.4 Procedures for Configuring Number Analysis and Routing Data The configuration comprises the parts as shown in Figure 15-5.Operation Manual . MSRNs or forwarded-to numbers transmitted by MAP signaling. In this way.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configure Incoming Original Called Number Correlation Processing Data Chapter 15 Configuring Number Analysis Data Configure Incoming Calling Number Correlation Processing Data Configure Incoming Number Preprocessing Data Figure 15-4 Procedures of incoming number pretreatment data configuration During the above procedures.

This part completes the functions of call analysis and routing. Call authority check data is used to set that a certain class of subscribers is only allowed to dial specified numbers. but also that of entire number analysis data configuration. It is also used to play announcements to the caller when the call is forwarded in the local office.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configure call prefix data Chapter 15 Configuring Number Analysis Data Enhanced route processing? Y Configure enhanced route processing data Check call authority/original called number corelation? Y Check call authority/ configure original call corelation processing data Configure call authority check data Configure service check data Calling number analysis? Y Configure calling number analysis data Configure calling number attribute processing data Configure calling number attribute analysis data Need number initial processing or not? Y Configure special DN processing data Configure failure processing data End Figure 15-5 Procedures of number analysis and routing data configuration The role of each part of data configuration is as follows: Call prefix data configuration is not only the core of number analysis and routing data configuration. Enhanced route processing data is used to select different outgoing route for the same call prefix. 15-9 . or that some subscribers are not allowed to dial certain numbers.Operation Manual . with different call types or different number length.

making the format of the outgoing number conformant with inter-office number transfer specifications. DN processing helps to conduct failure processing over the call in which the related call prefix is dialed. This index corresponds to the calling feature index in the calling feature analysis table. 15-10 . which form a keyword–calling feature index. The type of outgoing number processing is relatively simple. announcement playing or to reanalyze numbers. In this respect.3.5 Procedures for Configuring Outgoing Number Preprocessing Data Outgoing number processing is done during trunk outgoing according to corresponding trunk group numbers. Outgoing number processing is to normalize numbers. Failure processing data configuration helps to define the processing modes when both call authority check and DN processing are failed. Calling subscriber attribute analysis is used for special processing when the caller has some special serivce attributes (for example. 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. Outgoing number processing does not affect the number format of the exchange and bills. calling feature analysis and calling feature processing help to normalize the calling numbers of incoming calls from trunks. Calling subscriber attribute processing is used to map a subscriber’s special service attributes respectively to a series of keywords. whether the subscriber has subscribed to forwarding and service barring services). Data configuration is shown in Figure 15-6.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data Service check data is used to check whether the caller has the corresponding call authority. Outgoing number processing is implemented in three processes. Calling number analysis is used to process information such as calling numbers. it differs from incoming number processing and number conversion of number analysis. Calling number analysis. to select different routes according to calling features). 15. Number conversion can be done either with the attributes of the specified number or according to the specific data configuration. or to conduct various processing over different calling parties who dial the same call prefix (for example. Number conversion is performed to the sent calling number and called number according to the calling number and the original called number.Operation Manual .

But because that outgoing number preprocessing is more powerful than trunk group bearer data configuration. refer to Figure 15-7.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data Configure Outgoing Calling Number Correlation Processing Data Configure Outgoing Original Called Number Correlation Processing Data Configure Outgoing Number Preprocessing Data Figure 15-6 Procedures of outgoing number preprocessing data configuration The role of each part of data configuration is as follows: Outgoing calling number correlation processing data are used to convert the transmitted calling/called numbers and original called numbers or redesignate their formats according to calling number prefixes and their related attributes. If you need to convert calling/caller number according to trunk group number and call prefix. it is recommended to use outgoing number preprocessing. Here. outgoing trunks. Note: Original called correlation parameters and data are configured only when a call is forwarded. 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. 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.Operation Manual . 15-11 . by configuring trunk group bearer data. Outgoing number preprocessing data are used to convert calling/called numbers and original called numbers or redesignate their formats according to call sources. we introduce trunk group bearer data configuration in brief. requiring number conversion to other numbers during the call according to the original called number or to the original called number. called prefixes and related attributes.

Figure 15-8 shows the specific sequence. II.Operation Manual . MAP interface number processing data configuration. CLIP called correlation processing data should be configured. the system will initiate the call. The system can also control the formats of calling numbers to meet the requirements of CLIP service. Background Information Besides its powerful number normalization functions based on number analysis. caller identification processing data configuration. the system will call them with the calling number presented. Tables related to the configuration include CLIP Processing table and CLIP Called Correlation table.6 Other Number Data Configurations I.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configure trunk group bearer data Chapter 15 Configuring Number Analysis Data Configure trunk group bearer index data End Figure 15-7 Procedures for trunk group bearer data configuration 15. Configure CLIP Called Correlation Processing Data Configure CLIP Preprocessing Data Processing Data Figure 15-8 Procedures of calling number correlation processing data configuration 15-12 . CLIP processing data should be configured. auxiliary number processing data configuration and bill processing data configuration. For those who have subscribed to CLIP. Format Normalization of Caller Identification If the MSRN analysis result returned from the HLR shows that the called party is a local office subscriber. To realize this function. only CLIP processing data needs to be configured. If calling number conversion is associated with called subscriber attribute. In general. the system offers other number conversion functions. for example.3. both of which are associated through parameter [Callee Number Correlation Index].

Background Information This command is used to set a call source code according to calling party attributes. Command ADD CALLSRC III. V. Control of Bill Number Format (ADD BILLPROC) The system can convert the calling number. and trunk group data. IV. bill type and number prefix. Forwarded-to/Connected Number Normalization When the call originated at the local office is forwarded at the terminating office. II.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data III.1 Adding Call Source I. Major Parameters [Call Source] It is also called [Call Source Code].Operation Manual . outgoing route selection for calls to the same prefix.4. and number pre-analysis mode. It is recommended to group the local office subscribers and trunk groups without special requirements to the same call source. Cells or trunks having the same calling party call attributes are classified into the same call source. the local office can convert the connected number returned and send it back to the calling subscriber who has subscribed to CoLP service. 15. the local office can control the format of the forwarded-to number to be returned and send it back to the call originating office. Corresponding call source codes must be added before configuring number analysis or route analysis. Call source is referenced in the LAI/CGI table. Normalization (including number conversionation and number attribute designation) of forwarded-to/connected numbers can be realized through the configuration of auxiliary number conversion data. route analysis data.4 Configuring Preset Data Before Number Analysis 15. These attributes include the DN set. called number and third party number in bills and limit their length according to call source. Normalization of MAP Interface Number MAP interface number processing data are used to normalize the format of the called number contained in the Send Routing Information (SRI) message when a mobile subscriber is called and the system sends SRI message to the HLR of this subscriber. failure processing mode. When the call is forwarded at the local office. Different call source codes must be set according to different call attributes of the caller. 15-13 .

make sure that the index has been defined in PPS Subscriber Number Segment table. this parameter is set to "255". If the route selection methods are different.Operation Manual .1 Second)] If the office direction that the call source corresponds to is not the channel associated signaling office direction. [DnSet] Dialed number set (DN set) is used to categorize subscribers uniformly according to different understandings of the called number (or call prefix). Usually. Suppose the subscribers of two call sources belonging to the same DN set dial the same outgoing prefix of the DN set. this parameter need not be configured. For details. [Intelligent Number Local ACode Index] If Overlay mode is not adopted for the outgoing IN calls at the local office. Therefore. Callers with different call attributes have different route selection source codes. the default value. The data is cited during route analysis. [Toll Area Code] The toll area code of the area where the related call source is located. the value of the parameter is the area code. When the MSC triggers the IN service. [Route Selection Source Code] The code is used to classify route selection methods of subscribers of this call source. the value of this parameter will be sent to the SCP as "Location Number". Before configuring this parameter. calling numbers from different call sources can be differentiated through the setting of this parameter. If an MSC is in charge of multiple areas. Set one DN set for one office usually. [Fail Source Code] The code is used to classify call sources according to the failure processing method and cited by the failure processing table. If Overlay mode is adopted for the outgoing of IN calls at the local office. Values set for this parameter must contain no toll area code prefixes.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data 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). route selection source code and call source code are the same. any setting error may affect the normal operation of IN service. If the home MSC covers one area only. [Receive_Number Delay Value (0. [Prereceive Number Digits] Start the number analysis after "N" digits of the number are received. When the peer office 15-14 . refer to Chapter 17 “Configuring IN Service Data”. different route selection source codes can be allocated to the two call sources. It is numbered from 0. 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.

Major Parameters [Number Conversion Index] It serves as the index identifying records in Number Change table.4. [Number Conversion Type] 15-15 . Command ADD DNC III. 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.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data communicates with this office through channel associated signaling. Before converting a number. Other data tables cite corresponding records in Number Conversion table through this parameter. this parameter must be set in the corresponding call source data of the peer office so as to ensure the integrity of numbers received. Background Information This command is used to add records to Number Change table which defines various types of transformation modes performed by the MSOFTX3000 over numbers. Table 15-2 List of commands related to the configuration of call source code Command LST CALLSRC ADD CALLSRC MOD CALLSRC RMV CALLSRC To list call source code To add call source code To modify call source code To remove call source code Description 15.Operation Manual . IV. the MSOFTX3000 queries this table according to the number conversion index in other data tables so as to obtain the specific conversion mode. Related Commands See Table 15-2 for the commands related to the configuration of call source code.2 Configuring Number Conversion Data I.

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 .Operation Manual .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data There are 32 types of conversions in this parameter.

Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data 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 Conversion Start Position Number Conversion Length New Number Other Conversion Number Source New Number Address Nature ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ 15-17 .Operation Manual .

Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data 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 Conversion Start Position Number Conversion Length New Number Other Conversion Number Source New Number Address Nature ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ 15-18 .Operation Manual .

[Designated Chars] 15-19 .Operation Manual .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data 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 Conversion Start Position Number Conversion Length New Number Other Conversion Number Source New Number Address Nature ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ ⊕ [Designated Chars Length].

deletion of substrings to or from the current number and the modification of this number in positive/inverted sequence of the designated position. [New Number Address Nature] This parameter is valid only when [Number Conversion Type] is set to "Change number address attribute". you can change the number address attribute without changing number contents. When it is valid. Through this parameter. and enter the value of [New Number]. you can set [Number Conversion Length] as 4. to realize the "Insert number after designated character" function. etc. changing number in inverted sequence. [New Number] Number after change. if you need to delete four digits starting from the second digit. so as to accomplish the insertion. During the conversion. 15-20 . For example. Therefore. the length is calculated starting from the first digit after the designated character string. it is required to determine the sequence of conversions over this number based on these conversion sources. the number processing capability of the system has been enhanced.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data They are used together to determine the conversion (extracting number in positive/inverted sequence. In this way.Operation Manual . [Conversion Start Position] It is used to set the start position (counting from position 0 of the number) of the number conversion. set this parameter to "True". the designated new number can be added to the original number after the character string "2xxx". the priority of other sources is higher than the current one. [Other Conversion Number Source] It helps to apply the strings cut from other numbers to the current number conversion. set [Designated Chars Length] to "4" and [Designated Chars] to "2". [New Number Priority Flag] It sets the priority of the new number generated from the conversion. To set higher priority for the current conversion. when a number contains "2xxx". the conversions for numbers in CAP interface signaling can be accomplished according to several number conversion sources. there may be more than one conversion sources available for the conversion of the same number. [Number Conversion Length] If the designated character string has been given. For example. By default.) of numbers of certain length containing the designated character string.

It can convert the CLIP format. modification (by inverted/positive sequence). add substring extracted from other number to the suffix of calling/called number. IV. called number type. It can convert outgoing forwarded-to numbers and connected numbers. It is hard to make an arrangement for the MSOFTX3000 to perform various types of number conversion in sequence. no conversion will be conducted. Extract substring from calling/called number according to trunk group type (TUP/ISUP). the current number cannot be modified or deleted. add substring to the end of a number whose length is not specified or replace this number with another number. called number type (local/foreign/simulation network and PSTN) and calling subscriber type (local/foreign/simulation network and PSTN) when sending calling/called numbers. deletion (by inverted/positive sequence).Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data Note: Number Change table must be first defined according to the principle of “referenced contents first defined. You can add records for corresponding types of number conversion before configuring data of new types of number conversion. 15-21 . In this way. Related Commands See Table 15-4 for the commands related to the number conversion. Support the insertion. It supports number format conversion for the CAP signaling interface. deletion (by inverted/positive sequence). called number and original called number. and number attributes for different stages of a call (incoming stage/outgoing stage). When the parameter “Number Conversion Index” is set to "0" by default. That is. Support the insertion.Operation Manual . original called number type and calling subscriber type. and extraction (by inverted/positive sequence) of numbers according to the designated character. modification (by inverted/positive sequence) and extraction (in inverted/positive sequence) according to the designated position. Process a number whose length is not specified." because it may be invoked in every process of number analysis. Additional remarks: The MSOFTX3000 can convert calling number. the system provides flexible conversion of various types of number and number attributes: Extract substring from a number. Add the saved substring to a number according to trunk type (TUP/ISUP).

the MSOFTX3000 will not start incoming number pretreatment procedures until the complete number has been received. that is. "Calling Subscriber Prefix". Background Information This command is used to add records to Incoming Calling Number Associated Process table. II.Operation Manual . "Calling Number Address Attribute". Command ADD INCLRIDX III. If the receive-number delay interval has been set in Incoming Calling Number Assicaited Process table. [Calling Subscriber Prefix]. called numbers and original called numbers according to calling numbers and their attributes related. Then the MSOFTX3000 obtains the conversion indexes of calling/called/original called numbers. Major Parameters [Calling Number Associated Process Index] It is used to identify a calling number correlation processing record. there should be corresponding records of these values. the MSOFTX3000 queries Incoming Calling Number Assicaited Process table according to this index. [Calling Number Max. Length] 15-22 . [Calling Subscriber Type].1 Configuring Incoming Calling Number Associated Process Data I. which sets the conversions of calling numbers.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data 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 15. [Calling Number Address Attribute]. Upon obtaining the "Calling Number Associated Process Index" from Incoming Number Pretreatment table.5. and "Calling Number Max. The table also contains the information of receive-number delay interval and new DN set. Length". Values set for this parameter referenced in Incoming Number Pretreatment table must be defined in Incoming Calling Number Assicaited Process table. and normalizes these numbers according to the conversion indexes obtained.5 Configuring Incoming Call Number Preprocessing Data 15. "Calling Subscriber Type".

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. The MSOFTX3000 queries Incoming Number Pretreatment table and obtains the "Calling Number Associated Process Index". 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 corresponding number can be converted. Therefore. the system will set "Receive-Number Delay Processing Flag" as "Yes". It is configured only when the preprocessing of the incoming number is associated with the calling feature.Operation Manual .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data They determine the relevant attributes of calling number. then queries Incoming Calling Number Assicaited Process table according to the index and the relevant attributes of calling subscriber who originates the call. 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. Note: Incoming Calling Number Assicaited Process table serves as an auxiliary table of Incoming Number Pretreatment table. The setting of this parameter is the same as that of [Receive-Number Delay Interval] in Call Source table. The MSOFTX3000 conducts receive-number delay processing once at most. even when [Receive-Number Delay Interval] is set to "Yes" during the subsequent table-query procedures. In this case. 15-23 . [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. [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. If the processing has been accomplished in call source analysis. [Calling Number Conversion Index] It is set only when conversions are to be conducted over the calling number 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. the receive-number delay processing will not be conducted.

the MSOFTX3000 obtains the conversion indexes of calling/called/original called numbers from Incoming Original Called Number Correlation Processing table. All original called number associated process indexes referenced in Incoming Number Pretreatment table must be defined in Incoming Original Called Number Correlation Processing table. that is. This table is used to set the conversions performed over calling/called/original called numbers according to original called number and its attributes related. each index must correspond to a record in this table. II.Operation Manual . and to define new DN set.5. the original called number address nature. And according to this index. [Original Called Number Address Nature]. Based on the conversion indexes. Table 15-5 List of commands related to incoming calling number correlation data Command LST INCLRIDX ADD INCLRIDX MOD INCLRIDX RMV INCLRIDX 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 15. Background Information This command is executed to add records to Incoming Original Called Number Correlation Processing table.2 Configuring Correlation Processing Data of Incoming Original Called Number I. Major Parameters [Original Called Number Associated Process Index] It is used to identify an original called correlation processing record. [Original Called Prefix]. the MSOFTX3000 normalizes calling/called/original called numbers accordingly. The MSOFTX3000 obtains the [Original Called Number Associated Process Index] from Incoming Number Pretreatment table. Command ADD INORICLDIDX III. the original called prefix.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data IV. [Original Called Number Maximum Length] 15-24 . and the original called number maximum length. Related Commands See Table 15-5 for the commands related to incoming calling number correlation data.

Related Commands See Table 15-6 for the commands related to incoming original called number correlation 15-25 . the MSOFTX3000 can convert calling/called/original called numbers involved in current call according to the relevant attributes of the original called party. 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. The MSOFTX3000 obtains original called number associated process index from Incoming Number Pretreatment table. [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. [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. IV. [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. [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. In this way.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data They are used to specify the relevant attributes of the original called number.Operation Manual . then queries Incoming Original Called Number Correlation Processing table according to the relevant attributes of the original called party. Note: This table is an auxiliary table of Incoming Number Pretreatment table.

Background Information This command is used to add records to Incoming Number Pretreatment table.3 Configuring Incoming Number Pretreatment Data I. the MSOFTX3000 directly converts the corresponding number according to the conversion index of calling/called/original called number in this record. called prefix. [Call Source] 15-26 . They can also be MSRNs or forwarded-to numbers transmitted by MAP signaling.Operation Manual . The MSOFTX3000 queries Incoming Number Pretreatment table according to call source code. When both indexes are valid. These called numbers may be involved in incoming trunk calls and MO calls. the MSOFTX3000 queries Incoming Calling Number Assicaited Process table and Incoming Original Called Number Correlation Processing table respectively according to these indexes to obtain more number normalization information. called number address attribute and max.5. After the normalization. to obtain the incoming calling number associated process index and incoming original called number associated process index. length of called number. the table also provides the capability for receive-number delay processing based on called prefix to ensure that numbers are inputted completely and processed correctly. When both indexes are invalid. their formats can meet the internal specifications in the MSOFTX3000. Set different processing modes according to different call sources through this parameter.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data 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 15. Besides. Major Parameters [Call Source Code] Requirements for incoming number pretreatment may vary with different call sources. and called numbers changed in IN procedures. II. Command ADD INNUMPREPRO III. call source. The table is used to normalize called numbers.

Operation Manual . [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. its called number address attribute should be converted. The principle of "maximum matching" is adopted for prefixes in system number analysis. If the called number entered meets the requirements. Wide matching is applied here. indicating the minimum length of the called prefix. 15-27 . so that the system can provide different processing capabilities in terms of called address attributes. it is required in the number analysis procedures that the called number should be of international number format. 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. and Call Forwarding (CF). Then corresponding processing will be conducted according to the result. for calls from the following sources: trunks (including TUP/ISUP/R2/PRA/BICC). MAP. Be sure that the indexes used have been defined in these two tables. [Calling Number Associated Process Index]. [Called Number Address Attribute] It is an input parameter used to set the address attributes of called parties. if a national number is entered. [Max. The MSOFTX3000 queries Incoming Calling Number Assicaited Process table and Incoming Original Called Number Correlation Processing table according to these two parameters.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data 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. SCP. [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. In this case. For example. [Number Receiving Minimum Length] It is an output parameter. mobile subscribers. They should be set when the incoming number pretreatment procedures are associated with the calling number or original called number. [Original Called Number Associated Process Index] Both parameters are output index parameters. [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. no conversion is needed.

Incoming Original Called Number Correlation Processing table in turn through data configuration. For numbers sent by SCP. it is recommended to query Incoming Number Pretreatment table. "ISUP". IV. Incoming Calling Number Assicaited Process table. Note: If incoming number processing is associated with calling numbers or original called numbers.Operation Manual .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data [Receive-Number Delay Interval] When the call is of trunk incoming type (that is. this parameter is invalid. there may be some excessive-long called numbers (such as IP toll prefix "17951" in China). forwarded-to numbers or MSRNs sent by HLR. it is not necessary to set the parameter. In incoming number processing procedures. "R2". In this case. As a result. Then set index parameters in Incoming Number Pretreatment table to realize calling/original called number correlation processing of incoming numbers. or a combination of some of these types). please add the corresponding records to Incoming Calling Number Assicaited Process table or Incoming Original Called Number Correlation Processing table first. The final calling/called/original called number conversion index is determined by the valid conversion index obtained in the last query. Related Commands See Table 15-7 for the commands related to incoming number pretreatment. the complete called number might not be transmitted through inter-office call signaling at a time. 15-28 . Set proper [Receive-Number Delay Interval] to ensure that the called number data is completely received. "PRA" or “BICC”. the call source is "TUP".

and DN special processing. [Service Attribute] It is used to set the service attribute of a prefix. Major Parameters [DnSet] It indicates the DN set to which a call prefix belongs. “local”.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data 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 15. Generally. It corresponds to the DN set defined in the ADD CALLSRC command. route selection code. and maximum number length. “intelligent service”. [Route Selection Code] 15-29 . or “Internet access code”. Depending on different categories. “new service/supplementary service”. To set related attribute data of call prefix such as calling number analysis. select “basic service” for common call prefix. it can be set to “basic service”. Its basic attributes include service attribute. Command ADD CNACLD MOD CNACLD III. Background Information Call prefix is the start point of a number analysis process. You can select “intra-office”. II. and “new service/supplementary service” for service services. “national toll”.6 Route Selection Data Configuration 15. release control mode. “test”. the corresponding flag in the call prefix must be set to “YES”. “local toll”. or various new services. minimum number length.6. “international toll”.Operation Manual . [Call Prefix] It refers to a called number prefix or called number.1 Configuring Call Prefix I. [Service Category] It indicates the service category of a prefix.

15-30 . In the case of an Overlay outgoing PPS call prefix. For MSRN prefixes. [EARLY ACM Flag]. It is already defined in the ADD RTANA command. which should be set according to the actual situation. set this parameter respectively to "MSRN/HON". or last party release. calling party release. the switch will not process it. Configuration of this parameter will not affect number analysis procedures. Usually set it to first party release.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data The route selection code is used for identifying the route selection method for a call to the prefix. Set [EARLY ACM Flag] to "TRUE" and set [EARLY ACM Delay Value (0.1S)] properly. Select 65535 (invalid) for the local office prefix. If it is set to "Yes". 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). the MSOFTX3000 will query the Toll Area Code table and intercept toll calls after subscribers dial the local area code. and other types of prefixes. "ITT". [Release Mode] This parameter is used to set the release control mode. Release control mode may be first party release. The MSOFTX3000 also intercepts MSISDN call after subscribers dial the toll area code. called party release. If the length of a dialed number is less than the minimum number length. set this parameter to "MSISDN". “NO”. Usually use the default value. this setting is not necessary even for toll prefixes. and "PSTN" or "Unknown Number". but it will be marked in the bill. [Maximum Number Length] It indicates the maximum number length allowed by this type of call. [Minimum Number Length] It indicates the minimum number length allowed by this type of call.Operation Manual . "PSTN". PSTN call prefixes. Set this parameter to "TRUE" for call prefixes involved in calls whose service attributes are "NTT". the switch will not process the excessive digits. and valid route selection code for the outgoing call.1S)] These two parameters are used together to realize the EARLY ACM function at the local office. For other prefixes. [Emergency Call Observe Flag] It indicates whether a call of this class is an emergency call and is observed. If the length of a dialed number is longer than the maximum number length. or "PLMN Other MSC". set this parameter to "PPS (PPS Number)". [EARLY ACM Delay Value (0. set this parameter according to the actual situations. [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”. [Called Number Type] It defines the type of the called number. If the corresponding data preventing subscribers from nest-dialing have been configured in number analysis.

Calling subscriber attributes are determined by the configuration of corresponding call source codes. 15-31 . and configure corresponding analysis data of calling numbers and calling features. calling/called numbers can be converted in terms of calling attributes. the data of Enhanced Route Processing table should also be configured. Besides. If this parameter is not set to "65535". the MSOFTX3000 will query Service Check table through this parameter and then perform service check before number analysis. 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. set this parameter to "TRUE". If you do not need the MSOFTX3000 to send those information to the next office. Usually. Through the configuration of analysis data of calling numbers and calling features.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data [Gain] Usually. 2: for international toll call. [Calling Number Analyzing] It determines whether to conduct different processing over calls according to their various call prefixes and attributes. Therefore. Normally calls to the local area and local office require sending calling numbers and original called number to the next office. [Enhance Route Processing Flag] When subscribers dial the numbers with the same prefix. [Destination] It refers to the call destination. 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.Operation Manual . 0: for other cases. [Service Check Index] It is associated with [Service Check Index] in Service Check table. Through this parameter. the default value. When this parameter is set to "YES". [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. used in destination traffic measurement. this parameter needs not to be configured. set this parameter to “YES”. when it is necessary to configure different call source attribute for a specified calling subscriber. Therefore. [Toll Prefix Length] Length of a toll prefix is 1: for national toll call PSTN. this parameter can be set to "NO" by default. the calling subscriber can originate certain restricted services by dialing certain special prefixes. data in Supplementary Signaling table must also be configured.

Operation Manual . II.6. The table supports flexible routing function for call prefixes.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data To analyze calling numbers (such as normalizing calling numbers). In this case. the route selection code must be set and must have been defined in the route analysis table. IV. In this case.2 Configuring Enhanced Route Processing Data I. Table 15-8 List of commands related to call prefix configuration Command ADD CNACLD MOD CNACLD RMV CNACLD LST CNACLD LST RT To add call prefix To modify call prefix To remove call prefix To list call prefix To list route information (corresponding prefix of route can be found) Description 15. set this parameter to "TRUE". If the service attribute has been set to outgoing calls. the MSOFTX3000 queries Calling Number Analysis table and Calling Number Analysis table to analyze the calling number. for example. It selects different outgoing routes according to the length of called numbers and call types. the MSOFTX3000 will query DN Set Processing table for special processing on the DN set. number conversion and failure processing. Command ADD SUPERRT 15-32 . [Number Initial Processing] Set this parameter to "TRUE" if special processing is required for the DN set. otherwise. Background Information This command is associated with call prefix data configuration and is applied to add records to Enhanced Route Processing table when [Enhance Route Processing Flag] is set to "TRUE". the table will overflow. Related Commands See Table 15-8 for the commands related to call prefix configuration. Caution: The number of records for call prefix cannot be greater than the set value for this table in the maximum tuple number table.

[Call Type] When it is required that the outgoing route of a prefix of a normal call and the outgoing route forwarded in this office to the prefix are different. IV.3 Configuring Call Authority Original Called Correlation Processing Data I. Related Commands See Table 15-9 for the commands related to enhanced route processing data configuration. [Route Selection Code] It helps to modify the outgoing route selection information of the prefix defined in Called Number Analysis table. [Call Prefix] These two parameters are used to set the called prefix to be conducted for enhanced route processing. Table 15-9 List of commands related to enhanced route processing data configuration Command LST SUPERRT ADD SUPERRT MOD SUPERRT RMV SUPERRT Description To list enhanced route To add enhanced route To modify enhanced route To remove enhanced route 15.Operation Manual . and the DN set in which this called prefix is contained. Background Information This command is used to add records to Call Authority Check Original Called Correlation Processing table. and determine the corresponding call processing modes and measures related according to results of the check. Major Parameters [Number Initial Set]. [Max. This table is used to check forwarding calls according to their original called prefixes and roaming types. select different call types through this parameter and define different Route Selection Code to implement it. Length of Prefix] It helps to select different outgoing routes for called numbers with the same call prefix but different number length.6. The MSOFTX3000 queries Call Authority Check table and obtains the "Authority Check 15-33 . and obtain a new route selection code. If table-query fails. Route selection can also be done according to the length of the called number prefix.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data III. the MSOFTX3000 will still use Called Number Analysis table to obtain route selection code for route selection.

Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data Original Called Correlation Processing Index". Set this parameter to "contplay (Continue and play announcement)" or "notecontinue (Connect after playing announcement)" according to actual conditions. original called prefix and roaming type. Together with [Processing Type]. and [Processing Type] to "Prohibit". they can realize the restriction or processing of forwarding calls according to the original called prefix or roaming type. Command ADD PRICHKORICLDIDX III. Major Parameters [Authority Check Original Called Correlation Processing Index] It is used to identify the records in Call Authority Check Original Called Correlation Processing table. And other data tables can use these records through this parameter. 3) Set the parameter to "Inhibited (Prohibit)" for calls that cannot meet system analysis requirements or are restricted in the system. and it will be connected.Operation Manual . 15-34 . set [Original Called Party Roaming Type] to "Other Mobile Network". the MSOFTX3000 will query Failure Processing table through this parameter for corresponding processing. to restrict the forwarding of calls when the called party is an other-mobile-network subscriber and roams to the local office. Then according to this index. If no corresponding records are matched. In terms of various call authority check results. It is used to define the cause value of the call release. set this parameter to "passon (Continue Proceeding)". [Original Called Prefix]. In this case. that is. It is used to designate the code of the announcement to be played. [Original Called Party Roaming Type] These two parameters are the relevant attributes of the original called party. [Processing Type] It determines the processing modes for various calls. the MSOFTX3000 directly goes to the next procedures. the MSOFTX3000 queries Call Authority Check Original Called Correlation Processing table to obtain the processing mode for forwarding calls. [Tone Code] It is valid only when [Processing Type] is set to "Continue and play announcement" or "Connect after playing announcement". II. there are the following processing modes available: 1) The call meets the system analysis requirements after the check. For example. [Failure Cause Code] It is valid only when [Processing Type] is set to "Inhibited (Prohibit)". the corresponding failure processing data should be configured. 2) The call is forwarded at the local office. In the case of a failed check.

including: Call Forwarding Unconditional (CFU). II. IV. The table supports the flexible announcement processing of four types of supplementary services. Call Forwarding on mobile subscriber Busy (CFB). so as to conduct failure processing over calls that do not pass the check. Related Commands See Table 15-10 for the commands related to call authority original called correlation processing data configuration. if the corresponding original called correlation processing data have been configured. Table 15-10 List of commands related to call authority original called correlation processing data configuration Command LST PRICHKORICLDIDX ADD PRICHKORICLDIDX MOD PRICHKORICLDIDX RMV PRICHKORICLDIDX 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 15. For forwarding calls. Background Information This command is used to add records to Call Authority Check table. The MSOFTX3000 queries this table respectively during the incoming number analysis and when the call is forwarded at the local office. it is still required to query Call Authority Check Original Called Correlation Processing table. Call Forwarding on No Reply (CFNRy) and Call Forwarding on mobile subscriber Not Reachable (CFNRC).Operation Manual .4 Configuring Call Authority Check Data I. forwarded incoming calls and local forwarding calls. Both tables are applied in cooperation with Failure Processing table. Command ADD CALLPRICHK 15-35 .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data 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. And then the MSOFTX3000 determines the call processing mode by the result of the query. It also supports the check and restriction of ordinary incoming calls.6.

"Other International Mobile Network". the prefix of called number to be checked and its maximal length. [Calling Party Roaming Type] is used to set different call authorities for subscribers with different calling subscriber types so as to realize the corresponding restrictions (for example. It is configured when the call is forwarded and a call authority check should be conducted according to the attributes of the original callee/called party. Set this parameter to "contplay (Continue and play announcement)" or "notecontinue (Connect after playing announcement)" according to actual conditions. [Calling Subscriber Type]. set this parameter to "passon (Continue Proceeding)". In this case. [Authority Check Original Called Correlation Processing Index] It is an output index parameter. 2) The call is forwarded at the local office. that is. Major Parameters [Call Source Code] It is associated with [Call Source Code] in Call Source table and used to conduct call authority check over calls originated from various call sources. "International Mobile Network". that is. "Other National Mobile Network". [Failure Cause Code] 15-36 . [Calling Party Roaming Type] These two parameters determine the relevant attributes of calling subscriber. there are processing modes available as follows: 1) The call meets the system analysis requirements after the check. [Processing Type] It determines the mode to process the call after the check. All call sources should be configured with call authority check data. This parameter is valid when [Call Type] is not "COMMON (Ordinary Call)". [Called Prefix].Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data III. The first two parameters support maximum matching. When a subscriber dials the number with such a prefix. In terms of various call authority check results. restrict the forwarding of the call in which the other-mobile-network subscriber roaming to the local network is called). Length of Called Number] These two parameters determine the relevant attributes of the called party. [Max. the check will be conducted or the call will be barred. and "PSTN_SUBSCRIBER".Operation Manual . 3) Set the parameter to "Inhibited (Prohibit)" for calls that cannot meet system analysis requirements or are restricted in the system. and it will be connected. This parameter is used to query Call Authority Check Original Called Correlation Processing table for the corresponding processing mode. [Calling Subscriber Prefix]. "National Mobile Network". The options of [Calling Party Roaming Type] include "Local Mobile Network". the corresponding failure processing data should be configured. [Call Type] It helps to set various call authority check data for various types of calls (ordinary or forwarded calls).

The 15-37 .5 Configuring Service Check Data I. Background Information This command is used to add records to Service Check table. This parameter is used to define cause why the call is released. It is used to designate the code of the announcement to be played.Operation Manual . When the call authority check fails.6. the call processing shall be based on the result of the final query. Table 15-11 List of commands related to call authority check Command LST CALLPRICHK ADD CALLPRICHK MOD CALLPRICHK RMV CALLPRICHK Description To list call authority check To add call authority check To modify call authority check To remove call authority check 15. call authority check is done once only when number analysis starts. Therefore. If Authority Check table must be queried during data configuration. the MSOFTX3000 queries Failure Processing table through this parameter for the corresponding processing. For an one-stage call. Note: According to the sequence of number analysis. If Authority Check Original Called Correlation Processing table is also queried. Related Commands See Table 15-11 for the commands related to call authority check. so as to play proper announcement to the subscriber.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data It is valid only when [Processing Type] is set to "Inhibited (Prohibit)". IV. which is used to realize the flexible control over service attribute check of calling subscribers. the called number in the check should be the number that has been converted. the call processing shall be based on the query result of Authority Check table. and to set proper failure processing records in Failure Processing table. incoming number pretreatment procedures have been conducted before the call authority check. [Tone Code] It is valid only when [Processing Type] is set to "Continue and play announcement" or " Connect after playing announcement". Call authority check is carried out during number analysis. The check will not be conducted during the analysis of the MSRN prefix. instead of the number dialed by the calling subscriber.

If [Service Check Index] is not blank. the call will not be disconnected by default. [Service Check Type] and [Service Check Mode] are valid only when this parameter is set to "Yes". [Service Check Index] It is used to identify the records in Service Check table and corresponds to [Service Check Index] in Called Number Analysis table. Table 15-12 Service check processing mode Service check type 0 Service check mode 0 Meaning Services related will be processed according to the default modes stipulated in GSM specifications. that is. The MSOFTX3000 queries Called Number Analysis table in number analysis procedures. Major Parameters [Call Source Code] It determines the call source to be conducted for service check. II. [Restricted Session Duration(sec)] It is used to set the maximal conversation duration during the service restricted. They determine the mode to check the service. Both of them are generally set by default. [IWF Application Mode]. indicating that service check may be carried out over all call sources.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data MSOFTX3000 queries the records in this table according to the call source and [Service Check Index] in Called Number Analysis table. and the latter to "No". [Service Check Type]. 15-38 . and processes the call according to the settings in the records. When the call in session is checked and found to have reached the restricted session duration. Command ADD SRVCHK III.Operation Manual . as shown in Table 15-12. the former is set to "Automatic Application for IWF". [Perform Service Check] It determines whether to carry out service check over the service attribute of the call. [Service Check Mode] These two parameters indicate repsectively whether a service is to be checked and the mode of check. Its unit is second. It is associated with [Call Source Code] in Call Source table and generally set to "65534". the relevant records in Service Check table will be referenced through this parameter. [Forced EC Request] These two parameters determine the modes to apply for IWF and EC resources for the call being checked.

that is. set the two parameters aforementioned to "SCC=ODB_BAOC-0. Table 15-13 List of commands related to service check Command LST SRVCHK ADD SRVCHK MOD SRVCHK RMV SRVCHK Description To list service check To add service check To modify service check To remove service check 15. the call will be connected.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data Service check type Service check mode Meaning Calls of corresponding services will be processed as ordinary calls (for example. rerouting) over calls according to 15-39 . Related Commands See Table 15-13 for the commands related to service check. when service type is "ODB_BAOC" and the two parameters are configured as "SCC=ODB_BAOC-1. or to perform various special processing (for example. 0 1 1 0 1 1 Note: When a certain service is set to "1" in [Service Check Type]. the calls will be checked. Therefore.6. SCM=ODBACOC-1". announcements should be played for the failures of such calls.) Calls of corresponding services will be rejected. Background Information Calling number analysis is used to normalize the formats of calling numbers.6 Configuring Calling Number Analysis Data I. The command ADD CST can be used to add service check tone records for the announcements. when the service type is "ODB_BAOC". the call will be disconnected directly and corresponding announcement will be played for the subscriber. SCM=ODBBAOC-1". the subscriber being barred can still make calls. IV. it may result in the rejection of the call containing (or not containing) this service. If the check fails. Only calls requesting for such service will be connected. for example.Operation Manual .

including how to route. [Calling Subscriber Type] It determines the new calling subscriber type: ordinary subscriber. Command ADD CNACLR III. data subscriber.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data different attributes of calling numbes involved. Major Parameters [Call Source Code]. [Caller Minimum Length] It indicates how many digits the calling number must at least have. the calling number analysis table can be used to define new call source attributes. operator. the MSOFTX3000 will query Calling Number Analysis table. that is. [Call Source] It indicates whether the call is initiated from the mobile side or PSTN. [Call Prefix] It is the prefix of the called number. failure processing. [Calling Party Roaming Attribute]. II. If there is no matching record in Calling Attribute Analysis table. the MSOFTX3000 terminates calling number analysis. It is a processing method for calling number. Note: When “Calling Number Analysis flag” in the call prefix table is set to “YES”. If it is required to give a particular caller different call source attributes. and so on. [Number Initial Set] It indicates in which DN set the analysis is conducted. and calling/called number change. Multiple call sources (local subscribers or trunk users) are allowed to use the same call source code. [Calling Number] These parameters are used for the MSOFTX3000 to query Calling Number Analysis table so as to determine the call that needs the calling analysis. they have the same call attributes.Operation Manual . The call source attribute is defined in call source code. the MSOFTX3000 first queries Calling Attribute Analysis table (this table will be introduced in later sections) based on the attributes of the calling subscriber. or is a forwarded-to call. [Route Selection Source Code] 15-40 . Upon the success of querying Calling Attribute Analysis table.

this index will be used to obtain related information of SCP. indicating the code of the new route selection scheme of a called number. [Called Number Change Index] It indicates the change index of the called number. the new failure source code is used to query Failure Processing table. determining how to deal with the failure. [Failure Source Code] This parameter is used to set the new failure source code that the call corresponds to.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data It is an output parameter used to redesignate the outgoing route in terms of calling subscribers. “international” and “local service”. [New Service Property] If the processing type of the current processing is outgoing after route selection. [Processing Type] It indicates how to process the number when the analysis is successful. [Calling Number Change Index] It indicates the change index of the calling number. It includes failure processing. you can configure service attributes for instant outgoing. When this parameter is specified. the route selection source code obtained by querying Called Number Analysis table is invalid. When a subsequent failure occurs. [Failure Cause Code] It indicates the failure cause when [Processing Type] is “Failure Processing”.Operation Manual . including “national”. outgoing after instant route selection. It is defined in the ADD DNC command. [Route Selection Code] It is an output parameter. It is defined in the ADD DNC command. triggering NCSI DP2. [SCP Parameter Table Index] If the NCSI DP2 service is triggered. 15-41 .

special processing of the call will be conducted according to [Calling Feature Index]. IV. Related Commands See Table 15-14 for the commands related to calling number analysis. Calling Feature Processing table is referenced to Calling Feature Analysis table through this parameter. During calling feature analysis process. Background Information This command is used to add records in Calling Feature Processing table. II.7 Configuring Calling Feature Processing Data I. If [Calling Number Analysis Flag] exists during called number analysis. [Route Selection Source Code]. The number of records in Calling Number Analysis table cannot be greater than the set for this table in the maximum tuple number table. Major Parameters [Index] 15-42 . Before configuring calling number analysis data. Calling feature index corresponds to that in calling feature analysis. special processing of the call must be done by querying Calling Feature Processing table. Table 15-14 List of commands related to calling number analysis Command LST CNACLR ADD CNACLR MOD CNACLR RMV CNACLR Description To list calling number analysis To add calling number analysis To modify calling number analysis To remove calling number analysis 15. including [Call Source Code]. [Failure Source Code]. one or more service check types in the table will be mapped to a calling feature index. you must have defined parameters cited in Calling Number Analysis table.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data Caution: Calling Number Analysis table is valid only when [Calling Number Analysis Flag] of the call is “YES”. When defining records in Calling Feature Processing table.Operation Manual .6. Command ADD CLICRTPRO III. and [Calling Number Change Index].

8 Configuring Calling Feature Analysis Data I. Table 15-15 List of commands related to calling feature processing Command LST CLICRTPRO ADD CLICRTPRO MOD CLICRTPRO RMV CLICRTPRO Description To list calling feature processing To add calling feature processing To modify calling feature processing To remove calling feature processing 15. Background Information This command is used to add records in Calling Feature Analysis table. Calling Feature Analysis table is used for conducting special processing of the call according to the calling features (for example. Set no duplicate indexes. Command ADD CLICRTANA III. It corresponds to [Calling Feature] in Calling Feature Processing table. whether the subscriber has subscribed to forwarding and service restriction). II.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data It is used within the system.6. Major Parameters [Call Source Code] Call source code of the calling subscriber. IV. [Calling Feature] It is an output parameter. It corresponds to one or more service check types. Calling Feature Processing table is referenced to Calling Feature Analysis table through this parameter. [Service Check Type] It is an output parameter. [Calling Feature] It is the calling feature index. [Description] Description of the features of the calling subscriber.Operation Manual . Calling Feature Processing table is referenced to Calling Feature Analysis table through this parameter. Related Commands See Table 15-15 for the commands related to calling feature processing. 15-43 .

Operation Manual . [Route Selection Code] It is an output parameter. the route selection source code obtained by querying Called Number Analysis table is invalid. [Failure Source Code] This parameter is used to set the new failure source code that the call corresponds to. indicating the code of the new route selection scheme of a called number. and so on. [Route Selection Source Code] It is an output parameter used to redesignate the outgoing route in terms of calling subscribers. you can configure service attributes for instant outgoing. including “national”. outgoing after instant route selection. [Processing Type] It indicates how to process the number when the analysis is successful. triggering NCSI DP2.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data [Calling Subscriber Type] It determines the calling subscriber type: ordinary subscriber. 15-44 . [Number Initial Set] It indicates in which DN set the analysis is conducted. [Called Number Change Index] It indicates the change index of the called number. the new failure source code is used to query Failure Processing table. It is defined in the ADD DNC command. operator. determining how to deal with the failure. Length] It indicates how many digits the calling number can have at most. It includes failure processing. [Calling Number Change Index] It indicates the change index of the calling number. [Calling Number Max. When this parameter is specified. [Call Prefix] It is the prefix of the called number. “international” and “local service”. [Call Source] It indicates whether the call is initiated from the mobile side or PSTN. [New Service Property] If the processing type of the current processing is outgoing after route selection. When subsequent failure occurs. data subscriber. or is a forwarded-to call. It is defined in the ADD DNC command.

called numbers and DN sets. II. IV. and the type of signal tone sent. It is connected to multiple SCPs through ACCESS CODE. Related Commands See Table 15-16 for the commands related to calling number analysis. [SCP Access Mode] There are two SCP access modes: HSCP (HOME SCP) and AC (ACCESS CODE). Such modes include calling/called number converting. these modes are classified in terms of call source codes. Calls that have no corresponding processing modes in DN Special Processing table will be processed as usual. HSCP means that SCP is fixed on HOME SCP.6. Caution: Calling Number Analysis table is valid only when [Calling Number Analysis Flag] in Call Prefix table is “YES”. Command ADD PFXPRO 15-45 . AC means that SCP is not connected to another single SCP. this index will be used to obtain related information of SCP. [SCP Parameter Table Index] If the NCSI DP2 service is triggered.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data [Failure Cause Code] It indicates the failure cause when [Processing Type] is “Failure Processing”. Table 15-16 List of commands related to calling number analysis Command LST CLICRTANA ADD CLICRTANA MOD CLICRTANA RMV CLICRTANA Description To list calling number analysis To add calling number analysis To modify calling number analysis To remove calling number analysis 15.Operation Manual . Background Information This command is used to set various modes for the MSOFTX3000 to process calls. Besides. reanalysing.9 Configuring Dialed Number Special Processing Data I. failure processing.

Its value is defined in the ADD DNC command. or do not play an announcement. It is valid only when the parameter [Calling Number Change Flag] is set to “YES”. Major Parameters [Call Source Code] It identifies the call source to which a calling subscriber belongs. [Tone Type] It indicates the type of signal tone to be sent. and routing methods pertaining to the MSOFTX3000. [Calling Number Change Index] It indicates the number change index of a calling number. During number analysis. reanalyzing and so on. such as 117 time reporting and call barring tone.Operation Manual . Call prefix is the number used for indicating call connection. Its value is defined in the ADD DNC command. connect call after playing announcement. used to achieve conversion between DN sets during a call. DN processing happens when subscribers of this call source originate calls to a specified prefix. [Failure Cause Code] It indicates the cause when [Process Type] is “Failure Processing”. for the purposes of determining attributes of the call. 15-46 . triggering NCSI DP12. These types are failure processing. the called number tries to match the call prefix according to the maximum matching principle. [Called Number Change Index] It indicates the number change index of a called number. [Tone Sending Mode] This parameter is used to configure whether to play ordinary announcement.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data III. connect call and play an announcement at the same time. [Number Initial Set] It is the DN set to which a called prefix belongs. It is valid only when the parameter [Called Number Change Flag] is set to “YES”. [Process Type] This parameter refers to the call processing type after the success of number analysis. billing specifications. [Call Source] It is the category to which a calling subscriber belongs. Call prefix reflects information about numbering schemes. [New Number Initial Set] It is the new DN set after DN processing. [Call Prefix] It is the called prefix on which DN processing happens.

call source. the MSOFTX3000 queries Failure Processing table and obtains the corresponding call failure processing mode. Caution: Before adding DN special processing data. Special processing after call failure includes sending special signal tone. It can also be referenced through [Failure Cause Code] in Call Source table and [Call Failure Cause Code] detected by the exchange.10 Configuring Failure Processing Data I. II. If the NCSI DP12 service is triggered. 15-47 . you must have set the DN set. Through these codes. Table 15-17 List of commands related to DN special process Command LST PFXPRO ADD PFXPRO MOD PFXPRO RMV PFXPRO Description To list DN special process To add DN special process To modify DN special process To remove DN special process 15. Background Information Failure Processing table can be referenced from DN Special Processing table through [Failure Cause Code] in the latter table.6. Major Parameters [Failure Cause Code] A set of codes that are defined in the MSOFTX3000 and correspond to failure cause values.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data [SCP Parameter Table Index] This parameter indicates the intelligent parameter index.Operation Manual . call prefix. re-routing. Command ADD CFPRO III. and reanalyzing after number conversion. IV. this parameter will be used to obtain related information of SCP. Related Commands See Table 15-17 for the commands related to DN special process. call change index and the new DN set that are referenced.

interrupting. DP13.Operation Manual . IV. [Service Attribute] It indicates the service attribute that the concerned call must have for the purposes of starting a failure processing process. If a call failure meets preset conditions. [Processing Type] It specifies the processing way when the calls of this class fail. Number change tone with the number attached will be sent only when the failure cause code is number changed. re-selecting sub-route. Related Commands See Table 15-18 for the commands related to failure processing. The processing ways may be sending signal tone. [Caller Category] It indicates the subscriber category to which the calling party must belong for the purposes of starting a failure processing process. queuing. DP14 and not to trigger. [Trigger Type of IN Service] These types include DP4. this parameter determines a failure processing record. and so on. [Signal Tone Type] This parameter is enabled when the failure processing type is sending signal tone. Together with [Call Failure Cause Code] detected by the MSOFTX3000. signal tone selected in this parameter will be sent to the calling party.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data [Failure Source Code] It indicates failure source code in call source. Table 15-18 List of commands related to failure processing Command LST CFPRO ADD CFPRO MOD CFPRO RMV CFPRO Description To list failure processing To add failure processing To modify failure processing To remove failure processing 15-48 . inserting or re-analyzing after number change.

the MSOFTX3000 will process the call as usual.7. The MSOFTX3000 queries Outgoing Calling Number Correlation Processing table according to these parameters entered during the analysis. [Calling Number Conversion Index]. calling party roaming attribute. calling number address attribute. When [Designated Calling Number Format] is valid. Then the MSOFTX3000 obtains the conversion index of calling/called/original called numbers being sent. Background Information This command is used to add records to Outgoing Calling Number Correlation Processing table. Otherwise.7 Configuring Outgoing Number Preprocessing Data 15. The MSOFTX3000 obtains [Calling Number Associated Process Index] from Outgoing Number Preprocessing table. [Calling Subscriber Type]. The table helps to normalize the calling/called/original called numbers involved in outgoing calls according to the calling number and relevant attributes. [Calling Party Roaming Attribute]. the calling number is converted as specified. the MSOFTX3000 will query Number Change table by [Calling Number Conversion Index] and finds the mode to convert the calling number. Note that one number conversion mode can be used only at a time. [Designated Called Number Format] 15-49 . only one of the two parameters should be specified at a time. and calling number maximum length. [Calling Subscriber Prefix]. calling subscriber prefix.1 Configuring Outgoing Calling Number Correlation Processing Data I. Length] They are all parameters related to the calling subscriber. Major Parameters [Calling Number Associated Process Index] It uniquely identifies an outgoing calling number correlation processing record. II. If a record is matched. then queries Outgoing Calling Number Correlation Processing table according to this index. and normalize these numbers according to the conversion mode corresponding to the conversion index. [Calling Number Address Attribute]. Command ADD OUTCLRIDX III. [Called Number Conversion Index]. that is. the MSOFTX3000 will process the call as specified in the record. [Calling Number Max. When [Designated Calling Number Format] is invalid. calling subscriber type. [Designated Calling Number Format] They determine the mode to convert the calling number.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data 15.Operation Manual . The MSOFTX3000 queries Outgoing Calling Number Correlation Processing table through [Calling Number Associated Process Index] in Outgoing Number Preprocessing table during the outgoing number preprocessing.

Operation Manual . you need not to configure calling number correlation processing data.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data These two parameters determine the mode to convert the called number. [Redirecting Conversion Index]. Note that only one conversion mode can be used at a time. If conversion is done only based on the called number. Table 15-19 List of commands related to outgoing calling number correlation Command LST OUTCLRIDX ADD OUTCLRIDX Description To list outgoing calling number correlation To add outgoing calling number correlation 15-50 . the MSOFTX3000 queris Number Change table by [Original Called Number Conversion Index] and finds the mode to convert the original called number. IV. the original called number is converted as specified. [Original Called Number Conversion Index]. When [Designated Original Called Number Format] is invalid. When [Designated Called Number Format] is valid. Related Commands See Table 15-19 for the commands related to outgoing calling number correlation. [Designated Redirecting Number Format] These two parameters are used to set the mode for redirecting conversion. only one of two parameters should be specified at a time. Note that only one conversion mode can be adopted at a time. that is.When [Designated Original Called Number Format] is valid. the called number is converted as specified. the conversion mode that designates number format takes precedence. Note that only one mode of number conversion can be configured once. 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. When [Designated Redirecting Number Format] is invalid. When [Designated Called Number Format] is invalid. that is. [Designated Original Called Number Format] These two parameters are used to determine the mode to convert the original called number. two parameters cannot be configured at the same time. namely only one of these parameters can be configured. When [Designated Redirecting Number Format] is valid. the MSOFTX3000 queries Number Change table based on [Redirecting Conversion Index] to convert the original called number. the MSOFTX3000 queries Number Change table by [Called Number Conversion Index] and locates the corresponding mode to convert the number.

2 Configuring Outgoing Original Called Number Correlation Processing Data I. The MSOFTX3000 obtains the original called number associated process index. [Designated Called Number Format] These two parameters determine the mode to convert the called number. When [Designated Called Number Format] is invalid. to obtain the conversion indexes of the outgoing calling/called/original called numbers. [Called Number Conversion Index]. only one of the two parameters should be configured. that is.7. and then queries Outgoing Original Called Number Correlation Processing table according to this index. Note that only one conversion mode can be adopted at a time. Then the MSOFTX3000 normalizes these numbers according to the conversion mode corresponding to these conversion indexes. original called prefix. The table is used to normalize the calling/called/original called numbers involved in outgoing calls accroding to original called number and its relevant attributes. only one of the two parameters can be configured. Major Parameters [Original Called Number Associated Process Index] It identifies records in Outgoing Original Called Number Correlation Processing table. the MSOFTX3000 queries Number Change table according to [Calling Number Conversion Index] and finds the corresponding mode to convert the calling number. [Designated Calling Number Format] These two parameters determine the mode to convert the calling number. Outgoing Number Preprocessing table references the corresponding records in Outgoing Original Called Number Correlation table through this parameter. Note that only one mode of conversion can be conducted over the calling number at a time. the 15-51 . that is. II.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data Command MOD OUTCLRIDX RMV OUTCLRIDX Description To modify outgoing calling number correlation To remove outgoing calling number correlation 15. [Calling Number Conversion Index]. original called party roaming attribute. When [Designated Calling Number Format] is valid. original called number address nature. Background Information This command is used to add records to Outgoing Original Called Number Correlation Processing table.Operation Manual . the MSOFTX3000 converts the number in the mode with a specified format first. Command ADD OUTORICLDIDX III. When [Designated Calling Number Format] is invalid. and original called number maximum length.

Table 15-20 List of commands related to outgoing original called number correlation Command LST OUTORICLDIDX ADD OUTORICLDIDX MOD OUTORICLDIDX RMV OUTORICLDIDX 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 . When [Designated Original Called Number Format] is valid. Related Commands See Table 15-20 for the commands related to outgoing original called number correlation. When [Designated Original Called Number Format] is invalid.Operation Manual . When [Designated Redirecting Number Format] is invalid. [Redirecting Conversion Index]. the MSOFTX3000 queries Number Change table by [Original Called Number Conversion Index] and locates the corresponding mode to convert the number. namely only one of these parameters can be configured. the MSOFTX3000 converts the number in the mode with a specified format first. IV. Note that only one conversion mode can be adopted to convert the original called number at a time. When [Designated Called Number Format] is valid. the MSOFTX3000 converts the number in the mode with a specified format first. only one of the two parameters should be configured. [Original Called Number Conversion Index]. the MSOFTX3000 queries Number Change table based on [Redirecting Conversion Index] to convert the original called number.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data MSOFTX3000 queries Number Change table according to [Called Number Conversion Index] and locates the correspond mode to convert the called number. Note that only one mode of number conversion can be configured once. the conversion mode that designates number format takes precedence. When [Designated Redirecting Number Format] is valid. that is. 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. [Designated Original Called Number Format] These two parameters determine the mode to convert the original called number. [Designated Redirecting Number Format] These two parameters are used to set mode for redirecting conversion.

[Outgoing Trunk Group No. You can set index data in this parameter for referencing Outgoing Original Called Number Correlation Processing table to perform number conversion. and maximum length of called number. [Designated Calling Number Format] These two parameters determine the mode to convert the calling number. II. Note that only one conversion mode can be adopted at a time. The MSOFTX3000 queries Outgoing Number Preprocessing table according to call source code. [Original Called Number Associated Process Index] This parameter is set for the MSOFTX3000 to query Outgoing Original Called Number Correlation Processing table and obtain corresponding modes to convert trunk numbers. the MSOFTX3000 converts the calling/called/original called numbers directly. The table is used to preprocess (perform format control over calling/called/original called numbers) various numbers sent to outgoing trunks. Background Information This command is used to add records to Outgoing Number Preprocessing table. It is the index to query Outgoing Calling Number Correlation Processing table. Otherwise. these parameters are used for the MSOFTX3000 to query Outgoing Number Preprocessing table and obtain the conversion modes for calling/called/original called numbers involved.. DN set. outgoing trunk group No. only one of the two parameters should be configured at the same time. If both parameters are invalid. [Calling Number Conversion Index]. [Max. When [Designated Calling Number Format] is invalid.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data 15. [Number Initial Set]. the MSOFTX3000 queries Outgoing Calling Number Correlation Processing table and Outgoing Original Called Number Correlation Processing table through the two indexes to obtain number normalization information. so as to ensure these numbers meet the signaling transmission requirements of the interface. Command ADD OUTNUMPREPRO III. called prefix.Operation Manual . Major Parameters [Call Source Code]. [Called Number Address Attribute]. [Called Prefix]. Then it obtains the values of [Calling Number Associated Process Index] and [Original Called Number Associated Process Index]. the MSOFTX3000 queries Number Change table by [Calling Number 15-53 . Length of Called Number] During the outgoing of calls. called number address attribute. [Calling Number Associated Process Index] It should be configured when the conversions of calling/called/original called numbers are associated with calling number and its attributes.3 Configuring Outgoing Number Preprocessing Data I.7. that is.].

the MSOFTX3000 converts the number in the mode with a specified format first. When [Designated Original Called Number Format] is valid. When [Designated Called Number Format] is valid. then set corresponding index parameters in Outgoing Number Preprocessing table so as to realize the calling/original called number correlation processing. only one of the two parameters can be configured. [Designated Redirecting Number Format] These two parameters are used to set mode for redirecting conversion. [Designated Original Called Number Format] These two parameters determine the mode to convert the original called number. [Original Called Number Conversion Index]. Outgoing Calling Number Correlation Processing table. Note If it is required to conduct correlation processing over outgoing numbers according to calling numbers.Operation Manual . that is. the conversion mode that designates number format takes precedence. [Designated Called Number Format] These two parameters are used to determine the mode to convert the called number. [Called Number Conversion Index]. When [Designated Redirecting Number Format] is invalid. the MSOFTX3000 queries Number Change table based on [Redirecting Conversion Index] to convert the original called number. and Outgoing Original Called Number Correlation Processing 15-54 . if it is required to conduct correlation processing over outgoing numbers according to original called numbers. Similarly. the MSOFTX3000 convert the number in the mode with a specified format first. only one of the two parameters can be configured simultaneously. When [Designated Calling Number Format] is valid. 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. [Redirecting Conversion Index]. During outgoing number preprocessing procedures. When [Designated Redirecting Number Format] is valid. first configure outgoing original called number correlation processing data. the MSOFTX3000 queries in turn Outgoing Number Preprocessing table. that is.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data Conversion Index] and locates the mode to convert the calling number. Note that only one conversion mode can be adopted at a time. Note that only one conversion mode can be adopted at a time. IV. Note that only one mode of number conversion can be configured once. When [Designated Called Number Format] is invalid. first configure outgoing calling number correlation processing data. the MSOFTX3000 queries Number Change table by [Called Number Conversion Index] and obtains the corresponding mode to convert the called number. the MSOFTX3000 converts the number in the mode with a specified format first. namely only one of these parameters can be configured.

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 15. And the final conversion indexes of calling/called/original called numbers are the valid conversion indexes obtained in the last query.] in Trunk Group Bearer Index table. Command ADD TGLD III.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data table. [Trunk Seizure Point] It determines the number of digits of the called number received by the trunk side from the call control block (CCB) before sending Seize message to the next office.7. Major parameters [Bearer Index] It identifies the records in Trunk Group Bearer table and corresponds to [Bearer Index No.Operation Manual .4 Configuring Trunk Group Bearer Data I. [New Calling Party Cat] 15-55 . Related Commands See Table 15-21 for the commands related to outgoing number preprocessing.] in Trunk Group Bearer Index table. The MSOFTX3000 uses the corresponding records in Trunk Group Bearer table through [Bearer Index No. The MSOFTX3000 queries Number Change table through these two parameters to obtain the mode to convert calling/called outgoing numbers. then to route to the peer office by routes selected. Background Information This command is used to add records to Trunk Group Bearer table. [Called Number Sending Change Index] These parameters are associated with [Number Conversion Index] in Number Change table. [Caller Number Sending Change Index]. V. The table is used to set the number conversion index information for outgoing calls. II. to convert the calling/called numbers related in some calls from certain trunk group.

Related Commands See Table 15-22 for the commands related to trunk group bearer. and obtains the corresponding bearer index number. the call source code and called number. The table functions in cooperation with Trunk Group Bearer table to process the outgoing numbers involved in some calls to certain trunk group. Note: Number conversion in trunk group bearer is carried out over calling/called numbers after the number analysis and routing procedures. II. Major parameters [Trunk Group] 15-56 . Then it queries Trunk Group Bearer table through the bearer index number to obtain the processing information of the outgoing number. The function of this parameter is similar to that of number conversion. IV. Table 15-22 List of commands related to trunk group bearer Command LST TGLD ADD TGLD MOD TGLD RMV TGLD Description To list trunk group bearer To add trunk group bearer To modify trunk group bearer To remove trunk group bearer 15. the numbers sent by the local office will be normalized according to the number analysis of the peer office through trunk group bearer data configuration. In this way.Operation Manual .5 Configuring Trunk Group Bearer Index Data I.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data It redesignates the calling number type to meet the requirements of calling number formats in various countries. Background Information This command is used to add records to Trunk Group Bearer Index table. For outgoing calls. Command ADD TGLDIDX III. The MSOFTX3000 queries Trunk Group Bearer Index table according to the trunk group number (obtained through outgoing route selection). the requirements of numebr analysis at the next office can be satisfied.7.

[Call Prefix] The prefix of the called number. called number. Background Information This command is used to add records to CLIP Called Correlation Processing table. it is required to query Trunk Group Bearer table for the call whose called number contains such prefix for further processing.8 Configuring Other Number Conversion Data 15.1 Configuring CLIP Called Correlation Processing Data I. and called address naturer. IV. [Bearer Index] It is the result obained after the query of Trunk Group Bearer Index table. 15-57 . [Call Source] It determines the call source code requiring trunk group bearer conversion. it normalizes the calling number to be presented. [Call Source Code] and [Call Prefix] together determine the calls to be conducted for trunk group bearer processing. Then according to the calling number conversion index. But note that. that is. dialed number prefix set. the MSOFTX3000 queries CLIP Called Correlation Processing table and obtains the calling number conversion index.8. Related Commands See Table 15-23 for the commands related to trunk group bearer index. By [Callee Number Correlation Index] obtained from CLIP Processing table. Table 15-23 List of commands related to trunk group bearer index Command LST TGLDIDX ADD TGLDIDX MOD TGLDIDX RMV TGLDIDX 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. the [Callee Number Correlation Index] referenced by CLIP Processing table should have corresponding record in CLIP Called Correlation Processing table and have been configured before being referenced. The table is used to normalize the calling numbers to be presented according to called numbers and their attributes. The MSOFTX3000 queries Trunk Group Bearer table through this parameter to obtain the detailed information of the trunk group bearer.Operation Manual .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data It determines the trunk group to bear the outgoing call.

the MSOFTX3000 will convert the calling number or re-designate the calling number format as specified in this record. Table 15-24 List of commands related to CLIP called correlation Command LST CLCRPRO ADD CLCRPRO MOD CLCRPRO RMV CLCRPRO Description To list CLIP called correlation To add CLIP called correlation To modify CLIP called correlation To remove CLIP called correlation 15-58 . Major Parameters [Callee Number Correlation Index] It identifies the records in CLIP Called Correlation Processing table.Operation Manual . If more flexible conversion is required for the caller number. [Callee Number Prefix]. When CLIP is associated with the called subscriber attribute. Otherwise. Related Commands See Table 15-24 for the commands related to CLIP called correlation. only one conversion mode can be adopted. just set [Designated Caller Number Format].Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data II. Command ADD CLCRPRO III. Through this parameter. the conversion mode with a specified format presides. [Caller Number Change Index]. IV. you can first set corresponding conversion data in Number Change table. it will conduct the next procedure for processing. the MSOFTX3000 queries CLIP Called Correlation Processing table according to the above attributes and [Callee Number Correlation Index]. 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. In the above CLIP processing. If one matched record is found. If there is a conflict in data configuration. and then reference Number Change table through [Caller Number Change Index]. [Callee Number Address Type] These two parameters determine the relevant attributes of the called subscriber. [Designated Caller Number Format] If the system requires the caller number to be displayed in the specified format. the MSOFTX3000 references the corresponding records of this table during the number analysis.

The calling number is displayed according to the setting of this field.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data 15. calling number. and calling number length.Operation Manual . the MSOFTX3000 will query CLIP Called Correlation Processing table according to the setting of [CLIP Callee Number Correlation Index] in the record to obtain the number normalization information. Major Parameters [Call Source Code].2 Configuring CLIP Processing Data I. Then the MSOFTX3000 queries this table through [Caller Number Change Index] and obtains the mode to convert the number. If the data configurations conflict. II. Command ADD CLIPRO III. Then it processes (convert the caller number or query CLIP Called Correlation Processing table for processing) the calling number according to the modes defined in the matched record. just set [Designated Caller Number Format] accordingly. The MSOFTX3000 queries CLIP Processing table according to call source code. This parameter is valid only when it is set to values other than 65535. convert the number by the designated number format. The MSOFTX3000 queries CLIP Processing table according to the attributes specified by above parameters. 15-59 . “65535” indicates that no callee correlation processing is conducted. only one mode can be adopted to convert the number. calling number address nature. [Caller Number Change Index]. [Caller Number Maximum Length] These parameters determine the relevant attributes of the calling subscriber. The MSOFTX3000 will perform the corresponding number conversion over the presentation of the calling number according to the setting of [Caller Number Change Index] or [Designated Caller Number Format] in the record. when the caller displays the “Callee Number Correlation Index” other than 65535. it is required to set the corresponding data for the conversion in Number Change table. If the calling number is to be converted more flexibly. [Caller Number Prefix]. Background Information This command is used to add records to CLIP Processing table. [Callee Number Correlation Index] It is associated with the “Callee Number Correlation Index” in CLIP Called Correlation Processing table and is used to query records in this table to realize number conversion for the CLIP according to caller/callee numbers.8. [Designated Caller Number Format] If the calling number is to be presented in the designated format only. In addition. [Caller Number Address Type]. In the above processing over the presentation of calling number.

Major Parameters [Call Source] The call source code. The table is used to convert number prefixes according to forwarded-to numbers or connected numbers. If it is required to normalize the calling number being presented according to the called number and its attributes. it needs to configure format control data for forwarded-to numbers. the system can conduct processing accordingly through the setting of this parameter.3 Configuring Auxiliary Number Processing Data I.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data Note: This command is used only when the MSOFTX3000 serves as a visited mobile switching center (VMSC). or designate number attribute. In terms of connected numbers or forwarded-to numbers from various call sources. it can be configured with the format control data of connected numbers. When the local office serves as the call originating office. Related Commands See Table 15-25 for the commands related to CLIP. while if the call is forwarded at the local office. Table 15-25 List of commands related to CLIP Command LST CLIPRO ADD CLIPRO MOD CLIPRO RMV CLIPRO Description To list CLIP To add CLIP To modify CLIP To remove CLIP 15.Operation Manual . the configuration of CLIP called number correlation processing data should be accomplished first. [Number Type] 15-60 . IV. Background Information This command is used to add records to Auxiliary Number Processing table.8. II. Command ADD AIDNUMPRO III. Data that should be configured for a call originating office and a forwarding originating office are different.

Operation Manual . so as to index Number Change table and realize the format normalization of connected numbers or forwarded-to numbers. Major Parameters [NUMBER PREFIX] 15-61 . The MSOFTX3000 determines the number conversion index according to [Call Source]. [Number Type] and this parameter. If the local office has originated the call. Related Commands See Table 15-26 for the commands related to auxiliary number processing. it will send SRI message to the HLR requesting for the route information of the called (called MSRN information) through MAP interface.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data It comprises two types of numbers. if the call is forwarded at the local office. IV. Table 15-26 List of commands related to auxiliary number processing Command LST AIDNUMPRO ADD AIDNUMPRO MOD AIDNUMPRO RMV AIDNUMPRO 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 15. set this parameter to "Connected Number". namely. If the MSOFTX3000 finds that the called subscriber is a mobile subscriber (whose called number type is "MSISDN") during the number analysis procedures. number type and number prefix. it will be addressed to the HLR. This table is used to control the addressing format of the called number before the MAP sends out the SRI message. connected number and forwarded-to number. Command ADD MAPIFNP III. [Number Prefix] It determines the prefix of the number specified in [Number Type].4 Configuring MAP Interface Number Processing Data I.8. II. After the recombination of the called number. Background Information This command is used to add records to MAP Interface Number Processing table. set it to "Forwarded-to Number". [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.

if there are different needs for the format of MSISDNs sent to the HLR. In details. that is. Related Commands See Table 15-27 for the commands related to MAP interface number processing. Background Information This command is used to add records to Bill Processing table. determining the address nature of the MSISDN to be converted. Note that only one conversion mode can be adopted for a number at a time. MSRNs and charging MSISDNs. the third-party numbers. However. formats 15-62 . In this case.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data It defines the prefix of the MSISDN to be converted when this MSISDN is sent to the HLR. [NUMBER FORMAT] These two parameters determine the mode to convert the MSISDN which is defined in [Number Prefix] and [Change on Map.Operation Manual . V. SCCP or SMMO]. convert the number into the designated number format. [CHANGE INDEX].5 Configure Bill Processing Information I. to normalize the numbers to be entered to bills. SCCP OR SMMO] It is an output parameter. the configuration of MAP Interface Number Processing table is no longer necessary. The table is used to realize the flexible number conversion over numbers on the bill when it is generated. two parameters cannot be set at the same time. If the data configurations of two parameters conflict.8. IV. data in this table should be configured. Note The format of all mobile subscriber numbers have been normalized into international number format during the incoming number pretreatment. MSISDNs contained in SRI message sent by MAP are of international number format. So generally. including calling numbers. [CHANGE ON MAP. that is. such as national number or subscriber number. 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 15. called numbers.

The MSOFTX3000 will convert the numbers of bill set in [Number Type] field according to this parameter. the maximum length of numbers entered to bills can be restricted. Therefore.8. prefixes. [Input Number Maximum Length] These parameters are used for the MSOFTX3000 to query Bill Processing table so as to determine numbers to be normalized on the bill. Table 15-28 List of commands related to bill information processing Command LST BILLPROC ADD BILLPROC MOD BILLPROC RMV BILLPROC Description To list bill information processing To add bill information processing To modify bill information processing To remove bill information processing 15. number format requirements of types of bills in different countries can be satisfied.Operation Manual . maximum length of numbers. 15-63 . II. Command ADD BILLPROC III. Background Information This command is used to add records to Bill Control table. [Number Change Index] It corresponds to [Number Change Index] in Number Change table. Moreover. The table is used to control the MSOFTX3000 to generate gateway mobile switching center (GMSC) bills and roaming bills for certain office directions.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data of numbers on bills can be converted according to bill types. [Number Prefix]. And the basic conversion or replacement of numbers are supported. number types. the MSOFTX3000 will delete the excessive digits automatically. IV. and address nature of numbers.6 Configuring Bill Control Data I. If the length of the number is more than that specified. [Output Number Maximum Length] It determines the maximum length of the number outputted after the conversion. [Address Nature]. [Number Type]. Related Commands See Table 15-28 for the commands related to bill information processing. Major Parameters [Bill Type].

the MSOFTX3000 will generate roaming bills for incoming calls from this office direction. if it is set to "Home Network". Through this parameter. the MSOFTX3000 can references the records in Bill Control table. Major Parameters [Office Direction] It is used to set the office direction that needs bill control. [Opposition Office Type] When it is set as "Other Networks". IV. 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. it is unnecessary to configure bill control data. II. In this way. Note: Bill control information must be configured for all non-home network office directions. When the local office serves as a VMSC. The planning comprises two parts: One is to determine call prefix 15-64 .9 Configuration Examples 15.9.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data When the local office serves as a GMSC. Related Commands See Table 15-29 for the commands related to bill control.Operation Manual . Table 15-29 List of commands related to bill control Command LST BILLPROC ADD BILLPROC MOD BILLPROC RMV BILLPROC 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 15. data planning should be accomplished first. no roaming bill will be generated. Command ADD BILLCTRL III. On the contrary.1 Planning of Number Analysis Data Before the configuration of number analysis data. the GMSC can provide bill control information related to this office direction.

that is. The following takes China as the example to detail the planning of number analysis data. as shown in Table 15-30. and [Gain] to "Toll Gain". the other is to determine call special processing data. [Toll Prefix Length] to "2".Operation Manual . or other special processing.9. Set [Query Toll Area Code table] to "Yes". intercept of certain calls. 0 International toll prefix International toll GMSC 6 PSTN 0 National toll prefix 1 2 3 4 5 6 7 8 9 Local MSISDN number segment National Roaming MSIDSN number segment National Toll GMSC 6 PSTN 0 0 0 0 0 0 0 0 0 Local Local Local Local Local Local Local Local Local PLMN Local MSCs GMSC GMSC GMSC GMSC GMSC GMSC GMSC GMSC GMSC 3 3 3 3 3 3 3 3 3 PSTN PSTN PSTN PSTN PSTN PSTN PSTN PSTN PSTN 0 65535 11 MSISDN 0 PLMN National Toll MSC 65535 11 MSISDN 15-65 . Table 15-30 VMSC call prefix data configuration DN Set Call Prefix Service Attribute Route Selection Code Minimum Number Length Called Number Type Description of other parameters Set [Query Toll Area Code table] to "Yes". and [Gain] to "Toll Gain". including normalization of irregular numbers.2 Planning of Call Prefix Data I.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data data. to select outgoing routes according to certain call prefixes. VMSC Call Prefix Data Most of the prefix data configured for VMSCs are consistent except those configured to meet certain special requirements. 15. [Toll Prefix Length] to "1".

as shown in Table 15-31. etc. listed in [Route Selection Code] respectively stand for the route selection codes corresponding to specific office directions. excluding those data of call configured for special processing and particular requirements of offices. GMSC Call Prefix Data Most of the prefix data configured for GMSCs are consistent except those configured to meet certain special requirements. TMSC. National roaming MSIDSN number segment refers to the national universal roaming number segment used by operators.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data 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 Service Attribute PLMN Home MSC Route Selection Code 65535 Minimum Number Length 11 Called Number Type MSRN/HO N Description of other parameters 0 0 PLMN Local MSC VMSC 11 MSRN/HO N 0 PLMN National Toll MSC TMSC 11 MSRN/HO N 0 Local GMSC Length of fire call number PSTN Set [Emergency Call Observation] to "Yes" and [Charging] to "No Chanrging". GMSC.Operation Manual . II. 0 Local GMSC/TMS C TMSC/IP front end processor GMSC Length of special service number IP call prefix length PSTN 0 IP call prefix PLMN international toll prefix Local Toll PSTN 9 PLMN Intl Toll MSC 13 MSRN/HO N Note: Table 15-30 contains only the basic call prefix data. 15-66 .

Operation Manual .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data 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. Set international toll prefix based on actual conditions. 0 National prefix toll National Toll 6 PSTN Set [Query Toll Area Code table] to "Yes" and [Gain] to "Toll Gain". Set national toll prefix based on actual conditions 0 1 Local 3 PSTN 0 2 Local 3 PSTN 0 3 Local 3 PSTN 0 4 Local 3 PSTN 0 5 Local 3 PSTN 0 6 Local 3 PSTN 0 7 Local 3 PSTN 15-67 . 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 0 International toll prefix International toll 6 PSTN Set [Query Toll Area Code table] to "Yes" and [Gain] to "Toll Gain".

Operation Manual . 0 Fire alarm call Local Length of fire call number PSTN 0 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 3 PSTN 0 Local 3 PSTN 0 Local 3 PSTN 0 Local 3 PSTN 0 Local 3 PSTN 0 Local 3 PSTN 0 Local 3 PSTN 0 Local 3 PSTN 0 Local 3 PSTN 0 PLMN Local MSC 11 MSISDN 15-68 .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data 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 Minimum Number Length 3 Number Type Description of other parameters 0 8 Local PSTN 0 9 Local 3 PSTN Set [Emergency Call Observation] to "Yes". and [Charging] to "No Charging".

0 National toll prefix + Local area code + special service number Local PSTN gateway exchange/T MSC PSTN 0 IP call prefix PLMN international toll prefix Local Toll TMSC/IP front end processor PSTN gateway exchange PSTN 9 PLMN Intl Toll MSC 13 MSRN/HO N 15-69 .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data 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 Route Selection Code Minimum Number Length Number Type Description of other parameters 0 PLMN National Toll MSC 65535 11 MSISDN 0 PLMN Local MSC VMSC 11 MSRN/HO N 0 PLMN National Toll MSC TMSC 11 MSRN/HO N 0 Local PSTN gateway exchange 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 Set [Emergency Call Observation] to "Yes". and [Charging] to "No Charging".Operation Manual .

Configure corresponding route selection codes in terms of various call types (basic all and forwarded call) during the enhanced route processing data configuration. Table 15-32 lists the basic principles for call special processing data configuration: Table 15-32 Call special processing configuration principles Call processing requirements Data configuration If the forwarded-to numbers are required to be normalized according to the original called attributes during incoming number pretreatment data configuration. In Table 15-31. 15-70 . Normalize incoming forwarded-to numbers Normalize forwarded-to numbers. TMSC. call special processing data are important for the number analysis data configuration. 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. GMSC. Configuration Principles Besides basic routing data of call prefixes. given in [Route Selection Code] respectively stand for the route selection codes corresponding to specific office directions. configure incoming original called number correlation processing data first. Select different routes for call prefixes in terms of various call types. Therefore. redirecting numbers are contained in SETUP messages sent to the trunk side). there are two modes available to process the prefixes of PSTN local calls (including emergency calls). excluding those configured for call special processing and for particular requirements of offices. In Table 15-31. 15. 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. 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. Select different routes in terms of various call prefix length. Configure corresponding route selection codes in terms of various call prefix length during enhanced route processing data configuration.Operation Manual . etc. and then configure incoming number pretreatment data. 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.3 Planning of Call Special Processing Data I. connected numbers and redirecting numbers accordingly during auxiliary number analysis data configuration. certain processing principles should be mastered so as to ensure the correctness and standard of the configuration. Normalize forwarded-to numbers.9.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data Note: Table 15-31 contains only the basic call prefix data in GMSC.

Suppose call source code related to this 15-71 . outgoing calling numbers and calling numbers in bills are all determined by normalized numbers). If the normalization should be carried out by calling features. Normalize calling numbers accordingly during calling number analysis data configuration. who have been prohibited from originating calls. And configure corresponding service check indexes for special service call prefixes in call prefix configuration. Realize number-receive delay based on certain call prefix. Normalize calling/called/original called numbers accordingly during outgoing number preprocessing data configuration. Requiring PSTN Subscriber to Dial National Toll Prefix "0" to Connect a Foreign Mobile Subscriber at GMSC [Requirement Analysis]: It is required to conduct call authority check configuration to determine the format of numbers dialed by subscribers. Normalize calling numbers (calling numbers being presented. to make special service calls. Allow subscribers. Set not to conduct service check over barring service in service check configuration. If it is required to normalize calling numbers being displayed according to called prefixes. Select routes right after converting called numbers. the MSOFTX3000 cannot obtain the corresponding MSRN through the number of this format. emergency call. for example. if the dialed number is "0+MSISDN".Operation Manual .4 Examples of Call Special Processing Data Configuration I. called Normalize calling numbers being presented. Set number-receive delay interval in Call Source table. configure CLIP called number correlation processing data first. Data configuration Set corresponding interception data according to the called party and corresponding failure processing data during call authority check data configuration.9. Therefore. Set number-receive delay interval in incoming number pretreatment data configuration. Configure corresponding conversion data for called numbers in DN processing data configuration. 15. if the normalization should be conducted through original called subscriber attributes. configure outgoing calling number correlation processing data first. Realize number-receive delay at the local office for incoming numbers from other offices. Normalize calling/called/original numbers of outgoing calls. However. Convert call prefixes and then reselect routes through converted prefixes. [Realization Script Example]: /* In the script. it is required to configure DN processing data so as to delete "0" through DN processing and then re-analyse the number. configure outgoing original called number correlation processing data first. PSTN subscriber is required to dial "0" to connect a foreign MS at the GMSC of certain mobile operator in China. Convert corresponding called numbers and set [Reanalyze] to "True" during DN processing data configuration.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data Call processing requirements Intercept calls in which the format of the numbers dialed are incorrect.

CLITP=ALL. CALLTY=COMMON. The processing type is "Continue Proceeding" */ ADD ADD CALLPRICHK: CALLPRICHK: CSC=7. PROCTY=PASSON. PROCTY=INHIBITED. PROCTY=PASSON. ADD CALLPRICHK: CSC=7. ADD CALLPRICHK: CSC=7. CALLTY=COMMON. "139222". CPFX=K'eeeeeeee. PFX=K'13800138007. PFX=K'136 CPFX=K'eeeeeeee. PFX=K'138222. /*Set call authority check over national universal MSISDN special numbers of this mobile operator. The pocessing type is "Continue Proceeding". CLIRP=ALL. CLITP=ALL. CLIRP=ALL. CPFX=K'eeeeeeee. CLITP=ALL. PFX=K'138111. CPFX=K'eeeeeeee. CALLTY=COMMON. that of national universal MSISDN special service numbers should be accomplished. CPFX=K'eeeeeeee.Operation Manual . PROCTY=PASSON. PFX=K'135. CLITP=ALL.*/ ADD ADD CALLPRICHK: CALLPRICHK: CSC=7. PFX=K'139111. CLIRP=ALL. CPFX=K'eeeeeeee. FCC=UD13. PROCTY=INHIBITED. during the configuration of corresponding data. CSC=7. but intercept those in which the universal MSISDN number segment is dialed. CALLTY=COMMON. CLIRP=ALL. FCC=UD13. PROCTY=PASSON. CLITP=ALL. PROCTY=INHIBITED. CALLTY=COMMON. Processing type: Prohibit. CLIRP=ALL. besides the configuration of local MSISDN and PPS number segment.*/ /*Set call authority check over local MSISDN number segment. CALLTY=COMMON. "139222". CSC=7. FCC=UD13. CLIRP=ALL. PROCTY=PASSON. Therefore. CLIRP=ALL. CLIRP=ALL. CALLTY=COMMON. ……………………. local MSISDN number segment comprises "139111". CLITP=ALL. PFX=K'139222. CPFX=K'eeeeeeee. /*Set call authority check over other national universal MSISDN number segment of the mobile operator. 15-72 . CLITP=ALL. CSC=7. Failure cause code: UD13 ("0" is not added when dialing a foreign mobile subscriber) */ ADD CALLPRICHK: CSC=7. The processing type is "Continue Proceeding". CALLTY=COMMON. … */ /* To intercept calls to a foreign MS. CPFX=K'eeeeeeee. ………………………… /* Set call authority check over local PPS number segment. CALLTY=COMMON.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data PSTN subscriber is 7. local PPS number segment comprises "138111". PFX=K'135. the MSOFTX3000 will connect calls in which the local mobile subscriber number segment is dialed. CLITP=ALL. CLIRP=ALL. PROCTY=PASSON. CPFX=K'eeeeeeee. ….*/ ADD ADD CALLPRICHK: CALLPRICHK: CSC=7. CLITP=ALL. PFX=K'13800138000.

CSTP=BASE. CLIRP=ALL. CLIRP=ALL. PFX=K'0135. PFX=K'0136. PFX=K'0136. /*Configure call prefix data and conduct DN processing for the national universal MSISDN number segments with toll prefix "0" of this mobile operator.*/ /*Set call authority check over national universal MSISDN number segment. CLITP=ALL. 0137. PFX=K'139. ADD CALLPRICHK: CSC=7. PFX=K'0135. /* Configure DN processing data for number segments like 0135. MAXL=15. ICLDTYPE=MS. [Realization Script Example]: /* Call source code of the call from this local mobile subscriber is "0". FCC=UD13. MOD CNACLD: P=0. MOD CNACLD: P=0. 15-73 . PROCTY=INHIBITED. CALLTY=COMMON. 0136. DCL=1. …………………. CLITP=ALL. Delete "0" before each number segment and then re-analyse these numbers. CSTP=BASE. */ ADD DNC: DCX=10. CLDNCX=10. PFX=K'0135. FCC=UD13. P=0. DNPREPARE=TRUE. CS=ALL. II. /*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. ADD PFXPRO: CSC=7. 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. CLIRP=ALL. CALLTY=COMMON. 0139. Processing Type: Prohibit. 0139. P=0. CSA=MNTT. ADD CALLPRICHK: CSC=7. MINL=12. DNPREPARE=TRUE. 0138. RMT=ALL. CS=ALL. FPT=SIG. PFX=K'0135. CSA=ALL. ADD PFXPRO: CSC=7. PROCTY=INHIBITED. CALLTY=COMMON. PROCTY=INHIBITED. TT= ADD0. CLDNCX=10. PFX=K'137. DAI=NONE. */ ADD CNACLD: P=0. CLITP=ALL.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data ADD CALLPRICHK: CSC=7. PFX=K'138. CLITP=ALL. CSA=MNTT. MAXL=15. PT=REANA. FCC= CS0. 0136. FCC=UD13. DCT=TYPE6. ADD CNACLD: P=0. RSC=65534. PFX=K'0136. ICLDTYPE=MS. STF=NSDT. 0138. RSC=65534. CPFX=K'eeeeeeee. PT=REANA.Operation Manual . CPFX=K'eeeeeeee. CPFX=K'eeeeeeee. RUT=ALL. Failure cause code: CS0 */ ADD CALLPRICHK: CSC=0 CALLTY=COMMON. CLIRP=ALL. But route selection will not be carried out. CPFX=K'eeeeeeee. PROCTY=INHIBITED. ……………………. STF=NSDT. 0137. MINL=12. such as 0135.

CLDADDR=ALL. CLDADDR=ALL. CSA=MSLO. of a local MSOFTX3000 in China is 13000222. MAXL=18. RMT=ALL. CLDADDR=ALL. 00) + International number". However. P=254. P=254. Thus the call to PLMN Home MSC subscriber can be connected. DDX=4..Operation Manual . 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. CLDADDR=ALL. CLIANA=FALSE.. P=254. CSC=65534. DDX=4. DCT=TYPE6. TG=13. DCL=4. numbered respectively as 1. So there are 4 call sources that obtain route information from the local office. /*Re-analyse VMSC local numbers after the DN processing*/ ADD DNC: DCX=5. DCP=0. FPT=SIG. RUT=ALL. ND=K'0086.*/ ADD DNC: DCX=4. ADD ADD ADD ADD OUTNUMPREPRO: OUTNUMPREPRO: OUTNUMPREPRO: OUTNUMPREPRO: CSC=65534.. the MSOFTX3000 will automatically add the international number prefix beofore international MSRNs and convert national MSRNs into national numbers through trunk group bearers. ADD CNACLD: P=0. ADDSIG=TRUE. In addition. P=254. DDX=4. 3 and 4. CLDT=MSRN. MOD CNACLD: P=0. III. when the local office serves as a VMSC.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data . PFX=K'13000111. TT=NODSTRB. CSTP=BASE. Trunk group Nos are 10 and 11. the MSRNs returned from the HLR are of international number format.. CSC=65534. The MSOFTX3000 is connected directly with a VMSC (No. DCT=TYPE1. 15-74 . */ ADD CFPRO: FCC=CS0. In this case. TG=12. DDX=4. PFX=K'13000111. CSA=ALL. PFX=K'13000111. /* 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). CSC=65534. The conversion is done in the outgoing number preprocessing mode. PFX=K'008613000222. 13000111) only. [Realization Script Example]: /* The No. PFX=K'13000111. PFX=K'008613000222. TG=10. it will convert such local MSRNs sent from other offices into national numbers and then re-analyse them. MINL=11. 2. Nos of trunk groups from the local MSOFTX3000 to TMSC are 12 and 13. FSC=0.. TG=11.

Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 15 Configuring Number Analysis Data ADD PFXPRO: CSC=65534. that is. SCI=0. RSC=2. MINL=3. configure corresponding service check data to disable call barring service for certain subscribers. PT=REANA. ICLDTYPE =PSTN. CSA=LCT. RSC=2. SCM=ODBBAOC-1&BAOC-1&ODBBOIC-1. ISERVICECHECKINDEX =0. CF=ALL. 119) [Requirement Analysis]: To satisfy this requirement. ICLDTYPE=PS. [Realization Script Example]: ADD SRVCHK: CSC=65534. PFX="008613000222". ICLDTYPE =PSTN. ICLDTYPE =PSTN. CSA=LC. ADD CNACLD: P=0. CSA=LCT. P=0. MINL=3. ADD CNACLD: P=0. ADD CNACLD: P=0. then configure corresponding service check indexes for such call prefixes during call prefix data configuration. ISERVICECHECKINDEX =0. PFX=K'122. CSA=LC. MAXL=15. 15-75 . IFSC=YES. PFX=K'119. MAXL=15. CLDNCX =5. the MSOFTX3000 is required not to conduct corresponding service check when such call prefixes are dialed. ADD CNACLD: P=0. RSC=2. MAXL=15. SCIDX=0. IV. Requiring VMSC to Allow Subscriber Being Barred to Make Emergency Calls (such as 110. MAXL=15. ISERVICECHECKINDEX= =0. 122. SCC=ODB_BAOC-0&BAOC-0&ODB_BOIC-0. RSC=2. NP=0. PFX=K'110.Operation Manual . MINL=3. MINL=3. PFX=K'120.

A cell is a base station area when omni-directional antenna is used.1 Introduction to the Chapter Mobile service data provides mobility management function performed on mobile subscribers of the local office and those who are roaming to the local office. Roaming Services Roaming services include VLR list based on roaming restriction.2 Related Concepts I. This roaming restriction can be achieved in HLR.Operation Manual . new location update is not required. zone code based on roaming area restriction. a paging message will be sent to all the base stations within a location area. If a subscriber roams from one cell to another cell (within the same location area). The data defines a subscriber’s roaming scope that is based on VLR serving coverage. It is only required to configure data in HLR. Roaming restriction based on VLR list VLR list is the subscription data of a mobile subscriber in HLR. A location area is divided into several cells. Service area identifier (SAI) is used to uniquely identify the coverage of one or more cells in one location area in wideband code division multiple access (WCDMA).Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 16 Configuring Mobile Service Data Chapter 16 Configuring Mobile Service Data 16. instead of in MSC. Service Area Location area refers to a covering scope where mobile subscribers can roam. Cell. When a mobile subscriber is called. 16-1 . A mobile subscriber will be roaming restricted if the mobile subscriber is roaming in a VLR. This chapter contains the following sections: Related Concepts Configuring Location Update Data Configuring Enhanced Roaming Restriction Data Configuring Roaming Zone Code Service Configuration Examples 16. Location Area. which is not included in the VLR list. II. and enhanced roaming restriction. Base station identity code (BSIC) or cell global identification (CGI) is used to identify a radio covering region of GSM. A mobile subscriber registers permitted roaming VLR list when the subscriber is defined in HLR.

GMLC is the gateway for LCS Client to access the network. III. so that cooperation between MSC and HLR makes it possible to flexibly specify location scope allowed for the mobile subscriber to roam. The external LCS Client originates location request to MSC through GMLC. See Figure 16-1 for the structure of the LCS system in 3GPP.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 16 Configuring Mobile Service Data Roaming area restriction based one zone code Zone code is subscription data of a subscriber in HLR. It is possible for MSC to independently provide LAI based roaming restriction function for particular user group without help of HLR. 16-2 . subscriber authentication. and local geographical change according to the longitude and latitude. Location Service Location service (LCS) refers to handling procedures where the mobile communication system originates a request for providing location of a mobile subscriber.Operation Manual . GMLC is responsible for LCS Client authorization. When location information of a mobile subscriber is needed. performs location measurement and calculation. Customized location areas covered by a zone code can be defined in MSC. the request is originated to GMLC through the Le interface. Enhanced roaming restriction Enhanced roaming restriction service is one of special services provided by the product. There is not a direct association between LCS Client service procedures and the LCS system. and transfers location outcome. {LMU Type A} CBC Note 1) Uu Iu BC {3GSGSN } Lh Iu 3G MSC Server HLR Node B UE {(LMU Type B)} Iub SRNC (SMLC functionality) Iur Lg GMLC Le External LCS client Lg Lc Node B {(LMU Type B)} Iub RNC GMLC gsmSCF Other PLMN Figure 16-1 LCS system structure in 3GPP The external LCS Client is responsible for specific services. The data can restrict roaming area of the mobile subscriber. MSC can also report location information to LCS Client through GMLC.

allocated by respective HLR. SN: subscriber number. the country code of China is 86. It is stored in HLR and conveyed on the MAP interface to VLR. A subscriber number consists of the following parts: HLR identification number: H0H1H2H3 Mobile subscriber number: ABCD. MSOFTX 3000 Lg GMLC Le External LCS Client MAP Protocol stack structure TCAP SCCP MTP3 Figure 16-2 Networking between MSOFTX3000 and GMLC IV. It is a paging area in WCDMA system.164 numbering format. 16-3 . Its structure is shown in Figure 16-3. V. The general format for MSISDN is “CC-NDC-H0H1H2H3-ABCD”. NDC: national destination code. CC NDC SN National (significant) Mobile number Mobile station international ISDN number Figure 16-3 MSISDN structure CC: country code. They are allocated from recommendation E. The LAI structure is shown in Figure 16-4.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 16 Configuring Mobile Service Data Networking model between MSOFTX3000 and GMLC is shown in Figure 16-2. LAI Numbering Principles LAI is used to identify the VLR serving coverage where a roaming subscriber is residing currently. For example.Operation Manual . MSISDN Numbering Principles MSISDN is mobile subscriber international ISDN number which is used to call a mobile subscriber by dialing it.

The service area code (SAC) together with the PLMN-ID and the LAC will constitute the SAI. MSC-Number is basically the same as VLR-Number. Add GT data (ADD SCCPGT). SAI = PLMN-ID + LAC + SAC The cell identification (CI) is of two bytes represented in Hex and can be customized in respective MSC. Add IMSI-GT data (ADD IMSIGT).Operation Manual .1 General Configuration Procedures The procedures for configuring location update data are as follows: 1) 2) 3) 4) Add LAI or CGI/SAI data (ADD LAIGCI or ADD LAISAI).Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center MCC MNC Chapter 16 Configuring Mobile Service Data LAC Location Area Identification Figure 16-4 LAI structure MCC: mobile country code. X1X2 is globally allocated by the telecommunication administration authorities. 16-4 . For example. In this numbering plan.164 numbering plan is used for MSC/VLR numbers. the mobile country code of China is 460. The format is “CC+NDC+LSP”. MSC/VLR Numbering Principles E. Hexadecimal location area code (LAC) of two bytes presents itself as X1X2X3X4. MNC: mobile network code. VI. Note that neither 0000 nor FFFE can be used. It is used in SS7 signaling messages for the purposes of representing MSC number. Add SCCP subsystem data (ADD SCCPSSN).3.3 Configuring Location Update Data 16. CC and NDC are the same as those defined in MSISDN. Currently MSC and VLR are physically integrated together. The SAI is used to identify an area consisting of one or more cells belonging to the same location area. CI must be unique within a location area. X3X4 is customized by the serving operator. LSP is customized by the serving operator and the national numbering authority in the PLMN's country. 16.

Note: MSC number is already defined in the SET INOFFMSC command.3. so that HLR can be found according to subscriber's IMSI. Command ADD LAIGCI or ADD LAISAI. IV.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 16 Configuring Mobile Service Data 16. Mobile country code is used to identity the country to which the mobile subscriber belongs.Operation Manual . Background Information None. III. II. For more information about this command. 16. Major Parameters [MCC + MNC] It refers to mobile country code + mobile network code. Related Commands None. Mobile access code is actually the national destination code. refer to Chapter 5.3 Setting Global Title Table I. Command ADD IMSIGT III. Mobile network code is used to identify the mobile network to which the mobile subscriber belongs. [CC + NDC] It refers to country code + national destination code. The data is contained in the address information field of the global title. Related Commands None. 16-5 .2 Setting LAI or CGI/SAI I. “Configuring Data for Interworking with RNC” or Chapter 6. II. “Configuring Data for Interworking with BSC”.3. Background Information This section describes how to establish mapping relationship between mobile country code + mobile network code and country code + mobile access code.

used to look for the corresponding HLR during location update. [Translation Type] The default value “00” is used in the mobile network. For the GT mentioned in 1). Background Information Global titles of both local MSC and HLR must be set in MSOFTX3000 for the purposes of addressing. select GT4(TYPE4)”. For the GT mentioned in 2). For the GT mentioned in 3).4 Setting SCCP GT I. It is associated with the parameter in the ADD SCCPSSN command. set this parameter to the prefix at the front of the called MSISDN. You have to configure the following data: Global title of HLR obtained according to IMSI. [Translation Result Type] 16-6 .Operation Manual . [GT Indicator] In the mobile network. Global title of HLR obtained according to the called MSISDN. Major Parameters [GT Index] It identifies a GT code uniquely. Global title of the local MSC. [NI] Set this parameter to “NATIONAL NETWORK”.3. used to look for the corresponding HLR during routing information provision procedure triggered by called number analysis. Command ADD SCCPGT III.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 16 Configuring Mobile Service Data 16. II. it is the same as “CC+NDC” in ADD IMSIGT command. [Numbering Plan] Set this parameter to “ISDNMOV (ISDN/mobile numbering plan)” for the GT mentioned in 1). [GT address information] This field accommodates the specific address information. set this parameter to MSC/VLR number which is already defined in the SET INOFFMSC command. Set it to “ISDN (ISDN/telephony numbering plan)” for the GT mentioned in 2) and 3).

5 Setting Local Office SCCP Subsystem I. Major Parameters [SSN Index] It specifies the unique number of the SCCP subsystem. whereas set it to “SPC” if there is a directly associated link to carry signaling. IV. Table 16-1 List of commands related to SCCP GT configuration Command ADD SCCPGT RMV SCCPGT MOD SCCPGT LST SCCPGT To add SCCP global title To remove existing SCCP global title To modify existing SCCP global title To list SCCP global title Description 16. As GMSC location update does not happen here. it is required to configure SCCP subsystems relating to MSC and HLR for location update procedure. 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. [Network Indicator] 16-7 . The GT translation result. However.3.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 16 Configuring Mobile Service Data Global title of local office SCCP users is translated to “DPC”. Use the LST SCCPSSN command to have a check to avoid repeated work. for VMSC. it is unnecessary to configure IMSI data. II. IMSI must be configured and it is also required to configure the global title of the adjacent VMSC for the purposes of handover.Operation Manual . It is unnecessary to set the MTP routing data. DPC. 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. 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). Command ADD SCCPSSN III. Background Information When MSOFTX3000 functions as GMSC. The data might be already configured as part of the local office information. Related Commands See Table 16-1 for the commands related to SCCP GT configuration.

16-8 . Default value is used as there are no backup subsystems.1 Configuration Description The example for 2G-MSC enhanced roaming restriction is as follows. In 3G enhanced roaming restriction.4.Operation Manual . Table 16-2 List of commands related to SCCP subsystem configuration Command ADD SCCPSSN RMV SCCPSSN MOD SCCPSSN LST SCCPSSN SET SCCPSSN DSP SCCPSSN To add SCCP subsystem To remove existing SCCP subsystem To modify existing SCCP subsystem To list SCCP subsystem To set SCCP subsystem status for maintenance purpose To display SCCP subsystem of the host Description 16.4 Configuring Enhanced Roaming Restriction Data 16. Related Commands See Table 16-2 for the commands related to SCCP subsystem configuration. Usually set this parameter to “NAT(National Network)” for MSC and HLR. only setting LAISAI (using the ADD/MOD LAISAI command) is different from 2G. The relationship between the parameters of the commands of enhanced roaming restriction is shown in Figure 16-5. [SPC][ OPC] SPC and local OPC are set for the local office in the national network for related subsystems of MSC. [Local Concerned SSN1]–[Local Concerned SSN5] Default values are used as there are no related subsystems. SPC is the point code of HLR. [Backup SSN Index] It is used to specify the index of the backup subsystem of the specified subsystem.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 16 Configuring Mobile Service Data Network indicator identifies the network where the SCCP subsystem is resident. OPC is the point code of MSC used in the national network. It is valid only when MSOFTX3000 supports the load sharing function or backup function of SCCP DSP. IV. For related subsystems of HLR. The codes are already defined in the SET OFI command.

”.” with “Location Group No.] [Location Group No. MOD MAPACCFG [Use Enhanced Roaming Restrict] .] ADD LOCGRP [Location No.Operation Manual ..” by the command ADD ROAMUSRT. user groups will be divided through “Start User Number” and “End User Number”. and the configuration procedures are as follows: 1) Group LAIs according to “Location Group No... There are two conditions for grouping users: When “MSISDN” or “IMSI” is specified for the parameter “Restricted by” with the command ADD ROAMRESTGRP.] . ADD LAIGCI [Global Cell ID] [Location No. and open the enhanced roaming restriction function to special LAI ).] [Roaming Subscriber Type] ADD ROAMUSRTP [IMSI Prefix] [Roaming Subscriber Type] Figure 16-5 Parameter relationship of Enhanced roaming restriction The parameters displayed in the figure must be configured..] [Perform Roaming Analysis] [LA Category] .. 3) Associate “User Group No. ADD ROAMRESTGRP [Restricted By] [Start User Number] [End User Number] [User Group No. to implement special user group roaming in special LAIs. 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”. define the relationship between location number and location group number.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 16 Configuring Mobile Service Data ADD USROAMRT [Roaming Restriction] [Location Group No.”. 2) Group the user groups according to some common characters through “User Group No. 16-9 . implemented by the lower two commands in the right column in Table 16-5. implemented by the commands in the left column in Figure 16-5 (used to set location number to LAI.] [User Group No.

4. you can select “Yes” for the parameter “Use Enhanced Roaming Restrict” in the command MOD MAPACCFG. Important Note: This step is not required if “Use Enhanced Roaming Restrict” in MAP information is already set to YES.4. to implement roaming restriction to all LAIs except LAI1. 16. Background Information This section describes how to add LAI grouping information. Command ADD LOCGRP III.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 16 Configuring Mobile Service Data The parameter “Use Enhanced Roaming Restrict” in the command MOD MAPACCF controls roaming restriction to all location areas in the local office.] 16-10 . Major Parameters [Use Enhanced Roaming Restrict] Set this parameter to YES if the enhanced roaming restriction services of an MSC are expected. II. Background Information This section describes how to enable MSC to support enhanced roaming restriction services.2 Starting Enhanced Roaming Restriction Function I. This parameter controls roaming restriction to all location areas in the local office. II.3 Configuring LAI Grouping Information I. while the parameter “Perform Roaming Analysis” in the command ADD/MOD LAIGCI controls roaming restriction to one special location area. 16. Command MOD MAPACCFG III. Major Parameters [Location No. Different location numbers can belong to the same location group. For instance. and then select “No” for the parameter “Perform Roaming Analysis” in the command ADD/MOD LAIGCI.Operation Manual .

Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 16 Configuring Mobile Service Data Location number identifies the LAI. and the "LA Category" must be set to LAI. [Location Group No. Major Parameters [Perform Roaming Analysis] Roaming analysis is performed to the special LAI. II. This parameter is not necessary in enhanced roaming restriction data configuration. III. Command ADD/MOD LAIGCI Note: This command is used to configure location area. [Zone Code] Zone code identifies the LAI code. This parameter is set to YES if the LAI is required with roaming restriction. One or more LAIs can share one location group number.Operation Manual . Background Information None. You can input “65535”.4.] Location group number identifies the LAI grouping information. Table 16-3 List of commands related to LAI grouping information configuration Command MOD LOCGRP RMV LOCGRP LST LOCGRP Description To modify LAI grouping information To remove LAI grouping information To list LAI grouping information 16.4 Configuring LAI I. [LA Type] 16-11 . Related Commands See Table 16-3 for the commands related to LAI grouping information configuration. When adding LAI. IV. Configure it if the zone code roaming restriction service is expected. use enhanced roaming restriction to the special LAI through location number.

The LAI of the local MSC/VLR is marked "HVLR" and the location area of non-local MSC/VLR is marked as "NBVLR". IV. You can set roaming restriction to a specific number segment based on user group. Command ADD ROAMRESTGRP III.”.Operation Manual . Major Parameters [Restricted By] Roaming restriction user group can be grouped based on IMSI. Related Commands See Table 16-4 for the commands related to LAI/GCI configuration. so set this parameter to "LAI" only. Background Information This section describes how to add a roaming restriction user group. set it to "HVLR". MSIDSN.” in the command ADD LOCGRP. you can only use the command MOD LAIGCI to set the parameters “Perform Roaming Analysis” and “Location No. or roaming user type. Table 16-4 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 16. and it is used for roaming restriction and to group multiple location areas into different location groups.5 Configuring Roaming Restriction User Group I. [LA Category] Roming restriction is performed only to LAI. It is related to the parameter “Location No. II. [Location No. Here.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 16 Configuring Mobile Service Data This parameter is used to decide whether the current LAI belongs to local VLR or adjacent VLR. If the LAI is already added.4. [Start User Number] 16-12 .] It is the indicator corresponding to a location area.

Operation Manual . It is necessary to enter the whole number with the country code. Command ADD ROAMUSRT 16-13 . Table 16-5 List of commands related to the configuration of roaming restriction user group Command MOD ROAMRESTGRP RMV ROAMRESTGRP LST ROAMRESTGRP Description To modify roaming restriction user group To remove roaming restriction user group To list roaming restriction user group 16. Background Information None. Related Commands See Table 16-5 for the commands related to the configuration of roaming restriction user group.4.] This parameter is used to set the user group number. [End User Number] When the parameter “Restricted By” is set to “IMSI” or “MSIDSN”. [Roaming Subscriber Type] When the parameter “Restricted by” is set to “Roaming Subscriber Type”. II. this parameter is used to set the start user number of the number segment for roaming restriction purposes.6 Configuring Roaming Subscriber Type I. IV. The same user group number accommodates subscribers with the same roaming restriction attribute. 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.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 16 Configuring Mobile Service Data When the parameter “Restricted By” is set to “IMSI” or “MSIDSN”. [User Group No. select the classification of different subscriber roaming in the local MSC.

international HPLMN MS. national HPLMN MS. Here you can enter proper bits as required. you need to set the command ADD ROAMUSRT. [Roaming Subscriber Type] Classify different subscriber roaming in the local MSC. It is a 15-bit exclusive number in the digital PLMN to identify an MS. so that cooperation between MSOFTX3000 and HLR 16-14 . and international inter-work MS.1 Service Description Zone code is subscription data of a subscriber in HLR. IV. There are five types of roaming users: local MS.Operation Manual . Related Commands See Table 16-6 for the commands related to the configuration of roaming subscriber type.5. Customized location areas covered by a zone code can be defined in MSOFTX3000. [MSC Number] It specifies the number of the local MSC. Define the IMSI number segment through “Roaming Subscriber Type”. Major Parameters Important Note: When selecting “Roaming Subscriber Type” for the parameter “Restricted by” in the command ADD ROAMRESTGRP. The data can restrict roaming area of the mobile subscriber. This parameter is related to the parameter “Roaming Subscriber Type” in the command ADD ROAMRESTGRP.5 Configuring Roaming Zone Code Service 16. [IMSI Prefix] This parameter is the international mobile subscriber identity prefix. national inter-work MS. Table 16-6 List of commands related to the configuration of roaming subscriber type Command MOD ROAMUSRT RMV ROAMUSRT LST ROAMUSRT Description To modify user group roaming authority To remove user group roaming authority To list user group roaming authority 16.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 16 Configuring Mobile Service Data III.

That is. The subscriber can access the service in the subscribed area. Otherwise. and different areas can be overlapped through different ZCs. To implement ZC restriction service regional subscription data is provided for mobile subscriber in HLR. as shown Figure 16-6. the subscriber is restricted when roamed-to LAI does not match the subscribed zone codes. 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. The regional subscription data is composed of 10 ZCs which restrict the available areas at most. The example is to define zone codes in MSC coverage.Operation Manual . ZC is defined by operator in the MSC.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 16 Configuring Mobile Service Data makes it possible to flexibly specify location scope allowed for the mobile subscriber to roam. A ZC might be shared by one and more LAIs. and the level of ZC is related to LAI. ZC defined by the local office is unique in PLMN. If there is no regional subscription data. the subscriber is restricted except the emergence service. ZC=1110 ZC=1120 LAI1 LAI3 LAI2 Figure 16-7 The relationship between Zone code and LAI 16-15 . the subscriber can access the services. Zone code area roaming restriction service is a kind of roaming and services access restriction service based on LAI.

Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 16 Configuring Mobile Service Data According to the restriction principles of zone code restriction services. Open ZC restriction function flag to configure ZC restriction support function in MAP function table... Configure LAI information to define location number of LAIs. ADD LAIGCI Global Cell ID Location No. ADD ZC Zone Code Zone Name ADD LOCGRP Zone Code Location No. The parameters displayed in Figure 16-8 must be configured.5. Configure LAI grouping information to associate location number of LAIs and ZC. if User A has subscribed ZC=1110 service. Perform Roaming Analysis . and the configuration procedures are as follows: 1) 2) 3) 4) Define ZC for LAIs in MSC. Location Group No. MOD MAPACCFG Support Zone Code Restriction Figure 16-8 Parameter relationship of ZC restriction 16-16 . 16.2 Configuration Description Here is an example for 2G-MSC ZC restriction.Operation Manual . only setting LAISAI (using the ADD/MOD LAISAI command) is different from 2G. User A can neither access the network nor enjoy provided services when User A is in LAI3 currently. In 3G ZC restriction. User A can access the network and enjoy provided services when User A is in LAI1 or LAI2 currently.

Important Note: This step is not required if “support zone code restriction” in MAP information is already set to YES. 16-17 . Background Information This section describes how to allocate zone codes to MSC controlled LAIs. this table will be queried once a zone code from HLR is received. [Zone Name] It identifies an area.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 16 Configuring Mobile Service Data 16. It is unique in the PLMN. That is. Command ADD ZC III. Major Parameters [Zone Code] Zone code is used for ZC area restriction service. Background Information This section describes how to enable MSC to support zone code restriction services.Operation Manual .5. The same zone code can be allocated for different LAIs. the subscriber is restricted when roamed-to LAI does not match the zone code. IV.4 Adding Zone Code I. Major Parameters [Support Zone Code Restriction] Set this parameter to YES if the zone code restriction services of an MSC are expected.5. Consequently. Related Commands None. If the zone code is not found in the table. II. 16. It is required to use the ADD ZC command to configure all zone codes of MSC. the concerned subscriber will be restricted to access. II.3 Starting Zone Code Restriction Function I. Command MOD MAPACCFG III. This parameter controls ZC restriction to all location areas in the local office.

IV. Related Commands See Table 16-8 for the commands related to LAI grouping information configuration. II. Table 16-8 List of commands related to LAI grouping information configuration Command MOD LOCGRP RMV LOCGRP LST LOCGRP Description To modify LAI grouping information To remove LAI grouping information To list LAI grouping information 16-18 . [Location group No. One or more LAIs can share one location group number. Related Commands See Table 16-7 for the commands related to roaming zone code configuration.5. Table 16-7 List of commands related to roaming zone code configuration Command ADD ZC RMV ZC LST ZC Description To add roaming zone code To remove roaming zone code To list roaming zone code 16. use ZC roaming restriction to the special LA through special location number. Background Information This section describes how to configure the relationship between ZC and LAI.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 16 Configuring Mobile Service Data IV. Major Parameters [Location No. It is used for enhanced roaming restriction. Command ADD LOCGRP III.5 Configuring the Relationship Between ZC and LAI I. [Zone code] Zone code is already defined in the ADD ZC command.] Location group number identifies the LAI grouping information. Different location numbers can belong to the same ZC. When adding LAI.] Location number identifies the LAI.Operation Manual . Here you need not set it.

you can use the command MOD LAIGCI to configure the parameters “Perform Roaming Analysis” and “Location No. If the LAI is already added. and the "LA Category" must be set to LAI.] It is the indicator corresponding to a location area. Major Parameters [Perform Roaming Analysis] Roaming analysis is performed to the special LAI.Operation Manual . so set this parameter to "LAI" only. Here. Table 16-9 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 16-19 Description . Related Commands See Table 16-9 for the commands related to LAI/CGI configuration. [Location No.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 16 Configuring Mobile Service Data 16. II. III. The LAI of the local MSC/VLR is marked as "HVLR" and the location area of non-local MSC/VLR is marked as "NBVLR".6 Configuring LAI I. Background Information None. Command ADD/MOD LAIGCI Note: This command is used to configure location area. and it is used for roaming restriction.5.”. Set this parameter to YES if the LAI is required with roaming restriction. [LA Type] This parameter is used to decide whether the current LAI belongs to local VLR or adjacent VLR.” in the command ADD LOCGRP. IV. It is related to the parameter “Location No. set it to "Local VLR". [LA Category] Roming restriction is performed only to LAI.

2 Configuring Zone Code Restriction I.1 Configuring Enhanced Roaming Restriction to Number Segment by LAI I. ADD LOCGRP: LOCNO=9. MOD LAIGCI: GCI="460010066". LAIT=HVLR. ADD USROAMRT: USRGRP=11. Data Description The task is to define zone codes in 2G MSC coverage according to Figure 16-9. It is assumed that the corresponding location number of the LA is 9. ROAMREST=YES. ENDNUM=K'8613911901100.6. II. MOD MAPACCFG: IFSZCD=YES. Data Configuration According to Figure 16-9. Note that roaming analysis flag of the LA shall be set to YES and enhanced roaming restriction support flag in MAP information shall be set to YES.6. Data Description Assume that the MSISDN number segment of the local office is from 8613911901000 to 8613911901100. LOCGRPNO=8. and the location group number is 8. Data Configuration MOD MAPACCFG: IFUSROAMR=YES.6 Configuration Examples 16. MSC ZC=1110 ZC=1120 LAI1=460-00-270 LAI2=460-00-271 LAI3=460-00-280 Figure 16-9 Definition of zone codes II. BEGINNUM=K'8613911901000. LOCNO =9. LOCGPNO=8. and the user group number is 11. USRGRP=11.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 16 Configuring Mobile Service Data 16. zone codes of LAIs under MSC are configured as follows: 1) Open the ZC restriction flag. IFROAMANA=YES.Operation Manual . ADD ROAMRESTGRP: RSTRIBY=MSISDN. 16-20 . The task is to add enhanced roaming restriction to mobile subscribers in the LA 460010066. 16.

IFROAMANA=YES. ADD ZC: ZC=K'1110. 16. LOCNO =1. 3) Configure the relationship between ZC and LAI. LST NCODE: LST NCODE: NC=K'44. ADD ZC: ZC=K'1120. ADD LOCGRP: LOCNO =1.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 16 Configuring Mobile Service Data 2) Configure ZC. When a mobile subscriber in LAI 460009999 dials a special service number “110”.6. If not. LAIT=HVLR. MOD LAIGCI: GCI="46000271". ADD GMLCCLT: CLTID=K'8613800001111. Data Configuration First query whether or not the country code for England is already set. ADD ROAMUSRT: IMSIPFX="2340126". Data Description It is assumed that GMLC number is 8613900128.3 Configuring Location Service Data I. 16-21 . add it. ZCNAME="zc2_LAI3". IFROAMANA=YES. 16. ADD IMSIGT: MCCMNC="23401". and GMLC client ID is 8613800001111. II. MSCN="861390001". CCNDC="44236". GMLC=K'8613900128. LAIT=HVLR. ADD ECLLCSCLT: DN=K'110. ZCNAME="zc1_LAI1_and_LAI2". 4) Configure LAI. GCI="460009999". Data Description The task is to add international roaming data for roaming to England. LOCNO =1.6. ADD LOCGRP: LOCNO =2. It is assumed that England’s country code is 44. ZC="1110". and prefix of the roaming subscriber’s IMSI is 2340126. Data Configuration ADD GMLC: GMLC=K'8613900128. MCCMNC is 23401. LOCNO =2. II. MOD LAIGCI: GCI="46000280". MSTP=INTOTHMS. LAIT=HVLR. IFROAMANA=YES. The local MSC number is 861390001. CCNDC is 44236. signaling point code of the international gateway is 222222. it is required to report location information to GMLC.4 Adding International Roaming Data of a Newly Subscribed Country or Region I. MOD LAIGCI: GCI="46000270".Operation Manual . CLTID =K'8613800001111. ZC="1120".

ADDREXP=INTER. RESULTT=STP1. ADDR=K'44236.Operation Manual . NUMPLAN=ISDNMOV. SPC="222222". 16-22 .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 16 Configuring Mobile Service Data ADD SCCPGT: GTX=1. GTI=GT4.

II. number segment triggering. 17. 17. intelligent calls triggered by number segment are divided into two types: overlay incoming intelligent calls and the calls triggered by the local office number segment. SSP/IP will query data configurations according to the number segment to obtain the intelligent subscriber’s service key and SCP address.Operation Manual . MSC/GMSC will route these calls to the corresponding SSP/IP if the calling subscribers or the called subscribers are in the special number segment for intelligent subscribers. Overlay Incoming Intelligent Call Upon receiving a call from GMSC. MSC/GMSC will add 1or 2-digit area prefix before the called numbers to indicate the present area of MSC/GMSC. when the local office is an MSC/GMSC without SSP/IP function and receives Mobile Originated (MO) or Mobile Terminated (MT) calls. In addition.2. and standard CAMEL3 service triggering.3 Triggering of IN Service by Number Segment I. If so.1 Introduction to the Chapter This chapter describes basic concepts and data configuration procedures of Intelligent Network (IN) services.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 17 Configuring IN Service Data Chapter 17 Configuring IN Service Data 17. This chapter contains the following sections: Related Concepts Data Configuration Principles Procedures for Configuring IN Service Data Configuration Examples 17. Classification In terms of call source.1 Modes for Triggering IN Services Three modes are used to trigger IN services: overlay outgoing. SSP/IP judges whether an IN subscriber is related in this call according to the calling/called number. SSP/IP will also obtain the calling subscriber location 17-1 .2.2.2 Triggering of Overlay Outgoing Intelligent Call In the wireless intelligent network in which overlay mode is implemented.2 Related Concepts 17.

and that of called subscriber corresponds to N-CSI DP12/DP13/DP14. and location information of the calling or called subscriber. the VMSC or GMSC will determine whether to trigger the IN service through calling number analysis (or calling number attribute analysis) and number initial processing over calling/called subscribers during number analysis. and complete the intelligent call according to SCP call control instructions. III. In addition. called number. Intelligent Calls Triggered by Local Office Number Segment When VMSC or GMSC functions as an SSP/IP. upon receiving a call originated by a local office subscriber or PSTN subscriber. Number segment triggering of calling subscriber corresponds to N-CSI DP2/DP4. even when the call fails. the VMSC or GMSC can still determine whether to trigger IN service according to the failure cause and calling number. SSP/IP triggers the appropriate calling/called IN service procedure. the VMSC or GMSC will obtain the service key and SCP address information corresponding to the IN service according to the data configuration.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 17 Configuring IN Service Data information according to the special prefix of the called number. You can control whether to trigger NCSI DP2 before obtaining MSRN or after obtaining MSRN by configuring the intelligent trigger point configuration table. N-CSI DP2 The table query flow for N-CSI DP2 triggering is shown in Figure 17-1. If the called party is a mobile subscriber.Operation Manual . then trigger the IN service. SSP/IP will get from HLR the roaming number (MSRN) related to the called subscriber. and reports to SCP the service key. If it is necessary to trigger the IN service. 17-2 . SSP/IP conducts intelligent call handling based on the call control instructions from the SCP. calling number. Subsequently. and then obtain the location information according to the roaming number of the called subscriber.

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. 17-3 . N-CSI DP4 The table query flow triggered by N-CSI DP4 is shown in Figure 17-2. the VMSC or GMSC will query the calling number analysis table. If a record is matched and N_CSI DP 2 is triggered. If the number is not matched or N_CSI DP2 is not triggered. then query the SCP addressing information table to obtain the SCP address and SCP ID according to “SCP Addressing Index”. the VMSC or GMSC will continue to search the calling characteristics analysis table.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Calling number analysis Chapter 17 Configuring IN Service Data Record matched and NCSI_DP2 triggered? N Calling attribute analysis table Y Y Record matched and NCSI_DP2 triggered? N SCP parameter information table SCP address information table IN service not triggered Figure 17-1 Table query flow for DP2 triggering During calling number analysis. and then query the SCP addressing information table to obtain the SCP address and SCP ID according to “SCP Addressing Index”. If the number is matched and the “Processing Type” is set to "Trigger N-CSI DP2".Operation Manual . 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.

Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Failure processing table Chapter 17 Configuring IN Service Data Record matched and NCSI_DP4 triggered? N Y Failure processing IN service parameter table SCP parameter information table SCP address information table IN service not triggered Figure 17-2 Table query flow triggered by DP4 If the call fails. 17-4 .Operation Manual . If the failure cause code is matched and “Processing Type” is set to "Trigger N-CSI DP4". According to the parameter “SCP Parameter 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. the VMSC or GMSC will query the failure processing table according to the failure cause. the VMSC or GMSC will refer to the failure processing IN service parameter table for the SCP parameter index. the VMSC or GMSC will then query the SCP parameter information table for service key and SCP addressing index.

Short message service CAMEL subscription information (SMS-CSI). Mobility management CAMEL subscription information (M-CSI). Introduction to Standard CAMEL 3 IN Service In the standard mobile intelligent network. 17-5 . If the corresponding called number is found.Operation Manual . the VMSC or GMSC will query the number initial special processing table. Supplementary service invocation notification CAMEL subscription information (SS-CSI).4 Triggering of Standard CAMEL 3 IN Service I. This chapter covers only N-CSI data configuration. Dialed services CAMEL subscription information (D-CSI). 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”. VMSC terminating CAMEL subscription information (VT-CSI). and the parameter “Processing Type” is set to "Trigger N-CSI DP12". Network CAMEL service information (N-CSI).2. CAMEL subscription information includes: Originating CAMEL subscription information (O-CSI). 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”. 17. Terminating CAMEL subscription information (T-CSI).Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Number initial special processing table Chapter 17 Configuring IN Service Data Record matched and NCSI_DP12 triggered? N Y SCP parameter information table IN service not triggered SCP address information table Figure 17-3 Table query flow triggered by DP12 Before obtaining the roaming number of the called subscriber and conducting the secondary analysis. IN services are triggered according to the CAMEL subscription information (CSI) of the subscriber data.

17. including MTP signaling data and SCCP signaling data. III.Operation Manual . When the subscriber dials "0755666". provides the function for triggering IN services by dialing special access numbers in the network. the data to be configured for MSOFT3000 includes N-CSI DP3 information and D-CSI information. so as to achieve flexible rule matching. the IN service will still be triggered by deleting "0755 (area code)" through the D-CSI auxiliary configuration. the D-CSI subscribed by the subscriber is "666 Triggering". If the local MSC also functions as an overlay SSP. For example. N-CSI DP3 IN service will be triggered.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 17 Configuring IN Service Data N-CSI. which is usually stored in the MSC. 17-6 . II. the conversion over the called number dialed by this subscriber will be conducted through D-CSI auxiliary configuration during the IN service triggering.3 Data Configuration Principles General principles for configuring IN service data are as follows: SCP signaling data shall be configured correctly. N-CSI DP3 The table query flow for N-CSI DP3 is shown in Figure 17-4. the data related to IN service attributes shall be configured. Special resource capability data of SSP service shall be configured correctly. N-CSI Access code mode Home SCP mode Access code index TDP access code table Access code index and database field length SCP configuration table Office TDP configuration Service key SCP parameter index SCP parameter information SCP address information SCP address information Figure 17-4 Table query flow for N-CSIDP3 triggering If the calling number and the dialed prefix match the record of NCSI information. For the standard CAMEL3 IN service triggering. D-CSI If the subscriber has subscribed D-CSI data.

Add number initial special processing (ADD PFXPRO). Add SCP parameter information (ADD SCPPARA). Add TDP access code (ADD TDPAC).Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 17 Configuring IN Service Data If the local office provides SSP function.4. IN Services Triggered by Access Code Steps for configuring data for triggering N-CSI DP3 are as follows: 1) 2) 3) Add SCP addressing information (ADD SCPINFO). Add SCP parameter information (ADD SCPPARA). Add failure processing (ADD CFPRO).4 Procedures for Configuring IN Service Data 17.2 Configuring Data for Triggering N-CSI DP2 Steps for configuring data for triggering N-CSI DP2 are as follows: 1) 2) 3) Add SCP addressing information (ADD SCPINFO). all the data related to SCP shall be negotiated with the SCP. 17.4.4. and database index.4.4 Configuring Data for Triggering N-CSI DP4 Steps for configuring data for triggering N-CSI DP4 are as follows: 1) 2) 3) 4) Add SCP addressing information (ADD SCPINFO).4. such data includes SCP address. Add SCP configuration information (ADD SCPCFG). Add SCP parameter information (ADD SCPPARA).3 Configuring Data for Triggering N-CSI DP12 Steps for configuring data for triggering N-CSI DP12 are as follows: 1) 2) 3) Add SCP addressing information (ADD SCPINFO). Add SSP service specialized resource capability data (ADD SSPCAPA). 17. Add IN service failure processing parameter information (ADD INFLPRO). The specific data configuration steps may vary with different triggering modes. Add SCP parameter information (ADD SCPPARA). For IN services. service key.1 Configuring Basic Data of Local Office with SSP Function Steps for configuring the basic data of the local office with SSP function are as follows: 1) 2) 3) Add SCP addressing information (ADD SCPINFO).Operation Manual . 17-7 . 17. 17.5 Configuring Data for Triggering N-CSI DP3 I. 17. Add calling number analysis (ADD CNACLR).

For example. When there is large amount of traffic. The access mode is set to “access code”. This can be achieved by the configuration of D-CSI. Add D-CSI information (ADD DCSICFG). the number dialed by a subscriber should be converted. The differences between "access code" mode and "home SCP" mode lie in: By the "home SCP" mode. "#" have to be deleted. Note: If the parameter “Calling Number” in the ADD NCSICFG command is set to "eeeeeeee". By the "access code" mode. II. “Number conversion index” is used to query the number conversion table. The access mode is set to “home SCP”. corresponding relationship between access code and service key is established through the parameters “access code index” and “service key”. Data configuration flow is as follows: 1) 2) Add number conversion (ADD DNC). 17-8 . Access code index “Access Code Index” corresponds to the “access code index” ACIDX in the ADD TDPAC command.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 17 Configuring IN Service Data 4) Add TDP configuration information (ADD ITDPCFG). Add N-CSI (ADD NCSICFG). symbols in the number like "*".4. IN Services Triggered by HOME SCP Steps for configuring data for triggering N-CSI DP3 are as follows: 1) 2) 3) Add SCP addressing information (ADD SCPINFO).6 Configuring Data for Triggering DCSI In some cases. N-CSI DP3 will be triggered when any caller makes a call to the concerned number. Note: In this step.Operation Manual . detection points (DPs) used to trigger subscriber recharge and service query are set. Multiple SCPs can be found according to database location and service key. location of the database is found based on the parameter “Access Code Index” in office TDP configuration information. 5) Add N-CSI (ADD NCSICFG). different SCPs can be selected in turn. the specific SCP will be indexed according to "SCP Parameter Index". Add SCP parameter information (ADD SCPPARA). 17.

In this case. The route selection code is the route number from the local office to MSC with SSF. If the parameter “Trigger” is specified as YES. Conversion is performed on the called number. If it is found that called number conversion is required. Called Overlay Outgoing The analysis process of a called overlay outgoing intelligent call is as follows: 1) 2) 3) 4) 5) 6) The call prefix table is queried. II. A suitable route is selected for outgoing.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 17 Configuring IN Service Data 17. Number conversion is performed.Operation Manual . "Processing type” is set to "immediacy route selection". III. A proper route is selected for outgoing. The corresponding data configuration steps are as follows: 1) Add number conversion (ADD DNC). number conversion is necessary for the called number. Calling Overlay Outgoing The analysis process of a calling overlay outgoing intelligent call is as follows: 1) 2) 3) The calling number analysis table is queried. When A calls B and in case either is an intelligent subscriber.4. the called number shall be added with area prefix. Overlay Incoming The analysis process of an overlay incoming intelligent call is as follows: 1) 2) 3) The IN service attribute table is queried. overlay calls from a certain call source are allowed. Add calling number analysis (ADD CNACLR). 2) 3) Add call prefix (ADD CNACLD) Add number initial special processing (ADD PFXPRO). a prefix is added at the front of the called number. The corresponding data configuration steps are as follows: 1) 2) Add number conversion (ADD DNC). The number initial special processing table is queried. An area prefix is added before the number. For MSC without service switching function (SSF). An area prefix is added at the front of the called number. an area prefix is added before the called number when the call involves an intelligent subscriber. 17-9 . It is found that called number conversion is required and re-analysis after conversion is necessary.7 Configuring Data in Overlay Mode I. Number analysis is conducted again. The number is handled after the prefix has been removed. and the parameter [Processing Type] shall be specified as "number re-analysis".

whose number prefix is 1390231. various special resources shall be employed for the interactions with subscribers.5. Otherwise. emergency calls such as fire call and police call will be connected quickly without triggering IN service. Intelligent calls are triggered by local office number segment directly. For such numbers. Remove the area prefix from the number of the overlay incoming call. Version Number of the CAP supported by the SCP is 3. SCP addressing index is 1. relevant data will be set to the special number information. special resource capability data of SSP service shall be configured correctly to ensure that correct tones will be sent to subscribers and digit collection can be conducted error-free.1 IN Services Triggered by N-CSI DP3 I. and the service key is 2. When the system judges that a special number is dialed. 17-10 .1 “Configuring Basic Data of Local Office with SSP Function”. special intelligent resource capability data is also used for the traffic measurement of IN service. set the parameter to NO.4. The local office possesses SSP function. Add IN service attribute information (ADD INSATTR). For different data configuration of N-CSI triggering.4. Area code where the calling subscriber locates is obtained. To describe the special resource capabilities of the services supported by the local MSC. the IN service processing procedure will not be triggered. In addition. SCP parameter index is 2.Operation Manual .5 Configuration Examples 17. ADD SPCLDN: SPCLDN=K'112.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 17 Configuring IN Service Data For the MSC with SSF. the data configuration steps are as follows: 1) 2) Add number conversion (ADD DNC). 17. Data Description It is assumed that the access code of charging and querying flow of a certain pre-paid service is "13800138000". The local MSC is interconnected with the SCP whose address is "8613900123".4.9 Managing Special Number Information During actual operation.8 Configuring Special Intelligent Resource Capability Data When IN service is triggered. 17. refer to the relevant part in 17. The prefix before the called number is removed. 17. "Home SCP” is set as the access mode for mobile subscribers. You can configure the data by executing the command ADD SSPCAPA. The parameter “Trigger” is set to YES if triggering of IN services is required. and used to judge whether the current module supports the corresponding service logic when other modules apply for the special resources of the current module.

5. II. Data Cescription It is assumed that the access code of charging and querying flow of a certain pre-paid service is "13800138000". The call source and routing data have been set. SCFID="1". SCPPARAIDX=2. Data Configuration ADD SCPINFO: SCPADDRIDX=1. It is required to add "80" at the beginning of called numbers for intelligent calls from area B (call source code: 2) and then route them to SSP1. The local office is a VMSC that shall be configured with overlay outgoing data. CLDPFX=K'13800138000. whose number prefix is 1390231. FCC=CAN. RUT=ALL. INST=DP4. CLIPFX=K'1390231.3 Overlay Outgoing I. Data Configuration ADD SCPINFO: SCPADDRIDX=1. ADD INFLPRO: DPNUM=DP4. FSC=0.Operation Manual . SSPCAPA=IPRA-1&VOICEBACK-1&SPREC-1&VOICEREC-1&TEXTTOV-1. SCPADDRIDX=1. ADD NCSICFG: CLIPFX=K'1390231. too.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 17 Configuring IN Service Data II. SSPCAPA=IPRA-1&VOICEBACK-1&SPREC-1&VOICEREC-1&TEXTTOV-1. The intelligent call will be processed by the service key 4 of the SCP with the number "8613900123". CAPVER=3. SRVKEY=2. N-CSI DP4 is triggered when a call. SCPPARAIDX=1. CAPVER=3. DCH=RELESCALL. ADD SSPCAPA: SRVKEY=2.5. it is required to add "40" at the beginning of called numbers for intelligent calls from area A (call source code: 1) and then route them to the SSP1. ADD SCPPARA: SCPPARAIDX=1. originated by any subscriber with the local office number segment "1390231". CSA=ALL. SCPADDR=K'8613900123. ADD CFPRO: FCC=CAN. Data Description It is assumed that the access code of charging and querying flow of a certain pre-paid service is "13800138000". The serving area of the VMSC includes areas A and B. SRVKEY=4. The route selection source code of the route to SSP1 is 0 and the route selection code is 5. 17-11 . DCH=RELESCALL. AMODE=HOMESCP.2 IN Services Triggered by N-CSI DP4 I. ADD SCPPARA: SCPPARAIDX=2. FPT=RSRT. 17. SCPADDRIDX=1. SCFID="1". whose number prefix is 1390231. According to the plan. "Home SCP” is set as the access mode for mobile subscribers. "Home SCP” is set as the access mode for mobile subscribers. fails due to call barring. SCPADDR=K'8613900123. 17. ADD SSPCAPA: SRVKEY=4.

ADD CALLSRC: CSC=1. PFX=K'6666. ICLDTYPE=UN. GAIN=LGN.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 17 Configuring IN Service Data II. GAIN=LGN. RCM=NOC. CS=ALL. CLIN=K'1390230. ECOS=NO. ADD CALLSRC: CSC=2. CSCNAME="overlay_A". ADD CNACLR: CSC=2. DCT=TYPE1. PT=REANA. DAI=NONE. CSA=MLC. STF=NSDT. DAI=NONE. CSCNAME="overlay_B". ADD CNACLD: PFX=K'801380000. PT=IMRS. CS=ALL. DCT=TYPE1. SDESCRIPTION="IN-CALL-40". Called overlay outgoing data configuration ADD DNC: DCX=3. ADD PFXPRO: CSC=2. OTHERSRC=UNDIRECTED. NDPRI=FALSE. CS=ALL. CLINCX=3. CLIN=K'1390231. CSCNAME="overlay_B". 17-12 . RSC=5. MINL=9. ADD CALLSRC: CSC=1. DCT=TYPE1. ISEACM=FALSE. PFX="1380000". RSC=5. ECOS=NO. PT=IMRS. DCT=TYPE1. ND=K'80. ND=K'40. Data Configuration Calling overlay outgoing data configuration ADD DNC: DCX=3. CLDNCX=3. ADD CNACLR: CSC=1. MINL=7. ADD PFXPRO: CSC=1. NDPRI=FALSE. IAC=NO. CSTP=BASE. OTHERSRC=UNDIRECTED. CAT=NO. OTHERSRC=UNDIRECTED. PFX="1380000". NDPRI=FALSE. CSTP=BASE. RSC=5. NP=0. MAXL=11. ND=K'80. CS=ALL. ADD CNACLD: PFX=K'401380000.Operation Manual . IAC=NO. DAI=NONE. MAXL=11. ISEACM=FALSE. NDPRI=FALSE. CAT=NO. CLDNCX=4. PT= REANA. CSA=MLC. RSC=5. CSCNAME="overlay_A". ICLDTYPE=UN. RCM=NOC. NP=0. ADD DNC: DCX=4. OTHERSRC=UNDIRECTED. CLINCX=4. DAI=NONE. ADD CALLSRC: CSC=2. ADD DNC: DCX=4. STF=NSDT. PFX=K'6666. ND=K'40. SDESCRIPTION="IN-CALL-80".

2 Debugging Methods Follow the steps below for debugging: 1) 2) 3) Check if the MGW can be pinged successfully.2.248) 18.2 Debugging of SCTP 18. start the SCTP message trace.1 Background Information An example of a typical SCTP message interaction process is as shown in Figure 18-1. Use the command LST FECFG to check if the interface IP address of MSOFTX3000 is consistent with the data configuration plan. This chapter contains the following sections: Debugging of SCTP Debugging of M3UA Debugging of Mc (H. and analyze if the message content is valid. M3UA. Decide based on trace results if other debugging methods are required as checking parameters. 18-1 .1 Introduction to the Chapter This chapter focuses on the debugging methods of SCTP. If inconsistent. Figure 18-1 SCTP message interaction process To locate an SCTP issue. 4) If MSOFTX3000 and MGW are not directly connected. correct it. check if the message flow is correct. Check if the physical connection is normal. 18.Operation Manual .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 18 Debugging Chapter 18 Debugging 18. and H.2. use the command LST FECFG to check if the gateway IP address is correctly configured.248 protocols applied in MSOFTX3000.

3 FAQ I. Use LST SCTPPARA to check if the two ends are consistent in checksum algorithm. II. Cause analysis SCTP supports two checksum modes: ADLER32 and CRC32. Summary and suggestions This problem is generally caused by inconsistency of checksum algorithm between local and peer end. but it responds with the Abort message. use the command MOD MGW to modify the configuration. The two ends cannot be server or client at the same time. 18. and MGW is configured as a client. MSOFTX3000 is configured as a server. which are both supported in the MSOFTX3000. No Response from the Local SCTP Server End for INIT Message Fault description The local SCTP end is configured as a server. Solution Modify the checksum algorithm at local end with MOD SCTPPARA. Observed in message trace that it receives INIT message.2. but it does not respond. or the connection cannot be established. 7) Generally. 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.Operation Manual . Cause analysis The establishment of listening port fails. Be sure not to affect other SCTP connections. If the configured SCTP checksum algorithm differs at the two ends. Use the command LST MCLNK to check if the client and server ends of the SCTP connection conform to the data plan. If not correctly configured. the sent message from one end to the other will be regarded as invalid and discarded. Summary and suggestions 18-2 . If the SCTP upper layer user provides the maintenance command to query Solution Modify the configured parameters.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center 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.

3. 18. 3) 4) 5) Check if the link state is Active with the command DSP M3LNK. the debugging of M3UA layer completes.1 Background Information An example of a typical M3UA message interaction process is as shown in Figure 18-2 . Otherwise. Use the command LST FECFG to check if the interface IP address of MSOFTX3000 is consistent with the data configuration plan.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 18 Debugging This problem is generally caused by inconsistency of checksum algorithm between local and peer ends. ASP sends ASP UP message to SG.3 FAQ I. ASP sends ASP ACTIVE message to SG. 18.3. Unable to Establish M3UA Link Fault description 18-3 . correct it. and SG responds with ASP UP ACK message. Check if the link set state is Active with the command DSP M3LKS.3. and SG responds with ASP ACTIVE ACK message.2 Debugging Methods Follow the steps below for debugging: 1) 2) Check if the MGW can be pinged successfully. start the SCTP and M3UA message trace and check the message interaction. 18. the M3UA link is activated. Then. If inconsistent. If all states are correct. Figure 18-2 M3UA message interaction process SCTP reports UP message. Check if the destination entity state is Accessible with the command DSP M3DE.Operation Manual .3 Debugging of M3UA 18.

local port number. Check as follows: %%DSP M3LNK: MN=133.CONFIRM=Y. Check if the following parameters are correctly configured: Route context in ADD M3LE Work mode in ADD M3LKS C/S mode.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 18 Debugging The M3UA link state is displayed as Link Unestablished. peer IP address. Cause analysis Cause A: incorrect data configuration. and peer port number in ADD M3LNK Cause B: M3UA link is manually disconnected at client end.%% RETCODE = 0 Operation succeeded M3UA Link Status ---------------- Module Number = 133 Link Number = 0 SCTP Association ID = 4294967295 Lock Information = Unlocked Local Inactive Info = Link Not Inactivated Manually Local Release Info = Release Ungracefully Link Congestion Info = Not Congested Real In Stream Num = 0 Real Out Stream Num = 0 Status = Link Unestablished. as shown below: %%DSP M3LNK: MN=133.%% RETCODE = 0 Operation succeeded M3UA Link Status ---------------- Module Number = 133 Link Number = 0 SCTP Association ID = 4294967295 Lock Information = Unlocked Local Inactive Info = Link Not Inactivated Manually Local Release Info = Release Ungracefully Link Congestion Info = Not Congested Real In Stream Num = 0 18-4 . M3LNK=0.Operation Manual . M3LNK=0.CONFIRM=Y. local IP address.

Operation Manual . Cause C: SCTP abnormality causes M3UA link state to be Link Unestablished. Chapter 18 Debugging If Local Release Info is Release Ungracefully or Release Gracefully.%% RETCODE = 0 Operation succeeded M3UA Link Status 18-5 .CONFIRM=Y.CONFIRM=Y. it means that the M3UA link has been manually released. Cause B: Establish the M3UA link with EST M3LNK at client end as follows: %%EST M3LNK: MN=133. II. Cause analysis Cause A: The M3UA link is locked by the SG. %%DSP M3LNK: MN=132.%% RETCODE = 0 Operation succeeded Cause C: Refer to Chapter 8. M3LNK=0. Refer to Chapter 8. Interworking with MSC Server for details. M3UA Link Displayed as Link DOWN at ASP Side Fault description The M3UA link state is displayed as Link DOWN. M3LNK=0.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Real Out Stream Num = 0 Status = Link Unestablished. as shown below: %%DSP M3LNK: MN=133. Solution Cause A: Modify the data configuration of two ends.%% RETCODE = 0 Operation succeeded M3UA Link Status ------------------------- Module Number = 133 Link Number = 0 SCTP Association ID = 15 Lock Information = Unlocked Local Inactive Info = Link Not Inactivated Manually Local Release Info = Link Not Released Manually Link Congestion Info = Not Congested Real In Stream Num = 0 Real Out Stream Num = 0 Status = Link Down. Interworking with MSC Server for details. M3LNK=0.CONFIRM=Y.

M3LNK=0.CONFIRM=Y.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center ------------------------- 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. as shown below: %%DSP M3LNK: MN=133. M3LNK=0.CONFIRM=Y. --. M3UA Link Cannot Be Activated Fault description The M3UA link state is displayed as Link Inactive. %%REL M3LNK: MN=133.%% RETCODE = 0 Operation succeeded M3UA Link Status ------------------------- 18-6 .%% RETCODE = 0 Operation succeeded Cause B: Manually release and re-establish the M3UA link at the client end. M3LNK=0.END Cause B: SG and AS are abnormal. and vary in state.CONFIRM=Y. M3LNK=0.END %%EST M3LNK: MN=133.END III. it is Link Active at ASP side. For instance. Solution Cause A: Execute the command ULK M3LNK to unlock the M3UA link at SG side. %%ULK M3LNK: MN=133.CONFIRM=Y. but Link Down at SG side.Operation Manual .%% RETCODE = 0 Operation succeeded --.%% RETCODE = 0 Operation succeeded --.

%% RETCODE = 0 Operation succeeded M3UA Link Status ------------------------- Module Number = 132 Link Number = 0 SCTP Association ID = 108 Lock Information = Unlocked Local Inactive Info = Link Inactivated Manually Local Release Info = Link Not Released Manually Link Congestion Info = Not Congested Real In Stream Num = 17 Real Out Stream Num = 17 Status = Link Inactive --.END Cause analysis Cause A: incorrect data configuration. Cause B: The M3UA link is deactivated at ASP end. and locate the fault from the error message. local IP address.END 18-7 . Check if the following parameters are correctly configured: Route context in ADD M3LE Work mode in ADD M3LKS C/S mode. peer IP address. M3LNK=0.Operation Manual . start the M3UA message trace flow.CONFIRM=Y. local port number and peer port number in ADD M3LNK In addition.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center 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 --. %%DSP M3LNK: MN=132.

%%ACT M3LNK: MN=132.CONFIRM=Y. Query the SCTP link state with the command DSP MCLNK. MGW will first send the registration request to the active MSOFTX3000. ensure the intact physical connection between MSOFTX3000 and MGW.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 18 Debugging Solution Cause A: Modify the data configuration based on the error code type in the error message.Operation Manual . modify it of the two ends in the link set table into the same. Follow the steps below for debugging: 1) 2) 3) 4) 5) 6) Firstly. and the equipment is fully operational. Then MSOFTX3000 and MGW both receive HEARTBEAT and HEARTBEAT-ACK message. If not connected.4. The registration completes. check the physical connection between them.END 18. 18-8 . M3LNK=0.1 Background Information When the MSOFTX3000 and MGW are configured. All together there are four messages in both directions. 7) Display the MGW state with the command DSP MGW. When the error code is Invalid Routing Context.%% RETCODE = 0 Operation succeeded --. 18. When the error code is Unsupported Traffic Handling Mode.2 Debugging Methods During the startup of MSOFTX3000. check if the network interface indicator of the WIFM flashes normally. The debugging of MSOFTX3000 is to check if MGW is successfully registered. If all boards are functioning normally.4 Debugging of Mc (H. Start the SCTP and H. If it is Normal.248) 18. who will return the registration successful message. Observe the SCTP interface trace results to ensure the message interaction: MSOFTX3000 receives the INTI message and returns the INTI ACK message. the link state is normal. modify the routing context of the two ends into the same. Then the MGW can fully function under the supervision of MSOFTX3000. the work mode of the two ends are different. MGW will register to it and start the establishment of SCTP link. MGW has registered successfully. Cause B: Manually activate the M3UA link with ACT M3LNK at ASP end as follows.248 trace on messages interacting in the Mc interface.4. trace the interface interaction between the WIFM and the MPPB. if it is valid. Then.

18-9 . The two ends cannot be server or client at the same time. Observe the SCTP and H. Generally.2 Debugging of SCTP. and MGW is configured as a client.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 18 Debugging 8) Observe the H. If inconsistent. analyze the Mc interface message interaction.4. Modify the configuration of MSOFTX3000 with MOD SCTPPARA. Use the command LST MGW to check the client and server ends of the MGW to the data plan. Observed in message trace that the local SCTP server end (MSOFTX3000) receives INIT message. Verify the consistency of Checksum Arithmetic of the local and peer end with LST SCTPPARA. it will register to MSC SERVER. and establish the SCTP link. Check if the physical connection is normal. it does not respond. 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. The following are solutions to some frequently arising issues: Check if the MGW can be pinged.Operation Manual . If it is an SCTP issue. Use DEA MGW to log off the VMGW on MGW. 18. use the command MOD MGW to modify the configuration.3 FAQ The Mc interface is blocked due to physical connection or data configuration errors. If not correctly configured. MSOFTX3000 is configured as a server. correct it. use the command LST FECFG to check if the gateway IP address is correctly configured.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. During the initialization of MGW. Use the command LST FECFG to check if the interface IP address of MSOFTX3000 is consistent with the data configuration plan. Initiate MGW with ACT MGW. If MSOFTX3000 and MGW are not directly connected. refer to section 18. or the connection cannot be established.248 message interaction.

The two in back slots 0 and 2 are active boards. A-1 . This chapter describes the ideas and methods for configuring different entities.6 E1 of slot 0 and No. A.2. 2 and 3. 1. providing E1 interfaces. Figure A-2 tells the hardware configuration of MSOFTX3000. MSOFTX3000 starts with global data configuration from none. so as to provide four channels of 2Mbit/s clock signals and lead them into the active and standby WCKIs.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Appendix A An Example on Global Data Configuration Appendix A An Example on Global Data Configuration A.1 Introduction to the Appendix The example is for the deployment of a new office site after hardware installation. The MSRN/HON numbers are all in LAI number allocation mode.1 Example Description Here. The configurations are as follows: One integrated configuration cabinet. and the corresponding LAI number is “460000003”). and the configuration of service data is rather simple. the postfix index is “1”. The two active WEPIs (No. The MSOFTX3000 locks the line clock of the MGW. One basic frame. and the corresponding LAI number is “460000001”). The WEPI board of the MSOFTX3000 frame must be installed in the back slots 0.2 Configuration Example A.Operation Manual . and the other two in back slots 1 and 3 are standby boards without interface. Subscriber capacity: 150. an example of a single cabinet configuration will be introduced for explanation. excluding networking plan. The MSRN/HON numbers of 3G cell range from 86136000041000 to 86136000041999 (the prefix index of the number segment is “0”. the postfix index is “0”.000. The configuration examples in Chapters 1 to 13 are independent parts of this example. Figure A-1 is the networking diagram of MSOFTX3000 and other functional entities.0 E1 in slot 2) can lock the clock of MGW. which include two number segments: The MSRN/HON numbers of 2G cell range from 86136000040001 to 86136000040999 (the prefix index of the number segment is “0”.

you should select that of WIFM. If it is configured on the WIFM board.Operation Manual .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Appendix A An Example on Global Data Configuration Since the SCTP verification and algorithm of MSOFTX3000 is different from that of MGW.RANAP /IP ISUP. SCP SMC HLR GMLC MAP/TDM MAP/TDM MAP/TDM MAP/TDM MSC Server ISUP/TDM MSOFTX 3000 BSSAP+ /TDM SGSN H. the module number should be that of WIFM. For WBSG. when filling the module number of WIFM/WBSG/WMGC. the integrated configuration of WIFM/WBSG/WMG is adopted. If WIFM.] of command ADD MGW. In this example. you should note the following: Add the corresponding boards and configure the corresponding module number. If it is configured on WBSG.] in command ADD M3UA should be chosen according to the actual configuration of M3UA link. modifications are needed. Therefore. WBSG and WMGC are configured separately. For WMGC board. the parameter [Module No. the WMGC module number should be configured in the parameter [Control Module No.248. the module number should be that of the WBSG. Set the circular broadcast times of the time reporting announcement (TID_0X0002) to 3.BSSAP / TDM SPC MGW IP/TDM MGW (SG) ISUP/TDM PSTN RANAP/AAL2 /ATM BSSAP/TDM RNC BSC Figure A-1 Networking of MSOFTX3000 A-2 .

Other fields are the internal parameters of MSOFTX3000. 0 Frame No.2 Data Collection The data configurations of MSOFTX3000 and its ambient entities or interfaces are as shown in Table A-1 to Table A-13. 0 0 0 0 0 0 0 0 0 0 1 Slot number 0 1 2 3 4 5 10 11 12 13 Location 1 Front/back Front Front Front Front Front Front Front Front Front Front Row 1 Module No. 22 22 23 23 25 25 132 132 102 102 Slot No.2. The shaded parts indicate the parameters that need to be negotiated by both sides or need to inform the peer side. Table A-1 Table of hardware data Frame type Basic frame Board type WCSU WCSU WCSU WCSU WCCU WCCU WIFM WIFM WVDB WVDB Frame No.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Appendix A An Example on Global Data Configuration MGW(CLOCK RESOURCE1) MSC SERVER PSTN BSC RNC 0 Back W E P I W C S U 0 1 W E P I W C S U 1 2 W E P I W C S U 2 3 W E P I W C S U 3 4 MGW(CLOCK RESOURCE2) HLR SCP SMC SGSN GMLC 5 6 W S I U W C C U 4 W C C U W S M U 7 7 W H S C 8 W S I U W S M U 8 9 10 11 12 13 14 15 16 17 18 19 20 M 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 Backplane Front 5 6 9 10 11 12 13 14 15 16 17 18 19 20 Figure A-2 Hardware configuration of MSOFTX3000 A. of mutual aid board 1 0 3 2 5 4 11 10 13 12 Column A-3 .Operation Manual .

Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Appendix A An Example on Global Data Configuration Frame type WCDB WCDB WEPI WEPI WEPI WEPI WCKI WCKI Frame No.200.253 Frame format of E1 interface (DF/CRCR) DF Link type (64Kbit/s. 0 0 0 0 0 0 0 0 14 15 0 1 2 3 13 15 Location Row Front Front Back Back Back Back Back Back Column 103 103 15 14 IP address of FE interface 173. 2Mbit/s) 64Kbit/s Numbers of the frame/ slot/ E1 of the WEPI board.20.132 Balance mode of E1 interface (non-balance mode/ balance mode) Non-balance mode IP address of the router connected with MSOFTX3000 173. 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 . 0/0/6. from which the clock is extracted.Operation Manual .200.20.

2 00.13 2 CRC32 Remote MGW address of Link1 173.200.20.20.Operation Manual .93 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 .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Appendix A An Example on Global Data Configuration 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 Whether support position updating VLR the of / No Whether provide SMMO/SMMT function / Whether support pre-paging / No Yes No / / Whether support call hold Yes Whether support interface No Gs Whether use the reinforced roaming restriction None 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 Transmission layer protocol Checksu m mode Server or client / SCTP connection information / 1 SCTP connectio n number 1 1 SCTP Local WIFM address of Link1 173.

Operation Manual .20. 132 Data 460000003 Signaling point code of SG 1004 IP address of the peer MGW 173.1 32 Route selection code 65535 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 WCSU module number Link set Intra-modul e link number SLC Link type / 22 3 3 0 64 kbit/s Circuit / Trunk route / Prefix Termination ID (the number of the physical circuit from MGW to BSC) 96~127 Office direction 3 Prefix (local office) CIC 0~31 Trunk group 3 Route selection code MGW index 1 Circuit type BSSAP A-6 .200.93 Port of peer MGW 2905 Server/c lient Client 460000003 0004 All Local port 173.20.200.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Appendix A An Example on Global Data Configuration 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.

Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Appendix A An Example on Global Data Configuration Item / 1390752 Configure Data 65535 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.Operation Manual .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 Intra-module link number Link type / 1 1 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 / Trunk route / Prefix / 0~32 Sub-route number 1 Route selection source code 0 1 Circuit type ISUP 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 Intra-module link number Link type A-7 .

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 WCSU module number Link set Intra-module link number Link type / SCCP GT translation / / / 23 Encoding description IMSI GT HLR number MSIDSN 11 Numbering plan ISDNMOV ISDN ISDN 1 Address information 86139 8613907550 000 861390755 64 kbit/s A-8 .Operation Manual .Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Appendix A An Example on Global Data Configuration Item / 22 2 2 Data 1 WCCU/WCS U module number 25 Trunk group 2 80(2/16) 64 kbit/s 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 / 32~63 Sub-route number 2 Route selection source code 0 1 Circuit type ISUP 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.

Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Appendix A An Example on Global Data Configuration 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 Intra-module link number Link type / 12 2 64 kbit/s Table A-10 SMC information table Item Basic information / Signaling point code D02303 NI signaling point National of Data E.Operation Manual .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 WCSU module number Link set Intra-module link number Link type / 23 13 3 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 WCSU module number Link set Intra-mod ule link number Link type / 23 14 16 64 kbit/s A-9 .

A-10 .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] RNC BSC HLR MSC SERVER National reserved National reserved National National [SCMG].Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Appendix A An Example on Global Data Configuration 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. The SSNs configured in other entities are presented in corresponding chapters. [BSSAP/INAP] [HLR] [SCMG] [MSC] [VLR] [SCMG] [RANAP] [BSSAP/INAP] SCP SMC SGSN GMLC National National National National [SCMG] [CAP] [SCMG] [MSC] [SCMG] [GS] [SCMG] [GMLC] [CAP] [GS] Note: The configurations of SSNs configured for the local MSC/VLR are described in Chapter 3 Local Office Data Configuration. The SSN data serves as the global data. [RANAP] [SCMG].Operation Manual .

SN=0. ADD BRD: FN=0. ADD BRD: FN=0. BT=WCSU. ADD BRD: FN=0. ADD BRD: FN=0. SET FMT: STS=OFF. BT=WCDB.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Appendix A An Example on Global Data Configuration A. ADD BRD: FN=0. LOC=BACK. ADD BRD: FN=0. LOC=FRONT. LOF:. LOC=BACK. SN=2. CDPMN=103. BT=WEPI. ADD BRD: FN=0. LOC=FRONT. ADD SHF: SN=0. CN=1. LOC=BACK. BT=WEPI. //Turn off format conversion switch. //Turn off alarm switch. ADD FRM: FN=0. BT=WCKI. LOC=FRONT. LOC=BACK. ASS=3. LOC=BACK. BT=WCSU. LNKT=LINK_64K. ADD BRD: FN=0. Configuring Hardware Data //Set offline. //Configuring CDB function. LOC=FRONT. //Add subrack. CDPMN=103. //Add frame. A-11 . ADD BRD: FN=0. LT=" SX4". BT=WVDB. SN=10. LOC=FRONT. BT=WIFM. PN=1. LOC=FRONT. SN=13. ASS=15. BT=WEPI. SN=0. MN=103. SN=3. CDPMN=103. ASS=11. MN=22. LNKT=LINK_64K. CDPMN=103. PN=2. BT=WEPI. SN=12. SN=0. ADD CDBFUNC: FUNC=MGWR. ADD CDBFUNC: FUNC=TK. SET CWSON: SWT=OFF. BT=WCKI. SN=4. SN=1.3 Data Configuration I. MN=102. ADD BRD: FN=0. SN=2. SN=15.Operation Manual . ADD CDBFUNC: FUNC=CGAP. MN=132. LOC=BACK. MN=23. BT=WCCU. ASS=1. ADD BRD: FN=0. //Add board and module number.2. SN=14. ASS=5. ADD CDBFUNC: FUNC=VDB. ADD BRD: FN=0. RN=1. ASS=13. MN=25.

including MSC.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Appendix A An Example on Global Data Configuration //Configure FE interface information of WIFM. SET INOFFMSC: MSCN=K'8613600004. L1P=L1. B2P=L4. CIPHALG=NOCIPH2G-0&A5_1-0&A5_2-0&A5_3-0&NOCIPH3G-0&UEA1-0. ODBSS=ACOB-1&ICOB-1&ICOBNHP-1&ICB-1&ECB-1&SSAB-1&PSBT1-1&PSBT2-1&PSBT3-1&P SBT4-1. ADD BOSRC: FN=0. E0=DF. and MSRN/HON number allocation. SUPGSIE=YES.Operation Manual .253". VLR and SCMG subsystems. IFUSROAMR=NO. E5=DF. E4=DF. LOT=CMPX.0". E2=DF. IFUSACBUF=NO. MAPVER=PHASE3. EN=6. IFSZCD=NO. SN4=NAT2. E7=DF. NATIONPFX=K'0. NN=YES. ISSSMMT=YES. E3=DF. IFALTMSISA=NO. SN2=NAT2. ADD VLRCFG: MAXUSR=12000. ADD EPICFG: FN=0. IFVLRLU=NO. IFALTMSILU=NO.200. E2=DF. //Configure local SCCP subsystem. CAMELVER=PHASE3. SPF=YES. NNS=SP24. IP="173. E6=DF.20. ADD MAPACCFG: IFIDPROC=NO. E5=DF. EN=0. IFAUTHSA=NO. E0=DF. NPC="CC0004". ADD FECFG: MN=132. MCC=K'460. LNC=K'86.200. NN2S=SP14. WM=AUTO. SN=0.0. ADD BOSRC: FN=0. ISSSMMO=YES.255. B1P=L3. IFCIPH=NO. SN=2. SN3=NAT. VLRN=K'8613600004. SET CKICFG: CL=LEVEL2. SN=2. MCC=K'460. IFSCH=YES. E1=DF. E1=DF. SET OFI: OFN="SX4". E4=DF. E3=DF. MSRNAM=LAI. BM=NONBALANCED. ADD EPICFG: FN=0. E7=DF. MNC=K'00. II. Configuring Office Data //Configure local signaling point information. //Configure E1 and clock data. A-12 . SN1=NAT. NP2C="C04".132". NN2=YES.20. DGW="173. LAC=K'755. INNATIONPFX=K'00. //Configure local mobile office information. L2P=L2. SN=0. MNC=K'00. IFAUTHLU=IFAUTHLUP-0&IFAUTHPLUP-0&IFAUTHIA-0. IFFWD=YES. CTRYCODE=K'86. HONAM=LAI. E6=DF. BM=NONBALANCED. //Configure VLR information. MSK="255. //Configure MAP data.

OPC="CC0004". SPC="CC0004". SSN=SCMG. ECRATE=0. HRAMRR=RATE795-1&RATE740-1&RATE670-1&RATE590-1&RATE515-1&RATE475-1. LST SCTPPARA:. OPC="C04". SSN=SCMG. NI=NAT.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center ADD SCCPSSN: SSNX=0. ADD SCCPSSN: SSNX=2. //Add call source code. //Configure local SCCP GT. //Configure MGW SCTP connection information. CTRLMN=132. SNDDTMFRATE=0. NI=NATB.132". SSNNAME="LOCAL-MSC". SPC="C04". SVRCLIENT=SVR.20. ADD CALLSRC: CSC=0. TCRATE=1. BNCC=IP-1&AAL1-1. ENCT=NSUP.Operation Manual . Appendix A An Example on Global Data Configuration SSN=MSC.200. DETDTMFRATE=0. SPC="CC0004". DEVNAME="MGW1". SLOCIP1="173. TRNST=SCTP. MPTYRATE=0. ADDR=K'8613600004. SPC="CC0004". ADD SCCPSSN: SSNX=1. TRNST=SCTP. A-13 . LST FECFG:. NUMPLAN=ISDN. TONERATE=12. ADD SCCPSSN: SSNX=3. OPC="CC0004". NI=NAT. SSNNAME="LOCAL-NATB-SCMG". BSGMN=132. Adding a MGW //Check the WIFM module number. NI=NAT. //Configure basic information of MGW. III. ADD SCCPGT: GTX=0. RESULTT=LSPC2.200. CPB=TONE-1&PA-1&SENDDTMF-1&DETECTDTMF-1&MPTY-1&IWF-1. GTNAME="LOCAL-MSC". LST MDU:. LNKN=0. IP address and WMGC module number. SET SCTPPARA: CHKSUMTYPE=CRC32. SPC="CC0004".20. SSNNAME="LOCAL-VLR". 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. OPC="CC0004". IWFRATE=1.93". ADD MGW: MGWIDX=1. MGWDESC="MGW1". NI=NAT. ADD MCLNK: MGWIDX=1. TRANSLATETYPE="00". //Modify SCTP check and algorithm (optional). SSN=VLR. BCUID=1. SRMTIP1="173. SSNNAME="LOCAL-SCMG".

MSCN="8613600004". SIG=MTP3.20. RNCID1=4. SSNNAME="RNC4-SCMG". ADD RNC: RNCID=4.Operation Manual . ADD M3DE: DEX=0. OOFFICT=RNC.93". //Add SCCP. =FALSE . DPC1="D04". OSP="C04". DPC="D04". ADD SCCPDSP: DPX=4. //Query the OPC whose NI = NATB LST FECFG:. LSX=0. ADD M3LNK: MN=132. LET=AS. ON="RNC4". DENAME="MgwM3ua". ADD M3RT: RTNAME="ToRNC4". CYCN=3. SAI="4600000030004". global title and service zone of RNC. NI=NATIONBK. NI=NATB. SPC="C04". NI=NATB. ADD M3RT: RTNAME="ToMGW1". OPC="C04". OPC="C04". NI=NATB. MOD TONECFG: INTTID=TID_0X0002. RNCID1=4. DENAME="RncM3ua". OPC="C04". SSN=RANAP.200. Adding a RNC //Add M3UA. SPC="D04". DPC="1004".20. LAICAT=SAI. LSX=0. LSNAME="ToMGW1". PEERPORT=2905 CS=C. ADX=0. LAI="460000003". WM=ASP. LAICAT=LAI. VLRN="8613600004". NI=NATB. DEX=1. LOCIP1="173. SSNNAME="RNC4-RANAP". ADD M3LKS: LSX=0. OPC="C04". DOL=LOW. MSCN="8613600004". //Query MSC/VLR number ADD OFC: OFFICEDIR=4. LAIGCINAME="RNC4". ADD SCCPSSN: SSNX=6. LNKN=0. LENAME="MscM3UA". SPC="D04". SSN=SCMG. ADD M3DE: DEX=1. LST OFI:. NI=NAT2. ADD LAISAI: SAI="460000003". MLAIF DPC="D04". SHAREFLAG=NONE. //Query the local IP address of WIFM ADD M3LE: LEX=0. STPF=TRUE. //Add the office direction. NI=NATB. SSNNAME="LOCAL-RANAP". DPNAME="RNC4". SARL=A-1&B-1&C-1&D-1&E-1&F-1&G-1&H-1&SID-1&RATE0-1. DOA=RNC. LOCNO=65535. NI=NATB. A-14 . ASF=YES. PEERIP1="173. NI=NATB. VLRN="8613600004". OPC="C04". LAIT=HVLR. LSX=0. DPC="D04". ADD LAISAI: LOCNO=65535. ADD SCCPSSN: SSNX=5. DEX=0. SSN=RANAP. LAIGCINAME="RNC4". ADD SCCPSSN: SSNX=4.132". LOCPORT=2905. LAIT=HVLR. OFFICNUM="4". IV. LST INOFFMSC:. DET=SP.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Appendix A An Example on Global Data Configuration //Set playing capability of MGW voice (optional). DEVER=DRAFT10.200. LNKNAME="TO-MGW1". DET=SG.

LSX=3. OOFFICT=BSC. ASPX=3. LAI="460000001". ADD SCCPDSP: DPX=3. RTNAME="BSC-3". SSN=BSSAP/INAP.Operation Manual . MSCN="8613600004". TS=112. Adding a BSC //Query the information. SLC=0. OPC="C04". SSN=SCMG. DPC1="C03". LAIGCINAME="BSC3-LAI". ADD N7LKS: LSX=3. NI=NATB. BSCNM="BSC-3". ADD N7DSP: DPX=3. ADD SCCPSSN: SSNX=9. //Query the type of the signaling link configured on WCSU //Add MTP data. SPC="C04". SSNNAME="BSC-SCMG". LNKNAME="BSC3-1". LST MGW:. //Query the OPC whose NI=NATB LST SCCPSSN: NI=NATB. SPC="C03". LSNAME="BSC-3". LST INOFFMSC:. LNKTYPE=0. V. //Query MSC/VLR number LST MGW:. SSN=BSSAP/INAP. NI=NATB.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center OFFICNUM="4". MSCMN1=22. OPC="C04". OPC="C04". DPNAME="BSC-3". //Query MGW Inex ADD RANMGW: OFFICENO=4. //Add SCCP data. //Add BSSAP data. MLAIF=FALSE. Appendix A An Example on Global Data Configuration //Add access MGW. LST OFI:. DOA=BSC. A-15 . OPC="C04". DPC="C03". NI=NAT2. ADD N7LNK: MN=22. BTSNUM=1. DPC="C03". MGWIDX=1. NI=NATB. ADD LAIGCI: GCI="460000001". DPX=3. //Query MGW index ADD OFC: OFFICEDIR=3. SHAREFLAG=NONE. SPC="C04". ADD SCCPSSN: SSNX=8. ADD BSC: DPC="C03". SPC="C03". ADD N7RT: LSX=3. ON="BSC-3". SSNNAME="BSC-BSSAP". LNKN=3. NI=NATB. SSNNAME="LOCAL-SCMG". RSSC=0. DPNAME="BSC-3". SIG=MTP3. NI=NATB. //Query whether the local end has been configured with SCMG subsystem LST BRD: BT=WCSU. OPC="C04". DOL=LOW. ADD SCCPSSN: SSNX=7.

LSX=11. DPX=11. MOD AIETKC: MN=22. A-16 . ADD N7LKS: LSX=11. SPC="12345". CPN=0. ADDR=K'861390755. SPC="12345". DPC="AA0001". OPC="CC0004". RESULTT=STP1. NI=NAT. ADD AIETG: TG=3.OFFICNUM="3". RESULTT=LSPC2. SCF=TRUE. VI. ADD RANMGW: OFFICENO=3. NUMPLAN=ISDNMOV. SSNNAME="HLR-HLR". ADDR=K'8613907550000. LSNAME="HLR". ADDR=K'86139. ADD SCCPGT: GTX=9. SCIC=0. OPC="CC0004". BCR=SFR1-1&SFR2-1&SFR3-1&SHR1-1&SHR2-1&SHR3-1&DFR-1&DHR-1. OPC="CC0004". EC=112. CS=UNU. SC=96. VII. ADD SCCPSSN: SSNX=11. DPNAME="MSC-1". ADDREXP=INTER. ADD LAIGCI: GCI="4600000010001". OPC="CC0004". RESULTT=LSPC2. MSCN="8613600004". TID=96. TS=48. ADD SCCPGT: GTX=8. SSN=SCMG. NI=NAT. OFFICNUM="3". RTNAME="HLR". LAIT=HVLR. LAICAT=LAI. EC=127. DPC="12345". SLC=0. ADD N7RT: LSX=11.LNKTYPE=0. ADD ACPOOL: CPNO=0. GTNAME="HLR-NUMBER". VLRN="8613600004". TGN="BSC-3". ASPX=11. SSNNAME="HLR-SCMG". SOPC="C04". MGW=1. SSN=HLR. ADD N7LNK: MN=23. MOD AIETKC: MN=22. LAIT=HVLR.Operation Manual . Adding a MSC Server //Add MTP layer data. DPC="12345". GTNAME="HLR-IMSIGT". LAICAT=GCI. DPNAME="HLR". SC=96. CS=UNU. SHAREFLAG=NONE. Adding a HLR //Add MTP layer data.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Appendix A An Example on Global Data Configuration VLRN="8613600004". NUMPLAN=ISDN. GTNAME="HLR-MSIDSN". SDPC="C03". SPC="12345". ADD N7DSP: DPX=1. EC=96. DPNAME="HLR". BSCDPC1="C03". ADD AIETKC: MN=22. //Add trunk data. LNKN=1. NI=NAT. LNKNAME="HLR". SC=112. ADD SCCPGT: GTX=10. CCNDC="86139". ADD IMSIGT: MCCMNC="46000". MGWIDX=1. OPC="CC0004". SPC="12345". //Add SCCP layer data. ADD SCCPSSN: SSNX=10. TG=3. ADD N7DSP: DPX=11. BSCDPC1="C03". ADD SCCPDSP: DPX=11. LAIGCINAME="BSC3-GCI". SPC="12345".

//Configure the office direction directing to MSC. ADD N7TG: TG=1. SC=48. A-17 . SHAREFLAG=NONE. ASPX=1. //Configure the SS7 link directing to MSC. EC=32. NI=NAT. NUMPLAN=ISDN.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Appendix A An Example on Global Data Configuration ADD N7LKS: LSX=1. LNKN=2. LNKNAME="SCP-12". OPC="CC0004". OOFFICT=MSC. SSNNAME="MSC-SCMG". SOPC="CC0004". TG=1. SCIC=0. NI=NAT. RUT=ALL. LNKTYPE=0. GTNAME="MSC1-GT". SSNNAME="MSC1-VLR". OPC="CC0004". TID=32. LSX=1. SDPC="AA0001". DPNAME="SCP-12". RTNAME="MSC-1". RN="MSC-1". ADD N7RT: LSX=1. CT=ISUP. SC=32. SLC=0. ADD SCCPSSN: SSNX=14. R=1. SSNNAME="MSC1-MSC". OPC="CC0004". TGN="MSC-1". ADD N7LNK: MN=23. ADDREXP=INTER. NI=NAT. ADD SCCPGT: GTX=1.Operation Manual . LNKNAME="MSC-1". //Add SCCP layer data. EC=63. LNKN=1. GTI=GT4.TS=80. DOA=MSC. ADI=ALL. DPC="AA0001". ASPX=12. ADD N7TKC: MN=22. ADD SCCPSSN: SSNX=12. ADDR=K'8613500001. SSN=VLR. ADD OFC: OFFICEDIR=1. DPC1="AA0001". LSNAME="MSC-1". SRC=1. MOD N7TKC: MN=22. SPC="AA0001". VIII. OPC="CC0004". ADD RTANA: RSC=1. EC=48. SRN="MSC-1". LSNAME="SCP-12". SLC=0. SIG=MTP3. ISUP=ISUP_F. ADD RT: R=1. //Add SCCP layer data. TMX=0. NI=NAT. ADD SCCPSSN: SSNX=13. ADD N7RT: LSX=12. CS=UNU. LSX=12. ADD N7LKS: LSX=12. NI=NAT. ADD N7LNK: MN=22. RSSC=0. DPX=1. NI=NAT. DPC="D02302". SSN=SCMG. ADD SRT: SRC=1. CS=UNU. ON="MSC-1". OPC="CC0004". TS=48. SPC="AA0001". SSN=MSC. SPC="AA0001". ADD N7DSP: DPX=12. RESULTT=LSPC2. Adding a SCP //Add MTP layer data. MOD N7TKC: MN=22. TP=ALL. SCF=TRUE. SC=32. SR1=1. O=1. SPC="AA0001". DPX=12. RTNAME="SCP-12". G=INOUT. MGW=1. ADD SCCPDSP: DPX=1. DPNAME="MSC-1". DOL=SAME. LNKTYPE=0.

DPNAME="SMC-13". RESULTT=LSPC2. ADD SCCPSSN: SSNX=18.Operation Manual . SSN=MSC. GTI=GT4. ISSSMMT=YES. SSNNAME="MSC-CAP". OPC="CC0004". SPC="D02303". SSN=CAP. SSNNAME="SCP-CAP". SPC="D02302". NUMPLAN=ISDN. DPC="D02303". ADD SCCPSSN: SSNX=17. GTNAME="SMC GT".Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Appendix A An Example on Global Data Configuration ADD SCCPDSP: DPX=12. ADDREXP=INTER. SPC="CC0004". GTNAME="SCP-NUMBER ". OPC="CC0004". LNKNAME="SMC-13". LNKN=3. SSNNAME="SCP-SCMG". LSNAME="SMC-13". ADD SCPPARA: SCPPARAIDX=1. //Add SCCP layer data. SPC="D02302". ADD SCCPDSP: DPX=13. SSN=CAP. NI=NAT. NI=NAT. NI=NAT. GTI=GT4. ADD SSPCAPA: SRVKEY=1. SCPADDR=K'8613600012. ADD SCCPSSN: SSNX=16. ADD N7DSP: DPX=13. ADDR=K'8613600013. SLC=0. LSX=13. NI=NAT. OPC="CC0004". ADD N7RT: LSX=13. SSNNAME="SMC-MSC". ADD N7LNK: MN=23. SSPCAPA=IPRA-1&VOICEBACK-1&SPREC-1&VOICEREC-1&TEXTTOV-1. NUMPLAN=ISDN. RESULTT=LSPC2. DPNAME="SMC-13". OPC="CC0004". SPC="D02302". ADDR=K'8613600012. A-18 . //Add SCP data. SSNNAME="SMC-SCMG". Adding a SMC //Add MTP layer data. ADD SCCPGT: GTX=13. CAPVER=2. ADD SCCPSSN: SSNX=19. OPC="CC0004". ADD SCPINFO: SCPADDRIDX=0. MOD MAPACCFG: ISSSMMO=YES. LNKTYPE=0. //Modify MAP configuration parameter table. RTNAME="SMC-13". DPC="D02302". OPC="CC0004". SPC="D02303". NI=NAT. NI=NAT. DPC="D02303". ADD SCCPSSN: SSNX=15. OPC="CC0004". DPX=13. NI=NAT. NI=NAT. DPNAME="SCP-12".TS=112. SRVKEY=1. ADD SCCPGT: GTX=12. SCPADDRIDX=0. SSN=SCMG. NI=NAT. ADD N7LKS: LSX=13. IX. OPC="CC0004". SPC="D02303". DCH=CTNUCALL. SCFID="1". SHAREFLAG=NONE. ASPX=13. SSN=SCMG. SHAREFLAG=NONE.

NI=NAT. LNKNAME="SGSN-14". SSN=GS. ADD SCCPSSN: SSNX=22. ADD N7TKC: MN=25. ADD N7LNK: MN=23. SCF=TRUE. SDPC="BB0002".Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Appendix A An Example on Global Data Configuration X. SHAREFLAG=NONE. SPC="D02304". //ADD the data of the route to PSTN. LSX=14. RN="PSTN-2". EC=64. ADD SCCPDSP: DPX=14.Operation Manual . TG=2. SSN=SCMG. ISUP=ISUP_F. OOFFICT=NATT. DPNAME="PSTN-2". DPX=14. ADD N7TG: TG=2. NI=NAT. SLCS=2. RTNAME="SGSN-14". OPC="CC0004". DPNAME="SGSN-14". CS=UNU. DPC="D02304". DPC="D02304". RSSC=0. MGW=1. DOA=PSTN. ADD N7DSP: DPX=14. SOPC="CC0004". LNKN=16. LNKNAME="PSTN1-2". //ADD the data of the SS7 trunk circuit leading to PSTN. SSNNAME="SGSN-SCMG". O=2. Adding a SGSN //Add MTP layer data. SCIC=32. RUT=ALL. OPC="CC0004". SRN="PSTN-2". ADD N7LKS: LSX=14. //Add SCCP layer data. OPC="CC0004". TMX=0. TS=144. ADD RTANA: RSC=2. NI=NAT. SC=64. SC=64. SSNNAME="MSC-GS". XI. LNKN=2. Adding a PSTN //Add MTP layer data. SSN=GS. ADD SRT: SRC=2. MOD N7TKC: MN=25. SPC="D02304". DPC="BB0002". LNKTYPE=0. ICR=LCO-1&LC-1&LCT-1&NTT-1&ITT-1. ADD SCCPSSN: SSNX=21. R=2. ON="PSTN-2". A-19 . ASPX=14. SIG=MTP3. ASPX=2. ADD N7RT: LSX=2. LSNAME="SGSN-14". CS=UNU. DOL=SAME. SLC=1. EC=80. NI=NAT. SPC="CC0004". ADD N7LKS: LSX=2. ADD N7DSP: DPX=2. SRC=2. OPC="CC0004". ADD OFC: OFFICEDIR=2. ADI=ALL. DPX=2. TS=80. DPC1="BB0002". TP=ALL. OPC="CC0004". CRF=B0-1&B1-1. ADD RT: R=2. ADD SCCPSSN: SSNX=20. SC=80. LSNAME="PSTN-2". LSX=1. ADD N7RT: LSX=14. RTNAME="PSTN-2". LNKTYPE=0. TGN="PSTN-2". TID=64. NI=NAT. G=INOUT. SR1=2. EC=95. ADD N7LNK: MN=22. MOD N7TKC: MN=25. NI=NAT. SLC=0. DPNAME="SGSN-14".

ASPX=15. ADD GMLCCLT: CLTID=K'8613900111. RESULTT=LSPC2. ADDR=K'8613600014. CSA=MLCO. GTNAME="GMLC GT". SPC="D02305". MINL=11. OPC="CC0004". SSN=SCMG.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center SSNNAME="SGSN-GS". ADD N7RT: LSX=15. TS=176. GTI=GT4. ADD N7DSP: DPX=15. CLTID=K'8613900111. //Configure SGSN number. ADD SCCPDSP: DPX=15. LNKTYPE=0.SPC="D02304". ADD N7LKS: LSX=15. MOD MSFP: ID=P106. ICLDTYPE=MS. LSNAME="GMLC-15". RTNAME="GMLC-15". NI=NAT.Operation Manual . MAXL=11. SSNNAME="GMLC-GMLC". NI=NAT. NI=NAT. SSNNAME="GMLC-SCMG". XII. GCI="460000003". DPNAME="GMLC-15". LNKNAME="GMLC-15". PFX=K'139755. ADD SGSNNO: SGSN=K'8613600014. SPC="D02305". ADDR=K'8613600015. ADD SCCPSSN: SSNX=24. ADD ECLLCSCLT: DN=K'8613975500008. ADD SCCPSSN: SSNX=23. DPC="D02305". GTI=GT4. ISEACM=FALSE. SRVDN=K'8613975500008. DPNAME="GMLC-15". ADD GMLC: GMLC=K'8613600015. ADD SCCPGT: GTX=15. LNKN=17. ADD ESRVCAT: EMRSRV=EMG PLC. //Add SCCP layer data. ADD CNACLD: P=1. RESULTT=LSPC1. VAL="2". Appendix A An Example on Global Data Configuration ADD SCCPGT: GTX=14. OPC="CC0004". GMLC=K'8613600015. GAIN=LGN. NI=NAT. RCM=NOC. NUMPLAN=ISDN. DPX=15. OPC="CC0004". CSTP=BASE. SPC="D02305". SSN=GMLC. LSX=15. DPC="D02305". A-20 . MOD MAPACCFG: SUPGSIE=YES. OPC="CC0004". SSN=GS. SLC=0. NUMPLAN=ISDN. ECOS=YES. NI=NAT. //Configure LCS data. Adding a GMLC //Add MTP layer data. ADD N7LNK: MN=23. SHAREFLAG=NONE. GTNAME="SGSN GT".

XIV. number segment allocated by LAI. ADD CNACLD: PFX=K'861390752. ADD MHLAICFG: LAI="460000003". PRESFX=1. SFXE="1999". //Turn on alarm switch. CSTP=BASE. MSRNT=MSRNHON. //Format the data.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Appendix A An Example on Global Data Configuration XIII. ADD NACODE: NAC=K'136. MAXL=11.Operation Manual . //index is 1 for suffix 1000~1999 LST MHSUFFIX:. MAXL=11. ISEACM=FALSE. ICLDTYPE=PS. Configuring basic number analysis //Configure MSRN/HON number allocation. SFXL=4. //MSRN/HON number of 2G cell is 86136000040001~86136000040999. ISEACM=FALSE. CSA=MLCO. SFXS="0001". FMT:. RCM=NOC. CSA=LCO. MINL=6. SFXS="1000". //index is 0 for suffix 0001~0999 ADD MHSUFFIX: ID=1. MAXL=7. RSC=2. ADD CNACLD: PFX=K'861390755. RSC=1. and the cell should be added first. ICLDTYPE=MSRH. IOUTROUTE=YES. ADD CNACLD: PFX=K'8613910. GAIN=LGN. and load data of all modules. and the cell should be added first. CSA=MLC. ADD MHSUFFIX: ID=0. ISEACM=FALSE. Loading preparation //Set online. RCM=NOC. ADD CNACLD: PFX=K'666. LON:. HPFX=K'8613600004. MINL=11. GAIN=LGN. MAXL=11. MINL=11. PRESFX=0. RCM=NOC. SFXE="0999". CSTP=BASE. RCM=CLRC. ISEACM=FALSE. CSA=MLCO. A-21 . GAIN=LGN. //Power off and on. ICLDTYPE=MS. //MSRN/HON number of 3G cell is 86136000041000~86136000041999. SET FMT: STS=ON. CSTP=BASE. SDESCRIPTION="TOPSTN". PFXIDX=0. CSTP=BASE. ADD MHPREFIX: ID=0. ICLDTYPE=MS. SDESCRIPTION="TO MSC-1". MINL=11. MSRNT=MSRNHON. //Configure the data of called number analysis. // list the index relationship between prefix and suffix ADD MHLAICFG: LAI="460000001". PFXIDX=0. GAIN=LGN.

5-1 parameter relationship. 12-2 networking. 5-2 configure data for interworking with SCP example. 6-18 adding SCCP subsystem. 8-7 general procedures. 8-3 networking. 10-5 configure data for interworking with RNC example. 8-2 configure data for interworking with PSTN example. 13-7 general procedures. 6-26 adding A-interface circuit pool. 6-10 adding MTP link. 10-8 networking.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Index Index A associated mode of signaling.Operation Manual . 9-4 networking. 5-25 general procedures. 15-1 circuit identification code. 10-4 parameter relationship. 4-2 relationship between MSC server and MGW. 6-28 adding BSC global indicator. 14-1 parameter relationship. 6-14 adding MTP link set. 7-11 parameter relationship. 15-1 call source code. 6-7 networking. 10-20 general principles. 6-6 configure data for interworking with GMLC example. 14-8 general procedures. 6-32 general procedures. 6-20 negotiating and preparing data. 5-3 networkinge. 12-1 parameter relationship. 7-11 configure data for interworking with MGW example. 6-30 adding A-interface trunk group. 6-13 adding office direction to BSC. 4-1 parameter relationship. 6-21 adding SCCP remote signaling point. 6-9 B BSC C call prefix. 7-7 general procedures. 6-23 adding LAI or CGI. 9-1 configure data for interworking with MSC (MTP) example. 4-3 networking. 14-2 configure data for interworking with HLR example. 7-12 networking. 10-3 configure data for interworking with BSC example. 6-12 adding MTP route. 6-24 adding MTP destination signaling point. 14-3 networking. 9-24 general procedures. 7-19 i-1 . 8-1 parameter relationship. 6-1 parameter relationship. 12-2 configure data for interworking with SGSN example. 12-8 general procedures. 13-3 adding access media gateway. 6-27 adding A-interface trunk circuit. 9-1 parameter relationship. 15-1 call source. 4-14 general procedures. 4-1 configure data for interworking with MSC (ISUP/M3UA) example.

18-9 i-2 . 7-13 MGW. 15-62 configure outgoing number preprocessing data outgoing calling number correlation processing. 15-63 CLIP called correlation processing. 15-22 incoming number preprocessing. 1-3 configure trunk circuit and TID. 15-32 failure processing. 12-4 SGSN. 6-4 connected number. 15-60 bill control. 15-42 calling number analysis.248) FAQ. 15-59 MAP interface number processing. 14-3 HLR. 11-3 networking. 18-3 methods. 2-21 general procedures. 8-5 office data. 1-6 debug M3UA FAQ. 13-2 configure data for interworking with SMC example. 4-3 MSC (ISUP/M3UA). 15-13 number conversion. 11-6 general procedures. 15-56 configure preset data before number analysis call source. 3-4 configure other number conversion data auxiliary number processing.Operation Manual . 15-43 calling feature processing. 9-3 MSC Server(MTP). 2-6 parameter relationship.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center networking. 6-2 configure number analysis data examples. 5-4 SCP. 1-3 configure mobile service data examples. 6-8 equipment data. 15-24 configure interface data. 3-22 general procedures. 13-1 parameter relationship. 15-4 D data collection BSC. 10-8 RNC. 13-3 SMC. 15-40 enhanced route processing. 15-33 call prefix. 11-3 data preparation. 3-2 PSTN. 2-5 configure in service data examples. 11-2 configure equipment data example. 15-64 bill processing information. 16-20 configure MTP link. 2-4 GMLC. 15-47 number initial special processing. 3-4 parameter relationship. 15-38 configure service data. 15-35 Index call authority original called correlation processing. 15-53 outgoing original called number correlation processing. 15-15 configure route selection data call authority check. 15-26 incoming original called number correlation processing. 15-51 trunk group bearer. 15-57 CLIP processing. 15-29 calling feature analysis. 18-3 debug Mc (H. 11-1 parameter relationship. 15-65 configure office data example. 15-49 outgoing number preprocessing. 15-45 service check. 15-55 trunk group bearer index. 17-10 configure incoming call number preprocessing incoming calling number correlation processing.

7-13 adding SCCP DSP. A-3 description. A-24 configuring hardware data. 14-4 GT. 17-7 configuring data for triggering N-CSI DP3. 15-5 incoming number preprocessing data configuration procedures. 17-10 data configuration principles. 15-2 i-3 . A-22 adding a RNC. 2-6 adding subrack. 14-7 adding client GMLC information. 17-10 incoming number preprocessing. 2-11 adding FE port information of WIFM. 17-7 configuring data for triggering DCSI. 2-8 example on global data configuration adding a BSC. 16-12 roaming subscriber type. 14-6 adding GMLC number. 17-7 configuring data for triggering N-CSI DP2. 17-6 managing special number information. A-23 adding a HLR. 18-2 methods.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center methods. 14-4 configuring MTP data. 7-7 GT addressing for communication among SPs. 17-7 configuring data for triggering N-CSI DP4. 2-13 adding rack. 14-1 adding called analysis data. 16-11 LAI grouping information. 14-5 adding emergency call LCS client. A-18 adding a GMLC. 16-13 starting enhanced roaming restriction function. see also GT GMLC. A-16 adding a MSC Server. 15-1 failure source code. A-15 data collection. A-21 configuring basic number analysis. 17-8 configuring data for triggering N-CSI DP12. 15-4 Index G global configuration procedures. 17-9 configuring special intelligent resource capability data. A-20 adding a SGSN. A-17 adding a SCP. A-20 adding a PSTN. 17-7 configuring data in overlay mode. 7-16 adding SCCP subsystem. 18-1 destination signaling point. 2-9 adding CDB function. 15-7 F failure processing. 15-2 forwarded-to number. 16-8 LAI. 18-8 debug SCTP FAQ. 7-2 dialed number set. A-14 configuring office data. A-1 H HLR adding MTP layer data. 7-15 I IN service configuring basic data of local office with SSP function. 14-4 configuring SCCP data. 16-10 equipment data adding board.Operation Manual . 7-14 adding SCCP GT. A-22 adding a SMC. 16-10 roaming restriction user group. 15-3 enhanced roaming restriction configuration description. A-19 adding a MGW. 1-2 Global Title. 7-8 E early ACM.

9-5 MSC (MTP) adding routing information. 9-7 adding M3UA link. 3-14 i-4 . 4-8 setting SCTP checksum algorithm. 9-22 adding SS7 trunk group. 16-4 MSISDN numbering principles. 3-20 adding corresponding relationship between MSC and MSRN. 2-20 general procedures. 4-11 setting tone playing capability of MGW. 6-5 number conversion. 8-7 configuring MTP data. 3-2 L LAI numbering principles. 3-18 adding MSRN/HON suffix. 16-3 load sharing. 9-15 negotiating and preparing data. 2-20 E1 information. 15-6 number analysis and routing data configuration procedures. 2-16 general procedures. cell. 10-2 local office information.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Index adding M3UA link set. 3-2 mutual-assistant nodes. 16-1 location service. 15-8 number analysis preset data configuration procedures. 9-20 adding sub-route. 9-10 adding M3UA local entity. 16-5 setting LAI or CGI/SAI. 8-6 adding SS7 trunk circuit. 2-21 clock reference source. 1-5 using data script. 8-6 configuring SCCP data. 2-19 lock clock reference source through E1 checking clock reference source. 9-18 adding SS7 trunk circuit. 1-4 using MML command. 15-6 number analysis process. 15-3 O office data adding local SCCP GT. 2-15 E1 information. 9-17 adding route analysis data. 16-3 MSRN/HON allocation mode adding corresponding relationship between LAI and MSRN. 2-17 clock reference source. 2-14 WEPI and WCKI. 2-19 loading equipment data. 16-4 setting global title table. 4-4 adding SCTP link to MGW. 17-1 module number. 16-7 setting SCCP GT. 7-5 multiple signaling points. 1-4 modes for triggering in services. 2-14 M MGW adding MGW. 2-21 WEPI and WCKI. 16-2 location update general procedures. 3-21 adding MSRN/HON prefix. 3-19 MTP. 3-15 adding local SCCP subsystem. 16-5 setting local office SCCP subsystem. 10-1 MTP load sharing. 4-12 MML classification of commands. 9-11 N number analysis. 9-9.Operation Manual . 2-4 MSC (ISUP/M3UA) adding M3UA destination entity. 8-6 MSC number. 3-1 MSC/VLR numbering principles. 16-6 lock clock reference source through BITS checking clock reference source. 2-18 clock reference from WEPI. 3-1 location area. 9-6 adding office direction. 9-14 adding route. service area.

10-10 adding route. 15-3 service check. 2-2 SMC.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center adding local VLR information. 16-16 configuring LAI. 13-4 modifying map parameter table. 5-23 adding M3UA destination Entity. 10-12 adding route analysis data. 15-2 route selection source code. 10-1 original called number. 11-4 configuring SCCP data. 5-20 adding RNC office direction. 7-8 R rack number. 16-1 roaming zone code service i-5 . 16-17 configuration description. 13-5 signaling link. 5-6 adding M3UA route. 7-7 SCP adding SCP addressing information. 2-2 Q quasi-associated mode of signaling. 10-15 adding sub-route. 7-1 outgoing number preprocessing. 12-4 configuring SCCP data. 10-3. 1-1 slot number. 13-4 configuring SCCP data. 10-9 SCCP DSP. 3-18 MSRN/HON allocation modes. 3-7 setting local office information. 5-21 adding access media gateway. 10-2 route selection code. 13-1 configuring MTP data. 15-10 adding zone code. 10-14 adding ss7 trunk circuit. 15-3 set MSRN/HON allocation mode general procedures. 12-5 secondary number analysis. 3-9 adding MAP information. 16-17 route and sub-route. 3-5 office direction. 3-17 SGSN. 12-6 adding SCP parameter information. 7-3 situations requiring data configuration. 5-12 adding M3UA link set. 16-19 Index configuring the relationship between ZC and LAI. 11-4 subrack number. 5-10 adding M3UA local entity. 3-17 parameter relationship. 15-4 originating signaling point. 10-3. 10-16 adding ss7 trunk group. 10-10 negotiating and preparing data. 5-19 adding SCCP remote signaling point. 5-15 adding SCCP subsystem. 2-1 RNC adding 3G service area. 13-4 configuring SGSN number. 5-7 adding M3UA link. 12-4 configuring SSP capability. 16-18 starting zone code restriction function. 12-7 configuring MTP data. 13-5 modifying mobile soft parameter.Operation Manual . 5-11 adding RNC global indicator. 15-2 S P PSTN adding office direction. 7-6 SCCP subsystem. 7-4 signaling link set. 7-6 SCCP DSP working mode. 11-4 modifying MAP parameter table. 5-17 negotiating and preparing data. 5-5 roaming services. 7-3 signaling route. 10-11 configuring MTP data. 3-11 setting local mobile network information. 15-6 outgoing number preprocessing data configuration procedures. 11-1 configuring MTP data.

i-6 . see also zone code zone code.Operation Manual . 10-3 trunk group. 10-3 W wildcards. 17-5 trunk circuit.Data Configuration HUAWEI MSOFTX3000 Mobile SoftSwitch Center Index T triggering of IN service by number segment. 17-1 triggering of overlay outgoing intelligent call. 15-2 Z ZC. 16-14 V VLR number. 3-1 i. 17-1 triggering of standard CAMEL 3 IN service.